Digital PDFs

AA-H625D-TC

July 1985

329 pages

Original

13MB

Document:	RSX-11M System Generation and Installation Guide Version 4.2
Order Number:	AA-H625D-TC
Revision:	0
Pages:	329
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V4.2_Jul85/AA-H625D-TC_RSX-11M_V4.2_System_Generation_and_Installation_Guide_Jul85.pdf

OCR Text

RSX-11M
System Generation
and Installation Guide
Order No. AA-H625D-TC

RSX-11 M Version 4.2

digital equipment corporation · maynard, massachusetts

First Printing, June
Revised, November
Revised, April
Revised, July

1979
1981
1983
1985

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, 1985 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-IO
DECSYSTEM-20
DEC US
DECwriter

DIBOL
EduSystem
IAS
MASS BUS
MicroPDP-11
Micro/RSTS
Micro/RSX
PDP

PDT
RSTS
RSX
UNIBUS
VAX
VMS
VT

~a~aoma

HOW TO ORDER ADDITIONAL DOCUMENTATION
In Continental USA and Puerto Rico call 800-258-1710

DIRECT MAIL ORDERS (CANADA)

In New Hampshire, Alaska, and Hawaii call 603-884-6660

Digital Equipment of Canada Ltd.
100 Herzberg Road
Kanata, Ontario K2K 2A6
Attn: Direct Order Desk

In Canada call 613-234-7726 (Ottawa-Hull)
800-267-6215 (all other Canadian)
DIRECT MAIL ORDERS (USA & PUERTO RICO)*
Digital Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire 03061

DIRECT MAIL ORDERS (INTERNATIONAL)
Digital Equipment Corporation
PSG 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 (SOC), Digital Equipment
Corporation, Northboro, Massachusetts 01532

ZK2869

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
2.1
2.2
2.2.1
2.2.2
2.2.3

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

PREPARING FOR SYSTEM GENERATION
WHAT IS A DISTRIBUTION KIT?
• . • • • • • • • 2-1
OPERATING ENVIRONMENTS FOR GENERATING RSX-llM
2-3
Stand-Alone System Generation
• • • • • • • • • 2-3
On-Line System Generation on an RSX-llM Host • • 2-3
On-Line System Generation on an RSX-llM-PLUS
Host •

•

• •

•

• 2-4

2.2.4
On-Line System Generation on a VAX-11 RSX Host • 2-4
COPYING THE DISTRIBUTION KIT • • • • • • • •
• 2-4
2.3
2.3.1
Copying Kits Stand-Alone • • • • • • • • •
• 2-4
The BRU64K and BRUSYS Systems
• • • • • • • • 2-5
2.3.1.1
2.3.1.2
Copying a Magnetic Tape Kit Stand-Alone
• 2-6
Copying the RK06 or RK07 Disk Kit Stand-Alone 2-12
2.3.1.3
2.3.1.4
Copying the RL01/RL02 Disk Kit Stand-Alone • 2-15
Copying Kits On-Line • • • • • • • • • • •
2-19
2.3.2
2.3.2.1
Copying the Magnetic Tape Kit On-Line
2-19
Copying the RK06/RK07 Disk Kit On-Line •
2-22
2.3.2.2
2.3.2.3
Copying the RL01/RL02 Disk Kit On-Line •
2-24
2.4
THE UPDATE PROCEDURE •
2-26
2.4.1
The Update Package • • • • • •
2-27
How Update Works • • • • • •
• • • • •
2-27
2.4.2
2.4.2.1
The Update Command Procedure • • • • • •
2-28
Replacement Files • • • • • • • • •
2-28
2.4.2.2
2.4.2.3
Source Correction Files
• • • •
2-28
Preparing for Update • • •
• • • •
2-28
2.4.3
2.4.3.1
Hardware Required for Applying Update
2-29
Applying Update
• • • • • • •
2-29
2.4.4
2.4.4.1
Applying Update Stand-Alone
2-30
Applying Update On-Line
2-32
2.4.4.2
2.4.5
Errors During Update • • • • • •
2-34
Layered Product Files • • • • • • • •
2-35
2.4.6
2.4.6.l
Accessing the Corrections with the Magnetic
Tape Package • • • • • • • • • • • • • • • • 2-35
2.4.6.2
Accessing the Corrections on the RK06/RK07 or
RL01/RL02 Update Package •
• • • • • • 2-36
2.5
NON RSX-llM HOSTS
• • • • • •
• • • • • • 2-36
Update and System Generation on an RSX-llM-PLUS
2.5.1
Host • • • • • • • • • • • • • • •
2-36
Update and System Generation on a VAX/VMS Host 2-37
2.5.2
2.5.2.1
Logging In and Setting Up Privileges
2-37
Answering Questions Requiring Device
2.s.2.2
Specifications • • • • • • • • • • • •
2-37

iii

CONTENTS
CHAPTER 3
3.1
3.1.1
3.1. 2
3.1. 3
3.1.4
3.2
3.2.1
3.3
3.4
3.4.1
3.4.1.1
3.4.1.2
3.4.2
3.5
3.6
3.6.1
3.6.2
3.6.3
3.6.3.1
3.6.3.2
3.6.4
CHAPTER 4
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.8.l
CHAPTER 5
5.1
5.2
5.3
5.4
5.5
5.6
5.6.1
5.6.2

CHAPTER 6

STRUCTURE AND CONCEPTS OF SYSGEN
THE LOGICAL PARTS OF SYSGEN
• • • • •
• • 3-1
Phase I
• • • • •
• 3-1
Phase II •
• • • •
. • • •
3-2
VMR
• • • • • • • • • •
• • • • • • • • • • 3-3
Phase III
• • • •
• • • • • • 3-4
SYSGEN INDIRECT COMMAND FILES
• • • • • • • • • • 3-4
Independent SYSGEN Command Files
• • 3-5
FORMAT OF SYSGEN QUESTIONS • • • • •
• • 3-5
LOGICAL ORDER OF SYSGEN QUESTIONS
• • • • • • 3-7
Breakpoints
• . • •
• • • • • •
• 3-8
EOS Breakpoints
• • • •
• 3-8
EOX Breakpoints
• • • • • • • • • •
• 3-8
Chaining • • . • • • • • •
• • 3-9
SAVED ANSWER FILES • •
• • • 3-9
VARIOUS APPROACHES TO SYSGEN • •
3-10
SYSGEN with MCR Inhibited {PREPGEN)
3-11
The Standard Fune ti on Sys tern • • •
• • • •
3-11
The Autoconf igure Option • • • . . .
3-16
What Autoconf igure Does
• • • • • .
3-16
Overriding Autoconfigure Results •
3-19
Hardware Supported by Autoconf igure
3-20
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 • • .

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

. • • 4-2
• • • 4-3
4-11
• •
4-2 3
• •
4-2 5
• •
4-4 9
• •
4-59
4-67
4-93

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-18
Using VMR to Create Partitions for RMS-11
Libraries
••.••••••• e • • • • •
5-19
POST-SYSTEM-GENERATION GUIDELINES

6.1
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6

DO YOU HAVE AN UNSAVED SYSTEM? • •
••••••
STEPS FOR MAPPED TARGET SYSTEMS
• • •
How to Bootstrap the Unsaved System
•
How to Make Your Target System Hardware-Bootable
Invoke Phase III to Task Build BRU • • • • • • •
How to Recover Space on the Target System Disk •
Building or Rebuilding RSX-llM Tasks . • • • • •
How to Transfer the Target System to a Different
Type of Disk • • • • • • • • • • • • •
. •
Rebuilding user-Written Tasks
• • • •
• ••
6.2.7
6.2.8
Help Files • • • • • • • • • • • • • • • • •
Files for the Introduction to RSX-llM
•
6.2.8.1
6.2.9
Multiuser System Setup
••••••••••
iv

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

6-5
6-6
6-6
6-8
6-8

CONTENTS
6.2.10
6.2.11

Establishing System Features with VMR • • . • . 6-9
How to Create a Backup Copy of the Target System
Disk • • • • • • • • • • • • • •
6-9
Installing RMS-11 V2.0 • • • • • • • • •
6.2.12
• • 6-9
6.2.12.1
RK06 and RL01/RL02 Procedures
6-10
Startup Command Procedures •
6.2.12.2
6-11
6.2.13
Error Logging Support • • • •
6-11
6.2.14
Installing Layered Products in the Target
System . • • • • • • • • . • •
• • • • • • 6-12
6.3
STEPS FOR UNMAPPED SYSTEMS • • .
• • • •
6-12
6.3.1
Building or Rebuilding RSX-llM Tasks
6-12
How to Bootstrap the Unsaved System
6.3.2
6-12
6.3.3
How to Make Your Target System
Hardware-Bootable
• • • • • • • •
6-13
6.3.4
Invoke Phase III to Task Build DSC •
• • 6-13
How to Recover Space on the Target System Disk 6-14
6.3.5
6.3.6
How to Transfer the Target System to a
6-15
Different Type of Disk • • • • • • • • • •
6.3.7
Rebuilding User-Written Tasks
•••••
6-16
Help Files • • • • • • • • • • • • • • •
6-16
6.3.8
6.3.8.1
Files for the Introduction to RSX-llM
6·-18
Multiuser System Setup • • . . • • • • • •
6-18
6.3.9
Establishing System Features with VMR
6.3.9.1
6-19
How to Create a Backup Copy of the Target
6.3.9.2
System Disk
• • • • • •
• ••••
6-19
Installing Layered Products in the Target
6.3.9.3
System • • • • • • • • • • . •
• • • • • 6-19
CHAPTER 7
7.1
7.2

DETAILS OF SYSGEN PHASE III
PREPARING FOR PHASE III
PHASE III QUESTIONS

CHAPTER 8

SYSGEN ERROR MESSAGES

APPENDIX A

SAVED ANSWER SYMBOLS

APPENDIX B

HARDWARE BOOTSTRAP PROCEDURES

• 7-2
• 7-2

•
GENERAL BOOTSTRAPPING PROCEDURE
B.l
B.2
MRll-DB PROCEDURE • • • • • • •
•
M9301-YA AND M9301-YB PROCEDURE
B.3
B.4
M9301-YC PROCEDURE •
M9301-YF PROCEDURE • • • • • • •
B.5
B.6
M9312 PROCEDURE • • • • • • • •
.
Using the M9312 Console Emulator •
B.6.1
B.6.1.1
Push-Button Boot Using the M9312 Console
Emulator • • • • • •
B.6.1.2
Switch Register Boot Using the M9312 Console
Emu la tor • • • • •
• • • • • •
B.7
BOOTSTRAP LOAD PROGRAM FOR THE RLOl/02 AND RK07
B.8
BOOTSTRAP LOAD PROGRAM FOR THE TUlO, TElO, OR
TS 0 3 • • • • • • • • •
• • • • • •
APPENDIX C

RSX-llM DEVICES

APPENDIX D

FUNCTIONS IMPACTING POOL (DYNAMIC MEMORY)

D.l
D.2

COMMON FUNCTIONS • • •
REAL-TIME FUNCTIONS
v

•
•
•
•
•
•
•

B-1
B-3
B-3
B-4
B-5
B-5
B-6

• B-6
• B-6
• B-8
B-10

• D-1
• • D-5

CONTENTS
APPENDIX E
E.l
E.2
E.3
E.3.1
E.3.2
APPENDIX F

ADDRESS AND VECTOR ASSIGNMENTS
AUTOCONFIGURE DEVICE SUPPORT • • • • •
FLOATING ADDRESS ASSIGNMENT ALGORITHM
FLOATING ADDRESS WORKSHEET •
worksheet Format • • •
worksheet Instructions • • • • • • •

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

• • •
•
• •
• •

F-1
F-2
F-6
F-9
F-12
F-14
F-22
F-28

DIRECTORY LISTINGS

F.1.2
F .1.3
F. l . 4
F .1. 5
F. l . 6
F .1. 7

DISK DISTRIBUTION KIT VOLUME CONTENTS
RSXM38
EXCPRV
PRVBLD
RLUTIL
• • • •
MC RS RC
• • • • • • • •
HLPDCL
• • •
RMSV20

3-1
3-2

Sample Autoconf igure Output
Autoconf igure Remarks and Meanings

4-1

Annotated Terminal Output from SYS GEN
Phase I

F.l
F .1.1

•
• • •
• • •
•

• •
• •
• •

EXAMPLES

5-1

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

3-18
. . . . . . . . . . 3-19

. . . . . . . . . . . . . . . . . . . . 4-98
Annotated Terminal Output from SYS GEN
Phase II . . . . . . . . . . . . . . . . . . . . 5-20

Annotated Terminal Output from SYSGEN
Phase III
••••••••••••
Floating Address Worksheet (Configuration 1).
Floating Address Worksheet(Configuration 2). • •
Blank Floating Address Worksheet • • • •
• •

• 7-6
• E-6
• E-7
• E-8

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

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 II
• • • •
Partition Structure on Mapped Systems
Partition Structure on Unmapped 16K
through 24K Systems • • • • • • • •
Partition Structure on Unmapped 24K
through 28K Systems
• • • • • • • •

• • 5-3
5-15
5-17
5-18

7-1

Logical Flow of SYSGEN Phase III • • • • • • • • • 7-1

2-1

Inventory of the RSX-llM Distribution Kits • • • • 2-2

3-1
3-2

Phase I Sections and Functions •
Phase II Sections and Functions

TABLES

• 3-2
• • • • 3-3

CONTENTS
3-3
3-4
4-1
4-2
4-3
A-1

Options Included in the Standard Function
System • • • • • • • • • • • • • • • • • •
3-12
Hardware Supported by Autoconf igure • • • • • • • 3-21
PDP-11 Processor Memory Sizes for
RSX-llM/RSX-llS
• • • • • • • • • • • • • • • • 4-12
Peripheral Devices Supported by RSX-llM • • • • • 4-19
Standard Line Printer Devices • • • • • • • • • • 4-81
Definition of Saved Answer Symbols • • •
• • • A-2

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

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-6
RLOl/02 and RK07 Load Routines •
• • • •
• B-9

C-1

RSX-llM Devices

E-1

Autoconf iguration Device Support • • • • • • • • • E-2

B-1
B-2

• C-1

vii

PREFACE

MANUAL OBJECTIVES
The RSX-llM System Generation and Installation Guide provides you with
the information necessary tO--generate an RSX-llM operating system.
Included in this manual are descriptions of the interactive system
generation procedure called 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 intended for the system manager who is responsible for
generating and maintaining an RSX-llM operating system. Most of the
information in this manual requires familiarity with an RSX-llM
operating system and its component tasks.

STRUCTURE OF THIS MANUAL
Chapter 1 introduces the RSX-llM system
process.

generation

and

installation

Chapter 2 describes the RSX-llM distribution
media,
including
step-by-step instructions for copying the media in your distribution
kit to your target system disk.
The chapter also includes an
introduction to the various operating environments that can serve as a
host to RSX-llM system generation. Finally, the chapter describes the
procedures you use to apply an Update package to your RSX-llM
operating system.
Chapter 3 discusses 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.
It contains information
that is vital to performing a successful system generation.
Read it
carefully before you begin your system generation.
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 that you should follow once
you have generated your system.
Chapter 7 explains each of the questions in SYSGEN Phase III.
Chapter 8 explains the various system
generated during system generation.

error

messages

that

may

PREFACE
Appendix A defines the saved answer symbols that SYSGEN creates
on your responses to questions.

based

Appendix B provides information for hardware bootstrapping your PDP-11
processor.
Appendix C lists
controllers.

devices

and

associated

device

mnemonics

and

Appendix D lists the tasks and system functions that impact the
dynamic storage region (DSR), which is also called the "system pool."
Appendix E contains detailed information on floating control and
status register
(CSR)
and vector addresses, and defines the DIGITAL
standard hardware configuration algorithm.
Appendix F lists the
distribution kits.

directory

contents

each

volume

the

The following documents provide more detailed descriptions of some
the system components that are discussed in this manual:

ASSOCIATED DOCUMENTS

RSX-llM/M-PLUS
RSX-llM/M-PLUS
RSX-llM/M-PLUS
RSX-llM/M-PLUS
RSX-llM/M-PLUS

System Management Guide
and Micro/RSX Executive Reference Manual
MCR Operations Manual
and Micro/RSX I/O Drivers Reference Manual
and Micro/RSX Task Builder Manual

CONVENTIONS
This manual uses the following conventions:
Convention

Meaning
A symbol indicating that the CTRL key must be held down
while another key is pressed. For example,
(CTRL/ZJ
means
that you hold down the CTRL key while pressing z.

xxx

A 1- to 3-character key symbol.
For example,
~
indicates the RETURN key,
(kB
indicates the LINE FEED
key, and @
indicates the ESC key.

MCR>

The explicit Monitor Console Routine (MCR) prompt. MCR is
one
of two RSX-llM command line interpreters.
The
ex_amples in this manual show MCR commands only.

The implicit prompt that the system displays to indicate
that it is ready to accept input from a terminal.

A reverse number
(a white number printed in a black
circle) which is used to key a specific part of an example
to a numbered list that follows the example.
The
corresponding reverse number in the list explains that
part of the example.

Red Ink

T.he color of ink used to
examples.

show

user-entered

commands

SUMMARY OF TECHNICAL CHANGES

The RSX-llM System Generation and Installation Guide has been revised
to
reflect the following additions and changes to the system
generation procedure for RSX-llM Version 4.2:
•

The distribution kits that contain the files for generating
the new system image have undergone several changes:
For stand-alone system generations, the default CSR address
that the Stand-Alone Configuration and Disk Sizing Program
(CNF) expects for MT:-type devices has been changed. Also,
for the TKSO distribution kit
(which includes BRUSYS),
default values have been added for MU:-type devices.
The RLOl and RL02 distribution kits have been changed. The
RLOl kit now consists of seven disks rather than six. The
EXCPRV backup set has been split into two sets, EXCPRV and
PRVBLD.
EXCPRV contains the files for assembling the
Executive, device drivers, and some MCR modules during
Phase I of SYSGEN. PRVBLD contains the files for building
the Executive, device drivers, libraries, and privileged
tasks during Phase II of SYSGEN.
The RL02 distribution kit contains only five disks because
the PRVBLD and RLUTIL backup sets are on the disk labeled
PRVBLD, and the MCRSRC and HLPDCL backup sets are on the
disk labeled MCRSRC.
A new distribution kit is available with this version of
the operating system.
The new kit consists of two TKSO
magnetic tape cartridges that are driven by a
TKSO
streaming tape drive.
One tape contains the new system
files; the second tape contains BRUSYS, which is an RSX-118
system dedicated to stand-alone copying of the distribution
kit.
The procedure for copying the baseline system from magnetic
tape distribution kits to disk has been simplified. The
baseline system now includes an Indirect command procedure
named TAPEKIT.CMD that guides you through the copying
process.

•

The RSX-llM operating system now supports
features:

the

following

new

Asynchronous Terminal Interfaces: The YV drive for the
DHVll and DHUll multiplexers.
The DHVll is a Q-BUS
multiplexer that handles eight lines at speeds up to 19.2K
baud with full modem control.
The DHUll is the UNIBUS
equivalent of the DHVll.
It handles up to 16 lines with
full modem control.
You must select the full-duplex
terminal driver during SYSGEN if you want support for the
DHVll or DHUll.
Also, RSX-llM now supports the YZ drive
for the DZQll Q-BUS multiplexer.

SUMMARY OF TECHNICAL CHANGES
Terminal Characteristics: RSX-llM now supports additional
terminal characteristics if you select support for the
full-duplex terminal driver in the Terminal Driver Options
Section of Phase I of SYSGEN. The additional terminal
characteristics include parity generation and checking,
advanced video and editing options, ANSI-standard and
DIGITAL-specific escape sequences, ReGIS graphics, and
block-mode transmission.
Network Communications Driver: The DEUNA driver for the XE
UNIBUS Ethernet communications device.
DU devices:
RD52 fixed-media disks
RD53 fixed-media disks

MU devices:
TKSO magnetic tape cartridge
MU:-type devices as Crash Dump
devices

Analyzer

memory

dump

Controllers:
RUXSO UNIBUS controller for the RXSO disk drive
KDASO-Q controller for RA60 and RA80/RA81 disk drives
RQDX2 and RQDX3 controllers for RD and RX disk drives
Q-BUS controller for the TKSO cartridge tape drive

Printers:
LN03
LQP02
LQP03
LAlOO
LA210

Terminals:
VT200 series

Processors: The Jll-series of processors,
of the following processors:

which

consists

LSI-11/73
MicroPDP-11/23
MicroPDP-11/73
MicroPDP-11/83
PDP~ll/84

Note that, due to hardware restrictions, RSX-llM may not
work properly with most configurations built around the
LSI-11/73 processor module.
•

SYSGEN no longer supports
Package

UETP,

•

SYSGEN no longer automatically supports the IPll Industrial
Control Subsystem.
The IPll is now a layered product with its
own installation process; you can select support for it in the
System Options Section of Phase I of SYSGEN

xii

the

User

Environment

Test

SUMMARY OF TECHNICAL CHANGES

•

Several questions have been modified or added
dialogue:

the

SYSGEN

In the Setup Sections of Phases I and II, if you are using
an RLOl or RL02 distribution kit and doing a PREPGEN,
SYSGEN asks where you want the assembly and task-build
files to be located.
You can select the default user
device or the null device;
this saves space on the
distribution disks.
If you have an RLOl or RL02 distribution kit and you are
chaining from Phase I to Phase II, in the Setup Section of
Phase I SYSGEN asks you to specify the device on which the
PRVBLD disk will be mounted.
If you are not chaining from
Phase I to Phase II, SYSGEN asks you to specify the device
in the Setup Section of Phase II.
In the Executive Options Section of Phase I, if you select
support for DECnet-llM, SYSGEN asks if you want to include
support
Network Command Terminal
{NCT)
support.
NCT
enhances the full-duplex terminal driver by adding support
for modem hangup and out-of-band character ASTs, switch
characters, and extended I/O.
In the System Options Section of Phase I, SYSGEN asks if
you want to include support for the IPll Industrial Control
Subsystem. The IPll is a combined software and hardware
subsystem that controls and monitors industrial processes.
If you do select support for the IPll, SYSGEN then asks if
you also want IPll power-fail support.
In the Peripheral Options Section of Phase I, the prompt
for
DU:-type
devices has been changed.
Instead of
specifying a drive, you now specify the interrupt vector
address, the CSR address, and the number of disk drives for
each DU controller.
•

The following documentation has been added to this manual:
The installation procedure for applying software updates to
the operating system.
The instructions for
generation on a VAX
compatibility mode.

•

performing
an
RSX-llM
system
host computer running in VAX-11 RSX

The following errors occurred in the previous version {Version
4.1) of this manual and have been corrected in this version:
The references to an RC25 Disk Kit and to an RC25-specific
Big Disk Magnetic Tape Kit were incorrect. Support for
system generations targeted to RC25 system disks
is
provided in the magnetic tape distribution kit.
The reference to an RP07 Big Disk Magnetic Tape Kit was
incorrect.
RSX-llM does not support a system generation
targeted to an RP07 disk.
The reference to Record Management Services
{RMS)
in
Question 3 of the Executive Options Section of SYSGEN Phase
I was incorrect and has been removed.
The Files-11 ACP
{FCP)
supports file sharing and placement control, so
SYSGEN asks this question if your system includes the FCP,
regardless of whether your system also includes RMS.

xiii

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 tailored specifically 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 users with
sufficient understanding of the operating system to make the necessary
judgments.

1.2

SYSTEM GENERATION MINIMUM REQUIREMENTS

In order for you to perform an RSX-llM Version 4.2 SYSGEN,
system has to conform to two SYSGEN minimum requirements:

1.3

your

•

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

host

•

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

host
system

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, and 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 Chapte~ 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 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
You may find it
needs.
Experiment with it to see how it performs.
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 Version 4.2 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

Autoconfigure

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/RSX-llS 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, multiuser protection, and
intertask communications.
In general, the Executive monitors,
controls, and services system-level activity.
It provides a
relatively machine-independent environment in which to devel6p
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 instead of the task
issuing 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), whereas 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,
which includes the directory structure, storage allocation and
deallocation, and file security.
driver
A driver is a set of routines called by 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/O 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 Q-BUS).
When addressing a device, you are
actually addressing a set of registers that communicate with the
device.
One of the registers is called the Control and Status
Register (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 PSW (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 PSW and PC on a stack and loads the PSW 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 example, execution of the
TRAP instruction causes an interrupt where a new PSW 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 bootblack 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 BOOT
command.
(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 locationsc 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.
You
bootstrap the baseline system from the distribution kit into the
memory of your host computer. The baseline system then dedicates
the host computer's resources to the system generation process.

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.
That is, you
bootstrap the baseline system from the distribution kit into your
host computer's memory, thereby dedicating the host computer to
your use alone while you perform the system generation.
unsaved system
The term unsaved 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 unsaved system should be bootstrapped
only on the target system for which it was configured during the
system generation process.

1-6

CHAPTER 2
PREPARING FOR SYSTEM GENERATION

This chapter tells you how to prepare for
the system generation
procedure.
It begins with a description of the various RSX-llM
distribution kits and then it lists step-by-step instructions for
copying the distribution kits.
Next, the chapter briefly discusses
the host environments you can use to generate your RSX-llM Version 4.2
operating system.
Finally, the chapter concludes with a description
of the procedures for updating your system.

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:
•

Magnetic tape kits (800 or 1600 bpi)

•

TK50 magnetic tape cartridge kits

•

RK06 and RK07 disk kits

RLOl and RL02 disk kits

The RK06/RK07 and RL01/RL02 distribution kits are
All other
either magnetic tape or disk media.
distributed on magnetic tape only.

distributed on
disk kits are

Table 2-1 lists an inventory of RSX-llM distribution kits.
Each
distribution kit contains either magnetic tapes or disks, depending on
the type of kit ordered. The table shows the number of magnetic tape
or disk volumes that each kit consists of.
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 (located on the tape or disk labeled RSXM38) on
each kit in directory [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

PREPARING FOR SYSTEM GENERATION
Table 2-1
Inventory of the RSX-llM Distribution Kits
Kit 'rype

Number
of Disks

Magnetic Tape

TKSO

Tape
Length
(ft)

Tape
Density
( bpi)

2400

1600

2400

800

Number of
Tapesl

6667

RLOl Disk

RL02 Disk

RK06 Disk

RK07 Disk

1.
Each tape distribution kit includes
contains a stand-alone BRU system.
Each volume in your distribution
identifies the following:

kit

bears

an
a

additional

tape

that

physical

label

that

•

The specific software version number
Version 4.2)

(such as RSX-llM

•

The type of distribution kit (such as RLl or RL2)
NOTE
Because of character string limitations
on
the
physical tape label,
the type of distribution kit
specified on the label omits zeros.
For example, the
RLOl
and
RL02
kits are labeled RLl and RL2,
respectively.

•

The volume ID (such as RSXM38)

•

The number in the sequence (such as 1/2--the first disk
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 Version 4.2
distribution kits.

2-2

PREPARING FOR SYSTEM GENERATION

0
AM-D519D-BC
RSX11 M V4.2 ID:RSXM38 RK6 1/2

Dig1!ol Equipment Corporol1on

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.)
You can generate your system on a stand-alone host computer, or on an
on-line host computer.
If you use an on-line host computer, it can be
running under the control of an RSX-llM or RSX-llM-PLUS operating
system, or it can be a VAX computer running
in
VAX-11
RSX
compatibility mode.

2.2.1

Stand-Alone System Generation

You can generate your system by using an RSX-llM Version 4.2 baseline
system.
Generating an RSX-llM system from the baseline system is
called stand-alone system generation, because the baseline system
dedicates the host computer's resources to the system generation
procedure alone.
The baseline system consists of the software
components
necessary for system generation.
Stand-alone system
generation requires that you hardware bootstrap the baseline disk
(RSXM38) 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 on an RSX-llM Host

You can generate your system by using a host computer that is
currently running an RSX-llM Version 4.1 system, or a Version 4.2
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

PREPARING FOR SYSTEM GENERATION
2.2.3

On-Line System Generation on an RSX-llM-PLUS Host

You can generate your system by using a host computer that is
currently running an RSX-llM-PLUS Version 2.1 system, or a Version 3.0
system other than the baseline system.
This procedure requires
certain
privileges and conditions before you begin the system
generation. Refer to Section 2.5.1 for instructions on performing a
system generation on an RSX-llM-PLUS host.

2.2.4

On-Line System Generation on a VAX-11 RSX Host

You can generate your system by using a VAX/VMS host computer that is
currently running in VAX-11 RSX compatibility mode {VAX-11 RSX Version
1.0, or Version 2.0). This procedure requires certain privileges and
conditions before you begin the system generation. Refer to Section
2.5.2 for instructions on performing a system generation on a VAX-11
RSX host.

2.3

COPYING THE DISTRIBUTION KIT

Before you use your distribution kit to generate an RSX-llM system,
make a copy of the kit.
In this way, the original distribution kit
serves as a backup in case the copy is corrupted during the system
generation process.
Also,
the distribution kit serves as base
software against which you can apply subsequent Updates.
{If you need
to apply an Update to your system, you should do it before invoking
SYSGEN Phase I.)
If you have a magnetic tape distribution kit, you must copy the
contents of the kit to a blank disk.
After you have copied the kit to
the disk, the disk becomes your target system disk.
Since you must copy a magnetic tape distribution kit to a disk before
you invoke SYSGEN, the distribution tape can then serve as your
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.l tells you how to copy any of
the distribution kits stand-alone using the BRU64K, BRUSYS
{for the
TK50 cartridge tape), 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.
Go to 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, BRUSYS, and baseline stand-alone
systems.

2-4

PREPARING FOR SYSTEM GENERATION
2.3.1.1 The BRU64K and BRUSYS Systems - Each
distribution
kit
contains a BRU system.
Each tape distribution kit, except for the
TK50, includes a 600-foot tape that is labeled BRU64K. The TK50 tape
kit includes a second TK50 cartridge that is labeleG BRUSYS.
Each
disk distribution kit contains the files BRU64K.SYS and BRUSYS.SYS in
directory
[1,51].
This directory is located on the RSXM38 volume of
the RK06/RK07 kit, the RLUTIL volume of the RLOl kit, and the PRVBLD
volume of the RL02 kit.

The BRU64K and BRUSYS systems are limited-feature, memory-resident
RSX-118 systems.
You use them to prepare the target system disk and
then to copy the baseline system from the magnetic tape distribution
kit to the disk.
After you copy the tape to the disk, you use the
baseline system on the disk as the operating environment for a
stand-alone system generation.
Included with the BRU64K
following utilities:

and

BRUSYS

systems

•

Backup and Restore Utility (BRO)

•

Bad Block Locator Utility (BAD)

are

copies

the

NOTE
Since BRO and BAD share the same buffer space, the two
utilities 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 lets you change the default values for the device control
and status register
(CSR) address (/CSR=nnnnnn) , and for the device
vector (/VEC=nnn).
For MM:-type devices, you can also change the
default formatter number
(which is 0), by using the /FOR=n switch.
Unless you specify other values, the BRU systems assume the default
CSR and vector address values for your devices.
The following list
shows the default addresses for device types:
Device

CSR

Vector

CSR Status

DB
DK
DL
OM
DP
DR
DU
MM FOR=O
MS
MT

176700
177404
177440
177440
176714
176300
1 72150
172440
172522
160000

254
220
160
210
300
150
154
330
224
320

Present
Present
Not Present
Present
Present
Present
Not Present
Present
Not Present
Not Present

Additionally, BRUSYS expects
devices:

the

Device

CSR

Vector

174500

260

following

CSR Status

Present

2-5

addresses

for

MU:-type

PREPARING FOR SYSTEM GENERATION
If your devices are at different CSR and vector addresses or if your
MM:-type magnetic tape drive device is on a different formatter
number, you must change the values in BRU64K or BRUSYS.
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 and BRUSYS expect for DR:-, MS:-, and
MT:-type devices are nonstandard.
The CSR address that the BRU
systems expect for DR:-type devices 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 or BRUSYS 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=l 76700/VEC=254 (BD)
MS: /VEC=224 (BD)
MT: /VEC=2 2 4 (BD)
To begin copying your distribution kit, you must hardware bootstrap
the BRU64K or BRUSYS stand-alone system on your host computer. The
procedure for hardware bootstrapping the BRU systems depends on the
bootstrap
hardware present on the host computer.
(Appendix B
describes hardware bootstrap procedures.)
Following are the procedures
stand-alone host system.

for

copying

If you have a magnetic tape distribution
next.

distribution

kit,

read

kits

Section

2.3.1.2

If you have an RK06
2. 3.1. 3 next.

RK07

disk

distribution

kit,

read

Section

If you have an RLOl
2.3.1.4 next.

RL02

disk

distribution

kit,

read

Section

2.3.1.2 Copying a Magnetic Tape Kit Stand-Alone - Use the following
procedure to copy the 800 bpi or 1600 bpi magnetic tape kits or the
6667 bpi TK50 cartridge tape kit 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 to seven blank disks to copy the distribution kit,
depending on the type of distribution kit that you have. The first
disk will be your system disk after your system generation is
complete.
Place a physical label on the disk so that the blank disk
represents the backup set name in the distribution kit (RSXM38).
To copy your distribution tape(s) to disk
system, perform the following steps:
1.

using

stand-alone

host

Load the BRU64K tape on the appropriate tape drive.
(If you
have the TK50 tape kit, you will be using BRUSYS instead of
BRU64K, so mount the tape labeled BRUSYS.)
Next, load the
blank disk, which you have previously labeled RSXM38, in the

2-6

PREPARING FOR SYSTEM GENERATION
appropriate disk drive and spin up the disk.
If your medium
(all
is
an
RA80/RA81,
RC25, RD52/RD53 or RM80 disk
fixed-media disks), the fixed-media disk serves as the blank
disk.
2.

Hardware bootstrap the BRU64K or BRUSYS tape.
(Refer to
Appendix B for the hardware bootstrap procedures.)
The
RSX-115 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 Version 4.2 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 the default CSR or vector
addresses that BRU64K or BRUSYS expects, you must modify the
software to incorporate the correct addresses before you can
complete this step.
If you want 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 or BRUSYS expects, or if your MM:-type
magnetic tape drive is on a formatter number other than zero,
you must change the values in BRU. Do this by using the
following CNF switches when you enter the device name:
/CSR=csr address
/VEC=vector address
/FOR=f ormatter number
The vector addresses that BRU64K and BRUSYS expect for DR:-,
MS:-,
and MT:-type devices are nonstandard. The CSR address
that BRU 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 BRO 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~

2-7

PREPARING FOR SYSTEM GENERATION
4.

Press RETURN, then enter the date and time using the TIME
command.
Use the TIME 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/85 (8ITJ
>TIM (8ITJ
14:32:01 25-MAY-85

>
5.

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

BAD> DRO:/LIST (8ITJ
BAD -- ORO: Total bad blocks= O.
BAD> (CTRL/z)

>
The BAD /LIST
located.

switch

lists

any

bad

blocks

they

are

Repeat this step for each of the blank
copying the distribution kit to.

disks

that

you

are

Remove the BRU64K tape or the BRUSYS cartridge from the drive
and mount the distribution kit tape labeled RSXM38 on the
tape drive previously entered to CNF.

You are now ready to copy the files from the distribution
tape to the disk.
To do so, run the Backup and Restore
Utility (BRU), using the following command line:
>RUN BRU (5fl)
BRU>/REW/INI/DEN:density/BAC:narne mmn: ddn: (8ITJ
The switches and parameters in the BRU command line have
following functions:

the

The /REW (rewind)
switch ensures that the
completely rewound before BRU begins to copy.

The /IN! (initialize) switch initializes the disk volume
to which BRU is copying.
(Be aware that if there are any
files on the disk, they will be deleted.)

The /DEN (density) switch specifies the density at
the tape was written.

2-8

tape

which

PREPARING FOR SYSTEM GENERATION
the target system disk, depending
Each type
you are copying to.
you use with the /BAC switch
following list shows the name for

on which type of disk
of disk has a name that
The
to identify it.
each type of disk:

Disk Type

Name

RP04/RP05/RP06

DBSYS

RL01/RL02

DLSYS

RK06/RK07

DMSYS

RM02/RM03/RM05/RM80

DRSYS

RA60/RA80/RA81/RC25/RD52/RD53

DU SYS

The mmn:
specification identifies the
unit that you are copying from.

tape

device

and

The ddn:
specification identifies the
unit that you are copying to.

disk

device

and

For example,
to begin copying the tape labeled RSXM38
(mounted on device MMO:) to an RK06 disk, issue the following
command:
BRU>/REW/INI/DENS:800/BAC:DMSYS MM: DMl: IBTIJ
BRU - Starting Tape 1 on MMO:
BRU - End of Tape 1 on MMO:
BRU - Completed

In response to your command, BRU copies the backup set named
DMSYS from the tape and displays a message when the copy
operation is complete. You have now copied the backup set
for
the type of disk you are copying to.
This backup set
includes
indirect command files named
STARTUP.CMD
and
TAPEKIT.CMD that will copy the remainder of the distribution
kit to the disk for you.
The remaining steps in this
procedure show you how to invoke the command files.
8.

Hardware bootstrap the disk (labeled RSXM38)
that you have
copied from the distribution tape.
(Refer to Appendix B for
instructions on bootstrapping.) When you bootstrap the disk,
the system will display a series of messages and will prompt
you for
input.
The following example illustrates this
process, using an RK06 disk:
>RED DMl: SY:~
>RED DMl: LB:~
>MOU DMl:RSXM38 ~
>@DMl: [l,2]STARTUP~
PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY)
>TIM 18:50 26-MAY-85 IBITJ
ENTER LINE WIDTH OF THIS TERMINAL [D:l32]:
>SET BUF=TI: 132 ~
>ACS SY:/BLKS=l024 (BIT)

2-9

[S]: 18:50 26-MAY-85

PREPARING FOR SYSTEM GENERATION
9.

Invoke the TAPEKIT command procedure (by issuing the command
@TAPEKIT), and answer the questions that TAPEKIT displays.
The example that follows the note below shows the process
that TAPEKIT conducts in order to copy the remaining backup
sets from the distribution kit to the disk.
NOTE
If the recording density of the tapes in your
kit is 800 bpi, TAPEKIT will display a
message to notify you when it is time to
mount the second tape. TAPEKIT then copies
the contents of the second tape to your
disks.
If the data copying operation fails,
TAPEKIT displays a message to notify you of
the failure.
In such a case, retry the copy
operation.
If the copying fails again, retry
the copy procedure using a different output
disk.
If the copy operation still fails,
it
is likely that either your distribution kit
is defective and should be replaced, or your
hardware needs to be checked.
The following is an example of the TAPEKIT procedure:

>@TAPE KIT IBIT)

>;
>;
>; RSX-llM V4.2 BL38 tape distribution kit extraction procedure
>;
Started on 26-MAY-85 at 18:51:05

>;
>INS LB:$BRU

>* Enter disk type, RK06 or RK07 [D:RK07] [S] :RK06 IBm
>* Enter second drive and unit [ddn:] [S] :DMO: IBIT)

>;
>*Enter drive and unit with tape distribution kit [ddn:]
> * Dens i t y [ D : 16 0 0 ] [ S ] : 8 0 0 IBIT)

>;
>LOA MM:/PAR=GEN

>;
Copying rest of RSXM38 •••

>;
>BRU/DENS:800/NOINI/UFD/BAC:RSXBAS MM: DMl:
BRU - Starting Tape 1
BRU - End of Tape 1
BRU - Completed
>BRU/DENS:800/NOINI/SUP/UFD/BAC:EXCPRV MM: DMl:
BRU - Starting Tape 1
BRU - End of Tape 1
BRU - Completed
>BRU/DENS:800/NOINI/SUP/UFD/BAC:PRVBLD MM: DMl:
BRU - Starting Tape 1
BRU - End of Tape 1
BRU - Completed

2-10

[S]:MM: IBIT1

PREPARING FOR SYSTEM GENERATION

>BRO/DENS: 800/NOINI/SUP/UFD/BAC:RLUTIL MM: DMl:
BRU - Starting Tape 1
BRU - End of Tape 1
BRU - Completed

>;
>* Unload tape labeled RSXM38 1/2 from MMO:

>;
>; Load tape labeled RSXM38 2/2 on MMO:
>* Is MMO: ready? [Y/N]: Y ru

>; Load disk labeled CLISRC in DMO:
>* Is DMO: ready? [Y/N]: Y ru
>MOU DMO:/FOR
>BRU/DENS:SOO/INI/BAC:MCRSRC/OUT:CLISRC MM: DMO:
BRU - Starting Tape 1
BRU - This disk will not contain a hardware bootable system
BRU - End of Tape 1 on MMO:
BRU - Completed
>DMO DMO:
OMO -- TTO: dismounted from OMO: *** Final dismount initiated ***
19:02:31 *** DMO: -- Dismount completely
>MOU DMO:CLISRC
>BRU/DENS:800/NOINI/SUP/UFD/BAC:HLPDCL MM: DMO:
BRU - Starting Tape 1
BRU - End of Tape 1
BRU - Completed
>BRU/DENS:800/NOINI/SUP/UFD/BAC:RMSV20 MM: OMO:
BRU - Starting Tape 1
BRU - End of Tape 1
BRU - Completed
>DMO DMO:
DMO -- TTO: dismounted from OMO: *** Final dismount initiated ***
19:07:07 *** DMO: -- Dismount complete
>; Unload disk labeled CLISRC from OMO:

>;
>; Completed on 26-MAY-85 at 19:07:09

>;
>@ <EOF>

>
When the TAPEKIT procedure is completed, you are ready to begin
generating your RSX-llM system.
Refer 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-11

PREPARING FOR SYSTEM GENERATION
2.3.1.3 Copying the RK06 or RK07 Disk Kit Stand-Alone - Use the
following procedures to copy the RK06 or RK07 disk kit on a
stand-alone host computer. The term "output disk" or "blank disk"
in
this section refers to the disk or disks that you are using as the
target system disk. All commands shown in this section are issued to
the RSX-llS Basic MCR command line interpreter.
NOTE
Whereas the RK06 distribution kit consists of two
disks,
the RK07 kit contains the entire distribution
kit on a single disk.
Therefore, if you have an RK07
kit, when you perform the following procedure, follow
the first eight steps only.
You will need two blank disks to copy the RK06 distribution disks, and
one blank disk to copy the RK07 disk.
(Place a physical label on each
disk so that the blank 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 labeled RSXM38 and the blank
in the appropriate drives and spin them up.

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

Bootstrap the baseline system on the RSXM38 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.2 BL38

disk

124.K MAPPED (BASELINE)

>@ <EOF>

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

may

RSXM38 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 RSXM38 is in OMO:, enter the following commands:
>INS $B00(8IT)
>BOO OMO: [l,51]BRU64K lliITJ
Notice that you must first install the BOO (boot)
you can software bootstrap BRU64K.

2-12

task before

PREPARING FOR SYSTEM GENERATION
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).
5.

Enter the device specifications in response to the prompts
from CNF.
The "first device" is the drive containing the
RSXM38 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(BD)
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 RK06 disk device
(the one
containing RSXM38) 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(BD)
Enter second device:DMl: ffiD)
6.

>
2-13

PREPARING FOR SYSTEM GENERATION
7.

Run the Bad Block Locator Utility (BAD) first on the blank
disk
labeled RSXM38.
For example, if your output device is
DMl:, use the following command sequence:
>RUN BAD lliDJ
BAD> DMl: /LI ST lliDJ
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 RSXM38
distribution kit disk to the output disk. For example, if
your output disk is DMl:, use the following command sequence:
>RUN BRU (Bill
BRU>/INI/VERIBDJ
From:
OMO: IBrn
To:
DMl: ·IBDJ
The BRU /INI (initialize) switch initializes the disk volume
to which BRU is copying.
(Be aware that if there are any
files on the disk, they will be deleted.)
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:
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.

When RSXM38 is successfully copied, BRU issues the following
message at your terminal to indicate that it has finished:
BRU - Completed
B RU> (CTRL/Z)

>
If you have an RK07 distribution disk, the copying process is
now completed.
If you have an RK06 distribution kit, spin
down both disks and remove them.
Replace
the
first
distribution disk with the second one,
labeled CLISRC.
Replace the new copy of RSXM38 with the second blank disk,
and spin up both disks.
Again, write-protect the disk from
which you are copying data.

2-14

PREPARING FOR SYSTEM GENERATION
10.

Repeat Steps 7 and 8 in this procedure with the CLISRC disk.
NOTE
The following warning message
from
BRU
reminds you that the second disk being copied
cannot be hardware bootstrapped:
BRU - This disk will not contain a hardware bootable system

You can hardware bootstrap the baseline
only (the disk labeled RSXM38).

disk

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
RSXM38 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.4 Copying the RL01/RL02 Disk
Kit
Stand-Alone - Use
the
following procedures to copy the RLOl or RL02 disk kit using a
stand-alone host computer.
The term "output disk" or "blank disk" in
this section refers to the blank disks that you are using as the
target system disks. All commands shown in this section are issued to
the RSX-llS Basic MCR command line interpreter.
The RLOl kit consists of seven disks. The RL02 kit consists of only
five disks because two RL02 disks contain the contents of two RLOl
disks. The disk labels and contents are:
RLOl
Disk Label
RSXM38
EXCPRV
PRVBLD
RLUTIL
MCRSRC
HLPDCL
RMSV20

RL02
Disk Label

RLOl Volume(s)

RSXM38
EXCPRV
PRVBLD
MC RS RC
RMSV20

RSXM38
EXCPRV
PRVBLD, RLUTIL
MCRSRC, HLPDCL
RMSV20

The baseline disk (RSXM38) does not include the stand-alone BRU64K
utility.
Therefore, 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 labeled RLUTIL (PRVBLD in the RL02 kit).
You will need seven blank RLOl, or five blank RL02, disks to copy the
entire distribution kit.
{Place a physical label on each disk so that
the blank disks represent the volume names in the distribution kit.)
However, only the first four volumes (RSXM38, EXCPRV, PRVBLD, 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 backup sets.
To copy the disk distribution kit using a stand-alone system, perform
the following steps (if you have an RL02 distribution kit, substitute
the disk labeled PRVBLD for the disk labeled RLUTIL throughout the
following procedure):

2-15

PREPARING FOR SYSTEM GENERATION
1.

Place the baseline disk (RSXM38) and the distribution disk
labeled 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
information regarding the hardware bootstrap routines.)

Bootstrap the baseline system on the RSXM38 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.2 BL38

124.K MAPPED (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 HLPDCL is on DLl~, enter the
following command to mount RLUTIL:
>MOU DLl:RLUTILIBDJ

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

task before

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 blank disk labeled RSXM38 in the drive, and spin up
the disk.
Also, write-protect the RSXM38 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
RSXM38 distribution kit disk.
The "second device"
is the
drive containing the output disk labeled RSXM38.
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:/DEVIBIT)
2-16

PREPARING FOR SYSTEM GENERATION

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 that your first disk device
(the one
containing RSXM38) 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=300ID
Enter second device:DLl:ID
8.

14:32:01 25-MAY-85 ID

>
9.

Run the Bad Block Locator Utility (BAD) on the RSXM38 blank
disk.
For example,
if your output device is DLl:, use the
following command s~quence:
)RUN BAD ID
BAD> DLl: /LIST ID
BAD -- DLl: Total bad blocks= O.
BAD> (CTRL/Z)

>
The BAD /LIST
located.
10.

switch

lists

any

bad

blocks

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

they
the

are

RSXM38

For example, if your output device is DLl:, use the following
command sequence:
>RUN BRO (Bill
BRU>/INI/VER ID
From:
DLO: ID
To:
DLl: ID
2-17

PREPARING FOR SYSTEM GENERATION
The BRU /INI (initialize) switch initializes the disk volume
to which BRU is copying.
(Be aware that if there are any
files on the disk, they will be deleted.)
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
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
BRU>mRL/Z)

>
Spin down both disks and remove
them.
Replace
the
distribution disk with the next distribution disk.
Replace
the new disk copy with the next blank 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 do this,
press the write-protect button on the face of
the disk drive.
12.

Repeat Steps 9 to 11 with the rest of the disk volumes in the
distribution kit.
NOTE
The following warning message
from
BRU
reminds you that the other disks being copied
cannot be hardware bootstrappped:
BRU - This disk will not contain a hardware bootable system

Only the baseline disk is hardware-bootable
in the RLOl and RL02 distribution kits.
Therefore, the warnings appear when BRO is
copying all but the baseline disk (RSXM38).

2-18

PREPARING FOR SYSTEM GENERATION
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

This section describes the procedures that you use to copy each type
of distribution kit using an on-line host computer.
The host computer
can be running under the control of an RSX-llM or RSX-llM-PLUS
operating system, or it can be a VAX/VMS computer operating in VAX-11
RSX compatibility mode. This section discusses procedures for a host
computer running RSX-llM.
Refer to Section 2.5.1 for instructions on
using a host computer that is running RSX-llM-PLUS.
Refer to Section
2.5.2 for instructions on using a host computer that is running VAX-11
RSX.
If you have a magnetic tape kit, read Section 2.3.2.1 next.
If you have an RK06/07 disk kit, read Section 2.3.2.2 next.
If you have an RLOl/02 disk kit, read Section 2.3.2.3 next.

2.3.2.1 Copying the Magnetic Tape Kit On-Line - Use the following
procedure to copy the 1600 bpi or 800 bpi tape kit or the 6667.
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
term "output disk" or "blank disk" in this section refers to the blank
disk that you are using as the target system disk.
You will need one to seven blank disks to copy the distribution kit,
depending on the type of kit that you have.
Place a physical label on
the first disk so the blank disk represents the backup set name in the
distribution kit
(RSXM38).
If the disk you intend to copy to is an
RA80/RA81, RC25, RD52/RD53, or RM80 disk, the fixed disk is the blank
disk.
The type of blank disk you use must be compatible with your
distribution kit.
If your blank disk is a fixed-media disk, that disk
cannot be the disk that the current system is running on.
You should format removable-media blank disks (using the FMT utility)
and check either fixed- or removable-media blank 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 tape on a TU16 magnetic tape
drive and you plan to copy the tapes to an RK07 disk,
allocate the devices as follows:
>ALL OMO:~
>ALL MMO: ~

2-19

PREPARING FOR SYSTEM GENERATION
2.

Load and mount the distribution kit tape
the tape drive.

labeled

RSXM38

Load the blank disk,
which you have previously labeled
RSXM38,
in the drive and spin up the disk.
If your big-disk
med i a i s an RA 8 0 /RA 81 , RC 2 5 , RD 5 2 /RD 5 3 ,
or RM 8 0 d i s k
(a 11
fixed-media disks), the fixed-media disk serves as the blank
disk.
NOTE
The disk volume should not be mounted yet.
If the disk is mounted as a Files-11 device,
BRU will issue the following warning message:
BRU - *FATAL* - Privilege violation

You are now ready to copy the distribution tape to the disk.
Invoke the Backup and Restore Utility
(BRU), using the
following command line:
>BRU/REW/INI/DEN:density/BAC:name mmn: ddn: ~
The switches and parameters in the BRU command line have
following functions:

the

The /REW
(rewind)
switch ensures that the
completely rewound before BRU begins to copy.

The /INI (initialize) switch initializes the disk volume
to which BRU is copying.
(Be aware that if there are any
files on the disk, they will be deleted.)

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

The /BAC (backup set) switch identifies the BRU backup
set that you want to copy. A backup set is the unit of
data that is directed to or from a volume with a single
BRU command line
(during a single backup or restore
operation) • The distribution tape consists of a series
of BRU backup sets, all or some of which are copied to
the target system disk, depending on which type of disk
you are copying to.
Each type of disk has a name that
you use with the /BAC switch to identify it.
The
following list shows the name for each type of disk:

tape

Disk Type

Name

RP04/RP05/RP06

DB SYS

RL01/RL02

DLSYS

RK06/RK07

DMSYS

RM02/RM03/RM05/RM80

DRSYS

RA60/RA80/RA81/RC25/RD52/RD53

DU SYS

The mmn: specification identifies the
unit that you are copying from.

2-20

tape

device

and

PREPARING FOR SYSTEM GENERATION
f.

The ddn: specification identifies the
unit that you are copying to.

disk

device

and

For example, to begin copying the tape labeled RSXM38
(mounted on device MMO:) to an RK07 disK, issue the following
command:
BRU>/REW/INI/DEN:l600/BAC:DMSYS MM: DMO: film
BRU - Starting Tape 1 on MMO:
BRU - End of Tape 1 on MMO:
BRU - Completed
In response to your command, BRU copies the backup set named
DMSYS from the tape and displays a message when the copy
operation has been completed.
You have now copied the backup set for the type of disk you
are copying to.
This backup set includes an indirect command
file named TAPEKIT.CMD that will copy the remainder of the
distribution kit to the disk for you.
The remaining steps in
this procedure show you how to invoke the TAPEKIT command
file.
5.

Mount the disk that you have copied from the distribution
tape,
then copy the TAPEKIT command file from directory
[200,200] to your directory, using the following command
sequence (in the example, the disk is mounted on DMO:):
>MOU DMO:RSXM38film
>PIP /NV=DMl: [200, 200] TAPEKIT.CMD film

Invoke the TAPEKIT command procedure (by issuing the command
@TAPEKIT),
and answer the questions that TAPEKIT displays.
The example that follows the note below shows the process
that TAPEKIT conducts in order to copy the remaining backup
sets from the distribution kit to the disk.
NOTE
If the recording density of the tapes in your
kit is 800 bpi, TAPEKIT will display a
message to notify you when it is time to
mount the second tape. TAPEKIT then copies
the contents of the second tape to your disk.
If the copy operation fails, TAPEKIT displays
a message to notify you of the failure.
In
such a case,
retry the copy operation.
If
the copy fails again, retry the procedure
using a different output disk.
If the copy
still fails, it is likely that either your
distribution kit is defective and should be
replaced, or your hardware needs to
be
checked.

2-21

PREPARING FOR SYSTEM GENERATION
The following is an example of the TAPEKIT procedure,
disk:

using

RK07

>@TAPEKIT ID

>;
>;
>; RSX-llM V4.2 BL38 tape distribution kit extraction procedure
>;
Started on 26-MAY-85 at 18:51:05

>;
>;

>* Enter device and unit for disk ( s) [ddn:] [s] :DM: ID
>* Enter disk type, RK06 or RK07 [D:RK07] [S] =ID

>;
>*Enter drive and unit with tape distribution kit [ddn:]
> * Dens i t y : [ D: 16 0 0 ] [ S ] : ID

[S]:MM:IBIT)

>;
>; Copying rest of RSXM38 to DM: •••

>BRU/DENS:l600/NOINI/SUP/UFD/BAC:RSXBAS MMO: DM:
BRU - Starting Tape 1
BRU - End of Tape 1
BRU - Completed
>BRU/DENS:l600/NOINI/SUP/UFD/BAC:EXCPRV MMO: DM:
BRU - Starting Tape 1
BRU - End of Tape 1
BRU - Completed

>;
>; Completed on 26-MAY-85 at 19:02:07

>;
Note that BRU will display a message for each of the volumes
copies from the distribution tape.

that

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.2 Copying the RK06/RK07 Disk Kit On-Line - Use the following
procedure to copy the RK06/07 disk kit using the host computer on
line. The term "output disk" or "blank disk" in this section refers
to the blank disk that you are using as the target system disk.
You will need one blank disk to copy the RK07 distribution kit,
and
two blank disks to copy the RK06 distribution disk.
(Place a physical
label on each disk so that the blank disks represent the labels on the
respective disks in the distribution kit.)

2-22

PREPARING FOR SYSTEM GENERATION
and check
You should format the blank disks (using the FMT utility)
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:

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 DM 0: (@!)
>ALL DMl: (@!)

Load the distribution disk labeled RSXM38 in OMO:; then load
the blank disk labeled RSXM38
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.

Invoke the Backup and Restore Utility
(BRU)
and enter the
For example, enter the
command line to copy the disk.
following command line to BRU:
>BRU (5D)
BRU>/I NI/VER (5D)
From:
DM 0: (@!)
To:
DMl: (5D)
The BRU /INI (initialize) switch initializes the disk volume
to which BRU is copying.
(Be aware that if there are any
files on the disk, they will be deleted.)
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.

2-23

PREPARING FOR SYSTEM GENERATION
When the distribution disk is successfully copied, BRU issues
a message at your terminal to indicate that it has finished:
BRU - Completed
) (CTRL/Z)

>
4.

If you have an RK07 distribution disk, the copying process is
now completed.
If you have an RK06 distribution kit, spin
down both disks and remove them.
Replace
the
first
distribution disk with the second one,
labeled CLISRC.
Replace the new copy of RSXM38 with the second blank disk,
and spin up both disks. Again, write-protect the disk from
which you are copying data. Then repeat Steps ·2 to 4 of this
procedure with the CLISRC disk.
NOTE
The following warning message
from
BRU
reminds you that the second disk being copied
cannot be hardware bootstrapped:
BRU - This disk will not contain a hardware bootable system

You can hardware bootstrap the baseline
only (the disk labeled RSXM38).

disk

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 RL01/RL02 Disk Kit On-Line - Use the following
procedures to copy the RLOl or RL02 disk kit using a host computer on
line. The term "output disk" or "blank disk" in this section refers
to the blank disks that you are using as the target system disks.
All
commands shown in this section are issued to the RSX-llS Basic MCR
command line interpreter.
The RLOl kit consists of seven disks. The RL02 kit consists of only
five disks because two RL02 disks contain the contents of two RLOl
disks. The disk labels and contents are:
RLOl
Disk Label
RSXM38
EXCPRV
PRVBLD
RLUTIL
MCRSRC
HLPDCL
RMSV20

RL02
Disk Label

RLOl Volume(s)

RSXM38
EXCPRV
PRVBLD
MC RS RC
RMSV20

RSXM38
EXCPRV
PRVBLD, RLUTIL
MCRSRC, HLPDCL
RMSV20

You will need seven blank RLOl, or five blank RL02, disks to copy the
entire distribution kit.
(Place a physical label on each disk so that
the blank disks represent the volume names in the distribution kit.)
However, only the first four volumes (RSXM38, EXCPRV, PRVBLD, 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 backup sets.

2-24

PREPARING FOR SYSTEM GENERATION
You should check the blank 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.
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 labeled RSXM38 in DLO:,
then load the blank disk, labeled RSXM38, 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> /IN I/VER®
From:
DLO: ~
To:
DLl: ~
The BRU /INI (initialize) switch initializes the disk volume
to which BRU is copying.
(Be aware that if there are any
files on the disk, they will be deleted.)
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
NOTE
If the verify fails,
do not attempt the
system generation without first retryins 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-25

PREPARING FOR SYSTEM GENERATION
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 blank 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> /IN I/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 (RSXM38).
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 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

2.4

THE UPDATE PROCEDURE

This section describes how you use an Update package to apply
corrections to your RSX-llM Version 4.2 operating system and layered
products software.
The Update package consists of two groups of software: the Update kit
and the layered product files.
Depending on which type of Update
package you receive, the two groups of software are supplied on one or
two pieces of magnetic media.

2-26

PREPARING FOR SYSTEM GENERATION
The Update kit is a set of files that you use to apply corrections to
your operating system software.
These corrections are cumulative,
that is, each Update contains all of the corrections that have been
generated since the release of RSX-llM Version 4.2.
Included in the
Update kit is an interactive command procedure that applies the Update
files to your current operating system software.
You use the layered product files to apply corrections to some of the
layered products (such as languages and DECnet) that run on RSX-llM.
NOTE
If you are installing an RSX-llM system for the first
time, you must apply your Update package before you
invoke the SYSGEN procedure to generate your operating
system.

2.4.1

The Update Package

Your Update package is one of the following types:
•

Magnetic tape kit (800 or 1600 bpi)

RK06/RK07 disk kit

RL01/RL02 disk kit

•

TK50 magnetic tape cartridge kit

RK06/RK07 and RL01/RL02 Update packages are distributed on magnetic
tape or disk media. Update packages targeted for all other types of
disks are distributed on magnetic tape only.
The software in the Update package
categories:

falls

into

the

following

three

fiL.~

•

Update procedure command file - the indirect command
controls the Update command procedure

that

•

Replacement files - the updated or new object modules that
replace the object module files on your RSX-llM distribution
kit

•

Correction files - the files (.COR file type) that were used
to create the updated source files (.MAC file type) that are
applied during the Update command procedure

The layered product files are used to apply corrections to certain
layered products that run on RSX-llM.
For a list of the layered
product files and instructions on how to use them,
see the RSX-llM
Update Notes that are included with each Update.

2.4.2

How Update Works

Update is the name of a command procedure that applies corrections
your RSX-llM Version 4.2 operating system software.

The Update command procedure copies the replacement files
in the
update software to a disk containing a copy of your RSX-llM Version
4.2 distribution kit. Then you use the disk containing the updated
distribution kit to generate a new RSX-llM system.
2-27

PREPARING FOR SYSTEM GENERATION
The Update kit is cumulative. Therefore, each revision of the Update
kit contains all of the corrections that have been generated since the
last full release of RSX-llM.
You must apply this Update to an unaltered copy of the RSX-llM Version
4.2 distribution kit. Otherwise, the corrections will not be properly
integrated with the other system software components, so your system
will not work.

2.4.2.1 The Update Command Procedure - An indirect command file named
UPDATE.CMD is contained in UFD [200,200] on the baseline disk (the
disk labeled RSXM38) in your original RSX-llM Version 4.2 distribution
kit.
This indirect command file initiates the application of the
Update procedure. When you begin the Update procedure by invoking
UPDATE.CMD,
the file UP.CMD is copied from the Update kit medium to a
disk that contains a copy of your RSX-llM Version 4.2 distribution
kit.
UPDATE.CMD invokes UP.CMD, which then copies the replacement
files (new files that replace the original object modules and source
files)
to your distribution kit disk.
When the copying has been
completed, the Update has been applied and you have a target system
disk that contains all of the files necessary to generate an updated
RSX-llM operating system. You then invoke the SYSGEN procedure to
generate the updated system.
NOTE
Please note that questions asked by the Update command
procedure vary according to your distribution kit.

2.4.2.2 Replacement Files - The replacement object files
(.OBJ file
type) are the updated files that incorporate the latest corrections to
your RSX-llM system.
The Update command procedure copies these
replacement files to your target system disk. Then, when you perform
a new system generation, you create an updated system that contains
the corr~ctions and new software features supplied in the Update.

2.4.2.3 Source Correction Files - The Update kit also contains the
source correction files (.COR file type) that were used to create some
of the replacement files used by the Update procedure. The .COR files
are inciuded to provide documentation of the changes that the Update
has made to those portions of the system software for which MACR0-11
source code is supplied on the RSX-llM Version 4.2 distribution kit.
Generally, you do not need these files.
However, if your application
warrants it, you may edit the correction files to include your own
corrections.
You can then apply the edited correction files manually
to produce updated source files.

2.4.3 Preparing for Update
This section describes the necessary preparations for the Update
procedure.
Before you apply the Update package software, you must
create a disk copy of the original, unaltered RSX-llM Version 4.2
distribution kit.
This must not be a copy on which you have run the
SYSGEN command procedure, but a copy made directly from your original
RSX-llM Version 4.2 distribution kit. Copying your distribution kit
to disk ensures that you will have an original, unaltered distribution

2-28

PREPARING FOR SYSTEM GENERATION
kit to recopy if media or hardware problems occur during the Update
command procedure.
Refer to Section 2.3 for instructions on how to
copy your distribution kit.
In this section, the term "target system
disk" refers to the disk that you are copying the distribution kit to.

2.4.3.1 Hardware Required for Applying Update - Hardware requirements
differ according to the type of media in your distribution kit and
Update package.
If you have a magnetic tape distribution kit for any
of the supported target system disks except for RK06/RK07 or RL01/RL02
disks, you need one magnetic tape drive and one disk drive of the same
type as your target system disk.
If you have an RK06/RK07 or RL01/RL02 disk distribution kit and a
magnetic tape Update kit, you need one magnetic tape drive and two
RK06/RK07 or RL01/RL02 disk drives.
If you have an RK06/RK07 disk distribution kit and an
Update kit, you need two RK06/RK07 disk drives.

RK06/RK07

disk

If you have an RL01/RL02 disk distribution kit and an
Update kit, you need two RL01/RL02 disk drives.

RL01/RL02

disk

2.4.4

Applying Update

After you have made a copy of the distribution kit, you apply the
Update software to the distribution kit files.
You can apply Update
either on an on-line host computer, or on a stand-alone host computer.
If you have access to a system already running an on-line system, you
can use that system to apply Update on line. An on-line system is one
on which other activity may be occurring and on which other users may
be
logged
in.
The Update procedure executes on an RSX-llM,
RSX-llM-PLUS, or VAX-11 RSX on-line host computer.
If you do not have access to a system already running RSX-llM,
you
must use the baseline system on the RSX-llM distribution kit to apply
Update to a stand-alone system. A stand-alone system runs the RSX-llM
baseline system, which dedicates your host computer's resources to
your application alone.
If you are applying an Update for the first time, you should read
Chapter 1,
this chapter, and the RSX-llM Update Notes before you
invoke the Update procedure.
If you understand the Update and system
generation procedures before you begin them,
you will be better
prepared to avoid mistakes, and you can do a better job of tailoring
your system to suit your particular needs.
The following sections provide general instructions for applying
Update on either type of host.
In addition to reading the following
sections, refer to the applicable version of the RSX-llM Update Notes
for instructions specific to each Update.

2-29

PREPARING FOR SYSTEM GENERATION
2.4.4.1 Applying Update Stand-Alone - Follow the procedure in
section to apply your Update package using a stand-alone host:

this

Load the Update kit disk or tape on an appropriate drive.
Load the distribution kit baseline disk, (the disk labeled
RSXM38), on an appropriate drive.
Then hardware bootstrap
the distribution kit disk labeled RSXM38.
For example:

>;
RSX-llM V4.2 BL38 124K MAPPED (BASELINE}

>RED DL:=SY: ffim
>RED DL: =LB: IB@
>MOU DL: RSXM38 ffim
>@DL: [l,2]STARTUP ffim
>*PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY}

[S]: 18:34 17-JUN-85

>TIM 18: 34 l 7-JUN-85 00)
>*ENTER LINE WIDTH OF THIS TERMINAL

[D:l32.]: IBITJ

>SET /BUF=TI:l32
>ACS SY:/BLKS=512
>@ <EOF>

>
2.

Invoke the Update command procedure, by issuing the following
command:
>@UPDATE 00J

Answer the questions and follow the instructions that the
Update procedure displays.
If this is Update A, (the Update
distributed with the initial release of RSX-llM Version 4.2),
Update only displays a notification of corrections to layered
products. There are no corrections to the base system
software.
If this is not Update A, the Update
following steps.

will

proceed

with

the

If the Update kit is on magnetic tape, the correction files
must be copied to disk before they can be applied to the
distribution kit disks.
If the distribution kit is on an RK06/RK07 or an RL01/RL02, a
backup set is copied to a blank disk of the same type.
If the distribution kit is on a disk other than an RK06/RK07
or an RL01/RL02, a backup set is copied directly to the
distribution disk.

The Update procedure
distribution kit.

applies

the

corrections

the

If the distribution kit is an RK06/RK07 or an RL01/RL02,
the
disk with the Update files is software booted and the
correction files are applied to the distribution kit.
If the distribution kit is on a disk other than an RK06/RK07
or an RL01/RL02, the correction files are applied in place to
the distribution kit.

2-30

PREPARING FOR SYSTEM GENERATION
The following is an example of an Update A procedure on a
host:

stand-alone

>
>

>@UPDATE ruJ

>; RSX-llM

>;
>;
>;
>;
>;
>;
>;
>;

V4.2

UPDATE PROCEDURE

17-JUN-85 18:34:11

This command file initiates the Update Procedure for RSX-llM V4.2. It
will determine what type of Update media is being used as well as what
Update level is being applied. It will copy all of the files that are
necessary to bring your system up to the current patch level. The
destination of these files will be determined from what type of Update
media you are using and what Update level you are applying. When this
copying is complete and the Update has been applied, it may be necessary
to perform a SYSGEN to incorporate the new software.

>INS LB:$BRU

>;
>* Enter device and unit for update kit [ddn:]
>* Density [D: 1600] [SJ: Ifill

[S]: MM: (5TI)

> LOA MM:/PAR=GEN

>;
>*Enter device containing distribution kit [ddn:]

[S]:oL:~

>BRU/NOINI/SUP/UFD/DENS:l600/REW MM: [1,11] DL:
BRU - Starting Tape 1 on MMO:
BRU - End of Tape 1 on MMO:
BRU - Completed

>;
>; RSX-llM V4.2 UPDATE A
>;
>; There are no updates to the RSX-llM software on this version of
>; the Update kit. However, this Update kit contains corrections
>; for the following layered products:

>; DECnet-llM V4.0
>; DPM V4.l
>; FMS-11/RSX Vl.O
>; PDP-11 FORTRAN-IV V2.6
>; KMVll-A HDLC Framing Software Vl.O
>; DCX KMVll-A Development Tools Vl.O
>; RSX-11 2780/3780 Protocol Emulator V4.l
>; PDP-11 COBOL V4.4
>; COBOL-81/RSX V2.3
>; DATATRIEVE-11 V3.l
>; PDP-11 FORTRAN-77/RSX VS.O
>; PDP-11 FORTRAN-77 DEBUG/RSX Vl.O
>; PDP-11 PASCAL/RSX Vl.l
>; PDP-11 SORT/MERGE V3.0

>; Please read the documentation included in the
>; RSX-llM System Generation and Installation Guide
>; for directions on applying these Updates.

>; Application of the Update is complete. A record of this
>; will be appended to the KITIDENT file.

>SET /UIC=[200,200]
>@ <EOF>

2-31

PREPARING FOR SYSTEM GENERATION
2.4.4.2 Applying Update On-Line - Follow the procedure
section to apply your Update using an on-line host:

this

Log into a privileged account and set your command line
interpreter to MCR.
For systems other than RSX-llM, refer to
section 2.5 for the requirements necessary for running
Update.

Load the Update kit disk or tape on an appropriate drive.
Load the distribution kit baseline disk, (the disk labeled
RSXM38), on an appropriate drive.

Allocate and mount the baseline disk
issuing the following command sequence:

>ALL ORO:
>MOU DRO: RSXM38
4.

Copy the Update command procedure named
directory [200,200] to your directory:

from

ru
following

UPDATE.CMD

Invoke the Update command procedure by issuing the
command:
>@UPDATE

RSXM38,

>PIP /NV=DRO: [ 200, 200] UPDATE. CMD
5.

labeled

will

proceed

with

the

If the Update kit is on magnetic tape, the correction files
must be copied to disk before they can be applied to the
distribution kit disks.
If the distribution kit is on an RK06/RK07 or an RL01/RL02, a
backup set is copied to a blank disk of the same type and the
disk is mounted.
If the distribution kit is on a disk other than an RK06/RK07
or an RL01/RL02,
a backup set is copied directly to the
distribution disk.

If the Update kit is on an RK06/RK07
disk is mounted.

The Update procedure
distribution disk(s).

corrections

applies

the

RL01/RL02,
to

the
the

If the distribution kit is an RK06/RK07 or an RL01/RL02,
the
disk with the Update files is mounted and the correction
files are applied to the distribution kit from the Update
disk.
If the distribution kit is on a disk other than an RK06/RK07
or an RL01/RL02, the correction files are applied in place to
the distribution kit.

2-32

PREPARING FOR SYSTEM GENERATION
The following is an example of an Update A
host:

procedure

on-line

>
>

>@UPDATE ID

>;
>;

RSX-llM

V4.2

UPDATE PROCEDURE

17-JUN-85 18:34:11

>;
>;
>;
>;
>;
>;
>;
>;
>;

>* Enter device and unit for update kit [ddn: J [SJ :MM: ID
>*Density [D:l600J [SJ:ID

>;
>* Enter device containing distribution kit [ddn:J

[SJ :DL: ID

>;
>;
>BRU/NOINI/SUP/UFD/DENS:l600/REW
BRU - Starting Tape 1 on MMO:

MM: [l,llJ DL:

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

>;
>; RSX-llM V4.2 UPDATE A

>;
>; There are no Updates to the RSX-llM software on this version of
>; the Update kit. However, this Update kit contains corrections
>; for the following layered products:

>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;
>;

DECnet-llM V4.0
DPM V4.l
FMS-11/RSX Vl.O
PDP-11 FORTRAN-IV V2.6
KMVll-A HDLC Framing Software Vl.O
DCX KMVll-A Development Tools Vl.O
RSX-11 2780/3780 Protocol Emulator V4.l
PDP-11 COBOL V4.4
COBOL-81/RSX V2.3
DATATRIEVE-11 V3.l
PDP-11 FORTRAN-77/RSX V5.0
PDP-11 FORTRAN-77 DEBUG/RSX Vl.O
PDP-11 PASCAL/RSX Vl.l
PDP-11 SORT/MERGE V3.0

>;
>; Please read the documentation included in the
>; RSX-llM System Generation and Installation Guide
>; for directions on applying these Updates.

>;
>; Application of the Update is complete. A record of this
>; will be appended to the KITIDENT file.

>SET /UIC=[200,200J
>@ <EOF>

2-33

PREPARING FOR SYSTEM GENERATION
2.4.5

Errors During Update

There are some errors from which Update attempts to recover, such as
the ~nability to mount a disk. When such an error is encountered,
Update displays an error message and a list of options from which you
can choose the action you want Update to take.
The following is an example of the text
displays if a recoverable error occurs:

that

the

Update

procedure

>;
>; An error has occurred that prevents the Update procedure from
>; working correctly.
>;
>; If you know what caused the error, correct the error, then
>; either continue with the Update procedure or abort the Update
>; procedure and begin again.
>;
>; See the RSX-llM System Generation and Installation Guide
>; for more information on identifying and correcting errors.
>;
>; You may choose one of the following options:
>;
>;
A - > Abort and exit from the Update procedure
>;
c - > Continue with the Update procedure without
repeating the command that caused the error
>;
p - > Pause while you attempt to resolve the problem
>;
>;
R - > Repeat the command that caused the error
>;
>* Which option do you choose (A, C, P, or R)? [S]

If you choose option A, Update dismounts the target system disk and
exits.
Choose this option if you do not understand the circumstances
surrounding the error and you wish to terminate the Update procedure.
If you choose this option, Update prints the following messages on
your terminal:

>;
>; Refer to the instructions in the RSX-llM System Generation and
>; Installation Guide for installing this Update kit to make certain
>; you have not skipped a step or overlooked something.

>;
>; If you cannot identify and resolve the problem, please contact
>; your local DIGITAL software specialist for further assistance.

>TIM
17:09:31 12-JUN-1985

>;
>; Now dismounting the Update kit device and exiting •••
>;
>OMO MM:
OMO -- TT36: dismounted from MMO: ***Final dismount initiated

***

>;
>SET /UIC=[200,200]
>@(EOF>

>
If you choose option c, Update continues with the next command and
ignores the error.
You might choose this option if the Update
procedure's attempt to mount the Update kit disk failed because the
kit disk was already properly mounted.

2-34

PREPARING FOR SYSTEM GENERATION
If you choose option P, the Indirect Command Processor pauses until
you instruct it to continue by issuing the UNS command.
You might
choose this option if mounting the Update kit failed because you had
the kit mounted, but not properly for Update, and you want to dismount
the kit and then have Update reissue the MOUNT command.
When you
restart the Indirect Command Processor by using the UNS command, the
option question is repeated so that you may choose either option C or
option R.
The following is the text that Update prints
command to pause:

when

you

use

the

"P"

>;
>; The Update procedure will now pause to let you attempt to
>; resolve the problem. Please UNStop the indirect command file
>; processor when the problem has been resolved.

>;
AT.TO

Pausing. to continue type "UNS AT.@"

If you choose option R, Update repeats the command that failed.
You
might choose this option if mounting the Update kit failed because you
specified a device that did not contain the Update kit, but the kit is
now ready to be read from the specified device.

2.4.6

Layered Product Files

The Update package also
products.

includes

files

update

certain

layered

In the magnetic tape Update packages, the layered product files are on
the Update tape in the form of additional backup sets.
In the
RK06/RK07 and RL01/RL02 disk Update packages,
the layered product
files are in directories on the Update disk.
There is a documentation file
(.DOC file type)
for each layered
product that explains how to apply the corrections to that layered
product. Read the documentation files for each layered product that
you have on your system.
You should apply any corrections to layered products after you use the
SYSGEN procedure to generate a new system that incorporates the Update
corrections.
The layered products require the corrected versions of
certain files
(for example, SYSLIB.OLB) that are produced during the
system generation procedure.

2.4.6.l Accessing the Corrections with the Magnetic Tape Package - If
you have the magnetic tape Update package, the files for each product
are contained in a separate BRU backup set on the Update kit tape.
You must restore the backup set from the tape to the disk before you
can apply the layered product files.
Use the BRU utility to restore
the backup set to disk, and then type or print the appropriate
documentation file for further
instructions.
You can display an
instruction file at your terminal by using the following command ~ine:
>PIP TI:=ddnn: [ggg,200]product.DOCIBDJ
In the above command line, replace ddnn: with the name of the drive
that contains the Update kit and replace ggg with the group number
from the directory specification for the file that you want to display
(as listed in the RSX-llM Update Notes).

2-35

PREPARING FOR SYSTEM GENERATION
The following description shows you how to restore the BRU backup set
for PDP-11 FORTRAN-77/RSX. The backup set name for FORTRAN-77/RSX is
F77. For other layered products, substitute the applicable backup set
name.
To restore a backup set, mount the Update software contained on
magnetic tape.
For example, if the Update magnetic tape is loaded on
drive MMO:
and the disk to which you want to copy the FORTRAN-77
backup set to is the device DMO:
(an RK07 mounted as a Files-11
volume), use the following MCR command string:
>MOU /FOR MMO:IBITJ
>BRU /NOINI/UFD/DENS:l600/SUP/REW/BAC:F77 MMO: DMO: (8IT)
If you have the Update software contained on an 800 bpi magnetic tape,
substitute /DENS:800 for /DENS:l600 in the command string above.

2.4.6.2

Accessing the Corrections on the RK06/RK07 or RL01/RL02
Update Package - If you have the RK06/RK07 or RL01/RL02 disk
Update package, mount the Update disk as a Files-11 volume and type or
print
the
appropriate documentation file.
You can display a
documentation file at your terminal using the following command line:
>PIP TI:=ddnn: [ggg,200]product.DOC lBITJ
When you issue the above command line, replace ddnn: with the name of
the drive that contains the Update disk, and replace ggg with the
group number of the directory specification for the file that you want
to display (as listed in the RSX-llM Update Notes).
You can also copy the contents of selected directories to disk by
creating the necessary directories using the MCR UFD command, and then
using PIP. For example, if you want to copy the contents of UFD
[252,200)
from an RK07 Update disk mounted on DMl:
to your system
disk mounted on DMO:, use the following command sequence:
>UFD OMO: [252,200) (8IT)
>PIP DMO: [252,200)/CD/FO/SU=DMl: [252,200)(8@
Refer to the RSX-llM Update Notes for a list of the directory
specifications and backup set names for the layered product files.

2.5

NON RSX-llM HOSTS

You can perform an RSX-llM Update and system generation on host
computers that are running under the control of operating systems
other than RSX-llM.
This section describes the privileges and
conditions necessary to generate an RSX-llM system on an RSX-llM-PLUS
host, and on a VAX/VMS computer that is running under VAX-11 RSX
compatibility mode.

2.5.1

Update and System Generation on an RSX-llM-PLUS Host

To perform an RSX-llM Update and system generation on an RSX-llM-PLUS
host, you must log in to a privileged account and set your command
line interpreter to MCR.
In addition, on an RSX-llM-PLUS Version 3.0
host, you must set your directory to nonamed mode.

2-36

PREPARING FOR SYSTEM GENERATION
2.5.2

Update and System Generation on a VAX/VMS Host

To perform RSX-llM Update and system generation on a VAX host computer
running a VMS operating system of Version 4.0 or later, you must have
the VAX-11 RSX compatibility mode installed. Then you must set the
privileges and meet the requirements described in this section.

2.5.2.1 Logging In and Setting Up Privileges - VAX/VMS uses the MCR
indirect command file capability as the host system for RSX-llM Update
and system generation. To use this capability, you must set the
following privileges.
Note that if you run the system generation from
the system manager's account that is distributed with the VAX/VMS
system (as long as its privileges have not been altered), you
automatically have access to the required privileges.
1.

You must have change mode to kernel (CMKRNL) privilege.
This
allows you to perform a SET /UIC command that changes your
default UIC.

You must have logical I/O privilege
(LOG IO).
VMR to perform logical I/O on system files.

You must have volume protection privilege
(VOLPRO).
This
allows you to mount volumes with the /FOREIGN keyword for the
MOUNT command.

You must have system protection privilege
(SYSPRV).
allows you to create files in other directories.

Use the following procedure
privileges:
1.

log

and

set

This

the

allows

This

necessary

Log in on the VAX/VMS system with the /CLI=MCR qualifier so
that you can use MCR, the required command line interpreter
(CLI) for RSX-llM Update and system generation. For example:
User name: SYSTEM/CL I =MCR ID
Password: ID

Set up the required privileges specified in steps 1 through 4
of the previous list by issuing the following command line:
>SET PROCESS/PRIVILEGES=(CMKRNL,LOG IO,VOLPRO,SYSPRV)ID

Set your User Identification Code (UIC)

to (200,200]:

>Set /UIC=[200,200](BTI)
4.

Set your default device to the baseline disk.
For example,
if your baseline disk is an RK07 disk mounted in drive DMAO:,
issue the following command:
>Set default DMAO:(BTI)

2.5.2.2 Answering Questions Requiring Device Specifications - RSX-llM
procedures running under the VAX-11/RSX environment expect answers to
questions requiring device specifications to be in the form ddnn:,
where "dd" is the device type and "nn" is the unit number (and ":" is
a required terminator). However, on VMS systems, especially those on
a VAX cluster, this type of device specification may not be acceptable

2-37

PREPARING FOR SYSTEM GENERATION
because of units of the same device type on more than one controller
on the same processor (for example, DMAl:
and DMBl:); or because of
units of the same device type on more than one processor on a cluster
(for example, MFAO:
on node SIOUX and MFAO:
on node CUSTER).
To
resolve this ambiguity, you can use logical names in the form $$nn:
(your system manager can set up logical names in this form, according
to the instructions in the VAX-11 RSX documentation) to represent the
devices you will use.
If the RSX-llM procedures need to know what
type of physical device the logical represents, an additional question
will be asked:
Enter device type [dd]

[S]:

In such a case, answer this question with the RSX-llM two-character
name of the physical device type (for example, DM or MF).
NOTE
The RSX-llM and VAX/VMS
operating
systems
use
different two-letter mnemonics for some types of
devices.
For example, the VAX/VMS mnemonic for a TU77
magnetic tape drive is MT, while the RSX-llM mnemonic
is MM.
In such cases, you must enter the RSX-llM
device-type mnemonic when you are prompted for the
device type.

2-38

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
questions
Executive,
industrial

the assembly phase of SYSGEN.
After you answer the
in Phase I, SYSGEN uses your responses to assemble the
a subset of MCR modules, the device drivers, and any
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
functions 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
method for input

Target Configuration
Section

Defines
the
hardware
of the target system

Host Configuration
Section

Determines how
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 ~pecific
system
libraries to be included in your target
system

Peripheral Options
Section

Defines
control
information
for
peripheral devices included in your target
system

executes

handle

and

the

characteristics
assembly

and

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 Version 4.2 Task Builder
(TKB)
distributed on your kit.
The Task Builder is
installed as task ••• TKL.
If you are doing an on-line
SYSGEN,
other system users can still use the system's
TKB without any interference from 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.
3-2

with

their

respective

STRUCTURE AND CONCEPTS OF SYSGEN

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
Sectionl

Creates object libraries
existing libraries

Executive Task-Build
Section

Task

System Image
Creation Section 1

Creates
the
RSXllM.SYS

Full-Duplex Terminal
Driver Task-Build
Section l

Task builds the
driver (optional)

Loadable Driver
Task-Build Section

Task
builds
drivers

Common Block TaskBu i ld Sectionl

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

Privileged TaskBuild Section

Task
tasks

System VMR Section

Creates the VMR command file SYSVMR.CMD
and runs VMR to augment the system image

builds

the

RSX-llM

system

any

and

adds

Executive

image

file

full-duplex

terminal

loadable

device

privileged

and

system

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.1. 3

the

questions,

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.

3-3

STRUCTURE AND CONCEPTS OF SYSGEN
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. Wnen 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 Version 4.2 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 III

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, you 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.)
In SYSGEN Phase III, you can task build
any
privileged
or
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.2

the

questions,

SYSGEN INDIRECT COMMAND FILES

As stated at the beginning of this chapter, SYSGEN is a series of
related indirect command files.
An indirect command file is a text
file that contains commands interpreted by the Indirect Command
Processor.

3-4

STRUCTURE AND CONCEPTS OF SYSGEN
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 an indirect command file, issue the following command, where
filename is the name of the command file you want to invoke:
>@f ilenarne~

It is not necessary to include the file type .CMD when you
indirect command file'.

invoke

Phases I, II,
and III of SYSGEN reside in directory
[200,200].
However, while it runs, SYSGEN resets the directory.
If you exit
SYSGEN and want to restart, be sure to set your directory to be
[200,200].

3.2.1

Independent SYSGEN Command Files

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 &re:

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

the

format

SYSGEN

The general format for SYSGEN questions is an asterisk followed by the
9uestion 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 Indirect Command Processor
Manual for a complete description of question formats in an 1nd1rect
command file.

3-5

STRUCTURE AND CONCEPTS OF SYSGEN

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 to
indicate 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 typical 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.
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]:
3-6

STRUCTURE AND CONCEPTS OF SYSGEN
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
(R).
(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 that 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.
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.

3-7

STRUCTURE AND CONCEPTS OF SYSGEN
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 it can execute unattended whenever
appropriate.

3.4.1.1 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 from
example:

SYSGEN.

For

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

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.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

*EOX* Did the Executive assemble correctly? [Y/N]:

3-8

the

STRUCTURE AND CONCEPTS OF SYSGEN
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), 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 a valid transition from Phase I to Phase
II only.
SYSGEN cannot chain from Phase II to Phase
III.

3.5

SAVED ANSWER FILES

Whenever you answer a question during Phase I and Phase II, 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 Setup Questions in SYSGEN Phase I
and
(optionally)
in Phase II, you may create either a single file
containing saved answers for both Phase I and Phase II or you may have
one saved answer file for Phase I and a separate saved answer file for
Phase II.
In either case, SYSGEN always saves your responses in a
file.
NOTE
SYSGEN does not save responses to questions in the
Peripheral Options Section pertaining to ICR/ICS or
DSS/DRS devices. SYSGEN also does not save responses
to questions pertaining to the task building of the
LPA initialization code.

3-9

STRUCTURE AND CONCEPTS OF SYSGEN

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
directory other than the default [200,200] and if that directory does
not already exist, you must first create the directory 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 MCR
Operations Manual or the RSX-llM Command Language 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

[D:

SYSSAVED.CMD]

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. The file may
still be successfully used for input up to the point where the last
question was answered in the aborted SYSGEN.
(Before restarting
SYSGEN, remember to reset your directory 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 PDP-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.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-10

STRUCTURE AND CONCEPTS OF SYSGEN
3.6.1

SYSGEN with MCR Inhibited (PREPGEN)

During the Setup
question:

Section

Phase

SYSGEN

asks

the

* 3. Do you want to inhibit execution of MCR commands

following
(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 Version 4.2, 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 the contents of SGNSTAND.CMD.
This means that SYSGEN automatically answers most of the Phase
Phase II questions.
The Standard Function System builds an' RSX-llM
functionality including:

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 magnetic tape support

•

FCS resident library support

and NL:

pseudo devices

3-11

and

STRUCTURE AND CONCEPTS OF SYSGEN
•

Support for all selected loadable drivers in DRVPAR

•

Default values for
swapping priority)

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.

you

may

find

Table 3-3
Options Included in the Standard Function System
Setup Section
Question

Option

Mapped system

Target Configuration Section
Question

Option

Question

Option

K-series device support

CO:

and NL:

device support

{Continued on next page)

3-12

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

Executive Options Section
Question

Option

Question

Option

DBMS-11 support

Queue manager and queued
spooler

Files-11 ACP
36

Group global event flags

All system directives:
Get Partition Parameters

RMS-11 bucket locking
and placement control

Nonresident tasks

Get Task Parameters
Send/Receive

Loadable task loader

Alter Priority
Extend Task

Executive common

Connect to Interrupt Vector
Get Sense Switch

Memory management (PLAS)
directives

Set System Time
Stop-bit
Specify Requested Exit AST

Send/Receive By Reference
directives

Parent/offspring tasking
Parent/offspring tasking
with chaining

Get Mapping Context
directive

5 pre-allocated QIO packets

33-word size for the data

Address checking
transfer vector

I/O rundown

Multiuser protection

ANSI magnetic tape ACP

On-line formatting
or diagnostic QIOs

Loadable device drivers

5-tick interval for
round-robin scheduling

Highest priority class of
150 for round-robin
scheduling

(FMT)
42

Lowest priority class of
1 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

Option

Question

Option

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

Power fail recovery

Install, request, and
remove on exit

Large (20K) Executive

Logical device assignment

Error logging support

Checkpointing

Disk writecheck

Checkpointing with a system
checkpoint file

Software write-lock support
51

Crash Dump Analyzer

CDA output notification
device CSR value of 117564

Rotating pattern in data
lights

System-controlled partitions

Shuffler support

(CDA)

Terminal Driver Options Section
Question

Option

Question

Option

Full-duplex terminal driver
Terminal Driver Options

Get terminal driver options

Hold-screen mode

Transparent read/write

120-second unsolicited input
timeout value

Pass form feeds directly
to the terminal

Settable case conversion
for input

Automatic carriage
return/line feed

Read after prompt

Read with no echo

(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
Question

Option

Question

Option

Task checkpointable during
terminal input

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

Unsolicited input character
AST

Write with CTRL/O
cancellation

Break-through 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

Postmortem 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)
Question

Option

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 confusion, direct SYSGEN to Autoconfigure your hardware. The
Autoconfigure 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 directory (1,54]) supplied with
your RSX-llM Version 4.2 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 there be
no other activity on the system.
Autoconfigure can accurately
configure the hardware only when there is no pending I/O.
In
addition, to use the Autoconfigure 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 Autoconf igure results can be
used as responses. You can also override the results of 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 AND 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,
the saved answer file always
overrides the Autoconfigured list.
If SYSGEN fails to report Autoconfigure results (described in Example
3-1) within one minute,
then Auioconfigure 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.

3-17

STRUCTURE AND CONCEPTS OF SYSGEN
Example 3-1:

Sample Autoconfigure Output

Processor Type:

Memory Size:

11/70

512. Kw)

Options:
Floating Point Processor (FPll)
Extended Instruction Set (EIS)
.Extended (22-bit) Addressing
Switch Register (SWR)
Display Register
Cache Memory
Parity Memory
Name

Vector

CSR

OKA

220

177404

OMA

RHA

210

224

0
2

RK05
RK05

0
1
2

RK06
RK06
RK07

0 0
0 1

TU77
TU77

RM03

MLllA

0
1
2
3

RP06
RP06
RP05
RP05

Remarks

172440

150

176300

RHC

204

176400

RHO

254

176700

264
214
200
270
060
???
310
314
324
340
350
360
???

Type

177440

RHB

DXA
OTA
LPA
LPB
YLA
YLB
YMA
YMB
YMC
YHA
YHB
YHC
YHD

Unit

177170
177342
177514
164004
177560
175610
170500
170510
170520
160020
160040
160060
160100

TM03
TM03

Dual access

Failed to interrupt

Example 3-2 lists all the remarks that may be output by
with the configuration information.

3-18

Autoconf igure

STRUCTURE AND CONCEPTS OF SYSGEN
Example 3-2:

Autoconfigure Remarks and Meanings

Remark

Meaning

Failed to interrupt

Either
the
specified
device
is
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, O_l).

Priority n

Autoconfigure 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.

???

See Failed to interrupt.

(in the vector field)

Sector interleaved

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
Autoconfigure option, SYSGEN asks a second question that allows you to
override the results of 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 Autoconfigure results and either enter different values or
press the RETURN key to input the Autoconfigure result.

3-19

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.
The only exception to this is Question 15 in the Target Configuration
Section. This question always appears to allow you to add or delete
devices from your configuration.
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 using 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 Autoconfigure
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
Autoconfigure 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
Autoconfigure, 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, but 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 finds only those RKOS
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 Q-BUS.
NOTE
Autoconf igure will run only on processors with memory
management
(mapped)
hardware.
Also, Autoconfigure
computes the line frequency of your processor only if
a KWll-P programmable clock is present.

3-20

STRUCTURE AND CONCEPTS OF SYSGEN
Table 3-4
Hardware Supported by Autoconf igure
Processors (with memory management hardware}
PDP-11/23
PDP-11/23-PLUS

22-Bit Addressing

Mi croPDP-11

(Autoconf igure reports the MicroPDP-11 as
an 11/2 3-PLUS)

PDP-11/24

18- and 22-Bit Systems

PDP-11/34
PDP-11/35

(Autoconfigure reports the 11/35 as an 11/40)

PDP-11/40
PDP-11/44
PDP-11/45
PDP-11/50

(Autoconf igure reports the 11/50 as an 11/45)

PDP-11/55

(Autoconf igure reports the 11/55 as an 11/45)

PDP-11/60
PDP-11/70
LSI-11/73
Mi croPDP-11/7 3
Mi croPDP-11/8 3
PDP-11/84
Processor/Memory Options
FP-11

FPP--Floating Point Processor

KE-llE

EIS--Extended Instruction Set

KE-llA/B

EAE--Extended Arithmetic Element
CIS--Commercial Instruction Set
FIS--Floating Instruction Set
(Continued on next page)

3-21

STRUCTURE AND CONCEPTS OF SYSGEN

Table 3-4 (Cont.)
Hardware Supported by Autoconf igure
KWll-P

Programmable Clock
Cache Memory
Switch Register
Display Register
Parity Memory

KWll-W

Watchdog Timer
1/0 Peripherals and Controllers

TAll Tape Cassette

RP04/05/06 Disk Drive

TU58 Cartridge DECtape

RK11/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

UDA50 (RA60/RA80/RA81) Controller
RC25 Controller
RQDXl (RD51/RX50) Controller
RQDXl (RD52/RX180) Controller

RXll/RXOl Diskette (first controller only)

RX211/RX02 Diskette (first controller only)

MLll Nonrotating Electronic Memory

LP/LS/LV/11/LNOl Line Printer
(Continued on next page)

3-22

STRUCTURE AND CONCEPTS OF SYSGEN

Table 3-4 (Cont.)
Hardware Supported by Autoconfigure
MM

TU16/45/77/TE16 Magnetic Tape Drives

TS11/TSV05/TU80 Magnetic Tape Drives

TM11/TU10/TE10/TS03

TK50 Streaming Cartridge Tape

PRll/PCll Paper Tape Reader

PCll Paper Tape Punch

RH11/RH70 MASSBUS Controller

DEUNA UNIBUS Ethernet Controller

DHll Asynchronous Terminal Interface

DLll-A/B Asynchronous Terminal Interface
(including DLV)

DLll-C/D/E Asynchronous Terminal Interface
(including DLV)

DLll-J Asynchronous Terminal Interface
(including DLV)

DLll-W Console Interface with line clock

DMll-BB Modem Controller for DHll

DHUll/DHZll Asynchronous Terminal Interface

DZll Asynchronous Terminal Interface
(including DZQ and DZV)

3-23

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 divided logically 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 Version 4.1 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 fewer
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 Version 4.2 host
system, set your directory to be [200,200], assign the logical
device SY:
to your baseline disk, and invoke SYSGEN as
follows:
>SET /UIC= [200, 200] ID
>ASN ddu:=SY:ID
(where ddu: is the baseline disk, RSXM38)
>MOU ddu: RSXM38 ID
>@SYSGEN ID
The host system must have a null device
generate an RSX-llM system successfully.

•

(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 Autoconf igure 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
Autoconfigure 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, MT, and MU 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 configured automatically you may
add devices that Autoconf igure 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 your 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:
•

Creates the resident driver data base file (SYSTB.MAC)

•

Creates a partial, unusable Executive prefix file (RSXMC.MAC)

•

Creates a saved answer file

•

Creates the Executive task-build file

•

Creates the full-duplex terminal driver task-build
you select the full-duplex terminal driver)

•

Creates the Executive and driver assembly command files

4-4

file

(if

DETAILS OF SYSGEN PHASE I

SETUP (Cont.)

However, when you perform a PREPGEN, SYSGEN does not:
•

Make logical device assignments

•

Delete files from previous SYSGENs

•

Assemble files

•

Create libraries

If you are using an RL01/RL02 distribution kit and you select this
option, the number of drives required for doing a system generation
depends on whether you will be chaining from Phase I to Phase II
(Question 15 in this section) and if the system generation will be
unattended. The following list explains what happens in the various
situations:
•

If you are chaining from Phase I to Phase II, two drives are
required for the PREPGEN--one for the RSXM38 disk and one for
the EXCPRV disk.

•

If you are chaining from Phase I to Phase II and the system
generation will be unattended, three drives are required--one
each for the RSXM38, EXCPRV, and PRVBLD disks.

•

If you want to chain from Phase I to Phase II but only two
drives are available, you will be instructed at the beginning
of Phase II to remove the EXCPRV disk from its drive and
replace it with the PRVBLD disk.

•

If you are not chaining from Phase I to Phase II and Phase I
will be unattended, or if Phase II will be unattended, two
drives are required.
At the beginning of each Setup Section,
you will be requested to mount the appropriate disk (EXCPRV
for Phase I and PRVBLD for Phase II).

If you respond No to this question, SYSGEN executes MCR
creates your system.

commands

and

* 3A. Do you want to create the assembly and build files on the SY:
device? [Y/N D:Y]
This question appears only if you answered Yes to Question 3
(Inhibit
MCR commands) and if you are using the RL01/RL02 distribution kit.
Your answer determines where SYSGEN will create the assembly and
task-build files.
If you answer Yes or take the default, the files
are created on SY:.
If you answer No, the files are created on NL:.
Creating the files on one of these pseudo devices helps recover
on the RSXM38 and EXCPRV disks.

4. Have you made a copy of the distribution kit?

space

[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 Updates.
4-5

DETAILS OF SYSGEN PHASE I

SETUP (Cont.)

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-llS 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.
SYSGEN does not save responses to the Peripheral Options Section
questions for
the ICR/ICS or DSS/DSR 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 fi~e 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.

4-6

file

type,

DETAILS OF SYSGEN PHASE I

SETUP (Cont.)

If you are using an incomplete saved answer file for input, SYS GEN
In that
issues a message indicating that the file may be incomplete.
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 memory
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.

answer
as

that

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

file

name

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 SYSSAVEO.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]:

(saved)
answers to
This option allows you to use previously defined
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.
4-7

DETAILS OF SYSGEN PHASE I

SETUP (Cont.)

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

Question

(Use

11. Use saved peripheral configuration? [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.
Note that if you answer No, it does not affect the input saved answer
file and does not permit you to change vectors or CSRs of previously
defined devices. Answering No permits you to change only the number
of controllers.
Respond No to add or delete controllers.
This question appears only if you responded Yes
saved answers) •

Question

(Use

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

Phas~

•

After the Target and Host Configuration Sections

•

After the Executive Options Section

e 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) •

4-8

Question

(Use

DETAILS OF SYSGEN PHASE I

SETUP (Cont.)

13. Skip End-of-Execution (EOX) breakpoints? [Y/N]:

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

(Inhibit

14. Clean up files from previous GENs? [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 only if you respond No to
MCR commands) •

Question

(Inhibit

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-llS system or if SYSGEN2.CMD is not in
directory [200,200] on the SY: disk.
Chaining is most useful when you are using a compl,ete saved answer
file for
input to both Phase I and Phase II.
In this case, you can
complete most of a SYSGEN unattended.

16. Enter device for EXCPRV disk when it is ready (dduu:) [D: DLl:] [S]:

Enter the device type and unit number (dduu:) for the drive containing
the files needed to assemble the Executive, drivers, and some MCR
modules during Phase I (EXCPRV).
This disk will be dismounted at the
end of Phase I.
SYSGEN appends the trailing colon if you omit it in your response.
This question appears only if you are using the RL01/RL02 distribution
kit.

4-9

DETAILS OF SYSGEN PHASE I

SETUP (Cont.)

17. Enter device for PRVBLD disk when it is ready (dduu:) [D: DL2:] [S]:

Enter the device type and unit number (dduu:) for the drive containing
the files needed to build the Executive, drivers, libraries, and
privileged tasks during Phase II (PRVBLD). SYSGEN mounts the device
if it is not the same as the one used for the EXCPRV disk.
SYSGEN appends the trailing colon if you omit it in your response.
This question appears only if you are using the RL01/RL02 distribution
kit and if you are chaining from Phase I to Phase II.

4-10

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION

4.3

TARGET CONFIGURATION SECTION

This section of questions defines the target processor type and the
options and peripheral devices included in the target system.
If you
are running SYSGEN on a Version 4.2 system and if you choose the
Autoconf igure 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/20*

11/44

11/73

11/03*

11/23

11/45

11/83

11/04*

11/24

11/50

11/84

11/05*

11/34

11/55

KXJll

11/10*

11/35

11/60

11/15*

11/40

11/70

LSI-11/73

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
MicroPDP-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 a
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-11

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 that you use to key in
data to the switch register.

•

Some newer processors have a keypad on the front panel instead
of toggles.

•

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

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

3. Memory size (in K-word blocks)

R:l6.-124. 0: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 minimum 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 size must be specified in 4K increments
unmapped system).

memory
(except

sizes
for

for

the

30K

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

Minimum

Maximum

Minimum

Maximum

LSI-11, 11/03

Not supported

11/04, 11/05

(Continued on next page)
4-12

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)

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

RSX-llS

PDP-11 Processor

Minimum

Maximum

Minimum

Maximum

11/10, 11/15

11/20

11/23, 11/24

1920

11/40 (no KT-11)

11/44

1920

11/70

1920

All others(l)

124

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

are

the

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 MicroPDP-11, 11/23, 11/23-PLUS,
11/24, 11/44, 11/70, 11/73, 11/83, or 11/84 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? [Y/N D:N]:

The K-series laboratory options are a set of
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 automat1callY--includes support for the Connect
to
Interrupt directive and ASTs (asynchronous system traps).

5. Extended arithmetic element (KEll-A/B EAE) present? [Y/N D:N]:

The extended arithmetic element
(EAEl 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.

PDP-11/20

4-13

and

unmapped

(no

KT-11

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION {Cont.)

6. Floating point processor (FPll) present? [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

KEFll-AA, FPF-11

11/34

FPFll-A

11/44

FPFll-F

11/45' 11/50,
11/55, 11/70

FPFll-C

11/60

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-14

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)

8. Extended instruction set (EIS) present? [Y/N D:NJ:

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

EIS Feature

PDP-11
Processor

EIS Feature

LSI-11

Optional

11/45

Standard

LSI-11/73

Standard

11/50

Standard

11/03

Optional

11/55

Standard

11/23

Standard

11/60

Standard

11/24

Standard

11/70

Standard

11/34

Standard

11/73

Standard

11/35

Optional

11/83

Standard

11/40

Optional

11/84

Standard

11/44

Standard

KXJll

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

Multiply

DIV

Divide

ASH

Shift arithmetically

ASHC

Arithmetic shift combined

XOR

Exclusive OR

SOB

Subtract 1 and branch if not equal to 0

RTT

Return from interrupt

MFPI

Move from previous instruction space

MTPI

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.

4-15

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION {Cont.)

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

Three

your

A response of O 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
divisible into 10000(10)

select

must

evenly

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, too.

10. Line frequency:

A- 60Hz B- SOHz [D:

[SJ:

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 Autoconfigure 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.
4-16

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)

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

processors
for those

14. Highest interrupt vector [O R:0-774 D:O]:

The response to this question specifies the highest interrupt vector
address.
If you respond with 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 (notably 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.

4-17

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)

15. Devices [S]:

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.
NOTE
If you chose the Autoconf igure option, you can add new
devices,
you
can
add
devices
not
found by
Autoconfigure, and you can exclude any devices already
found by Autoconfigure.
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 RASO 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 mnemonics
number of controllers) by entering a question mark (?).

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 neces.sary 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 4-2 the most recent response for duplicate

4-lS

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)
entries. For example, if your system includes two RKll controllers
and one TCll DECtape controller, the following sequence corrects an
incorrect 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)
(termin~tes input)

Table 4-2 lists the peripheral devices supported by RSX-llM:
Table 4-2
Peripheral Devices Supported by RSX-llM
Mnemonic

Device

Hardware Controller

Analog-to-Digital Converter

ADOl-D

Analog-to-Digital Converter

AFCll

Laboratory Peripheral Subsystem

ARll

Card Reader

CRll/CMll-E

TU60 Cassette

TAll

RP04/05/06 disk packs

RH11/RH70

TU58 DECtape II

DLll

RFll disks

RFll

RKOS/J/F cartridge disk

RKll

RLOl disk drive
RL02 disk drive

RLll/RLVll
RL21/RLV21/RLV12

RK06/07 cartridge disk

RK611/RK711

RP02/03 disks

RPll/RPllC

RM02/03/05 disks and
RM80 fixed media

RH11/RH70
RH70

RS03/04 fixed-head disks

RH11/RH70

TU56 DECtape

TCll

RA60 removable media
RA80/81 fixed media
RC25 fixed/removable media
RDSl fixed media
RD52 fixed media

UDA50/KDA50-Q
UDASO/KDASO-Q
RC25
RQDXl
RQDXl
(Continued on next page)

4-19

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.}

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

Device

Hardware Controller

RD53 fixed media
RX50 diskette
RX180 IBM-compatible diskette

RQDX3
RQDX1/RUX50
RUX50

RXOl diskette

RXll

RX02 diskette

RX211/RXV21

MLll Nonrotating Electronic Memory

RH70

Graphics Display Processor and Scope

VT11/VS60

Industrial Control Subsystem

ICR/ICSll

Industrial Control Subsystem

DRS/DSll

Laboratory Peripheral Accelerator

LPAll-K

Line Printer

LAll/LPll/LSll/LVll

Laboratory Peripheral Subsystem

LPSll

TU45/TU16/TE16/TU77 magnetic tapes

RH11/RH70/TM02/TM03

TS11/TSV05/TU80 magnetic tapes

TSll

TS03/TU10/TE10 magnetic tapes

TMll/TMAll/TMBll

TK50 streaming cartridge tape

TQK50

Paper Tape Punch

PCll

Paper Tape Reader

PCll/PRll

Universal Digital Controller

UDCll

Interprocessor Link

DAll-B

UNIBUS Ethernet Controller

DEUNA

Interprocessor Link

DLll-E

Interprocessor Link

DMCll-E/DMRll

Synchronous Interface

DPll

Synchronous Interface

DQll

Synchronous Interface

DUll
(Continued on next page)

4-20

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)

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

Device

Hardware Controller

Synchronous Interface

DUPll

Asynchronous Terminal Interface

DHll

Asynchronous Terminal Interface

DJll

Asynchronous Terminal Interface

DLll/A/B/C/D/E/J/W

Asynchronous Terminal Interface

DHUll/DHVll

Asynchronous Terminal Interface

DZll/DZQll/DZVll

Pseudo devices:
CL

Console Listing Pseudo Device

N/A

Console Output Pseudo Device

N/A

Library Default Pseudo Device

N/A

Null Device

N/A

System Defau-lt Pseudo Device

N/A

Terminal Input Pseudo Device

N/A

NOTE
If you intend to perform future
using your target system, you
pseudo device.

system generations
must include the NL

If you are generating RSX-llM, SYSGEN forces YL into the system.
Normally, you must specify any pseudo devices if you want 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:, OF:, DK:, DL:, OM:, DP:, DR:, OS:, DX:, DY:,
DU:, or EM:. Otherwise, you must explicitly select NL:
(which is
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 pseudo device.

4-21

DETAILS OF SYSGEN PHASE I

TARGET CONFIGURATION (Cont.)

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 conside~ 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-22

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

configuration

1. Is a line printer available? [Y/N]:

This option allows you to
listings will be directed.

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.

Yes

If you respond Yes, Question 1 (List Executive map?} of the
Task-Build Section is not asked.

Executive

If you want to save the listings but not spool
this question (see Question 5).

respond

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

and

them,

3. 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 and
Micro/RSX 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} to direct SYSGEN
not to produce assembly listings.

4-23

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/RK07 or RL01/RL02 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 RL01/RL02 distribution kit, the map device must be
the device where the PRVBLD disk will be mounted in Phase II.
If you
are chaining from Phase I to Phase II,
the default is the device
specified for Question 17
(for the PRVBLD disk).
If you are not
chaining, the default is the device on which EXCPRV is currently
mounted.
If the PRVBLD disk will be mounted on another drive, you
should respond to this question with the device on which PRVBLD will
be mounted.
If you are using either an RK06/RK07 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 directory
[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-24

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 and Micro/RSX Executive Reference Manual
some of these directives and Executive options.

describes

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

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

For details on

DBMS~ll,

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~ll

•

Memory management (PLAS) directives

•

Send/Receive By Reference directives

•

Asynchronous system traps (AST)

•

System-controlled partition support

•

The following system directives:

bucket locking and placement control

Get Partition Parameters (A)
Get Task Parameters (B)
Send/Receive (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 want to include the services
described in the RSX-llM/M-PLUS 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-25

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

If you selected DBMS-11 support, SYSGEN

automatically

includes

this

option~

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.

System

Options

Section

3. Bucket locking (file sharing) and placement control? [Y/N]:

If Files-11 ACP (FCP) is included in your system either by default or
because you selected it in Question 2, SYSGEN asks this question to
provide the necessary Executive and FCP support.
If you do not choose this support, file sharing and placement
are not included in your system.

control

This option adds approximately
Executive.

200(10)

words

the

size

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.

* s. 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.
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 uses 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.

4-26

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

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.SK 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 II 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.

words

7. Memory management (PLAS) directives? [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.
The following lists the memory management directives:
Attach Region

Get Mapping Context

Create Address Window

Map Address Window

Create Region

Receive By Reference

Detach Region

Send By Reference

Eliminate Address Window

Unmap Address Window

4-27

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

Memory management directives are restricted to use on mapped systems.
Therefore, the question does not appear for unmapped systems.
If you select DBMS-11 (Question 1) , SYSGEN includes memory
directives by default and does not ask this question.

management

If you do not select memory management 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 directives add approximately 1000(10)
the Executive.

words

8. Send/Receive By Reference directives? [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 memory
this question does not appear.

management

directives,

9. Get Mapping Context directive? [Y/N]:

The Get Mapping Context directive retu~ns 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).

support

for

memory

10. Address checking? [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.

includes

Address checking is recommended
debugged application system.

unless

you

are

running

fully

11. I/O rundown? [Y/N]:

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

4-28

all

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

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

•

Break-through 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.

RSX-llS

system.

13. ANSI Magtape ACP? [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 magnetic
tape ACP support, SYSGEN automatically includes AST support.
ANSI magnetic tape ACP support increases the size of the Executive by
If you select this option, SYSGEN task
approximately 40(10)
words.
builds FllMSG
{the magnetic tape error processor) , MTAACP
{the
magnetic tape Ancillary Control Processor), and MAG {the magnetic tape
ACP control task) •
In addition,
if you select ANSI magnetic tape support, SYSGEN
generates
a
second
library
called ANSLIB.OLB.
This library
{ANSLIB.OLB) contains an FCS that communicates with the ANSI magnetic
tape ACP.
This FCS also supports the FCS big buffering feature.
See
the RSX-llM/MPLUS I/O Operations Manual for more information.
If you respond
included.

Yes,

support

for

4-29

the

Send/Receive

directive

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

If you do not select ANSI magnetic tape support, the system library,
SYSLIB.OLB, contains an FCS that does not communicate with the ANSI
magnetic tape ACP.
RSX-llS systems do not support ANSI magnetic tapes.
not appear.

The question does

14. Do you want on-line formatting (FMT) or diagnostic QIOs? [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.

The question

does

15. Loadable device drivers? [Y/N]:

This option
dynamically
except the
ICS/ICR, and

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.

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) i 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.

4-30

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

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.
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:
•

The ANSI magnetic tape ACP support

•

The Floating Point Processor (FPll)

DBMS-11

•

The LA driver (LPAll-K)

•

The K-series device support routines

selected

Respond Yes if you want AST support.
If you respond No, the
input character ASTs.
Section.)

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

18. 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/M-PLUS and
Micro/RSX 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.

automatically

includes

19. Task termination and device not ready messages (TKTN)? [Y/N]:

This option directs the system to generate on the inptit device and on
the console "Device not ready" and task termination messages when
these conditions occur.
You must select this option if you want Postmortem Dump
(PMD)
snapshot dump (SNAP$) support or Logging of Task Abort support.

4-31

and

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

20. Power fail recovery? [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.

the

Specify

Power

Recovery

AST

21. Install, request, and remove on exit? [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.

The question

does

22. Large (20K) Executive? [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 8K the maximum size of privileged tasks
that map the I/O page.
If you are generating an
appear.

unmapped

system,

4-32

this

question

does

not

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

23. Logical device assignment? [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 Logger 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:

DK:

DR:

DX:

MM:

DB:

DL:

DS:

DY:

MS:

DD:

DM:

OT:

EM:

MT:

OF:

DP:

DU:

MU:

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

The question does

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 drivers.
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).

4-33

the

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

26. Include routine $GTWRD? [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 routine:-- ~
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).

(you

27. Include routine $PTWRD? [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 routine.
~
~ ~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).

(you

28. Disk writecheck? [Y/N]:

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

If your target system configuration does
devices, the question does not appear.

not

include

any

NOTE
If you include write-checking 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 write-checking function after each
write operation.
For more information on the MCR SET
/WCHK command, see the RSX-llM/M-PLUS MCR Operations
Manual.

4-34

these

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

This is how the write-checking 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 write-checking function fails (that is,
if the
copies compared are not the same), the driver retries the original
write operation and performs another write-check until the maximum
retry count is reached (at which time the system issues the hard error
message IE.WCK).
RSX-llS does not support disk write-checking.
appear.

The question

does

not

29. Software write-lock support? [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

write-locking

Disks:
DB

Magnetic Tape:
MM

DECtape:
DD

Cassette:
CT
Support for software write-locking adds approximately 40(10) words
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/M-PLUS and
Micro/RSX Debugging Reference Manual 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.

4-35

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

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.

the

rotate

PDP-11/45,

11/50,

circular

11/55,

and

32. Include support for communications products (such as DECnet)? [Y/N]:

This option allows you to include DECnet or DPM/DPM-PLUS support.
Refer to the DECnet or DPM/DPM-PLOS 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

When you respond Yes, SYSGEN also automatically includes:
•

FCP support

•

AST (asynchronous system trap) support

•

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
4-36

for

the

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

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
(e.g.,
remote
terminal
support,
llS
task
loading/upline
dumping,
etc.)
require special
consideration during SYSGEN.

32A. Include Network Command Terminal support? [Y/N]:

This question appears only if you chose support for DECnet in Question
32 (include communications products?).
If you respond Yes, the full-duplex terminal driver supports modem
hangup ASTs,
out-of-band character ASTs, switch characters, extended
I/O, and internal I/O completion.

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]:
minimize
Shuffler

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

to
The

If you respond Yes to this question, SYSGEN builds the
(SHF) and includes it in your system image.

Shuffler

task

The Shuffler is not available 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
RSX-llM/M-PLUS System Management Guide.

4-37

Shuffler,

refer

the

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

NOTE
If you intend to include the Shuffler in your
system,
it
should
not
be
installed
system-controlled partition.

target
in
a

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 Batch and Queue Operations
Manual 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 available only 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 event flags, refer
RSX-llM/M-PLUS and Micro/RSX Executive Reference Manual.

the

37. Enter code for system directives

This option includes system directives.
by an associated letter code:

Each directive

A-Get Partition Parameters

G-Get Sense Switch

B-Get Task Parameters

H-Set System Time

C-Send/Receive

I-Stop-bit

4-38

indicated

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

D-Alter Priority

J-Specify Requested Exit AST

E-Extend Task

K-Parent/offspring tasking

F-Connect to Interrupt Vector

L-Parent/offspring
with chaining

tasking

Enter a
·Enter an asterisk (*) to display the table of directives.
percent sign
(%) to include all directives. Enter a period (.) to
terminate the question.
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 (.).
Refer to the RSX-llM/M-PLUS and Micro/RSX Executive
for descriptions of the d1rect1ves.

Reference

Manual

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 magnetic tape 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
tasking
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
directives.
If you select the Extend Task directive, SYSGEN automatically includes
checkpointing support.
This does not apply if you are generating an
RSX-llS system.
If you select the Specify Requested
automatically includes AST support.

Exit

AST

directive,

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

4-39

SYSGEN
does

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

38. Number of pre-allocated QIO packets [D R:0.-15. 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/O packet is
required, the Executive removes one from this list.
If the list is
empty, the Executive allocates the packet from dynamic memory
(a
significantly slower operation). When an I/O 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, determine 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 0 through 15(10), indicating the number of
packets to be preallocated.
The default is 5. When your system uses preallocated QIO packets
(that is, when you specify any value greater than zero), it takes
advantage of QIO speed optimization.
Enter O to exclude preallocated QIO
optimization.

packets

well

QIO

speed

39. Size of data transfer vector in words [D R:0.-33. 0: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.
Enter a number in the range 0 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
select this default.

33(10).

4-40

generally

advisable

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

If you specify a data transfer vector size that is greater than 0 but
less than 5, SYSGEN forces that value to 5.
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.
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. D:S]:

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.
I/O-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 the 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.

range

(time
1

and

through

Enter 0 if you do not want this option.
The default is 5.
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. 0:150.):

Round-robin scheduling affects a specified range of priority classes.
A typical range is 1 through 150(10). The permissible range is 1
through 250(10).
4-41

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

This entry provides the highest priority
class
round-robin scheduling. The default is 150(10).

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 through x(lO), where
highest priority class entered in response
default is 1.
This question appears only if you select
option.

the

x is equal to
to Question 41.
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.
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, within 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 ~ime a task is :ead into memory, the Executive initializes the
swapping priority in the task header to the value +S$$WPR (for
example, +5 if you specify 5 as the swapping priority in Question 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).

4-42

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

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 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.

44. Swapping priority [D R:l.-20. D:S.]:

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 through 20(10).
recommended that you enter the default swapping priority of 5.
This question
swapping.

appears

only

you

selected

Executive-level

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

4-43

SYSGEN

is
disk

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

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% 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).

The

the

permissible

MCR
range

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. D: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).
Specify the number of seconds between printer-not-ready messages.
entry of 0 suppresses the messages altogether.

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

the

4-44

value

other

than

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

47. 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
messages. An entry of 0 suppresses the messages altogether.

ready"

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

the

minimum

value

the

entry

48. 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.
Enter the CSR address of the device. The normal device is the console
terminal, which has a CSR address of 177564. This is the default
device.
Enter 0 to suppress this option.

If you specify a value other than
160000 through 177700(8).

o, it

can

only

the

range

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.

4-45

and

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

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 and Micro/RSX Task Builder Manual, particularly to the
information on using the /AL (allocate) 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.
If you
tasks
if you
error

Executive

cannot

select checkpointing, SYSGEN includes support for nonresident
(see Question 4). SYSGEN automatically includes checkpointing
select Executive level disk swapping (Question 43), support for
logging
(Question 24), or the Extend Task directive (Question

37) •

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

you

chose

DECnet

50. 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.
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-llS systems.

51. Crash dump analysis:

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

If you do not select the dump analysis option and a system failure
occurs, it may not be possible for you to capture vital data on the
state of the system at failure time. The RSX-llM Guide to Writing an
I/O Driver describes the PANIC dump routine. The-RS'X-ITM/M-PLUS and
MICro/RSX Crash Dump Analyzer Reference Manual describes CDA
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.

-rn

Enter A if you want the PANIC dump routine.

4-46

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

Enter B (the default) if you want Crash Dump Analyzer
It is recommended that you select CDA support.
If you select A, SYSGEN does not ask Questions 52,
does ask Question 55.

(CDA)

53,

and

support.
54,

but

If you select B, SYSGEN asks Questions 52, 53, and 54, but not 55.

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

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

Dump

Analyzer

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

message

selected

(Crash

53. Enter CDA memory dump device mnemonic (ddu:)

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

selected

[S R:3-4]:

(Crash

Dump

Analyzer

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

DU (RAGO, RX50, RC25-removable)

If you choose a device that is not on the first controller of a
multiple-controller disk, you must specify the physical unit number of
the device rather than the logical device unit number.
When the
system crashes,
the notification message also uses the physical unit
number of the device.
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/RA81,
the RD51/RD52/RD53, and the
fixed-disk portion of the RC25).
If possible, avoid using your system device as the crash dump
because CDA overwrites the contents of the crash dump device.

4-47

device

DETAILS OF SYSGEN PHASE I

EXECUTIVE OPTIONS (Cont.)

S4. Enter CDA memory dump device CSR (0 R:l60000-177700 D:l74500]:

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

selected

(Crash

Dump

Analyzer

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

176700

172510

176500

177170

177404

177170

174400

172440

177440

172522

176700

172522

177342

174500

The allowable DU:-type dump devices are the RAGO, the
removable-disk portion of the RC25.

RX50,

and

the

SS. 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.

S6. RT-11 emulation support? [Y/N]:

This option allows you to include RTEM support.
documentation for details.

4-48

Refer to your RTEM-11

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
that 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. Terminal driver desired (A/B/C/D,

I/O

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

•

Break-through 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-49

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

•

Automatic carriage return/line feed (Question 4)

•

Write with CTRL/O cancellation (Question 7)

•

Hold-screen mode (Question 14)

•

Transparent read/write (Question 15)

•

Settable case conversion for input (Question 16)

•

Read with no echo (Question 18)

•

Read with special terminator (Question 19)

•

Terminal-host synchronization (Question 21)

•

user terminal input buffering (Question 22)

•

Variable-length terminal input buffering (Question 23)

•

LA30P support (Question 24)

•

Parity enable and sense support

4-50

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)

•

ANSI-standard escape sequences

•

ANSI-defined advanced editing functions

•

Loadable (soft) character fonts

•

Block mode

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

automatically
not ask this

If you have not chosen a mapped system and loadable driver support,
you must 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 seconds. Valid time-out range is 0 through 255(10) seconds.
Enter 0 to inhibit the unsolicited
full-duplex terminal driver.

input

timeout

feature

for

the

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

3. 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
terminal, you should respond Yes.

LA180S

This option adds approximately 24(10) words to the terminal driver.

4-51

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)

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.

s. Task checkpointable during terminal input? [Y/N]:

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

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 driver.
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
displays only 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.

4-52

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)

7. 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.
If you respond Yes, a privileged task can issue a break-through 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 th1s 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 break-through 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 respona Yes, the terminal driver recognizes and treats
sequences
as
line terminators for all solicited input
read-pass-all or read-with-special-terminator requests.

4-53

escape
except

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)

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.
and want the
If you selected the full-duplex terminal driver
(C)
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.

should

include

this

terminal

driver

12. Set multiple characteristics? [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.

should

include

this

terminal

driver

13. Get terminal driver options? [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-54

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)

14. 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.
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.

16. Settable case conversion for input? [Y/N]:

This question appears only if you responded A to Question t.
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

4-55

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.)
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 approximately 128(10)
words to the full-duplex
terminal driver and approximately 185(10) words to the half-duplex
terminal driver.

18. Read with no echo? [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,
10.RVB, and
IO.RPR, and specify that the driver not echo terminal
input.
This option adds approximately 48(10) words to the terminal driver.

19. Read with special terminator? [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 erases a character on a CRT
terminal screen when you press the RUBOUT or DELETE key.
The driver
echoes the rubouts or deletions as backspace-space-backspace.
This option adds approximately 64(10) words to the terminal driver.

21. 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.

4-56

DETAILS OF SYSGEN PHASE I

TERMINAL DRIVER OPTIONS (Cont.}

This option adds approximately 84(10) words to the terminal driver.
NOTE
If your system includes a VT50 terminal with the
copier option or an LA120 or VTlOO with a baud rate
greater than 1200, you must respond Yes to this
question.

22. User terminal input buffering? [Y/N]:

This question appears only if you responded A to Question 1.
The terminal driver normally receives characters and stores the
characters in the Executive address space until 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.

23. 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 request.
The largest buffer can be 255(10) bytes
long.
This option adds approximately 24(10) words to the terminal driver.

24. 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-57

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-58

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/M-PLUS I/O
Operations Manual.)
If you respond Yes, SYSGEN creates ANSLIB.OLB as it would have if you
had chosen ANSI magnetic tape 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, or LS 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 PRVBLD
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.
The different libraries are necessary to
contain the different routines:
Device

Library

AR/LS

(1, l]LPSLIB.OLB

[ 1, 1 ] I CSL IB • 0 LB

[l, l] ISLIB.OLB

[l,l]LPALIB.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-59

the

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)

2A. Include support for the IPll Industrial I/O Subsystem? [Y/N]:

The IPll Industrial I/O Subsystem is a combined software and hardware
package used for process control and monitoring in the industrial and
manufacturing environment.
The subsystem consists of an RSX device
driver
(IPDRV)
and a set of FORTRAN-callable interface routines used
to interface to a variety of hardware I/0 modules,
including digital
sense interrupt, change-of-state, digital output, digital-to-analog
converter, and analog-to-digital converter modules.
Refer to the IPll Subsystem Software
information on installing the software.

Installation

Guide

for

2B. Include support for IPll powerfail? [Y/N]:

The IPll subsystem can optionally save the context of digital outputs
and digital-to-analog converters upon system power fail and restore
them when the power is restored.
Answering Yes to this question
causes the inclusion of the Executive support needed for this feature
and adds approximately 40(8) bytes to the size of the Executive.
This
support must be taken in order to have power-fail support in the IPll
driver itself.

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 magnetic tape
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 Question 7 of the Executive Options Section
earlier in Phase I.
This question does not appear for RSX-118 systems or if you did not
select FCP support in Question 2 of the Executive Options Section.

4-60

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)

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 1 imi ts.
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 just over
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.
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 on both mapped and unmapped
systems.

RSX-llM

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.5K
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/O requests require only a
few additional
I/0
The MIDDLE FCP generally
operations with this version of FCP.
provides the best performance without using undue amounts of
memory.

4-61

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)

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.
MIDDLE FCP is the default FCP for mapped RSX-llM systems.

The

Enter a response of C to choose this FCP.
D.

LARGE (FCPLRG)
This FCP provides the maximum performance.
It has no overlays,
thus it has no system overhead or I/O 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.
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.

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 directory
(1,54] for mapped systems and (1,50] for unmapped systems.

•

During Phase II, SYSGEN does not ask if you want to edit
SYSVMR.CMD.
Instead, it 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) •

4-62

the MOUNT command
RSX-llM/M-PLUS MCR

simplifies
Operations

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)

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.

s. Build Post Mortem Dump (PMD)?

[Y/N]:

This option lets you specify whether or not you want to have the Postmortem Dump (PMD) task built during Phase II.
The RSX-llM/M-PLUS and
Micro/RSX Task Builder Manual describes the PMD task.
This question does not appear for RSX-llS systems.

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 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 allows you to build the
serial despooler. See the RSX-llM/M-PLUS Batch and Queue Operations
Manual for details on the non-Queue Manager-prfn"FS"pooler.
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 Command Language Manual for further information on DCL.

4-63

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)

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)

system
• Asynchronous
Options Section)

(Question

traps

exit

(Question

the

Executive

Task Parameters directive (Question 37
• Get
Options Section)

the

Executive

Parent/offspring tasking with Chaining
• Executive
Options Section)

(Question

•

The ·stop-bit directives (Question 37 of the Executive
Section)

•

The Specify Requested Exit AST (Question 37 of
Options Section)

the

Options
Executive

This option is not available for RSX-llS, unmapped systems, or RSX-llM
systems without multiuser protection.

9. Enter the number of user-written CLis [D

R:<O-MAX>

D:O]:

A CL!
(command line interpreter)
is a task that receives all
unsolicited input from user terminals. The function of a CL! is to
interpret and execute the unsolicited input as commands. The commands
are predefined by the CLI.
(MCR is the system CL! 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(10).
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 CL!) 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 CL! support.
If you select DCL as an option,
SYSGEN automatically includes alternate CL! support.
Alternate CL! support is not available for RSX-llS, unmapped
or RSX-llM systems without multiuser protection.

systems,

10. 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.
4-64

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)

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-in 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 CL! 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.
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 available only 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

HEL

RMD

BYE

PMT

SHUTUP

The name must be from one through six alphanumeric characters. A name
with fewer 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]:

If you respond Yes, SYSGEN includes support for the
Software
Performance Monitor
(SPM-llM)
for RSX-llM systems. Refer to your
SPM-llM documentation for details.

4-65

DETAILS OF SYSGEN PHASE I

SYSTEM OPTIONS (Cont.)

To include SPM-llM support, you must have the following hardware:
•

Mapped system

•

Expansion space for the programmable clock provided
SPM-llM package

•

Extended Instruction Set (EIS)

with

the

If you have not previously included the following options in your
target system, SYSGEN automatically includes them when you respond Yes
to this question:
•

Asynchronous system
Section)

traps

(Question

•

The Get Task Parameters
Options Section)

•

The Extend Task
Section)

•

The Get Partition Parameters directive (Question 37, Executive
Options Section)

directive

Send/Receive directive
• The
Section)

(Question

to a system
• Checkpointing
Executive Options Section)

17,

Executive

(Question
37,

37,

checkpoint

Options

37,

Executive

Options

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-66

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
that
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:

Possible entries are defined as:
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, select 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
because they are always resident.
The full-duplex terminal driver is always loadable.
This
parameter does not appear for the full-duplex terminal
driver.
If you override the default (specify an 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-67

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

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

Enter parameterl, parameter2, ••• parametern for:
where parameters 1, 2, and 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.
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.

4-68

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

AD controller O [D:l76770]

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 [D:l34,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

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.
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.

4-69

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

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
CSR address of' the DRll-K (the default value is 170420). If you do
not enter the default DRll-K CSR address, the acceptable range is
160000 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 (0: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.
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 TAll
You must enter values within the acceptable ranges.

4-70

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

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/RP05/RP06 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

60 through 774(8)

CSR

160000 through 177700(8)

Number of drives

1 through 8 ( 10)

Unit number of first drive

0 through 7(10)

Off set recovery

O or NO

Subsequent RHll or RH70 controllers default only the
the first drive (0).

unit

number

NOTE
You can specify offset recovery support only for the
first DB controller.
If you include support for the
first controller, you automatically include offset
recovery
support
for
subsequent
controllers.
Likewise, if you exclude support, you exclude offset
recovery support for subsequent controllers.
After you enter the parameters for each RHll or RH70 controller
included in your system, SYSGEN immediately prompts for the drive
type.

DB Contr 0 unit 0 is an RP04/RP05/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.

4-71

for

each

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

DD controller 0 (0: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 I I
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
2 {10) •

through

OF controller 0 (0: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.

controller 0 (0:220,177404]

Enter the interrupt vector address {the default value is 220), the CSR
address {the default value is 177404), and the number of RK05 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.
The acceptable range for the number of RK05 drives is 1 through 8(10).
NOTE
An RK05F is a fixed-media RKOS drive equivalent to two
removable RK05 drives.
Specify every RK05F 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.

4-72

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

DL controller 0 [D:l60,174400]

Enter the interrupt vector address (the default value is 160), the CSR
address
(the default value is 174400), and the number of RL01/RL02
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 number of
through 4(10).

RL01/RL02

disk

drives

DL Contr 0 unit 0. is an RL01/RL02 [D: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

DM controller 0 [D: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/RK07 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/RK07 drives is
8 (10) •

through

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 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/RK07
drives.

4-73

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)

NOTE
You can specify offset recovery support only for the
first controller.
If you include support for the
first RK611 controller, you automatically include
offset recovery support for subsequent controllers.
Likewise, if you exclude support, you exclude offset
recovery support for subsequent RK611 controllers.

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

This question immediately follows parameter specification for each OM
controller.
You must specify the type of drive.
Enter either RK06
(the default response) or RK07.
SYSGEN repeats this question for each device unit specified
controller.

for

each

DP controller O [0:254,176714)

Enter the interrupt vector address (the default value is 254), the CSR
address (the default value is 176714), and the number of RP02/RP03
disk drives (there is no default for this parameter)
for the first
RPll controller.
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 number of
through 8(10).

RP02/RP03

disk

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.

4-74

for

each

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

DR controller 0 [0:254,176700,,0,0]

Enter the interrupt vector address
(the default is 254), the CSR
address
(the
default
is
176700),
the
number
of
RM02/RM03/RM05/RM80/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

60 through 774(8)

CSR

160000 through 177700(8)

Number of drives

1 through 8(10)

Unit number of first drive

0 through 7(10)

Off set recovery

O or NO

Subsequent RHll or RH70 controllers default only the
the first drive (0).

unit

number

NOTE
You can specify offset recovery support only for the
first DR controller. If you include support for the
first controller, you automatically include offset
recovery
support
for
subsequent
controllers.
Likewise, if you exclude support, you exclude offset
recovery support for subsequent controllers.

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), RMOS, RM80, or RP07.
SYSGEN repeats this question for each device unit specified
controller.

4-75

for

each

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)

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/RS04 disk
drives (there is no default value for this parameter), and the
physical unit number of the first RS03/RS04 drive (the default value
is 0) for the first RHll or RH70 controller.
The acceptable range for the number of RS03/RS04 drives is
8 ( 10) •

through

If you do not use the default values, the acceptable ranges are:
vector

60 through 774(8)

CSR

160000 through 177700(8)

Number of drives

1 through 8 ( 10)

Unit number of first drive

0 through 7(10)

Subsequent RHll or RH70 controllers default only the
the first drive (0).

unit

number

OS Contr 0 unit O. 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 0 [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 DT 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.
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.

4-76

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

DU contr O [D:154,172150]

Enter the interrupt vector address (the default value is 154), the CSR
address (the default value is 172150), and the number of DU:-type
(RA60/RA80/RA81/RC25/RD51/RD52/RX50/RX180) disk drives
(there is no
default value for this parameter).
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 four
RD51/RX50 units.
However, SYSGEN does not accept an answer of fewer
than three units
(one RDS! fixed-media disk drive and two RXSO
diskette drives).
If you respond with either one or two units, SYSGEN
forces three units into the system.
NOTE
An RD51/RXSO configuration requires one dedicated DU
controller.
No other DU devices
(for example, an
RA81) can be on that controller.
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.

4-77

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)

DX controller O [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
through 2(10).

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
through 2(10).

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.
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.
Note that the RXV21, the RX02 controller for the LSI-11 bus, does not
support 22-bit addressing because it cannot perform direct-memory
access for the total range of addresses on a 22-bit system. Using the
RXV21 controller on a 22-bit LSI-11 bus sytem will crash the system.

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

4-78

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

If you do not use the default values, the
follows:

acceptable

Vector

60 through 744(8)

CSR

160000 through 177700(8)

Number of MLll drives

1 through 8(10)

ranges

are

the

following

GR controller 0 [D:,172000,,l]

RSX-llM supports the graphics display
restrictions:

subsystem

with

•

There is 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.
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.

4-79

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

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
space.
Consult
representative if the
required CSR address
LPAll CSR group.

assigned from floating vector
your
DIGITAL
Field
Service
location is unknown.
Also, the
is that of the first word of the

If you include an 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 and Questions
2A and 2B in the System Options Section for the IPll Subsystem
questions.

LP controller 0 [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.
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 print only 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.

4-80

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)

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.
Table 4-3
Standard Line Printer Devices
Option

Printer 1

Column Width

Character Set

Lines/Minute

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

You can connect a maximum of eight line printers to the system.
{Continued on next page)

4-81

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

Table 4-3 {Cont.)
Standard Line Printer Devices

Option

Pr inter 1

Column Width

Character Set

Lines/Minute

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

You can connect a maximum of eight line printers to the system.

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.
NOTE
If you select KMC support, all printers must use the
KMC.
Those that do not use the KMC cannot operate.
You must respecify KMC parameters for each additional
line printer controller question asked by SYSGEN.

LS controller

o [D:,170400,,,o,o,o,No]

The clock vector address for the LPSll controller is assigned from the
floating vector space starting at 300.
It is located at an off set 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.
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) •

4-82

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

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 O through 85. Enter 0 to disable bandwidth
filtering.
If your system includes the D/A option, enter the number of channels
in the range O 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/O 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, SO, 80, 100, 125, 200, 250, 400, 500,
625, 1000, 1250, 2000, or 2500).

MM controller 0 (0:224,172440]

Enter the interrupt vector address (the default value is 224), the CSR
address
(the default value is 172440), and the number of TU45, TU16,
TE16, or TU77 magnetic tape 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 O unit O formatter [D R:0-7 D:O]

Each MM controller supports up to eight formatters.
Each TM02/03
formatter supports up to eight 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/TM03 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/TM03 formatter (tape controller) on the RHll or RH70.
The
default is O.
If you do not use the default response, the acceptable
range is 0 through 7(10), or 0 through 3(10) for TU77 drives.
SYSGEN repeats this question for each device unit specified
controller.

4-83

for

each

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)

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.
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 TSll controllers do not default the vector and
assignments.
You must enter a value within the acceptable range.
The TSll, TSV05, and TU80 magnetic
devices.

tape

drives

are

valid

CSR

MS:-type

MT controller 0 [0:224,172522)

Enter the interrupt vector address (the default value is 224), the CSR
address (the default value is 172522), and the number of TS03, TUlO,
or TElO magnetic tape drives (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.
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
MT
controllers.
You must enter values, within the acceptable ranges, for
the vector and CSR assignments as well as the number of tape drives.

MU controller 0 [0:260,174500)

Enter the interrupt vector address (the default value is 260) and
CSR address (the default value is 174500) for the controller.

the

If you do not enter the default value 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
MU
controllers.
You must enter values, within the acceptable ranges, for
the vector and CSR assignments.

4-84

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)

PP controller 0 [D:74,177554]

Enter the interrupt vector address (the default value is 74)
and the
PCll
CSR address
(the default value is 177554)
for the first
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.
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 PCll controllers do not default the vector and
assignments. You must enter values within the acceptable ranges.

CSR

PR controller 0 [D: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.
Subsequent PCll/PRll controllers do not default vector and
assignments.
You must enter a value within the acceptable range.

CSR

OD controller 0 [D: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.
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 a 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

4-85

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

•

Digital sense

•

1/0 counter

•

Single-shot output

Modules of the same type must occupy consecutive locations within the
UDCll.
Thus,
if there are seven analog input modules and the first
module starts at slot O, then the last analog input module must be at
slot 6.
Module types cannot overlap, but unassigned slots are
permitted.
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).
SYS GEN 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 O [D:l24,172414]

Enter the interrupt vector address (the default value is 124) and
the
CSR address
(the default value is 172414)
for the first DAll-B
interface.
If you do not enter the default for the vector and CSR assignments,
the acceptable range is 60 through 774 for the vector and 160000
through 177700 for the CSR.
Subsequent DAll-B interfaces do not default the vector and
~ssignments.
You must enter values within the acceptable ranges.

CSR

XE controller O [D:,,O]

Enter the interrupt vector address, the CSR address, and the number of
DEUNA Ethernet controllers in the target configuration.

4-86

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

The interrupt vector address for the DEUNA controller is assigned from
floating vector space starting at 300. Thus, there is no default
vector address for the DEUNA. 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 is assigned from floating address space starting at
160010.
Thus, there is no default CSR assignment for the DEUNA.
Enter a CSR address in the range 160010 through 177700. Consult your
DIGITAL Field Service representative if the CSR address is unknown.
The default number of DEUNA Ethernet controllers is none (0).

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.
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.

4-87

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

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.
The first DPll line defaults to a half-duplex line (H).
specify a full-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 DPll lines default only the half-duplex parameter (H).
must enter values for the vector and CSR assignments.

You

XQ controller 0 [D:,,H,E,C]

The vector address for the DQll synchronous line interface is assigned
from the floating vector space starting at 300. Thus, there is no
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.

4-88

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

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. 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.
Consult
your
DIGITAL Field Service
representative if the CSR address is unknown or see Appendix E.
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.

4-89

You must

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)

YH controller O [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).
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.

YJ controller O

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.

4-90

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

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 or see Appendix E.
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.
Each DJll can service up to 16 asynchronous serial lines.
Enter the
total number of lines by specifying the highest line number in the
range 0 through 15 (10) (0 indicates one line, 15 indicates 16 lines).
SYSGEN repeats this question for each DJll specified.

YL controller 0 [D:60,177560, NO]

This question always appears because you must include at least
DLll (YL) asynchronous line interface in an RSX-llM system.

one

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.
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.
Consult
your
DIGITAL Field Service
representative if the CSR address of additional lines is unknown or
see Appendix E.

YV controller 0 [,,,]

This question appears only if you specified a DHUll or DHVll
asynchronous line interface
(YV)
and have a Q-BUS processor (for
example, an LSI-11, PDP-11/03, PDP-11/23, or PDP-11/23-PLUS).

4-91

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS {Cont.)

The DHVll is the Q-BUS equivalent to the UNIBUS DHll
(refer to the
previous question about YH) • Unlike the DHll, the DHVll does not have
DMll-BB modem support. Also, the DHVll baud rates differ from those
of the DHll.
The DHUll is the UNIBUS equivalent of the DHVll.
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) •
The interrupt vector address for the DHUll/DHVll is assigned from
floating vector space starting at location 300. Thus, there is no
default vector assignment for the DHUll/DHVll.
Enter a vector address
in the range 300 through 770. Consult your DIGITAL Field Service
representative if the interrupt vector address is unknown.
The CSR address for the DHUll/DHVll is assigned from the floating
address space starting at 160010.
Thus, there is no default CSR
assignment for the DHUll/DHVll.
Enter a CSR address in the range
160010
through
177700.
Consult
your
DIGITAL Field Service
representative if the CSR address is unknown.
The DHUll 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 (0 indicates one line, 15 indicates 16 lines).
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 DHUll/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 want to include modem support, specify
the baud rate for all DHUll/DHVll remote lines.
Acceptable answer
speeds
(baud rates)
are 75, 110, 134.5, 150, 300, 600, 12_00, 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 DHUll/DHVll specified.
NOTE
If you include a DHUll/DHVll in your system, SYSGEN
automatically includes the full-duplex terminal driver
(Question 1, Option C,
Terminal
Driver
Options
Section} •

YZ controller 0 [D:,,,O]

This question appears only if you specified a
asynchronous
line multiplexer.
Note that
parameter does not appear.

4-92

DZll/DZQll/DZVll
(YZ)
the Loadable/Resident

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

The interrupt vector address for the DZll/DZQll/DZVll is assigned from
floating vector space starting at 300. Thus, there is no default
vector assignment for the DZll/DZQll/DZVll. 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 DZll/DZQll/DZVll is assigned from floating
address space starting at 160010.
Thus, there is no default CSR
assignment for the DZll/DZQll/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 DZQll can service up to four asynchronous lines. Enter the total
number of lines by specifying the line number in the range O through
4.
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/DZQll/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 want to include modem support,
specify only one baud rate for all DZll/DZQll/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 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 DZll/DZQll/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.

answer

the

2. 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.

4-93

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

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. 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 ICS-11.
repeats this question for each IC controller specified.

SYSGEN

6. 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 repeats
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(decimal).

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(decimal).

4-94

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

10. Restore module status on power and error recovery?

This question appears only if the system includes a
D/A converter, or I/O counter module.

bi~stable

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.

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 on line).
Enter a value in the range O through SOOO(decimal).
The ICS/ICR subsystem consists of six distinct modules:
•

D/A converter

•

Single-shot output

•

Bi-stable output

•

Digital sense

•

Digital interrupt

•

I/0 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:

4-95

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

17. Number of 1/0 counter modules in this ICS/ICR:

18. Expanded comments for DSS/DRS questions?

Expanded comments provide explanatory text that helps you
DSS/DRS questions.

answer

the

19. Number of DRS-11 modules:

Enter the number of DRS-11 digital output modules in the range 0
through 16 (decimal). 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.

774.

23. Number of DSS-11 digital input modules:

Enter the number of DSS-11 digital input modules. Note that the total
number of DRS-11 and DSS-11 modules cannot exceed 16. Thus, the
acceptable range for this response is O through 16 (decimal) •
minus
the number of DRS-11 modules specified in Question 19. If you enter
O, SYSGEN omits Questions 24, 25, and 26.

24. DSS-11 CSR address:

Enter a value for the CSR address in the range 160000 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.

4-96

774.

DETAILS OF SYSGEN PHASE I

PERIPHERAL OPTIONS (Cont.)

26. Task activation from unsolicited interrupts?

This option permits the DSS/DRS driver to initiate a task when the
driver receives unsolicit¥d input.
The option provides support for
tasks to link to inter~upts and obtain activation
data
upon
initiation.

4-97

DETAILS OF SYSGEN PHASE I

Example 4.-1

Annotated Terminal Output from SYSGEN Phase I

>@SYSGEN 0

>;
>; RSX-llM V4.2 BL38

System Generation PHASE I -- Version 2.10

>;
>; 12-JUN-85 13:46:03
>; Big disk distribution kit
>;
>*
>*
>*
>*

3.
5.
6.
8.

Do you want to inhibit execution of MCR commands (PREPGEN)? [Y/NJ: y
Are you generating an unmapped system? [Y/NJ: n
Use an input saved answer file? [Y/NJ: n
Do you want a Standard Function System? [Y/NJ: y

>; Standard Function System - Phase I SYSGEN

9. Name of output saved answer file [D: SYSSAVED.CMDJ

[SJ: (fl@ 6)

>; Phase I output saved answers created in file DUO: [200,200JSYSSAVED.CMD;l

>* 15. Chain to Phase II after Phase I completes? [Y/NJ: y 0

>;
>; Target configuration

>;
>* 1. Processor Type
[D: ll/34J
[SJ: 11/23
>* 2. Does processor have a switch register? [Y/N D:NJ:
>* 3. Memory size (in K-word blocks) [D R:l6.-1920. D:l6.J: 128.
>* 6. Floating point processor (FP-11) present? [Y/N D:NJ:
>* 7. Floating instruction set (FIS) present? [Y/N D:NJ:
>* 8. Extended instruction set (EIS) present? [Y/N D:NJ: y
A- 60 Hz
B- 50 Hz
[D: AJ [SJ:
>* 10. Line frequency:
>* 11. KWll-Y Watchdog timer support? [Y/N D:NJ:
>* 12. Memory parity support? [Y/N D:N]: y

>;
>;
>;
>;
>;
>;
>;
>;

The response to the following question specifies the highest interrupt
vector.
If you respond with a value less than or equal to 400, SYSGEN
will assign the value associated with the highest interrupt vector
specified during the Peripheral Section.
Therefore, if your system
will include devices that are not specified during the Peripheral
Section and which have vectors above 400 (devices such as K-series and
certain communication devices), specify that value in the next question.

>;
>* 14. Highest interrupt vector [O R:0-774 D:O]:
>;
For device configuration: "*" Prints device table, "·" Terminates inquiry
>;
"?" Prints current configuration
(6)
>;
Enter devices and number of controllers for devices which require drivers
>* 15. Devices [S]: * 0

>;
Device codes for A/D and industrial/laboratory devices:
>;
>;
>; AD- ADOl-D A/D Converter
>; AF- AFCll A/D Converter
>; AR- ARll Laboratory Subsystem
>; IC- ICRll/ICSll Industrial Control Subsystem

>; IS- DRSll/DSSll Industrial Control Subsystem
>; LA- LPAll Laboratory Subsystem
>; LS- LPSll Laboratory Subsystem
>; UD- UDCll Universal Digital Controller
>;
Device codes for Interprocessor communication devices:
>;
>;
>; XB- DAll-B Interprocessor Link
>; XE- DEUNA Unibus Ethernet Controller
>; XL- DLll-E Interprocessor Link

4-98

DETAILS OF SYSGEN PHASE I

Example 4-1 (Cont.)

Annotated Terminal Output from SYSGEN Phase I

>; XM- DMCll-E/DMRll Interprocessor Link
>; XP- DPll Synchronous Interface
>; XQ- DQll Synchronous Interface
>; XU- DUll Synchronous Interface
>; XW- DUPll Synchronous Interface
>;
>;
Device codes for unit record devices:
>;
>; CR- CRll/CMll-E Card Reader
>; GR- VT11/VS60 Graphics Subsystem
>; LP- LAll/LPll/LSll/LVll/LNOl Line Printer
>; PP- PCll Paper Tape Punch
>; PR- PCll/PRll Paper Tape Punch and Reader
>;
>;
Device codes for disk devices:
>;
>; DB- RP04/RP05/RP06 Disk Drive
>; 00- TU58 Cartridge DECtape II
>; OF- RFll Fixed Head Disk Drive
>; DK- RK03/RK05 Disk Drive
>; DL- RL01/RL02 Disk Drive
>; OM- RK06/RK07 Disk Drive
>; DP- RP02/RP03 Disk Drive
>; DR- RM02/RM03/RM05/RM80 Disk Drive
>; OS- RS03/RS04 Fixed Head Disk Drive
>; DT- TU56 DECtape
>; DU- RA60/RA80/RA81/RC25/RD51/RD52/RD53/RX50 Disk Drive
>; DX- RXOl Floppy Disk Drive
>; DY- RX02 Floppy Disk
>; EM- MLll Non-Rotating Electronic Memory
>;
>;
Device codes for Magnetic tape devices:
>;
>; CT- TU60 Cassette Tape Drive
>; MM- TU16/TU45/TU77/TE16 Magtape Drive
>; MS- TS11/TU80/TSVOS Magtape Drive
>; MT- TU10/TE10/TS03 Magtape Drive
>; MU- TKSO Magtape Drive
>;
Device codes for terminal interface devices:
>;
>;
>; YH- DHll Asynchronous Terminal Interface
>; YV- DHUll/DHVll Asynchronous Terminal Interface
>; YJ- DJll Asynchronous Terminal Interface
>; YL- DLll-A/-B/-C/-D/-E/-J/-W Asynchronous Terminal Interface
>; YZ- DZll/DZVll 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 device is specified without the number of controllers, the number
>;
of controllers defaults to 1.
>;
>;
Example: DK,DM=2,YL,NL.
>;
>;
>* 15. Devices [S]: dl,du,mu,lp,yl=2,yz. 0
>;
>; Processor:ll/23
Memory Size:l28K,Mapped
System:RSX-llM
>;
Extended Instruction Set
>;
Parity Memory
>;
>;

4-99

DETAILS OF SYSGEN PHASE I

Example 4-1 (Cont.)

Annotated Terminal Output from SYSGEN Phase I

>; Host configuration

>;
>*
>*
>*
>*

1.
3.
4.
5.

Is a line printer available? [Y/NJ: y
Does the listing/map device have at least 120 columns? [Y/N]: y
Assembly listings device (ddu:) [D: "NL:" J [SJ: sy:
Map device for Executive and device drivers (ddu:) [D: SYO:] [S]:

>; Executive Options

>;
>;
>;
>;
>;

Cancel selective marktime support will be included
Answer Y(ES) if the following support is desired

>* 30. Executive Debugging Tool (XDT)? [Y/N]: y
>* 32. Include support for communications products (such as DECnet)? [Y/N]: n
Checkpointing support will be included
>;
>* 53. Enter CDA memory dump device mnemonic (ddu:) [S R:3-4]: muO:
>* 54. Enter CDA memory dump device CSR [O R:l60000-177700 D:l74500J:
>* 56. RT-11 emulation support? [Y/N]: n

>;
>;

>; Terminal driver options

>;
>; The Full Duplex Terminal Driver will be included.
>;
>; System Options
>;
Answer Y(ES) if the following support is desired
>;
>;
>* 2A. Include support for the IPll Industrial I/O Subsystem? [Y/N]: n
>* 11. What name would you like to give your system [D: RSXllM] [S R:0-6J:
>* 12. Do you want SPM-11 support? [Y/NJ: n

>;
Thinking •••
>; End of Executive option generation at 13:49:32 on 12-JUN-85

>;
>; Peripheral configuration
>;
>;
Parameters appearing in square brackets "[ ••• J" can only be
specified for the first controller of a particular device.
>;
>;
Parameters appearing in parentheses "( ••• )" only need be specified
if
the indicated option is present on the target system.
>;
>;
>;
The
default for loadable drivers has been set to *TRUE*.
To override this setting 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: LP
>;
>; Enter [L/R,] vector, CSR, printer option
>;
(,[KMC timeout count <O=no KMC>, KMC vector, KMC CSR]) for:
>;
>* 16. LP controller 0 [D: 200,177514,LA180,0,300,160130J

[SJ: O

>; Disks: DL, DU

>;
>; Enter [L/R,J vector, CSR, number of drives for:
>;

, , 1 0
[SJ: rl02

>* 3. DL controller O [D: 160,174400]
>* 53. Contr 0 unit O. is an RL01/RL02 [D: RLOlJ

[S]:

[SJ: ,,3

3. DU controller 0 [D: 154,172150J

4-100

DETAILS OF SYSGEN PHASE I
Example 4-1 (Cont.)

Annotated Terminal Output from SYSGEN Phase I

>;
>; Tapes: MU

>; Enter [L/R,) vector, CSR for:

1. MU controller 0 [D: 260,174500)

>;
>; Non-physical (pseudo) devices:

[SJ:

co, TI, CL, LB, SY

>; Terminal interface devices: YL, YZ

>;
>; Enter vector, CSR, E=DLll-E modem support/NO=no for:
>;
>* 21. YL controller O [D: 60,177560,NO)
>* 21. YL controller 1 [D: ,,NO)

[SJ:

[S]: 300,176500

>; Enter vector, CSR, highest line number <O to 7> [, answer speed] for:

>* 24. YZ controller 0 [D: ,160100,,300]

[S]: 310,,3

>;
>;
>; 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? [Y/N]: N

>;
>;
>; Prepare for task building

>;
>;
>; Clean-up extraneous object files

>;
>;

>; End of SYSGEN phase I at 15:14:56 on 12-JUN-85
>; -- Chaining to [200,200]SYSGEN2.CMD

>;
>@SYSGEN C)

>;
>;
>;

>; RSX-llM V4.2 BL38

System Generation PHASE I -- Version 2.10

>;
>; 13-JUN-85 16:29:37
>; Big disk distribution kit

>*
>*
>*
>*
>*

>;
>;
>;
>;

3.
4.
S.
6.
7.

Do you want to inhibit execution of MCR commands (PREPGEN)? [Y/N]:
Have you made a copy of the distribution kit? [Y/N]: Y
Are you generating an unmapped system? [Y/N]:
Use an input saved answer file? [Y/N]: Y
Name of input saved answer file [D: SYSSAVED.CMD] [S]:

Phase I input saved answers
created on 12-JUN-85 at 14:52:56
by SYSGEN version 2.10
are from file DUO: [200,200]SYSSAVED.CMD;l
9. Name of output saved answer file [D: DUO: [200,200]SYSSAVED.CMD] [S]:

>;
>; Phase I output saved answers created in file DUO: [200,200]SYSSAVED.CMD;2

>;
>* 10. Use saved host configuration? [Y/N]: Y
>* 11. use saved peripheral configuration? [Y/N]: Y
>* 12. Skip end of section (EOS) breakpoints? [Y/N]: Y

4-101

DETAILS OF SYSGEN PHASE I

Example 4-1 (Cont.)

Annotated Terminal Output from SYSGEN Phase I

>* 13. Skip end of execution (EOX) breakpoints? [Y/N]: Y
>* 14. Clean up files from previous GENs? [Y/N]: Y
>* 15. Chain to Phase II after Phase I completes? [Y/N]: Y
>SET /UIC=[l,l]
>PIP [l,20]RSXBLD.CMD;*/DE/NM
>PIP [l,24]RSXBLD.CMD;*/DE/NM,TTDRVBLD;*
>PIP [l,50]SYSVMR.CMD;*/DE/NM,[l,54]SYSVMR;*
>PIP [11,20]*.0BJ;*/DE/NM,*.UDC;*,*.ICR;*,*·IDS;*,*·PCS;*
>PIP [11,24]*.0BJ;*/DE/NM,*.UDC;*,*•ICR;*,*·IDS;*,*·TTY;*,*·PCS;*
>PIP [ll,30]*.LST;*/DE/NM1[11,34]*.LST;*
>PIP [ll,10]RSXMC.MAC;*/DE/NM,ICTAB;*,[200,200]SGNPARM.CMD;*
>PIP [200,200]RSXBLD.CMD;*/DE/NM,TTDRVBLD;*
>PIP SY: [ll,20]RSXASM.CMD;*/DE/NM,RSXDRVASM;*,[12,20]MCRSETASM;*
>PIP SY: [ll,24]RSXASM.CMD;*/DE/NM,RSXDRVASM;*,[12,20]MCRSETASM;*
>PIP SYO: [ll,24]RSXASM.CMD;*/DE/NM,RSXDRVASM;*,[12,24]MCRSETASM;*
>PIP /FR
DUO: has 199226. blocks free, 37986. blocks used out of 237212.
Largest contiguous space = 114488. blocks
6962. file headers are free, 1137. headers used out of 8099.
>SET /UIC=[ll,10]

>;
>; Target configuration

>;
Memory Size:l28K,Mapped
System:RSX-llM
>; Processor:ll/23
>;
Extended Instruction Set
>;
Parity Memory
>;
>;
>; Host configuration
>;
>; Executive Options
>;
Checkpointing support will be included
>;
>;
>;
>; Terminal driver options
>; The Full Duplex Terminal Driver will be inlcuded.
>;
>; System Options
>;
>;
Thinking •••
>;
>; End of Executive option generation at 16:31:03 on 13-JUN-85
>;
>; Peripheral configuration
>;
Parameters appearing in square brackets " [ ••• J
can only be
>;
specified for the first controller of a particular device.
>;
Parameters appearing in parentheses"( ••• )" only need be specified
>;
if
the indicated option is present on the target system.
>;
>;
The
default for loadable drivers has been set to *TRUE*.
>;
To override this setting 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: LP
>;
>; Disks: DL, DU
>;
>; Tapes: MU
1

4-102

DETAILS OF SYSGEN PHASE I

Example 4-1 (Cont.)

Annotated Terminal Output from SYSGEN Phase I

>;
>; Non-physical (pseudo) devices: co, TI, CL, LB, SY
>;
>; Terminal interface devices: YL, YZ

>;
>SET /UIC=[l,24] 1 Creating TTDRVBLD.CMD
>SET /UIC=[ll,10]
>; End of interrupt vector area has been set to 400

>;
>;
>; Create Executive build files ~
>;
>PIP RSXMC.MAC=SYO:RSXMCO.MAC/AP
>ASN SY:=LB:

>;
>; Start of Executive assembly at 16:34:21 on 13-JUN-85
>SET /UIC=[ll,24]
>MAC @SY:RSXASM

>; End of.Executive assembly at 17:27:53 on 13-JUN-85

>; Start of MCR (subset) assembly at 17:27:53 on 13-JUN-85
>SET /UIC=[l2,24]
>PIP *.OBJ;*/DE/NM
>MAC @SY:MCRSETASM

>;
>; End of MCR (subset) assembly at 17:36:40 on 13-JUN-85

>;
>;
>; Start of device drivers assembly at 17:36:40 on 13-JUN-85
>SET /UIC=[ll,24]
>MAC @SY:RSXDRVASM

>;
>; End of device drivers assembly at 18:23:19 on 13-JUN-85
>ASN =LB:

>;
>; Prepare for task building
>;

>SET /UIC=[l,24]
>PIP RSXllM.OBS=[ll,24)*.0BJ
>PIP TTDRV.OBJ=[ll,24]*.TTY
>LBR RSXllM/CR:l00.:1010.:128.=RSXllM.OBS
>LBR TTDRV/CR:30.:380.:64.=TTDRV
>PIP [l,24]MCR.OBJ/NV/NM=[l2,24]*.0BJ
>PIP (12,24]*.0BJ;*/DE/NM
>PIP /NV=[ll,lO]RSXBLD.CMD
>PIP (11,lO]RSXBLD.CMD;*/DE/NM

>;
>; Clean-up extraneous object files

>PIP RSXllM.OBS;*/DE/NM,TTDRV.OBJ;*,(11,24]*.0BJ;*,*·TTY;*

>;
>; End of SYSGEN phase I at 18:26:40 on 13-JUN-85
>; -- Chaining to [200,200]SYSGEN2.CMD

>;)

4-103

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

Invoke SYSGEN and begin answering Phase I questions.

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.

Answer Yes if you want to chain from Phase I to Phase II
(If
you decide to chain, SYSGEN automatically proceeds to Phase
II from Phase I).

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
avoid making errors in your final response.

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

This is an example of how you can include default values in
your response to Peripheral Options questions. The commas
(,,) indicate that the default vector and CSR addresses were
selected for the DL controller.

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 prefix 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-104

CHAPTER 5
DETAILS OF SYSGEN PHASE II

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.2 Task
Builder (TKB) to task build its files.
The Version 4.2 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

This file is the Executive build file.
It 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

This file is the Executive object library file.
It
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

This is a parameter file containing Indirect symbol
definitions.
SYSGEN creates SGNPARM.CMD during Phase
I based on your responses to the questions.

5-1

DETAILS OF SYSGEN PHASE I I

TTDRVBLD.CMD

This file 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.
However, SYSGEN inputs these files to Phase II only 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 into 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 I I

Before beginning Phase II of SYSGEN,
following:
•

make

sure

you

have

done

the

If you generate your system from an on-line Version 4.2 host
system,
set your directory to be [200,200], assign the pseudo
device name SY: to your baseline disk, and invoke SYSGEN2.CMD
as follows:
>SET /UIC= [200, 200) IBIB
>ASN ddu:=SY:IBIB
{where ddu: is the baseline disk, RSXM38)
>MOU ddu: RSXM38 ~
> @SYSGEN2 IBIB

If you generate your system from a stand-alone host system,
• bootstrap
the baseline system (see Section 4.1) and then
invoke SYSGEN2.CMD as follows:
> @SYSGEN2 IBIB

5-2

DETAILS OF SYSGEN PHASE II

Figure 5-1 shows the processing steps that take
Phase II.
INPUT

place

ACTION

SAVED ANSWERS
EXPLICIT RESPONSES
EXECUTIVE, DRIVER,
AND MCR SUBSET OBJECT
FILES FROM PHASE I

..........
.,...... ...

TASK-BUILD THE
EXECUTIVE, DRIVERS,
AND PRIVILEGED TASKS

during

SYSGEN

OUTCOME

....... ....

.,...........

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

s.2
*

SETUP SECTION
1. In what UIC is SGNPARM.CMD if not <uic>? [SJ:

Enter the directory containing the file SGNPARM.CMD. SYSGEN replaces
<uic> with the directory from which you invoked Phase II of SYSGEN.
SYSGEN creates SGNPARM.CMD during Phase I in the same directory from
which you invoked Phase I.
Enter a different directory to override
this default; otherwise, press the RETURN key.
If you followed the
instructions in Section 4.1, your directory 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 directory corresponding to the directory from which you
invoked Phase I of SYSGEN.
If you are chaining to Phase II,
the response to this question
defaults to the directory 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 II, 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
• Does not create loadable driver task-build .CMD files
• Does not create SYSVMR.CMD

• Does not invoke an editor for modifying files
When y_ou perform a PREPGEN, SYSGE,N does create a saved answer file.
If you respond Yes and if you are using an RL01/RL02 distribution kit,
SYSGEN will mount the build files disk after you enter the drive
containing the disk
(Question 7) •
The build files disk in the
RL01/RL02 kit is PRVBLD.
See Question 2A in the Setup Section of
Phase I for more information.

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.

* 2A. Do you want to create the build files on the SY: device? [Y/N D:YJ
This question appears only if you answered Yes to Question 2 (Inhibit
MCR commands), you are not chaining from Phase I to Phase II, and you
are using the RL01/RL02 distribution kit.
Your 'answer determines where SYSGEN will create the task-build files.
If you answer Yes or take the default, the files are created on SY:.
If you answer No, the files are created on NL:.
Creating the files on one of these pseudo devices helps recover
on the RSXM38 and PRVBLD disks.

3. Use an input saved answer file?

space

[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
initializatipn 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, the 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.

5-5

DETAILS OF SYSGEN PHASE II

SETUP (Cont.)

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.

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 it 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.
SYSGEN proceeds directly to subsequent sections without
stopping.
This question appears only 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 ~o Quesfion 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.

5-6

DETAILS OF SYSGEN PHASE II

SETUP (Cont.)

7. Enter device for PRVBLD disk when it is ready (ddu:)

[D: DLl:]

[SJ:

To answer this question, enter the device type and unit number
(ddu:)
of the drive on which the PRVBLD disk should be mounted. The default
response is the drive specified in response to Question 17 in the
Phase I Setup Section.
This question appears only if you are using an RL01/RL02 distribution
kit and if you are not chaining from Phase I. SYSGEN mounts the
PRVBLD disk on the device you specify.
If you are chaining to Phase II from Phase I, this question does not
appear, and SYSGEN will mount the PRVBLD disk on the device that you
specified in response to Question 17 of the Phase I Setup Section.
SYSGEN always dismounts the PRVBLD disk at the end of Phase II.

5-7

DETAILS OF SYSGEN PHASE II

EXECUTIVE 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(10)-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 lists RSXllM.MAP only.
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 want 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>? [SJ:

Enter the directory containing the file SGNPARM.CMD. SYSGEN replaces
<uic> with the directory from which you invoked SGNBLDDRV.CMD. Enter
a different directory 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, and provides a means of communicating
between Phase I and the other phases of SYSGEN. SYSGEN creates this
file in the directory corresponding to the directory from which you
invoked Phase I of SYSGEN.

2. Enter device for <label> disk when it is ready (ddu:) [D:

<default>] [SJ:

To answer this question, enter the device mnemonic and unit number of
the drive containing the PRVBLD disk.
(SYSGEN replaces <label> with
the volume name of the appropriate disk.)
This question appears only if you are using an RL01/RL02
kit. SYSGEN replaces <label> with PRVBLD.

distribution

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 (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 size of your tasks.
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 directory [1,34] for mapped systems or [1,30] for unmapped systems
must exist on the volume.
The default output device for the task maps is NL:
5-9

(the null device).

DETAILS OF SYSGEN PHASE II

LOADABLE DRIVER TASK-BUILD (Cont.)

4. 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

5. Driver 2-character device mnemonic [SJ:

To answer this question, enter a two-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 ~T 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(10)-word boundary.
After all the drivers are successfully
through Question 7), 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 ~nd then to
task build them again. When you reinvoke Phase II, you should not use
an input saved answer file (Setup Section, Question 3).
You can determine the size of a driver by locating the line "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.

5-10

DETAILS OF SYSGEN PHASE II

LOADABLE DRIVER TASK-BUILD (Cont.)

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, YV, and YZ) •
If you selected the full-duplex
terminal driver
in Phase I,
the
full-duplex terminal driver has been task built already. 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> is
the two-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/RP05/RP06).
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(10)-word boundary.

5-11

DETAILS OF SYSGEN PHASE II

PRIVILEGED TASK-BUILD

5.5

PRIVILEGED TASK-BUILD SECTION
1. Map device for privileged tasks (ddu:)

[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 the directory
[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

[O 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
in 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 during 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(10)-word blocks for the GEN partition
and that you plan to include a 14K task partition (PAR14K) of which
GEN is an 8K subpartition.

5-12

DETAILS OF SYSGEN PHASE II

PRIVILEGED TASK-BUILD (Cont.)

If the target system has fewer 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(10)-word blocks for the GEN partition
and that GEN is an BK partition.
The base address of SYSPAR starts on a 32(10)-word boundary.

4. SPLPAR's base address in 32-word blocks [O 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
re-created 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 a 110 baud rate
(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 b.e 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 of the RSX-llM/M-PLUS
System Management 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 8K words, but it can
usually be made smaller.
TTPAR contains ~ode plus a private buffer pool, which is
allocated in 20-word(decimal) blocks for typeahead 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)

5-15

DETAILS OF SYSGEN PHASE I I

SYSTEM VMR (Cont.}

where:

•

is the size of TTPAR in decimal words

is the code size of the driver (from the line "TASK IMAGE
SIZE" in [11, 34]T'l1DRV.MAP)

is the number of terminals in the system

is the average number of
given time

If you
loads
you do
delete

I/O

requests

pending

any

selected loadable drivers, creates partition DRVPAR and
all loadable drivers built during Phase II into it.
If
not want to load all drivers,
edit SYSVMR.CMD and
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 10300(octal) bytes for a system with FCPMIN and
12000(octal) bytes for a system with FCPSML. The length-of
SYSPAR for nonmultiuser systems with full-duplex terminal
driver support is 11700(octal) bytes.
The length of SYSPAR
for all other cases is lOlOO(octal) bytes.

•

If you selected an FCP other than FCPMIN
partition FCPPAR.

•

Creates partition GEN
of memory) •

•

Installs tasks built during Phase II.

•

If you selected direct access to device registers for ICS/ICR,
UDCll,
or DSS/DRS devices, creates the respective device
common, which overmaps the I/0 page.

FCPSML,

(from the end of last partition

creates
to

top

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 16K to 24K system, the lack of adequate
memory prevents SYSMVR.CMD from creating PAR1,4K (the partition used by
MAC, TKB, and ICP). Note that for unmapped systems, SYSVMR does not
create driver partitions.
5-16

DETAILS OF SYSGEN PHASE II

SYSTEM VMR (Cont.)

devPAR
SPLPAR
(optional)

1100,1120

SYS PAR

1000
GEN

400
Executive

0
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(octal) bytes.

•

Creates partition SYSPAR. The base address of SYSPAR is the
base acdress specified as your response to Question 3 of the
Privileged Task-Build Section.
The length of SYSPAR is
lOOOO(octal) bytes for a system with FCPMIN and 12000(octal)
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
ICS/ICR, UDCll, or DSS/DRS device, creates the respective
device common, which overmaps the I/O page.

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.

5-17

DETAILS OF SYSGEN PHASE II

SYSTEM VMR (Cont.)

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
For 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.

partition SYSPAR.
The base address of SYSPAR is the
• Creates
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.

5.6.1

•

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
ICS/ICR,
UDCll, or DSS/DRS device, creates the respective
device common, which overmaps the I/O page.

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
Version 4.2 of VMR.
In an on-line environment, SYSGEN cannot tell
which version of VMR is available on your on-line system.

5-.18

DETAILS OF SYSGEN PHASE II

SYSTEM VMR (Cont.)

Therefore, if you invoked SYSGEN on an on-line system, you must:
1.

Assign the logical device LB:

to the baseline disk

Set your directory to be the target directory
(that is,
[1,54] for mapped systems or [1,50] for unmapped systems)

Install VMR Version 4.2

Invoke VMR and use SYSVMR.CMD

You may accomplish these steps by entering
after Phase II completes execution:

the

following

commands

>ASN (ddu:)=LB:lBITJ
>SET /UIC=[l,54]fil'.fl
>INS ddu: $VMRfil'.f)
>VMR @SYSVMR fil'.f)
where ddu:

is the device mnemonic of the baseline disk.

Using VMR to Create Partitions for RMS-11 Libraries

5.6.2

If you want to create the partitions for the RMS-11 resident library
(or libraries)
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 directory [1,34] or from the sample VMR SET
commands contained in [l,2]STARTUP.CMD.
the partition RMSRES •
Note
• Create
partition
depends
whether
on

that the size of this
you intend to use the
full-function RMS RES library or the subset library RMS RES SUB
(which supports sequential and relative file organizations
only) •
SET /MAIN=RMSRES:base:size:COM filD

•

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 filD

5-19

DETAILS OF SYSGEN PHASE I I
Example 5-1:

Annotated Terminal Output from SYSGEN Phase I I

>;
>; End of SYSGEN phase I at 15:14:56 on 12-JUN-85 0
>; -- Chaining to [200,200]SYSGEN2.CMO
>;
>;
>; RSX--llM V4. 2 BL38

System Generation PHASE II -- Version 2.11

>;
>; 12-JUN-85 15:14:56
>;
>;
>; Big disk distribution kit SYSGEN version 2.10 for RSX-llM BL38
>;
>; Continuation from SYSGEN PHASE I done on 12-JUN-85 at 15:14:49
>;
>; SYSGEN assumes that the map disk is already mounted in SYO: with

>; UFO [ 1, 3 4 ] •

>;
>;
>;
>; Standard Function System - Phase I I SYSGEN
>;
>;
>; Phase I I output saved answers created in file DUO: [200,200JSYSSAVED.CMD;l
>;
>;
>; Library build
>;
>;
>; Executive task build
>;
>* 1. List Executive map? [Y/N]: y
>;
>; System image creation
>;
>;
>; Full duplex terminal driver task build
>;
>;
>; Loadable driver task build
>;
>* 4. Build all selected loadable drivers into DRVPAR? [Y/N]: Y
>;
>; Common block task build
>;
>; Build the ANSLIB flavor of the FCS resident library common
>;
>;
>; Creating the task build .CMO and .ODL files in SY: [1,24]
>;
>;
>; Privileged task build
>;
>;
>; Note that the following tasks will be built for your system:
>;
INS
PMT
BOO
OMO
FCPMDL
ICP
INI
>;
QMGCLI QMGPRT LPP
QMG
DCL
MOU
MCR
>;
LOA
UNL
FllMSG MTAACP SAV
TKTN
UFO
>;
PMD
RMD
BYE
HEL
BRO
SHF
ACNT
>;
SHUTUP ACS
ERRLOG
ELI
RCT
>;
>;
>;

5-20

DETAILS OF SYSGEN PHASE II
>*
>*
>*

1. Map device for privileged tasks {ddu:) [D: NL:] [S]: SY:
5. Pause to edit any task build .CMD or .ODL files? [Y/N]: N
6. Delete task build .CMD and .ODL files after building? [Y/N]: N

>;
>;
>; It is assumed that [l,l]FCSRES.STB is an ANSLIB version of the FCS
>; resident library

>;
>;

>; Creating the task build .CMD and .ODL files in SY: [1,24)

>;
>;

>; System VMR

1. Edit SYSVMR.CMD? [Y/N]: N

>; An alternate version of SYSLIB.OLB, the system object library, was
>; created to provide support for ANSI magtape/FCS big-buffering {which
>;you selected in Phase I). You may want to rebuild DMP, FLX, PIP, and
>; VFY in Phase III to use ANSLIB.OLB.
Note, however, building 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 requirements. You may want to rebuild
>; tasks in Phase III to link to the FCS resident library.
>;
>; When SYSGEN finishes, boot in your target system, and save the system with a
>; bootstrap. For example:

>;
>;
>;
>;

>BOO [l,54]RSX11M
XDT: 38

>;
XDT>G
>; RSXllM V4.2 BL38

>;
>;
>;
>;
>;

>TIM 12:00 15-JUN-85
>SAV /WB

>; RSXllM V4.2 BL38 128.K
>;
>RED DR:=SY:
>;
>RED DR:=LB:
>;
>MOU DR:RSXM38
>;
>@DR: [l,2]STARTUP

MAPPED

>;
>;
>;
>;
>;
>; End of SYSGEN phase II at 15:19:32 on 12-JUN-85

>;
>@ <EOF>

>;
>;
>;
>; End of SYSGEN phase I at 18:26:40 on 13-JUN-85 f)
>; -- Chaining to [200,200]SYSGEN2.CMD

>;
>SET /UIC=[200,200]

>;
>; RSX-llM V4.2 BL38

System Generation PHASE II -- Version 2.11

>; 13-JUN-85 18:26:42

5-21

DETAILS OF SYSGEN PHASE II
>;
>;
>; Big disk distribution kit SYSGEN version 2.10 for RSX-llM BL38

>;
>; Continuation from SYSGEN PHASE I done on

13-JUN~85

at 18:26:39

>;
>; SYSGEN assumes that the map disk is already mounted in SYO: with
> ; UFD [ 1, 3 4 ] •

>;
>;
>INS SY: [l,54]TKB.TSK;l/TASK= ••• TKL

>;
>;
>;
>;
>;

>;
>;

Phase II input saved answers
created on 12-JUN-85 at 15:15:05
by SYSGEN version 2.11
are from file DUO: [200,200]SYSSAVED.CMD;l

>; Phase II output saved answers created in file DUO: [200, 200) SYSSAVED.CMD; 2 0

>;
>ASN SY:=LB:
>PIP /FR
DUO: has 191173. blocks free, 46039. blocks used out of 237212.
Largest contiguous space = 105488. blocks
6873. file headers are free, 1226. headers used out of 8099.

>;
>; Start of library build at 18:27:02 on 13-JUN-85

>SET /UIC= [l, 1)
>PIP LB:ANSLIB.OLB/NV=LB:SYSLIB.OLB
>LBR LB:ANSLIB/RP=SYO:FCSMTA
Module "ANSPAD" replaced
Module "ASSLUN" replaced
Module "BIGBUF" replaced
Module "CLOSE

" replaced

Module "CONTRL" replaced
Module "CREATE" replaced
Module "DIRECT" replaced
Module "FCSTYP" replaced
Module "GET
Module

GETSQ

Module "OPEN

" replaced
" replaced
II

replaced

Module "OPENR " replaced
Module "OPFID

replaced

Module "OPFNB

replaced

Module "PARSFN" replaced
Module "POINT

" replaced

5-22

DETAILS OF SYSGEN PHASE I I
Module "PUT

replaced

Module "PUT SQ

replaced

RDWAIT

replaced

Module "RETADR

replaced

Module

RSTFDB

replaced

Module

RWBLK

replaced

Module

Module "RWLONG 11 replaced
Module

WATSET 11 replaced

Module

WTWAIT 11 replaced

Module "WTWATD 11 replaced
>SET /UIC=[l,24]
>LBR SYO:MCR/RP=SYO:MCR.OBJ
Module 11 DV20V II replaced
Module

SPSOV

replaced

Module

STSUB

replaced

Module "SXlOV

replaced

SX20V

replaced

Module "SX30V

replaced

Module

SX40V

replaced

Module

ST50V

replaced

>;
>; End of library build at 18:31:46 on 13-JUN-85

>;
>;

>; Start of Executive task build at 18:31:47 on 13-JUN-85

>;
>;
>PIP [1,34]*.*;*/DE/NM
>TKL @LB:RSXBLD

>;
>; End of Executive task build at 18:36:51 on 13-JUN-85

>;
>PIP LP:=SYO: [l,34]RSX11M.MAP

>;
>; Start of system image creation at 18:36:53 on 13-JUN-85

>;
>PIP RSX11M.SYS/CO/NV/BL:498.=RSX11M.TSK

>;
>; End of system image creation at 18:36:58 on 13-JUN-85

>;
>;
>; Start of full duplex terminal driver task build at 18:36:58 on 13-JUN-85

>;
>SET /UIC= [l, 24]
>TKL @LB:TTDRVBLD

5-23

DETAILS OF SYSGEN PHASE I I
>;
>; End of full duplex terminal driver task build at 18:38:17 on 13-JUN-85

>;
>;
>; Start of loadable driver task build at 18:38:17 on

13-JUN-~5

>;
>TKL @SYO:DUDRVBLD
>TKL @SYO:MUDRVBLD
>TKL @SYO:LPDRVBLD

>;
>; End of loadable driver task build at 18:40:03 on 13-JUN-85

>;
>;

>; Start of common block task build at 18:40:03 on 13-JUN-85

>;
>; Build the ANSLIB flavor of the FCS resident library common

>;
>;
>; Creating the task build .CMD and .ODL files in SY: [1,24]

>;
>TKL @SY: [l,24]FCSRS1BLD.CMO

>;
>; End of common block task build at 18:42:11 on 13-JUN-85

>;
>;
>; Start of privileged task build at 18:42:11 on 13-JUN-85
>;
>;
>; Note that the following tasks will be built for your system:
>;
PMT
FCPMOL
IN!
INS
BOO
OMO
ICP
>;
QMGCLI QMGPRT LPP
QMG
MOU
MCR
OCL
>;
LOA
UNL
FllMSG MTAACP SAV
TKTN
UFO
>;
BRO
HEL
BYE
SHF
ACNT
PMD
RMO
>;
RCT
SHUT UP ACS
ERRLOG
ELI
>;
>;
>;
>; It is assumed that [l,l]FCSRES.STB is an ANSLIB version of the FCS
>; resident library

>;
>;
>; Creating the task build .CMD and .ODL files in SY: [1,24]

>;
>TKL @SY: [l,24]BOOBLO.CMD
>TKL @SY: [l,24]0MOBLO.CMD
>TKL @SY: [l,24]FCPMDLBLD.CMD
>TKL @SY: [l,24]ICPBLO.CMD
>TKL @SY: [l,24]INIBLO.CMO
>TKL @SY: [l,24]INSBLO.CMD
>TKL @SY: [l,24]PMTBLD.CMD
>TKL @SY: [l,24]MCMBLO.CMD
>TKL @SY: [l,24]DCLBLD.CMD
>TKL @SY: [l,24]MOUBLO.CMD
>TKL @SY: [l,24]QMGRESBLD.CMD
>TKL @SY: [l,24]QCLRESBLD.CMD
>TKL @SY: [l,24]QPRBLD.CMD
>TKL @SY: [l,24]LP~RESBLD.CMD
>TKL @SY [l,24]FllMSGBLD.CMD
>TKL @SY [l,24]MTABLD.CMD
>TKL @SY [l,24]SAVBLO.CMD
>TKL @SY [l,24]TKNBLD.CMD
>TKL @SY [l,24]UFDBLO.CMD
>TKL @SY [l,24]LOABLD.CMO

5-24

DETAILS OF SYSGEN PHASE I I
>TKL @SY [l,24]UNLRESBLD.CMD
>TKL @SY [l,24]PMDR~SBLD.CMD
>TKL @SY [l,24]RMDBLD.CMD
>TKL @SY: [l,24]SHFBLD.CMD
>TKL @SY: [l,24]ACNRESBLD.CMD
>TKL @SY: [l,24]BYEBLD.CMD
>TKL @SY: [l,24]HELRESBLD.CMD
>TKL @SY: [l,24]BROBLD.CMD
>TKL @SY: [l,24]SHUBLD.CMD
>TKL @SY: [l,24]ACSRESBLD.CMD
>TKL @SY: [l,24]ERLBLD.CMD
>TKL @SY: [l,24]ELIRESBLD.CMD
>TKL @SY: [l,24]RCTBLD.CMD

>; End of privileged task build at 20:31:12 on 13-JUN-85

>;
>;
>; Start of system VMR at 20:31:12 on 13-JUN-85

>SET /UIC=[l,54]

>;
>INS SY: $BOO; -1
>INS SY:$VMR;-l
>ASN SY:=LB:
>vmr @sysvmr
VMR -- *DIAG*-Partition reduced to executive common size
INS EXCOMl
VMR -- *DIAG*-Partition reduced to executive common size
INS EXCOM2
VMR -- *DIAG*-Loadable driver larger than 4K
LOA TT:
VMR -- *DIAG*-Installed tasks may no longer fit in partition
SET /TOP=DRVPAR:-*
POOL=l200:8700.:08700. 0
EXCOMl 117734 00120000 00014600 MAIN COM
EXCOM2 117670 00134600 00010300 MAIN COM
LDRPAR 117624 00145100 00002600 MAIN TASK
TTPAR 117260 00147700 00040000 MAIN TASK
DRVPAR 116734 00207700 00024600 MAIN SYS
116470 00214400 00007400 SUB DRIVER - MU:
116370 00224000 00010200 SUB DRIVER - DU:
116254 00234200 00000300 SUB DRIVER - LP:
SYSPAR 116210 00234500 00011700 MAIN TASK
PUCOM 116144 00246400 00007500 MAIN COM
FCSRES 116100 00256100 00040000 MAIN COM
FCPPAR 116034 00316100 00024200 MAIN SYS
GEN
115770 00342300 03435500 MAIN SYS
LOR ••• i3.02 117510 LDRPAR 248. 00002600 LB0:-00124326 FIXED
TKTN
05.00 111304 SYSPAR 248. 00011700 LB0:-00130111
•• RMD 03.00 114630 GEN
225. 00027200 LB0:-00130711
FllMSG 13.00 113720 GEN
200. 00005700 LB0:-00125745
MTAACP 15.00 113604 GEN
200. 00014700 LB0:-00130370
•• DMO 04.00 114264 GEN
160. 00014600 LB0:-00126070
MCR ••• 05.00 112560 SYSPAR 160. 00011700 LB0:-00112376
•• DCL 4.2
112444 GEN
160. 00051500 LB0~-00127242
•• MOU 27.00 111764 GEN
160. 00037700 LB0:-00126676
•• MCR 03.00 111420 GEN
160. 00020000 LB0:-00127042
FllACP 05.00 115654 FCPPAR 149. 00024200 LB0:-00126171
ERRLOG 2.00
114150 GEN
148. 00040000 LB0:-00125757
PMT ••• 2.00
113124 GEN
148. 00006300 LB0:-00126351
PMD ••• 08.00 113010 GEN
140. 00016200 LB0:-00130663
SHF ••• 6.00
111534 SYSPAR 105. 00011700 LB0:-00130143
•• INS 9.00
113240 GEN
100. 00034600 LB0:-00126637
•• SAV 05.00 111650 GEN
100. 00033200 LB0:-00130552
•• UFD 05.00 111170 GEN
100. 00005700 LB0:-00130121

5-25

DETAILS OF SYSGEN PHASE I I
RCT ••• 05.00 110740 GEN
QMG ••• 03. 03 11S424 GEN
PRT... 2. 0
11S060 GEN
LPO
04.01 114744 GEN
•• ACS 3. 00
114Sl4 GEN
1133S4 GEN
•• AT. 8.0
•• QUE 05.00 11S310 GEN
•• PRI 05.00 11Sl74 GEN
•• BOO 06.02 114400 GEN
•• ELI 1.00
114034 GEN
•• MAG 03. 00 113470 GEN
•• LOA 04 •. 02 112674 GEN
•• HEL 03.00 112330 GEN
•• BYE 06.00 112214 GEN
•• BRO 06.00 112100 GEN
•• UNL 4. 02
1110S4 GEN
LPO: Loaded
DLO:
DUO:
Loaded
DUl:
Loaded
DU2:
Loaded
MUO:
Loaded
COO:
TTO:
TTO:
Loaded
TTl:
Loaded
TT2:
Loaded
Loaded
TT3:
TT4:
Loaded
Loaded
TT5:
NLO:
TI 0:
COO: TTO:
CLO: TTO:
LBO: DBO:
SYO: DBO:

100. 00010700 LB0:-00131341
7S. 00031700 LB0:-001267S4
70. 00001100 LB0:-00127010
70. 00014SOO LB0:-001301S6
70. OOOOSOOO LB0:-00131310
64. 00060000 LB0:-00126443
SO. 00020100 LB0:-00127763
SO. 00020100 LB0:-00127763
SO. 00021700 LB0:-00126027
SO. 00017300 LB0:-00131317
SO. 00031SOO LB0:-00130043
SO. 00032600 LB0:-00130306
SO. 00024000 LB0:-00131211
SO. 00012SOO LB0:-001311SO
SO. 00030400 LB0:-001312SS
SO. 00024SOO LB0:-00130634

>;
>; End of system VMR at 20:41:17 on 13-JUN-8S

>;
>;
>; An alternate version of SYSLIB.OLB, the system object library, was
>; created to provide support for ANSI magtape/FCS big-buffering (which
>;you selected in Phase I). You may want to rebuild DMP, FLX, PIP, and
>; VFY in Phase III to use ANSLIB.OLB.
Note, however, building 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 requirements.
You may want to rebuild
>; tasks in Phase III to link to the FCS resident library.

>; When SYSGEN finishes, boot in your target system, and save the system with a
>; bootstrap. For example:

>;
>;

>BOO [l,54]RSX11M
XDT: 38

>;
XDT>G
>; RSXllM V4.2 BL38

>;
>;

>TIM 12:00 15-JUN-85
>SAV /WB

5-26

DETAILS OF SYSGEN PHASE I I
>; RSXllM V4.2 BL38 128.K
>;
>RED DR =SY:
>;
>RED DR =LB:
>;
>MOU DR RSXM38
>;
>@DR: [l,2]STARTUP

MAPPED

>;
>;
>;
>;
>REM TKL

>; End of SYSGEN phase II at 20:41:18 on 13-JUN-85

>;
>SET /UIC=[200,200]
>@ <EOF>

>
>;
>;
>BOO [l,54]RSX11M0
XDT: 38
XDT>G
RSXllM
V4.l
BL38

>TIM 20:42 13-JUN-85
>TIM
20:42:13 13-JUN-85
>SAV /WB
RSX-llM V4.2
>RED DU: =SY:·
>RED DU:=LB:
>MOU DU:RSXM38
>DU: [~ 1 2]STARTUP

BL38

128.K MAPPED

>*PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY) [S); 20:43 13-JUN-85
>TIM
>TIM 20:43 13-JUN-85
>*ENTER LINE WIDTH OF THIS TERMINAL [D D:l32.]:
>SET /BUF=TI:l32
>ACS SY:/BLKS=512

>; This system startup command file (LB: [l,2]STARTUP.CMD) contains a
>; template of commands to initialize the queue print spooler and
>;queue LPO:, initialize the error logger, initialize the DCL CLI,
>; and install the RMS Library and Utilities. As is, these commands
>; are written as comments and are not executed. To include these
>; commands as part of the startup procedure, edit the file to remove
>; the period and semicolon (.;) comment delimiter from the beginning
>; of each line. These commands may be useful for initializing the
>; various facilities for your installation or else they may provide
>; a model with which to tailor initializaton commands for your
>; particular installation.

>@ <EOF>

5-27

DETAILS OF SYSGEN PHASE II

Notes for the terminal output from SYSGEN Phase II
target system) while running qn a baseline system.

(for

mapped

Chain to Phase II of SYSGEN, then continue
answering
questions.
Note that this example shows a SYSGEN in which
chaining from Phase I to Phase II was selected. If you are
not chaining, you invoke Phase II by issuing the following
command:
>@SYSGEN2 (5li)

At this point, Phase II of PREPGEN
SYSGEN begins.

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
that 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 concern; they simply supply diagnostic
information about partition sizes.
(See Chapter 10 of the
RSX-llM/M-PLUS System Management Guide for explanations of
the 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 can optionally bootstrap your
unsaved system and make it hardware-bootable. See Chapter 6
for details.

ends,

and

Phase

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
POST-SYSTEM-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 AN UNSAVED 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 an unsaved system. Once you have bootstrapped and saved a
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 unsaved system and target system in Chapter 1.) You
must have an unsaved system to begin performing the steps listed in
this chapter.
If you are generating your RSX-llM system from an on-line hast, 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 unsaved system, follow the procedure beginning at
Section 6.2.1 after Phase II completes.
If you have either a standard, unmapped unsaved system (where the base
address of the GEN partition is the standard address of 40000) or a
nonstandard, unmapped unsaved system (where the base address of the
GEN partition is at an address of other than 40000), start at Section
6.3.

6-1

POST-SYSTEM-GENERATION GUIDELINES
NOTE
In the following procedure, assume that ddu: contains
the unsaved system on the disk volume labeled RSXM38,
and that RSXM38 contains a mapped 124K unsaved system
in directory
[1,54]
and includes support for the
Executive Debugging Tool (XDT).

6.2.l

How to Bootstrap the Unsaved System

Follow the steps lis~ed to bootstrap and save the unsaved system.
If the unsaved system includes support for the Executive Debugging
Tool
(XDT), the console terminal display~ a prompt from XDT (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 host
system, 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 unsaved
system from an on-line host system aborts the current running system
and brings up the unsaved system.
>INS $BOO;l ~
(For a stand-alone host system)
(For an on-line host system)
>INS $BOO ~
>BOO ddu: [l,54]RSX11M.SYS ~
XDT: 38-A
XDT>G ~
RSXllM V4.2 BL38
>TIM 11:23 10-MAY-85 ~
>TIM ~
11:24 10-MAY-85

(Set the time and date)
(Enter the TIME command)

>
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
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 SAVE
/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 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.
6-2

POST-SYSTEM-GENERATION GUIDELINES
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 IBm
RSXllM V4.2 BL38

124.K MAPPED

>RED ddu: =SY: IBm
>RED ddu: =LB: IBm
>MOU ddu: RSXM38 IBm
>@ddu: [l,2]STARTUP.CMD
>*PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY)

6.2.3

[S]:ll:30 10-MAY-85IBm

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.11.)

6.2.4

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, RL01/RL02 users may find this step useful.
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 directory to eliminate baseline
have been superseded by target system files:
>SET /U IC= [ 1 , 5 4] IBm
>INS $PIP IBm
>PIP ddu:*.*/PU ~

6-3

files

that

POST-SYSTEM-GENERATION GUIDELINES
2.

Delete the privileged baseline files that were not eliminated
by the purge operation.
Files to delete may include the
baseline Autoconfigure task ACF.SSL, baseline drivers for
devices not supported on your target system, and the baseline
FCP FCPSML. TSK.
>SET /OIC=[l,54] IBrn
>PIP ddu:ACF.BSL;l/DE,DPDRV.*;l,FCPSML.TSK;lIBrn

Use BRU to back up 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 $BRO IBrn
>ACS ddu:/BLKS=O IBrn
>DMO ddu:/DEV (B(i)
>BRU /INI /VER (B(f)
From: ddu: (B(f)
To:
dd uu: (B(f)
BRU > (CTRL/Z)
or if mtu:
is a magnetic tape
single disk drive:

drive

system

with

>INS $BRO (B(i)
>LOA mtu: (B(i)
>ACS ddu: /BLKS=O (B(f)
>DMO ddu:/DEV (B(f)
>BRO/DENS: number/REW/VER (B(f)
From: ddu: (B(f)
To :
m tu : (B(f)
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.2.S

Building or Rebuilding RSX-llM Tasks

Invoke SYSGEN Phase III to
build
or
rebuild
nonprivileged,
(See Chapter 7 for details on SYSGEN
DIGITAL-supplied RSX-llM tasks.
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.

6-4

POST-SYSTEM-GENERATION GUIDELINES
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
WY

following

tasks

EDT
ZAP

If you want to include any of these tasks in your target system,
invoke Phase III to build them.
(BRU is available only on mapped
systems. EDT is available only on mapped systems with the full-duplex
terminal driver.)

6.2.6

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 unsaved 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 unsaved 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 re-create 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 unsaved target system from an RK07 to an
RM05, 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.
If you do not change the system image file, your system will
be unpredictable at best.
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/RK07
support, your response to
the
SYSGEN
question
regarding the unit supported by the DM controller must
match exactly_the device that you want to be hardwarebootable.
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 !NI 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 IN! command.)

6-5

POST-SYSTEM-GENERATION GUIDELINES
2.

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: RSXM38 t8TIJ

Copy the system directories to the new target system disk:
(>)PIP dduu: [*,*]/NV/UF/FO=ddu: [1,1]*.*, [1,2]*.*, [l,54]*.* (8TI)
(>)PIP dduu: [*,*]/NV /UF /FO=ddu: [ 1, 3] *. *, [ 1, 4] *. *, [ 1, 6] *. *, [ 1, 7] *. * (8TI)

Reassign the logical devices SY:
system disk:

and LB:

to the new

target

>ASN dduu: =SY: (8TI)
>ASN dduu: =LB: t8Til

Re-create the system image on the new target system disk:
>SET /UIC= [ 1, 54] t8TIJ
>PIP RSXllM.SYS/NV/CO/BL:<n>=RSXllM.TSK(8TI)

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 t8TIJ
>VMR @SY SVMR (8TI)

To avoid any incompatibility problems,
the version of VMR
that you are using must originate from your target system
disk.

6.2.7

After VMR has updated the system image file and produced an
unsaved system,
software bootstrap the unsaved system and
then use the MCR
SAVE
command
to
make
the
disk
hardware-bootable.
(Refer to Sections 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 and Micro/RSX 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.8

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.

6-6

POST-SYSTEM-GENERATION GUIDELINES
You can find HELP.ULB in directory [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

RSXM38

RK06/RK07

CLISRC

RLOl/02

HLPDCL

Follow these steps to get HELP support:
1.

Establish [1,2] as the default directory for the terminal:
>SET /UIC= [1, 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 RL01/RL02 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/VERIBm
From: MM: [ 1, 2] HELP. ULB (BIT)
To:
LB: (BIT)
NOTE
RL01/RL02 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.)
3.

Extract the build module from HELP.ULB, then name this module
HELPBUILD.CMD:
>LBR HELPBUILD.CMD=HELP.ULB/EX:BUILD (BIT)

Invoke the HELPBUILD command file:
\

>@HELPBUILD filI)
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 the Introduction to RSX-llM.

6-7

POST-SYSTEM-GENERATION GUIDELINES
5.

When you finish ext~acting the desired modules from HELP.ULB,
delete the files HEtPBUILD.CMD and HELP.ULB from LB:.
>PIP HELPBUILD.CMD;*,HELP.ULB;*/DE(B@

See the HELPBUILD.CMD file for more information.

6.2.8.1 Files for the Introduction to RSX-llM - HELP.ULB includes
introductory files that are referred to in the warm-up session in the
Introduction to RSX-llM.
You can use these files
in two ways,
depending on the number of new users that will be using your system.
1.

You can put the files in [200,1] and create an account with
the name USER and the UIC [200,1].
New users can then log in
to the USER account when they are doing the warm-up session
in the Introduction to RSX-llM.

You can put separate copies of the files in each new user's
account,
then instruct each user to delete the introductory
files when he or she has completed the warm-up session.

To put the introductory files into account [200,1],
or to copy
files into a new user's account, perform the following procedure:

the

Extract the introductory files from [1,2]HELP.ULB (using
instructions provided in this section).

the

Set your UIC (using the SET /UIC=[g,m] command)
to
[200,1],
or to the new user's account, depending on where you want to
copy the files.

Copy the files
[1,2]
to the
is:

INTRO.ULB and INTROFIL.CMD from directory
The copy command
UIC that you set in Step 2.

>PIP /NV=[l,2]INTRO.ULB,INTROFIL.CMD(BIT)
4.

Use the following command to execute INTROFIL.CMD to
the introductory files from INTRO.ULB:

extract

>@INTROFIL@@

6.2.9

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.
You should also use an editor to create the file LOGIN.TXT in
directory
[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.)

6-8

POST-SYSTEM-GENERATION GUIDELINES
Install resident libraries (RMS-11 on mapped systems only; see
• Section
6.2.12),
utilities, and user tasks.
(See the
RSX-llM/M-PLUS MCR Operations Manual for details
INSTALL command-.-)-

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 Batch and Queue Operations Manual for
details on the Queue Manager-.-)-Tne-8TARTUP.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 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.10

Establishing System Features with VMR

If terminal speeds and types and partitions are stable and certain
tasks are used frequently, you may want 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.11

How to Create a Backup Copy of the Target System Disk

Now that you have saved your target system, you should create a backup
copy to protect yourself against any accident that might corrupt the
contents of the disk. First, check the blank disk for bad blocks
using the BAD utility. Then, using BRU, copy the target system disk
either to another disk of the same type or to magnetic tape.
For
example, assume dduu: is a second disk drive:
>BRU/INI/VERID
From: ddu: ID
To:
dduu: ID
BRU> (CTRL/Z)
or mtu:

is a magnetic tape drive:

>BRU/DENS: number/REW/VER ID
From: ddu: ID
To:
rntu: ID
BRO> (CTRL/Z)

6.2.12

Installing RMS-11 V2.0

On most mapped RSX-llM systems, all RMS-11 files are automatically
your system after SYSGEN.

6-9

POST-SYSTEM-GENERATION GUIDELINES
However, for systems that were generated using either the RK06 or the
RL01/RL02 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.12.2.

6.2.12.l RK06 and RL01/RL02 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 BRU (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(5fil)
This command procedure prompts you for information
copy operation in the following manner:
1.

RMSINSTAL asks you if want
system.

all

the

and

RMS-11

executes
files

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.

RMSINSTAL asks you to enter the name of the target disk
is to contain the RMS-11 files.

that

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.

RMSINSTAL displays a small table that assigns a number to
each type of kit (RL01/RL02 disk, RL01/RL02 magnetic tape,
RK06 disk, RK06 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).

RMSINSTAL 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
disk
and
magnetic
tape
distribution kits, BRU may be run twice by
RMSINSTAL.

6-10

asks

POST-SYSTEM-GENERATION GUIDELINES
When the BRU 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.12.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 (or libraries) 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 libraries and RMS-11 utilities already exist,
except that the command lines have been commented out by the period
and semicolon
(.;)
that begin each command line. Delete the period
and semicolon that proceed each command line 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-lI<locumentat1on and the RSX-llM/RSX-llS Release
Notes.

6.2.13

Error Logging Support

If you want error logging support and you have already created your
system from either an RK06/RK07 or an RL01/RL02 distribution kit, you
must copy the following error logging files from either the CLISRC
(RK06), HLPDCL
(RLOl), or MCRSRC (RL02) 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 named 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-11

POST-SYSTEM-GENERATION GUIDELINES
6.2.14

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 unsaved system, follow the procedure beginning
at Section 6.3.1 after Phase II completes.
NOTE
In the following procedure, assume that ddu: contains
the unsaved system on disk RSXM38 and that RSXM38
contains an unmapped 28K unsaved system in directory
[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 want 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.)

6.3.2

How to Bootstrap the Unsaved System

Follow the steps listed to bootstrap and save the unsaved 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 unsaved
system from an on-line host system aborts the current running system
and brings up the unsaved system.
>I NS $BOO; 1 (BIT)
(For a stand-alone host system)
>INS $BOO (BIT)
(For an on-line host system)
>BOO ddu: [l,SO]RSXllM.SYS(BIT)
RSXllM V4.2 BL38

>TIM 11:·23 10-MAY-8 5 (BIT)
>TIM(BIT)
11:24 10-MAY-85

(Set the time and date)
(Enter the TIME command)

>
6-12

POST-SYSTEM-GENERATION GUIDELINES
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 bootblock
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 SAVE
/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 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 ~

RSXllM V4.2 BL38

28.K UNMAPPED

>RED ddu:=SY:
>RED ddu:=LB:
>MOU ddu:RSXM38
>@ddu: [l,2]STARTUP.CMD
>*PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY)

6.3.4

[S]:ll:25

10-MAY-85~

Invoke Phase III to Task Build DSC

To execute some of the remaining steps in this chapter, you need the
Disk Save and Compress utility (DSC). The most efficient way to do
Refer to
this is to invoke Phase III of SYSGEN and task build DSC.
Chapter 7 for details on Phase III. After you task build DSC, exit
from Phase III, install DSC, and resume working at the next step.

6-13

POST-SYSTEM-GENERATION GUIDELINES
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
6.3.9.2.)

6.3.5

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, RL01/RL02 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

Purge the system directory to eliminate files that have
superseded by target system files:

been

>SET /UIC=[l,54] ~
>INS $PIP~
>PI P dd u : * • * ; */DE m
2.

>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:
>INS $DSC~
>ACS ddu:/BLKS=O~
>OMO ddu:/DEV~
>DSC dduu:/VE=ddu:~
or if mtu:
is a magnetic tape
single disk drive:
>INS $DSC~.
>LOA mtu: ~
>ACS ddu:/BLKS=O~
>OMO ddu :/DEV~
>DSC mtu:/VE=ddu:m

6-14

drive

(disk to tape)

system

with

POST-SYSTEM-GENERATION GUIDELINES
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

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 unsaved 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 unsaved 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 re-create 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 unsaved target system from an RK07 to an
RMOS, and if you were able to bootstrap the RMOS 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 what the system
expects.
If you do not change the system image file, your system will
be unpredictable at best.
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/RK07
support, your response to
the
SYSGEN
question
regarding the unit supported by the DM controller must
match exactly the device that you want to be hardwarebootable.
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:RSXM38(@)

6-15

POST-SYSTEM-GENERATION GUIDELINES

copy the system directories to the new target system disk:

>p Ip dduu: [*,*)/NV /UF /FO=ddu: [ 1, 1] * • * , [ 1, 2 J *. * , [ 1, 50] *. * IBITl

>PI p dduu: [*,*]/NV /UF/FO=ddu: [ 1, 3] *. *, [ 1, 4] *. *, [ 1, 6] *. *, [ 1, 7] *. * ~

Reassign the logical devices SY:
system disk:

and LB:

to the new

target

>ASN dduu:=SY: IBm
>ASN dduu: =LB: IBm

Re-create the system image on the new target system disk:
>SET /UIC=[l,50) IBm
>PIP RSXllM.SYS/NV/CO/BL:<n>=RSXllM.TSKIBIT)

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 IBm
>VMR @SYSVMR (8IT)

To avoid any incompatibility problems,
the version of VMR
that you are using must originate from the target system
disk.
7.

6.3.7

After VMR has updated the system image file and produced an
unsaved system, software bootstrap the unsaved system, and
then use the MCR
SAVE
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 and Micro/RSX Task Builder Manual for details
on specifying ANSLIB.OLB as the defau"ftlibrary using the /DL switch.
Remember to rebuild your privileged user-written tasks to link to
target Executive.

6.3.8

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.

6-16

Distribution Kit

Volume

Big-disk

RSXM38

RK06/RK07

CLISRC

RL01/RL02

HLPDCL

Follow these steps to get HELP support:
1.

Establish [1,2] as the default directory for the terminal:
>SET /UIC=[l,2] (Blil

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 ffim

NOTE
RL01/RL02 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 IBD)

Invoke the HELPBUILD command file:
> @HELPB UI LD IBD)

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 the Introduction to RSX-llM.
5.

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 not delete HELP.ULB.
It is your only
copy.
>PIP HELPBUILD.CMD;*,HELP.ULB;*/DE IBD)

See the HELPBUILD.CMD file for more information.
6-17

POST-SYSTEM-GENERATION GUIDELINES
6.3.8.1 Files for the Introduction to RSX-llM - HELP.ULB includes
introductory files that are referred to in the warm-up session in the
Introduction to RSX-llM.
You can use these files
in two ways,
depending on the number of new crsers that will be using your system.
1.

You can put the files in [200,l] and create an account with
the name USER and the UIC [200,l]. New users can then log in
to the USER account when they are doing the warm-up session
in the Introduction to RSX-llM.

You can put separate copies of the files in each new user's
account,
then instruct each user to delete the introductory
files when he or she has completed the warm-up session.

To put the introductory files into account [200,l], or to copy
files into a new user's account, peform the following procedure:

the

Extract the introductory files from [l,2]HELP.ULB (using
instructions provided in this section) •

the

Set your UIC (using the SET /UIC=[g,m] command)
to
[200,1],
or to the new user's account, depending on where you want to
copy the files.

Copy the files
[1,2]
to the
is:

INTRO.ULB and INTROFIL.CMD from directory
The copy command
UIC that you set in Step 2.

>PIP /NV= [l, 2] INTRO. ULB, INTROFIL.CMD tBru
4.

Use the following command to execute INTROFIL.CMD to
the introductory files from INTRO.ULB:

extract

>@INTROFIL tBru

6.3.9

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.
You should also use an editor to create the file LOGIN.TXT in
directory
[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, utilities, and user tasks.
(See
the RSX-llM/M-PLUS MCR Operations Manual for details on the
MCR INSTALL command.)~-

•

POST-SYSTEM-GENERATION GUIDELINES
6.3.9.1 Establishing System Features with VMR - If terminal speeds
and types and partitions are stable and certain tasks are used
frequently, you may want 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.9.2 How to Create a Backup Copy of the Target System Disk - Now
that you have set your target system, you should create a backup copy
to protect yourself against any accident that might corrupt the
contents of the target system disk.
Using DSC, copy the target system
disk RSXM38 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.9.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 I I I

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
~onprivileged
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
SYSG.EN 3. CMD.

command

file

that

controls

Phase

III

execution

If your target system is unmapped (regardless whether it is a standard
or a nonstandard unmapped system), you have to build a few RSX-llM
nonprivileged 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
something other than the default base address of 40000, you can easily
build RSX-llM tasks with the desired GEN partition base address during
Phase II I.
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

HEL
!OX
LBR
LPP

MAC
PAT
PIP
PMD

7-1

that
PRT
QMGCLI
QMG
SLP

you

can
STK
TKB
VFY
ZAP

link

DETAILS OF SYSGEN PHASE III
If you selected ANS! magnetic tape support or support for big
buffering 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
I I I.

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 Version 4.2 host
system,
set your directory to be
[200,200], assign the
logical device SY:
to your baseline disk, and invoke
SYSGEN3.CMD as follows:
>SET /U IC= [200, 200] ~
>ASN ddu:=SY:~
(where ddu: is your baseline disk)
>MOU ddu: RSXM38 ~
>@SYSGEN3 ~

If you generated your system from a stand-alone Version 4.2
host system, bootstrap the target disk (see Appendix B), then
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>? [SJ:

Enter the directory containing the file SGNPARM.CMD.
SGNPARM~CMD
supplies Indirect symbol definitions from Phase I that are relevant to
Phase III processing, and provides a means of communicating between
Phase I and the other phases of SYSGEN. SYSGEN creates this file in
the directory from which you invoked Phase I of SYSGEN.
SYSGEN replaces <uic> with the directory from which you invoked Phase
III of SYSGEN.
Enter a different directory to override this default;
otherwise, press the RETURN key.
Some tasks are not available on the baseline system (such as BAD).
If
you want to task build a nonprivileged task for the baseline system,
use the SGNPARM.CMD file for the baseline system in directory [1,54].

2. Are you building nonprivileged tasks? [Y/N]:

If you are building any of the following nonprivileged
respond Yes to this question:
BAD
BRU
CDA
CFL

CMP
CRF
DMP
DSC

EDI
EDT
FLX
FMT

FTB
IOX
LBR
MAC

PAT
PIP
RPT
SLP

7-2

STK
TKB
VFY
ZAP

tasks

listed,

DETAILS OF SYSGEN PHASE III
NOTE
See the RSX-llM/RSX-llS Information Directory and
Master 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.

2A. Is this an RLOl kit? [Y/N]:

This question applies only if you have an RL01/RL02 distribution kit.
SYSGEN uses your response to this question to determine the location
in your distribution kit of the files for building nonprivileged
tasks.
(In an RLOl kit, they are located on RLUTIL; on an RL02 kit,
they are located on PRVBLD.)

3. Enter device for <label> disk when it is ready (ddu:)

[D: <object>]

This question appears only if you are using an RL01/RL02
kit.

[SJ:

distribution

To answer this question, enter the device mnemonic and unit number of
the drive containing the requested object files disk.
(SYSGEN
replaces <label> with the volume name of the appropriate disk.)
If you are using an RLOl distribution kit and if you
Question 2, SYSGEN replaces <label> with PRVBLD.

answered. No

If you are using an RLOl distribution kit and you
Question 2, SYSGEN replaces <label> with RLUTIL.

answered

Yes

If you are using an RL02 distribution
with PRVBLD.

kit,

replaces

<label>

If you are using any other disk
"object."

SYSGEN

kit,

SYSGEN

replaces

<label>

The default response (<default>) is the response entered for
17 of the Setup Section in Phase I.

4. Enter map device (ddu:)

[D:

with

Question

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 device must be mounted, and the directory [1,34]
for
mapped systems or
[1,30]
for unmapped systems must exist on the
volume.
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.

7-3

DETAILS OF SYSGEN PHASE III
If you want 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 want to build all of the nonprivileged tasks
listed in the table.
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 magnetic tape 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(10)-word boundary.

7-4

DETAILS OF SYSGEN PHASE III
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) •

9. SYSPAR's base address in 32 word blocks (0 D:<default>J

This question appears only for unmapped systems and only · if
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(10)-word blocks for the GEN partition and that you
plan to include a 14K task partition (PAR14K) of which GEN is an BK
subpartition.
If the target system has fewer 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(10)-word blocks for the GEN
partition and that GEN is an BK 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>J:
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).

The base address of SPLPAR starts on a 32(10)-word boundary.
If you
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
re-created 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

@SYSGEN3 0

>; RSX-llM V4.2 System Generation PHASE III -- Version 2.05

>;
>; 14-JUN-85 13:29:15

>;
>*

1. In what UIC is SGNPARM.CMD if not in

[200,200]

[S]:

>; Big disk distribution kit SYSGEN version 2.10 for RSX-llM BL38

>;
>;-Continuation from SYSGEN PHASE I done on 13-JUN-85 at 18:26:39

>;
>* 2. Are you building nonprivileged ta3ks? [Y/N]: Y
>* 4. Enter map device (ddu:) [D: NL:] [S]: SY:
>ASN SY:=LB:

>;
>; For nonprivileged tasks:
* -- Prints the table of tasks
>;
%
Builds all tasks
>;
• -- Terminates inquiry

>;
>; Enter responses separated by commas.
>; not fit on one line.

All responses need

>;
>; Example:

BAD,LBR,PIP,.

>;
>* 5. Enter task name (s)

[S]: * 8

>; Nonprivileged tasks:

>;
>;
>;
>;
>;
>;
>;

BAD
CRF
FLX
MAC
STK

BRU
DMP
FMT
PAT
TKB

>* 5. Enter task name(s)

CDA
DSC
FTB
PIP

CFL
EDI
IOX
RPT

VFY

VMR

[S] : CDA.

CMP
EDT
LBR
SLP
ZAP

•

>; [l,l]FCSRES.STB can be used to build many tasks
>; so that those tasks link to the FCS resident library

6. Use [l,l]FCSRES.STB when building those tasks? [Y/N]: Y

>;
>; It is assumed that [1,l]FCSRES.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.

>* 11. Pause to edit any task build .CMD or .ODL files? [Y/N]:
>* 12. Delete task build .CMD and .ODL files after task building? [Y/N]:
>S_ET /UIC=[l,24]

>;
>; Creating the task build .CMD and .ODL files in SY: [1,24]

>;
>TKL @SY: [l,24]CDARESBLD.CMD
>ASN =LB:
>SET /UIC=[200,200]
>@ <EOF>

7-6

DETAILS OF SYSGEN PHASE I I I

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
target system, then terminate your input with a period.

your

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

CHAPTER 8
SYSGEN ERROR MESSAGES

All error messages from SYSGEN appear in this chapter in alphabetical
order. The descriptions that follow each message explain the possible
cause and, as necessary, suggest remedial action.
SGN -- You attempted to use non-existent default for parameter
-- RETRY

<parm>

Explanation: A required parameter was missing from the response
to the current peripheral question. SYSGEN 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.
SGN -- Baseline terminal
protection selected

driver

not

valid

option

with

multiuser

Explanation: The half-duplex baseline terminal driver includes
no SYSGEN options and cannot execute in a multiuser protection
system (for example, the break-through write option is required
but not included). Choose a different terminal driver.
SGN -- CO driver not valid on RSX-llS systems
Explanation: RSX-llS systems cannot include the
(CO). SYSGEN ignores this entry.

console

driver

Explanation: Unmapped systems cannot include the console
(CO). SYSGEN ignores this entry.

driver

SGN -- CO driver not valid on unmapped system

SGN -- Correct problems and reassemble the bad
continue when done

modules;

SYSGEN

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 SYSGEN
continues.

8-1

SYSGEN ERROR MESSAGES
SGN -- Correct problems -- SYSGEN will restart assemblies when done
Explanation: This message indicates that you detected an error
in assembling the laboratory peripheral devices.
After you
correct the error, SYSGEN attempts to reassemble the laboratory
peripherals common area(s).
SGN -- DMll-BB CSR address must be greater than 157777 if specified -RETRY
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 must be greater than 277 if specified -RETRY
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 O.
SGN -- DU not valid on an unmapped system -- SUPPRESSED
Explanation: Unmapped systems cannot support
SYSGEN ignores this entry.
SGN -- Dynamic storage space must be in
RETRY

multiples

the

UDA50

two

(DU:).

words

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 a 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 want to use it,
type CTRL/Z and restart your system generation specifying 124K or
less for memory size.

8-2

SYSGEN ERROR MESSAGES
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 not allowed.
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:
See
numeric response."

the

explanation

"Il~egal

character

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 supports only 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 be specified
only 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 <directive-code>
Explanation:
You have entered a code other than A, B,
F, G, H, I, J, K, or L.
The line is discarded.

SGN -- Invalid FCP code <fcp code> entered -- RETRY
Explanation: You have entered an FCP code other than A, B,
or E.
SYSGEN re~rompts for a valid FCP code.

8-3

c, D,

SYSGEN ERROR MESSAGES
SGN -- Invalid processor type -- RETRY
Explanation: You have
response to Question
SYSGEN Phase I.

entered an unknown processor type in
1 in the Target Configuration Section of

SGN -- Invalid system device -- RETRY
Explanation: The device specification for the
disk was entered incorrectly.

Executive

source

Big-disk kits: The default response is SY:.
Either enter Y or
press the RETURN key.
Otherwise, you must enter at least two
characters to identify the device that contains the Executive
sources.
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 an 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. If you want to print at LP:, specify LPO:.

8-4

SYSGEN ERROR MESSAGES
SGN -- Maximum of 1 CRT monitor possible with VTll -- RETRY
Explanation: A VS60 can support two CRT
supports only one.

monitors,

but

VTll

SGN -- Maximum of 8 printers allowed on a system with a KMC -- RETRY
Explanation:

The KMC-11 supports up 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 indicate only one controller.
Terminal driver controllers are specified later.
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 fewe~ than 24K words of memory for a mapped system.
SGN -- Memory not multiple of 4K
Explanation:
of four.

When you specify memory size, it must be a multiple

SGN -- More than 252.

modules specified -- RETRY

Explanation: The UDCll supports a maximum
You have specified more than the maximum.

252(10)

modules.

SGN -- Number of interrupts must be divisible into 10,000
Explanation: The number of interrupts per second specified 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.

8-5

per

second

SYSGEN ERROR MESSAGES
SGN -- Number of samples must be
RETRY

evenly

divisible

into

10000.

Explanation: The sampling rate 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.
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 (#n) <parm> out of range <min> to <max> -- RETRY
Explanation: The indicated parameter (excluding
within the acceptable range.

[L/R])

not

SGN -- Pausing to allow editing of Executive source
Explanation: This is not an error message;
the message is
informative.
It appears when you indicate you want to edit the
Executive files.
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 file has been invoked
user-written CLI. SYSGEN exits under this condition.

from

Set your terminal to either MCR or DCL and reinvoke SYSGEN.
SGN -- Saved answer file for a Standard Function System (SGNSTAND.CMD)
does not exist
Explanation: Either the saved answer file SGNSTAND.CMD does not
exist in the current directory 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.

8-6

SYSGEN ERROR MESSAGES
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.
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:
through 7.

The crash device must

unit

number

from

SGN -- Unrecognizable string "ddn" -- Ignored
Explanation:
SYSGEN could
Perhaps you omitted a comma.

not

parse

SGN -- Valid character detection expander
(yes) and "NO" (no) -- RETRY

the

unit

indicated

indicators

string.

are

"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 indicators are "D" (yes)
RETRY

and

"NO"

(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: OT, DK, MT, MS, MM, DB, OM, DL, DD, DR, DU, DX,
MU, and DY -- RETRY
Explanation: ~he Executive crash module
device you entered as a dump device.
8-7

does

not

support

the

SYSGEN ERROR MESSAGES
SGN -- Valid DRll-K present indicators are "ORK" (yes) and
-- RETRY

"NO"

(no)

Explanation: Valid responses
for this parameter are ORK to
indicate that ORll-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.
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.
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 OHll 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 OHVll controller does not support the specified

SGN -- Valid offset recovery indicators are "O"
RETRY

(yes) and "NO"

(no)

Explanation:
Valid responses
for this parameter are o to
indicate that all controllers of this type support off set
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.

8-8

SYSGEN ERROR MESSAGES
SGN -- WARNING -- CPU does not have
switch directive not included

switch

Get

sense

Explanation: The processor you specified does not have a switch
register.
Thus, you cannot use the Get Sense Switch directive.
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 of the 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 want 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

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)

A-1

SAVED ANSWER SYMBOLS
Table A-1
Definition of Saved Answer Symbols
Symbol

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
present?

$FPP

TC-6

Floating point processor (FPll) present?

$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:

$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
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
control?

arithmetic

element

(KEll-A/B

EAE)

A-60Hz B-50Hz

least

120

placement

(Continued on next page)

A-2

SAVED ANSWER SYMBOLS

Table A-1 (Cont.)
Definition of Saved Answer Symbols
Symbol

Key

Definition

$NRT

E-4

Nonresident tasks (task loader) supported?

$LLR

E-5

Loadable task

$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?

E-10

Address checking supported?

$IOR

E-11

I/O rundown supported?

$MUP

E-12

Multiuser protection supported?

$ANM

E-13

ANSI magnetic tape support?

$0UD

E-14

On-line formatting
supported?

$LOO

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
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 write-checking supported?

$SWL

E-29

Software write-locking supported?

$XDT

E-30

Executive Debugging Tool (XDT) supported?

load~r

supported?

(FMT)

and

diagnostic

QIOs

ready"

(Continued on next page)
A-3

SAVED ANSWER SYMBOLS

Table A-1 (Cont.)
Definition of Saved Answer Symbols
Symbol

Key

Definition

$ROT

E-31

Rotating pattern in data lights supported?

$NET

E-32

Communications products supported?

$TSA

E-32A

Network Command Terminal support?

$OMA

E-33

System-controlled partitions supported?

$AMC

E-34

Include support for the Shuffler?

$PRN

E-35

Queue
Manager
supported?

$GGE

E-36

Group global event flags supported?

$ORR

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 preallocated 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

and

queued

spooler

scheduling
$LOC

E-42

Lowest priority class for round-robin scheduling

$DKS

E-43

Executive level disk swapping interval

$SWP

E-44

Swapping priority

$DSA

E-45

Size of the dynamic
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?

storage

region

(pool)

(Continued on next page)

A-4

SAVED ANSWER SYMBOLS

Table A-1 (Cont.)
Definition of Saved Answer Symbols
Symbol

Key

Definition

$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:

A-PANIC B-CDA

See the documentation for Question 1 for
code and associated terminal driver.

letter

$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/0 cancellation supported?

$BWS

TT-8

Break-through 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?

$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

CR~

rubout support?
{Continued on next page)
A-5

SAVED ANSWER SYMBOLS
Table A-1 {Cont.)
Definition of Saved Answer Symbols
Symbol

Key

Definition

$THS

TT-21

CTRL/S and CTRL/Q supported?

$TIB

TT-22

Support for user terminal input buffering?

$VTB

TT-23

Support for
buffering?

$L30

TT-24

LA30P supported?

$HRE

TT-25

Support hardware
notification?

$DIC

TT-26

Support device-independent cursor positioning?

$BBF

S0-1

ANSLIB.OLB desired for big buffering?

$IP11

S0-2A

Support for IPll Industrial I/O Subsystem?

$IPPF

S0-2B

Support for IPll power-fail?

$ISA

S0-2

Build the library of ISA FORTRAN industrial/lab

variable-length

terminal

input

error

unrecoverable

routines?
$FRL

S0-3

Build the PLAS resident FCS?

$FCP

S0-4

Code for FCP:
See the documentation for Question 3 for
code and associated version of FllACP.

letter

$PMD

S0-5

Postmortem Dump (PMD) supported?

$RMD

S0-6

Resource
Monitoring
supported?

$PRT

S0-7

Non-Queue Manager print spooler (PRT) supported?

$DCL

S0-8

DIGITAL Command Language (DCL) supported?

$NUC

S0-9

Number of user-written CLis

$PMT

S0-10

Support for pool
(PMT)?

$NOD

S0-11

System
name
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?

$LDxN

DB-5

Loadable driver two-character device mnemonic

Display

monitoring/low
(six

fewer

(RMD)

task

pool

recovery

alphanumeric

(Continued on next page)
A-6

SAVED ANSWER SYMBOLS
Table A-1 (Cont.)
Definition of Saved Answer Symbols
Symbol

Key

Definition

$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-7

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 on 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
steps
disk,

The following procedures give a general description of the
necessary
to
hardware bootstrap a magnetic tape and a
respectively.
To bootstrap a magnetic tape:
1.

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 (ready) indicator is lit.

Ensure that the console terminal is on line.

Follow the bootstrap instructions (in this appendix) for
particular bootstrap you must use.

ON-LINE

the

To bootstrap a disk:
1.

Insert the disk (for instance, the baseline disk RSXM38)
free unit.

Ensure that the ROY (ready)

B-1

light is on.

in a

HARDWARE BOOTSTRAP PROCEDURES
3.

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
Device to Bootstrap

Bootstrap Type
MRll-DB

RFll disk

M9301-YA

M9301-YB

M9301-YC

M9301-YF M9312

100

773100

RS03/RS04 disk
RKOS disk cartridge
unit 0

773110

RP02 or RP03 disk
pack unit 0

773154

RP04, RPOS, or RP06
disk pack unit O

RKOS disk (unit n)

DKn

30+n

DKn

RL01/RL02 disk
unit n

DKn
DLn

RK06 disk (unit n)

DMn

RK07 disk (unit n)

DMn
DMn

RP02 or RP03 disk
pack (unit n)

DPn

RP04, RPOS, RP06,
RM02, RM03, RMOS,
RPO?, or RM80
disk (unit n)

DPn

40+n

DPn

DBn

70+n

DBn

RA60/80/81, RC25

DUn

TKSO

MUn

TUlO/TElO and TS03
magnetic tape

773136

TSll magnetic tape

MSn

TU16/TE16/TU45
/TU77 magnetic tape
TU56 DECtape

MTn

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 then back to its ENABLE position.

Set the CPU switch register to one of the following values:
773100 for
773110 for
773154 for
773136 for

B.3

position

RFll disk
RKOS disk cartridge
RP03 disk pack
TU10/TE10/TS03 magnetic tape

Press the CPU LOAD ADRS switch.

Press the cro START 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.

Device

Code

TU10/TE10/TS03 magnetic tape

TU16/TE16/TU45/TU77 magnetic tape 1

RKOS disk cartridge

RP02/RP03 disk pack

RP04/RP05/RP06/RM02/RM03 disk pack!

RS03/RS04 fixed-head disk 1

M9301-YB Bootstrap Terminator only.

B-3

HARDWARE BOOTSTRAP PROCEDURES
B.4

M9301-YC PROCEDURE

If the M9301-YC Bovtstrap Terminator is on
following steps:

the

system,

perform

the

Move the CPU ENABLE/HALT switch to its HALT position and then
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 Terminator 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 this occurs, call your
DIGITAL Field Service representative.
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 test detects an error.

B-4

HARDWARE BOOTSTRAP PROCEDURES
B.S

M9301-YF PROCEDURE

If the M9301-YF Bootstrap Terminator is on
following steps:

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 RS at the console terminal.
It
then prints a prompting character ($).

In response
to
the
prompting
character,
type
the
two-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.
Table B-4
Device Codes for the M9301-YF Bootstrap

B.6

Device

Code

TU10/TE10/TS03 magnetic tape

TU16/TE16/TU45/TU77 magnetic tape

RKOS disk cartridge

RK06/RK07 disk cartridge

RP02/RP03 disk pack

RP04/RP05/RP06/RM02/RM03 disk pack

RS03/RS04 fixed-head disk

M9312 PROCEDURE

The M9312 Bootstrap Terminator contains independent programs that can
bootstrap programs into memory from a selected peripheral device.
Through front-panel control or following 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.6.1.
{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.

•

If you have a CPU equipped with switch registers, know what
device ROMs are on the M9312 Bootstrap Terminator, but do not
have a console emulator, follow the procedures in Section B.

•

If you do not have the M9312 Bootstrap Terminator on your
system and need to boot the RLOl, RL02, or RK07 disk device,
perform the manual load routine described in Section B.7.

B.6.1

Using the 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

Switch Register Boot Using the M9312 Console Emulator -

Move the CPU console ENABLE/HALT switch to its HALT
and then back to its ENABLE position.

position

Set the CPU switch register to 765020.

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
(@) •

Table B-5
Device Names and Mnemonics
Device To
Be Booted

Mnemonic

Unit

Octal
Data

RLOl

0-3

042114

RK06/RK07

0-7

042115
(Continued on next page)

B-6

HARDWARE BOOTSTRAP PROCEDURES
Table B-5 (Cont.)
Device Names and Mnemonics
Device To
Be Booted

Mnemonic

Unit

Octal
Data

RXOl

0-1

042130

RX02

0-1

042131

RS03/RS04

0-7

042123

RP02/RP03

0-7

042120

RP04/RP05/RP06

0-7

RM 0 2 /RM 0 3 /RM 0 5

RM80/RP07

DB 1

RA60/RA80

RA81/RC25

0-7

042125

RK03/RK05

0-7

042113

TU55/TU56

0-7

TSll

0-7

046523

TU16/TE16/

0-7

046515

TU45/TU77

TU10/TE10/TS03

0-7

046524

Console Emulator

N/A

040460

N/A

041060

CPU ROM
Diagnostic ROM

177776

PDP-11/60/70

xxx777 3
1.
2.
3.

Type DB rather than DR if you are booting the
RM03, RMOS, RM80, or RP07 disk.
This is a continuation ROM of a multiple ROM boot.
Bad ROM or NO ROM present.

B-7

RM02,

HARDWARE BOOTSTRAP PROCEDURES
4.

In response
to
the
prompting
character,
type
the
two-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 registers RO, R4,
the 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.

zero.

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 Terminator, 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 appear 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 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
rema1n1ng addresses in the load routine.
Use the LAD and the DEP
buttons to correct any erroneous 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:

12700

1002:

174400

177440

1004:

12760

1006:

1010:

1012:

12701

1014:

2003 3

1016:

lOllO

1020:

105710

1022:

100376

1024:

12760

1026:

177601

177400

1030:

1032:

5721

62701

1034:

lOllO

1036:

105710

lOllO

1040:

100376

105710

1042:

12760

100376

1044:

177400

5710

1046:

100001

1050:

5060

1.
2.

Select drive number 0 through 7 for the RK07.
Load 4 for unit 0, 404 for unit 1, 1004 for unit 2,
for unit 3.
3. Load 3 for RK06.

and

1404

(Continued on next page)

B-9

HARDWARE BOOTSTRAP PROCEDURES
Table B-6 (Cont.)
RLOl/02 and RK07 Load Routines
RL01/RL02
Bootstrap
Routine

RK07
Bootstrap
Routine

Address

Contents

1052:

5007

1054:

62701

1056:

1060:

10110

1062:

105710

1064:

100376

1066:

5710

1070:

100001

1072:

1074:

5007

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.
To load the routine, perform the following steps:
1.

Move the CPU console ENABLE/HALT switch to its HALT
and then 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

012700

010002

172524

010004

005310

010006

012740

010010

060011

010012

105710

B-10

into

memory

using

the

position

Switch

HARDWARE BOOTSTRAP PROCEDURES

Address

Contents

010014

100376

010016

005710

010020

100767

010022

012710

010024

060003

010026

105710

010030

100376

010032

005710

010034

100777

010036

005007

Set the console switch register to 010000.

Press the CPU LOAD ADRS switch.

Press the CPU START 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-11

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 1 lists the pseudo devices.
Table C-1
RSX-llM Devices
Mnemonic

Device

Hardware Controller

Analog-to-Digital Converter

ADOl-D

Analog-to-Digital Converter

AFCll

Laboratory Peripheral Subsystem

ARll

Card Reader

CRll/CMll-E

TU60 Cassette

TAll

RP04/0S/06 disk drive

RH11/RH70

TU58 DECtape II

DLll

RFll disk drive

RFll

RKOS/J/F cartridge disk drive

RKll

RL01/RL02 disk drive

RL11/RLV11/RL21/RLV21

RK06/07 cartridge disk drive

RK611/RK711

RP02/03 disk drive

RPlL/RPllC

RM02/03/05 disk drive
RM80/RP07 fixed media

RH11/RH70
RH70

RS03/04 fixed-head disk drive

RH11/RH70

TU56 DECtape

TCll
{Continued on next page)

C-1

RSX-UM DEVICES
Table C-1 (Cont.)
RSX-llM Devices
Mnemonic

Device

Hardware Controller

RAGO removable media
RA80/81 fixed media
RC25 fixed/removable media
RD51 fixed media
RD52 fixed media
RD53 fixed media
RXSO diskette
RX180 IBM-compatible diskette

UDA50/KDA50-Q
UDA50/KDA50-Q
RC25
RQDXl
RQDXl
RQDX3
RQDX1/RUX50
RUX SO

RXOl diskette drive

RXll

RX02 diskette drive

RX211/RXV21/RXV12

MLll Nonrotating Electronic Memory

RH70

Graphics Display Processor and Scope

VT11/VS60

Industrial Control Subsystem

ICR/ICSll

Industrial Control Subsystem

DRS/DSll

Laboratory Peripheral Accelerator

LPAll-K

Line Printer

LAll/LPll/LSll/LVll

Laboratory Peripheral Subsystem

LPSll

TU45/TU16/TE16/TU77 magnetic tape drive RH11/RH70/TM02/TM03

TS11/TSV05/TU80 magnetic tapes

TSll

TS03/TU10/TE10 magnetic tape drive

TMll/TMAll/TMBll

TKSO streaming cartridge tape

TQKSO

Paper Tape Punch

PCll

Paper Tape Reader

PCll/PRll

Universal Digital Controller

UDCll

Interprocessor Link

DAll-B

UNIBUS Ethernet Controller

DE UNA

Interprocessor Link

DLll-E

Interprocessor Link

DMC 11-E/DMRll

Synchronous Interface

DPll

Synchronous Interface

DQll

Synchronous Interface

DUll
(Continued on next page)

C-2

RSX-llM DEVICES
Table C-1 (Cont.)
RSX-llM Devices
Mnemonic

Device

Hardware Controller

Synchronous Interface

DUPll

Asynchronous Te.rminal Interface

DHll

Asynchronous Terminal Interface

DJll

Asynchronous Terminal Interface

DLll/A/B/C/D/E/J/W

Asynchronous Terminal Interface

DHUll/DHVll

Asynchronous Terminal Interface

DZll/DZQll/DZVll

Mnemonic

Pseudo Device

Hardware Controller

Console Listing Pseudo Device

N/A

Console Output Pseudo Device

N/A

Library Default Pseudo Device

N/A

Null Device

N/A

System Default Pseudo Device

N/A

Terminal Input Pseudo Device

N/A

C-3

APPENDIX D
FUNCTIONS IMPACTING POOL (DYNAMIC MEMORY)

Use the following information when calculating the amount of pool
(dynamic memory)
to allocate during Phase I of SYSGEN. Section D.l
describes the common functions and Section D.2 describes the real-time
functions.

D.l

COMMON FUNCTIONS

Tasks
Each task installed in the system requires at least 25(10)
for a Task Control Block.

words

I/O Requests
Each I/O request results in the allocation of an 18(10)-word
packet, which is queued to the appropriate device driver.

I/O

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.

D-1

FUNCTIONS IMPACTING POOL (DYNAMIC MEMORY)
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
RSX-llM.

window

block

7(10)

•

The variable portion of the window is the
3(10) words.

•

The window block is rounded up to the next 2(10)-word boundary
for RSX-llM.

window

words
size

for
times

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 values were specified or
• unreasonable,
then a value of 7 is used.

are

A value of -1 has special significance.
The window size is
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.
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 released only 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
(VCB)
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 requires 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 MOUNT /LRU or /ACCESSED
keywords.

D-2

FUNCTIONS IMPACTING POOL (DYNAMIC MEMORY)
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 the UVL is 8(10) words.
Foreign Mounted Disks and Tapes
Each tape or disk mounted foreign requires only a short VCB.
size of this VCB is 10(10) words.

The

Clock Queue Entries
Each clock queue entry requires 8{10)words.
These entries
represent marktime, schedule, and periodic scheduling requests.
AST-Related Processing
Each power-fail, 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 several.
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 decimal words per logical
unit) and 7(10) window blocks {8 decimal words per window block).

D-3

FUNCTIONS IMPACTING POOL (DYNAMIC MEMORY)
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
linkage as follows:
for

for

interrupt

•

14(10) words per interrupt
non-error-logging drivers

entry

•

22(10) words per interrupt
non-error-logging drivers

entry

•

14(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

for

single-controller,
multicontroller,

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
(PLAS)
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-4

FUNCTIONS IMPACTING POOL (DYNAMIC MEMORY)
D.2

REAL-TIME FUNCTIONS

LPSll (Laboratory Peripheral Subsystem)
System)

and

ARll

(Analog

Real-time

Each LPSll/ARll synchronous function requires 20(10) words for
secondary control block.

ICS/ICRll (Industrial Control Subsystem/Industrial Control Remote)
Each task linked to ICS/ICR interrupts requires 16(10) words of
dynamic memory, plus 6(10) 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.
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 affects 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 affects 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

Table 1 lists the devices sµpported 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 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 o~ 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

The headings for the table indicate the following information:
"Device" denotes the device being autoconfigured.
"CSR" denotes the CSR address for the device.
"Reg. Size" denotes register size, expressed in octal number of
bytes.
"1st Vector" denotes the location of the first vector for
the
device.
"Ctrl (max)" denotes the maximum number of controllers allowed
for the device.
"Int. Pri." denotes the interrupt priority for the device.
Table E-1
Autoconf iguration Device Support
Device

CSR

Reg.

TAll

177500

TU58 (on a DLll)

1st Vector

Ctrl (max)

Int.

260

176500

300

RKll

177404

220

RL11/RL211

174400

160

RK611/RK711

177440

210

RPll

176714

254

TCll

177342

214

UOA50/RQDX1/RC25 1

172150

154

RX11/RX211

177170

264

RH11/RH702

172040

204

RH11/RH70 3

172440

224

RH11/RH70 4

176300

100

150

RH11/RH70 (MLll)

176400

204

RH11/RH70 S

176700

254

TMll

172522

224

TSll

172522

224

LP/LS/LVll (LPA)

177514

200

LP/LS/LVll (LPB)

164004

170

1.
2.
3.
4.
5.

Size

Pri.

All MSCP devices.
RS03/RS04.
TU16/45/77, TE16.
RS/RP/RM/TU alternate.
RP04/05/06 or RM02/03/05.

(Continued on next page)

E-2

ADDRESS AND VECTOR ASSIGNMENTS
Table E-1 (Cont.)
Autoconf iguration Device Support

Device

CSR

Reg.

LP/LS/LVll (LPC}

164014

LP/LS/LVll (LPD}

1st Vector

Ctrl (max}

Int.

174

164024

270

LP/LS/LVll (LPE}

164034

274

LP/LS/LVll (LPF}

164044

774

LP/LS/LVll (LPG}

164054

770

LP/LS/LVll (LPH}

164064

764

PRll

177550

070

PCll

177554

074

DHll

FLOAT

Rank 16

16.

DLll-A/B/J

176500

Rank 2

16.

DLll-C/D/E

175610

Rank 14

31.

DL11-W6

177560

060

DMll-BB

170500

Rank 6

16.

DZll

FLOAT

Rank 28

16.

E.2

Size

Pri.

Console terminal.

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 1.
If the system contains
devices not listed, you must configure them manually.
The floating address space starts at 760010
764000.

and

proceeds

upward

A gap in the address space (there is no SLAVE SYNC signal on the
implies that a device do~s not exist.

to
bus)

The first address of a new type of device will always be on a 2n-word
boundary, where n is the first integer greater than or equal to LOG m
and m is the number of device registers.

E-3

ADDRESS AND VECTOR ASSIGNMENTS

Number of
in Device

Registers
Possible Boundaries

Any word

xxxxxO, xxxxx4

3,4

xxxxxO

5,6,7,8

xxxxOO, xxxx20, xxxx40, xxxx60

9 through 16

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 qt least one word but may be longer than one word.
Gap length is determined by the boundary on which the next device 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 modulo 20 boundary following the
last DHll.
After all DHll addresses and the DHll gap are defined, DQll, DUll,
DUPll, LKll,
DMCll, DZll, and KMCll addresses and the required gaps
can be assigned in sequence.
Addresses for any future floating
address devices will be assigned in a similar manner.

E.3

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-4

ADDRESS AND VECTOR ASSIGNMENTS
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.2

Worksheet Instructions

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 oan
read the UNIBUS address for each device unit directly from
the worksheet.

E-5

t:rJ

;

"CS

.....

(EXAMPLE 1)

FLOATING ADDRESS WORKSHEET

DEVICE

DEVICE
ADDRESS

ADDRESSDDDDDL
J

H
1
1

U
1
1

U
p
1

K M Z M
p

1
1

c
1

1
1

c
1

1
1

ADDRESS

1
1

D
M

.....

z M

l'zj

761400

761020

761420

761030

761430

.....

~~~t~

761410

[]

761010

760430

761000
760410

t:rJ

rt
.....

761040

::s

[]

761050

760450

761070

761470

760500

761100

761500

760510

761110

'°g:
::::::~

0..
11

761120

761530

761130

760530

fn
fn

761540

760540

761550

761150

760550

761560

~~t~

760570

761170

760600

761200

761600

760620

761220

761620

760230

760630

761230

761630

760240

760640

761240

761640

760650

761250

761650

:::r

~:~:~:~:

CD
CD

760260

:::::::~

760270

760670

760300

760700

760310

760710

760320

760720

760330

760730

761330

[]

761300

761700

761310

761710

761320

761720

761340

761740

760350

760750

761350

761750

760360

760760

761360

760370

760770

761370

760340

DDDDDLDDK

JHOU

1
1

KMZM

1
1

_..i_

0
DH11
0011 ~
__Q__
DU11
I
DUP11
0
LK11

DMC11
DZ11
KMC11

1
1

7~00{0

vz.

_,_

Zl>OO~

PZ.

7~0010

..AL

'DJ

-1!_

]>:J"

p\JP

Dr1C.

(/)

7"0£;1.o

l>HC
1'Z.

lfo0£~0

U
p

DEV

ADDRESS

UNIT

-'-

MZM
p

DEV

QTY(n)

QTY (n)
DJ11

1
1

11
QI

.....

UNIT

__Q_

1
1

ADDRESS

DEV

D
1
1

D
p

UNIT

z
1

:s
.....

K
M

ADDRESS

]&:,0/(,0

7roo170
1'40J/()

7fi(2£ :;i0
ZK-357-81

<
t:rJ
0

G'l

'°c::

z>'

::s

.....

762000

t:rJ
tn
tn

tn
tn

t'h

761770

761400

761000

760400

::::::::

0
0

.....

~
t:rJ
z
~

t:r:J

"O
......

(EXAMPLE 2)

FLOATING ADDRESS WORKSHEET

(I)

DEVICE

DEVICE
ODDDLDD
HQUUKMZ

ADDRESS

J
1

D
H
1

D
Q

D
U

ADDRESS

D
U
1
1

c
1

1
1

D 0 0 D 0 L
JHOUUK
1
1

z
1

tr.I
I

1
t

l'Zj

760400

760000
760010

760410

760020

760420

760030

760430

760040

760440

760050

760450

760060

760460

760070

760470

......
D>
rt

....

760110

760510

760120

760520

760130

760530

760150

760550

760160

760560

760170

760570

760200

760600

761200

761220

760220

760620

......i

760230

760630

'°

761470

760500

760210

::s

761060

760100

t:rJ
I

761420

76\530

(I)

t:rJ
tll
tll

1:/.1
1:/.1

)ii

<
t:r:J

761250

761650

761260

761660

760270

760670

761270

760300

760700

761300

760310

760710

n
0
::s

761720

760320
760330

....'""

761730

761330

'°c

760740
761350

760350

760360

D>
rt

761370

760770

760370

....

761400

760400

0
J
1
1

H
1
1

1
1

p
1

D
J

D
H

1
1

DDDDDLDD
QUUKMZ

DDDDDLD
JHQUUKMZ
1
1

1
1

c
1

1
1

1
t

p
t

1
1

QTY (n)
DJ11

_0
__

DH11

0011
DU11

__
/_

DUP11 _0
__
LK11 __

o__

DMC11
DZ11
KMC11

QTY (n)
0

DEV

UNIT

1>H

J>tf

_.3_

_o_

J)f/

.1.B....

.1JL

-'~

=:L
_J_
4-

ADDRESS
7fob0()...0

7foOO'l0
ZtoOOW
7(eOfl0

UNIT

ADDRESS

7food.IO
l(pO.J.?9

7'20,230

-'-

DEV

UNIT

ADDRESS

7<Pol:Lo
7(pq{Lf0
ZK-358-81

::1'

760650

1:/.1

(I)
(I)

760240
760250

0
0

a..
a..
761130

)ii

tll
tll
1-4

G"l

z
:x
t:rJ
z
~

tll

tzJ
>C
DJ

ADDRESSD

U
p

OODDL

DOK

I
1

1
1

ADDRESS

....
(I)

DEVICE

(EXAMPLE 3)

FLOATING ADDRESS WORKSHEET

ADDRESSD

DDODL

JHQ

760400

761400

760410

761410

DOK

tzJ
I

KMZM

....DJ03

::::;:::

761420

760440

761040

760450

761050

~?t

761450

760460
760470

761470

760500

761500

itli

::::::::

....~

::·:·:·:
·:·:-.::

::::::::

761510

761520

760520
760530

761440

761460

760510

761430

760430

H~~~

:s
\Q

::::::::

761530
761540

::::::::

760170

t:i:j

I
CX>

760550

761550

760560

761560

760570

761570

760200

760600

760210

760610

760220

760620
:::;::::

761640

760650

761650

760260

760660

761660

760270

760670

760300

760700

761300

761700

760310

760710

761310

761710

760720

761320

761720

760730

761330

761730

760740

761340

761740

760750

761350

760360

760760

761360

761760

760370

760770

761370

761770

761000

761400

762000

~~~t~

760330
760340

760350

760400
D

ODDODLDDK

DDDOLDD

JHOUUK
1 1 1 p 1

HOUUKMZ

QTY (n)

QTY(n)
DJ11
DH11
0011
DU11
DUP11 _ __
LK11

DEV

UNIT

p
1
1

ADDRESS

DEV

1
1

UNIT

c
1

1
1

rn
:r
(I)

.:::::::

~~~l

(I)

i~i~i~~~

tzJ

'>'°

00
....
G'l
z

3:
~

DEV

z>'

HOUUKMZ

ADDRESS

tzJ
00
00

::::::::
DDDDLDDK

'°

tzJ

~§f

761750

~
t1

~;~~~~~;

761670

'::::::::

rn
rn

~~~f~

761630

760640

760320

(I)

tt
761230

::::::::

:;~~~=~=

761600

761200

~=~=~=~:

760230

>'
c..
c..

·:·:-:::

0
0

UNIT

ADDRESS

DMC11
DZ11
KMC11

--ZK-359-81

APPENDIX F
DIRECTORY LISTINGS

This appendix lists the user file directories (UFOs) that make up the
RSX-llM Version 4.2 distribution kits. The directories are listed
under the label of the volume they are located on in the RLOl disk
distribution kit.
Therefore,
if your disk distribution kit is one
other than an RLOl, you can use Table F-1 as a guide to the location
of directories or files.

F.l

DISK DISTRIBUTION KIT VOLUME CONTENTS

Table 1 lists the number of disks, the volume labels, and the volume
contents of each type of disk distribution kit.
You can then refer to
the list of directories under the appropriate volume labels to find
the locations of specific directories and files in your type of kit.
Table F-1
Volume Contents
Disk
Type

Number of
Disks

Volume
Label(s)

RLOl Volume
Contents

RLOl

RSXM38
EXCPRV
PRVBLD
RLUTIL
MC RS RC
HLPDCL
RMSV20

RL02

RSXM38
EXCPRV
PRVBLD
MC RS RC
RMSV20

RSXM38
EXCPRV
PRVBLD, RLUTIL
MCRSRC, HLPDCL
RMSV20

RK06

RSXM38
CLISRC

RSXM38, EXCPRV, PRVBLD, RLUTIL
MCRSRC, HLPDCL, RMSV20

All other disks

RSXM38

All volumes

F-1

DIRECTORY LISTINGS

RSXM38

F.1.1

RSXM38
UFD [1,1]
EXEMC.MLB;l
EXELIB.OLB;l
KITIDENT.DAT;l
ODT.OBJ;l
TRACE.OBJ;!
VMLIB.OLB;l
RSXMAC.SML;l
DEUNA.MLB;l
UNAMC.TSK;l
LUAMC.TSK;l
SYSLIB.OLB;l

73.
48.
1.
8.
3.
16.
287.
18.
3.
3.
238.

Total of 698./705. blocks in 11. files
UFD [1,2]
STARTUP.CMD;l
RMSINSTAL.CMD;l
QIOSYM.MSG;l

6.
14.
29.

Total of 49./49. blocks in 3. files
UFD [1,3]
Total of 0./0. blocks in 0. files
UFD [1,4]
Total of 0./0. blocks in 0. files
UFD [1,6]
Total of

o.;o. blocks in o. files
UFD [1,7]

Total of 0./0. blocks in

o. files

UFD [1,20]
Total of 0./0. blocks in 0. files
UFD [1,24]
Total of 0./0. blocks in O. files

F-2

DIRECTORY LISTINGS

RSXM38 (Cont.)

UFO [1,30]
Total of 0./0. blocks in

o. 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]
ACS.TSK;l
DMO.TSK;l
FCPSML.TSK;l
ICP.TSK;l
INS.TSK;l
LOA.TSK;l
MCR.TSK;l
MOU.TSK;l
RCT.TSK;l
SAV.TSK;l
TKN.TSK;l
UNL.TSK;l
DBDRV.TSK;l
DBDRV.STB;l
DDDRV.TSK;l
DDDRV.STB;l
DKDRV.TSK;l
DKDRV. STB; 1
DLDRV.TSK;l
DLDRV.STB;l
DMDRV.TSK;l
DMDRV. STB; 1
DPDRV.TSK;l
DPDRV.STB;l
DRDRV.TSK;l
DRDRV.STB;l
DUDRV.TSK;l
DUDRV.STB;l
DXDRV.TSK;l
DXDRV.STB;l
DYDRV.TSK;l
DYDRV.STB;l
PUCOM.TSK;l
PUCOM.STB;l
LPDRV.TSK;l
LPDRV. STB; 1
MMDRV.TSK;l
MMDRV.STB;l
MSDRV.TSK;l
MSDRV. STB; 1
MTDRV.TSK;l
MTDRV.STB;l

14.
15.
96.
143.
60.
29.
115.
46.
11.
78.
18.
2 3.
5.
1.
6.
1.
4.
1.
4.
1.
5.
1.
3.
1.
5.
1.
10.
2.
4.
1.
5.
1.
6.
1.
4.
1.
7.
1.
7.
1.
6.
1.

F-3

DIRECTORY LISTINGS

RSXM38 (Cont.)

MUORV.TSK;l
MUORV.STB;l
RSXllM.SYS; 1
RSXllM. STB; 1
BRU.TSK;l
SGNPARM.CMO;l
ACF.BSL;l
BOO.TSK;l
INI.TSK;l
UFO.TSK;l
RSXllM.TSK;l
BASVMR.CMO;l
ACO.TSK;l
VMR.TSK;l
MFT.TSK;l
EOI.TSK;l
FLX.TSK;l
LBR.TSK;l
MAC.TSK;l
PIP.TSK;l
SLP.TSK;l
TKB.TSK;l

9.
2.
258.
13.
181.
4.
28.
33.
58.
8.
114.
1.
40.
165.
147.
61.
132.
72.
89.
73.
48.
182.

Total of 2463./2463. blocks in 64. files
UFO (1,60]
Total of 0./0. blocks in

o. files

UFO (1,64]
Total of

o.;o. blocks in o. files
UFO [11,20]

Total of 0./0. blocks in

o. files

UFO (11,24]
Total of 0./0. blocks in

o. files

UFO (11,30]
Total of 0./0. blocks in

o. files

UFO (11,34]
Total of 0./0. blocks in

o. files

F-4

DIRECTORY LISTINGS

RSXM38 (Cont.)

UFO [200,200]
TAPEKIT.CMD;l
SGNTYP.CMO;l
BLDLAINIT.CMO;l
SGNSTANO.CMD;l
SGNBLDORV.CMO;l
SYSGEN.CMD;l
SYSGEN2.CMO;l
UPOATE.CMO;l
SGNKLAB.CMO;l
SYSGEN3.CMD;l

16.
1.
15.
4.
22.
74.
85.
15.
70.
44.

Total of 346./346. blocks in 10. files
UFO [l, 11]
Total of 0./0. blocks in O. files
UFO [11,10]
ICORV.MAC;l
ISDRV.MAC;l
TTORV.MAC;l
TTATT.MAC;l
TTCAN.MAC;l
TTCIS.MAC;l
TTDAT.MAC;l
TTFP.MAC;l
TTICH.MAC;l
TTINI .MAC; 1
TTJZ.MAC;l
TTMAC.MAC;l
TTMIS. MAC; 1
TTMOD.MAC;l
TTOON.MAC;l
TTOIS.MAC;l
TTRW.MAC;l
TTSUB.MAC;l
TTTBL.MAC;l
TTYH.MAC;l
TTYHV.MAC;l
TTYJ.MAC;l

179.
32.
262.
171.
34.
19.
104.
37.
206.
78.
8.
30.

TTYL.MAC;l
TTYZ.MAC;l

14.
19.

7.
28.
19.
16.
117.
75.
23.
43.
49.
6.

Total of 1576./1576. blocks in 24. files
UFO [12, 20]
Total of 0./0. blocks in O. files
UFO [12,24]
Total of 0./0. blocks in O. files
Grand total of 5132./5139. blocks in 112. files in 23.
directories
F-5

DIRECTORY LISTINGS

EXCPRV

F.1.2

EXCPRV
UFO [ 1, 30]
Total of 0./0. blocks in

o. files

UFO [1,34]
Total of 0./0. blocks in

o. files

UFO [11, 10]
RSXMCO .MAC; 1
BFCTL.MAC;l
CORAL.MAC;!
CRASH.MAC;!
CVRTM. MAC; 1
DRABO.MAC;l
DRASG.MAC;l
DRATP.MAC;l
DRATX. MAC; 1
DRCIN.MAC;l
DRCL I. MAC; 1
DRCMT.MAC;l
DRDAR.MAC;l
DRDCP.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
DRSMG.MAC;l
DRSWS.MAC;l
DRPUT.MAC;l
DRQIO.MAC; 1
DRRAS.MAC;l
DRREG.MAC;l
DRREQ.MAC;l
DRRES.MAC;l
DRSED.MAC;l
DRSPW.MAC;l
DRSST.MAC;l
DRSUB.MAC;l
ERROR.MAC;!
ERSUB.MAC;l
EXDBT.MAC;l
EXESB.MAC;l

8.
18.
29.
118.
5.
4.
10.
12.
9.
21.
33.
7.
6.
8.
46.
42.
16.
36.
19.
1.
6.
11.
3.
12.
16.
58.
11.
13.
7.
22.
7 5.
15.
3 7.
5.
12.
26.
86.
9.
38.
39.
40.
87.
28.

F-6

DIRECTORY LISTINGS

EXCPRV (Cont.)

INITL.MAC;l
IOSUB.MAC;l
LOADR.MAC;l
LOWCR.MAC;l
MDSUB.MAC;l
MEMAP.MAC;l
PANIC.MAC;!
PARTY.MAC;!
PLSUB.MAC;l
POWER.MAC;!
PMT.MAC;l
QUEUE.MAC;!
REQSB.MAC;l
SSTSR.MAC;l
SYSCM.MAC;l
SYSDF.MAC;l
SYSXT.MAC;l
SYTAB.MAC;l
TDSCH.MAC;l
ADDRV.MAC;l
AFDRV.MAC;l
ARDRV.MAC;l
CTDRV.MAC;l
DDDRV.MAC;l
DBDRV.MAC;l
DFDRV.MAC;l
DKDRV.MAC;l
DLDRV.MAC;l
DMDRV.MAC;l
DPDRV.MAC;l
DRDRV.MAC;l
DSDRV.MAC;l
DSSDI.MAC;l
DTDRV.MAC;l
DU.MAC;l
MU.MAC;l
DSAPRE.MAC;l
MSCPDRV.MAC;l
PUCOM.MAC;l
DXDRV.MAC;l
DYDRV.MAC;l
DYCOM.MAC;l
EMDRV.MAC;l
GRDRV.MAC;l
ICOM.MAC;l
ISCOM.MAC;l
LKDRV.MAC;l
LSDRV.MAC;l
MFDRV.MAC;l
MMDRV.MAC;l
MSDRV.MAC;l
MTDRV.MAC;l
NLDRV.MAC;l
NTDRV.MAC;l
PPDRV.MAC;l
PRDRV.MAC;l
UDCOM.MAC;l
UDDRV.MAC;l

34.
53.
54.
6.
41.
39.
16.
20.
16.
25.
82.
22.
105.
31.
39.
10.
98.
11.
20.
10.
17.
61.
19.
67.
49.
21.
23.
50.
71.
26.
62.
22.
7.
23.
2.
3.
20.
283.
88.
36.
80.
2.
20.
49.
4.
2.
33.
74.
126.
77.
91.
60.
4.
6.
14.
12.
7.
54.

F-7

DIRECTORY LISTINGS

EXCPRV (Cont.)

XBORV.MAC;l
XLORV.MAC;l
XPORV.MAC;l
XQORV.MAC;l
XUORV.MAC;l
XWORV.MAC;l
COORV .MAC; 1
CRORV.MAC;l
LAORV.MAC;l
LPORV.MAC;l
XEORV .MAC; 1
XEPRE.MAC;l
XMORV.MAC;l

28.
28.
25.
41.
27.
27.

10.
37.
93.
23.
421.
1.
66.

Total of 4328./4328. blocks in 114. files
UFO [11,20]
Total of 0./0. blocks in O. files
UFO [11,24]
Total of 0./0. blocks in O. files
UFO [12,10]
OV20V.MAC;l
SPSOV.MAC;l
STSUB.MAC;l
SXlOV.MAC;l
SX20V.MAC;l
SX30V.MAC;l
SX40V.MAC;l
ST50V.MAC;l

51.
71.

16.
42.
52.
18.
52.
49.

Total of 351./351. blocks in 8. files
UFO [12,20]
Total of 0./0. blocks in O. files
UFO [12,24]
Total of 0./0. blocks in O. files
UFO [200,200]
SGNEXEC.CMO;l
SGNICIS.CMO;l
SGNPER.CMO;l
SGNTT.CMO;l

186~

46.
189.
44.

Total of 465./465. blocks in 4. files
Grand total of 5144./5144. blocks in 126. files in 9. directories
F-8

DIRECTORY LISTINGS

PRVBLD

F.1.3

PRVBLD
UFO [l, 1]
KMCLP.BIN;l
FCSMTA.OBJ;l
LPA.OBJ;l
LPS.OBJ;l
PURICR.OBJ;l
PURISA.OBJ;l
PURPCS. OBJ; 1
PURUDC.OBJ;l

6.
30.
16.
5.
6.
8.
14.
3.

Total of 88./88. blocks in 8. files
UFO [ l ,, 20]
ACSBLD.BLD;l
BOOBLD.BLD;l
BYEBLD.BLD;l
HELBLD.BLD;l
INSBLD.BLD;l
LOABLD.BLD;l
LPIBLD.BLD;l
MCRBLD.BLD;l
MCMBLD.BLD;l
PMDBLD.BLD;l
SAVBLD.BLD;l
SHFBLD.BLD;l
SHUBLD.BLD;l
TKNBLD.BLD;l
UNLBLD.BLD;l
UMLBLD.BLD;l
ACNBLD.BLD;l
BROBLD.BLD;l
COTBLD.BLD;l
DCLBLD.BLD;l
DMOBLD.BLD;l
ELIBLD.BLD; 1
ERLBLD.BLD;l
FCPMINBLD.BLD;l
FCPSMLBLD.BLD;l
FCPMDLBLD.BLD;l
FCPLRGBLD.BLD;l
FCSRSlBLD.BLD;l
FllMSGBLD.BLD;l
ICPBLD.BLD;l
ICQBLD.BLD;l
ICPCOMBLD.BLD;l
LPPBLD.BLD;l
INIBLD.BLD;l
MOUBLD.BLD;l
MTABLD.BLD;l
PMTBLD.BLD;l
PRTBLD.BLD;l
QMGBLD.BLD;l

2.
5.
3.
8.
3.
4.
2.
18.
10.
11.
14.
2.
2.
2.
2.
2.
4.
2.
5-.
21.
3.
4.
5.
18.
12.
18.
10.
12.
3.
8.

9.
22.
21.
7.
4.
18.
8.
10.
17.

F-9

DIRECTORY LISTINGS

PRVBLD (Cont.)

QCLBLD.BLD;l
QPRBLD.BLD;l
RCTBLD.BLD;l
RMDBLD.BLD;l
TDXBLD.BLD;l
UFDBLD.BLD;l
ICBLD.CMD;l
ISBLD.CMD;l
UDCBLD.CMD;l
LPINIT.OBJ;l
SYSROT.OBJ;l
BOO.OLB;l
ERL.OLB;l
FCP.OLB; 1
FIL.OLB;l
FllMSG. OLB; 1
ICPllM. OLB; 1
ICQllM.OLB;l
!NI .OLB; 1
INS.OLB;l
LOA.OLB;l
MCR.OLB;l
MLTUSR.OLB;l
MTA.OLB;l
PMD.OLB;l
RMD.OLB;l
SAV.OLB;l
DCLO.OLB;l
DCLR.OLB;l
LAINIT.OLB;l
PRT.OLB;l

9.
2.

2.
15.

2.
2.
1.
1.
1.

4.
1.
11.
35.
88.
124.
9.
126.
129.
84.
35.

43.
195.
81.
102.
31.
71.
66.
739.

54.
21.
19.

Total of 2434./2436. blocks in 70. files
UFO [ 1, 24]
ICBLD.CMD;l
ISBLD.CMD;l
UDCBLD.CMD;l
LPINIT.OBJ;l
SHUFL.OBJ;l
SYSROT.OBJ;l
TDX.OBJ;l
BOO.OLB;l
COT.OLB;l
ERL.OLB;l
FCP.OLB; 1
FIL.OLB;l
ICPllM. OLB; 1
ICQllM. OLB; 1
!NI .OLB; 1
INS .OLB; 1
LOA.OLB;l
LPP.OLB;l
MCR.OLB;l
MLTUSR.OLB;l
MTA.OLB;l
PMD.OLB;l

1.
1.
4.
4.
1.
12.
11.
26.
35.
92.

124.
127.
133.
84.
37.
4 7.
60.
230.
81.
103.
33.

F-10

DIRECTORY LISTINGS

PRVBLD (Cont.)

QMG.OLB;l
QMGCLI .OLB; 1
RCT.OLB;l
RMD.OLB;l
SAV.OLB;l
UML.OLB;l
LAINIT.OLB;l
PIPUTL.OLB;l

7 5.
90.
18.
99.
69.
6.
21.

26.

Total of 1651./1654. blocks in 30. files
UFD [l, 30]
Total of 0./0. blocks in O. files
UFD [l, 34]
Total of 0./0. blocks in O. files
UFD [11,20]
Total of 0./0. blocks in

o. files

UFD [11,24]
Total of 0./0. blocks in

o. files

UFD [12,20]
Total of 0./0. blocks in 0. files
UFD [12, 24]
Total of 0./0. blocks in 0. files
Grand total of 4173./4178. blocks in 108. files in 9. directories

F-11

DIRECTORY LISTINGS

RLUTIL

F.1.4

RLUTIL
UFO [l,20]
ACOBLD.BLD;l
ACFBLD.BLD;l
BADBLD.BLD;l
BRUBLD.BLD;l
CDABLD.BLD;l
CFLBLD.BLD;l
CMPBLD.BLD;l
CRFBLD.BLD;l
DSCBLD.BLD;l
DMPBLD. BLD; 1
EDIBLD.BLD;l
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
MAKESTK.CMD;l
TKBBLD.BLD;l
TKBCOMBLD.BLD;l
VFYBLD.BLD; 1
VMRBLD.BLD;l
ZAPBLD.BLD;l
CDA.OLB;l
VMR.OLB;l
BAD.OLB;l
BRU.OLB;l
CMP.OLB;l
CRF.OLB;l
DSC.OLB;l
DMP.OLB;l
EDI.OLB;l
EDTLIB.OLB;l
FLX.OLB;l
FMT.OLB;l

3.
2.
2.
8.
21.
10.
6.
11.
7.
9.
8.
47.
18.
4.
5.
22.
24.
18.
8.
25.
16.
7.
9.
4.
9.
24.
9.
13.
4.
159.
237.
36.
287.
26.
40.
164.
39.
57.
376.
143.
55.

FTB.OLB;l
IOX.OLB; 1
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
UML.OLB;l
VFY.OLB;l
ZAP.OLB;l

112.
128.
70.
150.
14.
34.
96.
26.
220.
34.
314.
6.
53.
33.

Total of 3262./3312. blocks in 55. files
F-12

DIRECTORY LISTINGS

RLUTIL (Cont.)

UFO [1,24)
ACF.OLB;l

36.

Total of 36./36. blocks in 1. file
UFO [1,30)
Total of 0./0. blocks in

o. 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,51)
BRU64K.SYS;l
BRU64K.STB;l
BRUSYS.SYS;l
BRUSYS.STB;l

258.
13.
434.
13.

Total of 718./718. blocks in 4. files
UFO [1,54]
Total of O./O. blocks in

o. files

Grand total of 4016./4066. blocks in 60. files in 7. directories

F-13

DIRECTORY LISTINGS

MCRSRC

F .1. 5

MCRSRC

UFO [ 1, 1]
EXEMC.MLB;l
RSXMAC.SML;l

73.
287.

Total of 360./360. blocks in 2. files
UFO [l, 2]
Total of 0./0. blocks in

o. files

UFO [11, 10]
Total of 0./0. blocks in O. files
UFO [12,lOJ
BYE.MAC;!
BRKOV.MAC;l
CBTO.MAC;l
CDT2B.MAC;l
COT2B.MAC;l
DFSYM.MAC;l
EDCKP.MAC;l
FMTDV.MAC;l
GNBLK.MAC;l
GTBYT.MAC;l
GTMNM.MAC;l
GTTSK.MAC;l
ICBDEF.MAC;l
ABOOV.MAC;l
BOOT.MAC;l
BOTPH2.MAC;l
ALLSUB.MAC;l
FLAOV.MAC;l
SAVSUB.MAC; 1
MCRDIS.MAC;l
INSFSR.MAC;l
INSGC.MAC;l
KEYWD.MAC;l
LDBUF.MAC;l
LDCTL.MAC;l
LDDRV.MAC;l
LDFIL.MAC;l
LDUIC.MAC;l
LKLST.MAC;l
CLQOV.MAC;l
RAPOV.MAC;l
REAOV.MAC;l
MCROV.MAC;l
STlOV.MAC;l

47.
3.

7.
6.

4.
19.
4.
4.

6.
4.
8.

24.
29.

19.
21.

19.
35.

80.
2.
2.

6.
31.

26.
8.
3.
7.
19.
14.
7.
60.
36.

F-14

DIRECTORY LISTINGS

MCRSRC (Cont.)

TISUBS.MAC;l
UNLFIL.MAC;l
MDPOV.MAC;l
INSLB.MAC;l
SAVSIZ.MAC;l
INSFL.MAC;l
TKTN.MAC;l
IODAT.MAC;l
FILBN.MAC;l
ALLOV.MAC;l
DEVOV.MAC;l
SX40V.MAC;l
SX20V.MAC;l
SAVCPU.MAC;l
MCRDEF.MAC;l
PRlOV.MAC;l
SPSOV.MAC;l
ST20V.MAC;l
SAVFN.MAC;l
WRTMS.MAC;l
SYSROT.MAC;l
SAVST.MAC;l
SAVTRC.MAC;l
SAVBOT.MAC;l
SAVCl.MAC;l
SAVDB.MAC;l
SAVDF.MAC;l
SAVDK.MAC;l
SAVDL.MAC;l
SAVDM.MAC;l
SAVDP.MAC;l
SAVDR.MAC;l
SAVDS.MAC;l
SAVDT.MAC;l
SAVDX.MAC;l
SAVDRT.MAC;l
SAVDY.MAC;l
LDFIN.MAC;l
TIMOV.MAC;l
MCROOT.MAC;l
LUNOV.MAC;l
SYMTB.MAC;l
OPEOV.MAC;l
SSMOV.MAC;l
SAVEM.MAC;l
FNDUCB.MAC;l
SXlOV.MAC;l
INSBF.MAC;l
ACTFIL.MAC;l
ST30V.MAC;l
SRTOV.MAC;l
ERMSG.MAC;l
SX30V.MAC;l
GETNUM.MAC;l
INSCM.MAC;l
STSUB.MAC;l
ASNOV.MAC;l
CLIOV.MAC;l
SAVDU.MAC;l

4.
6.
10.
71.
26.
17.
50.
7.
21.
25.
45.
52.
52.
23.
4.
8.
71.
39.
16.
6.
11.
14.
2.
17.
20.
15.
12.
13.
18.
15.
14.
19.
13.
13.
19.
4.
18.
33.
26.
11.
13.
14.
62.
4.
13.
8.
42.
6.
6.
46.
29.
15.
18.
4.
10.
16.
55.
76.
28.

F-15

DIRECTORY LISTINGS

MCRSRC (Cont.)

BOOTRC.MAC;l
LDLDB.MAC;l
COLOG.MAC;l
SAVC2.MAC;l
SAVC3.MAC;l
MGCML.MAC;l
NETSUB.MAC;l
REQCOT.MAC;l
ACS.MAC;!
ALTOV.MAC;l
DEAOV.MAC;l
ATLOV.MAC;l
FIXOV.MAC;l
INSROT.MAC;l
SYSOV.MAC;l
REDOV.MAC;l
PAROV.MAC;l
TASOV.MAC;l
SAVE.MAC;!
ST40V.MAC;l
INSPS.MAC;l
INSHD.MAC;l
UNLCTL.MAC;l
ERRMSG.MAC;l
ERROV.MAC;l
RPSOV.MAC;l
RUNOV.MAC;l
DV20V.MAC;l
SAVINS.MAC;l
STSOV.MAC;l
ICPASK.MAC;l
ICPASV.MAC;l
ICPASl.MAC;l
ICPAS4.MAC;l
ICPCHA.MAC;l
ICPCHN.MAC;l
ICPERA.MAC;l
ICPFDC.MAC;l
ICPFEX.MAC;l
ICPFIL.MAC;l
ICPFMI.MAC;l
ICPFMO.MAC;l
ICPFMS.MAC;l
ICPFMX.MAC;l
ICPFUT.MAC;l
ICPFlO.MAC;l
ICPF52.MAC;l
ICPGNB.MAC;l
ICPGOT.MAC;l
ICPIFl.MAC;l
ICPIF2.MAC;l
ICPIF4.MAC;l
ICPMEM.MAC;l
ICPMEN.MAC;l
ICPNEC.MAC;l
ICPNEI .MAC; 1
ICPNEN.MAC;l
ICPNET.MAC;l
ICPNEX.MAC;l

2.
22.
9.
17.
6.
35.
2.
11.
23.
15.
9.
49.
31.
18.
23.
13.
24.
37.
62.
29.
26.
28.
30.
11.
15.
30.
26.
51.
68.
49.
6.
14.
12.
9.
7.
9.
5.
12.
4.
2.
2.
2.
27.
4.
22.
2.
1.
6.
16.
9.
6.
9.
5.
2.
1.
1.

2.
14.
3.

F-16

DIRECTORY LISTINGS

MCRSRC (Cont.)

ICPNPR.MAC;l
ICPNPl. MAC; 1
ICPPRS.MAC;l
ICPSTP. MAC; 1
ICPSUT.MAC;l
ICPSUl.MAC;l
ICPSU 5. MAC; 1
ICPSY2. MAC; 1
IC PS Y 3 • MAC ; 1
ICPTES.MAC;l
ICPTPA.MAC;l
IN I ALL. MAC; 1
INIBIT. MAC; 1
INIHOM.MAC; 1
ININDX.MAC; 1
INIMAG.MAC;l
INIUPD.MAC; 1
INIPAR.MAC;l
UFD.MAC;l
UFDPAR.MAC;l
UFDPTB.MAC;l
UFDTP.MAC;l
ICPVEC.MAC;l
ICPPOP.MAC;l
ICPIN5.MAC; 1
ICPENB.MAC;l
ICPSU2.MAC;l
ICPIF3.MAC;l
ICPWFT. MAC; 1
ICPXMD.MAC;l
IC PAS 2 • MAC ; 1
ICPAS3. MAC; l
ICPSU3.MAC;l
ICPGTN.MAC;l
IC PIN 4 • MAC ; 1
MOUCLS.MAC;l
MOUPRE.MAC;l
CRETSK.MAC;l
MSGOUT.MAC;l
TPNUMB.MAC;l
TPARS2.MAC; 1
TPDEB.MAC;l
TPMAC2.MAC; 1
MOUDIS.MAC;l
SMLGCL.MAC;l
IC PAS 5 • MAC ; 1
MOUMSG.MAC;l
MOUDAT.MAC;l
ICPSU4.MAC; 1
ICPONR.MAC;l
ICPERR.MAC;l
ICPATS.MAC;l
ICPPAR.MAC;l
DISMNT.MAC;l
ICPEXF.MAC;l
ICPIN3.MAC;l
ICPMCR. MAC; 1
ICPPOl.MAC;l

1.
5.
6.
5.

5.
20.
4.
13.
12.
11.

7.
21.
3 5.
23.
38.
42.
41.
112.
23.
16.
7.
6.
2.
12.

6.
19.
23.
8.
10.
4.
10.
11.
18.

4.
18.
21.

4.
16.
12.
8.
44.
5.
32.
24.
15.
8.
16.
18.
8.
32.
18.

14.
18.

79.
14.
18.

7.
8.

F-17

DIRECTORY LISTINGS

MCRSRC (Cont.)

ICPSYT.MAC;l
ICPSYl.MAC;l
ICPTOV.MAC;l
ICPSUB.MAC;l
ICPBLK.MAC; 1
ICPPRC.MAC;l
INIBAO.MAC; 1
ICPPRE.MAC;l
MOUFOR.MAC;l
MOUPAR.MAC;l
MOUSUB.MAC;l
MOUTAP.MAC;l
ICPGTK.MAC;l
ICPINX.MAC;l
ICPSET.MAC;l
ICPPOW.MAC;l
ICPEXI.MAC;l
ICPSYC.MAC;l
ICPIMP. MAC; 1
ICPFCL.MAC;l
VMSPAR.MAC;l
INIGCL.MAC;l
ICPIN2.MAC;1
ICPFOP.MAC;l
MOUOSK.MAC;l
MOUROT.MAC;l
ICPROT.MAC;l
ICPSU6. MAC; 1
HELLO.MAC;!
INIROT.MAC;l
XEPRE.MAC;l
INOSYS.CLB;l

2 7.
27.
18.
28.
8.
13.
SS.
31.
31.

43.
S3.
39.
13.
6.

7.
lS.
12.
16.
33.
8.
1.
70.
9.
21.
26.
9.
33.

s.
sa.

130.

1.
106.

Total of 4874./4968. blocks in 242. files
UFO [12,20]
LOAASM.CMO;l
MCRASM.CMO;l
MCRLIBBLO.CMO;l
FILASM.CMO;l
FILLIBBLO.CMO;l
ICPASM.CMO;l
ICPLIBBLO.CMO;l
INIASM.CMO;l
INILIBBLO.CMO;l

2.
14.
3.
4.
1.
12.
2.
2.
1.

Total of 41./41. blocks in 9. files
UFO [12,24]
LOAASM.CMO;l
MCRASM.CMO;l
MCRLIBBLO.CMO;l
FILASM.CMO;l
FILLIBBLO.CMO;l

2.
14.
3.
4.
1.

F-18

DIRECTORY LISTINGS

MCRSRC (Cont.)

ICPASM.CMO;l
ICPLIBBLO.CMO;l
INIASM.CMO;l
INILIBBLO.CMO;l

12.
2.
2.
1.

Total of 41./41. blocks in 9. files
UFO [12,30]
Total of 0./0. blocks in

o. files

UFO [12,34]
Total of 0./0. blocks in

o. files

UFO [14,10]
GBLCHA.MAC;l
V05CHA.MAC;l
V50CHA.MAC;l
V52CHA.MAC;l
VlHCHA.MAC;l
GBLGBM. MAC; 1
GBLHLM.MAC;l
V05HLM.MAC;l
V50HLM.MAC;l
V52HLM.MAC;l
VlHHLM.MAC;l
L36HLM.MAC;l
GBCMO.MAC;l
GB PAGE. MAC; 1
HLPAGE.MAC;l
NULllS.MAC;l
GBINIT.MAC;l
GBLMOM.MAC;l
L36CHA.MAC;l
RMORIV.MAC;l
TERMIO.MAC;l
ATCMO.MAC;l
GBLATM.MAC;l
V05ATM.MAC;l
GBLTHM.MAC;l
V52ATM.MAC;l
L36THM.MAC;l
V50ATM.MAC;l
THCMO.MAC;l
VlHATM.MAC;l
L36ATM.MAC;l
VlHTHM.MAC;l
V50THM.MAC;l
V52THM.MAC;l
HLINIT.MAC;l
RMOMAC.MAC;l
GBLIOM.MAC;l

3.
3.
2.
2.
3.
1.
1.
2.

2.
2.
2.
2.
2.
1.
1.

1.
1.
4.
2.
17.
8.
10.
3.

4.
5.
4.
6.
4.
6.
4.
4.
6.
6.
6.
5.

7.
3.

F-19

DIRECTORY LISTINGS

MCRSRC (Cont.)

V05IOM.MAC;l
VlHIOM.MAC; 1
V52IOM.MAC;l
V50IOM.MAC;l
IOCMD.MAC;l
GBLSSM.MAC;l
VlHSSM.MAC;l
SSCMD.MAC;l
V52SSM.MAC;l
L36SSM.MAC;l
ATPAGE.MAC;l
SSPAGE.MAC;l
THPAGE.MAC;l
IO PAGE. MAC ; 1
RMDEMO.MAC;l
IO IN IT .MAC; 1
REMAP.MAC;l
MDCOM.MAC;l
MDPAGE.MAC;l
MDCMD.MAC;l
MD IN IT • MAC ; 1
THINIT.MAC;l
SS IN IT .MAC; 1
ATINIT.MAC;l
L36MDM.MAC;l
V05MDM.MAC;l
VlHMDM. MAC; 1
V50MDM.MAC;l
V52MDM.MAC;l
THFllL .MAC; 1
RMDDEF.MAC;l
SSCOM.MAC;l
RMDXCM.MAC;l
IOCOM. MAC ; 1
GBCOM.MAC;l
ATCOM.MAC;l
THCOM.MAC;l
HLCOM.MAC;l

5.
5.
5.
5.
6.
5.
5.
3.
5.
5.
29.
34.
5 7.
35.
48.
11.
3.
6.
5 7.
6.
23.
13.
6.
7.
5.
5.
5.
5.
5.
14.
6.
2.
5.
3.
2.
4.
6.
1.

Total of 597./597. blocks in 75. files
UFD
RMDASM.CMD;l

[14, 20]

Total of 8./8. blocks in 1. file
UFD [ 14 I 24]
RMDASM.CMD;l

11.

Total of 11./11. blocks in 1. file
UFD [14, 30]
Total of 0./0. blocks in 0~ files

F-20

DIRECTORY LISTINGS

MCRSRC (Cont.)

UFD [ 14, 34]
Total of 0./0. blocks in O. files

UFD [15, 10]
SHUFL.MAC;l
SHUTUP.MAC;l
ACNT.MAC;l
BROAD.MAC;l
HELLO.MAC;l
HELROT.MAC;l
HLP.MAC;l
HSTTAB.MAC;l
HLPSUB.MAC;l

36.
54.
159.
57.
118.

15.
11.

25.
72.

Total of 547./547. blocks in 9. files

UFD [15,20]
SHUTUPASM.CMD;l
MLTASM.CMD;l
MLTLIBBLD.CMD;l

1.
1.
1.

Total of 3./3. blocks in 3. files

UFD [15, 30]
Total of 0./0. blocks in O. files

UFD [15, 34]
Total of 0./0. blocks in O. files

UFD [ 15, 24]
SHUTUPASM.CMD;l
SHUFLASM.CMD;l
MLTASM.CMD;l
MLTLIBBLD.CMD;l

1.
1.
1.
1.

Total of 4./4. blocks in 4. files
Grand total of 6486./6580. blocks in 355. files in 18.
directories

F-21

DIRECTORY LISTINGS

HLPDCL

F.1.6

HLPDCL
UFO [l, l]
EXEMC.MLB;l
EXELIB.OLB;l
FCS.OBJ;l
FCSMBF.OBJ;l
RSXMAC.SML;l
SYSLIB.OLB;l

73.
48.

25.
33.

287.
238.

Total of 704./704. blocks in 6. files

UFO [l, 2]
HELP.ULB;l

2925.

Total of 2925./2925. blocks in 1. file

UFO [1,6]
ERRLOG.ULB;l
ERRLOGETC.ULB;l

727.
72.

Total of 799./799. blocks in 2. files

UFO [23, 10]
ASSIGN.MAC;!
DEALLO.MAC;l
ALFN.MAC;l
ALFNUM.MAC;l
ALL.MAC;!
LOGIN.MAC;!
AND.MAC;!
ANDA.MAC;!
REQUEST.MAC;!
DEASSIGN.MAC;!
FIX.MAC;!
CALLOV.MAC;l
CATCHALL.MAC;!
CBM.MAC;l
SUBMIT.MAC;!
UNFIX.MAC;!
COP.MAC;!
REMOVE.MAC;!
CONVERT.MAC;!
DQBFS.MAC;l
ELEMENT.MAC;!
SORT.MAC;!
EOL.MAC;l
ERRl.MAC;l
ERRORR.MAC;l
FLAGS.MAC;!
FNAM.MAC;l

6.
3.
10.
13.
5.
3.
9.
4.
2.
4.
3.
7.
5.
3.
20.
3.
3.
4.
9.
4.
22.
30.
3.
3.
2.
4.
7.

F-22

DIRECTORY LISTINGS

HLPDCL (Cont.)

GTARG.MAC;l
JSR.MAC;l
LDCCD.MAC;l
LIT.MAC;l
LOAD.MAC;l
LOVR.MAC;l
MAP.MAC;!
MATCH.MAC;l
NEW.MAC;!
NLIT.MAC;l
OR.MAC;l
PARSER.MAC;!
RELEASE.MAC;!
HOLD.MAC;l
PRI.MAC;l
PRO.MAC;l
QUA.MAC;l
SCTBIT.MAC;l
TRANSL.MAC;l
TST.MAC;l
UND.MAC;l
XCOPY.MAC;l
ASTOV.MAC;l
COD.MAC;l
CSEP.MAC;l
CUIC.MAC;l
DATE.MAC;l
DBUG.MAC;l
DEV.MAC;l
EDOC.MAC;l
FIL.MAC;l
FSEP.MAC;l
IFIL.MAC;l
LAB.MAC;l
LUIC.MAC;l
NFT.MAC;l
ODEV.MAC;l
OUIC.MAC;l
PIP.MAC;l
PROC.MAC;l
SEP.MAC;l
SY.MAC;l
T.MAC;l
TERM.MAC;l
TI.MAC;l
TIME.MAC;l
UIC.MAC;l
VER.MAC;l
WFIL.MAC;l
WUIC.MAC;l
WVER.MAC;l
WXTN.MAC;l
XTN.MAC;l
APPEND.MAC;l
AT.MAC;l
MCR.MAC;l
PURGE.MAC;!
RENAME.MAC;l
TYPE.MAC;l

5.
3.
5.
17.
5.
12.
24.
7.
4.
3.
6.
8.
4.
4.
2.
9.
7.
7.
5.
5.
5.
6.
6.
3.
2.
3.
4.
10.
2.
2.
3.
2.
2.
2.
3.
10.
2.
2.
9.
2.
2.
3.
2.
2.
3.
2.
3.
2.
3.
3.
2.
2.
2.
11.
2.
2.
4.
5.
6.

F-23

DIRECTORY LISTINGS

HLPDCL (Cont.)

UNLOCK.MAC;!
COMMAC.MAC;l
LOGOUT.MAC;!
PRINT.MAC;!
ALLOCATE.MAC;!
CONTINUE.MAC;!
NFIL.MAC;l
DCL.MAC;l
BROADCAST.MAC;!
DCLMPL.MAC;l
SPAWN.MAC;!
ERRORO.MAC;l
COPY.MAC;!
LINKl.MAC;l
DEBUG.MAC;!
PREPARSE.MAC;l
ABORT.MAC;!
DCLMAC.MAC;l
DCLDAT.MAC;l
NOD.MAC;!
RUN.MAC;!
MOUNT.MAC;!
LIBRARY.MAC;!
INSTALL.MAC;!
BACKUP.MAC;!
DIRECTORY.MAC;!
EDIT.MAC;!
LINK.MAC;!
TLINK.MAC;l
MACRO.MAC;!
DISMOUNT.MAC;!
SETl.MAC;l
HELP.MAC;!
SET.MAC;!
TSET.MAC;l
STOP.MAC;!
SHOW.MAC;!
TSHOW.MAC;l
START.MAC;!
ERR.MAC;!
XDCL.MAC;l
DSPCMD.MAC;l
FORMAT.MAC;!
COMMAND.MAC;!
FORTRAN.MAC;!
COBOL.MAC;!
PASCAL.MAC;!
CORAL.MAC;!
BASIC.MAC;!
QIOBF.MAC;l
DIFFERENC.MAC;l
INITIAL.MAC;!
DELETE.MAC;!
DISPATCH.MAC;!
DQBFE.MAC;l

3.
1.
2.
15.
3.
3.
4.
2.
4.
1.
5.
5.
13.
6.
2.
14.
4.
56.
26.
3.
13.
19.
12.
11.
15.
9.
12.
35.
18.
19.
4.
36.
4.
51.
53.
9.
44.
29.
15.
11.
36.
39.
10.
11.
19.
16.
10.
15.
3.
7.
5.
20.
13.
9.
11.

F-24

DIRECTORY LISTINGS

HLPDCL (Cont.)

CREATE.MAC;l
CANCEL.MAC;l
OCLMIC.MAC;l
MERGE.MAC;l
ANALYZE.MAC;l

14.
2.
1.
20.
43.

Total of 1369./1369. blocks in 146. files
UFO [23,24]
OCL.CMO;l
OCLASM.CMO;l

4.
23.

Total of 27./27. blocks in 2. files
UFO [23,34]
Total of 0./0. blocks in O. files
UFO [24,10]
TOX.MAC;l

8 5.

Total of 85./85. blocks in 1. file
UFO [24,24]
TOXASM.CMO;l
CATCHALL.CMO;l

1.
7.

Total of 8./8. blocks in 2. files
UFO [45, 10]
KRATE.B2S;l
KRATE.FTN;l
KCLOKB. MAC; 1
KAAOMP.MAC; 1
KAAS03.MAC; 1
KAOAGR.MAC;l
KAOORV.MAC;l
KAOINO.MAC; 1
KAOINl.MAC; 1
KAOIN2.MAC; 1
KAOIN3.MAC;l
KAOIN4.MAC;l
KAO IN 5. MAC; 1
KAOSWP. MAC ; 1
KAST.MAC;!
KBFRMG.MAC; 1
KCLOKA.MAC; 1

7.
7.
10.
12.
5.
6.
14.
6.
8.
6.
8.
6.
8.
7.
14.
13.
5.

F-25

DIRECTORY LISTINGS

HLPDCL (Cont.)

KSWOF.MAC;l
KCOMM.MAC;l
KCVAOF .MAC; 1
KO IGO.MAC; 1
KOISWP.MAC;l
KOOSWP.MAC;l
KOSCAO.MAC;l
KOSOGO.MAC;l
KOVOF.MAC;l
KEFQA.MAC;l
KFLT16. MAC; 1
KIESTO.MAC; 1
KKWORV.MAC;l
KLQSUB.MAC; 1
KPAA.MAC;l
KMUL.MAC;l
KRWBF.MAC;l
KRCLKB.MAC;l
KRLOC.MAC;l
KPRE.MAC;l
KSTB.MAC;l
KSTIBF.MAC;l
KSTOP.MAC;l
LABMAC.MAC;l
KSUB.MAC;l
KGHIST.MAC;l
KSET.MAC;l
KAOGCH.MAC;l
KBFSTS.MAC;l
KOIO.MAC;l
KAAORV.MAC;l
KORORV.MAC;l
KSTAOC.MAC;l
KAOINP.MAC; 1

13.
5.
6.
10.

7.
7.
4.
4.
11.
10.
6.

4.
18.

7.
7.
3.
12.
5.

4.
4.
7.
5.

5.
6.
10.
21.
13.
20.
11.
12.
24.
30.

7.
13.

Total of 473./473. blocks in 51. files
UFO [45,20]
KLABMLB.CMO;l
ASMK.CMO;l
K4ASM.CMO;l
KLIBBLO.CMO;l
KLIBRP.CMO;l
KCLEAN.CMO;l
KCOMBLO.CMO;l

1.
1.
1.
1.
1.
1.
1.

Total of 7./7. blocks in 7. files
UFO [45,24]
KLABMLB.CMO;l
ASMK.CMO;l
KCLEAN.CMO;l
KLIBBLO.CMO;l

1.
1.
1.
1.

F-26

DIRECTORY LISTINGS

HLPDCL (Cont.)

KLIBRP.CMD;l
K4ASM.CMD;l
KCOMBLD.CMD;l

1.
1.

Total of 7./7. blocks in 7. files
UFO [45,30]
Total of 0./0. blocks in O. files
Directory DLl: [45,34]
Total of 0./0. blocks in O. files
Directory DLl: [200,200]
FCSRES.MAC;l

12.

Total of 12./12. blocks in 1. file
Grand total of 6416./6416. blocks in 226. files in 14.
directories

F-27

DIRECTORY LISTINGS

RMSV20

F.1.7

RMSV20
UFD [l, 1]
RMSLIB.OLB;l
RMSRES.STB;l
RMSRLX.ODL;l
RMSMAC.MLB;l
RMSDAP. OLB; 1
DAPRES.TSK;l
DAPRES.STB;l
DAPRLX.ODL;l
DAPllX.ODL;l
RMS 11. ODL; 1
RORMSl.MAC; 1
RMSllS. ODL; 1
RMSllX. ODL; 1
RMS12X.ODL;l
RMS12S.ODL;l
RMSRES.TSK;l
RMSRESSUB.TSK;l

239.
3.
2.
189.
104.
39.
2.
2.
6.
86.
12.
5.

6.
6.
4.
89.
49.

Total of 843./843. blocks in 17. files
UFD [1,2]
RMSDES.IDX;l

126.

Total of 126./126. blocks in 1. file
UFD [1,24]
RMSRES.CMD;l
RMSRES.ODL;l
DAPRES.CMD;l
DAPRES.ODL;l
BCKNRN.CMD;l
BCKNRN.ODL;l
BCKNON.CMD;l
BCKNON.ODL;l
RSTNRN.CMD;l
RSTNRN.ODL;l
RSTNON.CMD;l
RSTNON.ODL;l
CNVNRN.CMD;l
CNVNRN.ODL;l
CNVNON.CMD;l
CNVNON.ODL;l
CNVNRR.CMD;l
CNVNRR.ODL;l
CNVNOO.CMD;l
CNVNOO.ODL;l
DSPNRN.CMD;l
DSPNRN.ODL;l
DSPNON.CMD;l
DSPNON.ODL;l

1.
11.

1.
1.
1.
5.
1.

1.
5.

1.
5.
1.

1.
10.

1.
6.
1.
5.
1.

3.
1.

F-28

DIRECTORY LISTINGS

RMSV20 (Cont.)

DEFNRN.CMD;l
OEFNRN.OOL;l
OEFNON.CMO;l
OEFNON.OOL;l
OESNRN.CMO;l
DESNRN.ODL;l
DESNON.CMD;l
OESNON.OOL;l
IFLNON.CMO;l
IFLNON.ODL;l
IFLNRN.CMD;l
IFLNRN.OOL;l
RMSOES.OOL;l
RMSOOL.OOL;l
RMSUTL.OLB;l

1.
3.
1.
3.
1.
6.

1.
6.
1.

5.
1.

3.
9.
24.
810.

Total of 951./951. blocks in 39. files
UFO [1,34]
RMSRES.MAP;l
RMSRESSUB.MAP;l
OAPRES.MAP;l

59.
35.
17.

Total of 111./111. blocks in 3. files
UFO [ 1, 54]
RMSCNV.TSK;l
RMSOSP.TSK;l
RMSOEF.TSK;l
RMSOES.TSK;l
RMSIFL.TSK;l
RMSBCK.TSK;l
RMSRST.TSK;l

174.
181.
137.
243.
136.
183.
187.

Total of 1241./1241. blocks in 7. files
UFO [200, 1]
GSA.MAC;l
SEARCH.MAC;l
RENAME.MAC;l
ERASE.MAC;l
PARSE.MAC;l
SEARCH.TSK;l
RENAME.TSK;l
ERASE.TSK;l
PARSE.TSK;l

19.
10.
12.
10.
11.
25.
26.
25.
22.

Total of 160./160. blocks in 9. files
Grand total of 3432./3432. blocks in 76. files in 6. directories

F-29

INDEX

ACP
ANSI magnetic tape, 4-29
definition, 1-4
Address che.cking, 4-28
Ancillary Control Processor
See ACP
ANSLIB.OLB, 4-59
linking tasks to, 7-4
rebuilding user-written tasks,
6-6
AST, 4-31
Asynchronous system traps
see AST
Autoconf igure, 1-2
adding devices, 4-4
description, 3-17
failure, 3-18
overriding results, 3-20, 4-3
exception, 3-21
question, 4-3
restrictions, 3-17
sample output, 3-19
supported hardware, 3-21
use, 3-17
with saved answer files, 3-18
Backup and Restore Utility
see BRU
Baseline system
definition, 1-5
Big-buffering support, 4-59
BLDLAINIT.CMD, 3-5
Bootstrap
hardware, 1-5, B-1
mapped baseline system, 4-2
procetlure, B-1
software, 1-5
summary of addresses, B-2
unsaved system, 6-2
nonstandard unmapped, 6-12
Breakpoint
definition, 3-8
EOS, 3-8
EOX, 3-8
purpose, 3-8
BRU
task build, 6-3
using
recovering disk space, 6-3
using to backup target system
disk, 6-9
BRU64K, 2-5
See also BRUS'YS
CNF, 2-5
altering CSRs using, 2-5
altering vectors using, 2-5
BRUSYS, 2-4
See also BRU64K
CNF, 2-5
altering CSRs using, 2-5

BRUSYS
CNF (Cont.)
altering vectors using, 2-5
Build files
creating on SY:, 5-5
Cancel Selective Marktime
directive, 4-31
CDA
see Crash dump
Chaining, 4-9
See also Saved answer file
See also Standard Function
System
definition, 3-9
restriction, 3-9
Checkpointing, 4-45
with system checkpoint file,
4-46
CL!
See also DCL
user-written, 4-64
Clock
system, 4-16
watchdog timer, 4-16
Communications products
DECnet, 4-36
SYSGEN support, 4-36
Configuration
See also Autoconf igure
saved host, 4-7
saved peripheral, 4-8
Control and Status Register
see CSR
Copy
RA60/80/81 tape kit
on-line, 2-19
RK06/07 kit
disk kit
on-line, 2-22
stand-alone, 2-12
RLOl/02 kit
disk kit
on-line, 2-24
stand-alone, 2-15
RM02/03/05/80 tape kit
on-line, 2-19
RP04/05/06 tape kit
on-line, 2-19
tape kit
on-line, 2-19
stand-alone, 2-6
target system disk
mapped, 6-9
unmapped, 6-19
Crash dump
analysis, 4-46
CDA support, 4-46
device, 4-47
PANIC, 4-46

Index-1

INDEX
Crash dump
PANIC (Cont.)
device, 4-48
Crash Dump Analyzer
see Crash dump
CSR
alteriJg using CNF, 2-5
definition, 1-4
floating, E-4
DBMS-11, 4-25
DCL, 4-63
DECnet
see Communications products
Default response
examples, 3-6
Device
example, 4-67
logical, 4-33
pseudo, C-3
specifying, 4-18
specifying parameters, 4-67
support on RSX-llM, 4-18
supported on RSX-llM, C-1
Device controller
AD, 4-69
AF, 4-69
AR, 4-69
CR, 4-70
CT, 4-70
DB, 4-71
DD, 4-72
DF, 4-72
DK, 4-72
DL, 4-73
DM, 4-73
DP, 4-74
DR, 4-75
DS, 4-76
DT, 4-76
DU, 4-77
DX, 4-78
DY, 4-78
EM, 4-78
GR, 4-79
LA, 4-79
LP, 4-80
LS, 4-82
MM, 4-83
MS, 4-84
MT, 4-84
MU, 4-84
PP, 4-85
PR, 4-85
UD, 4-85
XB, 4-86
XE, 4-86
XL, 4-87
XM, 4-87
XP, 4-88
XQ, 4-88
XU, 4-89
xw' 4-89
YH, 4-90

Device controller (Cont.)
YJ, 4-90
YL, 4-91
YV, 4-91
YZ, 4-92
DIGITAL Command Language
see DCL, 4-63
Directives
Cancel Selective Marktime, 4-31
Get Mapping Context, 4-28
memory management (PLAS) , 4-27
Send/Receive By Reference, 4-28
system, 4-38
Disk
space recovery, 6-3, 6-14
swapping interval
priority, 4-43
swapping interval, 4-42
write-checking support, 4-34
Distribution kit
definition, 2-1
external volume label, 2-2
guidelines for copying, 2-4
inventory, 2-2
restriction, 2-2
types, 2-1
Driver
definition, 1-4
Loadable
partition for, 5-11
loadable, 4-30
default to, 4-30
partition for, 5-10
task-build, 5-9
terminal, 4-49
user-written, 4-33
DSC
task build, 6-13
using to backup target system
disk, 6-19
Dynamic storage region
see Pool
Dynamic storage region (DSR)
see Pool
EAE, 4-13
EIS, 4-14
EOS
breakpoint, 3-8, 4-8
EOX
breakpoint, 3-8, 4-9, 5-6
Error logging
device, 4-33
Error Messages, 8-1
Event flags
group global, 4-38
Executive
commons, 4-27
definition, 1-3
Large (20K), 4-32
routines
$GTWRD, 4-34
$PTWRD, 4-34
source files disk, 4-9

Index-2

INDEX
Executive Debugging Tool
see XDT
Extended arithmetic element
See EAE, 4-13
Extended instruction set
See EIS
FCP
definition, 1-4
file sharing, 4-26
option, 4-61
placement control, 4-26
support, 4-25
user-written, 4-62
FCPLRG, 4-62
FCPMDL, 4-61
FCPMIN, 4-61
FCPSML, 4-61
FCS
definition, 1-3
PLAS resident library, 4-60
tasks that use, 7-1
FCSRES
linking tasks to, 7-4
File Control Services
see FCS
Files-11 ACP
see FCP
See FCP, 4-25
FIS, 4-14
Floating instruction set
See FIS
Floating point processor
See FPll
FORTRAN
see ISA
FPll, 4-14
Get Mapping Context directive,
4-28
Help
extracting a help file, 6-6,
6-16
library, 6-6, 6-16
HELP.ULB, 6-6, 6-16
HELPBUILD.CMD, 6-7, 6-17
Host system
definition, 1-6

1/0 packets
pre-allocated, 4-40
1/0 rundown, 4-28
Indirect command files
independent, 3-5
BLDLAINIT.CMD, 3-5
SGNBLDDRV.CMD, 3-5
SGNKLAB.CMD, 3-5
invoking, 3-5
major, 3-5
overview, 3-4
Inhibit MCR
See MCR, 4-4
see MCR, 5-4

Interrupt
definition, 1-4
Introduction to RSX-llM, 6-8,
6-18
IPll
industrial I/O subsystem, 4-60
power fail, 4-60
ISA
FORTRAN routines, 4-59
industrial/laboratory libraries,
4-59
K-series
device support, 4-13
KWll-P
as system clock, 4-16
KWll-Y Watchdog timer, 4-16
Layered products
installing, 6-12, 6-19
Line printer
options, 4-80
Magnetic tape kit
copying
on-line, 2-19
stand-alone, 2-6
Map device, 4-24
Mapped
baseline system
bootstrapping, 4-2
system
definition, 1-5
MCR
creating saved answer file,
3-11
inhibit
execution
Phase II, 5-4
PREPGEN, 3-11
inhibit execution, 4-4
MCR RUN support, 4-32
Memory
cache, 4-17
management
PLAS directives, 4-27
parity support, 4-17
processor memory size, 4-12
Multiuser
protection, 4-29
Multiuser system
tailoring, 6-8, 6-18
NCT
including support for, 4-37
Network Command Terminal
See NCT
On-line
definition, 1-6
formatting (FMT) , 4-30
Partition
creating with SYSVMR.CMD, 5-14

Index-3

INDEX
Partition (Cont.)
DRVPAR, 5-10, 5-16
EXCOMl, 5-15
EXCOM2, 5-15
FCPPAR, 5-16
GEN, 5-12, 5-16, 5-17
specifying a base address,
7-4
PAR14K, 5-18
SLPPAR
specifying a base address,
7-5
specifying a base addrress,
5-12
SPLPAR, 5-13, 5-17, 5-18
SYSPAR, 5-12, 5-16, 5-17, 5-18
specifying a base address,
7-5
system-controlled, 4-37
TTPAR, 5-15
Phase I
description, 3-1
example, 4-98
preparation, 4-2
sections, 3-2
Phase II
Description, 5-1
description, 3-2
example, 5-20
input files
RSXllM. OLB, 5-1
RSXBLD.CMD, 5-1
SGNPARM.CMD, 5-1
TTDRVBLD.CMD, 5-2
preparation, 5-2
sections, 3-2, 5-2
Phase III
description, 3-4, 7-1
example, 7-6
preparation, 7-2
PLAS directives
see Memory
PMD, 4-63
PMT
see Pool
Pool
definition, 1-3
description, 4-44
device influence, D-5
monitoring, 4-64
PMT, 4-64
size
calculating, D-1
specifying, 4-44
task influence, D-1
Post Mortem Dump
see PMD, 4-63
Power fail recovery support, 4-32
PREPGEN, 3-11
See also MCR inhibit
Phase I, 4-4
Phase II, 5-4
Processor
memory size, 4-12

Processor (Cont.)
Rotating pattern in data lights,
4-36
valid on RSX-llM, 4-11
with switch register, 4-11
Protection
multiuser, 4-29
PRT print spooler, 4-63
QIO

diagnostic, 4-30
QIO packets
pre-allocated, 4-40
Question
default response, 3-6
examples, 3-6
format, 3-5
logical order, 3-7
Queue manager, 4-38
RA60/80/81 tape kit
copying
on-line, 2-19
Record Management Services
See RMS
Resource Monitoring Display
see RMD, 4-63
RK06/07 kit
disk kit
copying
on-line, 2-22
stand-alone, 2-12
RLOl/02 kit
disk kit
copying
on-line, 2-24
stand-alone, 2-15
RM02/03/05/80 tape kit
copying
on-line, 2-19
RMD, 4-63
RMS
Installing, 6-9
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-19
RSXllM.OLB
definition, 5-1
RSXBLD.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, 4-6

Index-4

INDEX
Saved answer file
input (Cont.)
Phase II, 5-5
naming conventions, 3-10
output, 4-7
Phase II, 5-6
purpose, 3-10
restrictions, 3-9
Scheduling
round-robin interval, 4-41
highest priority, 4-41
lowest priority, 4-42
Section
Executive Options, 4-25
Host Configuration, 4-23
Peripheral Options, 4-67
Setup, 4-3
System Options, 4-59
Target Configuration, 4-11
Send/Receive By Reference
directive, 4-28
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-37
Software Performance Monitor
see SPM
Space problems
disk space recovery, 6-3, 6-14
SPM, 4-65
Stand-alone
definition, 1-6
Stand-Alone Configuration and
Disk Sizing Program (CNF)
See BRU64K
See BRUSYS
Standard Function System, 1-2
See also Saved answer file
description, 3-11
options included, 3-12
purpose, 3-11
question, 4-7
restriction, 3-12
STARTUP.CMD, 6-8, 6-18
RMS procedures, 6-11
Subsytems
IC and IS, 4-93
Switch register
question, 4-11
Symbol
saved answer, A-1
SYS GEN
Autoconfigure, 3-17
definition, 3-1
independent command files, 3-5
indirect command files, 3-4
introduction to, 1-1
minimum requirements, 1-1, 4-2
operating environments, 2-3

SYS GEN
operating environments (Cont.)
on-line
RSX-llM host, 2-3
RSX-llM-PLUS host, 2-4
VAX-11 RSX host, 2-4
stand-alone, 2-3
overview, 1-2
phase, 3-1
Phase I, 4-1
Phase II, 5-1
Phase II I, 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
Standard Function System, 3-11
terminology, 1-3
System
baseline, 1-5
directives, 4-38
host, 1-6
mapped, 1-5
multiuser setup, 6-8, 6-18
naming, 4-65
on-line, 1-6
stand-alone, 1-6
target, 1-6
unmapped, 1-5
unsaved, 1-6, 6-1
System image
See SYSVMR.CMD
SYSVMR.CMD
creating partition structure,
5-14
creating RMS partitions, 5-19
description, 3-3
edit, 5-14
on mapped systems, 5-14
on unmapped systems, 5-17
restriction, 3-4
VMR
invoking from on-line host,
5-18
Target system
creating a backup copy, 6-9,
6-19
definition, 1-6
installing layered products in,
6-12, 6-19
saving, 6-2
nonstandard unmapped, 6-13
transferring to different type
of disk, 6-5, 6-15
Task
building
description, 6-4
nonprivileged task, 7-2

Index-5

INDEX
Task {Cont.)
rebuilding user-written, 6-6,
6-16
termination {TKTN) , 4-31
Task loader
loadable, 4-26
nonresident, 4-26
Terminal driver
options, 4-49
TKTN, 4-31
TTDRVBLD.CMD
definition, 5-2
UIC
setting, 4-2
Unmapped system
definition, 1-5
question, 4-6
Unsaved system
bootstrap, 6-2
nonstandard unmapped, 6-12
definition, 1-6
Update
applying, 2-29
on-line, 2-32
stand-alone, 2-30

Update {Cont.)
command procedure, 2-28
errors, 2-34
installing, 2-26
layered product files, 2-35
package, 2-27
preparations, 2-28
Vector
altering using CNF, 2-5
data transfer
size of, 4-40
definition, 1-4
floating, E-4
highest interrupt, 4-17
VMR
See also SYSVMR.CMD
editing SYSVMR.CMD, 5-14
establishing system features,
6-9, 6-19
invoking from on-line host,
5-18
Write-lock
software support, 4-35
XDT, 4-35

Index-6

RSX-llM System Generation
and Installation Guide
AA-H625D-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 inake 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

Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
D Student programmer
D Other (please specify)

Organization
Street
State ______ Zip Code - - - - - or Country

DoNotTear-FoldHereandTape -

~nmnoma

No Postage
Necessary
if Mailed in the
United States

111111

BUSINESS REPLY MAIL
FIRST CLASS PERMIT N0.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

SSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03062-2698

Do Not Tear - Fold Here