Digital PDFs

AA-H625C-TC

April 1983

390 pages

Original

14MB

Document:	RSX-11M System Generation and Instaliation Guide
Order Number:	AA-H625C-TC
Revision:	0
Pages:	390
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V4.1_Apr83/2_Operation/AA-H625C-TC_sysgen_198304.pdf

OCR Text

RSX-11M
System Generation
a nrl •nstallat"1on r.u"!f'IA
I I-

I I

•

•I

Order No. AA-H625C-TC

RSX-11 M Version 4.1

digital equipment corporation · maynard, massachusetts

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

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

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

DIBOL
EduSystem
!AS
MASSBUS
PDP
PDT
RSTS

RSX
UNIBUS
VAX
VMS
VT

~amaoma
ZK2246

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

800-258-1710

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

603-884-6660

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

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

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

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

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

CONTENTS

Page
PREFACE

SUMMARY OF TECHNICAL CHANGES

CHAPTER 1
1.1
1.2
1.3
1.4
1.5
1.6
1. 7
CHAPTER 2

INTRODUCTION
WHO IS QUALIFIED TO GENERATE AN RSX-llM SYSTEM?
SYSTEM GENERATION MINIMUM REQUIREMENTS
PLANNING AHEAD • • •
• • • • •
•
EXPERIMENT WITH YOUR NEW SYSTEM
•
EASE-OF-USE FEATURES •
• •
OVERVIEW OF SYSGEN •
• • • • •
SYSGEN TERMINOLOGY • • • • •
• • • •

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

GUIDE TO COPYING THE DISTRIBUTION KITS

2.1
WHAT IS A DISTRIBUTION KIT?
• • • • • • • • • • • 2-1
OPERATING ENVIRONMENTS FOR GENERATING RSX-llM • • 2-3
2.2
2.2.1
Stand~Alone System Generation
• 2-3
On-Line System Generation • • • •
• • 2-3
2.2.2
2.3
COPYING THE DISTRIBUTION KIT • • • • •
• • 2-3
Copying Kits Stand-Alone • • • • • • • • • • • • 2-4
2.3.l
2.3.1.1
The BRU64K System • • • • • • • • • • •
• 2-4
Copying the Big Disk Magnetic Tape Kit
2.3.1.2
Stand-Alone • • • • • • • • • • •
• 2-6
Copying the RC25 Disk Kit Stand-Alone
2.3.1.3
• • 2-9
2.3.1.4
Copying the RK06/07 1600 bpi Magnetic Tape
Kit Stand-Alone • • • • • • • • • • • • • • 2-11
2.3.1.5
Copying the RK06/07 800 bpi Magnetic Tape Kit
Stand-Alone • • • • • •
• • • • • • • • 2-14
2.3.1.6
Copying the RK06/07 Disk Kit Stand-Alone • • 2-17
Copying the RLOl/02 1600 bpi Magnetic Tape
2.3.1.7
Kit Stand-Alone • • • • • • • • • • • • • • 2-20
Copying the RLOl/02 800 bpi Magnetic Tape Kit
2.3.1.8
Stand-Alone • • • • • • • • • • • • • •
2-24
Copying the RLOl/02 Disk Kit Stand-Alone
2.3.1.9
2-28
2.3.2
Copying Kits On-Line • • • • • • • •
2-31
Copying the Big Disk Magnetic Tape Kit
2.3.2.1
On-Line • • • • • • • • • • • • • • • •
2-32
Copying the RC25 Disk Kit On-Line
2-34
2.3.2.2
2.3.2.3
Copying the RK06/07 1600 bpi Magnetic Tape
Kit On-line • • • • • • • • • • • • • • • • 2-35
2.3.2.4
Copying the RK06/07 800 bpi Magnetic Tape Kit
On-Line • • • • • • • •
• • • • • • • • 2-37
2.3.2.5
Copying the RK06/07 Disk Kit On-Line • • • • 2-39
Copying the RLOl/02 1600 bpi Magnetic Tape
2.3.2.6
Kit On-line • • • • • • • • • • • • • • • • 2-41
Copying the RLOl/02 800 bpi Magnetic Tape Kit
2.3.2.7
On-Line • • • • • • • •
• • • •
2-43
Copying the RLOl/02 Disk Kit On-Line • • • • 2-45
2.3.2.8
iii

CONTENTS
Page

CHAPTER 3

STRUCTURE AND CONCEPTS OF SYSGEN

3.1
THE LOGICAL PARTS OF SYSGEN
Phase I
• • • •
•
3 .1.1
3 .1. 2
Phase II • • • • • • • • •
VMR
• • • • • • • • • • •
3 .1.3
. • • •
3 .1. 4
Phase III • • • • • • • • •
SYSGEN INDIRECT COMMAND FILES • • •
3.2
Independent SYSGEN Command Files ••
3.2.1
FORMAT OF SYSGEN QUESTIONS • • • • •
• • • •
3.3
LOGICAL ORDER OF SYSGEN QUESTIONS
3.4
• • • •
Breakpoints • • • •
•
3.4.1
EOS Breakpoints
• • • •
3.4.1.1
EOX Breakpoints
• • • • •
3.4.1.2
Chaining • • • • • •
• •••
3.4.2
SAVED ANSWER FILES • • • • • • • • •
3.5
VARIOUS APPROACHES TO SYSGEN •
3.6
SYSGEN with MCR Inhibited (PREPGEN)
3.6.l
The Standard Function System • • • •
3.6.2
The Autoconf igure Option • • • • • •
3.6.3
What Autoconfigure Does • • • • •
3.6.3.1
Overriding Autoconfigure Results ••
3.6.3.2
3.6.4
Hardware Supported by Autoconfigure
CHAPTER 4
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.8.1
4.8.2
CHAPTER 5
5.1
5.2
5.3
5.4
5.5
5.6
5.6.1
5.6.2

CHAPTER 6
6.1
6.2
6.2.l
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6
6.2.7
6.2.8

• 3-1
• 3-1
• 3-2
• 3-4
3-4
3-5
• 3-5
• 3-5
3-7
• 3-8
3-8
3-9
3-9
3-9
3-11
3-11
3-11

3-16
3-16
3-18
3-19

DETAILS OF SYSGEN PHASE I
PREPARING FOR PHASE I
SETUP SECTION • • • •
TARGET CONFIGURATION SECTION
HOST CONFIGURATION SECTION •
EXECUTIVE OPTIONS SECTION
TERMINAL DRIVER OPTIONS SECTION
SYSTEM OPTIONS SECTION • • • • • • •
PERIPHERAL OPTIONS SECTION •
IC and IS Subsystems
• • • •
IP Subsystems • • • • • •

• • • • • 4-2
• • 4-3
4-10
• • • • 4-20
4-22
• • • • • 4-46
4-56
4-64
4-92
4-96

DETAILS OF SYSGEN PHASE II
PREPARING FOR PHASE II • • • • • • • •
5-2
SETUP SECTION • • • • • • • • • •
• • • • • 5-4
EXECUTIVE TASK-BUILD SECTION • • • •
• • •• 5-8
LOADABLE DRIVER TASK-BUILD SECTION •
• • • • • 5-9
PRIVILEGED TASK-BUILD SECTION
• • • •
5-12
SYSTEM VMR SECTION • • • • • • • •
• •
5-14
Invoking VMR from an On-line Host System •
5-19
Using VMR to Create Partitions for RMS-11
Libraries • • • • • • • • • • • • • • • •
5-19
POSTSYSTEM GENERATION GUIDELINES
DO YOU HAVE A VIRGIN SYSTEM? • • • • • • • • • • • 6-1
STEPS FOR MAPPED TARGET SYSTEMS • • • • • • • • • 6-1
How to Bootstrap the Virgin System • • • • • • • 6-2
How to Make Your Target System Hardware Bootable 6-2
Invoke Phase III to Task-Build BRU • • • • • • • 6-3
How to Recover Space on the Target System Disk • 6-3
Building or Rebuilding RSX-llM Tasks • • • • • • 6-5
Testing Your Target System with UETP • • • • • • 6-5
How to Transfer the Target System to a Different
Type of Disk • • • • • • • • •
• • • • •
6-6
Rebuilding User-Written Tasks
• • • • • • 6-7
iv

CONTENTS
Page
Help Files • • • • • • • • • • • • • • • • • • • 6-7
Multiuser System Setup = = = = = = = = = = = = = 6-8
Establishing System Features with VMR • • • • • 6-9
6.2.11
6.2.12
How to Create a Backup Copy of the Target System
Disk . • • • • • • . • . • • • • • •
6-9
6.2.13
Installing RMS-11 V2.0 • • • • •
6-10
RK06/07 and RLOl/02 Procedures • • • • • • • 6-10
6.2.13.1
6.2.13.2
Startup Command Procedures •
6-11
Error Logging Support • • • •
6.2.14
6-12
6.2.15
Installing Layered Products in the Target
Sys tern • • • • • • • • • • • •
• • • • • •
6-12
6.3
STEPS FOR UNMAPPED SYSTEMS • • •
• • • • • 6-12
6.3.1
Building or Rebuilding RSX-llM Tasks • • •
6-12
6.3.2
How to Bootstrap the Virgin System • • •
6-13
How to Make Your Target System Hardware
6.3.3
Bootable • • • • • • • • • • • • • • • • •
6-13
Invoke Phase III to Task-Build DSC • • •
6.3.4
6-14
How to Recover Space on the Target System Disk 6-14
6.3.5
Testing Your Target System with UETP
6-15
6.3.6
How to Transfer the Target System to a
6.3.7
Different Type of Disk • • • • • • • • • •
6-15
Rebuilding User-Written Tasks
6.3.8
6-17
Help Files • • • • • • • • • •
6-17
6.3.9
6.3.10
Multiuser System Setup • • • •
6-18
Establishing System Features with VMR
6-19
6.3.10.1
How to Create a Backup Copy of the Target
6.3.10.2
System Disk
• • • • • •
• • • • • 6-19
6.3.10.3
Installing Layered Products in the Target
Sys tern • • • •
• • • • • •
• • • • •
6-19
6.2.9

6 .. 2 .. 10

CHAPTER 7
7.1
7.2

DETAILS OF SYSGEN PHASE III
PREPARING FOR PHASE III
• • • • • • • • • • • • • 7-2
PHASE III QUESTIONS • • • •
• • • •
• 7-2

CHAPTER 8

SYSGEN ERROR MESSAGES

APPENDIX A

SAVED ANSWER SYMBOLS

APPENDIX B

HARDWARE BOOTSTRAP PROCEDURES

B.l
B.2
B.3
B.4
B.5
B.6
B.6.1
B.6.1.1

GENERAL BOOTSTRAPPING PROCEDURE • • • • • •
• B-1
MRll-DB PROCEDURE • • • • • • •
• • • • • • B-3
M9301-YA AND M9301-YB PROCEDURE
• • • •
B-3
M9301-YC PROCEDURE • • • • • • • • • • • • • • • • B-4
M9301-YF PROCEDURE • • • • • • •
• • • • • • B-5
M9312 PROCEDURE • • • • • • • • •
• • • B-5
Using M9312 Console Emulator • •
• • • B-6
Push-Button Boot using the M9312 Console
Emulator • • • • • •
• • • B-6
Switch Register Boot using the M9312 Console
B.6.1.2
Emulator • • • • •
• • • • • •
• • B-6
B.7
BOOTSTRAP LOAD PROGRAM FOR THE RLOl/02 AND
RK07 • • • • • • • • •
• • B-8
B.8
BOOTSTRAP LOAD PROGRAM FOR THE TUlO, TElO, OR
TS03 • • • • •
• • B-9

APPENDIX C

RSX-llM DEVICES

CONTENTS
Page
APPENDIX D
D.l
D.2
APPENDIX E
E.l
E.2
E.3
E.3.1
E.3.2

FUNCTIONS IMPACTING POOL (DYNAMIC MEMORY}
COMMON FUNCTIONS
REAL-TIME FUNCTIONS
ADDRESS AND VECTOR ASSIGNMENTS
AUTOCONFIGURE DEVICE SUPPORT
• • • •
FLOATING ADDRESS ASSIGNMENT ALGORITHM
FLOATING ADDRESS WORKSHEET •
• •
Worksheet Format • • • • •
Worksheet Instructions • •

APPENDIX F

DISTRIBUTION KIT CONTENTS

F.l

DIRECTORY LISTING OF THE
RSXM35 • • • • • •
DIRECTORY LISTING OF THE
RSXM35 • • • • • •
CLISRC • • • • • •
DIRECTORY LISTING OF THE
RSXM35
EXCPRV •
RLUTIL •
MCRSRC •
HLPDCL • •
• • • •
RMSV20
• • • •

F .1.1

F.2
F.2.1
F.2.2
F.3
F.3.1
F.3.2
F.3.3
F.3.4
F.3.5
F.3.6

• • • • • • D-1
• D-4

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

•
•
•
•

E-1
• E-2
• E-3
• E-3
• E-4

BIG DISK DISTRIBUTION KIT F-1
• • • • • • • • • F-1
RK06/07 DISTRIBUTION KIT F-29
• • • • • • • • • • • • F-29
• • • • • • • • • • • • F-39
RLOl/02 DISTRIBUTION KIT F-60
• • • • • F-60
F-65
F-71
• • • • • • • • •
F-73
• •
• • • •
F-82
• • • • • • • • • • • • F-91

INDEX

EXAMPLES
EXAMPLE 3-1
3-2
4-1
5-1
7-1
E-1
E-2
E-3

Sample Autoconf igure Output • • • • • • • • • • 3-1 7
Autoconfigure Remarks and Meanings • • • • • • • 3-18
Annotated Terminal Output from SYSGEN Phase I
• 4-101
Annotated Terminal Output from SYSGEN Phase I I • 5-20
Annotated Terminal Output from SYSGEN Phase III • 7-6
Floating Address Worksheet {Configuration 1)
E-5
Floating Address Worksheet (Configuration 2}
• E-6
Blank Floating Address Worksheet • • • • • • •
E-7

FIGURES
FIGURE

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

Examples of External Labels for RSX-llM Magnetic
Tapes and Disks • • • • • • • • • • • • • • • • • 2-3
Processing Steps in SYSGEN Phase I • • • • • • • • 4-1
Logical Flow of SYSGEN Phase I I . . • . • . . . . 5-3
Partition Structure on Mapped Systems • • • • • 5-15
Partition Structure on Unmapped 16K through 24K
Systems • • • • • • • • • • • • • • • • • • • • 5-17
Partition Structure on Unmapped 24K through 28K
Systems
• • • • •
• • • • 5-18
Logical Flow of SYSGEN Phase III • • • • • • • • • 7-1

CONTENTS

Page
TABLES
TABLE

2-1
3-1
3-2
3-3
3-4
4-1
4-2
4-3
B-1
B-2
8=3

B-4
B-5
B-6
C-1
E-1

Inventory of the Six RSX-llM Distribution Kits •• 2-2
Phase I Sections and Functions • • • • • • • •
3-2
Phase II Sections and Functions • • • • • • • • • 3-3
Options Included in the Standard Function System 3-13
Hardware Supported by Autoconfigure • • • • • • 3-20
PDP-11 Processor Memory Sizes for RSX-llM/RSX-llS 4-12
Peripheral Devices Supported by RSX-llM • • • • 4-18
Standard Line Printer Devices • • • • • • • • • 4-79
Summary of Hardware Bootstrap Addresses • • • • • B-2
Device Codes for M9301-YA and M9301-YB Bootstraps B-3
Device Codes for the M9301-YC Bootstrap • • • • • B-4
Device Codes for the M9301-YF Bootstrap
B-5
Device Names and Mnemonics • • •
• • • • • • B-7
RLOl/02 and RK07 Load Routines •
• • • • • • B-9
C-1
RSX-llM Devices • • • • • • • •
• • E-2
Autoconf iguration Device Support •

vii

PREFACE

MANUAL OBJECTIVES
The goal of this manual
is
to provide you with the information
necessary to successfully generate an RSX-llM operating system.
Included in this manual are conceptual descriptions of the system
generation procedure (SYSGEN), detailed information on how to use the
distribution media to generate your RSX-llM system, and an explanation
of each of the SYSGEN questions.

INTENDED AUDIENCE
This manual is primarily directed toward system managers
(that
is,
those responsible for
tailoring and maintaining RSX-llM systems).
Although RSX-llM V4.l provides options that can make the system
generation procedure considerably easier, most of the information in
this manual requires the reader to be familiar with RSX-llM and
its
component tasks.

STRUCTURE OF THIS DOCUMENT
This document details several major enhancements to the system
generation procedure.
Before you begin generating your RSX-llM
system, carefully read Chapter 3.
Chapter 1 is a general introduction to RSX-llM system
installation.

generation

and

Chapter 2 is a description of the RSX-llM distribution media.
It also
contains step-by-step instructions for copying the magnetic tape and
disk media.
Chapter 3 is a conceptual discussion of the RSX-llM system generation
procedure.
It describes the structure of SYSGEN as well as specific
SYSGEN options that make it easier to generate your system.
Chapter 4 explains each of the questions in SYSGEN Phase I.
Chapter 5 explains each of the questions in SYSGEN Phase II.
Chapter 6 describes the various procedures
after you have generated your system.
r'h;::int-t=::>r
~·--..----

that

you

should

explains each of the questions in SYSGEN Phase I I I .

PREFACE
Chapter 8 supplies explanations of the various system error messages.
Appendix A defines the saved answer symbols which SYSGEN creates based
on your responses to questions.
Appendix B provides information for hardware bootstrapping your PDP-11
processor.
Appendix C is a table of devices and the associated
and controllers.

device

mnemonics

Appendix D is a list of the tasks and system functions impacting
Dynamic Storage Region (DSR), also known as pool space.

the

Appendix E contains detailed information on floating Control Status
Register
(CSR) and vector addresses, and defines the DIGITAL standard
hardware configuration algorithm.
Appendix F is a directory listing of specific contents of each
of the distribution kits.

volume

ASSOCIATED DOCUMENTS
The RSX-llM Documentation Directory briefly describes all of the
manuals in the RSX-llM documentation set and provides a brief synopsis
of the contents of each manual. The following lists those manuals
most closely associated to the purposes of this document.
RSX-llM/M-PLUS System Management Guide
RSX-llM/M-PLUS Executive Reference Manual
RSX-llM/M-PLUS MCR Operations Manual
RSX-llM/M-PLUS I/O Drivers Reference Manual
RSX-llM/M-PLUS Task Builder Manual

CONVENTIONS USED IN THIS DOCUMENT
The following conventions are used in this manual:
Convention

Meaning

Red Ink

In examples of commands you enter and system
responses, all output lines and prompting
characters that the system prints or displays
are shown in black letters. All the lines
you type are shown in red letters.
The symbol CTRL/x indicates that you must
press
the
key
labeled CTRL while you
simultaneously
press
another
key,
for
example, CTRL/C, CTRL/O, CTRL/Y.

A reverse number is a white number printed in
a black circle. These numbers key a part of
an example to the text that explains that
part of the example.
The reverse number
appears both in
the
example
and
the
explanation.

SUMMARY OF TECHNICAL CHANGES

The following new options and features have been added to the
system generation and installation procedure:

RSX-llM

•

SYSGEN must be performed on a mapped host system with at least
64K words of memory.

•

SYSGEN no longer supports the RK05 distribution kit.

SYSGEN now supports SPM-llM.

•

SYSGEN now supports RA60 removable media and RA81 fixed
under the UDA50 hardware controller.

•

SYSGEN now supports RC25 fixed/removable media.

•

SYSGEN now supports RD51 fixed media and RX50
drives under the RQDXl hardware controller.

floppy

disk

•

SYSGEN now supports TSV05 and TU80 magnetic tape drives
the TSll hardware controller.

under

SYSGEN now supports the LNOl,
LP07,
LP26,
printers under the LPll hardware controller.

line

•

SYSGEN now supports the DHVll hardware controller.

•

The distribution kits
system.

•

The default for the target system configuration is now mapped.

•

SYSGEN will always install the V4.l TKB from the
kit with the task name ••• TKL.

•

SYSGEN now allows DU devices (RA60, RC25, and RX50 only)
chosen as the crash dump device.

•

In an RLOl/02 PREPGEN, the EXCPRV disk is mounted by SYSGEN.

•

The RSX-llM magnetic tape distribution kits are now in BRU
format.
Also, BRU is now used to copy all the RSX-llM V4.l
distribution kits.

•

RMS-11 V2.0 is now included in the RSX-llM
kit.

now

only

contain

and

LP27

mapped

V4.l

media

baseline

distribution
to be

distribution

CHAPTER 1
INTRODUCTION

The RSX-llM system generation
procedure
(SYSGEN}
offers
the
flexibility, through selection of specific hardware and software
options, to produce an RSX-llM system specifically tailored to the
requirements of a given user environment.

1.1

WHO IS QUALIFIED TO GENERATE AN RSX-llM SYSTEM?

Generating RSX-llM requires a fairly sophisticated understanding of
the operating system. If you have never generated an RSX-llM system,
you may find the system generation procedure overwhelming. There is a
lot to know and decide. For example, when selecting SYSGEN options,
you should be familiar with the trade-offs between memory and pool
(pool and other terms are defined in Section 1.6). Some information
concerning the amount of memory used by specific options is present in
this manual.
However, because hardware and software options can be
combined in so many different ways, it is impossible to prescribe a
simple formula to satisfy any given situation. Therefore, the task of
generating an RSX-llM system is generally reserved for
system
managers, system programmers, and that general class of user with
sufficient understanding of the operating system to make the necessary
judgements.

1.2

SYSTEM GENERATION MINIMUM REQUIREMENTS

In order for you to perform an RSX-llM V4.l SYSGEN, your
has to conform to two SYSGEN minimum requirements:

1.3

your

host

system

host

system

•

Your host system must be mapped. That is,
must support memory management hardware.

•

Your host system must have at least 64K words of memory.

PLANNING AHEAD

Before beginning the system generation procedure, you should spend
some time planning for it. Read through the manual (in particular,
Chapters 3 and 4) to familiarize yourself with the options you want.
Be sure that the options you select are compatible and that they make
sense; make sure that your hardware supports adequate memory to
accommodate the operating system you generate.
Careful planning before you generate your system
through the procedure more quickly and easily.

1-1

allows

you

INTRODUCTION
Calculations for things such as disk swapping intervals, round-robin
scheduling
intervals,
and
swapping
priorities
require
some
experimenting with the system.
If you are generating an RSX-llM
system for the first time, you may find such calculations difficult to
make.
However, each option comes with a default response that you may
select (see Chapter 3 for further explanation). Selecting the default
response allows you to postpone or avoid calculations such as those
mentioned above, until
it can be determined that the defaults are
inappropriate for your system.
For example, you should determine the amount of pool space required
for your system. Without enough pool the system response time may be
slow; with too much pool, you may be wasting valuable memory.
Appendix D may help you to make those calculations. By default,
SYSGEN allocates the maximum amount of pool space available to a
mapped system after you have selected all the hardware and software
options. Therefore, you may decide to let SYSGEN calculate your pool
size and wait until you have time to experiment with your new system
before making any adjustments.

1.4

EXPERIMENT WITH YOUR NEW SYSTEM

The first system you generate may not be optimal for your specific
needs.
Experiment with it to see how it performs.
You may find it
necessary to make some adjustments by adding memory or reducing
options.
All of this can be done gradually as you become more
familiar with your system and understand how various system features
affect one another.

1.5

EASE-OF-USE FEATURES

Some RSX-llM users may want to generate their system as quickly and
easily as possible and attend to system tuning adjustments afterward.
The RSX-llM V4.l system generation procedure contains two options that
can ease your
involvement in the system generation procedure and
minimize the number of questions you must answer.
•

The Autoconf igure option
automatically
determines
your
hardware configuration, and can eliminate the need to answer
most or all of the SYSGEN questions concerning your target
configuration and peripheral devices.

•

The Standard Function System option produces a mapped RSX-llM
operating system with the maximum number of software options,
including support for layered products.

Further information on the Standard Function System and
can be found in Chapters 3 and 4.

1.6

Autoconf igure

OVERVIEW OF SYSGEN

There are three phases to SYSGEN.
Phase I requires you to select the
hardware
and
software
options for your target system.
That
information is then used to assemble the Executive, device drivers,
and other parts of the system.
Phase II is dedicated to task building, or linking, your Executive,
device drivers, privileged and system tasks, and creating a system
image file.

1-2

INTRODUCTION
Phase III is dedicated
nonprivileged tasks.

task

building

selected

privileged

and

SYSGEN questions appear on your terminal based upon how you answer the
preceding SYSGEN questions;
they do not appear in strict numeric
order.
Also, the three phases of SYSGEN are not completely independent from
one another. For example, although you may invoke Phase III of SYSGEN
without having to go through an entire system generation, you cannot
invoke Phase II without having gone through Phase I. Phase II
requires input created during Phase I.
Read Chapter 3 for more
information on the structure and concepts of SYSGEN.

1.7

SYSGEN TERMINOLOGY

This section defines some terms used in this manual. The purpose of
defining these terms here is to familiarize you with them before you
begin generating your RSX-llM system. For more information on a given
term consult the RSX-llM Information Directory and Master Index.
Executive
The Executive is the software core, or kernel, of the RSX-llM
operating
system.
It is responsible for controlling such
activities as resource allocation, multi-user protection, and
inter-task communications.
In general the Executive monitors,
controls, and services system level activity.
It provides a
relatively machine independent environment in which to develop
and run user applications.
The Executive resides in low memory. On systems supporting the
memory management option, the Executive is permanently mapped by
the KERNEL mode mapping registers ranging from KERNEL virtual
address
O
up
to KERNEL virtual address 120000(8).
The
Executive's permanently mapped address space
contains
the
Executive code, the I/O device data base, and the system pool.
pool
Pool (also known as the Dynamic Storage Region, or DSR)
is a
contiguous area in memory, allocated by the Executive and used as
a work space for storing system data structures such as system
lists and control blocks.
Pool is included at the top of the
Executive's permanently mapped address space in memory. The size
of pool must be sufficient to handle all of the dynamic storage
requests of the system. By default, SYSGEN extends the mapped
system Executive to its maximum size to create the largest
possible pool space.
FCS (File Control Services)
FCS is a set of routines that can be used in tasks to read and
write files.
FCS provides a set of macros to simplify the user
interface to the system I/O structures. The FCS routines serve
as an intermediary between tasks and an ACP or a device driver.
Task input to FCS is in the form of data structures and calls to
the FCS subroutines. The output from FCS is QIO directives for
an ACP or device driver to process. FCS provides a convenient
and device independent interface for a task, rather than having
the task issue QIOs directly.

1-3

INTRODUCTION
ACP (Ancillary Control Processor)
An Ancillary Control Processor
(ACP)
is a privileged program
interfacing between a device driver and the Executive or a user
program.
An ACP acts as part of the I/O processing for a
particular device or group of devices and is commonly requested
to process an I/O request that must be translated to one or more
simpler
I/O requests that a device driver can process.
The main
difference between an ACP and a device driver
is that an ACP
services a class of devices
(such as disks), where a driver
services a specific device type (such as RL02s) • An ACP becomes
associated with a device through either a MOUNT command or by
some other special, privileged interface associated with the ACP.
Files-11 ACP
Files-11 ACP is a special ACP supplied with RSX-llM that,
like
other ACPs, becomes associated with a device or devices by the
MOUNT command. Once associated with the device,
it intercepts
certain I/O requests issued by programs as determined necessary
by the I/O system in the Executive.
In particular, the Files-11
ACP handles requests to create files, to extend files, to delete
unneeded files, and to access files.
Files-11 ACP is responsible
for the maintenance of the volume structure of a Files-11 disk,
including the directory structure, storage
allocation
and
deallocation, and file security.
driver
A driver is a set of routines called by in the Executive in
response to I/O requests from user programs.
One of those
routines
is the interrupt service routine, whose
specific
function is to service device interrupts.
(See the definition of
a vector.) The driver translates I/0 requests
into instructions
directed to a specific device type.
A driver is actually an
extension of the Executive;
it provides the software interface
between a user and the device itself.
Each type of peripheral device has its own driver.
Because
driver code may take substantial space in memory, you have the
option in SYSGEN to make specific drivers memory resident or
loadable~
Refer to the RSX-llM Guide to Writing an I/O Driver
for a full discussion of drivers.
CSR (Control and Status Register)
Every peripheral device has a unique address on the communication
bus (UNIBUS or QBUS). When addressing a device, you are actually
addressing a set of registers that communicate with the device.
One of the registers is called the CSR.
interrupt
An interrupt is the mechanism whereby the various external
hardware subsystems communicate a need for software servicing.
vector
Every device corresponds, through the system hardware,
to a
unique two-word location in the low end of memory called a
vector.
(The memory locations from 0 through 776 are the vector
areas.)
Each vector stores the PS (processor status word) and PC
(program counter) of the interrupt service routine for a specific

1-4

INTRODUCTION
device. When a device interrupts the CPU,
the CPU saves the
current PS and PC on a stack and loads the PS and PC from the
device's vector.
The address in the new PC points to the
interrupt service routine.
Not all vectors are assigned to peripheral devices.
Some are
reserved for software interrupts.
For instance, execution of the
TRAP instruction causes an interrupt where a new PS and PC are
loaded from the vector reserved for use only by the TRAP
instruction.
In addition, there are what is known as "floating vectors."
Floating vectors are those addresses from location 300 through
location 776~
The assignment of devices to those vectors is left
to the discretion of the system manager and the field service
representative.
Generally,
floating vectors are
used
for
assigning multiple devices of a given type that require more than
one controller.

hardware bootstrap
A hardware bootstrap is a process whereby a user
initiates a
software
(RSX-llM)
system startup by using the console switches
and/or the console terminal to instruct the bootstrap ROM to load
the hardware bootblock record from an input device into memory.
The bootblock record contains the code to load the system image
into memory.

software bootstrap
A software bootstrap is a process whereby a privileged user
initiates a new software system startup from an already running
system. Software bootstrapping requires the use of the MCR BOO
comrnanQ.
(See
the
RSX-llM/M-PLUS MCR Operations Manual,
particularly the SAVE and BOOT commands, for details on software
bootstrapping.)
Any valid RSX-llM system image can be software
bootstrapped.

mapped system
PDP-11 processors supporting memory management hardware are known
as mapped systems.
That is,
the memory management hardware
converts virtual addresses to physical addresses in memory.
In
addition the memory management hardware makes it possible to
access and address more memory by mapping 16-bit addresses to
virtual 16-bit, 18-bit, or 22-bit locations.
For contrast, see
the definition of an unmapped system.

unmapped system
An unmapped system is a system on which a virtual address
corresponds exactly to a physical address.
For example, the
virtual address 125003 corresponds to the physical location
125003 in memory.
Unmapped systems support up to 30K words of
memory, with 2K words left over to map the I/O page -- the extent
of 16-bit addressing.

baseline system
The baseline system is the stand~alone RSX-llM system included as
part of the distribution kit.
It contains only those software
components necessary for you to generate an RSX-llM system.

1-5

INTRODUCTION
target system
The term target system refers to the operating system produced by
the
system
generation procedure as well as the hardware
configuration on which it is intended to run.
System generation
may take place on the target system computer or on a different
computer (see "host system").
In either case, RSX-llM system
generation must be done using a PDP-11 processor.
host system
The host system is that system on which you perform an RSX-llM
system generation.
It may be the same hardware on which you
intend to run your new target system, or it may be a separate
configuration that is more convenient for system generation.
on-line system
An on-line system is an operating environment that shares
resources with other processing or development work in progress.
In the context of SYSGEN, generating RSX-llM on line means that
you are using host system software other than the baseline system
provided on the distribution kit.
stand-alone system
A stand-alone system is an operating environment that
is
dedicated to a single activity.
In the context of SYSGEN,
generating RSX-llM stand alone means that you are using the
baseline system provided on the distribution kit.
virgin system
The term virgin system refers to the state of the system image
after VMR has executed SYSVMR.CMD and before the system has been
saved.
(Refer to the SAVE command in the RSX-llM/M~PLUS MCR
Operations Manual.)· The virgin system should only be bootstrapped
on the target system that it was configured for during the system
generation process.

1-6

CHAPTER 2
GUIDE TO COPYING THE DISTRIBUTION KITS

This chapter is a discussion of the distribution kits containing
RSX-llM Version 4.1.
It describes each type of kit and how to use it
to prepare for the system generation procedure.

2.1

WHAT IS A DISTRIBUTION KIT?

RSX-llM distribution kits are the magnetic tape or disk media
containing the source, object,
task, and command files needed to
generate your RSX-llM system.
There are four general types of
distribution kits:
•

Big disk tape distribution kits

•

RC25 disk distribution kits

•

RK06/07 distribution kits

•

RLOl/02 distribution kits

The term "big disk" distribution kit applies to all distribution kits
(tape only)
that are supported on a single-disk volume (RP04/05/06,
RM02/03/05, RM80/RP07, and RA60/80/81/RC25).
Table 2-1 describes each type of kit.
Included in the table are the
number of magnetic tapes or disk volumes for each separate kit.
Each
distribution kit contains either magnetic tapes or disks; depending on
the type of kit ordered.
Check the contents of your distribution kit against the information in
Table 2-1 to ensure that you have a complete kit.
Each distribution kit contains an RSX-llM operating system known as
the "baseline system." The baseline system contains just enough
features to allow you to perform a system generation.
There is a
mapped baseline system (on disk volume or magnetic tape backup set
RSXM35) on each kit in UFO [1,54].
Regardless of whether your distribution kit is on magnetic tape or
disk, you can use only disk media to perform an RSX-llM system
generation.

2-1

GUIDE TO COPYING THE DISTRIBUTION KITS
Table 2-1
Inventory of the Six RSX-llM Distribution Kits
Number of
Tapes2

Tape
Length

Tape
Density

RSXM35

l
2

2400 ft
2400 ft

1600 bpi
800 bpi

RM02/03/05
RM80/RP07

RSXM35

l
2

2400 ft
2400 ft

1600 bpi
800 bpi

RA60/80/81
RC25

RSXM35

l
2

2400 ft
2400 ft

1600 bpi
800 bpi

RC25

RSXM35

RK06/07

RSXM35
CL IS RC

l
2

2400 ft
2400 ft

1600 bpi
800 bpi

RSXM35
EXCPRV
RLUTIL
MCRSRC
HLPDCL
RMSV20

l
2

2400 ft
2400 ft

1600 bpi
800 bpi

Kit Type

Backup
Set Names

RP04/05/06

RLOl/02

Number
of Disksl

1. Except for the RC25 disk distribution kit, the
distribution kits are distributed on magnetic tape only.

big

disk

2. Each tape distribution kit also includes a stand-alone BRU tape.
(See Section 2.3.)
Each volume in your distribution
identifying the following:

kit

bears

physical

label

•

The specific software version number (such as RSX-llM V4.l)

•

The type of distribution kit (such as RLl/2)
NOTE
Because of character string limitations
on the physical tape label, the type of
distribution kit specified on the label
omits
zeroes.
The RLOl/02 kit is
represented as RLl/2, and so forth.

•

The volume ID (such as RSXM35)

•

The number in the sequence (such as 1/2 -- the first disk in a
set of two)

•

Additional information for tape that specifies the file format
(such as BRU) and the tape density (such as MT:l600)

Figure 2-1 shows an example of an external, physical magnetic tape
label and an external, physical disk label for the RSX-llM V4.l
distribution kits.

2-2

GUIDE TO COPYING THE DISTRIBUTION KITS

BB-L9528-BC

AM-D519D-BC
RSX11M V4.1 !D:RSXM35

RK6

1/2

Digital Equipment Corparation
ZK-1110-82

Figure 2-1 Examples of External Labels
for RSX-llM Magnetic Tapes and Disks

2.2

OPERATING ENVIRONMENTS FOR GENERATING RSX-llM

To perform an RSX-llM system generation, you must have an operating
system to control the host computer's resources.
(The host computer
is the computer on which you are generating your new RSX-llM system.)

2.2.1

Stand-Alone System Generation

You may generate your system by using an RSX-llM V4.l baseline system.
This is known as a "stand-alone" system generation. The process
requires that you hardware bootstrap the baseline disk (RSXM35)
to
load
the baseline system into memory.
Further information on
stand-alone system generation appears in Chapter 4.

2.2.2

On-Line System Generation

You may generate your system by using a host computer that is
currently running an RSX-llM V4.0 or V4.l system other than the
baseline system. This is known as an "on-line" system generation.
This procedure requires specific logical device assignments before you
begin the system generation. Further information on on-line system
generation appears in Chapter 4.

2.3

COPYING THE DISTRIBUTION KIT

Before you use your distribution kit to generate an RSX-llM system,
first make a copy of the kit. The original distribution kit then
serves as a backup in case anything should happen to corrupt the
contents of the distribution kit copy during the system generation
process. The distribution kit also serves as base software against
which you can apply subsequent Autopatch updates.
(If you need to
apply an Autopatch to your system or to layered products: you should
do it before invoking SYSGEN Phase I.)

2-3

GUIDE TO COPYING THE DISTRIBUTION KITS
If you have a magnetic tape distribution kit, you must copy the
distribution kit to a blank disk that will be your target system disk.
Since you must copy a magnetic tape distribution kit to disk before
invoking SYSGEN,
the distribution tape may serve as the permanent
backup copy.
If you have a disk distribution kit, you must make a copy
distribution kit that you can use as the target system disk.

the

Details for copying each particular distribution kit appear in each of
the following sections.
Section 2.3.1 tells you how to copy any of
the distribution kits stand-alone using the BRU64K and baseline
stand-alone systems.
Section 2.3.2 tells you how to copy any of the
distribution kits using a host computer already running RSX-llM.
Find
the section that applies to your distribution kit and follow the
instructions for copying the kit.

2.3.l

Copying Kits Stand-Alone

The following sections describe the procedures used to copy each type
of distribution kit using the BRU64K and baseline stand-alone systems.

2.3.1.1 The BRU64K System - Each tape distribution kit includes a
600-ft tape labelled BRU64K.
The BRU64K system is a limited-feature,
memory-resident RSX-llS system.
It is used only to prepare the target
system disk and to copy the magnetic tape distribution kit.
The
baseline system contained on the target system disk is used as the
operating environment for stand-alone system generations.
Included with the BRU64K system are copies of the following utilities:
•

Backup and Restore Utility (BRU)

•

Bad Block Locator Utility (BAD)
NOTE
Since BRU and BAD share the same buffer
space, the two utilites cannot be run
simultaneously.

Also included is a special-purpose configuration program called the
RSX-llM/M-PLUS Stand-Alone Configuration and Disk Sizing Program
(CNF). CNF allows you to change the default device CSR (/CSR=nnnnnn),
the default device vector (/VEC=nnn), and the default formatter number
for MF:- and MM:-type magnetic tape devices
(/FOR=n)
in the BRU64K
system.
The BRU64K system expects your devices to be at the following
CSR and vector addresses:
Device

Formatter
Number

CSR

Vector

,~r~nn

i101uu

254

DK
DL

177404
177440

220
160

2-4

GUIDE TO COPYING THE DISTRIBUTION KITS

Device
OM
DP
DR
DU
MF
MM
MS
MT

Formatter
Number

0
0

CSR

vector

177440
176714
176300
172150
175400
172440
172522
172522

210
300
150
154
260
224
330
320

If your devices are at different CSR and vector addresses or if your
MF:-- or MM:-type magnetic tape drive device is on a different
formatter number, you must change the values in BRU64K.
You can do
this by using the following CNF switches when you enter the device
name:
/CSR=csr address
/VEC=vector address
/FOR=formatter number
The vector addresses that BRU64K expects for DR, MS, and MT are
nonstandard.
The CSR address that BRU64K expects for DR is also
nonstandard.
If you are using one of these devices as an input or
output device, you will always have to change the values in BRU64K to
match the CSR and vector addresses of your hardware.
You can enter
the standard values for these devices by using the following responses
to the CNF prompt:
DR:/CSR=l76700/VEC=254
MS:/VEC=224
MT:/VEC=224
To begin copying your distribution kit, you must hardware bootstrap
the BRU64K stand-alone system on your host computer. The procedure
for hardware bootstrapping the BRU64K system depends on the bootstrap
hardware present on the host computer.
If you have an big disk magnetic tape kit, read Section 2.3.1.2 next.
If you have an RC25 Disk kit, read Section 2.3.1.3 next.
If you have an RK06/07
2.3.1.4 next.

1600

bpi

magnetic

tape

kit,

read

Section

If you have an RK06/07 800 bpi magnetic tape kit, read Section 2.3.1.5
next.
If you have an RK06/07 disk kit, read Section 2.3.1.6 next.
If you have an RLOl/02
2.3.1.7 next.

1600

bpi

magnetic

tape

kit,

read

Section

If you have an RLOl/02 800 bpi magnetic tape kit, read Section 2.3.1.8
next.
If you have an RLOl/02 disk kit, read Section 2.3.1.9 next.

2-5

GUIDE TO COPYING THE DISTRIBUTION KITS
2.3.1.2 Copying the Big Disk Magnetic Tape Kit Stand-Alone - Use the
following procedure to copy either the 800 bpi or 1600 bpi magnetic
tape kits using a host computer stand alone.
The output disk referred
to in this section is the blank disk you intend to use as the target
system disk.
All commands shown in this section are issued to the
RSX-llS basic MCR command line interpreter.
You will need one scratch disk to copy the distribution kit.
This
will be your system disk after your system generation is complete.
(Place a physical label on the disk so that the scratch disk
represents the backup set name in the distribution kit.)
To copy your distribution tape(s) to disk
system, perform the following steps:

using

stand-alone

host

NOTE
If you have a 1600 bpi kit, you need
only perform the first seven steps.
1.

Load the BRU64K tape on the appropriate tape drive. Load the
scratch disk, which you have previously physically labelled
RSXM35, in the appropriate disk drive and spin up the disk.
If your big disk medium is either the RASO or the RA81 disk
(both fixed-media disks) or the fixed-media portion of the
RC25, the fixed-media disk serves as the scratch disk.

Hardware bootstrap the BRU64K tape (see Appendix B for the
information regarding hardware bootstrap routines).
The
RSX-llS stand-alone system prints an identification line on
your
terminal,
then
begins
to
run the Stand-Alone
Configuration and Disk Sizing Program (CNF).

Enter the device specifications in response to the prompts
from CNF.
The "first device" is the tape drive that will
contain the RSX-llM V4.l distribution kit;
the "second
device" is the drive containing the output disk.
If the magnetic tape controller or the disk controller, or
both, are not connected to CSR and vector addresses that
BRU64K expects, you must modify the software to incorporate
the correct addresses before you can complete this step.
If
you wish to check your CSRs and vectors against the list of
default CSR and vector addresses, enter the /DEV switch in
response to the first CNF prompt. For example:
Enter first device:/DEV
Device

CSR

Vector

DB
DK

176700
177404

254
220

CSR Status
Present
Not Present

,~~n-~o·

~AA·~~~

QUU•C~~

/VEC=vector address
/FOR=f ormatter number
2-6

GUIDE TO COPYING THE DISTRIBUTION KITS

The vector addresses that BRU64K expects for DR, MS, and MT
devices are nonstandard.
The CSR address that BRU64K expects
for DR-type devices is also nonstandard.
If you are using
one of these devices as an input or output device, change the
values in BRU64K to match the CSR and vector addresses of
your hardware.
For example, assume you have a TU16 magnetic tape with the
default addresses,
and an RM02 disk at standard CSR and
vector addresses of 176700
(octal)
and
254
(octal),
respectively.
Assuming that the unit number for both units
is zero, the following is the sequence of commands to CNF:
Enter first device:MMO:
Enter second device:DRO:/CSR=l76700/VEC=254
4.

Press RETURN, then enter the date and time using the TIM
command.
Use the TIM command again to verify that you
entered the correct date and time.
For example:
Hit RETURN and enter date and time as 'TIM HH:MM MM/DD/YY'
>TIM 14:32 05/25/83
>TIM
14:32:01 25-MAY-83

>
5.

Run the Bad Block Locator Utility (BAD) on your output disk.
For example, if your output device is DRO:, use the following
command sequence:
>RUN BAD

>
BAD> DRO:/LIST
BAD -- DRO: Total bad blocks= 0.
BAD> (CTRL Z)

>
The BAD /LIST
located.

switch

lists

any

bad

blocks

they

are

Remove the BRU64K tape from the tape drive and mount the
distribution kit tape labelled RSXM35 on the tape drive
previously entered to CNF.

Run the Backup and Restore Utility (BRU) to copy
set on the distribution kit tape to the disk.

the

backup

For example, to copy the distribution tape
(labelled RSXM35
and 1/2 if it is an 800 bpi tape kit) mounted on a TU16
magnetic tape drive to an RM02 disk,
enter the following
command to BRU:
>RUN BRU

>
BRU>/BAC:RSXM35/INI/REW/DEN:l600/VER (1600 bpi tape)
BRU>/BAC:RSXM35/INI/REW/DEN:800/VER (800 bpi tape)
From:
MMO:
To:
ORO:
BRU - Starting Tape 1 on MMO:

2-7

GUIDE TO COPYING THE DISTRIBUTION KITS

The BRU /BAC (backup set)
be copied.

switch specifies the backup set

The BRU /INI (initialize) switch initializes the disk
to which BRU is copying.
The BRU /REW
(rewind)
switch ensures that
completely rewound before BRU begins to copy.

the

volume
tape

The BRU /DEN (density) switch specifies the density (bpi)
which the tape was written.

The BRU /VER (verify) switch causes BRU to verify the data
after it is copied.
BRU issues the following messages to the
terminal indicating that it has begun to verify the data
copied:
BRU - End of Tape 1 on MMO:
BRU - Starting verify pass Tape 1 on MMO:
NOTE
If the verify fails,
do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails
again,
retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.
When the tape is successfully copied and verified, BRU issues
the following messages:
BRU - End of Tape 1 on MMO:
BRU - Completed
8.

If your distribution kit contains two 800 bpi tapes,
remove
the first distribution tape from the drive and replace it
with the second distribution tape
(labelled 2/2)
when
requested by BRU:
BRU - Mount Tape 2 on MMO:

When you have loaded the second tape, put the magnetic tape
drive on line. BRU will proceed to copy the second tape and
issue the following message:
BRU - Starting Tape 2 on MMO:
This message indicates ~nat ~~u has begun copying the
contents of the second distribution tape to disk.
(BRU also
verifies the second reel.)
When
the
tape
has
been
successfully copied, BRU returns the following messages
indicating that it has finished:
BRU - End of Tape 2 on MMO:
BRU - Starting verify pass Tape 2 on MMO:
BRU - End of Tape 2 on MMO:
BRU - Completed
BRU> (CTRL/Z)

>
You may then unload the second distribution tape.

2-8

GUIDE TO COPYING THE DISTRIBUTION KITS
At this point, you have completed the tape-to-disk copy and are ready
to bootstrap the baseline system and begin generating your RSX-llM
system.
Refer to Appendix B for
information on bootstrapping your
distribution disk.
Then turn to Chapter 3 for details on the
structure of SYSGEN.
It is important that you read Chapter 3 before
you begin generating your system.

2.3.1.3 Copying the RC25 Disk Kit Stand-Alone - Use the following
procedure to copy the RC25 disk kit using the host computer stand
alone. The output disk or the scratch disk referred to in this
section is the blank disk you intend to use as the target system disk.
All commands are issued to the RSX-118 basic MCR command line
interpreter.
You will need one scratch disk {presumably the fixed-media portion
the RC25 drive) to copy the disk distribution kit.
To copy the disk distribution kit using a stand-alone system,
the following steps:

perform

Load the disk labelled RSXM35 in the appropriate drive
spin up both the fixed-media and removable-media disks.

Determine the correct hardware bootstrap procedure for
the
disk drive on which RSXM35 is mounted.
(See Appendix B for
the information regarding hardware bootstrap routines.)

Bootstrap the baseline system on the RSXM35 disk by using the
appropriate bootstrap routine for your processor and disk
drive. When the baseline system comes up,
it prints the
following identification line on your terminal:

and

124.K (BASELINE)

RSX-llM V4.l BL35-A

>@ <EOF>

>
At this point, system initialization is complete and you
proceed to step 4.
4.

may

RSXM35 contains the BRU64K system that you need to copy the
distribution kit.
Therefore, software bootstrap the BRU64K
system, which runs the RSX-llS stand-alone system.
For
example, if RSXM35 is in DUO:, enter the following commands:
>INS $BOO
>BOO DUO: [l,5l]BRU64K
Notice that you must first install the BOO (boot)
software bootstrapping BRU64K.

task before

NOTE
When copying the distribution disk, you
should
write-protect the disk from which you are copying
data.
Io do this, press the write protect button
on
the front of the disk drive.

2-9

GUIDE TO COPYING THE DISTRIBUTION KITS
The RSX-llS stand-alone system prints an identification line
on
your terminal, then begins to run the Stand-Alone
Configuration and Disk Sizing Program (CNF).
5.

Enter the device specifications in response to the prompts
from CNF.
The "first device" is the drive containing the
RSXM35 distribution kit disk;
the "second device" is the
drive containing the fixed-media output disk.
If the disk controller is not connected to CSR and vector
addresses that BRU64K expects, you must modify the software
to incorporate the correct addresses before you can complete
this step.
If you wish to check your CSRs and vectors
against the list of default CSR and vector addresses, enter
the /DEV switch in response to the first CNF prompt.
For
example:
Enter first device:/DEV
Device

CSR

Vector

CSR Status

DB
DK

176700
177404

254
220

Present
Not Present

If your device is at CSR and vector addresses other than
those that BRU64K expects, you must change the values in
BRU64K. Do this by using the following CNF switches when you
enter the device name:
/CSR=csr address
/VEC=vector address
/FOR=f ormatter number
6.

Press RETURN, then enter the date and time using the TIM
command.
Use the TIM command again to verify that you
entered the correct date and time. For example:
Hit RETURN and enter date and time as 'TIM HH:MM MM/DD/YY'
>TIM 14:32 05/25/83
>TIM
14:32:01 25-MAY-83

>
7.

Run the Bad Block Locator Utility (BAD) on your output disk.
For example, if your output device is DUl:, use the following
command sequence:
>RUN BAD

BAD> DUl:/LIST
BAD -- DUl: Total bad blocks= O.
BAD> (CTRL1Zl

>
The BAD /LIST
located.

switch

lists

2-10

any

bad

blocks

they

are

GUIDE TO COPYING THE DISTRIBUTION KITS
8.

Run the Backup and Restore Utility
(BRO)
distribution kit disk to the output disk.

copy

the

>RUN BRU

BRU>/INI/VER
From:
DUO:
To:
DUl:
The BRU /INI (initialize)
to which BRU is copying.

switch initializes the disk

volume

The BRU /VER (verify) switch causes BRU to verify the data
after it is copied. BRU issues the following message to the
terminal indicating that it has begun to verify the data
copied:
BRO - Starting verify pass
NOTE
If the verify fails, do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again,
retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit
is defective and should be
replaced or your hardware needs to be checked.
9.

When RSXM35 is successfully copied, BRU issues the following
message at your terminal to indicate that it has finished:
BRU - Completed
BRU>~RUZJ

>
Spin down the disks, replace the removable-media distribution
disk with a scratch disk, and then spin up the disks again.
At this point, you have completed the disk-to-disk copy and are ready
to bootstrap the baseline system and begin generating your RSX-llM
system. Refer to Appendix B for
information on bootstrapping your
distribution disk.
Then turn to Chapter 3 for details on the
structure of SYSGEN.
It is important that you read Chapter 3 before
you begin generating your system.

2.3.1.4 Copying the RK06/07 1600 bpi Magnetic Tape Kit Stand-Alone Use the following procedure to copy the 1600 bpi magnetic tape kit
using the host computer stand alone.
The output disk or the scratch
disk referred to in this section is the blank disk you intend to use
as the target system disk. All commands shown in this section are
issued to the RSX-llS basic MCR command line interpreter.
You will need two scratch disks to copy the distribution tape.
(Place
a physical label on each disk so that the scratch disks represent the
backup set names in the distribution kit.)
To copy your distribution tape to disk
perform the following steps:
1.

using

stand-alone

system,

Load the BRU64K tape and the output disk, physically labelled
RSXM35, on the appropriate drives.

2-11

GUIDE TO COPYING THE DISTRIBUTION KITS
2.

Enter the device specifications in response to the prompts
from CNF.
The "first device" is the tape drive that will
contain the distribution kit;
the "second device"
is the
drive containing the output disk.
If the magnetic tape controller or the disk controller, or
both, are not connected to CSR and vector addresses that
BRU64K expects, you must modify the software to incorporate
the correct addresses before you can complete this step.
If
you wish to check your CSRs and vectors against the list of
default CSR and vector addresses, enter the /DEV switch in
response to the first CNF prompt.
For example:
Enter first device:/DEV
Device

CSR

Vector

CSR Status

DB
DK

176700
177404

254
220

Present
Not Present

If your devices are at CSR and vector addresses other than
those that BRU64K expects, or if your MF:- or MM:-type
magnetic tape drive is on a formatter number other than zero,
you must change the values in BRU64K.
Do this by using the
following CNF switches when you enter the device name:
/CSR=csr address
/VEC=vector address
/FOR=formatter number
The vector addresses that BRU64K expects for DR, MS, and MT
devices are nonstandard.
The CSR address that BRU64K expects
for DR-type devices is also nonstandard.
If you are using
one of these devices as an input or output device, change the
values in BRU64K to match the CSR and vector addresses of
your hardware.
For example, assume you have a TU16 magnetic tape at
nonstandard CSR and vector addresses of 176300 (octal) and
150 (octal), respectively, and an RK06 disk wth the default
addresses.
Assuming that the unit number for both units is
zero; the following is the sequence of commands to CNF:
Enter first device:MMO:/CSR=l76300/VEC=l50
Enter second device:DMO:
4.

Press RETURN, then enter the date and time using the TIM
command.
Use the TIM command again to verify that you
entered the correct date and time. For example:
Hit RETURN and enter date and time as 'TIM HH:MM MM/DD/YY'
>TIM 14:32 05/25/83
>TIM

14:32:01 25-MAY-83

>
2-12

GUIDE TO COPYING THE DISTRIBUTION KITS
5.

Run the Bad Block Locator Utility
(BAD)
on both of your
output disks.
For example, if your output device is DMO:,
use the following command sequence:
>RUN BAD

BAD> DMO :/LIST
BAD -- DMO: Total bad blocks= O.
BAD> ©°RUZ)

>
The BAD /LIST
located.

switch

lists

any

bad

blocks

they

are

Remove the BRU64K tape from the drive, and mount the
on the tape drive
distribution
tape, labelled RSXM35,
previously entered to CNF.

Run the Backup and Restore Utility (BRU) to copy the first
backup set on the distribution kit tape to the output disk.
For example, to copy the distribution tape placed on a TU16
magnetic tape drive to an RK06 disk, enter the following
command to BRU:
>RUN BRU

BRU>/BAC:RSXM35/INI/REW/DEN:l600/VER
From:
MMO:
To:
DMO:
BRU - Starting Tape 1 on MMO:
The BRU /BAC (backup set) switch specifies the backup set
be copied.
The BRU /INI (initialize) switch initializes the disk
to which BRU is copying.
The BRU /REW
(rewind)
switch ensures that
completely rewound before BRU begins to copy.

the

volume
tape

The BRU /DEN (density) switch specifies the density (bpi)
which the tape was written.

The BRU /VER (verify) switch causes BRU to verify the data
after it is copied.
BRU issues the following messages
indicating that it has begun to verify the data copied:
BRU - End of Tape 1 on MMO:
BRU - Starting verify pass Tape 1 on MMO:
NOTE
If the verify fails, do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again, retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.

2-13

GUIDE TO COPYING THE DISTRIBUTION KITS
8.

After the RSXM35 backup set portion of the tape has been
successfully copied to the disk and verified, BRO issues the
following messages at your terminal:
BRO - End of Tape 1 on MMO:
BRO - Completed

Remove the output disk labelled RSXM35 from the drive,
replace it with the scratch disk labelled CLISRC, and spin up
the disk.

10.

Enter the command line to
distribution tape to disk:

BRO

copy

the

rest

the

BRU>/BAC:CLISRC/INI/DEN:l600/VER
From:
MMO:
To:
DMO:
BRO - Starting Tape 1 on MMO:
The BRO /REW switch is not necessary because the tape should
already be correctly positioned to copy the CLISRC backup-set
portion of the distribution tape.
11.

After the CLISRC backup set portion of the distribution tape
has been successfully copied to the disk and verified, BRO
issues the following messages at your terminal:
BRO - End of Tape 1 on MMO:
BRO - Starting verify pass Tape 1 on MMO:
BRO - End of Tape 1 on MMO:
BRO - Completed
BRO> tTRLiz)

>
At this point, you have completed the tape-to-disk copy and are ready
to bootstrap the baseline system and generate your RSX-llM system.
Refer to Appendix B for information on bootstrapping your distribution
disk.
Then turn to Chapter 3 for details on the structure of SYSGEN.
It is important that you read Chapter 3 before you begin generating
your system.

2.3.1.5 Copying the RK06/07 800 bpi Magnetic Tape Kit Stand-Alone Use the following procedure to copy the 800 bpi magnetic tape kit
using the host computer stand alone.
The output disk or the scratch
disk ref erred to in this section is the blank disk you intend to use
as the target system disk.
All commands shown in this section are
issued to the RSX-llS basic MCR command line interpreter.
You will need two scratch disks to copy the distribution tape.
(Place
a
physical label on each disk so that the scratch disks represent the
backup set names in the distribution kit.)
To copy your distribution tapes to disk using
perform the following steps:

stand-alone

system,

Load the BRU64K tape and the output disk, labelled RSXM35, on
the appropriate drives.

Hardware bootstrap the BRU64K tape (see Appendix B for
the
information regarding hardware bootstrap routines).
The
RSX-llS stand-alone system prints an identification line on
yuuL
terminal,
then
begins
to
run the Stand-Alone
Configuration and Disk Sizing Program (CNF).
2-14

GUIDE TO COPYING THE DISTRIBUTION KITS
3.

Enter the device specifications in response to the prompts
from CNF.
The "first device" is the tape drive that will
contain the distribution kit;
the "second device" is the
drive containing the output disk.
If the magnetic tape controller or the disk controller,
or
both, are not connected to CSR and vector addresses that
BRU64K expects, you must modify the software to incorporate
the correct addresses before you can complete this step.
If
you wish to check your CSRs and vectors against the list of
default CSR and vector addresses, enter the /DEV switch in
response to the first CNF prompt.
For example:
Enter first

device~/DEV

Device

CSR

Vector

CSR Status

176700
177404

254
220

Present
Not Present

If your devices are at CSR and vector addresses other than
those that BRU64K expects, or if your MF:- or MM:-type
magnetic tape drive is on a formatter number other than zero,
you must change the values in BRU64K.
Do this by using the
following CNF switches when you enter the device name:
/CSR=csr address
/VEC=vector address
/FOR=formatter number
The vector addresses that BRU64K expects for DR, MS, and MT
devices are nonstandard.
The CSR address that BRU64K expects
for DR-type devices is also nonstandard.
If you are using
one of these devices as an input or output device, change the
values in BRU64K to match the CSR and vector addresses of
your hardware.
For example, assume you have a TU16 magnetic tape at
nonstandard CSR and vector addresses of 176300 (octal) and
150 (octal), respectively, and an RK06 disk with the default
addresses.
Assuming that the unit number for both units is
zero, the following is the sequence of commands to CNF:
Enter first device:MMO:/CSR=l76300/VEC=l50
Enter second device:DMO:
4.

Press RETURN, then enter the date and time using the TIM
command.
Use the TIM command again to verify that you
entered the correct date and time. For example:
Hit RETURN and enter date and time as 'TIM HH:MM MM/DD/YY 2
>TIM 14:32 05/25/83
>TIM
14:32:01 25-MAY-83

2-15

GOIDE TO COPYING THE DISTRIBUTION KITS
5.

Run the Bad Block Locator Utility
(BAD)
on both of your
output disks.
For example, if your output device is DMO:,
use the following command sequence:
>RUN BAD

>
BAD> DMO:/LIST
BAD -- DMO: Total bad blocks= 0.
BAD) tTRUz)

>
The BAD /LIST
located.

switch

lists

any

bad

blocks

they

are

Remove the BRU64K tape and mount the first distribution kit
tape
(labelled RSXM35) on the tape drive previously entered
to CNF.

Run the Backup and Restore Utility (BRU) to copy the first
backup set on the distribution kit tape to the output disk.
For example, to copy the first distribution tape placed on a
TU16 magnetic tape drive to an RK06 disk, enter the following
command to BRU:
>RUN BRU

>
BRU>/BAC:RSXM35/INI/REW/DEN:800/VER
From:
MMO:
To:
DMO:
BRU - Starting Tape 1 on MMO:
The BRU /BAC (backup set)
name to be copied.

switch

specifies

the

backup

The BRU /IN! (initialize) switch initializes the disk
to which BRU is copying.
The BRU /REW
(rewind)
switch ensures that
completely rewound before BRU begins to copy.

the

set

volume
tape

The BRU /DEN (density) switch specifies the density (bpi)
which the tape was written.

The BRU /VER (verify) switch causes BRU to verify the data
after it is copied.
BRU issues the following messages to the
terminal indicating that it has begun to verify the data
copied:
BRU - End of Tape 1 on MMO:
BRU - Starting verify pass Tape 1 on MMO:
NOTE
If the verify fails,
do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again,
retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.

2-16

GUIDE TO COPYING THE DISTRIBUTION KITS
8.

When the first tape is successfully copied and verified,
issues the following messages on your terminal:

BRU

BRU - End of Tape 1 on MMO:
BRU - Completed

Remove the first distribution tape from the drive and replace
it with the second distribution tape, labelled CLISRC.
Remove the output disk labelled RSXM35 from the drive,
replace
it with the disk labelled CLISRC, and spin up the
disk.

10.

Enter the following command line to BRU to
distribution tape to disk:

copy

the

second

BRU>/BAC:CLISRC/INI/REW/DEN:800/VER
From:
MMO:
To:
OMO:
BRU - Starting Tape 1 on MMO:
When the tape is successfully copied,
BRU returns
following messages indicating that it has finished:

the

BRU - End of Tape 1 on MMO:
BRU - Starting verify pass Tape 1 on MMO:
BRU - End of Tape 1 on MMO:
BRU - Completed
BRU> (CTRLZ)

2.3.1.6 Copying the RK06/07 Disk Kit Stand-Alone - Use the following
procedures to copy the RK06/07 disk kit using the computer stand
alone.
The output disk or the scratch disk referred to in this
section is the blank disk you intend to use for the target system
disk.
All commands shown in this section are issued to the RSX-llS
basic MCR command line interpreter.
The baseline disk includes neither the Backup and Restore Utility
(BRU)
nor the BRU64K system.
To create a backup copy of your
distribution kit on a stand-alone system, you must first bootstrap the
disk labelled CLISRC,
then software bootstrap BRU64K
(described
below) •
You will need two scratch disks to copy the distribution disks.
(Place a physical label on each disk so that the scratch disks
represent the labels on the respective disks in the distribution kit.)
To copy the disk distribution kit using a stand-alone system,
the following steps:

perform

Load the distribution disk labelled CLISRC and the scratch
disk labelled RSXM35 in the appropriate drives and spin them
up.

2-17

GUIDE TO COPYING THE DISTRIBUTION KITS
2.

Determine the correct hardware bootstrap procedure for the
disk drive on which CLISRC is mounted.
(See Appendix B for
the information regarding hardware bootstrap routines.)

Bootstrap the baseline system on the CLISRC disk by using the
appropriate bootstrap routine for your processor and disk
drive. When the baseline system comes up,
it prints the
following identification line on your terminal:
RSX-llM V4.l BL35-A

124.K (BASELINE)

>@ <EOF>

>
At this point, system initialization is complete and you
proceed to step 4.
4.

may

CLISRC contains the BRU64K system that you need to copy the
distribution kit.
Therefore, software bootstrap the BRU64K
system, which runs the RSX-llS stand-alone system.
For
example, if CLISRC is in DMO:, enter the following commands:
>INS $BOO
>BOO OMO: [l,5l]BRU64K
Notice that you must first install the BOO (boot) task before
software bootstrapping BRU64K.
NOTE
When copying the distribution disks, you should write
protect the disk from which you are copying data. To
do this, press the write protect button on the front
of the disk drive.
The RSX-llS stand-alone system prints an identification line
on
your terminal,
then begins to run the Stand-Alone
Configuration and Disk Sizing Program (CNF).

Enter the device specifications in response to the prompts
from CNF.
The "first device" is the drive containing the
CLISRC distribution kit disk; the "second device" is the
drive containing the output disk.
If one or both of the disk controllers are not connected to
CSR and vector addresses that BRU64K expects, you must modify
the software to incorporate the correct addresses before you
can complete this step.
If you wish to check your CSRs and
vectors against the list of default CSR and vector addresses,
enter the /DEV switch in response to the first CNF prompt.
For example:
Enter first device:/DEV
Device

CSR

Vector

CSR Status

DB
DK

176700
177404

254
220

Present
Not Present

2-18

GUIDE TO COPYING THE DISTRIBUTION KITS

If your devices are at CSR and vector addresses other than
those that BRU64K expects, you must change the values in
BRU64K. Do this by using the following CNF switches when you
enter the device name:
/CSR=csr address
/VEC=vector address
/FOR=formatter number
For example, assume your first RK06 disk device
(the one
containing CLISRC) is at nonstandard CSR and vector addresses
of 176714 (octal) and 300
(octal), respectively, and your
output RK06 disk device has the default addresses. Assuming
that the unit numbers for both units are zero and one,
respectively,
the following is the sequence of commands to
CNF:
Enter first device:DMO:/CSR=l76714/VEC=300
Enter second device:DMl:
6.

Press RETURN, then enter the date and time using the TIM
command.
Use the TIM command again to verify that you
entered the correct date and time. For example:
Hit RETURN and enter date and time as 'TIM HH:MM MM/DD/YY'
>TIM 14:32 05/25/83
>TIM
14:32:01 25-MAY-83

>
7.

Run the Bad Block Locator Utility (BAD) first on the scratch
disk labelled RSXM35.
After BAD finishes, spin down that
disk and mount the scratch disk labelled CLISRC in the disk
drive. Spin up that disk and run BAD on it. For example, if
your output device is DMl:, use the following command
sequence:
>RUN BAD

>
BAD> DMl:/LIST
BAD -- DMl: Total bad blocks= O.
BAD> (CTRL/Z)

>
The BAD /LIST
located.
8.

switch

lists

any

bad

blocks

they

are

Run the Backup and Restore Utility (BRU) to copy the CLISRC
distribution kit disk to the output disk. For example, if
your output disk is DMl:, use the following command sequence:
>RUN BRU

>
BRU> /!NI/VER
From:
DMO:
To:
DMl:
The BRU /!NI .(initialize)
switch initializes the disk
.
to which BRU is copying.

2-19

volume

GUIDE TO COPYING THE DISTRIBUTION KITS

The BRO /VER (verify) switch causes BRO to verify the data
after it is copied. BRO issues the following message to the
terminal indicating that it has begun to verify the data
copied:
BRU - Starting verify pass
NOTE
If the verify fails, do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again, retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.
9.

When CLISRC is successfully copied, BRU issues the following
message at your terminal to indicate that it has finished:
BRU - Completed
Spin the disks down and remove them.
Replace the CLISRC
distribution disk with the baseline disk, labelled RSXM35.
Replace the new copy of CLISRC with the second scratch disk,
labelled
RSXM35,
and
spin
up
both
disks.
Again,
write-protect the disk from which you are copying data.

10.

Copy the RSXM35 distribution disk to the output
example, enter the following command sequence:

disk.

For

copied

and

BRU>/INI/VER
From:
DMO:
To:
DMl:
BRU - Starting verify pass
11.

When the second disk volume is successfully
verified, BRO issues the following message:
BRU - Completed
BRU> (CTRL z;

>
At this point, you have completed the disk-to-disk copy of the
distribution kit and are ready to bootstrap the baseline system on the
RSXM35 disk and generate your RSX-llM system. Refer to Appendix B for
information on bootstrapping your baseline system.
Then turn to
Chapter 3 for details on the structure of SYSGEN~
It is
important
that you read Chapter 3 before you begin generating your system.

2.3.1.7 Copying the RLOl/02 1600 bpi Magnetic Tape Kit Stand-Alone Use the following procedure to copy the 1600 bpi magnetic tape kit
using the host computer stand alone.
The output disk or the scratch
disk referred to in this section is the blank disk you intend to use
as the target system disk. All commands shown in this section are
issued to the RSX-llS basic MCR command line interpreter~
You will need
distribution
scratch disks
However, only

six scratch RLOl or RL02 disks to copy the entire
nhuC!i,...:::.1
1:::.'hol
"'""' each disk so that the
tape.
(Place a t:'.l..6
.I ....., _., """""""
represent the backup set names in the distribution kit.)
the first three backup sets (RSXM35, EXCPRV, and RLUTIL)
..L.

2-20

..&.. ' - " ' , . _ , ' - ..L.

"'1L.I

GUIDE TO COPYING THE DISTRIBUTION KITS

are used during a system generation.
See post-system generation
guidelines in Chapter 6 to determine whether or not you need to copy
the remaining three backup sets;
To copy your distribution tape to disks using
perform the following steps:

stand-alone

system,

Load the BRU64K tape and the output disk, labelled EXCPRV, on
the appropriate drives.

Enter the device specifications in response to the prompts
from CNF.
The "first device" is the tape drive that will
contain the distribution tape;
the "second device" is the
drive containing the output disk.
If the magnetic tape controller or the disk controller, or
both, are not connected to CSR and vector addresses that
BRU64K expects, you must modify the software to incorporate
the correct addresses before you can complete this step.
If
you wish to check your CSRs and vectors against the list of
default CSR and vector addresses, enter the /DEV switch in
response to the first CNF prompt. For example:
Enter first device:/DEV
Device

CSR

Vector

CSR Status

DB
DK

176700
177404

254
220

Present
Not Present

If your devices are at CSR and vector addresses other than
those that BRU64K expects, or if your MF:- or MM:-type
magnetic tape drive is on a formatter number other than zero,
you must change the values in BRU64K. Do this by using the
following CNF switches when you enter the device name:
/CSR=csr address
/VEC=vector address
/FOR=formatter number
The vector addresses that BRU64K expects for DR, MS, and MT
devices are nonstandard.
The CSR address that BRU64K expects
for DR-type devices is also nonstandard.
If you are using
one of these devices as an input or output device, change the
values in BRU64K to match the CSR and vector addresses of
your hardware.
For example, assume you have a TU16 magnetic tape at
nonstandard CSR and vector addresses of 176300 (octal) and
150 (octal), respectively, and an RL02 with the default
addresses.
Assuming that the unit number for both units is
zero, the following is the sequence of commands to CNF:
Enter first device;MMO:/CSR=l76300/VEC=l50
Enter second device:DLO:

2-21

GUIDE TO COPYING THE DISTRIBUTION KITS
4.

Press RETURN, then enter the date and time using the TIM
command.
Use the TIM command again to verify that you
entered the correct date and time. For example:
Hit RETURN and enter date and time as 'TIM HH:MM MM/DD/YY'
>TIM 14:32 05/25/83
>TIM
14:32:01 25-MAY-83

>
5.

Run the Bad Block Locator Utility (BAD) on all your output
disks finishing with the scratch disk labelled RSXM35.
For
example, if your output device is DLO:,
use the following
command sequence:
>RUN BAD

BAD> DLO:/LIST
BAD -- DLO: Total bad blocks=
BAD> (CTRL!z)

>
The BAD /LIST
located.

switch

lists

any

bad

blocks

they

are

Remove the BRU64K tape from the drive
distribution
tape
(labelled RSXM35)
on
previously entered to CNF.

Run the Backup and Restore Utility (BRU) to copy the first
backup set on the distribution kit to output disk.
For
example, to copy the distribution tape from a TU16 magnetic
tape drive to an RL02, enter the following command to BRU:

and
the

mount
the
tape drive

>RUN BRU

BRU>/BAC:RSXM35/INI/REW/DEN:l600/VER
From:
MMO:
To:
DLO:
BRU - Starting Tape 1 on MMO:
The BRU /BAC (backup set} switch specifies the backup set
be copied.
The BRU /INI (initialize} switch initializes the disk
to which BRU is copying.
The BRU /REW
(rewind)
switch ensures
completely rewound before BRU begins to

that

the

volume
tape

The BRU /DEN (density) switch specifies the density (bpi)
which the tape was written.

The BRU /VER (verify) switch causes BRU to verify the data
after it is copied,
BRU issues the following messages
indicating that it has begun to verify the data copied:
BRU - End of Tape 1 on MMO:
BRU - Starting verify pass Tape 1 on MMO:

2-22

GUIDE TO COPYING THE DISTRIBUTION KITS
NOTE
If the verify fails,
do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again,
retry the
backup operation using a new output disk.
If the
verify fails once again, it
is likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.
8.

After the RSXM35 backup set portion of the tape has been
successfully copied to the disk, BRU issues the following
messages at your terminal:
BRU - End of Tape 1 on MMO:
BRU - Completed

Remove the first disk from the drive,
replace it with the
second scratch disk labelled EXCPRV, and spin up the disk.

10.

Enter the command line to BRU to copy the EXCPRV
portion of the distribution tape to disk:

backup

set

BRU>/BAC:EXCPRV/INI/DEN:l600/VER
From:
MMO:
To:
DLO:
BRU - Starting Tape 1 on MMO:
The BRU /REW switch is not necessary because the tape should
already be correctly positioned to copy the EXCPRV backup set
portion of the distribution tape.
The following warning message from BRU reminds you
backup set being copied is not hardware bootable:

that

the

After the EXCPRV backup set portion of the distribution tape
has been successfully copied to the disk, BRU issues the
following messages at your terminal:
BRU BRU BRU BRU -

End of Tape 1 on MMO:
Starting verify pass Tape 1 on MMO:
End of Tape 1 on MMO:
Completed

12.

To copy the RLUTIL backup set and any of the remaining backup
sets that you want to copy from the distribution tape to the
scratch disks, repeat steps 9, 10, and 11 and replace the
backup set name in the BRU command line with the backup set
name of the portion of the distribution tape to be copied.
Table 2-1 lists the RLOl/02 backup set names in the order
that you should copy them.
Be sure that the scratch disks to
which you are copying each backup set have been checked for
bad blocks using the BAD utility.

13.

To exit BRU after you have finished copying all the backup
sets you need, type CTRL/Z in response to the BRU prompt.

2-23

GUIDE TO COPYING THE DISTRIBUTION KITS
At this point, you have completed the tape-to-disk copy and are ready
to bootstrap the baseline system and generate your RSX-llM system.
Refer to Appendix B for information on bootstrapping your distribution
disk.
Then turn to Chapter 3 for details on the structure of SYSGEN.
It is important that you read Chapter 3 before you begin generating
your system.

2.3.1.8 Copying the RLOl/02 800 bpi Magnetic Tape Kit Stand-Alone Use the following procedure to copy the 800 bpi magnetic tape kit
using the host computer stand alone. The output disk or the scratch
disk referred to in this section is the blank disk you intend to use
as the target system disk. All commands shown in this section are
issued to the RSX-llS basic MCR command line interpreter.
You will need six scratch RLOl or RL02 disks to copy the entire tape
distribution kit.
(Place a physical label on each disk so that the
scratch disks represent the backup set names in the distribution kit.)
However, only the first three backup sets (RSXM35, EXCPRV, and RLUTIL)
are used during a system generation.
See post-system generation
guidelines in Chapter 6 to determine whether or not you need to copy
the remaining three backup sets.
To copy your distribution tapes to disks using a
perform the following steps:

stand-alone

system,

Load the BRU64K tape and the output disk, labelled EXCPRV, on
the appropriate drives.

Enter the device specifications in response to the prompts
from CNF.
The "first device" is the tape drive that will
contain the distribution kit tape;
the "second device"
is
the drive containing the output disk.
If the magnetic tape controller or the disk controller, or
both, are not connected to CSR and vector addresses that
BRU64K expects, you must modify the software to incorporate
the correct addresses before you can complete this step.
If
you wish to check your CSRs and vectors against the list of
default CSR and vector addresses, enter the /DEV switch in
response to the first CNF prompt.
For example:
Enter first device:/DEV
Device

CSR

Vector

CSR Status

DB
DK

176700
177404

254
220

Present
Not Present

2-24

GUIDE TO COPYING THE DISTRIBUTION KITS

If your devices are at CSR and vector addresses other than
those that BRU64K expects, or if your MF:- or MM:-type
magnetic tape drive is on a formatter number other than zero,
you must change the values in BRU64K. Do this by using the
following CNF switches when you enter the device name:
/CSR=csr address
/VEC=vector address
/FOR=formatter number
The vector addresses that BRU64K expects for DR, MS, and MT
devices are nonstandard. The CSR address that BRU64K expe~ts
for DR-type devices is also nonstandard.
If you are using
one of these devices as an input or output device, change the
values in BRU64K to match the CSR and vector addresses of
your hardware.
For example, assume you have a TU16 magnetic tape at
nonstandard CSR and vector addresses of 176300 (octal) and
150 (octal), respectively, and an RL02 disk with the default
addresses.
Assuming that the unit number for both units is
zero, the following is the sequence of commands to CNF:
Enter first device:MMO:/CSR=l76300/VEC=l50
Enter second device:DLO:
4.

Press RETURN, then enter the date and time using the TIM
command.
Use the TIM command again to verify that you
entered the correct date and time. For example:
Hit RETURN and enter date and time as 'TIM HH:MM MM/DD/YY'
>TIM 14:32 05/25/83
>TIM
14:32:01 25-MAY-83

>
5.

Run the Bad Block Locator Utility (BAD) on all your output
disks finishing ~ith the scratch disk labelled RSXM35. For
example, if your output device is DLO:, use the following
command sequence:
>RUN BAD

BAD>DLO:/LIST
BAD -- DLO: Total bad blocks= 0.
BAD> lCTRL Z)

>
The BAD /LIST
located.
6.

switch

lists

any

bad

blocks

they

are

Remove the BRU64K tape from the drive and mount
the
distribution kit tape labelled RSXM35 on the tape drive
previously entered to CNF.

2-25

GUIDE TO COPYING THE DISTRIBUTION KITS

Run the Backup and Restore Utility (BRU) to copy the first
backup set on the distribution kit tape to the output disk.
For example, to copy from a TU16 magnetic tape drive to an
RL02, enter the following command to BRU:
)RUN BRU

BRU>/BAC:RSXM35/INI/REW/DEN:800/VER
From:
MMO:
To:
DLO:
BRO

Starting Tape 1 on MMO:

The BRO /BAC (backup set)
be copied.

switch specifies the backup set

The BRO /IN! (initialize) switch initializes the disk
to which BRU is copying.
The BRU /REW
(rewind)
switch ensures that
completely rewound before BRO begins to copy.

the

volume
tape

The BRO /DEN (density) switch specifies the density (bpi)
which the tape was written.

The BRO /VER (verify} switch causes BRO to verify the data
after
it is copied.
BRU issues the following messages
indicating that it has begun to verify the data copied:
BRO - End of Tape 1 on MMO:
BRO - Starting verify pass Tape 1 on MMO:
NOTE
If the verify fails,
do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again,
retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit
is defective and should be
replaced or your hardware needs to be checked.
8.

After the RSXM35 backup set portion of the tape has been
successfully copied to the disk, BRO issues the following
message at your terminal:
BRO - End of Tape 1 on MMO:
BRO - Completed

Remove the first disk from the drive:
replace i r with the
second scratch disk labelled EXCPRV, and spin up the disk.

10.

Enter the command line to BRU to copy the
portion of the distribution tape to disk:
BRO>/BAC:EXCPRV/INI/DEN:800/VER
From:
MMO:
To:
DLO:
BRO - Starting Tape 1 on MMO:

2-26

EXCPRV

backup-set

GUIDE TO COPYING THE DISTRIBUTION KITS
The BRU /REW switch is not necessary because the tape should
already be correctly positioned to copy the EXCPRV backup set
portion of the distribution tape.
The following warning message from BRO rem1nas you
backup set being copied is not hardware bootable:

that

the

After the EXCPRV backup set portion of the distribution tape
has been successfully copied to the disk, BRU issues the
following messages on your terminal:
BRU
BRU
BRU
BRO

End of Tape 1 on MMO:
Starting verify pass Tape 1 on MMO:
End of Tape 1 on MMO:
Completed

12.

Repeat steps 9, 10, and 11 until you have sucessfully copied
the RLOTIL backup set portion of the distribution tape onto a
scratch disk labelled with the same name.
Simply replace the
backup set name in the BRO command line with the backup set
name of the portion of the distribution tape to be copied.

13.

Remove the first distribution tape from the drive and replace
it with the second tape, labelled MCRSRC if you are copying
any of the backup sets from it.

14.

Remove the disk labelled RLOTIL from the drive and replace it
with the next scratch disk, labelled MCRSRC, and spin up the
disk.

15.

Enter the command line to BRO to copy the MCRSRC
portion of the second distribution tape:

backup

set

BRO>/BAC:MCRSRC/INI/REW/DEN:800/VER
From:
MMO:
To:
DLO:
16.

To copy the two remaining backup sets on the
second
distribution tape to the two scratch disks, repeat steps 9,
10, and 11 and replace the backup set name in the BRO command
line with the backup set name of the portion of the
distribution tape to be copied. Table 2-1 lists the RLOl/02
backup set names in the order that you should copy them.
Be
sure that the scratch disks to which you are copying each
backup set have been checked for bad blocks using the BAD
utility.

17.

To exit BRO after you have finished copying the all the
backup sets you need,
type CTRL/Z in response to the BRU
prompt.

At this point, you have completed the tape-to-disk copy and are ready
to bootstrap the baseline system and generate your RSX-llM system.
Refer to Appendix B for information on bootstrapping your distribution
disk.
Then turn to Chapter 3 for details on the structure of SYSGEN.
It is important that you read Chapter 3 before you begin generating
your system.

2-27

GUIDE TO COPYING THE DISTRIBUTION KITS
2.3.l.9 Copying the RLOl/02 Disk Kit Stand-Alone - Use the following
procedures to copy the RLOl/02 disk kit using the computer stand
alone.
The output disk or the scratch disk referred to
in this
section is the blank disk you intend to use for the target system
disk.
All commands shown in this section are issued to the RSX-llS
basic MCR command line interpreter.
The baseline disk (RSXM35) includes neither the Backup and Restore
Utility
(BRU) nor the stand-alone BRU64K utility.
To create a backup
copy of your distribution kit on a stand-alone system, you must first
bootstrap
the
baseline system,
then software bootstrap BRU64K
(described in Step 5) from the distribution disk labelled RLUTIL.
You will need six scratch RLOl or RL02 disks to copy the entire
distribution kit.
(Place a physical label on each disk so that the
scratch disks represent the labels on the respective disks
in the
distribution kit.)
However,
only the first
three disks (RSXM35,
EXCPRV,
and RLUTIL)
are used during a
system generation.
See
post-system generation guidelines in Chapter 6 to determine whether or
not you need to copy the remaining three disks.
To copy the disk distribution kit using a stand-alone system,
the following steps:

perform

Place the baseline disk (RSXM35) and the distribution disk
labelled RLUTIL in the appropriate drives and spin them up.

Determine the correct hardware procedure for the disk drive
on which the baseline disk is mounted.
(See Appendix B for
the information regarding hardware bootstrap routines.)

Bootstrap the baseline system on the RSXM35 disk by using the
appropriate bootstrap routine for your processor and disk
drive (see Appendix B). When the baseline system comes up,
it prints the following identification line on your terminal:
RSX-llM V4.l BL35-A

124.K (BASELINE)

>@ <EOF>

>
At this point, system initialization is complete and you
proceed to step 4.
4.

may

The RLUTIL disk contains the BRU64K system that you need
to
copy the distribution kit.
Therefore,
when the baseline
system comes up, software mount RLUTIL.
For example, if your
baseline disk
is on DLO:
and RLUTIL is on DLl:, enter the
following command to mount RLUTIL:
>MOU DLl:RLUTIL

Software bootstrap the BRU64K system, which runs the RSX-llS
stand-alone system.
For example, if RLUTIL is in DLl:, enter
the following commands:
>INS $BOO
>BOO DLl: [l,5l]BRU64K
Notice that you must first install the BOO (boot)
software bootstrapping BRU64K.

2-28

task before

GUIDE TO COPYING THE DISTRIBUTION KITS
The RSX-llS stand-alone system prints an identification line
on
your terminal,
then begins to run the Stand-Alone
Configuration and Disk Sizing Program (CNF)
6.

Remove the RLUTIL distribution disk from DLl:, physically
mount the scratch disk labelled RLUTIL in the drive, and spin
up the disk. Also, write-protect the RSXM35 distribution
disk by pressing the write protect button on the face of the
disk drive.

Enter the device specifications in response to the prompts
from CNF.
The "first device" is the drive containing the
RSXM35 distribution kit disk;
the "second device"
is the
drive containing the output disk labelled RLUTIL.
If one or both of the disk controllers are not connected to
CSR and vector addresses that BRU64K expects, you must modify
the software to incorporate the correct addresses before you
can complete this step.
If you wish to check your CSRs and
vectors against the list of default CSR and vector addresses,
enter the /DEV switch in response to the first CNF prompt.
For example:
Enter first device:/DEV
Device

CSR

Vector

CSR Status

DB
DK

176700
177404

254
220

Present
Not Present

If your devices are at CSR and vector addresses other than
those that BRU64K expects, you must change the values in
BRU64K. Do this by using the following CNF switches when you
enter the device name:
/CSR=csr address
/VEC=vector address
/FOR=formatter number
For example, assume your first disk device
(the
one
containing RSXM35) is at nonstandard CSR and vector addresses
of 176714 (octal) and 300
(octal), respectively, and your
output disk device has the default addresses.
Assuming that
the unit numbers of both units
are
zero
and
one,
respectively,
the following
is the sequence of commands to
CNF:
Enter first device:DLO:/CSR=l76714/VEC=300
Enter second device:DLl:
8.

Press RETURN, then enter the date and time using the TIM
command.
Use the TIM command again to verify that you
entered the correct date and time. For example:
Hit RETURN and enter date and time as 'TIM HH:MM MM/DD/YY'
>TIM 14:32 05/25/83
>TIM
14:32:01 25-MAY-83

2-29

GUIDE TO COPYING THE DISTRIBUTION KITS
9.

Run the Bad Block Locator Utility (BAD) on all your output
disks beginning with the RLUTIL scratch disk and finishing
with the RSXM35 scratch disk.
For example,
if your output
device is DLl:, use the following command sequence:
>RUN BAD

BAD> DLl:/LIST
BAD -- DLl: Total bad blocks= 0.
BAD>mRLiz)

>
The BAD /LIST
located.
10.

switch

lists

any

bad

blocks

Run the Backup and Restore Utility (BRU) to copy
distribution kit disk to the RSXM35 output disk.

they
the

are

RSXM35

For example, if your output device is DLl:, use the following
command sequence:
>RUN BRU

>
BRU>/INI/VER
From:
DLO:
To:
DLl:
The BRU /IN! (initialize) switch initializes the disk
to which BRU is copying.

volume

The BRU /VER (verify) switch causes BRO to verify the data
after
it is copied.
BRU issues the following message
indicating that it has begun to verify the data copied:
BRU - Starting verify pass
NOTE
If the verify fails,
do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again,
retry the
backup operation using a
new output disk.
If the
verify fails once again, it is
likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.
11.

When the distribution disk is successfully copied, BRU issues
the following message to indicate that it has finished:
BRU - Completed
Spin down both disks and remove
them.
Replace
the
distribution disk with the next distribution disk.
Replace
the new disk copy with the next scratch disk,
and spin up
both disks.
NOTE
When copying the distribution disks,
it is a good
idea to write-protect the disk from which you are
copying data.
To de this, ~~c~~ the write protect
button on the face of the disk drive.

2-30

GUIDE TO COPYING THE DISTRIBUTION KITS
12.

Enter the command line to BRU to copy the next disk.
For
example,
if your output device is DLl:, use the following
command sequence:
BRU>/INI/VER
From:
DLO:
To:
DLl:
The following warning message from BRU reminds you
disk being copied is not hardware bootable:

that

the

BRU - This disk will not contain a hardware bootable system
Only the baseline disk is hardware bootable in the RLOl/02
distribution kit; Therefore; the warnings appear when BRU is
copying all but the baseline disk (RSXM35).
13.

When the disk is successfully copied, BRU issues
following messages to indicate that it has finished:

the

BRU - Starting verify pass
BRU - Completed
14.

To copy the remaining four distribution disks, simply repeat
steps 11, 12, and 13 with each remaining distribution disk
you need to copy for your system generation.

15.

To exit BRU ater you have finished copying all
the backup
sets you need, type CTRL/Z in response to the BRU prompt.

At this point, you have completed the disk-to-disk copy of the
distribution kit and are ready to bootstrap the baseline system again
and generate your RSX-llM system.
Refer to Appendix B for information
on bootstrapping your baseline disk.
Then turn to Chapter 3 for
details on the structure of SYSGEN.
It is important that you read
Chapter 3 before you begin generating your system.

2.3.2

Copying Kits On-Line

The following seven sections describe procedures for copying magnetic
tape and disk distribution kits using a host computer already running
an RSX-llM system.
If you have a big disk magnetic tape kit, read Section 2.3.2.1 next.
If you have an RC25 disk kit, read Section 2.3.2.2 next.
If you have an RK06/07
2.3.2.3 next.

1600

bpi

magnetic

tape

kit,

read

Section

If you have an RK06/07 800 bpi magnetic tape kit, read Section 2.3.2.4
next.
If you have an RK06/07 disk kit, read Section 2.3.2.5 next.
If you have an RLOl/02 1600 bpi magnetic tape kit
2.3.2.6 next.

kit,

read

Section

If you have an RLOl/02 800 bpi magnetic tape kit, read Section 2.3.2.7
next.
If you have an RLOl/02 disk kit, read Section 2.3.2.8 next.

2-31

GUIDE TO COPYING THE DISTRIBUTION KITS
2.3.2.1 Copying the Big Disk Magnetic Tape Kit On-Line - Use the
following procedure to copy either the big disk 1600 bpi tape kit or
the big disk SOO bpi tape kit using the host computer on line.
You
must use the disk copy of the distribution kit to generate an RSX-llM
system. The tape kit may serve as the permanent backup copy.
The
output disk or the scratch disk referred to in this section is the
blank disk you intend to use for the target system disk.

You will need one scratch disk to copy the distribution kit.
(Place a
physical label on the disk so that the scratch disk represents the
backup set name in the distribution kit.) If the disk you intend to
copy to is either an RASO disk or an RASl disk, the fixed disk is the
scratch disk. The type of scratch disk you use must be compatible
with your particular big disk kit.
If your scratch disk is a
fixed-media disk, that disk cannot be the disk that the current system
is running on.
You should format removable-media scratch disks
(using the FMT
utility)
and check either fixed- or removable-media scratch disks for
bad blocks (using the BAD utility} before copying the distribution kit
to them.
Refer to the RSX-llM/M-PLUS Utilities Manual for details on
using BAD and FMT.
To copy your distribution tapes
perform the following steps:
1.

disk

using

on-line

system,

If you are using a multiuser system, allocate the appropriate
disk and tape drives for the media to be used. For example,
if you load your distribution tapes on a TU16 magnetic tape
drive and copy the tapes to an RM02, allocate the devices as
follows:
>ALL DRO:
>ALL MMO:

Load the distribution
magnetic tape drive.

kit

tape

labelled

RSXM35

the

Load the scratch disk, physically labelled RSXM35,
in the
drive and spin up the disk.
If your big disk media is either
the RASO or the RASl
(both fixed-media disks)
or the
fixed-media portion of the RC25, the fixed-media disk serves
as the scratch disk.
NOTE
The disk volume should not be mounted.
If the disk
is mounted as a Files-11 device, BRU will issue the
following warning message:
BRU - *FATAL* - Privilege violation

Invoke the Backup and Restore Utility
(BRU)
and enter the
command line to copy the tape to disk. For example, to copy
the distribution tape to the RM02 disk, enter the following
command to BRU:
)BRU
BRU>/BAC:RSXM35/INI/REW/DEN:l600/VER (1600 bpi tape)
BRU>/BAC:RSXM35/INI/REW/DEN:800/VER (SOO bpi tape)
From;
MMO:
To:
DRO:
BRU - Starting Tape 1 on MMO:

2-32

GUIDE TO COPYING THE DISTRIBUTION KITS

The BRU /BAC (backup set) switch specifies the backup set
be copied.

The BRU /INI (initalize) switch initalizes the disk volume to
which BRU is copying.
The BRU /REW (rewind) switch ensures that
completely rewound before BRU begins to copy.

the

tape

The BRU /DEN (density) switch specifies the density (bpi)
which the tape was written.

The BRU /VER (verify) switch causes BRU to verify the data
after it is copied. BRU issues the following messages to the
terminal indicating it has begun to verify the data copied:
BRU - End of Tape 1 on MMO:
BRU - Starting verify pass Tape 1 on MMO:
NOTE
If the verify fails, do not attempt the system
generation
without
first
retrying
the backup
operation. If the verify fails again, retry the
backup operation using a new output disk. If the
verify fails once again, it is likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.
When the tape is successfully copied and verified, BRU issues
the following messages:
BRU - End of Tape 1 on MMO:
BRU - Completed
5.

If your distribution kit contains two 800 bpi tapes, remove
the first distribution tape from the drive and replace it
with the second distribution tape (labelled 2/2).
When you have loaded the second tape, put the magnetic tape
drive on-line. BRU will proceed to copy the second tape and
issue the following message:
BRU - Starting Tape 2 on MMO:
The message indicates that BRU has begun copying the contents
of the second distribution tape to disk.
(BRU also verifies
the second reel). When the tape is successfully copied, BRU
returns the following messages to indicate that it has
finished:
BRU BRU BRU BRU -

End of Tape 2 on MMO:
Starting verify pass Tape 2 on MMO:
End of Tape 2 on MMO:
Completed

BRU>~TRLz1

>
You may then unload the second distribution tape.
At this point, you have completed the tape-to-disk copy and are ready
to generate your RSX-llM system. Before you begin generating
system, it is important that you read Chapter 3 for details on
structure of SYSGEN.
2-33

GUIDE TO COPYING THE DISTRIBUTION KITS
2.3.2.2 Copying the RC25 Disk Kit On-Line - Use the
following
procedure to copy the RC25 disk kit using the host computer on line.
The output disk or the scratch disk referred to in this section is the
blank disk you intend to use for the target system disk.
You will need one scratch disk {presumably the
copy the distribution disk.

disk)

You should check the scratch disks for bad blocks {using the
utility)
before
copying
the distribution kit.
Refer to
RSX-llM/M-PLUS Utilities Manual for details on using BAD.

BAD
the

To copy your distribution disk using an on-line
following steps:

the

fixed-media

system,

perform

If you are using a multiuser system, allocate the appropriate
disk drives for the media to be used. F-or example, allocate
the devices as follows:
>ALL DUO:
>ALL DUl:

Load the distribution disk labelled RSXM35 in DUO:, and
up both disks.

spin

NOTE
The disk volume should not be mounted. If the disk
is mounted as a Files-11 device, BRU will issue the
following warning message:
BRU - *FATAL* - Privilege violation
When copying the distribution disks, it is a good idea
write protect the disk from which you are copying data.
3.

Invoke the Backup and Restore Utility (BRU) and enter the
following command line to copy the distribution disk to the
scratch {fixed-media) disk:
>BRU
BRU>/INI/VER
From:
DUO:
To:
DUl:
The BRU /INI (initialize) switch initializes the disk
to which BRU is copying.

volume

2-34

GUIDE TO COPYING THE DISTRIBUTION KITS
NOTE
If the verify fails, do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again,
retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.
4.

When the distribution disk is successfully copied, BRU issues
a message at your terminal to indicate that it has finished:
BRU - Completed
BRU> (CTRL z)

>
Spin down the disks, replace the distribution kit disk with a
scratch disk, and spin up both disks.
At this point, you have completed the disk=to=disk copy of the
distribution kit and are ready to generate your RSX-llM system.
Before you begin generating your system, it is important that you read
Chapter 3 for details on the structure of SYSGEN.

2.3.2.3 Copying the RK06/07 1600 bpi Magnetic Tape Kit On-line - Use
the following procedure to copy the RK06/07 1600 bpi tape kit using
the host computer on line.
You must use a disk copy of the
distribution kit to generate an RSX-llM system&
The tape kit may
serve as the permanent backup copy.
The output disk or the scratch
disk referred to in this section is the blank disk you intend to use
for the target system disk.
You will need two scratch disks to copy the distribution tape.
(Place
physical label on each disk so that the scratch disks represent the
backup set names in the distribution kit.)

You should format the scratch disks (using the FMT utility) and check
them for bad blocks
(using the BAD utility)
before copying the
distribution kit.
Refer to the RSX-llM/M-PLUS Utilities Manual for
details on using BAD and FMT.
To copy your distribution tape
perform the following steps:

disk

using

on-line

system,

If you are using a multiuser system, allocate the appropriate
disk and tape drives for the media to be used.
For example,
if you load your distribution tape on a TU16 magnetic tape
drive and copy the tape to RK06s or RK07s, allocate the
devices as follows:
>ALL OMO:
>ALL MMO:

Load a scratch disk physically labelled
appropriate drive and spin up the disk.

RSXM35

NOTE
The disk volume should not be mounted.
If the disk
is mounted as a Files-11 d~vice, BRU will issue the
following warning message:
BRU - *FATAL* - Privilege violation

2-35

the

GUIDE TO COPYING THE DISTRIBUTION KITS
3.

switch specifies the backup set

Ths BRU /!NI (initialize) switch initializes the disk
to which BRU is copying.
The BRU /REW
(rewind)
switch ensures that
completely rewound before BRU begins to copy.

the

volume
tape

The BRU /DEN (density) switch specifies the density (bpi)
which the tape was written.

The BRU /VER (verify) switch causes BRU to verify the data
after it is copied.
BRU issues the following message
indicating that it has begun to verify the data copied:
BRU - End of Tape 1 on MMO:
BRU - Starting verify pass Tape 1 on MMO:
NOTE
If the verify fails,
do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again,
retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.
4.

After the RSXM35 backup set portion of the tape has been
successfully copied to the disk, BRU issues the following
message on your terminal:
BRU - End of Tape 1 on MMO:
BRU - Completed

Remove the disk labelled RSXM35 from the drive,
replace it
with the scratch disk labelled CLISRC, and spin up the disk.

Enter the command line to
distribution tape to disk:

BRU

copy

the

rest

the

BRU>/BAC:CLISRC/INI/DEN:l600/VER
From:
MMO:
To:
OMO:
The BRU /REW switch is optional because the tape should
already be correctly positioned to copy the CLISRC backup set
portion of the distribution tape.

2-36

GUIDE TO COPYING THE DISTRIBUTION KITS
7.

After the CLISRC backup set portion of the distribution tape
has been successfully copied to the disk, BRU issues the
following messages at your terminal:
BRU - End of Tape 1 on MMO:
BRU - Starting verify pass Tape 1 on MMO:
BRU - End of Tape 1 on MMO:
BRU - Completed
BRU> (CTRL/Z)

>
At this point, you have completed the tape-to-disk copy and are ready
to generate your RSX-llM system.
Before you begin generating your
system, it is important that you read Chapter 3 for details on the
structure of SYSGEN.

2.3.2.4

Copying the RK06/07 800 bpi Magnetic Tape Kit On-Line - Use
the following procedure to copy the RK06/07 800 bpi tape kit using the
host computer on line. You must use a disk copy of the distribution
kit to generate an RSX-llM system.
The tape kit may serve as the
permanent backup copy.
The output disk or the scratch disk referred
to in this section is the blank disk you intend to use for the target
system disk.
You will need two scratch disks
to copy the distribution tapes.
(Place a physical label on each disk so that the scratch disks
represent the backup set names in the distribution kit.)
You should format the scratch disk (using the FMT utility)
and check
it for bad blocks
(using the BAD utility)
before copying the
distribution kit to it.
Refer to the RSX-llM/M-PLUS Utilities Manual
for details on using BAD and FMT.
To copy your distribution tapes
perform the following steps:
1.

disk

using

on-line

system,

If you are using a multiuser system, allocate the appropriate
disk and tape drives for the media to be used.
For example,
if you load your distribution tapes on a TU16 magnetic tape
drive and copy the tapes to either RK06s or RK07s, allocate
the devices as follows:
>ALL DMO:
>ALL MMO:

Load the first distribution tape on the drive.
The
should be identified by the backup set label RSXM35.

tape

Load the scratch disk physically labelled
appropriate drive and spin up the disk.

the

RSXM35

NOTE

The disk volume should not be mounted.
If the disk
is mounted as a Files-11 device, BRU will issue the
following warning message:
BRU - *FATAL* - Privilege violation

2-37

GUIDE TO COPYING THE DISTRIBUTION KITS
4.

Invoke the Backup and Restore Utility
(BRU)
and enter the
command line to copy the first tape to disk. For example,
enter the following command line to BRU:
>BRU
BRU>/BAC:RSXM35/INI/REW/DEN:800/VER
From:
MMO:
To:
OMO:
BRU - Starting Tape 1 on MMO:
The BRU /BAC (backup set) switch specifies the backup set
be copied.
The BRU /INI (initialize) switch initializes the disk
to which BRU is copying.
The BRU /REW
(rewind}
switch ensures that
completely rewound before BRU begins to copy.

the

volume
tape

The BRU /DEN (density) switch specifies the density (bpi}
which the tape was written.

The BRU /VER (verify) switch causes BRU to verify the data
after it is copied. BRU issues the following messages to the
terminal indicating it has begun to verify the data copied:
BRU - End of Tape 1 on MMO:
BRU - Starting verify pass Tape 1 on MMO:
NOTE
If the verify fails, do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again, retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.
5.

When the first tape is successfully copied and verified,
issues the following messages at your terminal:

BRU

BRU - End of Tape 1 on MMO:
BRU - Completed

Remove the first distribution tape from the drive and replace
it with the second distribution tape, labelled CLISRC.
Remove the disk iabeiied RSXM35 from the ar1ve,
replace it
with the second scratch disk labelled CLISRC, and spin up the
disk.

Enter the command line to BRU to copy the second distribution
tape to disk:

BRU>/BAC:CLISRC/IN!/REW/DEN:BOO/VER
From:
MMO:
To:
OMO:
BRU - Starting Tape 1 on MMO:

2-38

GUIDE TO COPYING THE DISTRIBUTION KITS
8.

When the tape is successfully copied, BRU returns
following messages to indicate that it has finished:

the

BRU - End of Tape 1 on MMO:
BRU - Starting verify pass Tape 1 on MMO:
BRU - End of Tape 1 on MMO:
BRU - Completed
BRU> (CTRL/Z)

>
You may then unload the second distribution tape and the
disk.

new

At this point, you have completed the tape-to-disk copy and are ready
to generate your RSX-llM system.
Before you begin generating your
system, it is important that you read Chapter 3 for details on the
structure of SYSGEN.

2.3.2.5 Copying the RK06/07 Disk Kit On-Line - Use the following
procedure to copy the RK06/07 disk kit using the host computer on
line.
The output disk or the scratch disk referred to in this section
is the blank disk you intend to use for the target system disk.
You will need two scratch disks to copy the distribution disks.
(Place a physical
label on each disk so that the scratch disks
represent the labels on the respective disks in the distribution kit.)
You should format the scratch disks (using the FMT utility) and check
them for bad blocks
(using the BAD utility)
before copying the
distribution kit.
Refer to the RSX-llM/M-PLUS Utilities Manual
for
details on using BAD and FMT.
To copy your distribution disk using an on-line
following steps:
1.

system,

perform

the

If you are using a multiuser system, allocate the appropriate
disk drives for the media to be used.
For example, allocate
the devices as follows:
>ALL DMO:
>ALL DMl:

Load the distribution disk labelled RSXM35
in DMO:;
then
load the scratch disk labelled RSXM35 in DMl:, and spin up
both disks.
NOTE
The disk volume should not be mounted.
If the disk
is mounted as a Files-11 device, BRU will issue the
following warning message:
BRU - *FATAL* - Privilege violation
When copying the distribution disks, it is a good
idea
write protect the disk from which you are copying data.

2-39

GUIDE TO COPYING THE DISTRIBUTION KITS
3.

(BRU)
and enter the
Invoke the Backup and Restore Utility
For example, enter the
command line to copy the disk.
following command line to BRU:
>BRU
BRU>/INI/VER
From:
OMO:
To:
DMl:
The BRU /INI (initialize) switch initializes the disk
to which BRU is copying.

volume

The BRU /VER (verify) switch causes BRU to verify the data
after
it is copied. BRU issues the following message to the
terminal indicating it has begun to verify the data copied:
BRU - Starting verify pass
NOTE
If the verify fails,
do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again,
retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.
4.

When the distribution disk is successfully copied, BRU issues
a message at your terminal to indicate that it has finished:
BRU - Completed
Spin down both disks and remove them.
Replace the first
distribution disk with the second one,
labelled CLISRC.
Replace the new copy of RSXM35 with the second scratch disk,
and spin up both disks.
Again, write protect the disk from
which you are copying data.

Enter the command line to BRU to copy the disks:
BRU>/INI/VER
From:
OMO:
To:
DMl:

When the second distribution disk volume is successfully
copied and verified, BRU issues the following message:
BRU - Starting verify pass
BRU - Completed
BRU> (CTRL/z)

>
At this point, you have completed the disk-to-disk copy of the
distribution kit and are ready to generate your RSX-llM system.
Before you begin generating your system, it is important that you read
Chapter 3 for details on the structure of SYSGEN.

2-40

GUIDE TO COPYING THE DISTRIBUTION KITS
2.3.2.6 Copying the RLOl/02 1600 bpi Magnetic Tape Kit On-line - Use
the following procedure to copy the RLOl/02 1600 bpi tape kit using
the host computer on line.
You must use a disk copy of the
distribution kit to generate an RSX-llM system.
The tape kit may
serve as the permanent backup copy.
The output disk or the scratch
disk referred to in this section is the blank disk you intend to use
for the target system disk.
You will need six scratch disks to copy the entire distribution tape.
(Place a physical label on each disk so that the scratch disks
represent the backup set names in the distribution kit.) However, only
the first three backup sets
(RSXM35, EXCPRV, and RLUTIL) are used
during a system generation. See the post-system generation guidelines
in Chapter 6 to determine whether or not you need to copy the three
remaining backup sets.
You should check the scratch disks for bad blocks
(using the BAD
utility)
before copying the distribution kit to it.
Refer to the
RSX-llM/M-PLUS Utilities Manual for details on using BAD and FMT.
To copy your distribution tape
perform the following steps:
1.

disk

using

on-line

system,

If you are using a multiuser system, allocate the appropriate
disk and tape drives for the media to be used.
For example,
if you load your distribution tape on a TU16 magnetic tape
drive and copy the tape to either RLOls or RL02s, allocate
the devices as follows:
>ALL DLO:
>ALL MMO:

Load a scratch disk physically labelled
appropriate drive and spin up the disk.

RSXM35

the

NOTE
The disk volume should not be mounted.
If the disk
is mounted as a Files-11 device, BRU will issue the
following warning message:
BRU - *FATAL* - Privilege violation
3.

Invoke the Backup and Restore Utility
(BRU)
and enter the
command line to copy the first backup set on the tape to
disk.
For example, enter the following command line to BRO:
>BRO
BRU>/BAC:RSXM35/INI/REW/DEN:l600/VER
From:
MMO:
To:
DLO:
BRU - Starting Tape 1 on MMO:
The BRO /BAC (backup set) switch specifies the backup set
be copied.
The BRO /INI (initialize) switch initializes the disk
to which BRO is copying.
The BRU
(rewind)
switch ensures that
completely rewound before BRO begins to copy.

2-41

the

volume
tape

GUIDE TO COPYING THE DISTRIBUTION KITS
The BRU /DEN (density) switch specifies the density (bpi)
which the tape was written.

The BRU /VER (verify) switch causes BRU to verify the data
after it is copied.
BRU issues the following messages
indicating that it has begun to verify the data copied:
BRU - End of Tape 1 on MMO:
BRO - Starting verify pass Tape 1 on MMO:
NOTE
If the verify fails, do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again, retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.
4.

After the RSXM35 backup set portion of the tape has been
successfully copied to the disk, BRU issues the following
messages at your terminal:
BRO - End of Tape 1 on MMO:
BRU - Completed

Remove the first disk labelled RSXM35 from the drive, replace
it with the second scratch disk labelled EXCPRV, and spin up
the disk.

Enter the command line to BRU to copy the EXCPRV
portion of the distribution tape to disk:

backup

set

BRU>/BAC:EXCPRV/INI/DEN:l600/VER
From:
MMO:
To:
DLO:
Starting Tape 1 on MMO:
The BRU /REW switch is optional because the tape should be
correctly positioned to copy the EXCPRV backup set portion of
the distribution tape.
The following message from BRO reminds you
set being copied is not hardware bootable:

that

the

backup

BRO - This disk will not contain a hardware bootable system
Only the baseline disk is hardware bootable in the RLOl/02
distribution kit. Therefore, the warnings appear when BRU is
copying all but the baseline disk (RSXM35).

After the EXCPRV backup set portion of the distribution tape
has been successfully copied to the disk, BRU issues the
following messages at your terminal:
BRU
BRO
BRO
BRO

End of Tape 1 on MMO:
Starting verify pass Tape 1 on MMO:
End of Tape 1 on MMO:
Completed

2-42

GUIDE TO COPYING THE DISTRIBUTION KITS
8.

To copy the four remaining backup sets on the distribution
tape to the four scratch disks, repeat steps 5, 6, and 7 and
reolace the backup set label in the BRU command line with the
backup set label of the portion of the distribution tape to
be copied. Table 2-1 lists the RLOl/02 backup set names in
the order that you should copy them.
Be sure that the
scratch disks to which you are copying each backup set have
been checked for bad blocks using the BAD utility.

To exit BRU after you have finished copying all the backup
sets you need, type CTRL/Z in response to the BRU prompt.

At this point, you have completed the tape-to-disk copy and are ready
to generate your RSX=llM system. Before you begin generating your
system, it is important that you read Chapter 3 for details on the
structure of SYSGEN.

2.3.2.7 Copying the RLOl/02 800 bpi Magnetic Tape Kit On-Line - use
the following procedure to copy the RLOl/02 800 bpi tape kit using the
host computer on line. You must use a disk copy of the distribution
kit to generate an RSX-llM system. The tape kit may serve as the
permanent backup copy. The output disk or the scratch disk referred
to in this section is the blank disk you intend to use for the target
system disk.
You will need six scratch RLOl or RL02 disks to copy the entire tape
kit.
(Place a physical label on each disk so that the scratch disks
represent the backup set names in the distribution kit.) However, only
the first three backup sets
(RSXM35, EXCPRV, and RLUTIL) are used
during a system generation. See the post-system generation guidelines
in Chapter 6 to determine whether or not you need to copy the three
remaining backup sets.
You should check the scratch disks for bad blocks (using the BAD
utility) before copying the distribution kit to it. Refer to the
RSX-llM/M-PLUS Utilities Manual for details on using BAD and FMT.
To copy your distribution tapes
perform the following steps:
1.

disk

using

on-line

system,

If you are using a multiuser system, allocate the appropriate
disk and tape drives for the media to be used. For example,
if you load your distribution tapes on a TU16 magnetic tape
drive and copy the tapes to either RLOls or RL02s, allocate
the devices as follows:
>ALL DLO:
>ALL MMO:

Load the first distribution tape,
drive.

labelled

RSXM35,

the

Load the scratch disk physically labelled
appropriate drive and spin up the disk.

RSXM35

the

NOTE
The disk volume should not be mounted.
If the disk
is mounted as a Files-11 device, BRU will issue the
following warning message:
BRU - *FATAL* - Privilege violation
2-43

GOIDE TO COPYING THE DISTRIBUTION KITS

Invoke the Backup and Restore Utility
(BRU)
and enter the
command line to copy the tape to disk.
For example, enter
the following command line to BRU:
>BRU
BRU>/BAC:RSXM35/INI/REW/DEN:800/VER
From:
MMO:
To:
DLO:
BRU - Starting Tape 1 on MMO:
The BRU /BAC (backup set) switch specifies the backup set
be copied.
The BRU /INI (initialize) switch initializes the disk
to which BRU is copying.
The BRU /REW
(rewind)
switch ensures that
completely rewound before BRU begins to copy.

the

volume
tape

The BRU /DEN (density} switch specifies the density (bpi)
which the tape was written.

If the verify fails, do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again,
retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit
is defective and should be
replaced or your hardware needs to be checked.
5.

After the RSXM35 backup set portion of the tape has been
successfully copied to the disk, BRU issues the following
messages at your terminal:
BRU - End of Tape 1 on MMO:
BRU - Completed

Remove the first disk labelled RSXM35 from the drive, replace
it with the second scratch disk labelled EXCPRV, and spin up
the disk.

Enter the command line to BRU to copy the EXCPRV
portion of the distribution tape to disk:

backup

set

BRU>/BAC:EXCPRV/INI/DEN:BOO/VER
From:
MMO:

To:

DLO:

BRU - Starting Tape 1 on MMO:
The BRU /REW switch is not necessary because the tape should
already be correctly positioned to copy the EXCPRV backup set
portion of the distribution tape.

2-44

GUIDE TO COPYING THE DISTRIBUTION KITS
The following warning message from BRU reminds you
backup set being copied is not hardware bootable:

that

the

After the EXCPRV backup set portion of the distribution tape
has been successfully copied to the disk, BRU issues the
following messages at you terminal:
BRU BRU BRU BRU -

End of Tape 1 on MMO:
Starting verify pass Tape 1 on MMO:
End of Tape l on MMO:
Completed

Repeat steps 6, 7, and 8 until you have sucessfully copied
the RLUTIL backup set portion of the distribution tape onto a
scratch disk of the same name
{the third backup set and
disk) •

10.

Remove the first distribution tape from the drive and replace
it with the second tape labelled MCRSRC.
Remove the disk labelled RLUTIL from the drive and replace it
with the next scratch disk, labelled MCRSRC, and spin up the
disk.

11.

Enter the command line to BRU to copy the MCRSRC
portion of the second distribution tape:

backup

set

BRU>/BAC:MCRSRC/INI/REW/DEN:800/VER
From:
MMO:
To:
DLO:
12.

To copy the two remaining backup sets on the
second
distribution tape to the two scratch disks, simply repeat
steps 6, 7, and 8 and replace the backup set label in the BRU
command line with the backup set label of the portion of the
distribution tape to be copied. Table 2-1 lists the RLOl/02
backup set names in the order that you should copy them.
Be
sure that the scratch disks to which you are copying each
backup set have been checked for bad blocks using the BAD
utility.

13.

To exit BRU after you have finished copying all the backup
sets you need, type CTRL/Z in response to the BRU prompt.

At this point, you have completed the tape-to-disk copy and are ready
to generate your RSX-llM system. Before you begin generating your
system, it is important that you read Chapter 3 for details on the
structure of SYSGEN.

2.3.2.8 Copying the RLOl/02 Disk Kit On-Line - Use the following
procedure to copy the RLOl/02 disk kit using the host computer on
line. The output disk or the scratch disk referred to in this section
is the blank disk you intend to use for the target system disk.

2-45

GOIDE TO COPYING THE DISTRIBUTION KITS
You will need six scratch RLOl or RL02 disks to copy the entire
distribution kit.
(Place a physical label on each disk so that the
scratch disks represent the labels on the respective disks
in the
distribution kit.) However, only the first three backup sets (RSXM35,
EXCPRV, and RLUTIL) are used during a
system generation.
See the
post-system generation guidelines in Chapter 6 to determine whether or
not you need to copy the three remaining backup sets.
You should check the scratch disks for bad blocks
(using the BAD
utility)
before copying the distribution kit to it. Refer to the
RSX-llM/M-PLUS Utilities Manual for details on using BAD and FMT.
To copy your distribution
following steps:
1.

kit

on-line

system,

perform

the

If you are using a multiuser system, allocate the appropriate
disk drives for the media to be used.
For example, allocate
the devices as follows:
>ALL DLO:
>ALL DLl:

Load the distribution disk physically labelled RSXM35
in
DLO:,
then load the scratch disk, labelled RSXM35, in DLl:,
and spin up both disks.
NOTE
The disk volume should not be mounted.
If the disk
is mounted as a Files-11 device, BRU will issue the
following warning message:
BRU - *FATAL* - Privilege violation
When copying the distribution disks, it is a good
idea
write protect the disk from which you are copying data.

Invoke the Backup and Restore Utility
(BRU)
and enter the
command line to copy the disk.
For example, enter the
following command line to BRU:
>BRU
BRU>/INI/VER
From:
DLO:
To:
DLl:
The BRU /INI (initialize) switch initializes the disk
to which BRU is copying.

volume

The BRU /VER (verify) switch causes BRU to verify the data
after
it is copied.
BRU issues the following message
indicating that it has begun to verify the data copied:
BRU - Starting verify pass

2-46

GUIDE TO COPYING THE DISTRIBUTION KITS
NOTE
If the verify fails, do not attempt the system
generation
without
first
retrying
the backup
operation.
If the verify fails again,
retry the
backup operation using a new output disk.
If the
verify fails once again, it is likely that either
your distribution kit is defective and should be
replaced or your hardware needs to be checked.
4.

When the disk is successfully copied and verified, BRU issues
the following message:
BRU - Completed
Spin down the disks and
remove
them.
Replace
the
distribution disk with the next one to be copied.
Replace
the new disk copy with the next scratch disk.
Spin up both
disks again remembering to write-protect the disk from which
you are copying data.

Enter the command line to BRU to copy the
disk:

distribution

BRU>/INI/VER
From:
DLO:
To:
DLl:
The following warning message from BRU reminds you
disk being copied is not hardware bootable:

that

the

BRU - This disk will not contain a hardware bootable system
Only the baseline disk is hardware bootable in the RLOl/02
distribution kit. Therefore, the warnings appear when BRU is
copying all but the baseline disk (RSXM35).
When the disk is successfully copied, BRU returns
following messages to indicate that it has finished:

the

BRU - Starting verify pass
BRU - Completed
You may then unload the distribution disk and
backup set.

the

new

disk

To copy the remaining four distribution disks, repeat steps 4
and 5 with each remaining distribution disk you need to copy
for your SYSGEN.

To exit BRU after you have finished copying all the
sets you need, type CTRL/Z in response to BRU prompt.

backup

At this point, you have completed the disk-to-disk copy of the
distribution kit and are ready to generate your RSX-llM system.
Before you begin generating your system, it is important that you read
Chapter 3 for details on the structure of SYSGEN.

2-47

CHAPTER 3
STRUCTURE AND CONCEPTS OF SYSGEN

The system generation procedure, called SYSGEN, is a series of related
Indirect command files.
SYSGEN displays questions that require you to
provide information concerning your target system hardware,
Executive
options, and general system features.
SYSGEN uses that information to
assemble and task build an RSX-llM operating system specifically
tailored to your needs.
This chapter discusses the general concepts and structure of SYSGEN.
It separates SYSGEN into its logical parts and defines the purpose of
each. This chapter also describes options that add flexibility and
ease of use to the SYSGEN procedure. These options allow you to
answer a minimum number of questions.

3.1

THE LOGICAL PARTS OF SYSGEN

There are three major parts to SYSGEN called phases.
These three
phases divide SYSGEN logically, based on the major activity in each
phase. Each phase of SYSGEN requires that you answer a series of
questions.
Those answers supply data necessary for creating specific
files during each phase of SYSGEN.
SYSGEN then uses those files to
produce an operating system that runs on your PDP-11 processor.

3.1.1

Phase I

Phase I is the assembly phase of SYSGEN.
After you answer the
questions in Phase I, SYSGEN uses your responses to assemble the
Executive, a subset of MCR modules, the device drivers, and any
industrial or laboratory I/O subsystems you may select.
Phase I is the largest of the three phases of SYSGEN;
it has more
questions than the other SYSGEN phases. These questions are logically
divided into seven sections.
Each section focuses on specific
function of your RSX-llM system.
SYSGEN pauses at the end of some sections to allow you the option to
go back and correct any mistakes you may have made in a particular
section without having to answer again all of the questions prior to
that section.
In this way, you can define your RSX-llM system section
by section rather than all at once.
(See Section 3.4.1.)
Table 3-1 lists the seven sections in Phase
functions.

3-1

and

their

respective

STRUCTURE AND CONCEPTS OF SYSGEN
Table 3-1
Phase I Sections and Functions
Section

Function

Setup Section

Defines how Phase I executes and the
method for input

Target Configuration
Section

Defines the hardware characteristics
of the target system

Host Configuration
Section

Determines how to handle
map listings

Executive Options
Section

Defines the features you want included
in
your
target
System's RSX-llM
Executive

Terminal Driver
Options Section

Defines the type of terminal driver
you want in your target system as well
as the software features you want the
terminal driver to support

System Options
Section

Defines general system features, some
privileged tasks, and specific system
libraries
to
be included in your
target system

Peripheral Options
Section

Defines
control
peripheral devices
target system

assembly and

information
included in

for
your

At the end of Phase I, SYSGEN has produced object and command files to
be used as input to Phase II.
Chapter 4 contains more information, including all of
relating to SYSGEN Phase I.

3.1.2

the

questions,

Phase II

Phase II is the task-build phase of SYSGEN. After you respond to the
questions in Phase II, SYSGEN uses your responses to task-build the
device drivers and privileged task images.

NOTE
SYSGEN always invokes the V4.l Task
Builder
(TKB)
distributed on your kit.
The new TKB is installed as task ••• TKL.
If you are doing a on-line SYSGEN, other
system users can still use the system's
TKB
without
any
interference from
SYSGEN.

3-2

STRUCTURE AND CONCEPTS OF SYSGEN
Phase II is divided into nine sections, according to the particular
processing activity.
Some of the processing during Phase II does not
require you to answer questions.
Therefore;
even though there are
nine logical sections to Phase II, only five of those sections contain
questions.
Table 3-2 lists the nine sections in Phase II
functions.

with

their

respective

Table 3-2
Phase II Sections and Functions
Section

Function

Setup Section

Defines how Phase II executes,
the
method for input and the saved answer
files that apply.

(Library Build
Section)l

Creates object libraries and adds to
existing libraries.

Executive Task-Build
Section

Task-builds the RSX-llM Executive.

(System Image
Creation Section)l

Creates
the
RSXllM.SYS.

(Full-Duplex Terminal
Driver TaskBuild Section)l

Task-builds the full-duplex
driver (optional).

Loadable Driver
Task-Build Section

Task-builds
drivers.

(Common Block TaskBuild Section) 1

Task-builds the optional FCS resident
library and
industrial or laboratory
device common blocks.

Privileged TaskBuild Section

Task-builds
tasks.

System VMR Section

Creates
the
VMR
SYSVMR.CMD, and runs
the system image.

system

any

image

file

terminal

loadable

device

and system

privileged

command
VMR to

file
augment

1. These sections do not contain questions.
At the end of Phase II, SYSGEN has produced a bootable system image on
which you can begin to run tasks.
Chapter 5 contains more information, including all of
relating to SYSGEN Phase II.

3-3

the

questions,

STRUCTURE AND CONCEPTS OF SYSGEN

3.1.3

VMR

The System VMR Section is a vital step in SYSGEN Phase II.
During
this part of Phase II, SYSGEN creates a file called SYSVMR.CMD that
augments the system image file using Virtual Monitor Console Routine
(VMR) commands.
VMR commands act on the file image on disk, whereas
MCR commands act on the memory-resident system.
(See Chapter 10 in
the
RSX-llM/M-PLUS
System
Management
Guide
for VMR command
descriptions.)
After creating SYSVMR.CMD, SYSGEN asks if you wish to edit it. If you
indicate that you wish to edit SYSVMR.CMD, SYSGEN pauses to allow you
to do so. SYSVMR.CMD does the following:
•

Extends pool size

•

Creates memory partitions

•

Loads all loadable drivers

•

Installs the file system processor (FllACP)

•

Installs privileged and system tasks

•

Sets system parameters

If you are generating your target system in a stand-alone environment,
SYSGEN invokes SYSVMR.CMD during the System VMR Section. When Phase
II ends you are ready to bootstrap your new RSX-llM system.
However, if you are generating your target system from an on-line host
system, the System VMR Section completes without invoking SYSVMR.CMD.
The reason for this is that you must use V4.l of VMR and, in an
on-line environment, SYSGEN cannot tell which version of VMR your
on-line system is running.
See Chapter 5 for more information on executing VMR
system.

3.1.4

from

on-line

Phase I I I

Phase III is a general task-building phase of SYSGEN.
Generally,
after the first two phases of SYSGEN have completed and you have saved
and bootstrapped the new system, yo~ are ready to invoke SYSGEN Phase
III.
(See the SAVE command in either the RSX-llM/M-PLUS System
Management Guide or the RSX-llM/M-PLUS MCR Operations Manual.)
any
privileged
or
In SYSGEN Phase III, you can
task-build
nonprivileged RSX-llM task. Phase III is also useful for rebuilding
RSX-llM tasks that you have patched.
Phase III allows you to rebuild some tasks to link to specific
libraries (such as a resident FCS library), if your target system has
such support.
(Linking tasks to resident libraries can make the task
images
smaller,
an
obvious advantage when memory size is a
limitation.)
Chapter 7 contains more information, including all of
relating to SYSGEN Phase III.

3-4

the

questions,

STRUCTURE AND CONCEPTS OF SYSGEN
3.2

SYSGEN INDIRECT COMMAND FILES

As stated at the beginning of this chapter, SYSGEN is a series of
An ina1rect command file is a text
related Indirect command files.
file containing commands interpreted by
the
Indirect
Command
Processor.
Three major Indirect command files control SYSGEN execution:
•

SYSGEN.CMD controls execution of Phase I

•

SYSGEN2.CMD controls execution of Phase II

•

SYSGEN3.CMD controls execution of Phase III

To invoke any Indirect command file, enter
>@filename
from your terminal.
It is not necessary to include the file type .CMD
when invoking Indirect command files.
Phases I, II, and III of SYSGEN reside in UIC
[200,200].
However,
while it runs, SYSGEN resets the UIC.
If you exit SYSGEN and want to
restart, be sure to set your UIC to [200,200].

Independent SYSGEN Command Files

3.2.1

Some SYSGEN files can or must be invoked outside the normal SYSGEN
procedure.
For example, to rebuild a particular loadable device
driver, you can invoke the file SGNBLDDRV.CMD without having to go
through an entire SYSGEN.
When you invoke any of these files, you
must answer questions that supply the necessary input to
the
particular file.
Those command files that can or must be invoked outside of SYSGEN are:

3.3

•

SGNBLDDRV.CMD can be invoked outside of SYSGEN to build device
drivers

•

SGNKLAB.CMD must be invoked outside of
K-series laboratory devices

BLDLAINIT.CMD can be invoked outside of SYSGEN to task-build
the LPAll-K device initialization task. The microcode that
must be loaded into the LPAll-K is selected during this
procedure.

SYSGEN

build

any

FORMAT OF SYSGEN QUESTIONS

SYSGEN questions allow you to select the features you want for your
target system.
Based on your responses, SYSGEN generates various
command files that control the assembly and task building of your
RSX-llM system.
The Indirect
questions.

Command

Processor

determines

3-5

the

format

SYSGEN

STRUCTURE AND CONCEPTS OF SYSGEN
The general format for SYSGEN questions is an asterisk followed by the
question number,
the text of the question, and a prompt (contained
inside brackets) indicating the type of response required.
Prompts in
SYSGEN questions contain key letters that indicate how to respond to
the question.
See the RSX~llM/M~PLUS MCR Operations Manual for
a
complete description of question formatS"ln an Indirect command file.
SYSGEN questions require one of the following types of response:
•

An ASCII string response

•

A logical response - Y (for yes) or N (for no)

•

A numeric response

Most SYSGEN questions have an implied response, known as the default.
The default is the assumption made by SYSGEN if a particular option is
not explicitly specified. Many of the SYSGEN questions contain the
default response within brackets immediately following the text of the
question.
The default response appears in a given question indicates
the type of response required for that question
(ASCII string,
logical, or numeric).
Press the RETURN key to select the default response for
question (unless there is no default for that question).

any

SYSGEN

The following is a typical SYSGEN question requiring an
response:

ASCII

string

Name of input saved answer file [D:

SYSSAVED.CMD]

[S]:

The prompt [S] at the end of the above question indicates that the
question should be answered with an ASCII string -- in this case, a
file name.
The default appears in this question (indicated by the key
letter D:) within the first set of brackets. Press the RETURN key to
select the default file name of SYSSAVED.CMD for
the input saved
answer file.
The following is a tvoical SYSGEN
(logical) response:

question

requiring

Yes

Do you want DIGITAL Command Language (DCL}? [Y/N]:

The prompt [Y/N] at the end of the question
indicates that the
response should be either a Y (for Yes) or an N (for No).
The implied
default response for this type of question is No,
unless explicitly
stated otherwise.
Some SYSGEN questions requiring a logical Yes or No
response display an explicit default (indicated by the key D:).
The following
response:

44.

typical

SYSGEN

question

Swapping priority [D R:l.-20.

requiring

numeric

D:5.]:

The prompt at the end of the question indicates that the question
requires a numeric response.
The first key letter D inside the
bracket indicates that the response is a decimal number.
The second
key letter R indicates that the range for the response is from 1
through 20.
The third key letter D indicates that the default
response is 5.
Press the RETURN key to enter the default value of 5.

3-6

STRUCTURE AND CONCEPTS OF SYSGEN
The questions in the Peripheral Options Section of SYSGEN Phase I (see
Section 4.8)
are more complicated than the other SYSGEN questions.
During this part of Phase I, SYSGEN provides additional information on
how to answer the questions. The following is a typical question from
the Peripheral Options Section:
Enter [L/R,] vector, CSR, number of drives, unit number of first drive,
[O=offset recovery support/No=no support] for:

DB controller 0 [D: 254,176700,,0,0]:

The information on the line preceding the above question corresponds
to the default field of the question.
The first field [L/R], allows
you to choose whether the driver for the DB controller is loadable (L)
or resident
lKJ.
{You determine whether the default for all drivers
is loadable or resident earlier in Phase I.)
The value 254 in the default field of the question is the vector
address.
The value 176700 is the default CSR address.
The two
successive commas following the CSR address imply that between them
should be the number of drives.
The description in the text for the
question states that there is no default for this value;
it must be
explicitly entered. The zero following the two commas is the default
unit number for the first drive. Finally, the letter O in the last
position of the default field indicates that offset recovery is the
default.
Thus if you were to select all of the possible defaults for the DB
controller, you would enter two commas (,,) followed by the explicit
number of drives (the range is from 1 through 8). So your response to
the question would look like the following:

DB controller 0 [D: 254,176700,,0,0]:

,,4

Everything after the number 4 in your response is implied and need not
be entered when you are selecting the defaults. The two initial
commas are necessary, however, to locate the value for the number of
drives.
When answering the questions in the Peripheral Options Section,
sure to read the accompanying text carefully to avoid mistakes.

When you answer a question with an incorrect value, SYSGEN displays a
message describing the error,
suggests a procedure to correct the
problem, and repeats the question.
Error messages appear alphabetically in Chapter 8.

3.4

LOGICAL ORDER OF SYSGEN QUESTIONS

Many of the options in SYSGEN are interdependent. Some options that
you select automatically include other options.
In such cases, SYSGEN
prints a message on your terminal,
informing you that these other
options have been included. Furthermore, when you select an option
that requires an option you did not previously select, SYSGEN
automatically includes the formerly excluded option and informs you
that it has been included.
Other options are mutually exclusive.
Therefore, even though SYSGEN
questions are numbered in the order of their occurrence in the SYSGEN
command files! not all SYSGEN questions appear on your terminal.

3-7

STRUCTURE AND CONCEPTS OF SYSGEN
For example, if you select DBMS-11 support in Question 1 of the
Executive Option Section of Phase I, SYSGEN automatically includes
support for Files-11 ACP (Question 2 of the Executive Options Section)
and displays a message that Files-11 support has been included:

1. Include support for DBMS-11? [Y/N]: Y
Files-11 ACP support will be included.

If you do not select DBMS-11 support, SYSGEN asks Question 2:

Include support for DBMS-11? [Y/N]:

Files-11 ACP? [Y/N]:

3.4.1

Breakpoints

During execution of Phase I and Phase II, SYSGEN provides breakpoints.
Breakpoints in SYSGEN are pauses at logical points during execution.
There are two types of breakpoints:
•

End-of-Section (EOS) breakpoints

•

End-of-Execution (EOX) breakpoints

These breakpoints cause SYSGEN to pause periodically during processing
to let you review the process just completed
(for example, the
assembly of the Executive source files).
SYSGEN allows you to
override breakpoints so that SYSGEN can execute unattended when that
mode of operation is appropriate.

3.4.1.l EOS Breakpoints - End-of-Section (EOS) breakpoints are pauses
at the end of each section of the SYSGEN procedure. For instance,
there are seven sections in Phase I. You can choose to answer the
questions in all sections without EOS pauses, or you can direct SYSGEN
to pause at each EOS breakpoint.
An End-of-Section breakpoint appears as a question
example:

from

SYSGEN,

for

*EOS* Do you want to: <CR>-continue R-repeat section E-exit P-pause [S]:

This breakpoint in the SYSGEN procedure allows you to:
•

Continue

Repeat the section of questions, perhaps to correct answers

•

Exit the SYSGEN procedure

•

Suspend SYSGEN processing

Note that if you type CTRL/Z in response to any question, SYSGEN exits
cleanly
(that is, all files are closed by the Indirect Command
Processor).

3-8

STRUCTURE AND CONCEPTS OF SYSGEN
3.4.1.2 EOX Breakpoints - End-of-Execution
(EOX)
breakpoints
are
pauses after significant SYSGEN operations, such as a MACRO assembly
or a task-build.
SYSGEN pauses at these points to ensure successful
completion of the operation. When you know that the operation will
execute successfully, you can direct SYSGEN to continue processing
without the breakpoint pauses.
The following EOX breakpoint question appears after
Executive:

assembly

the

*EOX* Did the Executive assemble correctly? [Y/N]:
If your response is Y (for yes), SYSGEN continues to assemble a subset
of MCR modules.
If there are errors in the assembly, your response
should be N (for No) 1 at which point SYSGEN informs you that it
is
pausing to allow you to correct the problem.

3.4.2

Chaining

SYSGEN normally exits at the end of Phase I execution.
However, an
option in the Setup Question Section of Phase I allows SYSGEN to
automatically invoke Phase II when Phase I completes. This process is
called chaining.
When SYSGEN chains to Phase II, it carries the
information supplied in the Setup Section of Phase I
to Phase II,
thereby allowing SYSGEN to bypass many of the Setup Questions in Phase
II.

Chaining is a particularly useful option when you use an input saved
answer file
(see Section 3.5)
or a Standard Function System (see
Section 3.6.2). When you use a
saved answer file and select the
chaining option,
you can generate a system without having to spend
much time answering questions at the terminal.
NOTE
Chaining is only a valid transition from
Phase I
to Phase
II.
SYSGEN cannot
chain from Phase II to Phase III.

3.5

SAVED ANSWER FILES

Whenever you answer a question during Phase I and Phase rI,
SYSGEN
saves your responses by converting them to symbol definitions and
outputs them in saved answer files.
(Appendix A lists the saved
answer symbol definitions.) You can use a saved answer file as input
to another SYSGEN.
When you use saved answer files
as
input, SYSGEN uses the symbol
definitions in the saved answer files as answers to SYSGEN questions.
The questions do not appear on the terminal.
If SYSGEN encounters a
question for which there is no saved answer, it prints the question on
the terminal and waits for a response.
Depending upon how you answer the
and
{optionally)
in Phase II,
containing saved answers for both
one saved answer file for Phase I
Phase II.
In either case, SYSGEN
file.

Setup Questions in SYSGEN Phase
I
you may create either a single file
Phase I and Phase II or you may have
and a separate saved answer file for
always saves your responses
in a

3-9

STRUCTURE AND CONCEPTS OF SYSGEN
NOTE
SYSGEN does not save
responses
to
questions
in the Peripheral Options
Section pertaining to ICR/ICS, OSS/ORS,
or IP11/IP300 devices. SYSGEN also does
not
save
responses
to
questions
pertaining to the task-building of the
LPA initialization code.
SYSGEN asks you to specify a name for the saved answer file.
You may
give the saved answer file (or files) any name or file type that you
wish.
If you want to place your saved answer files in a different UIC
other than the default
[200,200]
and if that UIC does not already
exist, you must first create the UIC using the MCR UFO command.
For
information on the UFO command, see the RSX-llM/M-PLUS MCR Operations
Manual.
Conventions governing file names for saved answer files are the same
as for all RSX-llM file names.
Refer to the RSX-llM/M-PLUS Utilities
Manual for more information on file names.
SYSGEN asks the following question in the Phase I and Phase
Section to allow you to name your saved answer file:

Name of output saved answer file [O:

SYSSAVEO.CMO]

Setup
[S]:

SYSGEN prints a message on the terminal letting you know the name
the output saved answer file to which it saves your responses.

If the system generation process is aborted for any reason
(for
example, if you exit by typing CTRL/Z in response to any question),
the output saved answer file is closed at the point in Phase I or
Phase II where it was interrupted.
If you use that output saved
answer file for input later on, SYSGEN accesses the file, scans it,
and prints a message that the file may be incomplete. That file may
still be successfully used for input up to the point where that last
question was answered in the aborted SYSGEN.
(Before restarting
SYSGEN, remember to reset your UIC to [200,200] .) At that point SYSGEN
begins explicitly asking questions again and creates a new saved
answer output file.
NOTE
If the output saved answer file becomes
locked when you abort a SYSGEN, you can
unlock the file using the PIP
/UN
switch.
See
the
RSX-llM/M-PLUS
Utilities Manual for details on using
the PIP /UN switch.
Saved answer files have a variety of uses.
For instance, you can
create a saved answer file that defines options for several different
target configurations; or you can create multiple saved answer files
that specify different options for the same POP-11 processor. See
Section 3.6.1 for details on creating saved answer files.
You can create saved answer files without having to fully execute
SYSGEN by selecting the option in the Phase I Setup Section that
inhibits execution of MCR commands in SYSGEN. Section 3.6 describes
that option in detail.

3-10

STRUCTURE AND CONCEPTS OF SYSGEN
3.6

VARIOUS APPROACHES TO SYSGEN

Some of the options available in the Setup Section of Phase I and
Phase II can make it significantly easier to generate your system,
particularly if you are generating an RSX-llM system for the first
time.
This section describes those options and how they can
facilitate the SYSGEN process for you.

3.6.1

SYSGEN with MCR Inhibited (PREPGEN)

During the Setup
question:

Section

Phase

SYSGEN

asks

the

following

Do you want to inhibit execution of MCR commands (PREPGEN)? [Y/N]:

This option allows you to perform the logical SYSGEN procedure, answer
SYSGEN questions, and create a saved answer file that you can use as
input to SYSGEN at a more convenient time when you actually generate
your system.

If you respond Yes to this option, SYSGEN displays the questions for
you to answer and creates a saved answer file of your responses.
However, SYSGEN does not process any MCR commands (such as PIP, MAC,
and TKB)
as it normally would and, therefore, does not create your
system.
If you respond No to this question, SYSGEN displays questions for you
to answer, creates a saved answer file of your responses, executes MCR
commands and generates your target RSX-llM system.
If you have never generated an RSX-llM system, or if you are
unfamiliar with RSX-llM V4.l, you may find it helpful to perform a
PREPGEN the first time you perform the SYSGEN procedure.

3.6.2

The Standard Function System

As previously explained, SYSGEN lets you create your own saved answer
files.
In addition, the distribution kit contains a saved answer
file, called SGNSTAND.CMD. SYSGEN uses SGNSTAND.CMD to generate a
Standard Function System when you select it as an option.
When you select the option in Phase I for a Standard Function System,
SYSGEN creates a mapped RSX-llM system that includes nearly all
available options. The Standard Function System provides responses
for SYSGEN questions pertaining to software.
CAUTION
Do
not
modify
SGNSTAND.CMD.

the

contents

This means that SYSGEN automatically answers most of the Phase
Phase II questions.

3-11

and

STRUCTURE AND CONCEPTS OF SYSGEN

The Standard Function System builds an
functionality including:

RSX-llM

system

with

maximum

•

The full-duplex terminal driver (with all valid options)

•

The MIDDLE version of FllACP

•

Support for all layered products

•

The CO:

•

ANSI magtape support

•

FCS resident library support

•

Support for all selected loadable drivers in DRVPAR

•

Default values for
swapping priority)

and NL:

pseudo devices

system

(numeric)

parameters

(such

The only SYSGEN option restricted from the Standard Function System is
support for user-written drivers.
In addition, when you select the
Standard Function System, SYSGEN bypasses EOS and EOX breakpoints and
does not pause for you to edit any files.
For the full list of options included in the Standard Function System,
see Table 3-3.
You can select some SYSGEN options
Function System.
SYSGEN displays
Some user-selectable options are:

when you choose the Standard
those options at your terminal.

• All Target Configuration Section questions

• The Executive Debugging Tool (XDT)
• The memory crash dump device

• Communications products (such as DECnet)
• A user-defined system name
If you are unsure of which options to choose for your system, you can
select the Standard Function System to quickly generate a usable
RSX-llM system. As you become familiar with your system requirements,
you can make more comfortable decisions about which system options are
needed and which options may be unnecessary. You can then create a
saved answer file geared more closely to your specific system
requirements and then generate a new system using that saved answer
file.
The Standard Function System option works like other saved answer
files since SYSGEN uses the symbols defined in that file as responses.
SYSGEN does not display questions on your terminal that are answered
by a saved answer file.
Whenever you select the Standard Function System,
helpful to also select the chaining option.

3-12

you

may

find

STRUCTURE AND CONCEPTS OF SYSGEN
Table 3-3
Options Included in the Standard Function System
Setup Section
Question
5

Option
Mapped system
Target Configuration Section

Question
4

Option

Question

K-series device support

CO:

and NL:

device support

Executive Options Section
Question

Option

DBMS-11 support

Files-11 ACP

RMS bucket locking
and placement control

Non-resident tasks

Loadable task loader

Executive common

Memory management (PLAS)
directives

Send/Receive By Reference
directives

Get Mapping Context
directive

Address checking

I/O rundown

Multiuser protection

ANSI magtape ACP

On-line formatting {FMT)
or diagnostic QIOs

Question

Option

Queue manager and queued
print spooler

Group global event flags

All system directives:
Get Partion Parameters
Get Task Parameters
Send/Receive
Alter Priority
Extend Task
Connect to Interrupt Vector
Get Sense Switch
Set System Time
Stop Bit
Specify Requested Exit AST
Parent/Offspring Tasking
Parent/Offspring Tasking
with Chaining

5 pre-allocated QIO packets

33-word size for the data
transfer vector

5-tick interval for
round-robin scheduling

Highest priority class of
150 for round-robin
scheduling

(continued on next page)

3-13

STRUCTURE AND CONCEPTS OF SYSGEN
Table 3-3 (Cont.)
Options Included in the Standard Function System
Executive Options Section
Question

Question

Option

Loadable device drivers

Lowest priority class of
1 for round-robin scheduling

All drivers loadable
by default

Executive level disk
swapping interval of 30

Asynchronous System Traps
(AST) support

Priority of 5 for
disk swapping

Task termination and device
not ready messages (TKTN)

30-second interval between
printer not ready messages

30-second interval between
card reader not ready
messages

System crash register and
stack dump device CSR
value of 177564

17
19
20

Power fail recovery

Install, request, and
remove on exit

Large (20K)

Logical device assignment

Error logging support

Checkpointing

Disk writecheck

Checkpointing with a system
checkpoint file

Software write-lock support
51

Crash Dump Analysis (CDA)

Rotating pattern in data
lights

CDA output notification
device CSR value of 117564-

Executive

System-controlled partitions

Shuffler support
Terminal Driver Options Section

Question

Option

Question

Full-duplex terminal driver
Terminal Driver Options

120-second unsolicited input
timeout value

Option

Get terminal driver options

Hold-screen mode

Transparant read/write

Pass form feeds directly
to the terminal

Settable case conversion
for input

Automatic carriage
return/line feed

Read after prompt

(continued on next page)

3-14

STRUCTURE AND CONCEPTS OF SYSGEN

Table 3-3 (Cont.)
Options Included in the Standard Function System
Terminal Driver Options Section
Option

Question

Option

Read with no echo

Read with special terminator

CRT rubout support

Terminal-host
synchronization

User terminal input
buffering

Variable-length terminal
input buffering

LA30P support

Hardware unrecoverable input
error notification

Device independent
cursor positioning

Task checkpointable during
terminal input

Unsolicited input character
AST

Write with CTRL/O
cancellation

Breakthrough write

CTRL/R support

Escape sequence handling

Get multiple characteristics

Set multiple characteristics

Systems Options Section
Question

Option

Question

Option

FCS resident library

Digital Command Language
(DCL)

Middle FCP (FCPMDL)
9

Post Mortem Dump (PMD)

Support for 2 user-written
CL Is

Resource Monitoring Display
task (RMD)

Pool monitoring and low
pool recovery

Loadable Driver Task-Build Section (Phase 2)
Option

Question
3

NL:

as the map device

3-15

STRUCTURE AND CONCEPTS OF SYSGEN
3.6.3

The Autoconfigure Option

Of all the questions to be answered in SYSGEN, the most complicated
are those of the Peripheral Options Section in Phase I.
It is not
always convenient to obtain the correct CSR and vector addresses for
your specific peripheral devices. Though SYSGEN provides default CSR
and vector addresses for most devices, there is no guarantee that your
devices correspond to those addresses.
To avoid that type of confusion, direct SYSGEN to Autoconfigure your
hardware. The Autoconf igure option is the first option offered in the
Setup Section of Phase I and is integrated with the SYSGEN procedure.
Autoconfigure is a valid option only if you are generating RSX-llM
from the baseline system (located in UIC [1,54]) supplied with your
RSX-llM V4.l distribution kit. Typically, on-line systems
(that is,
systems running from other than the baseline system) have some disk,
terminal, and CPU activity.
Part of autoconfiguration involves a
complex series of device interrupts, that require that there be no
other activity on the system. Autoconf igure can accurately configure
the hardware only when there is no pending I/O.
In addition, to use
the Autoconf igure results, the host system must be the same as the
target system.
Autoconfigure determines the correct hardware configuration.
a highly desirable option in all but two cases:

This

•

Autoconf igure cannot be used when the host
system
distinctly different from the target system configuration.

•

Autoconf igure cannot be used when the hardware does not
conform to the standard PDP-11 device configuration algorithm.
If your hardware does not conform to this standard, please see
Appendix E for
information on determining the algorithm for
your hardware.

Autoconf igure allows you to add or delete devices as well as
results. See Section 3.6.3.2.

override

3.6.3.1 What Autoconfigure Does - When you select the Autoconfigure
option,
SYSGEN
automatically
determines
the correct hardware
configuration of most (if not all) of your host system: the processor
type, the CSR and vector addresses of your peripheral devices, and any
optional hardware that may be present -- such as Floating Point or
Extended
Instruction
Set
hardware.
SYSGEN displays complete
information from the autoconf iguration at your terminal after the
Autoconfigure has completed.
You may use the Autoconfigure results for responses to questions in
the Target Configuration and Peripheral Options Section in Phase I.
In this case, SYSGEN automatically answers (and, therefore, bypasses)
any questions in those sections for which Autoconfigure results can be
used as responses.
You can also override the results of the
Autoconfigure (see Section 3.6.3.2).
In addition to those devices that are automatically configured, you
may add devices that Autoconfigure does not support. You can do this
by answering Question 15 in the Target Configuration Section, entering
the device names, and the number of controllers.
(See the Target
Configuration Section, Question 15 in Section 4.3 for more information
on adding devices.)

3-16

STRUCTURE ARD CONCEPTS OF SYSGEN
Furthermore, if you use an input saved answer file containing a saved
peripheral configuration and also Autoconfigure the host system
hardware, SYSGEN makes a contiguous list of all of those devices.
Where

there are discrepancies between the devices in the saved answer

file and the Autoconfigured list,
overrides the Autoconfigured list.

the

saved

answer

file

always

If SYSGEN fails to report Autoconfigure results, (described in Example
3-1) within one minute, then Autoconfigure has failed to configure
your hardware. If this occurs, you must rebootstrap the baseline
system and invoke SYSGEN again without using the Autoconfigure option.
When SYSGEN fails to report Autoconfigure results, it is generally an
indication that a severe hardware malfunction has occurred, or you
have not adhered to the standard DIGITAL PDP-11 device configuration
algorithm detailed in Appendix E.
Example 3-1
Processor

T~Pe:

Sample Autoconf igure Output
Hemor~

11/70

Size:

512. Kw

Options:
Floatins Point Processor <FP11>
Extended Instruction Set <EIS>
Extended <22-bit) Addressins
Switch Resister <SWR>
DisPla'!:I Resister
Cache Me111or~
Parit1:1 Memor1:1
Name

Vector

CSR

DKA

220

177404

DMA

RHA

210

224

Unit

T'!:IPe

0
2

RK05
RK05

0
1
2

RK06
RK06
RK07

o_o

TU77

0_1

TU77

RM03

ML11A

RP06
RP06
RP05
RP05

177440

172440

RHB

150

176300

RHC

204

176400

RHD

254

176700
1

2
3
DXA

I•TA
LPA
LPB
YLA
YLB
YMA
YMB
YMC

YHA
YHB
YHC
YHD

264
214
200
270
060
1'??

310
314
324
340
350
360
11?

Remarks

177170
177342
177514
164004
177560
175610
170500
170510
170520
160020
160040

TM03
TH03

Dual access

Failed to interrupt

160060

Failed to interrupt

160100

3-17

STRUCTURE AND CONCEPTS OF SYSGEN
Example 3-2 lists all the remarks that may be output by
with the configuration information.
Example 3-2

Autoconfigure

Autoconf igure Remarks and Meanings

Remark

Meaning

Failed to interrupt

The specified device is either
malfunctioning
or the hardware
configuration is nonstandard which
causes
Autoconf igure to report
unreliable information. Autoconfigure will place three question
marks (???) in the vector field.

Mixed MASSBUS devices

Autoconf igure
has
detected
a
MASSBUS controller configured with
several classes of
peripherals
attached to the same controller,
(such as RM03 and an RP06). Note:
Mixed MASSBUS configurations are
not supported by RSX-llM.

TM02
TM03
TM78

The type of magtape formatter
associated with this slave drive.
Magtape unit numbers are displayed
in the format:
Formatter Unit
number, underscore, Slave
Unit
number (for example, 0 1).

Priority n

Autoconf igure
has
detected
a
device with an interrupt priority
higher than expected.
n is the
actual interrupt priority.

Dual access

The specified unit has the Dual
access
option installed.
Dual
access allows a unit to be shared
by two controllers. Note: Use of
drives in dual-access mode is not
supported on RSX-llM.

???

(in the vector field)

Sector interleaved

See Failed to interrupt.
The
RS03
or
RS04
displayed
supports
sector
interleaving,
which allows the unit to optimize
data accesses.

3.6.3.2 Overriding Autoconfigure Results - When you
select
the
Autoconf igure option, SYSGEN asks a second question that allows you to
override the results of the Autoconfigure. This option directs SYSGEN
to display the Autoconfigure results in the default field of each
question where Autoconfigure would automatically provide a response.
In other words, instead of directing SYSGEN to use Autoconfigure
results as responses to the questions in the Target Configuration and
Peripheral Options Sections without displaying them on the terminal,
each SYSGEN question appears with the Autoconfigure results as the
default instead of the standard default response.
You may then
examine the Autoccnfigure results and either enter different values or
press the RETURN key to input the Autoconfigure result.

3-18

STRUCTURE AND CONCEPTS OF SYSGEN
If you choose not to override the results of Autoconfigure, SYSGEN
automatically answers any question in the Target Configuration and
Peripheral Option Sections, when Autoconfigure has provided responses.
~hP
nnlv PY~Pntion to this is Question 15 in the Taraet Confiauration
Section. This question always appears to allow you to add or delete
devices from your configuration.
----

_ ..... _.i.

-----~-----

------

----

..,,

You can override Autoconfigure results to enter
information not
normally determined by Autoconfigure.
For example, if your system has
four RK06 drives, but one is down with serious hardware problems,
Autoconfigure would only report finding three of them.
However, if
you know that the drive will be repaired soon, you can override the
Autoconfigure results by entering 4 as the number of unit types for
the RK06, instead of the default of 3 provided by Autoconfigure.
Furthermore, you can override Autoconfigure results so that you can
generate a transportable system. For example, if your site has two
PDP-11/34 processors but only one of them (that is, the host system)
has cache memory you can override the results of Autoconfigure by
deselecting the cache memory option to have an RSX-llM system that
runs on either processor.
Table 3-4 lists the devices supported by the Autoconf igure
Devices
that
are
not listed in Table 3-4, as well
malfunctioning devices, cannot be Autoconfigured.

option.
as any

NOTE
Your host system configuration
must
conform to the standard PDP-11 device
configuration
algorithm
for
Autoconf igure
to
report
reliable
information.
(See Appendix E.)

3.6.4

Hardware Supported by Autoconfigure

Autoconfigure supports most standard devices supplied by DIGITAL.
For
those DIGITAL devices in your hardware configuration not supported by
Autoconf igure, SYSGEN asks the appropriate question in the Peripheral
Options Section to get the specific controller information for those
devices.
Autoconfigure does not determine the number of units for DK, DP, OT,
or MT devices.
It does determine the CSR and vector addresses for
those devices.
SYSGEN asks the corresponding questions
in the
Peripheral Options Section that require you to input the number of
units for those devices.
In addition, Autoconfigure only finds those RK05
disks
in
them and are up and spinning at
Autoconfigure.

drives that have
the time of the

Table 3-4 is a list of the hardware supported by Autoconfigure.
Refer
to Appendix E for the algorithm used to assign addresses to devices
attached to the UNIBUS or QBUS.

3-19

STRUCTURE AND CONCEPTS OF SYSGEN
NOTE
Autoconfigure
will
only
run
on
processors
with
Memory
Management
(mapped) hardware.
Also, Autoconfigure
only computes the line frequency of your
processor if a KWll-P is present.
Table 3-4
Hardware Supported by Autoconf igure
Processors (with Memory Management hardware)
PDP-11/23
PDP-11/23-PLUS
MICRO/PDP-11
PDP-11/24
PDP-11/34
PDP-11/35
PDP-11/40
PDP-11/44
PDP-11/45
PDP-11/50
PDP-11/55
PDP-11/60
PDP-11/70

22-Bit Addressing
(Autoconf igure reports the MICRO/PDP-11 as
an 11/23-PLUS.)
18 and 22-Bit Systems
(Autoconfigure reports the 11/35 as an 11/40.)

(Autoconfigure reports the 11/50 as an 11/45.)
(Autoconfigure reports the 11/55 as an 11/45.)

Processor/Memory Options
FP-11
KE-llE
KE-llA/B
KWll-P

KWll-W

FPP - Floating Point Processor
EIS - Extended Instruction Set
EAE - Extended Arithmetic Element
CIS - Commercial Instruction Set
FIS - Floating Instruction Set
Programmable Clock
Cache Memory
Switch Register
Display Register
Parity Memory
Watchdog Timer
I/O Peripherals and Controllers

CT
DB
DD
DK

DL
DM
DP
DR
DS
DT

TAll Tape Cassette
RP04/05/06 Disk Drive
TU58 Cartridge DECtape
RKll/RK05
RLll/RLVll/RLOl Disks (first controller only)
RL211/RLV21/RLV12/RL02 Disks (first
controller only)
RK611/RK711 RK06/RK07 Disks
RP11/RP02/RP03
RM02/RM03/RM05/RM80/RP07 Disk Drives
RS03/RS04 Fixed Head Disks
TC11/TU56 DECtape
(continued on next page)

3-20

STRUCTURE AND CONCEPTS OF SYSGEN
Table 3-4 (Cont.)
Hardware Supported by Autoconf igure
I/O Peripherals and Controllers (Cont.)
DU
DX
DY
EM
LP
MF
MM
MS
MT
PR
pp

RH
YH
YL
YL
YL
YL
YM
YZ

UDASO (RA60/80/81) Controller
RC25 Controller
RQDXl (RD51/RX50) Controller
RXll/RXOl Floppy Disk (first controller only)
RX211/RX02 Floppy Disk (first controller only)
MLll Non rotating Electronic Memory
LP/LS/LV/11/LNOl Line Printer
TU78/TM78 Magtape
TU16/45/77/TE16 Magtape Drives
TS11/TSV05/TU80 Magtape Drives
TM11/TU10/TE10/TS03
PRll/PCll Paper Tape Reader
PCll Paper Tape Punch
RH11/RH70 MASSBUS Controller
DHll Asynchronous Terminal Interface
DLll-A/B Asynchronous Interface (including
DLV)
DLll-C/D/E Asynchronous Interface (including
DLV)
DLll-J Asynchronous Interface (including DLV)
DLll-W Console Interface with/line clock
DMll-BB Modem Controller for DHll
DZll Asynchronous Terminal Interface
(including DZV)

3-21

CHAPTER 4
DETAILS OF SYSGEN PHASE I

This chapter describes the questions in SYSGEN Phase I.
SYSGEN uses
your responses to the questions in Phase I to assemble the source
files for the Executive, device drivers, and any laboratory or
industrial I/O subsystems you select. As explained earlier in Chapter
3, SYSGEN never asks all of the questions described in this chapter.
Therefore, the questions do not always appear on your terminal in
numerical sequence. As long as you know the Phase I section that the
question appears in, you can locate the description of that question
by its number.
The questions are logically divided into seven sections:
•

Setup Section

•

Target Configuration Section

•

Host Configuration Section

•

Executive Options Section

•

Terminal Driver Options Section

•

System Options Section

•

Peripheral Options Section

Example 4-1 (at the end of this chapter)
is an annotated terminal
output from SYSGEN Phase I.
The responses in the example are not
necessarily the same as yours may be. However, the example will help
you to follow the flow of questions from section to section.
Figure 4-1 shows the processing steps that take
Phase I.
INPUT
SAVED ANSWERS
EXPLICIT RESPONSES
AUTOCONFIGURE RESULTS
EXECUTIVE, DRIVER, AND MCA
SUBSET SOURCE FILES

place

ACTION

OUTCOME

ASSEMBLE THE EXECUTIVE,
DRIVERS, AND A SUBSET
OF MCA

EXECUTIVE, DRIVER,
AND MCA SUBSET
OBJECT FILES

during

SYSGEN

PHASE II

ZK-322-81

Figure 4-1 Processing Steps in SYSGEN Phase I

4-1

DETAILS OF SYSGEN PHASE I
4.1

PREPARING FOR PHASE I

Before invoking SYSGEN, make sure you have done the following:

•

If you are using a V4.0 host system,
refer
to
the
RSX-llM/RSX-llS Release Notes before beginning your system
generation.
NOTE
To perform a SYSGEN, your host system must be mapped.
If your host system is not mapped, SYSGEN will display
the following message:
SYSGEN is not supported on
an unmapped host system.
Also, your host system must have at least 64K words of
memory.
If your system has less than 64K words of
memory, SYSGEN will display the following message:
SYSGEN is not supported on a
host system with less than 64KW.

•

If you generate your system from an on-line V4.l host system,
set your UIC to [200,200], assign the logical device SY:
to
your baseline disk, and invoke SYSGEN as follows:
>SET /UIC=[200,200]
>ASN ddu:=SY:
(where ddu: is the baseline disk, RSXM35)
>MOU ddu:RSXM35
>@SYSGEN
The host system must have a null device
successfully generate an RSX-llM system.

•

(NL:)

for

you

If you generate your system from a stand-alone host system,
hardware bootstrap the baseline system (see Appendix B).
Then invoke SYSGEN as follows:
>@SYSGEN

Phase I begins now.

4-2

DETAILS OF SYSGEN PHASE I

SETUP
4.2

SETUP SECTION

This section of questions provides SYSGEN with specific processing
information.
In addition, depending on your responses, it can help to
make your system generation significantly easier.

* 1.

Autoconfigure the host system hardware?

[Y/N]:

If you respond Yes to this question, SYSGEN automatically determines
the exact hardware configuration of your host system:
the processor
type, the CSR and vector addresses of your peripheral devices, and any
optional hardware that may be present -- such as Floating Point or
Extended Instruction Set hardware.
(See Section 3.6.3 for more
information on Autoconfigure.)
SYSGEN displays results from the autoconfiguration at your terminal
after Autoconfigure has completed.
Table 3-3 lists the devices
supported by Autoconfigure. Devices that are not listed in Table 3-3
as well as any malfunctioning devices cannot be autoconfigured.
NOTE
Your host system configuration
must
conform to the standard PDP-11 device
configuration
algorithm
for
Autoconf igure
to
report
reliable
information.
(See Appendix E.)
If you choose this option, you may use the results
of
the
autoconfiguration
for
responses
to
questions
in the Target
Configuration and Peripheral Options Sections.
If you respond Yes to
this question, and No to Question 2, SYSGEN bypasses any questions in
the Peripheral Options and Target Configuration Sections for which
Autoconfigure results can be used as responses.
This question only appears if you are generating
from a mapped RSX-llM baseline system.

* 2.

Do you want to override Autoconfigure results?

RSX-llM

system

[Y/N]:

This question appears only when you respond Yes to Question 1.
If you respond Yes to this question, you
can
override
Autoconfigure
results.
SYSGEN
displays
the
results of
autoconfiguration in the default field of each Peripheral Options
Target Configuration question asked.
You may then examine
Autoconfigure results and either modify them or press the RETURN
to take the default.
(See Section 3.6.3 for more information.)

the
the
and
the
key

If you respond No to this question, Autoconfigure automatically
answers the questions in the Target Configuration Section, except for
the K-series question (Question 4)
and Question 9 or 10 of that
section.

4-3

DETAILS OF SYSGEN PHASE I

SETUP (Cont.)
In addition to answering the Target Configuration Section questions,
Autoconf igure
automatically
answers
all
the questions in the
Peripheral Options Section for which Autoconfigure has results.
NOTE
Autoconf igure determines only the CSR
and vector addresses for DK, DP, DT, and
MT device types.
It cannot determine
the number of units for those devices.
SYSGEN asks the corresponding questions
in the Peripheral Options Section to
allow you to enter the number of units
for those devices.
In addition to those devices that are automatically configured, you
may add devices that Autoconfigure does not support or are not present
on the host system.
You do this by answering Question 15 in the
Target Configuration Section (this question is always asked), with the
device names and number of controllers for
those additional devices
not listed by Autoconfigure.
(See Question 15 for more information on
adding devices.
Also see Section 3.6.3)

* 3.

Do you want to inhibit execution of MCR commands (PREPGEN)?

[Y/N]:

If you respond Yes to this option, SYSGEN displays the questions for
you to answer and creates a saved answer file of your responses.
However, SYSGEN does not process any MCR commands as it normally
would, and,
therefore, does not create your system. When you are
ready to generate you system, you can then use this saved answer file
as input into SYSGEN.
It is recommended that you perform a PREPGEN first.
Doing so has two
advantages:
first,
it requires less time at your terminal to answer
SYSGEN questions;
second, if you are not satisfied with your system
configuration, you can easily change your responses in the saved
answer file rather than do another SYSGEN to change your system
configuration.
When you perform a PREPGEN, SYSGEN:

• Does not make logical device assignments

• Does not delete files from previous SYSGENs
• Does not assemble files
•

Does not create libraries

When you perform a PREPGEN, SYSGEN:
•

Does create the resident driver data base file

•

Does
/DCVMf"

create

partial,

unusable

M7\f"\

\J.'\.U.L~J.·.1¥ eJ..L~'-"J

4-4

Executive

(SYSTB.MAC)
prefix

file

DETAILS OF SYSGEN PHASE I

SETUP (Cont.)
•

Does create a saved answer file

•

Does create the Executive task-build file

•

Does create the full-duplex terminal driver task-build
(if you select the full-duplex terminal driver)

•

Does create the Executive and driver assembly command files

file

If you select this option and if you are using an RLOl/02 distribution
kit, SYSGEN will mount the Executive source disk after you enter the
drive containing this disk (Question 16). The Executive source disk
in the RLOl/02 kit is labelled EXCPRV.
If you respond No to this question, SYSGEN executes MCR
creates your system.

* 4.

Have you made a copy of the distribution kit?

commands

and

[Y/N]:

A copy of the distribution kit ensures that there is a backup copy in
case you inadvertently delete important files or data during the
system generation process.
A backup copy also serves as a base for
future Autopatch updates.
If you respond No, SYSGEN displays the message:
SGN -- You are or will be running on the
the
distribution kit.
Make a copy
procedure and restart.

original
via the

copy of
standard

SYSGEN then exits to allow you to copy the media.
Refer to Chapter 2 if you need help copying your distribution kit.
This question does not appear if you are generating an RSX-118 system
from a host system other than RSX-llM.
This question also does not
appear if your response to Question 3 is Yes.

* 5.

Are you generating an unmapped system?

[Y/N]:

Respond Yes to this question if your target system processor does not
include a Memory Management Unit (such as a KT-11) and if you intend
to generate an unmapped system.
If you generate an unmapped target system from the mapped baseline
system or from a mapped host system, you must invoke Phase III on the
host system to task-build unmapped versions of EDI, PIP, and TKB (that
is, before invoking Phase III on the target system).

* 6.

Use an input saved answer file?

[Y/N]:

Respond Yes to this question if you have previously created a saved
answer file.
This option lets you direct SYSGEN to use that file as
input responses to the questions.
Any SYSGEN question automatically
answered by a saved answer file does not appear on your terminal.
4-5

DETAILS OF SYSGEN PHASE I

SETUP (Cont.)
SYSGEN does not save responses to the Peripheral Options Section
questions for the ICR/ICS, DSS/DSR, or IP11/IP300 devices; you must
enter the responses for those devices.

* 7.

Name of input saved answer file [D:

<default> ] :

SYSGEN displays this question only if you respond Yes to Question 6.
If the file SYSSAVED.CMD exists in the current UFO, the default file
name for the input saved answer file is SYSSAVED.CMD.
Press the
RETURN key to input the default filename of SYSSAVED.CMD.
If you have created a saved answer file having a different file name,
you may enter the name of that file. The input saved answer file name
must conform to the RSX-llM file-name standard.
If the specified file does not exist, SYSGEN repeats Question 7.
If you enter a response other than the default and omit a
SYSGEN assumes the file type .CMD.

file

type,

If you are using an incomplete saved answer file for input, SYSGEN
issues a message indicating that the file may be incomplete. In that
case, when SYSGEN encounters a question for which your saved answer
file does not have a response, SYSGEN displays that question on your
terminal and waits for you to input a response.

* 8.

Do you want a Standard Function System?

[Y/N]:

This option allows you to direct SYSGEN to generate a mapped RSX-llM
system having most of the available software options automatically
included. Your target system should have at least 64K words of
memeory if you intend to select this option.
If you respond Yes to this question, SYSGEN displays
questions not defined in the Standard Function System.

only

those

If you respond No to this question, SYSGEN requires
each question individually.

you

answer

that

See Section 3.6.2 for more information on the Standard Function
System.
This question appears only if you are generating a mapped
RSX-llM system and did not choose to use an input saved answer file=

* 9.

Name of output saved answer file [D:

<default>]:

This option lets you assign a file name to the output saved
file (that is, the one created during the current SYSGEN).
The default name of the output saved answer file is the same
of the name of the input saved answer file.

4-6

answer
as

that

DETAILS OF SYSGEN PHASE I

SETUP (Cont.)
If you want to place your saved answer file in a UIC other than the
default UIC
([200,200]), you must create that UIC using the MCR UFO
command before beginning your SYSGEN if that UIC does not already
exist on the RSXM35 disk.
For more information on the MCR UFO
command, see the RSX-llM/M-PLUS MCR Operations Manual.
If that UIC does exist, type in the UIC and the file name in
to the question.

response

Otherwise, if you answered No to Question 7 or if you selected the
option for a Standard Function System, the default name of the output
saved answer file is SYSSAVED.CMO.
If you enter a response other than the default and
file type, SYSGEN assumes the file type .CMO.

you

omit

the

Press the RETURN key to select the default response.

* 10.

Use saved host configuration?

[Y/N]:

This option allows you to use previously defined
(saved)
answers to
Host Configuration Section questions. When you are running SYSGEN on
line and have all the listings you need, you may want to change the
Host Configuration Section answers in your saved answer file to
redefine the way SYSGEN handles listings.
If you respond YES, your answer implies that you are performing a
SYSGEN on the same, or similar, configuration you used to create the
saved answer file.
This question appears only if you responded Yes
saved answers) •

* 11.

Use saved peripheral configuration?

Question

(Use

[Y/N]:

This option allows you to modify the previously defined
(saved)
peripheral configuration contained in the saved answer file.
If you
respond Yes to this question, SYSGEN uses the saved peripheral
configuration.
If you respond No, SYSGEN asks Question 15 of the Target Configuration
Section.
Not~

that if you answer No, it
file and does not permit you
defined devices.
Answering No
of controllers; respond No to

does not affect the input saved answer
to change vectors or CSRs of previously
permits you to change only the number
add or delete controllers.

This question appears only if you responded Yes
saved answers) •

4-7

Question

(Use

DETAILS OF SYSGEN PHASE I

SETUP (Cont.)
* 12.

Skip End-of-Section (EOS) breakpoints?

[Y/N]:

This option allows you to choose whether or not to stop
at
End-of-Section
(EOS)
breakpoints.
At these breakpoints, you can
select whether to continue SYSGEN questions, repeat questions in the
preceding sections
(to correct answers), exit from SYSGEN, or cause
SYSGEN to pause.
Breakpoints occur at the following points in SYSGEN Phase I:
•

After the Target and Host Configuration Sections

•

After the Executive Options Section

•

After the Terminal Drivers Options Section

•

After the Peripherals Options Section

•

After the System Options Section

If the answers in the saved answer file correctly define the system
you want to generate, you can direct SYSGEN to complete execution
without interruption by answering Yes to this question.
This question appears only if you responded Yes
saved answers).

* 13.

[Y/N]:

Skip End-of-Execution (EOX) breakpoints?

Question

(Use

End-of-Execution (EOX) breakpoints occur after the MACR0-11 assembler
completes execution.
If you know that the MACR0-11 processing will
complete successfully, respond Yes to direct SYSGEN to proceed without
pausing.
If you respond No, SYSGEN pauses after execution of these tasks
allow you to check the results and make any necessary corrections.
This question appears only if you responded No to Question 3
MCR command lines) and Yes to Question 6 (Use saved answers).

* 14.

Clean up files from previous GENs?

(inhibit

[Y/N]:

When 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 allows you to direct SYSGEN to delete all such
unnecessary files.
This question appears oniy if you respond No to
MCR ccnunands) •

4-8

Question

(Inhibit

DETAILS OF SYSGEN PHASE I

SETUP (Cont.)
* 15.

Chain to Phase II after Phase I completes?

[Y/N]:

If you respond Yes to this question, SYSGEN automatically invokes
Phase II at the completion of Phase I.
This question does not appear
if you are generating an RSX-118 system or if SYSGEN2.CMD is not
in
UIC [200,200] on the SY: disk.
Chaining is most useful when you are using a complete saved answer
In this case, you can
file for
input to both Phase I and Phase I I.
complete most of a SYSGEN unattended.

* 16.

Enter device for EXCPRV disk when it is ready (ddu:) [D:

Enter the device type and unit number
the Executive source files.

(ddu:) for the

unit

DLl:]

containing

SYSGEN appends the trailing colon if you omit it in your response.
This question only appears if you are using the
kit.

4-9

RLOl/02

distribution

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION
4.3

TARGET CONFIGURATION SECTION

This section of questions defines the target processor type and
options, and peripheral devices included in the target system.
If you
are running SYSGEN on a V4.l system and if you
choose
the
Autoconfigure option
(Question 1 in the Setup Section), questions in
this section requiring a logical (Yes or No) response may display an
explicit default response.
The explicit default response (indicated
by the key D:) may be Yes or No.

* 1.

Processor Type [D:

11/34]:

Enter the target PDP-11 processor type.
Valid entries are:
LSI-11*
11/03*
11/04*
11/05*
11/10*
11/15*

11/20*
11/23
11/24
11/34
11/35
11/40

11/44
11/45
11/50
11/55
11/60
11/70

Those processors that are marked with an asterisk (*) do not support
memory management hardware.
Therefore, they support unmapped systems
only.
If you specified earlier that you are generating a mapped system, your
response to this question must be one of those processors listed that
is not marked with an asterisk.
Otherwise, SYSGEN ignores your
response and repeats the question.
NOTE
If
your
processor
is
either
a
PDP-11/23-PLUS or a MICRO/PDP-11, enter
11/23 as your processor.
Then
in
Question 3, enter 128(10) or more as the
memory size. Doing so tells SYSGEN that
your processor is an PDP-11/23-PLUS.
SYSGEN always asks this question.

* 2.

Does processor have a switch register?

[Y/N D:N]:

The switch register is a reserved memory address to which you can
write data.
Under program control, you can read the contents of the
switch register via the GSSW$ (Get Sense Switch) Executive directive.
Not all processors have a switch register.
If the processor for your
target system does not have a switch register, you cannot use the
GSSW$ directive.

4-10

_DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)
Processors that do have switch registers vary in the way that you
access them:

can

•

There may be toggles on the front panel which you use
in data to the switch register.

•

Some newer processors
instead of toggles.

panel,

•

On other processors, the console terminal replaces the toggles
or keypad as the means of accessing the switch register.

have

keypad

the

front

key

This question appears only if the PDP-11 processor you specified
(in
Target Question 1)
is an 11/03, 11/04, ii/23, or il/34. Other
processors always include a switch register.

* 3.

Memory size (in K-word blocks)

[D R:l6.-124.

D:64.]

Enter the amount of memory for your target system processor in
1024-word blocks (lK). Memory sizes apply to addressable memory only
(not including the I/O page) • The legal range is from 16K through
1920K; but that range depends on the minimum and maximum memory sizes
for your particular processor. SYSGEN calculates the range values
(min and max) based on your response to Question 1 in this section.
NOTE
Various system components
(especially
the Executive)
use the memory size to
determine whether your processor has
16-, 18-, or 22-bit addressing mode.
If you selected the Standard Function System (Setup Question 8), you
must specify a m1n1mum of 64K words of memory; otherwise, SYSGEN
issues an error message and exits.
Table 4-1 shows the minimum
and
RSX-llM-supported PDP-11 processors.

maximum

memory

Memory size must be specified in 4K increments
unmapped system) •

(except

4-11

sizes
for

the

for
30K

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)
Table 4-1
PDP-11 Processor Memory Sizes for RSX-llM/RSX-llS
Memory Size (in K-word blocks)

RSX-llM

RSX-llS

PDP-11
Processor

Maximum

Minimum

Maximum

Not supported
28
28
28
1920
28
1920
1920
124

8
16
16
16
8
16
64
32
8

30
28
28
28
1920
28
1920
1920
124

Minimum

Not supported
LSI-11, 11/03
16
11/04, 11/05
16
11/10, 11/15
16
11/20
16
11/23, 11/24
11/40 (no KT-11)
16
64
11/44
32
11/70
All othersl
16

1. In the category "all others," the processors are the
11/35, 11/40, 11/45, 11/50, 11/55, and 11/60.

PDP-11/34,

NOTE
Specifying 128K (or more)
of memory
indicates that you have a system with
22-bit addressing.
If
your
target
PDP-11
processor is a MICRO/PDP-11,
11/23, 11/23-PLUS, 11/24, 11/44,
or
11/70 and if you want to generate a
system that is transportable to
an
18-bit processor, you should specify
124K or less.

* 4.

Include support for K-series devices?

The

K-series

laboratory

options

are

[Y/N D:N]:

set

real-time

data

acquisition modules that interface to the PDP-11 family of computers.
Respond 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 support for Connect to Interrupt
and AST (Asynchronous System Traps).

4-12

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)
* 5.

Extended arithmetic element (KEll-A/B EAE) present?

[Y/N D:N]:

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.
This question appears only for
hardware) PDP-11/40 systems.

* 6.

PDP-11/20

and

Floating point processor (FPll) present?

unmapped

(no

KT-11

[Y/N D:N]:

The PDP-11 floating point processors perform floating point arithmetic
operations and convert data from integer to floating point format and
vice versa.
PDP-11 Processor

Floating Point Processor

11/23, 11/24
11/34
11/44
11/45, 11/50,
11/55, 11/70
11/60

KEFll-AA, FPF-11
FPFll-A
FPFll-F
FPFll-C
FPFll-E

The PDP-11/23 and PDP-11/24 have both a microcode floating point
option
(KEFll-AA)
and a hardware option (FPF-11); both options are
fully compatible with the 11/34 floating point instruction set.
If
the target processor is a PDP-11/60, floating point support is
automatically included and the question does not appear.
This question does not appear for other processors.
This feature should not be confused with the Floating Instruction
(FIS) described in Question 7 of this section.

Set

If you respond Yes to this question, SYSGEN automatically includes
Executive support for Asynchronous System Traps (ASTs). See Question
17 in the Executive Options Section.
If you respond No to this question, SYSGEN asks Question 7.

* 7.

Floating instruction set (FIS} present?

[Y/N D:N]:

The Floating Instruction Set (FIS) feature includes hardware functions
that perform floating point add, subtract, multiply, and divide
instructions.
This question appears only if your target system does not have the
floating point processor (Question 6) and if the target processor is
one of the following: LSI-11, PDP-11/03, 11/23, 11/24, 11/35, or
11/40.

4-13

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)
* 8.

Extended instruction set (EIS) present?

[Y/N D:N]:

This question only appears if EIS is standard or optional for your
particular target processor.
Those processors supporting the EIS
feature are:
PDP-11
Processor

EIS Feature

LSI-11
11/03
11/23
11/24
11/34
11/35
11/40

Optional
Optional
Standard
Standard
Standard
Optional
Optional

PDP-11
Processor

EIS Feature

11/44
11/45
11/50
11/55
11/60
11/70

Standard
Standard
Standard
Standard
Standard
Standard

If you choose this option, some of the following EIS instructions are
used by the Executive and the I/O drivers, thereby speeding up the
execution time of the operating system and reducing Executive and I/O
driver address space. The extended instruction set, which can be used
by the Executive and I/O drivers, consists of
the
following
instructions:
MUL
DIV
ASH
ASHC
XOR
SOB
RTT
MFPI
MTPI

Multiply
Divide
Shift arithmetically
Arithmetic shift combined
Exclusive OR
Subtract 1 and branch if not equal to 0
Return from interrupt
Move from previous instruction space
Move to previous instruction space

Note that if you are generating a system that you wish to run on
different processors, you should be aware that a software system that
supports EIS instructions does not run on processors that do not have
EIS hardware. Although your target processor may have EIS hardware as
a standard feature, this question allows you to exclude EIS support so
that your system is transportable to non-EIS hardware.

* 9.

If using KWll-P as system clock:

number of ints/sec.[D R:0-1000 D:O]

RSX-llM and RSX-llS require a real-time clock for
clocks are available:
•

The KWll-P programmable frequency clock

•

The KWll-L line frequency clock

•

The DLll-W line frequency clock/console

operations.

If your system has a KWll-P and you want to use this clock as
system clock, the acceptable range is from 0 through 1000(10).

4-14

Three

your

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)
A response of 0 indicates that there is no programmable clock in this
configuration or that you want to use the line frequency clock as the
system clock.
This question does not appear for the LSI-11, PDP-11/03, or
processors.

PDP-11/23

NOTE
The number of interrupts you select must
be evenly divisible into 10000(10)
More than 100(10) clock interrupts-per-second greatly increases system
overhead;
carefully consider the impact on your system before
specifying a number greater than 100(10)
interrupts-per-second.
If
you do specify more than 100(10) interrupts-per-second and the clock
is your system clock, you may have to adjust the algorithms for the
other clock functions
(for example, round-robin scheduling and disk
swapping).
Adjusting the algorithms compensates for the system
overhead caused by the high number of interrupts-per-second.
If you
need the clock for time-critical tasks, it is recommended that the
clock not be your system clock also.

* 10.

Line frequency:

A- 60Hz B- 50Hz [D:

[S]:

Specify a line frequency of either 50 or 60 Hz.
In the U.S.A. ,
frequency is always 60 Hz.
The default response is 60 Hz.

line

If a KWll-P programmable frequency clock is available and if you have
selected the Autoconf igure option (Setup Question 1), Autoconfigure
computes the line frequency.

* 11.

KWll-Y Watchdog timer support?

[Y/N D:N]:

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 message indicates that the system has
been corrupted.
This question always appears.

* 12.

Memory parity support?

[Y/N D:N]:

Respond Yes if your system includes parity
Executive support to detect parity errors.

memory

and

you

want

If you intend to log cache and memory parity errors, you must answer
Yes to this question.
(See Question 24 of the Executive Options
Section.)

4-15

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)
Memory parity support uses approximately 200 words of memory.
If you respond Yes to this question, SYSGEN asks Question 13.

* 13.

Cache memory?

[Y/N D:N]:

Cache memory is standard on PDP-11/44, 11/60,
Cache memory is optional on the PDP-11/34.

and

11/70

processors.

Respond Yes if you want Executive support to detect parity errors.
This question appears only for the previously specified
when you select memory parity support
(Question 12)
processors.

* 14.

processors
for those

Highest interrupt vector [O R:0-774 0:0]:

The response to this question specifies the highest interrupt vector
address.
If you respond 0 (or press RETURN) or with an even value
less than 400(8), SYSGEN calculates this address based on your answers
to the peripheral questions that occur later in Phase I. The end of
the vector area is minimally set to 400(8) bytes.
If it is necessary
for you to specify the end of the vector area yourself, remember that
some devices (noteably DLs and DZs) have two vectors:
one for
input
and one for output.
Check the PDP-11 Peripherals Handbook or the
Terminals and Communications Handbook if you are uncertain.
If you intend to include any devices in your target system that have
an interrupt vector greater than 400(8) (such as K-series and certain
communications devices), specify an even value for the highest
interrupt vector that you need to accommodate those devices at this
time.
NOTE
SYSGEN does not write this value to the
saved answer file until you complete the
Peripheral Options Section.
This question always appears.

* 15.

Devices

This question asks you to enter, in mnemonic form, the peripherals and
pseudo devices for your target configuration.
SYSGEN generates
questions only for those devices you specify in response to this
question.

4-16

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)
NOTE
If you chose the Autoconfigure option,
you can add new devices, you can add
devices not found by Autoconfigure, and
you can exclude any devices already
found by Autoconf igure.
Enter devices in the form:
device=number of controllers
where device is the device mnemonic and controllers is the number of
controllers for the device type. If you omit the controller entry
{=controllers), SYSGEN assumes one controller for that device type.
Generally, there may be one controller for several devices of a given
type.
For example, four RA80 drives can be connected to one UDASO
controller. In this case, all you are required to enter in response
to this question is DU; SYSGEN defaults to one controller for all
four RASO drives.
To help select the appropriate device mnemonic, enter an asterisk
to generate a list of devices.

(*)

You can display your current configuration (the device
number of controllers) by entering a question mark(?).

mnemonics

and

If you chose the Autoconfigure option, SYSGEN prints the list
devices that Autoconfigure found before this question is asked.
you are satisfied with Autoconfigure's results, enter a period(.)
response to this question.

of
If
in

If you are not satisfied with Autoconfigure's results, you can add new
devices,
modify existing devices, and delete any devices that
Autoconfigure found. Those devices you specify are the only devices
affected
in
the
Target
Configuration
saved
answer
file.
Autoconfigure's results remain the same for the rest of the hardware
configuration.
When you have entered all of the devices and controllers for your
target system, and have made any necessary corrections, terminate your
response by entering a period (.) either following the last controller
or on a line by itself.
If you make a mistake and specify a device type that is not included
in the target configuration, enter device=O
(see the following
example). Also, if you specify the wrong number of controllers, you
can correct this by reentering the device type and the new number of
controllers. SYSGEN uses the most recent response for duplicate
entries.
For example, if your system includes two RKll controllers
and one TCll DECtape controller, the following sequence corrects an
errant response of three RKlls, two TU56s and one RLll:
Devices:
Devices:
Devices:
Devices:
Devices:
Devices:
Devices:

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

(defaults to 1)
{supersedes previous value of 3)
(supersedes previous value of 2)
(removes previously specified RLll)
(terminates input)
4-17

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)
Table 4-2 lists the peripheral devices supported by RSX-llM:
Table 4-2
Peripheral Devices Supported by RSX-llM
Mnemonic

Device

AD
AF
AR
CR
CT
DB
DD
DF
DK
DL

Analog-to-Digital Converter
Analog-to-Digital Converter
Laboratory Peripheral Subsystem
Card Reader
TU60 Cassette
RP04/05/06 disk packs
TU58 DECtape II
RFll disks
RK05/J/F cartridge disk
RLOl disk drive
RL02 disk drive
RK06/07 cartridge disk
RP02/03 disks
RM02/03/05 disks and
RM80/RP07 fixed media
RS03/04 fixed-head disks
TU56 DECtape
RA60 removable media
RA80/81 fixed media
RC25 fixed/removable media
RD51 fixed disk
RXSO floppy disk
RXOl floppy disk
RX02 floppy disk
MLll Nonrotating Electronic
Memory
Graphics Display Processor
and Scope
Industrial Control System
Industrial Control System
Industrial Control Subsystem
Laboratory Peripheral Accelerator
Line Printer

DM
DP
DR
DS
DT
DU

DX
DY
EM
GR
IC
IP
IS
LA
LP
LS
MF
MM
MS
MT
pp

PR
UD

XB
XL
XM
XP

Hardware Controller

Laboratory Peripheral Subsystem
TU78 magtape
TU45/TU16/TE16/TU77 magtapes
TS11/TSV05/TU80 magtapes
TS03/TU10/TE10 magtapes
Paper Tape Punch
Paper Tape Reader
Universal Digital Controller
Interprocessor Link
Interprocessor Link
Interprocessor Link
Synchronous Interface

ADOl-D
AFCll
ARll
CRll/CMll
TAll
RH11/RH70
DLll
RFll
RKll
RLll/RLVll
RL21/RLV21/RLV12
RK611/RK711
RPll/RPllC
RH11/RH70
RH70
RH11/RH70
TCll
UDASO
UDASO
RC25
RQDXl
RQDXl
RXll
RX211/RXV21
RH70
VT11/VS60
ICR/ICSll
IP11/IP300
DRS/DSll
LPAll-K
LAll/LPll/LSll/LVll
LN01/LA180
LPSll
RH70/TM78
RH11/RH70/TM02/TM03
TSll
TMll/TMAll/TMBll
PCll
PCll/PRll
UDCll
DAll-B
DLll-E
DMCll
DPll

(continued on next page)

4-18

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)
Table 4-2 (Cont.)
Peripheral Devices Supported by RSX-llM

XQ
XU

YH
YL
YJ
YZ

Hardware Controller

Device

Mnemonic

Synchronous Interface
Synchronous Interface
Synchronous Interface
Asynchronous Terminal
Asynchronous Terminal
Asynchronous Terminal
Asynchronous Terminal

Interface
Interface
Interface
Interface

DQll
DUll
DUPll
DHll/DHVll
DLll/A/B/C/D/E/J/W
DJll
DZll/DZVll

Pseudo devices:
Console terminal
Null device

CO:
NL:
NOTE

If you intend to perform future system generations using
your target system, you must include the NL pseudo
device.
If you are generating RSX-llM,
SYSGEN forces YL into the system.
Normally, you must specify any pseudo devices if you wish to include
them.
In addition, SYSGEN forces the null device (NL:) into a system
only if
(1)
that system does not include an asynchronous terminal
interface and (2)
if that system includes at least one of the
following disks:
DB:, DF:, DK:, DL:, DM:, DP:, DR:, DS:, DX:, DY:,
DU:, or EM:. Otherwise you must explicitly select NL:
(necessary if
the new system will be the host system for a later SYSGEN).
If you specify CO, you get the Console Logger task and the CO driver.
If you do not specify CO, SYSGEN automatically includes the pseudo
device CO without the Console logger task and the CO driver. See the
RSX-llM/M-PLUS System Management Guide for details on the differences
between the CO driver and the CO pseudodevice.
CO is not available on unmapped systems or on RSX-llS systems.
GR is not valid on systems with more than 124K of memory.
NOTE
To specify the number of paper tape
device controllers, you must consider
the PCll reader/punch as two separate
devices, a reader (PR} and a punch (PP}.
Enter both a PR and a PP for each PCll,
but only a PR for each PRll.

4-19

DETAILS OF SYSGEN PHASE I

HOST CONFIGURATION
4.4

HOST CONFIGURATION SECTION

Your responses to these questions define the
you are running SYSGEN.

which

maps

and

If you respond Yes, you may direct SYSGEN to spool listings
to the line printer.

and

maps

* 1.

Is a line printer available?

This option allows you to
listings will be directed.

configuration

[Y/N]:

specify

the

device

If you respond NO, SYSGEN directs listings and maps to your terminal.

* 2.

Spool assembly listings and Executive and driver maps?

[Y/N]:

This option allows you to specify whether or not to spool listings.
For example, you can direct listings to an intermediate device.
Spooling the listings to an intermediate device allows you to save the
listings without the risk of filling up the distribution disk.
If you want the listings spooled to the line printer, respond
this question.
If you respond Yes, Question 1 (List Executive map?)
Task Build Section is not asked.
If you want to save the listings but not spool
this question (see Question 5).

Executive
No

This question appears only if you responded Yes to Question 1, and
you are generating your system from an on-line host computer.

* 3.

them,

of the

Yes

respond

Does the listing/map device have at least 120 columns?

[Y/N]:

If the listing device does not have at least 120 columns, SYSGEN
creates
a narrow listing for assembly and map listings.
For
information on narrow listings, refer to the descriptions of the /LI
switch for MACR0-11 and the /WI switch in the RSX-llM/M-PLUS Task
Builder Manual.

* 4.

Assembly listing file device (ddu:)

[D:

NL:]:

This option 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 direct the listings to the line printer
if you are
running stand-alone, to a disk device
(ddu:)
if you are running
on-line, and NL:
(the null device, and the default) ta direct SYSGEN
not to produce assembly listings.

4-20

DETAILS OF SYSGEN PHASE I

HOST CONFIGURATION (Cont.)
NOTE
The only driver that SYSGEN loads is the
LP: driver.
If you are generating your system with
either
an
RK06/07
or
RLOl/02
distribution kit, do not direct your
assembly
listings
to
any
of the
distribution kit disks;
there is not
sufficient space on those kits.

* 5.

Map device for Executive and device drivers (ddu:)

[D:

<default>]:

The response to this question defines the default device to which you
want to direct the Executive and device driver maps. You should
specify a device other than the system disk for these maps.
For unmapped systems, you should specify a device, since the maps are
necessary to determine the size of the Executive and device drivers
and to lay out memory partitions in SYSGEN Phase II.
If you are using an RLOl/02 distribution kit, the default response to
this question is the same as your response to Question 17 in the Setup
section.
If you are using either an RK06/07 or a "big disk"
the default response is SY:.

distribution

kit,

Unless you are performing a PREPGEN, you must mount
(using the MCR
MOUNT command) the disk to which you are directing map listings before
you invoke Phase II. That disk must contain the UFO
[1,34]
for a
mapped system, or [1,30] for an unmapped system.
If you direct SYSGEN
to chain directly to Phase II, you must mount the map listing disk
before you invoke Phase I.

4-21

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS
4.5

EXECUTIVE OPTIONS SECTION

Your responses to these questions define the RSX-llM Executive options
you want included in your target system.
The RSX-llM/M-PLUS Executive Reference Manual describes some of
directives and Executive options.

these

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

* 1.

Include support for DBMS-11?

[Y/N]:

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 generating RSX-llM.
If you select DBMS-11 support, SYSGEN automatically includes Executive
support for:
e

Files-11 ACP

•

RMS bucket locking and placement control

•

Memory management (PLAS) directives

•

Send/Receive By Reference directives

•

Asynchronous System Traps (AST)

•

System Controlled partition support

•

The following System directives:
Get Partition Parameters (A)
Get Task Parameters (B)
Send/Receieve (C)
Extend Task (E}
Stop Bit (I)
Parent/Offspring Tasking (K)

See Questions 2, 3, 7, 8, 17, 33, and 37 respectively.

* 2.

FILES-11 ACP?

[Y/N] :

You must select Files-11 ACP (FCP) if you wish to include the services
described in the IAS/RSX-11 I/O Operations Reference Manual or if you
intend to include RMS-11 or~-any file functions of a high-level
language.
DIGITAL-supplied software uses the FCP; you should select
this option.

4-22

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
If you selected DBMS-11 support, SYSGEN
option.

automatically

includes

this

If you are generating an RSX-llS system, this question does not appear
and an FCP is not included in your system.
If you choose this option, Question 4 of the
asks you to specify a version of the FCP.

* 3.

System

Options

Section

RMS bucket locking (file sharing) and placement control?

[Y/N]:

Record Management Services (RMS=ll) is an extended file access feature
supplied with RSX-llM.
RMS-11 bucket locking, which is necessary for
file sharing, and placement control are features of RMS-11 that are
described in the RMS-11 User's Guide.
If Files-11 ACP (FCP) is included in your system either by default or
by selecting Question 2, SYSGEN asks this question to provide the
necessary Executive and FCP support.
If you do not choose this support, RMS-11 file
placement control is not included in your system.
This option adds approximately
Executive.

200(10)

words

the

sharing
size

and/or
of

the

This option is not available for RSX-llS systems.

* 4.

Non-resident tasks (task loader)

[Y/N]:

It is highly recommended that you select this option.
Nonresident
task support allows tasks that are not permanently resident in your
system to be loaded from disk.
If you do not include support for the task loader, all tasks
installed and fixed into the system image by VMR.

must

If you answer No, Question 5 (loadable task loader) does not appear.
This question does not appear if you are generating an RSX-llS system.

* 5.

Loadable task loader?

[Y/N]:

The RSX-llM task loader reads tasks scheduled for execution from disk.
The loadable task loader is an RSX-llM Executive feature that reduces
the amount of address space required for the Executive
{excluding
pool).
This feature frees space for additional Executive dynamic
storage.

4-23

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
If you answer No to this question, SYSGEN task builds the loader into
the Executive which requires up to 2400 bytes of Executive virtual
address space. The system used the corresponding amount of main
memory to hold the loader as a fixed privileged task. By choosing the
loadable task loader option, those 2400 bytes become available for use
as dynamic storage (pool space) or for other Executive features.
This option does not appear for RSX-llS systems, unmapped systems,
systems that do not support nonresident tasks.

* 6.

Executive Common?

[Y/N]:

If you choose this option, much of the Executive's directive support
code will be set in external memory-resident commons rather than being
resident in the Executive itself. These memory-resident commons free
more of the Executive's address space, which can then be used for
additional pool space.
The Executive commons are two 4K-word partitions.
However, the
potential space available for the Executive commons is not totally
utilized. VMR calculates the actual size of the Executive commons
(based on which Executive options you select in this section) and
allocates the necessary amount of memory for the Executive commons
during Phase II.
Generally, VMR allocates about 5.5K words as the
combined size of both Executive commons.
The cost of choosing the Executive commons is that the Executive
commons occupy the equivalent amount of memory that they would
otherwise occupy in the Executive. The file SYSVMR.CMD includes a SET
/POOL command that always creates the maximum possible pool space for
a mapped target system.
SYSVMR.CMD may create more pool space than your system requires,
particularly if you choose the Executive Common support. This extra
pool space directly impacts the amount of memory available for your
applications. However, you can remedy this during Phase I I by editing
SYSVMR.CMD and modifying the SET /POOL command. Should the modified
pool size subsequently prove to be inadequate for your system's needs,
you can remodify the SET /POOL command to allocate more pool up to the
limits of the Executive's permanently mapped virtual address space
(normally 20K).
Remember, any time you modify the contents of
SYSVMR.CMD,
you must recreate the system image, then reinvoke
SYSVMR.CMD.
(See Example 5-1 at the end of Chapter 5 for details on
creating the system image file.)
This question appears only for mapped systems with at least 36K
of memory.

* 7.

Memory management (PLAS) directives?

words

[Y/N]:

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.

4-24

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
The following lists the memory management directives:
Attach Region
Create Address Window
Create Region
Detach Region
Eliminate Address Window

Get Mapping Context
Map Address Window
Receive By Reference
Send By Reference
Unmap Address Window

Memory management directives are restricted to use on mapped systems.
Therefore, the question does not appear for unmapped systems.
If you selected DBMS-11 (Question 1) SYSGEN includes memory management
directives by default and does not ask this question.
If you do not select memory management (PLAS) directives, you cannot
include Executive support for Send/Receive By Reference directives
(Question 8) or the Get Mapping Context directive (Question 9).
The memory management (PLAS)
words to the Executive.

* 8.

directives

add

Send/Receive By Reference directives?

approximately

1000(10)

[Y/N]:

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 that allows it to map to or delete
the region.
If you selected DBMS-11 and memory management PLAS directive support,
SYSGEN automatically includes Executive support for the Send/Receive
By Reference directives;
this question does not appear.
If you did not include support for
the
directives, this question does not appear.

* 9.

Get Mapping Context directive?

Memory

Management

(PLAS)

[Y/N]:

The Get Mapping Context directive returns parameters to the issuing
task that describe the current window-to-region mapping assignments.
These parameters allow you to restore the mapping context by using the
memory management Create Address Window directive.
This question appears only if you selected
Management (PLAS) directives (Question 7).

* 10.

Address checking?

support

for

Memory

[Y/N]:

Address checking directs the Executive to perform boundary checks and
alignment checks on addresses issued by users in Executive directives.
If you are generating a mapped system, SYSGEN automatically
address checking and does not ask this question.

4-25

includes

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
Address checking is recommended
debugged application system.

* 11.

I/O rundown?

unless

you

are

running

fully

[Y/N]:

I/O rundown ensures RSX-llM system integrity by completing
outstanding task-related I/O before allowing a task to exit.

all

If you are generating a mapped system, SYSGEN automatically includes
support for I/O rundown and does not ask the question.
I/O rundown is
recommended unless you are running a
fully debugged application
system.

* 12.

Multiuser protection?

[Y/N]:

This feature prevents tasks initiated at one terminal from interfering
with
tasks initiated at other terminals.
Multiuser protection
provides for public and private devices and login and logout with
password protection.
When you select this feature SYSGEN includes support for checkpointing
with the system checkpoint file.
In addition, SYSGEN automatically
includes the following terminal driver features:
•

Read with special terminator

•

Breakthrough write

•

Read with no echo

CTRL/R support

Multiuser protection increases
approximately 100(10) words.

the

size

the

Executive

Select multiuser protection support only if your system has 32K or
more of main memory.
If your target system is unmapped, it is
recommended that you not select this option.
Multiuser protection support is not available on
the question does not appear.

* 13.

ANSI Magtape ACP?

RSX-llS

system;

[Y/N]:

This feature provides support for volume and file labels that conform
to the ANSI standard (X3.27-1978) for industry-compatible tapes.
This
feature requires Executive AST support;
if you select ANSI magtape
ACP support, SYSGEN automatically includes AST support.
ANSI magtape ACP support increases the size of the Executive by
approximately 40(10)
words.
If you select this option, SYSGEN
task-builds FllMSG (the magtape error processor), MTAACP (the magtape
Ancillary Control Processor), and MAG (the magtape ACP control task)=

4-26

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
In addition, if you select ANSI magtape support, SYSGEN generates a
second library called ANSLIB.OLB.
This library (ANSLIB.OLB) contains
an FCS that communicates with the ANSI magtape ACP.
This FCS also
supports the FCS big buffer feature.
See the I/O Operations Manual
for more information.
~If you respond
included.

Yes,

support

for

the

Send/Receive

directive

If you do not select ANSI rnagtape support, the system library,
SYSLIB.OLB, contains an FCS that does not communicate with the ANSI
magtape ACP.
RSX-llS systems do not support ANSI magtapes;
appear.

* 14.

the question

does

Do you want on-line formatting (FMT) or diagnostic QIOs?

not

[Y/N]:

Diagnostic QIOs enable the Executive and device drivers to perform
special I/O functions and return additional device status information
required by on-line diagnostic tasks.
FMT is one utility that uses
those special I/O functions.
If you intend to either do on-line disk formatting or write your own
hardware diagnostic routines, you should answer Yes to this question.
See the RSX-llM/M-PLUS Utilities Manual for information on the on-line
formatter
(FMT)
and the RSX-llM/M-PLUS I/O Drivers Reference Manual
for a description of QIOs.
~This feature is not available for RSX-llS systems.
not appear.

* 15.

Loadable device drivers?

This option
dynamically
except the
ICS/ICR, and

The question

does

[Y/N]:

allows you to load and unload most device drivers
using MCR and VMR LOAD and UNLOAD commands. All drivers
industrial and process control device drivers
(UDC,
DRS/DSS) and the VT11/VS60 graphics driver are loadable.

Note that 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.
When you select this option, SYSGEN generates loadable device drivers;
however, SYSGEN makes all data bases resident.
If you respond No, SYSGEN links all device drivers generated for your
system into the Executive, making them all resident.
This impacts the
potential amount of pool space available to your system.
SYSGEN always asks this question.

4-27

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS {Cont.)
* 16.

Should the default for all applicable drivers be loadable?

[Y/N]:

If you included loadable device driver support, responding Yes to this
question specifies that all drivers (except UDC, ICS/ICR, DRS/DSS, and
VT11/VS60) are to be built as loadable by default
(you can override
the default in the Peripheral Options Section).
The response to this question sets the default, either L (loadable) or
R (resident) for the first parameter in some responses to peripherals
questions.
You can override this default in your responses to the
questions in the Peripheral Options Section.
If you respond No to this question, SYSGEN builds all drivers
the full-duplex terminal driver, if selected) as resident.

(except

If you do not choose loadable device driver support in Question 15,
all drivers will be resident, and you cannot override that condition
in the Peripheral Options Section.

* 17.

Include Support for Asynchronous System Traps (AST)?

[Y/N]:

This option allows the processing of Asynchronous System Traps.
Support for ASTs is automatically included if you previously
any of the following:

selected

• The ANSI magtape ACP support
• The Floating point processor (FPll)
• DBMS-11

• The LA driver (LPAll-K)
• The K-series device support routines
Respond Yes if you want AST support.
If you respond No, the
input character ASTs.
Section.)

* 18~

terminal driver cannot support unsolicited
(See Question 6 in the Terminal Driver Options

Include support for Cancel Selective Marktime?

[Y/N]:

If you select this option, you can selectively cancel specific
marktime requests.
See the CMKT$ directive in the RSX-llM Executive
Reference Manual for information on the Cancel Marktime directive.
If you do not select support for Cancel Selective Marktime, any
attempt by a task to cancel a marktime results in the cancellation of
all outstanding marktimes for that task.
If you selected support for DBMS-11,
SYSGEN
support for Cancel Selective Marktime.

4-28

automatically

includes

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
* 19.

Task termination and device not ready messages (TKTN)?

[Y/N]:

This option directs the system to generate on the input device and on
the console DEVICE NOT READY and task termination messages when these
conditions occur.
You must select this option if you want Post Mortem Dump (PMD)
Snapshot Dump (SNAP$) support or Logging of Task Abort support.

* 20.

Power fail recovery?

and

[Y/N]:

This option provides for automatic system recovery in the event of
power failure.
Device drivers and tasks that specify a power recovery
AST are notified when power returns.
There are three possible recovery procedures:
•

If a device was busy prior to the powerfail and the requested
I/O had not completed, the routine times out and checks the
device status until the device is "ready" for
I/O operations
to resume.

•

If a device was not busy prior to the powerfail and receives
an I/O request after the powerfail, the routine times out and
checks the device status until the device is "ready" for I/O
operations to resume.

•

If a device was not busy prior to the powerfail and there are
no pending I/O requests, operations resume with no special
handling by the recovery routine.

Note in the first two cases, if the maximum timeout count is reached
before the disk spins back up and is "ready," an unsuccessful I/O
completion code is returned.
This option is required to support
directive.

* 21.

the

Specify

Install, request, and remove on exit?

Power

Recovery

AST

[Y/N]:

This option (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. See the RSX-llM/M-PLUS MCR Operations
Manual for information on the RUN command.
This feature is not available for RSX-llS systems.
not appear.

4-29

The question

does

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
* 22.

Large (20K) Execative?

[Y/N]:

This option allows you to generate a 20K Executive 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
that map the I/O page.
If you are generating an
appear.

* 23.

unmapped

Logical device assignment?

system,

this

question

does

not

[Y/N]:

This option is highly recommended.
If you intend to use your target
system for subsequent SYSGENs, you must answer Yes to this question.
This option (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).
See the
RSX-llM/M-PLUS MCR Operations Manual for details on the ASN command.

* 24.

Include support for error logging?

[Y/N]:

If you choose this option, the Executive logs information on disk and
tape device errors and time-outs,
logs
information on traps to
undefined interrupt vectors, and logs cache and memory parity error
traps.
The Error Log task stores the recorded information in a disk
file for later analysis.
See the RSX-llM/M-PLUS Error Logging Manual
for detailed information.
Error logging is most useful for detecting intermittent faults on
large systems.
Error logging support adds approximately 700(10) words
of code to the Executive.
SYSGEN supports error logging only for the following devices:
CT:
DB:
DD:
OF:
When

you

select

DK:
DL:
OM:
DP:
this

DR:
OS:
OT:
DU:

DX:
DY:
EM:
MF:

MM:
MS:
MT:

option,

SYSGEN

includes

support

for

checkpointing, the Send/Receive directives, and f cr nonresident tasks.
If you did not select memory parity support (Question 12 of the Target
Configuration Section) ,
the Error Log task does not record cache or
memory parity errors.
Error logging is not available for RSX-llS systems.
not appear.

4-30

The question does

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
* 25.

Do you intend to include a user-written driver?

[Y/N]:

This question should be answered No if you do not intend to include a
user-written driver in your target system. A user-written driver is a
non-DIGITAL supplied and non-DIGITAL supported driver.
See the
RSX-llM Guide to Writing an I/O Driver for a complete discussion of
SYSGEN support for user-written"Cfrivers.
You should answer Yes if you want the user-written driver to be memory
resident.
If you respond Yes, SYSGEN asks Questions 26 and
27 concerning
Executive routines $GTWRD (GET WORD) and $PTWRD (PUT WORD).

* 26.

Include routine $GTWRD?

the

[Y/N]:

This option (the $GTWRD Executive routine) allows you to obtain a word
from a user-defined buffer.
See the RSX-llM Guide To Writing an I/O
Driver for information on how to use this routi~ ~
If you have included LA:
(LPAll-K) as one of the specified devices,
SYSGEN automatically includes support for the $GTWRD routine.
Also,
SYSGEN includes support for the Send/Receive directive.
This question does not appear if you responded No to Question 25
do not intend to include a user-written driver).

* 27.

Include routine $PTWRD?

(you

[Y/N]:

This option (the $PTWRD Executive routine) allows you to send a word
to a
user-defined buffer.
See the RSX-llM Guide To Writing an I/O
Driver for information on how to use this routi~ ~
If you have included the AD:
(ADOl-D) or AF:
(ACFll) subsystem
(see
Appendix C)
as one of the specified devices, SYSGEN automatically
includes support for the $PTWRD routine.
This question does not appear if you responded No to Question 25
do not intend to include a user-written driver).

* 28.

Disk writecheck?

(you

[Y/N]:

Writecheck support increases the data reliability of disks.
The added
activity of disk writecheck does, however, diminish the speed of disk
throughput.
If selected, writecheck may be enabled or disabled
dynamically on a per-drive basis with the MCR SET command.
SYSGEN supports disk writecheck for the following devices:
DB

JJU

T"'\TT

4-31

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
If your target system configuration does
devices, the question does not appear.

not

include

any

these

NOTE
If you include writecheck support and
want to use it, you must issue the MCR
SET /WCHK=ddnn:
command
after
you
complete SYSGEN.
This command causes
the driver to perform a
writecheck
function after each write.
For more
information on the
MCR
SET
/WCHK
command,
see the RSX-llM/M-PLUS MCR
Operations Manual.
Here is how the writecheck function works. After the data is written
to disk,
the disk controller reads a copy of that data from memory,
word by word, while simultaneously reading a second copy of that data
from the disk and does an exclusive OR (XOR instruction) to compare
them.
If the writecheck function fails
(that is,
if the copies
compared are not the same),
the driver retries the original write
operation and performs another writecheck until
the maximum retry
count is reached
(at which time the system issues the hard error
message IE.WCK).
RSX-llS does not support
appear.

* 29.

disk

writecheck;

Software write-lock support?

the

question

does

not

[Y/N]:

If you respond Yes to this question, SYSGEN includes Executive support
for
the MCR MOUNT /[NO]WRITE command.
The MCR MOUNT /[NO]WRITE
command allows you to gain control over write access to a specified
mass storage device. See the RSX-llM/M-PLUS MCR Operations Manual for
a complete description of the MCR MOUNT /[NO]WRITE command.
The MOUNT /[NO]WRITE command can be used
the following mass storage devices:

for

software

Disks:
DB
DP

DF
DR

DL
DU

Magnetic Tape:

Dectape:

Cassette:
CT

4-32

write-locking

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
Support for software write-lock adds approximately 40(10) words to the
size of the Executive.
This option is not available for RSX-llS systems.

* 30.

Executive Debugging Tool (XDT)?

[Y/N]:

The Executive Debugging Tool
(XDT)
provides a subset of ODT-11
commands to be used in the system state. See the RSXll-M Guide to
Writing an I/O Driver for details on XDT.
If you respond Yes, SYSGEN includes XDT in the Executive to allow
interactive debugging of Executive modules, privileged tasks, I/O
drivers, and interrupt service routines.
This option includes consistency checking in the dynamic storage
region (pool) routines.
The routines are used to detect corruption of
pool pointers. Also included is code to trap I/O process corruption
from drivers.
XDT adds approximately lK words to the size of the Executive.

* 31.

Rotating pattern in data lights?

[Y/N]:

This option causes the PDP-11 CPU lights
pattern when the processor is idle.
This option is available only on
11/70 processors.

* 32.

the

rotate

PDP-11/45,

11/50,

circular

11/55,

Include support for communications products (such as DECnet)?

and

[Y/N]:

This option allows you to include DECnet or DPM/DPM-PLUS support.
Refer to the DECnet or DPM/DPM-PLUS documentation for details.
If you respond Yes, SYSGEN includes
following products:

the

support

necessary

•

DECnet-llM

RSX DLX-11

•

RSX-11 PSI/CAN (X.25 packet-switched interface)

•

RSX-11 PSI/FR (X.25 packet-switched interface)

RSX-llM SNA PROTOCOL EMULATOR

RSX-11 3271 PROTOCOL EMULATOR

4-33

for

the

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
When you respond Yes, SYSGEN also automatically includes:
•

FCP support

•

AST (Asynchronous System Traps)

•

Cancel Selective Marktime support

•

Logical Device Assignment support

•

Loadable Device Driver support

•

Address Checking support

•

Get Partition Parameters Directive support

•

Get Task Parameters Directive support

•

Send/Receive Directive support

•

Extend Task Directive support

•

Asynchronous Buffered I/O support

support

When you respond Yes, the following message appears on your terminal:
If you will be generating DECnet into this system, be
sure you have read the section on SYSGEN requirements
in the RSX DECnet Network Generation and Installation
Guide.
Several DECnet features (eg. remote terminal support,
118 task loading/upline dumping etc.) require special
consideration during SYSGEN.

* 33.

System-controlled partitions?

[Y/N]:

This option allows the Executive to allocate available space in memory
to accommodate as many tasks as possible at any one time.
Unlike
user-controlled partitions where the user must define subpartitions to
run multiple tasks within a main partition, the Executive allocates
the space for the tasks within a system-controlled partition.
System-controlled partitions are most effective when combined with the
Shuffler (SHF) •
If you selected DBMS-11 support
(Question 1), SYSGEN automatically
includes support for system-controlled partitions and, therefore,
bypasses this question.
This option is not available for unmapped systems or for RSX-llS.

* 34.

Include support for the Shuffler?

[Y/N]:

The Shuffler
(SHF)
is a privileged task designed
fragmentation within system controlled partitions.
requires Executive support to run.

4-34

to
The

minimize
Shuffler

DETAILS OF SYSGER PHASE I

EXECUTIVE OPTIONS {Cont.)
Therefore, if you respond Yes to this question, SYSGEN then builds the
Shuffler task (SHF) and includes it in your system image.
The Shuffier is not avaiiabie for unmapped systems or for RSX-llS.
If
you did not select system-controlled partitions, this question does
not appear. For more detailed information on using the Shuffler,
refer to the RSX-llM/M-PLUS System Management Guide.
NOTE
If you intend to include the Shuffler in
your target system,
it should not be
installed
in
a
system-controlled
par ti ti on.

* 35.

Queue manager and queued print spooler?

[Y/N]:

This option allows you to provide user-controlled spooling support for
RSX-llM systems. See the RSX-llM/M-PLUS System Management Guide for a
description of the features of RSX-llM print spoolers.
If you respond Yes, the required support is built into the Executive.
If you respond No, you will be asked in the System Options Section
whether or not you want to build the serial despooler.
When you respond Yes, SYSGEN automatically includes:
•

Stop Bit Directive support

•

Send/Receive Directive support

•

Parent/Offspring Tasking Directive support

This option is only available for mapped RSX-llM systems.

* 36.

Group global event flags?

[Y/N]:

This option makes available 32(10) additional event flags for each
user group on the system. Group global event flags are in addition to
a single member's local event flags.
In the UIC
[303,26),
for
instance, 303 indicates the group number;
the number 26 indicates one
member in the group.
If the members in group 303 were running a
system that supported group global event flags, there would be 32
additional event flags to be shared among the members in the 303
group.
Another group, say 300, would have 32 additional event flags
to share among the members of that user group.
If you select this option, you get full support for Group Global Event
Flag directives as well.
For more information on Group Global
RSX-llM/M-Plus MCR Operations Manual.

4-35

Event

Flags,

refer

the

DETAILS OF SYSGER PHASE I

EXECUTIVE OPTIONS (Cont.)
* 37.

Enter code for system directives

This option includes system directives;
by the associated letter code:
A-Get Partition Parameters
B-Get Task Parameters
C-Send/Receive
D-Alter Priority
E-Extend Task
F-Connect to Interrupt Vector

each directive

indicated

G-Get Sense Switch
H-Set System Time
I-Stop Bit
J-Specify Requested Exit AST
K-Parent/Offspring Tasking
L-Parent/Offspring Tasking
with Chaining

Enter an asterisk (*) to display the table of directives.
Enter a
percent sign
(%)
to include all directives.
If you enter %, SYSGEN
includes all valid directives listed here and proceeds immediately to
the next question.
In this case, there is no need to terminate input
with a period (.).
Enter a period (.) to terminate the question.
Ref er to the
RSX-llM/M-PLUS
descriptions of the directives.

Executive

Reference

Manual

for

NOTE
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 and many
DIGITAL-supplied utilities (for example,
PIP) will not execute correctly.
If you select DBMS-11 or communications products support, SYSGEN
automatically
includes
the Get Partition Parameters, Get Task
Parameters, and Extend Task directives.
If you selected the queue manager for
your target system, SYSGEN
automatically
includes support for
the Parent/Offspring Tasking
directive.
If you select ANSI magtape support, error logging support, DBMS-11,
the Queue Manager
(QMG),
the CO driver,
communications products
support, or the LA:
(LPAll-K), SYSGEN
automatically
includes
Send/Receive directive support.
If you select any K-series
support is included.

devices,

Connect

Interrupt

Vector

Parent/Offspring
tas~ing
with
chaining
is
a
superset
of
Parent/Offspring tasking.
If you select DBMS-11, the queue manager,
or either Parent/Offspring Tasking or Parent/Offspring Tasking with
Chaining,
SYSGEN automatically includes support for
the Stop Bit
directive.
If you select the Extend Task directive, SYSGEN automatically includes
checkpointing support.
This does not apply if you are generating a
RSX-llS system.

4-36

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
If you select the Specify Requested
automatically includes AST support.

Exit

AST

directive,

SYSGEN

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

* 38.

Number of pre-allocated QIO packets [D R:0.-15.

does

D:S.]:

You can enhance I/O throughput by preallocating a number of I/O
packets from the dynamic storage region, and by 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;
specify the maximum size of this list with
your decimal response to this question.
When an I/0 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 an I/0 packet is deallocated,
the packet is linked back into the list, provided that the list is not
full.
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 make
the best use of this option, aetermine the average number of
outstanding concurrent I/O requests on your system and enter that
value as your response.
Enter a number in the range O.
packets to be preallocated.

through 15., indicating the number

The default is 5. When your system uses preallocated QIO packets
(that is, when you specify any value greater than zero) your system
takes advantage of QIO speed optimization.
Enter 0 to exclude preallocated QIO
optimization.

* 39.

packets

well

Size of data transfer vector in words [D R:0.-33.

QIO

speed

D:33]:

The value you supply in response to this question specifies the size
in words of the data transfer vector. The data transfer vector is a
series of MOV instructions in a
loop used by the Executive for
optimizing data transfers in the Executive routine $BLXIO which is
then used by the Shuffler. The greater the size of the data transfer
vector, the faster the Executive transfers the data in $BLXIO.
The
trade-off is speed for pool size.
The smaller the data transfer
vector, the greater the pool size.

4-37

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
Enter a number in the range 0(10) through 33(10) to specify the number
of MOV instructions in the vector.
If the size of the data transfer
vector were 16, for example, a 36-word data transfer enters the loop
control only 3 times rather than 36 times if there were only one MOV
instruction in the vector.
The default vector size is 33(10).
It is
select the default vector size of 33(10).

generally

advisable

If you specify a data transfer vector size that is greater than 0 but
less than 5(10), SYSGEN forces that value to 5(10).
The reason for
this is that the data transfer vector is not really efficient until
the number of MOV instructions in the loop is at least 5(10).
However, you may specify a O.
In this case, SYSGEN builds the data
transfer vector with a single MOV instruction in the loop.
This option does not apply to unmapped systems.

* 40.

Round-robin scheduling interval in ticks [D R:0.-1000.

0:5]:

When many competing memory-resident tasks have equal priority, the
Executive tends to give CPU time 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.
With the round-robin scheduling option, the Executive periodically
rotates
(when the specified number of ticks elapses) tasks of equal
priority within the Active Task List, so that tasks of equal priority
share CPU time.
Round-robin scheduling refers to the algorithm whereby each task of a
group
of tasks is successively given preference for available
processor time. The actual algorithm in RSX-llM is used to locate the
first task within each priority class that is not blocked from
executing, give it processor time, and, when it completes, move that
task to the end of its respective priority class. Tasks that are
mainly intended for computation, with a minimal amount of I/O, execute
in a round-robin fashion;
whereas I/0-bound tasks tend to remain at
the front of their respective priority class.
Round-robin scheduling does not affect the normal competition for CPU
time by tasks with different priorities.
It also does not affect
tasks not in the range set by the response to Questions 41 and 42.
Round-robin scheduling affects only those tasks in an ATL {in memory)
that are not blocked, checkpointed, or in a partition wait queue.
Round-robin scheduling requires little Executive
size) •

overhead

If you want this option, enter a number in the
1000(10). SYSGEN then asks Questions 41 and 42.
Enter 0 if you do not want this option.
The default is 5(10).

4-38

range

(time
1

and

through

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
NOTE
The tick interval value can be changed
after SYSGEN by using the VMR or MCR SET
/RNDC command.

* 41.

Highest priority class for consideration [D R:l.-249.

D:lSO.]:

Round-robin scheduling affects a specified range of priority classes.
A typical range is 1(10) through 150(10). The permissible range is
1(10) to 249(10).
This entry provides the highest priority
round-robin scheduling. Default is 150(10).

class

eligible

This question appears only if you selected the round-robin
option.

for

scheduling

NOTE
The highest priority class value can be
changed after SYSGEN by using the VMR or
MCR SET /RNDH command.

* 42.

Lowest priority class for consideration [D R:l.-x.

D:l.]:

This is the lowest priority class eligible for round-robin scheduling.
The permissible range is 1(10) through x(lO), where x is equal to
highest priority class entered in response to Question 41.
default is 1(10).
This question appears only if you select
option.

the

round-robin

the
The

scheduling

NOTE
The lowest priority class value can be
changed after SYSGEN by using the VMR or
MCR SET /RNDL command.

* 43.

Executive level disk swapping interval [D R:0-5000.

D:y]:

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 by
using the swapping algorithm.

4-39

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
The swapping algorithm creates an "effective" task priority by using
the swapping interval (the response to this question) and the swapping
priority
(the response to Question 44).
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 the Executive varies a task's priority.
(The
range
is
negative swapping priority through positive swapping
priority.)
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 44.
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 ~wapping priority in Question 44).
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 nonresident task with the effective
priority of the resident task (effective priority is the sum of the
running priority and the swapping priority).
If the nonresident task
can fit into the resident task's space and if, due to the decrementing
of swapping priority, the priority of the nonresident task is higher,
the nonresident task can checkpoint the resident task.
Disk swapping applies to tasks competing for each main partition
(except DEVICE and COMMON partitions) and for the highest priority,
nonresident tasks assigned to those partitions.
If you select this option, SYSGEN automatically includes
checkpointing.

support

for

The permissible range is 0(10) through 5000(10). The default (y) is a
value that is equal to the round-robin scheduling interval multiplied
by 6.
The maximum default size is 5000(10).
If the value of the
default calculated for y exceeds 5000, SYSGEN defaults the value to
the maximum size of 5000(10).
If the round-robin scheduling interval
was 0 (you excluded support), this default is 30(10).
To disable this option, enter O.
NOTE
The disk swapping interval
can
be
changed after SYSGEN by using the VMR or
MCR SET /SWPC command.
This question does not appear for RSX-llS systems.

4-40

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
* 44.

Swapping priority [D R:l.-20.

0:5.]:

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.
You can enter a number in the range 1(10)
through 20(10).
It
recommended that you enter the default swapping priority of 5(10).
This question
swapping.

appears

only

you

selected

Executive-level

is
disk

NOTE
The swapping priority can be changed
after SYSGEN by using the VMR or MCR SET
/SWPR command.

* 45.

Size of Dynamic Storage Region (Pool) in words [D R:256.-16384.

0:1024.]:

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), generally referred to as pool
space.
For example, the Executive uses this memory space to process
I/O or time-dependent scheduling requests. As demands for space are
made, the Executive allocates the necessary memory from pool using a
first-fit algorithm. When allocated space is no longer needed, it is
released back to the pool of available memory.
Pool 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 decrease in system
performance occurs and the system could hang with a pool deadlock. On
the other hand, if there is an unnecessarily large amount of pool
space allocated, you may be wasting system resources (memory).
The maximum size of pool space is limited by
unmapped system.

physical

memory

Appendix D specifies some RSX-llM functions that use dynamic
Use it to calculate how much memory you should allocate.

memory.

After you calculate the amount of pool space needed for your target
system, add approximately 12 to 18 percent to cover possible pool
fragmentation conditions.
Note that you can later extend this initial allocation using
or VMR SET /POOL command.
This entry must be in multiples of two words.
of entries is 256(10) through 16384(10).

4-41

The

the

permissible

MCR
range

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
This question appears for unmapped systems only.
SYSGEN forces a
minimum pool size of 1024(10) words for mapped systems, and expands
the pool size to the maximum size possible during the System VMR
Section of Phase II.
(See the SET /POOL command in Chapter 10 of the
RSX-llM/M-PLUS System Management Guide.)
The default is 1024(10).

* 46.

Seconds between printer not ready messages [D R:0.-255.

0:30.]:

SYSGEN asks this question if you included a
line printer in the
peripheral configuration and if you included TKTN support (the TKTN
task prints the device not ready message)
9

Specify the number of seconds between printer-not-ready messages.
entry of O suppresses the messages altogether.

the

The default is 30(10).
If you specify
minimum value of this entry is 15(10).

* 47.

value

other

than

Seconds between card reader not ready messages [D R:0.-255.

0:30.]:

This question appears if you included a card reader in the peripheral
configuration and
if you included TKTN support (the TKTN task prints
the device not ready message) •
Specify the number of seconds between card reader not ready
An entry of 0 suppresses the messages altogether.

messages.

The default is 30(10).
If you enter a nonzero value,
15(10).

* 48.

the

minimum

value

the

entry

System crash register and stack dump device CSR [O R:0-177700 0:177564):

If the system crashes and this option is included, the Executive stack
and registers are output to the selected device.
The normal device is the console
Enter the CSR address of the device.
.... 'h,...
rnk ..I..;;:,
-i edefault
terminal, which has a CSR address cf 1"7'7Ct:Ji
..LI I
device.
...IV*'%. •

J. 1.1

.LO

t...1.lC

Enter 0 to suppress this option.
I f you specify a value other than 0, it
160000 through 177700(8).

4-42

can

only

the

range

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
* 49.

Checkpointing [Y/N]:

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

partition

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.
Checkpointing optimizes the use of processor memory while maintaining
a priority-scheduling algorithm.
In some cases, an activated task cannot execute because the partition
where the task must execute is occupied.
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 moves 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
its priority is
lowered,
the lower priority task
(TASKA)
on disk moves back into
memory to continue execution.
This task (TASKA)
continues execution
from the point at which it was interrupted.
RSX-llM supports checkpointing in both user-controlled partitions
system-controlled partitions.

and

Respond Yes if you want checkpointing.
Electing this option and
answering
No
to
Question
50
requires that you build each
checkpointable task with its own contiguous checkpoint space,
into
which the executing task
image can be swapped.
Refer to the
RSX-llM/M-PLUS Task Builder Manual, particularly to the information on
using the /AL---ra11ocate)
switch.
(SYSGEN automatically includes
checkpointing if you selected Executive level disk swapping.)
Note that if you exclude checkpointing support, the
support task checkpointing during terminal input.

Executive

cannot

If you select checkpointing, SYSGEN includes support for nonresident
tasks
(see Question 4).
SYSGEN automatically includes checkpointing
if you select Executive level disk swapping (Question 43), support for
error logging
(Question 24), or the Extend Task directive (Question
37) •

This question appears for RSX-llS systems only
support (Question 32, Executive Options).

* 50.

you

chose

DECnet

Checkpointing with system checkpoint file [Y/N]:

Respond Yes if you want checkpointing with a system checkpoint file.
This option allows checkpointing with a system checkpoint file rather
than requiring contiguous checkpoint space for
each checkpointable
task image.
If you select checkpointing with a system checkpoint file,
you must
allocate space for the file when you start up the system, for example,
in the STARTUP.CMD file.
There is an ACS command
included in the
STARTUP.CMD file provided with your distribution kit.
Refer to the
ACS command in the RSX-llM/M-PLUS MCR Operations Manual for more
information.
4-43

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
If you select multiuser protection (Question 12), SYSGEN automatically
includes support for checkpointing with the system checkpoint file.
This question appears only if you answer yes to checkpointing
(Question 49) and if you are generating a mapped target system.
This question does not appear for RSX-118 systems.

* 51. Crash dump analysis:

A- PANIC B- Crash Dump Analysis (CDA) C- None [D:

If you do not select the dump analysis option 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 Manual describes the PANIC dump routine.
The
RSX-1IM,7M-PLUS Crash Dump Analyzer Reference Manual describes CDA in
detail. The CDA crash dump routine is normally used for debugging new
drivers or privileged tasks after the drivers or tasks crash the
system. CDA provides a means of generating a formatted dump of memory
on a line printer or a terminal.
Enter A if you want the PANIC dump routine.
Enter B (default) if you want Crash Dump Analysis (CDA)
is recommended that you select CDA support.

support.

If you select A, SYSGEN does not ask Questions 52, 53,
does ask Question 55.

and

If you select B, SYSGEN asks Questions 52, 53, and 54;

but not 55.

* 52.

54;

It
but

CDA output notification device CSR [O R:l60000-177700 0:177564]:

This question appears only if you
support) in Question 51.

Dump

Analysis

Enter the CSR for the device that you want the system crash
sent to. Typically, this is the console device (177564(8)).

message

* 53.

selected

(Crash

Enter CDA memory dump device mnemonic (ddu:)

This question appears only if you
support) in Question 51.

selected

[S R:3-4]:

(Crash

Dump

Analysis

Enter the mnemonic and unit number of the device on which you want to
output a memory dump in binary. Note that the memory dump device must
be part of the target hardware configuration but is not necessarily
generated into the target system. Supported devices are:
DB
DD
DK

DM
DR
DT
DX

DY
MM
MS
MT

DU (RA60, RC25, RX50 only)

4-44

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)
NOTE
If you choose DU as the crash dump
device, SYSGEN will issue a warning that
you cannot crash to a fixed-media disk
(the RA80/81, the fixed-media portion of
the RC25, and the RD51).
If possible, avoid using your system device as the crash dump
CDA overwrites the contents of the crash dump device.

* 54.

device;

Enter CDA memory dump device CSR [O R:l60000-177700 D:<default>]:

This question appears only if you
support) in Question 51.

selected

(Crash

Dump

Analysis

Enter the CSR address of the memory dump device. The default depends
on the type of device you specify in Question 52 as the crash dump
device:
Device
Type

Default
CSR

Device
Type

Default
CSR

DB
DD
DK
DL
DM
DR
DT

176700
176500
177404
174400
177440
176700
177342

DU
DX
DY
MM
MS
MT

172510
177170
177170
172440
172522
172522

The allowable DU:-type dump devices are the RA60, RC25, and the RXSO.

* 55.

Enter PANIC memory dump device CSR [O R:l60000-177700 D:l77564]:

If you selected PANIC dump rather than CDA, enter the CSR address of
the PANIC dump device.
Normally, this is the CSR address of the
console device, which is also the default.
This device
must
be
a
paper
tape-,
terminal-,
or
line
printer-compatible device. The device must receive a single byte at a
time.

* 56.

RT-11 emulation support?

[Y/N]:

This option allows you to include RTEM-11
RTEM-11 documentation for details.

4-45

support.

Ref er

your

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS
4.6

TERMINAL DRIVER OPTIONS SECTION

Your responses to these questions specify the RSX-llM terminal driver
you want as part of your target system. You can also specify terminal
driver options.
Terminal driver options are described fully in the RSX-llM/M-PLUS
Drivers Reference Manual.

* 1.

I/O

Terminal driver desired (A/B/C/D, * prints table)

This option 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 (three different versions)

•

Full-duplex

Enter A to select the half-duplex terminal driver that allows you to
specify the half-duplex terminal driver options that meet the needs of
your target system.
Enter B to select the user-oriented half-duplex terminal driver.
SYSGEN automatically includes the following terminal driver options
when you select the user-oriented terminal driver:
•

Automatic carriage return/line feed

(Question 4)

•

Task checkpointable during terminal input (Question 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 user-oriented terminal
driver.

•

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

•

Write with CTRL/O cancellation (Question 7)

•

Breakthrough write (Question 8)

•

CTRL/R (retype)

•

Get multiple characteristics (Question 11)

•

Get terminal driver options (Question 13)

•

Transparent read/write (Question 15)

•

Settable case conversion for input (Question 16)

•

Read after prompt (Question 17)

(Question 9)

4-46

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)

•

Read with no echo (Question 18)

•

Read with special terminator (Question 19)

•

CRT rubout support (Question 20)

•

Terminal-host synchronization (Question 21)

User terminal input buffering (Question 22)

•

Variable-length terminal input buffering (Question 23)
NOTE
If you want more or fewer options than
what is automatically included with the
user-oriented
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.
SYSGEN
automatically includes the following terminal driver options when you
select the full duplex terminal driver:
•

Passes form feeds directly to the terminal

(Question 1 Ji)'

•

Automatic carriage return/line feed

•

Task checkpointable during terminal input (Question.tpf.
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.

•

Write with CTRL/O cancellation (QuestiomW)

•

Hold screen mode (Question ~~ 1)

•

Transparent read/write (Question IDS'

•

Settable case conversion for input (Question !ll~9

•

Read with no echo (Question

•

Read with special terminator (Question

•

Terminal-host synchronization (Question :@1)

•

User terminal input buffering (Question

•

Variable-length terminal input buffering (Question 29')

•

LA30P support (Question~)

(Question!-'.~~''

:i_~IT)

1,19::,

~I~
1

' '~~r

If you include a DHVll device in your system, SYSGEN
includes the full-duplex terminal driver and does
question.

4-47

automatically
not ask this

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)
If you have not chosen a mapped system and loadable driver support,
SYSGEN will exit.
You should restart SYSGEN and choose the mapped
system and the loadable driver support to include the DHVll device.
Enter D to select the baseline terminal driver. Note that this driver
and a multiuser protection system are mutually exclusive. This
terminal driver (D) is a half-duplex terminal driver with minimum
functionality.
It has no SYSGEN options.

* 2.

Unsolicited input timeout value in seconds [D R:0.-255.

0:120.]:

This option is available with the full-duplex terminal driver only
(C);
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 time-out value that you specify. Valid time-out range is 0
through 255(10) seconds.
Enter 0 to inhibit the unsolicited
full-duplex terminal driver.

input

timeout

feature

for

Press the RETURN key for the default timeout value of 120 seconds, or
specify the number of seconds (in the range 1 through 255(10)) to wait
to timeout on unsolicited terminal input.
~~~

Pass form feeds directly to the terminal?

[Y/N]:

This option appears only if you responded A or B to Question
tailorable or user-oriented half-duplex terminal driver).
The half-duplex driver normally converts a form feed into
feeds.
Respond Yes to suppress this conversion.

(the

eight

line

NOTE
If your system includes an LA120 or an
LA180S terminal, you should respond Yes.
This option adds approximately 24(10) words to the terminal driver.

'4.

Automatic carriage return/line feed?

[Y/N]:

This option appears only if you responded A to Question 1
(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.

4-48

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)
* 5.

Task checkpointable during terminal input?

The option appears only if you responded A to
included Executive support for checkpointing.

[Y/N]:
Question

and

you

If you select this option, checkpointable tasks can be displaced
memory by another task during terminal input.

from

This option adds approximately 110(10) words to the terminal driver.
If your target system does not include DECnet and if you did not
select the full-duplex terminal driver, this option adds approximately
160(10) words to the terminal driver.

* 6.

Unsolicited input character AST?

[Y/N]:

This option appears if you responded A or C to Question 1 and included
Executive support for ASTs;
the user-oriented and full-duplex drivers
include this option by default if your target system includes
Executive support for ASTs
(Question 17 in the Executive Options
Section) .
If you respond Yes, a task that attaches to a terminal can specify an
AST entry point upon receiving unsolicited input from a terminal (for
example, CTRL/C attaches the task 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 drivero
Without support for unsolicited input character AST, you cannot use
EDT in character mode nor can you terminate RMD with a CTRL/Z.
In
addition, the I/O Exerciser (IOX) requires unsolicited input character
AST support if it is to support the CTRL/C function.
If you do not select this option and intend to use RMD, the RMD task
only displays the first page of output.
However,
it is still
possible, through other means, to read subsequent pages of the RMD
display.
See the RSX-llM/M-PLUS System Management Guide for an
explanation.
Write with CTRL/O cancellation?

[Y/N] :

This question appears only if you responded A to Question 1.
If you respond Yes, 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?

[Y/N]:

This question appears if you responded A or C to Question 1.
If you
selected multiuser protection support, SYSGEN automatically includes
this option.

4-49

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)
If you respond Yes, a privileged task can issue a breakthrough write
request that prints 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
(Question
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)?

[Y/N]:

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

and

did

If you respond Yes, the terminal driver sends to the terminal a
carriage return and 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.

* 10.

Escape sequence handling?

[Y/N]:

This question appears if you responded A or C to Question 1.
If you respond Yes, the terminal driver recognizes and treats
sequences
as
line terminators for all solicited input
read-pass-all or read-with-special-terminator requests.

escape
except

This option adds approximately 128(10)
words to the full-duplex
terminal driver and approximately 160(10) words to the half-duplex
terminal driver.

* 11.

Get multiple characteristics?

[Y/N]:

This question appears if you responded A or C to Question 1.
If you respond Yes, a task can determine physical characteristics (for
example, CRT, VT52,
slaved, or VTlOO) of individual terminals.
The
task RMD makes use of this option, for example.

4-50

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)
If you selected the full-duplex terminal driver
(C)
and want the
capability to display terminal characteristics, you must include
support for Get Multiple Characteristics.
This option adds approximately 96(10)
words to the full-duplex
terminal driver and approximately 110(10) words to the half-duplex
terminal driver.
Under most circumstances, you
option.

* 12.

should

Set multiple characteristics?

include

this

terminal

driver

[Y/N]:

This question appears if you responded A or C to Question 1.
If you respond Yes, 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
the
physical
characteristics of any terminal in the system.
If you selected the full-duplex terminal driver
(C)
and want the
capability to modify various terminal characteristics (see the MCR SET
command), you must include support for Set Multiple Characteristics.
This option adds approximately 256(10) words to the terminal driver.
Under most circumstances, you
option.

* 13.

should

Get terminal driver options?

include

this

terminal

driver

[Y/N]:

This question appears if you responded A or C to Question 1.
If you respond Yes, a task can determine which of the terminal
options were selected during system generation.

driver

This option adds approximately 32(10)
words to the full-duplex
terminal driver and approximately 64(10)
words to the half-duplex
terminal driver.

,:4.

Hold-screen mode?

[Y/N] :

This question appears only if you responded A to Question 1.
If you respond Yes 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.)
This option adds approximately 92(10) words to the terminal driver.

4-51

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)
NOTE
When you select this option, SYSGEN
automatically includes terminal driver
support for the transparent read/write
option (Question 15) •

!*, :~15~

Transparent read/write?

[Y/N] :

This question appears only if you responded A to Question
not include the hold-screen option (Question 14).

and

did

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 characters
(for
example, RETURN).
If you respond Yes, the terminal driver provides
support for I/O functions (IO.RAL and IO.WAL)
that bypass character
filtering and permit output of up to 32K bytes.
This option adds approximately 48(10) words to the terminal driver.
*,,,~~·

Settable case conversion for input?

[Y/N]:

This question appears only if you responded A to Question 1.
The terminal
received.

driver

normally

accepts

and

echoes

characters

If you respond Yes, you can selectively enable input character
conversion (using the MCR SET /[NO]LOWER command) so that the terminal
driver can automatically convert lowercase to uppercase. This option
also allows the terminal driver to recognize the brace character (175)
and the tilde character (176) as ASCII characters rather than a form
of escape when the terminal is set to lowercase.
This option adds approximately 30(10) words to the terminal driver.

* 17.

Read after prompt?

[Y/N]:

This question appears if you responded A or C to Question 1.
If you respond Yes, a read after a 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) has time to issue its read request.
This option adds
terminal driver
terminal driver.

approximately 128(10)
words to the full duplex
and approximately 185(10) words to the half duplex

4-52

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS {Cont.)
* 18.

Read with no echo?

[Y/N]:

This question appears only if you responded A to Question 1 and did
not include multiuser protection support.
(Multiuser protection
support automatically includes this terminal driver option.)
If you select this option, you can issue the read functions
IO.RLB,
IO.RVB, and IO.RPR and specify that the driver not echo terminal
input.
This option adds approximately 48(10) words to the terminal driver.
*il !·.19~

Read with special terminator?

[Y/N] :

This question appears only if you responded A to Question 1 and did
not include multiuser protection support.
(Multiuser protection
support automatically includes this terminal driver option.)
The line terminator for a normal read is the RETURN or ESCAPE.
If you
select this option, any character less than 40(8) or greater than
174(8) can terminate a read with a special terminator request.
However, escape sequences cannot be recognized in this mode.
Note that if the terminal
is set to lowercase,
characters less than 40(8) can act as terminators.

only

177(8)

and

This option adds approximately 45(10) words to the terminal driver.

* 20.

CRT rubout support?

[Y/N]:

This question appears if you responded A or C to Question 1.
If you respond Yes, the terminal driver echoes rubouts or deletes on a
CRT terminal as backspace-space-backspace;
this option erases the
character from the CRT screen when you press the RUBOUT or DELETE key.
This option adds approximately 64(10) words to the terminal driver.

~~~i.

Terminal-host synchronization?

[Y/N]:

This question appears if you responded A to Question 1.
If you respond Yes, 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.
This option adds approximately 84(10) words to the terminal driver.

4-53

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)
NOTE
If your system includes a VTSO terminal
with the copier option or an LA120 or
VTlOO with a baud rate greater than
1200, you must respond Yes to this
question.

~~~'~~ff-~;

User terminal input buffering?

[Y/N]:

This question appears if you responded A to Question 1.
The terminal driver normally receives characters and stores the
characters in the Executive address space until it receives a line
terminator. Upon receiving a line terminator, the driver places the
contents of the Executive address space into the requesting task's
input buffer.
If you respond Yes, 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.

* ~:,'.1•

Variable length terminal input buffering?

[Y/N]:

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 buffer allocation from dynamic memory.
If you respond Yes, the terminal allocates buffers large enough to
satisfy the read requeste The largest buffer can be 255 bytes long.
This option adds approximately 24(10) words to the terminal driver.

•t:i4.

LA30P support?

[Y/N]:

This question appears only if you responded A to Question 1.
The LA30P DECwriter connects to the processor with a single buffered
interface.
Respond Yes only if your system includes an ·LA30P
terminal;
the terminal driver supports all other combinations of
DIGITAL terminals and interfaces.
If you respond No, the second of two rapidly typed characters
discarded by the terminal driver.

may

This option adds approximately 48(10) words to the terminal driver.

4-54

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)
* 25.

Hardware unrecoverable input error notification?

[Y/N]:

This question appears only if you responded C to Question 1.
If you respond Yes, 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
of an input error (including type).
If you respond No, the driver
errors.

ignores

hardware

unrecoverable

input

This option adds approximately 32(10) words to the terminal driver.

* 26.

Device independent cursor positioning?

[Y/N]:

This question appears only if you responded C to Question 1.
If you respond Yes,
the full-duplex terminal
terminal-independent cursor-positioning commands.
cursor-positioning character, the driver outputs a
character string before it outputs the buffer.

driver
supports
When you specify a
cursor-positioning

This option adds approximately 192(10) words to the terminal driver.

4-55

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS
4.7

SYSTEM OPTIONS SECTION

This section presents several options that let you tailor your system
further.
Read the description of each option carefully before making
your selections.

* 1.

Include ANSLIB.OLB to support big-buffering?

[Y/N]:

This option allows you to include ANSLIB.OLB, which contains the
routines necessary to support big-buffering for FCS.
(If you need
more information on big-buffering for FCS, see the RSX-llM I/O
Operations Manual.)
If you respond Yes, SYSGEN creates ANSLIB.OLB as it would have if you
had chosen ANSI magtape support in Question 13 of the Executive
Options Section.

* 2.

Build library of ISA FORTRAN industrial/lab routines?

[Y/N]:

If you respond Yes to this question, SYSGEN builds the "Industrial
Computer System FORTRAN Procedures for Executive Function and Process
Input-Output (ISA SP61.l)" for the IC, IS, UD, AR,
LA, LS, or IP
devices in the system library. These routines (commonly known as the
Purdue calls)
comprise an interface of FORTRAN subroutines that
conform to a formal standard approved by the Instrument Society of
America. The standard deals with three areas of real-time systems:
the
Executive
interfaces,
the
process
input-output function
interfaces, and bit string manipulation.
If you include only one of the previously named devices, SYSGEN puts
the necessary routines in
[l,l]SYSLIB.OLB of the privileged object
disk (the baseline disk for the big disk distribution kit and EXCPRV
for the RLOl/02 distribution kit).
However, if you specify more than one of those devices for your target
system, SYSGEN builds individual libraries of routines for each
device. Some routines for a device have the same name as some
routines for another device, and the different libraries are necessary
to contain the different routines:

•
Device

Library

AR/LS
IC
IP
IS
LA
UD

[ 1 , 1] L PS LIB • OLB
(1,1] ICSLIB.OLB
[ 1, 1] PCSL IB. OLB
[ 1, 1] I SL IB. OLB
[ 1 , 1] L PAL IB • OLB
[l,l]UDCLIB.OLB

If you did not specify one of these devices in Question 15
Target Configuration Section, this question does not appear.

4-56

the

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)
* 3.

Build the PLAS resident FCS?

[Y/N]:

If you respond Yes, a copy of the FCS routines reside in a common area
in memory
(FCSRES). Tasks can then link to this resident library of
FCS routines rather than contain a copy of the FCS routines in their
task image. Tasks that use FCS and are linked to FCSRES are generally
smaller than tasks containing their own FCS routines. Therefore, they
task-build faster,
take up less disk space, and load faster.
In
addition, if you choose this option, SYSGEN optionally builds most
utilities to link to FCSRES (the introductory text in Chapter 7 lists
some of those utilities).
If you select this option,
SYSGEN
task-builds several privileged tasks during Phase II to link to
FCSRES.
Frequently, a highly overlaid task has FCS
FCSRES means fewer overlays in this case.

overlays.

Linking

If you have selected ANSLIB.OLB
(either by choosing ANSI magtape
support or by selecting ANSLIB for big buffering), Phase II of SYSGEN
builds FCSRES using ANSLIB.OLB.
If you are building a system with a relatively small amount of memory,
you may not want this option. The 6K FCSRES remains in memory.
This question appears only if you are generating a mapped RSX-llM
system and only if you selected the option for memory management
(PLAS) directives in the Question 7 Executive Options Section earlier
in Phase I.
This question does not appear for RSX-llS systems or if you did not
select FCP support in Question 2 of the Executive Options Section.
* 4.

Code for FCP (A/B/C/D/E, *prints table)

[D:

<default>]:

If you selected Files-11 ACP
(FCP)
support in Question 2 of the
Executive Options Section, SYSGEN displays this question to let you
select the version of FCP best suited to your application needs and
memory limits.
You may select from five FCPs. The first four versions of FCP (A,B,C,
and D) have the same functionality.
However, the performance of each
version differs greatly. Read the descriptions below carefully before
making your selection.
A.

MINIMUM (FCPMIN)
This version of FCP is not recommended for general use.
It
should be used only when size is critical.
It runs in 2K
words of memory and is heavily overlaid.
This version does not support buffer caching or other
performance optimization features. Furthermore, it does not
optimize directory operations.

4-57

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS {Cont.)
For example, an application running stand-alone that opens
large contiguous files and does no additional file I/O,
except for reading and writing to those files may get
adequate performance using the MINIMUM FCP.
The MINIMUM FCP is available
RSX-llM systems.

both

mapped

and

unmapped

Enter a response of A to choose this version of FCP.
B.

SMALL (FCPSML)
This version of FCP is heavily overlaid and supports limited
performance optimization features.
It runs in approximately
2.SK words of memory.
The SMALL FCP requires from 10 to 100 times more I/O for such
operations as looking for directories and opening files than
the larger versions of FCP. However, for many applications,
it provides satisfactory response.
Using a larger version of
FCP that results in more checkpointing or swapping may result
in
reduced
performance even in a program development
environment.
The SMALL FCP is available on both mapped and unmapped
RSX-llM systems.
The SMALL FCP is the default FCP for
unmapped RSX-llM systems.
Enter a response of B to choose this version of FCP.

MIDDLE (FCPMDL)
Most ACP I/0 requests require only a
few additional
I/O
operations
with this version of FCP.
The MIDDLE FCP
generally provides the best performance without using undue
amounts of memory.
The MIDDLE FCP provides buffering for caching of directories
and the bitmap, which significantly increases performance in
most cases.
The MIDDLE FCP provides additional buffer space
for about 20 open files and accessed directories, and,
therefore, minimizes the use of system pool. This FCP uses
approximately SK words of memory.
The MIDDLE FCP is available only on mapped RSX-llM systems.
The MIDDLE FCP is the default FCP for mapped RSX-llM systemsa
Enter a response of C to choose this FCP.

LARGE (FCPLRG)
This FCP provides the maximum performance.
It has no
overlays, thus it has no system overhead or I/0 overhead for
executing any code sequence. The LARGE FCP has the maximum
number of buffers for all operations
(such as creating,
extending, and deleting files, and directory operations)
as
well as a large directory buffer.
The large directory buffer
maximizes performance with large directories.
This version
also provides additional buffer space for about 20 open files
and accessed directories, minimizing the use of system pool.

4-58

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)
The LARGE FCP uses approximately lOK words of memory.
The LARGE FCP is available only on mapped RSX-llM systems.
Enter a response of D to choose this version of FllACP.
E.

OTHER
Enter a response of E to this question if you intend to
supply your own FCP. The following are general guidelines
for assembling, task-building, and installing your FCP in the
system image:
•

Following the completion of Phase I, assemble your FCP
using [11,lO]RSXMC.MAC (the Executive assembly prefix file
created by SYSGEN) and [l,l]EXEMC.MLB (the Executive macro
library) to produce FCP object file(s).

•

Task build your FCP in Phase II when SYSGEN pauses for
that purpose.
The FCP should be built using RSXllM.STB
(the Executive symbol table file) which can be found in
UIC
[1,54]
for mapped systems and [1,50] for unmapped
systems.

•

During Phase II, SYSGEN does not ask if you wish to edit
SYSVMR.CMD but instead automatically pauses to allow you
to edit SYSVMR.CMD. You must edit SYSVMR.CMD at that time
to include the command to install your FCP in the system
image.

For systems with several high-performance disks,
it is possible to
increase file system throughput by mounting each volume with a
separate FCP. Distinct FCPs allow a separate pool of FCBs
(File
Control Blocks)
for each disk volume in each FCP partition and allow
overlapping directory requests on each volume.
The FCP default name algorithm of
specifying separate FCPs
(see the
Manual).

the MOUNT command
RSX-llM/M-PLUS MCR

simplifies
Operations

It is recommended that the file system FCP 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 an FCP, and, while this I/O operation is in
progress, the tasks cannot be checkpointed.
Thus, if the FCP 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.

* 5.

Build Post Mortem Dump (PMD)?

[Y/N]:

This option lets you specify whether or not you want to have the Post
Mortem Dump (PMD) task-built during Phase II. The RSX-llM/M-PLUS Task
Builder Manual describes the PMD task.
This question does not appear for RSX-llS systems.

4-59

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)
* 6.

Build the Resource Monitoring Display task (RMD)?

[Y/N]:

This option lets you specify whether or not you want RMD task-built
during Phase II.
If you select this option and if you did not
previously select support for Asynchronous System Traps
(Question 17
in
the
Executive Options Section), unsolicited terminal
input
character AST (Question 6 in the Terminal Driver Options Section), and
Get Multiple Terminal Characteristics
(Question 11 of the Terminal
Driver Options Section), SYSGEN forces support for them at this time.
See the RSX-llM/M-PLUS System Management Guide for details on RMD.
This question does not appear for RSX-llS systems.

* 7.

Build the non-queue manager print spooler (PRT)?

[Y/N]:

If you did not select support for the queue manager in Question 35 of
the Executive Options Section, this option permits you to build the
serial despooler. See the RSX-llM/M-PLUS System Management Guide for
details on the nonqueue manager print spooler.
This question does not appear for RSX-llS systems.

* 8.

Do you want DIGITAL Command Language (DCL)?

[Y/N]:

DCL is an alternate CLI
(Command Line Interpreter)
supplied by
DIGITAL.
It is a user-oriented command language.
Refer to the
RSX-llM/M-PLUS Command Language Manual for further information on DCL.
If you have not previously included the following options in your
target system, SYSGEN automatically includes them when you respond Yes
to this question:
•

Install, request, and remove
Executive Options Section)

•

Asynchronous System
Options Section)

(Question

the

Executive

•

Get Task Parameters directive (Question 37
Options Section)

the

Executive

•

The Parent Offspring Tasking with Chaining (Question 37 of the
Executive Options Section)

•

The Stop Bit directive (Question 37 of the
Section)

•

The Specify Requested Exit AST (Question 37 of
Options Section)

Traps

exit

(Question

Executive
the

the

Options
Executive

This option is not available for RSX-llS, unmapped systems, or RSX-llM
systems without multiuser protection.

4-60

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)
* 9.

Enter the number of user-written CLis [D R:<O-MAX> D:O]:

A CLI
(Command Line Interpreter)
is a task that receives all
unsolicited input from user terminals. The function of a CLI is to
interpret and execute the unsolicited input as commands. The commands
are predefined by the CLI.
(MCR is the system CLI on RSX-llM.)
If you select this option, SYSGEN provides you with the necessary
Executive support for alternate CLis. Refer to the RSX-llM/M-PLUS
System Management Guide for details on writing a CLI.
The maximum number of CLis supported
(in any combination)
is 16.
Therefore, the maximum number of user-written CLis (<max>) is 16 minus
the number of CLis currently in the target system (where MCR, DCL, and
DECnet are CLis).
MCR (the system CLI) is always present on RSX-llM systems.
DECnet,
though it is included as one of the possible CLis, does not require
alternate CLI support. DCL, an alternate CLI supplied by DIGITAL,
does require alternate CLI support.
If you select DCL as an option,
SYSGEN automatically includes alternate CLI support.
Alternate CLI support is not available for RSX-llS, unmapped
or RSX-llM systems without multiuser protection.

* 10.

systems,

Do you want pool monitoring and low pool recovery (PMT)?

[Y/N]:

If you respond Yes to this question, SYSGEN includes the Pool Monitor
Task
(PMT) in your target system. PMT is a lK- to 2K-word privileged
task that runs at least once a minute to monitor pool fragmentation.
In addition, this option includes code in the Executive that monitors
the size of pool and notifies PMT whenever a significant change in the
pool size occurs.
PMT enables checkpointing for itself whenever it detects a normal pool
condition and disables checkpointing when pool is low or the largest
pool fragment is smaller than the size of the CLI buffer. The latter
guarantees that pool resources are always available for the PMT task
to execute.
Whenever either the Executive or PMT determines that pool resources
are low, PMT issues a warning to logged-on terminals that pool is low
and requests that users on the system exit from their active tasks.
In addition, PMT displays specific information at the console terminal
about the amount of free pool space and the size of the largest pool
fragment.
If PMT detects extreme pool fragmentation (that is, if the largest
pool fragment is less than the size of the CLI command buffer), PMT
also displays on the console terminal a list of abortable tasks in
memory and requests that the system manager abort one or more of them.
The SET /PLCTL command (described in the RSX-llM/M-PLUS MCR Operations
Manual) allows you to control pool limit parameters. For more details
on PMT, see the RSX-llM/M-PLUS System Management Guide.

4-61

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)
If you select this option and have not selected support for AST,
Cancel Selective Marktimes, system-controlled partitions, and Specify
Requested Exit AST (Questions 17, 18, 33,
and
37 of the Executive
Options Section), SYSGEN forces support for them at this time.
This option is only available for mapped RSX-llM systems.

* 11.

What name would you like to give your system?

[D:

<default>]:

This option allows you to assign a name to your system to distinguish
it from other RSX-llM systems you may have.
The following tasks all
make use of the system name:
BRO
BYE

HEL
PMT

RMD
SHUTUP

The name must be from one through six alphanumeric characters. A name
with less than six characters is padded to the right with spaces.
The default response for RSX-llM systems is RSXllM.
The default response for RSX-llS systems is RSXllS.

* 12.

Do you want SPM-11 support [Y/N]:

the
Software
If you respond Yes,
SYSGEN includes support for
Ref er to your
Performance Monitor
(SPM-llM)
for
RSX-llM systems.
SPM-llM documentation for details.
To include SPM-llM support, you must have the following hardware:
•

Mapped system

Expansion space for the KWll-P
with the SPM-llM package

•

Extended Instruction Set

programmable

clock

provided

(EIS)

If you have not previously included the following options
in your
target system, SYSGEN automatically includes them when you respond Yes
to this question:
Traps

(Question

,l.. ...! ;

Executive

Options

•

Asynchronous System
Section)

•

The Get Task Parameters
Options Section)

•

The Extend Task
Section)

•

The Get Partition Parameters directive (Question 37, Executive
Options Section)

directive

(Question

4-62

(Question
37,

37,

Executive

Options

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)

•

The Send/Receive directive
Section)

•

Checkpointing to a system
Executive Options Section)

(Question

37,

checkpoint

Executive
file

Options

(Question

50,

It is recommended that you have memory management
(PLAS)
support
(Question 7 of the Executive Options Section) for SPM-llM. Without
PLAS support, SPM-llM buffering is limited to 4K words, and overflows
may occur during data collection resulting in a loss of data. With
PLAS support, SPM-llM buffers can be allocated up to 32K words.
However, if you choose not to include PLAS support, but you still want
SPM-llM support, the following message will appear:
Because PLAS was not included,
the Data Collection (COL) task's buffer will
be limited to 4K word static common.
This question does not appear for RSX-llS systems,
or systems without EIS support.

4-63

unmapped

systems,

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS
4.8

PERIPHERAL OPTIONS SECTION

This section of questions describes the peripheral devices.
To make
references to specific device questions easier, the questions in this
section are listed by the device mnemonic in alphabetical order,
rather than by question numbers.
Your responses to 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 Question 15 of the
Target Configuration Section.
Enter the device-dependent parameters
which
define
addressing
information as well as special attributes for the peripheral devices.
SYSGEN displays a prompt line describing the required parameters and
then a specific device question, which includes any default values for
the parameters.
(See Example 4-1 at the end of this chapter for
typical SYSGEN prompts and questions for
the Peripheral Options
Section.)
For example, if you selected loadable driver support, the general form
of a SYSGEN prompt is:

* Enter

[L/R,] parameter!, parameter2, ••• parametern for:

where:
L/R

An optional parameter that specifies whether the driver
is
loadable
(L) or resident (R).
Note that you specified the
default value for
this parameter
in your response to
Questions 15 and 16 of the Executive Options Section.
To
have loadable driver support, you must answer Yes to
Executive Options Question 15. The default for loadable or
resident drivers (in the Peripheral Options Questions)
is
based on your
response to Question 16 in the Executive
Options Section.
If you do not, however,
seiect loadable
driver support (that is, if you answer No to Question 15 in
the Executive Options Section), all drivers for your target
system are resident and you cannot override that default in
this section.
The process control drivers
(UDC,
ICS/ICR, 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 residentc
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 L or an R),
you
must terminate this parameter with a comma (,), even if it
is the only parameter on the line.

parameter

A device-dependent parameter such as CSR or vector address.

4-64

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
If you did not select loadable driver support, the general form
SYSGEN prompt is:

Enter parameter!, 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 parentheses (()) 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 presents them on the same SYSGEN prompt
line.
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 parameter value.
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 checks 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 enter 300 as the CSR address
for a CRll controller SYSGEN displays:
SGN -- Parameter (#2)

"300" out of range 160000 to 177700

RETRY

and then repeats the question.
The number in parentheses is the
parameter count (excluding L/R if applicable) and the value in quotes
is the invalid parameter.
CAUTION

When you enter a numeric value, do not
include a period (to specify a decimal
number) or a pound sign (to specify an
octal number).
This causes an error;
SYSGEN
attempts
to
validate
your
response and does not permit explicit
decimal or octal entries.
Enter
numeric
values
within
the
acceptable range.
SYSGEN interprets the
response to be octal or decimal as
required.
Refer to the description accompanying
each question if you are unsure of the
base for a specific numeric response.

4-65

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
The following
is a detailed description of all the peripheral
questions.
All CSR and vector addresses are octal values. All other
values to be input are appropriately defined as octal or decimal.

* AD controller 0

(0:176770]

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 ADOl-D analog-to-digital converter is a noninterrupt
Therefore, you do not enter an interrupt vector address.

device.

The acceptable range for the number
64(10).

through

A/D

If you do not enter the default value for
acceptable range is 160000 through 177700.

channels

the

address,

CSR

There is no default CSR address for subsequent ADOl-D
you must enter a value within the acceptable range.

the

controllers;

* 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 for the number
1024(10).

A/D

channels

through

If you do not enter the default values for the vector and CSR
assignments, the acceptable range is 60 through 774 for the vector and
160000 through 177700 for the CSR.
There is no default CSR address for subsequent AFCll controllers; you
must enter a value, within the acceptable range, for the vector and
CSR addresses as well as the number of A/D channels.
*AR controller 0 [D:,170400,,,,,170420]
The clock vector address for the ARll controller is assigned from the
floating vector space starting at location 300(8).
It is located at
an offset of four 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(8).
Consult your
DIGITAL Field Service Representative if the clock vector address is
unknown.

4-66

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
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 through 177700.
The polarity mask word specifies whether an individual channel is
unipolar or bipolar;
it corresponds one-to-one with the 16 possible
channels.
A 1-bit designates a unipolar channel and a
0-bit
designates a bi-polar channel. The acceptable range for the polarity
mask word is 0 through 177777(8) (0 specifies 16 bi-polar channels,
177777 specifies 16 unipolar 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 D/A support
enter NO for parameter 4; the driver will be significantly smaller.
The maximum number of samples must be evenly divisible into 10,000 and
within the acceptable range of 1 through 2500(10).
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 by using the DRll-K.
If the DRll-K is present, enter
DRK in your response string just prior to the CSR address of the
DRll-K; otherwise, enter NO as the last parameter in your response.
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
CSB 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 through 177700.
Subsequent ARll controllers default only the CSR address of the DRll-K
option; you must enter the other values within the acceptable ranges.
Also, if subsequent ARll controllers do not include the DRll-K option,
you must exclude this parameter.

* 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 through 774 for the vector and
160000 through 177700 for the CSR.
There is no
controllers;

default CSR or vector address for subsequent CRll
you must enter values within the acceptable ranges.

* CT controller 0 [0:260,177500]
Enter the interrupt vector address (the default value is 260) and the
CSR address (the default value is 177500) for the first TAll cassette
controller.

4-67

DETAILS OF SYSGEN PHASE I

default CSR or vector address for subsequent TAll
you must enter values within the acceptable ranges.

* DB controller 0 [D: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, for 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 center line 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 read.
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
through 8(10).
If you do not use the default values, the acceptable ranges are:
Vector
CSR
Number of drives
Unit number of first drive
Off set recovery

60 through 774(8)
160000 through 177700(8)
1 through 8(10)
0 through 7(10)
0 or NO

Subsequent RHll or RH70 controllers default only the
the first drive (0).

unit

number

NOTE
You can only specify offset recovery
.C
support for the first DB controller.
.L.L
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.
T

After you enter the parameters for each RHll or RH70 controller
included in your system, SYSGEN immediately prompts for the drive
type.

4-68

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
* DB Contr 0 unit 0 is an RP04/05/RP06 [D:RP06]
This question immediately follows parameter specification for each DB
controller. You must specify the type of drive. Enter RP04, RPOS, or
RP06 (the default response).
SYSGEN repeats this question for each device unit specified
controller.

for

each

* DD controller O [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
controller.
The acceptable range for the number of DECtape II drives is 1

through

2 (10) •

* DF controller O [D:204,177460]
Enter the interrupt vector address (the default value is 204) and the
CSR address (the default value is 177460) for the first RFll
controller.
If you do not enter the default values for the vector and CSR
assignments, the acceptable range is 60 through 774 for the vector and
160000 through 177700 for the CSR.
There is no
controllers;

default CSR or vector address for subsequent RFll
you must enter values within the acceptable ranges.

* DK controller O [D:220,177404]
Enter the interrupt vector address (the default value is 220), the CSR
address (the default value is 177404), and the number of RKOS drives
(there is no default value for this parameter) for the first RKll
controller.
The CSR for the DK device is not the first register in the DK register
set.
The default CSR address displayed with this question is the
actual CSR address for this device.

4-69

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
The acceptable for the number of RKOS drives is 1 through 8(10}.
NOTE
An RKOSF is a fixed media RKOS drive
equivalent to two removable RKOS drives.
Specify every RKOSF as two RKOSs.
If you do not enter the default vector and CSR assignments, the
acceptable range is 60 through 774 for the vector and 160000 through
177700 for the CSR.

* DL controller 0

(0:160,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/RLVll (for RLOls) or RL21/RLV21/RLV12 (for RL02s) controller.
The acceptable range for the
through 4(10}.

number

RLOl/02

disk

drives

* OL Contr 0 unit o.

is an RL01/RL02 [O:RLOl]

This question immediately follows parameter specification for each DL
controller.
You must specify the type of drive. Enter either RLOl
(the default response) or RL02.
SYSGEN repeats this question for each device unit specified
controller.

for

each

* OM controller 0 (0:210,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 O is to
include offset recovery support) for the first RK611 controller.
The acceptable range for the number of RK06/07
8(10}.

4-70

drives

through

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)
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 center line 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 through 774 for the vector and 160000 through
177700 for the CSR.
There is no default CSR or vector address for subsequent RK611
controllers; you must enter values, within the acceptable ranges, for
the vector and CSR assignments as well as the number of RK06/07
drives.
NOTE
You can only specify offset recovery
support for the first controller.
If
you include support for the first RK611
controller, you automatically include
off set recovery support for subsequent
controllers.
Likewise, if you exclude
support, you exclude offset recovery
support
for
subsequent
RK611
controllers.

* OM Contr 0 unit o.

is an RK06/RK07 [D:RK06]

This question immediately follows parameter specification for each DM
controller.
You must specify the type of drive. Enter either RK06
(the default response) or RKO?.
SYSGEN repeats this question for each device unit specified
controller.

for

each

* DP controller 0 [D:254,176714]
Enter the interrupt vector address (the default value is 254), the CSR
addr ?ss
(the default value is 176714), and the number of RP02/03 disk
drives (there is no default for this parameter)
for the first RPll
0

con'~roller.

The CSR for the DP device is not the first register in the DP register
set.
The default CSR address displayed with this question is the
actual CSR address for this device.
The acceptable range for the
through 8 (10).

number

RP02/03

disk

drives

If you do not enter the default values for the vector and CSR
assignments, the acceptable range is 60 through 774 for the vector and
160000 through 177700 for the CSR.

4-71

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
There is no default CSR or vector address for subsequent RPll
controllers; you must enter values, within the acceptable ranges, for
the vector and CSR assignments as well as the number of RP02/03
drives.

* DP Contr 0 unit O.

is an RP02/RP03 [D:RP03]

This question immediately follows parameter specification for each DP
controller. You must specify the type of drive. Enter either RP02 or
RP03 (the default response).
SYSGEN repeats this question for each device unit specified
controller.

for

each

* DR controller 0 [D:254,176700,,0,0]
Enter the interrupt vector address
(the default is 254), the CSR
address
(the default is 176700), the number of RM02/03/05/80/RP07
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, for 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 center line 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 read.
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
through 8(10).
If you do not use the default values, the acceptable ranges are:
Vector
CSR
Number of drives
Unit number of first drive
Off set recovery

60 through 774(8)
160000 through 177700(8)
1 through 8(10)
0 through 7(10)
o or NO

Subsequent RHll or RH70 controllers default only the
the first drive (0).

unit

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.
4-72

number

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
* DR Contr 0 unit O.

is an RM02/03/05/80/RP07 [D:RM03]

This question immediately follows parameter specification for each DR
controller.
You must specify the type of drive. Enter either RM02,
RM03 (the default response), RM05, RM80, or RP07.
SYSGEN repeats this question for each device unit specified
controller.

for

each

* OS controller 0 [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
physical unit number of the first RS03/04 drive (the default value is
0) for the first RHll or RH70 controller.
The acceptable range for the number of RS03/04
8 ( 10) •

drives

through

If you do not use the default values, the acceptable ranges are:
Vector
CSR
Number of drives
Unit number of first drive

60 through 774(8)
160000 through 177700(8)
1 through 8(10)
0 through 7(10)

Subsequent RHll or RH70 controllers default only the
the first drive (0).

* OS Contr 0 unit O.

unit

number

is an RS03/RS04 [D:RS04]

This question immediately follows parameter specification for each OS
controller. You must specify the type of drive. Enter either RS03 or
RS04 (the default response).
SYSGEN repeats this question for each device unit specified
controller.

for

each

* OT controller O [0:214,177342]
Enter the interrupt vector address (the default value is 214), the CSR
address
(the default value is 177342), and the number of DECtape
drives (there is no default for this parameter)
for the first TU56
controller.
The CSR for the OT device is not the first register in the OT register
set.
The default CSR address displayed with this question is the
actual CSR address for this device.

4-73

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
The acceptable range for the number of DECtape
8 ( 10) •

drives

through

If you do not enter the default values for the vector and CSR
assignments, the acceptable range is 60 through 774 for the vector and
160000 through 177700 for the CSR.
Subsequent TU56 controllers do not default the vector and CSR
assignments.
You must enter a value within the acceptable ranges for
the vector and CSR assignments, as well as the number of drives.

* DU contr 0 [D:l54,172150,,4,4]
Enter the interrupt vector address (the default value is 154), the CSR
address
(the default value is 172150), the number of DU:-type
(RA60/80/81/RC25/RD51/RX50) disk drives (there is no default value for
this parameter), the number of command rings (the default value is 4),
and the number of response rings (the default value is 4).
The acceptable range for the number
controller is 1 through 4(10).

DU:-type

drives

for

each

An RC25 is both a fixed-media and a removable-media disk drive;
therefore, each RC25 is equivalent to two units. When you specify the
number of DU:-type devices, count two units for each RC25 disk drive.
It is recommended that you use extreme care if the RC25 is your system
device.
Because the RC25 is both a fixed-media and removable-media
disk drive, it is unlike other disk drives used as system disks.
For
example, if you want to spin down the removable disk to replace it
with another disk pack, the fixed-media disk
(possibly your system
disk)
has to be stopped as well. Doing so could seriously disrupt
system activities.
Before you replace the removable-media disk, you must ensure that all
I/O activity
(system and user) has stopped on the fixed media disk.
Both the system and the system's users cannot access files at this
time.
Also, all read and write operations to the drive result in
errors. For example, if you have a checkpoint file on the fixed unit
and you spin down the removable unit, you must be sure that the system
does not attempt to do a checkpoint read or a checkpoint write.
The
attempted checkpoint read results in a checkpoint read failure and the
task is aborted. The attempted checkpoint write results in both error
messages on the console and the checkpoint operation being terminated.
For RD51/RX50 configurations, a DU controller can accept up to 4
RD51/RX50 units;
however, SYSGEN does not accept an answer of less
than 3 units (one RD51 fixed media disk drive and two RX50 floppy disk
drives).
If you respond either 1 or 2 units, SYSGEN forces 3 units
into the system.

4-74

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
NOTE
An RD51/RX50 configuration requires one
dedicated DU controller.
No other DU
devices (for example, an RA81) can be on
that
controllere
Also,
only
two
RD51/RX50 configurations are allowed per
system.
If you do not enter the default values for the vector and CSR
assignments, the acceptable range is 60 through 774 for the vector and
160000 through 177700 for the CSR.
There is no default CSR or vector address for subsequent UDA
controllers; you must enter values, within the acceptable ranges, for
the vector and CSR assignment as well as the number of UDA drives on
that controller.
To understand the choice of a command ring size and a
size, carefully read through the following discussion.

response

ring

The software and hardware interface between drivers and controllers is
referred to as the port. The RSX-llM operating system is the host.
The port works as a set of data structures in host memory.
and disk controller use that set of data structures.

The

host

The actual transmission of commands and responses is effected by the
port through NPR transfers from and to a communication region in host
memory: the port polls this region for commands; the host polls it
for responses.
From the viewpoint of the host, an I/O operation
begins when the host deposits a command in the command queue;
the
operation is seen as complete when the corresponding response packet
is removed by the host from the response queue.
The communications area consists of two sections:
•

A header area containing interrupt identification words.

•

A variable-length section containing the response and
queues, organized into rings.

command

Note that the more command and response rings you select, the more I/O
requests the host can have outstanding to the disk controller. This
potentially increases the I/O speed by taking greater advantage of the
disk's optimization techniques.
However, increasing the number of
rings uses more of the driver's private buffer pool.
The communications area is aligned on a 16-bit word boundary.
The
communications area requires a minimum of 12(10) bytes of storage
allocated from the device driver's private buffer pool.
Additional
ring entries require 4 additional bytes of storage each.
Each ring entry points to a message packet, also contained _in the
device driver~s private buffer pool. Each response message packet
requires 60(10) bytes of storage while each command message packet
- - - ..... ..: _ _ ,...

~c~u~~c~

C') , ,

1'\

J~\•V/

\....TT ............ i!"I
u~~~~

,...../!
v~

I!:!' ..... ,.... ... ~,.~

~~v~g~;·

4-75

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
The acceptable range for both the number of command rings and response
rings is 1 through 8(10). A value of 3 is accepted; however, SYSGEN
rounds this entry to 4. A value of 5 through 7 is accepted; however,
SYSGEN rounds any of these entries to 8.
The default values require a total of 484(10)
bytes of
controller from the device driver's private buffer pool.

* DU contr 0 unit O.

storage

per

is an RA60/80/81/RC25/RD51/RX50 [D:RA81]

This question immediately follows parameter specifications for each DU
controller.
You must specify the type of drive.
Enter RAGO, RASO,
RA81, RC25, RD51, or RXSO.
If you specify unit 0 as a RD51 or RXSO, you can specify units
and 3 on that controller only as either RD5ls or RX50s.

If you specify unit 0 as a DU device other than the RD51 and RXSO,
RD51 and RX50 are excluded from your choices for units 1, 2, and 3 on
that controller.
SYSGEN repeats this question for each device unit specified
controller.

for

each

* 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.
The acceptable range for the number of RXOl floppy disk drives is 1 or
2 ( 10) •
If you do not enter the default values for the vector and CSR
assignments, the acceptable range is 60 through 774 for the vector and
160000 through 177700 for the CSR.
There is no default CSR or vector address for subsequent RXll
controllers; you must enter values, within the acceptable ranges, for
the vector and CSR assignments as well as the number of RXOl floppy

disk drives.

* 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/RXV21/RXV12 controller.
The acceptable range for the number of RX02 floppy disk drives is 1 or
2 ( 10) •

4-76

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
If you do not enter the default values for the vector and CSR
assignments, the acceptable range is 60 through 774 for the vector and
160000 through 177700 for the CSR.
There is no default CSR
or
vector
address
for
subsequent
RX211/RXV21/RXV12 controllers;
you must enter values, within the
acceptable ranges, for the vector and CSR assignments as well as the
number of RX02 floppy disk drives.

* EM controller 0 [D:

,176400]

Enter the interrupt vector address
(there is no default for the
interrupt vector), the CSR address (the default address is 176400),
and the number of MLll disk drives
(there is no default for this
parameter) •
If you do not use the default values, the
follows:
Vector
CSR
Number of MLll drives

acceptable

ranges

are

60 through 744(8)
160000 through 177700(8)
1 through 8(10)

*GR controller 0 [D:,172000,,l]
RSX-llM supports the graphics display
restrictions:

subsystem

with

the

following

•

One, and only one, VTll or VS60 in the system

•

The graphics display driver does not operate on any 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 graphics display driver is always resident.

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 in the range 300 through 774. Consult your DIGITAL Field
Service Representative 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 is 1).
If you do not enter the default CSR address and the number of CRT
monitors, the acceptable range is 160000 through 177700 for the CSR
and 1 through 2 for the number of CRT monitors.

4-77

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
NOTE
Only the VS60 can drive two CRT monitors
independently.
Thus, if your system
includes the VTll, you must specify the
default value of 1, for the number of
CRT monitors.

* LA controller 0

(0: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 UNIBUS 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 concurrently
active LPAll-K I/O transfers.
If the processor does not have extended
memory, the default for this parameter is O.
If the processor does
have extended memory, but the system does not include support for the
20K-word Executive, the default for this parameter is 4;
otherwise,
the default is 5. See the RSX-llM/M-PLUS I/O Drivers Reference Manual
for details.
-There is no default CSR or vector address for subsequent
LA
controllers;
you must enter values within the acceptable ranges for
the vector and CSR addresses as well as the number of UNIBUS mapping
registers for the LPAll-K.
NOTE
The vector address
is assigned from
floating vector space.
Consult your
DIGITAL Field Service Representative if
the location is unknown.
Also, the
required CSR address is that of the
first word of the LPAll CSR group.
If you include a LA device in your system, SYSGEN automatically
includes support for the Send/Receive directive (Question 37, Code C,
Executive Options Section).
See Section 4.8.1 for the IC and IS Subsystems questions
4.8.2 for IP Subsystems questions.

* LP controller 0

and

Section

[D:200,177514,LA180,0,300,160130]

Enter the interrupt vector address (the default value is 200), the CSR
address default value is 177514)
and the controller option (the
default option is LA180) for the first line printer controller. Valid
controller options are described in Table 4-3.

4-78

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)
Table 4-3
Standard Line Printer Devices

Option

Printer 1

Column
Width

Character
Set

LPll-A

LP25-A

132

285

LPll-B

LP25-B

132

204

LPll-C

LP14-C

132

890

LPll-D

LP14-D

132

650

LPll-E

LP26-E

132

420-600

LPll-F

LPOl-F

170-1110

LPll-G

LP07-G

132

1200

LPll-H

LPOl-H

170-1110

LPll-J

LP02-J

132

170-1110

LPll-K

LP02-K

132

170-1110

LPll-R

LP04-R

132

1110

LPll-S

LP04-S

132

1110

LPll-U

LP27-U

132

800-1200

LPll-V

LPOS-V

132

300

LPll-W

LP05-W

132

300

LPll-Y

LP06-Y

132

600

LPll-Z

LP06-Z

132

460

LNOl

132

12 pages

LSll

132

60-200

LVll

LVOl

132

500

LA180

132

150

1. You can connect a maximum of
system.

4-79

eight

line

Lines per
Minute

printers

the

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
For printer widths and speed,
consult your DIGITAL
Representative or the PDP-11 Peripherals Handbook.

Field

Service

The LPll-F and LPll-H printer options have a column width of only 80
chracters.
These printer options only print the first 80 characters
of a print line.
The LPll-A, -C, -F, -J, -R, -V, -Y, and LSll printer options may not
print lowercase characters.
If they do not, lowercase characters are
printed as spaces.
If your target system configuration includes an LPll-A,
-B,
-C,
-D,
-E,
-V,
-w, -Y, -Z, LSll, or LA180 printer option, but you did not
specify that particular printer option, a print line may be lost
(not
printed) when the line printer is turned off line.
If your target system configuration includes an LPll-F, -H, -J, -K,
-R,
-S or LVll, but you did not specify that particular printer
option, a file may take about 25 percent longer to print than if you
specify the correct printer option.
If your system includes KMC line printer support, you must enter the
KMC time-out 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 time-out count specifies the interval in which the KMC polls the
line printer between printed lines.
This value is measured in units
of 50 microseconds. For example, if you enter 1, the KMC polls the
line printer every 100 microseconds (as each print buffer empties).
The acceptable range is 0 through 100(10). For slower printers, poll
less frequently
(enter a higher number);
the polling interval
increases or decreases UNIBUS latency.
The acceptable range for
the KMC interrupt vector address is 60
through 774 and the range for the KMC CSR address is 160000 through
177700, both in octal.
NOTE
If you select KMC
must use the KMC;
the KMC cannot
respecify
KMC
additional
line
question asked by

* LS controller o

support, all printers
those that do not use
operate.
You
must
parameters
for each
printer
controller
SYSGEN.

[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 in the range 300 through 774.
Consult your DIGITAL Field
Service Representative if the clock vector address is unknown.

4-80

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)
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 through 177700.
The next parameter is the number of A/D channels; enter a value in
the range 1 through 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 bandwidth filter channel select delay (if required).
The polarity mask word specifies whether an individual channel
is
unipolar or bipolar;
it corresponds one-to-one with the 16 possible
channels.
A 1-bit designates a
unipolar channel and a
0-bit
designates a bipolar channel.
The acceptable range for the polarity
mask word is 0 through 177777 (0 specifies 16 bipolar channels, 177777
specifies 16 unipolar channels).
With bandwidth 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 microseconds to 8.5
milliseconds.
Consult the LPSll documentation to determine the proper
delay for your application.
Note that the response must be in 100
microsecond units (for example, specify 25 to delay 2.5 milliseconds).
The acceptable range is 0 through 85.
Enter 0 to disable bandwidth
filtering.
If your system includes the D/A option, enter the number of channels
in the range 0 through 10(10).
A response of 0 (the default)
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.
The LPSll supports a digital I/O and relay module.
You must specify
whether or not the option is present.
If the digital I/0 and relay
module is present, enter D;
otherwise enter No.
You then enter the
maximum number of samples per second.
The acceptable range is 1
through 2500(10).
Note that this value must be a factor 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).

* MF controller O [0:260,175400]
Enter the interrupt vector address (the default value is 260), the CSR
address (the default value is 175400), and the number of TU78 magnetic
tape drives (there is no default for this parameter)
for the first
TM78 tape controller.
If you do not use the default values, the
follows:
Vector
CSR
Number of TU78 drives

acceptable

ranges

are

60 through 774(8)
160000 through 177700(8)
1 through 4(10)

4-81

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
Subsequent MF controllers do not have default CSR and
vector
assignments. You must enter the vector and CSR assignments within the
acceptable range as well as the number of drives.

* MF controller 0 unit 0 formatter

[D R:0-7 D:O]

Each MF controller supports up to eight TM78 formatters.
Each TM78
formatter supports up to four units. When you specify the number of
units in the preceding question, SYSGEN asks this question to
determine which TM78 formatters connect to which units (drives).
This question immediately follows parameter specification for each MF
controller.
You must identify TM78 formatter number. The default is
O.
If you do not use the default response, the acceptable range is 0
through 7(10).
SYSGEN repeats this question for each device unit specified
controller.

for

each

* MM controller 0 [0:224,172440)
Enter the interrupt vector address (the default value is 224), the
Command Register 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.
The acceptable range for the number of tape drives is 1 through 8.
If you do not enter the default vector and CSR assignments, the
acceptable range is 60 through 774 for the vector and 160000 through
177700 for the CSR.
There is no default CSR or vector address for subsequent controllers;
you must enter values, within the acceptable ranges, for the vector
and CSR assignments as well as the number of tape drives.

* MM controller 0 unit 0 formatter [D R:0-7 D:O]
Each MM controller supports up to 8 formatters.
Each TM02/03
formatter supports up to 8 units
(except for TU77 drives, which
support up through four drives). When you specify the number of units
in the preceding question, SYSGEN asks this question to determine
which TM02/03 formatters connect to which units (drives).
This question immediately follows parameter specification for each MM
controller.
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
O through 7(10) or 0 through 3(10) for TU77 drives.

4-82

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
SYSGEN repeats this question for each device unit specified
controller.

for

each

* 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.
The CSR for the MS device is not the first register in the MS register
set.
The default CSR address displayed with this question is the
actual CSR address for this device.
I f you do not
enter the default values for the vector and CSR
assignments, the acceptable range is 60 through 774 for the vector and
160000 through 177700 for the CSR.

Subsequent TSll controllers do not default the vector and
assignments; you must enter a value within the acceptable range.

CSR

The TSll, TSV05, and TU80 magtape drives are valid MS:-type devices.

* MT controller 0

[0:224,172522]

Enter the interrupt vector address (the default value is 224), the
Command Register address (the default value is 172522), and the number
of TS03, TUlO, or TElO magtape ar1ves (there is no default for this
parameter) for the first TMll, TMAll, or TMBll controller.
The CSR for the MT device is not the first register in the MT register
set.
The default CSR address displayed with this question is the
actual CSR address for this device.
The acceptable range for the number of tape drives is 1 through 8(10).
If you do not enter the default values for the vector and CSR
assignments, the acceptable range is 60 through 774 for the vector and
160000 through 177700 for the CSR, both in octal.
There is no default command register or vector address for subsequent
MT controllers; you must enter values, within the acceptable ranges,
for the vector and CSR assignments as well as the number of tape
drives.

* PP controller 0

[0: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.
The CSR for the PP device is not the first register in the PP register
set.
The default CSR address displayed with this question is the
actual CSR address for this device.

4-83

DETAILS OF SYSGER PHASE I

PERIPHERAL OPTIONS (Cont.)
If you do not enter the default values for the vector and CSR
assignments, the acceptable range is 60 through 774 for the vector and
160000 through 177700 for the CSR, both in octal.
Subsequent PCll controllers do not default the vector and
assignments; you must enter values within the acceptable ranges.

* PR controller 0

CSR

(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 through 774 for the vector and
160000 through 177700 for the CSR, both in octal.
Subsequent PCll/PRll controllers do not default vector and
assignments; you must enter a value within the acceptable range.

* uo controller 0

CSR

[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 through 774 for the vector and
160000 through 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.
For clarity, this section lists the prompt lines in numeric order, not
in logical sequence. If you were performing ~ SYSGEN and included a
UDCll controller, the questions for UDCll would follow the vector and
CSR assignments.
The UDCll supports up to 252(10) modules, which can be classified into
seven types:

• Analog input
• Analog output
• Bi-stable output
• Digital interrupt
• Digital sense
• I/O counter
• Single-shot output

4-84

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
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.
You must enter the number of each module contained in the UDCll and
identify the first slot for that module.
The permissible range for
each entry is 0 through 252(10).
Note, however,
that
SYSGEN
decrements the range value for the number of 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) •
SYSGEN asks
boundaries.

the

following

questions

establish

UDCll

module

• UD controller 0 ADUOl analog input module
• UD controller 0 analog output module
• UD controller 0 bi-stable output module
• UD controller 0 digital interrupt module
• UD controller 0 digital sense module
• UD controller 0 I/O counter module

• UD controller 0 single-shot output module
* XB controller 0 [0:124,172414]
Enter the interrupt vector address
CSR address
(the default value
interface.

(the default value is 124) and the
is 172414)
for
the first DAll-B

If you do not enter the default for the vector and CSR assignments,
the acceptable range is 60 through 774 for the vector and 160000
through 177700 for the CSR, both in octal.
Subsequent DAll-B interfaces do not default the vector and
assignments;
you must enter values within the acceptable ranges.

CSR

*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
in the range 300 through 774.
Consult your DIGITAL Field Service
Representative if the vector address is unknown.

4-85

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
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 in the
range 175610 through 177700.
Refer to Appendix E or consult your
DIGITAL Field Service Representative if the CSR address is unknown.
The first DLll-E line defaults to a half-duplex line (H).
specify a full-duplex line.

Enter F

There is no default value for the parameter that specifies the
required number of synchronous characters in a synchronous leader.
You must enter a value in the range 3 through 14(10).
A typical
response is 4 through 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
synchronous characters.
There are no default parameters for subsequent DLll-E lines;
enter values for the vector and CSR assignments.

you must

* 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 in the
range
300
through
774.
Consult your DIGITAL Field Service
Representative 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 in the range 160010
through 177700. Consult your DIGITAL Field Service Representative if
the CSR address is unknown or see Appendix E.
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 F to indicate that the line is full-duplex, an H to
indicate that the line is a secondary station half-duplex, or P to
indicate that the line is a primary station half-duplex.

* 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
in the range 300 through 774. Consult your DIGITAL Field Service
Representative if the vector address is unknown or see Appendix E.
The standard CSR assignment for the DPll is 174770.
If you do not
enter the default CSR address, enter a value in the range 160000
through 177700 octal.
The first DPll line defaults to a half-duplex line (H).
specify a full-duplex line.

4-86

Enter

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
There is no default value for the parameter that specifies the
required number of synchronous characters in a synchronous leader.
You must enter a value in the range 3 through 14(10).
A typical
response is 4 through 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
synchronous characters.
Subsequent DPll lines default only the half-duplex parameter (H);
must enter values for the vector and CSR assignments.

you

* XQ controller O [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
default vector address for the DQll. Enter a vector address in the
range
300
through
774.
Consult your DIGITAL Field Service
Representative if the vector address is unknown or see Appendix E.
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 in the range
160010
through
177700.
Consult
your
DIGITAL Field Service
Representative 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 synchronous characters in a synchronous leader.
You must enter a value in the range 3 through 14(10).
A typical
response is 4 through 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
synchronous characters.
Subsequent DQll lines do not default any of the parameters;
enter values for the vector and CSR assignments.

you

must

* 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
in the range 300 through 774 octal.
Consult your DIGITAL Field
Service Representative if the vector address is unknown or see
Appendix E.
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 in the range
160010 through 177700 octal.
Consult your DIGITAL Field Service
Representative if the CSR address is unknown or see Appendix E.

4-87

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
The first DUll line defaults to a full-duplex line (F).
specify a half-duplex line.

Enter

There is no default value for the parameter that specifies the
required number of synchronous characters in a synchronous leader.
You must enter a value in the range 3 through 14(10).
A typical
response is 4 through 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
synchronous characters.
Subsequent DUll lines default only the full-duplex parameter (F);
must enter values for the vector and CSR assignments.

you

* XW controller 0 [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
address in the range 300 through 774. Consult your DIGITAL Field
Service Representative if the vector address is unknown or see
Appendix E.
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 in the
range 160010 through 177700.
Consult your DIGITAL Field Service
Representative if the CSR address is unknown or see Appendix E.
The first DUPll line defaults to a half-duplex line (H).
specify a full-duplex line.

Enter

There is no default for the parameter that specifies the required
number of synchronous characters in a synchronous leader.
You must
enter a value in the range 3 through 14(10). A typical response is 4
through 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 synchronous
characters.
Subsequent DUPll lines do not default any of the parameters;
enter values for the vector and CSR assignments.

you must

* YH controller 0 [D:,,,300,0,0]
This question appears only if you specified a DHll asynchronous line
interface
(YH)
and have a UNIBUS processor (for example, PDP-11/24,
PDP 11/44, or PDP 11/70). Note that the Loadable/Resident parameter
does not appear.
Enter the interrupt vector address (no default), the CSR address
(no
default),
the number of lines
(no default), the DMll-BB interrupt
vector address (no default), and the DMll-BB CSR address (no default).

4-88

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
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 in the range
300 through 774. Consult your DIGITAL Field Service Representative if
the interrupt vector address is unknown or see Appendix E.
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 in the range 160010 through 177700.
Consult your DIGITAL Field Service Representative if the CSR address
is unknown or see Appendix E.
The DHll can service up to 16 remote and local lines. Enter the total
number of lines desired by specifying the highest line number in the
range 0 through 15(10) (0 indicates one line, 15 indicates 16 lines).
If your DHll includes DMll-BB modem support, you must enter the baud
rate for all DHll remote lines. The default answer speed (baud rate)
is 300.
(This speed can be changed later on an individual line basis
using the MCR or VMR SET /REMOTE command.) If you do not use the
default response, the acceptable answer speeds (baud rates)
are 50,
75, 110, 134.5, 150, 200, 300, 600, 1200, 1800, 2400, 4800, or 9600.
You must also specify the DMll-BB vector and CSR assignments.
The
default response of 0 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 in the range 300 through 774 to include DMll-BB modem
support. Consult your DIGITAL Field Service Representative if the
interrupt vector address is unknown or see Appendix E.
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
through 177700 for the CSR assignment.
SYSGEN repeats this question for each DHll specified.

* YH controller 0 [D:,,,O]
'< v {cv- &. a~
This question appears only if you specified a DHVll asynchronous line
interface {YH) and have a Q-bus processor {for example, an LSI-11, PDP
11/03, PDP-11/23, or PDP-11/23-PLUS).
The DHVll is the Q-bus equivalent to the UNIBUS DHll
{refer to the
preceding question). Unlike the DHll, the DHVll does not have DMll-BB
modem support. Also, the DHVll baud rates differ from those of the
DHll.
Enter the interrupt vector address (no default), the CSR address
(no
default), the number of lines (no default), and the baud rate (the
default is 0).

4-89

DETAILS OF SYSGER PHASE I

PERIPHERAL OPTIONS (Cont.)
The interrupt vector address for the DHVll is assigned from floating
vector space starting at location 300(octal).
Thus, there is no
default vector assignment for the DHVll. Enter a vector address in
the range 300 through 774(octal). Consult your DIGITAL Field Service
Representative if the interrupt vector address is unknown or see
Appendix E.
The CSR address for the DHVll is assigned from the floating address
space starting at 160010(octal).
Thus, there is no default CSR
assignment for the DHVll. Enter a CSR address in the range 160010
through
177700(octal).
Consult
your
DIGITAL
Field
Service
Representative if the CSR address is unknown or see Appendix E.
The DHVll can service up to 8 remote and local lines. Enter the total
number of lines desired by specifying the highest line number in the
range 0 through 7 (0 indicates one line, 7 indicates 8 lines).
The DHVll can maintain a full-duplex connection through a Bell
103A-type modem.
However, modem support requires additional code in
the terminal driver and thus increases system overhead; select modem
support only if needed.
If you wish to include modem support, specify
the baud rate for all DHVll remote lines.
Acceptable answer speeds
(baud rates)
are 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2000,
2400, 4800, 9600, or 19200. This speed can be changed later on an
individual line basis using the MCR or VMR SET /REMOTE command. Note
that the default for this parameter (0) excludes modem support.
SYSGEN repeats this question for each DHVll specified.
NOTE
If you include a DHVll in your system,
SYSGEN
automatically
includes
the
full-duplex terminal driver (Question 1,
Option
C,
Terminal
Driver Options
Section).

* YJ controller 0
This question appears only if you specified a DJll
(YJ)
asynchronous
line multiplexer. Note that the Loadable/Resident parameter does not
appear because the DJll uses the same driver as the DLll and the DHll.

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 in the range 300
through 774. Consult your DIGITAL Field Service Representative 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 in the range 160010 through 177700.
Consult your DIGITAL Field Service Representative if the CSR address
is unknown or see Appendix E.

4-90

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
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 O through 15 decimal (0 indicates one line, 15 indicates 16
lines) •
SYSGEN repeats this question for each DJll specified.

* YL controller 0 [0:60,177560, NO]
This question always appears; you must include at least one DLll line
interface in an RSX-llM system.
The default interrupt vector address for the first DLll line is 60.
If you do not use the default vector assignment, the acceptable range
is 60 through 774.
The default CSR address for the first DLll line is 177560. If you do
not use the default CSR assignment, the acceptable range is 160000
through 177700.
If your DLll includes modem support (that is, if you have a DLll-E or
a DLVll-E), enter E; otherwise, enter No. The remote speed of the
DLll is determined by the hardware and cannot be changed using
software.
If you specify more than one DLll, you must enter the vector
assignment for each additional line.

and

CSR

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 through 774 octal. Consult your DIGITAL Field Service
Representative if the interrupt vector address of additional lines is
unknown or see Appendix E.
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 through 176770 octal.
Consult your DIGITAL Field Service
Representative if the CSR address of additional lines is unknown or
see Appendix E.

* YZ controller O [D:,,,O]
This question appears only if
asynchronous
line multiplexer.
parameter does not appear.

you specified a DZll/DZVll (YZ)
Note that the Loadable/Resident

The interrupt vector address for the DZll/DZVll is assigned from
floating vector space starting at 300. Thus, there is no default
vector assignment for the DZll/DZVll. Enter a vector address in the
range 300 through 774 octal.
Consult your DIGITAL Field Service
Representative if the vector address is unknown or see Appendix E.

4-91

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
The CSR address for the DZll/DZVll is assigned from floating address
space starting at 160010. Thus, there is no default CSR assignment
for the DZll/DZVll. Enter a CSR address in the range 160010 through
177700.
Consult your DIGITAL Field Service Representative if the CSR
address is unknown or see Appendix E.
Each DZll can service up to eight asynchronous lines. Enter the total
number of lines by specifying the highest line number in the range 0
through 7(10) (0 indicates one line, 7 indicates eight lines).
Each DZVll can service up to four asynchronous lines. Enter the total
number of lines by specifying the highest line number in the range 0
through 3 (10) (0 indicates one line, 3 indicates four lines).
The DZll/DZVll can maintain a full-duplex connection through a Bell
103A-type modem.
However, modem support requires additional code in
the terminal driver and thus increases system overhead; select modem
support only if needed.
If you wish to include modem support, specify
only one baud rate for all DZll/DZVll remote lines. Acceptable answer
speeds
(baud rates) are 50, 75, 110, 134.5, 150, 200, 300, 600, 1200,
1800, 2000, 2400, 3600, 4800, 7200, or 9600. This speed can be later
changed on a line basis using the MCR or VMR SET /REMOTE command.
Note that the default for this parameter (0) excludes modem support.
SYSGEN repeats this question for each DZll/DZVll specified.

4.8.1

IC and IS Subsystems

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.

* 1.

Expanded comments for ICS/ICR questions?

Expanded comments provide explanatory text that helps you
ICS/ICR questions.

* 2.

answer

the

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 through 774. Subsequent IC controllers
obtain vector assignments from floating vector space starting at 300.
Consult your DIGITAL Field Service Representative if the vector
addresses are unknown.

4-92

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
* 4.

CSR address:

The standard CSR address for the ICS/ICR subsystem is 171776. Enter a
value within the range 160000 through 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
repeats this query for each IC controller specified.

* 6.

ICS-11.

SYSGEN

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

The ICS/ICR subsystem supports up to 16 A/D converter modules, each
with 8 channels. Enter a value in the range 0 through 16(10).
If you
enter a non-zero value, SYSGEN asks Question 7.
SYSGEN Question 6
and, if applicable, Question 7, for each IC controller specified.

* 7.

A/D converter module number:

Enter the module number in the range 0 through 15.

* 8.

Number of expansion multiplexers:

Enter a value in the range 0 through 7.

* 9.

(<module name>) module number

This question appears for each module you include
(that is,
if you
enter non-zero values for Questions 12 through 19).
Enter a value in
the range 0 through 15.

* 10.

Restore module status on power and error recovery?

This question appears only if the system includes a bi-stable
D/A converter, or I/O counter module.

output,

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.

4-93

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
* 11.

How many line errors are acceptable per second?

This question appears only if you include the
option (respond Yes to Question 10).

restore

module

status

When serial line errors exceed the limit you specify in response to
this question, the IC driver places the affected subsystem off line
(when the line errors cease, the driver automatically places the
subsystem online).
Enter a value in the range 0 through 5000.
The ICS/ICR 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 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:

* 18.

Expanded comments for DSS/DRS questions?

Expanded comments provide explanatory text that helps you
DSS/DRS questions.

4-94

answer

the

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
* 19.

Number of DRS-11 modules:

Enter the number of DRS-11 digital output modules in the range
through 16.
If you enter O, SYSGEN omits Questions 20, 21, and 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 through 177700.

* 22.

DRS-11 vector address:

Enter a value for the vector address in the range 300 through
This question appears for each individual module you specify.

* 23.

774.

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 through 16 minus the number of
DRS-11 modules specified in Question 19. If you enter 0, SYSGEN omits
Questions 24, 25, and 26.

* 24.

DSS-11 CSR address:

Enter a value for the CSR address in the range 160000 through 177700.

* 25.

DSS-11 vector address:

Enter a value for the vector address in the range 300 through
This question appears for each individual module you specify.

* 26.

774.

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.

4-95

DETAILS OF SYSGER PHASE I

PERIPHERAL OPTIONS (Cont.)
4. 8. 2

IP. Subsystems

Included with selected questions below are associated conditional
symbols which are defined only if you respond Yes to a particular
question. Defined symbols are included in the file RSXMC.MAC.
This
file is created during SYSGEN and usually resides in SY:[ll,10].
SYSGEN uses these conditional symbols during the assembly of the IP
driver,
including certain portions of code only if you select the
support during SYSGEN. Prior to subsequent system generations, you
can refer to RSXMC.MAC to determine the support that was previously
included.
It is important to note that SYSGEN creates a new version
of RSXMC.MAC during each system generation.
If your system includes IP11/IP300 support, SYSGEN asks the following
questions.
Consult the IPll/IP300 documentation for details on the
IP11/IP300 I/O subsystem. 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.

* 1.

Extended comments for IP112/IP302?

[Y/N]:

Expanded comments provide explanatory text that helps you
IP112/IP302 questions.

* 2.

Do you want a loadable IP driver?

answer

the

[Y/N]:

Respond Yes to this question if you want a loadable IP driver.
to Question 17 for related information on the location
power-fail block.

Refer
of the

If you respond Yes to this question, SYSGEN generates the symbol LD$IP
in RSXMC.MAC.

* 3.

Treat all controllers as one unit?

[Y/N]:

If you respond Yes, SYSGEN generates one SCB and one UCB to cover all
IPll controllers. This creates the appearance of a single, large IPll
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 16.
If you respond Yes, SYSGEN generates the symbol !$$PUN in RSXMC.MAC.
If you respond No, SYSGEN generates one SCB and one UCB for each IPll
controller.
Each controller must then be referenced with a different
LUN.
If you enter No, each controller can support 16 A/D converters,
but the programmer must know on which controller a particular I/O
module is as well as the module index.

4-96

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)
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.
1 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
(Yes
to the previous 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 11 A/D converter modules
(A014).

* 4.

Any latching digital output modules?

[Y/N]:

If you respond Yes, SYSGEN generates the symbol I$$PDO in RSXMC.MAC.
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.

* S.

Any single-shot output modules?

[Y/N]:

If you respond Yes, SYSGEN generates the symbol !$$PSS in RSXMC.MAC.

* 6.

Direct output via QIO?

[Y/N]:

If you respond Yes, SYSGEN generates the symbol I$$PQO in RSXMC.MAC.
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 for
FORTRAN support to work.
However, if present, it does not interfere
with FORTRAN support.
The question appears only if you include a latching digital output
module or a single-shot output module (Yes response to Questions 3 or
4) •

* 7.

Any non-interrupting digital sense modules?

[Y/N]:

If you respond Yes, SYSGEN generates the symbol I$$PDS in RSXMC.MAC.

* 8.

Any interrupting digital sense modules?

[Y/N]:

If you respond Yes, SYSGEN generates the symbol I$$PDI in RSXMC.MAC.

4-97

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
* 9.

Any change-of-state modules?

[Y/N]:

If you respond Yes, SYSGEN generates the symbol I$$PCO in RSXMC.MAC.

* 10.

Any counter modules?

[Y/N]:

If you respond Yes, SYSGEN generates the symbol I$$PTI in RSXMC.MAC.

* 11.

Direct input via QIO?

[Y/N]:

If you respond Yes, SYSGEN generates the symbol I$$PRD in RSXMC.MAC.
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 Yes
Questions 6, 7, 8, or 9.

* 12.

Unsolicited interrupt support?

one

[Y/N]:

If you respond Yes, SYSGEN generates the symbol I$$PUI in RSXMC.MAC.
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 8.

* 13.

Event flag linkage to interrupts?

[Y/N]:

If you respond Yes, SYSGEN generates the symbol I$$PEF in RSXMC.MAC.
A task
event
driver
causes

can monitor digital interrupts by linking a contiguous group of
flags to interrupting bits.
If you select this option, the
sets the corresponding event flag whenever its associated bit
an interrupt.

* 14.

Any D/A converters?

[Y/N]:

If you respond Yes, SYSGEN generates the symbol I$$PDA in RSXMC.MAC.

4-98

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)
* 15.

Any A014 A/D converters?

[Y/N]:

If you respond Yes, SYSGEN generates the symbol I$$PAD in RSXMC.MAC.

* 16.
If you

* 17.

Any A020 A/D converters?

[Y/N]:

Yes, SYSGEN generates the symbol I$$Pl4

RSXMC.MAC.

How many output bytes should be saved on powerfail?

If your response is equal to or greater than 1, SYSGEN generates the
symbol I$$PPF = n in RSXMC.MAC., (where n is the number of bytes saved
on powerfail)
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 answer to this question reserves table space in the IP11/IP300
driver
(if the driver is resident) or in SYSTB.MAC (if the driver is
loadable).
If the answer to the question is n, (3*n)
+10 bytes are
reserved.
In either case,
this space is part of the Executive, so
available pool space is correspondingly decreased=
At power-fail 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.
The acceptable range is 0 through 3048(10).
Enter 0 (or press the RETURN key)

* 18.

to disable output restoration.

IPll controller vector (0 R:60:77 0:234]:

Enter the interrupt vector address for the first IPll controller. The
standard vector address, and the default value, is 234.
If you do not
use the default assignment, the acceptable range is 60 through 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
your
DIGITAL
Field Service
Representative if the IPll vector address is unknown.

* 19.

Base address (0 R:l60000-177400 0:171000]:

Note that this question requests the IPll base address and not the CSR
address.
The base address is the CSR address minus 377(8).

4-99

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)
For the first IPll controller, the default base address is 171000(8).
For the second IPll controller, the default base address is 171400(8).
The acceptable range for the
177400(8).

IPll

base

address

160000

through

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 your DIGITAL Field Service Representative
address is unknown.

4-100

the

IPll

base

DETAILS OF SYSGEN PHASE I

Example 4-1

Annotated Terminal Output from SYSGEN Phase I

RSX-11M V4.1 35-A.
>RED DU=SY:
>RED DL:=LB:
>MOU DL:RSXH35
>@DL![1,2JSTARTUP
>* PLEASE ENTER TIME AND DATE CHR:HN DD-MMM-YY> [SJ: 15:48 21-FEB-83
>TIM 15:48 21-FEB-83
>* ENTER LINE WIDTH OF THIS TERMINAL [D D:132.J:
>SET /BUF=TI!132.
>ACS SY:/BLKS=512.
>@ <EOF>
>SET /UIC
UIC=[200,200J
>@SYSGEN

); RSX-11M V4.1 BL35-A System Generation PHASE I -- version 2.0
); 21-FEB-83 15:48!26
); RL01/RL02 distribution kit
>* 1. Autoconfisure the host system hardware! [Y/NJ: Y
>INS $ACF. BSL
>INS $ACO
>ACF
>ACO SHOW
Processor Type:
11/23
MemorY Size:
128. Kw

Extended Instruction Set <EIS>
Extended (22-Bit) Addressins
Parity Memory
Name
DLA
LPA
YLA
DDA
YZA

Vector
160
200
060
300
310

CSR
174400

Unit

T"&Pe

0
1

RL02
RL02

Remark

177514
177560
176500
160100

>ACO SYSGEN
>REM ACF
>REM ACO
2. Do You want to override AutoconfiS•Jre results! [Y/NJ; Y 8
>* 3+ Do You want to inhibit execution of MCR commands CPREPGEN)! [Y/NJ! Y 8
>* 5. Are you seneratins an unmapped system! [Y/NJ: N
>* 6. Use an inPut saved answer file! [Y/NJ! N
>* 8. Do You want a Standard Function System! [Y/NJ: N
>* 9. Name of out Put saved answer f i 1 e [ D: SYSSAVED. CMD J [SJ: 0

>; Phase I output saved answers created in file DLO:r200,200JSYSSAVED.CMD;1

>* 15. Chain to Phase II after Phase I completes! [Y/NJ: N
>* 16. Enter device for EXCPRV disk when it is ready Cddu!> rD: DL1!J [SJ: DL1!
>MOU DL1!EXCPRV

>; Tarset confisuration
>* 1. Processor TYPe
CD: 11/23] [SJ:
>* 2. Does Processor have a switch resister! [Y/N D!NJ!
>* 3. Memors size Cin K-word blocks) [[I R!16.-1920. D!128.J!
>* 4. Include suPPort for K-series devices! [Y/N D!NJ:
>* 6. Floating Point Processor CFP-11) present! [Y/N D!NJ!
>* 7. Floatins instruction set <FIS> Present! [Y/N D!NJ:
>* 8. Extended instruction set <EIS) Present! [Y/N D!YJ:
>* 10. Line freauency!
A- 60 Hz
B- 50 Hz
CD: AJ [SJ:
>* 11. KW11-Y Watchdog timer suPPort! [Y/N D!NJ:
>* 12. Memory Parity support! [Y/N D!YJ:

(continued on next page)

4-101

DETAILS OF SYSGEN PHASE I
Example 4-1

(Cont.)

Annotated Terminal Output from SYSGEN Phase I

>; The response to the followins auestion sPecifies the hiShest interrupt
); vector.
If You respond with a value less than or eaual to 400, SYSGEN
will assisn the value associated with the hishest interrupt vector
specified durins the PeriPheral Section.
Therefore, if your system
will include devices that are not specified durins the Peripheral
Section and which have vectors above 400 (devices such as K-series and
certain communication devices), specify that value in the next auestion.

>;
>;
>;
>;
>;
>;

>* 14. Hishest interruPt vector [0 R:0-774 D:OJ:

'*' Prints device table' •.• Terminates inauirY

>;
>;
>;

1
? 1 Prints current confisuration
Enter devices and number of controllers for devices which reauire drivers

Current system confisuration:

For device confisuration:

);

:>;

DD=1, DL=1 r LP=-1 r YL=1, YZ=1

>;
>;

Device codes for A/D and industrial/laboratory devices:

>* 15. Devices [SJ! *0
>i

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
?'

>;
>;
>;
>;
>;
>;
>;
>;
>;
);

ADAFARICIPISLALSUD-

ADOl-D A/D Converter
AFC11 A/D Converter
ARll Laboratory Subsystem
ICRll/ICSll Industrial Control Subsystem
IP11/IP300 Industrial Control Subsystem
DRS11/DSS11 Industrial Control Subsystem
LPA11 Laboratory Subsystem
LPSll Laboratory Subsystem
UDC11 Universal Disital Controller

Device codes for Interprocessor comaunication devices:
XB- DAll-B Interprocessor Link
XL- DL11-E Interprocessor Link
XM- DMC11-E/DMR11 Interprocessor Link
XP- DP11 Synchronous Interface
XO- DQ11 Synchronous Interface
XU- DU11 Synchronous Interface
XW- DUP11 Synchronous Interface
Device codes for unit record devices:
CR- CR11/CM11-E Card Reader
GR- VT11/VS60 GraPhics Subsystem
LP- LA11/LP11/LS11/LV11/LN01 Line Printer
PP- PC11 PaPer Tape Punch
PR- PC11/PR11 PaPer Tape Punch and Reader

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

Device codes for disk devices:

Device codes for Masnetic tape devices:

>;
>;
>;
>;
>;

DBDDDFDKDL-

RP04/RP05/RP06 Disk Drive
TU58 Cartridse DECtape II
RF11 Fixed Head Disk Drive
RK03/RK05 Disk Drive
RL01/RL02 Disk Drive
trM- RK06/RK07 Disk Drive
J'OC•/\"7
DF'- RC•/\")
I v . ; . . / f'\I VW
Disk Drive
DR-- RM02/RM03/RM05/RM80/RP07 Disk Drive
DS- RS03/RS04 Fixed Head Disk Drive
DT- TU56 DECtaPe
DU- RA60/RA80/RA81/RC25/RD51/RX50 Disk Drive
DX- RXOl FloPPY Disk Drive
DY- RX02 FloPPY Disk
EM- MLll Non-Rotatins Electronic Memory

CTMFMMMSMT-

TU60 Cassette TaPe Drive
TU78 MastaPe DriNe
TU16/TU45/TU77/TE16 MastaPe Drive
TS11/TU80/TSV05 MastaPe Drive
TU10/TE10/TS03 Ma~ta~e Drive

(continued on next page)

4-102

DETAILS OF SYSGEN PHASE I
Example 4-1

>;
>;
>;
>;
>;
>;

(Cont.)

Annotated Terminal Output from SYSGEN Phase I

Device codes for terminal interface devices:
YHYJYLYZ-

};

>;
:>;

DH11/DHV11 Asynchronous Terminal Interface
DJ11 AsYnchronous Terminal Interface
DL11-A/-B/-C/-D/-E/-J/-W Asynchronous Terminal Interface
DZ11/DZV11 Asynchronous Terminal Interface

Device codes for Pseudo devices!

CO- console device
NL- null device

:>;
>;
:>;

Enter responses as: devl=number controllers,dev2=number controllers,
If a devices is specified without the number of controllers, the number
of controllers defaults to 1.

>;
>;

>;
>;
>; Processor!11/23

>;
>;
>;
>;

Memory Sizel128KrMaPPed

Sys tern: RSX-11 M

Extended Instruction Set
Parity Memory

>; Host confisuration

>*
>*
>*
>*

1+
3.
4.
5.

Is a line Printer available? CY/NJ: Y
Does the listins/maP device have at least 120 columns? CY/NJ: Y
Assembly listinss device Cddu!) ED! 1 NLl 1 J [SJ:
MaP device for Executive and device drivers Cddu!> CD: DL1!J CSJ!

>;
>* EDS * Do You want to: <CR>-continue R-rePeat section E-exit P-Pause [SJ:

>; Executive 0Ptions

>;
>;

Answer YCES) if the followins SUPPort is desired

>*
>*
>*
>*
>*
>*
>*
>*
>*

1.
2.
3.
4.
5.
6+
7.
8.
9.

>;
>* 12.
>* 13+
>* 14.
>* 15.
>* 16.
>;
>* 18+
>* 19.
>* 20.
>* 21+
>* 22.
>* 23.
>* 24.
>* 25.
>* 28.
>* 29.
>* 30.
>* 32.

>;
>;
>;

Include Sl.JPPOl't for DBMS-11? CY/NJ! N
FIL.ES-11 ACP r~ CY/NJ! Y
RMS bucket lockins (file sharins> and Placement control? CY/NJ! Y
Non-resident tasks <task loader)? CY/NJ! Y
Loadable task loader? CY/NJ! Y
Executive Common? [Y/NJ: Y
Memory manasement CPL.AS> directives? [Y/NJ! Y
Send/Receive b'::I reference directives? [Y/NJ: Y
Get maPPins context directive? CY/NJ! Y
Address checkins support will be included
I/O rundown support will be included
Multi-user Protection? [Y/NJ! Y
ANSI MastaPe ACP? CY/NJ: Y
Do You want on-line formattins CFMT> or diasnostic QIOs? [Y/NJ: Y
Loadable device drivers? [Y/NJ! Y
Should the default for all aPPlicable drivers be loadable? [Y/NJ! Y
AST suPPort will be included
Include SUPPort for Cancel Selective Marktime? [Y/NJ: Y
Task termination and device not ready messases <TKTN>? CY/NJ: Y
Power fail recovery? CY/NJ: Y
Install, reGuestr and remove on exit? [Y/NJ! Y
Larse <20K> Executive? CY/NJ: Y
Losical device assisnment? [Y/NJ! Y
Include support for error loSSins? [Y/NJ: Y
Do You intend to include a user-written driver? [Y/NJ: N
Disk writecheck? [Y/NJ: Y
Software write-lock? [Y/NJ! Y
Executive Debussins Tool <XDT>? [Y/NJ! Y
Include support for communications products <such as DECnet>? CY/NJ: Y

If You will be Seneratins DECnet into this system' be sure you have
read the section on SYS~EN reouirements in the 'RSX DECnet Network
Generation and Instaiiation Guide.=

(continued on next page)

4-103

DETAILS OF SYSGEN PHASE I
Example 4-1

(Cont.)

Annotated Terminal Output from SYSGEN Phase I

>;
>;
>;

Several DECnet features <es. remote terminal suPPortr 11S task
loadins/uPline dumPinsr etc.> reouire special consideration durins
SYS GEN.

>*
>*
>*
>*

33.
34.
35.
36.

System controlled partitions? [Y/NJ: Y
Include suPPort for the Shuffler? [Y/NJ: Y
Queue manaser and oueued Print spooler? [Y/NJ! Y
Group slobal event flass? [Y/NJ! Y

>;
>;

For directives:

>;
>;

* - Prints the table
- Terminates inouiry
%
Gets all valid directives and terminates inouirY

>;
>;

>* 37. Enter code for system directives [SJ:

>;
>;
>;
>;

A- Get Partition Parameters
c- Send/Receive
E- Extend tas",
G- Get sense switch
I- StoP bit
K- Parent offsPrir1s task ins

>;
>;
);

B- Get task Parameters
D- Alter Priority
F..:. Conr1ect to interrupt vector
H- Set SYStem time
J- SPecif'=l reouested exit AST
L- Parent offsPrins task ins with chainins

Enter responses as code 1 code2code3. • • <no co1Dmas > <e. s. : ABCDF • ) 0

>* 37.
>* 37.
>;
>* 38.
>* 39.
>* 40.
>* 41.
>* 42.
>* 43.
>* 44.
>* 46.
>* 48.
>* SO.
>* 51.
>* 52.
>* 53.
>* 54.
>* 56.

Enter code for sl:lstem directives CSJ: ABCDEFIK
Enter code for Sl:lstem directives CSJ! •
CheckPointins support will be included
Number of Pre-allocated OIO Packets CD R:0.-15+ D:S.J:
Size of data transfer vector in words CD R:0.-33. D:33.J:
Round-robin schedulins interval in ticks [D R:o.-1000. Dt5.J:
Hishest Priorit'=l class for consideration [D R:l.-249. D:150.J:
Lowest Prioritl:l class for consideration [D R:l.-150. 0:1.J:
Executive level disk swaPPins interval [D R:o.-sooo. D:3o.J:
SwaPPinS Prioritl:l [D R:l.-20. D:5.J:
Seconds between Printer not readl:l messases CD R:0.-255. D!30.J:
Sl:lstem crash resister and stack dump oevice CSR [Q R:0-177700 D:177564J:
CheckPointins with sl:lstem checkPoint file? [Y/NJ: Y
Crash dump anall:lsis: A- PANIC B- Crash Dump Anall:lsis CCDA> [D: BJ [SJ! B
CDA output notification device CSR CO R!160000-177700 D:177564J!
Enter CDA memory dump device mnemonic Cddu:> [S R:3-4J! DL1:
Enter CDA mem-0rl:l dump device CSR CO R!160000-177700 D:174400J!
RT-11 emulation SUPPOrt? [Y/NJ: N

* Do You want to: <CR>-continue R-rePeat section E-exit P-pause [SJ:

>* EOS

>;
>;

>; Terminal driver options
>*

1. Terminal driver desired CA/B/C/Dr

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

Terminal drivers!

* Prints table) [SJ! * aD

A- Tailorable half duplex
B- TailQred half duPlex <user-oriented>
C- F•Jll duPle:-~
D- Baseline half duPlex

1. Te!'minal d!'lYe!' desired (A/B/C/D1 *Prints table) [SJ! c~
2. Unsolicited input timeout value in seconds CD R:0.-255. 0:120.J:

>;
>;

Answer YCES> if the followins suPPort is desired

>;
>* 6.
>;
);
>* 10.

>* i i +

>*
>*
>*
>*
>*

12.
13.
17+
20.
25.

Unsolicited input character AST? [Y/NJ! Y
Breakthroush write support will be included
CTRL/R SUPPOrt will be included
Escape seouence handlins? [Y/NJ: Y
Get multiple characteristics? CY/NJ! Y
S~t multiple characteristics? [Y/NJ! Y
Get terminal driver oPtions? CY/NJ! Y
Read after PromPt? [Y/NJ! Y
CRT rubout SUPPOrt? [Y/NJ: y
Hardware unrecoverable inPut error notification? [Y/NJ! Y

(continued on next page)

4-104

DETAILS OF SYSGEN PHASE I
Example 4-1 (Cont.)

Annotated Terminal Output from SYSGEN Phase I

>* 26. Device independent cursor Positioninsl? EY/NJ! Y
>* EDS * Do you want to: <CR>-continue R-rePeat section E-exit P-Pause [SJ:

>;
); System 0Ptions

>;
>;
>;
>;

>*
>*

Answer Y<ES> if the followinsl support is desired
3. Build the PLAS resident FCS? EY/NJ: Y
4. Code for FCP CA/B/C/Il/E, * Prints table> ED: CJ ESJ: *f)

:::-;

The five FCP codes are:
A B C D
E -

MINIMUM:
SMALL:
MIDDLE:
LARGE:
OTHER:

Minimum functionality <2KW>
Full functionality, heavily overlased <2.5KW>
Full functionality, moderately overlaYed C5KW>
Full functionality, non-overlased <9KW>
User SUPPiied FCP

>* 4. Code for FCP ( A/B/C/D/E, * Prints table) ED: CJ ESJ: C~
>* 5. Build Post Mortem Dump <PMD>? EY/NJ: Y
>* 6. Build the Resource Monitorinsl DisPlas task <RMD>? EY/NJ: Y
>* a. Do YOU want DIGITAL Command Lansuase <DCL)? EY/NJ: y
>;
Parent offsPrins taskins with chainins directive suPPort will be included
>;
Specify reauest exit AST directive sUPPort will be included
>* 9. Enter the number of user-written CLis ED R:0.-13. D:O.J:
>* 10. Do sou want Pool monitorins and low Pool recovers <PMT>? EY/NJ: Y
>* 11. What name would sou like to sive sour system ED: RSX11HJ ES R:0-6J:
>* 12. Do you want SPM-11 support? EY/NJ: N
>* EDS * Do sou want to: <CR>-continue R-rePeat section E-exit P-pause ESJ:

:>;

Thinkinsl

);

>; End of Executive oPtion seneration at 15:58:38 on 21-FEB-83
>; Peripheral confisuration

Parameters aPPearins in sauare brackets •c ••• J• can only be
specified for the first ~ontroller of a Particular device.
Parameters aPPearinsl in Parentheses •c ••• > onls need be specified
if
the indicated option is Present on the tarset ssstem.

>;
>;
>;

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
specified
device.

>;
>;

>; A/D and Laboratory devices: None specified
>; Interprocessor communication devices: None sPecified
); Unit record devices: LP4D
>; Enter EL/R,J vector' CSR, Printer option
(,[KMC timeout count <O=no KHC>, KHC vector, KHC CSRJ> for:

.. '
>* 16. LP controller 0 rn: 200'177514rLA180,o,300,160130J ESJ:
:-

',LP11-BfD

>; Disks: DD, DL, DU
Enter EL/R,J vector, CSR, number of drives for:
3. DD controller 0 rn: 300,176500,2J

ESJ:

>* 3. DL ~ontroller 0 ED: 160,174400,2J
>* 53. Contr 0 unit o. is an RL01/RL02 rn: RL02J
>* 53. Con tr 0 unit 1. is an RL01/RL02 rn: RL02J

ESJ:
ESJ:
ESJ:

>;
>; Enter EL/R,J vector, CSRr number of drives, nuaber of command rinss,
)j

number of resPonse

rin~s

for:

(continued on next page}

4-105

DETAILS OF SYSGEN PHASE I

Example 4-1 (Cont.)

Annotated Terminal Output from SYSGEN Phase I

>;
>* 25. DU controller O [D: 154,172150,,4,4]
[SJ: ,,2,,
>* 60.
Contr 0 unit O. is an RA60/80/81/RC25/RD51/RX50 [D:
RA81J [SJt RC25
>* 60.
Contr 0 unit 1. is an RA60/80/81/RC25
[Dt
RA81J [SJ: RC25

>; TaPes: MS
>; Enter [L/R,J vector, CSR for:

1. MS controller 0 [D: 224,172522]

[SJ:

'·.

); Non-PhYsical (pseudo) devices: COr Nlr Tlr CL, LBr SY

>; Terminal interface devices: Ylr YZ
>; Enter vector, CSRr E=DL11-E modem suPPort/NO=no for:
);

[SJ:

>* 21. YL controller 0 CD: 60r177560,NOJ

>; Enter vector, CSR, hiShest line number <O to 7> [, answer sPeedJ for:

>;
[SJ:

>* 24. YZ controller 0 [Dt 310r160100,3r300J

>* EDS * Do You want to: <CR>-continue

R-re~eat

section E-exit P-pause [SJ:

>;
>;
>; End of interrupt vector area has been set to 400
>;
>;
>; Create Executive build files
>*

1. Do You wish to edit any of the Executive files? CY/NJ: N

>* EDS * Do You want to: <CR>-continue R-rePeat section E-exit P-pause [SJ:

>;
>;
>;

>; Prepare for task buildins

>;
>; Clean-up extraneous obJect files
);

>;
>* EDS * Do You want to: <CR>-continue R-rePeat section P-Pause [SJ!
>; End of SYSGEN Phase I at 16!09!21 on 21-FEB-83
>;
To continue tYPe: @(200,200JSYSGEN2

>@ <EDF>
>@SYSGEN ~

>;
>; RSX-11M V4.1 BL35-A System Generation PHASE I -- version 2.0
>;
>; 21-FEB-83 16:09!34
>; RL01/RL02 distribution kit

1.
3.
4.
5.
6.
7.

Autoconfi~ure the host system hardware? CY/NJ! N
Do You want to inhibit execution of MCR commands <PREPGEN>? (Y/NJ: N
Have YOU made a COPY of the distribution kit? (Y/NJ: Y
Are YOU Seneratins an unmapped sYstern? (Y/NJ: N
Use an inPut saved answer file? (Y/NJ: Y
Name of inP•.1t saved answer file CD: SYSSAVED.CMDJ [SJ:~

>; Phase I inPut saved answers
>; created on 21-FEB-83 at 15:49!05
); by SYSGEN version 2.0
>; are from file DLO:C200,200JSYSSAVED.CHD;1

9. Name of output saved answer file CD: DLO:r200,200JSYSSAVED.CHDJ [SJ:

(continued on next page)

4-106

DETAILS OF SYSGEN PHASE I

Example 4-1 (Cont.)

Annotated Terminal Output from SYSGEN Phase I

>;
>; Phase I outPut saved answers created in file DLO:c200,200JSYSSAVED.CMD;2
>*
>*
>*
>*
>*
>*
>*

10.
11+
12+
13+
14+
15.
16.

Use saved host confisuration? CY/NJ: Y
Use saved PeriPheral confisuration? CY/NJ: Y
SkiP end of section <EDS> breakPoints? CY/NJ: Y
SkiP end of execution <EOX> breakpoints? [Y/NJ: Y
Clean UP files from Previous GENs? CY/NJ: Y
Chain to Phase II after Phase I completes? [Y/NJ: N
Enter device for EXCPRV disk when it is ready (ddu:> CD: DL1:J [SJ:

DL1:

>;
>MOU DL1:EXCPRV
>SET /UIC=[ 1 d J
>INS :Pr J.r

>PIP
>PIP
>PIP
>PIP
>PIP
>PIP
>PIP
>PIP
>PIP
>PIP

[1,20JRSXBLD.CMD;*/DE/NM
[1,24JRSXBLD.CMD;*/DE/NM,TTDRVBLD;~

[1i50JSYSVMR.CMD;*/DE/NM,[1,54JSYSVMR;*
c11,20J*.OBJ;*/DE/NM'*•UDC;*'*•ICR;*'*•IDS;*'*•PCS;*
[11,24l*+OBJ;*/DE/NM,*.uoc;*'*·ICR;*,*·IDS;*,*·TTY;*,*·PCS;*
[11,10JRSXMC.MAC;*/DE/NMrICTAB;*,[200,200JSGNPARM.CMD;*
[2Q0,200JRSXBLD.CMD;*/DE/NM,TTDRVBLD;*
DL1:[11r20JRSXASM.CMD;*/DE/NMrRSXDRVASM;*,[12,20JMCRSETASM;*
DL1:[11r24JRSXASM.CMD;*/DE/NM,RSXDRVASM;*,[12,24JMCRSETASM;*
/FR

DLO: has 14863. blocks freer 5617. blocks used out of 20480.
Larsest contisuous space = 9578. blocks
1408. file headers are free' 128. headers used out of 1536.
>SET /UIC=[11r10J
>; Tarset confisuration

>;
>; Processor!ll/23

>;
>;
);

Memory Size!128KrMaPPed

SYstem:RSX-11M

Extended Instruction Set
Parity Memory

>;
>; Host confisuration

>;
>; Executive 0Ptions

>;
>;
>;

CheckPointinS support will be included

);

>; Terminal driver options
>;
>; System DPtions
>;
)j

>;
>;

Parent offsPrins taskins with chainins directive support will be included
Specify reouest exit AST directive support will be included

Thinkins •••

>; End of Executive option seneration at 16!14!02 on 21-FEB-83
>;
>; PeriPheral confisuration
);

>;
>;
>;
);

>;
>;

Parameters aPPearinS
in sauare brackets
•c ••• J"
can only be
specified for
the first
controller of a Particular device.
Parameters aPPearinS in Parentheses 1 < ••• > 1 only need be specified
if
the
indicated option
is present on the tarset system.
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
sPecified
device.

A/D and Laboratory devices: None specified

Interprocessor communication devices: None specified

(continued on next page)

4-107

DETAILS OF SYSGEN PHASE I
Example 4-1

(Cont.)

Annotated Terminal Output from SYSGEN Phase I

>; Unit record devices: LP
>; Disks: DD, DL, DU
>; Non-PhYsical <Pseudo> devices: co, NL, TI, CL, LB, SY
>; Terminal interface devices: YL, YZ
);

>SET /UIC=[1,24J ! Creatins TTDRVBLD.CMD
>SET /UIC=[11,10J
>; End of interrupt vector area has been set to 400
>; Create Executive build

files~

>PIP RSXMC.MAC=DLl:RSXMCO.HAC/AP
>INS $MAC
>ASN SY:=LB:

>; Start of Executive assembly at 16:22:06 on 21-FEB-83
>SET /UIC=Cll,24J
>MAC @DLl:RSXASM
>; End of Executive assembly at 16:s2:10 on 21-FEB-83
>; Start of HCR Cstibset> assembly at 16:52:11 on 21-FEB-83
>SET /UIC=C12,24J
>MAC @DLl:MCRSETASM
>; End of HCR <subset> assembly at 16:sa:oa on 21-FEB-83
)j

>; Start of device drivers assembly at 16:sa:oa on 21-FEB-83
>SET /UIC=[11,24J
>MAC @DLl:RSXDRVASM

>;
>; End of Device drivers assembly at 17:10:37 on 21-FEB-83
>ASN =LB:
);

>; Prepare for task buildins
>SET
>PIP
>PIP
>INS
>LBR
>LBR
>PIP

/UIC=[1,24J
RSX11M.OBS=[11,24J*.OBJ
TTDRV.OBJ=[11,24l*.TTY
$LBR
RSX11M/CR:100.:1010.:128.=RSX11M.OBS
TTDRV/CR:30.:256.:64.=TTDRV
/NV=[11,10JRSXBLD.CMD

>REM LBR

>; Clean-up extraneous obJect files
>PIP RSX11M.OBS;*/DE/NM,TTDRV.OBJ;*,[11r24l*•OBJ;*'*•TTY;*
>REM MAC
>DMO DLl:EXCPRV
DMO -- TTO:
dismounted from DLl:
DMO -- TTO:
dismounted from DL1:
Final dismount initiated
17:25:57
DL1: -- Dismount complete

***

(continued on next page)

4-108

DETAILS OF SYSGEN PHASE I

Example 4-1 (Cont.)

Annotated Terminal Output from SYSGEN Phase I

>REM PIP
>; End of SYSGEN Phase I at 17:25:57 on 21-FEB-83
);
To continue tYPe: @[2Q0,200JSYSGEN2
>SET /UIC=E200,200J

>@ <EOF>

4-109

DETAILS OF SYSGEN PHASE I
Notes for the terminal output from SYSGEN Phase I
system) while running on a baseline system:

(for a mapped target

Hardware bootstrap the baseline system.

Invoke SYSGEN and begin answering Phase I questions.

Answer Yes if you autoconf igured your system and you want to
modify Autoconfigure's results.
SYSGEN will ask you all the
questions in Phase I, but it will use Autoconfigure's results
as the defaults.

Answer Yes if you to want to do a PREPGEN first.

In this example, pressing the RETURN key as the response to
Question 9 selects the default output saved answer file named
SYSSAVED.CMD.
When you enter an asterisk (*) as a response to Question 15 in
the Target Configuration Section, SYSGEN displays a table of
RSX-llM devices.
Select the devices and the number of device controllers for
your target system.
You can display the current system
configuration by entering a
question
mark
(?)
before
terminating your input with a period (.).
If you make several corrections while specifying the devices
for your target system, entering the question mark shows you
the current status of your input. This feature can help you to
avoid making errors in your final response.

When you enter an asterisk (*) as a response to Question 37 in
the Executive Options Section, SYSGEN displays a list of the
system directives.

Specify the system directives you want for your
and terminate your input with a period (.).

fD)

When you enter an asterisk (*) as a response to Question 1 in
the Terminal Driver Options Section, SYSGEN displays the four
types of terminal drivers.

Enter one type of terminal driver.
In this example, the target
system will have the full-duplex terminal driver (C).

target

system

When you enter an asterisk (*) as a response to Question 4 in
the System Options Section, SYSGEN displays the five FCP
optionse

fl)

Enter one type of FCP.
In this example, the target system will
have the default FCP for mapped systems (C).

In the Peripheral Options Section, SYSGEN displays a comment
line before each question for each selected device.
The
comment line contains the various fields that specify the type
and order of the information for you to input.
(See Section
3.3 for more information.j
This is an example of how you can include default values in
your response to Peripheral Options questions.
The commas (,,)
in the response ",,LPll-B" for Question 16 indicate that the
default vector and CSR addresses were selected with the LPll-B.

4-110

DETAILS OF SYSGEN PHASE I
~

When the PREPGEN finishes and you are ready to perform your
SYSGEN, invoke SYSGEN Phase I again and use the saved answer
file created by the PREPGEN.
After all Phase I questions have been answered, SYSGEN creates
the pref ix file RSXMC.MAC.
SYSGEN uses RSXMC.MAC in the
Executive and device driver assemblies.

The remainder of Phase I involves the assembly of the Executive, a
subset of MCR, and device drivers.
Depending on the host system
processor and the options you selected, this process takes from one to
two hours. This is your opportunity to take a break.
If you directed
SYSGEN to pause at EOX breakpoints, you should check back every half
hour or so to answer EOX breakpoint questions at the end of the
assemblies.

4-111

CHAPTER 5
DETAILS OF SYSGEN PHASE I I

Phase II is the task-building phase of the system
generation
procedure.
During Phase II, SYSGEN task-builds the Executive and any
resident device drivers.
It also creates the system image file
RSXllM.SYS and task-builds loadable device drivers and privileged
tasks, such as MCR. Example 5-1 (at the end of this chapter)
is an
annotated terminal output from SYSGEN Phase II.
During this phase, SYSGEN creates the
Indirect
command
file
SYSVMR.CMD.
This file contains Virtual Monitor Console Routine (VMR)
commands that, upon execution, create partitions, load device drivers,
and install tasks in the system image file RSXllM.SYS. Toward the end
of Phase II, SYSGEN allows you to edit SYSVMR.CMD to modify partition
base addresses,
install additional tasks, or make other changes.
Then, if you are running SYSGEN on a stand-alone system, SYSGEN
invokes SYSVMR.CMD.
If you are generating your system from an on-line host system, you
should note the following two items.
First, SYSGEN does not invoke
VMR. You have to invoke VMR after SYSGEN completes Phase II.
(See
Section 5.6.1).
Second, SYSGEN always invokes the Version 4.1 Task
Builder (TKB) to task-build its files. The V4.l TKB is installed as
task ••• TKL.
This permits you to still use the current system's TKB
while the on-line SYSGEN is in progress.
SYSGEN uses the following files as input to Phase II:
RSXBLD.CMD

is the Executive build file. This file directs the Task
Builder in constructing the user-tailored Executive and
the resident device drivers. This file also task-builds
the loadable task loader and the Executive commons if
you selected either option during Phase I.
SYSGEN
creates
RSXBLD.CMD during Phase I
(based on your
responses) •

RSXllM.OLB

is the Executive object library file.
This
file
contains the Executive modules, standard driver modules,
and any user-written drivers. SYSGEN uses this library
to task-build the Executive (including any resident
drivers) and any loadable drivers.

SGNPARM.CMD

is a parameter
file
containing
Indirect
symbol
definitions.
SYSGEN creates SGNPARM.CMD during Phase I
based on your responses to the questions.

TTDRVBLD.CMD

directs the Task Builder in constructing the full duplex
terminal driver.
SYSGEN uses TTDRV.OLB as input from
Phase I to construct the object library for the full
duplex terminal driver.

5-1

DETAILS OF SYSGEN PHASE II
However, SYSGEN only inputs these files to Phase II if
you selected the full-duplex terminal driver in Phase I.
If you specified a resident half-duplex terminal driver,
SYSGEN treats it as any other resident driver in
RSXBLD.CMD.
If you specified a loadable half-duplex
terminal driver, SYSGEN creates the necessary task build
file during Phase II.
Phase II, like Phase I, is organized in logical sections.
However,
not all of the sections for Phase II require that you answer questions
(except for EOX breakpoints). For some sections, like the System
Image Creation Section, the processing does not require user input.
The section headings appear on your terminal, however, to show the
distinct logical parts of SYSGEN Phase II.
They also serve to allow
you to see how far processing has progressed.
The section headings
for
Phase II follow below.
Those sections not requiring user input
are enclosed in parentheses, and are not discussed.

5.1

•

Setup Section

•

(Library Build Section)

•

Executive Task-Build Section

•

(System Image Creation Section)

•

(Full-Duplex Terminal Driver Task-Build Section)

•

Loadable Driver Task-Build Section

•

Common Block Task-Build Section

•

Privileged Task-Build Section

•

System VMR Section

PREPARING FOR PHASE II

Before beginning Phase II of SYSGEN,
following:
•

make

sure

you

have

done

the

If you generate your system from an on-line V4.l host system,
set your UIC to [200,200], assign the logical device SY:
to
your baseline disk, and invoke SYSGEN2.CMD as follows:
>SET /UIC=[200,200]
>ASN ddu:=SY: (where ddu: is the baseline disk, RSXM35)
>MOU ddu:RSXM35
>@SYSGEN2

•

If you generate your system from a stand-alone host system,
bootstrap the baseline system (see Section 4.1) then invoke
SYSGEN2.CMD as follows:
>@SYSGEN2

Figure 5-1 shows the processing steps that take
Phase II.

5-2

place

during

SYSGEN

DETAILS OF SYSGEN PHASE I I

OUTCOME

ACTION

INPUT
SAVED ANSWERS
EXPL!C!T RESPONSES
EXECUTIVE, DRIVER,
AND MCR SUBSET OBJECT
FILES FROM PHASE I

TASK-BUILD THE

EXECUTIVE, DRIVERS,
AND PRIVILEGED TASKS

SYSTEM iMAGE
AND
TASK IMAGES

ZK-323-81

Figure 5-1 Logical Flow of SYSGEN Phase II

5-3

DETAILS OF SYSGEN PHASE II

SETUP
5.2

SETUP SECTION

* 1.

In what UIC is SGNPARM.CMD if not <uic> ?

(SJ:

Enter the UIC containing the file SGNPARM.CMD. SYSGEN replaces <uic>
with the UIC from which you invoked Phase II of SYSGEN. SYSGEN
creates SGNPARM.CMD during Phase I, and in the same UIC from which you
invoked Phase I.
Enter a different UIC to override this default,
otherwise, press the RETURN key.
If you followed the instructions in
Section 4.1, your UIC is [200,200].
SGNPARM.CMD supplies Indirect symbol definitions from Phase I that are
relevant to Phase II processing and provides a means of communicating
between Phase I and the other phases of SYSGEN.
SYSGEN creates this
file in the UIC corresponding to the UIC from which you invoked Phase
I of SYSGEN.
If you are chaining to Phase II the response to this question defaults
to the UIC from which you invoked Phase I and this question does not
appear.

* 2.

Do you want to inhibit execution of MCR commands {PREPGEN)?

[Y/N]:

This option allows you to perform the logical SYSGEN procedure and
create a saved answer file that you can use as input to SYSGEN later
when you actually generate your system.
If you respond Yes to this option, SYSGEN displays the questions and
creates a saved answer file of your responses.
However, SYSGEN does
not process any MCR commands (such as PIP and TKB)
as it normally
would, and, therefore, does not create your system.
When you perform a PRE PG EN in Phase I I, SYSGEN:

• Does not make logical device assignments
• Does not task-build files
• Does not task-build libraries
• Does not create privileged task-build .CMD or .ODL files
e

...

Does not create l.oaaao.ie driver task-build .CMD files
~

• Does not create SYSVMR.CMD
• Does not invoke an editor for modifying files
When you perform a PREPGEN, SYSGEN does create a saved answer file.
If you respond Yes and if you are using an RLOl/02 distribution kit,
SYSGEN will mount the Executive source disk after you enter the drive
containing this disk (Question 7).
The Executive source disk in the
RLOl/02 kit is EXCPRV.

5-4

DETAILS OF SYSGEN PHASE II

SETUP (Cont.)
If you respond No to this question, SYSGEN executes all
and generates an RSX-llM system.

MCR

commands

If you are chaining to Phase II,
the response to this question
defaults to the response given for Question 3 in the Setup Section for
Phase I.
In this case, the question does not appear.

* 3.

Use an input saved answer file?

[Y/N]:

If you have previously created a saved answer file, this option lets
you direct SYSGEN to use that file as input responses to the Phase II
questions. Any SYSGEN question that is automatically answered by a
saved answer file does not appear on your terminal.
SYSGEN does not
save responses to questions concerning the task-building of LPA
initialization code.
Enter a response of Yes to this question if you intend to use a saved
answer file for input.
If you selected the Standard Function System
{see Section 3.6.2) and did not direct SYSGEN to chain directly to
Phase II
(Question 16 in the Phase I Setup Section), respond Yes to
this question.
If you are using an input saved answer file,
SYSGEN
asks for the name of that file in Question 4.
If you directed SYSGEN to chain directly to Phase II,
the default
response to this question is the same as the response given for
Question 6 in the Phase I Setup Section.
In this case, this question
does not appear.

* 4.

Name of input saved answer file [D:

<default>]:

SYSGEN displays this question only if you responded Yes to Question 3.
If the saved answer file used as input for Phase I exists SYSGEN uses
that file name as the default response for this question.
If you
selected the Standard Function System in Phase I, the default input
saved answer file is SGNSTAND.CMD.
Otherwise, there is no default
response.
If you have previously created a saved answer file having a file name
different from the default response, you may enter the name of that
file.
If the specified file does not exist, SYSGEN repeats Question 3.
If you enter a response other than the default and omit a
SYSGEN assumes the file type .CMD.

file

type,

If you are chaining to Phase II,
the response to this question
defaults to the response given for Question 7 in the Setup Section in
Phase I.
In this case, the question does not appear.

5-5

DETAILS OF SYSGEN PHASE II

SETUP (Cont.)
* s.

Name of output saved answer file [D:

<default>]

SYSGEN saves your responses to Phase II questions in an output
answer file.
This question allows you to name that file.

saved

The default name of the output saved answer file is the same as
response given for Question 9 of the Setup Section in Phase I.

the

Likewise, if you are chaining to Phase II,
the response to this
question defaults to the response given for Question 9 in the Setup
Section of Phase I.
In these cases the question does not appear.
If the name of the output saved answer file for Phase II is the same
as the name of the output saved answer file from Phase I, SYSGEN does
not create a new output saved answer file but appends your Phase II
responses to the existing saved answer file.
If you enter a response other than the default and omit a
SYSGEN assumes the file type .CMD.

file

type,

End-of-execution (EOX) breakpoints occur after every section in
II except for the system VMR section.

Phase

* 6.

Skip end-of-execution (EOX) breakpoints?

[Y/N]:

When SYSGEN stops at EOX breakpoints, you can verify that no errors
have occurred during the preceding operation.
If you are confident
that no errors will occur during execution, answer Yes to this
question and SYSGEN proceeds directly to subsequent sections without
stopping.
This question only appears if you are doing an actual SYSGEN
(for
example, you answered No to Question 3 in Phase I), and if you
specified that you are using an input saved answer file (for example,
you answered Yes to Question 7 in Phase I).
If you are chaining to Phase II and did not direct SYSGEN to inhibit
MCR commands, the response to this question defaults to the response
given for Question 13 in the Setup Section of Phase I.
In this case,
the question does not appear.

* 7.

Enter device for EXCPRV disk when it is ready (ddu:) [D:

default]

(S]:

To answer this question, enter the device mnemonic of the drive that
holds the privileged object files disk.
The default response is the
mnemonic of the device specified in response to Question 16 in the
Phase I Setup Section
(the device containing the Executive source
files).

5-6

DETAILS OF SYSGEN PHASE II

~CTI ID

~ ... I

This question appears only if you are using an RL01/RL02
kit.

tr,.. ... +\

ur \ V U I U · J

distribution

If you are chaining to Phase II from Phase I using an RL01/RL02
distribution kit, this question does not appear. Since the device
used in Phase I for the Executive and driver sources is currently
mounted and contains the files needed for Phase II, the response
defaults to that given for Question 16 in the Setup Section for Phase
I•

5-7

DETAILS OF SYSGEN PHASE I I

EXECUTABLE TASK-BUILD
5.3

EXECUTIVE TASK-BUILD SECTION

* 1.

List Executive map?

[Y/N]:

The Executive map lists the Executive global symbols and their
locations in memory.
These locations are used to lay out partitions.
If you are generating a mapped system, the map is probably not
necessary.
If you are generating an unmapped system, the map is
necessary for you to know where to start setting up your system
partitions.
If you respond Yes, SYSGEN prints or spools the
printer (if the system includes one) or terminal.

map

the

line

If you are generating an unmapped system, you must establish the
locations for the system partitions. Look at the Executive map for
the symbol $SYTOP. The value of $SYTOP indicates the last address
allocated to the Executive.
Partitions may start on any 32-word
boundary beyond this address.
Following the Executive task-build, SYSGEN displays a table
(on the
terminal)
that contains information on the default size and base
address of the system partitions.
The information in this table,
together with the value of $SYTOP, may assist you in establishing
partitions.
SYSGEN calculates the partition base addresses on the assumption that
$SYTOP does not exceed 40000(8). You can specify a base address other
than the default base address in the Privileged Task-Build Section.
NOTE
SYSGEN only lists RSXllM.MAP.
If you
selected the Executive commons, SYSGEN
does not list the Executive commons maps
(EXCOMl.MAP
and EXCOM2.MAP)
and the
loadable task loader map (LOR.MAP).

5-8

DETAILS OF SYSGEN PHASE II

LOADABLE DRIVER TASK-BUILD
5.4

LOADABLE DRIVER TASK-BUILD SECTION

This section provides details for SYSGEN processing of loadable driver
task-build command files.
The file SGNBLDDRV.CMD controls the task-building of loadable drivers
and also permits incorporation of loadable user-written drivers.
SYSGEN invokes this command file during Phase II when your system
includes loadable drivers or if you specified that you wish to include
a user-written driver.
Note that SGNBLDDRV.CMD can be invoked
directly from MCR (outside SYSGEN)
to aid in task-building (or
re-task-building) drivers.
If you invoke SGNBLDDRV.CMD outside of SYSGEN, you must answer
Questions 1, 2, and 3.
If SYSGEN invokes SGNBLDDRV.CMD, these first
three questions do not appear.

* 1.

In what UIC is SGNPARM.CMD if not <uic> ?

[S]:

Enter the UIC containing the file SGNPARM.CMD. SYSGEN replaces <uic>
with the UIC from which you invoked SGNBLDDRV.CMD.
Enter a different
UIC to override this default, otherwise, press the RETURN key.
SGNPARM.CMD supplies Indirect symbol definitions from Phase I that are
relevant to Phase II processing.
It provides a means of communicating
between Phase I and the other phases of SYSGEN. SYSGEN creates this
file in the UIC corresponding to the UIC from which you invoked Phase
I of SYSGEN.

* 2.

Enter device for <label> disk when it is ready (ddu:)

(D:

<default>]

(S] :

distribution

If you are using an RLOl/02 distribution kit, SYSGEN replaces
with EXCPRV.

<label>

The default response (<default>) is the response entered for Question
16 (the Executive source disk) of the Setup Section in Phase I.

* 3.

Enter map device (ddo:)

[D:

NL:]:

Map listings are usually of little use if your target system is
mapped.
The map listings are more useful if your target system is
unmapped and you need to determine the size of your tasks.

5-9

DETAILS OF SYSGEN PHASE I I

LOADABLE DRIVER TASK-BUILD (Cont.)
If you want the maps, specify the desired output device as your
response.
If you specify a device other than LP:, SY:, LB:, TI:, TT:,
or NL:, the device must be mounted (using the MCR MOUNT command)
and
the UFO [1,34] for mapped systems or [l,30] for unmapped systems must
exist on the volume.
The default output device for the task maps is NL:

* 4.

(the null device).

Build all selected loadable drivers into DRVPAR?

[Y/N]:

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 loadable drivers you
in Phase I for partition DRVPAR.

selected

If you enter No, SYSGEN prompts for the drivers you want to
asking Question 5 of this section.

build

* S.

Driver 2-character device mnemonic [S]:

To answer this question, enter a 2-character device mnemonic for any
loadable driver
(including user-written drivers) you want to build.
Enter only one device mnemonic each time this question appears.
After
each response to this question, SYSGEN asks Question 6. Answer
Question 6 by entering the partition name into which you wish to build
each driver.
If your target system is unmapped, SYSGEN also asks for
the base address of each partition name in Question 7.
This sequence of two or three questions (three if your target system
is unmapped) appears for each loadable driver you want to build. When
you have entered all the driver names you intend to include in your
target system
(and the appropriate partition information), press the
RETURN key the next time Question 5 appears. SYSGEN then proceeds to
the Privileged Task-Build Section if SGNBLDDRV.CMD was invoked during
SYSGEN Phase II.
If SGNBLDDRV.CMD was
invoked outside SYSGEN,
it
exits at this point.
If you are generating an unmapped system, you should successively
task-build each of the loadable drivers twice.
For example, in the
first pass, you might task-build the DB, DK, DL, and TT drivers.
In
the second pass, task-build them again.
In the first pass, task-build the drivers using a temporary base
address for
the driver partition
(see Question 7).
The temporary
partition base address should be less than 28K and should begin on a
32-word boundary.
After all the drivers are successfully
through Question 7) r exit from Phase II:

built

the

first

time

(up

For the second pass, invoke Phase II again to look at the driver maps
(Question 3) to determine the size (length) of each driver and then to
task-build them again. When you reinvoke Phase II, you should not use
an input saved answer file (Setup Section, Question 3).

5-10

DETAILS OF SYSGEN PHASE I I

LOADABLE DRIVER TASK-BUILD (Cont.)
You can determine the size of a driver by locating the line 11 Task
address limits:" on the driver map and subtracting the first number in
the line from the second number in the line.
Then round the result up
to the nearest 64(10) or 100(8) number.
Using the size of each loadable driver, with information in your
terminal
output that follows the Executive task-build you can
establish the placement of each loadable driver partition.
Once you
have made these calculations, begin your second pass at task-building
the same drivers using the correct partition base address.
NOTE
TT is the mnemonic of the terminal
interfaces (YH, YJ, YL, and YZ).
If you selected the full-duplex
terminal driver in Phase I,
the
full-duplex terminal driver has already been task-built. Do not enter
the full-duplex terminal driver as part of your response to this
question.
This question appears if your target system is unmapped, if you have a
mapped target system in which all drivers are not to be built for
DRVPAR (that is, if you answered No to Question 4 in this section), or
if your target system includes any loadable user-written drivers.

* 6.

Driver partition name [D:

<dev>PAR]

[S]:

The default partition for mapped systems is DRVPAR.
The default partition for unmapped systems is <dev>PAR where <dev>
the 2-character device mnemonic specified in Question 5.

For unmapped systems, consider building the system disk driver for the
partition that corresponds to the two-character device mnemonic (for
example, DBPAR for RP04/05/06).
This is also recommended for other
drivers that should run in their own partition (for example, TTPAR).
A suggested partition name for less frequently used drivers is DRVPAR.
You can load a driver as you need it (after unloading the driver that
currently occupies the DRVPAR partition).

* 7.

<dev>PAR's partition base address in 32-word blocks [S]:

This question appears for unmapped systems only.
Enter the base address of the specified partition.
The base address is required during the dynamic creation of the driver
task-build command files.
The base address of the partition must
start on a 32-word boundary.

5-11

DETAILS OF SYSGEN PHASE II

PRIVILEGED TASK-BUILD
5.5

PRIVILEGED TASK-BUILD SECTION

* 1.

Map device for privileged tasks (dda:)

[D:NL:]

Usually, these maps are of little use if your target system is mapped.
The default response directs the maps to the null device.
The maps
are more useful if your target system is unmapped and you need 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:, TT:, or NL:, the device must be
mounted (using the MCR MOUNT command) and a UFO entry of
[1,30]
for
unmapped systems or
[1,34]
for mapped systems must exist on the
volume.

* 2.

GEN's base address in 32-word blocks (0 D:400]:

This question appears only for unmapped systems.
The partition base address of GEN is necessary during the dynamic
creation of task-build .CMD files for those RSX-llM tasks built to run
in GEN.
SYSGEN uses GEN's partition base address in the dynamically
created command file SYSVMR.CMD.
The base address of GEN starts on a 32(10) word boundary.
The default of 400
is based on the assumption that the highest
location in memory allocated to the Executive does not exceed 40000,
and that you intend to use the nonprivileged baseline tasks as they
were built (that is, to run in the GEN partition starting at location
40000) •
If you intend to include nonprivileged, DIGITAL-supplied RSX-llM tasks
your target system you must task-build those tasks during Phase

III.

* 3.

SYSPAR's base address in 32-word blocks [O D:<default>]:

This question appears only for unmapped systems.
The partition base address of SYSPAR is necessary durinq the dynamic
creation of task-build .CMD files for those RSX-llM tasks built to run
in SYSPAR.
SYSGEN also uses SYSPAR's base address in the dynamically
created command file SYSVMR.CMD.
If the target system has 24K words or more of memory,
the default
(<default>) is 1300.
This default is based on the assumption that you
selected the default of 400 32-word blocks for the GEN partition, and
that you plan to include a i4K task partition (PARi4Kj of which GEN is
an 8K subpartition.

5-12

DETAILS OF SYSGEN PHASE I I

PRIVILEGED TASK-BUILD (Cont.)
If the target system has less than 24K words of memory the default is
1000.
This default is based on the assumption that you have selected
the default of 400 32-word blocks for the GEN partition, and that GEN
is an SK partition.
The base address of SYSPAR starts on a 32(10) word boundary.

* 4.

SPLPAR's base address in 32-word blocks [0 D:l300]

This question appears for unmapped systems
selected the serial despooler
(Question
Section of Phase I) •

only,
7 in

and only if you
the System Options

The partition base address of SPLPAR is necessary during the dynamic
creation of PRTBLD.CMD.
SYSGEN uses SPLPAR's base address in the
dynamically created command file SYSVMR.CMD.
If you
The base address of SPLPAR starts on a 32(10) word boundary.
selected FCPMIN, the default response for this question can be
calculated by adding 100 to the default base address of SYSPAR.
If you selected FCPSML, the default response for this question can
calculated by adding 120 to the default of Question 3 above.

* S.

Pause to edit any task build .CMD or .ODL files?

[Y/N]:

If you answer Yes to this question, SYSGEN pauses to allow you to
selectively edit the task-build
.CMD or
.ODL files. This is the
logical place in SYSGEN to alter any task-build parameters for tasks
built during Phase II, if you need to do so.
If you choose to edit
any .CMD files, the information you require to edit a given file is
contained in comments within that file.

* 6.

Delete task-build .CMD and .ODL files after task-building?

[Y/N]:

It is usually not necessary to keep the .CMD and .ODL files after they
have been used to build their respective tasks.
They can be easily
recreated by reinvoking SYSGEN3.CMD. You can free the disk space
occupied by these files by answering Yes to this question.

5-13

DETAILS OF SYSGEN PHASE II

SYSTEM VMR
5.6

SYSTEM VMR SECTION

* 1.

Edit SYSVMR.CMD?

[Y/N]:

This question permits you to edit the SYSVMR.CMD file.
SYSGEN defaults all terminal lines to 110 baud (unknown terminal type
and lowercase input disabled).
Even if modem support is included, all
the lines are local and autobaud detection is disabled.
These
parameters can be changed to suit your particular configuration by
answering Yes when SYSGEN asks if you want to edit SYSVMR.CMD.
Include in
SYSVMR
the
appropriate
commands,
such
as
SET
/REMOTE=TT3:300 or SET /VT100=TT5:, as desired.
This ensures that
your terminal lines are set properly when the system is booted. These
commands may be entered directly to VMR at any time after SYSGEN.
They may also be entered to MCR.
However, in that case, their action
is lost the next time you bootstrap the system.
NOTE
VMR may
output
several
diagnostic
(*DIAG*) messages during its operation.
Diagnostic messages may be
ignored.
(See Example 5-1 at the end of this
chapter for sample messages.)
SYSGEN Phase II creates the file SYSVMR.CMD to create the partition
structure,
install tasks and commons, and load loadable drivers.
These actions prepare the system image file, created during Phase II,
for actual execution.
For mapped systems, it is not usually necessary to edit this file;
although, without editing,
it may not produce an optimal system on
small configurations. SYSVMR.CMD typically produces a valid mapped
system image. Figure 5-2 depicts a mapped system partition structure
that results from executing SYSVMR.CMD.
For mapped systems, SYSVMR:
•

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 asterisk
(*) to the specific desired value.
See the SET /POOL command in Chapter 10 on VMR commands in the
RSX-llM/M-PLUS System Mangement Guide.

•

If you selected the loadable loader, creates the
LDRPAR and installs and fixes the loader in it.

5-14

partition

DETAILS OF SYSGEN PHASE II

SYSTEM VMR (Cont.)

DEV common
(optional)

GEN

FCPPAR
(optional)

SYS PAR

DRVPAR
(optional)

TTPAR
(optional)
LDRPAR
(optional)

Executive
ZK-316-81

Figure 5-2 Partition Structure on Mapped Systems
•

•

If you selected support for the Executive commons in Phase I,
establishes
them in the system image in the following
sequence:
1.

A 4K partition called EXCOMl is created.

The first Executive common, EXCOMl.TSK,
is installed in
that partition.
As the common is installed, the EXCOMl
partition is automatically reduced in size to match the
size of EXCOMl.TSK.

A 4K partition called EXCOM2 is created.

EXCOM2.TSK is installed in that partition. As the common
is installed,
EXCOM2 is automatically reduced in size to
match the size of EXCOM2.TSK.

If you selected the full-duplex terminal driver, creates
partition TTPAR and loads the terminal driver into it. By
default, SYSGEN sets the size of TTPAR to BK words, but it can
usually be made smaller.

5-15

DETAILS OF SYSGEN PHASE I I

SYSTEM VMR (Cont.)
TTPAR contains code plus a private buffer pool, which is
allocated in 20-word blocks for type-ahead buffers, UCB
extensions, and I/O buffers.
Since the number of I/O
buffers required depends upon both system activity and the
length of the I/O requests, an exact sizing guideline
cannot
be
given.
However, a
rough algorithm for
determining the size of TTPAR is:
P = C + ( 20

* T) + ( 60 * A)

where:
P is the size of TTPAR in decimal words
C is the code size of the driver
(from
IMAGE SIZE" in [11,34] TTDRV.MAP)

the

line

"TASK

T is the number of terminals in the system
A is the average number of I/O
given time
•

requests

pending

any

If you selected loadable drivers, creates partition DRVPAR
and loads all loadable drivers built during Phase II into
it.
If you do not want to load all drivers, edit
SYSVMR.CMD and delete the LOAD command for each driver you
wish to exclude.
NOTE
SYSGEN uses wildcards (*) to create DRVPAR's size
as the sum total of all drivers loaded during the
execution of SYSVMR.CMD.
If you wish to allow
space
for other drivers, edit the partition
statement and specify sufficient space.
(You need
the driver maps to determine what size DRVPAR
should be.)
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.)

•

Creates partition SYSPAR and, if you selected FCPMIN or
FCPSML,
installs the respective FCP into it.
The length
of SYSPAR is 10100 bytes for a system with FCPMIN and
120000 bytes for a system with FCPSML.
The length of
SYSPAR for nonmultiuser systems with full-duplex terminal
driver support is 11700 bytes.
The length of SYSPAR for
all other cases is 10100 bytes.

If you selected an FCP other than FCPMIN or FCPSML creates
partition FCPPAR

•

Creates partition GEN (from the end of last
top of memory) .

5-16

partition

DETAILS OF SYSGEN PHASE I I

SYSTEM VMR {Cont.)

•

Installs tasks built during Phase II.

•

If you selected direct access to device registers for
IP11/IP300,
ICS/ICR, UDCll, or DSS/DRS devices, creates
the respective device common, which overmaps the I/O page.

For unmapped systems, it is not possible for SYSVMR.CMD to create an
optimal partition structure;
you must edit SYSVMR.CMD. Figure 5-3
depicts an unmapped 16K to 24K system that results from executing
SYSVMR.CMD.
In an unmapped 16-24K system, the lack of adequate memory
prevents SYSMVR.CMD from creating PAR14K (the partition used by MAC,
TKB, and ICP). Note that for unmapped systems, SYSVMR does not create
driver partitions.

devPAR
SPLPAR
(optional)

1100, 1120

SYS PAR

1000
GEN

400

------'o
Executive

ZK-318-81

Figure 5-3 Partition Structure on Unmapped 16K through 24K Systems
For unmapped 16K to 24K systems, SYSVMR:
partition GEN.
• Creates
address specified as

The base address of GEN is the base
your response to Question 2 of the
Privileged Task-Build Section. The length of GEN is always
40000 bytes.

•

Creates partition SYSPAR. The base address of SYSPAR is the
base address specified as your response to Question 3 of the
Privileged Task-Build Section. The length of SYSPAR is 10000
bytes for a system with FCPMIN and 12000 bytes for a system
with FCPSML.

•

If you selected PRT, creates SPLPAR.
The base address of
SPLPAR is the base address specified as the response to
Question 4 of the Privileged Task-Build Section.
The length
of SPLPAR is 10400 bytes.

•

Installs tasks built during Phase II.

•

If you selected direct

access to device registers for an
IP11/IP300,
ICS/ICR, UDCll, or DSS/DRS device, creates the
respective device common (which overmaps the I/O page).

5-17

DETAILS OF SYSGEN PHASE I I

SYSTEM VMR (Cont.)
Figure 5-4 depicts an unmapped 24K through 28K system that results
from executing SYSVMR.CMD.
Note that for unmapped systems, SYSVMR
does not create driver partitions.

devPAR
SPLPAR
(optional)

1400,1420

SYS PAR
1300
PAR14K

1000
GEN

400

Executive
0
ZK-317-81

Figure 5-4 Partition Structure on Unmapped 24K through 28K Systems
or unmapped 24K through 28K systems, SYSVMR:
•

Creates partition PAR14K. The base address of GEN and PAR14K
is the base address specified as your response to Question 2
of the Privileged Task-Build Section. The length of GEN is
always 40000 bytes;
the length of PAR14K is always 70000
bytes.

Creates partition SYSPAR. The base address of SYSPAR is the
• base
address specified as your response to Question 3 of the
Privileged Task-Build Section. The length of SYSPAR is 1000
bytes for a system with FCPMIN and 1200 bytes for a system
with FCPSML.
•

If you selected PRT, creates SPLPAR.
The base address of
SPLPAR is the base address specified as the response to
Question 4 of the Privileged Task-Build Section.
The length
of SPLPAR is 10400 bytes.

•

Installs tasks built during Phase II.

•

If you selected direct access to device registers for an
IP11/IP300,
ICS/ICR, UDCll, or DSS/DRS device, creates the
respective device common (which overmaps the I/O page).

5-18

DETAILS OF SYSGEN PHASE II

SYSTEM VMR {Cont.)
5.6.1

Invoking VMR from an On-line Host System

If you are running SYSGEN on an on-line system, SYSGEN completes Phase
II execution without invoking VMR (that is, SYSGEN does not invoke the
command file SYSVMR.CMD). The reason for this is that you must use
V4.l of VMR and, in an on-line environment, SYSGEN cannot tell which
version of VMR is available on your on-line system.
Therefore, if you invoked SYSGEN on an on-line system, you must:
1.

Assign the logical device LB:

to the baseline disk

Set your UIC to the target UIC (that is,
systems, or [1,50] for unmapped systems)

Install VMR V4.l

Invoke VMR and use SYSVMR.CMD

[1,54]

for

mapped

You may accomplish this by entering the following commands after Phase
II completes execution:
>ASN (ddu:)=LB:
>SET /UIC=[l,54]
>INS ddu: $VMR
> VMR @SYSVMR
where ddu:

5.6.2

is the device mnemonic of the baseline disk.

Using VMR to Create Partitions for RMS-11 Libraries

If you want to create the partitions for the RMS-11 resident
library(s), while you are in VMR, use VMR SET commands.
The following
VMR SET commands can be used as a guide, but you must replace the word
"base" with the octal address of the base of the partition and you
must replace the word "size" with the size of the resident library.
Sizes of the resident libraries can be determined from the .MAP files
in UFO [1,34], or from the sample VMR SET commands contained in
[l,2]STARTUP.CMD.
•

Create the partition RMSRES.
Note that the size of this
partition
depends
on
whether
you intend to use the
full-function RMSRES library, or the subset library RMSRESSUB
(which
only
supports
sequential
and
relative
file
organizations).
SET /MAIN=RMSRES:base:size:COM

•

If you want to use the RMSDAP resident library to access
RMS-11 files on remote nodes, create the partition DAPRES.
SET /MAIN=DAPRES:base:size:COM

5-19

DETAILS OF SYSGEN PHASE I I
Example 5-1

Annotated Terminal Output from SYSGEN Phase II

>SET /UIC
UIC=[200,200J
>@SYSGEN2t»
>; RSX-11M V4.1 BL35-A System Generation Phase II -- version 2+0
>; 21-FEB-83 17:30:36
>*

1. UIC of SGNPARM.CMD if not [200,200J [SJ:

>; RL01/RL02 distribution kit SYSGEN version 2.0 for RSX-11M BL35-A

>; Continuation from SYSGEN PHASE I done on 21-FEB-83 at 17:25:46
>; SYSGEN assumes that the map disk is already mounted in DLl: with
>; UFD [1,34J,
>*
>*

2. Do YOU want to inhibit execution of MCR commands CPREPGENJ? [Y/NJ: Y
3. Use an inPut saved answer file? [Y/NJ: N
5, Name of output saved answer file [D: DL0:[200,200JSYSSAUED.CMD;2J [SJ:

>; Phase II output saved answers created in file DL0:[200,200JSYSSAVED.CMD;2
>* 7. Enter device for EXCPRV disk when it is ready Cddu:> [D: DLl:J [SJ: DLll
>MOU DLl:EXCPRV

>; Library build
>; Executive task build
>*

1. List Executive maP? [Y/NJ: N

>; SYstem imase creation
>; Full duplex terminal driver task build
); Loadable driver task build
>*

4. Build all selected loadable drivers into DRVPAR? [Y/NJ: Y

>; Common block task build

>; Build the ANSLIB flavor of the FCS resident library common
>* 11. Pause to edit any task build .CHD or .ODL files? [Y/NJ: N

>; Creatins the task build .CMD and .ODL files in DL1:[1,24J
>; Privilesed task build
>;

Note that the followinS tasks will be built for your sYstem:

BOO
MCR
F11MSG
PMD
SHUT UP
>*
>*

OMO
DCL
MTAACP
RMD
ACS

FCPMDL
MOU
SAV
SHF
ERRLOG

ICP
QMG

TKTN
ACNT
ELI

INI
QHGCLI
UFD
BYE
RCT

INS
QHGPRT
LOA
HELBRO

PMT
LPP
UNL

1. MaP device for PrivileSed tasks Cddu:J [D: NL:J [SJ:
6. Delete task build +CMD and .ODL files after buildins? [Y/NJ: Y

>; Creatins the task build .CHD and ,ODL files in DL1:[1,24J
); 8Ystem VMR
>*

1. Edit SYSVMR.CMD? [Y/NJ: N

(continued on next page)

5-20

DETAILS OF SYSGEN PHASE II
Example 5-1 (Cont.)

Annotated Terminal Output from SYSGEN Phase II

>; An alternate version of SYSLIB.OLBr the system obJect library, was
>; created to Provide support for ANSI mastaPe/FCS bis-bufferins <which
}; you selected in Phase IJ.
You may want to rebuild DMPr FLXr PIPr and
>; VFY in Phase III to use ANSLIB.OLB. Noter however, buildins tasks with
>; ANSLIB.OLB causes an increase in the size of tasks as compared to the
>; SYSLIB.OLB version of the tasks.
); A memor!:I resident library of FCS ro•Jtines (which YOU selected in Phase I )
>; was built to help reduce task memory reauirements. You may want to rebuild
>; tasks in Phase III to link to the FCS resident library.
:::-;
); Because of the lack of adeauate disk space on the RSXM35 diskr the tasks
>; BADr BRUr CDAr CMPr CRFr DMPr FMTr IOX, PATr VFYr and ZAP were not
>; included in the baseline system.
If YOU want these tasks in your tarset
); swstemr thew should be built in Phase III.

>;
>; When SYSGEN finishes, boot in your tarset sYstemr and save the system with a
>; bootstrap. For example:

>;
>;

>BOO [1r54JRSX11M
XDT: 35-A

XDT>G
RSX11M V4.1 BL35-A

>;
>;
>;
>;

>TIM 11:23 14-0CT-81
>SAU /WB

>;
>;
>;
>r
>;

RSX11M V4+1 BL35-A
>RED DU=SY:
>RED DU=LB:
>MOU DL!RSXM35

128.K

MAPPED

>;
>;

>;
>;
>; End of SYSGEN Phase II at 17:40:03 on 21-FEB-83
>@ <EOF>
>@~:;YSGEN2

>;
>; RSX-11M V4.1 BL35-A System Generation Phase II -- version 2.0

>; 21-FEB-83 17:40:24
>;

1. UIC of SGNPARM.CMD if not [200r200J CSJ:

>; RL01/RL02 distribution kit SYSGEN version 2.0 for RSX-11M BL35-A

); Continuation from SYSGEN PHASE I done on 21-FEB-83 at 17!25:46
)•,

); SYSGEN assumes that the maP disk is already mounted in DL1: with
>; UFD [1,34J,

>;
>;

>*
>*

2. Do You want to inhibit execution of MCR commands CPREPGEN>? CY/NJ: N
3+ Use an inF'•Jt saved answer file? CY/NJ! Yf)
4+ Name of inPut saved answer file CD: DLO:C200,200JSYSSAVED,CMD;1J [SJ: SYSSAVED,CMD;2

>;
>;
>;
>;
>;

Phase II inPut saved answers
created on 21-FEB-83 at 17!31!17
bY SYSGEN version 2.0
are from file DL0![200r200JSYSSAVED.CMD;2

5. Name of output saved answer file [[I! DL0![200r200JSYSSAVED.CMD;2J [SJ!

Phase II output saved answers created in file DL0![200,200JSYSSAVED+CMD;2

** 6.7, SkiP
end of execution breakpoints? [Y/NJ: Y
Enter device for EXCPRV disk when it is ready (ddu:> CD: Dll!J [SJ: DLl!
MOU DL1:EXCPRlJ
LOA LP:

(continued on next page)

5-21

DETAILS OF SYSGEN PHASE I I

Example 5-1 (Cont.)
>INS
>INS
>INS
>INS
>ASN
>PIP

Annotated Terminal Output from SYSGEN Phase II

$PIP
$EDI
$LBF:
SY:E1,54JTKB.TSK;l/TASK= ••• TKL
SY: ==LB:
/FF:

DLO: has 14544. blocks free, 5936. blocks used out of 20480.
Largest contiguous space = 9578. blocks
1395. file headers are free, 141. headers used out of 1536.

>; Start of
>;

librar~

build at 17!41!49 on 21-FEB-83

>SET /UIC=E1 d J
>PIP LB!ANSLIB.OLB/NV=LB!SYSLIB.OLB
>LBR LB:ANSLIB/RP=DL1:FCSMTA
Module "ANSPAD" rePlaced
Module "ASSLUN" rePlaced
Module "BIGBUF" rePlaced
replaced

Module "CLOSE

Module "CONTRL" replaced
Module "CREATE• replaced
Module "DIRECT' replaced
Mod1.1 le 'FCSTYP" replaced
ModulEc' "GET
Module

"GETSll

Module "OPEN
Module "OPENR
Module "OPFifl
Mod1Jle "OPFNB

• rePlaced

.
.
.

replaced
replaced
re Placed
rePlaced
rePlaced

Module "F'ARSFN' rePlaced
Module

POINT

rePlaced

Module "PUT

re? laced

Module "PUTSQ

rePlaced

Mod1J!E! 'RDWAIT" replaced
Mod1Jle "RETADR" rePlaced
Module "RSTFDB" re? laced
Mod1Jle 'RWBLK

re? laced

Module "RWLONG" rePlaced
Module "WATSET" rer:• laced
Module "WTWAIT" replaced
Module 'WTWATD" replaced
>SET /UIC=[1,24J
>PIP DL1:MCR.OBJ/NV/NM=[i2,24J*,OBJ
>LBR DL1!MCR/RP=DL1:MCR,OBJ
Module 'DV20V • rePlaced

(continued on next page)

5-22

DETAILS OF SYSGEH PHASE I I
Example 5-1 (Cont.)
Module "SPSOV

Annotated Terminal Output from SYSGEN Phase II

rePlaced
replaced

Module "STSUB
Module ·sx1ov

replaced

Module ·sx2ov

replaced

Module "SX30V

replaced

Module "SX40V

replaced

>PIP sv:r12r24J*.DBJ;*/DE/NM
>;
>; End of library build at 17:53:19 on 21-FEB-83

>;
>;
>; Start of Executive task build at 17:53:19 on 21-FEB-83
>TKL @LB:RSXBLD
>; End of Executive task build at 17!57!53 on 21-FEB-83
>; Start of system imase creation at 17!57!54 on 21-FEB-83
>SET /UIC=[1r54J
>PIP RSX11M.SYS/CO/NV/BL!498.=RSX11M.TSK

>; End of sYstem imase creation at 17:58:01 on 21-FEB-83
>; Start of full duPlex terminal driver task build at 17!58:02 on 21-FEB-83
>SET /UIC=[1,24J
>TKL @LB:TTDRVBLD
>; End of full duplex terminal driver task build at 17:59:01 on 21-FEB-83
>;

); Start of loadable driver task build at 17:59!02 on 21-FEB-83
>TKL @Dll!DDDRVBLD
>TKL @DLl:DLDRVBLD
>TKL @DLl:DUDRVBLD
>TKL @DL1:LPDRVBLD
>TKL @Dll!MSDRVBLD
>REM TKL
>;
>; End of loadable driver task build at 18!01!49 on 21-FEB-83
);
);

>; Start of common block task build at 18!01:50 on 21-FEB-83

>; Build the ANSLIB flavor of the FCS resident library common
>;
>; Creatins the task build .CMD and .ODL files in DL1![1,24J
>INS SY![1r54JTKB.rsk;1/TASK= ••• TKt
>TKL @DL1:[1r24JFCSRS1BLD.CMD
>REM TKL
>; End of common block task build at 18:04!03 on 21-FEB-83
·/....
r

>; Start of Privilesed task build at 18!04!03 on 21-FEB-83
Note that the followinS tasks will be built for your SYStem:

BOO
MCR
F11MSG
PMD
SHUTUP

DMD
DCL
MTAACP
RMD
ACS

FCPMDL
MOU
SAV
SHF
ERRLOG

ICP
QMG
TKTN
ACNT
ELI

INI
QMGCLI
UFO
BYE
RCT

INS
QMGPRT
LOA
HELBRO

PMT
LPP
UNL

(continued on next page)

5-23

DETAILS OF SYSGEN PHASE I I
Example 5-1 (Cont.)

Annotated Terminal Output from SYSGEN Phase II

); It is assumed that [1,1JFCSRES.STB is an ANSLIB version of the FCS
>; reside~t librar~

.....,

>; Creatins the task build .CMD and .ODL files in DL1:[1,24J
>INS SY:[1,S4JTKB.TSK;1/TASK= ••• TKL
>TKL @DL1:[1,24JBOOBLD.CMD
>TKL @DL1:[1,24JDMOBLD.CMD
>TKL @DL1:[1,24JFCPMDLBLD.CMD
>TKL @DL1:[1r24JICPBLD.CMD
>TKL @DL1:[1,24JINIBLD.CMD
>TKL @DL1:[1r24JINSBLD.CMD
>TKC @DL1![1,24JPMTBLD.CMD
>TKL @DL1![1r24JMCMBLD.CMD
>TKL @DL1:[1,24JDCLBLD.CMD
>TKL @DL1:[1,24JMOUBLD.CMD
>TKL @DL1![1r24JQMGRESBLD.CMD
>TKL @DL1![1r24JQCLRESBLD.CMD
>TKL @DL1![1r24JQPRBLD.CMD
>TKL @DL1:[1r24JLPPRESBLD.CMD
>TKL @DL1:[1r24JF11MSGBLD.CMD
>TKL @DL1![1r24JMTABLD.CMD
>TKL @DL1:[1,24JSAVBLD.CMD
>TKL @DL1:[1,24JTKNBLD.CMD
>TKL @DL1![1,24JUFDBLD.CMD
>TKL @DL1:[1,24JLOABLD.CMD
>TKL @DL1![1,24JUNLRESBLD.CMD
>TKL @DL1![1,24JPMDRESBLD.CMD
>TKL @DL1:[1;24JRMDBLD+CMD
>TKL @DL1:[1,24JSHFBLD.CMD
>TKL @DL1![1r24JACNRESBLD+CMD
>TKL @DL1![1,24JBYEBLD.CMD
>TKL @DL1![1,24JHELRESBLD.CMD
>TKL @DL1![1r24JBROBLD.CMD
>TKL @DL1:[1,24JSHUBLD.CMD
>TKL @DL1![1,24JACSRESBLD.CMD
>TKL @DL1![1,24JERLBLD.CMD
>TKL @DL1:[1r24JELIRESBLD.CMD
>TKL @DL1![1r24JRCTBLD.CMD
>REM TKL
>; End of PrivileSed task build at 19:20:10 on 21-FEB-83

>;
_.:·,

); Delete the task build .CMD and .ODL files
>PIP DL1:[1,24JBOOBLD.CMD;O/DE/NM,BOOBLD.ODL;o
>PIP DL1![1,24JDMOBLD.CMD;O/DE/NM,DMOBLD.ODL;O
>PIP DL1:[1,24JFCPMDLBLD.CMD;o/DE/NMrFCPMDLBLD.ODL;o
>PIP DL1![1124JICPBLD.CMD;O/DE/NMrICPBLD.ODL;o
>PIP DL1![1r24JINIBLD.CMD;O/DE/NMrINIBLD.ODL;O
>PIP DL1![1,24JINSBLD.CMD;O/DE/NM,INSBLD.ODL;o
>PIP DL1![1,24JPMTBLD.CMD;O/DE/NM,PMTBLD.ODL;O
>PIP DL1![1r24JMCMBLD.CMD;O/DE/NMrMCMBLD.ODL;O
>PIP DL1![1,24JDCLBLD.CMD;O/DE/NM,DCLBLD.ODL;o
>PIP DL1![1124JMOUBLD.CMD;O/DE/NM1MOUBLD.ODL;O
>PIP DL1:[1,24JQMGRESBLD.CMD;O/DE/NM~QMGRESBLD.ODL~O
>PIP DL1![1,24JQCLRESBLD.CMD;o/DE/NM,QCLRESBLD.ODL;o
>PIP DL1:[1,24JQPRBLD.CMD;O/DE/NM1QPRBLD.ODL;O
>PIP DL1![1,24JLPPRESBLD.CMD;O/DE/NM,LPPRESBLD.ODL;o
>PIP DL1![1,24JF11MSGBLD.CMD;o/DE/NM,F11MSGBLD.ODL;o
>PIP DL1![1,24JMTABLD.CMD;O/DE/NM1MTABLD.ODL;O
>PIP DL1![1,24JSAVBLD.CMD;O/DE/NM,SAVBLD+ODL;o
>PIP DL1![1r24JTKNBLD.CMD;O/DE/NM,TKNBLD.ODL;o
>PIP DL1:r1,24JUFDBLD.CMD;O/DE/NM,UFDBLD.ODL;o
>PIP DL1![lr24JLOABLD.CMD;O/DE/NM,LOABLD.ODL;o
>PIP DL1![1,24JUNLRESBLD.CMD;Q/DE/NM1UNLRESBLD+DDL~O
>PIP DL1:r1,24JPMDRESBLD.CMD;o/DE/NMrPMDRESBLD+ODL;o
>PIP DL1:c1r24JRMDBLD.CMD;O/DE/NM1RMDBLD+ODL;o
>PIP DL1![1f24JSHFBLD+CMD;O/DE/NM,SHFBLD.ODL;Q
>PIP DL1l[1r24JACNRESBLD,CMD;Q/DE/NM1ACNRESBLD.ODL;O
f,...nn+-;
\ ..... ..., ........... n11c.rl
A.. __ _

5-24

on next

DETAILS OF SYSGEN PHASE II
Example 5-1 (Cont.)
~PIP

>PIP
>PIP
>PIP
>PIP
>PIP
>PIP
>PIP

Annotated Terminal Output from SYSGEN Phase II

DL1:r1.24JBYEBLD.CMDiO/DE/NMrBYEBLD.ODLiO
DL1!C1r24JHELRESBLD.CMD;O/DE/NMrHELRESBLD.ODL;o
DL1![1r24JBROBLD.CMDiO/DE/NMtBROBLD.ODLiO
DL1![1,24JSHUBLD,CMDiO/DE/NMrSHUBLD.ODLiO
DL1![1r24JACSRESBLD.CMD;O/DE/NMrACSRESBLD.ODLiO
DL1![1r24JERLBLD.CMDiO/DE/NMtERLBLD.ODLiO
DL1![1,24JELIRESBLD.CMDiO/DE/NM,ELIRESBLD.ODLiO
DL1![1,24JRCTBLD.CMDiO/DE/NM,RCTBLD.ODLiO

); Start of sYstem VMR at 19!29!35 on 21-FEB-83

>SET /UIC=C1r54J
>i

>INS SY!$B00i-1
>INS SY!$VMRi-1
>ASN SY!=LB!
>VMR @SYSVMF:
VMR -- *DIAG*-Partition reduced to executive corr1mon size 0
INS EXCOM1
VMR -- *DIAG*-Partition reduced to executive common size
INS EXCOM2
VMR -- *DIAG*-Loadable driver lar~er than 4K
LOA TT:
VMR -- *DIAG*-Installed tasks may no lon~er fit in Partition
SET /TOP=DRVPAR:-*
POOL=1200!9154.!09154.
EXCOMl 117734 00120000 00014600 MAIN COM~
EXCOM2 117670 00134600 00006400 MAIN COM
LDRPAR 117624 00143200 00002600 MAIN TASK
TTPAR 117260 00146000 00040000 MAIN TASK
DRVPAR 116734 00206000 00025700 MAIN SYS
116670 00206000 00003700 SUB DRIVER - DD!
116570 00211700 00002300 SUB DRIVER - DL!
116470 00214200 00012100 SUB DRIVER - DU!
116370 00226300 00001100 SUB DRIVER - LP!
116270 00227400 00004300 SUB DRIVER - MS!
SYSPAR 116170 00233700 00010100 MAIN TASK
FCSRES 116124 00244000 00031700 MAIN COM
FCPPAR 116060 00275700 00024000 MAIN SYS
GEN
116014 00321700 00456100 MAIN SYS
LDR ••• 13.02 117510 LDRPAR 248. 00002600 LBO -00012107 FIXED
TKTN
04.8
111444 SYSPAR 248. 00010100 LBO -00015237
••• RMD 2.0
114770 GEN
225. 00027100 LBO -00016670
F11MSG V0012 114060 GEN
200. 00005600 LBO -00015214
MTAACP 0013
113744 GEN
200. 00014700 LBO -00016505
••• DMO 03.01 114424 GEN
160. 00014600 LBO -00014272
MCR ••• 3.01
112720 SYSPAR 160, 00010100 LBO -00015056
••• DCL 02
112604 GEN
160. 00040000 LBO -00015522
••• MOU 2503
112124 GEN
160. 00037700 LBO -00015102
••• MCR 2.01
111560 GEN
160. 00020000 LBO -00015277
F11ACP 0402
115700 FCPPAR 149, 00024000 LBO -00014335
ERRLOG V2.1
114310 GEN
148. 00040000 LBO -00017251
PMT ••• 01.52 113264 GEN
148. 00006300 LBO -00015034
PMD ••• 07.2
113150 GEN
140. 00015700 LBO -00016246
SHF ••• 5.08
111674 SYSPAR 105. 00010100 LBO -00016467
••• INS 7.03
113400 GEN
100. 00034500 LBO -00014542
••• SAV 3.1
112010 GEN
100. 00033000 LBO -00016374
,,,UFD V0412 111330 GEN
100. 00005700 LBO -00015247
RCT ••• 2.02
111100 GEN
100. 00010200 LBO -00017336
QMG ••• 2.3
115564 GEN
75, 00031300 LBO -00015160
PRT ••• 2+0
115220 GEN
70. 00001100 LBO -00014601
LPO
02.02B 115104 GEN
70. 00013600 LBO -00016274
••• ACS 2.01
114654 GEN
70. 00004500 LBO -00015264
,,,AT. 02
113514 GEN
64, 00060000 LBO -00014671
•• ,QUE 2.1A
115450 GEN
50, 00020000 LBO -00016124
••• PRI 2+1A
115334 GEN
50. 00020000 LBO -00016124
••• BOO 06.02 114540 GEN
50, 00021700 LBO -00014231
••• ELI Vl,03 114174 GEN
50, 00017000 LBO -00017315
••• MAG 01.02 113630 GEN
50, 00031500 LBO -00016212
,,,LOA 03.3
113034 GEN
50. 00032300 LBO -00016633
••• HEL 01.0
112470 GEN
50. 00023400 LBO -00017130
••• BYE 04,2
112354 GEN
50. 00012400 LBO -00017067
••• BRO V04+3 112240 GEN
50. 00030300 LBO -00017172
,,,LJNL 3+1
111214 GEN
50. 00024400 LBO -00015463
LPO!
Loaded
DDO!
Loaded

(continued on next page)

5-25

DETAILS OF SYSGEN PHASE I I

Example 5-1 (Cont.)
DD 1:
Dl.O:

Loaded
Loaded
Loaded
Loaded
Loaded
Loaded
Loaded
Loaded
Loaded
Loaded
Loaded

DU:

rruo:

nui:

MSO:
TTO!
TTl !
TT2!
TT3:
TT4!
NLO!
TIO!

coo:

CLO!
LBO!
SYO:

Annotated Terminal Output from SYSGEN Phase II

no:
no:

[1[10:
DDO!

>;
>; End of s~stem VMR at 19:i3!40 on 21~FEB-83
>;
>;
>; An alternate version of SYSLIB.OLB~ the s~stem obJect

librar~r

was

>; created to provide support for ANSI mastape/FCS bis-bufferins <which
>; ~ou selected in Phase IJ. You may want to rebuild DMPr FLXr PIPr and
>; VFY in Phase III to use ANSLIB.OLB. Noter howeverr buildins tasks with
>; ANSLIB.OLB causes an increase in the size of tasks as compared to the
>; SYSLIB.OLB version of the tasks,
>;
>;
>;
>;
>;
>;
>;
>;
>;

A memory resident librarY of FCS routines <which you selected in Phase I>
was built to helP reduce task memory reauirements. You may want to rebuild
tasks in Phase III to link to the FCS resident library.
Because of the lack of adeauate disk space on the RSXM35 diskr the tasks
BADr BRUr CDAr CMPr CRFr DMPr FMTr IOXr PATr VFYr and ZAP were not
included in the baseline system.
If you want these tasks in your tarset
sYstemr thew should be built in Phase III.

>; When SYSGEN finishesr boot in your tarset systemr and save the system with a
>; bootstrap. For example!
>;
>;

>;
};

>BOO [1r54JRSX11M
XDT: 35-A
XDT>G
RSX11M V4.1 BL35-A

>TIM 11!23 14-0CT-81
>SAU /WB

>;
>;
>;

RSX11M V4.1 BL35-A
>RED DL!=SY:
>RED DU =LB!
>MOU DL!RSXM35
>@DL![1r2JSTARTUP

>•
>;

>;
>;
>;

128.K

MAPPED

-::.;

>;
>ASN :::LB!
>REM PIP

>REM EDI
>REM LBR
S·DMO DU: EXCPRV
DMD -- TTO:
dismounted from DL1:
DMO -- TTO!
dismounted from DL1!
19!33!49
DL1! -- Dismount complete

***

*** Final dismount initiated ***

>; End of SYSGEN Phase II at 19!33!49 on 21-FEB-83
>;
>SET /UIC=[200~200J
>@ <EOF>
>BOO [1,54JRSX11M0

XDT! 35-A

(continued en next

5-26

DETAILS OF SYSGEN PHASE I I

Example 5-1 (Cont.)

Annotated Terminal Output from SYSGEN Phase II

XDT>G
RSX11M V4.1 BL35-A
DEVICE DUOO: NOT IN CONFIGURATION
DEVICE ouo1: NOT IN CONFIGURATION
DEVICE Msoo: NOT IN CONFIGURATION

TIM 19t35 21-FEB-83
>TIM
19!35!03 21-FEB-83
>SAV /WB

RSX-11M V4.1 BL35-A 128.K MAPPED
>RED DL!=SY:
>RED DL:=LB!
>MOU DL!RSXM35
>@DLt[1,2JSTARTUP
>* PLEASE ENTER TIME AND DATE CHR:MN DD-MMM-YY> [SJ! 19!36 21-FEB-83
>TIM 19:36 21-FEB-83
>* ENTER LINE WIDTH OF THIS TERMINAL [D D:132.J!
>SET /BUF=TI!132.
>ACS SY!/BLKS=512+
>;
>;
>;
>;
>;
>;
>;

This system startup command file CLB![1,2JSTARTUP.CMD> contains a
template of commands to initialize the aueue Print spooler and aueue
LPO:, initialize the error loSSer, initialize the DCL CLJ, and install
the RMS Library and Utilities.
As is these commands are commented out
and are not executed. To include these commands as Part of the
startup Procedure, edit th~ file to remove the Period and semi-colon
c.;J comment delimiter from the beginning of each line. These
>; commands ma~ be useful for initializing the various facilities for
>; Your installation or else theY may Provide a model with which to
); tailor initialization commands for Your Particular installation.
>@ <EDF>

5-27

DETAILS OF SYSGEN PHASE I I

Notes for the terminal output from SYSGEN Phase II
target system} while running on a baseline system.

t»
~

(for

mapped

Invoke Phase II of SYSGEN and continue answering questions.
The default name for the output saved answer file from Phase I
is SYSSAVED.CMD.
Press the RETURN key if you want to specify
the same file name for the ouput saved answer file from Phase
II.
At the end of Phase II, if you select the default name of
the output saved answer file, SYSGEN will have created a single
saved
answer
file named SYSSAVED.CMD which contains the
responses from Phase I and Phase II questions.
You may see some diagnostic (*DIAG*} messages in your terminal
output during the System VMR Section of Phase II. They are no
cause for alarm;
they simply supply diagnostic information
about partition sizes.
(See Chapter 10 of the RSX-llM/M-PLUS
System Management Guide for details on VMR messages.)

During the System VMR Section, VMR
displays
information
concerning pool, partitions, installed tasks, and devices as an
indication of its successful completion.

At the end of Phase II, you should bootstrap your virgin system
and make it hardware bootable.
See Chapter 6 for details.
NOTE
If you are generating an unmapped target system, follow
the instructions at the end of Phase II.
Refer to
Chapter 6 for suggestions on procedures to follow
between Phase II and Phase III.

5-28

CHAPTER 6
POSTSYSTEM GENERATION GUIDELINES

After the completion of SYSGEN Phase II, several steps remain before
your system generation is actually complete.
These steps vary
depending on whether you are generating a mapped or an unmapped system
and whether you are running SYSGEN stand alone or on line. This
chapter describes some of those steps and provides some suggestions
for maximizing utilization of your system resources.
The information presented in this chapter is only a guideline.
The
steps presented occur in a sequence and, therefore, are not intended
to be executed at random. You may, however, find that you can skip
some of the steps because of the type of distribution kit you have,
the type of system you have generated, and the level of backup
security needed.

6.1

DO YOU HAVE A VIRGIN SYSTEM?

At the end of Phase II -- after SYSVMR.CMD has increased the system
image file
(RSXllM~SYS)
SYSGEN has produced a bootable RSX-llM
system known as a virgin system.
Once you have bootstrapped a virgin
system, that system is referred to as the saved target system.
These
are necessary distinctions within the context of this chapter.
(See
the definition of virgin system and target system in Chapter 1.) You
must have a virgin system to begin performing the steps listed in this
chapter.
If you are generating your RSX-llM system from an on-line host, SYSGEN
completes Phase II without invoking SYSVMR.CMD.
If you have not
already done so, make any necessary edits to SYSVMR.CMD and then
invoke VMR as described at the end of Chapter 5.

6.2

STEPS FOR MAPPED TARGET SYSTEMS

If you have a mapped virgin system, follow the procedure beginning
Section 6.2.1 after Phase II completes.

If you have either a standard, unmapped virgin system (where the base
address of the GEN partition is the standard address of 40000) or a
nonstandard, unmapped virgin system (where the base address of the GEN
partition is at an address of other than 40000), start at Section 6.3.

6-1

POSTSYSTEM GENERATION GUIDELINES
NOTE
In the following procedure, assume that
ddu:
contains the virgin system on the
disk volume labeled RSXM35, and that
RSXM35 contains a mapped 124K virgin
system in UFD
[1,54]
and
includes
support for the Executive Debugging Tool
( XDT) .

6.2.1

How to Bootstrap the Virgin System

Follow the steps listed to bootstrap and save the virgin system.
If the virgin system includes support for the Executive Debugging Tool
(XDT),
the console terminal displays a prompt (XDT>) from XDT during
the bootstrap procedure. To continue, enter a G from the console
terminal.
Note that, if you are generating your system from a stand-alone
system, you must install the version of BOO ($BOO;l) built to
the baseline system, not the most_ recent version of BOO
($BOO}
to
the target system.
-·
11

host

- ~

(For a stand-alone host system)
(For an on-line host system)

>INS $BOO;l
>INS $BOO
>BOO ddu: [l,54]RSX11M.SYS
XDT: 35-A
XDT>G
RSXllM V4.l BL35-A

(Set the time and date)
(Enter the TIME command)

>TIM 11:23 10-MAY-83
>TIM
11:24 10-MAY-83

>
The purpose of entering the TIM command after you set the time and
date is to ensure that your new system performs some fundamental
operations. The TIME command utilizes enough of the system resources
to be a satisfactory test.
Now you are ready to save your
hardware bootable.

6.2.2

system

and

make

the

target

system

How to Make Your Target System Hardware Bootable

Follow the steps below to save your target system. You use the SAV
/WB command to make the target system disk hardware bootable. See the
SAVE command in the RSX-llM/M-PLUS MCR Operations Manual for details
on what happens when you save the system.

6-2

POSTSYSTEM GENERATION GUIDELINES
NOTE
If you do not want to
write
the
bootblock the first time you save the
system, omit the /WB switch the first
time through the procedure. When you
are satisfied that the system works
correctly after saving it, repeat the
following steps and include the /WB
switch.
Once you have completed the following steps, your target system disk
can be hardware bootstrapped to bring up your new RSX-llM system.
>SAV /WB
124.K MAPPED

RSXllM V4.l BL35-A

>RED ddu:=SY:
>RED ddu:=LB:
>MOU ddu:RSXM35
>@ddu: [l,2]STARTUP.CMD
>* PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY)

6.2.3

[S] :11:30 10-MAY-83

Invoke Phase III to Task-Build BRU

To execute some of the remaining steps in this chapter, you need to
build the Backup and Restore Utility (BRU).
The most efficient way to
do this is to invoke Phase III of SYSGEN and task-build BRU. Refer to
Chapter, 7 for details on Phase III. After you task-build the utility,
exit from Phase III, install BRU, and resume working at the next step.
NOTE
You may want to back up the system disk
at
several
intervals
during
the
remaining steps to protect
yourself
against any accident that might corrupt
the contents of
the
system
disk.
Backing
up the system disk is not
critical at this point. However, after
you task-build BRU you may back up your
system disk whenever you like.
(See
Section 6.2.13.)

6.2.4

How to Recover Space on the Target System Disk

6-3

POSTSYSTEM GENERATION GUIDELINES
NOTE
Be sure that you have saved your system
and made the target system disk hardware
bootable before proceeding with these
steps.
Follow the steps below for recovering space on the target system disk:
1.

Purge the system UFD to eliminate baseline
been superseded by target system files:

files

that

have

>SET /UIC=[l,54]
>INS $PIP
>PIP ddu:*.*/PU

Delete the privileged baseline files that were not eliminated
by the purge operation.
Files to delete may include the
baseline Autoconfigure task ACF.ESL, baseline drivers for
devices not supported on your target system, and the baseline
FCP FCPSML.TSK.
>SET /UIC=[l,54]
>PIP ddu:ACF.BSL;l/DE,DPDRV.*;l,FCPSML.TSK;l

Use BRU to backup the target system disk to another disk of
the same type
(this disk should be checked for bad blocks
using the BAD utility before invoking BRU), or to a magnetic
tape,
to provide the largest possible contiguous space.
(If
you are copying from disk to disk,
this step recovers the
noncontiguous space freed by the files that were deleted and
purged.) For example, assume dduu:
is a second disk drive:
>INS $BRU
>ACS ddu:/BLKS=O
>DMO ddu:/DEV
>BRU/INI/VER
From: ddu:
To:
dduu:
BRO> (CTRL/Z)
or if mtu:
is a magnetic tape
single disk drive:

drive

system

with

>INS $BRU
>LOA mtu:
>ACS ddu:/BLKS=O
>DMO ddu:/DEV
>BRU/DENS:number/REW/VER
From: ddu:
To:
mtu:
BRU> (CTRL/Z)
If you used two disks for the BRU operation, remember that the newly
copied disk should now be your new system disk.
The disk that you
used to make the new copy is now your backup copy.
When you have copied the disk, bootstrap the new system disk (that is,
the one you just compressed} and continue with the remaining steps.

6-4

POSTSYSTEM GENERATION GUIDELINES
6.2.5

Building or Rebuilding RSX-llM Tasks

Invoke SYSGEN Phase III to
build
or
rebuild
nonprivileged,
DIGITAL-supplied RSX-llM tasks.
(See Chapter 7 for details on SYSGEN
Phase III.)
DMP, FLX, PIP, and VFY can use ANSI magnetic tape or big-buffering
capabilities, provided that you generated ANSI magnetic tape or
big-buffering support into your target system.
If you want any of
these tasks to have ANSI magnetic tape or big-buffering capabilities
(and if your target system includes the necessary support) ,
invoke
Phase III to build these tasks to link to ANSLIB.OLB.
A number of RSX-llM nonprivileged tasks can link to the FCS resident
library (on mapped systems). If your system has support for the FCS
resident library and if you want specific tasks to link to that
library,
invoke Phase III to build those tasks.
Chapter 7 includes a
list of tasks that can be linked to FCSRES.
If you are using the RL01/RL02 distribution kit, the
are not in the baseline system:
BAD
FMT

CDA
FTB

CMP
IOX

CRF
PAT

DMP
RPT

DSC
VFY

following

tasks

EDT
ZAP

If you wish to include any of these tasks in your target system,
invoke Phase III to build them.
(BRO is available only on mapped
systems;
EDT is available only on mapped systems with the full-duplex
terminal driver.)
BRO is also not included in the baseline system for any of the
distribution kits.
If you have not yet built BRO and if you wish to
include BRO in your target system, invoke Phase III to build it.
You
can include BRO with those tasks tested by UETP by building and
including it in your target system before invoking UETP.
Bear in mind that, if you intend to test your target system using the
User Environment Test Package (UETP), you should first build all of
the DIGITAL-supplied RSX-llM tasks that you intend to include in your
target system.

6.2.6

Testing Your Target System with UETP

If you wish to test your system, invoke UETP.
Before doing so, be
sure that you have read Chapter 9 in the RSX-llM/M-PLUS System
Management Guide.
It discusses UETP in detail, including those tasks
and ut1l1ties that must be built prior to invoking UETP.
NOTE
You should build any DIGITAL-supplied
RSX-llM tasks for your target system
during Phase III and before invoking
UETP.

6-5

POSTSYSTEM GENERATION GUIDELINES
6.2.7

How to Transfer the Target System to a Different Type of Disk

This is an optional step intended for those users who need to transfer
the virgin target system to a different type of disk.
If this is not
a concern for you, skip this section and go to the next one.
If you intend to transfer your virgin target system to a different
type of disk,
the system data base must adequately reflect the
characteristics of the new target system disk.
To do this, you must
invoke VMR and recreate the system image using the new target system
disk's characteristics. The reason for this is that the physical disk
locations of the installed tasks on the new disk are different from
those stored in the system image file,
which still has the disk
locations of the installed tasks for the old target disk. For
example, if you copied your virgin target system from an RK07 to an
RMOS, and if you were able to software bootstrap the RM05 disk, your
system will not be able to find any of the installed tasks because the
tasks are probably stored in different disk locations than the system
expects. Without changing the system image file, your system at best
will be unpredictable.
NOTE
Your response to the SYSGEN question
regarding the unit supported by the
device controller must have been the
exact device to which you intend to
transfer your
target
system.
For
example,
if
you
selected
RK06/07
support, your response to the SYSGEN
question regarding the unit supported by
the DM controller must exactly match the
device that you want to be hardware
bootable.
If you did not specify the correct device during SYSGEN, either
explicity or by selecting the default response, you must perform
another SYSGEN and supply the correct reponse in the Peripheral
Options Section.
Once you have ensured that the necessary device controller support is
included in your system, use the following procedure to transfer your
target system to the new target system disk:
1.

Use the BAD utility to check for bad blocks on the disk to
which you intend to transfer the target system;
then
initialize the disk with the MCR INI command.
(See the
RSX-llM/M-PLUS Utilities Manual for information on the BAD
utility.
The RSX-llM/M-PLUS MCR Operations Manual contains
information on the MCR INI command.)

Software mount the disk to which you intend to transfer the
target system (assume that dduu: contains the disk to which
you are copying the target system) :
>MOU dduu:RSXM35

Copy the system UFDs to the new target system disk:
>PIP dduu:/NV/UF/FO=ddu: [l,l]*.*,[l,2]*.*,[l,54]*.*
>PIP dduu:/NV/UF/FO=ddu: [l,3]*.*,[1,4]*.*,[l,6]*.*,[l,7]*.*

6-6

POSTSYSTEM GENERATION GUIDELINES
4.

Reassign the logical devices SY:
system disk:

and LB:

to the new

target

>ASN dduu:=SY:
)ASN dduu:=LB:
5.

Recreate the system image on the new target system disk:
>SET /UIC=[l,54]
>PIP RSXllM.SYS/NV/CO/BL:<n>=RSXllM.TSK
where <n> = (size of memory

* 4)

+ 2

The memory size is the response given during
Question 3 in the Target Configuration Section.
6.

SYSGEN

Install VMR and invoke SYSVMR.CMD:
>INS dduu:$VMR
>VMR @SYSVMR
To avoid any incompatibility problems,
the version of VMR
that you are using must originate from your target system
disk.

6.2.8

After VMR has updated the system image file and produced a
virgin system, pgftware bootstrap the virgin system, and ~
use the MCR SAV command to make the disk hardware bootable.
(Refer to Section 6.2.1 and 6.2.2 for those procedures.)

Rebuilding User-Written Tasks

If you have a mapped system with FCS resident library (FCSRES) support
or ANSI support and you want your user-written tasks to use these
resources, rebuild those tasks to include the desired support.
See the RSX-llM/M-PLUS Task Builder Manual for details on specifying
ANSLIB.OLB with the DL switch as the default library and for details
on using the LIBR or RESLIB options to link to FCSRES.
Remember to rebuild your privileged user-written tasks to link to
target Executive.

6.2.9

the

Help Files

Each distribution kit includes the file HELP.ULB, which consists of
the various HELP files
for the MCR, DCL, and UTILITY commands.
In
addition, there are introductory files included in HELP.ULB that are
referred to in the Introduction to RSX-llM and RSX-llM-PLUS.
You can find HELP.ULB in UFD (1,2] on all distribution kits.
However,
the volume on which the HELP files reside differs for each type of
kit. The following lists the various distribution kits and the
various locations for HELP.ULB:
Distribution Kit

Volume

Big disk
RC25
RK06/07
RLOl/02

RSXM35
RSXM35
CLISRC
HLPDCL

6-7

POSTSYSTEM GENERATION GUIDELINES
Follow these steps to get HELP support:
1.

Establish [1,2] as the default UIC for the terminal:
>SET

/UIC=[l~2]

Copy HELP.ULB to the LB: device (skip this step if
using a big disk distribution kit):

you

are

>PIP LB:/NV=ddu:HELP.ULB
If you have an RLOl/02 magnetic tape distribution kit and you
did not copy over your HELP files earlier, you must invoke
and run BRU to copy the files from tape to disk.
To do this,
mount the distribution tape onto a magnetic tape drive (if
the distribution tape is 800 bpi, mount the second tape
volume), and issue the following command lines to BRU:
>BRU
BRU>/NOI/BAC:HLPDCL/DENS:number/REW/VER
From: MM: [l,2]HELP.ULB
To:
LB:
NOTE
RLOl/02 users may not have sufficient space on the
target system disk for all of the HELP files.
In
such cases, your LB: device should point to another
type of disk, or you should print the help files as a
listing using the LBR utility to extract the files.
(See the RSX-llM/M-PLUS Utilities Manual for details
on using LBR.)

Extract the build-module from HELP.ULB, then name this module
HELPBUILD.CMD:
>LBR HELPBUILD.CMD=HELP.ULB/EX:BUILD

Invoke the HELPBUILD command file:
>@HELPBUILD
HELPBUILD.CMD asks a series of questions that allow you to
build either FULL or BRIEF HELP support for MCR and DCL
commands
and
the
RSX-llM
utilities.
In
addition,
HELPBUILD.CMD allows you to select the introductory files
used with Introduction to RSX-llM and RSX-llM-PLUS.

When you finish extracting the desired modules from HELP.ULB,
delete the files HELPBUILD.CMD and HELP.ULB from LB:.
>PIP HELPBUILD.CMD;*,HELP.ULB;*/DE

See the the HELPBUILD.CMD file for more information.

6.2.10

Multiuser System Setup

If you have a multiuser system, you should run the Account File
Maintenance Program
(ACNT)
to create an account file and user
accounts.
If you have a previously created account file,
copy the
account file to the new system disk. For details on ACNT, see the
RSX-llM/M-PLUS System Management Guide.

6-8

POSTSYSTEM GENERATION GUIDELINES
You should also use an editor to create the file LOGIN.TXT in UFD
[1,2]
on your LB: device to provide installation news and notices to
system users. For details on LOGIN.TXT, see the MCR HEL/LOG command
in the RSX-llM/M-PLUS MCR Operations Manual.
You can tailor
[l,2]STARTUP.CMD to your particular installation's
needs.
Following are some of the functions that you may want
STARTUP.CMD to perform:
•

Set the speed and type of terminals.
(See the RSX-llM/M-PLUS
MCR Operations Manual for details on the MCR SET command.)

Install resident libraries (RMS on mapped systems
• Section
6.2.13),
utilities, and user tasks.
RSX-llM/M-PLUS MCR Operations Manual for details
INSTALL command~

only,
(See
on the

see
the
MCR

•

Initialize the Queue Manager and Print Spooler
(on mapped
systems only)
if the system includes Queue Manager support.
(See the RSX-llM/M-PLUS System Management Guide for details on
the Queue Manager.) The STARTUP.CMD file contains commands in
commented form that provide a template for
initializing the
Queue Manager.

•

Initialize DCL (on mapped systems only) if the system includes
support for DCL.
(See the RSX-llM/M-PLUS Command Language
Manual for details on DCL.)
The STARTUP.CMD file contains
commands in commented form that provide a template for
initializing DCL.

•

Initialize the Error Logger if the system includes support for
error logging.
(See the RSX-llM/M-PLUS Error Logging Manual
for details.)
The STARTUP.CMD file contains commands in
commented form that provide a template for initializing the
Error Logger.

6.2.11

Establishing System Features with VMR

If terminal speeds and types and partitions are stable and certain
tasks are frequently used, you may wish to establish these features in
your system using VMR commands rather than having [l,2]STARTUP.CMD do
it at bootstrap time. This decreases the amount of time required for
the system to be ready for use after it has been bootstrapped.
(See
the RSX-llM/M-PLUS System Management Guide for details on VMR.)

6.2.12

How to Create a Backup Copy of the Target System Disk

Now that you have saved your target system, you should create a
back-up copy to protect yourself against any accident that might
corrupt the contents of the disk. First check the scratch disk for
bad blocks using the BAD utility. Then using BRO, copy the target

6-9

POSTSYSTEM GENERATION GUIDELINES
system disk e1tner to another disk of the same type or to
tape. For example, assume dduu:
is a second disk drive:

magnetic

>BRU/INI/VER
From: ddu:
To:
dduu:
BRO> (CTRL/Z)
or mtu:

is a magnetic tape drive:

>BRO/DENS:number/REW/VER
From: ddu:
To:
mtu:
BRU> (CTRL!Z)

6.2.13

Installing RMS-11 V2.0

On most mapped RSX-llM systems, all RMS-11 files are automatically
your system after SYSGEN.

However, for systems which were generated using either the RK06/07 or
the RLOl/02 distribution kits, the RMS-11 files must be copied to the
new system disk after SYSGEN.
If your system was not generated using
one of these kits, skip this section and continue with Section
6.2.13.2.

6.2.13.1 RK06/07 and RLOl/02 Procedures - To copy RMS-11 files to
your
new system disk, you must execute the command procedure
[l,2]RMSINSTAL.CMD. Before you invoke this command file, you must
task-build BRO (see Section 6.2.3). After SYSGEN Phase III builds the
BRU task, you should log into a privileged account and invoke
RMSINSTAL.CMD using the following command line:
>@[l,2]RMSINSTAL
This command procedure prompts you for information
copy operation in the following manner:
1.

and

executes

RMSINSTAL.CMD asks you if want all the RMS-11 files
system.

the
your

If you answer "NO" to this question, all the RMS-11 files
will
be
transferred
except
the .MAP files and the
demonstration programs.
2.

The procedure asks you to enter the name of the
that is to contain the RMS-11 files.

target

disk

This disk should be write-enabled.
3.

RMSINSTAL deletes all copies or previous versions of the
RMS-11 files on the target disk that the procedure will be
copying to that disk.
This step allows you to restart
RMSINSTAL if errors occur the first time it is invoked.

RMSINSTAL displays the free space on the target disk and asks
you if the target disk contains enough free space to copy the
RMS-11 files.

6-10

POSTSYSTEM GENERATION GUIDELINES

RMSINSTAL displays a small table that assigns a number to
each type of kit
(RLOl/02 disk, RLOl/02 magnetic tape,
RK06/07 disk, RK06/07 magnetic tape).
Then RMSINSTAL asks you to enter the number that
to your type of distribution kit.

corresponds

If your distribution kit is on magnetic tape, RMSINSTAL
you for the density (either 800 bpi or 1600 bpi).

asks

The procedure asks you to physically mount the appropriate
distribution disk or tape and then prompts you for the device
name.

RMSINSTAL generates the appropriate BRU commands that copy
RMS-11 files from the distribution kit to the target disk.
NOTE
On the RK06/07 disk and magnetic tape distribution
kits, BRO may be run twice by RMSINSTAL.
When the BRO commands have been executed, the procedure
displays the amount of remaining free space on the target
disk.

The RMS-11 file copy operation is now complete. For more
on RMS-11, see the RSX-llM/RSX-llS Release Notes.

information

6.2.13.2 Startup Command Procedures - If all the RMS-11 files have
been transferred to your system, the next step is to install the
resident library(s) and the RMS-11 utilities during system startup.
To do this, you should edit LB: [l,2]STARTUP.CMD.
The commands to
install the resident library(s)
and RMS-11 utilities already exist
except that the command lines have been commented out by the period
and semicolon
(.;) that begins each command line. Delete the period
and semicolon that proceeds each command line that you want startup to
execute. For those command lines that you do not want to be executed,
leave the line as it is.
Unless you have already done so with VMR (see Section 5.6.2), you must
allocate a partition for each resident library you use by issuing MCR
SET commands. Note that you must replace the word "base" with the
octal address of the base of the partition.
You can include MCR SET commands in your startup command file or you
can permanently include the RMSRES and DAPRES partitions in your
system by performing the following steps:
1.

Use MCR SET commands to include the necessary partions.

Use MCR INSTALL commands to install the tasks in the
system.

Use the MCR SAVE command to save RMSRES and DAPRES
system image.

running
into

the

For information on the MCR SET, INSTALL, and SAVE commands, please see
the RSX-llM/M-PLUS MCR Operations Manual. For more information on
RMS-11, see the RMS-lrci"ocumentation and the RSX-llM/RSX-llS Release
Notes.
6-11

POSTSYSTEM GENERATION GUIDELINES
6.2.14

Error Logging Support

If you want error logging support and you have already created your
system from either an RK06/07 or an RLOl/02 distribution kit, you must
copy the following error logging files
from either the CLISRC
(RK06/07)
or HLPDCL (RLOl/02) distribution disk or backup set to your
default library disk (LB: [1,6]):
[l,6]ERRLOG.ULB
[l,6]ERRLOGETC.ULB
The Report Generator (RPT) needs ERRLOG.ULB in order for it to work.
ERRLOGETC.ULB contains a module name TUNE that fine tunes ERRLOB.ULB
to your particular system by removing unneccessary modules in the
universal
library.
For more information on RPT and ERRLOG.ULB, see
the RSX-llM/M-PLUS Error Logging Manual.

6.2.15

Installing Layered Products in the Target System

If you intend to include any layered products in your
target
you can do it now.
Refer
to the appropriate layered
documentation for specific instructions.

6.3

system,
product

STEPS FOR UNMAPPED SYSTEMS

If you have an unmapped virgin system follow the
at Section 6.3.1 after Phase II completes.

procedure

beginning

NOTE
In the following procedure, assume that
ddu: contains the virgin system on disk
RSXM35 and
that RSXM35 contains
an
unmapped
28K
virgin system in UFD
[ 1, 50] •

6.3.1

Building or Rebuilding RSX-llM Tasks

Invoke SYSGEN Phase
III
to
build
or
rebuild
nonprivileged,
DIGITAL-supplied
RSX-llM tasks
that you wish
to start at
the
nonstandard (for nonstandard unmapped systems) or
the standard
(for
standard unmapped systems) base address of the GEN partition in your
target system.
NOTE
In order for your system
to
work
correctly after you save the target
system, be sure to build TKB,
PIP,
and
EDI before you bootstrap the target
system.
(See Chapter 7 for details on
SYSGEN Phase III.)
Bear in mind that, if you intend to test your target system using
the
User Environment Test Package (UETP), you should first build all of
the DIGITAL-supplied RSX-llM tasks that you intend to include in your
target system.
6-12

POSTSYSTEM GENERATION GUIDELINES
6.3.2

How to Bootstrap the Virgin System

Follow the steps listed to bootstrap and save the virgin system.
Note that if you are generating your system from a stand-alone host,
you must install the version of BOO ($BOO;l) built to run on the
baseline system, not the most recent version of BOO
($BOO)
built to
run on the target system. Also note that bootstrapping the virgin
system from an on-line host system aborts the current running system
and brings up the virgin system.
>INS $BOO;l
>INS $BOO
>BOO ddu: [l,50]RSX11M.SYS

(For a stand-alone host system)
(For an on-line host system)

RSXllM V4.l BL35-A
(Set the time and date)
(Enter the TIME command)

>TIM 11:23 10-MAY-83
>TIM
11:24 10-MAY-83

>
The purpose of entering the TIME command after you set the time and
date is to ensure that your new system performs some fundamental
operations. The TIME command utilizes enough of the system resources
to be a satisfactory test.
Now you are ready to save your system and write the hardware bootblack
on the target system disk.

6.3.3

How to Make Your Target System Hardware Bootable

Follow the steps below to save your target system. You use the SAV
/WB command to make the target system disk hardware bootable.
{See
the SAVE command in the RSX-llM/M-PLUS MCR Operations Manual for
details on what happens when you save the system.)
NOTE
If you do not want to
write
the
bootblack the first time you save the
system, omit the /WB switch the first
time through the procedure. When you
are satisfied that the system works
correctly after saving it, repeat the
following steps and include the /WB
switch.
Once you have completed the following steps, your target system disk
can be hardware bootstrapped to bring up your new RSX-llM system.
>SAV /WB
RSXllM V4.l BL35-A

28.K UNMAPPED

>RED ddu:=SY:
>RED ddu:=LB:
>MOU ddu:RSXM35
>@ddu:[l,2]STARTUP.CMD
>* PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY)
6-13

[S] :11:25 10-MAY-83

POSTSYSTEM GENERATION GUIDELINES
6.3.4

Invoke Phase III to Task-Build DSC

To execute some of the remaining steps in this chapter, you need the
The most efficient way to do
Disk Save and Compress utility (DSC).
this is to invoke Phase III of SYSGEN and task-build DSC.
Refer to
After you task-build DSC, exit
Chapter 7 for details on Phase III.
from Phase III, install DSC, and resume working at the next step.
NOTE
You may want to back up the system disk
at
several
intervals
during
the
rema1n1ng steps to protect
yourself
against any accident that might corrupt
the contents of the system disk.
This
is not critical.
However, after you
task-build DSC, you may back up your
system disk whenever you like.
(See
Section 6e3el0e2e)

6.3.S

How to Recover Space on the Target System Disk

To make efficient use of the space available on your target system
disk, you should delete unnecessary files from the disk.
This is an
optional step, particularly for users with larger distribution kits.
However, RLOl/02 users may find this step useful.
NOTE
Be sure that you have saved your system
and made it hardware bootable before
proceeding with these steps.
Follow these steps for recovering space on the target system disk:
1.

If you are using the big disk distribution
unused baseline system as follows:

kit,

delete

the

have

been

>SET /UIC=[l,54]
>ms $PIP
>PIP ddu:*.*;*/DE
2.

Purge the system UFO to eliminate
superseded by target system files:

files

that

>SET /UIC=[l,50]

>PIP ddu:*.*/PU
3.

Use DSC to copy the target system disk to another disk of the
same type,
or to a magnetic tape, to provide the largest
possible contiguous space.
(This
step
recovers
the
noncontiguous space freed by the files that were deleted and
purged.) For example, assume dduu:
is a second disk drive:
>ms $DSC
>ACS ddu:/BLKS=O
>DMO ddu:/DEV
>osc dduu:/VE=ddu:

6-14

POSTSYSTEM GENERATION GUIDELINES
or if mtu:
is a magnetic tape
single disk drive:
>INS $DSC
>LOA mtu:
>ACS ddu:/BLKS=O
>DMO ddu:/DEV
>DSC mtu:/VE=ddu:

drive

system

with

(disk to tape)

If you used two disks for the DSC operation, remember that the newly
copied disk should now be your new system disk.
The disk that you
used to make the new copy is now your backup copy.
When you have copied the disk, bootstrap the new system disk (that is,
the one you just copied) and continue with the remaining steps.

6.3.6

Testing Your Target System with UETP

If you wish to test your system, invoke UETP.
Before doing so, be
sure that you have read Chapter 9 in the RSX-llM/M-PLUS System
Management Guide.
It discusses UETP in detail, including those tasks
and utilities that must be built prior to invoking UETP.
NOTE
You should build any DIGITAL-supplied
RSX-llM tasks for your target system
during Phase III and before invoking
UETP.

6.3.7

How to Transfer the Target System to a Different Type of Disk

6-15

POSTSYSTEM GENERATION GUIDELINES
NOTE
Your response to the SYSGEN question
regarding the unit supported by the
device controller must have been the
exact device to which you intend to
transfer your
target
system.
For
example,
if
you
selected
RK06/07
support, your response to the SYSGEN
question regarding the unit supported by
the DM controller must exactly match the
device that you want to be hardware
bootable.
If you did not specify the correct device during SYSGEN, either
explicity or by selecting the default response, you must perform
another SYSGEN and supply the correct reponse in the Peripheral
Options Section.
Once you have ensured that the necessary device controller support
is
included
in your system, use the following procedure to transfer your
target system to the new target system disk:
1.

Use the BAD utility to check for bad blocks on the disk to
which you intend to transfer
the target system;
then
initialize the disk with the MCR INI command.
(See the
RSX-llM/M-PLUS Utilities Manual for information on the BAD
utility.
The RSX-llM/M-PLUS MCR Operations Manual contains
information on the MCR INI command.)

Software mount the disk to which you intend to transfer the
target system (assume that dduu:
contains the disk to which
you are copying the target system):
>MOU dduu:RSXM35

Copy the system UFOs to the new target system disk:
>PIP dduu:/NV/UF/FO=ddu: [l,l]*.*,[l,2]*.*,[1,50]*.*
>PIP dduu:/NV/UF/FO=ddu: [l,3]*.*,[l,4]*.*,[l,6]*.*,[1,7)*.*

Reassign the logical devices SY:
system disk:

and LB:

to the new

target

>ASN dduu:=SY:
>ASN dduu:=LB:
5.

Recreate the system image on the new target system disk:
>SET /UIC=[l,50)
>PIP RSXllH.SYS/NV/CO/BL:<n>=RSXllM.TSK
where <n> = (size of memory

* 4)

+ 2

The memory size is the response given during
Question 3 in the Target Configuration Section.

6-16

SYSGEN

POSTSYSTEM GENERATION GUIDELINES
6.

Install VMR and invoke SYSVMR.CMD:
>INS dduu:$VMR
>VMR @SYSVMR
To avoid any incompatibility problems, the version of VMR
that you are using must originate from the target system
disk.

6.3.8

After VMR has updated the system image file and produced a
virgin system, software bootstrap the virgin system, and then
use the MCR SAV command to make the disk hardware bootable.
(Refer to Sections 6.3.2 and 6.3.3 for those procedures.)

Rebuilding User-Written Tasks

If your system includes ANSLIB.OLB (that is,
if you selected ANSI
magnetic tape support or big-buffering) and you want your user-written
tasks to link to it, rebuild those tasks to include the necessary
support.
See the RSX-llM/M-PLUS Task Builder Manual for details on
ANSLIB.OLB as the default library using the /DL switch.

specifying

Remember to rebuild your privileged user-written tasks to link to
target Executive.

6.3.9

the

Help Files

Each distribution kit includes the file HELP.ULB, which consists of
the various HELP files for the MCR, DCL, and UTILITY commands.
In
addition, there are introductory files included in HELP.ULB that are
referred to in the Introduction to RSX-llM and RSX-llM-PLUS.
You can find HELP.ULB in UFO [1,2] on all distribution kits. However,
the volume on which the HELP files reside differs for each type of
kit. The following lists the various distribution kits and the
various locations for HELP.ULB:
Distribution Kit

Volume

Big disk
RC25
RK06/07
RLOl/02

RSXM35
RSXM35
CLISRC
HLPDCL

Follow these steps to get HELP support:
1.

Establish [1,2] as the default UIC for the terminal:
>SET /UIC=[l,2]

6-17

POSTSYSTEM GENERATION GUIDELINES
2.

Copy HELP.ULB to the LB: device (skip this step if
using a big disk distribution kit):

you

are

>PIP LB:/NV=ddu:HELP.ULB
NOTE
RLOl/02 users may not have sufficient space on the
target system disk for all of the HELP files.
In
such cases, your LB:
device should point to a
different type of disk, or you should print the help
files as a listing using the LBR utility to extract
them.
(See the RSX-llM/M-PLUS Utilities Manual for
details on using LBR.)
3.

Extract the build module from HELP.ULB, then name this module
HELPBUILD.CMD:
>LBR HELPBUILD.CMD=HELP.ULB/EX:BUILD

When you finish extracting the desired modules from HELP.ULB,
delete the files HELPBUILD.CMD and HELP.ULB from LB:.
CAUTION
If you are using a big disk distribution kit, do
delete HELP.ULB -- it is your only copy.

not

>PIP HELPBUILD.CMD;*,HELP.ULB;*/DE
See the HELPBUILD.CMD file for more information.

6.3.10

Multiuser System Setup

If you have a multiuser system, you should run the ~ccount File
Maintenance Program
(ACNT)
to create an account f iie and user
accounts.
If you have a previously created account file, copy the
account file to the new system disk.
For details on ACNT, see the
RSX-llM/M-PLUS System Management Guide.
You should also use an editor to create the file LOGIN.TXT in UFD
[1,2]
on your LB: device to provide installation news and notices to
system users.
For details on LOGIN.TXT, see the MCR HEL/LOG command
in the RSX-llM/M-PLUS MCR Operations Manual.

6-18

POSTSYSTEM GENERATION GUIDELINES

You can tailor
[l,2]STARTUP.CMD to your particular installation's
needs.
Following are some of the functions that you may want
STARTUP.CMD to perform:
•

Set the speed and type of terminals.
(See the RSX-llM/M-PLUS
MCR Operations Manual for details on the MCR SET command.)

•

Install resident libraries, utilities, and user tasks.
(See
the RSX-llM/M-PLUS MCR Operations Manual for details on the
MCR INSTALL command.)

•

6.3.10.1 Establishing System Features with VMR - If terminal speeds
and types and partitions are stable and certain tasks are frequently
used, you may wish to establish these features in your system using
VMR commands rather than having [l,2]STARTUP.CMD do it at bootstrap
time. This decreases the amount of time required for the system to be
ready for use after it has been bootstrapped.
(See the RSX-llM/M-PLUS
System Management Guide for details on VMR.)

6.3.10.2 How to Create a Backup Copy of the Target System Disk - Now
that you have set your target system, you should create a back-up copy
to protect yourself against any accident that might corrupt the
contents of the target system disk. Using DSC copy the target system
disk RSXM35 either to another disk of the same type or to magnetic
tape. For example, assume dduu:
is a second disk drive:
>DSC dduu:/VE=ddu:
or mtu:

is a magnetic tape drive:

>DSC mtu:/VE=ddu:

6.3.10.3 Installing Layered Products in the Target System - If you
intend to include any layered products in your target system, you can
do it now. Refer to the appropriate layered product documentation for
specific instructions.

6-19

CHAPTER 7
DETAILS OF SYSGEN PHASE III

Phase III is the last of the three interactive system generation
procedures.
This is the general task-building phase of SYSGEN.
During Phase III, you can task-build, or rebuild, any privileged or
nonprivileged RSX-llM task.
Figure 7-1 shows the logical flow of
SYSGEN Phase III. You may find Phase III useful for rebuilding
RSX-llM tasks that you have patched. You can also use Phase III to
build RSX-llM tasks that are not available on the baseline system.
Example 7-1 is an annotated terminal output from SYSGEN Phase III.
INPUT

ACTION

EXPLICIT RESPONSES

...........

TASK OBJECT FILES

'"""""'"

...

TASK-BUILD SPECIFIC
PRIVILEGED AND
UNPRIVILEGED TASKS

OUTCOME

.............

TASK IMAGES

·~

ZK-324-81

Figure 7-1 Logical Flow of SYSGEN Phase III
The Indirect
SYSGEN3.CMD.

command

file

that

controls

Phase

III

execution

If your target system is unmapped (regardless whether it is a standard
or a non-standard unmapped system), you have to build a few RSX-llM
non-privileged tasks (PIP, TKB, and EDI) before you can use your new
system.
Also, if you specified during the Privileged Task-Build
Section of Phase II that the base address for the GEN partition is
other than the default base address of 40000, you can easily build
RSX-llM tasks with the desired GEN partition base address during Phase
III.

The distribution kits do not contain tasks linked to a resident FCS
library (FCSRES). However, if your target system includes FCSRES, you
can build nonprivileged tasks in Phase III to access FCSRES.
The following is a list of some of the tasks
FCSRES:
ACN
ACS
CDA
CMP

COT
CRF
DMP
EDI

EDT
ELI
FLX
FTB

BEL
!OX
LBR
LPP

MAC
PAT
PIP
PMD

that
PRT
QMGCLI
QMG
SLP

you

can

link

STK
TKB
VFY
ZAP

If you selected ~..NS! magtape support or support for bia-bufferinq
during Phase I and if you want the DMP, FLX, PIP, or VFY utilities to
use this support, you must build those tasks during Phase III.

7-1

DETAILS OF SYSGEN PHASE III
The task-build .CMD and .ODL files for RSX-llM tasks are not available
on the distribution kit.
Prior to task-building a task, SYSGEN3
dynamically creates the .CMD and .ODL files.
Phase III consists of a single section of questions.

7.1

PREPARING FOR PHASE III

Before beginning Phase III of
following:
1.

SYSGEN,

sure

you

have

done

the

If you generated your system from an on-line V4.l host
system, set your UIC to [200,200], assign the logical device
SY:
to your baseline disk, and
invoke SYSGEN3.CMD as
follows:
>SET /UIC=[200,200]
>ASN ddu:=SY: (where ddu: is your baseline disk)
>MOU ddu: RSXM35
>@SYSGEN3

If you generated your system from a stand-alone V4.l host
(see Appendix B), then
system, bootstrap the target disk
invoke SYSGEN3.CMD as follows:
>SET /UIC=[200,200]
>@SYSGEN3

7.2

PHASE III QUESTIONS

* 1.

In what UIC is SGNPARM.CMD if not <uic>?

[S]:

Enter the UIC containing the file SGNPARM.CMD.
SGNPARM.CMD supplies
Indirect symbol definitions from Phase I that are relevant to Phase
III processing.
SGNPARM.CMD provides a means of communicating between
Phase I
and the other phases of SYSGEN. SYSGEN creates this file in
the UIC from which you invoked Phase I of SYSGEN.
SYSGEN replaces <uic> with the UIC from which you invoked Phase III of
SYSGEN.
Enter a different UIC to override this default, otherwise,
press the RETURN key.
Some tasks are not available on the baseline system (such as BAD) e
If
you wish to task-build a nonprivileged task for the baseline system,
use the SGNPARM.CMD file for the baseline system in UFO [1,54].

* 2.

Are you building nonprivileged tasks?

[Y/N]:

If you are building any of the following nonprivileged
respond Yes ~- this question:

tasks

BAD
BRO
CDA
CFL

CMP
CRF
DMP
DSC

EDI
EDT
FLX
FMT

FTB
!OX
~R

MAC

7-2

PAT
PIP
RPT
SLP

STK
TKB
VFY
ZAP

listed,

DETAILS OF SYSGEN PHASE III
NOTE
See the
RSX-llM/RSX-llS
Information
Directory
and
Index to locate the
appropriate
documentation
on
these
tasks.
BRU is available only on mapped
systems.
EDT is available only
on
mapped
systems with the full-duplex
terminal driver.

* 3.

Enter device for <label> disk when it is ready (ddu:)

[D:

This question appears only if you are using an RL01/RL02
kit.

<default>]

[S]:

distribution

To answer this question, enter the device mnemonic and unit number of
the drive containing the object files disk requested.
(SYSGEN
replaces <label> with the volume name of the appropriate disk.)
If you are using an RLOl/02 distribution kit and if you answered No to
Question 2, SYSGEN replaces <label> with EXCPRV.
If you are using an RLOl/02 distribution kit and you answered
Question 2, SYSGEN replaces <label> with RLUTIL.

Yes

The default response (<default>) is the response entered for
17 of the Setup Section in Phase I.

Question

* 4.

Enter map device (ddu:)

[D:

NL:] :

Map listings are usually of little use if your target system is
mapped.
The map listings are more useful if your target system is
unmapped and you need to determine the exact size of your tasks.
If you want the map listings, specify the desired output device as
your response.
If you specify a device other than LP:, SY:, LB:, TI:,
TT:, or NL:, the ~evice must be mounted apd the UFO [1,34] for mapped
systems or [1,30] for unmapped systems must exist.
The default output device for the
device).

* 5.

Enter task name(s)

map

listings

NL:

(the

null

[S]:

Enter the names of those tasks that you wish to build.
If you intend
to build more than one task, separate the names of the tasks with a
comma. You need not enter all the task names on one line.
When you
have entered the names of all tasks to be built, enter a period (.) to
terminate input.
If you wish to build MCR for a multiuser system, enter MCM as the task
name.
If you answered Yes to Question 2 to indicate that you intend to build
nonprivileged tasks, you may enter an asterisk (*) to display a table
of the nonprivileged tasks.
Likewise, you may enter a percent sign
(%)
to indicate that you wish to build all of the nonprivileged tasks
listed in the table.

7-3

DETAILS OF SYSGEN PHASE III
NOTE
You may rebuild privileged tasks using
SYSGEN3.CMD.
However,
you should not
use
Phase
III
for
building
all
privileged tasks.
If you
intend to
rebuild several
(or all)
privileged
tasks, you should do so in Phase II.

* 6.

Use [l,l]FCSRES.STB when building those tasks?

[Y/N]:

If your target system includes the FCS resident library
(FCSRES)
and
if you want your task(s) to link to that library, answer Yes to this
question.
If you answer No, any tasks built during Phase III are not linked to
the FCS resident library;
instead each task contains all of the
necessary FCS modules within the task image •

•

Tasks linked to the FCS resident library can only run on a system with
that FCS resident library installed.
Tasks built to link to FCSRES
cannot run on the baseline system.
This question does not appear if you did not select the FCS resident
library
(FCSRES) in Question 3 of the System Options Section in Phase
I.

* 7.

Use LB:[l,l]ANSLIB.OLB when building those tasks?

[Y/N]:

If your target system includes ANSLIB.OLB and if you want to build any
tasks with ANSLIB, answer Yes to this question.
This question appears only if you are building DMP, FLX, PIP, or VFY
and if you selected ANSI magtape support (Question 13 of the Executive
Options Section in Phase I) or support for big buffering
(Question 1
of the System Options Section in Phase I).
If you answer No to this question, any tasks you specify to
for your target system are built with SYSLIB.OLB.

built

This question does not appear if your target system includes a
resident FCS and does not include ANSLIB.OLB.
See Question 3 of the
System Options Section in Phase I for more information on the ANSI
version of FCSRES.

* 8.

GEN's base address in 32 word blocks [O 0:400]:

This question appears only for unmapped systems and only if you
building a task other than MCR, PRT, TKTN, FCPMIN, or FCPSML.

are

Enter the same base address for GEN that you specified in Phase II
(Question 2 in the Privileged Task-Build Section).
The base address
for GEN starts on a 32(10j word boundary.
The default of 400 is based on the assumption that the highest
location in memory allocated to the Executive does not exceed 40000
and that you intend to use nonprivileged tasks built to run in the GEN
partition starting at location 40000 (for example, the default of 400
is correct for standard unmapped systems).

7-4

DETAILS OF SYSGEN PHASE I I I

* 9.

SYSPAR's base address in 32 word blocks [O D:<defaolt>]

This question appears only for unmapped systems and only
building MCR, TKTN, FCPMIN, or FCPSML.

you

are

Enter the same base address for SYSPAR that you specified in Phase II
(Question 3 of the Privileged Task-Build Section).
If the target
system has 24K words or more of memory,
the default
(<default>)
is
1300.
The default is based on the assumption that you selected the
default of 400 32-word blocks for the GEN partition and that you plan
to include a
14K task partition
(PAR14K)
of which GEN is an SK
subpartition.
If the target system has less than 24K words of memory,
the default
base address
is 1000. This default is based on the assumption that
you have selected the default of 400 32-word blocks for the GEN
partition and that GEN is an 8K partition.
The base address for SYSPAR starts on a 32(10) word boundary.

* 10.

SPLPAR's base address in 32 word blocks [O D:<default>]:

This question appears for unmapped systems only, and only if
building the serial despooler task (PRT).

you

are

Enter the same base address for SPLPAR that you specified in Phase
(Question 4 of the Privileged Task-Build Section).

If you
The base address of SPLPAR starts on a 32(10) word boundary.
selected FCPMIN,
the default response for
this question can be
calculated by adding 100 to the default base address of SYSPAR.
If you selected FCPSML, the default response for this question can
calculated by adding 120 to the default of Question 10 above.

* 11.

Pause to edit any task build .CMD or .ODL files?

[Y/N]:

If you answer Yes to this question, SYSGEN pauses to allow you to
selectively edit the task-build
.CMD or
.ODL files.
This is the
logical place in SYSGEN to alter any task-build parameters if you need
to do so.
If you choose to edit any .CMD files, the information to
edit a given file is contained in comments within that file.

* 12.

Delete task build .CMD and .ODL files after task building?

[Y/N]:

It is not necessary to keep the .CMD and .ODL files after they have
been used to build their respective tasks.
They can be easily
recreated by reinvoking SYSGEN3.CMD.
You can free the disk space
occupied by these files by answering Yes to this question.

7-5

DETAILS OF SYSGEN PHASE III

Example 7-1

Annotated Terminal Output from SYSGEN Phase III

>SET /UIC
UIC=Cl r54J
>SET /UIC=[2Q0,200J
>SET /UIC
UIC=[200r200J
>@SYSGEN3 0

>; RSX-11M U4.1/RSX-11M-PLUS V2.1 System Generation Phase III -- version 2+0

>; 21-FEB-83 19:37:49

>;
>*

1+ In what UIC is SGNPARM.CMD if not in [200r200J [SJ:

>; RL01/RL02 distribution kit SYSGEN version 2+0 for RSX-11M BL35-A
>;
>; Continuation from SYSGEN PHASE I done on 21-FEB-83 at 17:25:46

>;
>* 2. Are you buildins non~rivileSed tasks? [Y/NJ: Y
>* 3. Enter device for RLUTIL device when it is ready (ddu:> [D: DLl:J [SJ: DL1:
>MOU DU :RLUTIL
>* 4. Enter maP device (ddu:> [D: NL:J [SJ:
>ASN sv:=LB:

>;
>;
>;
>;

For nonPrivileSed tasks!

*
/.

Prints the table of tasks
Builds all tasks
Terminates inGuirY

);

>;
>;

>;
>*
>;

>;
>;

Enter responses separated bY commas.
not fit on one line.

All responses need

5. Enter task name<s> [SJ! * f)
NonPrivilesed tasks:
BAD
CRF
FLX
MAC
STK

BRU
DMP
FMT
PAT
TKB

CDA
DSC
FTB
PIP
VFY

CFL
EDI
IOX
RPT
VMR

CMP
EDT
LBR
SLP
ZAP

5+ Enter task name(s) [SJ: BRUrEDTrLBRrPIPr
5. Enter task name(s) [SJ! TKBrVMRrZAPr .C)

>;
>; [1,1JFCSRES.STB can be used to build many tasks
>; so that those tasks link to the FCS resident library

6. Use [1r1JFCSRES.STB when buildins those tasks? [Y/NJ: Y

>;
>; It is assumed that r1,1JFCSRES.STB is an ANSLIB version of the FCS
>; resident library

>;
>;
); Note that tasks linked to the FCS resident library can only
); run on a system with the FCS resident library installed.
>i

>* 11. Pause to edit any task build .CMD or .ODL files? [Y/NJ: N
>* 12. Delete task build .CMD and .ODL files after task buildins? CY/NJ: Y
>SET /UIC=[lr24J
>; Creatins the task build .CMD and .ODL files in DL1:[1,24J

7-6

DETAILS OF SYSGEN PHASE III

Example 7-1 (Cont.)
··..·..

Annotated Terminal Output from SYSGEN Phase III

~
)-"

>INS SY![1,54JTKB.TSK;1/TASK= ••• TKL
>TKL @DL1![1,24JBRUBLD.CMD
>TKL @DL1![1,24JEDTRESBLD.CMD
>TKL @DL1![1,24JLBRRESBLD.CMD
>TKL @DL1![1,24JPIPRESBLD.CMD
>TKL @DL1![1,24JTKBRESBLD.CMD
>TKL @DL1![1,24JUMRBLD.CMD
>TKL @DL1![1,24JZAPRESBLD.CMD
>REM TKL
>ASN =LB!

>;
>~

Delete the task build .CMD and .ODL files

>INS SY:tPIP
>PIP DL1![1,24JBRUBLD.CMD;O/DE/NM,BRUBLD.ODL;o
>PIP DL1![1,24JEDTRESBLD.CMD;O/DE/NM,EDTRESBLD.ODL;o
>PIP DL1![1,24JLBRRESBLD.CMD;O/DE/NM,LBRRESBLD.ODL;O
>PIP DL1![1,24JPIPRESBLD.CMD~O/DE/NM~PIPRESBLD.ODL;o
>PIP DL1![1,24JTKBRESBLD.CMD;O/DE/NM,TKBRESBLD.ODL;o
>PIP DL1![1,24JUMRBLD.CMD;o/DE/NM,UMRBLD.ODL;o
>PIP DL1![1,24JZAPRESBLD.CMD;O/DE/NM,ZAPRESBLD.ODL;o
>REM PIP
>SET /UIC=E200,200J
>@ <EDF>

7-7

DETAILS OF SYSGEN PHASE III

Notes for the terminal output from SYSGEN
target system) :

Phase

III

(for

mapped

(»

Invokes Phase III.

When you enter an asterisk (*) as a response to Question 5,
SYSGEN displays a list of the nonprivileged tasks that you can
task-build.

Enter the names of the tasks you want task-built for your target
system, then terminate your input with a period.

The system generation procedure is now complete.
You may want to make
some adjustments to your system after you have had some time to use
it. Appendix D may help you to adjust the amount of pool space your
system needs.
In addition, the RSX-llM/M-PLUS System Management Guide
may also help you to optimize your system's performance.

7-8

CHAPTER 8
SYSGEN ERROR MESSAGES

All error messages from 8Y8GEN appear in this chapter in alphabetical
order. The descriptions that follow each message explain the possible
cause and, as necessary, suggest remedial action.
8GN -- You attempted to
<parm> -- RETRY

use

non-existent

default

for

parameter

Explanation: A required parameter was missing from the response
to the current peripheral question. 8Y8GEN replaces <parm> with
a number indicating the position in the prompt line of the
missing parameter.
Reenter the entire response.
Note that the
[L/R] parameter is not considered as one of missing parameters.
8GN -- Baseline terminal driver
protection selected

not

valid

option

with

multiuser

Explanation: The half-duplex baseline terminal driver includes
no 8Y8GEN options and cannot execute in a multiuser protection
system (for example, the breakthrough write option is required
but not included). Choose a different terminal driver.
8GN -- CO driver not valid on R8X-118 systems

Explanation: R8X-118 systems cannot include the
(CO). 8Y8GEN ignores this entry.

console

driver

Explanation: Unmapped systems cannot include the console
(CO). 8Y8GEN ignores this entry.

driver

8GN -- CO driver not valid on unmapped system

8GN -- Correct problems and reassemble the bad modules;
continue when done

8Y8GEN

will

Explanation: This message indicates that you detected an error
in the Executive or device drivers assembly (you responded No at
either the Executive or driver EOX breakpoint).
After you
correct
the error, reassemble the bad modules and 8Y8GEN
continues.
8GN -- Correct problems -- 8Y8GEN 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, 8Y8GEN attempts to reassemble the laboratory
peripherals common area(s).
8-1

SYSGEN ERROR MESSAGES
SGN -- DMll-BB CSR address
specified -- RETRY

must

greater

than

157777

Explanation:
If the system includes a DMll-BB, the CSR address
must be greater than or equal to 160000.
If DMll-BB is not
included, the CSR address must be O.
SGN -- DMll-BB vector address
specified -- RETRY

must

greater

than

277

Explanation:
If the system includes a DMll-BB, the interrupt
If DMll-BB
vector address must be greater than or equal to 300.
is not included, the vector address must be 0.
SGN -- DU not valid on an unmapped system -- SUPPRESSED
Explanation: Unmapped systems cannot
SYSGEN ignores this entry.
SGN -- Dynamic storage
words -- RETRY

space

must

support

the

UDA50

(DU:).

two

multiples

Explanation: The system allocates pool
in four-byte sections.
Thus, the amount of pool must be a multiple of four bytes.
SGN -- EDT only built for mapped systems with a
driver.

full-duplex

terminal

Explanation:
You must be generating a mapped system with a
full-duplex terminal driver to include EDT in your target system.
Otherwise, SYSGEN does not build the task.
SGN -- FCP <fcp> not valid on an unmapped system -- RETRY
Explanation:
The FCP indicated
is not available
systems.
SYSGEN reprompts for different FCP.

unmapped

SGN -- File <file>.BLD does not exist
Explanation:
SYSGEN cannot find the specified task's .BLD file,
which SYSGEN needs to dynamically create the .CMD and .ODL files
for that task.
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 your system generation specifying 124K or
less for memory size.
SGN -- Illegal character in numeric response -- RETRY
Explanation: A character other than 0 through 7 for an octal
response or 0 through 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.

8-2

SYSGEN ERROR MESSAGES
SGN -- Illegal device mnemonic -- RETRY
Explanation:
You specified a drive type that the device does not
support (such as an RP06 for a DL device).
SGN -- Illegal numeric answer -- RETRY
Explanation:
response.

See the description of illegal character in numeric

SGN -- Illegal printer specification -- Valid types are LPll-A, B, C,
D, E, F, H,
J, K, R, s, v, w, Y, z, LSll, LA180, LNOl, and
LVll -- RETRY
Explanation:
SYSGEN only supports the line printer controllers
listed.
If you have a different controller,
refer to the
Peripheral Options question concerning LP:
to match your printer
characteristics with a DIGITAL printer.
SGN -- Illegal trailing characters or extra parameters "parm" -- RETRY
Explanation:
You have specified more parameters than allowed for
this response.
Note that parameters in brackets can only be
specified for the first controller of this type.
SGN -- Indirect Command Processor error encountered in <file>.BLD
Explanation: SYSGEN encountered an error while processing the
specified .BLD file.
The .CMD and .ODL files created by the .BLD
file may not have been created correctly.
SGN -- Input saved answer file <file> does not exist -- RETRY
Explanation:
Either the indicated input saved answer file does
not exist, or SYSGEN had a problem referencing the file.
SYSGEN
repeats Setup Question 8.
SGN -- Invalid directive code <direc-code>
You have entered other than A, B, C, D, E, F, G, H,
Explanation:
The line is discarded.
I, J, K, or L.
SGN -- Invalid FCP code <fcp code> entered -- RETRY
Explanation:
You have entered an FCP code other than A, B, C, D,
or E.
SYSGEN reprompts for a valid FCP code.
SGN -- Invalid system device -- RETRY
Explanation:
The device specification for the
disk was incorrectly entered.

Executive

source

Big disk kits:
The default response is SY:; enter either Y or
press the RETURN key.
Otherwise, you must enter at least two
characters to identify the device that contains the Executive
sources.

8-3

SYSGEN ERROR MESSAGES
RLOl kits:
There is no default response to this question.
Enter
at least two characters to identify the device that contains the
Executive sources.
SGN -- Listing files cannot be sent directly to LP: -- RETRY
Explanation: Spooled listings must go to a spool device.
Also,
for on-line SYSGENs, maps cannot be spooled 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 -- Mapping option of the input saved answer file is different from
the mapping option selected in Question 5
Explanation: The mapping option that you specified in Question 5
of the Phase I Setup Section conflicts with the mapping option in
the input saved answer file.
For instance, your response to
Question 5 may indicate that you want to generate an unmapped
system, but the input saved answer file indicates a mapped
system.
Reinvoke SYSGEN and select an input saved answer file that
corresponds to the type of system (mapped or unmapped) that you
indicated in Setup Question 5.
SGN -- Maps cannot be sent directly to line printer

RETRY

Explanation: Spooled maps must first go to a spool device.
Also, for on-line SYSGENs, the maps cannot be spooled directly to
the line printer (specify LPO:).
SGN -- Maximum of 1 CRT monitor possible with VTll -- RETRY
Explanation: A VS60 can support two CRT
supports only one.
SGN

monitors,

but

VTll

Maximum of 8 printers allowed on a system with a KMC -- RETRY
Explanation:

The KMC-11 supports up through 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 controllers are specified later.

8-4

SYSGEN ERROR MESSAGES
SGN -- Memory management and loadable drivers options
to include DHVll support

support

needed

Explanation: You tried to include DHVll support without first
including full-duplex terminal driver support (Question 1, Option
C in the Terminal Driver Options Section) which requires memory
management support (Question 5 in the Setup Section) and loadable
drivers options support (Question 15 in the Executive Options
Section) •
Restart SYSGEN using the saved answer file you just created
($SAO)
and include memory mangement support and loadable drivers
support.
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 more than 28K words of memory
for an unmapped system (Question 3 in the Target Configuration
Section) or less than 24K words of memory for a mapped system.
SGN -- Memory not multiple of 4K
Explanation:
of 4.

When you specify memory size, it must be a multiple

SGN -- More than 252.

modules specified -- RETRY

Explanation: The UDC-11 supports a maximum of 252 modules.
have specified more than the maximum.

You

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
that you have indicated as occupied by other modules.

use

slots

Review your configuration and try again.
SGN -- Parameter (in) <parm> out of range <min> to <max>
Explanation: The
indicated
parameter
Loadable/Resident) is not within the acceptable range.

8-5

RETRY
(excluding

SYSGEN ERROR MESSAGES
SGN -- Pausing to allow editing of Executive source
Explanation: This is not an error message;
informative.
It appears when you indicate
Executive files.

the message is
you wish to edit

SGN -- Procedure can only be executed under the ICP.TSK version of the
Indirect Command Processor
Explanation:
ICQ.TSK and
condition.

The Indirect Command Processor presently running is
has limited capability.
SYSGEN exits under this

Remove AT., install ICP.TSK (the version of the Indirect Command
Processor with the capability required for system generation),
then reinvoke SYSGEN.
SGN -- Procedure can only be run from MCR or DCL
Explanation: The Indirect command procedure has been invoked
from a user-written CLI. SYSGEN exits under this condition.
Set your terminal to either MCR or DCL and reinvoke SYSGEN.
SGN -- Saved
answer
file
for
a
(SGNSTAND.CMD) does not exist

Standard

Function

System

Explanation:
Either the saved answer file SGNSTAND.CMD does not
exist in the current UFO on the SY: disk, or SYSGEN has a
problem referencing it. SYSGEN repeats Setup Question 8 under
this condition.
SGN -- Standard Function System requires at least 96K words of memory
Explanation: You cannot generate the Standard Function System
because the target system does not have sufficient memory.
SYSGEN exits under this condition.
Reinvoke SYSGEN but do not choose the Standard Function System.
SGN -- String <string> ignored
Explanation: The <string> portion of the response to Question 5
of Phase III
is invalid.
SYSGEN ignores that part of your
response.
SGN -- SYSGEN encountered an unrecoverable
<module>
Explanation:
SYSGEN encountered an
the module <module>.

error

within

unrecoverable

the

module

error

within

Submit an SPR for the problem and include a hardcopy listing of
the SYSGEN dialog, as well as the saved answer file that was
created from SYSGEN.

8-6

SYSGEN ERROR MESSAGES
SGN -- Task <task> is not built for unmapped systems
Explanation: SYSGEN cannot build the indicated task for
unmapped system. The task is valid on mapped systems only.

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
management support and loadable driver
full-duplex terminal driver.

must include memory
support to select the

SGN -- Unit number must be an integer in the range 0 to 7
Explanation:

The crash device must be a unit number 0 through 7.

SGN -- Unrecognizable string "ddn" -- Ignored
Explanation: SYSGEN could not
Perhaps you omitted a comma.

the

indicated

string.

unit

indicators

are

parse

SGN -- Valid character detection expander
(yes) and "NO"
(no) -- RETRY

"C"

Explanation: Valid responses for this parameter are C
to
indicate that the controller includes a character unit and NO to
indicate that it does not.
SGN -- Valid D/A present
(no) -- RETRY

indicators

are

"D"

(yes)

and

"NO"

Explanation: Valid responses for this parameter are D, to
indicate that the controller includes a D/A converter and NO to
indicate that it does not.
SGN -- Valid devices: DT, DK, MT, MS, MM, DB, DM,
DX, and DY -- RETRY

DL,

DD,

DR,

DU,

Explanation: The Executive crash module
device you entered as a dump device.

not

support

the

SGN -- Valid DRll-K present
(no) -- RETRY

indicators

are

does

"DRK"

(yes)

and

"NO"

Explanation: Valid responses for this parameter are DRK to
indicate that DRll-K is present and NO to indicate that it is
not.
SGN -- Valid duplex indicators are "H" and "F" -- RETRY
Explanation: Valid responses for this parameter are H, to
indicate a half-duplex line and F to indicate a full-duplex line.

8-7

SYSGEN ERROR MESSAGES
SGN -- Valid error detection expander unit indicators
and NO (no) -- RETRY

are

"E"

(yes)

Explanation:
Valid responses for this parameter are E to
indicate that the 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 a half-duplex line, P to indicate primary station of
line, and F to indicate a full-duplex line.
SGN -- Valid graphic device 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 a
VS60 graphics display device.
SGN -- Valid line speeds are 50, 75, 110, 134.5, 150, 200,
1200, 2400, 4800, and 9600 -- RETRY
Explanation:
line speed.

The DHll controller does not support the

SGN -- Valid line speeds are 75, 110, 134.5, 150, 300,
1800, 2000, 2400, 4800, 9600, and 19200 -- RETRY
Explanation:
line speed.

300,

600,

specified

600,

1200,

The DHVll controller does not support the specified

SGN -- Valid offset
(no) -- RETRY

recovery

indicators

are

"O"

(yes)

and

"NO"

Explanation:
Valid responses for this parameter are O to
indicate that all controllers of this type support offset
recovery, and NO to indicate that none of the controllers of this
type support it.
SGN -- WARNING -- Console terminal interface (YL) forced into system
Explanation:
RSX-llM requires
a
terminal
interface
for
operation.
You failed to specify a terminal interface in your
system, so SYSGEN included the console terminal interface
(YL)
for you~
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.

8-8

SYSGEN ERROR MESSAGES
SGN -- WARNING -- Input saved answers for Phase <n> may be incomplete

Explanation:

The saved answer file presently being used for
input to SYSGEN does not contain answers for all or ~ne questions
in either Phase I or Phase II.
(The error message specifies the
exact phase of SYSGEN that was preempted.) Therefore, SYSGEN
prompts you for input to those questions that do not have saved
responses.
SGN -- WARNING -- Null device forced into system

Explanation: This message indicates that SYSGEN has forced the
null device into your configuration. The null 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).

8-9

APPENDIX A

SAVED ANSWER SYMBOLS

This appendix lists all of the possible symbols that could be created
during SYSGEN and stored in your saved answer file.
At some time you
may wish to examine a previously generated saved answer file to see
which options you included or excluded.
Following each symbol listed below is a key indicating the exact
SYSGEN section and question number associated with the symbol and the
text of the specific SYSGEN question. The exact text of the question
is not always given below when it is more helpful to expand the text.
The legend below defines the keys used to identify the SYSGEN phase
and question number associated with each symbol. For example, the key
S0-4, following the symbol $FCP, indicates that the symbol $FCP is
associated with Question 4 in the System Options Section of SYSGEN
Phase I.
Legend:
S
TC
HC
E
TT
SO
EB
DB
TB
V

Symbol

Setup Questions Section (Phase I)
Target Configuration Section (Phase I)
Host Configuration Section (Phase I)
Executive Options Section (Phase I)
Terminal Driver Options Section (Phase I)
System Options Section (Phase I)
Exec TKB Section (Phase II)
Loadable Driver Build Section (Phase II)
Privileged TKB Section (Phase II)
System VMR Section (Phase II)
Key

$MAP

Definition
Is the system mapped (True) or unmapped {False)?

$TPR

TC-1

Processor Type

$SWR

TC-2

Does the processor have a switch register?

$TME

TC-3

Memory size {in K-word blocks)

$KSR

TC-4

Include support for K-series devices?

$EAE

TC-5

Extended arithmetic element (KEll-A/B EAE)
present?

$FPP

TC-6

Floating point processor {FPll) present?

A-1

SAVED ANSWER SYMBOLS
Symbol

Key

Definition

$FIS

TC-7

Floating instruction set (FIS) present?

$EIS

TC-8

Extended instruction set (EIS) present?

$PRO

TC-9

Number of KW-llP clock interrupts per second

$LIN

TC-10

Line frequency: A-60Hz

$WAT

TC-11

KWll-Y Watchdog timer support?

$MPR

TC-12

Memory parity support?

$CAH

TC-13

Cache memory support?

$HIV

TC-14

Highest interrupt vector

$DEV

TC-15

Peripheral devices and number of controllers

$DV2

TC-15

Peripheral devices and number of controllers

$DV3

TC-15

Peripheral devices and number of controllers

$LPR

HC-1

Is a line printer available?

$SPL

HC-2

Spool assembly listings and Executive and
driver maps?

$PWI

HC-3

Does the listing/map device have at least
120 columns?

$ALO

HC-4

Assembly listing file device

$MPD

HC-5

Map device for Executive and device drivers

$DBM

E-1

Include support for DBMS-11?

$Fll

E-2

FILES-11 ACP supported?

$RMS

E-·3

RMS bucket locking (file sharing) and placement
control?

$NRT

E-4

Non-resident tasks (task loader) supported?

$LLR

E-5

Loadable task loader supported?

$DRC

E-6

Executive Common support?

$MMD

E-7

Memory management (PLAS) directives supported?

$SRR

E-8

Send/Receive By Reference directives supported?

$GMC

E-9

Get Mapping Context directive supported?

$ACK

E-10

Address checking supported?

$IOR

E-11

I/0 rundown supported?

$MOP

E-12

Multi-user protection supported?

$ANM

E-13

ANSI magtape support?

$000

E-14

Online formatting (FMT) and diagnostic QIOs
supported?

A-2

B-50Hz

SAVED ANSWER SYMBOLS

Symbol

Key

Definition

$LOD

E-15

Loadable device drivers supported?

$LLD

E-16

Is the default for drivers loadable or resident?

$AST

E-17

Include Asynchronous System Trap (AST) support?

$CSM

E-18

Include Cancel Selective Marktime support?

$TKT

E-19

Support task termination and device not ready
messages?

$PRF

E-20

Support power fail recovery?

$IRR

E-21

Support install, request and remove on exit
(MCR RUN)?

$20K

E-22

Large (20K) Executive supported?

$LGD

E-23

Logical device assignment supported?

$ERL

E-24

Include support for error logging?

$UWD

E-25

Do you intend to include a user-written driver?

$GTW

E-26

Include the $GTWRD (get word) Executive routine?

$PTW

E-27

Include the $PTWRD (put word) Executive routine?

$WCH

E-28

Disk writecheck supported?

$SWL

E-29

Software write-lock supported?

$XDT

E-30

Executive Debugging Tool (XDT) supported?

$ROT

E-31

Rotating pattern in data lights supported?

$NET

E-32

Communications products supported?

$DMA

E-33

System-controlled partitions supported?

$AMC

E-34

Include support for the Shuffler?

$PRN

E-35

Queue manager and queued print spooler
supported?

$GGE

E-36

Group global event flags supported?

$DRR

E-37

Supported system directives:
See the documentation of Question 37 for the
relationship between the directives and the
associated letter codes.

$NPK

E-38

Number of pre-allocated QIO packets

$DTV

E-39

Size of the data transfer vector in words

$RRS

E-40

Round-robin scheduling interval in ticks
A value of 0 excludes the round-robin
scheduler

$HIC

E-41

Highest priority class for round-robin
scheduling

A-3

SAVED ANSWER SYMBOLS
Symbol

Key

Definition

$LOC

E-42

Lowest priority class for round-robin scheduling

$OKS

E-43

Executive level disk swapping interval

$SWP

E-44

Swapping priority

$DSA

E-45

Size of the dynamic storage region (pool}
in words

$PNR

E-46

Seconds between printer not ready messages

$CRR

E-47

Seconds between card reader not ready messages

$RSD

E-48

System crash register and stack dump device CSR

$CHK

E-49

Checkpointing?

$DYN

E-50

Checkpointing with system checkpoint file?

$CRA

E-51

Type of crash dump analysis:

$NOT

E-52

CDA output notification device CSR

$MOD

E-53

CDA memory dump device mnemonic

$MDC

E-54

CDA memory dump device CSR

$POD

E-55

PANIC memory dump device CSR

$RTE

E-56

RT-11 emulation support?

$TTY

TT-1

Terminal driver desired:
Consult documentation for Question 1 for
letter code and associated terminal
driver.

$TMN

TT-2

Unsolicited input timeout value in seconds

$FRM

TT-3

Pass form feeds directly to the terminal?

$ACR

TT-4

Automatic carriage return/line feed?

$TCK

TT-5

Task checkpointable during terminal input?

$USC

TT-6

Unsolicited input character AST supported?

$CNO

TT-7

Write with CTRL/O cancellation supported?

$BWS

TT-8

Breakthrough write supported?

$CNR

TT-9

CTRL/R retype supported?

$ESC

TT-10

Escape sequence handling?

$MLC

TT-11

Support for get multiple characteristics?

$SMC

TT-12

Support for set multiple characteristics?

$GTD

TT-13

Support for get terminal driver options?

$HSM

TT-14

Hold screen mode supported?

A-4

A-PANIC

B-CDA

SAVED ANSWER SYMBOLS
Symbol

Key

Definition

$TRW

TT-15

Transparent read/write supported?

$SCC

TT-16

Settable case conversion for input supported?

$RAP

TT-17

Support for read after prompt?

$RNE

TT-18

Support for read with no echo?

$RST

TT-19

Support for read with special terminator?

$RUB

TT-20

CRT rubout support?

$THS

TT-21

CTRL/S and CTRL/Q supported?

$TIB

TT-22

Support for user terminal input buffering?

$VTB

TT-23

Support for variable length terminal input
buffering?

$L30

TT-24

LA30P supported?

$HRE

TT-25

Support hardware unrecoverable input error
notification?

$DIC

TT-26

Support device independent cursor positioning?

$BBF

S0-1

ANSLIB.OLB desired for Big-buffering?

$ISA

S0-2

Build the library of ISA FORTRAN industrial/lab
routines?

$FRL

S0-3

Build the PLAS resident FCS?

$FCP

S0-4

Code for FCP
Consult documentation for Question 3 for
letter code and associated version of
FllACP.

$PMD

S0-5

Post Mortem Dump (PMD)

$RMD

S0-6

Resource Monitoring Display task (RMD)
supported?

$PRT

S0-7

Non-queue manager print spooler (PRT) supported?

$DCL

S0-8

Digital Command Language (DCL) supported?

$NOC

S0-9

Number of user-written CLis:

$PMT

S0-10

Support for pool monitoring/low pool recovery
(PMT)?

$NOD

S0-11

System name (up to 6 alphanumeric characters)

$SPM

S0-12

Do you want SPM-11 support?

$LEM

EB-1

List executive map?

$LDM

DB-3

Device mnemonic for loadable driver maps

$BAD

DB-4

Build all selected loadable drivers into DRVPAR?

A-5

supported?

SAVED ANSWER SYMBOLS
Symbol

Key

Definition

$LDxN

DB-5

Loadable driver 2-character device mnemonic

$LDxP

DB-6

Loadable driver partition name

$LDxB

DB-7

Loadable driver x partition base address

$PRM

TB-1

Device mnemonic for privileged task maps

$GPB

TB-2

GEN's base address

$SPB

TB-3

SYSPAR's base address

$PPB

TB-4

SPLPAR's base address

$EDF

TB-5

Pause to edit any task build .CMD or ODL files?

$DFL

TB-6

Delete task build .CMD and .ODL files after
task building?

$ERV

V-1

Edit SYSVMR.CMD?

A-6

APPENDIX B
HARDWARE BOOTSTRAP PROCEDURES

Bootstrapping a device involves using the central processor unit (CPU)
console switches to initiate a hardware loader. The hardware loader
contains machine instructions for reading a special record from the
device.
The record, called a bootstrap record, is transferred into
memory and executes a specially designed software program.
For the
bootstrap operation to succeed, the device accessed must be on line
and ready;
the medium accessed must contain a proper bootstrap
record;
and the console terminal must be on line.
The PDP-11 console switches and their use are described
in the
Processor Handbook.
The bootstrap procedure that you should use
depends upon the type of hardware bootstrap device on the system.
Table B-1 summarizes the addresses needed to bootstrap each device.
The detailed procedures to bootstrap a device are presented according
to the types of hardware bootstrap devices available.

B.l

GENERAL BOOTSTRAPPING PROCEDURE

The following procedures give a general description of the
necessary
to
hardware bootstrap a magnetic tape and a
respectively.

steps
disk,

To bootstrap a magnetic tape:

Physically mount the magnetic tape
(for
instance,
the
stand-alone BRU64K tape)
on unit O, with the write-enable
ring removed.

Ensure that the tape is at its load point.
(The BOT
indicator light comes on.)
The CPU does not bootstrap the
device unless the tape is at its load point.

Set the ON-LINE/OFF-LINE switch on the tape unit to
and ensure that the ROY indicator is lit.

Ensure that the console terminal is on line.

Follow the bootstrap instructions (in this appendix)
particular bootstrap you must use.

ON-LINE,

for

the

baseline

disk

To bootstrap a disk volume:
1.

Insert the disk volume
RSXM35) in a free unit.

(for

Ensure that the RDY light is on.

B-1

instance,

the

HARDWARE BOOTSTRAP PROCEDURES

Ensure that the console terminal is on line.

Follow the bootstrap instructions (in this appendix) for
particular bootstrap you must use.

the

Table B-1
Summary of Hardware Bootstrap Addresses
Bootstrap Type
Device to Bootstrap
RFll disk

MRll-DB

M9301-YA

M9301-YB

M9301-YC

M9301-YF M9312

100

773100

RS03/RS04 disk
RK05 disk cartridge
unit 0

773110

RP02 or RP03 disk
pack unit 0

773154

RP04, RP05, or RP06
disk pack unit 0

RK05 disk

DKn

30+n

DKn

(unit n)

RL01/RL02 disk
unit n

DLn

RK06 disk (unit n)
RK07 disk

DMn

(unit n)
DPn

RP04, RP05, RP06,
RM02, RM03, RM05,
RPO?, or RM80
disk (unit n)

DPn

40+n

DPn

DBn

70+n

DBn

RA60/80/81, RC25

DUn
773136

TSll magnetic tape

MTn
MSn

TU16/TE16/TU45
/TU77 magnetic tape
TU56 DECtape

DMn
DMn

RP02 or RP03 disk
pack (unit n)

TU10/TE10 and TS03
magnetic tape

DKn

773120

B-2

MMn

DTn

HARDWARE BOOTSTRAP PROCEDURES

B.2

MRll-DB PROCEDURE

If the MRll-DB Bulk Storage Loader
following steps:

the

system,

perform

the

Move the CPU console ENABLE/HALT switch to its HALT
and back to its ENABLE position.

Set the CPU switch register to one of the following values:
773100
773110
773154
773136

B.3

for
for
for
for

position

RFll disk
RK05 disk cartridge
RP03 disk pack
TU10/TE10/TS03 magnetic tape

Press the CPU LOAD ADRS switch.

Press the CPU

S~ART

switch.

M9301-YA AND M9301-YB PROCEDURE

If the M9301-YA or M9301-YB Bootstrap Terminator
perform the following steps:
1.

the

system,

While holding down the CTRL switch, press the BOOT switch
the front of the CPU.

The bootstrap prints the contents (in octal) of registers RO,
R4, the stack pointer, and the program counter at the console
terminal.
It then prints a prompting character ($).
2.

In response to the prompting character, type the 2-character
device code and the unit number of the device to be
bootstrapped.
Terminate your response by pressing the RETURN
key.
Table B-2 describes the device codes.
Table B-2
Device Codes for M9301-YA and M9301-YB Bootstraps
Device

Code

TU10/TE10/TS03 magnetic tape

TU16/TE16/TU45/TU77 magnetic tapel

RK05 Disk cartridge

RP02/RP03 disk pack

RP04/RP05/RP06/RM02/RM03 disk packl

RS03/RS04 fixed head diskl

1. M9301-YB Bootstrap Terminator only.

B-3

HARDWARE BOOTSTRAP PROCEDURES

B.4

M9301-YC PROCEDURE

If the M9301-YC bootstrap is on
steps:

the

system,

perform

the

following

Move the CPU ENABLE/HALT switch to its HALT position and back
to its ENABLE position.

Set the start address of 17765000 with the console switches.

Press the CPU LOAD ADDR switch.

Set the device unit number with switches 0 through 2.

Set the device code for the device to be bootstrapped
switches 3 through 6.
Table B-3 lists the device codes.
Table B-3
Device Codes for the M9301-YC Bootstrap
Device

Code

TU10/TE10/TS03 magnetic tape

RK05 disk cartridge

RP02/RP03 disk pack

TU16/TE16/TU45/TU77 magnetic tape

RP04/RP05/RP06/RM02/RM03 disk pack

RS03/RS04 fixed head disk

Ensure that switches 7 through 21 are off (down).

Press the CPU START switch.
NOTE
Before the M9301-YC bootstrap actually
bootstraps the system, it performs CPU
tests, instruction and addressing tests,
and
memory and cache tests.
If a
hardware failure
is
detected,
the
diagnostic program halts.
The lights
contain the ROM address of the halt.
If
.a-i.....1 1
occurs,
1..ut
Ll.L\:l.L
field
service engineer.
~~

T'\T,..Tm"J\r

'--Q..L..L

.1.~u

It may, however, be possible to continue
with the bootstrap operation if the
lights contain the address
1773764,
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.

B-4

HARDWARE BOOTSTRAP PROCEDURES

B.5

M9301-YF PROCEDURE

If the M9301-YF Bootstrap Terminator is on

the

system,

perform

the

While holding down the CTRL switch, press the BOOT switch
the front of the CPU.

The bootstrap prints the contents (in octal) of registers RO,
R4, the stack pointer, and R5 at the console terminal.
It
then prints a prompting character.

In response to the prompting character, type the 2-character
device code and unit number of the device to be bootstrapped.
Terminate your response by pressing the RETURN key=
Table
B-4 lists the device codes.

-----··---;;;; ---J::'--

fnllnwinn

~t-i:::-n~!

Table B-4
Device Codes for the M9301-YF Bootstrap
Device

Code

TU10/TE10/TS03 magnetic tape

TU16/TE16/TU45/TU77 magnetic tape

RK05 disk cartridge

RK06/RK07 disk cartridge

RP02/RP03 disk pack

RP04/RP05/RP06/RM02/RM03 disk pack

RS03/RS04 fixed head disk

B.6

M9312 PROCEDURE

The M9312 contains independent programs that can bootstrap programs
into memory from a selected peripheral device. Through front panal
control or folowing power-up, the computer can execute a bootstrap
directly, without manual keying of the initial program. The M9312
contains four sockets for peripheral bootstrap loader programs encoded
in
ROMs.
The
choice
of ROMs is determined by the system
configuration.
After execution of the CPU diagnostics, the M9312 turns control of the
system over to the user at the console terminal.
The system prints
out status information and is ready to accept simple user commands for
checking and modifying information within the computer, starting a
program already in memory, or executing a device bootstrap.
If the M9312 Bootstrap Terminator is on the system, perform one of the
following procedures:
•

If you have the M9312 Console Emulator on the system, follow
the procedures in Section B.10.l (PDP-ll/60s and PDP-ll/70s
usually do not have console emulators) •
If that procedure
does not work, perform the next step to verify that you have
a console emulator.

B-5

HARDWARE BOOTSTRAP PROCEDURES

•

If you have a CPU equipped with switch registers and do not
know what devices the M9312 will boot, perform the procedures
in Section B.10.2.

•

If you have a CPU equipped with switch registers, know what
device ROMs are on the M9312 Bootstrap Module, but do not
have a console emulator, follow the procedures in Section
B.10.3.

•

If you do not have the M9312 Bootstrap Terminator on your
system and need to boot the RLOl, Rl02, or the RK07 disk
device, perform the manual load routine described in Section
B.7.

B.6.1

Using M9312 Console Emulator

The M9312 Console Emulator can be initiated in two ways depending
the type of CPU (push button or switch register) on the sytem.

B.6.1.1
1.

Push-Button Boot using the M9312 Console Emulator

While holding down the CTRL button, press the BOOT button
the CPU.

The bootstrap prints the contents (in octal) of registers RO,
R4,
the stack pointer, and RS at the console terminal.
It
then prints a prompting character.
2.

B.6.1.2

In response to the prompting character, type the 2-character
device code and the unit number of the device to be
bootstrapped.
Terminate your response by pressing the RETURN
key.
If the unit number is not entered, it is assumed to be
zero.
Table B-S lists the device codes.

Switch Register Boot using the M9312 Console Emulator

Move the CPU console ENABLE/HALT switch to its HALT
then back to its ENABLE position.

Set the CPU switch register to 76S020.

Press the START switch. The bootstrap prints the contents
(in octal) of registers RO, R4, the stack pointer, and RS at
the console terminal.
It then prints a prompting character
(@) •

B-6

position

HARDWARE BOOTSTRAP PROCEDURES
Table B-5
Device Names and Mnemonrcs
Device To
Be Booted

Mnemonic

Unit

Octal
Data

RLOl

0-3

042114

RK06/RK07

0-7

042115

RXOl

0-1

042130

RX02

0-1

042131

RS03/RS04

0-7

042123

RP02/RP03
RP04/RP05/RP06
RM02/RM03/RM05
RM80/RP07

DP
DB

0-7
0-7

042120

Dal

RA60/RA80
RA81/RC25

0-7

042125

RK03/RK05
TU55/TU56

DK
DT

0-7
0-7

042113

TSll

0-7

046523

TU16/TE16/
TU45/TU77

0-7

046515

TU10/TE10/TS03

0-7

046524

Console Emulator
CPU ROM

N/A

040460

Diagnostic ROM
PDP-11/60/70

N/A

041060
177776 2
XXX777 3

1. Type DB rather than DR if you
RM03, RM05, RM80, or RPO? disk.

are

booting

the

RM02,

2. This is a continuation ROM of a multiple ROM boot.
3. Bad ROM or NO ROM present.
4.

In response to the prompting character type, the 2-character
device code and the unit number of the device to be
bootstrapped. Terminate your response by pressing the RETURN
key.
The prompting character returns at this point if the
correct boot ROM was not installed, or if a nonexistent
device code is entered.
If the contents of the registers RO,
R4, stack pointer, and RS appear before the prompting
character, this indicates that at least one boot ROM socket
is empty and it can accommodate another boot ROM.
If the unit number is not entered, it is assumed to be
Table B-5 lists the device codes.

B-7

zero.

HARDWARE BOOTSTRAP PROCEDURES

Successful completion of the switch register
bootstrap
procedure
produces
header
information on the console
terminal, similar to the example given for the Push Button
Boot. After the message appears, begin the system generation
process.

B.7

BOOTSTRAP LOAD PROGRAM FOR THE RLOl/02 AND RK07

To bootstrap an RLOl, RL02, or RK07 device when the system does not
have the M9312 Bootstrap Module, you must manually enter a bootstrap
load ROUTINE using the CPU console. The following procedure describes
the manual load process for the PDP-11/34 (a similar procedure is
followed using the CPU LOAD ADRS, DEP, and EXAM switches for the
PDP-11/70 computer):
1.

While holding down the CTRL button, press the
on the CPU.

HLT/SS

Set address 1000 in the
numbered console buttons.

Press the LAD (load address) button.

Press the CLR button to clear the register.

Load the contents that appears in Table B-6 into memory using
the numbered buttons and the DEP button.
Press the CLR
button after you have placed the contents in the CPU register
and pressed the DEP button.

console

button

using

the

After the contents are loaded, perform the following steps:
1.

Set address 1000 in the console register again by
numbered buttons.

using

the

Press the LAD (load address) button.

While holding the CTRL button down, press the START button on
the CPU to boot the device.

You can verify the accuracy of the load ROUTINE by using the CPU EXAM
button.
Set address 1000 in the console register register and press
the LAD button. Press the EXAM button to reveal the contents of
address 1000.
It should be 12700 for both the RLOl, RL02, and RL07
routines. Continue to press the EXAM button to check the contents of
the remaining addresses in the load ROUTINE. Use the LAD and the DEP
buttons to correct any e~roneous contents.

B-8

HARDWARE BOOTSTRAP PROCEDURES
Table B-6
RLOl/02 and RK07 Load Routines
RL01/RL02 Bootstrap
Routine

RK07 Bootstrap
Routine

Address

Contents

1000:
1002:
1004:
1006:
1010:
1012:
1014:
1016:
1020:
1022:
1024:
1026:
1030:
1032:
1034:
1036:
1040:
1042:
1044:
1046:
1050:
1052:
1054:
1056:
1060:
1062:
1064:
1066:
1070:
1072:
1074:

12700
174400
12760
13

12700
177440
12760

10
12701
20033
10110
105710
100376
12760
177400
2
62701
16
10110
105710
100376
5710
100001
0
5007

12701
42
10110
105710
100376
12760
177601
4

5721
10110
105710
100376
12760
177400
6
5060
4
62701
6
10110
105710
100376
5710
100001
0
5007

1. Select drive number 0 through 7 for the RK07.
2. Load 4 for unit 0, 404 for unit 1, 1004
and 1404 for unit 3.

for

unit

3. Load 3 for RK06.

B.8

BOOTSTRAP LOAD PROGRAM FOR THE TUlO, TElO, OR TS03

To bootstrap a TU10/TE10/TS03 magnetic tape when the system does not
have a bootstrap that handles
it, you must manually enter a load
ROUTINE into memory using the CPU console switch register and the DEP
switch.

B-9

HARDWARE BOOTSTRAP PROCEDURES

To load the routine, perform the following steps:
1.

Move the CPU console ENABLE/HALT switch to its HALT
and back to its ENABLE position.

Set the CPU switch register to 010000.

Press the CPU LOAD ADRS switch.

Load the following contents
Register and DEP switch.
Address

Contents

010000
010002
010004
010006
010010
010012
010014
010016
010020
010022
010024
010026
010030
010032
010034
010036

012700
172524
005310
012740
060011
105710
100376
005710
100767
012710
060003
105710
100376
005710
100777
005007

into

memory

Set the console switch register to 010000.

Press the CPU LOAD ADRS switch.

Press the CPU START switch.

using

the

position

Switch

If the system reads the tape but halts at address 010034, the magnetic
tape generated a parity error. Try another drive and make it unit O.
If the system appears to take no action and halts, verify the accuracy
of the routine by using the CPU console EXAM switch. Use the switch
register and the DEP switch to correct any erroneous contents.
Rewind
the tape to its load point before executing the routine again.
If no
recovery is successful, you should have a DIGITAL field service
representative check the device.
If the hardware is working properly,
you should use a new magnetic tape reel.

B-10

APPENDIX C
RSX-llM DEVICES

This appendix is a table of RSX-llM devices.
It lists the device
mnemonic, the device type, and the associated device controller. The
bottom section of Table C-1 separately lists pseudo devices.
Table C-1
RSX-llM Devices
Mnemonic
AD
AF
AR
CR
CT
DB
DD
DF
DK
DL
DM
DP
DR
DS
DT
DU

DX
DY
EM
GR
IC
IP
IS
LA
LP
LS
MF
MM
MS
MT
pp

Hardware Controller

Device
Analog-to-Digital Converter
Analog-to-Digital Converter
Laboratory Peripheral Subsystem
Card Reader
TU60 Cassette
RP04/05/06 disk drive
TU58 DECtape II
RF ll di s k d r i Ve
RKOS/J/F cartridge disk drive
RL01/RL02 disk drive
RK06/07 cartridge disk drive
RP02/03 disk drive
RM02/03/05 disk drive
RM80/RP07 fixed media
RS03/04 fixed-head disk drive
TU56 DECtape
RA60 removable media
RA80/81 fixed media
RC25 fixed/removable media
RD51 fixed media
RXSO floppy disk
RXOl floppy disk drive
RX02 floppy disk drive
MLll Nonrotating Electronic Memory
Graphics Display Processor and Scope
Industrial Control Subsystem
Industrial Control Subsystem
Industrial Control Subsystem
Laboratory Peripheral Accelerator
Line Printer
Laboratory Peripheral Subsystem
TU78 magtape drive
TU45/TU16/TE16/TU77 magtape drive
TSll/TSV05/TU80 magtapes
TS03/TU10/TE10 magtape drive
Paper Tape Punch

ADOl-D
AFCll
ARll
CRll/CMll-E
TAll
RH11/RH70
DLll
RFll
RKll
RL11/RLV11/RL21/RLV21
RK6 ll/RK7 ll
RPll/RPllC
RH11/RH70
RH70
RH11/RH70
TCll
UDASO
UDASO
RC25
RQDXl
RQDXl
RXll
RX211/RXV21/RXV12
RH70
VT11/VS60
ICR/ICSll
IP11/IP300
DRS/DSll
LPAll-K
LAll/LPll/LSll/LVll
LPSll
RH70/TM78
RH11/RH70/TM02/TM03
TSll
TMll/TMAll/TMB 11
PCll

(continued on next page)

C-1

RSX-llM DEVICES

Table C-1 (Cont.)
RSX-llM Devices
Mnemonic

Hardware Controller

Device

YH
YJ
YL
YZ

Paper Tape Reader
Universal Digital Controller
Interprocessor Link
Interprocessor Link
Interprocessor Link
Synchronous Interface
Synchronous Interface
Synchronous Interface
Synchronous Interface
Asynchronous Terminal Interface
Asynchronous Terminal Interface
Asynchronous Terminal Interface
Asynchronous Terminal Interface

PCll/PRll
UDCll
DAll-B
DLll-E
DMC 11-E/DMR 11
DPll
DQll
DUll
DUPll
DHll/DHVll
DJll
DLll/A/B/C/D/E/J/W
DZll/DZVll

Mnemonic

Pseudo Device

Hardware Controller

Console Listing Pseudo Device
Console Output Pseudo Device
Library Default Pseudo Device
Null Device
System Default Pseudo Device
Terminal Input Pseudo Device

N/A
N/A
N/A
N/A
N/A
N/A

PR
OD
XB
XL
XM
XP
XQ
XU

LB
NL
SY
TI

C-2

APPENDIX D

FUNCTIONS IMPACTING POOL (DYNAMIC MEMORY)

D.l

COMMON FUNCTIONS

Use the following information when calculating the amount
(dynamic memory) to allocate during Phase I of SYSGEN.

pool

Tasks
Each task installed in the system
words for a task control block.

requires

least

25(10)

I/O Requests
Each I/O request results in the allocation of an 18(10)-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(10)-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 18(10) 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.

Open Files on Files-11 Disks
Each open disk file requires a File Control Block for each file
header.
However, only one FCB is required, no matter how many
accessors there are to a particular file. The size of an FCB
is 22(10)
words.
If FllACP has sufficient buffer space, the
FCB will be contained within the task address space.
Each accessor to a disk file requires a window block.
(Each
LUN that has a file open counts as a separate accessor.) The
size of a window block varies depending on a number of factors:
•

The fixed portion of the window block is 7(10)
RSX-llM.

•

The variable portion of the
~imoc ~fl n'
wnrrlc
..
..,, \ .... ....,,

-- ··--

-----·

D-1

window

the

words

for

window

size

FUNCTIONS IMPACTING POOL (DYNAMIC MEMORY)
•

The window block is rounded
boundary for RSX-llM.

the

2(10)-word

The window size is determined when the file is accessed from:

• The value specified when the file is accessed
• The value specified when the volume was mounted
• The value specified when the volume was created
If none of the previous were specified or are unreasonable
• then
a value of 7 is used.
the window size is
A value of -1 has special significance;
determined by the number of pointers required to map all of the
file with a limit of about 100(10) words. The typical window
size is 28(10)
words. Therefore, the window size can exceed
250(10) words.
If block locking is enabled, each lock requires a primary
pool-lock block.
The size of this lock block is 4(10) words.
An initial entry is allocated when the file is first accessed
with locking enabled.
Additional entries are allocated as
required when the I/O takes place.
Lock blocks are only
released when the file is no longer accessed.
(Thus a cache of
lock blocks is available for quick use.)
Open Files on Labeled or Unlabeled Tapes
The window block is included in the Volume Control Block and
consequently no additional pool is required when a file is
accessed. There is no FCB equivalent.
All Mounted Volumes
Each mounted system volume and each mounted private volume
require a control block in a system-wide list of mounted
volumes. Each shared mounted volume requires a control block
for each separate user. The size of this block is 4(10) words.
Mounted Files-11 Disk Volumes
Each mounted disk volume r~quires a Volume Control Block (VCB) •
The VCB is 28(10) words long.
In addition, each header of the
index file requires an FCB, normally only one at 22(10) words.
This FCB will be allocated in the FllACP's internal pool if
possible. A window block is allocated for the index file. See
the
discussion on sizes and locations of file windows.
Additional FCBs will be allocated as needed for the fast
directory access cache controlled by the /LRU or /ACCESSED
keyword.
Mounted Labeled and Unlabeled Tapes
Each file-structured tape set requires a single Volume Control
Block
(regardless of the number of units or tapes), a Mounted
Volume List (MVL) entry for each device unit, and an Unmounted
Volume List
(UVL)
entry for each two-tape volume in the tape
volume set. The size of the VCB is 70(10) words, the MVL is
8(10) words, and UVL is 8(10) words.
Foreign Mounted Disks and Tapes
Each tape or disk mounted foreign requires only
The size of this short VCB is 10(10) words.
D-2

short

VCB.

FUNCTIONS IMPACTING POOL (DYNAMIC MEMORY)
Clock Queue Entries
Each clock queue entry requires
represent marktime, schedule, and

8(10)words.
-

-- .!

.=t .!

pe.r:.LUU.l(.;

_,_ -

These
..:i __ ,

.! -

::S(.;lleUU.L.l.111.J

entries
-- -

--- -

L.. -

Ley_ue::;L::;.

AST-Related Processing
Each powerfail, receive, and floating point processor AST
trap-enable for active tasks requires 8(10) words for an AST
control block. Half-duplex and full-duplex terminal drivers
allocate 14(10)-word blocks for single-character ASTs. At any
point in time, the full-duplex terminal driver will have only
one
AST
outstanding
on a given terminal, whereas the
half-duplex terminal driver could have many.
I/O Buffers
With the full-duplex terminal driver, output is buffered in the
terminal driver before it is transferred to the user buffer.
Each solicited and unsolicited input request requires
a
42(10)-word input buffer for half-duplex terminal drivers, and
successive 20(10)-word blocks, as needed, for the full-duplex
terminal driver.
Card Images
Card images read from the CM/CRll are buffered by the card
reader driver before the driver transfers the information to
the user buffer. Binary output requires an 80(10)-word buffer,
whereas ASCII input requires a 4(10)-word buffer.
Task Headers
In a mapped system, the task header is copied into a block of
memory allocated from the dynamic storage region. The standard
task header size for each task in memory (that is, in execution
and not checkpointed or inactive and fixed) is 62(10) words
with a default of six LUNs and one window block.
You can
specify up through 250 logical units for a task (2(10) words
per logical unit) and 7(10)
window blocks
(8(10)
words per
window block) •
It is possible that a task with many LUNs and window blocks
could use all the available dynamic memory.
If the loader
fails to load such a task
{that is, fails to allocate the
header for that task) , the loader tries to checkpoint any tasks
waiting to be checkpointed to free adequate contiguous pool
space.
If enough contiguous pool space does not become
available for the large task header, all tasks currently
running continue to run, but no tasks can be loaded.
Data Bases for Loadable Drivers
Data bases that are loaded into a system with a loadable driver
require the amount of memory equal to the size of the data
base.
Loadable Drivers
Loadable drivers on a mapped system require space for interrupt
linkage as follows:
•

14(10) words per interrupt
non-error-logging drivers

D-3

entry

for

single-controller,

FUNCTIONS IMPACTING POOL (DYNAMIC MEMORY)
•

22(10)
words per interrupt entry for multicontroller,
non-error-logging drivers le;l4(10) words for the first (or
only) interrupt entry for error-logging drivers, plus 6(10)
words for each additional interrupt entry for error-logging
drivers

Checkpointing
Systems with dynamic checkpoint space allocation require 8(10)
words to describe each checkpoint file and 8(10) words for each
task checkpointed to a checkpoint file.
Memory Management Directives
Systems supporting the memory management directives require
6(10)
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 Directive
Systems supporting the Connect-to-Interrupt directive require
22(10)
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
that has not been serviced by the Error Logger.
Error limiting
protects pool from being flooded by a sudden burst of device
errors.
(See the RSX-llM/M-PLUS Error Logging Manual.)

D.2

REAL-TIME FUNCTIONS

LPSll (Laboratory Peripheral Subsystem) and ARll
System)
Each LPSll/ARll synchronous function requires
secondary control block.

(Analog

Real-time

20.words

for

ICS/ICRll (Industrial Control Subsystem/Industrial Control Remote)
Each task linked to ICS/ICR interrupts requires 16.words of
dynamic memory, plus 6.words for each additional interrupt
linkage.
DRS/DSSll (Industrial Control System Modules)
Each task linked to DRS/DSS interrupts requires 9(10) words of
dynamic memory, plus 5(10) words for each additional interrupt
linkage.
IPll (Industrial Processor)
Each task linked to IPll interrupts requires 18(10) words of
dynamic memory, plus 8(10) words for each additional interrrupt
linkage.
Each Digital Sense Interrupt (OSI) module requires one byte of
dynamic memory per each module byte for a change-of-state
history table.

D-4

FUNCTIONS IMPACTING POOL (DYNAMIC MEMORY)
A to D mapping tables require 8(10) words for each A014
and 10(10) words for each A020 module.

module

LPAll (Laboratory Peripheral Accelerator)

For the duration of every transfer, 10(10) words of dynamic
memory are allocated for (Unibus mapping Register UMR) mapping
work space.
For a Request Data Array (RDA), see the LPA-11 documentation.
For the duration of every transfer
in
which
an
AST
(Asynchronous System Trap) is specified, 6(10) words of dynamic
memory are allocated for an AST block.

D-5

APPENDIX E
ADDRESS AND VECTOR ASSIGNMENTS

Specific algorithms exist for assigning UNIBUS addresses and interrupt
vector addresses to all devices attached to PDP-11 hardware.
UNIBUS
addresses and interrupt vector address assignments are either floating
or fixed.
If a device has a floating address assignment, the presence or absence
of any floating address device effects the assignment of addresses to
other floating address devices. Similarly, many devices have floating
vector addresses.
According to the algorithm, interrupt vectors must be assigned in a
specific sequence and the presence of one type of device effects the
correct assignment of interrupt vectors of other devices.
If a device
has a fixed address or vector, its location is unaffected by other
devices on the system.
This appendix presents the algorithms for assigning floating addresses
and vectors.
It also lists the fixed assignments for devices
supported by the Autoconfigure task.
DIGITAL recommends that the
hardware follow the configuration rules.

E.l

AUTOCONFIGURE DEVICE SUPPORT

The following table lists the devices supported by autoconfiguration.
This list is only a subset of the devices supported by RSX-llM.
The
complete list of devices supported by RSX-llM can be found in Appendix
C or in the RSX-llM Software Product Description.
As stated previously, many devices have floating CSR addresses.
A
complete description of the algorithm used to determine these CSR
addresses can be found in Section E.2.
Table E-1 also contains those devices that have floating vectors.
These devices can be identified by a ranking priority under the vector
label.
The floating vectors begin at address 300 and proceed
continuously upwards.
Gaps in the vector assignments are not required.
The
vector
assignment sequence is done based on ascending vector ranking.
That
is, the device with the lowest rank is assigned the next floating
vector address.
The autoconfiguration process dynamically computes
the vectors of all supported devices.
This is done by forcing each
present device to interrupt.

E-1

ADDRESS AND VECTOR ASSIGNMENTS

Table E-1
Autoconf iguration Device Support

Maximum
Number
Ctrl

Interrupt
Priority

260
300
220
160
210
254
214

1.
4.
1.
1.
1.
1.
1.

6
5
5
5
5
5
6

4
10
40
40
100
100
54
54

154
264
204
224
260
150
204
254

1.
1.
1.
1.
1.

5
5
5
5
5
5
5
5

20
4
10
10
10
10
10
10
10
10
4
4
20
10
10
10
10
10

224
224
200
170
174
270
274
774
770
764
070
074
Rank
Rank
Rank
060
Rank
Rank

CSR
Address

Reg.
Size

First
Vector

TAll
TU58
RKll
RLll/RL2ll
RK6 ll/RK7 ll
RPll
TCll
UDA50/RQDX1
RC25
RXll/RX2ll
RHll/RH70
RHll/RH70
RHll/RH70
RHll/RH70
RHll/RH70
RHll/RH70

177500
176500
177404
174400
177440
176714
177342

4
10
20
20
40
40
20

172150
177170
172040
172440
175400
176300
176400
176700

TMll
TSll
LP/LS/LVll
LP/LS/LVll
LP/LS/LVll
LP/LS/LVll
LP/LS/LVll
LP/LS/LVll
LP/LS/LVll
LP/LS/LVll
PRll
PCll
DHll
DLll-A/B/J
DLll-C/D/E
DLll-W
DMll-BB
DZll

172522
172522
177514
164004
164014
164024
164034
164044
164054
164064
177550
177554
FLOAT
176500
175610
177560
170500
FLOAT

Device

E.2

1.
1.

8.
1.
1.
1.

1.
1.
1.

16
2
14

1.
1.
1.
1.
16.
16.
31.

6
28

16.
16.

5
5
4
4
4
4
4
4
4
4
4
4
5
5
5
4
5
5

Remarks

On a DLll

All MSCP devices
RS03/RS04
TU16/45/77, TE16
TU78
RS/RP/RM/TU ALT.
MLll
RP04/05/06 or
RM02/03/05
LPA
LPB
LPC
LPD
LPE
LPF
LPG
LPH

Console

FLOATING ADDRESS ASSIGNMENT ALGORITHM

The following is the algorithm used to assign CSR addresses to all
devices that have floating addresses.
The autoconfiguration process
finds only the devices listed in Table E-1.
If the system contains
devices not listed, you must configure them manually.
The floating address space starts at 760010(8) and proceeds upward
764000 (8).
A gap in the address space (no SLAVE SYNC)
not exist.

implies that a device

to
does

The first address of a new type device will always be on a 2 N word
boundary, where N is the first integer greater than or equal to LOG M
and M i~ the number of device registers.

E-2

ADDRESS AND VECTOR ASSIGNMENTS
Number of Registers
in Device
1
2
3,4
5,6,7,8
9 thru 16

Possible Boundaries
Any Word
XXXXXO, XXXXX4
XXXXXO
XXXXOO, XXXX20, XXXX40, XXXX60
XXXXOO, XXXX40

A gap of at least one word will be left after each type of device,
starting on the same boundary the device would start on.
Note that
the gap must be at least one word but may be longer than one word.
Gap length is determined by the boundary on which the next must be
addressed contiguously.
Address 760010 is reserved for the first DJll.
Since the DJll has
four registers, additional DJlls are assigned addresses modulo 10
(base 8} immediately following the first DJll
(that is,
760010,
760020, and the like.) The modulo 10 (base 8) address following the
last DJll is left empty and is known as the DJll gap.
If there are no
DJlls, the gap is at 760010.
If there is one DJll, the gap will be at
760020. All gaps must be at least one word.
After all DJll addresses and the DJll gap are defined, the address for
the first DHll can be assigned.
DHlls have eight registers which
implies a modulo 20 ·(base 8} boundary.
The address of the first DHll
is the first modulo 20 address following the DJll gap.
If there are
no DJlls (DJll gap at 760010}, the first DHll is assigned address
760020. Similarly, if there is one DJll, the DJl gap begins at 760020
and the next available modulo 20 boundary is 760040.
All additional
DHlls are assigned addresses modulo 20 immediately after the first
DHll.
The DHll gap begins on the module 20 boundary following the
last DHll.
After all DHll addresses and the
DOPll,
LKll, DMCll, DZll, and
can be assigned in sequence.
address devices will be assigned

E.3

DHll gap are defined, DQll, DUll,
KMCll addresses and the required gaps
Addresses for any future floating
in a similar manner.

FLOATING ADDRESS WORKSHEET

The algorithm for assignment of floating addresses can be confusing
for a large configuration with multiple units of several types of
floating address devices. The floating address worksheet that follows
is a graphic aid that should eliminate some confusion and relieve
configuration problems.
The worksheet allows you to assign device
addresses quickly without referring to the formal rules.
Instructions
for use of the worksheet follow.
Two configuration examples
(Example
E-1 and Example E-2} and a blank worksheet (Example E-3} at the end of
this appendix are provided for general use.

E.3.1

Worksheet Format

The worksheet is divided into four sections covering the address range
760010 through 762000.
Although the floating address area continues
up to address 764000, the worksheet should cover most configurations.
If necessary, you can create a second worksheet by adding 2000 to all
addresses listed.

E-3

ADDRESS AND VECTOR ASSIGNMENTS

Worksheet Instructions

E.3.2

The following are the instructions for the use of the worksheet:
1.

Record the quantity of each type of floating
in the space provided on the worksheet.

address

device

Beginning at the upper left of the worksheet at address
760010 and proceeding down the DJll column, record the unit
numbers for all DJlls in the configuration.
Begin with unit
0 and end with unit n-1.
(There are n DJlls in the
configuration.)

Immediately below the last DJll unit, mark an X for
the
required DJll address gap.
Also mark an X in the box
immediately to the right (DHll column) •
In general, when numbering device units down the appropriate
column, use only the unshaded boxes.
The shaded boxes
represent illegal addresses for the particular device type.
Because the gap address must also be a legal device address,
use only an unshaded box for the gap X when numbering down a
column.
In marking an X in the column to the right of a device
address gap,
use shaded boxes because the X in the next
column merely provides a starting point for
numbering units
of the next device type.
If there are no units of a
particular device type, enter only the gap Xs on the
worksheet.
If you use all available space in one section of the
worksheet,
simply copy the entries on the last line of the
full section to the top line of the next section.
Then
continue numbering in the new section.

Continuing just below the X in the DHll column, number all
DHll units.
Once again, start with unit 0 and continue to
unit n-1.
Skip the shaded boxes
in numbering down the
column.
In the first unshaded box below the last DHll unit,
mark an X for the DHll gap.
Also mark an x in the box to the
right, whether it is shaded or unshaded.

Continue with the remaining floating address devices.
In
each case,
number units
from 0 to n-1 down the column
beginning in the first unshaded box below the X.
Mark an x
in the next unshaded box below the last unit and in the box
immediately to the right of the last unit (whether that box
is shaded or unshaded) •

After you have recorded all floating address devices, you can
read the UNIBUS address for each device unit directly from
the worksheet.

E-4

Example E-1 Floating Address Worksheet (Configuration 1)
(EXAMPLE 1)

FLOATING ADDRESS WORKSHEET
DEVICE
ADDRESS

0
U
p
1

L
K
1

D
M

K
M

ADDRESS

DEVICE

---,

--,
D
Z
1

DEVICE

~-rg ~ ~ ~

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

D D D D D L D D K
JHQUUKMZM
1
1
p
1

D
M

D
Z

c
1

1
760400

761000

760410

761010

760420

761020

1
1

-- - +---1--1--

1--+--

1--761420

f---

-1-

ill

1--+760440

\--

--1

760450
761060

760470

761070

760500

761100

- -

1--+- -1---1----l---

-+ 1---

761470

761110

f---

760520

760530

1---761530

760540

761540

760550

760600

l::tj

I
U'1

760620

761220

760630

761230

761620

761630

760640

760650

761250

760660

761260

760670

761270

1--1-

761650

\-~-

761670
761700

761300
761310

760710

l-+-

760720

\-761730

761330
760740

- 1--

1--761740
761750

760750
760760

~7~0.3~~

760770

760400

761000

761400

J
1
1

1
1

DH11
0011
DU11
DUP11
LK11

_..1._
_o_ _
_Q__
_Q__

I
0

u u

L
K

DMC11

DEV

QTY (n)

DEV

UNIT

ADDRESS

;J_

..EL

7~00{0

)>::T

¢)
J_

7600~

PZ.

.lli£.

7~001Q.

DZ11

KMC11

_I_

[)t'CC.

vz..

_,_

ADDRESS

7bOl(eO
?Co0t70

DEV

--- - -- -

~--

1
1

UNIT

_J)__

DDDDDL
Q
K

DD DD L DD
OUUKMZ

QTY (n)
DJ11

1---l--+-

~--

H
1

p
1

1
1

UNIT

t---+-+--

ADDRESS

1<DOJ./(J

7~o~;J..o

t>HC

lfoO£~Q

J:>.Z:

rt>

7'1Ql 2.Q
ZK-357-81

Example E-2 Floating Address Worksheet (Configuration 2)

-;;-i···;;- 0

HI a u

111

(EXAMPLE 2)

FLOATING ADDRESS WORKSHEET
DEVICE

71~

I ,

JHOUUKMZ
1
1

D
H
1
1

D
0
1
1

µ:
N:
~;

ltd
J:ll
f'DH

r;11

f!1

761260

1-- ----+---tzj

µL:l

151210
761300

761jjQ
761340
761350

761400

t--·-I)

a u u

L
K

OOOODLDOK

J
1

H
1

QTY (n)
DJ11

_o_

.3
DHl1
DQ11 ~
DUl1
DUP11
LK11

-'._o__
_o__

DMC1·1
DZ11
KMC11

QTY (n)
0

_..3
__
~

U
p

Z
1

--t--t-+0

c ,

1
1

ADDRESS
7foDOJ..O

DEV

UNIT

ADDRESS

'PZ.

_!12__

7fDOd2.IO

7foDO'l0
ZtoOObO
l(p0/10
7(po/:Z..o

~
~

l(o0.),.20
l&,OJ.30

7(pQ/40

UNIT

_!b__

-'_L_

-'-

DEV

UNIT

ADDRESS

ZK-358-81

Example E-3 Blank Floating Address Worksheet

FLOATING ADDRESS WORKSHEET

(EXAMPLE 3)
DEVICE

DEVICE

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

ADDRESS

D
M

D
Z

1
1

ADDRESS

K
K

D
J
1

1
1

----

DEVICE
,-----~,-~~~~~~

U
1

L
1

761000

760000

760410
760420

760020

1--

760030

760430

760040
760050

tt
- b

:_::;:::~

760450

7604 70

~~~lt

- ---+---

1--1---

761010
--

-+--+-+--

---

+-+

-"- t---

761030

761040

761450

761050

760060
760070

761470

-1

\::::~,:

761500

760100

760510
760120

1--

761510

760530

760130

------j-

I-

760520
~ ---

760540

760140

-1----1

tIt--

1---

1--

761520

I--761530

760550

760150

761540

PIT

761550

t
t--

t----

760560

:)~:·
l::rj

760200

760210

......i

760570

761170

761570

760600

761200

761600

760610
760620

1-----

760630

760230

760250

-~ill\

761620

I-

f----+ t -

\!i;

b:,.

761660

- -+--

760300

1--

f 760730

--h:c

t----

760350

1---------P
+100100

:::::::::

700740

'--·'---'---'---'--__.j

QTY (n)

DEV

+- -

762000

I-

U
p

1
1

Z
1
1

c
1

UNIT

1
1

DJ11
DH11
0011
DU11
DUP11 _ __

!-1--1---

:~::::;

DDDDDLDD

(:::

761760

761360

-- t-- ~ +~- -+-----1

,___16__
100
__0__,__--+----I--- I--+-+~
JHOUUKM
1
1 p
1

I----+-+--

t:::::

761350

!;8,:,.

t-750770 L~ bC'
t----' p

~rn

-f---i

--t-lt-I

761740

761340

. -- -+

760150 I~

760400

761710

t---

t-·

760330

760360

7611370

I-

rn=

760370

:~;:::;:

761640

761240
761250

760320

t----1
I

1--1---

760260

760270

~ff

ADDRESS

DEV

UNIT

ADDRESS

DEV

UNIT

ADDRESS

DMC11
DZ11
KMC11

LK11
ZK-359-81

APPENDIX F

DISTRIBUTION KIT CONTENTS

This appendix contains directory listings
of
four
types
of
distribution kits.
Files appear under the appropriate UFD for each
kit.
For those volumes consisting of more than one disk volume,
the
volume name precedes those files contained in each disk volume of the
kit.

F.l

DIRECTORY LISTING OF THE BIG DISK DISTRIBUTION KIT

The big disk distribution kit applies to the following disk volumes:
RP04/05/06,
RM02/03/05/80,
RP07, RA60/80/81, and RC25.
The big disk
distribution kit is the same for all these disks.

F.1.1

RSXM35
UFD [1,1]

KMCLP. BIN; 1
RSXMACID.MAC;l
RORMSl.MAC;l
EXEMC.MLB;l
RMSMAC.MLB;l
FCS.OBJ;l
FCSMBF.OBJ;l
FCSMTA.OBJ;l
LPA.OBJ;l
LPS.OBJ;l
ODT.OBJ;l
PURICR.OBJ;l
PURISA.OBJ;l
PURPCS.OBJ;l
PURUDC.OBJ;l
TRACE.OBJ;l
DAPRLX.ODL;l
DAPllX. ODL; 1
RMSRLX.ODL;l
RMSll. ODL; 1
RMSllS.ODL; 1
RMSllX. ODL; 1
RMS12S.ODL;l
RMS12X.ODL;l
EXELIB.OLB;l
RMSDAP.OLB;l
RMSLIB.OLB;l
SYSLIB.OLB;l
VMLIB. OLB; l

RSXMAC.SML;l

6.
38.
12.
66.
185.
24.
32.
30.
16.
5.

8.
6.
8.
14.
3.
3.
2.

6.
2.
85.
4.

6.
4.

6.
45.
95.
214.
230.
16.
253.

F-1

DISTRIBUTION KIT CONTENTS

BIG

DISK

RSXM35
UFD [ 1, l]

OAPRES.STB;l
RMSRES.STB;l
OAPRES.TSK;l
RMSRES.TSK;l
RMSRESSUB.TSK;l

40.
87.
48.

Total of 1604./1609.

blocks in 35.

files

UFO [ 1, 2]
RMS IN STAL. CMO; 1
STARTUP.CMO;l
RMSOES.HLP;l
QIOSYM.MSG;l
HELP.ULB;l
Total of 2610./2610.

14.
6.
308.
29.
2253.
blocks in 5.

files

UFO [ 1, 3]
Total of 0./0.

blocks in O.

files

UFO [ 1, 4]
Total of 0./0.

blocks in O.

files

UFO [ 1, 6]
ERRLOG.ULB;l
ERRLOGETC.ULB;l
Total of 692./692.

622.
70.
blocks in 2.

files

UFO [ 1, 7]
Total of 0./0.

blocks in 0.

files

F-2

DISTRIBUTIOM KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [1,20]
ACFBLD.BLD;l
ACNBLD.BLD;l
ACOBLD.BLD;l
ACSBLD.BLD;l
BADBLD.BLD;l
BOOBLD.BLD;l
BROBLD.BLD;l
BRUBLD.BLD;l
BYEBLD.BLD;l
CDABLD.BLD;l
CFLBLD.BLD;l
CMPBLD.BLD;l
COTBLD.BLD;l
CRFBLD.BLD;l
DCLBLD.BLD;l
DMOBLD.BLD;l
DMPBLD.BLD;l
DSCBLD.BLD;l
EDIBLD.BLD;l
EDTBLD.BLD;l
ELIBLD.BLD; 1
ERLBLD.BLD;l
FCPLRGBLD.BLD;l
FCPMDLBLD.BLD;l
FCPMINBLD. BLD; 1
FCPSMLBLD.BLD;l
FCSRSlBLD.BLD;l
FLXBLD.BLD;l
FMTBLD.BLD;l
FTBBLD.BLD;l
FllMSGBLD.BLD;l
HELBLD.BLD;l
ICPBLD.BLD;l
ICPCOMBLD.BLD;l
ICQBLD.BLD;l
INIBLD .BLD; 1
INSBLD. BLD; 1
IOXBLD.BLD;l
LBRBLD.BLD;l
LOABLD.BLD;l
LPIBLD.BLD; 1
LPPBLD.BLD;l
MACBLD.BLD;l
MCMBLD.BLD;l
MCRBLD.BLD;l
MOUBLD.BLD;l
MTABLD.BLD;l
PATBLD.BLD;l
PIPBLD.BLD;l
PMDBLD.BLD;l
PMTBLD.BLD;l
PRTBLD.BLD;l
QCLBLD.BLD;l
QMGBLD.BLD;l
QPRBLD.BLD;l
RCTBLD.BLD;l

5.
2.
2.
2.

5.
2.

3.
2.
20.
9.
6.
4.
13.
21.

3.
9.
7.
8.
5.
4.
5.
9.
17.
17.
11.
10.
18.
3.
5.
3.
8.
8.
21.
9.
7.
3.
22.
24.
4.
2.
11.
16.
9.
18.
4.
17.
8.
24.
10.
8.
9.
8.

9.
2.
2.

F-3

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFD [1,20]
RMDBLD.BLD;l
RPTBLD.BLD;l
SAVBLD.BLD;l
SHFBLD.BLD;l
SHUBLD.BLD;l
SLPBLD.BLD;l
STKBLD.BLD;l
TDXBLD.BLD;l
TKBBLD.BLD;l
TKNBLD.BLD;l
UFDBLD.BLD;l
UNLBLD.BLD;l
VFYBLD.BLD;l
VMRBLD.BLD;l
ZAPBLD.BLD;l
ICBLD.CMD;l
IPBLD.CMD;l
ISBLD .CMD; 1
UDCBLD.CMD;l
LP IN IT. OBJ; 1
SYSROT.OBJ;l
BAD.OLB;l
BOO.OLB;l
BRU.OLB;l
CDA.OLB;l
CMP.OLB;l
CRF.OLB;l
DCLO.OLB;l
DCLR.OLB;l
DMP.OLB;l
DSC.OLB;l
EDI.OLB;l
EDTLIB. OLB; 1
ERL.OLB;l
FCP.OLB;l
FIL.OLB;l
FLX.OLB;l
FMT.OLB;l
FTB.OLB;l
FllMSG. OLB; 1
ICPllM. OLB; 1
INI.OLB;l
INS .OLB; 1
IOX.OLB;l
LAIN IT. OLB; 1
LBR.OLB;i
LOA.OLB;l
MAC.OLB;l
MCR.OLB;l
MLTUSR.OLB;l
MTA.OLB;l
NEISLB. OLB; l
PAT~OLB;l

PIP.OLB;l
PIPUTL.OLB;l
PMD.OLB;l

15.
14.
14.
2.
2.
7.
28.
2.
31.
2.
2.
2.
9.
12.
4.
1.
1.
1.
1.
4.
1.
36.
11.
279.
144.
26.
40.
493.
54.
39.
164.
57.
184.
35.

87.
124"

142.
55.
105.
9.
120.
84.
35.
127.
21.
70.
43.
149.
193.
81.
102.
14.
34.
96.
25.
32.

F-4

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFD [ 1, 20]
PRT.OLB;l
RMD.OLB;l
RPT.OLB;l
SAV.OLB;l
SLP.OLB;l
TKB.OLB;l
VFY.OLB;l
VMR.OLB;l
ZAP.OLB;l

Total of 4990./5050.

19.
70.
222 ..
65.
34.
308.
53.
226.
33.
blocks in 121.

files

UFD [ 1, 24]
BCKNON.CMD;l
BCKNRN.CMD;l
CNVNON.CMD;l
CNVNOO.CMD;l
CNVNRN.CMD;l
CNVNRR.CMD;l
DAPRES.CMD;l
DEFNON.CMD;l
DEFNRN.CMD;l
DESNON.CMD;l
DESNRN.CMD;l
DSPNON.CMD;l
DSPNRN.CMD;l
ICBLD.CMD;l
IFLNON.CMD;l
IFLNRN.CMD;l
IPBLD.CMD;l
ISBLD.CMD;l
RMSRES.CMD;l
RSTNON.CMD;l
RSTNRN.CMD;l
UDCBLD.CMD;l
LP IN IT. OBJ; 1
SHUFL.OBJ;l
SYSROT.OBJ;l
TDX.OBJ;l
BCKNON.ODL;l
BCKNRN.ODL;l
CNVNON.ODL;l
CNVNOO.ODL;l
CNVNRN.ODL;l
CNVNRR.ODL;l
DAPRES.ODL;l
DEFNON.ODL;l
DEFNRN.ODL;l
DESNON.ODL;l
DESNRN.ODL;l
DSPNON.ODL;l
DSPNRN.ODL;l
IFLNON.ODL;l

1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.

4.
4.
1.

12.
8.

8.
10.
5.
5.
5.
1.

3.
3.
6.
6.

7.
7.
5.

F-5

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [l,24]

3.
9.
24.

IFLNRN.OOL;l
RMSOES.OOL;l
RMSOOL.OOL;l
RMSRES.OOL;l
RSTNON.OOL;l
RSTNRN.OOL;l
ACF.OLB;l
BOO.OLB;l
COT.OLB;l
ERL.OLB;l
FCP.OLB;l
FIL.OLB;l
ICPllM. OLB; 1
!NI .OLB; 1
INS.OLB;l
LAIN IT. OLB; 1
LOA.OLB;l
LPP.OLB;l
MCR.OLB;l
MLTUSR.OLB;l
MTA.OLB;l
PIPUTL.OLB;l
PMO.OLB;l
QMG.OLB;l
QMGCLI.OLB;l
RCT.OLB;l
RMO.OLB;l
RMSUTL.OLB;l
SAV.OLB;l
Total of 2397./2401.

11.
11.
11.
31.
11.
26.

35.
92.
124.
120.
84.
37.
21.
47.
57.
211.
81.
102.
25.
33.
74.
89.
17.
98.
722.
69.
blocks in 699

files

UFO [l,30]
Total of 0./0.

blocks in O.

files

UFO [1,34]
OAPRES.MAP;l

16.
59.
35.

RMSRES~MAP;l

RMSRESSUB.MAP;l
Total of 110./110.

blocks in 3.

files

UFD [1,50]
Total of 0./0.

blocks in O.

files

F-6

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFD [ 1, 51]
BRU64K.STB;l
BRU64K.SYS;l

Total of 272./272.

ACF.BSL;l
SGNPARM.CMD;l
DBDRV.STB;l
DDDRV.STB;l
DKDRV.STB;l
DLDRV.STB;l
DMDRV.STB;l
DPDRV.STB;l
DRDRV.STB;l
DUDRV.STB;l
DXDRV.STB;l
DYDRV.STB;l
LPDRV.STB;l
MMDRV.STB;l
MSDRV.STB;l
MTDRV.STB;l
RSXllM.STB;l
RSXllM.SYS;l
ACO.TSK;l
ACS.TSK;l
BAD.TSK;l
BOO.TSK;l
BRU.TSK;l
CDA.TSK;l
CMP.TSK;l
CRF.TSK;l
DBDRV.TSK;l
DDDRV.TSK;l
DKDRV.TSK;l
DLDRV.TSK;l
DMDRV.TSK;l
DMO.TSK;l
DMP.TSK;l
DPDRV.TSK;l
DRDRV.TSK;l
DUDRV.TSK;l
DXDRV.TSK;l
DYDRV.TSK;l
EDI.TSK;l
FCPSML.TSK;l
FLX.TSK;l
FMT.TSK;l
ICP.TSK;l
!NI. TSK; 1
INS. TSK; 1
IOX.TSK;l
LBR.TSK;l

14.
258.
blocks in 2.

files

26.
4.
1.
1.
1.
1.
1.
1.
1.

2.
1.
1.
1.
1.
1.
1.

12.
258.
39.
14.
53.
33.
176.
166.
50.
36.
5.
6.

4.
4.

5.
15.
61.
3.
5.
11.
4.
5.
61.
96.
132.
68.
141.
58.
60.
109.
72.

F-7

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [1,54]
LOA.TSK;l
LPORV.TSK;l
MAC.TSK;l
MCR.TSK;l
MMORV.TSK;l
MOU.TSK;l
MSORV.TSK;l
MTORV.TSK;l
PAT.TSK;l
PIP.TSK;l
RCT.TSK;l
RMSBCK.TSK;l
RMSCNVeTSK;l
RMSOEF.TSK;l
RMSOES.TSK;l
RMSOSP.TSK;l
RMSIFL.TSK;l
RMSRST.TSK;l
SAV.TSK;l
SLP.TSK;l
TKB.TSK;l
TKN.TSK;l
UFO.TSK;l
UNL.TSK;l
VFY.TSK;l
VMR.TSK;l
ZAP.TSK;l
Total of 4009./4009.

29.
4.
89.
113.
7.

46.
7.

6.
45.
73.
11.
157.
167e
139.
241.
142.
136.
177.
77.
48.
176.
18.
8.
23.
56.
156.
51.

blocks in 74.

files

UFO [ 1, 60]
Total of 0./0.

blocks in O.

files

UFO [l,64]
Total of 0./0.

blocks in O.

files

UFO [ 2, 300]
FILEl.;l
FILE2.;l
CMP.CMD;l
CONALL.CMO;l
CONCNT.CMO;l
DMP.CMO;l
DSC.CMO;l
FLX.CMO;l
INSTSK. CMO; 1

1.
1.
2.
7.
2.
1.
6.
3.
1.

F-8

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 {Cont.)
UFD [2,300]
INTERA.CMD;l
LBR.CMD;l
LOAD.CMD;l
MCRTST.CMD;l
PAT.CMD;l
PMD.CMD;l
SIOE.CMD;l
SLP.CMD;l
SLPCMD.CMD;l
STRTUP.CMD;l
UETP.CMD;l
UNLOAD.CMD;l
UTIL.CMD;l
CRTEST.MAC;l
DEFINE.MAC; 1
DUMMY.MAC;l
LOGGER.MAC;l
MACROl.MAC;l
MACR02.MAC;l
MACR03.MAC;l
NULl.MAC;l
NUL2.MAC;l
NUL3.MAC;l
OBJCTl.MAC;l
OBJCT2.MAC;l
OBJCT3.MAC;l
PATCHl.MAC;l
QTRUN.MAC;l
PATCHl.OBJ;l
DEVM.SAM;l
UETPCOR.TMP;l
ASRC.XXX;l
PATCHD.XXX;l
SLPDAT.XXX;l
SLPOUT.XXX;l
Total of 300./300.

4.
2.
10.
6.
2.
5.
9.
2.
,
.L.

10.
25.
2.
l.

1.
49.
1.
26.
1.
1.
1.
19.
19.
19.
1.
1.
1.
1.
28.
1.
3.
18.
1.
1.
1.
3.
blocks in 44.

files

UFD [ 11, 10]
ADDRV.MAC;l
AFDRV.MAC;l
ARDRV.MAC;l
BFCTL.MAC;l
CODRV.MAC;l
CORAL.MAC;l
CRASH.MAC;l
CRDRV.MAC;l
CTDRV.MAC;l
CVRTM.MAC;l
DBDRV.MAC;l
DDDRV.MAC;l
DFDRV.MAC;l
DKDRV.MAC;l

10.
17.
61.
18.
9.
28.
99.
36.
19.
5.
49.
71.
21.
23.

F-9

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [11,10]
DLDRV.MAC;l
DMDRV .MAC.;l
DPDRV.MAC;l
DRABO.MAC;l
DRASG.MAC;l
DRATP.MAC;l
DRATX.MAC;l
DRCIN .MAC; 1
DRCLI.MAC;l
DRCMT.MAC;l
DRDAR.MAC;l
DRDCP.MAC;l
DRDRV.MAC;l
DRDSP.MAC;l
DREIF.MAC;l
DREXP.MAC;l
DRGCL.MAC;l
DRGEF.MAC;l
DRGIN. MAC; 1
DRGLI.MAC;l
DRGPP.MAC;l
DRGSS.MAC;l
DRGTK.MAC;l
DRGTP.MAC;l
DRMAP.MAC;l
DRMKT.MAC;l
DRPUT.MAC;l
DRQIO .MAC; 1
DRRAS.MAC;l
DRREG.MAC;l
DRREQ.MAC;l
DRRES.MAC;l
DRSED.MAC;l
DRSMG.MAC;l
DRSPW.MAC;l
DRSST.MAC;l
DRSUB.MAC;l
DRSWS.MAC;l
DSDRV.MAC;l
DSSDI.MAC;l
DTDRV.MAC;l
DUDRV.MAC;l
DXDRV.MAC;l
DYDRV .. MAC;l
EMDRV.MAC;l
ERROR.MAC;l
ERSUB.MAC;l
EXDBT.MAC;l
EXESB.MAC;l
GRDRV.MAC;l
ICDRV.MAC;l
ICOM.MAC;l
IN I TL. MAC; l
IOSUB.MAC;l
IPCOM.MAC;l
IPDRV.MAC;l

51.
71.
26.
4.
10.
12.

9.
21.
33.
7.
6.
8.
62.
47.
43.
17.
36.
19.
1.
6.
11.
3.
7.
16.
58.
11.
22.
75.
15.
37.
5.
12.
26.
13.
85.
9.
36.
7.
22.
7.
23.
227.
36.
50.
20.
74.
40.
87.
29.
49.
179.
4.
33.
53.
2.
255.

F-10

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFD [ 11, 10]
IPMAP.MAC;l
ISCOM.MAC;l
ISDRV.MAC;l
LADRV.MAC;l
LKDRV.MAC;l
LOADR.MAC;l
LOWCR.MAC;l
LPDRV.MAC;l
LSDRV.MAC;l
MDSUB.MAC;l
MEMAP.MAC;l
MFDRV.MAC;l
MMDRV.MAC;l
MSDRV.MAC;l
MTDRV.MAC;l
NLDRV.MAC;l
NTDRV.MAC;l
PANIC.MAC;l
PARTY.MAC;l
PLSUB.MAC;l
PMT.MAC;l
POWER.MAC;l
PPDRV.MAC;l
PRDRV.MAC;l
QUEUE.MAC;l
REQSB.MAC;l
RSXMCO.MAC;l
SSTSR.MAC;l
-SYSCM.MAC;l
SYSDF.MAC;l
SYSXT.MAC;l
SYTAB.MAC;l
TDSCH.MAC;l
TTATT.MAC;l
TTCAN.MAC;l
TTCIS.MAC;l
TTDAT.MAC;l
TTDRV.MAC;l
TTFP.MAC;l
TTICH.MAC;l
TT IN I .MAC; 1
TTJZ.MAC;l
TTMAC.MAC;l
TTMIS.MAC;l
TTMOD.MAC;l
TTODN.MAC;l
TTOIS.MAC;l
TTRW.MAC;l
TTSUB.MAC;l
TTTBL.MAC;l
TTYH.MAC;l
TTYHV.MAC;l
TTYJ.MAC;l
TTYL.MAC;l
TTYZ.MAC;l
UDCOM.MAC;l

2.
2.
32.
90.
33.
54.
6.
24.

74.
43.
39.
124.
81.

97.
59.
4.
6.
16.
21.
16.
81.
24.
14.
12.
22.
105.
9.

31.
37.
10.
99.
11.
20.
73.
27.
19.
90.
262.
15.
122.
35.

7.
15.

7.
20.
18.
14.
83.
41.
20.
35.
28.
6.
16.

17.
7.

F-11

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [11,10]

54.
29.
28.
66.
25.

UDDRV.MAC;l
XBDRV.MAC;l
XLDRV.MAC;l
XMDRV.MAC;l
XPDRV.MAC;l
XQDRV.MAC;l
XUDRV.MAC;l
XWDRV.MAC;l

41.
27.
27.

Total of 5165./5165.

blocks in 134.

files

UFD [ 11, 20]

Total of 0./0.

blocks in O.

files

UFD [ 11, 24]

Total of 0./0.

blocks in O.

files

UFD [ 11, 30]

Total of 0./0.

blocks in O.

files

UFO [ 11, 34]

Total of 0./0.

blocks in O.

files

UFD [ 11, 40]

Total of 0./0.

oiocKs in 0.

files

F-12

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFD [ 12, 10]
INDSYS.CLB;l
ABOOV.MAC;l
ACS.MAC;!
ACTFIL.MAC;l
ALLOV.MAC;l
ALLSUB.MAC;l
ALTOV.MAC;l
ASNOV.MAC;l
ATLOV.MAC;l
BOOT.MAC;!
BOOTRC.MAC;l
BOTPH2.MAC;l
BRKOV.MAC;l
BYE.MAC;!
CBTO.MAC;l
CDT2B.MAC;l
CLIOV.MAC;l
CLQOV.MAC;l
COLOG.MAC;l
COT2B.MAC;l
CRETSK.MAC;l
DEAOV.MAC;l
DEVOV.MAC;l
DFSYM.MAC;l
DISMNT.MAC;l
DV20V.MAC;l
EDCKP.MAC;l
ERMSG.MAC;l
ERRMSG.MAC;l
ERROV.MAC;l
FILBN.MAC;l
FIXOV.MAC;l
FLAOV.MAC;l
FMTDV.MAC;l
FNDUCB.MAC;l
GETNUM.MAC;l
GNBLK.MAC;l
GTBYT.MAC;l
GTMNM.MAC;l
GTTSK.MAC;l
HELLO.MAC;!
ICBDEF.MAC;l
ICPASK.MAC;l
ICPASV.MAC;l
ICPASl.MAC; 1
ICPAS2.MAC;l
ICPAS3.MAC;l
ICPAS4.MAC;l
ICPAS5.MAC;l
ICPATS.MAC;l
ICPBLK.MAC;l
ICPCHA.MAC;l
ICPCHN.MAC;l
ICPENB.MAC;l
ICPERA.MAC;l
ICPERR.MAC;l

103.
24.
23.
6.
27.
21.
15.
34.
49.
29.
2.
19.
3.
45.

7.
6.
76.
19.
9.
4.
16.
10.
47.
19.
79.
52.
4.
15.
10.
13.
20.
30.
19.
4.
8.
4.
5.
6.
4.
8.
146.
5.
6.

14.
12.
10.
11.
9.
7.
11.
8.
5.
9.
16.
5.
18.

F-13

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFD [12,10]
ICPEXF.MAC;l
ICPEXI .MAC; 1
ICPFCL.MAC;l
ICPFDC.MAC;l
ICPFEX.MAC;l
ICPFIL.MAC;l
ICPFMI.MAC;l
ICPFMO.MAC;l
ICPFMS.MAC;l
ICPFMX.MAC;l
ICPFOP.MAC;l
ICPFUT.MAC;l
ICPFlO.MAC;l
ICPF52.MAC;l
ICPGNB.MAC;l
ICPGOT.MAC;l
ICPGTK.MAC;l
ICPGTN.MAC;l
ICPIFl.MAC;l
ICPIF2.MAC;l
ICPIF3.MAC;l
ICPIF4.MAC;1
ICPIMP.MAC;l
ICPINX .MAC; 1
ICPIN2. MAC; 1
ICPIN3.MAC;1
ICPIN4.MAC;l
ICPIN5.MAC;1
ICPMCR.MAC;l
ICPMEM.MAC;l
ICPMEN.MAC;l
ICPNEC.MAC;l
ICPNEI .MAC; 1
ICPNEN.MAC;l
ICPNET.MAC;l
ICPNEX.MAC;l
ICPNPR.MAC;l
ICPNPl .MAC; 1
ICPONR.MAC;l
ICPPAR.MAC;l
ICPPDW.MAC;l
ICPPOP.MAC;l
ICPPOl.MAC;l
ICPPRC.MAC;l
ICPPRE.MAC;l
ICPPRS.MAC;l
ICPROT.MAC;l
ICPSET.MAC;l
ICPSTP.MAC;l
ICPSUB.MAC;l
ICPSUT.MAC;l
ICPSUl~MAC;l

ICPSU2.MAC;l
ICPSU3.MAC;l
ICPSU4.MAC;l
ICPSU5.MAC;l

14.
7.

7.
11.

4.
2.
2.
2.
27.
4.

18.
22.

2.
1.
6.
14.
13.

4.
9.
6.
8.
8.
30.
6.
8.
15.
18.
6.
7.
5.
2.
1.
1.
2.
lL
3.
1.
5.
24.
15.
14.
11.
8.
13~

29.
6.
28.
6.
3.
28.
5.
20.

19.
18.
8.

F-14

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [12,10]
ICPSU6.MAC;l
ICPSYC.MAC;l
ICPSYT.MAC;l
ICPSYl.MAC;l
ICPSY2.MAC;l
ICPSY3.MAC;l
ICPTDV.MAC;l
ICPTES.MAC;l
ICPTPA.MAC;l
ICPVEC.MAC;l
ICPWFT.MAC;l
ICPXMD.MAC;l
INIALL.MAC;l
INIBAD.MAC;l
INIBIT.MAC;l
INIGCL.MAC;l
INIHOM.MAC; 1
INIMAG.MAC;l
ININDX.MAC; 1
INIPAR.MAC;l
INIROT .MAC; 1
INIUPD .MAC; 1
INSBF.MAC;l
INSCM.MAC;l
INSFL.MAC;l
INSFSR.MAC;l
INSGC.MAC;l
INSHD.MAC;l
INSLB.MAC;l
INSPS .MAC; 1
INSROT.MAC;l
IODAT.MAC;l
KEYWD.MAC;l
LDBUF.MAC;l
LDCTL.MAC;l
LDDRV.MAC;l
LDFIL.MAC;l
LDFIN.MAC;l
LDLDB.MAC;l
LDUIC.MAC;l
LKLST.MAC;l
LNlOV.MAC;l
LUNOV.MAC;l
MCRDEF.MAC;l
MCRDIS.MAC;l
MCROOT.MAC;l
MCROV.MAC;l
MDPOV.MAC;l
MGCML.MAC;l
MOUCLS.MAC;l
MOUDAT.MAC;l
MOUDIS.MAC;l
MOUDSK.MAC;l
MOUFOR.MAC;l
MOUMSG.MAC;l
MOUPAR.MAC;l

5.
14.
25.
26.
8.

12.
19.
11.
7.
2.
10.
4"

23.
55.
35.
69.
23.
42.
38.
119.
64.
41.

6.
10.
17.
2.
2.
30.
72.
26.
19.

7.
5.
6.
27.
26.
8.

33.
22.
3.
7.
9.
13.
5.
79.
10.
59.
10.
35.
20.
18.
32.
26.
30.
16.
43.

F-15

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [ 12, 10]
MOUPRE.MAC;l
MOUROT.MAC;l
MOUSUB.MAC;l
MOUTAP.MAC;l
MSGOUT.MAC;l
NETSUB.MAC;l
OPEOV.MAC;l
PAROV.MAC;l
PRlOV.MAC;l
RAPOV.MAC;l
REAOV.MAC;l
REDOV.MAC;l
REQCOT.MAC;l
RPSOV.MAC;l
RUNOV.MAC;l
SAVBOT.MAC;l
SAVCPU.MAC;l
SAVCl.MAC;l
SAVC2.MAC;l
SAVC3.MAC;l
SAVDB.MAC;l
SAVDF.MAC;l
SAVDK.MAC;l
SAVDL.MAC;l
SAVDM.MAC;l
SAVDP.MAC;l
SAVDR.MAC;l
SAVDRT.MAC;l
SAVDS.MAC;l
SAVDT.MAC;l
SAVDU.MAC;l
SAVDX.MAC;l
SAVDY.MAC;l
SAVE.MAC;l
SAVEM.MAC;l
SAVFN.MAC;l
SAVINS. MAC; 1
SAVSIZ.MAC;l
SAVST.MAC;l
SAVSUB.MAC;l
SAVTRC.MAC;l
SMLGCL.MAC;l
SPSOV.MAC;l
SRTOV.MAC;l
SSMOV.MAC;l
STSUB.MAC;l
STlOV.MAC;l
ST20V.MAC;l
ST30V.MAC;l
ST40V.MAC;l
SXlOV.MAC;l
SX20V.MAC;l
SX30V.MAC;l
SX40V.MAC;l
SYMTB.MAC;l
SYSOV.MAC;l

4.
9.

52.
38.
12.
2.
62.
24.
8.

14.
7.

12.
11.

28.
26.
17.
13.
20.
17.
6.
14.
12.
13.
18.
15.
14.
19.

4.
12.
13.
28.
19.
18.
62.
12.
16.

66.
26.
14.
35.
2.
15.
62.
27.
4.
16.
35.
41.
41.
29.
42.
52.
18.
40.
14.
23.

F-16

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFD [ 12I10]
SYSROT.MAC;l
TASOV.MAC;l
TIMOV .MAC; 1
TISUBS.MAC;l
TKTN.MAC;l
TPARS2.MAC;l
TPDEB .. MAC;l
TPMAC2.MAC;i
TPNUMB.MAC;l
UFD.MAC;l
UFDPAR.MAC;l
UFDPTB.MAC;l
UFDTP.MAC;l
UNLCTL.MAC;l
UNLFIL.MAC;l
WRTMS.MAC;l

10.
36.
26.
4.

49.
44.
5.
32.
8.
23.
16.
7.

6.
29.
6.
6.

Total of 4725./4731.

blocks in 240.

files

UFD [12,20]

FILASM.CMD;l
FILLIBBLD.CMD;l
ICPASM.CMD;l
ICPLIBBLD .CMD; 1
INIASM.CMD;l
INILIBBLD .CMD; 1
LOAASM.CMD;l
MCRASM.CMD;l
MCRL IBBLD. CMD; 1
Total of 41./41.

1.
12.
2.

2.
1.

2.
14.
3.

blocks in 9.

files

UFD [12,24]

FILASM.CMD;l
FILLIBBLD.CMD;l
ICPASM.CMD;l
ICPLIBBLD .CMD; 1
INIASM.CMD;l
INILIBBLD.CMD;l
LOAASM.CMD;l
MCRASM.CMD;l
MCRLIBBLD.CMD;l
Total of 41./41.

1.
12.
2.

2.
1.
2.
14.
3.

blocks in 9.

files

UFD [12,30]
Total of 0./0.

blocks in 0.

files

F-17

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFD [ 12, 34]
Total of 0./0.

blocks in 0.

files

UFD [12,40]
Total of 0./0.

blocks in 0.

files

UFD [14,10]
ATCMD.MAC;l
ATCOM.MAC;l
ATINIT.MAC;l
ATPAGE.MAC;l
GBCMD.MAC;l
GBCOM.MAC;l
GBINIT.MAC;l
GBLATM.MAC;l
GBLCHA.MAC;l
GBLGBM.MAC;l
GBLHLM.MAC;l
GBLIOM.MAC; 1
GBLMDM.MAC;l
GBLSSM.MAC;l
GBLTHM.MAC;l
GBPAGE.MAC;l
HLCOM.MAC;l
HLINIT.MAC;l
HLPAGE.MAC;l
IOCMD.MAC;l
IOCOM.MAC;l
IOINIT.MAC;l
IOPAGE.MAC;l
L36ATM.MAC;l
L36CHA.MAC;l
L36HLM.MAC;l
L36MDM.MAC;l
L36SSM.MAC;l
L36THM.MAC;l
MDCMD.MAC;l
MDCOM.MAC;l
MD IN IT .MAC; 1
MDPAGE.MAC;l
NULllS .MAC; 1
REMAP.MAC;l
RMDDEF.MAC;l
RMDEMO.MAC;l
RMDMAC.MAC;l
RMDRIV.MAC;l
RMDXCM.MAC;l
SSCMD.MAC;l

10.

4.
7.
29.
2.
2.
1.
3.
3.

1.
1.
3.

4.
5.
5.
1.
1.
5.
1.

6.
3.
11.
33.
4.

2.
2.

5.
5.
6.
6.
7.
25.
57.
1.
3.

6.
48.
7.
17.

5.
3.

F-18

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [ 14I10]

2.
6.
30.
8.

SSCOM.MAC;l
SSINIT.MAC;l
SSPAGE.MAC;l
TERM ID .MAC; 1
THCMO.MAC;l
THCOM.MAC;l
THFllL .MAC; l
THIN IT .MAC; 1
THPAGE.MAC;l
V05ATM.MAC;l
V05CHA.MAC;l
VOSHLM.MAC;l
VOS ICM.MAC; 1
VOSMOM.MAC;l
VlHATM.MAC;l
VlHCHA.MAC;l
VlHHLM.MAC;l
VlHIOM.MAC; 1
VlHMOM.MAC;l
VlHSSM.MAC;l
VlHTHM.MAC;l
V50ATM.MAC;l
V50CHA.MAC;l
VSOHLM.MAC;l
VSOIOM.MAC; 1
V50MOM.MAC;l
VSOTHM.MAC;l
V52ATM.MAC;l
V52CHA.MAC;l
V52HLM.MAC;l
V52 IOM. MAC; 1
V52MOM.MAC;l
V52SSM.MAC;l
V52THM.MAC;l
Total of 594./594.

6.
15.
13.
56.
4.
3.

5.
5.
4.

3.
2.
5.
5.
5.
6.

4.
2.

2.
5.
5.
6.

4.
2.
2.
5.
5.
5.
6.
blocks in 75.

files

UFO [ 14 I 20]
RMOASM.CMO;l
Total of 8./8.

blocks in 1.

file

UFO [14,24]
RMOASM.CMO;l
Total of 11./11.

11.

blocks in 1.

file

F-19

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 {Cont.)
UFO [14,30]

Total of 0./0.

blocks in 0.

files

UFO [14,34]

Total of 0./0.

blocks in O.

files

UFO [14,40]

Total of 0./0.

blocks in O.

files

UFO [ 15, 10]
ACNT.MAC;l
BROAO.MAC;l
HELLO.MAC;l
HELROT.MAC;l
HLP.MAC;l
HLPSUB.MAC;l
HSTTAB.MAC;l
SHUFL.MAC;l
SHUTUP.MAC;l

Total of 567./567.

162.
61.
129.
13.
8.
78.
23.
36.
57.

blocks in 9.

files

UFO [15,20]
MLTASM.CMO;l
MLTLIBBLO.CMO; 1
SHUTUPASM.CMO;l

Total of 3./3.

blocks in 3.

1.
1.
1.
files

UFO [15,24]
MLTASM.CMO;l
MLTL IBBLO. CMO; l
SHUFLASM.CMO;l
SHUTUPASM.CMO;l

Total of 4./4.

blocks in 4.

1.
1.
1.
1.

files

F-20

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [15,30]

Total of 0./0.

blocks in O.

files

UFO [15,34]

Total of 0./0.

blocks in O.

files

UFO [15,40]

Total of 0./0.

blocks in 0.

files

UFO [23,10]
ABORT.MAC;l
ALFN.MAC;l
ALFNUM.MAC;l
ALL.MAC;l
ALLOCATE.MAC;l
ANO.MAC;l
ANOA.MAC;l
APPENO.MAC;l
ASSIGN.MAC;l
ASTOV.MAC;l
AT.MAC;l
BACKUP.MAC;l
BASIC.MAC;l
BROAOCAST.MAC;l
CALLOV.MAC;l
CANCEL.MAC;l
CATCHALL.MAC;l
CBM.MAC;l
COBOL.MAC;l
COO.MAC;l
COMMAC.MAC;l
COMMANO.MAC;l
CONTINUE.MAC;l
CONVERT.MAC;l
COP.MAC;l
COPY.MAC;l
CORAL.MAC;l
CREATE.MAC;l
CSEP.MAC;l
CUIC.MAC;l
DATE.MAC;l
DBUG.MAC;l

4.
10.
13.

5.
3.
9.
4.
3.

6.
6.
2.
13.
3.
4.
7.
2.
5.
3.
21.
3.
1.
10.
2.

7.
3.
4.
15.
4.
2.
3.
4.
10.

F-21

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [23,10]
DCL.MAC;l
DCLDAT.MAC;l
DCLMAC.MAC;l
DCLMPL.MAC;l
DEALLO.MAC;l
DEASSIGN.MAC;l
DEBUG.MAC;l
DELETE.MAC;l
DEV.MAC;l
DIFFERENC.MAC;l
DIRECTORY.MAC;l
DISMOUNT.MAC;l
DISPATCH.MAC;l
DQBFE.MAC;l
DQBFS.MAC;l
DSPCMD.MAC;l
EDIT.MAC;l
EDOC.MAC;l
ELEMENT.MAC;l
EOL.MAC;l
ERR.MAC;l
ERRORO.MAC;l
ERRORR.MAC;l
ERRl.MAC;l
FIL.MAC;l
FIX.MAC;l
FLAGS.MAC;l
FNAM.MAC;l
FORMAT.MAC;l
FORTRAN.MAC;l
FSEP.MAC;l
GTARG.MAC;l
HELP.MAC;l
HOLD.MAC;l
IFIL.MAC;l
INITIAL .MAC; 1
INSTALL.MAC;l
JSR.MAC;l
LAB.MAC;l
LDCCD.MAC;l
LIBRARY .MAC; 1
LINK .MAC; 1
LINKl.MAC; 1
LIT.MAC;l
LOAD.MAC;l
LOGIN .MAC; 1
LOGOUT.MAC;l
LOVR.MAC;l
LUIC.MAC;l
MACRO.MAC;l
MAP.MAC;l
MATCH.MAC;l
MCR.MAC;l
MOUNT.MAC;l
NEW.MAC;l
NFIL.MAC;l

2.
22.
56.
1.

3.
4.
2.
7.
2.
5.
5.
4.
3.
10.
4.
28.
12.
2.
22.
3.
11.
5.
2.
3.
3.
3.
4.
6.
9.
17.
2.
5.
4.
3.
2.
16.
6.
3.
2.
5.
12.
16.
6.
17.
5.
2.
2.
12.
3.

18.
24.
7.
2.
14.
4.
3.

F-22

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [23,10]
NFT.MAC;l
NLIT.MAC;l
NOD.MAC;l
ODEV.MAC;l
OR.MAC;l
OUIC.MAC;l
PARSER.MAC;l
PASCAL.MAC;l
PIP.MAC;l
PREPARSE.MAC;l
PRI.MAC;l
PRINT .. MAC; 1
PRO.MAC;l
PROC.MAC;l
PURGE.MAC;l
QIOBF .MAC; 1
QUA.MAC;l
RELEASE.MAC;l
REMOVE.MAC;l
RENAME.MAC;l
REQUEST.MAC;l
RUN.MAC;l
SCTBIT.MAC;l
SEP.MAC;l
SET.MAC;l
SETl.MAC; 1
SHOW.MAC;l
SORT.MAC;l
SPAWN.MAC;l
START.MAC;l
STOP.MAC;l
SUBMIT.MAC;l
SY.MAC;l
T.MAC;l
TERM.MAC;l
TI.MAC;l
TIME.MAC;l
TLINK.MAC;l
TRANSL.MAC;l
TSET.MAC;l
TSHOW.MAC;l
TST.MAC;l
TYPE.MAC;l
UIC.MAC;l
UND.MAC;l
UNFIX.MAC;l
UNLOCK.MAC;l
VER.MAC;l
WFIL.MAC;l
WUIC.MAC;l
WVER.MAC;l
WXTN.MAC;l
XCOPY.MAC;l
XDCL.MAC;l
XTN.MAC;l
Total of 1002./1002.

3.
3.
2.
2.
6.
2.
7.
...,
I

•

7.
14.
2.
lL
9.
2.
3.
8.
7.
3.
2.
3.
2.

7.
7.
2.
15.
21.
21.

10.
5.
9.
8.
9.
3.
2.
2.
3.
2.
10.
5.
20.
16.
5.
3.
2.
5.
3.
3.
2.
2.
2.
2.
2.
6.
35.
2.
blocks in 143.

F-23

files

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [23,24]
DCL.CMD;l
OCLASM.CMO;l
Total of 26./26.

4.
22.

blocks in 2.

files

UFO [23,34]
Total of 0./0.

blocks in 0.

files

UFO [23,40]
Total of 0./0.

blocks in 0.

files

UFO [24,10]
TOX.MAC;l

108.

Total of 108./108.

blocks in 1.

file

UFO [ 24, 20]
TOXASM.CMD;l
Total of 1./1.

blocks in 1.

file

UFO [45,10]
KRATE.B2S;l
KRATE.FTN;l
KAAOMP.MAC;l
KAADRV .. MAC;l
KAAS03 .. MAC;l
KADAGR.MAC;l
KADDRV.MAC;l
KADGCH.MAC;l
KADINP.MAC; 1
KADINO .MAC; 1
KADINl.MAC;l
KADIN2.MAC;l

7.
7.
12.
24.
5.

6.
14.
20.
13.

6.
8.
6.
n

KAD IN 3 • MAC ; l

KAOIN4.MAC;l

F-24

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 {Cont.)
UFO [45,10]

KAOIN5.MAC;1
KAOSWP.MAC;l
KAST.MAC;l
KBFRMG.MAC;l
KBFSTS.MAC;l
KCLOKA.MAC;l
KCLOKB.MAC;l
KCOMM.MAC;l
KCVAOF.MAC;l
KOIGO.MAC;l
KOIO.MAC; 1
KDISWP.MAC;l
KOOSWP.MAC;l
KORORV.MAC;l
KOSCAO.MAC;l
KOSOGO.MAC;l
KOVOF.MAC;l
KEFQA.MAC;l
KFLT16.MAC;l
KGHIST.MAC;l
KIESTO.MAC; 1
KKWORV.MAC;l
KLQSUB.MAC;l
KMUL.MAC;l
KPAA.MAC;l
KPRE.MAC;l
KRCLKB.MAC;l
KRLOC.MAC;l
KRWBF.MAC;l
KSET.MAC;l
KSTAOC.MAC;l
KSTB.MAC;l
KSTIBF .MAC; 1
KSTOP.MAC;l
KSUB.MAC;l
KSWOF.MAC;l
LABMAC.MAC;l
Total of 473./473.

7.
14.
13.
11.

5.
10.

5.
6.
10.
12.
7.
7.
30.
4.
4.
11.
10.
6.
21.
4.

18.
7.

3.
7.
4.
5.
4.
12.
13.

7.
7.
5.
5.
10.
13.
6.
blocks in 51.

files

UFO [ 45 I 20]
ASMK.CMO;l
KCLEAN.CMO;l
KCOMBLO.CMO;l
KLABMLB.CMO;l
KL IBBLO. CMO; 1
KLIBRP.CMO; 1
K4ASM.CMO;l
Total of 7./7.

blocks in 7.

1.
1.
1.
1.
1.
1.
1.
files

F-25

DISTRIBUTIOR KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [45,24]
ASMK.CMO;l
KCLEAN.CMO;l
KCOMBLO.CMO;l
KLABMLB.CMO;l
KLIBBLO.CMO; 1
KLIBRP.CMO;l
K4ASM.CMO;l
Total of 7./7.

blocks in 7.

1.
1.
1.
1.
1.
1.
1.

files

UFO [45,30]
Total of 0./0.

blocks in O.

files

UFO [45,34]
Total of 0./0.

blocks in O.

files

UFO [104,10]
OEVSMl.CNF; 1
OEVUOA.CNF;l
OISPATCH.CNF;l
DSPlMl.CNF;l
OSP2Ml.CNF;l
DSP3Ml.CNF;l
DSP4Ml.CNF;l
DSP5Ml.CNF;l
DSP6Ml.CNF;l
DSP7Ml.CNF; 1
EMLll.CNF; 1
ERK05.CNF;l
ERK67.CNF;l
ERL12.CNF;l
ERM05.CNF;l
ERM23.CNF;l
ERM80.CNF;l
ERP07.CNF;l
ERP23.CNF;l
ERP456.CNF;l
ERRORM.CNF;l
ERSll .CNF; 1
ERS34.CNF;l
ERXOl.CNF; 1
ERX02.CNF;l

28.
15.
46.
40.
17.
17.
15.
19.
7.
27.
37.
29.
64.
40.
49.
49.
48.
46.
31.
51.
20.
24.
36.
21.
28.

F-26

DISTRIBOTIOR KIT CONTENTS

BIG DISK RSXM35 (Cont.)
UFO [104,10]
16.
19.
57.
26.
38.
26.
38 ..
15.
30.
38.
38.
36.
40.

ETAll.CNF;l
ETCll.CNF; 1
ETSll.CNF;l
ETU58.CNF;l
ETU77.CNF;l
ET0310.CNF;l
ET1645 .. CNF;l
EUNKWN.CNF;l
EllXX.CNF;l
Ell34.CNF; 1
Ell44.CNF;l
Ell60.CNF;1
Ell7X.CNF;l
FINLMl .CNF; 1
FMlNMl.CNF;l
FMlWMl.CNF;l
FM2CM1.CNF;l
FM3CM1.CNF;l
FM4NM1.CNF;l
FM4WM1.CNF;l
INITMl.CNF;l
MSCPAT.CNF;l
MSCPBO.CNF;l
MSCPEN.CNF;l
MSCPTO.CNF;l
NMLll.CNF; 1
NRK67.CNF;l
NRM05 .. CNF; l
NRM23.CNF;l
PARSEM.CNF;l
PARSlM.CNF;l
PARS2M.CNF;l
PARS3M.CNF;l
PRS2AM.CNF;l
PRS2BM.CNF;l
SELTMl.CNF;l

4.
7.
7.
5.
7.
27.
28.

9.
25 ..
82.
81.
45.

6.
4.
5 ..
5.
38.
29.
7.
13.
33.
32.
12.

Total of 1732./1732.

blocks in 61.

files

UFO (104,20]
26.
3.

ERRLOGASM.CMO;l
ERRLOGLIB .CMO; 1
Total of 29./29.

blocks in 2.

files

UFO [104,30]
Total of 0./0.

blocks in 0.

files

F-27

DISTRIBUTION KIT CONTENTS

BIG DISK RSXM35 (Cont.)

UFO (104,40]
blocks in O.

Total of 0./0.

files

UFO (200,1]
ERASE.MAC;l
GSA.MAC;l
PARSE.MAC;l
RENAME.MAC;l
SEARCH.MAC;l
ERASE.TSK;l
PARSE.TSK;l
RENAME.TSK;l
SEARCH.TSK;l

18.
9.
10.
8.

25.
22.
26.
25.

Total of 151./151.

blocks in 9.

files

UFO (200,200]
14.
19.
175.
45.
29.
70.
183.

BLOLAINIT .CMO i 1
SGNBLOORV.CMD;l
SGNEXEC.CMD;l
SGNICIS.CMD;l
SGNIP.CMO;l
SGNKLAB.CMO;l
SGNPER.CMO;l
SGNSTANO.CMO;l
SGNTT.CMD;l
SYSGEN.CMO;l
SYSGEN2.CMO;l
SYSGEN3.CMD;l
FCSRES.MAC;l
Total of 802./802.
Grand total
directories

4.
42.
77.
78.
55.
11.
blocks in 13.

33014./33089.

files
blocks

F-28

1144.

files

57.

DISTRIBUTION KIT CONTENTS

RK06/07 RSXM35
F.2

DIRECTORY LISTING OF THE RK06/07 DISTRIBUTION KIT

All the files included in the RK06/07 distribution kit are
follows:

F.2.1

RSXM35
UFD [1,1]

KMCLP.BIN;l
EXEMC.MLB;l
FCS.OBJ;l
FCSMBF.OBJ;l
FCSMTA.OBJ;l
LPA.OBJ;l
LPS.OBJ;l
ODT.OBJ;l
PURICR.OBJ;l
PURISA.OBJ;l
PURPCS.OBJ;l
PURUDC.OBJ;l
TRACE.OBJ;l
EXELIB. OLB; 1
SYSLIB.OLB;l
VMLIB. OLB; 1
RSXMAC.SML;l

6.
66.
24.
32.
30.
16.
5.
8.
6.

8.
14.
3.
3.
45.
230.
16.
253.

Total of 765./765.

blocks in 17.

files

UFO (1,2]
RMSINSTAL.CMD;l
STARTUP.CMD;l
QIOSYM.MSG; 1
Total of 49./49.

blocks in 3.

14.
6.
29.
files

UFO [ 1, 3]
Total of 0./0.

blocks in O.

files

UFO [1,4]
Total of 0./0.

blocks in O.

files

UFO (1,6]
Total of 0./0.

blocks in O.

files

F-29

listed

DISTRIBUTION KIT CONTENTS

RK06/07 RSXM35 (Cont.)

UFO [1,7]

Total of 0./0.

blocks in 0.

files

UFO [1,20]
ACFBLD.BLD;l
ACNBLD.BLD;l
ACOBLD.BLD;l
ACSBLD.BLD;l
BADBLD.BLD;l
BOOBLD.BLD;l
BROBLD.BLD;l
BRUBLD.BLD;l
BYEBLD.BLD;l
CDABLD.BLD;l
CFLBLD.BLD;l
CMPBLD.BLD;l
COTBLD.BLD;l
CRFBLD.BLD;l
DCLBLD.BLD;l
DMOBLD.BLD;l
DMPBLD.BLD;l
DSCBLD.BLD;l
EDIBLD.BLD;l
EDTBLD.BLD;l
ELIBLD.BLD;l
ERLBLD.BLD;l
FCPLRGBLD.BLD;l
FCPMDLBLD.BLD;l
FCPMINBLD.BLD;l
FCPSMLBLD.BLD;l
FCSRS lBLD. BLD; 1
FLXBLD.BLD;l
FMTBLD.BLD;l
FTBBLD.BLD;l
FllMSGBLD.BLD;l
HELBLD.BLD;l
ICPBLD.BLD;l
ICPCOMBLD.BLD;l
!CQBLD.BLD;l
INIBLD .. BLD; l

2.
5.
2.
2.
2.
5.
2.
3.
2.
20.

9.
6.
4.
13.
21.
3.

9.
7.
8.
5.
4.
5.
9.
17.
17.
11.
10.
18.
3.
5.
3.
8.
8.
21.

.,
I

•

INSBLD.BLD;l
IOXBLD .. BLD;l
LBRBLD.BLD;l
LOABLD.BLD;l
LPIBLD .BLD; 1
LPPBLD.BLD;l
MACBLD.BLD;l
MCMBLD.BLD;l
MCRBLD.BLD;l
MOUBLD.BLD;l
MTABLD.BLD;l
PATBLD.BLD;l

3.
22.
24.
4.
2.
11.
16.
9.
18.
4.
17.
8.

OTORT.n

24"

RT.n•1
..... -- .--,,.,_

F-30

DISTRIBOTIOR KIT CONTENTS

RK06/07 RSXM35 (Cont.)
UFO [1,20]
PMDBLD.BLD;l
PMTBLD.BLD;l
PRTBLD.BLD;l
QCLBLD.BLD;l
QMGBLD.BLD;l
QPRBLD.BLD;l
RCTBLO.BLD;l
RMDBLD.BLD;l
RPTBLD.BLD;l
SAVBLD.BLD;l
SHFBLD.BLD;l
SHUBLD.BLD;l
SLPBLD.BLD;l
STKBLD.BLD;l
TDXBLD.BLD;l
TKBBLD.BLD;l
TKNBLD.BLD;l
UFDBLD.BLD;l
UNLBLD.BLD;l
VFYBLD.BLD;l
VMRBLD.BLD;l
ZAPBLD.BLD;l
ICBLD.CMD;l
IPBLD.CMD;l
ISBLD.CMD;l
UDCBLD.CMD;l
LPINIT.OBJ;l
SYSROT.OBJ;l
BAD.OLB;l
BOO.OLB;l
BRU.OLB;l
CDA.OLB;l
CMP.OLB;l
CRF.OLB;l
DCLO.OLB;l
DCLR.OLB;l
DMP.OLB;l
DSC.OLB;l
EDI.OLB; 1
EDTLIB. OLB; 1
ERL.OLB;l
FCP.OLB;l
FIL.OLB;l
FLX.OLB;l
FMT.OLB;l
FTB.OLB;l
FllMSG.OLB;l
ICPllM. OLB; 1
INI .OLB; 1
INS.OLB;l
IOX.OLB;l
LAIN IT. OLB; 1
LBR.OLB;l
LOA.OLB;l
MAC.OLB;l
MCR.OLB;l

10.
8.
9.
8.
9.
2.
2.
15.
14.
14.
2.
2.
7.
28.
2.
31.
2.
2.
2.
9.
12.
4.
1.
1.
1.
1.

4.
1.

36.
11.

279.
144.
26.
40.
493.
54.
39.
164.
57.
184.
35.
87.
124.
142.
55.
105.
9.

120.
84.
35.
127.
21.
70.
43.
149.
193.

F-31

DISTRIBUTION KIT CONTENTS

RK06/07 RSXM35 (Cont.)
UFD [1,20]
MLTUSR.OLB;l
MTA.OLB;l
NEISLB.OLB;l
PAT.OLB;l
PIP.OLB;l
PIPUTL.OLB;l
PMD.OLB;l
PRT.OLB;l
RMD.OLB;l
RPT.OLB;l
SAV.OLB;l
SLP.OLB;l
TKB.OLB;l
VFY.OLB;l
VMR.OLB;l
ZAP.OLB;l
Total of 4990./5050.

81.
102.
14.
34.
96.
25.
32.
19.
70.
222.
65.
34.
308.
53.
226.
33.

blocks in 121.

files

UFD [1,24]
ICBLD.CMD;l
IPBLD.CMD;l
ISBLD.CMD;l
UDCBLD.CMD;l
LP IN IT. OBJ; 1
SHUFL.OBJ;l
SYSROT.OBJ;l
TDX.OBJ;l
ACF.OLB;l
BOO.OLB;l
COT.OLB;l
ERL.OLB;l
FCP.OLB;l
FIL.OLB;l
ICPllM. OLB; 1
INI .OLB; 1
INS. OLB; 1
LAINIT.OLB;l
LOA.OLB;l
LPP.OLB;l
MCR.OLB;l
MLTUSR.OLB;l
MTA.OLB;l
PIPUTL.OLB;l
PMD.OLB;l
QMG.OLB;l
QMGCLI.OLB;l
RCT.OLB;l
RMD .. OLB;l
SAV.OLB;l
Total of 1509./1513.

1.
1.
1.
1.

4.
4.
1.
12.
31.
11.
26.
35.
92.
124.
120.
84.
37.
21.
47.
57.
211.
81.
102.
25.
33.
74.
89.
17.
98 ..

69.
blocks in 30.

F-32

files

DISTRIBUTION KIT CONTENTS

RK06/07 RSXM35 (Cont.)

UFO [1,30]

Total of 0./0.

blocks in 0.

files

UFO [1,34]

Total of 0./0.

blocks in O.

files

UFO [1,50]

Total of 0./0.

blocks in O.

files

UFO [1,54]
ACF.BSL;l
SGNPARM.CMO;l
DBDRV.STB;l
OOORV.STB;l
DKDRV.STB;l
DLDRV.STB;l
DMDRV.STB;l
OPDRV.STB;l
DRDRV.STB;l
DUDRV.STB;l
DXDRV.STB;l
DYDRV.STB;l
LPDRV.STB;l
MMDRV.STB;l
MSORV.STB;l
MTORV.STB;l
RSX11M. STB; 1
RSX11M. SYS; 1
ACO.TSK;l
ACS.TSK;l
BAO.TSK;l
BOO.TSK;l
BRU.TSK;l
COA.TSK;l
CMP.TSK;l
CRF.TSK;l
DBORV.TSK;l
DOORV.TSK;l
DKDRV.TSK;l
DLDRV.TSK;l
OMORV.TSK;l
OMO.TSK;l
DMP.TSK;l
DPORV.TSK;l
ORORV.TSK;l

26.
4.
1.
1.
1.
1.
1.
1.
1.
2.
1.
1.
1.
1.
1.
1.
12.
258.
39.
14.
53.
33.
176.
166.
50.
36.
5.
6.
4.
4.
5.
15.
61.
3.
5.

F-33

DISTRIBUTION KIT CONTENTS

RK06/07 RSXM35 (Cont.)
UFO [1,54]
OUORV.TSK;l
OXORV.TSK;l
OYORV.TSK;l
EOI.TSK;l
FCPSML.TSK;l
FLX.TSK;l
FMT.TSK;l
ICP.TSK;l
INI.TSK; 1
INS.TSK;l
IOX.TSK;l
LBR.TSK;l
LOA.TSK;l
LPORV.TSK;l
MAC.TSK;l
MCR.TSK;l
MMORV.TSK;l
MOU.TSK;l
MSORV.TSK;l
MTORV.TSK;l
PAT.TSK;l
PIP.TSK;l
RCT.TSK;l
SAV.TSK;l
SLP.TSK;l
TKB.TSK;l
TKN.TSK;l
UFO.TSK;l
UNL.TSK;l
VFY.TSK;l
VMR.TSK;l
ZAP.TSK;l
Total of 2850./2850.

11.

4.
5.
61.
96.
132.

68.
141.
58.
60.
109.
72.
29.
4.

89.
113.

7.
46.

7.
6.
45.
73.
11.
77.

48.
176.
18.

8.
23.
56.
156.
51.
blocks in 67.

files

UFO [1,60]
Total of 0./0.

blocks in 0.

files

UFD [l,64]
Total of 0./0.

blocks in O.

files

F-34

DISTRIBUTION KIT CONTENTS

RK06/07 RSXM35 (Cont.)
UFO [11,10]
ADDRV.MAC;l
AFDRV.MAC;l
ARDRV.MAC;l
BFCTL.MAC;l
CODRV.MAC;l
CORAL.MAC;l
CRASH.MAC;l
CRDRV.MAC;l
CTDRV.MAC;l
CVRTM.MAC;l
DBDRV.MAC;l
DDDRV.MAC;l
DFDRV.MAC;l
DKDRV.MAC;l
DLDRV.MAC;l
DMDRV.MAC;l
DPDRV.MAC;l
DRABO.MAC;l
DRASG.MAC;l
DRATP.MAC;l
DRATX.MAC;l
DRCIN .MAC; 1
DRCLI .MAC; 1
DRCMT.MAC;l
DRDAR.MAC;l
DRDCP.MAC;l
DRDRV.MAC;l
DRDSP.MAC;l
DREIF .. MAC;l
DREXP.MAC;l
DRGCL.MAC;l
DRGEF.MAC;l
DRGIN .MAC; 1
DRGLI.MAC;l
DRGPP.MAC;l
DRGSS.MAC;l
DRGTK.MAC;l
DRGTP.MAC;l
DRMAP.MAC;l
DRMKT.MAC;l
DRPUT.MAC;l
DRQIO.MAC;l
DRRAS.MAC;l
DRREG.MAC;l
DRREQ.MAC;l
DRRES.MAC;l
DRSED.MAC;l
DRSMG.MAC;l
DRSPW.MAC;l
DRSST.MAC;l
DRSUB.MAC;l
DRSWS.MAC;l
DSDRV.MAC;l
DSSDI.MAC;l
DTDRV.MAC;l

10.
17.
61.

18.
9.
28.
99.
36.

,..L :::7 •
('\

5.
49.
71.
21.
23.
51.
71.

26.
4.
10.
12.
9.
21.

33.

7.
6.
8.
62.
47.
43.
17.
36.
19.
1.
6.
11.
3.
7.
16.
58.
11.
22.
75.
15.
37.

5.
12.
26.
13.

85.
9.
36.
7.
22.

7.
23.

F-35

DISTRIBUTION KIT CONTENTS

RK06/07 RSXM35 (Cont.)
UFD [ 11, 10]
DUDRV.MAC;l
DXDRV.MAC;l
DYDRV.MAC;l
EMDRV .. MAC;l
ERROR.MAC;!
ERSUB.MAC;l
EXDBT.MAC;l
EXESB.MAC;l
GRDRV.~AC;l

ICDRV.MAC;l
ICOM.MAC;l
INITL~MAC;l

IOSUB.MAC;l
IPCOM.MAC;l
IPDRV.MAC;l
IPMAP.MAC;l
ISCOM. MAC; 1
ISDRV.MAC;l
LADRV.MAC;l
LKDRV.MAC;l
LOADR.MAC;l
LOWCR.MAC;l
LPDRV.MAC;l
LSDRV.MAC;l
MDSUB.MAC;l
MEMAP.MAC;l
MFDRV.MAC;l
MMDRV.MAC;l
MSDRV.MAC;l
MTDRV.MAC;l
NLDRV.MAC;l
NTDRV.MAC;l
PANIC.MAC;!
PARTY.MAC;!
PLSUB.MAC;l
PMTeMAC;l
POWER.MAC;!
PPDRV.MAC;l
PRDRV.MAC;l
QUEUE.MAC;l
REQSB.MAC;l
RSXMCO.MAC;l
SSTSR.MAC;l
SYSCM.MAC;l
SYSDF.MAC;l
SYSXT.MAC;l
SYTAB.MAC;l
TDSCH.MAC;l
TTATT.MAC;l
TTCAN.MAC;l
TTCIS .MAC; 1
TTDAT.MAC;l
TTDRV.MAC;l
TTFP.MAC;l
TTICH.MAC;l

227.
36.
50.
20.
74.
40.
87.
29.
49.
179.
4.
33.
53.

2.
255.
2.
2.
32.

90.
33.
54.
6.
24.
74.
43.
39.
124.
81.

97.
59.
4.
6.
16.
21.
16.
81.
24.
14.
12.
22.
105.
9.
31.

37.
10.
99.
11.
20.

73.
27.
19.
90.
262.
15.
122.

F-36

DISTRIBUTION KIT CONTENTS

RK06/07 RSXM35 (Cont.)
UFO [ 11, 10]

35.
7.
15.
7.
20.

TTINI .MAC; 1
TTJZ.MAC;l
TTMAC.MAC;l
TTMIS .MAC; 1
TTMOO.MAC;l
TTOON.MAC;l
TTOIS.MAC; 1
TTRW .. MAC;l
TTSUB.MAC;l
TTTBL.MAC;l
TTYH.MAC;l
TTYHV.MAC;l
TTYJ.MAC;l
TTYL.MAC;l
TTYZ.MAC;l
UOCOM.MAC;l
UOORV.MAC;l
XBORV.MAC;l
XLORV.MAC;l
XMORV.MAC;l
XPORV.MAC;l
XQORV.MAC;l
XUORV.MAC;l
XWORV.MAC;l

18.

14.
83.
41.
20.

35.
28.
6.
16.
17.

7.
54.
29.
28.
66.
25.
41.
27.
27.

Total of 5165./5165.

blocks in 134.

files

UFO [11,20]

Total of 0./0.

blocks in 0.

files

UFO [ 11, 24]

Total of 0./0.

blocks in 0.

files

UFO [11,30]

Total of 0./0.

blocks in 0.

files

UFO [11,34]

Total of 0./0.

blocks in 0.

files

F-37

DISTRIBUTION KIT CONTENTS

RK06/07 RSXM35 (Cont.)
UFO [ 11, 40]
blocks in O.

Total of 0./0.

files

UFO [12,10]
52.

OV20V.MAC;l
SPSOV.MAC;l
STSUB.MAC;l
SXlOV.MAC;l
SX20V.MAC;l
SX30V.MAC;l
SX40V.MAC;l

62.
16.
42.
52.
18.
40.

Total of 282./282.

blocks in 7.

files

UFO [ 12, 20]
blocks in O.

Total of 0./0.

files

UFO [12,24]
blocks in O.

Total of 0./0.

files

UFO [12,40]
blocks in O.

Total of 0./0.

files

UFO [200,200]
BLOLAINIT .CMO; 1
SGNBLOORV.CMO;l
SGNEXEC.CMD;l
SGNICIS .CMO; 1
SGNIP.CMO;l
SGNKLAB.CMO;l
SGNPER.CMO;l
SGNSTANO.CMO;l
SGNTT.CMO;l
SYSGEN.CMD;l
SYSGEN2.CMO;l
SYSGEN3.CMO;l
Total of 792./792.

total
directories

VJ..

14.
20.
175.
45.
29.
70.
184.
4.
42.
77.
78.
54.
blocks in 12.

files
blocks

F-38

392.

files

25.

DISTRIBUTIOR KIT CONTESTS

RK06/07 CLISRC
F.2.2

CLISRC
UFO [ 1, l]
RSXMAC ID. MAC; 1
RORMSl.MAC;l
EXEMC.MLB;l
RMSMAC.MLB;l
OAPRLX.OOL;l
OAPllX.OOL;l
RMSRLX.ODL;l
RMSll. OOL; 1
RMSllS.OOL;l
RMSllX.OOL; 1
RMS12S .. ODL;l
RMS12X.OOL;l
RMSOAP.OLB;l
RMSLIB.OLB;l
RSXMAC.SML;l
OAPRES.STB;l
RMSRES.STB;l
OAPRES.TSK;l
RMSRES.TSK;l
RMSRESSUB.TSK;l

85.
4.
6.
4.
6.
95.
214.
253.
2.
3.
40.
87.
48.

Total of 1158 ./1163.

blocks in 20.

38.
12.
66.
185.
2.
6•

..,
".

files

UFO [1,2]
STARTUP.CMO;l
RMSOES.HLP;l
HELP.ULB;l
Total of 2567./2567.

6.
308.
2253.
blocks in 3.

files

UFO [ 1,6]
ERRLOG.ULB;l
ERRLOGETC.ULB;l
Total of 692./692.

622.
70.
blocks in 2.

files

F-39

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UFD [1,24]
BCKNON.CMD;l
BCKNRN.CMD;l
CNVNON.CMD;l
CNVNOO.CMD;l
CNVNRN.CMD;l
CNVNRR.CMD;l
DAPRES.CMD;l
DEFNON.CMD;l
DEFNRN.CMD;l
DESNON.CMD;l
DESNRN.CMD;l
DSPNON.CMD;l
DSPNRN.CMD;l
IFLNON.CMD;l
IFLNRN.CMD;l
RMSRES.CMD;l
RSTNON.CMD;l
RSTNRN.CMD;l
BCKNON.ODL;l
BCKNRN.ODL;l
CNVNON.ODL;l
CNVNOO.ODL;l
CNVNRN.ODL;l
CNVNRR.ODL;l
DAPRES.ODL;l
DEFNON.ODL;l
DEFNRN.ODL;l
DESNON.ODL;l
DESNRN.ODL;l
DSPNON.ODL;l
DSPNRN.ODL;l
IFLNON.ODL;l
IFLNRN.ODL;l
RMSDES.ODL;l
RMSODL .. ODL;l
RMSRES.ODL;l
RSTNON.ODL;l
RSTNRN.ODL;l
RMSUTL.OLB;l

Total of 888./888.

1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
l.
1.
1.
1.

1.
1.

8.
8.
10.
5.
5.
5.
1.

3.
3.
6.
6.
7.
7.
5.
3.
9.
24.
11.
11.
11.
722.

blocks in 39.

files

UFO [l,34]
DAPRES.MAP;l
RMSRES.MAP;l
RMSRESSUB.MAP;l

Total of 110./110.

16.
59.
35.

blocks in 3.

files

F-40

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UFD [1,50]
Total of 0./0.

blocks in O.

files

UFD [1,51]
BRU64K.STB;l
BRU64K.SYS;l
Total of 272./272.

14.
258.
blocks in 2.

files

UFD [1,54]
ACF.BSL;l
DBDRV.STB;l
DDDRV.STB;l
DKDRV.STB;l
DLDRV.STB;l
DMDRV.STB;l
DPDRV.STB;l
DRDRV.STB;l
DUDRV.STB;l
DXDRV.STB;l
DYDRV.STB;l
LPDRV.STB;l
MMDRV.STB;l
MSDRV.STB;l
MTDRV.STB;l
RSXllM.STB;l
RSXllM. SYS; 1
ACO.TSK;l
ACS.TSK;l
BAD.TSK;l
BOO.TSK;l
BRU.TSK;l
CDA.TSK;l
CMP.TSK;l
CRF.TSK;l
DBDRV.TSK;l
DDDRV.TSK;l
DKDRV.TSK;l
DLDRV.TSK;l
DMDRV.TSK;l
DMO.TSK;l
DMP.TSK;l
DPDRV.TSK;l
DRDRV.TSK;l
DUDRV.TSK;l
DXDRV.TSK;l
DYDRV.TSK;l
EDI.TSK;l
FCPSML.TSK;l

26.
1.
1.
1.
1.
1.
1.
1.
2.
1.
1.
1.
1.
1.
1.
12.
258.
39.
14.
53.
33.
176.
166.
50.
36.
5.
6.
4.

4.
5.
15.
61.
3.
5.
11.
4.
5.
61.
96.

F~41

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UIC [1,54]
FLX.TSK;l
FMT.TSK;l
ICP.TSK;l
INI. TSK; 1
INS.TSK;l
IOX.TSK;l
LBR.TSK;l
LOA.TSK;l
LPDRV.TSK;l
MAC.TSK;l
MCR.TSK;l
MMDRV.TSK;l
MOU.TSK;l
MSDRV.TSK;l
MTDRV.TSK;l
PAT.TSK;l
PIP.TSK;l
RCT.TSK;l
RMSBCK.TSK;l
RMSCNV.TSK;l
RMSDEF.TSK;l
RMSDES.TSK;l
RMSDSP.TSK;l
RMSIFL.TSK;l
RMSRST.TSK;l
SAV.TSK;l
SLP.TSK;l
TKB.TSK;l
TKN.TSK;l
UFD.TSK;l
UNL.TSK;l
VFY.TSK;l
VMR.TSK;l
ZAP.TSK;l

Total of 4005./4005.

132.
68.
141.
58.
60.
109.
72.
29.
4.
89.
113.
7.
46.
7.
6.
45.
73.
11.
157.
167.
139.
241.
142.
136.
177.
77.
48.
176.
18.
8.
23.
56.
156.
51.

blocks in 73.

files

UFO [2,300]
FILEl.; 1
FILE2.;l
CMP.CMD;l
CONALL.CMD;l
CONCNT.CMD;l
DMP.CMD;l
DSC.CMD;l
FLX.CMD;l
INSTSK.CMD;l
INTERA.CMD;l
LBR.CMD;l
LOAD.CMD;l
MCRTST.CMD;l
PAT.CMD;l
PMD.CMD;l

1.
1.
2.
""I

•

2.
1.
6.
3.
1.

4.
2.
10.
6.
2.
5.

F-42

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UIC [2,300]

9.
2.

SIOE.CMD; 1
SLP.CMD;l
SLPCMD.CMD;l
STRTUP.CMD;l
UETP.CMD;l
UNLOAD.CMD;l
UTIL.CMD;l
CRTEST:MAC;l
DEFINE.MAC; 1
DUMMY.MAC;!
LOGGER.MAC;!
MACROl.MAC;l
MACR02.MAC;l
MACR03.MAC;l
NULl.MAC; 1
NUL2.MAC;l
NUL3.MAC;l
OBJCTl.MAC;l
OBJCT2.MAC;l
OBJCT3.MAC;l
PATCHl.MAC;l
QTRUN.MAC;l
PATCHl.OBJ; 1
DEVM.SAM;l
UETPCOR.TMP;l
ASRC.XXX;l
PATCHD.XXX;l
SLPDAT.XXX;l
SLPOUT.XXX;l
Total of 300./300.

1.
10.
25.
2.
1.
1.
49.
1.
26.
L
1.
1.
19.
19.
19.
1.
1.
1.
1.
28.
1.
3.
18.
1.
1.
1.
3.

blocks in 44.

files

UFO [ 11, 10]
Total of 0./0.

blocks in O.

files

UFO [12,10]
INDSYS.CLB;l
ABOOV.MAC;l
ACS.MAC;!
ACTFIL.MAC;l
ALLOV.MAC;l
ALLSUB.MAC;l
ALTOV.MAC;l
ASNOV.MAC;l
ATLOV.MAC;l
BOOT.MAC;!
BOOTRC.MAC;l
BOTPH2.MAC;l
BRKOV.MAC;l

103.
24.
23.
6.
27.
21.
15.
34.
49.
29.
2.
19.
3.

F-43

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UIC [12,10]
BYE.MAC;!
CBTO.MAC;l
CDT2B.MAC;l
CLIOV .MAC; 1
CLQOV.MAC;l
COLOG.MAC;l
COT2B.MAC;l
CRETSK.MAC;l
DEAOV.MAC;l
DEVOV.MAC;l
DFSYM.MAC;l
DISMNT.MAC;l
DV20V.MAC;l
EDCKP.MAC;l
ERMSG.MAC;l
ERRMSG.MAC;l
ERROV.MAC;l
FILBN.MAC;l
FIXOV.MAC;l
FLAOV.MAC;l
FMTDV.MAC;l
FNDUCB.MAC;l
GETNUM.MAC;l
GNBLK.MAC;l
GTBYT.MAC;l
GTMNM.MAC;l
GTTSK.MAC;l
HELLO.MAC;!
ICBDEF.MAC;l
ICPASK.MAC;l
ICPASV.MAC;l
ICPASl.MAC;l
ICPAS2.MAC;l
ICPAS3.MAC;l
ICPAS4,,MAC;l
ICPASS.MAC;l
ICPATS.MAC;l
ICPBLK.MAC;l
ICPCHA.MAC;l
ICPCHN .MAC; 1
ICPENB.MAC;l
ICPERA.MAC;l
ICPERR.MAC;l
ICPEXF.MAC;l
ICPEXI.MAC;l
ICPFCL.MAC;l
ICPFDC.MAC;l
ICPFEX.MAC;l
ICPFIL.MAC;l
ICPFMI .MAC; 1
ICPFMO.MAC;l
ICPFMS.MAC;l
ICPFMX.MAC;l
ICPFOP.MAC;l
ICPFUT.MAC;l

45.
7.
6.
76.
19.
9.
4.
16.
10.

47.
19.
79.
52.
4.
15.
10.
13.
20.
30.

19.
4.
8.
4.
5.
6.

4.
8.
146.
5.
6.
14.
12.
10.
11.

9.
7.
11.
8.

5.
9.
16.
5.
18.
14.
7.

7.
11.

4.
2.
2.
2.
27,,

18.
22.

F-44

DISTRIBU'l'IOR KIT CONTENTS

RK06/07 CLISRC (Cont.)
UIC [12,10]
ICPFlO.MAC;l
ICPF52.MAC;l
ICPGNB.MAC;l
ICPGOT .MAC; 1
ICPGTK.MAC;l
ICPGTN .MAC; 1
ICPIFl.MAC;l
ICPIF2.MAC;1

ICPIF3.MAC;l
ICPIF4.MAC;l
ICPIMP.MAC;l
ICPINX.MAC;l
ICPIN2. MAC; 1
ICPIN3.MAC;1
ICPIN4.MAC;l
ICPIN5.MAC;1
ICPMCR.MAC;l
ICPMEM.MAC;l
ICPMEN.MAC;l
ICPNEC.MAC;l
ICPNEI. MAC; 1
ICPNEN.MAC;l
ICPNET.MAC;l
ICPNEX.MAC;l
ICPNPR.MAC;l
ICPNPl.MAC;l
ICPONR.MAC;l
ICPPAR.MAC;l
ICPPDW.MAC;l
ICPPOP.MAC;l
ICPPOl.MAC;l
ICPPRC.MAC;l
ICPPRE.MAC;l
ICPPRS.MAC;l
ICPROT.MAC;l
ICPSET.MAC;l
ICPSTP.MAC;l
ICPSUB.MAC;l
ICPSUT.MAC;l
ICPSUl.MAC;l
ICPSU2.MAC;l
ICPSU3.MAC;l
ICPSU4.MAC;1
ICPSU5.MAC;l
ICPSU6.MAC;l
ICPSYC.MAC;l
ICPSYT.MAC;l
ICPSYl.MAC; 1
ICPSY2.MAC;l
ICPSY3.MAC;l
ICPTDV.MAC;l
ICPTES.MAC;l
ICPTPA.MAC;l
ICPVEC.MAC;l
ICPWFT.MAC;l

2.
1.

6.
14.
13.

4.
9.
6.
8.
8.
30.
6.
8.
15.
18.

6.
7.
5.
2.
1.
1.
2.
14.
3.
1.
5.
24.
15.
14.
11.
8.
13.
29.

6.
28.
6.
3.
28.
5.
20.
19.
18.
8.

4.
5.
14.
25.
26.
8.
12.

19.
11.
7.
2.
10.

F-45

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UIC [12,10]
ICPXMD.MAC;l
INIALL.MAC;l
INIBAD.MAC;l
INIBIT .MAC; 1
INIGCL.MAC;l
INIHOM.MAC; 1
INIMAG.MAC;l
ININDX .MAC; 1
INIPAR.MAC;l
INIROT.MAC;l
INIUPD. MAC; 1
INSBF.MAC;l
INSCM.MAC;l
INSFL.MAC;l
INSFSR.MAC;l
INSGC.MAC;l
INSHD.MAC;l
INSLB.MAC;l
INSPS.MAC;l
INSROT.MAC;l
IODAT.MAC;l
KEYWD.MAC;l
LDBUF.MAC;l
LDCTL.MAC;l
LDDRV.MAC;l
LDFIL.MAC;l
LDF IN. MAC; 1
LDLDB.MAC;l
LDUIC.MAC;l
LKLST.MAC;l
LNlOV.MAC;l
LUNOV.MAC;l
MCRDEF.MAC;l
MCRDIS.MAC;l
MCROOT,.MAC;l
MCROV.MAC;l
MDPOV.MAC;l
MGCML.MAC;l
MOUCLS.MAC;l
MOUDAT.MAC;l
MOUDIS.MAC;l
MOUDSK.MAC;l
MOUFOR.MAC;l
MOUMSG.MAC;l
MOUPAR.MAC;l
MOUPRE.MAC;l
MOUROT.MAC;l
MOUSUB.MAC;l
MOUTAP.MAC;l
MSGOUT.MAC;l
NETSUB.MAC;i
OPEOV.MAC;l
PAROV.MAC;l
PRlOV.MAC;l
RAPOV.MAC;l

4.
23.
55.
35.
69.
23.
42.
38.
119.

64.
41.

6.
10.
17.
2.
2.
30.
72.
26.
19.
7.
5.
6.
27.
26.
8.
33.
22.
3.
7.
9.
13.
5.
79.
10 ..
59.
10.
35.
20.
18.
32.
26.
30.
16.
43.
4.
9.
52.
38.
12.
2.
62.
24.
8.
14.

F-46

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UIC [12,10]
REAOV.MAC;l
REDOV.MAC;l
REQCOT.MAC;l
RPSOV.MAC;l
RUNOV.MAC;l
SAVBOT.MAC;l
SAVCPU.MAC;l
SAVCl.MAC;l
SAVC2.MAC;l
SAVC3.MAC;l
SAVDB.MAC;l
SAVDF .. MAC;l
SAVDK.MAC;l
SAVDL.MAC;l
SAVDM.MAC;l
SAVDP.MAC;l
SAVDR.MAC;l
SAVDRT.MAC;l
SAVDS.MAC;l
SAVDT.MAC;l
SAVDU.MAC;l
SAVDX.MAC;l
SAVDY.MAC;l
SAVE.MAC;!
SAVEM.MAC;l
SAVFN.MAC;l
SAVINS.MAC;l
SAVSIZ.MAC;l
SAVST.MAC;l
SAVSUB.MAC;l
SAVTRC.MAC;l
SMLGCL.MAC;l
SPSOV.MAC;l
SRTOV.MAC;l
SSMOV.MAC;l
STSUB.MAC;l
STlOV.MAC;l
ST20V.MAC;l
ST30V.MAC;l
ST40V.MAC;l
SXlOV.MAC;l
SX20V.MAC;l
SX30V.MAC;l
SX40V.MAC;l
SYMTB.MAC;l
SYSOV.MAC;l
SYSROT.MAC;l
TASOV.MAC;l
TIMOV.MAC;l
TISUBS. MAC; 1
TKTN.MAC;l
TPARS2.MAC;l
TPDEB.MAC;l
TPMAC2.MAC;l

7.
12.
11.
28.
26.
17.
13.
20 ..

17.
6.
14.
12.
13.
18.
15.
14.
19.
4.
12.
13.
28.
19.
18.
62.
12.
16.
66.
26.
14.
35.
2.
15.
62.
27.
4.
16.
35.
41.
41.
29.
42.
52.
18.
40.
14.
23.
10.
36.
26.
4.
49.
44.
5.
32.

F-47

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UIC [12,10]
TPNUMB.MAC;l
UFO.MAC;l
UFOPAR.MAC;l
UFOPTB.MAC;l
UFOTP.MAC;l
UNLCTL.MAC;l
UNLFIL.MAC;l
WRTMS.MAC;l

23.
16.
7.
6.
29.
6.
6.

Total of 4725./4731.

blocks in 240.

files

UFO [12,20]
FILASM.CMO;l
FILLIBBLO .CMO; 1
ICPASM.CMO;l
ICPLIBBLO.CMO; 1
INIASM.CMO;l
INILIBBLO .CMO; 1
LOAASM.CMO;l
MCRASM.CMO;l
MCRLIBBLO.CMO;l
Total of 41./41.

4.
1.
12.
2.
2.
1.
2.
14.
3.

blocks in 9.

files

UFO [ 12, 24]
FILASM.CMO;l
FILLIBBLO .CMO; 1
ICPASM.CMO;l
ICPLIBBLO.CMO;l
INIASM.CMO;l
INILIBBLO .CMO; 1
LOAASM.CMO;l
MCRASM.CMO;l
MCRLIBBLO.CMO;l
Total of 41./41.

4.
1.

12.
2.
2.
1.
2.
14.
3.

blocks in 9.

files

UFO [12,30]
Total of 0./0.

blocks in 0.

files

UFO [12,34]
Total of 0./0.

blocks in O.

files

F-48

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UFO [ 12, 40]

Total of 0./0.

blocks in 0.

files

UFO [14,10]
ATCMD.MAC;l
ATCOM.MAC;l
ATINIT.MAC;l
ATPAGE.MAC;l

, n
.J..V •

4.
7.
29.

GBCMD~MAC;l

GBCOM.MAC;l
GBINIT.MAC; 1
GBLATM.MAC;l
GBLCHA.MAC;l
GBLGBM.MAC;l
GBLHLM.MAC;l
GBLIOM.MAC;l
GBLMOM.MAC;l
GBLSSM.MAC;l
GBLTHM.MAC;l
GBPAGE.MAC;l
HLCOM.MAC;l
HLINIT .MAC; 1
HLPAGE.MAC;l
IOCMO.MAC;l
IOCOM.MAC;l
IOINIT .MAC; 1
IOPAGE.MAC;l
L36ATM.MAC;l
L36CHA.MAC;l
L36HLM.MAC;l
L36MOM.MAC;l
L36SSM.MAC;l
L36THM.MAC;l
MOCMO.MAC;l
MOCOM.MAC;l
MOINIT .MAC; 1
MOPAGE.MAC;l
NULllS. MAC; 1
REMAP.MAC;l
RMOOEF.MAC;l
RMOEMO.MAC;l
RMOMAC.MAC;l
RMORIV.MAC;l
RMOXCM.MAC;l
SSCMO.MAC;l
SSCOM.MAC;l
SSINIT.MAC; 1
SSPAGE.MAC;l
TERM ID. MAC; 1
THCMO.MAC;l
THCOM.MAC;l

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

6.
3.
11.
33.
4.
2.
2.
5.
5.

6.
6.
7.
25.
57.
1.
3.

6.
48.
7.
17.
5.
3.
2.
6.

30.
8.

6.
6.

F-49

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UIC [14,10]
THFllL.MAC; 1
THINIT.MAC;l
THPAGE.MAC;l
V05ATM.MAC;l
V05CHA.MAC;l
V05HLM.MAC;l
V05IOM.MAC;l
V05MOM.MAC;l
VlHATM.MAC;l
VlHCHA.MAC;l
VlHHLM.MAC;l
VlHIOM.MAC; 1
VlHMOM.MAC;l
VlHSSM.MAC;l
VlHTHM.MAC;l
V50ATM.MAC;l
V50CHA.MAC;l
V50HLM.MAC;l
V50!OM.MAC;1
V50MOM.MAC;l
V50THM.MAC;l
V52ATM.MAC;l
V52CHA.MAC;l
V52HLM.MAC;l
V52IOM.MAC; 1
V52MOM.MAC;l
V52SSM.MAC;l
V52THM.MAC;l

15.
13.
56.
4.
3.
2.
5.
5.
4.
3.
2.
5.
5.
5.
6.
4.
2.
2.
5.
5.
6.
4.
2.
2.
5.
5.
5.
6.

Total of 594./594.

blocks in 75.

files

UFO [14,20]
RMOASM.CMO;l
Total of 8./8.

blocks in 1.

file

UFO [14,24]
RMOASM.CMO;l
Total of 11./11.

11.
blocks in 1.

file

UFO [14,30]
Total of 0./0.

blocks in O.

files

F-50

DISTRIBDTIOR KIT CONTENTS

RK06/07 CLISRC (Cont)
UFO [14, 34]
Total of 0./0.

blocks in O.

files

UFO [14,40]
Total of 0./0.

blocks in 0.

files

UFO [15,10]
ACNT.MAC;l
BROAD.MAC;!
HELLO.MAC;!
HELROT.MAC;l
HLP.MAC;l
HLPSUB.MAC;l
HSTTAB.MAC;l
SHUFL.MAC;l
SHUTUP.MAC;l
Total of 567./567.

162.
61.
129.
13.
8.
78.
23.
36e
57.
blocks in 9.

files

UFO [15,20]
MLTASM.CMO;l
MLTLIBBLD.CMO;l
SHUTUPASM.CMO;l
Total of 3./3.

blocks in 3.

1.
1.

1.
files

UFO [15,24]
MLTASM.CMO;l
MLTLIBBLO.CMO;l
SHUFLASM.CMO;l
SHUTUPASM.CMO;l
Total of 4./4.

blocks in 4.

1.
1.
1.
1.

files

UFO [15,30]

Total of 0./0.

blocks in O.

files

F-51

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UFO [15,34]
Total of 0./0.

blocks in O.

files

UFO [15,40]
Total of 0./0.

blocks in 0.

files

UFD [23,10]
ABORT.MAC;l
ALFN.MAC;l
ALFNUM.MAC;l
ALL.MAC;l
ALLOCATE.MAC;l
AND.MAC;l
ANDA.MAC;l
APPEND.MAC;l
ASSIGN.MAC;l
ASTOV.MAC;l
AT.MAC;l
BACKUP.MAC;l
BASIC.MAC;l
BROADCAST.MAC;l
CALLOV.MAC;l
CANCEL.MAC;l
CATCHALL.MAC;l
CBM.MAC;l
COBOL.MAC;l
COD.MAC;l
COMMAC.MAC;l
COMMAND.MAC;l
CONTINUE. MAC; 1
CONVERT.MAC;l
COP.MAC;l
COPY.MAC;l
CORAL.MAC;l
CREATE.MAC;l
CSEP.MAC;l
CUIC.MAC;l
DATE.MAC;l
DBUG.MAC;l
DCL.MAC;l
DCLDAT.MAC;l
DCLMAC.MAC;l
DCLMPL.MAC;l
DEALLO.MAC;l
DEASSIGN.MAC;l
DEBUG.MAC;l
DELETE.MAC;l

4.
10.
13.
5.
3.
9.
4.

3.
6.
6.

2.
13.
3.
4.
7.
2.
5.
3.
21.
3.
L
10.
2.
7.
3.
4.
15.
4.
2.
3 ..
4.
10.
2.
22.
56.
1.
3.
4.
2.
7.

F-52

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UIC [23,10]
DEV.MAC;l
DIFFERENC.MAC;l
DIRECTORY. MAC; 1
DISMOUNT.MAC;l
DISPATCH.MAC;l
DQBFE.MAC;l
DQBFS.MAC;l
DSPCMD.MAC;l
EDIT.MAC;l
EDOC.MAC;l
ELEMENT.MAC;l
EOL~MAC;l

ERR.MAC;l
ERRORO.MAC;l
ERRORR.MAC;l
ERRl.MAC; 1
FIL.MAC;l
FIX.MAC;l
FLAGS.MAC;l
FNAM.MAC;l
FORMAT.MAC;l
FORTRAN.MAC;l
FSEP.MAC;l
GTARG.MAC;l
HELP.MAC;l
HOLD.MAC;l
IFIL.MAC;l
INITIAL.MAC;l
INSTALL.MAC;l
JSR.MAC;l
LAB.MAC;l
LDCCD.MAC;l
LIBRARY.MAC;l
LINK .MAC; 1
LINKl.MAC; 1
LIT.MAC;l
LOAD.MAC;l
LOGIN .MAC; 1
LOGOUT.MAC;l
LOVR.MAC;l
LUIC.MAC;l
MACRO.MAC;l
MAP.MAC;l
MATCH.MAC;l
MCR.MAC;l
MOUNT.MAC;l
NEW.MAC;l
NFIL.MAC;l
NFT.MAC;l
NLIT.MAC;l
NOD.MAC;l
ODEV.MAC;l
OR.MAC;l
OUIC.MAC;l
PARSER.MAC;l

2.
5.
5.
4.
3.
10.
4.
28.
12.
2.
22.
3.
11.

5.
2.
3.
3.

3.
4.
6.

9.
17.
2.
5.
4.
3.
2.
16.
6.
3.
2.
5.
12.
16.
6.
17.
5.
2.
2.
12.
3.
18.
24.
7.
2.
14.
4.
3.
3.
3.
2.
2.
6.
2.
7.

F-53

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UIC [23,10]
PASCAL.MAC;!
PIP.MAC;l
PREPARSE.MAC;l
PRI.MAC;l
PR INT • MAC; 1
PRO.MAC;!
PROC.MAC;l
PURGE.MAC;!
QIOBF .MAC; 1
QUA.MAC;!
RELEASE.MAC;!
REMOVE.MAC;!
RENAME.MAC;!
REQUEST.MAC;!
RUN.MAC;!
SCTBIT.MAC;l
SEP.MAC;!
SET.MAC;!
SETl.MAC; 1
SHOW.MAC;!
SORT.MAC;!
SPAWN.MAC;!
START.MAC;!
STOP.MAC;!
SUBMIT.MAC;!
SY.MAC;l
T.MAC;l
TERM.MAC;!
TI.MAC; 1
TIME.MAC;l
TLINK.MAC; 1
TRANSL.MAC;!
TSET.MAC;l
TSHOW.MAC;l
TST.MAC;l
TYPE.MAC;!
UIC.MAC;l
UND.MAC;l
UNFIX.MAC;!
UNLOCK.MAC;!
VER.MAC;l
WFIL.MAC;l
WUIC.MAC;l
WVER.MAC;l
WXTN.MAC;l
XCOPY.MAC;l
XDCL.MAC;l
XTN.MAC;l
Total of 1002./1002.

7.
7.
14.
2.
11.
9.
2.
3.
8.

7.
3.
2.
3.
2.
7.
7.
2.
15.
21.
21.
10.
5.
9.
8.
9.
3.
2.
2.
3.
2.
10.
5.
20.
16.
5.
3.
2.
5.
3.
3.
2.
2.
2.
2.
2.
6.
35.
2.

blocks in 143.

F-54

files

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UFO [23,24]

4.
22.

OCL.CMO;l
OCLASM.CMO;l
Total of 26./26a

Total of 0./0.

blocks in 2.

blocks in 0.

files

UFO [23,40]
Total of 0./0.

blocks in O.

files

UFO [24,10]
TOX.MAC;l

108.

Total of 108./108.

blocks in 1.

file

UFO [24,20]
TOXASM.CMO;l
Total of 1./1.

blocks in 1.

file

UFO [45,10]
KRATE.B2S;l
KRATE.FTN;l
KAAOMP.MAC;l
KAAORV.MAC;l
KAAS03.MAC;l
KADAGR.MAC;l
KADORV.MAC;l
KADGCH.MAC;l
KADINP.MAC;l
KADINO .MAC; 1
KADINl .MAC; 1
KADIN2.MAC;1
KAOIN3.MAC;1
KAOIN4.MAC;l
KAOIN5.MAC;l
KADSWP.MAC;l

7.
7.
12.
24.
5.
6.
14.
20.
13.
6.
8.
6.
8.
6.
8.
7.

F-55

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UIC [45,10]

14.
13.
11.
5.
10.
5.
6.
10.
12.
7.
7.
30.
4.
4.
11.
10.
6.
21.
4.
18.
7.
3.
7.
4.
5.
4.
12.
13.
7.
7.
5.
5.
10.
13.

KAST.MAC;!
KBFRMG.MAC;l
KBFSTS.MAC;l
KCLOKA.MAC;l
KCLOKB.MAC;l
KCOMM.MAC;l
KCVADF.MAC;l
KDIGO.MAC;l
KDIO.MAC; 1
KDISWP .MAC; 1
KDOSWP.MAC;l
KDRDRV.MAC;l
KDSCADeMAC;l
KDSDGO.MAC;l
KDVDF.MAC;l
KEFQA.MAC;l
KFLT16.MAC;l
KGHIST.MAC;l
KIESTO.MAC; 1
KKWDRV.MAC;l
KLQSUB.MAC;l
KMUL.MAC;l
KPAA.MAC;l
KPRE.MAC;l
KRCLKB.MAC;l
KRLOC.MAC;l
KRWBF.MAC;l
KSET.MAC;l
KSTADC.MAC;l
KSTB.MAC;l
KSTIBF.MAC;l
KSTOP.MAC;l
KSUB.MAC;l
KSWDF.MAC;l
LABMAC.MAC;l

Total of 473./473.

blocks in 51.

files

UFO [45,20]
ASMK.CMD;l
KCLEAN.CMD;l
KCOMBLD.CMD;l
KLABMLB.CMD;l
KL IBBLD. CMD; 1
KLIBRP.CMD; 1
K4ASM.CMD;l

Total of 7./7.

blocks in 7.

1.
1.

.i. •

1.
1.
1.
1.

files

F-56

DISTRIBDTIOR KIT CONTENTS

RK06/07 CLISRC (Cont.)
UFO [ 45, 24]
ASMK.CMD;l
KCLEAN.CMD;l
KCOMBLO.CMD;l
KLABMLB.CMD;l
KLIBBLD.CMD;l
KLIBRP.CMD; 1
K4ASM.CMD;l
Total of 7./7.

blocks in 7.

1.
1.
1.
1.
1.
1.
1.

files

UFO (45,30]
Total of 0./0.

blocks in O.

files

UFO [45,34]
Total of 0./0.

blocks in 0.

files

UFO [104,10]
DEVSMl.CNF; 1
DEVUDA.CNF;l
DISPATCH .CNF; 1
DSPlMl.CNF; 1
DSP2Ml. CNF; 1
DSP3Ml.CNF;l
DSP4Ml.CNF;l
DSP5Ml.CNF;l
DSP6Ml.CNF;l
DSP7Ml.CNF;l
EMLl 1. CNF; 1
ERK05.CNF;l
ERK67.CNF;l
ERL12.CNF;l
ERM05.CNF;l
ERM23.CNF;l
ERM80.CNF;l
ERP07.CNF;l
ERP23.CNF;l
ERP456.CNF;l
ERRORM.CNF;l
ERSll .CNF; 1
ERS34.CNF;l
ERXOl.CNF;l
ERX02.CNF;l
ETAll.CNF; 1
ETCl 1. CNF; 1

28.
15.
46.
40.
17.
17.
15.
19.

7.
27.
37.
29.
64.
40.
49.
49.
48.
46.
31.
51.
20.
24.
36.
21.
28.
16.
19.

F-57

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UIC [104,10]
ETSll. CNF; 1
ETU58.CNF;l
ETU77.CNF;1
ET0310.CNF;l
ET1645.CNF;l
EUNKWN.CNF;l
EllXX.CNF;l
Ell34.CNF;1
Ell44. CNF; 1
Ell60.CNF;1
Ell7X.CNF;l
FINLMl .CNF; 1
FMlNMl.CNF;l
FMlWMl.CNF;l
FM2CM1.CNF;l
FM3CM1.CNF;l
FM4NM1.CNF;l
FM4WM1.CNF;l
INITMl.CNF;l
MSCPAT.CNF;l
MSCPBD.CNF;l
MSCPEN.CNF;l
MSCPTO.CNF;l
NMLll.CNF; 1
NRK67.CNF;l
NRM05.CNF;l
NRM23.CNF;l
PARSEM.CNF;l
PARSlM.CNF;l
PARS2M.CNF;l
PARS3M.CNF;l
PRS2AM.CNF;l
PRS2BM.CNF;l
SELTMl.CNF;l

57.
26.
38.
26.
38.
15.
30.
38.
38.
36.
40.
4.
7.

7.
5.
7.
27.
28.
9.
25.
82.
81.

45.
6.
4.
5.
5.
38.
29.
7.
13.
33.
32.
12.

Total of 1732./1732.

blocks in 61.

files

UFO [104,20]
ERRLOGASM.CMD;l
ERRLOGLIB.CMD;l
Total of 29./29.

26.
3.

blocks in 2.

files

UFD [104,30]
Total of 0./0.

biocks in O.

files

F-58

DISTRIBUTION KIT CONTENTS

RK06/07 CLISRC (Cont.)
UFD (104,40]
Total of 0./0.

blocks in 0.

files

UFD (200,l]
ERASE.MAC;l
GSA.MAC;l
PARSE.MAC;l
RENAME.MAC;l
SEARCH.MAC;l
ERASE.TSK;l
PARSE.TSK;l
RENAME.TSK;l
SEARCH.TSK;l
Total of 151./151.

18.
9.

10.
8.

25.
22.
26.
25.
blocks in 9.

files

UFD (200,200]
FCSRES.MAC;l

11.

Total of 11./11.

blocks in 1.

Grand totai
directories

20041./20052.

file
biocks

F-59

828.

files

45.

DISTRIBUTION KIT CONTENTS

RL01 /02 RSXM35
F.3

DIRECTORY LISTING OF THE RLOl/02 DISTRIBUTION KIT

All the files included in the RLOl/02 distribution kit are
follows:

F.3.1

RSXM35
UFO [1,1]

66.
8.
3.
45.
230.
16.
253.

EXEMC.MLB;l
ODT.OBJ;l
TRACE.OBJ;l
EXELIB. OLB; 1
SYSLIB.OLB;l
VMLIB. OLB; 1
RSXMAC.SML;l

Total of 621./621.

blocks in 7.

files

[ 1, 2]

UFO

14.
6.
29.

RMS IN STAL. CMD; 1
STARTUP.CMD;l
QIOSYM. MSG; 1

Total of 49./49.

blocks in 3.

files

UFO

Total of 0./0.

blocks in O.

[ 1, 3]

files

UFD (1,4]

Total of 0./0.

blocks in

files

UFD

Total of 0./0.

blocks in 0.

files

UFO

Total of 0./0.

blocks in 0.

[ l; 6]

[ 1, 7]

files

F-60

listed

DISTRIBUTION KIT CONTENTS

RL01/02 RSXM35 (Cont.)
UFD [l,20]
Total of 0./0.

blocks in O.

files

UFD [1,24]
Total of 0./0.

blocks in 0.

files

UFD [l,30]
Total of 0./0.

blocks in 0.

files

UFD [1,34]
Total of 0./0.

blocks in 0.

files

UFD [l,50]
Total of 0./0.

blocks in 0.

files

UFD [1,54]
ACF.BSL;l
SGNPARM.CMD;l
DBDRV.STB;l
DDDRV.STB;l
DKDRV.STB;l
DLDRV.STB;l
DMDRV.STB;l
DPDRV.STB;l
DRDRV.STB;l
DUDRV.STB;l
DXDRV.STB;l
DYDRV.STB;l
LPDRV.STB;l
MMDRV.STB;l
MSDRV.STB;l
MTDRV.STB;l
RSXllM. STB; 1
RSXllM. SYS; 1

26.
4.
1.
1.
1.
1.
1.
1.
1.
2.
1.
1.
1.
1.
1.
1.
12.
258.

F-61

DISTRIBUTION KIT CONTENTS

RL01/02 RSXM35 (Cont.)
UIC [1,54)

39.
14.
33.
5.

ACO.TSK;l
ACS.TSK;l
BOO.TSK;l
DBDRV.TSK;l
DDDRV.TSK;l
DKDRV.TSK;l
DLDRV.TSK;l
DMDRV.TSK;l
DMO.TSK;l
DPDRV.TSK;l
DRDRV.TSK;l
DUDRV.TSK;l
DXDRV.TSK;l
DYDRV.TSK;l
EDI.TSK;l
FCPSML.TSK;l
FLX.TSK;l
ICP.TSK;l
INI.TSK;l
INS.TSK;l
LBR.TSK;l
LOA.TSK;l
LPDRV.TSK;l
MAC.TSK;l
MCR.TSK;l
MMDRV.TSK;l
MOU.TSK;l
MSDRV.TSK;l
MTDRV.TSK;l
PIP.TSK;l
RCT.TSK;l
SAV.TSK;l
SLP.TSK;l
TKB.TSK;l
TKN.TSK;l
UFD.TSK;l
UNL.TSK;l
VMR.TSK;l

Total of 1979./1979.

4.
4.
5.
15.
3.
5.

11.
4.

5.
61.
96.
132.
141.
58.
60.
72.
29.
4.

89.
113.
7.
46.
7.
6.
73.
11.
77.
48.
176.
18.
8.
23.
156.
blocks in 56.

UFO

Total of 0./0.

blocks in O.

[ 1, 60]

files

UFO

Total of 0./0.

files

[1,64]

files

F-62

DISTRIBUTION KIT CONTENTS

RL01/02 RSXM35 (Cont.)
UFO [ 11, 10]

179.
255.
32.
73.
27.
19.

ICORV.MAC;l
IPORV.MAC;l
ISORV.MAC;l
TTATT.MAC;l
TTCAN.MAC;l
TTCIS .MAC; 1
TTOAT.MAC;l
TTDRV .. MAC;l
TTFP.MAC;l
TTICH.MAC;l
TTINI .MAC; 1
TTJZ.MAC;l
TTMAC.MAC;l
TTMIS.MAC;l
TTMOO.MAC;l
TTODN.MAC;l
TTOIS.MAC;l
TTRW.MAC;l
TTSUB.MAC;l
TTTBL.MAC;l
TTYH.MAC;l
TTYHV.MAC;l
TTYJ.MAC;l
TTYL.MAC;l
TTYZ.MAC;l

90.
262:
15.
122.
35.
7.
15.
7.
20.
18.
14.
83.
41.
20.
35.
28.
6.
16.
17.

Total of 1436./1436.

blocks in 25.

files

UFO [11,20]

Total of 0./0.

blocks in 0.

files

UFO [ 11, 24]

Total of 0./0.

blocks in O.

files

UFO [11, 40]

Total of 0./0.

blocks in O.

files

UFO [12,20]

Total of 0./0.

blocks in O.

files

F-63

DISTRIBUTION KIT CONTENTS

RL01/02 RSXM35 (Cont.)
UFO (12,24]
Total of 0./0.

blocks in O.

files

UFO (200,200]
BLDLAINIT.CMD;l
SGNBLDDRV.CMD;l
SGNKLAB.CMD;l
SGNSTAND.CMD;l
SYSGEN.CMD;l
SYSGEN2.CMD;l
SYSGEN3.CMD;l
Total of 317./317.

14.
20.
70.
4.
77.
78.
54.
blocks in 7.

Grand total of 4402./4402.

files

blocks in 98.

F-64

files in 21.

directories

DISTRIBUTION KIT CONTENTS

RL01/02 EXCPRV
F.3.2

EXCPRV

UFD [ 1, 1]
KMCLP.BIN;l
FCSMTA.OBJ;l
LPA.OBJ;l
LPS.OBJ;l
PURICR.OBJ;l
PURISA.OBJ;l
PURPCS.OBJ;l
PURUDC.OBJ;l
Total of 88./88.

6.
30.
16.
5.
6.
8.
14.
3.

blocks in 8.

files

UFD [l,20]
ACNBLD.BLD;l
ACSBLD.BLD;l
BOOBLD.BLD;l
BROBLD.BLD;l
BYEBLD.BLD;l
COTBLD.BLD;l
DCLBLD.BLD;l
DMOBLD.BLD;l
ELIBLD.BLD; 1
ERLBLD.BLD;l
FCPLRGBLD.BLD;l
FCPMDLBLD.BLD;l
FCPMINBLD.BLD; l
FCPSMLBLD.BLD;l
FCSRSlBLD.BLD;l
FllMSGBLD. BLD; 1
HELBLD.BLD;l
ICPBLD.BLD;l
ICPCOMBLD.BLD;l
ICQBLD.BLD;l
INIBLD. BLD; 1
INSBLD.BLD;l
LOABLD.BLD;l
LPIBLD.BLD; 1
LPPBLD.BLD;l
MCMBLD.BLD;l
MCRBLD.BLD;l
MOUBLD.BLD;l
MTABLD.BLD;l
PMDBLD.BLD;l
PMTBLD.BLD;l
PRTBLD.BLD;l
QCLBLD.BLD;l
QMGBLD.BLD;l
QPRBLD.BLD;l
RCTBLD.BLD;l
RMDBLD.BLD;l
SAVBLD.BLD;l

5.
2.

5.
2.
2.
4.
21.
3.
4.
5.
9.
17.
17.
11.
10.
3.
8.
8.
21.
9.
7.
3.
4.
2.
11.

9.
18.

4.
17.
10.
8.

9.
8.
9.
2.
2.
15.
14.

F-65

DISTRIBUTION KIT CONTENTS

RL01/02 EXCPRV (Cont.)
UIC [1,20]
SHFBLD.BLD;l
SHUBLD.BLD;l
TDXBLD.BLD;l
TKNBLD.BLD;l
UFDBLD.BLD;l
UNLBLD.BLD;l
ICBLD.CMD;l
IPBLD.CMD;l
ISBLD.CMD;l
UDCBLD.CMD;l
LPINIT.OBJ;l
SYSROT.OBJ;l
BOO.OLB;l
DCLO.OLB;l
DCL.R. OLB; 1
ERL.OLB;l
FCP.OLB;l
FIL.OLB;l
FllMSG.OLB;l
ICPllM. OLB; 1
INI .OLB; 1
INS.OLB;l
LAIN IT. OLB; 1
LOA.OLB;l
MCR.OLB;l
MLTUSR.OLB;~

MTA.OLB;l
PIPUTL.OLB;l
PMD.OLB;l
PRT.OLB;l
RMD.OLB;l
SAV.OLB;l
Total of 2042./2047.

2.
2.
2.
2.
2.
2.
1.
1.
1.
1.
4.
1.
11.

493.
54.
35.
87.
124.
9.
120.
84.
35.
21.
43.
193.
81.
102.
25.
32.
19.
70.
65.
blocks in 70.

files

UFO [ 1, 24]
ICBLD.CMD;l
IPBLD.CMD;l
ISBLD.CMD;l
UDCBLD.CMD;l
LP IN IT. OBJ; 1
SHUFL.OBJ;l
SYSROT.OBJ;l
TDX.OBJ;l
BOO.OLB;l
COT.OLB;l
ERL.OLB;l
FCP.OLB;l
FIL.OLB;l
ICPllM. OLB; 1
IN!. OLB; 1
INS.OLB;l

1.
1.
1.
1.

4.
4.
1.
12.
11.
26.
35.
92.
124.
120.
84.

37.

F-66

DISTRIBUTION KIT CONTENTS

RL01/02 EXCPRV {Cont.)
UIC [1,24]
21.
47 ..
57.
211.
81.
102.
25 ..
33.
74.
89.
17.
98.
69.

LAIN IT. OLB; 1
LOA.OLB;l
LPP.OLB;l
MCR.OLB;l
MLTUSR.OLB;l
MTA.OLB;l
PIPUTLoOLB;l
PMD.OLB;l
QMG.OLB;l
QMGCLI.OLB;l
RCT.OLB;l
RMD.OLB;l
SAV.OLB;l
Total of 1478./1482.

blocks in 29.

files

UFD [1,30]
Total of 0./0.

blocks in 0.

files

UFD [l,34]
Total of 0./0.

blocks in O.

files

UFD [11, 10]
ADDRV.MAC;l
AFDRV.MAC;l
ARDRV.MAC;l
BFCTL.MAC;l
CODRV.MAC;l
CORAL.MAC;!
CRASH.MAC;!
CRDRV.MAC;l
CTDRV.MAC;l
CVRTM.MAC;l
DBDRV.MAC;l
DDDRV.MAC;l
DFDRV.MAC;l
DKDRV.MAC;l
DLDRV.MAC;l
DMDRV.MAC;l
DPDRV.MAC;l
DRABO.MAC;l
DRASG.MAC;l
DRATP.MAC;l
DRATX.MAC;l

28.
99.
36.
19.
5.
49.
71.
21.
23.
51.
71.
26.
4.
10.
12.
9.

DRCIN .. MAC i l

21.

10.
17.
61.
18.
9.

F-67

DISTRIBUTION KIT CONTENTS

RL01/02 EXCPRV (Cont.)
UIC [11,10]
DRCLI.MAC;l
DRCMT.MAC;l
DRDAR.MAC;l
DRDCP.MAC;l
DRDRV.MAC;l
DRDSP.MAC;l
DREIF.MAC;l
DREXP.MAC;l
DRGCL.MAC;l
DRGEF.MAC;l
DRGIN. MAC; 1
DRGLI.MAC; 1
DRGPP.MAC;l
DRGSS.MAC;l
DRGTK.MAC;l
DRGTP.MAC;l
DRMAP.MAC;l
DRMKT.MAC;l
DRPUT.MAC;l
DRQIO. MAC; 1
DRRAS.MAC;l
DRREG.MAC;l
DRREQ.MAC;l
DRRES.MAC;l
DRSED.MAC;l
DRSMG.MAC;l
DRSPW.MAC;l
DRSST.MAC;l
DRSUB.MAC;l
DRSWS.MAC;l
DSDRV.MAC;l
DSSDI .MAC; l
DTDRV.MAC;l
DUDRV.MAC;l
DXDRV.MAC;l
DYDRV.MAC;l
EMDRV.MAC;l
ERROR.MAC;l
ERSUB.MAC;l
EXDBT.MAC;l
EXESB.MAC;l
GRDRV.MAC;l
ICOM.MAC;l
INITL~MAC;l

IOSUB.MAC;l
IPCOM .. MAC;l
IPMAP.MAC;l
ISCOM.MAC;l
LADRV.MAC;l
LKDRV.MAC;l
LOADR.MAC;l
LOWCR.MAC;l
LPDRV.MAC;l
LSDRV.MAC;l
MDSUB.MAC;l

33.
7.
6.

8.
62.
47.

43.
17.

36.
19.
1.
6.
11.
3.
7.
16.
58.
11.

22.
75.

15.
37.

5.
12.

26.
13.

85.
9.
36.
7.
22.
7.
23.
227.

36.
50.
20.
74.

40.
87.
29.
49.
4.

33.
53.
2.
2.
2.

90.
33.
54.
6.
24.
74.

43.

F-68

DISTRIBUTION KIT CONTENTS

RL01/02 EXCPRV (Cont.)
UIC [11,10]
MEMAP.MAC;l
MFDRV.MAC;l
MMDRV.MAC;l
MSDRV.MAC;l
MTDRV.MAC;l
NLDRV.MAC;l
NTDRV.MAC;l
PANIC.MAC;!
PARTY.MAC;!
PLSUB.MAC;l
PMT.MAC;l
POWER.MAC;!
PPDRV.MAC;l
PRDRV.MAC;l
QUEUE.MAC;!
REQSB.MAC;l
RSXMCO.MAC;l
SSTSR.MAC;l
SYSCM.MAC;l
SYSDF.MAC;l
SYSXT.MAC;l
SYTAB.MAC;l
TDSCH.MAC;l
UDCOM.MAC;l
UDDRV.MAC;l
XBDRV.MAC;l
XLDRV.MAC;l
XMDRV.MAC;l
XPDRV.MAC;l
XQDRV.MAC;l
XUDRV.MAC;l
XWDRV.MAC;l
Total of 3729./3729.

39.
124.
81.
97.

59.
4.
6.
16.
21.
16.
81.
24.
14.
12.
22.
105.
9.
31.
37.
10.
99.
11.
20.
7.
54.
29.
28.
66.
25.
41.
27.
27.
blocks in 109.

files

UFD [ 11, 20]
Total of 0./0.

blocks in O.

files

UFD [ 11, 24]
Total of 0./0.

blocks in 0.

files

UFD [ 11, 40]
Total of 0./0.

blocks in O.

files

F-69

DISTRIBUTION KIT CONTENTS

RL01/02 EXCPRV (Cont.)
UFO [12,10]
OV20V.MAC;l
SPSOV.MAC;l
STSUB.MAC;l
SXlOV.MAC;l
SX20V.MAC;l
SX30V.MAC;l
SX40V.MAC;l

52.
62.
16.
42.
52.
18.
40.

Total of 282./282.

blocks in 7.

files

UFO [ 12, 20]
Total of 0./0.

blocks in 0.

files

UFO [12,24]
Total of 0./0.

blocks in O.

files

UFO [12,40]
Total of 0./0.

blocks in O.

files

UFO [200,200]
SGNEXEC.CMO;l
SGNICIS.CMO;l
SGNIP.CMD;l
SGNPER.CMO;l
SGNTT.CMD;l
Total of 475./475.

175.
45.
29.
184.
42.
blocks in 5.

Grand total of 8094./8103.

files

blocks

F-70

228.

files in 14.

directories

DISTRIBUTION KIT CONTENTS

RL01/02 RLUTIL
F.3.3

RLUTIL
UFD [ 1, 20]
ACFBLD.BLD;l
ACOBLD.BLD;l
BADBLD.BLD;l
BRUBLD.BLD;l
CDABLD.BLD;l
CFLBLD.BLD;l
CMPBLD.BLD;l
CRFBLD.BLD;l
DMPBLD.BLD;l
DSCBLD.BLD;l
EDIBLD.BLD; 1
EDTBLD.BLD;l
FLXBLD.BLD;l
FMTBLD.BLD;l
FTBBLD.BLD;l
IOXBLD. BLD; 1
LBRBLD.BLD;l
MACBLD.BLD;l
PATBLD.BLD;l
PIPBLD.BLD;l
RPTBLD.BLD;l
SLPBLD.BLD;l
STKBLD.BLD;l
TKBBLD.BLD;l
VFYBLD.BLD;l
VMRBLD.BLD;l
ZAPBLD.BLD;l
BAD.OLB;l
BRU.OLB;l
CDA.OLB;l
CMP.OLB;l
CRF.OLB;l
DMP.OLB;l
DSC.OLB;l
EDI.OLB;l
EDTLIB. OLB; 1
FLX.OLB;l
FMT.OLB;l
FTB.OLB;l
IOX.OLB;l
LBR.OLB;l
MAC.OLB;l
NEISLB.OLB;l
PAT.OLB;l
PIP.OLB;l
PIPUTL.OLB;l
RPT.OLB;l
SLP.OLB;l
TKB.OLB;l
VFY.OLB;l
VMR.OLB;l
ZAP.OLB;l

Total of 2973./3028.

2.
2.
2.
3.

9.
6.
13.
9*

7.
8.
5.

18.
3.
5.
22.
24.
16.
8.
24.

14.
7.
28.
31.

9.
12.
4.
36.
279.
144.
26.
40.
39.
164.
57.
184.
142.
55.
105.
127.
70.
149.
14.
34.
96.
25.
222.
34.
308.
53.
226.
33.
blocks in 52.

F-71

files

DISTRIBUTION KIT CONTENTS

RL01/02 RLUTIL (Cont.)
UFO [1,24]
ACF.OLB;l

31.

Total of 31./31.

blocks in 1.

file

UFO [1,30]
Total of 0./0.

blocks in 0.

files

UFO [1,34]
Total of 0./0.

blocks in O.

files

UFO [1,50]
Total of 0./0.

blocks in O.

files

UFD [1,51]
BRU64K.STB;l
BRU64K.SYS;l
Total of 272./272.

14.
258.
blocks in 2.

files

UFO [1,54]
Total of 0./0.

blocks in O.

Grand total of 3784./3839.

files
blocks in 61.

F-72

files in 7.

directories

DISTRIBUTION KIT CONTENTS

RL01/02 MCRSRC
F.3.4

MCRSRC
UFO [ 1, l]
38.
66.
253.

RSXMAC ID. MAC; 1
EXEMC.MLB;l
RSXMAC.SML;l
Total of 357./357.

blocks in 3.

files

UFD [11,10]
Total of 0./0.

blocks in O.

files

UFD [12,10]
INDSYS.CLB;l
ABOOV.MAC;l
ACS.MAC;l
ACTFIL.MAC;l
ALLOV.MAC;l
ALLSUB.MAC;l
ALTOV.MAC;l
ASNOV.MAC;l
ATLOV.MAC;l
BOOT.MAC;l
BOOTRC.MAC;l
BOTPH2.MAC;l
BRKOV.MAC;l
BYE.MAC;l
CBTO.MAC;l
CDT2B.MAC;l
CLIOV. MAC; 1
CLQOV.MAC;l
COLOG.MAC;l
COT2B.MAC;l
CRETSK.MAC;l
DEAOV.MAC;l
DEVOV.MAC;l
DFSYM.MAC;l
DISMNT.MAC;l
DV20V.MAC;l
EDCKP.MAC;l
ERMSG.MAC;l
ERRMSG.MAC;l
ERROV.MAC;l
FILBN.MAC;l
FIXOV.MAC;l
FLAOV.MAC;l
FMTDV.MAC;l
FNDUCB.MAC;l
GETNUM.MAC;l

103.
24.
23.
6.
27.
21.
15.
34.
49.
29.
2.
19.
3.
45.

7.
6.
76.
19.
9.
4.
16.
10.
47.

19.
79.
52.
4.
15.
10.
13.
20.
30.
19.
4.
8.
4.

F-73

DISTRIBUTION KIT CONTENTS

RL01/02 MCRSRC (Cont.)
UIC [12,10]
GNBLK.MAC;l
GTBYT.MAC;l
GTMNM.MAC;l
GTTSK.MAC;l
HELLO.MAC;l
ICBDEF.MAC;l
ICPASK.MAC;l
ICPASV. MAC; 1
ICPASl.MAC; 1
ICPAS2.MAC;l
ICPAS3.MAC;l
ICPAS4.MAC;l
ICPAS5.MAC;l
ICPATS.MAC;l
ICPBLK.MAC;l
ICPCHA.MAC;l
ICPCHN.MAC;l
ICPENB.MAC;l
ICPERA.MAC;l
ICPERR.MAC;l
ICPEXF.MAC;l
ICPEXI.MAC;l
ICPFCL.MAC;l
ICPFDC.MAC;l
ICPFEX.MAC;l
ICPFIL.MAC;l
ICPFMI.MAC;l
ICPFMO.MAC;l
ICPFMS.MAC;l
ICPFMX.MAC;l
ICPFOP.MAC;l
ICPFUT.MAC;l
ICPFlO.MAC;l
ICPF52.MAC;l
ICPGNB.MAC;l
ICPGOT.MAC;l
ICPGTK.MAC;l
ICPGTN.MAC;l
ICPIFl. MAC; 1
ICPIF2.MAC;l
ICPIF3.MAC;l
ICPIF4.MAC;1
ICPIMP.MAC;l
ICPINLMAC;l

ICPIN2.MAC;1
ICPIN3.MAC;l
ICPIN4.MAC;1
ICPIN5.MAC;1
ICPMCR.MAC;l
ICPMEM.MAC;l
ICPMEN.MAC;l
ICPNEC.MAC;l
ICPNEI.MAC;l
ICPNEN.MAC;l
ICPNET.MAC;l
ICPNEX.MAC;l

5.
6.
4.
8.
146.
5.
6.
14.
12.
10.
11.
9.
7.
11.
8.
5.
9.
16.
5.
18.
14.

7.
7.
11.
4.
2.
2.
2.
27.
4.
18.
22.

2.
1.
6.

14.
13.
4.

9.
6.
8.
8.
30.
6e
8.
15.
18.
6.
7.
5.
2.
1.
1.

2.
14.
3.

F-74

DISTRIBUTIOR KIT CONTENTS

RL01/02 M·CRSRC {Cont.)
UIC [12.10]
ICPNPR.MAC;l
ICPNPLMAC i 1
ICPONR.MAC;l
ICPPAR.MAC;l
ICPPDW.MAC;l
ICPPOP.MAC;l
ICPPOl.MAC;l
ICPPRC.MAC;l
ICPPRE.MAC;l
ICPPRS.MAC;l
ICPROT.MAC;l
ICPSET.MAC;l
ICPSTP.MAC;l
ICPSUB.MAC;l
ICPSUT.MAC;l
ICPSUl.MAC; 1
ICPSU2.MAC;l
ICPSU3.MAC;l
ICPSU4.MAC;l
ICPSU5.MAC;1
ICPSU6.MAC;l
ICPSYC.MAC;l
ICPSYT.MAC;l
ICPSYl.MAC;l
ICPSY2.MAC;l
ICPSY3.MAC;l
ICPTDV.MAC;l
ICPTESoMAC;l
ICPTPA.MAC;l
ICPVEC.MAC;l
ICPWFT.MAC;l
ICPXMD.MAC;l
INIALL.MAC;l
INIBAD.MAC;l
INIBIT.MAC;l
INIGCL .MAC; 1
INIHOM.MAC; 1
INIMAG.MAC; 1
ININDX .MAC; 1
INIPAR.MAC; 1
INIROT. MAC; 1
INIUPD .MAC; 1
INSBF.MAC;l
INSCM. MAC; 1
INSFL.MAC;l
INSFSR.MAC;l
INSGC.MAC;l
INSHD.MAC;l
INSLB.MAC;l
INSPS.MAC;l
INSROT.MAC;l
IODAT.MAC;l
KEYWD.MAC;l
LDBUF.MAC;l
LDCTL.MAC;l
LDDRV .. MAC;l

1.
5.
24.
15.
14.
11.
8.
13.
29.
6.
28.
6.
3.
28.
5.
20.
19.
18.
8.
4.
5.
14.
25.
26.
8.
12.
19.
11.

7.
2.
10.
4.
23.
55.
35.
69.
23.
42.
38.
119.
64.
41.
6.
10.
17.
2.
2.
30.
72.
26.
19.
7.
5.
6.
27.
26"

F-75

DISTRIBOTION KIT CONTENTS

RL01/02 MCRSRC {Cont.)
UIC [12,10]
LDFIL.MAC;l
LDFIN .MAC; 1
LDLDB.MAC;l
LDUIC.MAC;l
LKLST.MAC;l
LNlOV.MAC;l
LUNOV.MAC;l
MCRDEF.MAC;l
MCRDIS.MAC;l
MCROOT.MAC;l
MCROV.MAC;l
MDPOV.MAC;l
MGCML.MAC;l
MOUCLS.MAC;l
MOUDAT.MAC;l
MOUDIS.MAC;l
MOUDSK.MAC;l
MOUFOR.MAC;l
MOUMSG.MAC;l
MOUPAR.MAC;l
MOUPRE.MAC;l
MOUROT.MAC;l
MOUSUB.MAC;l
MOUTAP.MAC;l
MSGOUT.MAC;l
NETSUB.MAC;l
OPEOV.MAC;l
PAROV.MAC;l
PRlOV.MAC;l
RAPOV.MAC;l
REAOV.MAC;l
REDOV.MAC;l
REQCOT.MAC;l
RPSOV.MAC;l
RUNOV.MAC;l
SAVBOT.MAC;l
SAVCPU.MAC;l
SAVCl.MAC; 1
SA VC 2 • MAC ; 1
SAVC3.MAC;l
SAVDB.MAC;l
SAVDF.MAC;l
SAVDK .. MAC;l
SAVDL.MAC;l
SAVDM.MAC;l
SAVDP.MAC;l
SAVDR.MAC;l
SAVDRT.MAC;l
SAVDS.MAC;l
SAVDT.MAC;l
SAVDO.MAC;l
SAVDX.MAC;l
SAVDY.MAC;l
SAVE.MAC;l
SAVEM.MAC;l
SAVFN.MAC;l

8.
33.
22.
3.

7.
9.
13.
5.
79.
10.
59.
10.
35.
20.
18.
32.
26.
30.
16.
43.
4.
9.

52.
38.
12.
2.
62.
24.
8.
14.
7.
12.
11.
28.
26.
17.
13.
20.
17.
6.
14.
12.
13.
18.
15.
14.
19.
4.
12.
13.
28.
19.
18.
62.
12.
16.

F-76

DISTRIBUTION KIT CONTENTS

RL01/02 MCRSRC (Cont.)
UIC [12,10]

66.
26.
14.
35.
2.
15.
62.
27.
4.
16.
35.

SAVINS.MAC; 1
SAVSIZ.MAC;l
SAVST.MAC;l
SAVSUB.MAC;l
SAVTRC.MAC;l
SMLGCL.MAC;l
SPSOV.MAC;l
SRTOV.MAC;l
SSMOV.MAC;l
STSUB.MAC;l
STlOV.MAC;l
ST20V.MAC;l
ST30V.MAC;l
ST40V.MAC;l
SXlOV.MAC;l
SX20V.MAC;l
SX30V.MAC;l
SX40V.MAC;l
SYMTB.MAC;l
SYSOV.MAC;l
SYSROT.MAC;l
TASOV.MAC;l
TIMOV.MAC;l
TISUBS.MAC;l
TKTN.MAC;l
TPARS2.MAC;l
TPDEB.MAC;l
TPMAC2.MAC;l
TPNUMB.MAC;l
UFD.MAC;l
UFDPAR.MAC;l
UFDPTB.MAC;l
UFDTP.MAC;l
UNLCTL.MAC;l
UNLFIL.MAC;l
WRTMS.MAC;l

41.
41.
29.
42.
52.
18.
40.
14.
23.
10.

36.
26.
4.

49.
44.
5.
32.
8.
23.
16.
7.
6.
29.
6.
6.

Total of 4725./4731.

blocks in 240.

files

UFO [12,20]
FILASM.CMD;l
FILLIBBLD .CMD; 1
ICPASM.CMD;l
ICPLIBBLD .CMD; 1
INIASM.CMD;l
INILIBBLD .CMD; 1
LOAASM.CMD;l
MCRASM.CMD;l
MCRLIBBLD.CMD;l
Total of 41./41.

blocks in 9.

4.
1.
12.

2.
2.
1.

2.
14.
3.
files

F-77

DISTRIBUTION KIT CONTENTS

RL01/02 MCRSRC (Cont.)
ore [12,24]
4.

FILASM.CMD;l
FILLIBBLD.CMD;l
ICPASM.CMD;l
ICPLIBBLD .CMD; 1
INIASM.CMD;l
INILIBBLD .CMD; 1
LOAASM.CMD;l
MCRASM.CMD;l
MCRL IBBLD. CMD; 1

Total of 41./41.

12.
2.
2.
1.

2.
14.
3.

blocks in 9.

files

UFD [12,30]

Total of 0./0.

blocks in O.

files

UFD [12,34]

Total of 0./0.

blocks in O.

files

UFO [12,40]

Total of 0./0.

blocks in O.

files

UFD [14,10]
ATCMD.MAC;l
ATCOM.MAC;l
ATINIT.MAC; 1
ATPAGE.MAC;l
GBCMD.MAC;l
GBCOM.MAC;l
GBINIT.MAC;l
GBLAT-M.MAC;l
GBLCHA.MAC;l
GBLGBM.MAC;l
GBLHLM.MAC;l
GBLIOM.MAC; 1
GBLMDM.MAC;l
GBLSSM.MAC;l
GBLTHM.MAC;l
GBPAGE.MAC;l
HLCOM.MAC;l
HLINIT .MAC; 1
HLPAGE.MAC;l

10.
4.
7.

29.
2.
2.
L

3.
3.
1.
1.

3.
4.
5.
c

".Je

1.
1.

5.
1.

F-78

DISTRIBUTION KIT CONTENTS

RL01/02 MCRSRC {Cont.)
UIC [14,10]
IOCMD.MAC;l
IOCOM.MAC;l
IOINIT.MAC; 1
IOPAGE.MAC;l
L36ATM.MAC;l
L36CHA.MAC;l
L36HLM.MAC;l
L36MDM.MAC;l
L36SSM.MAC;l
L36THM.MAC;l
MDCMD.MAC;l
MDCOM.MAC;l
MDINIT.MAC;l
MDPAGE.MAC;l
NULllS.MAC;l
REMAP.MAC;l
RMDDEF.MAC;l
RMDEMO.MAC;l
RMDMAC.MAC;l
RMDRIV.MAC;l
RMDXCM.MAC;l
SSCMD.MAC;l
SSCOM.MAC;l
SSINIT.MAC; 1
SSPAGE.MAC;l
TERM ID .MAC; 1
THCMD.MAC;l
THCOM.MAC;l
THFllL. MAC; 1
THIN IT. MAC; 1
THPAGE.MAC;l
V05ATM.MAC;l
V05CHA.MAC;l
V05HLM.MAC;l
V05IOM.MAC; 1
V05MDM.MAC;l
VlHATM.MAC;l
VlHCHA.MAC;l
VlHHLM.MAC;l
VlHIOM.MAC; 1
VlHMDM.MAC;l
VlHSSM.MAC;l
VlHTHM.MAC;l
V50ATM.MAC;l
V50CHA.MAC;l
V50HLM.MAC;l
V50IOM.MAC; 1
V50MDM.MAC;l
V50THM.MAC;l
V52ATM.MAC;l
V52CHA.MAC;l
V52HLM.MAC;l
V52IOM.MAC; 1
V52MDM.MAC;l
V52SSM.MAC;l
V52THM.MAC;l
Total of 594./594.

6.
3.
11.
33.

4.
2.

2.
c

.J.

5.
6.
6.

7.
25.
57.
1.
3.

6.
48.

7.
17.

5.
3.
2.

6.
30.

8.
6.

6.
15.
13.
56.

4.
3.
2.
5.
5.

4.
3.
2.

5.
5.
5.

6.
4.
2.
2.
5.
5.

6.
4.
2.

2.
5.
5.

5.
6.
blocks in 75.

files

F-79

DISTRIBUTION KIT CONTENTS

RL01/02 MCRSRC (Cont.)
UIC [14,20]
RMOASM.CMO;l
Total of 8./8.

blocks in 1.

file

UFO [14,24]
RMOASM.CMO;l
Total of 11./11.

11.

blocks in 1.

file

UFO [14,30]
Total of 0./0.

blocks in 0.

files

UFO [14,34]
Total of 0./0.

blocks in 0.

files

UFO [14,40]
Total of 0./0.

blocks in 0.

files

UFO [15,10]
ACNT.MAC;l
BROAO.MAC;l
HELLO.MAC;l
HELROT.MAC;l
HLP.MAC;l
HLPSUB.MAC;l
HSTTAB.MAC;l
SHUFL.MAC;l
SHUTUP.MAC;l
Total of 567./567.

162.
61.
129.
13.
8.
78.
23.
36.
57.
blocks in 9.

files

F-80

DISTRIBOTION KIT CONTENTS

RL01/02 MCRSRC (Cont.)
UIC [15,20]
MLTASM.CMO;l
MLTLIBBLO.CMO;l
SHUTUPASM.CMO;l
Total of 3./3.

blocks in 3.

1.
1.
1.
files

UFO [15,24]
MLTASM.CMO;l
MLTLIBBLO.CMO;l
SHUFLASM.CMO;l
SHUTUPASM.CMO;l
Total of 4./4.

blocks in 4.

1.
1.
1.
1.
files

UFO [15,30]
Total of 0./0.

blocks in 0.

files

UFO [15,34]
Total of 0./0.

blocks in O.

files

UFO [15,40]
Total of 0./0.

blocks in 0.

Grand total of 6351./6357.

files
blocks in 354.

F-81

files in 20.

directories

DISTRIBUTION KIT CONTENTS

RL01/02 HLPDCL
F.3.5

HLPDCL
UFO [1,1]
EXEMC.MLB;l
FCS.OBJ;l
FCSMBF.OBJ;l
EXELIB. OLB; 1
SYS LIB. OLB; 1
RSXMAC.SML;l

Total of 650./650.

66.
24.
32.
45.
230.
253.
blocks in 6.

files

UFO [ 1, 2]
HELP.ULB;l
Total of 2253./2253.

2253.
blocks in 1.

file

UFO [ 1,6]
ERRLOG.ULB;l
ERRLOGETC.ULB;l
Total of 692./692.

622.
70.
blocks in 2.

files

UFO [2,300]
FILEl.;l
FILE2.;l
CMP.CMD;l
CONALL.CMD;l
CONCNT.CMD;l
DMP.CMD;l
DSC.CMD;l
FLX.CMD;l
INSTSK.CMD;l
INTERA.CMD;l
LBR.CMD;l
LOADcCMD;l
MCRTST.CMD;l
PAT.CMD;l
PMD.CMD;l
SIOE.CMD; 1
SLP.CMD;l
SLPCMD.CMD;l
STRTUP.CMD;l
UETP.CMD;l
UNLOAD.CMD;l
UTIL.CMD;l
CRTEST.MAC;l

1.
1.
2.
7.
2.
1.
6.
3.
1.

4.
2.
10.
6.
2.
5.
9.
2.
1.
10.
25.
2.
1.
1.

F-82

DISTRIBUTION KIT CONTENTS

RL01/02 HLPDCL (Cont.)
UIC [2,300]
DEFINE.MAC; 1
DUMMY.MAC;l
LOGGER.MAC;l
MACROl.MAC;l
MACR02.MAC;l
MACR03.MAC;l
NULl.MAC; 1
NUL2.MAC;l
NUL3.MAC;l
OBJCTl.MAC;l
OBJCT2.MAC;l
OBJCT3.MAC;l
PATCHl.MAC; 1
QTRUN.MAC;l
PATCHl. OBJ; 1
DEVM.SAM;l
UETPCOR.TMP;l
ASRC.XXX;l
PATCHD.XXX;l
SLPDAT.XXX;l
SLPOUT.XXX;l
Total of 300./300.

49.
1.
26.
1.
1.
1.
19.
19.
19.
1.
1.
1.
1.
28.
1.
3.
18.
1.
1.
1.
3.
blocks in 440

files

4e
10.
13.
5.
3.
9.
4.
3.
6.
6.
2.
13.
3.
4.
7.
2.
5.
3.
21.
3.
1.
10.
2.
7.
3.
4.
15.

F-83

DISTRIBUTION KIT CONTENTS

RL01/02 HLPDCL (Cont.)
UIC [23,10]
CREATE.MAC;l
CSEP.MAC;l
CUIC.MAC;l
DATE.MAC;l
DBUG.MAC;l
DCL.MAC;l
DCLDAT.MAC;l
DCLMAC.MAC;l
DCLMPL.MAC;l
DEALLO.MAC;l
DEASSIGN.MAC;l
DEBUG.MAC;l
DELETE.MAC;l
DEV.MAC;l
DIFFERENC.MAC;l
DIRECTORY.MAC;l
DISMOUNT.MAC;l
DISPATCH.MAC;l
DQBFE.MAC;l
DQBFS.MAC;l
DSPCMD.MAC;l
EDIT.MAC;l
EDOC.MAC;l
ELEMENT.MAC;l
EOL.MAC;l
ERR.MAC;l
ERRORO.MAC;l
ERRORR.MAC;l
ERRl.MAC; 1
FIL.MAC;l
FIX.MAC;l
FLAGS.MAC;l
FNAM.MAC;l
FORMAT.MAC;l
FORTRAN.MAC;l
FSEP.MAC;l
GTARG.MAC;l
HELP.MAC;l
HOLD.MAC;l
IFIL.MAC;l
INITIAL.MAC; 1
INSTALL.MAC;l
JSR.MAC;l
LAB.MAC;l
LDCCD.MAC;l
LIBRARY. MAC; 1
LINK.MAC; 1
LINKl.MAC; 1
LIT.MAC;l
LOAD.MAC;l
LOGIN .MAC; 1
LOGOUT.MAC;l
LOVR.MAC;l
LUIC.MAC;l
MACRO.MAC;l
MAP.MAC;l

4.
2.
3.

4.
10.
2.
22.

56.
1.

3.
4.
2.
7.
2.

5.
5.
4.
3.
10.
4.

28.
12.

2.
22.

3.
11.

5.
2.
3.

3.
3.
4.
6.
9.
17.
2.
5.
4.
3·.
2.
16.
6.
3.
2.
5.
12.
16.
6.
17.
5.
2.
2.
12.
3.
18.
24.

F-84

DISTRIBUTION KIT CONTENTS

RL01/02 HLPDCL {Cont.)
UIC [23,10]
MATCH.MAC;l
MCR.MAC;l
MOUNT.MAC;l
NEW.MAC;l
NFIL.MAC;l
NFT.MAC;l
NLIT.MAC;l
NOD .. MAC;l
ODEV.MAC;l
OR.MAC;l
OUIC.MAC;l
PARSER.MAC;l
PASCAL.MAC;l
PIP.MAC;l
PREPARSE.MAC;l
PRI.MAC;l
PRINT. MAC; 1
PRO.MAC;l
PROC.MAC;l
PURGE.MAC;l
QIOBF. MAC; 1
QUA.MAC;l
RELEASE.MAC;l
REMOVE.MAC;l
RENAME.MAC;l
REQUEST.MAC;l
RUN.MAC;l
SCTBIT.MAC;l
SEP.MAC;l
SET.MAC;l
SETl.MAC;l
SHOW.MAC;l
SORT.MAC;l
SPAWN.MAC;l
START.MAC;l
STOP.MAC;l
SUBMIT.MAC;l
SY.MAC;l
T.MAC;l
TERM.MAC;l
TI. MAC; 1
TIME.MAC;l
TL INK .MAC; 1
TRANSL.MAC;l
TSET.MAC;l
TSHOW.MAC;l
TST.MAC;l
TYPE.MAC;l
UIC.MAC;l
UND.MAC;l
UNFIX.MAC;l
UNLOCK.MAC;l
VER.MAC;l

7.
2.
14.
4.
3.
3.
3.
2.

2.
6.
2.
7.
7.
7.
14.
2.
11.
9.
2.
3.
8.
7.
3.
2.
3.
2.
7.
7.
2.
15.
21.
21.
10.
5.
9.
8.
9.
3.
2.
2.
3.
2.
10.
5.
20.
16.
5.
3.
2.
5.
3.
3.
2.

F-85

DISTRIBUTION KIT CONTENTS

RL01/02 HLPDCL (Cont.)
UIC [23,10]
WFIL.MAC;l
WUIC.MAC;l
WVER.MAC;l
WXTN.MAC;l
XCOPY.MAC;l
XOCL.MAC;l
XTN.MAC;l

2.
2.
2.
2.

6.
35.
2.

Total of 1002./1002.

blocks in 143.

files

UFO [ 23, 24]
OCL.CMO;l
OCLASM.CMO;l

Total of 26./26.

4.
22.

blocks in 2.

files

UFO [23,34]

Total of 0./0.

blocks in 0.

files

UFO [23,40]

Total of 0./0.

blocks in O.

files

UFO [24,10]
TOX.MAC;l

108.

Total of 108./108.

blocks in 1.

file

UFO [ 24, 20]
TOXASM.CMO;l

Total of 1./1.

blocks in 1.

file

F-86

DISTRIBUTION KIT CONTENTS

RL01/02 HLPDCL (Cont.)
UIC [45,10]
KRATE.B2S;l
KRATE.FTN;l
KAADMP.MAC;l
KAADRV.MAC;l
KAAS03.MAC;l
KADAGR.MAC;l
KADDRV.MAC;l
KADGCH.MAC;l
KADINP. MAC i 1
KADINO .MAC; 1
KAD IN 1 • MAC ; 1
KADIN2.MAC;1
KADIN3.MAC;l
KADIN4.MAC;1
KAD IN 5 • MAC ; 1
KADSWP.MAC;l
KAST.MAC;l
KBFRMG.MAC;l
KBFSTS.MAC;l
KCLOKA.MAC;l
KCLOKB.MAC;l
KCOMM.MAC;l
KCVADF.MAC;l
KDIGO-•MAC; 1
KDIO.MAC; 1
KDISWP.MAC;l
KDOSWP.MAC;l
KDRDRV.MAC;l
KDSCAD.MAC;l
KDSDGO.MAC;l
KDVDF.MAC;l
KEFQA.MAC;l
KFLT16.MAC;l
KGHIST.MAC;l
KIESTO.MAC;l
KKWDRV.MAC;l
KLQSUB.MAC;l
KMUL.MAC;l
KPAA.MAC;l
KPRE.MAC;l
KRCLKB.MAC;l
KRLOC.MAC;l
KRWBF.MAC;l
KSET.MAC;l
KSTADC.MAC;l
KSTB.MAC;l
KST IBF. MAC; 1
KSTOP.MAC;l
KSUB.MAC;l
KSWDF.MAC;l
LABMAC.MAC;l
Total of 473./473.

7.
7.
12.
24.

5.
6.
14.
20.
13.

6.
8.

7.
14.
13.
11.

5.
10.
5.
6.
10.
12.

7.
7.
30.
4.

4.
11.

10.
6.
21.

4.
18.
7.
3.
7.

4.
5.
4.
12.
13.

7.
7.
5.
5.
10.
13.

6.
blocks in 51.

files

F-87

DISTRIBUTION KIT CONTENTS

RL01/02 HLPDCL (Cont.)
UIC [45,20]
ASMK.CMD;l
KCLEAN.CMD;l
KCOMBLD.CMO;l
KLABMLB.CMO;l
KL IBBLO. CMO; 1
KLIBRP .CMO; 1
K4ASM.CMO;l
Total of 7./7.

blocks in 7.

1.
1.
1.
1.
1.
1.
1.

files

UFO [45,24]
ASMK.CMO;l
KCLEAN.CMO;l
KCOMBLO.CMO;l
KLABMLB.CMO;l
KLIBBLO .CMO; 1
KLIBRP .GMO; 1
K4ASM.CMO;l
Total of 7./7.

blocks in 7.

1.
1.
1.
1.
1.
1.
1.

files

UFO [45, 30]
Total of 0./0.

blocks in O.

files

UFO [45,34]
Total of 0./0.

blocks in O.

files

UFO [104,10]
OEVSMl.CNF;l
DEVUDA.CNF;l
DISPATCH.CNF;l
DSPlMl.CNF;l
DSP2Ml. CNF; 1
OSP3Ml.CNF;l
DSP4Ml.CNF;l
DSP5Ml.CNF;l
DSP6Ml~CNF;l

DSP7Ml.CNF;l
EMLll.CNF; 1
ERK05.CNF;l
ERK67.CNF;l

28.
15.
46.
40.
17.
17.
15.
19.
7.
27.
37.
29.
64.

F-88

DISTRIBUTION KIT CONTENTS

RL01/02 HLPDCL (Cont.)
UIC [104,10]
ERL12.CNF;l
ERM05.CNF;l
ERM23.CNF;l
ERM80.CNF;l
ERPO?.CNF;l
ERP23.CNF;l
ERP456.CNF;l
ERRORM.CNF;l
ERSll. CNF; 1
ERS34.CNF;l
ERXO 1. CNF; 1
ERX02.CNF;l
ETAl 1. CNF; 1
ETCll .CNF; 1
ETSll.CNF; 1
ETU58.CNF;l
ETU77.CNF;l
ET0310.CNF;l
ET1645.CNF;l
EUNKWN.CNF;l
Ell XX. CNF; 1
Ell34.CNF; 1
Ell44.CNF;1
Ell60.CNF;1
Ell 7X .CNF; 1
FINLMl .CNF; 1
FMlNMl.CNF;l
FMlWMl.CNF;l
FM2CM1.CNF;l
FM3CM1.CNF;l
FM4NM1.CNF;l
FM4WM1.CNF;l
IN I TMl. CNF; 1
MSCPAT.CNF;l
MSCPBD.CNF;l
MSCPEN.CNF;l
MSCPTO.CNF;l
NMLll.CNF; 1
NRK67.CNF;l
NRM05.CNF;l
NRM23.CNF;l
PARSEM.CNF;l
PARSlM.CNF;l
PARS2M.CNF;l
PARS3M.CNF;l
PRS2AM.CNF;l
PRS2BM.CNF;l
SELTMl.CNF;l
Total of 1732./1732.

40.

49.
49.
48.
46.
31.
51.
20.
24.
36.
21.
28.
16.
19.
57.
26.
38.
26.
38.
15.
30.
38.
38.
36.
40.
4.
7.
7.
5.
7.
27.
28.
9.
25.
82.
81.
45.

6.
4.
5.
5.
38.
29.
7.
13.
33.
32.
12.
blocks in 61.

F-89

files

DISTRIBUTION KIT CONTENTS

RL01/02 HLPDCL (Cont.)
UIC [104,20]
26.
3.

ERRLOGASM.CMD;l
ERRLOGLIB.CMO;l
Total of 29./29.

blocks in 2.

files

UFO [104,30]
Total of 0./0.

blocks in 0.

files

UFO [104,40]
Total of 0./0.

blocks in O.

files

UFO [200,200]
FCSRES.MAC;l
Total of 11./11.

11.

blocks in 1.

Grand total of 7291./7291.

file

blocks in 329.

F-90

files in 20.

directories

DISTRIBUTION KIT CONTENTS

RL01/02 RMSV20
F.3.6

RMSV20

UFO [1,1]
RORMSl.MAC;l
RMSMAC.MLB;l
DAPRLX.ODL;l
DAPllX.ODL;l
RMSRLX .. OOL;l
RMSll. OOL; 1
RMSllS. OOL; 1
RMSllX. OOL; 1
RMS12S.OOL;l
RMS12X.OOL;l
RMSOAP.OLB;l
RMSLIB. OLB; 1
DAPRES.STB;l
RMSRES.STB;l
OAPRES.TSK;l
RMSRES.TSK;l
RMSRESSUB.TSK;l
Total of 801./806.

12.
185.
2.
6.
2.
85.
4.
6.
4.
6.
95.

214.
2.
3.
40.
87.

48.
blocks in 17.

files

UFO [ 1, 2]
RMSOES.HLP;l
Total of 308./308.

308.
blocks in 1.

file

UFO [ 1, 24]
BCKNON.CMO;l
BCKNRN.CMD;l
CNVNON.CMO;l

1.
1.
1.

F-91

DISTRIBUTION KIT CONTENTS

RL01/02 RMSV20 (Cont.)
UIC [1,24]
CNVNOO.CMD;l
CNVNRN.CMD;l
CNVNRR.CMD;l
DAPRES.CMD;l
DEFNON.CMD;l
DEFNRN.CMD;l
DESNON.CMD;l
DESNRN.CMD;l
DSPNON.CMD;l
DSPNRN.CMD;l
IFLNON.CMD;l
IFLNRN.CMD;l
RMSRES .. CMD;l
RSTNON.CMD;l
RSTNRN.CMD;l
BCKNON.ODL;l
BCKNRN.ODL;l
CNVNON.ODL;l
CNVNOO.ODL;l
CNVNRN.ODL;l
CNVNRR.ODL;l
DAPRES.ODL;l
DEFNON.ODL;l
DEFNRN.ODL;l
DESNON.ODL;l
DESNRN.ODL;l
DSPNON.ODL;l
DSPNRN.ODL;l
IFLNON.ODL;l
IFLNRN.ODL;l
RMSDES.ODL;l
RMSODL.ODL;l
RMSRES.ODL;l
RSTNON.ODL;l
RSTNRN.ODL;l
RMSUTL.OLB;l

Total of 888./888.

1.
1.
1.
1.
1.
1.
1.
1.
1.
1.
1.

1.
1.
1.
1.

8.
8.
10.
5.
5.
5.
1.
3.
3.

6.
6.
7.
7.
5.
3.
9.
24.
11.
11.
11.
722.

blocks in 39.

files

UFO [ 1, 34]
DAPRES.MAP;l
RMSRES.MAP;l
RMSRESSUB.MAP;l

Total of 110./110.

16.
59.
35.

blocks in 3.

files

F-92

DISTRIBUTION

~IT

CONTENTS

RL01/02 RMSV20 (Cont.)
UFD [1,54]
RMSBCK.TSK;l
RMSCNV.TSK;l
RMSDEF.TSK;l
RMSDES.TSK;l
RMSDSP.TSK;l
RMSIFL.TSK;l
RMSRST.TSK;l
Total of 1159./1159.

157.
167.
139.
241.
142.
136.
177.
blocks in 7.

files

UIC [200,1]
ERASE.MAC;l
GSA.MAC;l
PARSE.MAC;l
RENAME.MAC;l
SEARCH.MAC;l
ERASE.TSK;l
PARSE.TSK;l
RENAME.TSK;l
SEARCH.TSK;l
Total of 151./151.

8.
18.
9.
10.
8.
25.
22.
26.
25.
blocks in 9.

Grand total of 3417./3422.

files

blocks in 76.

F-93

files in 6.

directories

INDEX

ACP
ANSI magtape, 4-26
definition, 1-4
Address checking, 4=25
Ancillary Control Processor
See also ACP
ANSLIB.OLB, 4-56
linking tasks to, 7-4
rebuilding user-written tasks,
6-7
AST, 4-28
Asynchronous System Traps
See also AST
Autoconfigure, 1-2
adding devices, 4-4
description, 3-16
device support, E-1
failure, 3-17
overriding results, 3-18, 4-3
exception, 3-19
question, 4=3
restrictions, 3-16
sample output, 3-17
supported hardware, 3-19
use, 3-16
with saved answer files, 3-17
Backup and Restore Utility
See also BRU
Baseline system
definition, 1-5
Big disk tape kit
copying
on-1 ine, 2-32
stand-alone, 2-6
Big-buffering support, 4-56
BLDLAINIT.CMD, 3-5
Bootstrap
hardware, 1-5, B-1
mapped baseline system, 4-2
procedure, B-1
software, 1-5
summary of addresses, B-2
virgin system, 6-2
nonstandard unmapped, 6-13
Breakpoint
definition, 3-8
EOS I 3-8
EOX, 3-9
purpose, 3-8
BRU
task build: 6-3
using
backup target system disk,
6-9

BRU
using (Cont.)
recovering disk space, 6-3
BRU64K, 2-4
CNF
altering CSRs using, 2-4
altering vectors using, 2-4
Cancel Selective Marktime
directive, 4-28
CDA
See also Crash dump
Chaining, 4-9
See also Saved answer file
See also Standard Function
System
definition, 3-9
restriction, 3-9
Checkpointing, 4-43
with system checkpoint file,
4-43
CLI
See also DCL
user-written, 4-61
Clock
system, 4-14
watchdog timer, 4-15
Communications products
DECnet, 4-33
SYSGEN support, 4-33
Configuration
See also Autoconf igure
saved host, 4-7
saved peripheral, 4-7
Control and Status Register
See also CSR
Copy
big disk tape kit
on-line, 2-32
stand-alone, 2-6
RA60/80/81, RC25 tape kit
on-line, 2-32
stand-alone, 2-6
RC25 disk kit
on-line, 2-34
stand-alone, 2-9
RK06/07 kit
1600 bpi tape kit
on-line, 2-35
stand-alone, 2-11
800 bpi tape kit
on-line• 2-37
stand-alone, 2-14
disk kit
on-line, 2-39

Index-1

INDEX
Copy
RK06/07 kit
disk kit (Cont.)
stand-alone, 2-17
RLOl/02 kit
1600 bpi tape kit
on-line, 2-41
stand-alone, 2-20
800 bpi tape kit
on-line, 2-43
stand-alone, 2-24
disk kit
on-line, 2-45
stand-alone, 2-28
RM02/03/05/80, RPO? tape kit
on-line, 2-32
stand-a·lone, 2-6
RP04/05/06 tape kit
on-line, 2-32
stand-alone, 2-6
target system disk
mapped, 6-9
unmapped, 6-19
Crash dump
analysis, 4-44
CDA support, 4-44
device, 4-44
PANIC, 4-44
device, 4-45
Crash dump analysis
See also Crash dump
CSR
altering using CNF, 2-4
definition, 1-4
floating, E-3
DBMS-11, 4-22
DCL, 4-60
DECnet
See also Communications
products
SYSGEN support, 4-33
Default response
examples, 3-6
Device
controller
AD, 4-66
AF, 4-66
AR, 4-66
CR, 4-67
CT, 4-67
DB, 4-68
DD, 4-69
DF, 4-69
DK, 4-69
DL, 4-70
DM, 4-70
DP, 4-71
DR, 4-72
DS, 4-73
DT, 4-73
DU~ 4-74
DX, 4-76

Device
controller (Cont.)
DY, 4-76
EM, 4-77
GR, 4-77
LA, 4-78
LP, 4-78
LS, 4-80
MF, 4-81
MM, 4-82
MS, 4-83
MT, 4-83
PP, 4-83
PR, 4-84
UD, 4-84
XB, 4-85
XL, 4-85
XM, 4-86

XP, 4-86
XQ, 4-87
XU, 4-87
xw, 4-88
YH, 4-88
YJ, 4-90
YL, 4-91
YZ, 4-91
example, 4-64
logical, 4-30
pseudo, C-2
specifying, 4-16
specifying parameters, 4-64
support on RSX-llM, 4-16, C-1
DIGITAL Command Language
See also DCL
Directive
Cancel Selective Marktime,
4-28
Get Mapping Context, 4-25
memory management (PLAS) ,
4-24
Send/Receive By Reference,
4-25
system, 4-36
Disk
space recovery, 6-3, 6-14
swapping interval, 4-39
priority, 4-41
writecheck support, 4-31
Distribution kit
definition, 2-1
directory listing
big disk, F-1
RK06/07
CLISRC, F-39
RSXM35, F-29
RlOl/02
EXCPRV, F=65
HLPDCL, F-82
MCRSRC, F-73
RLUTIL, F-71
RMSV20, F-91
RSXM35, F-60
external volume label, 2-2

Index-2

INDEX

Distribution kit (Cont.)
guidelines for copying, 2-3
inventory, 2-2
restriction, 2-2
types, 2-1
Driver
definition, 1-4
loadable, 4-27
default to, 4-28
partition for, 5-10
task-build, 5-9
terminal, 4-46
user-written, 4-3i
DSC
task build, 6-14
using to backup target system
disk, 6-19
Dynamic Storage Region
See also Pool
EAE, 4-13
EIS, 4-14
EOS
breakpoint, 3-8, 4-8
EOX
breakpoint, 3-9, 4-8, 5-6
Err o r 1 og g i ng
device, 4-30
Error message, 8-1
Event flags
group global, 4-35
Executive
commons, 4-24
definition, 1-3
Large (20K), 4-30
routines
$GTWRD, 4-31
$PTWRD, 4-31
source files disk, 4-9
Executive Debugging Tool
See also XDT
Extended arithmetic element
See also EAE
Extended instruction set
See also EIS
FCP
definition, 1-4
option, 4-57
support, 4-22
user-written, 4-59
FCPLRG, 4-58
FCPMDL, 4-58
FCPMIN, 4-5 7
FCPSML, 4-58
FCS
definition, 1-3
PLAS resident library, 4-57
tasks that use, 7-1
FCSRES
linkinn
- - .. ···-··j

r~~k~

---··-

rn_
-- ,

7-~

File Control Services
See also FCS

Files-11 ACP
See also FCP
FIS, 4-13
Floating instruction set
See also FIS
Floating point processor
See also FPll
FORTRAN
See also ISA
FPll, 4-13
Get Mapping Context directive,
4-25

Help
extracting a help file, 6-7,
6-17

library, 6-7, 6-17
HELP.ULB, 6-7, 6-17
HELPBUILD.CMD, 6-8, 6-18
Host system
definition, 1-6
I/O packets
pre-allocated, 4-37
I/O rundown, 4-26
Indirect command file
independent, 3-5
BLDLAINIT.CMD, 3-5
SGNBLDDRV.CMD, 3-5
SGNKLAB.CMD, 3-5
invoking, 3-5
major, 3-5
overview, 3-5
Inhibit MCR
See also MCR
Interrupt
definition, 1-4
ISA
FORTRAN routines, 4-56
industrial/laboratory
libraries, 4-56
K-series
device support, 4-12
KWll-P
as system clock, 4-14
KWll-Y Watchdog timer, 4-15
Layered product
installing, 6-12, 6-19
Line printer
options, 4-78
Map device, 4-21
Mapped
baseline system
bootstrapping, 4-2
system
definition, 1-5
MCR

creating saved answer file,
3-11

Index-3

INDEX
MCR (Cont.)
inhibit execution
Phase I, 4-4
Phase II , 5-4
PREPGEN, 3-11
MCR RUN support, 4-29
Memory
cache, 4-16
management
PLAS directives, 4-24
parity support, 4-15
processor memory size, 4-11
Multiuser
protection, 4-26
system
tailoring, 6-8, 6-18
On-line
definition, 1-6
formatting (FMT), 4-27
Partition
creating with SYSVMR.CMD,
5-14
DRVPAR, 5-10, 5-16
EXCOMl, 5-15
EXCOM2, 5-15
FCPPAR, 5-16
GEN, 5-12, 5-16 to 5-17
specifying a base address,
7-4
PAR14K, 5-18
specifying a base addrress,
5-12
SPLPAR, 5-13, 5-17 to 5-18
specifying a base address,
7-5
SYSPAR, 5-12, 5-16 to 5-18
specifying a base address,
7-5
system-controlled, 4-34
TTPAR, 5-15
Phase I
description, 3-1
example, 4-101
preperation, 4-2
sections, 3-2
Phase II
description, 3-2, 5-1
example, 5-20
input files
RSXllM.OLB, 5-1
RSXBLD.CMD, 5-1
SGNPARM.CMD, 5-1
TTDRVBLD.CMD, 5-1
preperation, 5-2
sections, 3-3, 5-2
Phase III
description, 3-4, 7-1
example, 7-7
preperation, 7-2
PLAS directives
See also Memory management

PMD, 4-59
PMT
See also Pool
Pool
definition, 1-3
description, 4-41
device influence, D-4
monitoring, 4-61
PMT, 4-61
size
calculating, D-1
specifying, 4-41
task influence, D-1
Post Mortem Dump
See also PMD
Power fail
recovery support, 4-29
PRE PG EN, 3-11
See also MCR inhibit
Phase I, 4-4
Phase II , 5-4
Processor
memory size, 4-11
rotating pattern in data
lights, 4-33
valid on RSX-llM, 4-10
with switch register, 4-10
Protection
multiuser, 4-26
PRT print spooler, 4-60
QIO

diagnostic, 4-27
QIO packets
pre-allocated, 4-37
Question
default response, 3-6
examples, 3-6
format, 3-5
logical order, 3-7
Queue manager, 4-35
RA60/80/81, RC25 tape kit
copying
on-line, 2-32
stand-alone, 2-6
RC25 disk kit
copying
on-line, 2-34
stand-alone, 2-9
Record Management Services
See also RMS
Resource Monitoring Display
See also RMD
RK06/07 kit
1600 bpi tape kit
copying
on-line, 2-35
stand-alone, 2-11
800 bpi tape kit
copying
o n-1 in e ~ 2- 3 7
stand-alone, 2-14

Index-4

INDEX
RK06/07 kit (Cont.)
disk kit
copying
on-line, 2-39
stand-alone, 2-17
RLOl/02 kit
1600 bpi tape kit
copying
on-1 ine, 2-41
stand-alone, 2-20
800 bpi tape kit
copying
on-1 ine, 2-43
stand-alone, 2-24
disk kit
copying
o n-1 i ne , 2-4 5
stand-alone, 2-28
RM02/03/05/80, RP07 tape kit
copying
on-1 ine, 2-32
stand-alone, 2-6
RMD, 4-60
RMS
file sharing, 4-23
Installing, 6-10
RMSINSTAL.CMD, 6-10
startup command procedures,
6-11
using VMR to create
partitions, 5-19
RP04/05/06 tape kit
copying
on-line, 2-32
stand-alone, 2-6
RSXllM.OLB
definition, 5-1
RSXeLD.CMD
definition, 5-1
Saved answer file
See also Standard Function
System
aborted, 3-10
creating, 3-10
default name, 4-6
definition, 3-9
input
Phase I, 4-5
Phase II , 5-5
naming conventions, 3-10
output
Phase I, 4-6
Phase II, 5-6
purpose, 3-10
restrictions, 3-10
Scheduling
round-robin interval, 4-38
highest priority, 4-39
lowest priority, 4-39
Section
Phase I
Executive Options, 4-22

Section
Phase I (Cont.)
Host Configuration, 4-20
Peripheral Options, 4-64
Setup, 4-3
System Options, 4-56
Target Configuration, 4-10
Terminal Driver Options,
4-46
Phase II
Executive Task-Build, 5-8
Loadable Driver Task-Build,
5-9
Privileged Task-Build, 5-12
Setup, 5-4
System VMR, 5-14
Send/Receive By Reference
directive, 4-25
SGNBLDDRV.CMD, 3-5
SGNKLAB.CMD, 3-5
SGNPARM.CMD
definition, 5-1
description, 7-2
question, 5-4
SGNSTAND.CMD, 3-11
Shuffler support, 4-34
Software Performance Monitor
See also SPM
Space problems
disk space recovery, 6-3,
6-14
SPM, 4-62
Stand-alone
definition, 1-6
Stand-Alone Configuration and
Disk Sizing Program (CNF)
See also BRU64K
Standard Function System, 1-2
See also Saved answer file
descrition, 3-11
options included, 3-13
purpose, 3-11
question, 4-6
restriction, 3-12
STARTUP.CMD, 6-9, 6-19
RMS procedures, 6-11
Subsystems
IC and IS, 4-92
IP, 4-96
Switch register
question, 4-10
Symbol
saved answer, A-1
SYSGEN
Autoconfigure, 3-16
definition, 3-1
independent command files,
3-5
indirect command files, 3-5
introduction to, 1-1

.minim11m
.·-··-···-·· --'--:1,----···-··--, -1-1_,_
r~n11ir~m~nt-c::_

4-2
operating enviroments, 2-3

Index-5

INDEX
SYSGEN
operating enviroments (Cont.)
on-line, 2-3
stand-alone, 2-3
overview, 1-2
phase, 3-1
Phase I, 4-1
Phase II, 5-1
Phase III, 7-1
planning suggestions, 1-1
PREPGEN, 3-11
See also MCR inhibit
Phase I, 4-4
Phase II, 5-4
question
format, 3-5
logical order, 3-7
Standard Function System,
3-11
terminology, 1-3
System
baseline, 1-5
directives, 4-36
host, 1-6
mapped, 1-5
multiuser setup, 6-8, 6-18
on-line, 1-6
stand-alone, 1-6
target, 1-6
unmapped, 1-5
virgin, 1-6, 6-1
System image
See also SYSVMR.CMD
SYSVMR.CMD
creating partition structure,
5-14
creating RMS partitions, 5-19
description, 3-4
edit, 5-14
on mapped systems, 5-14
on unmapped systems, 5-17
restriction, 3-4
Target system
creating a backup copy, 6-9,
6-19
def i ni ti on, 1-6
installing layered products
in, 6-12, 6-19
saving, 6-2
nonstanard unmapped, 6-13

Target system (Cont.)
test with UETP, 6-5, 6-15
transferring to different
type of disk, 6-6, 6-15
Task
building
description, 6-5
nonprivileged, 7-2
loader
loadable, 4-23
nonresident, 4-23
rebuilding user-written, 6-7,
6-17
termination
See also TKTN
Terminal driver
options, 4-46
TKTN, 4-29
TTDRVBLD.CMD
definition, 5-1
UETP
test target system, 6-5, 6-15
UIC
setting, 4-2
Unmapped system
def ini ti on, 1-5
question, 4-5
Vector
altering using CNF, 2-4
data transfer
size of, 4-37
definition, 1-4
floating, E-3
highest interrupt, 4-16
Virgin system
bootstrap, 6-2
nonstandard unmapped, 6-13
definition, 1-6
VMR
See also SYSVMR.CMD
editing SYSVMR.CMD, 5-14
establishing system features,
6-9, 6-19
invoking from on-line host,
5-19
Write-lock
software support, 4-32
XDT, 4-33

Index-6

RSX-llM System Generation
and Installation Guide
AA-H625C-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? If so, specify the error and the page number.

Please indicate the type of user/reader that you most nearly represent.

D
D
D
D
D
D

Ass"mbly language programmer
Higner-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student programmer
Other (please specify)

Organization
Street
State _ _ _ _ _ _ Zip Code - - - - - or Country

Do Not Tear - Fold Here and Tape

~omoomn

111111

BUSINESS REPLY MAIL
FIRST CLASS PERMIT N0.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

BSSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03061

Do Not Tear - Fold Here

No Postage
Necessary
if Mai led in the
United States