Digital PDFs

AA-2552D-TC

December 1977

323 pages

Original

13MB

Document:	RSX-11M System Generation Manual Version 3.1
Order Number:	AA-2552D-TC
Revision:	0
Pages:	323
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V3.1_Dec77/1A_System_Reference_Information/AA-2552D-TC_RSX-11M_3.1_System_Generation_Manual_Dec77.pdf

OCR Text

RSX-11M
System Generation Manual
Order No. AA-2552D-TC

RSX-11 M Version 3.1

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

digital equipment corporation · maynard. massachusetts

First printing, November 1974
Revised:
September 1975
January 1977
December 1977

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 only be used or copied in accordance with the terms of such
license.
No responsibility is assumed for the use or reliability of software on
equipment that is not supplied by DIGITAL or its affiliated companies.

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

DIGITAL
DEC
PDP
DECUS
UNIBUS
COMPUTER LABS
COMTEX
DDT
DECCOMM
ASSIST-II

DECsystem-10
DECtape
DIBOL
EDUSYSTEM
FLIP CHIP
FOCAL
INDAC
LAB-8
DECSYSTEM-20
RTS-8

1/78-14

MASSBUS
OMNIBUS
OS/8
PHA
RSTS
RSX
TYPESET-8
TYPESET-II
TMS-Il
ITPS-IO

CONTENTS

Page
PREFACE

ix
0.1
0.2
0.3
0.4
0.5

CHAPTER

xii

INTRODUCTION TO SYSTEM GENERATION

1-1

1.1
1.2
1.2.1
1.2.2

SYSTEM GENERATION OVERVIEW
FUNCTIONAL FLOW OF SYSTEM GENERATION
Configuration and Assembly of the Executive
Setting Up Partitions, Building and
Installing Tasks
DIFFERENCE BETWEEN MAPPED AND UNMAPPED
SYSTEM

1-1
1-1
1-2

GETTING STARTED

2-1

2.1
2.1.1
2.1.1.1

CONTENTS OF THE DISTRIBUTION KITS
2-1
Single RKOS Release Kits - Summary
2-1
Summary of Single RKOS Disk Release Kit
2-1
Contents
Summary of Single RKOS Magtape Release
2-3
Kit Contents
Single RKOS Release Kits - Details
2-3
2-3
Executive Source Disk Contents
2-5
Unmapped Object Disk Contents
2-6
Mapped Object Disk Contents
MCR Source Disk Contents
2-7
2-8
FCP and DMP Source Disk
Utility Object Disk Contents
2-9
Device Combinations Supported by the
2-9
Single RKOS Distribution Kits
2-9
Dual RKOS Release Kits - Summary
Summary of Dual RKOS Disk Release Kit
2-9
Contents
Summary of Dual RKOS Magtape Release Kit
2-10
Contents
2-11
Dual RK05 Release Kits - Details
2-11
Baseline System Disk (BASLINE) Contents
2-12
Executive Source Disk (EXECSRC) Contents
2-12
Utility Object Disk (UTILOBJ) Contents
User-tailored System Disk (SYSTEM) Contents 2-12
2-13
MCRFCP Source Disk (MCRFCP) Contents
2-13
Device Combinations Supported by Dual RKOS
2-13
RL01 Kits - Summary
2-13
Summary of RL01 Disk Release Kit Contents
Summary ofRL01 Magtape Release Kit Contents 2-14

1.3
CHAPTER

ix
ix

MANUAL OBJECTIVES AND READER ASSUMPTIONS
STRUCTURE OF THE DOCUMENT
ASSOCIATED DOCUMENTS
THE BASELINE SYSTEM
USING THIS MANUAL TO ACQUIRE SYSTEM
GENERATION SKILLS

2.1.1.2
2.1.2
2.1.2.1
2.1.2.2
2.1.2.3
2.1.2.4
2.1.2.5
2.1.2.6
2.1.2.7
2.1.3
2.1.3.1
2.1.3.2
2.1.4
2.1.4.1
2.1.4.2
2.1.4.3
2.1.4.4
2.1.4.5
2.1.4.6
2.1.5
2.1.5.1
2.1.5.2

iii

x
x

1-4
1-5

CONTE'NTS (Cont.)

Page
2-14
2-14
2-16
2-17

2.3.6
2.3.7
2.4

RLOl Release Kits - Details
Mapped System Object Disk (MAPSYS)
Unmapped System Object Disk (UNMSYS)
Utility Object Disk (RLUTIL)
RP02/03, RP04/05/06" RM03 and _RK06 Magtape
Release Kit
RP02/03, RP04/05/06, RM03, and RK06 Magtape
Release Kit Contents
SAVING DISTRIBUTION DISKS
Saving the Single and Dual RK05 Distribution
Disks
Preserving an RK05 on DECtape:
Preserving an RK05 on Cassette:
Saving an RK05 on an RK05:
Preserving an RK05 on Floppy Disk:
Saving an RK05 on Magtape:
Saving the RP02/03, RP04/05/06, RK05/06,
RL01, and RM03 Distribution Kits
Restoring Damaged Volumes
Cassette Restoration
DECtape Restoration
Floppy Disk-to-RK Disk Restoration
Restoring Damaged Disks with DSC
Exiting from PRESRV or DSC
Formatting Disks
BOOTSTRAPPING THE BASELINE SYSTEM
Start-up Using the BM792-YB Bootstrap ROM
Start-up Using the MRll-DB Bootstrap ROM
Start-up Using the BM873-YA Bootstrap ROM
Start-up using the BM873-YB Bootstrap ROM
Start-up Using the M930l-YA or M9301-YB
Bootstrap ROM
M930l-YC Bootstrap (PDP-ll/70 Only)
M930l-YF Bootstrap ROM
CONSOLE DISPLAY

SYSGEN DIALOGUE DETAILS

3-1

3.1
3.2
3.3
3.4
3.5
3.6
3.7

SYSGEN DIALOGUE
SYSGEN.CMD FILE DETAILS
SYSGEN QUERY SECTION
SYSGEN2.CMD FILE DETAILS
SYSGEN3.CMD FILE DETAILS
BLDUMD.CMD FILE DETAILS
SGN ERROR MESSAGES

3-1
3-2
3-15
3-70
3-98
3-111
3-116

GENERATING LARGER SYSTEMS

4-1

4.1
4.1.1
4.1.2
4.1.2.1
4.1.2.2

DEFINING MEMORY PARTITIONS
Laying Out Partitions - Software Options
Partitions - User- and System-Controlled
User-Controlled Partitions
System-Controlled Partitions
Checkpointing
Memory Compaction in a System-Controlled
Partition (Shuffler)
The Shuffler's First Pass
The Shuffler's Second Pass

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

2.1.6
2.1.6.1
2.1.6.2
2.1.6.3
2.1.7
2.1.7.1
2.2
2.2.1
2.2.1.1
2.2.1.2
2.2.1.3
2.2.1.4
2.2.1.5
2.2.2
2.2.3
2.2.3.1
2.2.3.2
2.2.3.3
2.2.3.4
2.2.4
2.2.5
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5

CHAPTER

4.l~2.3

4.1.3
4.1.3.1
4.1.3.2

2-17
2-18
2-20
2-20
2-21
2-22
2-22
2-22
2-22
2-23
2-24
2-24
2-25
2-25
2-26
2-27
2-27
2-27
2-27
2-28
2-28
2-29
2-30
2-30
2-31
2-32

4-6
4-6
4-6

CONTENTS ( Con t. )

Page
4.1.3.3
4.1.4
4.1.5
4.1.6
4.1.7
4.1.8
4.2

CHAPTER

Unshufflable Tasks
Advantages of System-Controlled Partitions
Unmapped System - Executive Less Than 8K
Unmapped System - Executive Greater Than 8K
Mapped Systems
Example of a Large Mapped System
BUILDING SYSTEMS FOR RESIDENCE ON OTHER
DEVICES
4.3
SUPPORTING MORE THAN ONE SYSTEM ON THE SAME
VOLUME
4.4
INCREASING FILE SYSTEM THROUGHPUT
4.4.1
Building a Faster File System
4.4.2
File Control Primitives Dynamic Memory
Requirements
4.4.2.1
Directory Least-Recently-UsedList
4.4.2.2
File Control Block Allocation
4.4.3
Multiple File Systems
4.5
INSTALLING AND USING RESIDENT LIBRARIES AND
COMMON BLOCKS
4.5.1
Setting up a Common Partition
4.5.2
Installing a Library or Common Block
4.5.3
Eliminating a Library or Common Block
4.6
BUILDING A FORTRAN OTS RESIDENT LIBRARY
4.7
BUILDING AN FCS (POSITION-INDEPENDENT)
RESIDENT LIBRARY
4.8
PRINT SPOOLER (PRT)
4.9
BUILDING MULTI-USER SYSTEMS
4.9.1
Setting Up a Multi-User System
4.9.2
Installing Checkpointable Tasks
4.9.2.1
Systems without Dynamic Allocation of
Checkpoint Space
4.9.2.2
Systems with Dynamic Allocation of Checkpoint Space
4.9.3
Installing Noncheckpointable Tasks
4.9.3.1
Fixed Partition Systems
4.9.3.2
System-Controlled Partitions
4.9.4
Task Invocation
4.9.5
Disk Swapping
4.9.6
Round-Robin Scheduler
4.9.7
Checkpointing During Terminal Input Wait
Dynamic Checkpoint Space Allocation and
4.9.8
Task Extension
4.9.9
QIO Speed Optimizations
4.9.9.1
I/O Packet Preallocation
4.9.9.2
BLXIO (Block Transfer) Speed Optimizations
4.9.9.3
Overlapped I/O Completion
4.9.10
Multiuser Protection
4.9.10.1
Abort, Resume, and Cancel Schedule Requests
4.9.10.2
Request and Run
4.9.10.3
Queue I/O Request
4.9.10.4
Slave Tasks
4.9.11
Multiple ACPs - Executive Interface
4.9.12
ALTER PRIORITY Directive

4-7
4-7
4-8
4-10
4-10
4-10

VMR COMMANDS

5-1

5.1

COMMAND SUMMARY

5-1

4-11
4-12
4-14
4-14
4-14
4-14
4-15
4-15
4-15
4-16
4-16
4-16
4-16
4-18
4-19
4-20
4-20
4-21
4-21
4-21
4-21
4-21
4-22
4-22
4-22
4-23
4-24
4-24
4-25
4-25
4-26
4-26
4-26
4-26
4-27
4-27
4-27
4-27
4-27

CONTENTS (Cont.)

Page
5.2
5.2.1
5.2.2
5.3
5.3.1
5.3.2
5.3.3

5.4
5.4.1

5."4.2
5.4. 3

5.5
5.6

5.7
CHAPTER

6.1
6.2
APPENDIX A
A.1
A.1.1
A.1.2
A.2
APPENDIX B
B.1
B.2
B.3
B.3.1
B.3.2
B.4
B.5
APPENDIX C
C.1
C.2
C.3
C.4
C.5
APPENDIX D

MONITOR CONSOLE INTERFACE
Introduction
Starting VMR
VMR FILE SPECIFIERS
Command Syntax
Keywords
Comments
COMMAND NAMES
Lower-Case
Brackets []
Numeric Values
COMMAND DESCRIPTION FORMAT
VMR COMMAND DESCRIPTIONS
VMR ERROR MESSAGE SUMMARY

5-2
5-2
5-2

5-4
5-4
5-5

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

MOVING A VERSION 3.1 SYSTEM TO A VERSION 3
DISK

6-1

COPYING VERSION 3.1 TO MAGTAPE
COPYING VERSION 3.1 TO A VERSION 3 DISK

6-2
6-3

SYSTEM CONVENTIONS

A-I

RSX-11M UIC CONVENTIONS
Group Number
Member Number
NAMING CONVENTIONS

A-I
A-I
A-I
A-3

OPERATING HINTS

B-1

BOOTSTRAPPING A WRITE-LOCKED DISK
B-1
RUNNING OUT OF DYNAMIC MEMORY
B-1
DYNAMIC MEMORY REQUIREMENTS
B-2
Sources Requiring Dynamic Memory
B-2
Space Saving Hints
B-4
PARITY MEMORY SUPPORT
B-4
SAVING THE SYSTEM WITH A KW11-Y WATCHDOG TIMER B-5
RMDEMO

C-l

INTRODUCTION
HARDWARE REQUIREMENTS
BENEFITS OF USING RMDEMO
EXPLANATION OF THE OUTPUT
CONFIGURATION OPTIONS

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

EXAMPLE SYSGEN

D-l

INDEX

Index-1

FIGURES
FIGURE

2-1
2-2

Baseline Single RK05 Unmapped System
Partition Layout
Baseline RK05 Mapped System Partition Layout
vi

2-4
2-7

CONTENTS (Con t. )

Page
FIGURES (Cont.)
FIGURE

4-1
4-2
C-l

Typical Unmapped 24K System
Typical Unmapped 28K System
Example of RMDEMO Display

4-8
4-9
C-3

TABLES
TABLE

A-I

System Identification Codes

vii

A-4

PREFACE

0.1

MANUAL OBJECTIVES AND READER ASSUMPTIONS

System generation is a fairly complicated process.
To understand
fully what is taking place, you must be knowledgeable in the operation
of RSX-IIM and its component tasks. Refer to Section 0.3 below for
further information regarding related manuals and recommended reading.
NOTE
Users
should
undertake
a
system
generation only with adequate planning.
This includes a thorough sttidy of the
query programs in Chapter 3 and the
answers the user will provide, so that
the
options
for
the
Executive,
processor, and peripherals are those
describing the intended target system.
In addition, a preliminary layout of
memory partitions is essential if the
later phases of the system generation
process are to proceed smoothly.

0.2

STRUCTURE OF THE DOCUMENT

This manual provides information on how to generate an RSX-IIM system
tailored to a particular installation's hardware configuration. As
delivered, RSX-IIM includes an operational Executive, called the
Baseline System.
Section 0.4 describes the Baseline System and
Section 2.3 describes the bootstrap procedures that the user must
follow to load the system.
Chapter 1 contains an overview of the system generation process.
It
acquaints you with the various phases involved in producing a tailored
system.
Chapter 2 describes the contents of the distribution kit and
information on getting started.

provides

The actual procedures involved in system generation are provided in
Chapter 3.
This chapter describes the step-by-step process followed
in generating a system.
Chapter
4
covers
procedures
multi-function systems.

needed

for

generating

larger

Chapter 5 describes the commands and operation of Virtual Monitor
Console Routine (VMR) , a program that initializes the target system in
the final stage of system generation.
The remaining sections comprise appendixes describing Ule conventions,
RSX-IIM operational hints, and a sample system generation.

0.3

ASSOCIATED DOCUMENTS

Other manuals closely allied to the purposes of this document are
described briefly in the RSX-IIM/RSX-IIS Documentation Directory. The
Documentation Directory defines the intended readership of each manual
in the RSX-IIM/RSX-IIS set and provides a brief synopsis of each
manual's contents.

0.4

THE BASELINE SYSTEM

RSX-IIM services a wide range of PDP-II hardware configurations.
The
system generation process tailors a system to a local set of hardware
and performance requirements.
The tailoring process is run on an RSX-IIM system called the Baseline
System.
The Baseline System is a fully operational RSX-IIM system
built explicitly for generating target systems. It is not for general
use because of the small size of the dynamic memory pool. The
Baseline System contains the following Executive options and device
support:
Executive options in the Baseline System:
Files-II Ancillary Control Processor (FIIACP)
Checkpointing
Nonresident task support
Address checking (mapped system only)
I/O rundown
External MCR functions
Task termination and device-not-ready messages
GET PARTITION PARAMETERS directive
GET TASK PARAMETERS directive
Install, request, and remove on exit support
Logical device assignment support
At least 400. words of dynamic memory
Loadable Drivers

Processor options in the Baseline System:
For unmapped RKOS disk systems-16K of memory
For unmapped RP02/03, RP04/0S/06, RK06, and dual RKOS systems-24K of memory
For all mapped systems-24K of memory
Memory management unit CKTII)
Peripheral device support in the single RKOS disk Baseline System:
2 RK05 disk drives

2 TAll cassette drives
2 TUS6 DECtape drives

2 RXOI floppy disk drives

2 TE/TUIO or TS03 magtape drive

2 TE/TU16 or TU45 magtape drive

I LPII or LSII line printer

I PCII paper tape punch
I terminal

Peripheral device support in the dual RK05 disk Baseline System:
4 RKOS disk drives

2 TAll cassette drives
2 TU56 DECtape drives

2 RXOl floppy disk drives

2 TE/TUIO or TS03 magtape drive

2 TE/TUI6 or TU45 magtape drive

I LPll or LSII line printer
I PCIl paper tape punch

I terminal

* Supplied as a loadable driver with loadable data base.
xi

CHAPTER 1
INTRODUCTION TO SYSTEM GENERATION

1.1

SYSTEM GENERATION OVERVIEW

The object of the system generation procedure (SYSGEN) is to create an
RSX-llM system tailored to your local hardware configuration and
performance requirements. This chapter provides an outline of the
stages involved in performing system generation. Chapter 3 describes
the system generation procedures.
The system generation process implies variability
categories of choices are available:
1.

Executive service options

Processor options

Peripheral devices

Partition configurations

Member tasks

You tailor a system to your local
these five categories.

1.2

needs

and

choice.

Five

options

from

selecting

FUNCTIONAL FLOW OF SYSTEM GENERATION

SYSGEN has three separate phases. You perform a particular set of
actions to produce specific system output for each phase. These three
phases are:
1.

Configuring and assembling the Executive.

setting up
Building the Executive and privileged tasks;
partitions, installing tasks, and bootstrapping and saving
the new system.

Building the nonprivileged utility tasks.
This step is
usually unnecessary for unmapped systems if the SYSGEN
received adequate planning and is not necessary on a mapped
system unless you want to build the utilities (utility tasks
are supplied in object form).

The entire SYSGEN process, of which the above phases are
is
directed
by
three
indirect
command
files:
SYSGEN2.CMD; and SYSGEN3.CMD.

1-1

components,
SYSGEN.CMD;

INTRODUCTION TO SYSTEM GENERATION
SYSGEN.CMD determines the features that will be included in the new
system and assembles the Executive. The SYSGEN.CMD file does this by
activating the following three query files:
•

SGNEXEC.CMD - queries you to determine the desired executive
service and processor options and produces the conditional
assembly parameter file.

•

SGNPER.CMD - queries you to determine the desired peripheral
options and creates the Executive prefix file, the build
files, and the device database for the system that is being
generated.

•

SGNTT.CMD - queries you to determine the
system's terminals.

data

base

for

the

SYSGEN2.CMD builds the Executive and all of the privileged tasks.
SYSGEN3.CMD builds the non-privileged
diagnostics.

utility

tasks

and

user

The dual RK05 distribution kit uses three additional indirect
files:
PRESYSGEN.CMD, SGNXFER.CMD, and SGNXFER2.CMD.

mode

command

PRESYSGEN.CMD - initializes the system for a dual RK05 SYSGEN.
The command file prepares the system disk for use
by the
other
system
generation
programs.
PRESYSGEN.CMD
chains
(invokes)
the indirect
command file SYSGEN.CMD
SGNXFER.CMD

- transfers control from SYSGEN.CMD to SYSGEN2.CMD.
This transfer program is necessary because the
files SYSGEN.CMD and SYSGEN2.CMD are on different
disks.

SGNXFER2.CMD

- transfers control from SYSGEN2.CMD to SYSGEN3.CMD
and
then
back to SYSGEN2.CMD.
Again, the
transfer program is necessary because the files
are on different disks.

1.2.1

Configuration and Assembly of the Executive

To use the Baseline Executive, which exists on the distribution disks,
conduct this phase by answering the questions during SYSGEN.CMD that
are asked by the three query files (SGNEXEC, SGNPER, SGNTT). When you
answer these questions you will determine the:
1.

Executive service options

Processor options

Peripheral device set

that will be incorporated into the Executive being created to
your configuration.

1-2

service

INTRODUCTION TO SYSTEM GENERATION
NOTE
The indirect command file SYSGEN.CMD
provides the means for specifying all
Executive options, processor options and
peripheral devices to be generated for
the target
system.
Thus,
it
is
necessary to thoroughly read Chapter 3
and the RSX-llM Executive
Reference
Manual to know what and how to specify
the options required in the
target
Executive. The SYSGEN.CMD file, and the
query files it references, determine the
processor and Executive options;
also
determined are the number and type of
peripheral
devices
that are to be
generated for the target system.
Your interaction with SYSGEN.CMD and the three query files results
the creation of five files on the disk:
1.

RSXMC.MAC

SYSTB.MAC

RSXASM.CMD

RSXBLD.CMD

ICTAB.MAC (only if ICS/ICR-ll support is included)

RSXMC.MAC contains the conditional assembly
produce the user-tailored Executive.
SYSTB.MAC is a file of device
peripheral configuration.

table

parameters

descriptions

that

necessary

de£ine

the

RSXASM.CMD is a MACRO-II indirect command file that directs the
conditional assembly of the user-tailored Executive. RSXBLD.CMD is a
Task Builder indirect command file that directs the building of the
user-tailored Executive.
ICTAB.MAC is a MACRO-II source file that defines the module layout of
an ICS/ICR-ll subsystem.
It is generated only when you select the
ICS/ICR-Il subsystem for inclusion in the target system.
After the questions asked by the query files have been answered and
the
five output files created,
the user-tailored Executive is
assembled via the indirect command file RSXASM.CMD. The indirect MCR
command file SYSGEN.CMD directs both the configuration, query section,
and assembly. Thus, to initiate Phase 1:
1.

Mount the correct disk

Bootstrap the Baseline System

Enter the time and date

1-3

INTRODUCTION TO SYSTEM GENERATION
4.

Initiate the indirect MCR command file, SYSGEN.CMD,
distribution kits except the dual RK05 kit

Initiate the indirect MCR command
dual RK05 systems

1.2.2

file,

for

all

PRESYSGEN.CMD,

for

Setting Up Partitions, Building and Installing Tasks

During Phase 2, the following tasks are built:
the user-tailored
Executive,
any loadable drivers,
the privileged tasks, and, under
certain conditions, some nonprivileged system tasks. At the end of
building the Executive, you have a nonoperational Executive, and the
value of the symbol $SYTOP is known.
The symbol $SYTOP represents the address of the last word in the
user-tailored Executive, which enables you to determine the size of
the Executive. A complete, operational system consists of:
1.

An Executive

Resident and loadable drivers

Privileged and nonprivileged system tasks

User tasks

A set of memory partitions into which tasks can be
and run

installed

Having the value of $SYTOP, you can divide memory into the partitions
and subpartitions needed to meet the application and performance
requirements of the system.
The indirect MCR command file SYSGEN2.CMD controls this phase.
Once
you initiate SYSGEN2.CMD,
it guides you through the building and
installation of requisite tasks. On all kits except the single RK05
or the RLOI kit, SYSGEN3.CMD can be called directly by SYSGEN2.CMD to
build the utility tasks. On single RK05 or RLOI kits, SYSGEN3.CMD is
supplied on the utility disk, and must be run separately.
The building of privileged and nonprivileged system tasks occurs after
you established partition boundaries, because these tasks ultimately
execute in these partitions.
Using virtual MCR (VMR) and the disk image of the target system, you
can now establish the partitions and install the tasks needed to
complete the operational system.
Having created the operational system, complete with partitions and
tasks, you now must bootstrap the system, using the MCR BOOT command,
and then save the system, using the MCR SAVE command with the /WB
switch appended. MCR saves the system and then automatically re-boots
it.
The indirect command file, SYSGEN2.CMD, directs VMR processing to
partitions, install tasks, bootstrap and save the system.

set

For SYSGENs using a single RK05 kit or an RLOI kit,
nonprivileged
tasks cannot be built on the related object disk because of space
limitations. The utility object disk contains all the files needed to
build
the
nonprivileged
tasks and the indirect command file
SYSGEN3.CMD to direct the process.

1-4

INTRODUCTION TO SYSTEM GENERATION
For SYSGENs
SYSGEN3.CMD.

using

any

other

kits,

SYSGEN2.CMD

directly

calls

On all kits, SYSGEN3.CMD may be run separately at a later time.

1.3

DIFFERENCE BETWEEN MAPPED AND UNMAPPED SYSTEM

RSX-lIM runs on all models of the PDP-II processor except the LSI-II
or
PDP-II/03.
The
basic addressing scheme of the processor
instructions allows direct addressing of up to 32K words
(64K bytes)
of memory.
Note the 4K words are reserved for UNIBUS I/O device
registers (see the appropriate Processor Handbook). To use memories
larger than 28K words,
the memory management unit (KTII) must be
present. It is available on the PDP-II/34/35/40/45/50/55/60/70. This
unit maps a task's virtual address
(O-32K words) into a physical
memory address (O-124K words except on the PDP-II/70, which may be
expanded to 1920K words) •
On an unmapped system, tasks must be linked to the physical base
address of the partition in which they run; however, in a mapped
system, all tasks are mapped with the KTII, and the virtual base
address of the task is usually zero. To run a task built for an
unmapped system in a partition with a different base address, the task
must be rebuilt to link it to the physical base address of the new
partition. This is not necessary on a mapped system, because the
physical base address of the partition is determined by the KTII.
Thus, any task on a mapped system can be run in any partition large
enough to accommodate it, whether or not it is the partition for which
the task was built.
This affects the SYSGEN procedure, because
altering the partitions in an unmapped system can force you to rebuild
all the utility tasks, whereas, in a mapped system, this does not
happen.

1-5

CHAPTER 2
GETTING STARTED
2.1

CONTENTS OF THE DISTRIBUTION KITS

Each RSX-IIM V3.1 distribution kit contains a system that can be
bootstrapped.
This system can run on the minimum configuration for
which it is intended. All system components required to run and
generate custom tailored systems are included in the kits. We
distribute RSX-IIM in 11 different kits:
1.

Six RK05 disks (single RK05 kit)

Five RK05 disks (dual RK05 kit)

One RK06 disk

Three RLOI disks

Six 600-foot 800-BPI tapes containing DSC images of
RK05 disks in one above

Five 600-foot 800-BPI tapes containing DSC images of the five
RK05 disks in two above

Three 600-foot 800-BPI tapes containing DSC images of an RK06
disk

Three 600-foot 800-BPI tapes containing DSC images
RLOI disks

Three 600-foot 800-BPI tapes containing DSC images of an RM03
disk

10.

Three 600-foot 800-BPI tapes
RP02/03 disk

containing

DSC

images

11.

Three 600-foot 800-BPI
RP04/05/06 disk

containing

DSC

images

tapes

the

six

three

In addition, all tape kits contain an additional 600-foot, 800-BPI
tape with a bootable, stand-alone copy of the Disk Save and Compress
(DSC) utility.

2.1.1

Single RK05 Release Kits - Summary

2.1.1.1 Summary of Single RK05 Disk Release Kit
Contents - The
distribution kit contains six RK05 disk cartridges identified as:
1.

Executive source Disk - EXCSRCI

2-1

GETTING STARTED
2.

Unmapped object Disk - UNMOBJ

Mapped object Disk - MAPOBJ

MCR source Disk - MCRSRC

FCP and DMP source disk - FCPDMP

Utility object disk - UTLOBJI

For generating mapped or unmapped systems, two or three of these disks
are used -- the Executive source disk, the applicable object disk, and
possibly the utility object disk.
If you are building a mapped
system, your system must have a minimum of 24K of memory and a Memory
Management Unit. The MCRSRC, and FCPDMP source disks are used if you
want to modify MCR or FCP. The DMP sources are included as an example
of how a typical MCR utility program is written. DMP is on the FCPDMP
source disk.
The first phase of SYSGEN uses the Executive source disk.
Among its files are:
1.

The Baseline System Executive and loadable drivers

A subset of the system tasks

Complete source code for the Executive

The system generation indirect MCR command files SYSGEN.CMD
SYSGENO.CMD, SGNEXEC.CMD, SGNPER.CMD, and SGNTT.CMD.

Output files created during the first phase of system
generated on the Executive source disk.

generation

The object disk (mapped or unmapped) is used for the second
SYSGEN and contains among its files:

phase

are
of

The Baseline System Executive, loadable drivers,
and system
tasks.
The unmapped object disk contains a 16K unmapped
Baseline System and the object libraries for an unmapped MCR
and FCP.
The mapped object disk contains a 24K mapped
Baseline System and the object libraries for a mapped MCR and
FCP.

Task-build command files
tasks

Object library files for all privileged system tasks

The system generation indirect MCR command file, SYSGEN2.CMD,
SYSGEN2A.CMD, and BLDDRV.CMD

create

all

privileged

system

In addition, the following files, created on the Executive source disk
during phase 1, are copied to the object disk:
the concatenated
Executive object file RSXllM.OBJ,
the
SYSGEN
parameter
file
SGNPARM.CMD, the Executive task-build command file RSXBLD.CMD, and the
ICSjICR-ll table module ICTAB.MAC.
The latter part of SYSGEN creates
the user-tailored Executive on the object disk, which ultimately
becomes your system disk.

2-2

GETTING STARTED
To obtain a detailed list of
following commands:

the

contents

the

disks,

use

the

)RUN $PIP
PIP)DKO:[*,*]/LI
This command sequence produces, on the console terminal,
directory listing of the volume mounted on DKO:.

complete

2.1.1.2 Summary of Single RK05 Magtape Release Kit Contents - The
release kit consists of seven 600-foot, 9-track, 800-BPI magtapes.
The magtapes each contain one of six RKOS disk images and a seventh
tape contains a stand-alone version of DSC. The six images correspond
to the six disks described earlier. The disk images on each magnetic
tape are:
1.

Executive source tape containing the file EXCSRCI

The unmapped object tape containing the file UNMOBJ

The mapped object tape containing the file MAPOBJ

MCR source tape contains the file MCRSRC

FCP and DMP tape containing the file FCPDMP

Utility object tape containing the file UTLOBJI

Before beginning a SYSGEN, you must copy the files that you need from
these tapes onto RKOS cartridges using the Disk Save and Compress
utility (DSC). Section 2.2.3.S contains an example of using DSC.

2.1.2

Single RK05 Release Kits - Details

2.1.2.1 Executive Source Disk Contents - The
contains the following:
UIC
[1,1]
[1,2]
[l,SO]
[11,10]
[11,20]
[11,24]
[11,40]
[200,200]

Executive

source

disk

CONTENTS
System and Executive macro libraries
Error message text file, startup command file
Baseline unmapped Executive and tasks required for
SYSGEN
Executive source modules
Directory for unmapped Executive object modules
Directory for mapped Executive object modules
Directory for Executive correction files
SYSGENO.CMD, SYSGEN.CMD, SGNEXEC.CMD, SGNPER.CMD,
SGNTT.CMD and RSXMC.MAC for the baseline system.

The RSX-IIM system files distributed on this disk provide a limited number of utility
tasks.

2-3

GETTING STARTED
The tasks are:
BOO
DMO
IND
INI
INS
LOA
MCR
MOU
SAV
TKN
UFD
UNL
FCPNMH
PIP
FLX
BIGMAC
MAC
EDI
SLP
VFY

MCR BOOT command
MCR DISMOUNT command
MCR indirect command file processor
MCR Disk Initialization command
MCR INSTALL command
MCR LOAD command
Monitor console routine
MCR MOUNT command
MCR SAVE command
Task termination notification routine
MCR User File Directory command
MCR UNLOAD command
2K non-multi-header file system
Peripheral Interchange Program
File exchange program
14K MACRO-II assembler
8K MACRO-II assembler
Line text editor
Source Language Input Program
File Structure Verification Program

The partition layout for the system on the source
Figure 2-1.

22K

disk

shown

130000(8)
UNASSIGNED
(6K)

16K

100000(8)

PAR14K
Partition
(14K)
GEN
Subpartition
(8K)

40000(8)

8K
SYSPAR Partition

30100(8)
SECPAR Partition
25200(8)
DSKPAR Partition
24400(8)
Executive

Figure 2-1

Baseline Single RK05 Unmapped System Partition Layout

2-4

GETTING STARTED
This system runs on a processor with 16K of memory or more.
The
assembler uses the subpartition GEN on 16K systems, and partition
PAR14K on systems with at least 22K of memory.
If you want Executive
listings on a 16K system, two assemblies are recommended -- one to
produce the object modules, and one to produce the listings.
On
systems with more than 16K of memory, this restriction does not exist.
You must not use the PAR14K partition to run tasks on a 16K machine,
because it maps into 6K of nonexistent memory. Devices generated into
this system are:
2 RK05 drives
1 terminal
In addition, loadable drivers with loadable data
for the following:

bases

are

provided

2 TCll/TU56 DECtape drives
2 TAll/TU60 Cassette drives
2 RXll/RXOl Floppy disk drives
2 TMll/TMAll/TMBll - TUIO/TS03/TEIO magtape drive
2 RHll/RH70/TM02/03 - TU16/TU45/TE16 magtape drive
1 PCll Paper Tape punch

2.1.2.2 Unmapped Object
contains the following:

Disk

Contents - The

unmapped

object

disk

UIC

CONTENTS

[1,1]

System object library, Executive symbol definition
library, ODT and TRACE object modules; concatenated
object module files for the FORTRAN
Purdue
ISA
Routines,
and
a concatenated object module file
containing FCS routines for ANSI magtape support

[1,2]

Error message text file, startup command file

[1,3]

Directory for lost files found by VFY

[1,4]

Directory for Snap-Shot and Post-Mortem Dumps

[1,6]

Directory for Error Log files

[1,20]

Object module libraries, task-build command files,
overlay
description
files
for
all DEC-supplied
privileged
tasks,
and
overlay
description
and
task-build command files for nonprivileged system tasks

[1,30]

Directory for task maps

[1,50]

RSX-IIM Baseline System Executive and all DEC-supplied
tasks built to run with the Baseline System Executive

[1,60]

Directory for RSX-llS Executive and tasks

[200,200] SYSGEN2.CMD, BLDDRV.CMD, and
SYSGEN2A.CMD
command
files, and source module for building resident file
control services (FCS) and FORTRAN Object Time System
(OTS) libraries

2-5

GETTING STARTED
The partition layout and device configuration of the system that is
distributed on the unmapped object disk is identical to that of the
source disk. Use the unmapped object disk to build a new, unmapped
RSX-IIM system to your specifications.

2.1.2.3 Mapped Object Disk Contents - The mapped object disk contains
the following:
UIC

CONTENTS

[1,1]

System object library, Executive symbol definition
library, ODT and TRACE object modules, concatenated
object module files for the FORTRAN
Purdue
ISA
routines,
and
a concatenated object module file
containing FCS routines for ANSI magtape support

[1,2]

Error message text file, startup command file

[1,3]

Directory for lost files found by VFY

[1,4]

Directory for Snap-Shot and Post-Mortem Dumps

[1,6]

Directory for Error Log files

[1,20]

Object module libraries and overlay
for all nonprivileged system tasks

[1,24]

Object module libraries and overlay description files
for all privileged tasks, task-build command files for
all tasks not distributed or built under UIC [1,54]

[1,34]

Directory for task maps

[1,54]

RSX-IIM mapped 24K Baseline System Executive and
DEC-supplied tasks built to run with the Executive

[1,64]

Directory for RSX-IIS Executive and tasks

descriptor

files

all

[200,200] SYSGEN2.CMD and BLDDRV.CMD command files, and source
module for building resident file control services
(FCS) and FORTRAN Object Time System libraries
The device configuration for this system is identical to that of the
system on the source disk. The partition layout appears in Figure
2-2.

2-6

GETTING STARTED
24K

140000(8)
UNASSIGNED
(6K)

18K

PAR14K
Partition
(14K)

110000(8)
GEN
Su bpartiti on
(8K)

50000(8)
SYSPAR Partition (2K)
8K

40000(8)
DSKPAR Partition
36100(8)
SECPAR Partition
33200(8)

Executive

o
Figure 2-2

Baseline RK05 Mapped System Partition Layout

The minimum configuration supported by the mapped RSX-llM system is
24K words.
The partitioning scheme is such that all tasks except
BIGMAC and BIGTKB run in partition GEN.
BIGMAC and BIGTKB must run in
partition PAR14K.

2.1.2.4 MCR Source Disk Contents - The MCR source disk
following:

UIC

contains

the

CONTENTS

[1,1]

System and Executive macro libraries

[1,2]

Error message text file, startup command file

[1,20]

Directory for unmapped MCR library files

[1,24]

Directory for mapped MCR library files

[1,50 ]

Baseline unmapped Executive and utility tasks

[12,10]

MCR source modules

[12,20]

Unmapped MCR assembly command files and
file

library

build

[12,24]

Mapped MCR assembly command
file

library

builn

2-7

files

and

GETTING STARTED
[12,30]

Directory for unmapped MCR listing files

[12,34]

Directory for mapped MCR listing files

[12,40]

Directory for MCR correction files

[45,10]

K-series lab peripheral support source files

[45,20]

Assembly command files
devices (unmapped)

for

K-series

lab

peripheral

[45,24]

Assembly command
devices (mapped)

for

K-series

lab

peripheral

[200,200]

files

SGNKLAB.CMD for generation of K-series lab support

The RSX-llM system files distributed on this disk provide a limited
number of utility tasks. The utility tasks are identical to those on
the Executive source disk.

2.1.2.5 FCP and DMP Source
contains the following:

Disk - The

UIC

FCP

and

DMP

source

disk

CONTENTS

[1,1]

System and Executive macro libraries

[1,2]

Error message text file, start up command file

[1,20]

Directory for unmapped FCP library file

[1,24]

Directory for mapped FCP library file

[1,50]

Baseline unmapped
SYSGEN

[13,10]

FCP source modules

[13,20]

Unmapped FCP assembly command file

[13,24]

Mapped FCP assembly command file

[13,30]

Directory for unmapped FCP listing files

[13,34]

Directory for mapped FCP listing files

[13,40]

Directory for FCP correction files

[15,10]

Source files for RMDEMO and the task shuffler

[15,20]

Directory for unmapped object modules

[15,24]

Directory for mapped object modules

[15,30]

Directory for unmapped listing files

[15,34]

Directory for mapped listing files

[35,10]

DMP source files

[35,20]

DMP assembly command file

[35,30]

Directory for DMP listing files

Executive

2-8

and

tasks

required

for

GETTING STARTED
The RSX-IIM system files distributed on this disk provide a limited
number of utility tasks. The utility ~asks are identical to those on
the Executive source disk.

2.1.2.6 Utility Object
contains the following:

Disk

Contents - The

utility

object

disk

CONTENTS

UIC
[1,1]

System object library, ANSI
object module, and ODT

[1,2]

Error message file and Startup command file

[1,20]

ODL and build command files for unmapped utility tasks

[1,24]

Build command files for mapped utility tasks

[1,30]

UIC for unmapped map files

[1,34]

UIC for mapped map files

[1,50]

Baseline unmapped
SYSGEN

[1,54]

UIC for mapped task files

Executive

magtape

and

FCS

concatenated

tasks

required

[200,200] SYSGEN3.CMD and BLDUMD.CMD command files to
utility tasks and user mode diagnostic tasks.

for

build

2.1.2.7 Device Combinations Supported by the Single RK05 Distribution
Kits - The following list contains the valid combinations of devices
for use in generating a target system.
You must have one of the
following combinations to successfully complete a system generation
with the single RK05 kits:
1.

RK05 disk and TAll cassette (working storage)

RK05 disk and TU56 DEC tape (working storage)

RK05 disk and RXOI floppy disk (working storage)

RK05 disk and TUlO, TEIO or TS03 magtape (working storage)

RK05 disk and TU16, TE16, or TU45 magtape (working storage)

Two RK05
mounted)

2.1.3

disks

(source

and

object

disk

simultaneously

Dual RK05 Release Kits - Summary

2.1.3.1 Summary of Dual RK05 Disk Release
Kit
Contents - The
distribution kit contains five RK05 disk cartridges identified as:
1.

Baseline System Disk - BASLINE

2-9

GETTING STARTED
2.

Executive Source Disk - EXECSRC

User-tailored System Disk - SYSTEM

Utility Object Disk - UTILOBJ

MCR/FCP Source Disk - MCRFCP

For a given system generation type, mapped or unmapped system,
three
of these disks are used:
the Baseline system disk;
the Executive
source disk;
and the User-tailored system disk. The Utility object
disk is used if the non-privileged utility tasks are to be built. The
MCR source disk is used if the user wishes to modify MCR or FCP.
The dual RK05 distribution kit requires 24K words of memory and either
one RK05 removable platter drive and one RKOSF fixed platter drive, or
two RKOS removable platter drives.
The Baseline system disk (BASLINE),
and the Executive source
(EXECSRC), are used during the first phase of system generation.

disk

Among the files on the BASLINE disk are:
1.

The mapped and unmapped Baseline system Executive.

The system tasks

The system generation indirect command files PRESYSGEN.CMD,
PRESGNl.CMD, PRESGN2.CMD, SGNXFER.CMD, and SGNXFER2.CMD.

Among the files on the EXECSRC disk are:
1.

The system generation indirect command file, SYSGEN.CMD,
three
query
files
SGNEXEC,
SGNPER,
and SGNTT,
SGNKLAB.CMD.

the
and

Output files created during the first phase of system generation are
generated on the EXECSRC disk and then copied to the BASLINE disk.

2.1.3.2 Summary of Dual RK05 Magtape Release Kit Contents - The
release kit consists of five 600-foot,
9-track, 800 BPI magnetic
tapes. The magtapes contain five RKOS disk images. Also included, is
a tape containing a stand-alone version of DSC. The five images
correspond to the five disks described in Section 2.1.3.1.
The five magtapes are:

Baseline system tape containing the file BASLINE

Executive source tape containing the file EXECSRC

User-tailored system tape containing the file SYSTEM

Utility object tape containing the file UTILOBJ

MCR/FCP source tape containing the file MCRFCP

Before beginning a ~YSGEN, the appropriate files must be copied
RK05 cartridges uS1ng the Disk Save and Compress Utility (DSC).
procedure is described later in this Chapter.

2-10

onto
This

GETTING STARTED
2.1.4

Dual RK05 Release Kits - Details -

2.1.4.1 Baseline System Disk (BASLINE) Contents - The Baseline system
disk contains the following:
Contents

UIC
[1,1]

System libraries
library

and

the

virtual

[1,2]

Error message text and the startup command file

[1,50]

Unmapped Baseline Executive and system tasks

[1,54]

Mapped Baseline Executive and system tasks

[200,200]

PRESYSGEN.CMD, PRESGNl.CMD, PRESGN2.CMD,
SGNXFERX.CMD, and COPYTSK.CMD

The RSX-IIM system that is distributed on this disk
the utility tasks.

memory

SGNXFER.CMD,

provides

The tasks contained on the BASLINE disk are:
BAD
BIGMAC
BIGTKB
BOO
CDA
CMP
DMO
DMP
EDI
FCPNMH
FLX
IND
INI
INS
LBR
LOA
MAC
MCR
MOU
PAT
PIP
SAV
SLP
TKB
TKN
UFD
UNL
VFY
VMR
ZAP

Bad block locator routine
14K Macro-II assembler
14K Task builder (RSX-IIM Linker)
MCR Boot command
Crash dump analyzer
Routine to compare ASCII source files
MCR Dismount command
File dump routine
Line text editor
2K non-multi-header file system
File transfer routine
Indirect command file processor
MCR Disk Initialization command
MCR Install command
Library files maintenance and creation routine
MCR Load command
8K Macro-II assembler
Monitor console routine
MCR Mount command
Object module patch routine
Peripheral interchange program
MCR Save command
Source language input program
8K task builder
Task termination notification routine
MCR User File Directory command
MCR Unload command
File structure verification routine
Virtual monitor console routine
Task image and data files patch routine

Devices generated into this system are:
4 RK05 disk drives
1 terminal

2-11

workfile

all

GETTING STARTED
In addition, loadable drivers and data
following:

bases

are

provided

for

the

2 TAll cassette drives
2 TU56 DECtape drives
2 RXOI floppy disk drives
1 TE/TUIO or TS03 magtape drive
1 TE/TU16 or TU45 magtape drive
1 LPll or LSll line printer
1 PCll paper tape punch

2.1.4.2 Executive Source Disk
(EXECSRC)
source disk contains the following:
UIC

Contents - The

Executive

Contents

[11,10]

The Executive source files

[45,10]

K-series lab peripheral support sources

[45,20]

Assembly command files for K-series lab peripherals
an unmapped system

[45,24]

Assembly command files for K-series lab peripherals
a mapped system

[200,200] SGNEXEC.CMD,
SGNTT.CMD,
SYSGENO.CMD, SGNKLAB.CMD

SGNPER.CMD,

2.1.4.3 Utility Object Disk (UTILOBJ) Contents - The
disk contains the following:
UIC

SYSGEN.CMD,

utility

object

Contents

[1,1]

System libraries

[1,2]

Error message text and the startup command file

[1,20]

Object module libraries, task build command
unmapped systems

[1,24]

Task build command files for mapped systems

files

for

[200,200] SYSGEN3.CMD and BLDUMD.CMD

2.1.4.4 User-tailored
System
Disk
(SYSTEM)
User-tailored system disk contains the following:
UIC

Contents - The

Contents

[1,1]

System libraries, Executive symbol definition library,
ODT and TRACE object modules, concatenated object
module files for the Purdue ICS/ISA/UDC routines,
virtual memory workfile library, and a concatenated
object module file containing FCS routines for ANSI
magtape support

[1,2]

Error message text and the

2-12

startu~

command file

GETTING STARTED
[1,20]

Build command files for the system tasks on an unmapped
system

[1,24]

Build command files for the system tasks
system

mapped

[200,200] Assembly files
for
FCS
ANSI
magtape
support,
SYSGEN2.CMD, 11SGEN.CMD, BLDDRV.CMD, and SYSGEN2A.CMD

2.1.4.5 MCRFCP Source Disk (MCRFCP) Contents - The
contains the following:
UIC

MCR

source

disk

unmapped

and

the

shuffler

Contents

[1,1]

The Executive macro library

[1,20]

The build command
system

[1,24]

The build command files for
(SHF) on a mapped system

[12,10]

Sources for MCR

[12,20]

MCR assembly command files for an unmapped system

[12,24]

MCR assembly command files for a mapped system

[13,10]

Sources for FCP

[13,20]

FCP assembly command file for an unmapped system

[13,24]

FCP assembly command file for a mapped system

[15,10]

Sources for RMDEMO and the task shuffler SHF

files

for

RMDEMO
RMDEMO

2.1.4.6 Device Combinations Supported by Dual RK05 - The following is
a list of the valid device combinations for use in generating a target
system. One of these combinations is required when using the dual
RK05 distribution kit.
1.

An RK05 removable platter
platter disk drive

Two RK05 removable platter disk drives

2.1.5

disk

drive

and

RK05F

fixed

RLOI Kits - Summary

2.1.5.1 Summary of RLOI Disk Release Kit Contents - The
kit contains three RLOI disk cartridges identified as:
1.

Mapped system object disk - MAPSYS

Unmapped system object disk - UNMSYS

Utility object disk - RLUTIL
2-13

distribution

GETTING STARTED

For a given system generation type, mapped or unmapped system, one or
two of these disks are used -- the applicable system object disk and,
if any of the utilities are to be rebuilt, the utility object disk.
The system object disks are
SYSGEN.

used

during

the

first

two

phases

Among the files on these disks are:
1.

The Baseline System Executive and loadable drivers

The System tasks

Complete source code for the Executive

The system generation indirect MCR command files SYSGEN.CMD,
SYSGENO.CMD, SGNEXEC.CMD, SGNPER.CMD, SGNTT.CMD, SYSGEN2.CMD,
11SGEN.CMD, and BLDDRV.CMD

2.1.5.2 Summary of RLOI Magtape Release Kit Contents - The release
kit consists of three 600-foot, 9-track, 800-BPI magtapes. The
magtapes contain three RLOI disk images. Also included, is a tape
containing a stand-alone version of DSC. The three images correspond
to the three disks described in Section 2.1.5.1. The three magtapes
are:
1.

Mapped system object disk - MAPSYS

Unmapped system object disk - UNMSYS

Utility object disk - RLUTIL

Before beginning a SYSGEN, the appropriate files must be copied
RLOI cartridges using the Disk Save and Compress utility (DSC).
procedure is described in Section 2.2.3.5.

2.1.6

onto
This

RLOI Release Kits - Details

2.1.6.1 Mapped System Object D,isk
(MAPSYS) - The
generating a mapped system contains the following:
UIC

object

disk

for

Contents

[1,1]

Executive and system macro libraries, virtual memory
workfile library; FORTRAN Purdue ICR/ICS/UDC r'outines
object modules, ANSI magtape FCS concatenated object
module, and ODT and TRACE debugging aids.

[1,2]

System error message file and the startup command file.

[1,24]

Mapped system tasks object module libraries and
system task-build command files.

[1,54]

Utility tasks

2-14

mapped

GETTING STARTED
All system-supplied tasks and loadable drivers built to
run with this Executive.

[11,10]

[200,200] The system generation indirect MCR command
files
SYSGEN.CMD.
SYSGENO.CMD,
SGNEXEC.CMD,
SGNPER.CMD,
SGNTT.CMD, 'SYSGEN2.CMD, and 11SGEN.CMD.
The RSX-llM system that is distributed on this disk
the utility tasks.

provides

all

for

the

The tasks contained on the MAPSYS disk are:
BAD
BIGMAC
BIGTKB
BOO
CDA
CMP
DMO
EDI
FCPNMH
FLX
IND
INI
INS
LBR
LOA
MAC
MCR
MOU
PAT
PIP
SAV
SLP
TKB
TKN
UFD
UNL
VFY
VMR
ZAP

Bad block locator routine
14K Macro-II assembler
14K Task builder (RSX-llM Linker)
MCR Boot command
Crash dump analyzer
Routine to compare ASCII source files
MCR Dismount command
Line text editor
2K non-multi-header file system
File transfer routine
Indirect command file processor
MCR Disk Initializaiton command
MCR Install command
Library file, maintenance and creation routine
MCR Load command
8K Macro-II assembler
Monitor console routine
MCR Mount command
Object module patch routine
Peripheral interchange program
MCR Save command
Source language input program
8K task builder
Task termination notification routine
MCR User File Directory command
MCR Unload command
File structure veri~ication routine
Virtual monitor console routine
Task image and data files patch routine

Devices generated into this system are:
2 RLOI disk drives
1 terminal
In addition, loadable drivers and data
following:
2 TAll cassette drives
2 TU56 DECtape drives
2 RXOI floppy disk drives
1 TUIO or TS03 magtape drive
1 TU16 or TU45 magtape drive
1 LPll or LSll line printer
1 PCll papter tape punch

2-15

bases

are

provided

GETTING STARTED
2.1.6.2 Unmapped System Object Disk (UNMSYS) - The object
generating an unmapped system contains the following:

disk

for

Contents

UIC
[1,1]

Executive and system macro libraries, virtual memory
workfile library, FORTRAN Purdue ICR/ICS/UDC routines
object modules, ANSI magtape FCS concatenated object
module, and ODT and TRACE debugging aids.

[1,2]

System error message file and the startup command file.

[1,20]

Unmapped system tasks object module libraries
unmapped system task-build command files.

[1,50]

Utility tasks

[11,10]

All system-supplied tasks and loadable drivers built to
run with this Executive.

and

[200,200] The system generation indirect MCR command
files
SYSGEN.CMD,
SYSGENO.CMD,
SGNEXEC.CMD,
SGNPER.CMD,
SGNTT.CMD, SYSGEN2.CMD,and 11SGEN.CMD.
The RSX-IIM system that is distributed on this disk
the utility tasks.

provides

The tasks contained on the UNMSYS disk are:
BAD
BIGMAC
BIGTKB
BOO
CDA
CMP
DMO
DMP
EDI
FCPNMH
FLX
IND
INI
INS
LBR
LOA
MAC
MCR
MOU
PAT
PIP
SAV
SLP
TKB
TKN
UFD
UNL
VFY
VMR
ZAP

Devices generated into this system are:
2 RLOI disk drives
1 Terminal

2-16

all

GETTING STARTED
In addition, loadable drivers and data
following:

bases

are

provided

for

the

2 TAll cassette drives
2 TU56 DECtape drives
2 RXOI floppy disk drives
1 TUIO or TS03 magtape drive
1 TU16 or TU45 magtape drive
1 LPll or LSll line printer
1 PCll paper tape punch

2.1.6.3 Utility Object
contains the following:
UIC

Disk

(RLUTIL) - The

object

disk

Contents

[1,1]

Exeuctive and system macro libraries, virtual memory
workfile library, ANSI magtape FCS concatenated object
module, and ODT and TRACE debugging aids.

[1,2]

System error message file and the startup command file.

[1,20]

Task-build command files.

[1,50]

Baseline Executive and system tasks.

[12,10]

MCR source modules.

[13,10]

FCP source modules.

[15,10]

Source files for RMDEMO and the task shuffler.

[35,10]

DMP source files.

[45,10]

Source files for the K-series laboratory peripherals.

[45,20]

Build command files for K-series laboratory peripherals
on an unmapped system.

[45,24]

Build command files for K-series laboratory peripherals
on a mapped system.

[200,200] System
generation
indirect
SYSGEN3.CMD and BLDUMD.CMD.

2.1.7

utility

MCR

command

files

RP02j03, RP04jOSj06, RM03 and RK06 Magtape Release Kit

The RP02/03, RP04/05/06, and RK06 magtape release kits consist of four
magtapes.
Three tapes contain the saved image of the disk contents
and the fourth tape contains a bootable, stand-alone version of the
Disk Save and Compress utility (DSC) that copies the tape to disk.
Each disk image contains a running unmapped and mapped Executive and
all tasks.
The unmapped Executive is bootstrapped automatically by
the hardware bootstrap.
In addition to the two systems,
the disks
contain all of the files necessary to build a target system as well as
the source for the Executive, MCR, FCP, DMP, RMDEMO, and the shuffler
task.
You can generate a mapped or unmapped system while running
either the unmapped or mapped Executive. The only difference between
the kits is that each has the appropriate disk driver for the disk it
is to run on.

2-17

GETTING STARTED
2.1.7.1 RP02/03, RP04/05/06, RM03, and RK06 Magtape Release Kit
Contents - The disk images in the magtape release kits contain the
following:
UIC

CONTENTS

[1,1]

Executive and system macro libraries,
the virtual
memory
workfile
library,
system object library,
Executive symbol definition library, FORTRAN Purdue ISA
routine object modules, ANSI magtape FCS concatenated
object module, and ODT and TRACE debugging aids

[1,2]

SYSGEN text file, system error
command file

[1,3]

Directory for lost files found by VFY

[1,4]

Directory for Snap Shot and Post-Mortem Dumps

[1,6]

Directory for Error Log files

[1,20]

Unmapped
system
privileged
task
object
module
libraries, nonprivileged task object module libraries,
and unmapped system task-build command and overlay
descriptor files

[1,24]

Mapped system privileged task object module libraries,
and
mapped system task-build command and overlay
descriptor files

[1,30]

Directory for unmapped system task build maps

[1,34]

Directory for mapped system task-build maps

[1,50]

RSX-IlM unmapped Baseline System Executive and all
system-supplied tasks and loadable drivers built to run
with this Executive

[1,54]

RSX-IIM mapped Baseline System Executive and
all
system-supplied tasks and loadable drivers built to run
with this Executive

[1,60]

Directory for unmapped RSX-IIS Executive and tasks

[1,64]

Directory for mapped RSX-llS Executive and tasks

[11,10]

Executive source files

[11,20]

Directory for unmapped Executive object files

[11,24]

Directory for mapped Executive object files

[11,30]

Directory for unmapped Executive listing files

[11,34]

Directory for mapped Executive listing files

[11,40]

Directory for Executive source correction files

[12,10]

MCR source files

[12,20]

Unmapped MCR assembly command files and object
build command file

2-18

message

file,

startup

library

GETTING STARTED
[12,24]

Mapped MCR assembly command
library build command file

[12,30]

Directory for unmapped MCR listing files

[12,34]

Directory for mapped MCR listing files

[12,40]

Directory for MCR correction files

[13,10]

FCP source files

[13,20]

Unmapped FCP assembly command file

[13,24]

Mapped FCP assembly command file

[13,30]

Directory for unmapped FCP listing files

[13,34]

Directory for mapped FCP listing files

[13,40]

Directory for FCS correction files

[15,10]

Source files for RMDEMO system
shuffler

[15,20]

Directory for unmapped RMDEMO and shuffler object files

[15,24]

Directory for mapped RMDEMO and shuffler object files

[15,30]

Directory for
files

[15,34]

Directory for mapped RMDEMO and shuffler listing files

[35,10]

DMP source files

[35,20]

DMP assembly command file

[35,30]

Directory for DMP listing files

[45,10]

K-series lab peripheral support source files

[45,20]

Assembly command files
devices (unmapped)

for

K-series

lab

peripheral

[45,24]

Assembly command
devices (mapped)

for

K-series

lab

peripheral

unmapped

files

and

display

RMDEMO

and

object

task

module

and

shuffler

the

listing

[200,200] SYSGEN command files,
FCS and FORTRAN Object Time
System
(OTS)
resident library files, and SGNKLAB.CMD
file for generating K-series lab support
The devices generated into the system for this kit are:
2 RP02/03, RP04/05/06 or RK06 disk drives
1 terminal

2-19

GETTING STARTED
In addition, loadable drivers with loadable data
for the following devices:

bases

are

supplied

2 TAlljTU60cassette drives
2 TClljTU56 DECtape drives
2 RXlljRXOl floppy disk drives
2 TUIO, TEIO, or TS03 magtape drive or
1 TU16, TE16, or TU45 magtape drive
1 LPll line printer
1 PCll paper tape punch
The partition layouts for the unmapped and mapped systems are
identical to those for the RK05 distribution disks. Both the mapped
and unmapped Executives are supplied with copies of all the system
tasks.

2.2

SAVING DISTRIBUTION DISKS

2.2.1

Saving the Single and Dual RK05 Distribution Disks

Because the distribution disks are actively manipulated during the
generation of a user-tailored system, you must back up the disks prior
to their actual use in system generation. To allow preserving RK05
disks on cassette, DECtape or floppy disk, DIGITAL provides a
stand-alone utility called the Volume Preservation Program (PRESRV).
To save RK05 disks on magtape or RKOS disk, DIGITAL provides the
utility DSC (disk save and compress) as a stand-alone system and also
as an object library to be built as a task. Both PRESRV and DSC are
described in separate manuals.
You must always save the object disk on which the system is to be
generated, because the target system will replace the Baseline System
on that disk.
(It is also good practice to save the Executive source
disk, as well as the MCR, FCP and DMP, and utility object disks.)
Before saving the single RKOS release disks, you should verify that
they can be read on your disk drives. You can do this by using the
read-check option of the VFY program, which is available on all disks.
After bootstrapping a disk, run VFY and specify the JRC (read-check)
switch. If any blocks are unreadable, VFY reports them.
VFY is
described in the RSX-ll Utilities Procedures Manual. If a disk is
unreadable, call the local DIGITAL Software Support Specialist for
assistance.
A minimum RKOS system must
peripheral devices:

include

one

the

following

An RK05 disk and a dual TU56 DEC tape unit,

An RK05 disk and a dual TAll cassette tape unit,

Dual RKOS units,

An RK05 and an RXOI floppy disk, or

An RK05 disk and a TUIO, TU16,
magtape drive.

2-20

TU4S,

TEIO,

TE16,

sets

TS03

GETTING STARTED
To save the disks in the distribution kit, follow the appropriate
procedure described in Section 2.3 to bootstrap the unmapped object
disk. Then, use the MCR BOOT command to bootstrap DSC or PRESRV. The
full sequence is described below.
Bootstrapping the system -- the following display results:
RSXIIM V03.1 BL22 16K
>RED DKO:=SYO:
>RED DKO:=LBO:
>MOU SYO:UNMOBJ
>@STARTUP
*PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY)
>TIM hrs:mins[:secs] [mnth/day/year]
>@<EOF>
>INS [1,50]BOO

[S]:

Bootstrapping DSC using the following MCR command:
>BOO [1,50]DSCSYS
DSC is bootstrapped and the following display occurs:
DSC>RSX-llS V02.1 BL22 DISK SAVE AND COMPRESS UTILITY
Bootstrapping PRESRV using the following MCR commands:
>BOO [1,50]PRESRV
PRESRV is bootstrapped and the following display occurs:
RSX-llS V02.1 BL22
VOLUME PRESERVATION PROGRAM - V02.5
FOR HELP TYPE /HE
nne - BLOCKS AVAILABLE FOR BUFFERING
PRE>
indicating that the PRESRV program is ready for input.
nne - BLOCKS AVAILABLE FOR BUFFERING indicates how
blocks are available for buffering.

The message
many 256-word

Depending on the specific backup medium you use
(cassette, DECtape,
RK05 disk, or magtape), you should select one of the following
procedures to back up the contents of the RK05 disk.

2.2.1.1

Preserving an RK05 on DECtape:

To backup an RK05 on DECtape, use the following PRESRV command lines:
PRE>DTO:label/BL:l/VE=DKO:/BL:l

(16K machines)

PRE>DTO:label/BL:4/VE=DKO:/BL:4

(all others)

where label is the name to be given to the file on DECtape.

2-21

GETTING STARTED
2.2.1.2

Preserving an RKOS on Cassette:

To back up an RKOS on a cassette, use
lines:

the

following

PRESRV

PRE)CTO:label/BL:l/VE=DKO:/BL:l

(16K machines)

PRE)CTO:label/BL:3/VE=DKO:/BL:3

(all others)

command

where label is the name to be given to the file on the cassette.

2.2.1.3

Saving an RKOS on an RKOS:

To back up an RKOS on an RKOS, use the following DSC command line:
DSC)DKl:/VE=DKO:

2.2.1.4

Preserving an RKOS on Floppy Disk:

To back up an RKOS on a floppy disk, use the following PRESRV
lines:
PRE)DXO:label/BL:l/VE=DKO:/BL:l

(16K machines)

PRE)DXO:label/BL:6./VE=DKO/BL:12.

(all others)

command

where label is the name given to the file on the floppy disk.

2.2~1.S

Saving an RKOS on Magtape:

To back up an RKOS on a magnetic tape, use the following
lines:

DSC

command

DSC)MTO:/VEC=224
DSC)MTO:/VE=DKO:

(TU10, TE10, and TS03)

DSC)MMO:/VE=DKO:

(TU16, TE16, and TU4S)
NOTE

The following table shows the assignment
of interrupt vectors in DSC to specific
devices either by
default,
or
by
explicit use of the /VEC switch:

Interrupt
Vector

Default Devices

Must Specify by /VEe

224

TU 16/TE 16ITU45

TU 1O/TE 1O/TS03

254

RP04/05/06

RM03, RP02/03

2-22

GETTING STARTED
The first DECtape, cassette, or floppy disk that you use to preserve a
volume contains a bootstrappable image of PRESRVi
thus, if the system
disk is inadvertently destroyed, you can restore it by bootstrapping
from
the first tape created.
Such bootstrapping automatically
initiates PRESRV, which you can then use to restore the original disk
contents.
You can put DSC onto a magtape or DECtape by using the VMR SAV command
and thus make it available to single disk systems.
For example, the following procedure copies DSC to a bootable magtape:
)ASN XXn:=LB:
)ASN XXn:=SY:
)SET /UIC=[l,50]
)LOA MT:
)RUN $VMR
ENTER FILE NAME:DSCSYS
VMR)SAV MT:DSCSYS
VMR)"Z
)

2.2.2 Saving the
Distribution Kits

RP02/03,

RP04/05/06,

RK05/06,

RLOl,

and

RM03

These distribution kits are on 600-foot, 9-track, BOO-BPI magtapes and
therefore,
are already saved.
To create a disk, you must copy the
disk image file from tape to the disk by using DSC.
The first step is
to select the DSC tape, mount it on the drive, and boot in the
stand-alone version of DSC.
The first tape is then mounted on tape
drive zero.
Following this, the disk is mounted on disk drive zero
and allowed to reach operating speed.
The command strings shown below copy the disk image from tape to disk.
For RP02 and RP03 disks:
DSC)DP:/VEC=254
DSC)MTO:/VEC=224
DSC)DP:/VE=MTO:

(TUlO, TElO, and TSOl)

DSC)DP:/VEC=254
DSC)DP:/VE=MMO:

(TU16, TE16, and TU45)

For RP04/05/06 disks:
DSC)MT:/VEC=224
DSC)DB:/VE=MTO:

(TUlO, TElO, and TS03)

DSC)DB:/VE=MMO:

(TU16, TEl6, and TU45)

For RK05 disks:
DSC)MTO:/VEC=224
DSC)DKO:/VE=MTO:

(TUlO, TElO, and TSOl)

DSC)DKO:/VE=MMO:

(TU16, TEl6, and TU45)

2-23

GETTING STARTED

For RK06 disks:
DSC)MT:/VEC=224
DSC)DM:/VE=MTO:

(TUlO, TElO, and TS02)

DSC)DM:/VE=MMO:

(TU16, TE16, and TU45)

For RLOI disks:
DSC)MTO:/VEC=224
DSC)DLO:/VE=MTO:

(TUlO, TElO, and TSOl)

DSC)DLO:/VE=MMO:

(TU16, TE16, and TU45)

For RM03 disks:
DSC)MT:/VEC=224
DSC)DR:/VEC=254
DSC)DR:/VE=MTO:

(TUlO, TElO, and TS03)

DSC)DR:/VEC=254
DSC)DR:/VE=MMO:

(TU16, TE16, and TU45)

2.2.3

Restoring Damaged Volumes

If the system disk is destroyed on a single RK05 system, it must be
re-created by means of a backup that has been created by PRESRV or
DSC. Bootstrapping a tape backup created via PRESRV produces the
following console display:
RSX-llS V02.1 BL22
VOLUME PRESERVATION PROGRAM - V02.4
FOR HELP TYPE /HE
nne - BLOCKS AVAILABLE FOR BUFFERING
PRE)
PRESRV is now ready to accept commands. To restore the contents of a
disk from cassette, DECtape or floppy disk, assuming the disk and
backups are mounted on unit 0 of their respective controllers.
You
should then enter the appropriate commands given in sections 2.2.3.1
through 2.2.3.5.

2.2.3.1

Cassette Restoration

PRE)DKO:/VE/BL:l/FO=CTO:label

(16K machines)

PRE)DKO:/VE/FO=CTO:label

(all others)

where label is the name that was specified when the disk was preserved
on the cassette.
Cassette bootstrapping without a cassette ROM
bootstrap requires an extensive key-in procedure via the console
switch register.
On an 11/05/10/20/34/35/40/45/50/55/60/70, the key-in procedure is:
1.

Press HALT.

Enter the address 001000 in the console switch
press LOAD ADRS.

2-24

and

GETTING STARTED
3.

Enter the first value from the right-hand column of the table
below in the console switch register; lift the DEP switch.

Enter the next value from the right-hand column of the
in the console switch register;
lift the DEP switch.

Repeat Step 4 for the remaining 26 values in the table.

Enter the address 001000 in the console switch
press LOAD ADRS.

Lift the HALT switch.

Press START.

At this point, the cassette is bootstrapped and
initial message and prompt.

2.2.3.2

ADDRESS VALUE

001000 012700
001002 177500
001004 005010
001006 010701
001010 062701
001012 000052
001014 012702
001016 000375
001020 112103
001022 112110
001024 100413
001026 130310
001030 001776
001032 105202

001034 100772
001036 116012
001040 000002
001042 120337
001044 000000
001046 001767
001050 000000
001052 000755
001054 005710
001056 100774
001060 005007
001062 017640
001064 002415
001066 112024

PRESRV

table

and

displays

its

DECtape Restoration

PRE)DKO:/VE/BL:l/FO=DTO:1ahe1/TP

(16K machines)

PRE)DKO:/VE/FO=DTO:1abel/TP

(all other s)

where label is the name that was specified when the disk was preserved
to DECtape.

2.2.3.3

Floppy Disk-to-RK Disk Restoration

PRE)DKO:/VE/FO/BL:l.=DXO:1abel/TP

(16K machines)

PRE)DKO:/VE/FO/BL:12.=DXO:labe1/TP

(all others)

where label is the name that was specified when the disk was preserved
to floppy disk.

2-25

GETTING STARTED
2.2.3.4 Restoring Damaged Disks with DBC - Mount the tape with the
bootable image of DSC on unit zero of the appropriate controller and
boot it with the bootstrap ROM. When DSC is loaded, it displays the
following:
RSX-llS V02.l BL22 DISK SAVE AND COMPRESS UTILITY
DSC)
It is now ready to accept commands.
Disk to disk restoration:
DSC)DKl:/VE=DKO:

(RK05)

DSC)DMl:/VE=DMO:

(RK06)

DSC)DP:/VEC=254
DSC)DPl:/VEC=254
DSC)DPl:/VE=DPO:

(RP02/03)

DSC)DBl:/VE=DBO:
DSC)DLl:/VE=DLO:
DSC)DR:/VEC=254
DSC)DRl:/VEC=254
DSC)DRl:/VE=DRO:

(RP04/05/06)

Magtape restoration:

(TUlO/TElO/TS03)

DSC)MT:/VEC=224

(setup vector for MT:)

DSC)DKO:/VE=MTO:

(RK05)

DSC)DMO:/VE=MTO:

(RK06)

DSC)DP:/VEC=254
DSC)DPO:/VE=MTO:

(RP02/03)

DSC)DBO:/VE=MTO:
DSC)DRO:/VEC=254
DSC)DRO:/VE=MTO:

(RP04/05/06)

Magtape restoration:

(TUl6/TEl6/TU45)

DSC)DKO:/VE=MMO:

(RK05)

DSK)DMO:/VE=MMO:

(RK06)

DSC)DP:/VEC=254
DSC)DP:/VE=MMO:

(RP02/03)

DSC)DB:/VE=MMO:

(RP04/05/06)

It is advisable to create a backup disk.
In the event that
inadvertent destruction of a system disk occurs, a backup is available
and you can create an additional backup at will.
On systems with more than one disk unit, where disks are the normal
backup medium, you can restore damaged system disks by copying the
existing backup disk.

2-26

GETTING STARTED
2.2.4

Exiting from PRESRV or DSC

Because PRESRV and DSC are stand-alone programs, the only way to exit
from them is to bootstrap in a new system or stand-alone program.

2.2.5

Formatting Disks

Formatted disks are required to restore or create a disk copy of the
saved distribution kit disks.
RK05, RP02/03, and RP04/05/06 disks
that have never been used, require formatting before any data can be
written on them.
RK06 disks are pre-formatted at the factory and
should not be formatted at the customer site.
Formatting a disk
causes timing and addressipg information to be recorded on the disk.
This is done by using the stand-alone PRESRV program.
The command
lines given in Section 2.2.3 include the switch /FO, which indicates
that a format pass should be made before copying the backup to the
disk.
This ensures that all data is readable on the disk.
For
additional information see the PDP-II Volume Preservation
(PRESRV)
User's Guide.
You may also use the User Mode Diagnostics in an
on-line system to format the disks.

2.3

BOOTSTRAPPING THE BASELINE SYSTEM

The procedure for bootstrapping depends on which hardware bootstrap is
present on the host processor.
On processors with a programmer
console, the operator must first halt the processor by pressIng the
HALT key, set the console switches to the hardware bootstrap ROM
address, press the LOAD ADRS key, and then press the START key.
The
RSX-IIM system message is then displayed at the console terminal. The
step-by-step procedure is carried out as described in section 2.3.1,
2.3.2, or 2.3.3.
On an 11/04/34 processors having the M930l-YA/YB
ROM, and those processors with the M930l-YF ROM the operator must
press the BOOT button and enter (via the console terminal) the device
name and unit number of the peripheral device from which the bootstrap
is to occur.
The step-by-step procedure is described in section
2.3.4.

2.3.1

Start-up Using the BM792-YB Bootstrap ROM
1.

Press HALT.

Set the console switches to 173100.

Press LOAD ADRS.

Enter the address of the load device in the console switches:
RKll disk

177406

RPll disk

176716

TCll DEC tape

177344

Lift up the HALT key.

Press START.

The start-up sequence shown in section 2.4 is then
console terminal.
2-27

displayed

the

GETTING STARTED
2.3.2

Start-up Using the MRII-DB Bootstrap ROM
1.

Press HALT.

Enter the address of the load device in the console switches:
RKll disk

173110

TCll DEC tape

173120

TMll magtape

173136

RPll disk

173154

Press LOAD ADRS.

Lift up the HALT key.

Press START.

The start-up sequence shown in section 2.4 is then
console terminal.

2.3.3

displayed

the

Start-up Using the BM873-YA Bootstrap ROM
1.

Press HALT.

Enter the address of the load device in the console switches:
RKll disk

173010

TC11 DEC tape

173030

TMl1 magtape

173050

RP11 disk

173100

RC11 disk

173144

KL11/DLl1

173210

TAll cassette

173230

PC11 papertape 173312
3.

Press LOAD ADRS.

Lift up the HALT key.

Press START.

The start-up sequence shown in section 2.4 is then
console terminal.

2-28

displayed

the

GETTING STARTED
2.3.4

Start-up Using the BM873-YB Bootstrap ROM
1.

Press HALT.

Enter the address of the load device in the console switches:
RKll disk (unit 0)

173030

RKll disk (unit in switch register)

173032

TCll DECtape (unit 0)

173070

TMll/TMAll magtape (unit 0)

173110

RFll disk

173136

RHll/RH70/TM02/TU16 magtape (unit 0)

173150

RCll disk

173212

RHll/RH70 device combination (unit 0)

173230

RHll/RH70 device combination (unit in
switch register)

173232

RHll/RH70/RP04 disk (unit 0)

173320

RHll/RH70/RP04 disk (unit in
switch register)

173322

RPll/RP02/RP03 disk (unit 0)

173350

RPll/RP02/RP03 disk (unit in
switch register)

173352

KLll/DL11 console terminal reader

173510

TAll cassette (unit 0)

173524

TAll cassette (unit in switch register)

173526

PCll paper tape reader

173620

Press LOAD ADRS.
(For units
number in switch register.)

Lift up the HALT key.

Press START.

other

than

The start-up sequence shown in section 2.4 is then
console terminal.

2-29

zero,

enter

displayed

unit

the

GETTING STARTED
2.3.5

Start-up Using the M9301-YA or M9301-YB Bootstrap ROM
1.

Press the BOOT switch.

In response to the "$" prompt on the console terminal,
one of the following:

enter

M9301-YB only

DB - RJP04 disk
DK - RKll disk
DP - RPll (RP02j03) disk
DT - TCll DECtape
DX - RXll floppy disk
CT - TAll cassette tape
MC - Mixed massbus device

M9301-YB only

MM - TM02/TU16 magtape

M9301-YB only

MT - TMll/TUlO magtape
PR - PCll/PRll paper tape reader
TT - KLll/DLll console terminal reader
followed by an optional, single octal digit for bootstrapping
from units other than zero, and terminated by a carriage
return.
The start-up sequence shown in section 2.4 is then
console terminal.

2.3.6

displayed

the

Perform

the

M9301-YC Bootstrap (PDP-ll/70 Only)

The M9301-YC bootstrap operates only on the
following steps to use the bootstrap:

PDP-llj70.

Press HALT switch and set back to ENABLE position.

Set the start of address of 17765000 in the console switches.

Press LOAD ADDR.

Set the device unit number in switches 0 through 2.

Set the device code in switches
codes are:
Code

through

Device

0001

TMll/TUlO/TElO/TS03 Magnetic Tape

0010

TCll/TU56 DECtape

0011

RKll/RK05 DECpack Disk Cartridge

0100

RPll/RP02/RP03 Disk Pack

2-30

The

device

GETTING STARTED
0110

RH70/TM02/TU16/TE16/TU45 Magnetic Tape

0111

RH70/RP04/RPOS/RP06 Disk Pack

RH70/RS04/RS03 Fixed Head Disk

Ensure that switches 7 through 21 are off (down).

Press START.

The system then displays on the console terminal the start-up sequence
described in Section 2.4.
Before the M9301-YC bootstrap actually boots 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 local DIGITAL Field Service Engineer.
It may, however, be possible to continue with the bootstrap operation
if the lights contain the address 17773644, 17773736, or 17773764,
which indicates a cache failure.
To continue in this case, press
CONT.
The M9301-YC bootstrap is capable of relocating its input to various
banks of memory.
However, RSX-IIM can not be bootstrapped in this
manner.

2.3.7

M9301-YF Bootstrap ROM

The following instructions bootstrap the system by means of the
M9301-YF console emulator.
Refer to the M9301 Bootstrap/Terminator
Maintenance Manual, Order Number EK-M9301-MM, for other ways to boot
the system with the M9301-YF.
Follow this procedure at the operator's terminal:
1.

Press the console BOOT switch.
If diagnostics are enabled,* the M9301-YF performs primary
CPU diagnostics. The terminal then displays the contents of
RO, R4, SP, and RS, respectively;
the contents appear as
four 16-bit octal numbers.
Note that pressing the BOOT
switch at this time causes PDP-II systems without console
registers
(PDP-llj04s,
for example) to copy the PC into RS
before the power-up sequence begins.
The terminal then displays the prompt $ at the beginning of a
new line.

* The M9301-YF micro switches must be set to 000 to
perform
diagnostics when using the console emulator to boot the system.
If
the switches are set to 002, the M9301-YF console emulator boots the
system without performing diagnostics.
Consult a DIGITAL Field
Service engineer or see the M9301 Bootstrap/Terminator Maintenance
Manual.

2-31

GETTING STARTED
2.

In response to the prompt $, type the appropriate device code
at the terminal, followed by carriage return:
Code

Device

DBn

RP04, RPOS, RP06

DKn

RKOS

DMn

RK06

DTn

TUS6

DXn

RXOl

MMn

TUl6, TU4S, or TEl6

MTn

TUlO or TEIO

PCll

DLll

In the list of codes above, n represents the device unit number;
the
only permissible values are 0 through 7. The unit number can be
omitted if it is o.
If diagnostics are enabled, the M930l-YF performs secondary CPU and
memory diagnostics before booting the system.
The system then
displays on the console terminal the start-up sequence described in
section 2.4.

2.4

CONSOLE DISPLAY

If the system being bootstrapped contains support for devices which
are not in the host configuration, a series of messages appears on the
console terminal in the following form:
DEVICE ddnn:

NOT IN CONFIGURATION

where:
dd
device name
nn = unit number
Messages of this form indicate which devices are not physically
present on the host system. These units are declared OFFLINE by the
bootstrap code.

2-32

GETTING STARTED

Then the system displays:
RSX-IIM V03.1 BL22 nnnnK [MAPPED]
>RED ddnn:=SYO:
>RED ddnn:=LBO:
>MOU ddnn:label
>@[1,2]STARTUP
where:
V03.1

- The RSX-IIM version number.

BL22

- The RSX-IIM base level number.

nnnnK

- Size of memory on hardware configuration
from which the system was bootstrapped.

MAPPED

- MAPPED is displayed for systems built to
use the memory management unit.

- Load device name.

- Load device unit.

label

- The volume label of the system disk.

@[1,2]STARTUP

- Start-up MCR command file that contains
user determined commands to initialize the
system.

The system is now ready to run. The RED and MOU commands displayed
are internally generated REDIRECT and MOUNT commands. The REDIRECT
command establishes the load device as the system devices
(LB:
and
SY:), and the MOUNT command mounts the load device as a Files-II
volume. The @[1,2]STARTUP command is also internally generated and
executes a set of MCR commands that initialize your system (e.g., to
request that you set the time and date, etc.).

2-33

CHAPTER 3
SYSGEN DIALOGUE DETAILS

3.1

SYSGEN DIALOGUE

This chapter provides details of the SYSGEN dialogue.
Each phase of
the process is discussed. Section 3.2 covers phase 1 (SYSGEN.CMD and
SYSGENO.CMD);
Section 3.3, the query section
(SGNEXEC, SGNPER,
SGNTT); Section 3.4 covers phase 2 (SYSGEN2.CMD and BLDDRV.CMD);
and
Section 3.5, phase 3 (SYSGEN3.CMD and BLDUMD.CMD).
All text, questions, and commands displayed during the running of the
command file are described.
However, during any single run of the
command file, many of these questions and commands will not be
executed, since they depend on both the machine configuration that the
system generation is being run on, and the target machine the system
is being built for.
Appendix D contains a console output listing for
an actual system generation run.
At various places during the execution of the command files,
SYSGEN
asks questions to which the user must reply by typing Y (for yes), or
N (for no), followed by a carriage return.
(A reply of just a
carriage return is an alternative way of saying no.) Such questions
are distinguished by a leading asterisk (*) and trailing"?
[YIN] :".
Other questions require a string response.
These have a leading
asterisk and trailing "[S] :". There are also questions that requIre a
numeric response.
These have a leading asterisk and trailing "[0]:"
for an octal response or "[D]:h for a decimal response.
Usually,
the
numeric queries contain range and default arguments such as "[D
R:l.-16. D:4.) :." (Range arguments are the limits that the response
must be within and the default argument is the value assigned if just
carriage return is typed.) Command file processing is suspended until
an answer is keyed in.
In many places in the description of the command files,
a command
shown has a UIC specification containing one of the characters x and
y. The command actually issued when the command file is processed
will contain the character 0 or 4 as a replacement for x or y.
The
replacement for x depends on the target system
(the system being
generated) -- if the target system is unmapped, x is replaced by 0;
if the target system is mapped, x is replaced by 4.
Similarly,
the
replacement for y depends on the host system (the system that is
currently running) -- if the host system is unmapped, y is replaced by
0; if the host system is mapped, y is replaced by 4.
Example:
SET /UIC=[1,2x]
will, during the processing of the command file, appear as
SET /UIC=[1,24]
if a mapped system is being generated.
3-1

SYSGEN DIALOGUE DETAILS
The SYSGEN command files have been designed
to
inhibit
the
installation and removal of tasks already installed in the host
system. This makes it possible to perform a SYSGEN on a multi-user
system without affecting the tasks in that system. A SYSGEN can be
performed on-line with a multi-user system by using the Assign
(ASN)
command to assign a logical device name (SY:) to a physical device
containing a release disk.

3.2

SYSGEN.CMD FILE DETAILS

This section describes the entire SYSGEN.CMD indirect command file by
adding descriptive text to the actual command file to clarify the
SYSGEN process. The command file is presented in upper-case text;
the descriptive text is presented in upper- and lower-case text.
The SYSGEN.CMD indirect command file is common to all distribution
kits. Hence, some sections pertain only to a specific kit or group of
kits.
Each section of the file that differs between kits is
identified. To avoid confusion, read only these sections that pertain
to your kit.
If you are using the dual RK05 distribution kit, you must initialize
the system and supply parameters specific to the dual RK05 kit. Also,
it is required that you copy the distribution kit before beginning
SYSGEN.
The
indirect command file PRESYSGEN.CMD supplies the
necessary parameters and insures that you have copied the distribution
kit.
***DUAL RK05***
The command file PRESYSGEN.CMD is used only when you are performing
SYSGEN with the dual RK05 distribution kit.
PRESYSGEN <VERSION 03.1>
COPYRIGHT (C) 1977
DIGITAL EQUIPMENT CORP., MAYNARD, MASS.

01754

INITIALIZE SYSTEM FOR DUAL RK05 SYSGEN
THIS COMMAND FILE WILL PREPARE THE SYSTEM DISK FOR USE
BY THE SYSTEM GENERATION PROGRAMS.
THE DUAL RK05 DISTRIBUTION KIT REQUIRES AT LEAST:
24K WORDS OF MEMORY, AND
ONE RK05 REMOVABLE PLATTER DISK DRIVE, PLUS
ONE RK05F FIXED PLATTER DISK DRIVE
OR
TWO RK05 REMOVABLE PLATTER DISK DRIVES.
* DOES THIS SYSTEM MEET THE ABOVE REQUIREMENTS? [YIN]:
If it does not, you are informed to contact your local
Digital office to obtain the correct distribution kit.
If it does, PRESYSGEN continues.
BEFORE STARTING SYSGEN, YOU MUST MAKE A COPY OF THE DISTRIBUTION
KIT. THIS WILL ENSURE THAT YOUR DISTRIBUTION KIT IS COMPLETE AND

3-2

SYSGEN DIALOGUE DETAILS

SERVE AS A BACKUP. AS THE BASLINE, EXECSRC, AND SYSTEM DISKS ARE
ALTERED BY SYSGEN, IT IS NECESSARY TO USE A NEW COpy EACH TIME.
* HAVE YOU COPIED THE DISTRIBUTION KIT AS REQUIRED? [YIN]:
If you have not made a copy, the following is displayed
PRESYSGEN halts.

and

WE WILL EXIT NOW SO THAT YOU CAN COpy THE DISTRIBUTION KIT.
AFTER THE COPYING IS COMPLETE, START THE PRESYSGEN FILE AGAIN.
If you have copied the kit, PRESYSGEN continues.
* IN WHICH RK05 UNIT IS THE BASLINE DISK MOUNTED?

[0 R:O-3] :

The following assumes that the BASLINE disk
DKI: .

mounted

The RK05 unit containing the BASLINE disk is assigned to the
pseudo device SY:.
ASN DKI:=SY:
* ARE YOU RUNNING SYSGEN STANDALONE?

[YIN]:

**STANDALONE SYSGEN**
ASN DKI:=LB:
* DOES THIS SYSTEM HAVE TWO RK05 REMOVABLE PLATTER DRIVES?

[YIN]:

If you have two removable RK05 drives, the next question
bypassed.

If you have a fixed platter drive, you must copy the BASLINE
disk to it.
* HAVE YOU COPIED THE BASLINE DISK TO THE RK05F?

[YIN] :

If you have not, instructions for doing so are displayed and
PRESYSGEN terminates.
Otherwise, PRESYSGEN continues with
the query to determine whether or not you are generating a
mapped system.
WE WILL USE ONE UNIT OF THE RK05F FOR THE SYSTEM DISK. YOU WILL
HAVE TO COPY THE SYSTEM DISK TO THE RK05F, USING DSCSYS. BECAUSE
DSCSYS SUPPORTS ONLY TWO LOGICAL DEVICE UNITS, USE THE IUNIT
SWITCH AS SHOWN BELOW:
RSX-IIS V02.1 8L22 DISK SAVE AND COMPRESS UTILITY
DSC)DKO:/UNIT=n
DSC)DKI:/UNIT=m
DSC)DKO:=DKI:
DSC)
AFTER DSC HAS COMPLETED THE COPY, HARDWARE BOOT THE RK05F AND
START THE PRESYSGEN COMMAND FILE ON IT
INS $BOO
BOO [1,50]DSCSYS
If you have two removable RK05 drives or if you have copied
the BASLINE disk to the RK05F, PRESYSGEN continues here.

3-3

SYSGEN DIALOGUE DETAILS

* ARE YOU GENERATING A MAPPED SYSTEM?

[Y/N]:

*STANDALONE AND MAPPED*
SET /UIC=[1,54]
INS $PIP
PIP [1,54]/RE/NV=[1,50]BADSYS.*;*,DSCSYS.*;*,PRESRV.*;*
REM PIP
WE WILL NOW BOOT THE MAPPED BASELINE SYSTEM. ONCE IT IS RUNNING,
DISMOUNT THE SYSTEM DISK AND SAVE THE SYSTEM, WRITING A NEW BOOT
BLOCK. WHEN THE SYSTEM COMES UP AGAIN, START THE PRESGNI INDIRECT
COMMAND FILE. E.G.,
RSXllM V03.1 BL22 64K MAPPED
>RED DKl:=SYO:
>RED DKl:=LBO:
>MOU DKl:BASLINE
>@[1,2]STARTUP
>*PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY)
>TIM 1:00 1/1/78
>@ <EOF>
>DMO DKl:
>SAV /WB
RSXllM V03.1 BL22 64K MAPPED
>RED DKl:=SYO:
>RED DKl:=LBO:
>MOU DKl:BASLINE
>@[1,2]STARTUP
*PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY)
>TIM 1:02 1/1/78
>@ <EOF>
>@ PRESGNI

[S]: 1:00 1/1/78

[S]: 1:02 1/1/78

INS $BOO
BOO [1,54]RSXllM
The following is the display of PRESGNI.
* HAVE YOU SAVED THE MAPPED SYSTEM?

[Y/N]:

If you have not, the following is displayed
halts. Otherwise, PRESGNI continues.

and

PRESGNI

WE WILL EXIT NOW SO THAT YOU CAN DISMOUNT THE BASLINE DISK,
SAVE AND WRITE A BOOT BLOCK FOR THE MAPPED SYSTEM AND THEN
RESTART THE PRESGNI COMMAND FILE.
>DMO DKl:
>SAV /WB
If you have saved the mapped system, PRESGNI continues here.
INS $PIP
SET /UIC=[1,54]
PIP [1,50]*.*;*/DE
The above commands delete the unmapped system.
* ENTER THE UNIT NUMBER OF THE EMPTY RK05 DRIVE [0 R:0-3]:
The following assumes DK2:

3-4

is the empty drive.

SYSGEN DIALOGUE DETAILS

PLACE THE EXECSRC DISK IN DK2:
* IS THE EXECSRC DISK READY?

AND START IT UP

[Y/N]:

This query is repeated until the disk is ready (Y response).
MOU DK2:EXECSRC
ASN DK2:=SY:
ASN DKl:=LB:
SET /UIC=[l,l]
PIP LB:/CO=RSXMAC.SML
REM PIP
Control is
SYSGEN.CMD.

then

passed

the

indirect

command

file

*STANDALONE AND UNMAPPED*
SET /UIC=[1,54]
INS $PIP
PIP *.*;*/DE
The above commands delete the mapped system.
* ENTER THE UNIT NUMBER OF THE EMPTY RK05 DRIVE [0 R:O-3]:
The following assumes DK2:

is the empty drive.

PLACE THE EXECSRC DISK IN DK2: AND START IT UP (WRITE ENABLED)
* IS THE EXECSRC DISK READY? [Y/N]:
This query is repeated until the disk is ready (Y response).
MOU DK2:EXECSRC
ASN DK2:=SY:
SET /UIC=[l,l]
PIP LB:/CO=RSXMAC.SML
REM PIP
Control is
SYSGEN.CMD.

then

passed

the

indirect

command

file

**ON-LINE SYSGEN**
TO PERFORM A SYSGEN ON-LINE, THE FOLLOWING TASKS MUST BE
INSTALLED: EDI, FLX, INI, MAC, PIP, TKB, AND UFD. THESE TASKS MUST
REMAIN INSTALLED ON THE RUNNING SYSTEM UNTIL THE SYSGEN PROCESS IS
COMPLETE. WE WILL PAUSE NOW TO ALLOW YOU TO INSTALL THE REQUIRED
TASKS.
After you have installed the requisite tasks, type RES AT.
to continue.
The RK05 unit that contains the BASLINE disk
is then assigned to the pseudo device LB:.
The following
assumes that DKl: contains the BASLINE disk.
ASN DKl:=LB:
* DOES THE RUNNING SYSTEM HAVE TWO REMOVABLE RK05 DISK DRIVES?

[Y/N]:

If you have two removable RK05s, the following is displayed.
If you have an RK05F, the next three queries and associated
text is omitted;
the next query will concern the unit
number of the RK05F.
3-5

SYSGEN DIALOGUE DETAILS
* ARE YOU GENERATING A MAPPED SYSTEM?

[Y/N]:

If you are, the unmapped BAD, DSC,
and PRESRV files are
copied to the mapped directory and then the unmapped files
are deleted.
SET /UIC=[1,54]
PIP [1,54]/RE/NV=[1,50]BADSYS.*;*,DSCSYS.*;*,PRESRV.*;*
PIP [ 1 , 50] * . * ; * /D E
If you are not generating a mapped system, the files
mapped system are deleted.

for

SET /UIC=[1,50]
PIP [1,54] * • *; * /DE
Whether you are generating a mapped or unmapped system,
following is displayed.

the

* ENTER THE UNIT NUMBER OF THE EMPTY RK05 DRIVE [0 R:0-3]:
The following assumes that DK2:
PLACE THE EXECSRC DISK IN DK2:
* IS THE EXECSRC DISK READY?
This question
response) .

is the empty drive.

AND START IT UP (WRITE ENABLED).

[Y/N]:
repeated

until

the

disk

ready

MOU DK2:EXECSRC
ASN DK2:=SY:
SET /UIC=[l,l]
PIP LB:/CO=RSXMAC.SML
Control then passes to the indirect command file SYSGEN.CMD.
The following is displayed if you have an RK05F drive.
WE WILL USE ONE UNIT OF THE RK05F FOR THE BASLINE DISK.
BECAUSE
THE BASLINE DISK WILL NOT BE USED AS THE RUNNING SYSTEM, WE WILL
CREATE THE UFD'S NECESSARY AND PIP THE FILES TO THE RK05F.
* ENTER ONE UNIT NUMBER OF THE RK05F:
The following assumes that DK1: was entered.
ALL DK1:
INI DK1:BASLINE/BAD=[AUTO]
MOU DK1:BASLINE
ASN DK1:=SY:
SET /U I C= [ 1 , 1] ,
PIP /UF/CO=LB:SYSLIB.OLB,VMLIB
SET /UIC=[1,2]
PIP /UF/CO=LB:QIOSYM.MSG,STARTUP.CMD
UFD DK1: [1,20]
UFD DK1: [1,24]
UFD DK1: [1,50]
UFD DK1: [1,54]
UFD DK1: [2,20]
UFD DK1: [200,200]
SET /UIC=[200,200]
PIP =LB:PRESGN2.CMD,SGNXFER,SGNXFER2,COPYTSK

3-6

SYSGEN DIALOGUE DETAILS
* ARE YOU GENERATING A MAPPED SYSTEM? [YIN]:
The following assumes that you are generating a mapped
system.
Note that if you are generating an unmapped system
the UIC is set to [1,50].
SET IUIC=[1,54]
PIP =LB:[1,50]BADSYS.*,DSCSYS.*,PRESRV.*
PIP @[200,200]COPYTSK
After the files are copied,
the indirect command file
PRESGN2.CMD is invoked to replace the BASLINE disk with the
EXECSRC
disk.
The
following
actually
comes
from
PRESGN2.CMD.
DMO LB:
ASN LB:=SY:
REMOVE THE BASLINE DISK FROM DKl:
EXECSRC DISK.
* IS THE EXECSRC DISK READY?
This question
response) .

AND REPLACE IT WITH THE

[YIN] :

repeated

then

passed

until

the

disk

ready

MOU DKl:EXECSRC
ASN DKl:=LB:
SET IUIC=[l,l]
PIP LB:/CO=RSXMAC.SML
Control is
SYSGEN.CMD.

indirect

the

command

file

***ALL SYSTEMS***
The following begins the display
file SYSGEN.CMD.
SYSGEN PART 1

the

indirect

command

COPYRIGHT (C) 1975, 1976, 1977
DIGITAL EQUIPMENT CORP., MAYNARD MASS. 01754.
DETERMINE SYSTEM FEATURES AND ASSEMBLE THE EXECUTIVE

SET IUIC=[200,200]
EXPANDED COMMENTS PROVIDE A DESCRIPTION OF EVERY STEP IN THIS
SYSGEN COMMAND FILE. ON THE OTHER HAND, SHORT COMMENTS
PROVIDE VIRTUALLY NO EXPLANATORY TEXT.
I

* DO YOU WANT EXPANDED COMMENTS? [YIN]:
For the experienced programmer who has performed many
SYSGENs, much of the descriptive text in the file may be
suppressed by answering N to this question.
It
is
recommended that the less experienced or first time user
answer Y,
in order to be guided thtough the
system
generation process.

3-7

SYSGEN DIALOGUE DETAILS
The next set of queries are asked to
identify
the
distribution kit that is being used in SYSGEN. When a kit
has been identified (a Y response to the query),
further
queries as to which distribution kit is being used are
omitted and SYSGEN continues processing the applicable
sections.

[YIN]:

* DO YOU HAVE THE SINGLE RK05 DISTRIBUTION KIT?

If the response is affirmative, further queries to identify
the kit are not necessary. The next queries are found under
the heading SINGLE RK05 kit.
If the response
asked.

negative,

the

* DO YOU HAVE THE DUAL RK05 DISTRIBUTION KIT?

following

question

[YIN]:

If the response is affirmative, continue under
DUAL RK05 KIT.

the

If the response
asked.

question

fiegative,

* DO YOU HAVE THE RLOI DISTRIBUTION KIT?

the

following

heading
is

[YIN]:

This is the last query to identify the distribution kit.
A
Y response obviously means that the kit is an RLOI kit. The
next queries are found under the Heading RLOI KIT.
An N response implies that the distribution kit is a big
disk type
(RP02/03/04/05/06, RM03, or RK06).
The next
queries are found under the heading ALL KITS.
*****SINGLE RK05 KIT*****
This sections appears only if the response as to whether
single RK05 kit is being used was affirmative.

not

the

AS A RESULT OF THE SYSGEN PROCEDURE, THE DISTRIBUTION KIT WILL
BE CUSTOMIZED TO YOUR TARGET SYSTEM CONFIGURATION. YOU MUST MAKE
A COpy OF IT BEFORE PROCEEDING ANY FURTHER IF YOU HAVEN'T
ALREADY DONE SO.

,
* HAVE YOU ALREADY MADE A COPY OF THE EXEC SOURCE DISK? [YIN]:
As a result of SYSGEN, a number of files will be modified on
the distribution kit. This might make the kit unusable for
later SYSGENs. Therefore, the user must make a backup copy
before performing a SYSGEN.
If the answer to this question
is N, SYSGEN part 1 terminates.
DUE TO DISK SPACE RESTRICTIONS ON THE RK05 DISTRIBUTION KIT
(BOTH RK DISK AND MAG~APE KITS) DRIVERS WHICH WILL NOT
BE USED IN YOUR TARGET SYSTEM MUST BE DELETED.
;

* HAVE YOU ALREADY DELETED THE DRIVER SOURCE MODULES? [YIN]:
If the answer to this question is Y,
the next section is
bypassed.
If the answer is N, the next section is entered
to delete unused files.
This text actually comes from the
command file SYSGENO.CMD.

3-8

SYSGEN DIALOGUE DETAILS

WE WILL NOW DELETE THE UNUSED DRIVER MODULES. THIS WILL MAKE
ROOM FOR COMPLETING THE SYSGEN AND ALSO ROOM FOR CORRECTIONS
TO THE EXECUTIVE WHICH ARE PUBLISHED IN THE SOFTWARE
DISPATCH.
IN GENERAL THIS WILL NOT CAUSE PROBLEMS
SINCE RSXllM SUPPORTS A NUMBER OF PERIPHERAL DEVICES
WHICH HAVE BEEN SUPERSEDED BY THOSE OF NEWER DESIGN.
FOR EXAMPLE:
IF YOU HAVE AN RP04/05/06 YOU PROBABLY DON'T HAVE AN RPR02/03
IF YOU HAVE AN RS03/RS04 YOU PROBABLY DON'T HAVE AN RFll
IF YOU HAVE A TU16/45 YOU PROBABLY DON'T HAVE A TUIO
IF YOU HAVE A DMCll YOU PROBABLY DON'T HAVE A DAll-B
AND SO ON.
IF AT A LATER DATE, YOU ACQUIRE A DEVICE WHOSE DRIVER HAS BEEN
DELETED FROM THIS DISK, YOU CAN EASILY RETRIEVE IT FROM THE
ORIGINAL DISTRIBUTION DISK AND PUT IT ON THIS DISK.
;

SET IUIC=[ll,lO]
In the following section, there is a question preceding each
PIP command.
The PIP command will actually be issued only
if the answer to the preceding question is N.
* DO YOU HAVE ANY ADOl-D AID CONVERTER CONTROLLERS? [YIN]:
PIP ADDRV.MAC;*/DE
* ANY AFCll AID CONVERTER CONTROLLERS? [YIN]:
PIP AFDRV.MAC;*/DE
* ANY ARll LABORATORY PERIPHERAL SYSTEM CONTROLLERS? [YIN]:
PIP ARDRV.MAC;*/DE
* ANY CRll/CMll CARD READER CONTROLLERS? [YIN]:
PIP CRDRV.MAC;*/DE
* ANY TAll/TU60 CASSETTE DRIVES? [YIN]:
PIP CTDRV.MAC;*/DE
* ANY RJP/RWP04/05/06 DISK DRIVES? [YIN]:
PIP DBDRV.MAC;*/DE
* ANY RFll FIXED HEAD DISK DRIVES? [YIN]:
PIP DFDRV.MAC;*/DE
* ANY RKll/RK03/05 DISK DRIVES? [YIN]:
PIP DKDRV.MAC;*/DE
* ANY RLll/RLOl DISK DRIVES? [YIN]:
PIP DLDRV.MAC;*/DE
* ANY RK6ll/RK06 DISK DRIVES? [YIN]:
PIP DMDRV.MAC;*/DE
* ANY RPll/RPR02/RP03 DISK DRIVES? [YIN]:
PIP DPDRV.MAC;*/DE
* ANY RWM03 DISK DRIVES? [YIN]:
PIP DRDRV.MACj*/DE
* ANY RJS/RWS03/04 FIXED HEAD DISK DRIVES? [YIN]:
PIP DSDRV.MACj*/DE
* ANY TCll/TU56 DECTAPE DRIVES? [Y/N]:
PIP DTDRV.MACj*/DE
* ANY RXll/RXOl FLOPPY DISK DRIVES? [YIN]:
PIP DXDRV.MACj*/DE
* ANY VTll/VS60 GRAPHICS DISPLAYS? [YIN]:
PIP GRDRV.MAC;*/DE
* ANY LPAll LABORATORY PERIPHERAL ACCELERATORS? [YIN]:
PIP LADRV.MACj*/DE
* ANY LPll/LSll/LVll PRINTERS? [YIN]:
PIP LPDRV.MAC;*/DE
* ANY LPSll LABORATORY PERIPHERAL SYSTEMS? [YIN]:
PIP LSDRV.MACj*/DE
* ANY TJ/TWU16/45/TE16 TAPE DRIVES? [YIN]:
PIP MMDRV.MACj*/DE

3-9

SYSGEN DIALOGUE DETAILS

* ANY TMll/TUlO/TElO/TS03 TAPE DRIVES? [Y/N]:
PIP MTDRV.MACi*/DE
* ANY PCll PAPER TAPE READER/PUNCHES? [Y/N]:
PIP PPDRV.MACi*/DE
* ANY PRll PAPER TAPE R~ADERS? [Y/N]:
PIP PRDRV.MACi*/DE
* ANY ICR/ICSll INDUSTRIAL CONTROLLERS? [Y/N]:
PIP ICDRV.MACi*/DE,ICOM.MACi*
* ANY DRS/DSSll DIGITAL INPUT/OUTPUT MODULES? [Y/N]:
PIP ISDRV.MACi*/DE,ISCOM.MACi*,DSSDI.MACi*
* ANY UDCll UNIVERSAL INDUSTRIAL CONTROLLERS? [YIN]:
PIP UDDRV.MACi*/DE,UDCOM.MACi*
* ANY DAII-B UNIBUS LINKS? [Y/N]:
PIP XBDRV.MACi*/DE
* ANY DLII-E ASYNCHRONOUS LINES? [Y/N]:
PIP XLDRV.MACi*/DE
* ANY DMCll INTERPROCESSOR LINKS? [Y/N]:
PIP XMDRV.MACi*/DE
* ANY DPll SYNCHRONOUS LINE INTERFACES? [Y/N]:
PIP XPDRV.MACi*/DE
* ANY DQll SYNCHRONOUS LINE INTERFACES? [Y/N]:
PIP XQDRV.MACi*/DE
* ANY DUll SYNCHRONOUS LINE INTERFACES? [Y/N]:
PIP XUDRV.MACi*/DE
* ANY DUPll SYNCHRONOUS LINE INTERFACES? [Y/N]:
PIP XWDRV.MACi*/DE
This is the end of SYSGENO.CMD.
SET /UIC=[200,200]
PIP SYSGENO.CMDi*/DE
The next queries that will be
heading ALL KITS.

displayed

appear

under

the

*****DUAL RK05 KIT*****
This section appears only if the response as to whether or not the
dual RK05 kit is being used was affirmative and if SYSGEN is being
initiated manually. The user is asked to identify the RKOS units that
contain the BASLINE disk and the EXECSRC disk.
*IN WHICH RK05 UNIT IS THE BASLINE DISK MOUNTED?
*IN WHICH RK05 UNIT IS THE EXECSRC DISK MOUNTED?
The unit that contains the BASLINE disk is then assigned to
LB:, and the unit that contains EXECSRC is assigned to SY:.
ASN DKn:=SY:
ASN DKn:=LB:
DUE TO DISK SPACE RESTRICTIONS ON THE RKOS DISTRIBUTION KIT
(BOTH RK DISK AND MAGTAPE KITS) DRIVERS WHICH WILL NOT
BE USED IN YOUR TARGET SYSTEM MUST BE DELETED.
i

* HAVE YOU ALREADY DELETED THE DRIVER SOURCE MODULES? [Y/N]:
If the answer to this question is Y,
the next section
bypassed.
If the answer is N, the next section is entered
to delete unused files.
This text actually comes from the
command file SYSGENO.CMD.
WE WILL NOW DELETE THE UNUSED DRIVER MODULES. THIS WILL MAKE
ROOM FOR COMPLETING THE SYSGEN AND ALSO ROOM FOR CORRECTIONS

3-10

SYSGEN DIALOGUE DETAILS
TO THE EXECUTIVE WHICH ARE PUBLISHED IN THE SOFTWARE
DISPATCH. IN GENERAL THIS WILL NOT CAUSE PROBLEMS
SINCE RSXIIM SUPPORTS A NUMBER OF PERIPHERAL DEVICES
WHICH HAVE BEEN SUPERSEDED BY THOSE OF NEWER DESIGN.
FOR EXAMPLE:
IF YOU HAVE AN RP04/05/06 YOU PROBABLY DON'T HAVE AN RPR02/03
IF YOU HAVE AN RS03/RS04 YOU PROBABLY DON'T HAVE AN RFll
IF YOU HAVE A TU16/45 YOU PROBABLY DON'T HAVE A TUIO
IF YOU HAVE A DMCll YOU PROBABLY DON'T HAVE A DAII-B
AND SO ON.
IF AT A LATER DATE, YOU ACQUIRE A DEVICE WHOSE DRIVER HAS BEEN
DELETED FROM THIS DISK, YOU CAN EASILY RETRIEVE IT FROM THE
ORIGINAL DISTRIBUTION DISK AND PUT IT ON THIS DISK.
;

SET /UIC=[ll,lO]
In the following section, there is a question preceding each
PIP command.
The PIP command will actually be issued only
if the answer to the preceding question is N.
* DO YOU HAVE ANY ADOI-D A/D CONVERTER CONTROLLERS? [YIN]:
PIP ADDRV.MAC;*/DE
* ANY AFCll A/D CONVERTER CONTROLLERS? [Y/N]:
PIP AFDRV.MACi*/DE
* ANY ARll LABORATORY PERIPHERAL SYSTEM CONTROLLERS? [Y/N]:
PIP ARDRV.MAC;*/DE
* ANY CRll/CMll CARD READER CONTROLLERS? [Y/N]:
PIP CRDRV.MACi*/DE
* ANY TAll/TU60 CASSETTE DRIVES? [Y/N]:
PIP CTDRV.MACi*/DE
* ANY RJP/RWP04/05/06 DISK DRIVES? [Y/N]:
PIP DBDRV.MACi*/DE
* ANY RFll FIXED HEAD DISK DRIVES? [Y/N]:
PIP DFDRV.MAC;*/DE
* ANY RKll/RK03/05 DISK DRIVES? [Y/N]:
PIP DKDRV.MACi*/DE
* ANY RLll/RLOl DISK DRIVES? [Y/N]:
PIP DLDRV.MACi*/DE
* ANY RK611/RK06 DISK DRIVES? [Y/N]:
PIP DMDRV.MAC;*/DE
* ANY RPll/RPR02/RP03 DISK DRIVES? [Y/N]:
PIP DPDRV.MACi*/DE
* ANY RWM03 DISK DRIVES? [Y/N]:
PIP DRDRV.MACi*/DE
*ANY RJS/RWS03/04 FIXED HEAD DISK DRIVES? [Y/N]:
PIP DSDRV.MACi*/DE
* ANY TCll/TU56 DECTAPE DRIVES? [Y/N]:
PIP DTDRV.MACi*/DE
* ANY RXll/RXOl FLOPPY DISK DRIVES? [Y/N]:
PIP DXDRV.MACi*/DE
* ANY VTll/VS60 GRAPHICS DISPLAYS? [Y/N]:
PIP GRDRV.MACi*/DE
* ANY LPAll LABORATORY PERIPHERAL ACCELERATORS? [Y/N]:
PIP LADRV.MACi*/DE
* ANY LPll/LSll/LVll PRINTERS? [Y/N]:
PIP LPDRV.MACi*/DE
* ANY LPSll LABORATORY PERIPHERAL SYSTEMS? [Y/N]:
PIP LSDRV.MACi*/DE
* ANY TJ/TWU16/45/TE16 TAPE DRIVES? [Y/N]:
PIP MMDRV.MACi*/DE
* ANY TMll/TUlO/TElO/TS03 TAPE DRIVES? [Y/N]:
PIP MTfiRV.MACi*/DE
* ANY PCll PAPER TAPE READER/PUNCHES? [Y/N]:

3-11

SYSGEN DIALOGUE DETAILS
PIP PPDRV.MAC:*/DE
* ANY PRll PAPER TAPE READERS? [YIN]:
PIP PRDRV.MAC:*/DE
* ANY ICR/ICSll INDUSTRIAL CONTROLLERS? [Y/N]:
PIP ICDRV.MAC:*/DE,ICOM.MAC:*
* ANY DRS/DSSll DIGITAL INPUT/OUTPUT MODULES? [YIN]:
PIP ISDRV.MAC:*/DE,ISCOM.MAC:*,DSSDI.MAC:*
* ANY UDCll UNIVERSAL INDUSTRIAL CONTROLLERS? [YIN]
PIP UDDRV.MAC;*/DE,UDCOM.MAC;*
* ANY DAII-B UNIBUS LINKS? [YIN]:
PIP XBDRV.MAC;*/DE
* ANY DLII-E ASYNCHRONOUS LINES? [YIN]:
PIP XLDRV.MAC;*/DE
* ANY DMCll INTERPROCESSOR LINKS? [Y/N]:
PIP XMDRV.MAC;*/DE
* ANY DPll SYNCHRONOUS LINE INTERFACES? [Y/N]:
PIP XPDRV.MAC;*/DE
* ANY DQll SYNCHRONOUS LINE INTERFACES? [Y/N]:
PIP XQDRV.MACj*/DE
* ANY DUll SYNCHRONOUS LINE INTERFACES? [Y/N]:
PIP XUDRV.MACj*/DE
* ANY DUPll SYNCHRONOUS LINE INTERFACES? [Y/N]:
PIP XWDRV.MAC;*/DE
This is the end of SYSGENO.CMD.
SET /UIC=[200,200]
PIP SYSGENO.CMD;*/DE
The next queries that will be displayed appear under the
heading ALL KITS.
****RLOI KIT****
This section appears only if the response as to whether or not the
RLOI kit is being used was affirmative.
If you are using the RLOI
kit, you must make a copy of it before proceeding with SYSGEN.
YOU MUST MAKE A COpy OF THE RLOI DISTRIBUTION KIT, IF YOU
HAVE NOT DONE SO ALREADY.
* HAVE YOU COPIED THE RLOI DISTRIBUTION KIT? [Y/N]:
If you have not copied the kit, the following is displayed
and the command file exits. You must then restart SYSGEN.
WE WILL EXIT NOW SO THAT YOU CAN COpy THE DISTRIBUTION KIT.
AFTER YOU HAVE COPIED THE KIT RESTART THE SYSGEN COMMAND FILE.
If you have copied the kit, the next
the heading ALL KITS.

queries

appear

under

*****all kits*****
* ARE YOU BUILDING AN RSXIIS SYSTEM? [Y/N]:
The selection of features and assembly of the Executive are
controlled by the SYSGEN.CMD command file. This question is
used later to select the correct SYSGEN phase 2 command file
for RSX-IIM or RSX-IIS and to determine the Executive
options.

3-12

SYSGEN DIALOGUE DETAILS

* ARE YOU BUILDING A MAPPED SYSTEM?

[Y/N]:

The reply to this question determines the UIC settings that
will be generated during the SYSGEN process. See Appendix A
for UIC conventions used on the distribution kit disks.

* ARE YOU RUNNING ON A MACHINE WITH AT LEAST 24K WORDS? [Y/N]:
The Baseline System Executive is set up with a 14K partition
that can be used if the host machine has at least 24K of
memory.
If this is the case, SYSGEN will use the larger and
faster version of MACRO-II and the task builder during the
generation process.

* ARE YOU RUNNING ON A MACHINE WITH A LINE PRINTER?
If you are, the next question is
omitted.

asked.

[YIN]:
Otherwise

* IS IT A 132. COLUMN LINE PRINTER? [Y/N]:
* WILL YOUR SYSTEM INCLUDE DSS-ll SUPPORT? [Y/N]:
* WILL YOUR SYSTEM INCLUDE ICS/ICR-ll SUPPORT?

[Y/N]:

When building DSS-ll and/or ICS/ICR-ll support into the
Executive, device common blocks that map to the DSS-ll
and/or ICS/ICR-ll device registers must be copied from the
source disk to the disk on which SYSGEN phase 2 will be run.
The reply to this question will cause the proper files to be
copied at the right time.

* WILL YOUR SYSTEM INCLUDE UDC-ll SUPPORT? [Y/N]:
When building UDCll support into the Executive, device
common blocks that map to the UDCll device registers must be
copied from the source disk to the disk on which SYSGEN
phase 2 will be run. The reply to this question will cause
the proper files to be copied at the right time.
This
question will not be asked if ICS/ICR-ll support was
selected, since ICS/ICR-ll support precludes UDCll support.
The following section is pertinent if you are using an RK06,
RLOl, or RP distribution kit.
It is also necessary on the
RK05 kits
(single or dual)
if the driver sources have
already been deleted.
DELETE FILES FROM PAST SYSGENS
NOTE: ON VIRGIN DISKS, NONE OF THE FILES WE TRY TO
DELETE WILL EXIST. PIP WILL GIVE ERROR MESSAGES
THAT SHOULD INDICATE THAT THE FILE DOES NOT EXIST.
In generating a system, several files are created.
These
files are of no use after a successful completion of a
SYSGEN.
If another SYSGEN is to be performed from a disk on
which a previous SYSGEN was performed, these files should be
deleted to free disk space.
The
following
commands
accomplish the desired cleanup.
By convention, the following files in an unmapped system are
stored under UIC [11,20]:

3-13

SYSGEN DIALOGUE DETAILS
1.

The assembly command
(RSXASM.CMD)

file

assemble

the

Executive

The

file

build

the

Executive

build

command

(RSXBLD~CMD)

Executive object modules created during the assembly
the Executive

A file of concatenated Executive object modules built by
PIP and used by the Librarian to build the Executive
object module library

Files for the DSS-ll and/or ICS/ICR-ll or UDCll used to
build device common blocks for tasks which reference the
device

PIP [11,20] *.OBJi*/DE,*.UDCi*,*.ICRi*,*.IDS;*
The preceding PIP commands delete:
1.

All object module files

All versions of UDCll modules

All versions of ICS/ICR-ll modules

All versions of DSS-ll modules
On a release kit disk that has never had a SYSGEN
performed on it, no residual files from a previous
SYSGEN exist.
Thus, the attempted deletion is
flagged by PIP.
These are warning diagnostics and do not affect the
SYSGEN currently in progress.

PIP [11,24] *.OBJ;*/DE,*.UDC;*,*.ICR;*,*.IDS;*
It cannot be known whether the previous SYSGEN done on the
source disk was for a mapped or an unmapped system. The
preceding command deletes the files generated for building a
mapped system.
PIP [11,30] UDCOM.LST;*/DE,ICTAB;*,ICOM;*,DSSDI;*,ISCOM;*
PIP [11,34] UDCOM.LST;*/DE,ICTAB;*,ICOM;*,DSSDI;*,ISCOM;*
The previous commands delete listing files generated for
DSS-ll, ICR/ICS-ll, or UDCll common blocks for both mapped
and unmapped areas on the disk.
By convention, UIC [11,10] is used for the device table file
(SYSTB.MAC), prefix file
(RSXMC.MAC), and the ICR/ICS-ll
table file produced during the running of the three query
files.
The output of the query files is used to configure
the system.
PIP [11,10] RSXMC.MAC;*/DE,SYSTB;*,ICTAB;*,RSXBLD.TMP;*
Delete all existing versions of the
prefix file, and ICS/ICR-ll table.

3-14

device

table

file,

SYSGEN DIALOGUE DETAILS
PIP [11,20] RSXASM.CMD;*/DE,RSXBLD;*
PIP [11,24] RSXASM.CMD;*/DE,RSXBLD;*
Delete all existing versions of the assembly command
and task-build command file for the executive.

file

Regardless of the distribution kit you are using and whether
or not the driver sources have been deleted, processing
continues here.
SET /UIC=[ll,lO]
3.3

SYSGEN QUERY SECTION

NOW WE BEGIN THE SYSGEN QUERY SECTION TO SELECT THE EXECUTIVE
FEATURES AND PERIPHERAL DEVICES WE WANT IN THE NEW SYSTEM
Control is then passed to the SYSGEN query section beginning
with the indirect command file SGNEXEC.CMD.
The SYSGEN query section is run to produce the five files
mentioned previously. This process consists of a number of
interactive questions.
The answers you supply to these
queries provide SYSGEN with the information necessary to
construct its output files.
These files are then used by
MACRO-II and the Task Builder to create the user-tailored
system.
The question pertaining to production of the Executive map
should be answered Y,
since it is required in phase 2 of
SYSGEN to determine partition layout.
The Baseline System
therefore, spooling
specified.

does not contain a print spooler;
of the listings or map should not be

The SYSGEN query section presents queries which, when
answered, define Executive options, Processor options, and
the Peripheral set for the user-tailored system.
The query section consists of a series of questions which the user
answers.
At the completion of the query section,
the user has
specified all of the following:
1.

Executive options

Processor options

Peripheral set

This section contains every question (listed in order of appearance)
in the dialogue conducted by the query section. The dialogue itself
has two options, long and short. Short dialogue consists only of the
queries.
Long dialogue precedes each query with explanatory text.
In the text Which follows, upper case is produced by the query section
dialogue.
Any additional explanation required appears in lower case
and is indented for easy recognition.
EXPANDED COMMENTS RESULT IN THE DISPLAY OF EXPLANATORY TEXT
PRECEDING EACH QUERY. SHORT DIALOGUE OMITS THE TEXT. EXPANDED
COMMENTS ARE AVAILABLE ON A PER QUERY BASIS BY ENTERING ESCAPE
OR ALTMODE FOLLOWING THE DISPLAY OF THE QUERY.
* LONG DIALOGUE DESIRED FOR EXECUTIVE/PROCESSOR OPTIONS? [Y/N]:
3-15

SYSGEN DIALOGUE DETAILS

Once long dialogue is chosen, the explanatory text is
displayed prior to each Executive/processor query and cannot
be suppressed (except on a per query basis with CTRL/O).
Selective short dialogue produces explanatory text following
the query only when that query has been answered using
ALTMODE/ESCAPE.
SYSGEN PRODUCES INDIRECT FILES WHICH ARE SUBSEQUENTLY USED TO
ASSEMBLE THE USER-TAILORED EXECUTIVE. LISTING PRODUCTION IS
TIME CONSUMING AND IS NOT RECOMMENDED, ESPECIALLY IF THE 8K
ASSEMBLER IS BEING USED (WHICH IS REQUIRED ON A 16K SYSTEM).

* ASSEMBLY LISTING FILES DESIRED? [YIN]:
FOR THE SINGLE RK05, DUAL RK05 OR RLOl DISTRIBUTION KITS, RUNNING
STANDALONE, YOU MAY DIRECT THE EXECUTIVE LISTINGS TO THE LINE
PRINTER, OR ANOTHER DISK OF THE SAME TYPE AS YOUR KIT. NOTE THAT
THE LISTINGS WILL NOT FIT ON THE DISTRIBUTION DISKS FOR THE ABOVE.
FOR OTHER DISTRIBUTION KITS, YOU MAY SPECIFY A LINE PRINTER, THE
THE DISTRIBUTION KIT DISK (SYO) OR A SECOND DISK OF THE SAME TYPE.
FOR ALL ONLINE SYSGENS, YOU MAY SPECIFY ANY DISK WITH A LEAST
4000 FREE BLOCKS. NOTE THAT SYSGEN WILL NOT LOAD THE DRIVER FOR
THIS DISK.
The next two queries do not appear unless assembly
were requested.

listings

* WHAT IS TO BE THE LISTING DEVICE? [DDU]:
The listing files need not be directed to a line printer.
They can be directed to a terminal or a disk, e.g., TTO:
or
DK1:, subject to the above restrictions.
SPOOLING WILL ONLY ACTUALLY OCCUR FOR DIRECTORY DEVICES.
NOTE THAT THE BASELINE SYSTEM DOES NOT INCLUDE A PRINT SPOOLER.

* SPOOL LISTING FILES? [Y/N]:
The Baseline System does not have a
print
spooler.
Therefore,
if the SYSGEN is being performed on the Baseline
System, the user should select no spooling of either listing
files or map files.
A TASK BUILDER MAP IS STRONGLY RECOMMENDED. ESTABLISHING
PARTITIONS AND DIAGNOSING SYSTEM FAILURES REQUIRE THIS MAP.
FOR ALL DISTRIBUTION KITS. IT IS RECOMMENDED
THAT YOU SPECIFY SYO FOR THE MAP
DEVICE.

* TASK BUILDER MAP DESIRED? [Y/N]:
The only way to layout partitions for a target system is to
have the value of the last address used by the Executive.
This value can be obtained only from the Executive memory
allocation map. The next two queries do not appear unless a
map was requested.

* WHAT IS TO BE THE MAP DEVICE? [DDU]:
3-16

SYSGEN DIALOGUE DETAILS

* SPOOL MAP FILE? [YIN]:
SPOOLING WILL ONLY ACTUALLY OCCUR FOR DIRECTORY DEVICES.
NOTE THAT THE BASELINE SYSTEM DOES NOT INCLUDE A PRINT SPOOLER.
THE PRECEDING QUERIES DO NOT AFFECT THE USER-TAILORED
EXECUTIVE. THE EXECUTIVE OPTION QUERIES THAT FOLLOW WHICH ARE
PRECEDED BY A SINGLE ASTERISK ARE INCLUDED IN THE BASELINE
SYSTEM. THE FEATURE, HOWEVER, IS NOT ESSENTIAL TO THE
OPERATION OF A MINIMUM SYSTEM. DOUBLE ASTERISKED QUERIES MUST
BE SELECTED FOR FULL SUPPORT OF THE MINIMUM SYSTEM. QUERIES
WITH NO ASTERISKS ARE NOT IN THE MINIMUM SYSTEM AND ARE
OPTIONAL.
The indication of minimum system features
RSX-llM systems.

applies

only

iBEGIN EXECUTIVE SERVICE OPTIONS.

AS DISTRIBUTED, THE RSX-llM SOURCE DISK PROVIDES FOR THE
GENERATION OF AN RSX-llS EXECUTIVE.
IN ORDER TO GENERATE SUCH
A SYSTEM YOU MUST HAVE AN RSX-llS LICENSE AND CANNOT INCLUDE
FILES-II, CHECKPOINTING, NONRESIDENT TASK, OR DYNAMIC MEMORY
ALLOCATION SUPPORT.
* ARE YOU BUILDING AN RSX-llS SYSTEM? [YIN]:
The following question concerning terminal driver support
appears only if an RSX-llS system is being generated.
* DO YOU WANT TERMINAL DRIVER SUPPORT? [YIN]:
If an RSX-llS system is being generated, then the next
queries do not appear.

four

FAILURE TO INCLUDE THIS OPTION ELIMINATES ALL THE SERVICES
DESCRIBED IN THE RSX-ll 1/0 OPERATIONS REFERENCE MANUAL. SINCE
DEC SUPPLIED SOFTWARE MAKES USE OF THESE SERVICES, THEIR
ELIMINATION IS NOT RECOMMENDED.
* **DO YOU WANT FILES-II ACP SUPPORT? [YIN]:
THIS OPTION IS REQUIRED IF YOU WANT SUPPORT FOR RMS-ll.
* DO YOU WANT RMS RECORD LOCKING AND PLACEMENT CONTROL SUPPORT? [YIN]:
IF TASKS ARE TO BE DISPLACED FROM A PARTITION TO YIELD THE
PROCESSOR RESOURCES TO A TASK OF HIGHER PRIORITY ABLE TO USE
THE PARTITION, THEN CHECKPOINTING IS REQUIRED.
* **DO YOU WANT CHECKPOINTING? [YIN]:
For large systems, checkpointing may not be required if MCR,
TKN, and FCP each operate in a dedicated partition;
thus,
checkpointing may be omitted
(checkpointing is, however,
strongly recommended) ~
Note that,
in a minimum system,
these tasks must run in the same partition and,
therefore,
checkpointing is required.
If checkpointing is selected, then the following question is
asked, and the nonresident task query does not appear.

3-17

SYSGEN DIALOGUE DETAILS
SELECTION OF THIS OPTION ALLOWS CHECKPOINTING INTO A SYSTEM
CHECKPOINT FILE RATHER THAN REQUIRING SPACE IN EACH TASK.
If selected, system checkpoint files are allocated by an MCR
command.
The first checkpoint file allocated becomes the
primary file and so forth.
* DO YOU WANT DYNAMIC CHECKPOINT ALLOCATION?

[YIN]:

IF SELECTED, THE SYSTEM WILL CONTAIN A TASK LOADER. NOT
INCLUDING THIS LOADER MEANS TASKS MUST BE PERMANENTLY RESIDENT
IN THE GENERATED SYSTEM.
* **DO YOU WNAT NON-RESIDENT TASK SUPPORT? [YIN]:
REQUIRED IF THE USER-TAILORED SYSTEM HAS A
MEMORY MANAGEMENT UNIT FOR WHICH RSX-IIM/S SUPPORT IS DESIRED.
* ARE YOU BUILDING A MAPPED SYSTEM? [YIN]:
If you are not building
questions are omitted.

For unmapped systems, the
with address checking.

mapped
next

system,

questions

the

five

displayed

begin

*MAPPED*
THIS OPTION ALLOWS AS MANY TASKS AS WILL FIT IN A PARTITION TO
BE SIMULTANEOUSLY RESIDENT. THE ALLOCATION OF PARTITION MEMORY
IS AUTOMATIC AND IS CARRIED OUT DYNAMICALLY BY THE RSX-IIM
EXECUTIVE.

* DO YOU WANT DYNAMIC MEMORY ALLOCATION SUPPORT? [YIN]:
If dynamic memory allocation is selected, the next
is also asked.

question

AUTOMATIC MEMORY COMPACTION MINIMIZES THE EFFECTS OF
FRAGMENTATION IN DYNAMICALLY ALLOCATED PARTITIONS.
IT IS
INVOKED WHEN FREE SPACE EXISTS BETWEEN RESIDENT
NONCHECKPOINTABLE TASKS AND TASKS ARE WAITING TO BE LOADED
INTO THE PARTITION.
* DO YOU WANT AUTOMATIC MEMORY COMPACTION? [YIN]:
Memory compaction is implemented as a nonresident task
called the Shuffler.
Whenever it is necessary to compact
memory in a partition, the Shuffler is automatically loaded
and proceeds to checkpoint tasks and move them toward the
front of the partition in an attempt to provide better
memory utilization.
THE MEMORY MANAGEMENT DIRECTIVES PROVIDE TASKS WITH A PROTECTED
MECHANISM BY WHICH THEY CAN DYNAMICALLY CREATE AND DELETE
COMMON BLOCKS AND DYNAMICALLY MODIFY THEIR PHYSICAL ADDRESS
SPACE MAPPING.
* DO YOU WANT THE MEMORY MANAGEMENT DIRECTIVES? [YIN]:
The memory management directives are
mapped system.
If selected,
the
asked.

3-18

available only on a
next two questlons are

SYSGEN DIALOGUE DETAILS
THESE DIRECTIVES ALLOW ONE TASK TO SEND TO ANOTHER TASK A
REFERENCE TO AN AREA WITHIN A PARTITION. THE RECEIVER TASK IS
GIVEN A SPECIFIED ACCESS ALLOWING IT TO SUBSEQUENTLY MAP TO OR
DELETE THE PARTITION.
* DO YOU WANT THE SEND/RECEIVE BY REFERENCE DIRECTIVES? [Y/N]:
THIS DIRECTIVE ALLOWS A TASK TO OBTAIN A SNAPSHOT OF ITS
CURRENT VIRTUAL-TO-PHYSICAL ADDRESS SPACE MAPPING.
* DO YOU WANT THE GET MAPPING CONTEXT DIRECTIVE? [YIN]:
*UNMAPPED*
IF ADDRESS CHECKING IS INCLUDED, USER GENERATED ADDRESSES
PASSED IN EXECUTIVE DIRECTIVES WILL BE SUBJECT TO BOUNDARY,
ALIGNMENT, AND MODULUS CHECKS.
* DO YOU WANT ADDRESS CHECKING? [Y/N]:
This feature is automatically included if the target system
contains a memory management unit.
If memory management
support is included, this question is omitted.
I/O RUNDOWN INSURES THE INTEGRITY OF AN RSX-llM SYSTEM BY
MAKING SURE ALL OUTSTANDING TASK RELATED I/O OPERATIONS ARE
CLEANED UP BEFORE ALLOWING THE TASK TO EXIT. OMISSION OF THIS
FEATURE SHOULD BE CAREFULLY CONSIDERED.
* **DO YOU WANT I/O RUNDOWN? [Y/N]:
This feature is automatically included if the target system
contains a memory management unit.
If memory management
support is included, this question is omitted.
Processing continues here whether the system
unmapped.

mapped

*MAPPED AND UNMAPPED*
The following two options are available
systems,
they are not displayed if
RSX-llS system.

only with RSX-llM
you are building an

MULTI-USER PROTECTION PREVENTS ONE USER FROM INTEFERING WITH
THE OPERATION OF ANOTHER BY PROVIDING FOR PUBLIC AND PRIVATE
DEVICE OWNERSHIP AND LOGON/LOGOFF WITH PASSWORD PROTECTION.
SELECTION OF THIS FEATURE AUTOMATICALLY INCLUDES TERMINAL
DRIVER SUPPORT FOR READ WITH SPECIAL TERMINATOR, BREAKTHROUGH
WRITE, AND READ WITH NO ECHO.
* DO YOU WANT MULTI~USER PROTECTION SUPPORT? [Y/N]:
It is suggested that you have a mlnlmum of 32K
memory to select multi-user protection support.

words

SELECTION OF ANSI MAGTAPE SUPPORT PROVIDES VOLUME AND FILE
LABELING WHICH CONFORMS TO THE ANSI STANDARD FOR INDUSTRY
COMPATIBLE TAPE.
THIS OPTION REQUIRES EXECUTIVE AST SUPPORT.
* DO YOU WANT ANSI MAGTAPE ACP SUPPORT? [Y/N]:
The following options are available
RSX-llS systems.

3-19

for

both

RSX-llM

and

SYSGEN DIALOGUE DETAILS

USER MODE DIAGNOSTIC SUPPORT ENABLES THE EXECUTIVE AND DEVICE
DRIVERS TO SERVICE SPECIAL I/O FUNCTIONS AND RETURN ADDITIONAL
DEVICE STATUS INFORMATION AS REQUIRED BY ONLINE DIAGNOSTIC
TASKS.
* DO YOU WANT SUPPORT FOR ONLINE, USER MODE DIAGNOSTICS? [Y/N]:
LOADABLE DEVICE DRIVER SUPPORT ALLOWS MOST DEVICE DRIVERS TO BE
REMOVED FROM THE EXECUTIVE. THEY CAN BE LOADED AND UNLOADED
ALMOST AT WILL. AT THIS POINT ONLY THE PROCESS CONTROL DRIVERS
(UDC, ICS/ICR, AND DRS/DSS DRIVERS) AND THE VTll/VS60 GRAPHICS
DRIVER CAN NOT BE LOADABLE. LOADING OF THE TERMINAL DRIVER IS
RESERVED FOR VMR LOAD.
NOTE: LOADABLE DRIVER SUPPORT IN RSX-llS IS LIMITED TO VMR.
* *DO YOU WANT LOADABLE DEVICE DRIVER SUPPORT? [Y/N]:
AS DISTRIBUTED, THE RSX-llM SOURCE DISK PROVIDES FOR THE
GENERATION OF AN RSX-llM OR RSX-llS EXECUTIVE THAT CONTAINS
SUPPORT FOR NETWORK COMMUNICATIONS.
IN ORDER TO GENERATE SUCH
A SYSTEM YOU MUST HAVE THE APPROPRIATE NETWORK SOFTWARE
LICENSE.
* DO YOU WANT NETWORK ACP SUPPORT? [Y/N]:
If you select Network
questions are asked.

ACP

support,

the

following

two

the

following

* DO YOU WANT DECNET VERSION 2 SUPPORT? [Y/N]:
If you select DECNET Version 2 support,
displayed. Otherwise, it is omitted.

WITH THE ADDITION OF VERSION 2 DECNET SUPPORT IT IS NECESSARY
TO SPECIFY THE HIGHEST VECTOR ADDRESS IN THE SYSTEM SO THAT
ADEQUATE SPACE IS RESERVED FOR INTERRUPT VECTORS, SINCE V2
DECNET DEVICES WILL BE SPECIFIED DURING NETGEN RATHER THAN
SYSGEN.
* WHAT IS THE HIGHEST INTERRUPT VECTOR ADDRESS? [0 R: 300-774]:
* DO YOU WANT DECNET VERSION 1 SUPPORT? [Y/N]:
Network software provides the capability of simultaneously
operating tasks on different systems to establish logical
communication links, and to exchange data. If this option
is not selected, the next seven queries are omitted.
Users should not attempt to answer the network questions
without consulting the RSX-ll DECNET-ll Programmer's Guide
and Reference Manual.
If Network ACP support and DECNET version 1 support is
selected, the following ten questions, pertinent only to
network support, are asked.
If you do not select DECNET support, the next
displayed appears under the heading ALL SYSTEMS.
*NETWORK ACP SUPPORT ONLY*
SELECTION OF THIS OPTION PROVIDES SUPPORT FOR THE LOADING OF
TASKS FROM A MASS STORAGE DEVICE ON ANOTHER SYSTEM.

3-20

query

SYSGEN DIALOGUE DETAILS
* DO YOU WANT SUPPORT FOR REMOTE TASK LOADING? [Y/N]:
This question is asked only for RSX-llS
selected, the next question is also asked.

systems.

THIS OPTION ALLOWS TASKS THAT ARE REMOTELY LOADED TO BE
CHECKPOINTED BY HIGHER PRIORITY TASKS.
CHECKPOINT STORAGE
SPACE IS PROVIDED ON THE HOST MASS STORAGE DEVICE.
* DO YOU WANT REMOTE TASK CHECKPOINTING SUPPORT? [Y/N]:
Remote task checkpointing on slow communication links can be
a lengthy process.
Selection of this feature should be
given careful thought.
The following is displayed
Version 1 support.

only

you

selected

DECNET

IN AN RSX-llM SYSTEM THE NETWORK ACP MAY BE OVERLAID.
OVERLAYING CONSERVES APPROXIMATELY lK OF MEMORY AT THE COST OF
A SLIGHT DEGRADATION IN PERFORMANCE.
* SHOULD THE NETWORK ACP BE OVERLAID? [Y/N]:
The above question is asked only for RSX-llM systems.
network ACP cannot be overlaid in an RSX-llS system.

The

The following question is
generating a mapped system.

are

displayed

only

you

IN A MAPPED SYSTEM, THE NETWORK ACP CAN MAP OVER THE I/O PAGE.
THIS ALLOWS THE ACP TO HAVE AN EXTRA 4K OF BUFFERS, HOWEVER,
IT RESULTS IN A SLIGHT DEGRADATION OF SYSTEM I/O PERFORMANCE.
* SHOULD THE NETWORK ACP MAP OVER THE I/O PAGE? [Y/N]:
THIS HARDWARE OPTION PROVIDES EFFICIENT CALCULATION OF MESSAGE
BLOCK CHECK CHARACTERS.
* DOES THE TARGET SYSTEM HAVE A KGll CRC OPTION? [Y/N]:
This option cannot
actually present.

selected

unless

the

hardware

NETWORK MESSAGE TIMEOUT IS PROVIDED TO DETECT COMMUNICATION
LINK AND REMOTE SYSTEM FAILURES. TYPICAL. TIMES (IN SECONDS)
ARE ON THE ORDER OF TWICE THE LONGEST MESSAGE ROUND TRIP TIME.
* WHAT IS TIMEOUT PERIOD FOR NETWORK MESSAGES? [D R:3.-60.]:
TYPICAL NETWORK MESSAGE LENGTHS ARE SO. TO 12S. BYTES.
* WHAT IS THE MAX NETWORK MESSAGE SIZE IN BYTES? [D R:64.-52S.]:
THE COMMUNICATION BETWEEN TASKS IN A NETWORK IS VIA LOGICAL
CHANNELS. ONE LOGICAL CHANNEL IS REQUIRED FOR EACH PAIR OF
COMMUNICATING TASKS.
* HOW MANY CHANNELS CAN BE ACTIVE SIMULTANEOUSLY? [D R:l.-254.]:
*ALL SYSTEMS*
IF YOU INTEND TO USE THE K-SERIES LAB PERIPHERALS SUPPORT
ROUTINES, THE LPAll LAB. PERIPHERAL ACCELERATOR, THE PRINT

3-21

SYSGEN DIALOGUE DETAILS
SPOOLER, THE FORTRAN ISA PROCESS CONTROL SUBROUTINE CALLS,
ANSI MAGTAPE, OR UNSOLICITED TERMINAL AST' IS, THEN
ASYNCHRONOUS SYSTEM TRAP PROCESSING SUPPORT IS REQUIRED.
SEE THE EXECUTIVE REFERENCE MANUAL FOR A DETAILED DESCRIPTION
OF THE AST FACILITY PROVIDED IN RSX-llM/S.
* DO YOU WANT AST SUPPORT? [Y/N]:
AST support is included automatically if Floating Point
Processor, ANSI magtape, or network support is selected.
If
ANSI magtape or network support is selected,
this question
is omitted.
ABNORMAL TASK TERMINATION AND DEVICE NOT READY MESSAGES ARE
AUTOMATICALLY PRODUCED BY THE SYSTEM IF THIS OPTION IS
SELECTED. THIS OPTION IS REQUIRED IF PMD SUPPORT IS DESIRED.
* **DO YOU WANT TASK TERMINATION AND DEVICE NOT READY MESSAGES? [Y/N]:
If this option is included in an RSX-llM/S system, then the
Task Termination Notification Task
(TKN)
must also be
included in the system for
the messages to actually be
printed.
IF THE POWER FAILS AND THIS OPTION IS INCLUDED,
SYSTEM OPERATION IS
AUTOMATICALLY COMMENCED WHEN POWER IS RESTORED.
* DO YOU WANT POWERFAIL RECOVERY? [Y/N]:
REQUIRED IF DEC-SUPPLIED PROGRAM DEVELOPMENT SOFTWARE (I.E.,
TKB, MAC, ETC.) IS TO BE RUN.
* **00 YOU WANT GET PARTITION PARAMETERS DIRECTIVE? [Y/N]:
THIS DIRECTIVE PROVIDES THE CAPABILITY TO READ THE PROCESSOR
SWITCH REGISTER AND RETURN ITS CONTENTS TO THE REQUESTING TASK.
NOTE THAT SOME PROCESSORS DO NOT HAVE A CONSOLE SWITCH REGISTER
AND, THEREFORE, CANNOT SUPPORT THIS DIRECTIVE.
* DO YOU WANT GET SENSE SWITCHES DIRECTIVE? [Y/N]:
REQUIRED IF DEC-SUPPLIED PROGRAM DEVELOPMENT SOFTWARE (I.E.
TKB, MAC, ETC.) IS TO BE RUN.
* **DO YOU WANT GET TASK PARAMETERS DIRECTIVE? [Y/N]:
THESE DIRECTIVES PROVIDE THE CAPABILITY FOR CO-OPERATING TASKS
TO COMMUNICATE VIA SYSTEM MAINTAINED MESSAGE QUEUES.
IF THE
TARGET SYSTEM WILL CONTAIN THE PRINT SPOOLER, OR IF LPAll-K
POWERFAIL SUPPORT OR ANSI MAGTAPE SUPPORT IS DESIRED,
THIS OPTION MUST BE INCLUDED.
* DO YOU WANT SEND/RECEIVE DIRECTIVES? [Y/N]:
THIS DIRECTIVE ALLOWS A TASK TO ALTER ITS OWN OR ANOTHER TASK'S
PRIORITY AT EXECUTION TIME. ITS INCLUSION WILL ALSO ALLEVIATE
THE PROBLEMS WITH ABORTED, NON-RESIDENT TASKS.
* DO YOU WANT ALTER PRIORITY DIRECTIVE? [Y/N]:
THIS DIRECTIVE ALLOWS A TASK TO CONNECT AN INTERRUPT VECTOR
TO AN INTERRUPT SERVICE ROUTINE IN ITS OWN SPACE. IT IS REQUIRED
IF K-SERIES LABORATORY PERIPHERALS SUPPORT IS DESIRED.

3-22

SYSGEN DIALOGUE DETAILS

* DO YOU WANT CONNECT TO INTERRUPT VECTOR DIRECTIVE? [Y/N]:
If selected, you must specify the highest vector you plan to
use.
The following note and query is displayed only if the
connect to interrupt vector directive is selected.
NOTE: DUE TO AN EXECUTIVE RESTRICTION, YOU ARE
REQUIRED TO HAVE SUPPORT FOR LOADABLE DRIVERS
IF YOU DESIRE CONNECT TO INTERRUPT VECTOR
DIRECTIVE SUPPORT. THIS HAS BEEN SELECTED
AUTOMATICALLY.
SINCE THE VECTOR ADDRESSES OF DEVICES THAT WILL BE CONNECTED
WITH THIS FACILITY ARE NOT SPECIFIED DURING SYSGEN, YOU MUST
RESERVE SPACE FOR THEIR INTERRUPT VECTORS.

* WHAT IS THE HIGHEST INTERRUPT VECTOR ADDRESS? [0 R:300-774]:
THIS DIRECTIVE ALLOWS A TASK TO INCREASE ITS ADDRESS
SPACE AT EXECUTION TIME.

* DO YOU WANT EXTEND TASK DIRECTIVES? [YIN]:
This feature is only available on systems that include both
checkpointing
and
dynamic
memory allocation support;
otherwise, the question is omitted.
SELECTION OF THIS OPTION WILL SIGNIFICANTLY INCREASE SYSTEM I/O
THROUGHPUT AT THE EXPENSE OF ADDITIONAL EXECUTIVE CODE.

* DO YOU WANT QUEUE I/O SPEED OPTIMIZATIONS? [YIN]:
If Queue I/O speed optimizations are selected, the following
two questions are asked.
I/O THROUGHPUT IS ENCHANCED BY PRE-ALLOCATING A NUMBER OF I/O
PACKETS FROM THE POOL, LEAVING THEM AVAILABLE FOR QUICK USE BY
QUEUE I/O.

* HOW MANY I/O PACKETS SHOULD BE PRE-ALLOCATED? [D R:I.-15.]:
AN ADDITIONAL SPEED IMPROVEMENT IS ACHIEVED BY OPTIMIZING DATA
TRANSFERS IN THE EXECUTIVE MODULE 'BLXIO'. ONE IMPROVEMENT IS
THE USE OF A SERIES OF 'MOV' INSTRUCTIONS WHICH IS USED IN LIEU
OF A LOOP. THIS IS CALLED THE DATA TRANSFER VECTOR.

* ENTER SIZE OF DATA TRANSFER VECTOR IN WORDS

[D R:4.-33.]:

The next query is omitted if you are qenerating
system.

RSX-IIS

THIS FACILITY OF MCR CAN SUBSTANTIALLY REDUCE THE NUMBER OF
INSTALLED TASKS NEEDED FOR CONVENIENT SYSTEM OPERATION. SEE
DESCRIPTION OF THE RUN COMMAND IN THE RSX-IIM OPERATOR'S
PROCEDURES MANUAL FOR DETAILS.

* * DO YOU WANT INSTALL, REQUEST, AND REMOVE ON EXIT SUPPORT? [YIN]:
Support for this option is highly recommended if your system
has limited dynamic memory.
The install, request, and. remove
available with RSX-IIS systems.

3-23

exit

option

not

SYSGEN DIALOGUE DETAILS
LOGICAL DEVICE ASSIGNMENT PROVIDES THE CAPABILITY TO ASSOCIATE
A LOGICAL NAME TO A PHYSICAL DEVICE UNIT. ASSIGNMENTS MAY BE
MADE ON A PER TERMINAL OR SYSTEM WIDE BASIS.
* *DO YOU WANT LOGICAL DEVICE ASSIGNMENT SUPPORT? [YIN]:
THE NULL DEVICE WILL ALWAYS RETURN THE I/O STATUS FOR SUCCESSFUL COMPLETION FOR AN OUTPUT REQUEST AND END-OF-FILE FOR
AN INPUT REQUEST.
IT IS VERY USEFUL TO ASSIGN IT AS THE OUTPUT
DEVICE WHEN USING PRE-WRITTEN COMMAND FILES FOR WHICH CERTAIN
TYPES OF OUTPUT SHOULD BE SURPPRESSED. THE NULL DEVICE DRIVER
IS NOT LOADABLE
If you are generating an RSX-llS system without terminals or
without a disk, a null device is automatically included;
a
null device is generated whether selected or not.
* *DO YOU WANT A NULL DEVICE? [YIN]:
If you are generating an RSX-llS system and answered N to
terminal driver support, then the following terminal driver
questions are omitted.
* ALL SYSTEMS EXCEPT RSX-llS WITHOUT TERMINAL DRIVER SUPPORT*
THE BASELINE TERMINAL DRIVER SUPPLIES A BASIC HALF DUPLEX
CONNECTION TO TERMINALS INTERFACED BY A DLll, DHll/DMll-BB,
DJll, OR DZll. IT IS THE SMALLEST TERMINAL DRIVER.
* *DO YOU WANT THE BASELINE TERMINAL DRIVER? [YIN]:
If multi-user protection support was selected earlier,
then
baseline terminal support cannot be offered;
this query is
omitted.
If the baseline driver is selected, the next queries,
concern user oriented terminal drivers, are bypassed.
*USER ORIENTED TERMINAL DRIVERS*
THE USER ORIENTED TERMINAL DRIVER CONTAINS THOSE FEATURES FOUND
MOST DESIRABLE BY USERS ON A PROGRAM DEVELOPMENT SYSTEM. THE
FOLLOWING FEATURES ARE INCLUDED:
-

AUTOMATIC CARRIAGE RETURN/LINE FEED
BREAKTHROUGH WRITE
TASK CHECKPOINTING DURING TERMINAL INPUT (NEEDS EXEC SUPPORT)
UNSOLICITED INPUT CHARACTER AST (NEEDS EXEC SUPPORT)
WRITE WITH CONTROL-O CANCELLATION
CONTROL-R SUPPORT
GET TERMINAL CHARACTERISTICS
GET TERMINAL DRIVER SUPPORT
SETTABLE CASE CONVERSION
READ WITH NO ECHO
READ AFTER PROMPT
SPECIAL CHARACTER LINE TERMINATOR SUPPORT
CRT RUBOUT
TERMINAL-HOST SYNCHRONIZATION
TRANSPARENT TERMINAL READ/WRITE
VARIABLE LENGTH INPUT BUFFERING

IF MORE OR FEWER FEATURES ARE DESIRED, ANSWER NO.

3-24

which

SYSGEN DIALOGUE DETAILS

* DO YOU WANT THE USER ORIENTED TERMINAL DRIVER? [Y/N]:
THE TERMINAL DRIVER NORMALLY CONVERTS A FORM FEED INTO 8 LINE
FEEDS. CHOOSING THE NEXT OPTION WILL SUPPRESS THIS CONVERSION.
IF YOU HAVE AN LA120 OR LA180S, YOU MUST ANSWER YES TO THE NEXT
QUESTION.
* DO YOU WANT FORM FEEDS PASSED DIRECTLY TO TERMINALS? [Y/N]:
IF THE USER ORIENTED TERMINAL DRIVER IS SELECTED,
19 QUERIES ARE BYPASSED.

THE

*OPTIONS FOR A USER-TAILORED TERMINAL DRIVER*
WHEN THIS OPTION IS SELECTED, A CARRIAGE RETURN AND LINE FEED
WILL BE GENERATED WHENEVER THE TERMINAL BUFFER IS FILLED EITHER
ON OUTPUT OR ECHO. THE BUFFER SIZE MAY BE EXAMINED OR ALTERED
BY THE 'SET /BUF' MCR COMMAND.
.
* DO YOU WANT AUTOMATIC CARRIAGE RETURN/LINE FEED? [Y/N]:
The following query is omitted if checkpointing support
not included in the Executive.

was

SELECTION OF THIS OPTION ALLOWS CHECKPOINTABLE TASKS TO BE
DISPLACED FROM MEMORY DURING TERMINAL INPUT BY HIGHER PRIORITY
TASKS. THIS OPTION REQUIRES EXECUTIVE CHECKPOINTING SUPPORT.
* DO YOU WANT TASKS TO BE CHECKPOINTABLE DURING TERMINAL INPUT? [Y/N]:
The following query is omitted
included in the Executive.

AST

support

was

WHEN ATTACHING A TERMINAL, A TASK CAN SPECIFY AN AST ENTRY
POINT TO BE USED WHEN AN UNSOLICITED INPUT CHARACTER IS
RECEIVED. THIS OPTION REQUIRES EXECUTIVE AST SUPPORT.
* DO YOU WANT UNSOLICTED INPUT CHARACTER AST SUPPORT? [Y/N]:
A WRITE REQUEST ISSUED WITH CONTROL-O CANCELLATION WILL PRINT
TO THE TERMINAL REGARDLESS OF WHETHER OR NOT THE TERMINAL
OUTPUT HAS BEEN SUPPRESSED BY CONTROL-O.
* DO YOU WANT WRITE WITH CONTROL-O CANCELLATIONS? [Y/N]:
TYPING CONTROL-R DURING INPUT CAUSES THE TERMINAL DRIVER TO
SEND A CARRIAGE RETURN/LINE FEED FOLLOWED BY THE CONTENTS OF
THE INPUT BUFFER.
* DO YOU WANT CONTROL-R SUPPORT? [Y/N]:
ESCAPE SEQUENCES WILL BE RECOGNIZED AND TREATED AS LINE
TERMINATORS FOR SOLICITED INPUT WHICH IS NOT READ-PASS-ALL OR
READ-WITH-SPECIAL-TERMINATOR.
* DO YOU WANT ESCAPE SEQUENCE HANDLING? [Y/N]:
GET MULTIPLE (TERMINAL) CHARACTERISTICS ALLOWS A TASK TO
DETERMINE MANY OF THE PHYSICAL CHARACTERISTICS (E.G. CRT,
VT05, SLAVED, ETC) OF INDIVIDUAL TERMINALS.
* DO YOU WANT GET MULTIPLE CHARACTERISTICS SUPPORT? [Y/N]:
SET MULTIPLE (TERMINAL) CHARACTERISTICS ALLOWS A TASK TO SET

3-25

not

SYSGEN DIALo.GUE DETAILS
AND RESET MANY OF THE CHARACTERISTICS (E.G. CRT, VT05, ETC) OF
ITS TI: TERMINAL. A PRIVILEGED TASK MAY ALSO S'ET THECHARACTERISTICS OF OTHER TERMINALS IN THE SYSTEM.

* DO YOU WANT SET MULTIPLE (TERMINAL) CHARACTERISTICS SUPPORT? [Y/N]:
GET TERMINAL DRIVER SUPPORT ALLOWS A TASK TO DETERMINE WHICH OF
THE OPTIONAL FEATURES WERE CHOSEN FOR THE TERMINAL DRIVER AT
SYSTEM GENERATION.

* DO YOU WANT GET TERMINAL DRIVER SUPPORT? [YIN]:
HOLD-SCREEN SUPPORT ALLOWS TERMINALS (WITH SPECIAL HARDWARE) TO
BREAK STREAM OUTPUT INTO PAGES THAT FIT ON THE SCREEN.
ENTERING AN UNSOLICITED CONTROL-C WILL DISABLE HOLD-SCREEN
MODE. WHEN THIS OPTION IS SELECTED, SUPPORT FOR TRANSPARENT
READ/WRITE IS AUTOMATICALLY INCLUDED.

* DO YOU WANT HOLD-SCREEN MODE SUPPORT? [YIN]:
TERMINAL INPUT IS USUSALLY FILTERED ON BOTH INPUT AND OUTPUT.
THIS IS NECESSARY TO RECOGNIZE CONTROL CHARACTERS THAT HAVE
SPECIAL MEANING (I.E. ALTMODE OR ESC) OR REQUIRE FILL
CHARACTERS (I.E. CARRIAGE RETURN) . THIS OPTION PROVIDES
SUPPORT FOR I/O FUNCTIONS (IO.RAL AND IO.WAL) THAT BYPASS
CHARACTER FILTERING AND PERMITS OUTPUT OF UP TO 32K BYTES.

* DO YOU WANT TRANSPARENT TERMINAL READ/WRITE SUPPORT? [YIN]:
NORMALLY THE TERMINAL DRIVER ACCEPTS AND ECHOS CHARACTERS AS
RECEIVED.
SELECTION OF THIS OPTION PROVIDES THE CAPABILITY TO
SELECTIVELY ENABLE A TERMINAL SO THAT THE TERMINAL DRIVER WILL
AUTOMATICALLY CONVER'! ALL LOWER CASE INPUT TO UPPER CASE.
IT
ALSO ALLOWS THE RECOGNITION OF BRACE (175) AND TILDE (176) AS
ASCII CHARACTERS RATHER THAN A FORM OF ALTMODE IF THE TERMINAL
IS SET TO LOWER CASE.

* DO YOU WANT SETTABLE CASE CONVERSION FOR TERMINAL INPUT?

[YIN]:

A READ AFTER PROMPT REQUEST ACTS LIKE A WRITE TO THE TERMINAL
FOLLOWED BY A READ. HOWEVER, THE OVERHEAD OF ONE I/O REQUEST
AND CONTEXT SWITCHING IS ELIMINATED. IN ADDITION, THE
EXECUTION WINDOW IS REMOVED BY WHICH ONE TASK CAN PROMPT AND
ANOTHER TASK INITIATE I/O TO THE TERMINAL BEFORE THE FIRST HAD
TIME TO ISSUE ITS READ REQUEST, PROVIDED THE TERIMINAL WAS NOT
ATTACHED.

* DO YOU WANT READ AFTER PROMPT SUPPORT?

[Y/N]:

Multi-user
protection
support
includes
support
for
breakthrough write,
read with no echo, and read with a
special terminator. Therefore, if multi-user support was
selected, the following three questions are omitted.
A BREAKTHROUGH WRITE REQUEST ISSUED BY A PRIVILEGED TASK WILL
AUTOMATICALLY PRINT TO THE TERMINAL REGARDLESS OF ITS CURRENT
OUTSTANDING I/O ACTIVITY.

* DO YOU WANT BREAKTHROUGH WRITE SUPPORT? [Y/N]:
READ WITH NO ECHO SUPPORT ALLOWS THE READ FUNCTIONS (IO.RLB,
IO.RVB, AND IO.RPR) TO BE ISSUED SPECIFFYING THAT THE TERMINAL
INPUT SHOULD NOT BE ECHOED.

3-26

SYSGEN DIALOGUE DETAILS

* DO YOU WANT READ WITH NO ECHO SUPPORT? [YIN]:
THE LINE TERMINATORS FOR A NORMAL READ ARE ALTMODE OR CARRIAGE
RETURN. HOWEVER, ANY CHARACTER LESS THAN 40 OCTAL AND GREATER
THAN 174 OCTAL WILL TERMINATE A READ WITH SPECIAL TERMINATOR
REQUEST. ESCAPE SEQUENCES CANNOT BE RECOGNIZED IN THIS MODE.
IN ADDITION, IF THE TERMINAL HAS BEEN SET TO LOWER CASE, ONLY
177 OCTAL AND CHARACTERS LESS THAN 40 OCTAL ARE TERMINATORS.
* DO YOU WANT READ WITH SPECIAL TERMINATOR SUPPORT? [YIN]:
WHEN THIS OPTION IS INCLUDED, RUBOUTS ENTERED ON A CRT TERMINAL
WILL BE ECHOED AS BACKSPACE-SPACE-BACKSPACE (OR NUMBER THEREOF
FOR TABS). THIS HAS THE AFFECT OF ERASING THE CHARACTER FROM
THE SCREEN.
* DO YOU WANT CRT RUBOUT SUPPORT? [YIN]:
TERMINAL-HOST SYNCHRONIZATION ALLOWS OUTPUT TO BE TURNED OFF
(CNTRL-S) AND ON (CNTRL-Q) FROM A TERMINAL. THIS MAY BE USEFUL
FOR HIGH BAUD RATE DISPLAY TERMINALS AND IS REQUIRED IF THE
TARGET SYSTEM CONTAINS VT50 TERMINALS WITH THE COPIER OPTION.
* DO YOU WANT TERMINAL-HOST SYNCHRONIZATION SUPPORT? [YIN]:
NORMALLY, ALL RECEIVED CHARACTERS ARE STORED IN A BUFFER IN THE
EXECUTIVE ADDRESS SPACE UNTIL A TERMINATOR CHARACTER IS SEEN.
AT THAT TIME THE CONTENTS OF THE BUFFER ARE COPIED INTO THE
REQUESTING TASK'S INPUT BUFFER. SELECTION OF THIS OPTION WILL
PLACE THE INPUT CHARACTERS DIRECTLY INTO THE TASK BUFFER WHEN
THEY ARE RECEIVED, PROVIDED THE TASK IS NOT CHECKPOINTABLE.
* DO YOU WANT USER TERMINAL INPUT BUFFERING? [YIN]:
NORMALLY, ALL TERMINAL DRIVER INPUT BUFFERS ARE BO BYTES LONG.
THIS IMPLICITLY LIMITS THE SIZE OF THE MAXIMUM TERMINAL INPUT
REQUEST AS WELL AS THE SIZE OF THE MINIMUM BUFFER ALLOCATION
FROM DYNAMIC MEMORY. VARIABLE LENGTH BUFFERING ALLOCATES THE
BUFFERS JUST LARGE ENOUGH TO SATISFY THE READ REQUESTS. THE
LARGEST BUFFER MAY BE 255 BYTES LONG.
* DO YOU WANT VARIABLE LENGTH TERMINAL INPUT BUFFERING? [YIN]:
THE LA30P DECWRITER IS CONNECTED TO THE PDP-II VIA A SINGLE
BUFFERED INTERFACE. THEREFORE, THE SECOND OF TWO QUICKLY TYPED
CHARACTERS MAY BE DISCARDED BY THE TERMINAL DRIVER UNLESS THIS
OPTION IS SELECTED. ALL OTHER COMBINATIONS OF DEC TERMINALS
AND INTERFACES ARE PROPERLY SUPPORTED BY THE TERMINAL DRIVER.
THIS OPTION SHOULD BE CHOSEN ONLY IF YOU HAVE AN LA30P
TERMINAL.
* DO YOU WANT LA30P SUPPORT? [YIN]:
**ALL SYSTEMS**
IT IS POSSIBLE TO GENERATE AN EXECUTIVE LARGER THAN 16K TO
INCREASE THE SIZE OF THE EXECUTIVE DYNAMIC STORAGE REGION.
DOING THIS WILL REDUCE THE SIZE OF PRIVILEGED TASKS WHICH MAP
INTO THE EXECUTIVE TO BK.
* DO YOU WANT SUPPORT FOR A 20K EXECUTIVE? [YIN]:
ROUND ROBIN SCHEDULING PROVIDES THE CAPABILITY FOR A GROUP

3-27

SYSGEN DIALOGUE DETAILS

OF TASKS WITHIN A RANGE OF PRIORITIES TO SHARE THE AVAILABLE
PROCESSING TIME. EACH PRIORITY CLASS WITHIN THE RANGE IS ROUND
ROBIN SCHEDULED AT EACH SCHEDULE INTERVAL (TIME SLICE).

* DO YOU WANT EXECUTIVE LEVEL ROUND ROBIN SCHEDULING? [Y!N]:
Round-robin scheduling refers to the algorithm whereby each
task of a qroup of tasks is successively given preference in
allocating available processor time. The actual algorithm
used in RSX-llM is to locate the first task within each
priority class that is not blocked from executing, and to
move that task to the end of its respective priority class.
Compute-bound tasks tend to actually round robin, whereas
I/O-bound tasks tend to remain at the front of their
respective priority class.
If Executive level round-robin scheduling is selected, you
must specify a scheduling interval and the range of priority
classes to be considered. Therefore, the following three
questions are asked.
If not selected, the next three questions are omitted.
ROUND ROBIN SCHEDULING IS EXECUTED ON A PERIODIC BASIS.
A TYPICAL SCHEDULING INTERVAL IS ON THE ORDER OF 100
MILLISECONDS (6 .CLOCK TICKS FOR A 60 CYCLE LINE FREQUENCY
CLOCK) •

* ENTER LENGTH OF SCHEDULE INTERVAL IN TICKS [0 R:l.-lOOO. 0:6]:
ROUND ROBIN SCHEDULING IS EXECUTED FOR A RANGE OF PRIORITY
CLASSES. TYPICAL RANGES ARE 1. TO 100.

* ENTER HIGHEST PRIOR. CLASS TO BE CONSIDERED
* ENTER LOWEST PRIOR. CLASS TO BE CONSIDERED

[0 R:l.-249.]:

[0 R:l.-x]:

Note that x above is the value of the previous answer.
To Round-Robin schedule a system that is executing multiple
copies of the MCR indirect command processor (AT.), the
response to the above question must be 1.
The following option is not available on systems that do not
include
checkpointing.
Therefore,
if
you have not
previously selected
checkpointing,
the
next
queries
concerning disk swapping are omitted.
THE DISK SWAPPING ALGORITHM PROVIDES FOR THE VARIATION OF A
RESIDENT TASK'S EFFECTIVE PRIORITY WHEN IT IS BEING CONSIDERED
FOR CHECKPOINTING. A TASK'S EFFECTIVE PRIORITY IS DETERMINED
BY BIASING ITS RUN PRIORITY WITH A POSITIVE SWAPPING PRIORITY
EACH TIME IT IS LOADED INTO MEMORY (E.G., INITIAL TASK LOAD OR
CHECKPOINT READ). AS THE TASK CONTINUES TO RESIDE IN MEMORY,
ITS SWAPPING PRIORITY BECOMES NEGATIVE, EVENTUALLY REACHING A
LOWER BOUND; IT IS THIS BIAS WHICH IS USED TO DETERMINE
EFFECTIVE PRIORITY. EVENTUALLY, THE TASK BECOMES ELIGIBLE FOR
CHECKPOINTING BY TASKS OF EQUAL PRIORITY WHICH ARE NOT RESIDENT
(OR BY LOWER PRIORITY TASKS WITHIN THE SPECIFIED RANGE) •

* DO YOU WANT EXECUTIVE LEVEL DISK SWAPPING? [YIN]:
If this option is not selected, the
omitted.

3-28

two

queries

are

SYSGEN DIALOGUE DETAILS
SWAPPING PRIORITIES ARE DECREMENTED ON A PERIODIC BASIS. A
TYPICAL TIME INTERVAL IS ON THE ORDER OF 500 MILLISECONDS (30
CLOCK TICKS FOR A 60 CYCLE FREQUENCY CLOCK). TYPICALLY, THE
SWAPPING INTERVAL SHOULD BE AT LEAST 5 TIMES THE ROUND ROBIN
SCHEDULING INTERVAL.

* ENTER LENGTH OF SWAPPING INTERVAL IN TICKS [D R:I.-5000.

D:5.]:

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. THE SWAPPING
PRIORITY DETERMINES THE RANGE OVER WHICH LOWER PRIORITY TASKS
MAY CHECKPOINT HIGHER ONES: THE LARGER THE SWAPPING PRIORITY,
THE GREATER THE RANGE.
A TYPICAL VALUE FOR THIS PARAMETER IS 5.

* WHAT IS THE SWAPPING PRIORITY?

[D R:I.-20.

D:5.]:

ADDITION OF A USER WRITTEN DRIVER REQUIRES THAT ADEQUATE SPACE
BE ALLOCATED FOR INTERRUPT VECTORS DURING THE ASSEMBLY OF THE
GENERATED EXECUTIVE. ACTUAL DRIVER INCLUSION OCCURS WHEN THE
TARGET EXECUTIVE IS BUILT.

* ARE YOU PLANNING TO INCLUDE A USER WRITTEN DRIVER?

[Y/N]:

If a user-written driver is not being incorporated, the next
three queries are omitted.

* WHAT IS THE HIGHEST INTERRUPT VECTOR ADDRESS?

[0 R:

x-774]:

The low range for the highest interrupt vector address x is
either 300 or the value that was specified in the response
to the query concerning the highest interrupt vector you
plan to use. If your response is greater than the low range
argument, the highest interrupt vector address is then
increa~ed.
This is done to prevent the Executive stack from
overwriting the vector addresses
(including the vector
addresses needed for user-written drivers) .
THE EXECUTIVE ROUTINES $GTWRD AND $PTWRD ARE USED BY DRIVERS TO
TRANSFER A WORD FROM (OR TO) A USER SPECIFIED BUFFER. THEIR
INCLUSION IS OPTIONAL SINCE ONLY ONE OR TWO OF THE DEC SUPPLIED
DRIVERS USE THEM.

* DO YOU REQUIRE THE EXECUTIVE ROUTINE $GTWRD? [Y/N]:
* DO YOU REQUIRE THE EXECUTIVE ROUTINE $PTWRD? [Y/N]:
THE EXECUTIVE DEBUGGING TOOL PROVIDES A SUBSET ODT-II THAT RUNS
AS A PART OF THE RSX-IIM EXECUTIVE. THIS TOOL ALLOWS
INTERACTIVE DEBUGGING OF EXECUTIVE MODULES, I/O DRIVERS, AND
INTERRUPT SERVI~E ROUTINES. SELECTION OF THIS OPTION ALSO
INCLUDES CONSISTENCY CHECK CODE IN THE DYNAMIC MEMORY ROUTINES.

* DO YOU WANT TO INCLUDE THE EXECUTIVE DEBUGGING TOOL? [Y/N]:
See the RSX-IIM Guide to Writing an I/O Driver for a
description of XDT. At the expense of additional overhead
code in the Executive module CORAL, selection of this option
also includes consistency checking when deallocating dynamic
memory. Since errors in deal location (via I/O done, etc.)
are common causes of system crashes, the overhead in a
system debugging situation may be justified.

3-29

SYSGEN DIALOGUE DETAILS
IF THE SYSTEM CRASHES AND THIS OPTION IS INCLUDED, THE
EXECUTIVE STACK AND REGISTERS WILL BE DUMPED TO THE SELECTED
DEVICE.

* DO YOU WANT REGISTER AND STACK DUMP AT SYSTEM CRASH? [YIN]:
If this option is selected, you are required to specify the
CSR address of the device. Thus, the following question is
asked.
If you do not select this option, the Executive stack and
registers are not dumped upon a system crash. The following
question is not displayed.
T~E DEVICE ON WHICH THE STACK AND REGISTER DUMP APPEARS
MUST BE A TERMINAL OR LINE PRINTER COMPATIBLE DEVICE; THAT
IS, IT MUST RECEIVE A SINGLE BYTE AT A TIME. THE NORMAL
DEVICE IS THE CONSOLE TERMINAL WHICH HAS A CSR ADDRESS OF
177564.

* ENTER DUMP DEVICE CSR ADDRESS [0 R:160000-177700 0:177564]:
SELECTION OF THIS OPTION INCLUDES CODE TO DUMP MEMORY TO
SECONDARY STORAGE FOR LATER ANALYSIS BY THE CRASH DUMP
ANALYSIS PROGRAM. THE CRASH DUMP DEVICES SUPPORTED ARE:
DT, DK, MT, AND MM.

* DO YOU WANT CRASH DUMP ANALYSIS SUPPORT? [YIN]:
If this option is selected, you must specify the CSR address
of the output device, the device mnemonic on which memory is
to be dumped, its CSR address, and the physical unit number.
Thus, the following four questions are asked.
If not selected, the next four quesitons are not displayed.
THE DEVICE ON WHICH THE CRASH NOTIFICATION APPEARS MUST BE A
PAPER TAPE, TELETYPE, OR LINE PRINTER COMPATIBLE DEVICE; THAT
IS, THE DEVICE MUST RECEIVE A SINGLE BYTE AT A TIME. THE
NORMAL CRASH OUTPUT DEVICE IS THE CONSOLE TERMINAL WHICH HAS A
CSR ADDRESS OF 177564.
IN RESPONSE TO THE NEXT QUESTION, ENTER THE CSR ADDRESS OF THE
DEVICE ON WHICH THE CRASH NOTIFICATION IS TO APPEAR.

* ENTER OUTPUT DEVICE CSR ADDRESS [0 R: 160000-177700 D:177564]:
MEMORY CAN BE DUMPED ONTO ANY OF THE FOLLOWING DEVICES:
DT, DK, MT, MM

* ENTER CRASH MEMORY DUMP DEVICE MNEMONIC? [S]:
In the next query, it is assumed that DT was entered as
memory dump device.

* WHAT IS ITS CSR ADDRESS?

[0 R:

the

160000-177700 0:177342]:

Since it was assumed that DT was the memory dump device, the
default argument for the CSR address is 177342. Note that
in an actual SYSGEN, the default argument is the standard
CSR address of your memory dump device.

3-30

SYSGEN DIALOGUE DETAILS

* WHAT IS THE PHYSICAL UNIT NUMBER OF CRASH UNIT?

[0 R:

0-7 D:O]:

The panic dump routine is not available if crash dump
analysis support was selected. Therefore, if you selected
crash dump analysis support,
the following questions are
omitted.
SELECTION OF THIS OPTION INCLUDES CODE TO DUMP SELECTED
PORTIONS OF MEMORY TO A HARD COpy DEVICE. THE DEVICE MUST
RECEIVE A BYTE AT A TIME (I.E. A TERMINAL OR LINE PRINTER).
THE DEFAULT DEVICE IS THE LINE PRINTER.

* DO YOU WANT THE PANIC DUMP ROUTINE?

[YIN]:

If this option is omitted and a system failure should occur,
it may not be possible for the user to capture vital data on
the state of the system at failure time.
The panic dump routine is normally used in debugging new
drivers or privileged tasks.
It provides a means of
generating a formatted dump of memory on a line printer or a
terminal.
If the dump routine query is not selected, then
the next two queries will not appear.

* ENTER THE DUMP DEVICE CSR ADDR? [0 R: 160000-177700 D:177514]:
The device that the formatted dump appears must be a paper
tape,
terminal, or line printer compatible device;
the
device must transmit a single byte at a time.
The normal
crash dump device is a line printer (CSR address 177514).
IF YOUR PROCESSOR DOES NOT HAVE A CONSOLE SWITCH REGISTER, THE
PANIC DUMP ROUTINE MUST INPUT ITS DUMP ADDRESS LIMITS FROM
LOCATION ZERO RATHER THAN FROM THE CONSOLE SWITCHES.

* DOES YOUR PROCESSOR HAVE A CONSOLE SWITCH REGISTER?

[Y/N]:

Error logging is not available on an
following is not displayed.

RSX-IIS

system;

the

The error logging queries are
generating an RSX-IIM system.

displayed

are

only

you

SELECTION OF ERROR LOGGING WILL CAUSE DISK AND TAPE DEVICE
ERRORS TO BE INTERCEPTED AND INFORMATION CONCERNING THEM TO BE
WRITTEN INTO A DISK FILE FOR LATER ANALYSIS. NOTE THAT THIS
OPTION AUTOMATICALLY INCLUDES SUPPORT FOR CHECKPOINTING AND THE
SEND/RECEIVE DIRECTIVES.

* DO YOU WANT DEVICE ERRORS AND TIMEOUTS LOGGED?

[Y/N]:

SELECTION OF THIS OPTION ALLOWS THE EXECUTIVE TO DETECT THE
OCCURRENCE OF TRAPS TO UNUSED INTERRUPT VECTORS AND TO STORE
INFORMATION ABOUT THEM IN A FILE FOR LATER ANALYSIS. INCLUDING
THIS OPTION ALSO REQUIRES SUPPORT FOR SEND/RECEIVE DIRECTIVES
AND CHECKPOINTING.

* DO YOU WANT UNDEFINED INTERRUPTS LOGGED? [YIN]:
SELECTION OF THIS OPTION WILL CAUSE CACHE AND MEMORY PARITY
ERROR TRAPS FROM USER TASKS TO BE INTERCEPTED WITH INFORMATION
CONCERNING THEM TO BE WRITTEN INTO A FILE FOR LATER ANALYSIS.
NOTE THAT THIS OPTION ALSO INCLUDES SUPPORT FOR PARITY MEMORY,
CHECKPOINTING, AND THE SEND/RECEIVE DIRECTIVES.

3-31

SYSGEN DIALOGUE DETAILS

* DO YOU WANT PARITY ERROR TRAPS LOGGED? [YIN]:
A NON ZERO RESPONSE TO THIS QUERY IS REQUIRED. A MINIMUM OF
256 WORDS WILL BE ACCEPTED TO INSURE MINIMUM OPERATIONS. 1024
WORDS IS A REASONABLE ESTIMATE FOR ADEQUATE PERFORMANCE OF A
SET OF USER TASKS MAKING FULL USE OF THE BASELINE SYSTEM.
RESPONSE LIMITS: 256.-16384. MINUS SIZE OF EXECUTIVE
* **ENTER SIZE OF DYN. STORAGE REGION IN WORDS (D R: 256.-16384.]:
The amount of dynamic memory needed depends
on
the
configuration of the machine and the number of tasks
installed. See Appendix B for a complete description. Keep
in mind that it is advisable to answer this question
conservatively. This will ensure that the size of your
executive will not exceed pre-established size goals. Once
the Executive is built, additional pool may be allocated
when configuring the system with VMR.
IF SELECTED, THE SYSTEM WILL, WHEN IDLE, CAUSE THE DATA LIGHTS
TO FLICKER IN A PRONOUNCED CIRCULAR ROTATION. THE OPTION
FUNCTIONS PROPERLY ONLY ON PDP-ll/45/50/55/70 SYSTEMS.
* DO YOU WANT ROTATING PATTERN IN DATA LIGHTS? [YIN]:
END EXECUTIVE SERVICE OPTIONS.
BEGIN PROCESSOR OPTIONS.
THE PDP-ll/70 REQUIRES ADDITIONAL EXECUTIVE SUPPORT IF YOU
WISH TO UTILIZE MEMORY ABOVE 124K.
* IS YOUR TARGET PROCESSOR A PDP-ll/70? [Y/N]:
THE MINIMUM MEMORY IS 16K FOR AN RSX-IIM SYSTEM AND 8K FOR AN
RSX-IIS SYSTEM. THE MAXIMUM MEMORY SIZE IS 1920K FOR AN
RSX-IIM SYSTEM AND 124K FOR AN RSX-IIS SYSTEM. IN ORDER TO
UTILIZE MEMORY ABOVE 28K THE TARGET SYSTEM MUST CONTAIN A
MEMORY MANAGEMENT UNIT.
If your target processor is not an 11/70, the high value for
the range argument is 124K.
If it is an 11/70, the high value is 1920K.
Regardless of the target processor, if you have not selected
memory management, the maximum size of physical memory is
28K.
In the next question, it is assumed that the processor is an
11/70, the memory management option was selected, and an
RSX-IIM system is being qenerated.
* ENTER SIZE OF PHYS.

MEMORY IN 1024 WORD BLOCKS [D R:

16.-1920.]:

Note that the range argument is dependent upon whether or
not the target processor is an 11/70, memory management was
selected, and an RSX-IIM system is being generated.
If you do not have memory management and/or specified a size
for physical memory less than 124K (a target processor other
than an 11/70), the next two questions are asked.

3-32

SYSGEN DIALOGUE DETAILS
If you have memory management, the following two questions
are omitted;
the next question asked concerns floating
point support.
RSX-IIM/S IS CAPABLE OF RUNNING ON ALL PDP-II PROCESSORS. THE
LSI-II IS THE SMALLEST MEMBER OF THE PDP-II FAMILY OF
PROCESSORS AND IS CONSTRUCTED USING LARGE SCALE INTEGRATED
CIRCUIT TECHNOLOGY. THE PDP-ll/03 IS THE PACKAGED VERSION OF
THE LSI-II PROCESSOR.

* IS THE TARGET PROCESSOR AN LSI-II OR PDP-II/03? [YIN]:
If this query is answered affirmatively, the next question
asked concerns FIS support; EAE and floating point support
are not available on an LSI-II or PDP-II/03.
THE EXTENDED ARITHMETIC ELEMENT (EAE) (KEII-A/B) IS AN OPTION
WHICH PERFORMS MULTIPLICATION, DIVISION, MULTIPLE POSITION
SHIFTS AND NORMALIZATION SIGNIFICANTLY FASTER THAN SOFTWARE
ROUTINES. IT CONNECTS DIRECTLY TO THE UNIBUS AND IS PROGRAMMED
AS A PERIPHERAL, ALLOWING OVERLAP BETWEEN CPU AND EAE
OPERATIONS.

* DO YOU WANT EAE SUPPORT? [YIN]:
If answered affirmatively, the next query is omitted.
The following question is
memory management support.

asked

the

system

contains

It is also asked if EAE support was not selected.
THE PDP-II FLOATING POINT PROCESSOR IS AN OPTIONAL ARITHMETIC
PROCESSOR. IT PERFORMS ALL FLOATING POINT ARITHMETIC
OPERATIONS AND CONVERTS DATA BETWEEN INTEGER AND FLOATING POINT
FORMATS. THIS OPTION IS AVAILABLE ON THE PDP 11/34/45/50/55,
60 AND 70. THIS SHOULD NOT BE CONFUSED WITH THE FIS
(FLOATING INSTRUCTION SET) OPTION AVAILABLE WITH THE PDPIl/40.

* DO YOU WANT FLOATING POINT PROCESSOR SUPPORT? [Y/N]:
If you answer affirmatively the FIS query is omitted.
THE FIS OPTION (WHICH REQUIRES THE EIS OPTION) INCLUDES
HARDWARE FLOATING POINT ADD, SUBTRACT, MULTIPLY, AND DIVIDE
INSTRUCTIONS.

* DO YOU WANT FIS SUPPORT? [YIN]:
The following query, and
the
associated
number
of
interrupts, is omitted if the target processor is an LSI-II.
RSX-IIM/S REQUIRES A REAL-TIME CLOCK FOR ITS OPERATION. EITHER
THE KWII-P PROGRAMMABLE FREQUENCY CLOCK OR KWII-L LINE
FREQUENCY CLOCK OR THE DLII-W LINE FREQUENCY CLOCK/CONSOLE
INTERFACE MAY BE USED.

* DO YOU HAVE A PROGRAMMABLE CLOCK? [Y/N]:
If the answer is affirmative, the next question is asked.
THE NUMBER OF INTERRUPTS SPECIFIED MUST BE EVENLY DIVISIBLE
INTO 10000(10).

3-33

SYSGEN DIALOGUE DETAILS

* WHAT IS THE NUMBER OF INTERRUPTS PER SECOND? [D R: 1.-1000.]:
Specifying the number of clock interrupts to be greater than
100.
per seeond should be considered carefully, because it
adds significant system overhead.
LINE FREQUENCY IS EITHER 50 OR 60 HERTZ. IN THE U.S.A. LINE
FREQUENCY IS ALWAYS 60 HERTZ.

* IS YOUR LINE FREQUENCY 50 HERTZ?

[YIN]:

THE KWII-Y IS A WATCHDOG TIMER THAT IS CONSTANTLY ATTEMPTING TO
TIME OUT SYSTEM ACTIVITY. THE RSX-IIM/S EXECUTIVE REFRESHES
THE TIMER AT EVERY CLOCK INTERRUPT. IF THE SYSTEM FAULTS OR A
HARDWARE FAILURE OCCURS AND THE TIMER ELAPSES AN EXTERNAL
SIGNAL IS GENERATED.

* DO YOU WANT KWII-Y WATCHDOG TIMER SUPPORT? [YIN]:
If this option is selected, the generated system will only
run on configurations that contain a KWII-Y. An attempt to
boot such a system on a configuration not having the KWII-Y
will result in an immediate system crash.
PARITY MEMORY PROVIDES CIRCUITRY TO CHECK THE INTEGRITY OF
STORED DATA. PARITY CHECKING BITS ARE GENERATED WHEN DATA
WORDS ARE WRITTEN INTO MEMORY AND CHECKED WHEN THE DATA WORDS
ARE SUBSEQUENTLY READ OUT OF MEMORY.

* DO YOU WANT PARITY MEMORY SUPPORT?

[YIN]:

If error logging of parity errors was selected earlier, this
option has been included already;
the question is omitted.
The parity memory option provides the system with detection
of errors in the memory system.
If this query is answered
affirmatively, the next question is asked.
However, if it is known already that the target processor is
a PDP-11/70 (by specifying physical memory greater than 124K
earlier), then the following query is omitted.
THE PDP-11/70 PROVIDES ADDITIONAL PARITY CHECKING CIRCUITRY.
THE BUFFER MEMORY (CACHE) USED TO SPEED UP MAIN MEMORY
OPERATIONS IS ALSO CAPABLE OF GENERATING AND CHECKING PARITY.

* DOES THE TARGET PROCESSOR HAVE A CACHE MEMORY? [YIN]:
END PROCESSOR OPTIONS
BEGIN PERIPHERAL OPTIONS
Selection of a peripheral option (nonzero response to the
query) will require the user to enter information concerning
the device.
This information pertains to the device's
vector and CSR addresses and, if loadable driver support has
been selected, whether or not the driver is to be loadable.
If the reply to the query for the number of the specific
peripherals that are in your system is greater than one, the
vector address query is repeated. The second and subsequent
displays require an interrupt vector.

3-34

SYSGEN DIALOGUE DETAILS
The CSR query appears as many times as the number of
peripheral's specified.
Note that the queries for the
interrupt vector and CSR occur one after the other for each
peripheral. The repeat sequence repeats both queries.

* EXPANDED COMMENTS DESIRED FOR PERIPHERAL OPTIONS? [YIN]:
Once long dialogue is chosen,
the explanatory text is
displayed prior
to each peripheral option query and cannot
be suppressed (except on a per query basis with CTRL/O).
Selective short dialogue produces explanatory text following
the query only when that query has been answered using
ALTMODE/ESCAPE.
It is assumed that expanded comments were selected.
If loadable driver support was selected, you have the option
of designating drivers as loadable or resident.
For each
device to be included in the system
(except ICS/ICR,
UDC,
DRS/DSS, and VTll/VS60), a loadable driver question is
asked. Answer Y for loadable drivers, and N or a carriage
return for resident drivers.
WRITECHECK INCREASES THE DATA RELIABILITY OF DISKS AT THE
COST OF' A DEGRADATION IN DISK THROUGHPUT. WRITECHECK, IF
SELECTED, MAY BE ENABLED/DISABLED DYNAMICALLY ON A PER DRIVE
BASIS VIA THE MCR SET COMMAND.
WRITECHECK IS CURRENTLY SUPPORTED FOR ALL DISKS EXCEPT THE RLOI
AND RXOI.
DO YOU WANT DISK WRITECHECK SUPPORT? [YIN]:
write check is the process where the driver performs a read
after each write.
If the data canot be read or does not
match the data written, the data is rewritten and another
read attempt is performed.
PROCESS I/O AND LABORATORY PERIPHERALS CONSIST OF THE FOLLOWING:
-

ADOI-D MULTICHANNEL ANALOG DATA ACQUISITION OPTION
AFCII DIFFERENTIAL ANALOG INPUT SUBSYSTEM
ARII LABORATORY PERIPHERAL SYSTEM
LPAII LABORATORY PERIPHERAL ACCELERATOR SUBSYSTEM
LPSII LABORATORY PERIPHERAL SYSTEM
ICSIl/ICRll INDUSTRIAL CONTROL SUBSYSTEMS
UDCII UNIVERSAL DIGITAL CONTROLLER
DRS/DSS DIGITAL I/O MODULES

* DO YOU HAVE ANY PROCESS I/O OR LABORATORY PERIPHERALS?

[YIN]:

Note that because K-series peripheral support does not
require a device driver, they are not included in the above
list.
If you answer Y to this question, the following queries
concerning the above process I/O peripherals are asked.
If
you do not have any process I/O peripherals, skip this
section and continue reading from the CM/CRII card reader
section (under the heading ALL SYSTEMS).
Ifloadable driver support was selected, you have the option
of designating drivers as loadable or resident.
For each
device to be included in the system
(except ICS/ICR,
UDC,

3-35

SYSGEN DIALOGUE DETAILS

DRS/DSS, and VTll/VS60), a 10adable driver
asked. Answer Y for loadable drivers, and N or
return for resident drivers.

question is
a carriage

Selection of a peripheral option (nonzero response to the
query) will require the user to enter information concerning
the device.
This information pertains to the device1s
vector and CSR addresses and, if loadable driver support has
been selected, whether or not the driver is to be loadable.
If the reply to the query for the number of the specific
peripherals that are in your system is greater than one, the
vector address query is repeated. The second and subsequent
displays require an interrupt vector.
The CSR query appears as many times as the number of
peripherals specified.
Note that the queries for the
interrupt vector and CSR occur one after the other for each
peripheral. The repeat sequence repeats both queries.
**PROCESS I/O AND LAB PERIPHERALS**
THE ADOI-D IS A MULTICHANNEL ANALOG DATA ACQUISITION OPTION
WHICH INTERFACES DIRECTLY TOPDP-ll COMPUTERS.
THE STANDARD AD01-D CONSISTS OF AN EXPANDABLE SOLID-STATE INPUT
MULTIPLEXER, PROGRAMMABLE INPUT RANGE SELECTOR, AID CONVERTER,
CONTROL, AND BUS INTERFACE. THE MULTIPLEXER CAN BE EXPANDED BY
; ADDING 4-CHANNEL MODULES UP TO 32 CHANNELS. AN EXPANSION
MULTIPLEXER MAY BE ADDED TO PROVIDE A MAXIMUM CONFIGURATION OF
64 CHANNELS.
* HOW MANY AD01-D AID CONVERTERS DO YOU HAVE? [D R: 0.-16.]:
* ENTER CSR ADDR. OF THE NEXT ADOl [0 R: 160000-177700 DL176770]:

* HOW MANY AID CHANNELS DOES IT HAVE? [D R:l.-64.]:
This query appears as many times as the number of AD01-Ds
specified.
Note that the queries for the CSR, and the
number of channels occur one after the other for each
ADOI-D. The repeat sequence repeats both of the queries.
; THE AFCl1 IS A DIFFERENTIAL ANALOG INPUT SUBSYSTEM FOR
; IDACS-11 INDUSTRIAL CONTROL SYSTEMS. THE AFCll SYSTEM
MULTIPLEXES UP TO 1024 DIFFERENTIAL INPUT ANALOG SIGNALS,
SELECTS GAIN, AND PERFORMS A l3-BITANALOG-TO-DIGITAL
CONVERSION AT A 200 CHANNEL PER SECOND RATE UNDER PROGRAM
CONTROL.

* HOW MANY AFCll AID CONVERTERS DO YOU HAVE? [0 R: 0.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:

* ENTER VECTOR ADDRESS OF THE NEXT AFCll? [0 R: 60-774 D:134]:
* WHAT IS ITS CSR ADDRESS? IO R: 160000-177700 D:172570]:
* HOW MANY AID CHANNELS DOES IT HAVE? {D R:l.-I024.]:
; THE ARll LAB PERIPHERAL SYSTEM IS A LOW-COSTREALTTME SUBSYSTEM
WHICH INTERFACES TO THEPDP-11FAMILY OF COMPUTERS. THE SYSTEM
; INCLUDES A la-BIT AID CONVERTOR, PROGRAMMABLE REALTIME CLOCK,
AND DISPLAY CONTROL,.

3-36

SYSGEN DIALOGUE DETAILS

* HOW MANY ARll LAB PERIPHERAL SYSTEMS DO YOU HAVE?

[D R: 1-1024.]:

* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
THE CLOCK VECTOR ADDRESS FOR THE ARll IS ASSIGNED FROM THE
FLOATING VECTOR SPACE STARTING AT 300. IT IS LOCATED AT AN
OFFSET OF FOUR (4) FROM THE BEGINNING OF THE ARll VECTOR SPACE.
CONSULT FIELD SERVICE TO DETERMINE LOCATION IF UNKNOWN.

* ENTER CLOCK VECTOR ADDRESS OF THE NEXT ARll [0 R:300-774J:
For the ARll driver to operate properly,
the interrupt
vector of its real-time clock must be specified.
If the
number of ARlls specified was greater than 1, this query is
repeated by SGN for each ARll.
170400 IS THE STANDARD CSR ADDRESS FOR THE ARll. THE ADDRESS
REQUIRED HERE IS THAT OF THE FIRST WORD OF THE ARll CSR GROUP.

* WHAT IS ITS CSR ADDRESS?

[0 R:160000-177700 D:170400]:

THE POLARITY MASK WORD CORRESPONDS ONE-TO-ONE WITH THE 16
POSSIBLE CHANNELS. A I-BIT DESIGNATES A UNI-POLAR CHANNEL.
A O-BIT DESIGNATES A BI-POLAR CHANNEL.

* WHAT IS THE POLARITY MASK WORD? [0]:
* IS THE DIA OPTION PRESENT? [YIN]:
Although the ARll module includes a DIA converter, support
for the DIA is optional in the driver.
If DIA support is
not chosen, the driver will be significantly shorter.
THE QUERY RESPONSE VALUE MUST BE EVENLY DIVISIBLE INTO 10000.

* ENTER MAXIMUM NUMBER OF SAMPLES PER SECOND [D R:l.-2500.]:
THE ARll DOES NOT INCLUDE THE 16-BIT DIGITAL 1/0 OPTION THAT IS
AVAILABLE WITH THE LPSll. THE SAME FUNCTIONALITY, HOWEVER, MAY
BE ACHIEVED BY USING A DRII-K THAT IS JUMPER SELECTED TO USE
THE 16 INDIVIDUAL INPUT LINES WITHOUT INTERRUPTS.

* IS THE DRII-K OPTION PRESENT? [YIN]:
This query appears as many times as the number of ARlls
specified. Note that the queries for interrupt vector, CSR,
polarity mask word, DIA option, maximum sample rate, and
DRII-K option occur one after the other for each ARll. The
repeat sequence repeats all six queries.
If this question
is answered affirmatively, then the next question is also
asked.

* WHAT IS ITS CSR ADORESS? [0 R:160000-177700 D:170420]:
THE LPAll LAB PERIPHERAL ACELERATOR IS A REAL-TIME SUBSYSTEM WHICH
INTERFACES TO THE PDP-II FAMILY OF COMPUTERS. THE SYSTEM CONSISTS
OF THE LPA-ll, UP TO 2 AID CONVERTERS, A PROGRAMMABLE REAL-TIME
CLOCK, A DIA CONVERTER, AND UP TO FIVE DIGITAL 1/0 MODULES.

* HOW MANY LPAII-K LAB SUBSYSTEMS DO YOU HAVE: [D R:0.-16.]:

* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN):

LPAIl'S ARE ASSIGNED VECTORS FROM THE FLOATING VECTOR SPACE. CONSULT

3-37

SYSGEN DIALOGUE DETAILS

FIELD SERVICE TO DETERMINE THE LOCATION IF UNKNOWN.

* ENTER VECTOR ADDRESS OF THE NEXT LPAll [0 R:300-774]:
170460 IS THE STANDARD CSR ADDRESS FOR THE FIRST LPAll. NOTE THAT
THE ADDRESS REQUIRED IS TljAT OF THE FIRST WORD OF THE LPAll CSR
GROUP. CONSULT FIELD SERVtCE TO DETERMINE ITS LOCATION IF UNKNOWN.

* WHAT IS ITS CSR ADDRESS?

[0 R:160200-l77700 D:170460]:

THE LPSll LAB PERIPHERAL SYSTEM IS A REAL-TIME SUBSYSTEM WHICH
INTERFACES TO THE PDP-II FAMILY OF COMPUTERS. THE SYSTEM
HOUSES A l2-BIT A/D CONVERTOR, PROGRAMMABLE REAL-TIME CLOCK,
DISPLAY CONTROLLER AND A l6-BIT DIGITAL I/O OPTION.

* HOW MANY LPSll LAB. PERIPHERAL SYSTEMS DO YOU HAVE? [D R:0.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [Y/N]:

THE CLOCK VECTOR ADDRESS FOR THE LPSll IS ASSIGNED FROM THE
FLOATING VECTOR SPACE STARTING AT 300. IT IS LOCATED AT AN
OFFSET OF FOUR (4) FROM THE BEGINNING OF THE LPSll VECTOR
SPACE. CONSULT FIELD SERVICE TO DETERMINE THE LOCATION IF
UNKNOWN.

* ENTER CLOCK VECTOR ADDRESS OF THE NEXT LPSll

[0 R:300-774]:

170400 IS THE STANDARD CSR ADDRESS FOR THE LPSll. NOTE THAT THE
ADDRESS REQUIRED IS THAT OF THE FIRST WORD OF THE LPSll CSR
GROUP.

* WHAT IS ITS CSR ADDRESS? [0 R:160000-l77700 D:170400]:
* HOW MANY A/D CHANNELS DOES IT HAVE? [D R:l.-64.]:
* IS THE GAIN RANGING OPTION PRESENT? [YIN]:
If the gain ranging option is present, you are asked to
identify the polarity mask word and whether or not bandwidth
filtering is enabled. Otherwise, the next three queries are
skipped.
THE POLARITY MASK WORD CORRESPONDS ONE-TO-ONE WITH THE 16
POSSIBLE CHANNELS. A I-BIT DESIGNATES A UNI-POLAR CHANNEL. A
O-BIT DESIGNATES A BI-POLAR CHANNEL.

* WHAT IS THE POLARITY MASK WORD? [0]:
* DO YOU HAVE BANDWIDTH FILTERING ENABLED? [YIN]:
If bandwidth filtering is enabled, the following query
concerning the channel select delay is asked; otherwise it
is omitted.
WITH BANDWIDTH FILTERING ENABLED, THE LPSll DRIVER MUST IMPOSE
A SOFTWARE DELAY BETWEEN THE TIME IT CHANGES CHANNELS ON THE
MULTIPLEXER AND THE TIME IT INITIATES THE A/D CONVERSION. THIS
DELAY PERIOD CAN RANGE FROM 85 USEC TO 8.5 MSEC. CONSULT THE
LPSll LABORATORY PERIPHERAL SYSTEM USER'S GUIDE FOR THE PROPER
DELAY FOR YOUR APPLICATION.
NOTE THAT THE RESPONSE MUST BE IN 100 USEC UNITS, I.E. SPECIFY
25 TO DELAY 2.5 MSEC.

* ENTER CHANNEL SELECT DELAY (IN 100 USEC UNITS) [D R:l.~85.]:
Whether or not gain ranging is present, you are asked if the
D/A option is present.

3-38

SYSGEN DIALOGUE-DETAILS

* IS THE D/A OPTION PRESENT? [YIN]:
If it is present, you must enter the number of D/A channels.

* HOW MANY D/A CHANNELS DOES IT HAVE?

[D R:l.-lO.]:

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 LPSDR-A DIGITAL I/O AND RELAY MODULE IS SUPPORTED AS AN
OPTION BY THE LPSll DRIVER.

* IS THE DIGITAL I/O AND RELAY OPTION PRESENT?

[Y/N]:

THE QUERY RESPONSE VALUE MUST BE EVENLY DIVISIBLE INTO 10000.

* ENTER MAXIMUM NUMBER OF SAMPLES PER SECOND [D R:l.-2500.]:
Selection of ICS/ICR-ll support precludes UDC-ll
ICS/ICR-ll and UDC-ll are mutually exclusive.

support;

THE ICS-ll AND ICR-ll ARE PROCESS I/O SUBSYSTEMS WHICH PROVIDE
ANALOG AND DIGITAL INTERFACE CAPABILITIES BETWEEN THE PDP-II
COMPUTER SYSTEMS AND TYPICAL INDUSTRIAL INSTRUMENTATION AND
TRANSDUCERS. THE ICS-ll IS A LOCAL SUBSYSTEM FOR DIRECT
CONNECTION TO THE PDP-II UNIBUS. THE ICR-ll IS CONNECTED TO
THE PDP-II BY A HIGH-SPEED SERIAL LINE WHICH CAN BE UP TO
6000 FEET (1830 METERS) LONG.
EACH ICS/ICR-ll CAN ACCOMMODATE UP TO 16 FUNCTIONAL I/O MODULES.
RSX-llM/S SUPPORTS ANY MIXTURE OF ICS-ll AND ICR-ll SUBSYSTEMS
TO A MAXIMUM OF 12.
;

* HOW MANY ICS/ICR-ll SUBSYSTEMS DO YOU HAVE?

[D R:0.-12.]:

THE RSX-llM/S ICS/ICR-ll DRIVER PROVIDES THE CAPABILITY TO
INITIATE A TASK AS THE RESULT OF AN UNSOLICITED (EXTERNAL)
INTERRUPT. IF THIS OPTION IS SELECTED, SUPPORT IS PROVIDED TO
ALLOW TASKS TO BE LINKED TO INTERRUPTS AND TO OBTAIN ACTIVATION
DATA WHEN INITIATED .

* DO YOU WANT TASK ACTIVATION FROM UNSOLICITED INTERRUPTS?

[Y/N]:

234 IS THE STANDARD VECTOR ADDRESS FOR THE FIRST ICS/ICR-ll.
ADDITIONAL VECTORS ARE ASSIGNED FROM THE FLOATING VECTOR SPACE
STARTING AT 300. CONSULT FIELD SERVICE TO DETERMINE LOCATIONS
IF UNKNOWN.
;

* ENTER VECTOR ADDRESS OF THE NEXT ICS/ICR-ll

[0 R:234-774 D:234]:

171776 IS THE STANDARD CSR ADDRESS FOR THE FIRST ICS/ICR-ll.
ADDITIONAL ICS/ICR-ll CSR ADDRESSES ARE ASSIGNED STARTING AT
171766 AND PROCEED DOWNWARD AT EIGHT BYTE INTERVALS (E.G.
1 71 766, 1 71 756, 1 71 746, ETC.).
;

* WHAT IS ITS CSR ADDRESS?

[0 R:160000-l77700 D:17l776]:

Note that the default
described above.

CSR

* IS IT AN ICR-ll? [YIN]:
3-39

address

decremented

SYSGEN DIALOGUE DETAILS

This query is repeated for each ICS/ICR-ll selected.
THE IAD-IA IS A MERCURY WETTED FLYING CAPACITOR ANALOG TO
DIGITAL CONVERTER WITH 8 CHANNELS OF WIDE RANGE DIFFERENTIAL
INPUT.

* HOW MANY A/D CONVERTER MODULES IN THIS ICS/ICR? [D R:0.-16.]:
This query appears as many times as the
number
of
ICS/ICR-lls specified.
If answered with a non-zero value,
the next two questions are asked.

* WHAT IS THE MODULE NUMBER OF THE NEXT A/D CONVERTER?

[D R:0.-15.]:

THE IMX-IA IS A 16 CHANNEL EXPANDER MULTIPLEXER FOR THE IAD-IA
A/D CONVERTER. UP TO 7 IMX-IA MODULES MAY BE ADDED TO EACH
IAD-IA A/D CONVERTER. ALL IMX-IA MODULES MUST BE PHYSICALLY
ADJACENT TO THEIR ASSOCIATED IAD-IA CONVERTER.

* HOW MANY EXPANSION MULTIPLEXERS DOES IT HAVE? [D R:0.-7.]:
This query is repeated as many times as the number of A/D
converters specified.
Note that the queries for module
number and number of multiplexers occur one after the other
for each A/D converter. The repeat sequence repeats both
queries.
THE IDA-OA IS A 4 CHANNEL DIGITAL TO ANALOG CONVERTER CAPABLE
OF DRIVING 0 TO 10 VOLTS OR 0 TO 50 MILLIAMPS.

* HOW MANY D/A CONVERTER MODULES IN THIS ICS/ICR? [D R:O.-16.]:
This query appears as many times as the
number
of
ICS/ICR-lls specified.
If this query is answered with a
nonzero value, then the next question is asked.
Note that in the next six queries,
types
is
16 minus the number
specified.

the number
of modules

of module
previously

* ENTER THE MODULE NUMBER OF THE NEXT D/A CONVERTER [D R:0.-15.]:
This query is repeated as many times as the
converters specified.

number

D/A

THE SINGLE-SHOT OUTPUTS AVAILABLE FOR THE ICS/ICR-ll INCLUDE
THE IDC-OB DC VOLTAGE OUTPUT AND THE IAC-OB AC VOLTAGE OUTPUT
MODULES.

* HOW MANY SINGLE-SHOT OUTPUT MODULES IN THIS ICS/ICR? [D R:O.-x.]:
This query appears as many times as the
number
of
ICS/ICR-lls specified.
If this query is answered with a
nonzero value, then the next question is asked.

* ENTER MODULE NUMBER OF THE NEXT SINGLE-SHOT OUTPUT [D R:0.-15.]:
This query is repeated as many times
single-shot output modules specified.

the

number

THE BI-STABLE DIGITAL OUTPUT MODULES FOR THE ICS/ICR-ll INCLUDE
THE IRL-OA AND IRL-OB RELAY OUTPUTS, AND THE IAC-OA AC VOLTAGE
OUTPUTS.

3-40

SYSGEN DIALOGUE DETAILS
i

* HOW MANY BI-STABLE OUTPUT MODULES IN THIS ICS/ICR?

[D R:O.-x.l:

This query appears as many times as the
number
of
ICS/ICR-lls specified.
If this query is answered with a
nonzero value, then the next question is asked.

* ENTER MODULE NUMBER OF THE NEXT BI-STABLE OUTPUT [D R:O.-15.]:
This query is repeated
specified.

for

each

bi-stable

output

module

THE DIGITAL SENSE MODULES FOR THE ICS/ICR-ll INCLUDE THE IDC-IA
ISOLATED DC INPUT, THE IDC-ID NON-ISOLATED INPUT, AND THE
IAC-IA AC INPUT.

* HOW MANY DIGITAL SENSE MODULES IN THIS ICS/ICR?

[D R:O.-x.]:

This query appears as many times as the
number
of
ICS/ICR-lls specified.
If this query is answered with a
nonzero value, then the next question is asked.

* ENTER MODULE NUMBER OF THE NEXT DIGITAL SENSE [D R:O.-15.]:
This query
specified.

repeated

for

each

digital

sense

module

THE DIGITAL INTERRUPT MODULES FOR THE ICS/ICR-ll INCLUDE THE
IDC-IB ISOLATED DC INTERRUPT, THE IDC-IE NON-ISOLATED DC
INTERRUPT, AND THE IAC-IB AC INTERRUPT.

* HOW MANY DIGITAL INTERRUPT MODULES IN THIS ICS/ICR? [D R:O.-x.]:
This query appears as many times as the
number
of
ICS/ICR-lls specified.
If this query is answered with a
nonzero value, then the next question is asked.

* ENTER MODULE NUMBER OF THE NEXT DIGITAL INTERRUPT ]D R:O.-15.]:
This query is repeated for
specified.

each

digital

interrupt

module

THE IDC-IC IS A 16 BIT BINARY UP-COUNTER WITH PRESCALAR INPUT
AND BOTH EXTERNAL TRIGGER AND OVERFLOW OUTPUTS.

* HOW MANY I/O COUNTER MODULES IN THIS ICS/ICR? [D R:O.-x.]:
This query appears as many times as the
number
of
ICS/ICR-lls specified. Note that the queries fo~ interrupt
vector, CSR, and ICS/ICR-ll and the key queries for A/D
converters, D/A converters, single-shot outputs, bistable
outputs, digital sense, digital interrupt, and I/O counters
occur one after the other for each ICS/ICR-ll. The repeat
sequence repeats all ten queries. If the answer to this
query is nonzero, then the next question is asked.

* ENTER MODULE NUMBER OR THE NEXT I/O COUNTER [0 R:O.-15.]:
This query
specified.

repeated

for

each

I/O

counter

module

THE RSX-IIM/S ICS/ICR-ll DRIVER WILL OPTIONALLY RESTORE THE
STATE OF ALL BI-STABLE DIGITAL OUTPUTS, ANALOG OUTPUTS, AND I/O
PRESCALAR VALUES ON POWER RECOVERY AND RECOVERY FROM SUSTAINED

3-41

SYSGEN DIALOGUE DETAILS
ICR-ll SERIAL TRANSMISSION ERRORS.

* RESTORE MODULE STATUS ON POWER AND ERROR RECOVERY? [YIN]:
The above query is asked only if the target system contains
a bistable output, D/A converter, or I/O counter modules.
THE RSX-IIM/S ICS/ICR-ll DRIVER WILL PLACE AN ICR-ll SUBSYSTEM
OFFLINE IF THE SERIAL LINE ERRORS EXCEED A PREDEFINED LIMIT
DURING ONE SECOND OF ELAPSED TIME. THE SUBSYSTEM WILL
AUTOMATICALLY BE PLACED ONLINE WHEN SERIAL LINE ERRORS HAVE
STOPPED.

* HOW MANY LINE ERRORS ARE ACCEPTABLE PER SEC.? [0 R:O.-5000.]:
The above query is asked only if the target system
an ICR-ll subsystem.

contains

THE DRS-II IS A DIGITAL I/O MODULE DESIGNED TO MEET THE NEEDS
OF SMALL INDUSTRIAL DATA ACQUISITION AND CONTROL SYSTEMS.
EACH DRS-II MODULE PROVIDES 48 BUFFERED DIGITAL OUTPUTS AND
ONE RC FILTERED INTERRUPT INPUT.

* HOW MANY DRS-II DIGITAL OUTPUT MODULES DO YOU HAVE? [0 R:O.-16.]:
* DO YOU WANT MODULE STATUS RESTORED ON POWER RECOVERY? [YIN]:
* ENTER CSR ADDRESS OF THE FIRST DRS-II [0 R:160000-177700]:
* WHAT IS THE VECTOR ADDRESS OF THE NEXT DRS-II? [0 R:300-774]:
Note that since the DRS/DSS-ll driver cannot
the loadable driver query was omitted.

loadable,

The power recovery and CSR address questions are asked only
once.
The vector address question is asked for each DRS-II
specified.
THE DSS-ll IS A DIGITAL I/O MODULE DESIGNED TO MEET THE NEEDS
OF SMALL INDUSTRIAL DATA ACQUISITION AND CONTROL SYSTEMS.
EACH DSS-ll MODULE PROVIDES 49 OPTICALLY ISOLATED INPUTS
CONSISTING OF 48 NON-BUFFERED SENSE DATA INPUTS AND 1 INTERRUPT
INPUT.

* HOW MANY DSS-ll DIGITAL INPUT MODULES DO YOU HAVE? [0 R:O.-x.]:
Note that x above is replaced by
DRS-lIs specified.

minus

the

number

The combined number of DRS-II and DSS-ll modules cannot
exceed 16. Therefore, if 16 DRS-II modules were specified,
the above DSS-ll query and the next two pertaining to the
CSR and vector addresses of the DSS-ll module are omitted.

* ENTER CSR ADDRESS OF THE FIRST DSS-ll [0 R:160000-177700]:
* WHAT IS THE VECTOR ADDRESS OF THE NEXT DSS-ll? [0 R:300-774]:
THE RSX-IIM/S DRS/DSS-ll DRIVER PROVIDES THE CAPABILITY TO
INITIATE A TASK AS THE RESULT OF AN UNSOLICITED (EXTERNAL)
INTERRUPT. IF THIS OPTION IS SELECTED, SUPPORT IS PROVIDED TO
ALLOW TASKS TO BE LINKED TO INTERRUPTS AND TO OBTAIN ACTIVATION
DATA WHEN INITIATED.

* DO YOU WANT TASK ACTIVATION FROM UNSOLICITED INTERRUPTS? [YIN]:

3-42

SYSGEN DIALOGUE DETAILS
This question is asked if at least one DRS/DSS-ll module was
specified.
The following queries
concerning
the
UDCll
digital
controllers are asked only if ICS/ICR support was omitted.
THE UDCll IS AN INPUT/OUTPUT OPTION FOR INDUSTRIAL AND PROCESS
CONTROL APPLICATIONS THAT USE THE PDP-II COMPUTER. THE UDCll
INTERROGATES OR DRIVES UP TO 252 DIRECTLY ADDRESSABLE DIGITAL
SENSE AND CONTROL FUNCTIONAL I/O MODULES OR UP TO 4032
INDIVIDUAL DIGITAL POINTS.
RSX-llM/S SUPPORTS ONLY ONE UDC CONTROLLER. THE ONLY VALID
ANSWERS TO THIS QUERY ARE 0 AND 1.

* HOW MANY UDCll CONTROLLERS DO YOU HAVE? [D R:O.-l.]:
234 IS THE STANDARD VECTOR ADDRESS FOR THE UDCll.

* WHAT IS THE VECTOR ADDRESS OF THE UDCll? [0 R:60-774 D:234]:
171776 IS THE STANDARD CSR ADDRESS FOR THE UDCll.

* WHAT IS ITS CSR ADDRESS? [0 R:160000-l77700 D:17l776]:
The UDCll can support up to
classified into seven types:
1.
2.
3.
4.
5.
6.
7.

252

modules,

which

can

Analog input
Analog output
Digital interrupt
Digital sense
Bistable output
Single-shot output
I/O counters

RSX-llM/RSX-llS requires that modules of the same type
occupy consecutive locations within the UDCll. Thus, if
there are seven analog input modules and the first module
starts at slot 0,
then the last must be at slot 6.
Obviously, module types cannot overlap, though unassigned
slots are permitted.
The queries which follow establish the module boundaries.

* HOW MANY ADUOI ANALOG INPUT MODULES DO YOU HAVE?
[D R:0.-252.]:
* ENTER MOD. NUMBER OF THE FIRST ADUOI ANALOG INPUT [D R:0.-252.]:
The next query appears only if the number
input modules was zero.

ADUOI

analog

* HOW MANY IAD-IA ANALOG INPUT MODULES DO YOU HAVE? [D R:0.-252.]:
* ENTER MOD. NUMBER OF THE FIRST IAD-IA ANALOG INPUT [D R:0.-252.]:
Note that in the following queries, x is replaced
minus the number of other modules specified.

* HOW MANY ANALOG OUTPUT MODULES DO YOU HAVE? [D R:O.-x.]:
* ENTER MOD. NUMBER OF THE FIRST ANALOG OUTPUT [D R:0.-252.]:
* HOW MANY DIGITAL INTERRUPT MODULES DO YOU HAVE? [D R:O.-x.]:
* ENTER MOD. NUMBER OF THE FIRST DIGITAL INTERRUPT [D R:0.-252.]:
* HOW MANY DIGITAL SENSE MODULES DO YOU HAVE? [D R:O.-x.]:
* ENTER MOD. NUMBER OF THE FIRST DIGITAL SENSE [D R:0.-252.]:
* HOW MANY BI-STABLE OUTPUT MODULES DO YOU HAVE? [D R:O.-x.]:
3-43

252

SYSGEN D.IALOGUE DETAILS

* ENTER MOD. NUMBER OF THE FIRST BI-STABLE OUTPUT [D R:0.-252.]:
* HOW MANY SINGLE-SHOT OUTPUT MODULES DO YOU HAVE? [D R:O.-x.]:
* ENTER MOD. NUMBER OF THE FIRST SINGLE-SHOT OUTPUT [D R:0.-252.]:
* HOW MANY I/O COUNTER MODULES DO YOU HAVE? [D R:O.-x.]:
* ENTER MOD. NUMBER OF THE FIRST I/O COUNTER [D R:0.-252.J:
This is the end of process I/O peripheral queries.
**ALL SYSTEMS**
THE CRll CARD READER READS EIA STANDARD 80-COLUMN PUNCHED DATA
CARDS AT 300 CARDS PER MINUTE; THE CMII-F READS SO-COLUMN
MARK-SENSE CARDS, WHICH CAN HAVE PUNCHED HOLES, AT 285 CARDS
PER MINUTE.
* HOW MANY CM/CRll CARD READERS DO YOU HAVE? [0 R:0.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
* enter VECTOR ADDRESS OF THE NEXT CM/CRll? [0 r:60-774 d:230]:
* WHAT IS ITS CSR ADDRESS? [0 r:160000-l77700 d:1777160]:

YOU MAY OPTIONALLY SPECIFY THE TIME BETWEEN READER NOT READY
MESSAGES. A RESPONSE OF ZERO SUPPRESSES THE MESSAGES ENTIRELY •

* ENTER INTERVAL FOR READER NOT READY MESSAGES [D R:0.-255. D:15.]:
Reader not ready messages are displayed in
1-255 seconds each on the console terminal.

intervals

THE TAll MAGNETIC TAPE CASSETTE SYSTEM IS DUAL-DRIVE,
REEL-TO-REEL UNIT DESIGNED TO REPLACE PAPER TAPE. ITS TWO
DRIVES RUN NON-SIMULTANEOUSLY USING PROPRIETARY DIGITAL
EQUIPMENT CORPORATION PHILIPS-TYPE CASSETTES. THE TAll
INCLUDES A CONTROL UNIT AND A DUAL TAPE TRANSPORT.
* HOW MANY TAll DUAL CASSETTES DO YOU HAVE? [D R:0.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
* WHAT IS THE VECTOR ADDRESS OF THE NEXT TAll [0 R:60-774 D:260]:
* WHAT IS ITS CSR ADDRESS? [0 R:160000-177700 D:177500]:
THE RJ/RWP04-05-06 ARE 19 DATA SURFACE, REMOVABL~, RANDOM ACCESS
BULK STORAGE SYSTEMS WITH A STORAGE CAPACITY OF 43,980,288 WORDS
(RP04-05) AND 87,211,520 WORDS (RP06) PER PACK. EACH INCLUDES
A CONTROL UNIT AND THE FIRST DISK PACK DRIVE AND IS EXPANDABLE
UP TO EIGHT DRIVES.
* HOW MANY RJ/RWP04-05-06 DISK CONTROLLERS HAVE YOU? [0 R:0.-16.]:
OFFSET RECOVERY IS A TECHNIQUE FOR READING DATA IN INSTANCES
WHERE IT CANNOT OTHERWISE BE RECOVERED. IT INVOLVES MOVING THE
DISK READ HEAD IN SMALL INCREMENTS ABOUT CYLINDER CENTERLINE IN
AN ATTEMPT TO PICK UP A STRONGER SIGNAL AND THUS ALLOW DATA TO
BE RECOVERED.
* DO YOU WANT OFFSET RECOVERY SUPPORT?[Y/N]:
Offset recovery is especially important in environments
where disk packs are frequently moved from drive to drive.
It is also recommended when a high degree
of
data
reliability is required.
3-44

SYSGEN DIALOGUE DETAILS

* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
* ENTER VECTOR ADDRESS OF THE NEXT RJ/RWP04-05-06? [0 R:60-774 D:254]:
* WHAT IS ITS CSR ADDRESS? [0 R:160000-177700 D:176700]:
* HOW MANY DRIVES DOES IT HAVE? [D R:l.-8.]:
This query appears as
controllers specified.

many

times

the

number

THE TYPICAL RESPONSE TO THE NEXT QUESTION IS ZERO. A NONZERO
RESPONSE SHOULD BE ARRIVED AT AFTER CONSULTATION WITH A DEC
FIELD SERVICE REPRESENTATIVE.

* ENTER PHYSICAL UNIT NUMBER OF THE FIRST DRIVE

[0 D:O]:

This query appears as many times as the
number
of
controllers specified.
Note that the queries for the
interrupt vector, CSR, the number of drives, and physical
unit number occur one after the other for each controller.
The repeat sequence repeats all four of the queries.

* IS THE FIRST DRIVE AN RP04 OR RP05? [YIN]:
* IS THE NEXT DRIVE AN RP04 OR RP05? [YIN]:
RP05s and RP06s can be mixed on the same controller:
specify N to indicate an RP06 unit. The second query is
repeated as many times as the number of drives previously
specified.
THE RFII-A IS A FAST, LOW-COST, RANDOM-ACCESS BULK-STORAGE
SYSTEM. AN RFII-A PROVIDES 262,144 17-BIT WORDS (16 DATA BITS
AND 1 PARITY BIT) OF STORAGE. UP TO EIGHT RSll DISKS CAN BE
CONTROLLED BY ONE RFll CONTROL FOR A TOTAL OF 2,047,102 WORDS
OF STORAGE. AN RFII-A INCLUDES A CONTROL UNIT AND THE FIRST
DISK DRIVE.

* HOW MANY RFll DISK CONTROLLERS DO YOU HAVE? [D R:0.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
* ENTER VECTOR ADDRESS OF THE NEXT RFll? [0 R:60-774 D:204]:
* WHAT IS ITS CSR ADDRESS? [0 R:160000-177700 D 1777460]:
THE RKII-D CARTRIDGE DISK DRIVE AND CONTROL IS A COMPLETE MASS
STORAGE SYSTEM FOR LARGE VOLUME, RANDOM ACCESS DATA STORAGE.
THE SYSTEM INCLUDES A MODULAR MASS STORAGE DEVICE UTILIZING
REMOVABLE DISK CARTRIDGES AND A COMPLETE, EASY-TO-PROGRAM,
CONTROL UNIT. A DISK CARTRIDGE HOLDS OVER 1.2 MILLION WORDS.
THE SYSTEM IS EXPANDABLE UP TO 9.6 MILLION WORDS PER CONTROL (8
DISKS). AN RKII-D INCLUDES A CONTROL UNIT AND THE FIRST DISK
DRIVE. OPTIONALLY, THE CONTROLLER CAN SUPPORT UP TO FOUR RK05F
FIXED PLATTER DRIVES HAVING TWICE THE CAPACITY OF THE STANDARD
RK05 DRIVES.

* HOW MANY RKll DISK CONTROLLERS DO YOU HAVE?

[D R:0.-16.]:

* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:

3-45

SYSGEN DIALOGUE DETAILS

* ENTER VECTOR ADDRESS OF THE NEXT RKll [0 R:60-774 D:220]:
* WHAT IS ITS CSR ADDRESS? [0 R:160000-177700 D:177404]:
* ENTER NUMBER OF RK05F FIXED PLATTERS [0 R:0-4]:
This query appears as many times as the number of RKII-Ds
specified.
Note that the queries for the interrupt vector,
CSR, and the number of drives occur one after the other for
each RKII-D controller.
The repeat sequence repeats all
three of the queries.
If fewer than 4 RK05Fs are specified,
the next two questions are asked:
otherwise they are
omitted.

* ENTER NUMBER OF RK05 REMOVABLE PLATTERS [D R:l.-x.]:
Note that x above is replaced by eight minus two
number of RK05Fs.

times

the

The RKII-D controller can service up to 8 units where each
RK05F is handled as 2 standard RK05 units.
If the total
number of units calculated is odd and there is at least one
RK05F drive present, the next question is asked: otherwise
it is omitted.

* IS THE LAST DRIVE AN RK05F? [YIN]:
Since each RK05F requires two unit slots and must begin on
an even numbered unit,
it may be necessary for the query
section to add one dummy unit to the system.
An example
would be the case in which unit 0 is an RK05, unit 1 is an
empty slot, and units 2 and 3 are an RK05F.
In this
instance, an affirmative answer (Y) should be supplied, so
that the query section could supply the required fourth unit
control block.
THE RLll/RLOl DISK SUBSYSTEM USES A MEDIUM PERFORMANCE, DIRECT
ACCESS DRIVE WITH A SINGLE READ/WRITE HEAD PER SURFACE. EACH
DRIVE PROVIDES 2,621,440 16-BIT WORDS OF STORAGE ON A REMOVABLE,
TOP LOADING CARTRIDGE. THE SUBSYSTEM IS EXPANDABLE UP TO FOUR
DRIVES.

* HOW MANY RLll DISK CONTROLLERS DO YOU HAVE? [D R:0.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [Y/N]:
* ENTER VECTOR ADDRESS OF THE NEXT RLll [0 R:60-774 D:330]:
* WHAT IS ITS CSR ADDRESS? [0 R:160000-177700 D:174400]:
* HOW MANY DRIVES DOES IT HAVE? [D R:l.-4.]:
THE RK611/RK06-07 IS A 3 DATA SURFACE, REMOVABLE, RANDOM ACCESS
BULK STORAGE SYSTEM WITH A STORAGE CAPACITY OF 6,944,256 (RK06)
OR 13,770,240 (RK07) 16-BIT WORDS PER PACK. THE RK611/RK06-07
INCLUDES A CONTROL UNIT AND THE FIRST DISK PACK DRIVE. THE
SYSTEM IS EXPANDABLE UP TO EIGHT DRIVES.

* HOW MANY RK611 DISK CONTROLLERS DO YOU HAVE? [D R:0-16.]:
OFFSET RECOVERY IS A TECHNIQUE FOR READING DATA IN INSTANCES
WHERE IT CANNOT OTHERWISE BE RECOVERED. IT INVOLVES MOVING THE
DISK READ HEAD IN SMALL INCREMENTS ABOUT CYLINDER CENTERLINE IN
AN ATTEMPT TO PICK UP A STRONGER SIGNAL AND THUS ALLOW DATA TO
BE RECOVERED.
3-46

SYSGEN DIALOGUE DETALLS

* DO YOU WANT OFFSET RECOVERY SUPPORT? [Y/N]:
Offset recovery is especially important in environments
where disk packs are frequently moved from drive to drive.
It is also recommended where a higher degree of data
reliability is required.

* DO YOU WANT THE DRIVER TO BE LOADABLE?

[Y/N]:

* ENTER VECTOR ADDRESS OF THE NEXT RK611 [0 R:60-774 D:210]:
* WHAT IS ITS CSR ADDRESS? [0 R:160000-177700 D:177440]:
* HOW MANY DRIVES DOES IT HAVE? [D R:l.-8.]:
This query appears as many times as the number of RK611
controllers specified.
Note that the queries for
the
interrupt vector, command register, and the number of drives
occur one after the other for each RK611 controller. The
repeat sequence repeats all three of the queries.

* IS THE FIRST DRIVE AN RK06? [Y/N]:
* IS THE NEXT DRIVE AN RK06? [Y/N]:
THE RPII-C/E IS A COMPLETE MASS STORAGE SYSTEM USING A MAGNETIC
DISK PACK WITH 20 DATA SURFACES AND A MOVING READ/WRITE HEAD.
THE RPII-C/E INCLUDES A CONTROL UNIT AND THE FIRST DISK PACK
DRIVE. THE SYSTEM IS EXPANDABLE UP TO 8 DRIVES, EACH HAVING A
CAPACITY OF 20,480,000 (RP03)
OR 10,240,000
(RPR02)
16-BIT
WORDS. ACCESS TIMES ARE 29 MSEC. AVERAGE LATERAL (CYLINDER TO
CYLINDER) AND 12.5 MSEC. HALF ROTATIONAL.

* HOW MANY RPII-C/E DISK CONTROLLERS DO YOU HAVE? [D R:0.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [Y/N]:
* ENTER VECTOR ADDRESS OF THE NEXT RPIIC/E? [0 R:60-774 D:254]:
* WHAT IS ITS CSR ADDRESS? [0 R:160000-177700 D:176714]:
* HOW MANY DRIVES DOES IT HAVE? [D R:l.-8.]:
This query appears as many times as the number of RPIIC/E
controllers specified.
Note that the queries for
the
interrupt vector, CSR, and the number of drives, occur one
after the other for each RPIIC/E controller. The repeat
sequence repeats all three of the queries.

* IS THE FIRST DRIVE AN RPR02? [Y/N]:
* IS THE NEXT DRIVE AN RPR02? [Y/N]:
This query is repeated as many times as the number of drives
previously specified.
THE RWM03 IS A REMOVABLE PACK, RANDOM ACCESS DISK STORAGE
SYSTEM WITH A STORAGE CAPACITY OF 33,710,080 WORDS PER PACK.
EACH INCLUDES A CONTROL UNIT AND THE FIRST DISK PACK DRIVE AND
IS EXPANDABLE TO EIGHT DRIVES.

3-47

SYSGEN DIALOGUE DETAILS
;

* HOW MANY RWM03 DISK CONTROLLERS DO YOU HAVE? [D R:0.-16.]:
OFFSET RECOVERY IS A TECHNIQUE FOR READING DATA IN INSTANCES
WHERE IT CANNOT OTHERWISE BE RECOVERED. IT INVOLVES MOVING THE
DISK HEAD ON EITHER SIDE OF THE CYLINDER CENTERLINE IN AN
ATTEMPT TO PICK UP A STRONGER SIGNAL AND THUS ALLOW DATA TO BE
RECOVERED.

* DO YOU WANT OFFSET RECOVERY SUPPORT? [YIN]:
Offset recovery is especially important in environments
where disk packs are frequently moved from drive to drive.
It is also recommended where a higher degree of data
reliability is required.

* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
* ENTER VECTOR ADDRESS OF THE NEXT RWM03 [0 R:60:774 D:254]:
* WHAT IS ITS CSR ADDRESS? [0 R:160000-l77700 D:176700]:
* HOW MANY DRIVES DOES IT HAVE? [D R:l.-B.]:
This query is repeated as many times as the number of RWM03
controllers specified.
Note that the queries for the
interrupt vector, CSR, and the number of drives, occur one
after the other for each RWM03 controller. The repeat
sequence repeats all three of the queries.
THE TYPICAL RESPONSE TO THE NEXT QUESTION IS ZERO. A NONZERO
RESPONSE SHOULD BE ARRIVED AT AFTER CONSULTATION WITH A DEC
FIELD SERVICE REPRESENTATIVE.

* ENTER PHYSICAL UNIT NUMBER OF THE FIRST DRIVE [0 D:O]:
THE RJ/RWS03-04 USES THE RH1l CONTROLLER. THE RJ/RWS03 HAS A
CAPACITY OF 256K WORDS; THE RJ/RWS04 HAS A CAPACITY OF 5l2K
WORDS. TRANSFER RATE IS 4-MICROSECONDS PER WORD WITH AN
AVERAGE LATENCY OF B-MILLISECONDS.
;

* HOW MANY RJ/RWS03-04 DISK CONTROLLERS DO YOU HAVE?

[D R:0.-16.J:

* DO YOU WANT THE DRIVER TO BE LOADABLE? [Y/NJ:
* ENTER VECTOR ADDRESS OF THE NEXT RJ/RWS03-04 [0 R:60-774 D:204]:
* WHAT IS ITS CSR ADDRESS? [0 R:160000-l77700 D:172040]:
* HOW MANY DRIVES DOES IT HAVE? [D R:l.-B.J:
This query appears as many times
RJ/RWS03-04 controllers specified.

the

number

THE TYPICAL RESPONSE TO THE NEXT QUESTION IS ZERO; A NON-ZERO
RESPONSE SHOULD BE ARRIVED AT AFTER CONSULTATION WITH A DEC
FIELD SERVICE REPRESENTATIVE.

* ENTER PHYSICAL UNIT NUMBER OF THE FIRST DRIVE [0 D:OJ:
This query is repeated as many times as the number of
RJ/RWS03-04 controllers specified.
Note that the queries
for the interrupt vector, CSR, number of drives, and the

3-4B

SYSGEN DIALOGUE DETAILS
unit number of first drive occur one after the other for
each RJ/RWS03-04 controller. The repeat sequence repeats
all four of the queries.

* IS THE FIRST DRIVE AN RS03?

[YIN]:

* IS THE NEXT DRIVE AN RS03? [YIN]:
RS03s and RS04s can be mixed on the same controller;
specify N to indicate an RS04 unit. This query is repeated
as many times as the number of drives previously specified.
THE TCll-G IS A DUAL-UNIT BIDIRECTIONAL MAGNETIC-TAPE TRANSPORT
SYSTEM FOR AUXILIARY DATA STORAGE.
THE SYSTEM STORES INFORMATION AT FIXED POSITIONS ON MAGNETIC
TAPE AS IN MAGNETIC DISK OR DRUM STORAGE DEVICES, RATHER THAN
AT UNKNOWN OR VARIABLE POSITIONS AS IN CONVENTIONAL MAGNETIC
TAPE SYSTEMS.
A DECTAPE SYSTEM CONSISTS OF UP TO 4 DUAL TRANSPORTS, AND A
CONTROL UNIT (WHICH WILL BUFFER AND CONTROL INFORMATION FOR UP
TO FOUR DUAL TRANSPORTS). A TCll-G INCLUDES A CONTROL UNIT AND
THE FIRST DUAL TAPE TRANSPORT.

* HOW MANY TCII DECTAPE CONTROLLERS DO YOU HAVE? [D R:O.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
* ENTER VECTOR ADDRESS OF THE NEXT TCll? [0 R:60-774 D:2l4]:
* WHAT IS ITS CSR ADDRESS?

[0 R:160000-l77700 D:177342]:

* HOW MANY DRIVES DOES IT HAVE?

[D R:l.-8.]:

This query appears as many times as the number of TCll-G
controllers specified.
Note that the queries for the
interrupt vector, command register, and the number of drives
occur one after the other for each TCII controller. The
repeat sequence repeats all three of the queries.
THE RXII IS AN INDUSTRY-COMPATIBLE DISK STORAGE SYSTEM FOR
FLEXIBLE (FLOPPY) DISKS. AN RXII IS CAPABLE OF CONTROLLING TWO
FLEXIBLE DISK DRIVES EACH HAVING A CAPACITY OF 128,128 l6-BIT
WORDS.

* HOW MANY RXII DISK CONTROLLERS DO YOU HAVE? [D R:O.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
* ENTER VECTOR ADDRESS OF THE NEXT RXll?

[0 R:60-774 D:264]:

* WHAT IS ITS CSR ADDRESS? [0 R:160000-l77700 D:177l70]:
* HOW MANY DRIVES DOES IT HAVE? [0 R:1-2]:
This query appears as many times as the number of RXII
controllers specified.
Note that the queries for the
interrupt vector, CSR, and the number of drives occur one
after the other for each RXII controller.
The repeat
sequence repeats all three of the queries.

3-49

SYSGEN DIALOGUE DETAILS
If the target system is a PDP-11/70 with extended memory
support,
then the next five questions are omitted. Note
also that the VTll/VS60 driver cannot be loadable.
THE VTll IS A LOW COST, LINE DRAWING, GRAPHICS DISPLAY
SUBSYSTEM, WHICH MAY BE PACKAGED IN THE GT SERIES OF DISPLAY
SYSTEMS OR RUN SEPARATELY. VTll SUPPORT IN RSX-1IM HAS THE
FOLLOWING RESTRICTIONS:
ONLY ONE VTll (OR VS60) IN THE SYSTEM,
THE DRIVER DOES NOT OPERATE ON THE PDP-11/70 IN 22-BIT MODE,
THE DISPLAY BUFFER OF THE TASK DRIVING THE VTll MUST RESIDE
COMPLET~LY IN THE LOW 28K OF SYSTEM MEMORY.

* DO YOU HAVE A VTll GRAPHICS DISPLAY SUBSYSTEM? [YIN]:
An affirmative reply to this query will exclude the high
performance
VS60 graphics display subsystem from your
configuration. Hence a Y response to VTll will inhibit the
display of queries concerning the VS60.
THE VECTOR ADDRESS FOR THE GRAPHICS DISPLAY SUBSYSTEMS IS
ASSIGNED FROM THE FLOATING VECTOR SPACE STARTING AT 300.
CONSULT FIELD SERVICE TO DETERMINE THE LOCATION IF UNKNOWN.

* ENTER VECTOR ADDRESS OF THE GRAPHICS SUBSYSTEM [0 R:300-774]:
* WHAT IS ITS CSR ADDRESS? [0 R:160000-l77700 D:172000]:
The following queries concerning the VS60
subsystem are displayed only if VTll
selected.

graphics display
support was not

THE VS60 IS A HIGH PERFORMANCE, LINE DRAWING, GRAPHICS DISPLAY
SUBSYSTEM. THE VS60 IS SUPPORTED IN RSX-llM .WITH THE FOLLOWING
RESTRICTIONS:
- THE DRIVER DOES NOT OPERATE ON THE PDP-11/70 IN 22-BIT MODE,
- ONLY ONE VS60 (OR VTll) IN THE SYSTEM.
;

* DO YOU HAVE A VS60 GRAPHICS DISPLAY SUBSYSTEM? [YIN]:
the vs60 can drive two crt monitors independently.

* DOES IT DRIVE TWO CRT MONITORS? [YIN]:
This query determines whether or not such
desired.

functionality

* ENTER VECTOR ADDRESS OF THE GRAPHICS SUBSYSTEM [0 R:300-774]:
* WHAT IS ITS CSR ADDRESS? [0 R:160000-l77700 D:172000]:
THE LPll HIGH SPEED LINE PRINTER IS AVAILABLE IN EIGHT MODELS.
LPll-F
LPII-H
LP1I-J
LPII-K
LPII-R
LPII-S
LP1I-V
LP1I-W

80 COLUMN, 64 CHARACTER
80 COLUMN, 96 CHARACTER
132 COLUMN, 64 CHARACTER
132 COLUMN, 96 CHARACTER
132 COLUMN, 64 CHARACTER (HEAVY DUTY, HIGH SPEED)
132 COLUMN, 96 CHARACTER (HEAVY DUTY, HIGH SPEED)
132 COLUMN, 64 CHARACTER
132 COLUMN, 96 CHARACTER

3-50

SYSGEN DIALOGUE DETAILS
THE LSll LINE PRINTER IS A MEDIUM-SPEED IMPACT DOT-MATRIX LINE
PRINTER FOR THE PDP-II FAMILY. THE LINE PRINTER PRINTS AT A
RATE OF 165 CHA&~CTERS PER SECOND AT 10 CHARACTERS PER INCH
WITH UP TO 132 CHARACTERS PER LINE.
THE LA180 LINE PRINTER IS A DEC MANUFACTURED DEVICE SIMILAR TO
THE LSll WITH THE EXCEPTION THAT IT PRINTS AT THE RATE OF 180
CHARACTERS PER SECOND.
THE LVII IS A HIGH-SPEED ELECTROSTATIC PRINTER-PLOTTER. ONLY
THE PRINT OPTION IS SUPPORTED UNDER RSX-IIM/S.

* HOW MANY LP/LS/LVII/LA180 LINE PRINTERS DO YOU HAVE?

[D R:0-16]:

TO ENSURE MAXIMUM THROUGHPUT ON THE LPII-R OR LPII-S
ANSWER YES TO THE NEXT QUESTION.

* DO YOU WANT FAST PRINTER SUPPORT? [YIN]:
This option ensures maximum print throughput on
or LPII-S.

the

LPII-R

* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
* ENTER VECTOR ADDRESS OF THE NEXT LINE PRINTER? [0 R:60-774 D:200]:
* WHAT IS ITS CSR ADDRESS? [0 R:160000-177700 D:177514]:
* IS IT AN LSll, LA180, OR LPII-V/W? [YIN]:
Improper specification of the printer type may cause
failures.

output

This query is repeated for each printer specified.

* IS IT A 132. COLUMN PRINTER? [YIN]:
Improper specification of line width will cause buffer
truncation. An N or null response defaults to 80 columns.
This query appears as many times as the number of printers
specified.
Note that the queries for the interrupt vector,
CSR, LSll, and line width occur one after the other for each
printer specified. The repeat sequence repeats all four of
the queries.
After the repeat sequence completes, the following is asked.
YOU MAY OPTIONALLY SPECIFY THE NUMBER OF SECONDS BETWEEN PRINTER
NOT READY MESSAGES. AN INTERVAL OF ZERO SUPPRESSES THE MESSAGES
ALTOGETHER. THE DEFAULT IS 15. SECONDS. FOR THE MINIMUM SYSTEM
YOU MUST ANSWER THE NEXT QUESTION YES.

* DO YOU WANT 15. SECONDS BETWEEN PRINTER NOT READY MESSAGES? [YIN]:
If not, you are asked to specify the interval in seconds
that the message will be displayed. Printer not ready is
displayed on the console terminal.

* HOW MANY SECONDS BETWEEN NOT READY MESSAGES [D R:0.-255. D:15]:
THE TJ/TWU/TWE16-45 IS A MAGNETIC TAPE SYSTEM IDEALLY SUITED FOR
WRITING, READING, AND STORING LARGE VOLUMES OF DATA AND
PROGRAMS IN A SERIAL MANNER. THE 10 1/2-INCH TAPE REELS

3-51

SYSGEN DIALOGUE DETAILS
CONTAIN UP TO 2400 FEET OF TAPE. THE TAPE IS 9-TRACK, RECORDED
EITHER NRZI OR PHASE ENCODED WITH RECORDING DENSITIES OF 800 OR
1600 BPI.

* HOW MANY TM02/03 MAGTAPE CONTROLLERS HAVE YOU? [0 R:0.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:

* ENTER VECTOR ADDRESS OF THE NEXT TJ/TWU/TWE16-45?

[0 R:60-774

D:224]:

* WHAT IS ITS CSR ADDRESS? [0 R:160000-177700 D:172 440]:
* HOW MANY DRIVES DOES IT HAVE? [D R:l.-8.]:
This query appears as many times
TJ/TWU16-45 controllers specified.

the

number

THE TYPICAL RESPONSE TO THE NEXT QUESTION IS ZERO; A NON-ZERO
RESPONSE SHOULD BE ARRIVED AT AFTER CONSULTATION WITH A DEC
FIELD SERVICE REPRESENTATIVE.

* ENTER PHYSICAL UNIT NUMBER OF THE TM02/03 FORMATTER

[0 D:O]:

This query appears as many times as the
number
of
TJ/TWU16-45s specified.
Note that the queries for the
interrupt vector, CSR,
the number of drives, and the
physical unit number occur one after the other for each
TJ/TWU16-45. The repeat sequence repeats all four of the
queries.
THE TM/TMA/TMBll IS A MAGNETIC TAPE SYSTEM IDEALLY SUITED FOR
WRITING, READING, AND STORING LARGE VOLUMES OF DATA AND
PROGRAMS IN A SERIAL MANNER. THE SYSTEM READS AND WRITES IN
INDUSTRY-COMPATIBLE FORMAT. TMll/TU/ElO DRIVES SUPPORT 10.5-INCH
REELS CONTAINING UP TO 2400 FEET OF TAPE UPON WHICH OVER 180
MILLION BITS OF DATA CAN BE STORED ON HIGH DENSITY 9-TRACK TAPE
OR OVER 140 MILLION BITS CAN BE STORED ON HIGH DENSITY 7-TRACK
TAPE. TMAll/TS03 DRIVES SUPPORT 7-INCH REELS CONTAINING UP TO
600 FEET OF TAPE IN HIGH DENSITY 9-TRACK FORMAT. TMBll/TUlOW
DRIVES ARE COMPATIBLE WITH TUIO DRIVES EXCEPT THEY OPERATE ONLY
ON 800 BPI, 9-TRACK TAPE.

* HOW MANY TM/TMA/TMBll MAGTAPE CONTROLLERS HAVE YOU [D R:0.-16.]
* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:

* ENTER VECTOR ADDRESS OF THE NEXT TM/TMA/TMBll? [0 R:60-774 D:224]:
* WHAT IS ITS CSR ADDRESS?

[0 R:160000-177700 D:172522]:

* HOW MANY DRIVES DOES IT HAVE? [D R:l.-8.]:
This query appears as many times as the
number
of
TM/TMA/TMBlls specified.
Note that the queries for the
interrupt vector, command register, and the number of drives
occur one after the other for each controller. The repeat
sequence repeats all three of the queries.
THE PCll IS A HIGH SPEED PAPER TAPE READER/PUNCH THAT IS
CAPABLE OF READING EIGHT-HOLE UNOILED PERFORATED PAPER TAPE AT
300 CHARACTERS PER SECOND, AND PUNCHING TAPE AT 50 CHARACTERS
PER SECOND.

3-52

SYSGEN DIALOGUE DETAILS

* HOW MANY PCll PAPER TAPE READER/PUNCHES DO YOU HAVE?

[D R:0.-16.]:

* DO YOU WANT THE DRIVERS TO BE LOADABLE? [YIN]:
The answer to this query determines whether both or neither
of the two paper tape drivers (PRDRV and PPDRV) are to be
loadable.

* ENTER VECTOR ADDRESS OF THE NEXT PCll? [0 R:60-774 D:70]:
* WHAT IS ITS CSR ADDRESS?

[0 R:160000-177700 0:177550]:

THE PRll IS A HIGH SPEED PAPER TAPE READER THAT IS CAPABLE OF
READING EIGHT-HOLE UNOILED PERFORATED PAPER TAPE AT 300
CHARACTERS PER SECOND.
EXCLUDE THE NUMBER OF PCIIIS, IF ANY,
FROM THE ANSWER TO THE NEXT QUESTION.

* HOW MANY PRll PAPER TAPE READERS DO YOU HAVE?

[D R:0.-16.]:

* DO YOU WANT THE DRIVER TO BE LOADABLE? [Y/N]:
* ENTER VECTOR ADDRESS OF THE NEXT PRll?

[0 R:60-774 D:70]:

* WHAT IS ITS CSR ADDRESS? [0 R:160000-177700 D:177550]:
NOTE
THE OPERATOR CONSOLE
VIA A DLll.

MUST

ATTACHED

THE DLll SERIES OF ASYNCHRONOUS SINGLE LINE INTERFACES HANDLE
FULL OR HALF DUPLEX COMMUNICATION BETWEEN A WIDE VARIETY OF
SERIAL COMMUNICATION CHANNELS AND A PDP-II COMPUTER.
WITH A DLll INTERFACE, A PDP-II COMPUTER CAN COMMUNICATE WITH A
LOCAL TERMINAL SUCH AS A CONSOLE TELEPRINTER.
INCLUDE CONSOLE IN THE ANSWER TO
THE NEXT QUESTION.

* ENTER NUMBER OF DLll LINE INTERFACES [D R: 1.-8.]:
For RSX-IIM systems, at least one DLll must be
generated
in
the
system;
there is no DLll
requirement f?r RSX-IIS systems. If the answer to
this query 1S nonzero, then the next three queries
appear. Otherwise they are not displayed.
The driver services terminals that are connected to a
DLII-A/B/C/DjW only. The DLII-E requires a separate
driver.
THE TERMINAL DRIVER CAN ONLY BE LOADED BY VMR.

* DO YOU WANT THE DRIVER TO BE LOADABLE? [Y/N]:
60 IS THE STANDARD VECTOR ADDRESS FOR THE FIRST DLll.
ADDITIONAL VECTORS ARE ASSIGNED FROM THE FLOATING VECTOR SPACE
STARTING AT 300. CONSULT FIELD SERVICE TO DETERMINE LOCATIONS
IF UNKNOWN.

* ENTER VECTOR ADDRESS OF THE NEXT DLll [0 R:60-774 D:60]:
3-53

SYSGEN DIALOGUE DETAILS
177560 IS THE STANDARD CSR ADDRESS FOR THE FIRST DLll.
ADDITIONAL DLII CSR ADDRESSES ARE ASSIGNED IN THE RANGE 176000
TO 176770. CONSULT FIELD SERVICE TO DETERMINE LOCATIONS IF
UNKNOWN.

* WHAT IS ITS CSR ADDRESS? [0 R:160000-177700 D:177560]:
THE DHll MULTIPLEXER CONNECTS THE PDP-II WITH 16 ASYNCHRONOUS
SERIAL COMMUNICATIONS LINES OPERATING WITH INDIVIDUALLY
PROGRAMMABLE PARAMETERS. THESE PARAMETERS ARE:
TRANSMITTER SPEED (BAUD)
RECEIVER SPEED (BAUD)

* ENTER NUMBER OF DHll ASYNCHRONOUS LINE MULTIPLEXERS [D R:0.-16.]:
THE TERMINAL DRIVER CAN ONLY BE LOADED BY VMR.

* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
If a DLll has been included in the system,
the loadable
driver question will be suppressed because these controllers
are supported by the same driver.
REMOTE LINES WILL OCCUpy CONSECUTIVE LINE LOCATIONS, AND IF
MORE THAN 16 REMOTE LINES ARE SPECIFIED THEY MUST ALSO OCCUpy
CONSECUTIVE DHll'S. ASSIGNMENT OF LINES IS BY GROUPS OF 4.
Note that in the following question, x
times the number of DHlls specified.

replaced

* ENTER TOTAL NUMBER OF DIAL UP LINES [D R:O.-x.]:
If the reply to this question is zero, the next two queries
are omitted.
If DMII-BB modem support is selected, the
initial dial-in terminal baud rate must be specified.
The
available baud rates are 110, 150, or 300. The selected
baud rate applies to all dial-in lines serviced by any
DMII-BB.
THE BAUD RATE AT WHICH ALL REMOTE LINES ARE ANSWERED MAY BE SET
TO 110, 150, OR 300 BAUD.

* DO YOU WANT TO ANSWER AT 110 BAUD? [YIN]:
* DO YOU WANT TO ANSWER AT 150 BAUD? [YIN]:
If both of these queries are answered
initial dial-in baud rate is set to 300.

negatively,

LOCAL LINES WILL ALSO OCCUpy CONSECUTIVE LINES AND DHll'S.
THEIR ASSIGNMENT FOLLOWS THE ASSIGNMENT OF ANY REMOTE LINES
SPECIFIED.
LOCAL LINES CAN BE EITHER EIA OR 20 MILLIAMP. EACH TYPE MUST
HAVE AN APPROPRIATE INTERFACE, AND THE INTERFACE SERVICES A
GROUP OF FOUR LINES OF THE SAME TYPE. THE RESPONSE TO THE
LOCAL LINE QUERY MAY BE LARGER THAN THE ACTUAL NUMBER OF LOCAL
LINES, SINCE ALLOCATION IS BY GROUPS OF FOUR. HENCE IF SIX EIA
LINES ARE INSTALLED, TWO LINE GROUP SLOTS, WHICH CONTAIN EIGHT
LINES, ARE NEEDED.
THE REQUIRED RESPONSE TO THE LOCAL LINE QUERY CAN BE CALCULATED
BY SUMMING THE NUMBER OF EIA AND 20 MILLIAMP LINE GROUPS (EACH

3-54

the

SYSGEN DIALOGUE DETAILS

LINE GROUP CONTAINS SLOTS FOR FOUR LINES) AND MULTIPLYING BY
FOUR.
Note that in the following question, x is replaced by 16
times the number of DHlls minus the number of dial-up lines.

* ENTER TOTAL NUMBER OF LOCAL LINES [D R:O.-x.]:
THE VECTOR ADDRESS FOR THE DHll IS ASSIGNED FROM THE FLOATING
VECTOR SPACE STARTING AT 300. CONSULT FIELD SERVICE TO
DETERMINE THE LOCATION IF UNKNOWN.

* ENTER VECTOR ADDRESS OF THE NEXT DHll [0 R:300-774]:
THE CSR ADDRESS FOR THE DHll IS ASSIGNED FROM THE FLOATING
ADDRESS SPACE STARTING AT 160010. CONSULT FIELD SERVICE TO
DETERMINE THE LOCATION IF UNKNOWN.

* WHAT IS ITS CSR ADDRESS?

[0 R:160000-177700]:

THE VECTOR ADDRESS FOR THE DMII-BB IS ASSIGNED FROM THE
FLOATING VECTOR SPACE STARTING AT 300. CONSULT FIELD SERVICE
TO DETERMINE THE LOCATION IF UNKNOWN.
IF A USER HAS SPECIFIED
THE EXISTENCE OF REMOTE DIAL-UP LINES THE DMII-BB INTERFACE IS
REQUIRED. ONE DMII-BB CAN SERVICE UP TO 16 REMOTE DIAL-UP
LINES.

* ENTER VECTOR ADDRESS OF THE NEXT DMII-BB

R:300-744]:

If the reply to the query for the number of remote lines was
nonzero, this query is repeated for each DMll-BB that is
required.

* WHAT IS ITS CSR ADDRESS?

[0 R:16000-177700 D:170500]:

If the reply to the query for the number of remote lines was
nonzero,
this query is repeated for each DMll-BB that is
required. Note that the queries for remote dial-up lines,
local lines, DHll interrupt vector, DHll CSR, DMII-BB
interrupt vector, and DMll-BB CSR occur one after the other
for each DHll.
The repeat sequence repeats all 6 of the
queries as appropriate.
THE DJll IS A MULTIPLEXER INTERFACE BETWEEN 16 ASYNCHRONOUS
SERIAL DATA-COMMUNICATION CHANNELS AND THE PDP-II UNIBUS. THE
DJll IS A UNIT WHOSE CHARACTER FORMATS AND OPERATING SPEEDS ARE
JUMPER OR STRAP SELECTABLE IN GROUPS OF FOUR LINES.

* ENTER NUMBER OF DJll ASYNCHRONOUS LINE MULTIPLEXERS

[D R:0.-16.]:

THE TERMINAL DRIVER CAN ONLY BE LOADED BY VMR.

* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
If a DLll or DHll has been included in the system,
the
loadable driver question will be suppressed because these
controllers are supported by the same driver.
THE VECTOR ADDRESS FOR THE DJll IS ASSIGNED FROM THE FLOATING
VECTOR SPACE STARTING AT 300. CONSULT FIELD SERVICE TO
DETERMINE THE LOCATION IF UNKNOWN.

* ENTER VECTOR ADDRESS OF THE NEXT DJll

3-55

[0 R:300-774]:

SYSGEN DIALOGUE DETAILS
If the reply to the query for the number of
nonzero, this query is repeated for each DJll.

DJlls

was

THE CSR ADDRESS FOR THE DJll IS ASSIGNED FROM THE FLOATING
ADDRESS SPACE STARTING AT 160010. CONSULT FIELD SERVICE TO
DETERMINE THE LOCATION IF UNKNOWN.

* WHAT IS ITS CSR ADDRESS? [0 R: 160010-177700]:
* HOW MANY LINES DOES IT HAVE? [D R:l.-16.]:
This query appears as many times as the number of DJlls
specified.
Note that the queries for the interrupt vector,
CSR, and the number of lines occur one after the other for
each DJll.
The repeat sequence repeats all three of the
queries.
THE DZll MULTIPLEXER CONNECTS THE PDP-II WITH 8 ASYNCHRONOUS
SERIAL COMMUNICATIONS LINES OPERATING WITH INDIVIDUALLY
PROGRAMMABLE PARAMETERS. THESE PARAMETERS ARE:
TRANSMITTER SPEED (BAUD)
RECEIVER SPEED (BAUD)
THE DZIl-E MULTIPLEXER SHOULD BE TREATED AS TWO Dzll' 'So THUS IF
YOU HAVE 1 DZll-E ANSWER THE NEXT QUESTION WITH 2.

* ENTER NUMBER OF DZll ASYNCHRONOUS MULTIPLEXERS

[D R:0.-16.]:

THE TERMINAL DRIVER CAN ONLY BE LOADED BY VMR.

* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
If a DLll, DHll, or DJll has been included in the system,
the loadable driver question will be suppressed because
these controllers are supported by the same driver.
THE DZll HAS THE ABILITY TO MAINTAIN A FULL DUPLEX CONNECTION
THROUGH A BELL 103A TYPE MODEM. MODEM SUPPORT REQUIRES ADDED
CODE IN THE TERMINAL DATA BASE AS WELL AS IN THE DRIVER, AND
@NCVEASES SYSTEMIOVERHEAD. AS A RESULT, IT SHOULD BE SELECTED
ONLY IF NEEDED.

* DO ANY OF THE LINES REQUIRE MODEM SUPPORT? [YIN]:
If the reply to this question is negative, the next two
questions are omitted.
If modem support is selected, the
initial dial-in terminal baud rate must be specified.
The
available baud rates are 110, 150, or 300. The selected
baud rate applies to all dial-in lines serviced by any DZll.
THE BAUD RATE AT WHICH ALL REMOTE LINES ARE ANSWERED MAY BE SET
TO 110, 150, OR 300 BAUD.

* DO YOU WANT TO ANSWER AT 110 BAUD? [YIN]:
* DO YOU WANT TO ANSWER AT 150 BAUD? [YIN]:
If both of these queries are answered
initial dial-in baud rate is set to 300.

negatively,

THE VECTOR ADDRESS FOR THE DZll IS ASSIGNED FROM THE FLOATING
VECTOR SPACE STARTING AT 300. CONSULT FIELD SERVICE TO
DETERMINE THE LOCATION IF UNKNOWN.

3-56

the

SYSGEN DIALOGUE DETAILS

* ENTER VECTOR ADDRESS OF THE NEXT DZll [0 R:300-774]:
THE CSR ADDRESS FOR THE DZll IS ASSIGNED FROM THE FLOATING
ADDRESS SPACE STARTING AT 160010. CONSULT FIELD SERVICE TO
DETERMINE THE LOCATION IF UNKNOWN.

* what is its csr address? [0 r:160010-177700]:
* HOW MANY LINES DOES IT HAVE? [D R:l.-8.]:
INTER-PROCESSOR COMMUNICATION DEVICES CONSIST OF THE FOLLOWING:
- DAII-B HIGH-SPEED PARALLEL UNIBUS LINK
DLII-E ASYNCHRONOUS SERIAL LINE INTERFACE
DMCll SYNCHRONOUS SERIAL LINE INTERFACE
DPll SYNCHRONOUS SERIAL LINE INTERFACE
DQll HIGH-SPEED SYNCHRONOUS SERIAL LINE INTERFACE
DUll SYNCHRONOUS SERIAL LINE INTERFACE
DUPll SYNCHRONOUS SERIAL LINE INTERFACE

* DO YOU HAVE ANY INTER-PROCESSOR COMMUNICATION DEVICES?
If you do, the pertinent queries concerning
communication devices are asked.

[YIN]:

inter-processor

THE DAII-B UNIBUS LINK IS A HIGH-SPEED, HALF-DUPLEX CHANNEL FOR
CONNECTING TWO PDP-II COMPUTERS OVER A DISTANCE OF UP TO 100
FEET (30 METERS). USING THE DIRECT-MEMORY-ACCESS FACILITIES OF
EACH COMPUTER, IT IS CAPABLE OF TRANSFERING BLOCKS OF DATA AT
HIGH DATA RATES WITH MINIMAL PROCESSOR OVERHEAD.

* HOW MANY DAII-B PARALLEL LINE INTERFACES DO YOU HAVE

[D R:0.-16.]:

* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
* ENTER VECTOR ADDRESS OF THE NEXT DAII-B [0 R:60-774 D:124]:
* WHAT IS ITS CSR ADDRESS?

[0 R:160000-177700 D:172414]:

THE DLII-E SERIES OF ASYNCHRONOUS SINGLE LINE INTERFACES HANDLE
FULL OR HALF DUPLEX COMMUNICATION BETWEEN A WIDE VARIETY OF
SERIAL COMMUNICATION CHANNELS AND A PDP-II COMPUTER.

* HOW MANY DLII-E ASYNC. LINE INTERFACES DO YOU HAVE? [D R:0.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
THE VECTOR ADDRESS FOR THE DLII-E IS ASSIGNED FROM THE FLOATING
VECTOR SPACE STARTING AT 300.
CONSULT FIELD SERVICE TO
DETERMINE THE LOCATION IF UNKNOWN.

* ENTER VECTOR ADDRESS OF THE NEXT DLII-E

[0 R:300-774]:

THE CSR ADDRESS FOR THE DLII-E IS ASSIGNED FROM THE ADDRESS
SPACE STARTING AT 175610. CONSULT FIELD SERVICE TO DETERMINE
THE LOCATION IF UNKNOWN.

* WHAT IS ITS CSR ADDRESS?
* IS IT A HALF DUPLEX LINE?

[0 R:175610-177700]:

[YIN]:

* HOW MANY SYNC CHAR.S ARE REQUIRED IN A SYNC LEADER?

3-57

[D R:3.-14.]:

SYSGEN DIALOGUE DETAILS
A typical response is 4-6.
If the line is to run at high
speeds or
the expected system load is to be heavy, then
specify a greater number of sync characters.
If the reply to the query for
the number of DLII-Es was
greater than 1,
this query is repeated for each DLII-E.
Note that the queries for
interrupt vector, CSR, half
duplex, and sync leader occur one after the other for each
DLII-E. The repeat sequence repeats all four queries.
THE DMCll IS A FULL-DUPLEX, SERIAL COMMUNICAITONS LINK WHICH
IMPLEMENTS THE DDCMP LINE PROTOCOL USING A HIGH SPEED
MICROPROCESSOR. DATA MESSAGES ARE TRANSFERRED WITH MINIMAL
PROCESOR OVERHEAD USING THE DMA FACILITIES OF THE PDP-II.

* HOW MANY DMCll SYNC. LINE INTERFACES DO YOU HAVE? [D R:0.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:

THE VECTOR ADDRESS FOR THE DMCll IS ASSIGNED FROM THE FLOATING
VECTOR SPACE STARTING AT 300.
CONSULT FIELD SERVICE TO
DETERMINE LOCATION IF UNKNOWN.

* ENTER VECTOR ADDRESS OF THE NEXT DMCll [0 R:300-774]:
THE CSR ADDRESS FOR THE DMCll IS ASSIGNED FROM THE FLOATING
ADRESS SPACE STARTING AT 160010. CONSULT FIELD SERVICE TO
DETERMINE LOCATION IF UNKNOWN.

* WHAT IS ITS CSR ADDRESS? [0 R:160010-177700]:
* IS IT A HALF DUPLEX LINE? [YIN]:
The vector address, CSR address, and half
are repeated for each DMCll specified.

duplex

If the answer to the half duplex question is
next query is omitted.

questions

negative,

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.

* IS IT THE PRIMARY STATION? [YIN]:
THE DPll PROVIDES A DOUBLE-BUFFERED PROGRAM INTERRUPT INTERFACE
BETWEEN A PDP-II AN A SERIAL SYNCHRONOUS LINE.
THE DPll INTERFACE HANDLES A WIDE VARIETY OF TERMINALS AND LINE
DISCIPLINES (I.E., LINE CONTROL PROCEDURES AND ERROR CONTROL
TECHNIQUES). A PROGRAMMER CAN VARY SYNC CHARACTER, CHARACTER
SIZE, AND MODEM CONTROL LEADS. AUTOMATIC SYNC CHARACTER
STRIPPING AND AUTOMATIC IDLING ARE ALSO PROGRAM SELECTABLE.
WHILE IDLING, THE DPll TRANSMITS THE CONTENTS OF THE SYNC BUFFER.

* HOW MANY DPll SYNC LINE INTERFACES DO YOU HAVE? [0 R:0.-16.]:
THE VECTOR ADDRESS FOR THE DPll IS ASSIGNED FROM THE FLOATING
VECTOR SPACE STARTING AT 300.
CONSULT FIELD SERVICE TO
DETERMINE LOCATION IF UNKNOWN.

* ENTER VECTOR ADDRESS OF THE NEXT DPll

[0 R:300-774]:

* WHAT IS ITS CSR ADDRESS? [0 R:160000-177700 D:174770]:
* IS IT A HALF DUPLEX LINE? [YIN]:

* HOW MANY SYNC CHAR.S ARE REQUIRED IN A SYNC LEADER? [D R:3.-14.]:

3-58

the

SYSGEN DIALOGUE DETAILS
A typical response is 4-6.
If the line is to run at high
speeds or
the expected system load is to be heavy, then
specify a greater number of sync characters.
If the reply to the query for
the number of DPlls was
greater
than 1, this query is repeated for each DPll.
Note
that the queries for interrupt vector, CSR, half duplex, and
sync leader occur one after the other for each DPll.
The
repeat sequence repeats all four queries.
THE DQll IS A HIGH-SPEED, DOUBLE BUFFERED COMMUNICATIONS DEVICE
DESIGNED TO INTERFACE THE PDP-II PROCESSOR TO A SERIAL
SYNCHRONOUS COMMUNICATION LINE.
USING THE DIRECT-MEMORY-ACCESS
FACILITIES OF THE PDP-II, IT IS CAPABLE OF TRANSFERING BLOCKS
OF DATA AT HIGH DATA RATES WITH MINIMAL PROCESSOR OVERHEAD.

* HOW MANY DQll SYNC. LINE INTERFACES DO YOU HAVE? [0 R: 0.-16.]:
* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
THE VECTOR ADDRESS FOR THE DQll IS ASSIGNED FROM THE FLOATING
VECTOR SPACE STARTING AT 300.
CONSULT FIELD SERVICE TO
DETERMINE LOCATION IF UNKNOWN.

* ENTER VECTOR ADDRESS OF THE NEXT DQll

[0 R:300-774]:

THE CSR ADDRESS FOR THE DQll IS ASSIGNED FROM THE FLOATING
ADDRESS SPACE STARTING AT 160010.
CONSULT FIELD SERVICE TO
DETERMINE LOCATION IF UNKNOWN.

* WHAT IS ITS CSR ADDRESS? [0 R:1600l0-l77700]:
* IS IT A HALF DUPLEX LINE? [YIN]:
* DOES IT HAVE THE ERROR DETECTION EXPANDER UNIT? [YIN]:
* DOES IT HAVE THE CHARACTER DETECTION EXPANDER UNIT? [YIN]:
* HOW MANY SYNC CHAR.S ARE REQUIRED IN A SYNC LEADER? [D R:3.-l4.]:
A typical response is 4-6.
If the line is to run at high
speeds or
the expected system load is to be heavy, then
specify a greater number of sync characters.
If the reply to the query for
the number of DQlls was
greater
than 1, this query is repeated for each DQll.
Note
that the queries for interrupt vector, CSR,
half duplex,
error detection, character detection, and sync leader occur
one after the other for
each DQll.
The repeat sequence
repeats all six queries.
THE DUll PROVIDES A DOUBLE-BUFFERED PROGRAM INTERFACE BETWEEN A
PDP-II AND A SERIAL SYNCHRONOUS LINE.
THE DUll PROVIDES A FLEXIBLE INTERFACE IN THAT THE PROGRAMMER
CAN SPECIFY THE SYNC AND CHARACTER SIZE.
MODEM CONTROL
CAPABILITY ALLOWS THE USE OF THE DUll IN SWITCHED OR DEDICATED
APPLICATIONS.
THE INTERFACE PROVIDES STRIP SYNC AND IDLE SYNC
FEATURES TO SIMPLIFY PROGRAMMING AND REMOVE PROCESSOR OVERHEAD.

* HOW MANY DUll SYNC.

LINE INTERFACES DO YOU HAVE? [0 R:0.-16.]:

* DO YOU WANT THE DRIVER TO BE LOADABLE? [YIN]:
THE VECTOR ADDRESS FOR THE DUll IS ASSIGNED FROM THE FLOATING
VECTOR SPACE STARTING AT 300.
CONSULT FIELD SERVICE TO
DETERMINE THE LOCATION IF UNKNOWN.

* ENTER VECTOR ADDRESS OF THE NEXT DUll [0 R:300-774]:
3-59

SYSGEN DIALOGUE DETAILS

THE CSR ADDRESS FOR THE DUll IS ASSIGNED FROM THE FLOATING
ADDRESS SPACE STARTING AT 160010. CONSULT FIELD SERVICE TO
DETERMINE LOCATION IF UNKNOWN.

* WHAT IS ITS CSR ADDRESS? [0 R:160010-177700]:

* IS IT A HALF DUPLEX LINE? [YIN]:
* HOW MANY SYNC CHAR.S ARE REQUIRED IN A SYNC LEADER? [D R:3.-14.]:
A typical response is 4-6.
If the line is to run at high
speeds or the expected system load is to be heavy, then
specify a greater number of sync characters.
If the reply to the query for
the number of DUlls was
greater than 1, this query is repeated for each DUll. Note
that the queries for interrupt vector, CSR, half duplex, and
sync leader occur one after the other for each DUll. The
repeat sequence repeats all four queries.
THE DUPll PROVIDES A DOUBLE-BUFFERED PROGRAM INTERFACE BETWEEN A
PDP-II AND A SERIAL SYNCHRONOUS LINE.
THE DUPll PROVIDES A FLEXIBLE INTERFACE IN THAT THE PROGRAMMER
CAN SPECIFY THE SYNC AND CHARACTER SIZE. MODEM CONTROL
CAPABILITY ALLOWS THE USE OF THE DUPll IN SWITCHED OR DEDICATED
APPLICATIONS. THE INTERFACE PROVIDES STRIP SYNC AND IDLE SYNC
FEATURES TO SIMPLIFY PROGRAMMING AND REMOVE PROCESSOR OVERHEAD.

* HOW MANY DUPII SYNC.

LINE INTERFACES DO YOU HAVE? [D R:0.-16.]:

* DO YOU WANT THE DRIVER TO BE LOADABLE?

[YIN]:

THE VECTOR ADDRESS FOR THE DUPII IS ASSIGNED FROM THE FLOATING
VECTOR SPACE STARTING AT 300. CONSULT FIELD SERVICE TO
DETERMINE THE LOCATION IF UNKNOWN.

* ENTER VECTOR ADDRESS OF THE NEXT DUPII

[0 R:300-774]:

THE CSR ADDRESS FOR THE DUPII IS ASSIGNED FROM THE FLOATING
ADDRESS SPACE STARTING AT 160010. CONSULT FIELD SERVICE TO
DETERMINE LOCATION IF UNKNOWN.

* WHAT IS ITS CSR ADDRESS?

[0 R:160010-177700]:

* IS IT A HALF DUPLEX LINE? [YIN]:

* HOW MANY SYNC CHAR.S ARE REQUIRED IN A SYNC LEADER?

[D R:3.-14.]:

A typical response is 4-6.
If the line is to run at high
speeds or the expected system load is to be heavy, then
specify a greater number of sync characters.
The vector address, CSR address, half duplex, and sync
character questions are repeated for each DUPII specified.
END PERIPHERAL OPTIONS
There is a significant delay at this point while device
tables are generated for the null device and network device
(if selected)
and tables for
all
of
the
standard
pseudo-devices.

AT THIS POINT WE RENAME THE ASSEMBLY COMMAND FILE
AND THE SYSTEM BUILD COMMAND FILE TO [11,2x]

3-60

SYSGEN DIALOGUE DETAILS
;

PIP [11,2x]/RE=RSXASM.CMD;*,RSXBLD.CMD;*
SGN runs under UIC [11,10] and produces five files which are
recorded in the [11,10] file directory.
Command files are
conventionally stored in [11,20] or [11,24]. The preceding
PIP commands, only one of which is actually issued, puts the
command files into the proper directory.
* DID YOU ANSWER THE SYSGEN QUESTIONS TO YOUR SATISFACTION? [YIN]:
If, for any reason,
the query section dialogue included
responses that would result in a user-tailored Executive
which did not reflect the user's intentions, an N response
to this query causes the files created by the query section
to be deleted and the query section restarted.
If
the
response is N, the following lines are displayed:
IF YOU HAVE A REASONABLY GOOD UNDERSTANDING OF RSX-llM AND THE
SYSGEN PROCESS (AIDED BY LISTING OF SGNEXEC, SGNPER, AND SGNTT)
YOU CAN CORRECT MOST MINOR ERRORS BY EDITING THE FOLLOWING FILES:
[ll,lO]RSXMC.MAC - EXECUTIVE OPTIONS, PERIPHERAL COMPONENTS
[ll,lO]SYSTB.MAC - PERIPHERAL'S DATA BASES (DCB'S,UCB'S,SCB'S)
[11,2X]RSXASM.CMD - TO CHANGE LISTING DEVICE, ETC.
[11,2X]RSXBLD.CMD - TO CHANGE MAP DEVICE, ETC.
NOTE THAT CORRECTING ICS/ICR-ll AND UDC ERRORS BY EDITING IS NOT
RECOMMENDED.
THE ALTERNATIVE TO EDITING THESE FILES IS TO RUN THROUGH THE ENTIRE
QUERY SECTION AGAIN.
* DO YOU WANT TO RESTART THE QUERY SECTION? [YIN]:
If you do not want to
displays

restart

the

query

section,

SYSGEN

WE WILL PAUSE SO YOU CAN EDIT THE FILES.
Otherwise, the query section is restarted.
If no errors occurred during the running of the three
files, SYSGEN processing continues here.

query

IF YOU ARE BUILDING A SPECIALIZED SYSTEM YOU
MAY WISH TO EDIT THE FILES WHICH ARE PRODUCED
BY THE QUERY SECTION.
;

* DO YOU WANT TO EDIT ANY OF THE QUERY SECTION OUTPUT FILES? [YIN]:
If the answer is Y, SYSGEN will pause to let you edit the
output files.
When you are finished editing, type RES AT.
to continue SYSGEN.
If LP:, NL:, or SY: was specified as
the next section is bypassed.

* IS DK1:

the

In the following lines it is
specified as the listing device.

assumed

ALREADY INITIALIZED AND MOUNTED?

[YIN]:

3-61

listing
that

device,

DK1:

was

SYSGEN DIALOGUE DETAILS

If it has been, the queries concerning it are skipped.
ALL DKl:
DMO DKl:
PLACE A FORMATTED DISK IN DKl:

(WRITE-ENABLED).

;

* IS THE DISK READY IN DKl:? [Y/N]
This question causes the indirect file processor to suspend
itself until the disk reaches operating speed. When the
disk is ready, the user answers Y to this question.

* IS THE DISK IN DKl: INITIALIZED AS A FILES-II VOLUME? [Y/N]:
* WHAT IS ITS LABEL? [S]:
If the disk is not initialized, an N answer will cause the
disk to be initialized by the following commands, which
install task INI, initialize the disk, and then remove INI.
If the disk is already initialized, processing continues
with the Mount (MOU) command.
INS [1,5y]INI
INI DKl:LIST/BAD=[AUTO]
REM INI
Whether or not the disk needs to
processing continues at this point.

initialized,

DKl:

MOU DKI:LIST
MOU DKl:/OVR
INS [1,5y]UFD
SET /UIC=[l,l]
UFD DKl: [11,3x]
REM UFD

* WAS DKl: MOUNTED SUCCESSFULLY? [Y/N]:
* WAS THE UFD CREATED (OR ALREADY ON THE DISK)? [Y/N]:
If any error messages appeared when the MOU and UFD commands
were issued, the user answers N to this question, and
processing resumes with the
SYSGEN
prompt
IS
DKl:
INITIALIZED AND MOUNTED, as given above.
Processing continues at this point.
NOW WE ASSEMBLE THE EXECUTIVE
INS $MAC
INS $BIGMAC/PAR=PAR14K
The proper version of MACRO-II is installed, according to
whether or not the host system has at least 24K of memory.
BIGMAC is the assembler of choice in this case, and is
always chosen when at least 24K of memory is available.
ASSEMBLING THE EXECUTIVE TAKES ANYWHERE FROM 20
MINUTES (ON AN 11/70) TO 2 HOURS (ON AN 11/10).
TAKE A BREAK.

3-62

SYSGEN DIALOGUE DETAILS

SET /UIC=[11,2x]
TIM
MAC @RSXASM
TIM
UNL LP:
The SET command establishes the default UIC.
MACRO-II
is
requested to run with RSXASM as an indirect command file.
Note that MACRO-II is running under [11,20] or [11,24] and,
since RSXASM is part of an indirect file request, .CMD is
the default file type. The assembly will require from 20
minutes to 2 hours to complete, depending upon the hardware
available and the configuration of the target system.
If the DSS-ll and/or UDC-ll or ICS/ICR-ll was selected for
the target system,
the following text and commands are
displayed:
NOW WE ASSEMBLE THE MODULES NECESSARY FOR TASKS TO ACCESS
UDC-ll, DSS-ll OR ICS/ICR-ll I/O MODULE REGISTERS WITHIN
THE I/O PAGE.
I/O MODULE TYPES ACCESSED DIRECTLY ARE:
ICS/ICR-ll:
DIGITAL INPUT
COUNTER INPUT
DSS-ll INPUTS
UDe-ll:
ANALOG OUTPUTS
SINGLE SHOT DIGITAL OUTPUTS
DIGITAL INPUTS
COUNTER INPUTS
If the ICS/ICR-ll was selected, the
asked:

following

question

* IS DIRECT ACCESS TO ICS/ICR-ll I/O MODULES REQUIRED? [Y/N]:
If the UDCll was selected, the following question is asked:

* IS DIRECT ACCESS TO UDC-ll I/O MODULES REQUIRED? [Y/N]:
If either of these questions is answered Y or
if DSS-ll
support was included, the following text is displayed:
IN AN UNMAPPED SYSTEM ACCESS TO I/O MODULES IS
THROUGH UNRESTRICTED REFERENCE TO THE I/O PAGE
OR VIA A GLOBAL COMMON BLOCK THAT OCCUPIES THE SET
OF PHYSICAL LOCATIONS RESERVED FOR THE DEVICE REGISTERS. IF YOU WISH TO ACCESS THE DEVICE THROUGH THE
COMMON BLOCK, YOU MUST EDIT THE FILE RSXMC.MAC UNDER
UFD [11,10], AS SHOWN IN THE FOLLOWING EXAMPLE:
Note, if you include the FORTRAN callable process I/O
routines (See the RSX-llM I/O Drivers Reference Manual), the
global common block is required. These are also required on
an unmapped system.
3-63

SYSGEN DIALOGUE DETAILS
For ICS/ICR-ll::
*PL I$$Cll
I$$Cll=O
*1 I$$COM=O
for DSS-ll:
*T
*PL I$$Sll
I$$Sll=l
*1 I$$SCM=O
FOR UDCll
*PL U$$Dll
U$$Dll=O
*1 U$$DCM=O
Finally:
*ED
In either case, the following question is asked:
* DO YOU HAVE TO EDIT FILE RSXMC.MAC? [Y/N]:
If this question is answered Y, the following
issued:

commands

are

INS [1,5y]EDI
EDI [ll,lO]RSXMC.MAC
You should now perform the required edits.
Editor
(EDI)
is then removed and the
assembled.

The Line Text
correct modules

REM EDI
MAC
MAC
MAC
MAC
MAC

[11,2x]ICTAB.ICR, [11,3x] ICTAB/-SP=[ll,lO] ICTAB
[11,2x]ICOM.ICR, [11,3x] ICOM/-SP=[ll,lO]RSXMC,ICOM
[11,2x]UDCOM.UDC, [11,3x]UDCOM/-SP=[11,lO]RSXMC,UDCOM
[11,2x]ISCOM.IDS, [11,3x] ISCOM/-SP=[ll,lO]RSXMC,ISCOM
[11,2x]DSSDI.IDS,[11,3x]DSSDI/-SP=[11,lO]RSXMC,DSSDI
Whether or not DSS-ll and/or UDC-ll or ICS/ICR-ll support is
selected, all processing continues here.

REM MAC
The disk for Exec listings is dismounted.
DMO DKl:
NOW WE BUILD THE CONCATENATED OBJECT MODULE FILE
FOR THE EXECUTIVE.
The assembly of the Executive results in the creation of a
number of individual object module files.
These individual
files can be concatenated into a single file with a
substantial savings in disk space. Later, during the build

3-64

SYSGEN DIALOGUE DETAILS
phase, the Task Builder processes a library produced from
this concatenated file to create the task image of the
user-tailored Executive.
PIP RSX.OBS=*.OBJ
PIP RSXIIM.OBJ/RE=RSX.OBS
PIP RSXllS.OBJ/RE=RSX.OBS
All existing object files cataloged under the default UFD
are concatenated as a result of this command. The file
RSX.OBS is then renamed RSXIIM.OBJ if an RSX-IIM system is
being generated, or RSXllS.OBJ if an RSX-llS system is being
generated.
At this point, processing of SYSGEN.CMD is dependent on the
type of distribution kit you are using. For those using the
single RK05 distribution kit, the queries and text under the
heading SECONDARY STORAGE FOR SINGLE RK05 are applicable.
For those using the dual RK05 distribution kit, the queries
and
text
under
the heading DUAL RK05 TRANSFER are
applicable. Those using any other distribution kit are
asked the next question, since all files, needed are on the
disk.
* DO YOU WANT TO GO DIRECTLY TO THE NEXT PHASE OF THIS SYSGEN?

[YIN):

Since all files needed for a SYSGEN reside on an RK06, RLOl,
RM03, or an RP disk, it is possible to invoke SYSGEN phase 2
immediately. If this question is answered Y,
the SYSGEN
phase 2 command file will be entered.
For RSX-IIM SYSGEN, the command file selected will be
[200,200)SYSGEN2.CMD.
For RSX-llS SYSGEN, the command file
selected will be [200,200]11SGEN.CMD. After phase 2,
the
command file will exit.
WHEN THIS COMMAND FILE IS FINISHED, YOU MAY CONTINUE WITH
THE NEXT PHASE OF THIS SYSGEN WITH THE FOLLOWING COMMAND:
@SYSGEN2
@llSGEN
If SYSGEN phase 2 on RP disk is not selected, it may be done
manually at a later time by following the directions given
at the end of the SYSGEN command file. At this point, RP
processing terminates and the command file will exit.
*****SECONDARY STORAGE*****
***FOR***
*****SINGLE RK05*****
For purposes of SYSGEN using the single RK05 distribution
kit,
the following section is necessary to determine the
secondary storage device. Secondary storage devices can be
one of the following:
1.

An RK05 disk

A cassette tape

A DECtape

3-65

SYSGEN DIALOGUE DETAILS
4.

A magtape

An RXOI floppy disk

Questions are asked until one of these configuration types
is established.
For disk-tape configurations, two files,
RSXBLD.CMD and RSXIIM.OBJ, must be copied to backup tape
for
later restoration to the object disk.
In addition, if
the UDC-II was included, the common block module UDCOM.UDC
must be copied.
If the ICS/ICR-II was included, the files
ICOM.ICR and ICTAB.ICR must be copied.
NOW WE COPY THE BUILD COMMAND FILE, THE ASSEMBLY PREFIX
FILE, THE UDC, DSS OR ICS/ICR FILES AND THE CONCATENATED
OBJECT MODULES TO SECONDARY STORAGE.
SET /UIC=[1,2x]

* IS YOUR SECONDARY STORAGE DEVICE AN RK05 DISK? [Y/N]:
The following instructions and commands are executed if
system has as a secondary storage device an RK05 disk.

the

* ENTER DEVICE FOR SECONDARY DISK [S]:
For the following commands, it is
that DKI:
is the device entered.

assumed

example,

PUT THE UNMAPPED OBJECT DISK IN DKI:
PUT THE MAPPED OBJECT DISK IN DKI:
AND MAKE SURE THAT THE DRIVE IS WRITE ENABLED.
;

* IS THE DISK IN DKI: READY? [Y/N]:
MOU DKI:MAPOBJ
MOU DKI:UNMOBJ
PIP DKI:/NV=[11,2x]RSXBLD.CMD,RSXIIM.OBJ
PIP DKI:/NV=[11,2x]RSXBLD.CMD,RSXIIS.OBJ
PIP DKI:/NV=[11,2x]UDCOM.UDC
PIP DKI:/NV=[11,2x]ICOM.ICR,ICTAB.ICR
PIP DKI:/NV=[11,2x]ISCOM.IDS,DSSDI.IDS
PIP DKI: [200,200]/NV=[II,IO]RSXMC.MAC
DMO DKI:
INS [1,5y]FLX
All other configurations, except the RXOl, require the File
Transfer Program
(FLX)
to copy the files to the medium.
Thus, the proper version of FLX is installed.

* IS YOUR SECONDARY STORAGE DEVICE A CASSETTE TAPE?

[Y/N]:

The following instructions and commands are executed if
system has as a secondary storage device cassette tape.
PUT A BLANK CASSETTE IN DRIVE 0
;

* IS THE BLANK CASSETTE IN DRIVE 0 READY? [Y/N]:
LOA CT:
FLX CT:/ZE
FLX CT:/VE/BS:512.=[11,2x]RSXBLD.CMD/RS,RSXIIM.OBJ
FLX CT:/VE/BS:512.=[11,2x]RSXBLD.CMD/RS,RSXIIS.OBJ
3-66

the

SYSGEN DIALOGUE DETAILS

FLX CT:/VE/BS:5l2.=[11,2x]UDCOM.UDC/FB/RS
FLX CT:/VE/BS:5l2.=[11,2x] ICTAB. ICR/RS/FB,ICOM. ICR/FB
FLX CT:/VE/BS:5l2.=[11,2x]DSSDI.IDS/RS/FB,ISCOM.IDS/FB
FLX CT:/VE/BS:5l2.=[11,lO]RSXMC.MAC/RS

* IS YOUR SECONDARY STORAGE DEVICE A DECTAPE? [YIN]:
The following instructions and commands are executed if
system has as a secondary storage device a DECtape.
PUT A BLANK DECTAPE IN DRIVE

the

;

* IS THE BLANK DECTAPE IN DRIVE 0 READY? [Y/N]:
LOA DT:
FLX DT:/ZE
FLX DT:/DO=[11,2x]RSXBLD.CMD/RS,RSXllM.OBJ
FLX DT:/DO=[11,2x]RSXBLD.CMD/RS,RSXllS.OBJ
FLX DT:/DO=[11,2x]UDCOM.UDC/FB/RS
FLX DT:/DO=[11,2x] ICTAB. ICR/RS/FB, ICOM. ICR/FB
FLX DT:/DO=[11,2x]DSSDI.IDS/RS/FB,ISCOM.IDS/FB
FLX DT:/DO=[ll,lO]RSXMC.MAC/RS

* IS YOUR SECONDARY STORAGE DEVICE A MAGTAPE? [Y/N]:
The following instructions and commands are executed if the
system has as a secondary storage device a magtape (TUlO,
TS03, TU16).

MOUNT A MAGTAPE IN DRIVE 0

* IS THE MAGTAPE IN DRIVE ZERO READY? [YIN]:
* IS THE MAGTAPE DRIVE A TU16, TU45, or TE16? [Y/N]:
The device mnemonic for TU16 or TU45 magtape is MM.
The
device mnemonic for TUIO and TS03 is MT. This question is
used to select the proper sequence of commands.
In the following commands, MT: will be replaced by MM:
you answered Y to this question.

LOA MT:
FLX MT:/ZE
FLX MT:/DO=[11,2x]RSXBLD.CMD,RSXllM.OBJ
FLX MT:/DO=[11,2x]RSXBLD.CMD,RSXllS.OBJ
FLX MT:/DO=[11,2x]UDCOM.UDC/FB/RS
FLX MT:/DO=[11,2x] ICTAB. ICR/RS/FB,ICOM. ICR/FB
FLX MT:/DO=[11,2x]DSSDI.IDS/RS/FB,ISCOM.IDS/FB
FLX MT:/DO=[ll,lO]RSXMC.MAC/RS

* IS YOUR SECONDARY STORAGE DEVICE AN RXOI FLEXIBLE DISK? [Y/N]:
The following instructions and commands are executed if
system has as a secondary storage device a floppy disk.
LOA DX:
;

; PLACE A BLANK FLEXIBLE DISK IN DRIVE 0
;

* IS THE FLEXIBLE DISK IN DRIVE 0 READY? [Y/N]:
INS [1,5y]INI
INI DXO:SYSGEN

3-67

the

SYSGEN DIALOGUE DETAILS
REM INI
MOU DXO:SYSGEN
INS [1,5y]UFD
UFD DXO: [1,2x]
REM UFD
PIP DX:=[11,2x]RSXBLD.CMD,RSXIIM.OBJ
PIP DX:=[11,2x]RSXBLD.CMD,RSXIIS.OBJ
PIP DX:=[11,2x]UDCOM.UDC
PIP DX:=[11,2x]ICTAB.ICR,ICOM.ICR
PIP DX:=[11,2x]DSSDI.IDS,ISCOM.IDS
PIP DX:=[ll,lO]RSXMC.MAC
DMO DXO:
If none of the supported configurations is selected,
the
following text is displayed and the questions are repeated.
***
ERR 0 R
***
THE CONFIGURATION YOU ARE RUNNING ON IS NOT
A STANDARD SYSGEN CONFIGURATION. YOU MUST HAVE ONE OF
THE COMBINATIONS OF DEVICES SPECIFIED ABOVE. WE WILL
REPEAT THE CONFIGURATION QUESTIONS.
Normal processing continues
processing is completed.

here

after

specific

device

REM FLX
REM PIP
The FLX and PIP tasks are removed;
their function has been
completed, and they are removed to bring the system back to
its initial state.

DISMOUNT THE SYSTEM DISK AND MOUNT THE
UNMAPPED OBJECT DISK
MAPPED OBJECT DISK
IN DRIVE 0 AND BOOT IN THE SYSTEM ON THAT DISK
WHEN THE SYSTEM IS UP, SET THE TIME AND DATE
AND INITIATE THE INDIRECT COMMAND FILE
[200,200]SYSGEN2.CMD. FOR EXAMPLE:
[200,200]11SGEN.CMD.
FOR EXAMPLE:
>TIM 10:20 11/15/77
>@SYSGEN2
>@llSGEN
SET /UIC=[200,200]
*****DUAL RK05 TRANSFER*****
The indirect command file SGNXFER.CMD transfers control from
SYSGEN.CMD to Sysgen2.cmd.
This transfer
is necessary
because the files SYSGEN and SYSGEN2 are on different disks.
The unit that contains the EXECSRC disk is dismouned.
The
following assumes that the EXFCSRC disk was mounted in DKl:.
DMO DKl:

3-68

SYSGEN DIALOGUE DETAILS

REMOVE THE EXECSRC DISK FROM DKl:. BEFORE PROCEEDING TO THE NEXT
PHASE OF SYSGEN, YOU MUST COpy THE SYSTEM DISK.
IF YOU HAVEN'T
DONE SO ALREADY.
* HAVE YOU MADE A COpy OF THE SYSTEM DISK? [YIN]:
If you haven't made a copy, SGNXFER exits. To continue with
SYSGEN, you must manually re-start [200,200] SGNXFER.CMD on
the BASLINE disk.
WE WILL EXIT NOW SO YOU CAN COPY THE SYSTEM DISK. TO
CONTINUE WITH SYSGEN START [200,200]SGNXFER.CMD ON THE
BASLINE DISK.
If you have already copied the SYSTEM disk,
SGNXFER
continues.
The unit that contained the EXECSRC disk is
assigned to the pseudo device SY:
and the RKOS unit
containing the BASLINE disk is assigned to the pseudo device
LB: .
ASN DKl: = SY:
ASN DKN: = LB:
If you are generating
section is omitted.

RSX-IIM

system,

the

following

**RSX-IIS ONLY**
Note that if you are generating an RSX-IIS system and are
using the RSX-IIM dual RKOS distribution kit, this section
is omitted.
PUT THE lIS KIT DISK IN DKl: AND START IT UP (WRITE PROTECTED).
* IS THE lIS KIT DISK READY? [YIN]:
This question
response) .
MOU DKl: IISKIT
SET IUIC = [2,20]
PIP LB: [2,20] IUFINVIFO
DMO DKl:

repeated

until

the

disk

ready

SY: [2,20]*.*

**RSX-IIM AND RSX-IIS**
PUT THE SYSTEM DISK IN DKl: AND START IT UP (WRITE ENABLED).
* IS THE SYSTEM DISK READY? [YIN]:
This question is repeated until the disk is ready (Y
response) .
MOU DKl:SYSTEM
; DELETE MAPPED OR UNMAPPED OBJECT LIBRARIES AND BUILD FILES
SET IUIC=[1,2x]
For a mapped system, the unmapped system files are deleted.
PIP [ 1 , 20] * . * ; * ID E

3-69

SYSGEN DIALOGUE DETAILS
For an unmapped system, the mapped system files are deleted.
PIP [1,24]*.*;*/DE
SET /UIC=[1,5x]
PIP @LB: [200,200]COPYTSK
PIP /CO=LB:BADSYS.*,DSCSYS.*,PRESRV.*
; COPY SYSTEM OBJECT AND BUILD FILES FROM BASLINE DISK
SET /UIC=[1,2x]
The proper object files are then copied.
system, the PIP command is

For an RSX-llS

PIP /NV=LB:RSXBLD.CMD,RSXllS.OBJ
For an RSX-IIM system, the PIP command is
PIP /NV=LB:RSXBLD.CMD,RSX-IIM.OBJ
If support for ICS/ICR, UDC-ll, or DSS-11 was included, the
appropriate PIP commands are issued.
For ICS/ICR, the PIP command is
PIP /NV=LB:ICTAB.ICR,ICOM.ICR
For UDC-ll, the PIP command is
PIP /NV=LB:UDCOM.UDC
For DSS-ll, the PIP command is
PIP /NV=LB:DSSDI.IDS,ISCOM.IDS
PIP [200,200]/NV=LB: [200,200]RSXMC.MAC
* DO YOU WANT TO CONTINUE WITH THE NEXT PHASE OF SYSGEN!

[YIN]:

If you do not wish to continue, instructions for doing so
are given and SGNXFER exits. Otherwise, SGNXFER continues.
SET /UIC=[200,200]
The proper file is then invoked; SYSGEN2 for an RSX-IIM
system and 11SGEN for an RSX-llS system.
End of SYSGEN phase 1.

3.4

SYSGEN2.CMD FILE DETAILS

The user-tailored Executive is built under the direction of the
indirect file SYSGEN2.CMD.
At the completion of the assembly and
configuration phases, directions were given to the single RK05 user to
bootstrap from the proper object disk, set the time, and initiate the
indirect file SYSGEN2.CMD. The narrative which follows is a display
of the SYSGEN2.CMD file.
The conventions used in describing the
SYSGEN.CMD file apply.

3-70

SYSGEN DIALOGUE DETAILS
SYSGEN PART 2

COPYRIGHT (C) 1975, 1976, 1977
DIGITAL EQUIPMENT CORP., MAYNARD, MASS. 01754
BUILD THE EXECUTIVE AND ALL REQUIRED TASKS
EXPANDED COMMENTS PROVIDE A DESCRIPTION OF EVERY STEP IN THIS
SYSGEN2 COMMAND FILE. ON THE OTHER HAND, SHORT COMMENTS
PROVIDE VIRTUALLY NO EXPLANATORY TEXT.
;

* DO YOU WANT EXPANDED COMMENTS FOR SYSGEN PART 2? [YIN]:
As in SYSGEN Phase 1, expanded comments provide much
descriptive text which the experienced user may wish to
dispense with.
If you are using the single RK05 distribution kit, you must
copy the files from secondary storage to your object disk.
The following text and queries are not displayed if you are
using other than the single RK05 kit.
**SINGLE RK05 KIT ONLY**
THIS COMMAND FILE WILL PRODUCE THE TARGET SYSTEM ON THE DISK
PACK CURRENTLY MOUNTED AS SY:.
IT WILL REPLACE THE BASE-LINE
SYSTEM THAT YOU ARE CURRENTLY RUNNING. YOU MUST SAVE
THIS DISK BEFORE PROCEEDING ANY FURTHER IF YOU HAVEN'T
DONE SO ALREADY.
;

* DO YOU WANT TO CONTINUE WITH SYSGEN PART 2? [YIN]:
This question allows the user to exit in order to preserve
the disk before modifying it in building the target system.
NOW WE COpy THE EXEC BUILD FILE, THE ASSEMBLY PREFIX FILE, THE
UDC, DRSll/DSSll OR ICS FILES AND THE CONCATENATED EXECUTIVE OBJECT
MODULES FROM THE SECONDARY STORAGE MEDIUM TO THE SYSTEM DISK.
IF DURING SYSGEN PART 1 YOU ANSWERED THAT YOUR SECONDARY
STORAGE MEDIUM WAS AN RK DISK CARTRIDGE, THESE FILES
WERE COPIED TO THE SYSTEM DISK AT THAT TIME.
* ARE THE FILES ALREADY ON THIS DISK? [YIN]:
If they are not,
the indirect command file SYSGEN2A is
called to copy them.
If they are, SYSGEN2A is deleted. The
following dialogue actually comes from SYSGEN2A (it appears
only if you have not already copied the required files).
Three files, RSXBLD.CMD, RSXllM.OBJ, and RSXMC.MAC must be
on the system disk to complete SYSGEN phase 2.
In addition,
the files for
the UDC, DRS/DSSll, or ICR/ICS-ll common
blocks must also be on the system disk if user tasks are
going to access the device registers. For all kits except
the single RK05,
these files are already on the disk and
need not be copied. For the single RK05 distribution kit,
they must be transferred to the system disk. RSXBLD.CMD is
the command file that directs the
Task
Builder
in
constructing the user-tailored Executive. It was built by
the query section. RSXllM.OBJ is the concatenated object
module file produced by PIP from the user-tailored Executive
object modules during the assembly run following
the
completion of the dialogue program.
RSXMC.MAC is the
assembly prefix file produced by the query section.
It is

3-71

SYSGEN DIALOGUE DETAILS

used to control the assembly of options selected during the
running of the query section. They were saved on the backup
medium and now must be copied onto the object disk where
they will be used to build the user-tailored Executive. For
RP or RK06 system disks, this question will not be issued;
instead, control will pass immediately to the point where
the three files are purged and the Executive library is
created (under the leading All Kits).

* IS YOUR SECONDARY STORAGE DEVICE A CASSETTE TAPE? [YIN]:
If the host system is an RKOS-cassette system, the following
commands will copy the required files from cassette to the
system disk.
MOUNT THE CASSETTE FROM SYSGEN PART I IN DRIVE 0
;

* IS THE CASSETTE IN DRIVE 0 READY? [YIN]:
LOA CT:
INS $FLX
FLX SY:=CT:RSXIIM.OBJ,RSXBLD.CMD
FLX SY:=CT:ICTAB.ICR/FB,ICOM.ICR/FB
FLX SY:=CT:UDCOM.UDC/FB
FLX SY:=CT:ISCOM.IDS/FB,DSSDI.IDS/FB
FLX SY: [200,200]=CT:RSXMC.MAC
UNL CT:
End of RKOS-cassette commands. Control passes to the point
where the files are purged (under the leading ALL KITS).

* IS YOUR SECONDARY STORAGE DEVICE A DECTAPE? [YIN]:
If the host system is an RKOS-DECtape system, the following
commands will copy the specified files from DECtape to the
system disk.
MOUNT THE DECTAPE FROM SYSGEN PART I IN DRIVE 0
;

* IS THE DECTAPE IN DRIVE 0 READY? [YIN]:
LOA DT:
INS $FLX
FLX SY:=DT:RSXIIM.OBJ,RSXBLD.CMD
FLX SY:=DT:ICTAB.ICR/FB,ICOM.ICR/FB
FLX SY:=DT:UDCOM.UDC/FB
FLX SY:=DT:ISCOM.IDS/FB,DSSDI.IDS/FB
FLX SY: [200,200]=DT:RSXMC.MAC
UNL DT:
End of RKOS-DECtape commands. Control passes to the point
where the files are purged (under the leading ALL KITS).

* IS YOUR SECONDARY STORAGE DEVICE A MAGTAPE? [YIN]:
If the host system is an RKOS-magtape system, the following
commands will copy the specified files from magtape to the
system disk.
MOUNT THE MAGTAPE FROM SYSGEN PART I IN DRIVE 0
;

* IS THE MAGTAPE IN DRIVE 0 READY? [YIN]:

* IS THE MAGTAPE DRIVE A TUI6, TEl6 OR TU4S?
3-72

[YIN]:

SYSGEN DIALOGUE DETAILS

If the magtape is a
commands are issued:

TE16,

TU16

TU4S,

the

following

TUIO

TS03,

the

following

LOA MM:
INS $FLX
FLX SY:=MM:RSXIIM.OBJ,RSXBLD.CMD
FLX SY:=MM:ICTAB.ICR/FB,ICOM.ICR/FB
FLX SY:=MM:UDCOM.UDC/FB
FLX SY:=MM:ISCOM.IDS/FB,DSSDI.IDS/FB
FLX SY: [200,200]=MM:RSXMC.MAC
UNL MM:
If the magtape is a
commands are issued:

TEIO,

LOA MT:
INS $FLX
FLX SY:=MT:RSXIIM.OBJ,RSXBLD.CMD
FLX SY:=MT:ICTAB.ICR/FB,ICOM.ICR/FB
FLX SY:=MT:UDCOM.UDC/FB
FLX SY:=MT:ISCOM.IDS/FB,DSSDI.IDS/FB
FLX SY: [200,200]=MT:RSXMC.MAC
UNL MT:
End of RKOS-magtape commands. Control passes to the point
where the files are purged (under the leading ALL KITS) •

* IS YOUR SECONDARY STORAGE DEVICE AN RXOI FLEXIBLE DISK?

[YIN]:

If the host system is an RK floppy disk system,
the
following commands will copy the specified files from floppy
disk to the system disk.
LOA DX:
; MOUNT THE FLEXIBLE DISK FROM SYSGEN PART 1 IN DRIVE 0
;

* IS THE FLEXIBLE DISK IN DRIVE 0 READY? [Y/N]:
MOU DX:SYSGEN
PIP SY:/NV=DX:RSXIIM.OBJ,RSXBLD.CMD
PIP SY:/NV=DX:ICTAB.ICR,ICOM.ICR
PIP SY:/NV=DX:UDCOM.UDC
PIP SY:/NV=DX:ISCOM.IDS,DSSDI.IDS
PIP SY: [200,200]/NV=DX:RSXMC.MAC
DMO DX:
UNL DX:
End of RKOS-RXOI commands.
Control passes to the point
where the files are purged (under the heading ALL KITS) •
If none of the supported configurations is specified, the
following error message is issued and the questions are
repeated to determine the secondary storage medium used
during SYSGEN phase 1.

***

ERROR

***

YOU HAVE NOT CHOSEN ONE OF THE STANDARD SYSGEN SECONDARY
STORAGE DEVICES. WE WILL REPEAT THE QUESTIONS.
;

* WERE THE FILES COPIED SUCCESSFULLY? [Y/N]:

3-73

SYSGEN DIALOGUE DETAILS
If not, you may repeat the questions or pause so that you
may copy the files yourself.
If successful, SYSGEN2.CMD
continues.
**ALL KITS**
Note, if you are using the dual RK05 distribution kit,
you
must identify the RK05 units that contain the BASLINE and
SYSTEM disks.
Control passes to this location after
the
files RSXBLD.CMD, RSXIIM.OBJ, RSXMC.MAC and, conditionally,
ICTAB.ICR, ICOM.ICR, ISCOM.IDS, DSSDI.IDS, and UDCOM.UDC,
are copied to the system disk;
or, in the case of RP, RK06,
or dual RK05 disk systems, control passes to this location
immediately on determining the system type.
* HAVE YOU ALREADY BUILT THE EXEC?

[YIN]:

This question asks whether or not the Executive has been
linked together by the Task builder. SYSGEN phase 1 does
not link the Executive, it only assembles it.
Therefore,
the first time you encounter this question, it should be
answered negatively.
Typically, before a partition can be laid out,
the user
needs a Task Builder map of the newly built user-tailored
Executive. This occurs later in SYSGEN2.CMD and may require
a lengthy off-line analysis of partition layout for the
target system.
After analyzing the partition
layout,
SYSGEN2.CMD can be re-initiated.
If, at this point, an
affirmative answer is typed, the process of building the
user-tailored Executive is skipped, and SYSGEN2.CMD advances
to the dialogue for
the partitioning phase of system
generation.
DELETE ALL BUT THE LATEST VERSIONS OF THE TASK IMAGE
FILES FOR PIP, EDI, TKB, BIGTKB, VMR, AND BOO.
SET IUIC = [1,5x]
PIP PIP.TSK/PU EDI,TKB,BIGTKB,VMR,BOO
SYSGEN2 may, at a later stage, call SYSGEN3 to build new
versions of the task PIP, EDI, TKB, BIGTKB, VMR and BOO.
After having done so, SYSGEN2 must be able to install the
versions of these tasks which are, at this stage, the latest
versions. The PIP command above is executed to make a later
identification of those versions possible.
INS $LBR
If you are using an RLOI or either of the RK05
kits, the file IlSGEN.CMD is deleted.

distribution

PIP IlSGEN.CMD;*/DE
If ICS/ICR, DSS, or UDC support was not selected previously,
the next question is omitted.
* DO YOU WANT TO BUILD THE UDC, DSS OR ICS/ICR DEVICE COMMON BLOCK?
AS DISTRIBUTED ON THE OBJECT DISK, THE SYSTEM OBJECT
LIBRARY (SYSLIB) DOES NOT CONTAIN THE FORTRAN RUN TIME
SYSTEM MODULES FOR THE LPS-ll MODULES, THE PURDUE ISA MODULES
FOR THE UDC, DSSIIIDRSII OR ICS SUBSYSTEMS. THEY MUST BE
ADDED IF YOU PLAN TO USE THESE ROUTINES IN YOUR TARGET SYSTEM.
SET IUIC = [1,1]
3-74

[YIN]:

SYSGEN DIALOGUE DETAILS
* DO YOU WISH TO ADD THE UDC/LPS/ICS/DSS ROUTINES TO SYSLIB? [YIN]:
If the answer to this question is N,
bypassed.

the

section

* DOES YOUR TARGET SYSTEM HAVE THE UDC-II SUBSYSTEM? [YIN]:
LBR SYSLIB/RP=PURUDC
* DOES YOUR SYSTEM HAVE THE DRS/DSS-II DIGITAL 1/0 SUBSYSTEM? [YIN]:
* DOES YOUR SYSTEM HAVE THE ICS/ICR-II SUBSYSTEM? [YIN]:
* DOES YOUR SYSTEM HAVE THE DSRII/DSSII SUBSYSTEM? [YIN]:
LBR SYSLIB/RP = PURICR
* DOES YOUR TARGET SYSTEM HAVE THE LPS-II OR AR-II SUBSYSTEMS? [YIN]:
LBR SYSLIB/RP = LPS
* DO YOU WANT TO ADD THE PURDUE ISA ROUTINES TO SYSLIB? [YIN]:
The following command is issued only
these routines.

you

wish

add

LBR SYSLIB/RP = PURISA
The next command is issued only if you are using the RLOI or
either of the RK05 distribution kits.
PIP PURISA.OBJ;*/DE,PURUDC;*,PURICR;*,LPS;*,LPA;*
SET IUIC = [1,2X]
REM LBR
DELETE ALL BUT LATEST VERSION OF EXEC BUILD COMMAND FILE,
ASSEMBLY PREFIX FILE, AND ALL EXEC OBJECT LIBRARIES IF ANY.
;

PIP RSXBLD.CMD/PU
PIP RSXIIM.OLB;*/DE
PIP [200,200]RSXMC.MAC/PU
If a previous SYSGEN was not done on this disk,
the file
RSXIIM.OLB will not exist.
PIP will issue a warning message
to this effect.
NOW WE BUILD THE EXEC LIBRARY
Following the assembly of the user-tailored Executive,
the
individual object modules were concatenated into a single
file named RSXIIM.OBJ.
Concatenation was performed to save
space
on
the
secondary medium.
This file must be
transformed into a library file for processing by the Task
Builder (TKB).
INS $LBR
LBR RSXIIM/CR:80.:640.:128.=RSXIIM.OBJ
PIP RSXIIM.OBJ;*/DE
!DELETE OBJECT MODULE FILE
The preceding commands create a
library
file
named
RSXIIM.OLB from the concatenated object file, and delete the
no-Ionger-needed concatenated object file, thus freeing disk
space.

3-75

SYSGEN DIALOGUE DETAILS
However, if the distribution kit is other than an RLOI or
either of the RK05 kits, the last command above is replaced
by the command
PIP RSXllM.OBJ/PU

!DELETE ALL BUT LATEST OBJECT MODULE FILE

in order to preserve the latest object module file.
REM PIP
* DO YOU WISH TO ADD USER WRITTEN DRIVER(S) TO THE EXEC? [Y/N]:
As part of the SYSGEN process, the user's own specialized
drivers can be included in the Executive. An affirmative
answer to this question will guide the user
in assembling
the driver and devi~e table modules, inserting them into the
Executive object library, and modifying the Executive build
command file to include the driver when the Executive is
built. See the RSX-llM Guide to Writing an I/O Driver
for
additional information on writing drivers and including them
in the system.
If the response to the above question
following is displayed.

affirmative,

the

If you do not wish to add user written drivers to the
Executive,
the next display appears under the heading ALL
SYSTEMS.
*USER WRITTEN DRIVERS ONLY*
SET /UIC=[200,200]
WE WILL PAUSE WHILE YOU ASSEMBLE YOUR DRIVER(S) AND USRTB
MODULE.
THE EXEC ASSEMBLY PREFIX FILE RSXMC.MAC IS ALREADY
LOCATED UNDER UFD [200,200]. ASSUMING YOUR DRIVER(S) NAME IS
XXDRV, WHERE XX IS THE DEVICE NAME (E.G., DK), THE FOLLOWING
COMMANDS WILL ASSEMBLE THE DRIVER(S) AND THE USRTB MODULE.
)RUN $MAC
)RUN $BIGMAC
MAC)XXDRV=[l,l]EXEMC/ML, [200,200]RSXMC,XXDRV
MAC)USRTB=[1,1]EXEMC/ML,[200,200]RSXMC,USRTB
MAC)A Z
At this point, the indirect file will pause while
assembles the drivers and user device tables.

the

user

NOW YOU MUST ADD YOUR DRIVER(S) AND USRTB MODULE
TO THE EXEC OBJECT MODULE LIBRARY. THE FOLLOWING IS AN EXAMPLE:
LBR)RSXllM/RP=[200,200]XXDRV,USRTB
LBR)~Z

;

SET /UIC=[1,2x]
LBR
When the Librarian prompts for input, the user should
in a command to include the drivers and device table.
REM LBR
; YOU MUST NOW ADD COMMANDS TO INCLUDE YOUR DRIVER(S) AND USRTB

3-76

type

SYSGEN DIALOGUE DETAILS
MODULE INTO THE EXEC BY EDITING THE EXEC TASK BUILD COMMAND FILE.
TO ADD DRIVER(S) INSERT COMMANDS OF THE FORM:
RSXllM/LB:XXDRV
INTO THE COMMAND FILE IN THE PLACE WHERE THE OTHER DRIVERS ARE
REFERENCED.
XXDRV REPRESENTS THE NAME OF YOUR DRIVER(S) .
The next three lines are displayed only if you answered Y to
loadable driver support.
A loadable driver must not be
specified in the TKB Command file to build the executive.
NOTE:
FOR THOSE DRIVERS WHICH YOU WANT TO BE LOADABLE,
DO NOT INCLUDE CORRESPONDING COMMANDS TO ADD THEM TO
THE EXECUTIVE.
The next two lines are displayed regardless of
specified loadable driver support or not.

whether

you

THEN LOCATE THE LINE IN WHICH THE MODULE SYSTB IS REFERENCED
AND ADD THE ENTRY FOR YOUR USRTB MODULE IMMEDIATELY AFTER IT. EG:
[1,2x]RSXllM/LB:LOADR:NULTK:SYSTB:USRTB:SYTAB:INITL
FINALLY, LOCATE THE LINE:
GBLDEF=$USRTB:O
AND DELETE IT.
;

INS $EDI
EDI RSXBLD.CMD
REM EDI
When the Line Text Editor (EDI)
perform the required edits.

prompts,

the

user

should

YOUR NON-LOADABLE DRIVERS WILL AUTOMATICALLY BE LINKED
WITH THE EXECUTIVE YOU ARE BUILDING.
*ALL SYSTEMS*
Whether or not the user is adding a driver to the Executive,
processing continues at this point. The word NON-LOADABLE
is omitted if you did not specify loadable driver support.
INS $BIGTKB
INS $TKB
Only one of the above commands
proper task builder.

issued

install

the

SET /UIC=[1,2x]

; NOW WE BUILD THE EXECUTIVE
TKB @RSXBLD
The correct version of the Task Builder is installed and
used to build the Executive.
The Task Builder (TKB) is
controlled by the command file RSXBLD.CMD, which is created
during the running of SGN (and possibly modified to include
other drivers).
3-77

SYSGEN DIALOGUE DETAILS
* DID THE EXECUTIVE BUILD SUCCESSFULLY?

[Y/N]:

If the reply indicates that it did
displayed.

not,

the

WE WILL PAUSE NOW SO THAT YOU CAN CORRECT THE PROBLEM.
RESUMING, WE WILL BUILD THE EXECUTIVE AGAIN.

following

AFTER

The following text is displayed only when the UDCll, DSSll,
or ICS/ICR-ll is being included in the user's target system
and the device common block is to be built.
NOW WE BUILD THE UDC, DSS OR ICS/ICR DEVICE
COMMON BLOCKS. A DEVICE COMMON BLOCK RESIDES
ON THE I/O PAGE AND IS REFERENCED WHENEVER A TASK
DIRECTLY ACCESSES ANY I/O MODULES.
;

TKB @UDCBLD
TKB @ICBLD
YOU MUST EDIT THE RESIDENT LIBRARY BUILD FILE
FOR THE DSSll COMMON BLOCK TO SET THE BASE OF
THE 32-WORD BOUNDARY AT OR IMMEDIATELY BELOW
THE FIRST DSSll BUS ADDRESS SPECIFIED DURING
SYSGEN PHASE 1.
EXAMPLE OF EDITING COMMANDS TO SET
THE BASE ADDRESS OF THE COMMON BLOCK:
IF THE BASE PHYSICAL BUS ADDRESS OF THE
DSSll MODULES IS 160010 AND ONE MODULE
IS INSTALLED, THE EDITING COMMANDS ARE:
*L PAR
PAR=ISCOM:XXXXXX:400
*R PAR=ISCOM:160000:100
*ED
;

INS $EDI
EDI [l,20]ISBLD.CMD
REM EDI
The EDI example and command appear only if you have
specified that DSS-ll support is desired, and the target
the user should
system is unmapped.
When EDI prompts,
perform the required edits.
TKB @ISBLD
The TKB command occurs only if DSS-ll support is required.
REM TKB
SET /UIC=[l,l]
INS $LBR
LBR SYSLIB/RP=[l,20] ICOM.ICR
LBR SYSLIB/RP=[l,20]UDCOM.UDC
LBR SYSLIB/RP=[l,20]ISCOM.IDS
LBR SYSLIB/RP=[l,2x] ICTAB.ICR
LBR ISLIB/RP=[l,2x]DSSDI.IDS
LBR SYSLIB/RP=[l,2x]DSSDI.IDS

3-78

SYSGEN DIALOGUE DETAILS

Of the last two lines, only 1 will actually appear.
The
first command is executed if you have specified support for
DSS-ll and UDC.
The second command 1S executed if you
specified support for DSS-ll only, or with ICR/ICS-ll.
INS
PIP
PIP
PIP

$PIP

[1,2x]*.ICR;*/DE
[1,2x]*.UDC;*/DE
[1,2x]*.IDS;*/DE
Whether or not the UDC,
DSS-ll, or ICS/ICR-ll is being
included in the target system, processing continues at this
point.

REM LBR
INS $PIP
UNL LP:
PIP [1,2x]ICBLD.CMD;*/DE,UDCBLD.CMD;*,ISBLD.CMD;*
The TKB command files to build the device common blocks are
deleted, unless your distribution kit is other than an RLOI
or either of the RK05s.
YOU NOW NEED THE MAP OF THE EXECUTIVE TO LAYOUT
THE PARTITIONS IN YOUR NEW SYSTEM.
;

* DO YOU HAVE THE MAP ALREADY? [YIN]:
LOA LP:
PIP LP:=[1,3x]RSXIIM.MAP
UNL LP:
At this point, the user must find the symbol $SYTOP in the
map.
The symbol $SYTOP provides the value of the highest
memory location occupied by the user-tailored Executive and
is used for partition layouts.
In an unmapped system, tasks
are linked to the physical base address of the partition in
which they run. To create an unmapped user-tailored system,
the task-build command files for FCP, MCR, and TKTN must be
edited if $SYTOP is above 30100(8).
If $SYTOP is above
40000(8), all other task-build command files must be edited,
and the associated tasks must be rebuilt.
In a mapped
system, tasks are linked to a virtual base address rather
than a physical base address and, thus, do not depend on the
physical base address of the partition.

LOOK IN THE MAP OF THE EXEC FOR THE SYMBOL $SYTOP WHICH
INDICATES THE LAST ADDRESS ALLOCATED TO THE EXEC.
USER
PARTITIONS MAY START AT ANY LOCATION BEYOND THIS ADDRESS
AS LONG AS THEY FALL ON A 64 BYTE BOUNDARY.
SEE THE
SYSGEN MANUAL FOR A DESCRIPTION OF HOW TO SET UP PARTITIONS.
YOU MAY WISH TO STOP AT THIS TIME TO LAY OUT YOUR PARTITIONS.

* DO YOU WANT TO CONTINUE AND BUILD THE TASKS NOW? [YIN]:
If the user wishes to consider the partition layout,
it is
possible, at this point,
to interrupt the SYSGEN phase 2
process. See Chapter 4 for
information on laying out
partitions.
At
a later
time,
the user may restart
SYSGEN2.CMD and pass control directly to the point where the
system tasks are built.
If the user Bpecifies an exit from

3-79

SYSGEN DIALOGUE DETAILS

SYSGEN phase
displayed.

this

time,

the

following

text

WE WILL EXIT NOW. WHEN YOU ARE READY TO RESUME
THE BUILDING OF THE SYSTEM, EXECUTE THIS INDIRECT COMMAND FILE
AND ANSWER Y TO THE FOLLOWING QUESTION:
>* HAVE YOU ALREADY BUILT THE EXEC? [YIN]:
The SYSGEN process will shut down, allowing the user to lay
out the partitions. After laying out partitions, the SYSGEN
process can be resumed by rebootstrapping the system
(if
necessary) and starting SYSGEN2.CMD again.
If the user elects to continue with the
continues at this point.

SYSGEN,

processing

INS $EDI
INS $PIP
WE WILL NOW EDIT THE TASK BUILD COMMAND FILES
AND BUILD THE REQUIRED TASKS.
If a mapped system is being generated, the following text is
displayed.
MOST OF THE TASKS TO BE BUILT HAVE TASK BUILD
COMMAND FILES WHICH SPECIFY EITHER PARTITION
SYSPAR OR GEN. SYSPAR IS A PARTITION WHICH IS
ASSUMED TO BE 10000(8) BYTES LONG
GEN IS A PARTITION WHICH IS 40000(8) BYTES LONG
If an unmapped system is being generated, the following text
is displayed.
MOST OF THE TASKS TO BE BUILT HAVE TASK BUILD
COMMAND FILES WHICH SPECIFY EITHER PARTITION
SYSPAR OR GEN. SYSPAR IS A PARTITION WHICH IS
ASSUMED TO BE 7700(8) BYTES LONG
AND IS ASSUMED TO BE BASED AT 30100(8).
GEN IS A PARTITION WHICH IS 40000(8) BYTES LONG
AND IS ASSUMED TO BE BASED AT 40000(8).
The privileged tasks must always be rebuilt when the
Executive has been rebuilt. The privileged tasks are linked
to the Executive symbol table file and map into the
Executive address space so that they may access various
system lists and data structures.
If the Executive is
changed, these addresses change; thus, the tasks have to be
rebuilt.
The Line Text E~itor (EDI) may be used to examine the PAR
command line In each file that may require modification.
Every file in question must be checked, since a Partitions
command which does not reflect the requirements of the
user-tailored system can produce tasks which will not run.
A typical sequence as it would appear on the console is:
>EDI BOOBLD.CMD
[PAGE
1]
*L PAR=

3-80

SYSGEN DIALOGUE DETAILS
PAR=GEN:40000:40000
*KILL
EDI)A Z
[EXIT]
For an unmapped system, tasks built to run
the Task Builder command:

SYSPAR

have

PAR=SYSPAR:30100:7700
Those built to run in the GEN subpartition specify:
PAR=GEN:40000:40000
For mapped systems, the respective commands are:
PAR=SYSPAR:0:10000
PAR=GEN:0:40000
If alteration is necessary, the change may be accomplished
as shown below. Suppose, for example, the GEN subpartition
is to start at 50000(8).
The above sequence would be
changed to:
)EDI BOOBLD.CMD
[PAGE 1]
*L PAR
PAR=GEN:40000:40000
*C/4/5
PAR=GEN:50000:40000
*EX
[EXIT]
SET /UIC=[1,2x]
If loadable driver support has not been included and if you
are using an RLOl or either of the RK05 distributidn kits,
the next command is issued to delete unnecessary files.
PIP LOA.OLBj*/DE,LOADBLD.CMDj*,UNLBLDj*
If you did not include LPA-ll support and if you are using
an RLOl or either of the RK05 distribution kits, the next
command is issued to delete the LPA-ll files.
PIP LAINIT.OLBj*/DE,[200,200]BLDLAINIT.CMDj*
IT IS POSSIBLE TO BUILD 3 VERSIONS OF THE FILE SYSTEM:
l} 2K NON-MULTI-HEADER
2) 2.5K MULTI-HEADER
3} 5.5K FAST MULTI-HEADER
THE NON-MULTI-HEADER FILE SYSTEM RESTRICTS FILES TO A
MAXIMUM OF 26,112 BLOCKS OF 512 BYTES. THE MULTI-HEADER
FILE SYSTEMS DO NOT ENFORCE THIS RESTRICTION. ;F YOU
ARE BUILDING A 16K SYSTEM, YOU MUST ALWAYS BUILD THE 2K
FCP. FOR SYSTEMS WITH RP02/03/04/05/06 DISKS IT IS
RECOMMENDED THAT YOU BUILD THE 5.5K FCP. BIGFCP IS
STRUCTURED SO THAT IT STORES AS MANY FILE CONTROL BLOCKS
(FCBS) IN ITS TASK IMAGE AS POSSIBLE BEFORE OVERFLOWING
INTO THE DYNAMIC STORAGE REGION. AS DISTRIBUTED, THE
BUILD COMMAND FILE ALLOCATES SPACE FOR 24. FCBIS. YOU
MAY CHANGE THIS LIMIT BY EDITING THE BUILD COMMAND FILE.
* DO YOU WISH TO BUILD THE BIG (5.5K) AND FASTER FILE SYSTEM? [YIN]:

3-81

SYSGEN DIALOGUE DETAILS

* DO YOU WANT TO BUILD THE 2.SK MULTIHEADER FCP? [YIN]:
It is possible to build different file systems: one 2K in
siza,
with
file size limited to 26,112 blocks, and
relatively heavily overlaid; one 2.SK in size with no file
size limit and ~eavily overlaid; and one a default of S.SK
in size, which is less overlaid, has a file size limited
only by the capacity of the disk, and provides faster
processing of file access requests. Note that the smallest
(2K)
file system does not support RMS record locking.
(See
Chapter 4 for details of the three versions of FCP.)
As a
result of the answer to these questions, one of the
following three questions is asked.
BIGFCP'S BUILD FILE SELECTS PARTITION FCPPAR
WHICH STARTS AT 100000(8) AND IS
26000(8) LONG.
IN MOST CASES, THESE LIMITS WILL
HAVE TO BE ALTERED FOR YOUR SYSTEM.
For a mapped system partition FCPPAR starts at 0(8).

* DO YOU HAVE TO EDIT THE S.SK FCP TASK BUILD COMMAND FILE?

[YIN]:

The default partition for the S.SK FCP is FCPPAR,
26000(8) bytes long.

which

THE 2.SK FCP WILL BUILD TO RUN IN PARTITION
SYSPAR, WHICH FOR THIS VERSION OF FCP MUST
BE AT LEAST 10500 OCTAL BYTES BIG.
IN MOST CASES, YOU HAVE TO EDIT THE BUILD FILE.

* DO YOU NEED TO EDIT THE TASK BUILD COMMAND FILE FOR FCP? [YIN]:
The default partition for the 2.SK FCP is SYSPAR, which (for
this version of FCP)
has to be 10SOO(8) bytes long.
For
unmapped systems, it starts at 30100(8).
You will almost
certainly want to change this.
THE 2K FCP WILL BUILD TO RUN IN
PARTITION SYSPAR AS DEFINED ABOVE.
YOU MUST EDIT THE BUILD COMMAND
FILE IF YOU WANT TO CHANGE ITS PARTITION
;

* DO YOU NEED TO EDIT THE TASK BUILD COMMAND FILE FOR FCP?

[YIN]:

The default partition for the 2K FCP is SYSPAR, which is
7700(8)
bytes long.
For unmapped systems, it starts at
30100(8).
Depending on the answer to the appropriate
preceding
question, one of the following three commands may be issued
to allow editing of the correct task-build command file.
EDI BIGFCPBLD.CMD
EDI FCPBLD.CMD
EDI FCPNMHBLD.CMD
THE TASKS MCR, MCRMU, AND TKTN NORMALLY RUN
IN PARTITION SYSPAR. IF YOU WISH TO CHANGE THE PARTITION NAME,
PUT ANY OF THESE TASKS IN OTHER PARTITIONS,

SYSGEN DIALOGUE DETAILS

For a mapped system
OR CHANGE THE LENGTH OF SYSPAR FROM 10000(8),
For a unmapped system
OR CHANGE THE BASE ADDRESS OR LENGTH OF SYSPAR,
For both mapped and unmapped systems
YOU MUST EDIT THE TASK BUILD COMMAND FILES.
THERE ARE TWO VERSIONS OF MCR AVAILABLE -- A SINGLE USER
VERSION AND A MULTI-USER VERSION. THE SINGLE USER MCR
PROCESSES ALL COMMANDS SERIALLY AND RUNS IN PARTITION
SYSPAR. THE MULTI-USER VERSION CONSISTS OF TWO TASKS,
MCRMU AND SYS. TASK MCRMU RECEIVES ALL COMMANDS IN
THE NORMAL SERIAL MANNER, BUT IT PASSES MOST ON TO
TASK SYS FOR PROCESSING. SINCE MULTIPLE COPIES OF
SYS MAY BE RUNNING (ONE FOR EACH TERMINAL) A DEGREE
OR PARALLELISM IS ACHIEVED. TASK MCRMU RUNS IN
PARTITION SYSPAR WHILE TASK SYS RUNS IN GEN.
;

* DO YOU WANT TO BUILD THE MULTI-USER VERSION OF MCR? [YIN]:
If the previous question was answered affirmatively,
the
following question will be displayed. The EDI command will
depend on the answer to the edit question.
NOTE
This sequence of two questions and an
EDI
command is repeated many times
further on in the command file.
The
operation
is
always
the
same;
therefore, a description will not be
given for each successive one.

* DO YOU HAVE TO EDIT THE TASKBUILD FILE FOR MCRMU AND SYS? [YIN]:
EDI MCRMUBLD.CMD
Note that MCRMUBLD.CMD controls the task-build of both MCRMU
and SYS.
If you do not want the multi-user
following question is asked:

version

MCR,

the

* DO YOU HAVE TO EDIT THE TASK BUILD FILE FOR MCR? [YIN]:
EDI MCRBLD.CMD
* DO YOU HAVE TO EDIT THE TASK BUILD COMMAND FILE FOR TKTN? [YIN]:
EDI TKNBLD.CMD
The default partition for TKTN is SYSPAR.
If support for ANSI format magtape was not selected
SYSGEN phase 1, the next section is bypassed.
THE TASK MTAACP IS THE ANSI MAGTAPE FILE SYSTEM
AND MUST BE BUILT IF YOU WISH SUPPORT FOR ANSI FORMAT
MAGTAPE. THE TASK MTAACP WILL BUILD TO
RUN IN PAR4K WHICH IS BASED AT
130000(8) AND REQUIRES ONLY 13000(8) BYTES.

3-83

during

SYSGEN DIALOGUE DETAILS
THE TASK FIIMSG IS THE MAGTAPE MESSAGE TASK, AND
ISSUES MESSAGES FROM THE MAGTAPE ACP.
IT WILL BUILD
TO RUN IN SYSGEN AS DESCRIBED ABOVE.
If the target system is mapped, MTAACP will build to run in
partition GEN, which is based at 0(8) and requires only
13000(8) bytes.

* DO YOU HAVE TO EDIT THE TASK BUILD COMMAND FILE FOR MTAACP? [YIN]:
EDI MTABLD.CMD
* DO YOU HAVE TO EDIT THE TASK BUILD COMMAND FILE FOR FllMSG? [YIN]:
EDI FIIMSGBLD.CMD
Processing continues here whether ANSI magtape
selected or not.

support

was

THE FOLLOWING TASKS PROCESS ADDITIONAL MCR COMMANDS:
BOO, DMO, AT., INI, INS, LOA, MOU, SAV, UFD, AND UNL.
THEIR TASK BUILD COMMAND FILES SPECIFY PARTITION GEN, WHICH IS
8K WORDS (OCTAL 40000 BYTES) LONG.
IF YOU WISH TO CHANGE THE
PARTITION IN WHICH ANY OF THEM RUN, YOU MUST EDIT THE
APPROPRIATE BUILD FILE.
IN ADDITION, FOR UNMAPPED SYSTEMS PARTITION GEN
IS ASSUMED TO START AT 40000.
IF IN YOUR TARGET
SYSTEM GENIS BASE ADDRESS HAS CHANGED, YOU MUST
EDIT THE BUILD COMMAND FILES FOR ALL OF THESE TASKS.
IF THE ALTER-PRIORITY DIRECTIVE WAS NOT INCLUDED IN THE
EXECUTIVE, YOU MUST EDIT THE COMMAND FILE FOR TASK AT.

* DO YOU HAVE TO EDIT ANY FILES FOR MCR TASKS? [YIN]:
If the previous question is answered affirmatively,
the
following questions are displayed;
depending on the user's
response, the EDI command mayor may not be issued.

* DO YOU WANT TO EDIT TASK BOO'S BUILD COMMAND FILE?
EDI BOOBLD.CMD
* DO YOU WANT TO EDIT TASK DMO'S BUILD COMMAND FILE?
EDI DMOBLD.CMD
* DO YOU WANT TO EDIT TASK AT. 's BUILD COMMAND FILE?
EDI INDBLD.CMD
* DO YOU WANT TO EDIT TASK INI'S BUILD COMMAND FILE?
EDI INIBLD.CMD
* DO YOU WANT TO EDIT TASK INS'S BUILD COMMAND FILE?
EDI INSBLD.CMD
* DO YOU WANT TO EDIT TASK MOU'S BUILD COMMAND FILE?
EDI MOUBLD.CMD
* DO YOU WANT TO EDIT TASK SAV'S BUILD COMMAND FILE?
EDI SAVBLD.CMD
* DO YOU WANT TO EDIT TASK UFD'S BUILD COMMAND FILE?
EDI UFDBLD.CMD
The next two questions are displayed only
support for loadable drivers.

[YIN]:
[YIN]:
[YIN]:
[YIN]:
[YIN]:
[YIN]:
[YIN]:
[YIN]:
if

you

* DO YOU HAVE TO EDIT TASK LOA'S BUILD COMMAND FILE? [YIN]:
EDI LOABLD.CMD
* DO YOU HAVE TO EDIT TASK UNL'S BUILD COMMAND FILE? [YIN]:
EDI UNLBLD.CMD
The following text is always displayed.

3-84

selected

SYSGEN DIALOGUE DETAILS
THE TASKS HELLO AND BYE PROVIDE LOGIN/LOGOUT SUPPORT FOR
IF YOU SELECTED MULTI-USER PROTECTION
MULTI-USER SYSTEMS.
SUPPORT DURING SYSGEN PARTl, YOU MUST BUILD HELLO AND BYE.
THE ACCOUNT FILE MAINTENANCE PROGRAM ACNT MUST ALSO BE
BUILT TO CREATE AND MAINTAIN THE PASSWORD FILE.
IN
ADDITION, TWO OPTIONAL TASKS ARE AVAILABLE:
BRO - BROADCAST MESSAGE TO TERMINALS
SHUTUP - PERFORM ORDERLY SYSTEM SHUTDOWN.
ALL OF THE DISTRIBUTED COMMAND FILES SPECIFY THAT THE
TASKS RUN IS PARTITION GEN.
* DO YOU WANT TO BUILD THE MULTI-USER PROTECTION TASKS? [Y/N]:
* DO YOU WANT TO BUILD THE MULTI-USER UTILITIES? [Y/N]:
* DO YOU WANT TO EDIT THE BUILD FILES FOR HELLO, BYE, AND ACNT? [Y/N]:
If you do not wish to build the multiuser protection tasks
and are using an RLOI or either of the RK05 distribution
kits a PIP command is issued to delete the unused files.
PIP MLTUSR.OLB;*,ACNTBLD.*;*,BYEBLD.*;*,HELBLD.*;*/DE
Similar commands are issued to delete
For brevity, these are omitted.

other

unused

files.

IF YOUR TARGET SYSTEM DOES NOT HAVE A LINE PRINTER, YOU MUST
EDIT THE BUILD FILE FOR ACNT TO REMOVE THE ASSIGNMENT TO LP:.
* DO YOU HAVE TO EDIT THE BUILD FILES FOR HELLO, BYE, AND ACNT? [Y/N]:
EDI ACNTBLD.CMD
EDI BYEBLD.CMD
EDI HELBLD.CMD
* DO YOU HAVE TO EDIT THE BUILD FILES FOR BRO AND SHUTUP? [Y/N]:
EDI BROBLD.CMD
EDI SHUTUPBLD.CMD
If you want to build any of the multi-user protection tasks,
you must edit the appropriate task-build command file under
one of the following conditions:
the target system is
unmapped and the GEN partition is not at 40000, or you want
to change the partition.
THE TASKS ERL AND ERF SUPPORT ERROR LOGGING.
ERL IS THE
ERROR LOGGER TASK, ERF TURNS ERROR LOGGING OFF.
THEY MUST
BE BUILT IF YOU SELECTED ERROR LOGGING SUPPORT DURING SYSGEN
PART ONE. THE TASK BUILD COMMAND FILES BUILD BOTH TASKS TO
RUN IN PARTITION GEN.
;

* DO YOU WANT TO BUILD THE ERROR LOGGING TASKS? [Y/N]:
* DO YOU HAVE TO EDIT THE BUILD FILES FOR ERL AND ERF? [Y/N]:
The remaining error logging tasks
(PSE and SYE)
are not
privileged and, therefore, are not built during SYSGEN phase
2.
If you want to build the tasks PSE and SYE, you must do
so at a
later
time
(initiate SYSGEN phase 3 at the
appropriate time).
EDI ERFBLD.CMD
EDI ERLBLD.CMD
THE TASK ACS ALLOCATES/DEALLOCATES THE CHECKPOINT FILE
IF YOU SELECTED SUPPORT FOR DYNAMIC ALLOCATION OF
CHECKPOINT SPACE DURING SYSGEN PART 1, YOU MUST BUILD
THIS TASK.
IT WILL BUILD TO RUN IN PARTITION GEN.

3-85

SYSGEN DIALOGUE DETAILS

* DO YOU WANT TO BUILD TASKS ACS? [YIN]:

* DO YOU HAVE TO EDIT TASK ACSIS BUILD COMMAND FILE? [YIN]:
EDI ACSBLD.CMD
Again, edit task-build command files for tasks you want to
build, if the GEN partititon start address has changed, or
you want to change the partition.
TASK PMD IS THE POST-MORTEM AND SNAP DUMP PROCESSOR.
IT IS A PRIVILEGED TASK AND FOR CORRECT OPERATION IT SHOULD
RUN IN A PARTITION WITH ONLY CHECKPOINTABLE TASKS.
THE TASK BUILD COMMAND FILE BUILDS THE TASK FOR PARTITION
PAR4K WHICH IS 20000(8) LONG
AND IS ASSUMED TO START AT 130000(8). (Only displayed for unmapped
systems)

* DO YOU WANT TO BUILD TASK PMD? [YIN]:
* DO YOU HAVE TO EDIT PMD'S BUILD COMMAND FILE? [YIN]:
EDI PMDBLD.CMD
The task SHF ... , referred to below, may only run in a mapped
system. Therefore, the text associated with it will only be
displayed during the building of mapped systems.
TASK SHF IS THE SYSTEM CONTROLLED PARTITION TASK
COMPACTION ROUTINE.
IT WILL AGGLOMERATE FREE SPACE
IN A SYSTEM CONTROLLED PARTITION ON REQUEST FROM
THE EXECUTIVE. YOU MUST HAVE SELECTED DYN. MEM. ALLOC.
DURING SYSGEN PART 1 FOR THIS TASK TO BE CALLED BY
THE EXECUTIVE.
IT NORMALLY RUNS IN PARTITION SYSPAR.
, THE PARTITION IT RUNS IN MUST NOT BE SYSTEM CONTROLLED.
* DO YOU WANT TO BUILD TASK SHF? [YIN]:
* DO YOU HAVE TO EDIT TASK SHFIS BUILD COMMAND FILE? [YIN]:
EDI SHFBLD.CMD
THE TASK RMDEMO DISPLAYS SYSTEM STATUS ON A VTOS OR VTS2.
IT DISPLAYS THE ACTIVE TASK, POOL STATUS, PARTITION
IT WILL BUILD
LAYOUT, AND TASKS RESIDENT IN MEMORY.
FOR PARTITION GEN BUT ONLY REQUIRES 4K TO RUN AND
USES LUNl AS THE DISPLAY DEVICE.
;

* DO YOU WANT TO BUILD TASK RMDEMO? [YIN]:
* DO YOU WANT TO BUILD IT FOR A VTOS? [YIN]:

* DO YOU WANT TO BUILD IT FOR A VTS2? [YIN]:

* DO YOU HAVE TO EDIT TASK RMDEMO'S BUILD COMMAND FILE? [YIN]:
EDI RMDOSBLD.CMD
EDI RMDS2BLD.CMD
THE PRINT SPOOLER IS NOT DISTRIBUTED AS A TASK IMAGE.
IF YOU
WISH TO USE A PRINT SPOOLER IN YOUR TARGET SYSTEM, YOU MUST
EXPLICITLY BUILD IT.
THE TASK BUILD COMMAND FILE
SPECIFIES PARTITION SPLPAR WHICH IS 10000(8) LONG
AND IS ASSUMED TO START AT 130000(8).
The last line of the text above
generating an unmapped system.

appears

only

If you wish to build the print spooler,
affirmatively to the next question.

you

must

* DO YOU WANT TO BUILD TASK PRT (PRINT SPOOLER)? [YIN]:

3-86

you

are

answer

SYSGEN DIALOGUE DETAILS

The command file specifies that PRT be a checkpointable
task;
its performance can be improved by making it
non-checkpointable. The command file also builds PRT to
delete all spooled files after printing;
this attribute can
be altered.
If either of these changes to PRT is desired,
answer Y to the following question.
THE DEFAULT PRINT SPOOLER WILL ONLY DELETE FLES NAMED
LP.LST, LP.MAP, *.PMD, AND *.DMP.
IF YOU WANT THE SPOOLER
TO DELETE ALL FILES, YOU MUST EDIT THE BUILD COMMAND FILE.
The criteria for user-selectable file
discussed in Chapter 4.

deletion

PRT

* DO YOU WANT TO EDIT TASK PRT'S BUILD COMMAND FILE? [YIN]:
EDI PRTBLD.CMD
; NOW WE BUILD THE PRIVILEGED AND MCR TASKS.
INS $TKB
INS $BIGTKB
INS $PIP
SET IUIC=[1,2x]
PIP *.CMD/PU
The SYSGEN procedure selects the proper version of the Task
Builder, if the Task Builder is not already installed. This
could be the case if SYSGEN2.CMD was terminated after
building the Executive. The PIP command deletes all but the
latest versions of the command files.
* DO YOU WANT TO GENERATE THE MAPS FOR THE ABOVE TASKS? [YIN]:
In most cases, these maps are of little use to the user and
are not needed. Therefore, a negative response is usually
given.
If, however,
displayed.

the

maps

are

desired,

the

following

FOR THE SINGLE RKOS, DUAL RKOS OR RLOI DISTRIBUTION KITS, RUNNING
STANDALONE, YOU MAY DIRECT THE TASK BUILDER MAPS TO THE LINE
PRINTER, OR ANOTHER DISK OF THE SAME TYPE AS YOUR KIT. NOTE THAT
THE MAPS WILL NOT FIT ON THE DISTRIBUTION DISKS FOR THE ABOVE.
FOR OTHER DISTRIBUTION KITS, YOU MAY SPECIFY THE LINE PRINTER,
THE DISTRIBUTION KIT DISK (SYO) OR A SECOND DISK OF THE SAME TYPE.
FOR ALL ONLINE SYSGENS, YOU MAY SPECIFY ANY DISK WITH AT LEAST
1400 FREE BLOCKS NOTE THAT SYSGEN WILL NOT LOAD THE DRIVER FOR
THIS DISK.
* WHAT IS TO BE THE MAP DEVICE? [DDU]

[S]:

The response is then assigned to the logical device
The following assumes DKl:
is to be the map device.

MP:.

ASN DKl:=MP:
If you do not wish to print the maps, they are assigned
null device.
ASN NL:=MP:

3-87

the

SYSGEN DIALOGUE DETAILS

TKB @BOOBLD
PIP BOO.OLBi*/DE, BOOBLD.CMDi*/DE
The previous two commands build the task and delete the
unused files.
The unused files are deleted only if you are
using an RLOI distribution kit or either of the RK05
distribution kits. Similar commands will now be issued for
all tasks that were selected to be built in the preceding
sections.
TKB @DMOBLD
PIP DMOBLD.CMDi*/DE
TKB @FCPBLD
TKB @FCPNMHBLD
TKB @BIGFCPBLD
The selected version
built.

the

file

control

primitives

PIP FCP.OLB;*,FCPBLD.CMDi*,BIGFCPBLD.*;*/DE
TKB @INDBLD
PIP IND.OLB,INDBLD.*;*/DE
TKB @INIBLD
PIP INIBLD.*;*/DE
TKB @INSBLD
PIP INS.OLD;*,INSBLD.*;*/DE
TKB @MCRBLD
TKB @MCRMUBLD
PIP MCRBLD.*;*/DE
PIP MCRMUBLD.*;*,SYSBLD.*;*/DE
TKB @MOUBLD
PIP MOU.OLB;*,INI.OLB;*MOUBLD.*;*/DE
If ANSI magtape support was selected, the next two
are issued.

commands

TKB @FIIMSGBLD
PIP FIIMSG.OLB;*,FIIMSGBLD.OLD;*,.CMD;*/DE
TKB @MTABLD
PIP MTA.OLB;*,MTABLD.*;*/DE
TKB @SAVBLD
PIP SAV.OLB;*,SAVBLD.*;*/DE
TKB @TKNBLD
PIP TKNBLD.CMD;*/DE
TKB @UFDBLD
PIP UFD.OLB;*,UFDBLD.CMDi*/DE
The next two commands are issued
driver support was selected.

only

loadable

device

TKB @LOABLD
. TKB @UNLBLD
PIP LOABLD.CMD;*,UNLBLD;*,LOA.OLB;*/DE
The next command is issued only if the Post-mortem and
Shot Dump task was selected to be built.

Snap

TKB @PMDBLD
PIP PMD.OLBi*,PMDBLD.*;*/DE
One of the next two commands is issued only if the
status display task RMDEMO was selected to be built.

3-88

system

SYSGEN DIALOGUE DETAILS
TKB @RMD05BLD
TKB @RMD52BLD
PIP RMD05.0BJ;*,RMD05BLD.CMD;*/DE
PIP RMD52.0BJ;*,RMD52BLD.CMD;*/DE
The next command is issued only when the
routine was selected to be built.

memory

compaction

TKB @SHFBLD
PIP SHUFL.OBJ;*,SHFBLD.CMD;*/DE
The next 2 commands are issued only if the print spooler was
selected to be built.
TKB @PRTBLD
PIP PRT.OLB;*,PRTBLD.ODL;*,PRTBLD.CMD;*/DE
The next set of commands are issued only if
protection tasks were selected to be built.

the

multi-user

the

multi-user

TKB @ACNTBLD
PIP ACNTBLD.*;*/DE
TKB @BYEBLD
PIP BYEBLD.CMD;*/DE
TKB @HELBLD
PIP HELBLD.CMD;*/DE
The next set of commands are issued only if
utility tasks were selected to be built.
TKB @BROBLD
PIP BROBLD.CMD;*/DE
TKB @SHUTUPBLD
PIP MLTUSR.OLB;*/DE
The next command is· issued only if the
allocation task was selected to be built.

checkpoint;

space

TKB @ACSBLD
PIP ACSBLD.CMD;*/DE
PIP MCR.OLB;*/DE,SYSROT.OBJ;*
The next 3 commands are issued only
tasks were selected to be built.

the

LPA-ll

error

logging

TKB @ERFBLD.CMD
TKB @ERLBLD.CMD
PIP ERF.OBJ;*/DE,ERL.OLB;*
The following
included.

displayed

only

If you have not included LPA-ll support,
appear under the heading ALL SYSTEMS.

the

support
next

queries

**LPA-ll SUPPORT ONLY**
* DO YOU WANT THE MAPS FOR THE MICRO CODE LOADER TASKS? [Y/N]:
The proper version of the task builder is then installed.
INS $TKB
INS $BIGTKB
SET /UIC=[l,2x]

3-89

was

SYSGEN DIALOGUE DETAILS

THE LPA-ll MAY BE LOADED WITH ONE OF THREE VERSIONS
OF THE MICRO CODE:

MULTI-REQUEST MODE
DEDICATED MODE A/D INPUT
DEDICATED MODE D/A OUTPUT

1
2
;

* ENTER MICRO CODE VERSION DESIRED FOR LPA-ll #N[O R:0-2 0:1]:
Note that N above is replaced by the unit being referenced
(for example, the first time the question is asked, N is
replaced by 0 and so on).
* IS THE LAB I/O ON THIS LPA-ll AN ARll?
The above two queries are
specified.

[Y/N]:

repeated

for

each

LPA-ll

* DO YOU WANT TO EDIT THE LOADER TASK BUILD COMMAND FILES?

unit

[Y/N]:

Editing the command file is necessary if you wish to change the
partition name or, on an unmapped system, the partition base. The
indirect command file [200,200]BLDLAINIT.CMD contains further details.
If you want to edit the command files, EDI is installed to
to do so.
INS
EDI
EDI
REM

allow

$EDI
LAINIXBLD.CMD
LAINITBLD.CMD
EDI
The proper task builder commands are then issued.

TKB @LAINIXBLD
TKB @LAINITBLD
PIP is then installed to delete the LPA-ll files.
INS $PIP
PIP LAINIXBLD.CMD;*/DE,LAINITBLD;*
REM PIP
REM TKB
IN ORDER FOR THE LPA-ll MICRO CODE LOADER TO FUNCTION PROPERLY,
ON POWERFAIL RECOVERY OR DRIVER LOAD YOU MUST HAVE THE
FOLLOWING TASKS INSTALLED:
LAINIT - THE MICRO CODE LOADER
LAINO - LOADER REQUESTOR FOR LPA-ll UNIT 0
LAINl - LOADER REQUESTOR FOR LPA-ll UNIT 1

LAIN17 - LOADER REQUESTOR FOR LPA-ll UNIT 17(8)
SYSGEN2, WHEN IT CREATES INSTALL.CMD, ONLY INSTALLS LAINIT AND
LAINO. YOU MUST EDIT INSTALL.CMD TO INCLUDE THE OTHER REQUESTOR
TASKS. IF THE REQUIRED TASKS ARE NOT INSTALLED, THE
LPA-ll MICROCODE WILL NOT BE LOADED AUTOMATICALLY.
**ALL SYSTEMS**

3-90

you

SYSGEN DIALOGUE DETAILS

PIP [200,200]BLDLAINIT.CMD;*/DE,LAINIT.OLB;*
At this point, all tasks have been built.
If the host
system is running on an RK05 disk, all object module
libraries, task-build command files, and overlay description
files are deleted, except for the Executive object library
and task-build command file.
PIP [200,200]/RE=RSXBLD.CMD,RSXIIM.OLB
PIP *.*;*/DE
PIP [1,2x]/RE=[200,200]RSXBLD.CMD,RSXIIM.OLB
If maps were printed on the line printer, the
unloads the LP driver.

command

loadable

device

UNL LP:
The next question is displayed
driver support was selected.

only

* DO YOU WANT TO BUILD ANY LOADABLE DRIVERS NOW? [Y/N]:
If the answer is Y, the following questions
from the file BLDDRV.CMD are issued.

and

commands

If loadable drivers were not selected or if you do not wish
to build them, the next display appears under the heading
ALL SYSTEMS.
*BUILDING LOADABLE DRIVERS ONLY*
SET /UIC=[200,200]
YOU MAY NEED THE TASK BUILD MAPS FOR THE DRIVER(S) FOR
YOUR PARTITION LAYOUT.
;

* DO YOU WANT THE MAPS? [YIN]:
If the answer to this question is N, no maps will be
generated for the loadable drivers. Otherwise, the maps
will be output on the line printer if the system has one, or
on the console terminal.
One of the following three
messages is displayed.
THE MAPS WILL BE SPOOLED TO THE LINEPRINTER
THE MAPS WILL BE PRINTED ON THE LINEPRINTER
THE MAPS WILL BE PRINTED ON THE CONSOLE TERMINAL
If maps are directed to the line printer, the
is issued to load the LP driver.

LOA LP:
SET /UIC=[1,2x]
WHEN ALL DRIVERS ARE BUILT, STRIKE CARRIAGE RETURN WHEN ASKED
FOR DEVICE MNEMONIC.
;

* WHAT IS THE DRIVER 2-CHARACTER DEVICE MNEMONIC? [S]:

3-91

command

SYSGEN DIALOGUE DETAILS
The answer should be the 2-character device mnemonic for the
(next)
loadable driver to build;
e.g., MT, followed by
carriage return.
If a single carriage return is answered,
the driver build section is terminated.
* WHAT IS THE DRIVER PARTITION NAME? [S]:
The answer should be a 1- to 6-character
where the driver is intended to run.

partition

name

* WHAT IS ITS PARTITION BASE ADDRESS? [S]:
This question is displayed only if an unmapped system is
being generated.
The answer should be the base address
(octal bytes) for the driver partition.
TKB @[200,200]XXDRVBLD
This command builds the specified driver for
the specified
partition. XX is the driver mnemonic entered in response to
a previous question.
PIP [200,200]XXDRVBLD.CMD;*/DE
The command above deletes the command file that was used
build the driver.

Processing now resumes with the DEVICE MNEMONIC question,
and the previous sequence is repeated to build the next
driver.
If no more drivers are selected to be built,
the driver
build section terminates.
If maps were directed to the line
printer, the following command unloads the LP driver.
*ALL SYSTEMS*
Whether or not loadable drivers were built, BLDDRV.CMD exits
and processing will resume here in SYSGEN2.CMD.
INS $PIP
If a new line printer driver was built,
the following
is
performed before the line printer is unloaded. Otherwise,
it is omitted.
BECAUSE UNLOAD WILL BE CONFUSED BY THE NEW LP DRIVER,
WE WILL RENAME IT. BEFORE WE RUN VMR, WE WILL CHANGE
IT BACK.
SET /UIC=[l,5x]
PIP LPNEW.TSK/NV/RE=LPDRV.TSK
PIP LPNEW.STB/NV/RE=LPDRV.STB
Whether or not a new driver was built, the line
unloaded.

printer

the

UNL LP:
REM TKB
If support for ANSI magtape
section is bypassed.
SET /UIC=[l,l]
INS $LBR

3-92

was

not

selected,

SYSGEN DIALOGUE DETAILS

If the system disk is an RK05 or RLOI, the FCS routines that
handle ANSI magtape will now be inserted in SYSLIB.
AS DISTRIBUTED, SYSLIB DOES NOT CONTAIN THE FILE CONTROL
SERVICES SUBROUTINES FOR ANSI MAGTAPE SUPPORT. WE WILL NOW
INSERT THEM INTO SYSLIB.
NOTE: THESE ROUTINES CAUSE AN INCREASE IN THE SIZE
OF MOST TASKS BUILT WITH THEM AS COMPARED TO
THE NON-ANSI VERSION OF FCS.
* DO YOU WANT ANSI MAGTAPE SUPPORT IN SYSLIB? [YIN]:
LBR SYSLIB/RP=FCSMTA
PIP FCSMTA.OBJj*/DE
On the other hand, if the system disk is an RP or RK06 disk,
an alternative version of SYSLIB will be created, called
ANSLIB.
AS DISTRIBUTED, SYSLIB DOES NOT CONTAIN THE FILE CONTROL
SERVICES SUBROUTINES FOR ANSI MAGTAPE SUPPORT. WE WILL NOW
CREATE AN ALTERNATIVE VERSION OF SYSLIB, WITH THE FILE NAME
"[I,I]ANSLIB", THAT CONTAINS THE ANSI SUPPORT ROUTINES.
THIS LIBRARY SHOULD BE INCLUDED AS INPUT TO THE TASK BUILDER
WHENEVER YOU BUILD A TASK THAT REQUIRES ANSI SUPPORT.
NOTE: THESE ROUTINES CAUSE AN INCREASE IN THE SIZE
OF MOST TASKS BUILT WITH THEM AS COMPARED TO
THE NON-ANSI VERSION OF FCS.
j

* HAS ANSLIB ALREADY BEEN CREATED BY A PREVIOUS SYSGEN? [YIN]:
The following three commands are issued if this question was
answered with an N.
PIP ANSLIB.OLBj*/DE
PIP ANSLIB.OLB/CO=SYSLIB.OLB
LBR ANSLIB/RP=FCSMTA
For all systems with ANSI magtape support, the next
is issued.

command

REM LBR
Whether ANSI magtape support was selected or not, processing
continues here.
THE UTILITY TASKS (MAC, PIP, TKB ETC.) ARE ALREADY BUILT TO RUN IN
PARTITION GEN (EXCEPT BIGMAC AND BIGTKB WHICH ARE BUILT TO RUN
IN PARI4K).
IF YOU WISH TO CHANGE THE PARTITION IN WHICH ANY OF THEM
RUN YOU MUST EDIT THE APPROPRIATE TASK'S BUILD COMMAND FILE
AND REBUILD THE TASK.
The following note appears only when building mapped systems.
NOTE: FOR MAPPED SYSTEMS IT ISN'T NECESSARY
TO REBUILD ANY OF THESE TASKS SINCE YOU
MAY EXPLICITLY SPECIFY THE PARTITION IN
WHICH THEY RUN AT INSTALL TIME.

3-93

SYSGEN DIALOGUE DETAILS

SINCE YOU HAVE SELECTED SUPPORT FOR ANSI MAGTAPE,
YOU WILL PROBABLY WANT TO REBUILD PIP AND POSSIBLY
OTHER UTILITY TASKS TO BE ABLE TO HANDLE ANSI MAGTAPES.
THE USER MODE DIAGNOSTICS ARE NOT DISTRIBUTED AS TASK IMAGES.
IF YOU WANT THEM, YOU HAVE TO BUILD THEM.
If you are using an RLOI or either of the RK05 distribution
kits, there is not enough disk space to rebuild any utility
tasks or user mode diagnostics.
The following is displayed if you are using
distribution kit.

the

dual

RK05

IF YOU WANT TO REBUILD THE UTILITY OR DIAGNOSTIC TASKS
AND THE SYSTEM YOU ARE GENERATING HAS AT LEAST 24K OF
MEMORY AND IT WILL RUN THE DISTRIBUTED TASKS, IT IS
SUGGESTED THAT YOU REBUILD THEM USING YOUR SYSTEM DISK
INSTEAD OF THE BASLINE DISK, AFTER SYSGEN2 IS COMPLETED.
OTHERWISE, ANSWER YES TO THE FOLLOWING QUESTION.
The following is displayed if
single RK05 distribution kit.

you

are

using

RLOI

IF YOU WISH TO REBUILD THE UTILITY TASKS AND/OR BUILD THE USER MODE
DIAGNOSTICS, YOU MUST DO SO AFTER SYSGEN PART 2 HAS BEEN COMPLETED.
AT THAT TIME, MOUNT THE DISK LABELED "UTILITY OBJECTS" AND
RUN THE INDIRECT COMMAND FILE [200,200]SYSGEN3.CMD
If you are using a distribution kit other than an RLOI or
single RK05, the following question is asked:

* DO YOU WANT TO REBUILD UTILITIES AND/OR BUILD DIAGNOSTICS? [Y/N]:
If you answer Y, the command file SYSGEN3.CMD (described in
Section 3.5)
is automatically called. However, if you are
using the dual RK05 distribution kit, the indirect command
file
SGNXFER2.CMD
is used to transfer control.
The
following text, which actually comes
from
the
file
SGNXFER2.CMD, is displayed for dual RK05 SYSGENS.
*DUAL RK05 KIT*
The following assumes that the SYSTEM disk
DKl:.

was

mounted

DMO DKl:
REMOVE THE SYSTEM DISK FROM DKl: AND REPLACE IT WITH
THE UTILOBJ DISK. START UP THE UTILOBJ DISK (WRITE
ENABLED) •
* IS THE UTILOBJ DISK READY? [Y/N]:
The query is repeated until the disk is ready (Y response).
The disk is then mounted and control passed to SYSGEN3.CMD
(see Section 3.5).
MOU DKl:UTILOBJ2

3-94

SYSGEN DIALOGUE DETAILS
When SYSGEN3.CMD is completed, SGNXFER2.CMD continues.
DMO DKl:
REMOVE THE UTILOBJ DISK FROM DKl: AND REPLACE IT
WITH THE SYSTEM DISK.
* IS THE SYSTEM DISK READY? [YIN]:
The query is repeated until the disk is ready (Y response).
The disk is then mounted and the new tasks are copied to the
system disk.
MOU DKl:SYSTEM
WE WILL NOT COpy THE NEW TASKS TO THE SYSTEM DISK.
,PIP IS THEN INSTALLED AND THE TASKS COPIED.
*ALL KITS*
Processing of SYSGEN2.CMD continues here.
SET IUIC=[1,5y]
INS $PIP;-l
The following text and questions appear only
mapped target systems.

when

building

If you are building an unmapped system,
appears under the heading ALL SYSTEMS.

display

the

*MAPPED SYSTEMS ONLY*
YOU NOW MUST SPECIFY WHETHER THE MEMORY SIZE WHICH YOU
SPECIFIED FOR YOUR TARGET SYSTEM IN SGN DURING SYSGEN
PHASE ONE IS GREATER THAN 32K WORDS
;

* IS YOUR TARGET SYSTEM LARGER THAN 32K WORDS? [YIN]:
If the answer to this question is affirmative, the following
text is displayed.
If you respond negatively, the next
the heading ALL SYSTEMS.

display

appears

under

IF YOU EVER WISH TO FIX TASKS ABOVE 32K OR LOAD DRIVERS
ABOVE 32K AND SAVE THE SYSTEM OR IF THE TASK SAV
(WHICH NORMALLY RUNS IN GEN) IS EVER TO BE RUN ABOVE
32K, YOU MUST CREATE A LARGER COPY OF YOUR TARGET SYSTEM
WITH PIP AT THIS TIME.
NOTE: IT IS NOT POSSIBLE TO BOOT A VIRGIN MAPPED
SYSTEM WHICH HAS DRIVERS LOADED ABOVE 27.5K FROM
AN UNMAPPED SYSTEM. IT IS, HOWEVER, POSSIBLE TO
BOOT A SAVED MAPPED SYSTEM WITH ANY CONFIGURATION
FROM ANY UNMAPPED SYSTEM.
;

* DO YOU WI~H TO CREATE A LARGER COpy OF YOUR SYSTEM? [YIN]:
If the answer to this question is affirmative, the following
text is diplayed. Otherwise the next display appears under
the heading ALL SYSTEMS.

3-95

SYSGEN DIALOGUE DETAILS

TO CREATE A SYSTEM IMAGE IN WHICH TASK IMAGES MAY BE FIXED UP
TO M K WORDS, OR IN WHICH THE TOP OF SAV MAY BE AS HIGH
AS M K WORDS, YOU MAY CALCULATE THE NUMBER OF BLOCKS (N)
NEEDED AS FOLLOWS:
N=(4*M)+2
FOR EXAMPLE A 40K SYSTEM WOULD USE (40.*4)+2=162. BLOCKS
NOTE:

SAVE IMAGES ON THE 11/70 ARE CURRENTLY
SUPPORTED ONLY TO A MAXIMUM OF l24K WORDS
(I.E. N=498.) ALSO, THE NUMBER OF BLOCKS
IS ASSUMED TO BE OCTAL. TO SPECIFY A
DECIMAL NUMBER, APPEND A TRAILING DECIMAL POINT.
FOR SINGLE RK05 DISTRIBUTION KITS, THE
MAXIMUM SYSTEM IMAGE SIZE IS 64K (258.
BLOCKS) DUE TO A LACK OF CONTIGUOUS SPACE.

;

* ENTER THE NUMBER OF BLOCKS FOR YOUR SYSTEM IMAGE FILE [S]:
PIP is now invoked to copy
example,
if the response
command will be:

the system image file.
For
to this question is 162., the

PIP RSXllM.SYS/CO/NV/BL:162.=RSXllM.TSK
The next lines are displayed only if the size of the system
is less than 32K or if the user did not want to extend the
size of the system image file.
WE WILL NOW MAKE A COpy OF YOUR TARGET SYSTEM
PIP RSXllM.SYS/NV=RSXllM.TSK
No matter how large the target system is the processing
text and commands continues at this point.

*ALL SYSTEMS*
SET /UIC=[1,5y]
RSXllM.TSK IS A BACKUP COpy OF THE EXECUTIVE YOU JUST BUILT.
IF YOU DO NOT WISH TO RETAIN IT, WE WILL DELETE IT NOW.
;

* DO YOU WISH TO DELETE THE SYSTEM BACKUP FILE RSXllM.TSK? [Y/N]:
The normal reason (aside from backup)
for
retaining the
RSXllM.TSK file is to be able to set up two or more systems:
one for program development, and one for production; or two
systems with different partition layouts.
If the answer to
this question is affirmative,
the following command is
issued:
PIP RSXllM.TSK;O/DE
In all SYSGENs, the following text is displayed to guide the
user in setting up partitions and installing tasks into the
target system Executive.
REM PIP

3-96

SYSGEN DIALOGUE DETAILS
YOUR TARGET SYSTEM IS NOW READY TO SET UP PARTITIONS AND INSTALL
THE REQUIRED TASKS. THE PROCEDURE TO FOLLOW ONCE VIRTUAL MCR
IS RUNNING IS:
1)
EXTENDED POOL SPACE TO BASE OF FIRST PARTITION
2)
SET UP YOUR PARTITIONS
2A) SET UP UDC, DSS OR ICS/ICR-ll COMMON BLOCK
3)
INVOKE THE INDIRECT FILE INSTALL.CMD IN VMR TO
INSTALL THE PRIVILEGED TASKS YOU JUST BUILT
4)
LOAD ANY LOADABLE DRIVERS THAT YOU WANT RESIDENT
IN THE SYSTEM IMAGE.
IF THE TERMINAL AND/OR SYSTEM DISK
DRIVERS ARE LOADABLE, THEY MUST BE LOADED USING VMR.
5)
EXIT FROM VIRTUAL MCR AND BOOT IN YOUR TARGET SYSTEM
;

* DO YOU WANT A VMR EXAMPLE DISPLAYED? [Y/N]:
If you answer Y to this question, a VMR example that depicts
your system requirements is displayed. Since the example
displayed depends on the options you select during SYSGEN,
it is omitted here.
THE FILE [200,200]INSTALL.CMD CONTAINS COMMANDS
TO INSTALL ALL THE PRIVILEGED TASKS THAT YOU BUILT
IN YOUR TARGET SYSTEM.
YOU MAY WISH TO EDIT INSTALL.CMD TO INCLUDE OTHER TASKS.
NOTE - IF YOU INSTALL A TASK
WITH VMR THAT WAS NOT BUILT DURING
THIS SYSGEN, YOU CANNOT RUN THAT TASK
IN THE CURRENT SYSTEM!
THIS IS TRUE FOR BOTH MAPPED AND UNMAPPED
TARGET SYSTEMS, AND FOR BOTH PRIVILEGED
AND NON-PRIVILEGED TASKS. THEREFORE,
BOOT THE NEW SYSTEM IMMEDIATELY
AFTER SYSGEN HAS FINISHED, OR AVOID
INSTALLING TASKS WITH VMR THAT WERE
NOT BUILT DURING THIS SYSGEN.
;

* DO YOU WANT TO EDIT INSTALL.CMD? [Y/N]:
SYSGEN phase 2 has created the file
[200,200]INSTALL.CMD
which will be used by VMR to install all the privileged
tasks that have been built.
If you want to edit that file,
answer Y.
INS [1,5y]EDI;-1
SET /UIC=[200,200]
EDI INSTALL.CMD
SET /UIC=[1,5y]
REM EDI
;

; NOW WE WILL RUN VIRTUAL MCR SO THAT YOU MAY INITIALIZE
; YOUR SYSTEM.
;

INS $BOO;-l
INS $VMR;-l
ASN SY:=LB:
VMR
WHEN THE INDIRECT FILE EXITS, BOOT IN YOUR TARGET SYSTEM,
SET THE DATE AND TIME, AND SAVE THE SYSTEM WITH A BOOTSTRAP.
WHEN YOUR SYSTEM REBOOTS ITSELF, PURGE THE OLD TASK FILES.
E.G.,
>BOOT RSXIIM

3-97

SYSGEN DIALOGUE DETAILS

RSXIIM V03.1 BL22
>TIM 1/1/77 12:00:00
>SAV /WB
RSXIIM V03.1 BL22
28K
>RED DKO:=SY:
>MOU DKO:UNMOBJ
>@[1,2]STARTUP
>* PLEASE ENTER TIME AND DATE (HH:MM MM/DD/YY)
>TIM 1/1/77 12:01
>@ <EOF>
>SET /UIC=[1,50]
>RUN $PIP
PIP>*.*/PU

[S]:

PIP>~Z

If you selected multiuser protection, the following reminder
is displayed.
DON'T FORGET TO CREATE ACCOUNTS AFTER SAVING YOUR SYSTEM
The user should bootstrap the user-tailored Executive, using
the previous commentary as a model.

3.5

SYSGEN3.CMD FILE DETAILS.

SYSGEN part 3 builds selected utility tasks, and/or user mode
diagnostic tasks.
For SYSGENS using any distribution kit except the
RLOI or single RK05, SYSGEN3 is performed as part of SYSGEN2,
if the
following question is answered with a Y.
* DO YOU WANT TO REBUILD UTILITIES AND/OR BUILD DIAGNOSTICS? [Y/N]:
If you are using an RLOI kit or the single RK05 kit,
there is not
enough on-line disk storage to do SYSGEN3 during SYSGEN2, and the
previous question does not appear during SYSGEN2.
In such systems,
SYSGEN3 must be invoked manually after SYSGEN2 has finished using the
Utility Object Disk (which is part of all distribution kits)
as the
system disk. The appropriate command is then:
>SET /UIC=[200,200]
>@SYSGEN3
This section describes details of the SYSGEN3 procedure.
SYSGEN PART 3

01754

BUILD SELECTED UTILITY TASKS AND/OR USER MODE
DIAGNOSTICS.
EXPANDED COMMENTS PROVIDE A DESCRIPTION OF EVERY STEP IN THIS
SYSGEN3 COMMAND FILE. ON THE OTHER HAND, SHORT COMMENTS
PROVIDE VIRTUALLY NO EXPLANATORY TEXT.

3-98

SYSGEN DIALOGUE DETA,ILS

* DO YOU WANT EXPANDED COMMENTS FOR SYSGEN PART 3? [YIN]:
The following section of the dialogue establishes certain
parameters concerning the current system and the target
system. If SYSGEN3 has been called from SYSGEN2, after
answering Y to the question

* DO YOU WANT TO REBUILD UTILITIES ANDIOR BUILD DIAGNOSTICS? [YIN]:
These parameters are
section is bypassed.

already

known,

and

* ARE YOU RUNNING ON A MACHINE WITH AT LEAST 24K WORDS?

the

following

[YIN]:

If the current system has less than 24K words of memory, the
utility tasks cannot be built. The following message is
displayed and SYSGEN3 terminates.SORRY, YOU CANNOT BUILD ANY UTILITIES WITH A MACHINE
SMALLER THAN 24K WORDS!
If the system has enough memory, processing continues here.

* ARE YOU BUILDING A MAPPED SYSTEM? [YIN]:
The following questions are asked
to
determine
the
distribution kit you are using.
An affirmative answer
suppresses further distribution kit queries.

* DO YOU HAVE THE SINGLE RKOS DISTRIBUTION KIT?

[YIN]:

If not, the next question is asked.

* DO YOU HAVE THE DUAL RKOS DISTRIBUTION KIT?

[YIN]:

If you have this kit, you must then identify the RKOS
that contain the BASLINE and UTILOBJ disks.
If you do not have the dual RKOS kit, the next
are omitted.

two

units
queries

* IN WHICH RKOS UNIT IS THE BASLINE DISK MOUNTED?:
* IN WHICH RKOS UNIT IS THE UTILOBJ DISK MOUNTED?:
These are then assigned to LB:

* DO YOU HAVE THE RLOI DISTRIBUTION KIT?

and SY:.
[YIN]:

* ARE YOU RUNNING ON A MACHINE WITH A LINEPRINTER? [YIN]:
* WAS ANSI MAGTAPE SUPPORT SELECTED IN SYSGEN PART I? [YIN]:
Processing
continues
here
automatically from SYSGEN2.

SYSGEN3

was

called

* WAS USER MODE DIAGNOSTIC SUPPORT SELECTED IN SYSGEN PART I? [YIN]:
Since SYSGEN3 may be called to build either utility tasks or
user mode diagnostic tasks or both,
the following two
questions are asked to determine further action.
(The
second question is asked only if user mode diagnostic
support was selected in SYSGEN part 1.)

3-99

SYSGEN DIALOGUE DETAILS
* DO YOU WANT TO REBUILD ANY UTILITY TASKS·? [YIN]:
If user mode diagnostic support was not selected in part 1,
you cannot build the user mode diagnostics. Therefore, if
not selected previously, the next question is omitted.
* DO YOU WANT TO BUILD ANY USER MODE DIAGNOSTICS?

[yiN]:

The responses to the above queries determine
following sections will be displayed.

which

the

If you wish to rebuild any of the utility tasks and none of
the user mode diagnostics, only those queries under the
heading UTILITY TASKS are displayed. The queries under the
heading USER MODE DIAGNOSTICS are omitted.
If you wish to build user mode diagnostics
(provided that
user mode diagnostic support was selected in part 1) and not
rebuild any utility tasks, only those queries under the
heading USER MODE DIAGNOSTICS are displayed. The queries
concerning rebuilding utility tasks are omitted.
If you wish to rebuild utility tasks and also
mode diagnostics, both sections are displayed.

build

user

***UTILITY TASKS***
IN ORDER FOR THE UTILITY TASKS TO USE ANSI FORMAT TAPE
THEY MUST BE BUILT WITH THE ANSI FCS ROUTINES. THESE
ROUTINES MAY CAUSE CERTAIN TASKS TO INCREASE BEYOND THE
NORMAL 8K SIZE.
IF YOU WANT TO BUILD THE UTILITY TASKS WITH
ANSI MAGTAPE SUPPORT, YOU HAVE TO EDIT THE TASK
BUILD COMMAND FILES FOR THESE TASKS.
The task-build command file for a particular utility task
has to be edited only if the task size turns out to be above
8K words. This means that SYSGEN3 may have to be run a
second time.
YOU MUST ALSO INCLUDE THE FILE CONTROL SERVICES ROUTINES
FOR ANSI MAGTAPE SUPPORT IN SYSLIB.
As described above, you must include the ANSI magtape FCS
routines in SYSLIB,
if you have selected ANSI magtape
support. It is possible that these changes to SYSLIB have
already been made by a previous SYSGEN3 on this disk.
If
so, answer Y to the next question.
* IS SYSLIB ALREADY CORRECT FROM A PREVIOUS RUN OF THIS FILE?

[YIN]:

the next section is
If the answer to this question is Y,
bypassed.
Otherwise the following commands create a new
version of SYSLIB.
INS $PIP
INS $LBR
If you are using the dual RK05 kit, the RK05 unit containing
the BASLINE disk is assigned to the pseudo device SY:.

3-100

SYSGEN DIALOGUE DETAILS
ASN DKn:=SY:
SET IUIC=[l,l]
If you are using an RLOI kit or either of the RK05 kits, the
following command is issued.
PIP SYSLIB.OLB;*/DE
PIP SYSLIB.OLB=SYSLIB.VIR
If you want the utility tasks to support ANSI magtape,
answer Y to the next question, and the following command is
executed to include the FCS routines in SYSLIB.
* DO YOU WANT THE UTILITY TASKS TO SUPPORT ANSI MAGTAPE? [YIN]:
LBR SYSLIB/RP=FCSMTA
Further processing for an RK05 system continues with the REM
PIP command below.
For systems with an RP, RK06, RM03 as system disk,
if ANSI
magtape support was selected, the special version of SYSLIB
called ANSLIB containing the ANSI routines, was created
during SYSGEN part 2. Furthermore, the ARITH module in both
SYSLIB and ANSLIB is already the correct one.
Therefore, processing for RP, RK06, RM03
ask only the following question.

systems

INS $PIP
INS $LBR
SET IUIC=[l,l]
* DO YOU WANT THE UTILITY TASKS TO SUPPORT ANSI MAGTAPE?

needs

[YIN]:

If the answer to this question is Y, the following command
is issued to t~mporarily rename ANSLIB to SYSLIB~ for use
during the task-builds to come.
It will later be renamed
back to SYSLIB. As a result of this, two passes are needed
if you are building the utilities with or without ANSI
support.
PIP SYSLIB.OLB/NV=ANSLIB.OLB
Processing continues here for systems
support, whatever the system disk is.

with

ANSI

magtape

REM PIP
REM LBR
Processing continues here for all
magtape support was selected or not.

systems

whether

ANSI

MOST OF THE TASKS TO BE BUILT HAVE TASK BUILD
COMMAND FILES WHICH SPECIFY PARTITION GEN OR
PAR14K. GEN IS ASSUMED TO BE 40000(8) BYTES LONG
AND IS ASSUMED TO BE BASED AT 40000(8).
PAR14K IS A PARTITION WHICH IS 70000(8) BYTES LONG
AND IS ASSUMED TO BE BASED AT 40000(8).
For a mapped system, no physical base addresses are required
for partitions, and the corresponding two lines above are
suppressed.

3-101

SYSGEN DIALOGUE DETAILS

TASK FTB IS A FAST TASK BUILDER WITH LIMITED FUNCTIONALITY.
IT DOES NOT SUPPORT OVERLAYS OR GLOBAL CROSS-REFERENCE
BUT IT IS THREE TIME FASTER THAN BIGTKB. IT REQUIRES
A 20K PARTITION TO RUN1IN AND IS NOT DISTRIBUTED IN TASK
IMAGE FORM. YOU MUST BUILD IT IF YOU INTEND TO USE IT.
THE TASK DSC IS THE DISK SAVE AND COMPRESS UTILITY. IT IS
DISTRIBUTED AS A STANDALONE SYSTEM ON ALL DISTRIBUTION SYSTEMS
AS DSCSYS.SYS.
IT MAY ALSO BE BUILT AS A TASK, BUT IS NOT
DISTRIBUTED IN THAT FORM.
IT REQUIRES A 16K PARTITION TO RUN IN.
ALL OF THE TASK BUILD COMMAND FILES BUILD CHECKPOINTABLE
TASKS FOR USE WITH SYSTEMS WITH DYNAMIC ALLOCATION OF
CHECKPOINT SPACE.
IF YOUR SYSTEM DOES NOT SUPPORT
THIS OPTION, INSTALL WILL DEFAULT THEM TO NON-CHECKPOINTABLE.
IF YOU WISH YOU MAY BUILD TASKS WHICH ARE CHECKPOINTABLE
AND WHICH ALLOCATE SPACE IN THEIR TASK IMAGE BY CHANGING
THE ICP SWITCH TO THE IAL SWITCH IN THE BUILD COMMAND FILE.
NOTE: TASKS WHICH ALLOCATE CHECKPOINT SPACE IN THEIR
TASK IMAGE REQUIRE MORE DISK SPACE THAN TASKS THAT DON'T.
NOTE THAT THE TASKS TEC, VTEC, RNO, AND SRD ARE NOT SUPPORTED
PRODUCTS. THEY HAVE BEEN ADDED TO THE SYSGEN3 PROCEDURE
; FOR YOUR CONVENIENCE.
SET IUIC=[1,2x]
INS $EDI
* DO YOU WANT TO BUILD TASK MAC? [YIN]:
* DO YOU WANT TO EDIT TASK MACiS BUILD COMMAND FILE? [YIN]:
EDI MACBLD.CMD
The previous three lines serve the following purposes:
1.

to decide whether to build task MAC

if MAC is to be built, to edit
file, if desired

the

build

command

If the first question is answered with N, the two following
lines do not appear.
If the first question is answered with
Y, and the second with N, the EDI command is not issued.
In the following, a similar sequence is performed
utility task.

* DO YOU WANT TO BUILD TASK BIGMAC? [YIN]:

for

* DO YOU WANT TO EDIT TASK BIGMACiS BUILD COMMAND FILE? [YIN]:
EDI BIGMACBLD.CMD
* DO YOU WANT TO BUILD TASK TKB? [YIN]:
* DO YOU WANT TO EDIT TASK TKB'S BUILD COMMAND FILE? [YIN]:
EDI TKBBLD.BMD
* DO YOU WANT TO BUILD TASK BIGTKB? [YIN]:
* DO YOU WANT TO EDIT TASK BIGTKB'S BUILD COMMAND FILE? [YIN]:
EDI BIGTKBBLD.CMD
* DO YOU WANT TO BUILD TASK PIP? [YIN]:
* DO YOU WANT TO EDIT TASK PIP'S BUILD COMMAND FILE? [YIN]:
EDI PIPBLD.CMD
* DO YOU WANT TO BUILD TASK FLX? [YIN]:
* DO YOU WANT TO EDIT TASK FLX'S BUILD COMMAND FILE? [YIN]:
EDI FLXBLD.CMD
* DO YOU WANT TO BUILD TASK VFY? [YIN]:
* DO YOU WANT TO EDIT TASK VFY'S BUILD COMMAND FILE? [YIN]:
EDI VFYBLD.CMD
* DO YOU WANT TO BUILD TASK DMP? [YIN]:
3-102

each

SYSGEN DIALOGUE DETAILS

* DO YOU WANT TO EDIT TASK DMP'S BUILD COMMAND FILE? [yiN]:
EDI DMPBLD.CMD
* DO YOU WANT TO BUILD TASK EDI? [YIN]:
* DO YOU WANT TO EDIT TASK EDI'S BUILD COMMAND FILE? [YIN]:
EDI EDIBLD.CMD
* DO YOU WANT TO BUILD TASK SLP? [YIN]:
* DO YOU WANT TO EDIT TASK SLP'S BUILD COMMAND FILE? [YIN]:
EDI SLPBLD.CMD
* DO YOU WANT TO BUILD TASK LBR? [YIN]:
* DO YOU WANT TO EDIT TASK LBR'S BUILD COMMAND FILE? [YIN]:
EDI LBRBLD.CMD
* DO YOU WANT TO BUILD TASK TEC? [YIN]:
* DO YOU WANT TO EDIT TASK TEC'S BUILD COMMAND FILE? [YIN]:
EDI TECBLD.CMD
* DO YOU WANT TO BUILD TASK VTEC? [YIN]:
* DO YOU WANT TO EDIT TASK VTECiS BUILD COMMAND FILE? [YIN]:
EDI VTECBLD.CMD
* DO YOU WANT TO BUILD TASK PSE? [YIN]:
* DO YOU WANT TO EDIT PSE'S BUILD COMMAND FILE? [YIN]:
EDI PSEBLD.CMD
* DO YOU WANT TO BUILD TASK SYE? [YIN]:
* DO YOU WANT TO EDIT SYE'S BUILD COMMAND FILE? [YIN]:
EDI SYEBLD.CMD
* DO YOU WANT TO BUILD TASK CRF? [YIN]:
* DO YOU WANT TO EDIT TASK CRF'S BUILD COMMAND FILE? [YIN]:
EDI CRFBLD.CMD
* DO YOU WANT TO BUILD TASK ZAP? [YIN]:
* DO YOU WANT TO EDIT TASK ZAP'S BUILD COMMAND FILE? [YIN]:
EDI ZAPBLD.CMD
* DO YOU WANT TO BUILD TASK BAD? [YIN]:
* DO YOU WANT TO EDIT TASK BAD'S BUILD COMMAND FILE? [YIN]:
EDI BADBLD.CMD
* DO YOU WANT TO BUILD TASK VMR? [YIN]:
* DO YOU WANT TO EDIT TASK VMR'S BUILD COMMAND FILE? [YIN]:
EDI VMRBLD.CMD
* DO YOU WANT TO BUILD TASK RNO? [YIN]:
* DO YOU WANT TO EDIT TASK RNO'S BUILD COMMAND FILE? [YIN]:
EDI RNOBLD.CMD
* DO YOU WANT TO BUILD TASK SRD? [YIN]:
* DO YOU WANT TO EDIT TASK SRD'S BUILD COMMAND FILE? [YIN]:
EDI SRDBLD.CMD
* DO YOU WANT TO BUILD TASK FTB? [YIN]:
* DO YOU WANT TO EDIT TASK FTB'S BUILD COMMAND FILE? [YIN]:
EDI FTBBLD.CMD
* DO YOU WANT TO BUILD TAS CMP? [YIN]:
* DO YOU WANT TO EDIT TASK CMP'S BUILD COMMAND FILE? [YIN]:
EDI CMPBLD.CMD
* DO YOU WANT TO BUILD TASK PAT? [YIN]:
* DO YOU WANT TO EDIT TASK PAT'S BUILD COMMAND FILE? [YIN]:
* DO YOU WANT TO BUILD TASK DSC? [YIN]:
* DO YOU WANT TO EDIT TASK DSC'S BUILD COMMAND FILE? [YIN]:
EDI DSCBLD.CMD
* DO YOU WANT TO BUILD TASK CDA? [YIN]:
* DO YOU WANT TO EDIT CDA'S BUILD COMMAND FILE? [YIN]:
EDI CDABLD.CMD
* DO YOU WANT TO BUILD TASK EDT? [YIN]:
* DO YOU WANT TO EDIT EDT'S BUILD COMMAND FILE? [YIN]:
EDI EDTBLD.CMB
If you are using the single RK05 distribution kit,
you
cannot build the RMS utilities. The RMS utilities can only
be built when using any of the other kits, hence the
following querles,
pertinent to RMS, are not displayed in
SYSGEN using the single RK05 kit.

3-103

SYSGEN DIALOGUE DETAILS
* DO YOU WANT TO BUILD THE RMS UTILITIES?

[YIN]:

If you answer affirmatively,
the
following
queries,
pertinent to RMS utilities, are displayed. Otherwise, they
are omitted.
* DO YOU WANT TO BUILD TASK RMSBCK?
* DO YOU WANT TO EDIT TASK RMSBCK'S
EDI RMSBCKBLD.CMD
* DO YOU WANT TO BUILD TASK RMSCNV?
* DO YOU WANT TO EDIT TASK RMSCNV'S
EDI RMSCNVBLD.CMB
* DO YOU WANT TO BUILD TASK RMSDEF?
* DO YOU WANT TO EDIT TASK RMSDEF'S
EDIT RMSDEFBLD.CMD
* DO YOU WANT TO BUILD TASK RMSDFN?
* DO YOU WANT TO EDIT TASK RMSDFN'S
EDI RMSDFNBLD.CMD
* DO YOU WANT TO BUILD TASK RMSDSP?
* DO YOU WANT TO EDIT TASK RMSDSP'S
EDI RMSDSPBLD.CMD
* DO YOU WANT TO BUILD TASK RMSRST?
* DO YOU WANT TO EDIT TASK RMSRST'S
EDI RMSRSTBLD.CMD

[YIN] :

BUILD COMMAND FILE? [YIN] :
[YIN]:

BUILD COMMAND FILE? [YIN] :
[YIN] :

BUILD COMMAND FILE? [YIN] :

INS [l,Sy]PIP
INS [l,Sy]BIGTKB
* DO YOU WANT TO PRINT THE MAPS FOR THE UTILITY TASKS? [YIN]:
The maps for the utility tasks are of little use, and this
question is normally answered with an N, in which case no
maps are generated.
THE TASK MAPS WILL BE PRINTED ON
YOUR TERMINAL
; THE LINE PRINTER
LOA LP:
The next display is dependent upon the distribution kit
are using.

you

If you are using an RLOl distribution kit or either of the
RKOS distribution kits, you must make some preparations
prior to building the utility tasks.
Read the section
pertinent to your distribution kit.
If you are using a distribution kit other than an RL01,
single RKOS, or dual RKOS, no preparations are necessary.
**Single RKOS and RLOl Kits**
DEPENDING ON THE SECONDARY STORAGE MEDIUM AND THE NUMBER
OF TASKS TO BE COPIED, YOU MAY HAVE TO MOUNT A BLANK MEDIUM
IN THE DRIVE AFTER COPYING A TASK. THE RECOMMENDED NUMBER OF FILES
PER MEDIUM IS:
RKOS,RLOl AND MAGTAPE (TS03,RU10,TU16,TU4S) - ALL TASKS WILL FIT
FLOPPY DISK AND DECTAPE - 4 TASKS PER DISK OR TAPE
CASSETTE - 1 TASK PER CASSETTE
IF YOUR SECONDARY STORAGE IS OTHER THAN RKOS, RLOl OR MAGTAPE,

3-104

SYSGEN DIALOGUE DETAILS
AFTER COPYING A TASK, YOU WILL BE ASKED IF YOU WISH TO MOUNT
A NEW MEDIUM.
IF SO THE INDIRECT FILE PROCESSOR WILL
PAUSE TO ALLOW TIME TO MOUNT IT.
THE FOLLOWING ARE LEGAL SECONDARY STORAGE DEVICES:
DK
(RK05 DISK, FOR RK05 DISTRIBUTION KITS ONLY)
DL
(RLOl DISK, FOR RLOl DISTRIBUTION KITS ONLY)
DX
(RXOl FLOPPY DISK)
CT
(TU60 CASSETTE TAPE)
DT
(TU56 DECTAPE)
MT
(TS03, TEIO, OR TUIO MAGTAPE)
(TU16, TE16, OR TU45 MAGTAPE)
MM
* ENTER DEVICE FOR SECONDARY STORAGE [DDU]
The next query displayed
storage device.

[S]:

dependent

your

secondary

*DK: or DL: as Secondary Storage Device*
was

entered

until

the

The following assumes DK:
storage device.

the

secondary

device

ready

PUT YOUR TARGET SYSTEM DISK IN DK:
* IS DK:

READY?

[YIN]:

This query
response) .

* ENTER VOLUME LABEL OF DK:

repeated

[S] :

The device is then mounted using this volume label.
MOU DK:

label
*DX: as Secondary Storage Device*
If DX:

is not loaded, the MCR LOA command is issued.

LOA DX:
*CT:,DT:,MT:, or MM:, as Secondary Storage*
The following assumes DT:
storage device.

was

entered

the

secondary

If the secondary storage device is not loaded, the
command is isssued.

MCR

LOA

LOAD DT:
**Dual RK05 Kits**
* DO YOU HAVE AN EMPTY RK05 REMOVABLE DRIVE AVAILABLE?

[YIN]:

If not, instructions are given for copying the task
files from secondary storage to the system disk.
If an empty drive is available, you are
the unit number.
* WHAT IS THE UNIT NUMBER OF THE EMPTY DRIVE?

3-105

asked

[0 R:0-3]:

image

identify

SYSGEN DIALOGUE DETAILS
The following assumes that DK2:

is the empty drive.

PLACE THE SYSTEM DISK IN DK2: AND START IT UP (WRITE
ENABLED). WE WILL COpy THE TASKS DIRECTLY TO THE SYSTEM DISK.

* IS THE SYSTEM DISK READY? [Y/N]:
This question is repeated until the disk
response). When ready, the disk is mounted.

ready

MOU DK2:SYSTEM

* WAS THE SYSTEM DISK MOUNTED SUCCESSFULLY?

[Y/N]:

If not, the MOU command is issued again.
NOW WE BUILD THE REQUESTED UTILITY TASKS
ASN LP:=MP:
ASN TT:=MP:
ASN NL:=MP:
SET /UIC=[1,20]
The selected utility tasks are now built.
If you are using the RLOI distribution kit or either of the
RKOS distribution kits, the build files are copied to your
secondary storage device and the old versions are deleted.
Depending on your secondary storage device, either PIP or
FLX is used to accomplish this (PIP for DL:, DK:, or DX: as
secondary storage and FLX for CT:, DT:, MM:, MT:
as
secondary storage).
The appropriate command is issued
following the task builder directive. The following is an
example of the display for a dual RKOS SYSGEN using an RKOS
(DK:) for secondary storage.
TKB @[1,2x] MACBLD
PIP DK: [l,Sx]/NV=[l,Sx]MAC.TSK
* WAS MAC COPIED SUCCESSFULLY? [Y/N]:
PIP [l,Sx]MAC.TSK;O/DE
For brevity, the PIP and/or FLX commands, which appear only
if you are using an RLOI kit or either of the RKOS kits, are
omitted here.
Note that all commands are suppressed for a specific task if
that task was not selected to be rebuilt. The following
displays all of the tasks.
Similar commands are issued to build each of the selected
utility tasks.
In some cases, the old versions are purged
(PIP .•. /PU), leaving the most recent version,
instead of
being deleted
(PIP ... /DE). The reason for this is to keep
tasks that may be required at later stages during SYSGEN.
TKB @[1,2x]MACBLD
TKB @[1,2x]BIGMACBLD
TKB @[1,2x]TKBBLD
TKB @[1,2x]BIGTKBBLD
TKB @[1,2x]PIPBLD
TKB @[1,2x]FLXBLD
TKB @[1,2x]VFYBLD
TKB @[1,2x]DMPBLD

3-106

SYSGEN DIALOGUE DETAILS
TKB @[1,2x]EDIBLD
TKB @[1,2x]SLPBLD
TKB @[1,2x]LBRBLD
TKB @[1,2x]PSEBLD
TKB @[1,2s]SYEBLD
TKB @[1,2x]CRFBLD
TKB @[1,2x]ZAPBLD
TKB @[1,2x]BADBLD
TKB @[1,2x]VMRBLD
TKB @[1,2x]PATBLD
TKB @[1,2x]CDABLD
TKB @[1,2x]CMPBLD
TKB @[1,2x]FTBBLD
TKB @[1,2x]DSCBLD
TKB @[1,2x]RNOBLD
TKB @[1,2x]TECBLD
TKB @[1,2x]SRDBLD
TKB @[1,2x]EDTBLD
TKB @[1,2x]RMSBCKBLD
TKB @[1,2x]RMSCNVBLD
TKB @[1,2x]RMSDEFBLD
TKB @[1,2x]RMSDFNBLD
TKB @[1,2x]RMSDSPBLD
TKB @[1,2x]RMSRTIBLD
TKB @[1,2x]VTECBLD
The task-builds are complete.
If user mode diagnostics were to be built, control passes to
the indirect command file BLDUMD.CMD (see Section x.x.x).
The task image files that have been built (utilities and/or
user mode diagnostics) will now be transferred to secondary
storage.
WE WILL PAUSE NOW TO ALLOW YOU TO COpy
- ANY FILES THAT WERE NOT SUCCESSFULLY TRANSFERRED
- THE DIAGNOSTIC TASKS
WHEN THE DIAGNOSTIC TASKS HAVE BEEN COPIED, YOU
MAY DELETE THEM FROM THIS DISK.
WHEN DONE, RESUME AT. AS SHOWN BELOW.
If only user mode diagnostics were selected to be built and
no utility task, an example of how to do the transfers is
displayed like the one below.
(PUT A BLANK MEDIUM IN MTO:)
>REM PIP
>INS [1,54]FLX;-1
>FLX MTO:/ZE
>FLX MTO:/DO=RK05.TSK/RS,TS03.TSK,TERM.TSK
>RES ••• AT.
AT.

PAUSING.

TO CONTINUE TYPE "RES ••. AT."

At this time, you may manually copy any files that were not
successfully transferred by the previous commands, and/or
the user mode diagnostics if they were selected to be built.
DMO DXO:
UNL DXO:

3-107

SYSGEN DIALOGUE DETAILS
The secondary storage is dismounted and the driver unloaded.
If you have a dual-RK05 system, the task image files are now
resident
on
the target system disk.
Otherwise, the
following section of text is displayed to guide you in
transferring the task image files to the target system disk.
TO COpy THE TASK IMAGE FILES FROM THE SECONDARY
STORAGE MEDIUM TO THE SYSTEM DISK, PROCEED AS FOLLOWS
AFTER SYSGEN3 HAS TERMINATED:
If your secondary storage is DX, the following example
displayed (u is replaced by the actual unit number):

(BOOT THE SYSTEM DISK)
>SET /UIC=[l,5x]
>INS PIP
>LOA DX:
REPEAT FROM HERE .•.
REPLACE "TASKX" BY
ACTUAL VOLUME LABEL

>MOU DXu:TASKX
>PIP =DXu:*. *
>DMO DXu:

... TO HERE FOR ALL VOLUMES
USED FOR TRANSFER

>UNL DX:
>REM PIP
If your secondary storage is MT, MM, CT or DT, the following
example is displayed (dd is replaced by the actual device
mnemonic, and u is replaced by the actual unit number):
(BOOT THE SYSTEM DISK)
>SET /UIC=[1,5x]
>INS FLX
>LOA dd:
REPEAT FROM HERE ..•
>FLX =ddu:*.*
•.• TO HERE FOR ALL VOLUMES
USED FOR TRANSFER
>UNL dd:
>REM FLX
>INS PIPj-l
>@MTSKCO

MAKE TASK FILES CONTIGUOUS
A SERIES OF PIP COMMANDS FOLLOW

>@ <EOF>
>PIP MTSKCO.CMDjO/DE
>REM PIP
REM FLX
REM INI
REM UFD
REM PIP
***USER MODE DIAGNOSTICS***
Due to space limitations and the physical locations of files
on the RK05 distribution kits, the user mode diagnostics are
built in slightly differing ways.
Read
the
section
pertinent to your distribution kit.

3-108

SYSGEN DIALOGUE DETAILS
SET IUIC=[1,20]
**Single RK05 and RLOl Kits**
NOW WE BUILD AND COpy THE TASKS TO THE SECONDARY
STORAGE MEDIUM.
DEPENDING ON THE SECONDARY STORAGE MEDIUM AND THE NUMBER
OF TASKS TO BE COPIED, YOU MAY HAVE TO MOUNT A BLANK MEDIUM
IN THE DRIVE AFTER COPYING A TASK. THE RECOMMENDED NUMBER OF FILES
PER MEDIUM IS:
RK05,RLOl AND MAGTAPE (TS03,TUIO,TU16,TU45) - ALL TASKS WILL FIT
FLOPPY DISK AND DECTAPE - 4 TASKS PER DISK OR TAPE
CASSETTE - 1 TASK PER CASSETTE
IF YOUR SECONDARY STORAGE IS OTHER THAN RK05, RLOl OR MAGTAPE,
AFTER COPYING A TASK, YOU WILL BE ASKED IF YOU WISH TO MOUNT
A NEW MEDIMUM.
IF SO THE INDIRECT FILE PROCESSOR WILL
PAUSE TO ALLOW TIME TO MOUNT IT.
THE FOLLOWING ARE LEGAL SECONDARY STORAGE DEVICES:
DK
(RK05 DISK, FOR RK05 DISTRIBUTION KITS ONLY)
DL
(RLOl DISK, FOR RLOl DISTRIBUTION KITS ONLY)
DX
(RXOl FLOPPY DISK)
CT
(TU60 CASSETTE TAPE)
DT
(TU56 DECTAPE)
MT
(TS03, TEIO, OR TUIO MAGTAPE)
MM
(TU16, TE16, OR TU45 MAGTAPE)
* ENTER DEVICE FOR SECONDARY STORAGE [DDU]
The next query displayed
storage device.

[S]:

dependent

your

secondary

*DK: or DL: as Secondary Storage Device*
was

entered

until

the

The following assumes DK:
storage device.

the

secondary

device

ready

PUT YOUR TARGET SYSTEM DISK IN DK:
* IS DK:

READY?

[YIN]:

This query
response) •

* ENTER VOLUME LABEL OF DK:

repeated

[S] :

The device is then mounted using this volume label.
MOU DK:volume label
Control then passes to the indirect command file
(see that Section).

BLDUMD.CMD

*DX: as Secondary Storage Device*
If DX:

is not loaded, the MCR LOA command is issued.

LOA DX:
TO COpy THE TASK IMAGE FILES FROM THE SECONDARY
STORAGE MEDIUM TO THE SYSTEM DISK, PROCEED AS FOLLOWS
AFTER SYSGEN3 HAS TERMINATED:

3-109

SYSGEN DIALOGUE DETAILS

z
(BOOT THE SYSTEM DISK)
)SET JUIC = [1,5x]
)INS $PIP
)LOA DX:
!REPEAT FROM HERE •..
)MOU DX:TASKX
REPLACE "TASKX" BY
ACTUAL VOLUME LABEL
)PIP = DX:*.*
)DMO DX:
! ••. TO HERE FOR ALL VOLUMES
!USED FOR TRANSFER
)UNL DX:
Control then passes to the indirect command file
(see Section x.x.x).

BLDUMD.CMD

*CT:, DT:, MT:, or MM: as Secondary Storage Device*
The following assumes DT:
storage device.

was

entered

the

secondary

If the secondary storage device is not loaded, the
command is issued.

MCR

LOA

LOA DT:
TO COpy THE TASK IMAGE FILES FROM THE SECONDARY
STORAGE MEDIUM TO THE SYSTEM DISK, PROCEED AS FOLLOWS
AFTER SYSGEN3 HAS TERMINATED:
(BOOT THE SYSTEM DISK)
)SET IUIC
[1,5x]
)INS $FLX
)LOA DT:
REPEAT FROM HERE ...
)FLX = DT:*.*
.•• TO HRE FOR ALL VOLUMES
USED FOR TRANSFER
)UNL DT:
)REM FLX
Control then passes to the indirect command file
(see Section xxx).

BLDUMD.CMD

**Dual RK05 Kits**
* DO YOU HAVE AN EMPTY RK05 REMOVABLE DRIVE AVAILABLE?

[YIN]:

If not, instructions are given for copying the task
files from secondary storage to the system disk.
If an empty drive is available, you are
the unit number.

* WHAT IS THE UNIT NUMBER OF THE EMPTY DRIVE?
The following assumes that DK2:

asked

identify

[0 R:O-3]:

is the empty drive.

PLACE THE SYSTEM DISK IN DK2: AND START IT UP (WRITE
ENABLED). WE WILL COpy THE TASKS DIRECTLY TO THE SYSTEM DISK.

3-110

image

SYSGEN DLALOGUE DETAILS

* IS THE SYSTEM DISK READY?

[YIN]:

This question is repeated until the disk
response). When ready, the disk is mounted.

ready

the

indirect

MOU DK2: SYSTEM
* WAS THE SYSTEM DISK MOUNTED SUCCESSFULLY?

[YIN]:

If not, the MOUnt command is issued again.
If mounted successfully, control passes to
command file BLDUMD.CMD (see Section x.x.x).
**All Kits Except RLOI Kit and RK05 Kits**
Control is passed directly to the
BLDUMD.CMD (see Section x.x.x).

indirect

command

file

End of SYSGEN part 3.
3.6

BLDUMD.CMD FILE DETAILS

BLDUMD is the indirect command file to task-build all or selected User
Mode Diagnostics.
BLDUMD is called from SYSGEN part 3 if the
corresponding question is answered appropriately.
It may also be
called manually at any time with the following command:
>@[200,200]BLDUMD
The following is a detailed description of all the steps in BLDUMD.
BLDUMD <VERSION 03.1>
COPYRIGHT (C) 1976, 1977
DIGITAL EQUIPMENT CORP., MAYNARD, MASS.

01754

BUILD ALL OR SELECTED USER MODE DIAGNOSTICS.
;

* ARE YOU RUNNING ON A MACHINE WITH AT LEAST 24K WORDS? [YIN]:
If the answer is N, the
BLDUMD terminates.

following

text

displayed

and

SORRY, YOU CANNOT BUILD (OR RUN) THE USER MODE DIAGNOSTICS
ON A MACHINE WITH LESS THAN 24 K WORDS!
Otherwise, processing continues here.
As in the previous sections of
your distribution kit.

SYSGEN,

* DO YOU HAVE THE DUAL RK05 DISTRIBUTION KIT?

you

must

identify

[YIN]:

If you do, you are asked to identify the RK05 drives that
contain the UTILOBJ and BASLINE disks. The UTILOBJ disk is
then assigned to SY: and the BASLINE disk is assigned to
LB: •

3-111

SYSGEN DIALOGUE DETAILS

* IN WHICH RK05 DRIVE IS THE UTILOBJ DISK MOUNTED?
* IN WHICH RK05 DRIVE IS THE BASLINE DISK MOUNTED?
The following assumes DKO:
for the BASLINE disk.

[0 R:O-3]:
[0 R:O-3]:

for the UTILOBJ

disk

and

DKl:

If you replied negatively to the dual RKOS query,
query displayed is

the

ASN DKO:=SY:
=LB:
ASN DKl:

* IS THE CURRENT SYSTEM DISK AN RP02/03/04/0S/05 OR RK06?
* DO YOU WANT EXPANDED COMMENTS FOR THE UMD BUILD PROCEDURE?

[YIN]:

Expanded comments provide a lot of descriptive text that the
experienced user might want to dispense with.
DIAGNOSTIC TASKS CAN BE BUILT FOR THE FOLLOWING DEVICES:
MNEMONIC
DB:
DB:
DB:
DF:
OK:
OM:
DP:
DP:
DP:
OS:
OS:
DT:
MM:
MM:
MT:
MT:
TT:

DEVICE

RJP04/RWP04
RJP05/RWP05
RJP06/RWP06
RFll/RSll
RKll/RKOS
RK6ll/RK06
RPll/RP02
RPll/RP03
RPllE/RPR02
RJS03/RWS03
RJS04/RWS04
TCll/TU56
TJU16/TWU16
TJU16/TWU45
TMAll/TUlO
TMAll/TS03
TERMINAL

DIAGNOSTIC NAME
RP04
RP05
RP06
RFll
RK05
RK06
RP02
RP03
RPR02
RS03
RS04
TU56
TU16
TU45
TU10
TS03
TERM

;

* DO YOU WANT DIAGNOSTICS FOR A MAPPED SYSTEM? [YIN] :
;

SET UIC=[1,2x]
If you are using other than a dual RKOS distribution kit,
the task image files will be generated on the system disk,
and the next section is bypassed.
THE DIAGNOSTIC TASKS WILL BE STORED ON THE SYSTEM DISK BY DEFAULT.
IF YOUR SYSTEM DISK IS AN RK05 YOU MAY BE REQUIRED TO STORE THE
DIAGNOSTICS ON A SEPARATE DISK TO AVOID ALLOCATION PROBLEMS.
IF YOU HAVE THE DUAL RK05 RELEASE KIT, YOU SHOULD SPECIFY
THAT THE DIAGNOSTICS BE STORED ON ANOTHER DISK. IF YOU HAVE
A THIRD RK05 PUT THE PRIVOBJ DISK IN IT AND STORE THE DIAGNOSTICS
ON IT. OTHERWISE, STORE THEM ON LBO:.

3-112

SYSGEN DIALOGUE DETAILS

* DO YOU WANT THE DIAGNOSTICS STORED ON ANOTHER DISK? [YIN]:
If this question is answered with an N, the next section is
bypassed.
Otherwise, you are asked for the device mnemonic
and unit number of the disk where to store the diagnostics.

* ENTER THE OUTPUT DEVICE NAME AND UNIT NUMBER (E.G.

DKl)

[S]:

It is assumed in the following lines that you answered
question with DKI.

this

THE COMMAND BUILD FILE WILL NOW PAUSE WHILE YOU MOUNT DK1:
YOU MUST CREATE THE UFD'S [1,3x] AND [1,5x] ON THE DISK
(THE FORMER ONLY IF YOU WANT THE TASK BUILD MAPS) IF THEY
DO NOT ALREADY EXIST.
EXAMPLE:
>INIT DK1:DIAGNOSTICS
>MOUNT DK1:DIAGNOSTICS
>UFD DK1: [1,3x]
>UFD DK1: [1,5x]
AT.

PAUSING. TO RESUME TYPE "RES ... AT."
Whatever the system disk type is, processing continues here.

DIAGNOSTICS ARE GENERALLY RUN WITH THE FOLLOWING ATTRIBUTES:
PARTITION =
BASE ADDRESS
SIZE =

GEN
40000
40000

The last two lines appear only
diagnostics for an unmapped system.

you

are

building

; IF YOUR SYSTEM IS DIFFERENT ANSWER YES TO THE FOLLOWING QUESTION.

* DO YOU WANT TO ALTER THE DEFAULT PARTITION ATTRIBUTES? [YIN]:
The following three questions are bypassed if
this question with an N.

* ENTER THE PARTITION NAME

(DEFAULT=GEN)

you

(DEFAULT=40000)
(DEFAULT=40000) [S]:

[S]:

* ENTER THE PARTITION BASE ADDRESS

answered

are

building

[S]:

The following question is asked only
diagnostics for an unmapped system.

* ENTER THE PARTITION SIZE

you

THE DIAGNOSTIC TASKS ARE NORMALLY BUILT TO TRANSFER DATA VIA
A 2000 OCTAL BYTE DATA BUFFER. YOU MAY SPECIFY A DIFFERENT
BUFFER SIZE BY ANSWERING THE NEXT QUESTION.
;

* ENTER THE BUFFER SIZE IN OCTAL BYTES

(DEFAULT=2000)

[S]:

NORMALLY DIAGNOSTIC TASK BUILD MAPS ARE NOT REQUIRED.
IN THE UNLIKELY EVENT YOU NEED THEM, ANSWER "YES" TO THE
FOLLOWING QUESTION.

* DO YOU WANT TASK BUILD MAPS? [YIN]:
* DO YOU WANT THE MAPS LISTED ON THE LINEPRINTER? [YIN]:
3-113

SYSGEN DIALOGUE DETAILS

If you answered Y to the first question and N to the second
of the two questions above, the maps will be directed to UFD
[1,3x] on the output disk.
NORMALLY YOU ENTER EACH DIAGNOSTIC NAME REQUIRED FOR YOUR SYSTEM.
AN ALTERNATE METHOD IS PROVIDED WHICH ALLOWS BUILDING ALL
AVAILABLE DIAGNOSTICS. THIS METHOD REQUIRES ABOUT 500 BLOCKS OF
DISK SPACE ON THE OUTPUT DEVICE. THE DIAGNOSTICS THAT DO NOT APPLY
CAN BE DELETED AT A LATER TIME.
;

* DO YOU WANT TO BUILD ALL AVAILABLE DIAGNOSTICS? [YIN]:
* HAVE ALL QUESTIONS BEEN ANSWERED TO YOUR SATISFACTION? [YIN]:
If you answered these questions with N, processing will
restart at the beginning of BLDUMD. Otherwise, if you want
to build all diagnostics, the next section that asks for
diagnostic names is bypassed.
ENTER THE NAME OF THE DIAGNOSTIC TASKS TO BUILD, ONE AT
A TIME. WHEN DONE, ENTER A SINGLE CARRIAGE RETURN.
THE FOLLOWING IS A LIST OF VALID DIAGNOSTIC NAMES:
RP04,RP05,RP06,RFII,RK05,RK06,RP02,RP03,RPR02,RS03
RS04,TU56,TUI6,TU45,TUIO,TS03,TERM
HERE IS A SAMPLE DIALOGUE TO BUILD THE RJP04/RWP04 DISK AND THE
TMAII/TS03 MAGTAPE DIAGNOSTICS ( <CR) = CARRIAGE RETURN) :
NAME [S]:RP04<CR)
NAME [S]:TS03<CR)
NAME [S]:<CR)
The next question requires as a response, the name of
next diagnostic to build, out of the list shown above.

the

* NAME [S]:
If an invalid name
following
message
repeated.

is entered
(for example "XX"), the
is displayed, and the question is

;***** "XX" DIAGNOSTIC IS NOT AVAILABLE*****
The question "* NAME [S]:" is repeated to allow you to enter
the names of all diagnostics to be built. When done, answer
with a single carriage return.
If you chose to build all the diagnostics, or when you have
entered the names of all the desired diagnostics, processing
continues here.
NOW WE TASK BUILD THE SELECTED DIAGNOSTICS
INS $BIGTKB
TKB @UMDBLD
The command above builds the selected diagnostics, according
to specifications defined by the previous sections.

3-114

SYSGEN DIALOGUE DETAILS
REM TKB
End of UMDBLD.
The following sample dialogue builds diagnostics for RK05,
TU16, and terminals to run on an unmapped system. The GEN
partition in that system starts at 50000.
The task image
files are directed to the target system disk which is put in
drive DKl:.
>@[200,200]BLDUMD

>;
>; BLDUMD <VERSION 03.1>

>;
>; COPYRIGHT (C) 1976, 1977
>; DIGITAL EQUIPMENT CORP., MAYNARD, MASS. 01754

>;
>;

BUILD ALL OR SELECTED USER MODE DIAGNOSTICS.

>;
>* ARE YOU RUNNING ON A MACHINE WITH AT LEAST 24K WORDS? [Y/N]:Y
>* DO YOU HAVE THE DUAL RK05 DISTRIBUTION KIT? [YIN]:
>* IS THE CURRENT SYSTEM DISK AN RP02/03/04/05/06 OR RK06? [YIN]: Y
>* DO YOU WANT EXPANDED COMMENTS FOR THE UMD BUILD PROCEDURE? [YIN]:
>* DO YOU WANT DIAGNOSTICS FOR A MAPPED SYSTEM? [YIN]:
>SET IUIC=[1,20]
>* DO YOU WANT THE DIAGNOSTICS STORED ON ANOTHER DISK? [Y/N]:Y
>* ENTER THE OUTPUT DEVICE NAME AND UNIT NUMBER (E.G. DKl) [S]: DKI

>;
>; THE COMMAND BUILD FILE WILL NOW PAUSE WHILE YOU MOUNT DKl:
>; YOU MUST CREATE THE UFD'S [1,30] AND [1,50] ON THE DISK
>; (THE FORMER ONLY IF YOU WANT THE TASK BUILD MAPS) IF THEY
>; DO NOT ALREADY EXIST.

>;
AT. -- PAUSING. TO CONTINUE TYPE "RES •.• AT"
>MOU DKl:UNMOBJ
>RES .•. AT
AT. -- CONTINUING

>
>*
>*
>*
>*
>*
>*
>*
>*

DO YOU WANT TO ALTER THE DEFAULT PARTITION ATTRIBUTES? [Y/N]:Y
ENTER THE PARTITION NAME (DEFAULT=GEN) [S]:
ENTER THE PARTITION BASE ADDRESS (DEFAULT=40000) [S]: 50000
ENTER THE PARTITION SIZE (DEFAULT=40000) [S]:
ENTER THE BUFFER SIZE IN OCTAL BYTES (DEFAULT=2000) [S]:
DO YOU WANT TASK BULD MAPS? [YIN]:
DO YOU WANT TO BUILD ALL AVAILABLE DIAGNOSTICS? [YIN]:
HAVE ALL QUESTIONS BEEN ANSWERED TO YOUR SATISFACTION? [Y/N]:Y

>;
>; ENTER THE NAME OF THE DIAGNOSTIC TASKS TO BUILD, ONE AT
>; A TIME. WHEN DONE, ENTER A SINGLE CARRIAGE RETURN.

>;
>* NAME
>* NAME
>* NAME
>* NAME

[S]: RK05
[S]: TU16
[S]: TERM
[S]:

>;
>; NOW WE TASK BUILD THE SELECTED DIAGNOSTICS

>;
>TKB @UMDBLD

>;
>@ <EOF>

3-115

SYSGEN DIALOGUE DETAILS
3.7

SGN ERROR MESSAGES

The System Generation files issue a message whenever an error in the
response to a query is detected. These messages are listed below in
alphabetical order. Most messages apply to a number of queries.
Those which are specific to a single query are so noted in the
explanatory text following the message.
Each message is preceded by *DIAG*-ILLEGAL VECTOR ADDRESS
The numeric value entered was not on a double word
(the last digit was not 0 or 4).

boundary

Determine the correct vector address and reenter the value.
INVALID ANSWER
The response to the number of clock interrupts is not evenly
divisible into 10,000(10).
Enter a clock rate that evenly divides into 10,000(10).
MODULE xx IS ALREADY IN USE
The specified
previously.

ICR/ICS

UDCll

module

number

was

used

Reenter the correct module number.
MODULES GREATER THAN 252.
The highest module number for the UDCll is 252(10).
Reenter the correct module number.
OVERLAPPING MODULES
The ranges specified for the UDCll modules have at least one
overlapping specification.
Check the module
correct values.

range

specifications

and

reenter

the

RSX-llM/S DOES NOT SUPPORT MIXED MASSBUS DEVICES
Only one type of device
controller.

allowed

single

MASSBUS

Review your configuration requirements and specify only
device type per MASSBUS controller.

3-116

one

SYSGEN DIALOGUE DETAILS

VECTOR ALREADY IN USE
In the specification of vector
following conditions occured:

addresses,

one

the

•

two resident drivers have duplicate vector address values

•

a resident driver and a loadable
vector address values

driver

have

duplicate

•

a loadable driver and a resident
vector address values

driver

have

duplicate

Reenter the correct vector address value.

3-117

CHAPTER 4
GENERATING LARGER SYSTEMS

Most of the features discussed in this chapter are intended for use in
larger systems.
However, some of the features discussed are also
extremely useful in obtaining increased flexibility from a small
system. Potentially useful in small systems are features such as disk
swapping, checkpointing during terminal input, dynamic checkpoint
space allocation, and the ACP-Executive interface.

4.1

DEFINING MEMORY PARTITIONS

In a 16K system, you must observe the partition boundaries defined in
the Baseline System. Specifically, SYSPAR starts at 30l00(8), and GEN
starts at 40000(8).
The two partitions DSKPAR and SECPAR are
partitions for loadable drivers. The system disk driver resides in
DSKPAR, and various secondary storage device drivers as well as the
line printer driver are loaded into SECPAR. This configuration allows
the SYSGEN procedure to be performed on all supported hardware
configurations.
On a 16K system, you can alter the use of the space
dedicated to DSKPAR and SECPAR by building resident drivers instead of
loadable drivers, but this may not be done with SYSPAR and GEN.
If
the system has more than 16K, you have the option of considering a
different partition layout.
The consequences of this flexibility
depend on the size of the user-tailored Executive and whether the
system is mapped or unmapped.

4.1.1

Laying Out Partitions - Software Options

Given the case of having more than 16K of memory (this usually means
memory in at least 8K multiples), you should be aware of certain
DIGITAL-supplied software options before laying out partitions. These
options are described below:
A.

There are two versions of the Task Builder and MACRO-II. The
standard versions operate with 8K of memory. The larger
versions (named BIGTKB and BIGMAC) require a 14K partition,
but run considerably faster than the standard versions.
In
addition, BIGMAC supports the floating point instruction set
and storage allocation assembler directives.
BIGTKB is
required for rebuilding the Task Builder itself.
BIGMAC is
built by the command file BIGMACBLD.CMD, and BIGTKB is built
by the command file BIGTKBBLD.CMD.
In addition,
if the
EXTEND TASK directive is generated for the target system and
BIGMAC and BIGTKB are installed in a system controlled
partition, both use this feature and extend themselves up to
the limit (set by the MCR SET /MAXEXT command) to keep their
symbol tables memory resident.
If this Executive option is

4-1

GENERATING LARGER SYSTEMS

not included, both tasks still benefit from
in partitions larger than 14K.

being

installed

The Files-II ACP (FIIACP) is available in three versions.
The first
(FCPNMH.TSK)
requires 2K of memory and does not
support multi-header files or RMS record-locking. The second
version (FCP.TSK)
supports multi-header files and RMS but
requires 2.SK of memory.
The third version
(BIGFCP.TSK)
supports RMS and multi-header files and operates two to three
times faster than the smaller version. The minimum size of
BIGFCP is 4.SK plus 32 words (22100 octal); however, the
standard task-build command file, BIGFCPBLD.CMD, specifies
options that increase the memory requirements to S.SK.

MCR, FIIACP, and TKTN share a partition in a minimum 16K
system.
If more memory is available, you should consider
dedicating a
partition
to
FCP.
Depending
on
the
characteristics of the software applications, substantial
throughput improvements are possible.
If large disks are being used (RP02/03/04/0S/06 or RK06)
the
system can benefit from the use of more than one file system.
Install as many copies of FIIACP as there are disks and mount
each disk with its own copy by specifying the /ACP switch on
the MOUNT command.
When you generate a system in which MCR shares SYSPAR with
the file system (FIIACP), it is important that you build the
tasks with a partition size that properly reflects the SYSPAR
to be used. This requirement is necessary because the tasks
are checkpointable and have checkpoint space allocated in
their task image files.
In a standard system where MCR and FCPNMH both reside in a
SYSPAR that is 7700(8) bytes long, there is no problem.
If,
however, the multiheader file system FCP is used, SYSPAR must
be increased to 10SOO(8) bytes. As a result, you must modify
the MCR task-build command file to reflect the new partition
size.
An alternative approach on a mapped system is to define
SYSPAR to be a system-controlled partition. Thus, MCR would
not map to the entire partition, but only to the 7700(8)
bytes it requires.
This has the side-effect of requiring
additional Executive dynamic memory. A PCB is permanently
allocated for MCR because it always remains active; a PCB is
allocated for FCP as long as it remains active (such as when
a device is mounted) .
NOTE
If SYSPAR is system controlled, the
SHF, must not be installed in it.

shuffler

task,

The tasks AT., CRF, EDI, LBR, MAC, PIP, TKB, and VFY
determine the size of the partition in which they are
executing, and make use of any additional space for symbol
t~ble
or additional buffer storage. Thus, they benefit from
being installed in a partition larger than 8K.
Similarly,
BIGTKB and BIGMAC benefit if they are installed in a
partition larger than 14K.
If, during
a
task-build,
assembly, or library operation, the condition of insufficient

4-2

GENERATING LARGER SYSTEMS
dynamic memory is reported, the symbol table space must be
expanded by using a larger partition. If these tasks are
installed in a system-controlled partition, the amount of
space allocated to them can be adjusted using the IINC
keyword on the INSTALL command.
If the IINC keyword is
omitted the tasks occupy 8K; BIGMAC and BIGTKB occupy 14K.
E.

You can generate a multi-user system if enough memory exists
to support more than one system task at a time. A multi-user
system has several terminals that can be used simultaneously
for program development or running other tasks. Given enough
memory and a suitable processor, RSX-llM can satisfactorily
support from 2 to 24 or more users who are editing,
compiling, task-building, debugging, and running production
tasks.

You can generate multi-user protection for the system.
This
feature provides protection for the system and users from
destructive interference by others. It limits system access
to users whose identification codes have been put into an
account file by the system administrator.
The availability
of numerous Executive directives is limited for nonprivileged
users,
thus
preventing
destructive
interference.
Furthermore, certain MCR commands are absolutely privileged,
whereas others, which are normally privileged, may be issued
by
nonprivileged users for initializing, mounting, and
dismounting private volumes.

You can split MCR into two cooperating tasks, MCRMU and SYS.
MCRMU is the command dispatcher and executes only a few
commands; SYS processes all the remaining commands normally
provided by the task MCR.
In addition, MCRMU initiates
several copies of SYS as needed to process simultaneous
requests from multiple terminals.

There are a number of optional tasks that are not supplied in
task-image format, but they add considerable usefulness to
the system. The tasks HEL, BYE, and ACNT are required to
support
multi-user protection systems.
BRO and SHUTUP
(neither of which require multiuser resources) broadcast
messages and shut down the system. PSE, SYE, ERL, and ERF
are the tasks which support the error logging features of the
Executive.
MTAACP and FllMSG supply ANSI format magtape
support.
The
task
SHF
reallocates
memory
in
system-controlled partitions when requested by the Executive.
ACS allocates dynamic checkpoint files for the Executive.
PRT is the print spooler that overlaps task execution with
printing of files.
These all require an 8K (or less)
user-controlled partition or a system-controlled partition.
FTB is a fast task builder which requires 20K and builds
nonoverlaid tasks up to 3-4 times faster than BIGTKB. DSC is
the disk save and compress utility that, in task form,
requires 14K.

TKTN ideally runs in a partition in which all tasks are
either checkpointable or execute quickly. In the minimum 16K
configuration, TKTN shares SYSPAR with MCR and FCPNMH.
In
this configuration the following situation can occur. A TAS
command can be·issued with TI: directed to the line printer.
If the line printer is offline, TKTN cannot get into memory
to print the device-offline message. The result is that the
TAS listing does not occur, the printer-not-ready messages do
not occur, and the pool can eventually become exhausted by
the messages queued to TKTN.

4-3

GENERATING LARGER SYSTEMS

One solution to this problem is simply to take care not to
cause
it
to
happen.
However, if this solution is
unreasonable and sufficient memory is available, separate
partitions should be dedicated for TKTN and MeR.
System tuning is application sensitive.
Each installation must
establish optimum trade-offs of hardware and software. The partition
guidelines offered in the following sections are mainly designed to
minimize the duration of the tuning process itself, while maintaining
a balance with known performance and size requirements of system
software.

4.1.2

Partitions - User- and System-Controlled

RSX-IIM supports two kinds of partitions in which tasks can execute:
user-controlled
(or
fixed)
partitions,
and
system-controlled
partitions.

4.1.2.1 User-Controlled
Partitions - A
user-controlled
(main)
partition
can
be
subdivided
into a maximum of seven fixed
subpartitions. A single task can execute in the entire partition, or
up to seven tasks can execute simultaneously in the subpartitions. No
tasks can execute in a subpartition if a task is executing in the
entire main partition.
The main attribute of a user-controlled main partition is that only
one task can be executing in the partition at once, regardless of
memory requirments. This can lead to substantial waste in memory
resources, but gives you absolute control over system activity.
Disregarding checkpointing,
the
allocation
of
user-controlled
partitions and the subpartitions is simple and straightforward. Tasks
are granted residency on the basis of their priority. When a task is
made active,
it is merged into a priority-ordered queue of tasks
waiting to gain residency in the partition. When the paritition is
freed, the highest priority task is granted control of the partition.

4.1.2.2 System-Controlled Partitions - System-controlled partitions
are
contiguous areas of physical memory that are managed and
dynamically allocated to tasks by the Executive.
As many tasks as
will fit are allowed to run simultanedusly in a system-controlled
partition. Tasks are allocated a contiguous region in the partition
and are relocated with the memory management hardware.
Each time a task is activated to run in a system-controlled partition,
the task is merged into a priority-ordered queue of tasks waiting to
be loaded into the partition.
To allocate the system-controlled
partition
(disregarding checkpointing),
the Executive examines the
current state of the partition to determine whether there is enough
contiguous space to load the highest priority task currently in the
partition wait queue. To do this, the Executive examines a list of
allocated areas in the partition and calculates the size of the gaps
that exist between allocated areas. The list of allocated areas is
ordered by physical memory address, which allows a simple computation
of gap size. The first gap that is big enough is allocated to the
task, and its allocation descriptor is merged into the list of
allocated areas.

4-4

GENERATING LARGER SYSTEMS

If a big enough gap cannot be found, the Executive attempts to fit the
task in the system-controlled partition by checkpointing neighboring
tasks of lower priority.
If the task cannot be brought in by
checkpointing, then the, Executive requests the shuffler task (SHF •.. )
if you generated memory compaction
support
for
the
system.
Checkpointing
and shuffling in system controlled partitions is
discussed later in this section. Each time a task exits and frees
memory in the partition, the Executive examines the partition wait
queue and tries to allocate memory to the highest priority waiting
task.

4.1.2.3 Cbeckpointing - RSX-IIM supports checkpointing in both userand
system-controlled
partitions.
The objective is to avoid
preempting a lower priority task, unless a higher priority task can be
brought in to make use of the freed memory. This optimizes the use of
computer system resources while maintaining a priority scheduling
discipline.
Checkpointing in a user-controlled partition occurs under one
conditions:

two

A task requires the user-controlled main partition and is of
a higher priority than any task currently occupying it or any
of its subpartitions.
Furthermore, all of the occupying
tasks must be checkpointable and have checkpointing enabled.
If all these conditions are met, all the tasks that occupy
the partition are written onto a disk and the Executive gives
control of the partition to the higher priority task.

A task requires a subpartition of the user-controlled main
partition, and a lower priority task occupies the main
partition or the subpartition into which the task is to be
loaded.
Furthermore,
the
occupying
task
must
be
checkpointable and have checkpointing enabled. If all these
conditions are met, the task that occupies the partition is
written onto a disk and the Executive gives control of the
subpartition to the higher priority task.

Checkpointing in a system-controlled partition occurs as the result of
a memory allocation failure, as described earlier. That is, the
Executive tries to allocate a contiguous region of a system-controlled
partition to a task and it cannot find an unoccupied memory area of
sufficient size. In this case, the Executive reexamines the list of
allocated areas in the partition to determine whether it can form a
free space of sufficient size by checkpointing one or more neighboring
tasks.
As with user-controlled partitions, each task considered for
checkpointing must be of a lower priority, it must be checkpointable,
and it must have checkpointing enabled.
The Executive scans the list from the beginning, looking for a series
of neighboring tasks, possibly separated by gaps of free space, where
each task satisfies the checkpoint criteria. If the aggregate sum of
the memory occupied by such a series of tasks and free space satisfies
the memory requirement for the higher priority task, the tasks are
checkpointed and the higher priority task is allocated the released
memory. If such a series of neighboring tasks cannot be found and you
generated memory compaction for the system, the Executive calls the
shuffler task to try to bring in the highest priority waiting task by
compacting memory and checkpointing a sufficient number of lower
priority tasks that are not necessarily neighbors in the partition.

4-5

GENERATING LARGER SYSTEMS
4.1.3

Memory Compaction in a

System~Controlled

Partition (Shuffler)

The shuffler's algorithm consists of two
passes
through
the
system-controlled partition;
the steps in each pass are executed
iteratively until the partition reaches a stable state.

4.1.3.1 The Shuffler's First Pass - In the first pass,
the shuffler
starts at the beginning of the system-controlled partition and tries
to move (shuffle) all tasks that are sitting above a gap of free space
down to the base of the free space.
When possible,
it also
checkpoints any tasks that it encounters, which are waiting for
terminal input. Task shuffling occurs in the following steps:
1.

The task is blocked from further execution and
allocates the free space below the task.

the

shuffler

If necessary, the shuffler waits for the task's outstanding
I/O count to reach zero by checking it at intervals of
approximately one-eighth of a second.
If the task I/O count
does not drop to zero in about a half of a second, the
shuffler
marks
the
task's
partition
as
having
long-outstanding I/O, deallocates the free space below the
task, and restarts its first-pass scan of the partition. The
Executive clears the task's partition long-outstanding I/O
indicator when it reduces the task's I/O count to zero.

If the task's I/O count drops to zero within a half of a
second, the shuffler moves the task down to the base of the
free space. The speed of this move increases if the QIO
speed optimizations were included during phase 1 of SYSGEN
and a large BLXIO transfer vector was allocated.

After the move is complete, the task is unblocked to allow
further execution and the free space (now above the task) is
deallocated.

When the shuffler has completed its first pass, all free space in the
partition has been merged into one hole at the top partition. But,
there may be additional holes below tasks which cannot be shuffled.

4.1.3.2 The Shuffler's Second Pass - If the shuffler completes its
first pass and some tasks still are actively competing for memory in
the partition, the shuffler executes its second pass algorithm.
In
the second pass, the shuffler creates an ascending, priority-ordered
list of the tasks in the partition.
It then uses this list to
determine if the size of the waiting task is less than the sum of the
free space in the partition and the size of one or more of the
(lower
priority)
tasks that may be checkpointed.
If the waiting task's size
is less than this sum, the lower priority tasks are checkpointed. The
shuffler then restarts its first-pass algorithm to accumulate the
freed-up space and allocate it to the waiting task.
If tasks that
cannot be shuffled fragment the system-controlled partition, the
second-pass algorithm is executed once for each fragment of the
partition.
If the shuffler completes its second pass without finding space for
the waiting task, it searches for the next system-controlled partition
in the system and exits if there are none.

4-6

GENERATING LARGER SYSTEMS
When the shuffler is active but not actually executing, i.e., waiting
for
task I/O or a checkpoint operation to complete, it places itself
in a state in which it may be checkpointed by any task.
Therefore,
the shuffler does efficiently share a partition with other tasks such
as MCR or FIIACP. However, for large systems the shuffler is more
responsive when it is installed (and FIXED in memory) in a dedicated
partition. Note that the shuffler requires less than .5K words of
memory. The shuffler should never be installed in a system-controlled
partition.
RSX-IIM's philosophy of checkpointing in system-controlled partitions
avoids preempting memory unless it can actually be used. No lower
priority task is checkpointed unless it is known beforehand that
enough contiguous space can be made available to load the higher
priority task.
The one exception is a checkpointable task waiting for
terminal input.
It is swapped out unconditionally to make room for
other tasks whenever the shuffler is activated.
It is not brought
back in until the terminal input request is completed.

4.1.3.3 Unshufflable Tasks - Tasks that have been FIXED in memory can
be shuffled. However, the following occupants of a system-controlled
partition cannot be shuffled and cause free space to be fragmented in
the partition.

4.1.4

Loaded device drivers.

Tasks that are connected to the ICS/ICR-ll or ODC-ll drivers.

A task whose partition was previously marked by the shuffler
as having a long-outstanding I/O and whose I/O count has yet
to drop to zero. Typical extreme examples of this case are
tasks that issued terminal reads and cannot be checkpointed,
LPAll or tasks that have synchronous functions being serviced
by the ARll, LPSll, or tasks using the Connect to Interrupt
Vector directive.

Tasks that have been aborted and fixed by the Executive for a
memory parity error.

Dynamically-created common regions.

Advantages of System-Controlled Partitions

System-controlled partitions are especially useful in multi-user
systems.
By installing all the user tasks in a system-controlled
partition, the Executive allocates space as needed. One user can be
running an 8K task,
such as PIP, while another user is running a
larger task,
such as BIGTKB;
neither user needs a
dedicated
partition.
In essence,
the memory allocation of the system adapts
itself to meet its user's requirements.
If a system-controlled partition is the last real memory partition in
the system
(not including device partitions), the partition's size
will be altered dynamically at bootstrap time to reflect the actual
amount of memory from the beginning of the partition to the end of
physical memory.
Thus, if a system is bootstrapped on a processor having more or less
memory than that recorded in the system image, the partition will be
adjusted to the proper size. As a result, a system generation is not

4-7

GENERATING LARGER SYSTEMS
required to make use of memory that may be added to a configuration in
the future.

4.1.5

Unmapped System - Executive Less Than 8K

All system tasks for an unmapped system run at specific physical
memory addresses and must be rebuilt if they are to run elsewhere.
The tasks distributed on the release disks fall into two classes:
1.

Those built to run at 30100(8)

(SYSPAR partition)

Those built to run at 40000(8)

(GEN partition)

If, after the creation of the user-tailored Executive, $SYTOP exceeds
30100(8), but is less than 40000(8), move the SYSPAR partition to
avoid rebuilding all of the utility tasks.
As a result only the
task-build command files for MCR, FCPNMH, and TKTN need to be edited.
Figure 4-1 depicts a suggested layout for a 24K system where $SYTOP
lies between 30100(8) and 40000(8).
One way to avoid moving SYSPAR is to generate loadable driver support
into the system. Loadable driver support requires less than ten words
in an unmapped Executive. However, it allows you to build a selected
number of loadable drivers in partitions above GEN, reducing the size
of the Executive.
24K

140000(8)
SYSPAR PARTITION
(2K)
130000(8)

22K
USER
ALLOCATABLE
(6K)

100000(8)

16K
PAR14K
PARTITION
(14K)
GEN
SUBPARTITION
(8K)

40000(8)

EXECUTIVE
(8K)

o
Figure 4-1

Typical Unmapped 24K System

4-8

GENERATING LARGER SYSTEMS
Figure 4-1 shows that SYSPAR was moved from its location in the
baseline system (refer to Figure 2-1). Moving SYSPAR requires the
editing of the task-build command files for MCR, FCPNMH, and TKN. The
partition PAR14K is now a real partition
(rather than a pseudo
partition, as was the case in a 16K system) and is correctly placed to
run BIGMAC and BIGTKB without rebuilding them.
Furthermore, because
GEN has not been moved, tasks running in GEN do not need to be
rebuilt.
Finally, a 6K subpartition is available in PAR14K. You are
free to divide this 6K memory block into any configuration of
subpartitions that meets local requirements.
Figure 4-2 illustrates a suggested 28K unmapped system.
It is
identical to Figure 4-1 in its allocation of the 0-24K block of
memory. The additional 4K is allocated to main partition PMDPAR that
PMD uses. Also, the print spooler can use a 2K subpartition, SPLPAR,
leaving an additional 2K to suit your requirements.
28K

160000(8)
PMDPAR PARTITION (4K)
SPLPAR SUBPARTITION (2K)

24K

140000(8)
SYSPAR PARTITION
(2K)

22K

130000(8)

USER
ALLOCATABLE
(6K)

16K

PAR14K
PARTITION
(14K)

100000(8)

GEN
SUBPARTITION
(8K)

40000(8)

EXECUTIVE
(8K)

Figure 4-2

Typical Unmapped 28K System

Both of these layouts are attempts to balance SYSGEN requirements with
known system software requirements. Local requirements may dictate an
alternative scheme. The following system requirements for unmapped
systems should, however, be considered:
1.

Most DIGITAL nonprivileged software requires an 8K partition.
This software assumes that its name is GEN and that it starts
at 40000 (8) •

4-9

GENERATING LARGER SYSTEMS
These tasks
it starts at

MCR, FCPNMH, and TKN require a 2K partition.
assume that its name is SYSPAR and that
30100 (S) •

BIGTKB and BIGMAC require 14K. These tasks assume that the
partition is named PAR14K and that it starts at 40000(S).

Changing a starting address requires editing
files and rebuilding the involved tasks.

the

task-build

command

Changing the partition's name does not require a rebuild, because the
INSTALL command allows you to specify the partition name. However,
the base addresses of the new partition and that for which the task
was built must be the same.

4.1.6

Unmapped System - Executive Greater Than 8K

If the value of $SYTOP exceeds 40000(S) on an unmapped system, all
privileged and nonprivileged system tasks must be rebuilt.
Because
TKB must be rebuilt with BIGTKB, a 24K system is, in general,
the
m1n1mum system for a user-tailored Executive that exceeds SK.* The
layout of partitions becomes a user responsibility, limited only by
the
stated
requirements
for
system software and application
performance goals. Note however, that loadable driver support could
reduce the size of the Executive to below SK.

4.1.7

Mapped Systems

The minimum memory size for a mapped system is 24K.
You need not
rebuild nonprivileged tasks in a mapped system when physical partition
boundaries move. This is true because nonprivileged tasks on a mapped
system run at a virtual base address of zero, rather than at a
physical base address.
Thus,
the value of $SYTOP is much less
critical in a mapped system.
You must always rebuild privileged tasks, as with an unmapped system,
because they are linked to the Executive symbol table file.
You must
rebuild nonprivileged tasks only if you change any of the task's
attributes such as checkpointability. The Task Builder establishes
the attributes when building a task. Consult the RSX-IIM Task Builder
Reference Manual for a comprehensive discussion of task attributes and
associated Task Builder switches.

4.1.S

Example of a Large Mapped System

To realize the highest throughput for a large mapped system, there are
a number of configuration options which must be considered. The
example addresses a system with the following hardware:
PDP-ll/45 with 124K of memory
2 RS04 fixed head disks
2 RK05 disks
2 RP06 disks

* New systems exist in multiples of SK, 16K, and 32K memory stacks.
Existing systems of 20K could support a user-tailored Executive which
exceeded SK.
4-10

GENERATING LARGER SYSTEMS

2 TU16 magtape drives
2 TU56 DECtape drives
1 DHll with 4 remote lines and 12 local lines
1 LPll printer
1 DLII-A line interface
The following partition layout may be used

760000

GEN

210000
SPLPAR

200000
FCPPAR

150000
SYSPAR

140000
DRVPAR

120000
EXEC+
DYNAMIC STORAGE
REGION

o
DRVPAR is a 4K, system-controlled partition for loadable drivers;
this is sufficient for loading all of the device drivers including the
terminal driver. SYSPAR is a 2K partition for MCRMU, TKTN, and the
shuffler.
FCPPAR is a 6K partition for the primary BIGFCP;
this is
sufficient to allocate approximately 50 file control blocks
(FCBs).
SPLPAR is a 2K partition for the print spooler. All other tasks run
in the system-controlled GEN partition. For increased throughput, a
second copy of BIGFCP is installed in GEN to service the second RP06.
In addition to providing overlapped operations, this allows FCBs for
files accessed on the second RP06 to be stored in the second task
image. A third version of the file system should be built and
installed
with
the name DTAACP if you want Files-II DECtape
processing. This version should be the 2K, non-multiheader FCPNMH.
Primary checkpoint space of 1024 blocks is allocated on an RS04
fixed-head disk and secondary space of 2048 blocks is allocated on the
first RP06. Under control of the startup file
[1,2]STARTUP.CMD, all
utility tasks (e.g., BIGMAC, BIGTKB, PIP, EDI, SLP etc.) are copied to
an RS04 and the work files for BIGTKB, BIGMAC, and CRF
(LUN 8)
are
assigned to the second RS04.
This increases system throughput by
providing faster overlay and work file processing.

4.2

BUILDING SYSTEMS FOR RESIDENCE ON OTHER DEVICES

An RSX-llM system can reside on any file-structured device. Thus,
in
addition to the RK05, RP02, RP03, RP04, RP05, RP06, and RK06 disks,
the system may reside on the RFll, RS03/RS04, or RXOI disks, or on
DECtape.
Because
the
system,
including
all privileged and

4-11

GENERATING LARGER SYSTEMS

nonprivileged tasks, requires approximately 2200 blocks of storage,
use
of the alternate devices requires careful examination and
planning.
It is fairly easy to put a system on another device.

The steps are:

Format the disk, if necessary.

Initialize the disk as a Files-II volume.

Mount the disk and establish the following directories on it:
[1,1], [1,2],

[1,4],

[1,6], and [1,50] or [1,54]

Transfer all files in [1,1], [1,2], and [1,50] or [1,54]
the system disk to the target device, as shown below:

from

>SET /UIC=[l,l]
>PIP DSO:=DKO:*.*
>PIP DSO: [1,2]=DKO: [1,2]*.*
>PIP DSO: [1,50]=DKO: [1,50]*.*
5.

If the Executive in the system image file RSXIIM.SYS,
contains installed tasks, create a new system image file by
copying the Executive task image contained in RSXIIM.TSK.
(Thus, in SYSGEN2 you should specify that the Executive
backup file be retained.)
Follow the procedure used in
SYSGEN2 to ensure that the resulting file is contiguous and
is sufficiently long.
NOTE
The target system Executive must include
support for the device on which it is to
reside;
otherwise the device driver
will not be available to load tasks.

Using the MCR ASN command, create the logical device names
LB:
and SY:
and assign them to the target disk, as follows:
>ASN DSO:=SY:
>ASN DSO:=LB:

Run VMR to set up the partitions and install the required
tasks.
Note that all tasks must be installed from device
LB: •

Bootstrap the new system and save it with the /WB
rewrite the bootstrap block.

switch

>BOO DS: [1, 50 ]
RSX-llM V03.1 BL22
>SAV /WB

4.3

SUPPORTING MORE THAN ONE SYSTEM ON THE SAME VOLUME

Supporting more than one system on the same device is fairly
straightforward. Create a separate directory for the new system, such
as [2,50] or [2,54].

4-12

GENERATING LARGER SYSTEMS
1.

Copy (or rename) all files from [1,50] or [1,54] to the new
directory.
Note that tasks may not be installed in two
systems at the same time;
therefore, all tasks to be
installed concurrently in both systems must have separate
task images.

Create the file RSXllM.SYS from the RSXllM.TSK file.

Run VMR, set up partitions, and install tasks.

Bootstrap the system and save it (specifying the
to write a new bootstrap block, if desired).

/WB

switch

There are now two
systems
on
the
same
volume.
If
the
install-run-and-remove option of the RUN command is to work properly,
the default UIC for the task image (specified by $ in RUN $xxx)
must
be set up for the proper UIC. This may be done with the SET /SYSUIC
command as in SET /SYSUIC=[2,54].
EXAMPLE:
)UFD SY: [2,54]
)SET /UIC=[2,54]
)PIP =[1,54]
)PIP RSXllM.SYS;*/DE
)PIP RSXllM.SYS=RSXllM.TSK
)VMR
ENTER FILENAME: RSXllM
VMR>SET /POOL=400
VMR>SET /MAIN=SYSPAR:400:l00:TASK
VMR>SET /MAIN=GEN:500:ll00:SYS
VMR>INS FCP
VMR>INS INS
VMR>INS MCR
VMR>INS MOU
VMR>INS SAY
VMR)"Z
>BOO
RSXllM V03.l BL22
>SET /SYSUIC=[2,54]
>SAV
RSXllM V03.l BL22 64K MAPPED
>RED DKO:=LBO:
>RED DKO:=SYO:
>MOU DKO:SYSTEM
>@[1,2]STARTUP
>@<EOF>
If disk space is limited, you may alter step 1 above to include only
those tasks that are to be statically installed in one or both
systems.
Typically this means that only
one
copy
of
each
nonprivileged user task is maintained. These utility tasks may then
either be installed by the STARTUP file or always initiated using RUN
$XXX.
In this case, if Executives are identical, or no drivers are to
be loaded on-line, the system UIC should be the same for both systems.

4-13

GENERATING LARGER SYSTEMS
4.4

INCREASING FILE SYSTEM THROUGHPUT

4.4.1

Building a Faster File System

As distributed, the SYSGEN command files build a 2K, 2.5K, or 5.5K
file system.
The 5.5K file system is two to three times faster than
the smaller versions for certain operations. However, increased speed
in directory operations is possible by increasing the number of
directory blocks read in at one time. This may become important on
large disks, such as the RP02, RP03, RP04, RP05, RP06, RM03, and RK06.
To increase or decrease the number of directory blocks read in at one
time, you must edit the file BIGFCPBLD.CMD. The size of BIGFCP can be
reduced to 5K by eliminating the additional buffers allocated to
directory blocks, or it may be increased by .25K for each additional
block. The program section containing the extended directory buffers
is $$BUF3. To reduce the size of BIGFCP to 5K, delete the line:
EXTSCT=$$BUF3:2000
To increase the number of blocks read, edit the line to increase the
PSECT by the number of additional bytes to be read. Keep in mind that
directory blocks are read in multiples of lOOO(8)
bytes;
thus,
the
PSECT should be altered only by increments of lOOO(8). For example,
the statement:
EXTSCT=$$BUF3:5000
allocates buffer space for five additional blocks permitting up to six
directory blocks to be read at a time.
NOTE
The file system task should not share a
user-partition
with
any
task that
performs file-structured I/O. Any other
configuration will cause a malfunction
of the RSX-IIM system. The operation of
RSX-IIM 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 FIIACP, and while
this I/O operation is in progress, the
tasks cannot be checkpointed. Thus, if
FIIACP is running in the same partition,
it may not be loaded into memory to
process the request.

4.4.2

File Control Primitives Dynamic Memory Requirements

4.4.2.1 Directory Least-Recently-Used List - A special feature of the
file control primitive
(FIIACP)
task improves the performance of
directory operations. However, as many as 54
(decimal)
words of
dynamic memory may be required for each mounted volume.

4-14

GENERATING LARGER SYSTEMS
This feature allows directories to be pre-accessed, as follows:
the
first time a directory operation is performed on a given directory
(master file directory or user file directory), the directory is
accessed.
An 18-word file control block
(FCB)
is stored in the
directory least-recently-used (LRU) list. The LRU list is actually a
thread through the FCB list pointed to by the volume control block.
Pre-accessing directories in this way generally saves three disk
accesses for every directory operation. The search of the master file
directory for the identification of the user file directory is
bypassed completely, thus eliminating the read of the MFD file header
and MFD data block.
Pre-accessing the user file directory also
eliminates reading the UFD's file header.
The dynamic memory needed to include this time saving feature may be
intolerable for users with limited dynamic memory, because up to three
18-word LRU entries may be required for each mounted volume.
The
maximum number of directory LRU-list entries that FCP uses is set when
the volume is initialized by the /LRU keyword;
the default is 3. The
LRU value can be overridden when the volume is mounted.

4.4.2.2 File Control Block Allocation - For each open file in the
system, a 50(8) byte File Control Block (FCB) is required. The file
system uses this control block to maintain critical information about
the file.
In the 2K FCPNMH and 2.5K FCP, FCBs are allocated from the
Executive's dynamic storage region. However, in the 5.5K BIGFCP, FCBs
may be allocated from space within FCP's partition before overflowing
into the dynamic storage region. PSECT $$FREl controls the amount of
memory allocated to FCBs, which is extended in the build command file
BIGFCPBLD.CMD.
This feature is especially important for large,
multi-user systems because it reduces the load on the dynamic storage
region.

4.4.3

Multiple File Systems

For systems with several high-performance disks it is possible to
increase file system throughput by mounting each volume with a
separate FIIACP. This allows a separate pool of FCBs for each disk
volume (in each FllACP partition), and allows overlapping of directory
requests on each volume.
If Files-II support for DECtape is desired, a separate FIIACP should
be installed with the name DTAACP, the primary default file system ACP
for mounted DECtapes. This version of FllACP should be the smallest
(2K)
file
system
that
does
not support multi-header files
(FCPNMH.TSK) .

4.5

INSTALLING AND USING RESIDENT LIBRARIES AND COMMON BLOCKS

RSX-llM supports resident libraries and common blocks which may be
shared by several tasks. Resident libraries and common blocks must be
installed in common partitions.

4-15

GENERATING LARGER, SYSTEMS
4.5.1

Setting up a Common Partition

Establish a common partition by using the MCR SET command specifying
the partition type COM. For example, the following command:
)SET

/MAIN=FORRES:lOOO:300:COM

sets up a main common partition named FORRES, starting at 100000, that
is 30000 bytes long.
To eliminate a common partition, use the SET
command.

4.5.2

/NOMAIN

SET

/NOSUB

Installing a Library or Common Block

Both the task and symbol table files (.TSK and .STB) must be stored
under UIC
[1,1]
on device LB:.
Tasks using the common block or
resident library must specify its name during task-build.
You must
install the common block or library before you install a task
referencing the library or common block. This is done with the MCR
INSTALL command, as shown below:
)INS

[1 ,1] FORRES/PAR=FORRES

This command causes the library or common block to be loaded into the
partition.
Note that this is special case processing by Install.
Normally, Install only creates Task Control Blocks
(TCBs)
for
tasks
without reading executable code. For a common block or library, the
common block or library is read into memory.
You can then install
tasks that reference the library or common block.

4.5.3

Eliminating a Library or Common Block

You can eliminate a common block or library only by using the MCR
command. For example, the command:

SET

)SET /NOMAIN=FORRES
eliminates the library FORRES (installed as shown in Section 4.5.2)
and the partition FORRES.
Use care when eliminating a library or
common block to remove any tasks that reference it before eliminating
the library.

4.6

BUILDING A FORTRAN OTS RESIDENT LIBRARY

To save memory space, you may want to build a resident
library containing frequently-used FORTRAN routines.

(sharable)

A MACRO-II source file that aids you in building a resident FORTRAN
library is distributed with RSX-llM. This file, named FORRES.MAC, is
under UIC [200,200] on the system disk (on the RK05 kits, the mapped
and unmapped object disks). As distributed, this module generates an
8K library for a system with no extended arithmetic support.
While it is not necessary to build the resident library during system
generation, memory space for it should be considered at that time.
Otherwise, it may be difficult to install the library.

4-16

GENERATING LARGER SYSTEMS
Building an optimal resident library is an iterative process.
The
file FORRES.MAC must be edited with consideration for size and program
requirements.
For most efficient use of virtual memory, the library should be as
close as possible to a 4K boundary, without exceeding that boundary.
The following steps are a guide to tailoring the FORTRAN library to
individual system requirements.
This process assumes that a system
generation has already been done, that all tasks are installed, and
that the system has been saved.
1.

For easy reference to the
FORRES.MAC may be useful:

MACRO-II

file,

listing

entry

points

>SET /UIC=[200,200]
>PIP LP:=FORRES.MAC
2.

Edit the MACRO-II file to insert or remove
needed.

Assemble the MACRO-II file:
>MAC FORRES,LP:=FORRES

Task-build the object file,
specifying the /-HD and I-PI
switches on the symbol table file.
The only Task Builder
option required is STACK=O. The appropriate command sequence
is shown below:
TKB>,LP:,SY:FORRES/-HD/-PI=FORRES
TKB>/
ENTER OPTIONS:
TKB>STACK=O
TKB>//

Examine the Task Builder map to obtain the size of the
library
(in octal bytes), as shown in the line R/W MEM
LIMITS:.
If the library does not fit into the partition
planned for
it, examine the rest of the map to obtain the
sizes of individual modules.
Remember that the library
should be as close as possible to a 4K boundary, without
exceeding that boundary.
If the size of the library is not
through 5.

correct,

repeat

steps

When the library is the desired size, task-build it in UIC
[1,1], specifying all output files.
In addition to the STACK
option, you must use the PAR option, as shown below:
>SET /UIC=[l,l]
>TKB
TKB>FORRES,LP:,SY:FORRES/-HD/-PI=[200,200]FORRES
TKB>/
ENTER OPTIONS:
TKB>STACK=O
TKB>PAR=FORRES:base:length
TKB>//
The base address for FORRES should be set as high as possible
for a mapped system.
(For example,
if the size of the
library is greater than 4K but less than 8K, the base address
should be set to 140000.) For an unmapped system, it is the

4-17

GENERATING LARGER SYSTEMS

actual common block base address. The size of the partition
may be assumed to be SK.
After one task-build, a more
accurate size can be given.
(If there is a FCS resident library available, the TKB option
LIBR=FCSRES:RO may also be used.)
7.

Allocate space for the library, as shown below:
>SET /MAIN=FORRES:base:length:COM

Install the library using the following command:
>INS FORRES

4.7

Now perform a SAVE, or edit the
[1,2]
STARTUP.CMD command
file to install FORRES when the system is bootstrapped.

BUILDING AN FCS (POSITION-INDEPENDENT) RESIDENT LIBRARY

To save memory, you may want to produce a position-independent library
containing all the FCS modules required by a set of programs that are
intended to run simultaneously.
The MACRO-II source file, [200,200] FCSRES.MAC, aids you in building
an FCS resident library.
As distributed, this file produces a 4K
library and contains every module in FCS.
If you want to produce a
smaller
version of FCSRES you must edit the FCSRES.MAC file,
eliminating the .GLOBL references for those modules to be excluded.
It should be understood that the number of FCS modules that are
included in a resident library is dependent upon the applications that
require the FCS library. An essential point to consider is that a
task that links to FCSRES cannot include missing FCS modules from the
system object library, SYSLIB.OLB. Such a program cannot link with
FCSRESi
it must instead link all of FCS from SYSLIB.
To build FCSRES:
1.

Edit the FCSRES.MAC file, if desired.

Assemble it, as shown below:
MAC>FCSRES,LP:=FCSRES

Task-build it with the following command sequence:
>SET /UIC=[l,l]
>TKB
TKB>FCSRES/-HD/PI,LP:,SY:FCSRES=[200,200]FCSRES
TKB>/
ENTER OPTIONS:
TKB>STACK=O
TKB>PAR=FCSRES:base:size
TKB>//
The base address for FCSRES is always 0 for a mapped system.
For an unmapped system, it is the actual common block base
address. The size of the partition may be assumed to be 4K.
After one task-build, a more accurate size can be given.

4-lS

GENERATING LARGER SYSTEMS
4.

Allocate space for the library, as shown below:
)SET /MAIN=FCSRES:1400:200:COM
This example creates a 4K common block (library) at
address 140000.

physical

Install the library using the following command:
)INS [l,l]FCSRES

Save the system or edit the [1,2] STARTUP.CMD command file to
install FCSRES when the system is bootstrapped.

If a FORTRAN resident library is required in conjunction with an FCS
resident library,
first build FCSRES, then 'include the Task Builder
option statement
LIBR=FCSRES:RO
in the task-build options for FORRES. This results in a considerably
smaller FORRES.
By properly tailoring the FORTRAN resident library, a
flexible 4K FORRES using a 4K FCSRES can be built.
In addition,
this
allows the use of FCSRES by itself when FORRES is not required.

4.8

PRINT SPOOLER (PRT)

A print spooler (PRT) task is provided that you can build to print
listings simultaneously with the operation of other tasks. The
MACRO-II assembler, Task Builder, and FORTRAN compilers try to spool
all listing or map files generated by them onto disk.
If the print
spooler is not installed, the files remain on disk.
If the spooler is
installed, it is started, thus printing any files in its receive list
(input queue).
Using the print spooler speeds up the operation of
MACRO-II, the Task Builder, and compilers, because they do not have to
wait for I/O to complete on the relatively slow (compared to disk)
line printer.
For optimum operation, the print spooler should be installed
own
2K
partition.
It
may
be built checkpointable
checkpointable.

in
or

its
not

Under normal circumstances the spooler deletes only a small class of
files after printing.
However,
it is possible for you to build a
deleting print spooler. Do this by editing the task-build command
file PRTBLD.CMD during SYSGEN phase 2. When the line text editor
(EDI) prompts, enter the following commands:
*F GBLPAT=PRT:$DELET
GBLPAT=PRT:$DELET:O
*C/O/l
GBLPAT=PRT:$DELET:l
*EX
The spooler built without this patch deletes only the following files:
*.PMD, *.DMP, LP.LST, and LP.MAP.
You may supply an alternative file deletion algorithm and include it
in task PRT. The module should define the global entry point $DELCK.
The routine is called with register RO containing the FDB of the file
just printed.
On return, RO must be preserved and the processor
status C-bit should be set to indicate that the file is to be deleted.

4-19

GENERATING LARGER SYSTEMS

Use of this feature bypasses all of PRT1s default file deletion logic.
To include this module, insert it in the object library PRT.OLB,
and
edit the task-build command file PRTBLD.CMD, deleting the following
line:
GBLDEF=$DELCK:O
Before a file is printed, an identification page is generated.
This
page contains the RSX-IIM version number; the date and time; and the
device, UFD, and name of the file being printed.
In addition,
the
file name is printed in large block letters for readability. Two
formats are available, a large one for 132-column printers, and a
smaller one for 80-column printers.
You may build PRT to omit the file identification page by modifying
global patch in the task-build command file as follows:

*F GBLPAT=PRT:$FLAG
GBLPAT=PRT:$FLAG:l
*C/I/O/
GBLPAT=PRT:$FLAG:O
Note that the value specified in the GBLPAT statement is used to
determine the number of title pages printed. There are additional
options for specifying flag page size and the number of trailing form
feed
characters
to be printed.
The task-build command file,
PRTBLD.CMD, contains detailed commentary concerning these options.

4.9

BUILDING MULTI-USER SYSTEMS

RSX-IIM can support more than one terminal that is running tasks.
Such
systems are called multi-user systems.
Depending on the
processor, disks, memory size, and job mix, RSX-IIM can support from 2
to 24 or more users simultaneously.

4.9.1

Setting Up a Multi-User System

At system generation, more than one terminal should be generated for
the system. These terminals may consist of any combination of DLlls,
DJlls, DHlls, or DZlls. DHlls and DZlls may have both local and
remote lines.
The system manager has the choice of defining fixed partitions or
system-controlled
partitions.
Support
for
system-controlled
partitions must be included in the Executive during system generation.
In a fixed partition system, each user terminal is allocated a
dedicated partition in which to run its tasks;
all tasks for that
terminal
must
be installed to run in that partition.
In a
system-controlled partition, the Executive allocates memory to user
tasks, as required;
all tasks regardless of terminal association may
be installed in the same partition. This scheme is much more flexible
than a fixed partition scheme, because only the space needed for the
current task mix is used. In a fixed partition system, much space
could be wasted if partitions are made big enough to run tasks such as
BIGTKB and BIGMAC; most work is done using smaller tasks such as EDI
or PIP.

4-20

GENERATING LARGER SYSTEMS
4.9.2

Installing Checkpointable Tasks

4.9.2.1 Systems. without Dynamic Allocation of Checkpoint ~ Space - A
single task image may be installed any number of times if it is not
checkpointable. If the task is checkpointable it can be installed
only once because it must checkpoint into the space allocated in its
task image file. To install many copies of checkpointable tasks in
this system, there must be a corresponding number of task image files.
Checkpointable MCR task image files should be copied and named
according to the following conventions. The first three characters of
the task name should be the MCR command name that invokes the task.
This should be suffixed with the letter T and the unit number of the
terminal from which the copy of the task is invoked.
The tasks can
then be installed with task names constructed in the same manner.
For example, assume the MACRO-II assembler (MAC) is checkpointable,
and copies of its task image file must be made to allow more than one
user to run it.
In such a case, there should be MACTO.TSK,
MACTl.TSK, ... ,MACTn.TSK, where the Tn suffix corresponds to a terminal
number.
Then, the file MACTO.TSK should be installed as task
MACTO, MACTl.TSK as MACTl, and MACTn.TSK should be installed as task
MACTn.

4.9.2.2 Systems with Dynamic Allocation of Checkpoint Space - On
systems
with
dynamic
allocation
of
checkpoint
space
and
system-controlled partitions, only one copy of an MCR task needs to be
installed.
The system automatically spawns additional copies of the
tasks as needed, and they are checkpointed on demand to the checkpoint
file.
The spawned tasks are named as described in the previous
section.
If the system has only fixed partitions, an MCR task must be installed
once for each partition (terminal) using the naming conventions
discussed earlier. However, only a single copy of the task image file
is required.

4.9.3

Installing Noncheckpointable Tasks

4.9.3.1 Fixed Partition Systems - For fixed partition systems, all
MCR tasks should be installed for each partition (terminal) using the
naming conventions discussed earlier. However, only a single copy of
the task image file is required.
For tasks that are activated by the install-run-and-remove option of
the RUN command, the task INS should be installed in each dedicated
terminal partition.
Tasks started by the install-run-and-remove
command are named TTn, where n is the unit number of the terminal from
which it was started. The task runs in the partition in which the
task INSTn was running. The partition and naming conventions may be
overridden by explicitly including the task and partition name in the
RUN command.

4-21

GENERATING LARGER SYSTEMS
4.9.3.2 System-Controlled Partitions - For multi-user systems with a
system-controlled partition, the Executive names and creates tasks.
Only one copy of each task needs to
be
installed
in
the
system-controlled partition. The default name should be that used in
single-user systems (e.g., MACRO-II is ••• MAC).

4.9.4

Task Invocation

When you type the command to invoke an MCR task
(e.g.,
)MAC A,A=B),
the system executes the following algorithm, where XXX is the command
name:
1.

Search for ••• XXX in the list of installed tasks.
If found
and not active, start it, and assign TI:
to the terminal
which issued the command.
Otherwise:

Search for XXXTn in the list of installed tasks.
If found
and not active, start it, and assign TI:
to the terminal
which issued the command.
If XXXTn is active, issue TASK ACTIVE message.
Otherwise:

If task XXXTn was not found, and task •.. XXX was found but
was
active,
and
if
task ... XXX is installed in a
system-controlled partition, then duplicate the task control
block entry for
task ..• XXX, name the task XXXTn, start it,
and assign TI:
to the invoking terminal.
On task exit,
deallocate the temporary task control block entry for the
XXXTn.

If both tasks ..• XXX and XXXTn were not found, issue TASK NOT
IN SYSTEM message.

For the install-run-and-remove option of the RUN command, the task is
always named TTn, where n is the unit number of the terminal from
which it was requested.
It is installed in the partition that task
INS is running in, unless overridden by the /PAR= option.

4.9.5

Disk Swapping

Disk swapping allows more tasks of equal (or close) priority to share
an amount of memory into which they cannot be loaded simultaneously.
Swapping is accomplished by varying task priorities so that tasks of
similar priorities checkpoint each other periodically. Swapping is
supported in both mapped and unmapped systems, and in user- and
system-controlled partitions;
the only required Executive feature is
checkpointing. Swapping costs very little in terms of Executive (size
and time) overhead. The disk requirements of a swapping system can be
greatly reduced by the inclusion of dynamic
checkpoint
space
allocation in the Executive.
Swapping does not affect the basic checkpointing algorithm
as
described earlier.
For .example, a task can only checkpoint another
task of lower priority, never one of equal or higher priority.
However, when swapping is enabled, the priority of tasks resident in
memory, with respect only to the allocation of memory, varies with

4-22

GBRERATIRG LARGER SYSTEMS
time.
The task's priority
resources DOES NOT CHANGE.

with respect to all of the other system

There are two SYSGEN parameters that control the swapping algorithm.
1.

Swapping interval. This parameter determines how often the
Executive scans the partition lists to modify the memory
priority of resident tasks.
A typical swapping interval
might be about a half of a second.

Swapping priority range. 'This is the absolute value of the
range through which a task's priority varies from its
installed priority. A typical value is 5. This value would
cause a task's memory priority to vary from P+5 to P-5, where
P is the priority set for the task when it was installed.

The key element of the swapping algorithm is a byte in the task's
header in which the swapping priority of the task is maintained. The
symbol S$$WPR is equated to the swapping priority range specified
during SYSGEN.
In a swapping system, the Executive determines whether
a nonresident task should checkpoint a resident task by comparing the
running priority of the nonresident task with the sum of the running
and swapping priorities of the resident task. Each time a task is
read into memory as the result of an initial task load or checkpoint
read, the swapping priority byte in the task header is initialized to
+S$$WPR.
On the occurrence of each swapping interval, the swapping
priority of each resident task is reduced by one until it reaches
-S$$WPR.
If there is a possibility that checkpointing within a main
partition might occur based on the new priorities, the Executive
executes its partition allocation algorithm for that main paritition.
When specifying the swapping parameters, consider the following hints.

4.9.6

From the time a task is loaded into memory, the average time
it takes for it to be checkpointed by a task of the same
running priority is roughly equal to the product of the two
swapping parameters.

Tasks of the same running priority tend to get the same
amount of time in memory. Tasks whose running priorities
differ by less than the swapping priority range tend to
receive different amounts of time in memory with the higher
priority tasks getting more time.

In a system that supports checkpointing during terminal
input,
terminal
input
is
also a factor
in causing
checkpointing to occur. Editors and other interactive tasks
nor~ally
should
run
at a higher priority than more
compute-bound tasks. However, when an editor is waiting for
terminal input, it can be checkpointed by any lower priority
task. As soon as its input is complete, the editor can come
back into memory by checkpointing the lower priority task.
It is possible in a highly interactive system,
that the
naturally high checkpoint rate reduces the need for the
Executive swapping code to service many tasks of equal
priority.

Round-Robin Scheduler

You can include an optional round-robin scheduler in the Executive.
This scheduler time-slices the CPU among tasks in a specified priority
range.
It ensures that all tasks of equal priority share the CPU.

4-23

GENERATIRG.LARGER SYSTEMS
Round-robin
scheduling
does not affect the standard processor
competition by tasks of different priorities. It also does not affect
tasks that are not in the specified priority range.
The round-robin scheduler affects only those tasks in memory (tasks
that are on the Active Task List). Tasks that are checkpointed or in
the partition wait queue are not affected.

4.9.7

Checkpointing During Terminal Input Wait

You can select an Executive SYSGEN option that allows tasks that are
checkpointable to be displaced from memory while they are waiting for
terminal input. This feature allows more copies of terminal I/O-bound
tasks (e.g., EDI) to be run than normally could be run in a given
amount of memory.
When the terminal driver dequeues a terminal input request for a
checkpointable task that has checkpointing enabled, is not at AST
state, and has ASTs enabled, the task is stopped from further
execution.
Thus, even if the task has not entered a wait state for
the terminal input, its execution immediately stops when the request
is dequeued by the terminal driver.
Normally, a task that has been checkpointed for terminal input is not
brought
back into memory until its terminal request has been
satisfied. This is true even if memory becomes available during the
wait.
The only way the task can execute further, prior to the
completion of the terminal input, is to receive an AST.
When a task is stopped in this manner, its effective priority within
its partition drops to zero.
(Its actual priority never changes.)
Therefore, lower priority tasks ready to run can cause a higher
priority task that is waiting for terminal input to be checkpointed.
When the terminal input to the checkpointed higher-priority task
completes, the Executive removes the stop condition and the task can
be brought back into memory. If necessary, the Executive displaces
lower priority checkpointable tasks to make room for it.

4.9.8

Dynamic Checkpoint Space Allocation and Task Extension

Memory usage can be improved in large multi-user systems by making all
or most of the tasks in the system checkpointable. In doing so, the
system disk requirements can be greatly reduced if the system includes
dynamic checkpoint space allocation.
With this feature, all task
checkpointing operations use common system checkpoint files.
Thus,
tasks can be installed as checkpointable without having to allocate
checkpoint space in the task image file. Furthermore, multiple copies
of a checkpointable task can be run from a single task image. Coupled
with task checkpointing during terminal input, the number of tasks
that absolutely require memory residency can be reduced sharply.
System checkpoint files are established and eliminated with the MCR
ACS command. One checkpoint file may be established for each mounted
Files-II volume. When the Executive requires checkpoint space, it
favors the devices in the allocation order of the checkpoint files.
Therefore, if multiple ACS commands are issued, the fastest devices
should be specified first.
For example, a system may have both an RS04 fixed-head disk, and an
RP06 movable-head disk. The system manager may determine that limited

4-24

GENERATING LARGERSYSTBMS
checkpoint space (200 blocks) can be allocated on the RS04. To ensure
that checkpoint allocation failures never occur, additional space
(1200 blocks) should be allocated on the RP06.
The startup command
file would then contain the following two lines:
ACS DS:/BLKS=200.
ACS DB:/BLKS=1200.

!ALLOCATE PRIMARY CHECKPOINT FILE.
!ALLOCATE SECONDARY CHECKPOINT FILE.

As the Executive allocates and deallocates checkpoint space, the
checkpoint files can fill up and become fragmented. When possible,
freed-up checkpoint space is reused. However, depending on the sizes
of the checkpoint files and the amount of fragmentation, the Executive
may fail to find space to fulfill a checkpoint request.
In this case,
a task that is intended to get into memory does not get in until
additional memory or checkpoint space becomes available.
If a critical task must get into memory, it may be unacceptable for a
checkpoint operation to fail.
To ensure that any given task can
always be checkpointed, allocate checkpoint space in the task image
file. There can be no checkpoint allocation failures in partitions in
which all active tasks have preallocated checkpoint space.
For
example,
all tasks running in SYSPAR should have preallocated
checkpoint space. A task which has checkpoint space preallocated in
its task 1mage file is checkpointed to this space only if the
Executive fails to find space for the task in the checkpoint files.
With this algorithm, the Executive tends to checkpoint a task to the
fastest device when a task was installed from a slower device.
Selection of the Extend Task directive during SYSGEN allows tasks to
increase
or decrease their memory allocation during execution.
Although this feature does not require dynamic checkpoint space
allocation,
its flexibility is limited without it.
The system
utilities, MACRO and Task Builder, use the Extend Task directive to
maintain a memory-resident symbol table until reaching the maximum
size as specified by the system manager. In a system that supports
the Extend Task directive, these utilities can be installed with an
increment as low as 2048 to reduce their initial memory requirements.
For large assemblies and task-builds -these utilities increase their
size to the operator-set maximum for increased speed, and return to
their original size before processing the next command.

4.9.9

QIO Speed Optimizations

If you select the QIO speed optimizations during SYSGEN, the speed
QIO operations are increased in the following three ways:
1.

I/O packets are preallocated

BLXIO (block transfer) speed is optimized

I/O completion is overlapped.

4.9.9.1 I/O Packet Preallocation - The Executive maintains a LIFO
list of preallocated I/O packets;
the maximum size of the list is
specified by the system manager. 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;
this is a
significantly slower operation. When an I/O packet is deallocated, it
is linked into the list if the list is not full.
Thus,
in each
non-ACP I/O request, two fast LIFO list operations replace the slower

4-25

GENERATING LARGER SYSTEMS
core
allocations
and
deallocations,
saving
several
microseconds.
Some I/O requests involving ACPs require
packets and therefore benefit twice as much.

hundred
two I/O

In considering the number of I/O packets to preallocate, the number
should be considered on the normal fluctuation in the total number of
I/O requests, which is always a smaller number than the total number
of I/O requests typically outstanding on the system. The storage
needed is 18 words per I/O packet.

4.9.9.2 BLXIO (Block Transfer) Speed Optimizations - This feature
optimizes the Executive routine $BLXIO in the module BFCTL for mapped
systems only. The optimizations are as follows.
1.

The routine decides whether or not it can perform the
transfer a word at a time, as opposed to a byte at a time.

Vectors of word and byte MOV instructions are allocated
(up
to a user-specified length)
to save time on loop control
during the move. For example, if you specify 16 words in
each vector, a 36 word transfer causes the loop control to be
entered three times as opposed to 36 times if there was a
single MOV instruction.

The following users can benefit from this feature:
1.

File system ACP (for open and close operations)

The shuffler task

DECNET

4.9.9.3 Overlapped I/O Completion - This support causes the execution
of I/O completion code for each I/O request to be postponed until the
next request has been initiated. If I/O requests are in the driver's
queue, this action causes the Executive to complete the I/O processing
while the physical device services the next request.
A minor side
effect of this feature may cause multiple I/O requests to the same
device to complete in an order other than the issued order.

4.9.10

Multiuser Protection

multiuser
The following sections summarize the implications of
protection on various system directives.
Refer to the RSX-IIM
Executive Reference Manual for a detailed description of Executive
directives.

4.9.10.1 Abort, Resume,
and
Cancel
Schedule
Requests - These
directives, when issued from a nonprivileged task, are rejected for a
privilege violation if the target task does not have the same TI
terminal (i.e., was not initiated from the same terminal). The CANCEL
SCHEDULE REQUESTS directive is rejected if the TI address of the
nonprivileged issuing task is not CO:.

4-26

GENERATING LARGER SYSTEMS
4.9.10.2 Request and Run - If a nonprivileged task issues a REQUEST
directive that specifies a UIC different from its own, only the
default UIC of the requested task is set to the UIC specified.
The
protection UIC of the requested task is the same as that of the
requesting task.
Because of a data structure size limitation,
nonprivileged tasks cannot specify a UIC other than their own in a RUN
directive.

4.9.10.3 Queue I/O Request - A nonprivileged task cannot issue an I/O
request to a privately allocated device unless its TI terminal is the
same as the terminal to which the device is allocated (i.e.,
it owns
the device).

4.9.10.4 Slave Tasks - Slave tasks perform functions for other tasks
on a SEND DATA and REQUEST basis. Examples supplied with RSX-IIM are
the print spooler and cross-reference tasks. When a slave task issues
a RECEIVE DATA directive, it automatically assumes the TI terminal and
protection UIC of the sender task. Thus, a slave task always has the
same access to files and allocated volumes as its sender tasks.
However, when a slave task issues an ASSIGN LUN directive, all logical
assignments for the current TI of the slave task (via the MCR ASN
command) are ignored. Note that file specifiers to the print spooler
and cross-reference tasks always include actual physical device names
resolved prior to the issuance of the SEND DATA directive according to
the logical device assignments in effect at that time.

4.9.11

Multiple ACPs - Executive Interface

The Executive supports a multiple ACP interface to the ACPs, MCR,
Shuffler, and Loader.
When these tasks are active, but detect that
there is nothing for them to do, they set a bit in their task control
block which makes them checkpointable by any other task in the
partition, regardless of priority.
The Shuffler exits when all
system-controlled partitions in the system have reached a stable state
(see Section 4.1.4); MCR and the Loader are now always active.
The
interface provides the following benefits:
1.

Multiple ACPs can share the same partition.
In fact,
the
partition may further be shared with MCR, the Shuffler and
TKTN if desired.

MCR and the Loader never exit, thereby improving the response
to these system tasks.
Furthermore, if MCR is placed in a
dedicated partition, or in a partition with only the Shuffler
and TKTN,
it tends to remain in memory between commands for
even faster response.

4.9.12

ALTER PRIORITY Directive

The ALTER PRIORITY directive allows one task to modify the priority of
itself or another task. Any control blocks associated with the task
in priority-ordered queues are reordered immediately.
This includes
such things as the task control blocks and I/O packets. Any I/O
packets for the task which are currently being processed by a driver
or ACP are not affected. In systems with multi-user protection, a
task must be privileged to issue this directive.

4-27

GERERATING,LARGER,SYSTERS
One possible use of the ALTER PRIORITY directive is to implement
scheduling algorithms to run in addition to or instead of the
Executive's round-robin scheduling and disk swapping algorithms. Such
scheduling algorithms could be implemented by a task using the ALTER
PRIORITY directive that runs both privileged and at high priority.
Two MeR features use the ALTER PRIORITY directive:
1.

The ABORT MeR command elevates a task's priority to 247 when
it is being aborted,
thus allowing the task to exit the
system quickly.

The MeR indirect command file processor task AT., alters its
priority to 10 whenever waiting for a task to exit.
It
returns to its installed priority after detecting the task's
exit. Thus, with the ALTER PRIORITY directive in the system,
the /PRI option of INSTALL may be used to install AT.
at a
high priority such as 65 to make the processing of indirect
command files more responsive.
If the Alter
Priority
directive is not in the system, AT. must be installed with a
priority of 10.

CHAPTER 5

VMR COMMANDS

5.1

COMMAND SUMMARY

The Virtual Monitor Console Routine (VMR) commands specified in this
chapter are listed below by category.
This command summary provides a
compact overview of the facilities available through VMR.
The
detailed descriptions of the VMR commands given in Section 5.6 are
presented in alphabetical order, according to command name, for quick
reference.
Initialization Commands
ASN

Define or delete a global logical device assignment.
List current assignments on user's terminal.

INSTALL

Install a task in the system image.

LOAD

Load a device driver.

REDIRECT

Redirect all I/O requests from one physical device
another.

SAVE

Write the system image of memory
media in boot-strappable format.

SET

define
Set system and terminal characteristics;
partition
partitions;
display
terminal
and
characteristics on entering terminal.

TIME

Enter time and/or date into the system image;
the time and date on entering terminal.

UNLOAD

Unload a device driver.

onto

secondary

display

Informational Commands
DEVICES

Display on the entering terminal a list of
devices defined in the system image.

LUNS

Display on the entering terminal
assignments for an indicated task.

PARTITIONS
TASKLIST

LUN

Display on the entering terminal
the
partitions defined in the system image.

list

Display on the entering terminal a list of
installed in the system image.

all

5-1

the

peripheral

list

tasks

VMR COMMANDS
Task Control Commands
ALTER

Alter the priority of a task.

CANCEL

Cancel time-based initiation requests for a task.

FIX

Fix a task in system image.

REASSIGN

Change a task's LUN assignment.

REMOVE

Remove a task from the system image.

RUN

Schedule a task's activation. The task may run after
one clock tick, after a delay, or in synchronization
with the system clock.
Periodic rescheduling is
optional.

UNFIX

Unfix a task from the system image.

5.2
5.2.1

MONITOR CONSOLE INTERFACE
Introduction

The Virtual Monitor Console Routine (VMR) is an RSX-IlM system program
that allows the complete online configuration of RSX-llM and RSX-IIS
systems. As its name suggests, VMR provides the capability to execute
MCR commands that are directed to the disk image of a system.
VMR supports a compatible subset of the MCR commands described in the
RSX-IIM Operator's Procedures Manual.
All supported commands have
identical syntax and semantics as their MCR counterpart with the one
exception of the SAVE command.

5.2.2

Starting VMR

You have four methods for starting VMR. The first three methods apply
when VMR is installed and ready to be executed. The fourth method
installs VMR, executes it, and then removes it on exit.
Method 1:
>VMR @indirect
The system loads VMR, executes
file, and then VMR exits.

the

specified

indirect

command

Method 2:
>VMR
The system loads VMR and then VMR
prompt:
ENTER FILENAME:

5-2

responds

with

the

following

VMR COMMANDS
Method 3:
>RUN VMR
The system loads VMR and then VMR
prompt:

responds

with

the

following

ENTER FILENAME:
Method 4:
>RUN $VMR
The system installs VMR from the pseudo device LB:
under
the
system UIC
(normally, [1,50] or [1,54]), loads it, and VMR then
responds with the following prompt:
ENTER FILENAME:
In all starting methods except method 1, VMR prompts with:
ENTER FILENAME:
At this point, you specify the file that contains the image of the
RSX-llM or RSX-llS system to be modified.
A symbol table file
but
corresponding to the system image file with the same filename,
with file
type
.STB, must be under the same UIC.
(See exception
described for the /IM switch below.) For example, if you entered the
file specifier RSXllS.SYS in response to the
ENTER FILENAME:
prompt, a corresponding file, RSXllS.STB, must exist that contains the
symbol definitions for the RSXllS.SYS system image.
The system image and symbol table files are
produced by the RSX-llM Task Builder.

the

standard

format

Upon receiving a valid file specifier, VMR opens and reads the symbol
table file;
it also opens the system image file and verifies that the
file is actually a system image. VMR then prompts with
VMR>
and waits for you to enter a command.
command or end VMR by typing CTRL/Z*.

You may

enter

any

valid

VMR

If you used method 1 to start VMR,
the specified file contains a
serIes of commands to be executed by VMR. The first record in the
file must contain a file specifier for the system image file
that is
to be modified.
In addition to specifying an indirect file to start VMR, you may
enter

also

@filespecifier
anytime that VMR is prompting for input.
This directs VMR to get
input from the specified file until it reaches an end-of-file and to
*CTRL/Z is typed by simultaneously depressing the CTRL and Z keys.

5-3

VMR COMMANDS
return to the terminal for further input. This feature of VMR is very
useful in cases where a series of INSTALL commands, for example, are
to be repeated for several generated systems.

5.3

VMR FILE SPECIFIERS

File specifiers accepted by VMR are in the standard RSX-IIM form:
dev: [g,m]filename.typeiverjsw
where:
dev:

is the device-unit on which the volume containing the
desired file is mounted, for example, DKO: or DT1:.
The name consists of two ASCII characters followed,
by
an optional 1- or 2-digit octal unit number.
Default:

[g,m]

is the User File Directory (UFO), consisting of a group
number and a member number.
Default:

filename

the UIC under which VMR is running.

is the name of the file.
In RSX-IIM, a filename can be
up to nine alphanumeric characters in length.
Filename
and type are always separated by a period (.).
Default:

typ

SYO:

nonei

must be specified.

is the the file type,
alphanumeric characters.
Default: SYS for
indirect files.

ver

image

three

files,

and

CMD

for

is the version number in the range 0 through 77777(8).
Default:

jsw

system

consisting

highest version.

is a 2-character
option.

ASCII

name

identifying

switch

Only one switch option (JIM) is provided with VMRi
it is used in
conjunction with the Save command to write non-RSX-IIMjRSX-IIS system
images to secondary media in bootstrappable format.
The switch may be
specified only on the system image file and overrides the requirement
for the symbol table file.
When the JIM switch is specified, the only command VMR will accept is
the Save command. The JIM switch is useful when RSX-IIM is used as a
host system to develop and create small, core-only systems that must
be loaded from a serial medium such as paper tape.

5.3.1

Command Syntax

It is not necessary to type the entire command name when entering a
command. VMR requires only the first three letters of a command name,
followed by the command parameters,
if any exist.
If parameters
exist, they must be preceded by at least one blank or tab.

5-4

VMR COMMANDS
The following example shows how the Time command can be specified.
Note that the square brackets in the example indicate that the "E" is
optional;
the square brackets are not part of the command name.
The
angle brackets denote that the enclosed values are not literally part
of the command syntax.
For example, (CR> indicates that a
carriage
return terminates the input line.
VMR>TIM[E] (CR>
14:00:04 21-NOV-77
Thus, either
VMR>TIM (CR>
or
VMR>TIME (CR>
is acceptable.

5.3.2

Keywords

Some commands use keywords that generally apply to a command argument.
A
keyword
consists
of
a
slash
(/),
followed by an ASCII
identification, and optionally followed by an equal sign (=)
and
the
value of the keyword, as follows:
/Keyword=value
As an example of keyword usage,
Keywords can be entered in any order.
the INSTALL command requires a filename argument specifying the task
One such
to be installed.
Keywords can be appended to the filename.
keyword, /TASK,
can specify the name under which the task is to be
installed.
Thus,
VMR>INS JIM.TSK/TASK=SUPER
causes the task contained in the file named JIM.TSK to be installed
with a name of SUPER.
Keywords are command-specific and are defined
with each command.

5.3.3

Comments

VMR treats a line of text as a comment if the first character
in the
line is a semicolon (;).
In addition, the exclamation mark (!) may be
used to delimit comments in a command.
The first exclamation mark
starts the comment and
the next exclamation mark or end of line
terminates the comment. All text between the two exclamation marks is
ignored.
For example:
>;

THIS LINE IS A COMMENT

>TAS !THIS IS A COMMENT STRING!
Comments are especially useful to clarify commands in VMR indirect
command files.
(See the RSX-IIM Operator's Procedures Manual for
further information about indirect command files.)

5-5

VMR COMMANDS
5.4

COMMAND NAMES

Command names are at least three characters in length.
VMR accepts
the first three characters of a command and then searches for a blank,
tab, carriage return, or ESCape character. Therefore, embedded blanks
If a command is entered
are not allowed in a command name.
incorrectly, VMR displays an error message at the entering terminal.
Syntactical descriptions of commands and messages described
chapter observe the following notational conventions:

5.4.1

this

Lower-Case

Lower-case indicates a variable with an actual value determined when
the command is entered or the message is issued.
For example, the
value of taskname depends on the name of the task associated with the
command or message.

5.4.2

Brackets []

Brackets [] enclose optional items. A syntactical element enclosed in
brackets
(for example,
edt])
is optional;
it mayor may not be
included in the command. One common exception to this rule is the
syntax for the specification of a UIC. The format for a UIC is [g,m],
where the square brackets are required syntactical elements.

5.4.3.

Numeric Values

Numeric values may be entered in a command as decimal or octal unless
explicitly qualified.
Decimal values are indicated by a trailing
period; octal values are indicated by the absence of a trailing
period. Thus,
255. and 377
have the same value.
octal. )

5.5

(The number 255. is decimal;

the number 377

COMMAND DESCRIPTION FORMAT

The following subheadings are used
in
the
detailed
command
descriptions given in Section 5.6. Subheadings that do not apply to a
particular command are omitted from the command description.
COMMAND NAME
This subheading identifies the command name in capital letters.
The
minimal VMR command acronym is shown on the right margin. The text
following this subheading describes the command's function.
The command format is given, and all parameters are described.
Examples:
Example uses are shown.

5-6

VMR COMMANDS

Notes:
A list of special considerations that may assist the programmer
in using the command properly appears under this subheading.
Command Related Error Messages:
Error messages specific to the command appear under
this
subheading.
The command may also produce the common error
messages listed in Section 5.7. These common error messages are
not listed with the individual commands presented in this
chapter.

5-7

VMR COMMANDS
5.6

VMR COMMAND DESCRIPTIONS

ALTER

ALT

The ALTER command allows the operator to change the static priority of
an installed task.
The format of the ALTER command is:
ALT[ER]

taskname /PRI=priority

where:
taskname

The name of the task whose priority is to be altered.

/PRI

Changes the task's static priority.

priority

The new priority to be assigned to the specified
from 1 to 250 (decimal).

Example:
)ALT TEST /PRI=248.
Alter the static priority of task TEST to 248(10).

5-8

task,

VMR COMMANDS

ASSIGN

ASN

The ASSIGN command defines, deletes, or displays logical-device
assignments.
Logical-device assignments are a way to associate
logical names with physical devices, pseudo devices, or other logical
devices.
When you assign a logical name to a pseudo or logical
device, the system resolves the assignment to the associated physical
device.
There are three types of logical-device assignment: global,
local, and login. VMR supports the manipulation of global assignments
only.
See the RSX-IIM Operator's Procedures Manual for additional
information on local and login assignments.
The manipulation of global assignments applies to
running system.

all

tasks

the

A logical-device name has the same syntax as a physical device unit;
it consists of a 2-character ASCII name (alphabetic) and an optional
1- or 2-digit octal unit number, followed by a colon
(:).
The
2-character name either can be equivalent to a standard RSX-IIM device
name (for example, DK:) or two letters picked at random (for example,
XY: ) •

When you install a task, or the system executes an ASSIGN LUN
directive,
the system scans the logical device table before the
physical device table when it searches for a specified device.
As a
result, you can define logical device names that are identical to
physical device names even though the logical and physical device
names do not refer to the same physical device. The system resolves a
specified device name to the first matching table entry found.
If a
logical device name is identical to a physical device name, the
logical name has precedence.
The formats of the ASSIGN command are:
ASN ppnn:=llnn:/GBL
Define a global assignment that associates the logical name lInn: with
device ppnn:.
ASN /GBL
Display all global assignments for the system.
ASN =[llnn:]/GBL
Delete the specified global logical-device assignment
assignments if the command omits lInn:.
where:
pp

Physical, logical, or pseudo device name

unit number

Logical device name

5-9

all

global

VMR COMMANDS

Examples:
VMR>ASN

DK:=GBO:/GBL

!Define global logical device name

VMR>ASN
GBO:

/GBL
DKO:

!List all assignments

VMR>ASN

=/GBL

GLOBAL
!Delete all global assignments

Command Error Messages:
VMR -- LOGICAL DEVICE NOT IN SYSTEM
The specified logical device name was not defined and therefore
could not be found in the logical device assignment table.
VMR -- PSUEDO DEVICE ASSIGNMENT ERROR
A logical device name cannot be assigned to a pseudo device.

5-10

VMR COMMANDS

CANCEL

CAN

The CANCEL command allows you to cancel time-based initiation requests
for a task.
These requests result from the RUN$ directive or any of
the time-synchronized variations of the MCR or VMR RUN command.
CANCEL does not affect the execution of the task that may be active in
the saved system image.
It removes only the time-based schedule
requests still in the queue.
The format of the CANCEL command is:
CAN [CEL] taskname
Example:
VMR>CAN XKE
Cancel all periodic rescheduling
requests for task XKE.

5-11

and

time-based

initiation

VMR COMMANDS

DEVICES

DEV

The DEVICES command displays on the entering terminal the symbolic
names of all device-units or, optionally, all of a particular device
type defined in the system image. The device names appear in one
column;
a second column contains additional information
(when
necessary) about each device.
The format of the DEVICE command is:
DEV [ICES]
DEV dd:
where:
is the particular device type to be displayed.

dd
Examples:

VMR>DEV
LOADED
DBO:
DBl:
LOADED
LOADED
DB2 :
OFFLINE LOADED
DB3:
LOADED
DKO:
DKl:
DK2:
DSO:
DSl:
LOADED
DTO:
LOADED
DTl:
LOADED
LPO:
MMO:
LOADED
LOADED
MMl:
UNLOADED
PPO:
UNLOADED
PRO:
TTO:
TTl:
TT2:
TT3:
TT4:
COO:
TTO:
LPO:
CLO:
SyO:
DBO:
VMR>DEV DK:
DKO:
LOADED
DKl:
DK2:
Please note that the pseudo device SY:
is not Redirected until the
system is booted. The following notes describe the messages that can
appear in the second column. More than one message can appear on the
same line.
•

OFFLINE indicates that, although the system tables contain
entries for this device, the system as saved did not contain
the related device.

•

LOADED indicates that the driver for the
and is currently loaded.

5-12

device

loadable

VMR COMMANDS
•

UNLOADED indicates that the driver for the device is
and is currently not loaded.

loadable

•

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

of either LOADED or UNLOADED in the second column
• Absence
indicates that the driver
is permanently resident;
it is
linked with the Executive.

5-13

VMR COMMANDS
FIX-IN-MEMORY

FIX

The FIX-IN-MEMORY command allows you to load a task into its partition
in the system image. Requests for running the task can be serviced
more quickly because the task is memory-resident and does not have to
be loaded from the disk before it can run. VMR can fix a task in the
system image only if the partition in which it is to be fixed
is
available.
The command cannot be used to fix a task in a system
controlled partition. On RSX-IIS systems, all installed tasks must be
fixed since they cannot be loaded into the running RSX-IIS system.
Fixed tasks remain physically in memory even after they exit.
Therefore,
they do not have to be reloaded when a request is made to
run them.
(Note that re-executing fixed tasks is not
always
practical.)
Only an UNFIX or REMOVE command can free the occupied
partition.
The following restrictions apply to the fixing of tasks:
•

Checkpointable tasks cannot be fixed,

•

Active tasks cannot be fixed,

•

A task must be installed before it can be fixed,

•

VMR cannot fix a task into a system controlled partition.

The format of the FIX-IN-MEMORY command is:
FIX taskname
Example:
VMR>FIX XKE
FIX task XKE in its partition.
Command Error Messages:
VMR -- CANNOT FIX A TASK IN A SYSTEM CONTROLLED PARTITION
This is a restriction of VMR.
To fix a
task in a system
controlled partition,
use the MCR FIX command and then SAVe the
system image.
VMR

FILE name HAS INCONSISTENT DATA

The task or partition that you are trying
beyond the end of the system image file.
VMR

fix

logically

PARTITION BUSY

The partition in which the task was to be fixed was occupied,
the task could not be fixed.

VMR -- TASK ALREADY FIXED
The specified task was already fixed in memory.
VMR -- TASK CHECKPOINTABLE
The subject task was checkpointable.
cannot be fixed in memory.

5-14

checkpointable,

task

VMR COMMANDS
INS

INSTALL

The INSTALL command makes a specified task known in the system image,
or loads a resident library into a common partition in the system
image. An installed task is dormant until the Executive receives a
request
for
it to run.
The optional keywords either provide
parameters that were not specified at task build, or they override
previously specified parameters.
When a task is installed, VMR creates a Task Control Block
(TCB)
for
the task in a system image table called the System Task Directory
(STD). The task parameters contained in the TCB enable the system to
run the task when requested to do so by an MCR command, VMR command,
or a system directive. A task cannot be run until you install it.
A task's TCB contains the address of the load-device Unit Control
Block (UCB) and the Logical Block Number (LBN) of the task image file.
The Executive can therefore load the task image in one transfer when
an MCR command or system directive requests an installed task.
(Loading does require more than one transfer if the task is greater
than 32K words.)
When VMR installs a task in a virgin system, it stores the task's file
identification in the task header. When you save a system, the SAVE
command places the file identification, rather than the file's LBN, in
the TeB. Then, when the system is rebooted, it reopens the task file
and stores the new current LBN of the task in the TCB.
If a task has
been deleted, the system cannot open the task file when the system is
rebooted. The system then automatically removes the task's TCB from
the STD. When VMR installs a task in a saved system image, it stores
the task's file identification rather than the LBN in the TCB to allow
a reboot to occur successfully.
Also a saved system does not retain the physical addresses of
installed tasks.
The Disk Save and Compress
(DSC)
utility can
compress and copy a disk containing a saved system,
thus moving the
task files to different physical locations.
But because the TCB
entries contain task file identifications, rather than LBNs, after a
system save, the system can function normally when it is rebooted.
The format of the INSTALL command is:
INS [TALL] filespec [/keyword] [/keyword] ...
Keywords:
/CKP=option
/INC=size
/PAR=pname
/PMD=option
/PRI=number
/SLV=option
/TASK=taskname
/UIC=[group,member]

5-15

VMR COMMANDS

where:
filespec

is the file specifier in the form:
dev: [group,member]filename.typeiversion
The type defaults to TSKi
the remaining fields.

CKP

standard defaults

apply

/CKP=option.
Checkpoint option.
If CKP=YES
(default
for checkpointable tasks),
checkpointing is allowed.
If CKP=NO, checkpointing is disabled for the task.
The /CKP keyword overrides the /CP switch specified
task build.

On systems that support the dynamic allocation of
checkpoint space, the task image file does not need to
contain allocated checkpoint space.
The presence of
the /CKP=YES keyword instructs the system to allocate
checkpoint space for the task when required from a
checkpoint file.
INC

/INC=size.
The number of additional words of address
space to be allocated to a task that is to run in a
system-controlled partition.
The extension size is
usually expressed in octal but may also be expressed in
decimal by appending a period. This keyword overrides
the EXTTSK or PAR parameter used at task-build time.
Tasks that specify the size of the partition in which
they are running use this keyword to identify how much
dynamic space they may allocate to symbol tables or
buffers.
Tasks such as MACRO-II, TKB, PIP, VFY, and
AT.
use the space from the end of the task image to
the end of their address space as dynamic memory.
In
effect, the INC keyword defines the number of words in
this dynamic region.
Default:

PAR

size specified at task-build time, or zero.

/PAR=pname.
A partition name that overrides
the
partition specified at task-build time.
In an unmapped
system, the specified partition must have the same base
address as the partition for which the task was built.
If the keyword specifies a nonexistent partition, VMR
issues a warning message and attempts to install the
task in the GEN partition.
Default: TKB uses the name GEN.
(See Chapter 4 for an
explanation of multiuser system defaults.)

PMD

/PMD=option.
Post-Mortem Dump option.
If PMD=YES,
a
post-mortem dump is requested for the task if it aborts
because of an SST error condition.
If PMD=NO
(the
default from a task-build), no dump is requested at SST
abort time. To generate a dump, the post-mortem dump
task PMD...
must be installed in the system.
This
keyword overrides the
/PM
switch
specified
at
task-build time.
Default:

Specified at task-build time.

5-16

VMR COMMANDS

PRI

/PRI=number. Priority number. The value range
through 250(10). Number conventions apply.
Default:

SLY

/SLV=option. Slave task option. The two options are
YES and NO.
If the command specifies /SLV=YES, data
sent to the installed task is marked with the TI:
of
the sending task. When the installed task receives the
data,
the system sets the task's TI:
to
that
associated with the data. This keyword overrides the
/SL switch specified at task build.

Default:

UIC

/PRI=50.

If the command specifies /SLV=NO, the TI:
does not change when receiving data.

TASK

of the

task

Specified at task build.

/TASK=taskname.
referred.

The name by which the task

Default: The name specified at task-build time or
first 6 characters of the filename.

the

/UIC=[group,member]. The square brackets are required
syntax.
This UIC is the default for the task.
It can
be overridden in the RUN command.
The task UIC
determines into what file-protection class (system,
owner, group, world) a task belongs, and thus directly
influences file access. Note that file protection may
differ from file to file.
Default:
default from task build.
This
default
applies only to tasks started by a RUN$ directive or a
RUN command that specifies a time delay before runtime.
Tasks started by typing the name as a command (for
example, PIP and TKB) run under the default UIC of the
terminal from which the command was issued.

Examples:
VMR>INSTALL SCAN
Install task SCAN.

Priority and UIC defaulted.

VMR>INSTALL DKl: [1,111]SCAN.TSK;4/PRI=103
Install task SCAN, file type TSK, version 4 on device DKl:, group
number 1, member number Ill, with a priority of 103(8).
VMR>INS MAC/INC=4096./PAR=SYSCTL
Install task MAC in the system-controlled partition
increase the task size by 4096 decimal words.

5-17

SYSCTL

and

VMR COMMANDS

Comm.and Er ror Mes:sages ~
VMR -. . . . ADDRE.SSING EXTENSIONS NOT SUPPORTED
The command tried to. install a task wit.h a VSECT (virtual
seetio·n) into a system image that does not support the feature.
VMR _.... BASE ADDRESS MUST BE ON 41< BOUNDARY
The base virtual address of the task was not on a 4K boundary.
This mes.sage is appl icable only to mapped system images.
VMR _.... BASE M.ISMATCa COMMON BLOCK <common .... name>
The base address of the partition did not match that of the
common block. This message is applicable only to unmapped system
images.•
VMR ........ CHECKPOINT AREA TOO SMALL
The area allocated for checkpointing in the task image file was
sm.aller than the. part.i tion into which the task was being
installed.
The system image does not support the dynamic
allocation of checkpoint space.
VMR .... - CHECKPOINT SPACE TOO SMALL, USING CHECKPOINT FILE
A warning message. The checkpoint space allocated in the task
image file is too small for the size of the task (usually because
Qf the lINe keyword). The system image supports the dynamic
allocation
of
checkpoint space and will therefore u.se a
checkpoint file to contain the rolled-out task. Note that since
no checkPoint file exis.ts when the systm is booted, this message
should be considered a fatal error if it is issued by any of the
tasks use·d by the system dur ing the boot. These. tasks are: MeR;
MOV; and FIlACP.
VMR -- COMfJ10N BLOCK IS TASK PARTITION <common-name>
A task I s request. for access to a common block was
because the requested partition waS a task partition.

rejected

VMR -... COMMON BLOCK NOT LOADED <common-name>
The specified common block was: 1 inked to the task but had not
been. installed into the system image. Install the COmmon block,
then install the task.
VMR ........ COMMON BLOCK OCCUPIED
An attempt was made to load a common block that was occupied.
VM.R -- COMMON BLOCK PARAMETER M.ISM.ATCH <common-name>
Parameter.s of a common block did not match those
label block.

5-18

the

task's

VMR COMMANDS

VMR -- COMMON BLOCK SEGMENT COUNT ERROR
The command tried to install a resident library with overlays,
but the number of overlay segments specified in the task header
is different from the number
specified
in
the
segment
descriptors.
VMR -- DEVICE ddn:

NOT IN SYSTEM

The specified device is not defined in the system image.
VMR -- FILE filename HAS INCONSISTENT DATA
When loading a common library, the partition extended beyond
size of the task image file and thus could not be loaded.

the

VMR -- FILE NOT CONTIGUOUS
An attempt was made to install a task from a non-contiguous file.
Task images must be contiguous files.
VMR -- FILE NOT TASK IMAGE
Data in the label block was not correct, indicating that the file
was not a task image.
VMR -- ILLEGAL FIRST APR
A task was built using a base APR other than zero
for
non-privileged tasks or APR 4 or APR 5 for privileged tasks.
If
the Executive has been built to support 20K of address space, APR
5 is the only valid base APR for tasks mapping into the
Executive.
A privileged task that does not map into the
Executive must use APR 0 as its base.
(See the RSX-llM Task
Builder Reference Manual for a description of the /PR keyword.)
This message applies only to mapped system images.
VMR -- ILLEGAL PRIORITY
The value of the priority specified in the command
range (that is, not 1 to 250(10), inclusive).

was

out

VMR -- LENGTH MISMATCH COMMON BLOCK <blockname>
The length parameter for the common block, as described in the
label block for the task image, did not match the corresponding
length parameter defined in the system image.
A taskJs label
block data must match system data for that task before it can be
installed.

5-19

VMR COMMANDS
VMR -- NO CHECKPOINT SPACE, ASSUMING NOT CHECKPOINTABLE
This is a warning message. The command attempted to install the
task
as
checkpointable;
but the task was not built as
checkpointable with checkpoint space allocated in its task image
file.
Because the system does not support the dynamic allocation
of checkpoint space,
it considers the
task
not
to
be
checkpointable.
VMR -- NOT ENOUGH APRS FOR TASK IMAGE
The Task Builder allows the user to specify the virtual base
address of a task image as a multiple of 4K.
Privileged tasks
start at virtual 100000(8) to map the first 16K of the Executive,
or virtual 120000(8)
to map the first 20K of the Executive, at
the same time as the user task.
If the virtual base address is
set too high,
the task image may not be able to be mapped with
the remaining mapping registers. This message is applicable to
mapped system images only.
VMR -- PARTITION NOT COMMON
A partition specified for a common area or library is not defined
as a common partition.
VMR -- PARTITION par NOT IN SYSTEM, DEFAULTING TO GEN
This is a warning message.
The specified partition does not
exist;
VMR therefore attempts to install the task in the GEN
partition.
VMR -- PRIVILEGED TASK LARGER THAN 12K
A privileged task was larger than 12K. Privileged
unmapped system have a maximum size of 12K.

tasks

VMR -- SPECIFIED PARTITION FOR COMMON BLOCK
A task was being installed into a common block.
VMR -- SPECIFIED PARTITION TOO SMALL
The task being installed was larger than the partition into which
it was being installed.
VMR -- TASK AND PARTITION BASES MISMATCH
The base of the partition did not match the base of the task
being installed. This message applies only to unmapped systems.
VMR -- TASK IMAGE I/O ERROR
VMR could not read the task-image file, or could not rewrite
task-image header (the device is write-locked.)

5-20

the

VMR COMMANDS

VMR -- TASK IMAGE CURRENTLY INSTALLED
The requested task image, which was checkpointable, had already
been installed.
On systems that do not support the dynamic
allocation of checkpoint space, checkpointable tasks that have
checkpoint space allocated can be installed only once; other
tasks can be installed more than once.
VMR -- TASK IMAGE VIRTUAL ADDRESS OVERLAPS COMMON BLOCK <block-name>
The virtual addresses reserved for the task image overlap those
reserved for
the common block specified in the message. A
corruption of the task image file probably caused the overlap.
VMR -- TASK NAME ALREADY IN USE
An attempt was made to install a task with the same name
already in the system image.

one

VMR -- TOO MANY COMMON BLOCK REQUESTS
A task made too many common-block requests.
seven common-block references.

A task is limited to

VMR -- TOO MANY LUNS
A task requested more than 255(10) LUNs to be assigned.
VMR -- UNDEFINED COMMON BLOCK <blockname>
A task referenced a common block that is not defined in the
system image. Usually, this message indicates that the task was
built for another system.
VMR -- WARNING - PRIVILEGED TASK OVERMAPS I/O PAGE
A privileged task that is mapped into the Executive is usually
also mapped into the I/O page in order to access the KTll
registers and other devices.
Many privileged tasks do not
require this access and can use the additional 4K words of
virtual address'space for the task image.
This message warns
that a privileged task that may require access to the I/O page
does not have the access.

5-21

VMR COMMANDS
LOAD

LOA

The LOAD command loads a nonresident device driver into the system
image and constructs the data base and interrupt vector linkages
required to allow access to the device. This command eliminates the
need to link infrequently used device drivers permanently into the
Executive.
(Executive support of loadable device drivers is a system
generation option.)
The command includes an optional keyword that specifies the partition
into which the driver is to be loaded. The specified partition cannot
be a common partition;
but all other types of partition are
permissible.
If the command does not name a partition, VMR loads the
driver into the partition chosen when the driver was built.
The format of the LOAD command is:
LOA[D] dd: [/PAR=parname]
where:
dd:

is a 2-character ASCII device name

par name

is the name of the
is to be loaded.

partition

into

which

the

driver

Examples:
VMR>LOAD

MM:

!LOAD TU16 DRIVER (MMDRV)

VMR>LOA

LS:/PAR=DRVPAR

!LOAD LPSll DRIVER (LSDRV) INTO DRVPAR

Notes:
•

Guidelines for building loadable device-driver tasks
are
rigidly defined. These guidelines are described in the RSX-llM
Guide to Writing an I/O Driver.
Note that the
system
generation procedures include provisions to simplify the task
building of drivers.

•

The LOAD command requires that a driver's TSK and STB files
reside under the same UIC and on the same disk as the system
image being worked on. For example, the command
LOA

DT:

requires that the files DTDRV.TSK and DTDRV.STB reside
under the current UIC.
•

SY:

The LOAD command requires pool space as follows:
1.

If the driver data base is being loaded, the command needs
pool space equal in size to the size of the data base.

In a mapped system, the command needs
Interrupt Control Block (ICB) for
point in the driver.

If the driver is being loaded
partition, the command needs
Control Block (PCB).

5-22

pool space for an
each interrupt entry

into a system-controlled
pool space for a Partition

VMRCOMMANDS
Command Error Messages:
VMR -- DEVICE ddn:

NOT IN SYSTEM

The data base fot the device driver was
image nor in the driver's task image.

neither

the

system

The specified device driver is already loaded or
resident in the system image.

permanently

VMR -- DRIVER ALREADY RESIDENT

VMR -- DRIVER BUILT WITH WRONG STB FILE
The STB file for the driver is not compatible with the
STB file for the current system image.

Executive

VMR -- DRIVER REQUIRES RUNNING SYSTEM FOR LOAD/UNLOAD
The requested driver included the symbols $ddLOA or $ddUNL in its
source. Support of driver load/unload calls can only be provided
by MCR LOAD/UNLOAD.
Note however,
that these symbols ate
reserved for future use by the MCR LOAD and UNLOAD commands.
VMR -- FILE name HAS ILLEGAL FORMAT
The driver's STB file contained illegal object code or data.
VMR -- FILE name HAS INCONSISTENT DATA
The partition for loadable drivers is logically beyond the end of
the system file image.
The driver task was not built according to guidelines.
See the
RSX-llM Guide to Writing an I/O Driver. Alternatively, the
driver has an invalid loadable data base.
VMR -- FILE name NOT A VALID DRIVER TASK IMAGE
The driver's task image was either overlaid, had a
or referenced a resident library.

task

header,

file

must

VMR -- FILE NOT CONTIGUOUS
The file ddDRV.TSK
contiguous.

was

not

contiguous.

The

VMR -- ILLEGAL DRIVER TASK APR USAGE
A device driver must be built for APR 5 and must be less than 4K
(e.g.
PAR=DRVPAR:120000:20000). This message applies to mapped
systems only.

5-23

the

nonsense

VMR -- INVALID DRIVER DATA BASE AT OFFSET xxxx IN FILE name
The driver had an invalid data base value at offset xxxx relative
to the symbol $ddDAT.
(See the RSX-llM Guide to writing an I/O
Driver.)
VMR -- INVALID INTERRUPT VECTOR
The interrupt vector address specified in the
was too high for the current system image.

driver

data

base

VMR -- INVALID RECORD ADDRESS FOR FILE name
An attempt was made to write outside of the system image file or
to write beginning at a byte boundary. The most frequent cause
of this is a corrupted system image or an STB file that does not
match the system image.
VMR -- LOADABLE DRIVER SUPPORT NOT IN SYSTEM
The system generation option to support loadable
was not chosen for the system image.

device

drivers

VMR -- NO POOL SPACE
The required amount of pool space was not available in the system
image.
VMR -- PARTITION BUSY
The user-controlled partition or subpartition into which the
driver was to be loaded was already occupied, or there was not
enough room in a system-controlled partition.
VMR -- PARTITION name IS A COMMON
into a common
An attempt was made to load a device driver
partition.
A device driver cannot be loaded into a common
partition.

5-24

VMR COMMANDS

VMR -- PARTITION NOT IN SYSTEM
The partition specified either in the LOAD
build was not in the system image.

command

task

loaded

was

not

VMR -- SPECIFIED PARTITION TOO SMALL
The partition into which the driver was
large enough to contain it.

VMR -- SYMBOL symname IS DOUBLY DEFINED BY FILE name
The symbol symname is defined twice by the file name.
symbols are illegal.

Duplicate

VMR -- SYMBOL symname IS UNDEFINED IN FILE name
The symbol symname was found in the file name, but it was
symbol definition.

not

VMR -- TASK AND PARTITION BASES MISMATCH
The base address of the partition into which the driver was to be
loaded did not match the base address of the partition address
for which the task was built. This message applies to unmapped
system images only.

5-25

VMR COMMANDS

LOGICAL UNIT NUMBERS

LUN

The LUN command displays at the entering terminal the static LUN
assignments for a specified task.
(Static assignments are those
recorded in the task's disk-image file.) The display consists of a
list of physical device units in one column, with the corresponding
LUNs in an adjoining column. This command is valid for a virgin
system only. It is not accepted for a saved system image.
The format of the LUN command is:
LUN[S] taskname
Example:
VMR>LUN XKE
SYO:
SYO:
CLO:

1
2
3

TT3:
TT3:
DKO:
TT3:

4
5
6
7

The display shows static assignments for LUNs 1
recorded in the task-image file header;
no
statically assigned to the task XKE.

through 7 as
other LUNs are

Command Error Messages:
VMR -- ILLEGAL OPERATION FOR SAVED SYSTEM
The LUN command can only be issued for a virgin system image.
VMR -- NO LUNS
The task that is the argument of the LUN command did not have any
logical units.
This 1S not an error message;
it merely
indicates that there were no assignments to display.

5-26

VMR COMMANDS
PARTITION DEFINITIONS

PAR

The PAR command displays on the entering terminal
each memory partition in the system image.

description

The display consists of five columns that specify:
1.
2.
3.
4.
5.

Partition name,
Partition base address (octal),
Partition size (octal),
Partition kind, main partition (MAIN) or subpartition
and
Partition type:

(SUB),

TASK for user-controlled,
COM for common,
DEV for device registers,
SYS for system-controlled,
(taskname for task region),
DYNAMIC for dynamically created region, or
DRIVER for region occupied by a loadable driver.
COM partitions are used for re-entrant libraries and common data
areas. DEV partitions allow tasks to communicate with specific device
registers, such as the UDC-ll and ICS/ICR-ll industrial control
subsystems.
See the RSX-llM Operator's Procedures Manual for a
description of system- and user-controlled partitions, as well as
subpartitions.
Dynamic and task regions are defined in the RSX-llM
Executive Reference Manual. See the description of the VMR LOAD
command for information concerning loadable drivers.
The format of the PAR command is:
PAR[TITIONS]
Examples:
Name

Base

VMR>PAR
LOR
000000
SYSPAR 110000
FCPPAR 120000
DRVPAR 146000
146000
155700
160000
162700
163700
165100
166200
167400
170400
170500
174000
GEN
174000

Size

Kind Type

000000 MAIN TASK
010000 MAIN TASK
026000 MAIN TASK
026000 MAIN SYS
007700 SUB DRIVER 002100 SUB DRIVER 002700 SUB DRIVER 001000 SUB DRIVER 001200 SUB DRIVER 001100 SUB DRIVER 001200 SUB DRIVER 001000 SUB DRIVER 000100 SUB DRIVER 003300 SUB DRIVER 200000 MAIN SYS
040000 SUB
( •.• SAV)

5-27

TT:
DB:
DM:
DS:
DK:
DT:
DX:
LP:
NL:
MM:

VMR COMMANDS
Name

Base

VMR>PAR
LDR
000000
100000
GEN
TPSPAR 460000
TPMLIB 720000
TSTLIB 740000
MESS
750000

Size

Kind Type

000000
360000
240000
020000
010000
010000

MAIN TASK
MAIN SYS
MAIN SYS
MAIN COM
MAIN COM
MAIN COM

5-28

VMR COMMANDS
REASSIGN

REA

The REASSIGN command allows the operator to reassign a task's Logical
unit Numbers
(LUNs)
from one physical device-unit to another.
The
reassignments affect only the static assignments recorded
in the
task's disk image file.
The command does not affect a memory-resident task.
Hence,
REASSIGN
has no effect on the assignments for a task that is fixed or loaded in
memory.
The format of the REASSIGN command is:
REA[SSIGN]

taskname lun nud:

where:
lun

is the logical unit number

nud

is the new device-unit, which
logical, or pseudo device.

can

physical,

Examples:
VMR>REA JOE 3 TTO:
Reassign LUN 3 of task JOE to device TTO:.
VMR>REA BILL 2 TTl:
Reassign LUN 2 of task BILL to device TTl:.
VMR>REA TEST 3 XX:
Reassign LUN 3 of task TEST to logical device XX:.
Command Error Messages:
VMR -- ILLEGAL OPERATION FOR SAVED SYSTEM
The REASSIGN function is not allowed for a saved system image.
VMR -- LUN OUT OF RANGE
An attempt was made to reassign a LUN that was greater
maximum number of LUNs allocated during task build.

5-29

than

the

VMR COMMANDS
REDIRECT

RED

The REDIRECT command allows the operator to redirect all I/O requests
directed to one physical device-unit to another physical device-unit.
Note that an attached device and the device TI: cannot be redirected.
In addition, one pseudo device cannot be redirected to another pseudo
device.
The format of the REDIRECT command is:
RED [IRECT] nud:=old:
where:
nud:

is the new
redirected.

device-unit

which

old:

is the old device-unit from which
directed.

requests
requests

will
have

be
been

Examples:
VMR>RED TT3:=TT6:
Redirect all I/O requests for device TT6:

to device TT3:.

VMR>RED TT:=LP:
Redirect all I/O requests for device LPO:

to device TTO:.

Command Error Messages:
VMR -- CIRCULAR REDIRECT ERROR
The attempt to redirect a device would result in a circular
of redirections.

list

VMR -- DEVICE NOT REDIRECTABLE
An attempt
redirected.

was

made

VMR -- DEVICE ddnn:

redirect

device

that

cannot

NOT IN SYSTEM

The specified device in the REDIRECT command was not known to the
system (did not exist in the device tables).
VMR -- OLD DEVICE ATTACHED
An attempt was made to redirect an attached device.

5-30

VMR COMMANDS

VMR -- PSEUDO DEVICE REDIRECT ERROR
An attempt was made to redirect
pseudo device.

one

pseudo

device

the

pseudo

device

TI: •

another

VMR -- TI REDIRECT ERROR
An attempt was made to redirect
device may not be redirected.

5-31

This

VMR COMMANDS
REMOVE

REM

The REMOVE command allows you to delete a task name from the System
Task Directory
(STD)
and thereby remove the task from the system
image. Removing a task from the system image makes the task unknown
to the system.
The action resulting from this command is the
complement of INSTALL.
The REMOVE command cannot remove an active task from a saved system.
An example of such a task is the SAVE task;
an attempt to remove SAVE
from a saved system results in an error. The message TASK ACTIVE
is
displayed.
The format of the REMOVE command is:
REM [OVE]

taskname

Example:
VMR>REM SCAN
Remove the task named SCAN from the system image.
file remains unaffected.

The task-image

Notes:
•

If a task that is the object of a REMOVE command is fixed, the
command automatically unfixes the task from the system image.

•

REMOVE automatically cancels all time-based schedule
for the specified task.

•

REMOVE cannot
deallocate
any
receive-data packets for the task.

requests

receive-by-reference

and

Command Error Message:
VMR -- RECEIVE DATA OR BY REFERENCE LIST NOT EMPTY
A task with entries in its receive queues may not be removed from
the system image.

5-32

VMR COMMANDS

RUN

RUN
The RUN command initiates the execution of a task.
cause a task to be:

The

command

can

•

Started one clock tick after system boot,

•

Started at a time increment from the system image time,

•

Started at a time increment from clock unit synchronization,

•

Started at an absolute time of day.

All these options, are available with or without rescheduling.
RUN has four format variations, as described below.
The formats of the RUN command are:
1.

Run one clock tick after system boot.
RUN taskname [/RSI=magu] [/UIC=[uic]]
where:
taskname

is a 1- to 6-character taskname.

RSI

is the reschedule interval.
The format is
the same as for dtime, which is detailed
reschedule
below under
format
2.
The
interval specifies how often the task is to
be rerun.
Thus, each time the specified
interval
of
time lapses, an initiation
request is made for the specified task.
Default:

UIC

is the UIC that has the format [g,m] where g
and m represent the group and member numbers
respectively;
legal group and member numbers
range from 1 through 377(8).
The square
brackets are required syntax.
This is the
UIC under which the task is requested.
The
UIC determines which files the task may
access.
Default:

co: .

no rescheduling.

the value established for

terminal

Run at a time increment from the system image time.
RUN taskname dtime [/RSI=magu] [/UIC=[uic]]
where:
taskname

is a 1- to 6-character taskname.

dtime

is the time at which the task is initiated in
time units from current system image time.
It follows the form magu.

5-33

VMR COMMANDS

A time parameter consists of two fields:
a.

A magnitude field, and

A units field.

where:
mag
u

is the magnitude
specifies time units as
following letters:

one

the

T
S
M
H

The legal value of the magnitude is related
to the value of the units field, which is
encoded as:
T

for ticks.
A tick is a
clock
interrupt, and the rate at which
interrupts occur depends on the type
of clock installed in the system.
For a line frequency clock, the tick
rate is either 50 or 60 per second,
corresponding to the line frequency.
For a programmable clock, a maximum
of
1000
ticks
per
second is
available.
(The
frequency
is
selected at system generation.)

for seconds.

for minutes.

for hours.

The magnitude is the number of units to be
clocked,
but the magnitude value cannot
exceed 24 hours in the specified units.
Units = T.

Any positive value is
(maximum of 15 bits) •

valid

Units

Any positive value is
(maximum of 15 bits) .

valid

Units

The maximum
1440 (10) .

magni tude

Units

The maximum
24(10).

magni tude

RSI

See Format 1, above.

Ule

See Format 1, above.

5-34

VMR COMMANDS

Run at a time increment from clock unit synchronization.
The task start-time is determined by computing the number of
ticks until the next time unit's occurrence (hour, minute,
second, tick) and then adding on the number of ticks for
the
specified time increment to elapse.
Run taskname sync [dtime] [/RSI=magu] [/UIC=[uic]]
where:
taskname

is a I- to 6-character taskname.

sync

M
S
T

synchronize
synchronize
synchronize
synchronize

on
on
on
on

the
the
the
the

next hour;
next minute;
next second, and
next tick.

dtime

is as defined in Format 2, above; dtime,
if
present, is added to the synchronization unit
to produce the actual run time for
running
the task.

RSI

See Format 1, above.

UIC

See Format 1, above.

Run at an absolute time of day.
RUN taskname atime [/RSI=magu] [/UIC=[uic]]
where:
taskname

is a 1- to 6-character taskname.

atime

is the absolute time of day when this task
will be initiated.
Input format is hh:mm:ss.
hh
mm
ss

hours (decimal assumed);
minutes (decimal assumed) , and
seconds (decimal assumed) .

RSI

See Format 1, above.

UIC

See Format 1, above.

Examples:
>RUN XKE 15M
Run task XKE 15 minutes from the current system image time.
>RUN XKE l5M/RSI=90S/UIC=[3,1]
Run task XKE 15 minutes from the current system image time,
rescheduling it every 90 seconds, with a UIC code of [3,1].
Note:
•

The correct value to be inserted in the clock for
forms 2
through 4 is computed from the current value of the system
time stored in the system image. Thus, the system image time
must be set before any RUN requests are made or they may not
occur at the correct time after the system is booted.

5-35

VMR COMMANDS
Command Error Messages:
VMR -- INVALID TIME PARAMETER
A specified time field was incorrect.

5-36

VMR COMMANDS
SAY

SAVE

The VMR SAVE command writes the image of a system onto a sequential
medium in bootstrappable format.
This command allows you to copy an
RSX-IIS or foreign system (see /IM switch) onto a tape or floppy disk
that you can transport to another system and bootstrap using a
hardware bootstrap or the /BO switch in PRESRV.
System images created with the SAVE command on all media, except paper
tape, are in a format compatible with the logical tape format in
PRESRV.
Thus, any of PRESRV's logical tape operations can be
performed on system images created with the SAVE command. System
images created by the SAVE command always start at the beginning of
the medium.
On paper tape, system images are created in absolute loader format and
must be bootstrapped with the absolute loader.
The format of the SAVE command is:
SAyrE] ddnn: [label]
where:
ddnn:

specifies the device-unit onto which the
is to be written. Valid devices are:
CT:
OT:
OX:
MM:
MT:
PP:

label

system

image

Tape cassette,
OECtape,
Flexible diskette,
TE/TUI6/TU45 magtape,
TE/TUIO/TS03 magtape, and
Paper tape.

is the file label name that must be specified for
all
secondary media except paper tape.
It consists of from
one to twelve alphanumeric characters.

Example:
VMR>SAV MT:MYSYS
In the example above, the system image is written onto MT:
in
bootstrappable format.
System changes made by other VMR commands
are also saved with the system image.
Notes:
•

When the /LI command is used in PRESRV to list a medium (other
than paper tape)
containing a system image created with the
SAVE command, each system image causes a line to be printed
which contains the following:
VM (for VMR), indicated as the
source device, the label specified in the SAY command line, a
block size of 512, the number of 512-byte blocks in the system
image (excluding boot and label blocks), and the date and time
that the system was saved.

•

When RSX-I1S systems are saved on paper tape (without the /IM
switch specified at VMR initiation time), the last 1000(8)
bytes of the system image are not written out.
This allows
space to accommodate the absolute loader. When the /IM switch

5-37

VMR COMMANDS

has been specified with the system's file name, the entire
system image is written out to paper tape. In this case, it
is your responsibility to ensure that the system image is not
so large that it overlays the Absolute Loader.
•

When saving a system on paper tape, contiguous blocks that
contain zero only and that begin on a 32-word address are
compressed into a 2-word descriptor.
This
compression
significantly reduces both the amount of paper tape required
and the time expended to create the tape and to read it into
memory. After the entire image has been loaded into memory, a
short routine zeroes the appropriate blocks of memory before
passing control to the bootstrapped system.

•

When bootstrapping systems on media other than paper tape,
regardless of the size of the system image, the last 1000(8)
bytes of physical memory are not copied to accommodate the
bootstrap.

•

Systems saved on a TE/TU10/TS03, 9-track magtape drive can
booted from a TE/TU16 drive, and vice-versa.

•

When the /IM switch has been specified with the system file
specifier, the SAVE command always uses a bootstrap that does
not enable memory management.

•

The maximum memory size of a mapped system is l24K words. For
physical and practical limitations, the SAVE command imposes
maximum sizes on saved images in mapped systems for certain
devices.
If a mapped system is saved, whose memory size is
greater than the maximum size imposed by the SAVE command for
the specified device, only the amount of memory equal to the
maximum size (starting at physical location 0) is saved;
no
diagnostic message is issued. The devices for which the SAVE
command imposes a maximum size on saved system images are:

Paper tape punch (PP) - 28K words,
Flexible disk (DX) - l23K words, and
Cassette tape (CT) - 28K words.
•

None of the bootstraps require that the target RSX-llS
have a driver for the bootstrap device.

system

Command Error Messages:
VMR -- DEVICE ddn: NOT IN SYSTEM
The specified device does not exist on the host system.
VMR -- ILLEGAL DEVICE VOLUME
The specified device was other than
specified above.

one

the

valid

devices

An I/O error was encountered on the output device
the system image.

while

writing

VMR -- I/O ERROR ON OUTPUT DEVICE

5-38

VMR COMMANDS

SET

The SET command allows you to alter a number of
system-wide
characteristics.
The following list describes all the available
options. The text in parentheses specifies keywords associated with
the options. The SET command allows you to:
•

Display the status (determined by the keyword
all terminals.

•

Establish device characteristics for any device in the system
(BUF, CRT, ESCSEQ, LA30S, LA180S, LOWER, REMOTE, SPEED, and
VT05B) ,

•

Establish the default UIC for
(UIC) ,

•

Set the status of any terminal in the system (PRIV or SLAVE),

•

Create partitions or subpartitions (MAIN and SUB),

•

Add space to the system dynamic memory (POOL),

•

Enable write check on devices that support it (WCHK).

any

terminal

Improper use of the SET command can result in a
privileged
operator input is not accepted.
situations should be avoided:

specified)

the

system

situation in which
The following two

•

There are no non-slave, privileged terminals in the system.
Non-privileged terminals cannot enter privileged commands.
Slaved terminals cannot enter unsolicited input to MCR.
See
the description of the /SLAVE keyword below.

•

The buffer length of all non-slave, privileged terminals is
shorter than 14 bytes.
In this case, the terminal buffer is
too short to enter many important commands required to
continue system operation or alter the status of other
terminals. See the description of the /BUF keyword below.

A number of SET command options (CRT, ESCSEQ, LOWER, and WCHK) require
Executive features that must be included at system generation.
If
support for a specified option has not been generated into the system
image, the SET command has no effect.
Only one keyword per command is permitted.
Most keywords can be
prefixed by NO to negate or disable the function of the keyword.
Exceptions are BUF, POOL, SPEED, and UIC: VMRreturns a syntax error
whenever NO precedes one of these keywords.
The format of the SET command is:
SET /keyword=values

Device Characteristics Keywords:
/BUF=dev: [size]
/CRT[=ttn:]

5-39

VMR COMMANDS

/ESCSEQ[=dev:]
/LA30S[=dev:]
/LA180S[=dev:]
/LOWER[=dev:]
/PRIV[=dev:]
/REMOTE[=dev:]
/SLAVE[=dev:]
/SPEED=dev: [recv:xmit]
/UIC[=uic[:dev:]]
/VT05B[=dev:]
/WCHK[=dev:]

Keyword Definitions:
BUF

/BUF=dev: [size]. Set or display the default buffer
size of the specified device.
If the buffer size is
omitted, this keyword causes the current size to be
displayed.
The specified size must be greater than 0
and less than or equal to 255 decimal (for a terminal,
the buffer size must be greater than or equal to two).
BUF is particularly useful for defining line printer
width (80 or 132 columns).

CRT

/CRT[=dev:] where dev:
is a cathode ray tube
(CRT)
terminal.
The CRT keyword defines the terminal as a
CRT and enables the backspace deletion option.
Typing
the RUBOUT or DELETE key moves the printing position
one space to the left and erases any
character
displayed in that position.
When the keyword omits =dev:, VMR
devices that are defined as CRTs.

NOCRT

displays

the

/NOCRT[=dev:] where dev:
is a cathode ray tube
(CRT)
terminal.
The NOCRT keyword deletes the CRT status of
the specified device and disables
the
backspace
deletion option.
When the keyword omits =dev:, VMR displays
terminals that are not defined as CRTs.

ESCSEQ

all

the

/ESCSEQ[=dev:] where dev:
is a terminal.
The ESCSEQ
keyword enables the recognition of escape sequences
from the specified terminal.
The terminal driver
treats the ESC character as the beginning of an escape
sequence rather than as a line terminator.
See the
RSX-IIM
I/O Drivers Reference Manual for
further
information about escape sequences.
When the keyword omits =dev:, VMR displays
terminals that recognize escape sequences.

5-40

all

the

VMR COMMANDS
NOESCSEQ

/NOESCSEQ[=dev:]
where dev:
is a terminal.
The
NOESCSEQ keyword disables the recognition of escape
sequences at the specified terminal.
When the keyword omits =dev:, VMR displays all the
terminals that do not support the recognition of escape
sequences.

LA30S

/LA30S[=dev:].
Establishes the specified
terminal
device as an LA30S and generates fill characters
required for an LA30S.
If =dev:
is omitted,
all
terminals defined as LA30S are displayed.

NOLA30S

/NOLA30S[=dev:].
Resets the terminal to a device other
than an LA30S.
If =dev:
is omitted, all non-LA30S
terminals are displayed.

LA180S

/LA180S[=dev:].
Establishes the specified terminal
device as an LA180S and causes the terminal driver to
suppress normal conversion 9f form feeds to 8 line
feeds.
If the keyword omits =dev:, all terminals
defined as LAl80S are displayed.

NOLA180S

/NOLA180S[=dev:]. Resets the terminal to a non-LA180S
device.
If the keyword omits =dev:, all non-LA180S
terminals are displayed.

LOWER

/LOWER[=dev:].
Specifies that lower-case characters
are not to be converted to upper case when they are
received from the specified terminal.
If =dev:
is
omitted, all terminals for which lower-case characters
are not converted are displayed.

NOLOWER

/NOLOWER[=dev:].
Resets the terminal characteristics
so that lower-case characters received on input are
automatically converted to upper case and echoed as
upper case.
Absence of =dev:
results in the display
of all terminals for which conversion to upper case is
specified.

PRIV

specified
terminal
to
/PRIV[=dev:].
Sets
the
is omitted, VMR displays
privileged status.
If =dev:
all privileged terminals.

NOPRIV

/NOPRIV[=dev:].
Sets the identified
terminal
to
results in a
nonprivileged status.
Absence of =dev:
display of all nonprivileged terminals.

REMOTE

/REMOTE[=dev:] where dev:
is a terminal with a line to
a DZII multiplexer.
The keyword declares that the
specified terminal is connected to a modem and can be
connected by means of a dial-up network.
When the keyword omits =dev:, VMR displays
lines (including DHII lines).

NOREMOTE

all

remote

/NOREMOTE[=dev:] where dev:
is a line to a DZII
multiplexer.
The NOREMOTE keyword establishes the
terminal's line as a local line not connected to a
modem.
When the keyword omits =dev:, VMR displays
lines
(including
DLll,
DHll,
DJII,
multiplexers) .

5-41

all
and

local
DZII

VMR COMMANDS

SLAVE

/SLAVE[=dev:]. Establishes the specified terminal as
one that can enter data only if it is solicited from a
task;
thus, the specified terminal always rejects
unsolicited input
(other than CTRL/O, CTRL/Q, and
CTRL/S). Absence of dev:
results in the display of
all terminals currently classified as slaved.

NOS LAVE

/NOSLAVE[=dev:].
Sets the specified
nonslave status.
Absence of =dev:
display of all nonslave terminals.

SPEED

/SPEED=dev: [recv:xmit]. Establishes the receive and
transmit baud rate for terminals attached to the system
through a DHII or DzIl multiplexer.
The argument
"recv" is the baud rate at which characters are input
to the computer from the terminal; and "xmit" is the
baud rate at which the computer outputs characters to
the terminal. Both must be specified in setting the
speed.
If neither is specified, the current settings
are displayed.

terminal
to
results in the

Valid baud rates for the DHII are: 0, 110, 150, 200,
300,
600,
1200,
1800,
2400,
4800,
9600,
A
(user-specified baud rate A), and B (user-specified
baud rate B) .
Valid baud rates for the DZII are: 0, 110, 150, 300,
600, 1200, 1800, 2000,
2400, 3600, 4800, 7200, and
9600. The receive and transmit baud rates for the DZll
must be the same;
the Dzll does not support split
speeds.
UIC

/UIC[=uic[:dev:]]. The specified UIC is established as
the default UIC for the entering terminal unless dev:
is specified.
If you specify dev:, the default UIC is
set for that terminal. All tasks run from the terminal
are run with the UIC of the terminal, except in a
multiuser protection system.
In such a system, a
privileged user can override the terminal UIC with the
UIC switch in the RUN command. Further, external MCR
function tasks* are requested with this UIC.
If a UIC is not specified, the current Ule
is
displayed.
If only dev:
is specified, the UIC for the
specified terminal is displayed.

VT05B

/VT05B[=dev:]. Sets the specified terminal as a VT05B
(a 2400 baud VT05) and generates fill characteristics
of a VT05B.
If =dev:
is omitted, all terminals
classified as VT05B are displayed.

NOVT05B

/NOVT05B[=dev:]. Resets the terminal to other than a
VT05B.
If =dev:
is omitted, all terminals classified
as non-VT05B terminals are displayed.

WCHK

/WCHK[=dev:].
Specifies for all Files-II
devices
except DX:
and DL:
and magnetic tape (MM:
and MT:)
that all writes are to be followed by a write check.
This
feature
provides high reliability for data
transfers to the specified disk. Executive support for
write check is a SYSGEN option and must be selected for

* These tasks are the MCR MOUNT,
INSTALL, DMO, and
(which run as tasks) and all system-supplied software.
5-42

UFD

commands

VMR COMMANDS

this command to have any effect.
If =dev:
is omitted,
all Files-II disk drives with write check enabled are
displayed.
NOWCHK

/NOWCHK[=dev:]. Specifies that write check is to be
disabled for
the specified device.
If =dev:
is not
specified, all disks that support write check, but have
it disabled are displayed.

Examples:
>SET /BUF=LPO:
BUF=LPO:132.
Display the current buffer size of LPO:
>SET /BUF=TTI:40.
Set TTl:

buffer size to 40(10).

>SET /CRT=TT3:
Enable the backspace deletion
identified by TT3:.

option

the

display

terminal

>SET /CRT
CRT=TT3 :
Display all terminals that support the backspace deletion option.
>SET /ESCSEQ=TT3:
Establish terminal TT3:
escape sequences.

as a terminal that can send and

receive

>SET /ESCSEQ
ESCSEQ=TT3:
Display all terminals that can send and receive escape sequences.
>SET /NOESCSEQ=TT3:
Disable support of escape sequences on TT3:.
>SET /LA30S=TT2:
>SET /LA30S
LA30S=TTO:
LA30S=TT2 :
Set TT2: as an LA30S.
Display all LA30S terminals.
>SET /NOLA30S=TTO:
Set TTO: to other than an LA30S terminal.

5-43

VMR COMMANDS

)SET /PRIV=TTO:
Set TTO: to a privileged terminal.
)SET /PRIV
PRIV=TTO:
PRIV=TTI:
Display all privileged terminals.
)SET /REMOTE=TT21:
Set the terminal line corresponding to TT21: as a remote dial-in
line. The line must be connected to a DzII multiplexer.
)SET /REMOTE
REMOTE=TTI:
REMOTE=TT2:
REMOTE=TT3:
REMOTE=TT4:
REMOTE=TT21:
Display all terminals that are currently set as remote dial-in
lines.
TTl:, TT2:, TT3:, and TT4: are DHII lines~ TT21:
is a
DZII line.
)SET /SLAVE=TT3:
Set TT3:

to a slave terminal.

)SET /VT05B
VT05B=TT4:
VT05B=TT5 :
VT05B=TT6:
Display all VT05B terminals.
)SET /WCHK=DKI:
Enable write check on DKI:.
Memory Allocation Keywords:
/MAIN=pname[:base:size:type]
/NOMAIN=pname
/SUB=mname:pname[:base:size]
/NOSUB=mname:pname
/POOL[=top]
These keywords are used as follows:
MAIN

The MAIN keyword establishes a main partition.

5-44

VMR COMMANDS

pname

is the 1- to 6-character alphanumeric partition name.

:base

is the physical base address of the partition specified
as a number of 64-byte blocks.

:size

is the size of the partition specified as a number of
64-byte blocks. The maximum size is 32K minus 32 words
for a task, common, main, or sub partition unless the
system has memory management.

: type

is TASK for a user-controlled task partition,
is SYS for a system-controlled task partition,
is COM for a common partition, or
is DEV for a common partition mapping into
registers.

the

device

User-controlled and system- controlled task partitions
are allocated for user tasks and loadable drivers.
Common partitions are used for resident libraries and
common
blocks.
Device
partitions
are used by
nonprivileged tasks to access device registers in the
external page,
such as those for
the UDC-ll and
ICS/ICR-ll.
Base and size may be entered in any of the following formats;
where nnnn is a number to which a multiplication factor is
applied to determine the value used.
Format

Calculated Value

nnnn
nnnn.
nnnK
nnn.K

Octal (nnnn*lOO)
Decimal (nnnn.*64.)
Octal K (nnn*4000)
Decimal K (nnn.*2048.)

Valid ranges of calculated values are:
Octal
Decimal
Octal K
Decimal K

0<=base<177777
O.<=base<65535
OK<=base<3777K
0.K<=base<2047.K

0<size<2000
0.<size<1024.
OK<size<40K
0.K<size<32.K

For system-controlled partitions, size may range from
1920.K or any valid representation of these limits.

Example:
Any of the following inputs for size will allocate
byte partition.

1920.

40
32.
lK
1.K
If the command does not specify base, size, and type, VMR
displays the values of these parameters for
the named
partition.
If the named partition is a main partition, VMR
also displays the parameters of all its subpartitions.

5-45

VMR COMMANDS

NOMAIN

is the keyword that eliminates the named partition
system.

SUB

is
the
keyword
that
establishes
a
subpartition.
Subpartitions may only be established in user-controlled main
partitions.

from

the

mname

is the 1- to 6-character main partition name. The
subpartition being defined becomes a subpartition
in the named main partition.

:pname

is the 1- to 6-character subpartition name.
The
subpartition being defined becomes a subpartition
of the main partition specified in mname.

:base

is the physical base address of the subpartition,
specified as a number of 64-byte blocks.

:size

is the size of the subpartition,
number of 64-byte blocks.

specified

Base and size may be entered in any of the following
formats;
nnnn is a number to which a multiplication factor
is applied to determine the value used.
Format

Calculated Value

nnnn
nnnn.
nnnK
nnn.K

Octal (nnnn*lOO)
Decimal (nnnn.*64.)
Octal K (nnn*4000)
Decimal K (nnn.*2048.)

Valid ranges of values are:
Octal
Decimal
Octal K
Decimal K

O<=base<lOOOO
0.<=base<4096.
OK<=base<200K
0.K<=base<2047.K

0<size<2000
0.<size<1024.
OK<size<40K
0.K<size<32.K

Example:
Any of the following inputs for size will allocate
byte subpartition.

2048.

40
32.
lK
1.K
If base and size are omitted, the current
displayed for the named subpartition.
NOSUB

is the keyword that eliminates the
the system.

5-46

named

values

will

subpartition

from

VMR COMMANDS

is the keyword that increases the size of the dynamic storage
region.

POOL

top

is the first location in memory used for partition
allocation. The location is specified in units of
64-byte blocks. It can be given in octal or
decimal.
If top is not given, the system prints
out the current top of memory,
the size of the
longest block of pool space in words, and the
total number of words in the pool.
The format is:
POOL = top:max:total
where top is given in units of 64-byte
Max and total are in decimal words.

blocks.

Notes:
•

If a partition currently hosts installed tasks or loaded
drivers, and a command
(for example, /NOMAIN or /NOSUB)
attempts to eliminate the partition, VMR rejects the command.

•

A command that eliminates a main partition also eliminates all
its subpartitions.
A command that eliminates a specified
subpartition eliminates only that specified subpartition.

•

If a command attempts to eliminate a main partition that has
subpartitions in which tasks are installed or drivers loaded,
the system rejects the command until those tasks are removed
from the subpartitions.

defining a partition (main or sub)
• When
already be defined as a partition.

the name must not
In addition, a main
partition can not overlap any other main partition; nor can a
subpartition
of
partition
overlap any other
a
main
subpartition of the main partition.

•

The numeric value convention applies to all
numeric values.

•

The address specified with the POOL command must be lower than
the base address of the first partition in the system with the
exception of partition LDR.

•

Once space has been allocated to the dynamic storage region,
the space can never be recovered for use in partitions.

•

System-controlled partitions can not include subpartitions
explicitly defined by the SET command. An attempt to define
subpartitions of system-controlled partitions in this way will
be rejected. The Executive dynamically defines subpartitions
of a system-controlled partition as needed to load tasks and
drivers in the system-controlled partition.

•

When the highest memory addresses of a system are allocated to
a system-controlled partition, the size of the partition is
modified automatically to reflect the amount of memory present
when the system is bootstrapped.

5-47

the

SET

command

VMR COMMANDS

Examples:
)SET /MAIN=SYSPAR:420:140:TASK
Define a main partition called SYSPAR as a user-controlled
partition whose base address is 42000(8) and whose length is
14000(8) bytes.
)SET /SUB=SYSPAR:MCRPAR:445:56
Define a subpartition called MCRPAR of main partition SYSPAR
whose base address is 44500(8) and whose length is 5600(8) bytes.
)SET /MAIN=SYSPAR
MAIN=SYSPAR:0420:0140:TASK
SUB=SYSPAR:MCRPAR:0445:0056
Display the parameters of the main partition SYSPAR
its subpartitions.

and

all

)SET /NOSUB=SYSPAR:MCRPAR
Eliminate subpartition MCRPAR.
)SET /NOMAIN=SYSPAR
Eliminate main partition SYSPAR.
SET /MAIN=GEN:IOOO:6000:SYS
Define a main partition called GEN as a system-controlled
partition whose base address is 100000(8) and whose length is
600000(8) bytes.
)SET /POOL=420
(No user defined partition can be to 42000(8).
)SET /POOL
POOL=0420:150:430.
The first available location for user partitions is 42000;
the
longest free block is 150. words, and the total of all pool space
is 430. words.
Command Error Messages:
VMR -- ALIGNMENT ERROR
An attempt was made to create a partition, but the base address
or size conflicted with existing partitions or physical memory
size.

5-48

VMR COMMANDS
VMR -- DEVICE NOT VARIABLE SPEED MULTIPLEXER
An attempt was made to set the baud rate for a terminal that
not attached to a DBll or DZll multiplexer.

was

VMR -- DEVICE NOT TERMINAL
An attempt was made
nonterminal device.

set

terminal

characteristics

for

VMR -- INVALID SPEED
The multiplexer line specified does not support the requested
speed;
or the command specified unequal receive and transmit
speeds for a DZll. The DZll does not support split speeds.
VMR -- LINE NOT DZll
The command attempted to set to
attached to a DZll multiplexer.

remote

line

that

was

not

VMR -- NON EXISTENT MEMORY
An attempt was made to define a partition in nonexistent memory~
VMR -- PARTITION ALREADY EXISTS
An attempt was made to define a partition with a name already
use.

VMR -- PARTITION BUSY
A task or a driver
is installed
partition or subpartition.

loaded

the

specified

VMR -- POOL LINK ERROR AT xxxx BLOCK=yyyy zzzz
When SET IPOOL traced the pool linkage, it detected an error at
location xxxx in the system image.
The contents of xxxx is yyyy
and the contents of xxxx+2 is zzzz.
VMR -- SPACE USED
An attempt was made to create a partition or
storage area already occupied.

subpartition

An attempt was made to define more than seven subpartitions.
main partition is limited to a maximum of seven subpartitions.

VMR -- TOO MANY SUBPARTITIONS

5-49

VMR COMMANDS
VMR -- UNKNOWN MAIN PARTITION
An attempt was made to define a
main partition.

subpartition

nonexistent

VMR -- WRITE CHECK NOT SUPPORTED FOR DEVICE
An attempt was made to enable write check on a device that does
note support it.
Write check is currently supported for all
disks except DL:
and DX:.

5-50

VMR COMMANDS
TAS

TASKLIST

The TASKLIST command displays a description of each installed task on
the entering terminal.
The display contains in columnar form, from
left to right:
1.
2.
3.
4.
5.
6.
7.
8.

Task name,
Task version identification,
Partition name,
Task priority,
Size of task in bytes (octal),
Load device identification,
Disk address logical block number (octal), in a virgin system
image or task file identification in a saved system image,
and
Task memory state.

The format of the TASKLIST command is:
TAS[KLIST]
Example:
VMR>TAS
LDR.
LDR
248.
03
SYSPAR 248.
TKTN
RMDEMO M03
GEN
225.
MTAACP 0005
GEN
200.
FllMSG VOOIO SYSPAR 200.
SYSPAR 160.
• .• MCR 02
GEN
160.
· .• SYS 01
GEN
150.
• .• HEL 01
GEN
150.
• •• BYE 01
FllACP MM0234 FCPPAR 149.
DTAACP MS0234 GEN
149.
GEN
140.
· .. DMO 03
GEN
140.
· •. INI 03
GEN
140.
· •. MOU 03
140.
• .. UFD V0407 GEN
PMD ... 03
PMDPAR 130.

000000 LBO:-OOOOOOOO FIXED
010000 LBO:-00657407
013400 LBO:-00662334
012600 LBO:-00677004
010000 LBO:-00666657
010000 LBO:-00657050
010000 LBO:-00657202
040000 LBO:-00655150
040000 LBO:-00655ll7
026000 LBO:-00724342
010000 LBO:-00667662
040000 LBO:-00655177
040000 LBO:-00655206
040000 LBO:-00657271
040000 LBO:-00657416
020000 LBO:-00666610

On a system image generated for on 11/70 with more than l24K
words of memory, the size field (fifth column) contains 8-digit
rather than 6-digit numbers. This display is for a virgin system
image.
FIXED indicates that the task is fixed in memory.
VMR>TAS
· LDR.
TKTN
· •• MCR
• .• SYS
FllACP
· •• DMO
· .. INI
· .. MOU
• •. UFD
PMD ••.
SHF ••.
· .• INS

LDR
248.
SYSPAR 248.
SYSPAR 160.
GEN
160.
FCPAR 149.
GEN
140.
140.
GEN
GEN
140.
GEN
140.
PMDPAR 130.
SYSPAR 105.
GEN
100.

000000
010000
010000
010000
026000
040000
040000
040000
040000
020000
010000
040000

LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO :- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE

5-51

ID: (O,O) FIXED
ID: (2572,11)
ID: (2563,11)
ID: (2565,11)
ID: (2576,11)
ID: (2556,11)
ID: (2557 ,II)
ID: (2567 ,II)
ID: (2573,11)
ID: (26l0,12)
ID: (2606,11)
ID: (2562,11)

VMR COMMANDS
· •• SAY
· •. BAO
PRT •••
· •• BOO
• .. ACS
• •. PIP
· •. PSE
· .• AT.

GEN
GEN
PMOPR
GEN
GEN
GEN
GEN
GEN

100.
100.
10.
50.
50.
50.
50.
1.

040000
040000
020000
040000
040000
054300
031600
040000

LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO:- FILE
LBO :- FILE
LBO :- FILE

10: (2570,11)
10: (6l62,34)
10: (52l0,6)
10: (2273, 30)
10: (1066, 22)
10: (2627 ,II)
10: (5552,4)
10: (50l3,4)

The above display is from a saved system.
It differs from a
virgin system in two ways:
the task version is not displayed and
the file id of the task file,
rather than the logical block
number is displayed.

5-52

VMR COMMANDS
TIM

TIME
The TIME command allows you to:
• Set the time of day,
• Set the date, or
• Display the time and date.
The format of the TIME command is:
TIM[E]

[hrs:mins[:secs]]

[ml/day/year]

or
TIM[E]

[hrs:mins[:secs]]

[day-m2-year]

where:
hrs

hours (range 0-23)

mins

minutes (range 0-59)

secs

seconds (range 0-59)

numeric representation of month (range 1-12)

3-letter abbreviation for month

day

day (range 1-31)

year

year (range 0-99). Year is relative
1977 is entered as 77.

(optional)

1900;

•

If the command specifies neither time nor date,
the current system image time and date.

•

If the command specifies the time and date,
it sets the
system image clock and calendar.
If only the time is
specified, only the clock is set;
if only the date is
specified, only the calendar is set.

•

The time and date can be specified in any order.

•

All numeric values are decimal.
necessary (nor permitted).

terminating

Examples:
)TIM
10:23:31 03-NOV-77
Display the current system image time and date.
)TIM 1:30 11/4/77
Set the time to 01:30:00 and the date to 04-NOV-77

5-53

thus,

displays

period

VMR COMMANDS
UNFIX

UNF

The UNFIX command allows you to free a fixed task
image.
UNFIX is the complement of the FIX command.

from

If a fixed task exits or aborts, it still occupies
memory of the partition.

the

system

image

Format:
UNF[IX]

taskname

Example:
>UNFIX xke
Unfix task XKE, freeing the partition in which it resides.
Command Error Messages:
VMR -- TASK NOT FIXED
An attempt was made to
fixed.

5-54

unfix

task

that

was

not

VMR COMMANDS
UNLOAD

UNL

The UNLOAD command removes a loadable device driver from the system
image.
If a device is attached, its driver cannot be unloaded.
To unload a device driver from the system image, the driver's STB file
must reside on the same disk and under the same UIC as the system
image file.
The UNLOAD command cannot remove a data base from the system
even if the data base was loaded by means of the LOAD command.

image,

The format of the UNLOAD command is:
UNL[OAD] dd:
where:
dd:

is a 2-character ASCII device name

Example:
VMR>UNL LS:

!UNLOAD LPSll DRIVER (LSDRV)

Command Error Messages:
VMR -- DEVICE ddn:

NOT IN SYSTEM

No such device existed in the system.
VMR

DEVICE ddn:

IS ATTACHED

One or more device-units handled by the driver are attached.
The
first such unit is ddn:,
therefore,
the driver cannot be
unloaded.
VMR -- DRIVER BUILT WITH WRONG STB FILE
The STB file for the driver was not compatible with
Executive.

the

current

VMR -- DRIVER CAN NOT BE UNLOADED
The UNLOAD command attempted to remove a permanently resident
device driver (that is, a driver linked to the Executive).
VMR -- DRIVER NOT LOADED
The specified device
resident in memory.

driver

the

UNLOAD

command

was

VMR -- FILE name HAS ILLEGAL FORMAT
The driver's STB file contained incorrect object code or data.

5-55

not

VMR COMMANDS
VMR -- ILLEGAL VALUE FOR SYMBOL symname IN FILE name
The symbol symname has been defined to an illegal value by the
file name.
This occurs for several reasons, some general and
some specific to the individual symbols.
For example, most
symbols cannot be defined to zero and mapped loadable drivers
cannot reference $INTSV.
VMR -- INVALID RECORD ADDRESS FOR FILE name
An attempt was made to write outside of the system image file or
to write beginning at a byte boundary. The most frequent cause
of this is a corrupted system image or an STB file that does not
match the system image.
VMR -- LOADABLE DRIVER SUPPORT NOT IN SYSTEM
The system generation option to support loadable
was not chosen for the current system image.

device

drivers

VMR -- SYMBOL symname IS DOUBLY DEFINED BY FILE name
The symbol symname is defined twice by the
symbols are illegal.

filename.

Duplicate

VMR -- SYMBOL symname IS UNDEFINED IN FILE name
The symbol symname was found in the file name, but it was
symbol definition.

5.7

not

section

VMR ERROR MESSAGE SUMMARY

All error messages
alphabetical order.

produced

VMR

appear

this

VMR -- ADDRESSING EXTENSIONS NOT SUPPORTED
The command tried to install a task with a VSECT
(virtual
section) into a system image that does not support the feature.
VMR -- ALIGNMENT ERROR
The command tried to create a partition, but the base address or
size conflicts with existing partitions or physical memory size.
VMR -- BASE ADDRESS MUST BE ON 4K BOUNDARY
The base address of the task is not on a 4K boundary.
only to mapped system images.

Applicable

VMR -- BASE MISMATCH COMMON BLOCK <common-name>
The base address of the partition does not match that of
common block. Applicable only to unmapped system images.

5-56

the

VMR COMMANDS
VMR -- CANNOT FIX A TASK IN A SYSTEM CONTROLLED PARTITION
This is a restriction of VMR.
To fix a task in a system
controlled partition, use the MCR FIX command and then SAVe the
system image.
VMR

CHECKPOINT AREA TOO SMALL

The area allocated for checkpointing in the task image file is
smaller
than the partition into which the task is being
installed.
The system image does not support the dynamic
allocation of checkpoint space.
VMR -- CHECKPOINT SPACE TOO SMALL, USING CHECKPOINT FILE
This is a warning message. The checkpoint space allocated in the
task image file is too small for the size of the task (usually
because of the /INC keyword).
The system image supports the
dynamic allocation of checkpoint space and therefore uses a
checkpoint file to contain the rolled-out task.
VMR -- CIRCULAR REDIRECT ERROR
The command tried to redirect a device such that a circular
of redirected devices would result.

list

VMR -- COMMAND I/O ERROR
An I/O error was detected during a read from an indirect file.
VMR -- COMMAND SYNTAX ERROR
command line
The command line printed has incorrect syntax.
VMR -- COMMON BLOCK IS TASK PARTITION <common-name>
A task's request for access to a common block is rejected because
the partition requested is a task partition.
VMR -- COMMON BLOCK NOT LOADED <common-name>
The specified common block is linked to the task, but it has not
been loaded into the system image.
Install the specified common
block, then install the task.
VMR -- COMMON BLOCK OCCUPIED
The command
occupied.

tried

load

common

block

that

already

the

task's

VMR -- COMMON BLOCK PARAMETER MISMATCH <common-name>
Parameters of a common block do not match
label block.
5-57

those

VMR COMMANDS
VMR -- COMMON BLOCK SEGMENT COUNT ERROR
The command tried to install a resident library with overlays,
but the number of overlay segments specified in the task header
is different from the number
specified
in
the
segment
descriptors.
VMR

DEVICE ddn:

IS ATTACHED

One or more device-units handled by the
Therefore, the driver cannot be unloaded.
VMR -- DEVICE ddn:

driver

are

attached.

NOT IN SYSTEM

The specified device in the command was not defined in the system
image;
or the data base for a device driver to be loaded was
neither in the system image nor in the driver's task image.
VMR

DEVICE NOT MOUNTED

The device containing the system image file was not mounted.
VMR -- DEVICE NOT REDIRECTABLE
The specified device cannot be redirected.
VMR -- DEVICE NOT TERMINAL
The command tried to set terminal characteristics
that is not a terminal.

for

device

VMR -- DEVICE NOT VARIABLE SPEED MULTIPLEXER
The command tried to set the baud rate for a
not attached to a DHll or DZll multiplexer.

terminal

that

was

VMR -- DRIVER ALREADY RESIDENT
The specified device driver is already loaded or
resident in the system image.

permanently

VMR -- DRIVER BUILT WITH WRONG STB FILE
The STB file for the driver is not compatible with the
STB file for the current system image.

Executive

VMR -- DRIVER CANNOT BE UNLOADED
The UNLOAD command attempted to remove a permanently resident
device driver (that is, a driver linked to the Executive).

5-58

VMR COMMANDS

VMR -- DRIVER NOT LOADED
The specified device
resident in memory.

driver

the

UNLOAD

command

was

not

VMR -- DRIVER REQUIRES RUNNING SYSTEM FOR LOAD/UNLOAD
The requested driver included the symbols $ddLOA or $ddUNL in its
source. Support of driver load/unload calls can only be provided
by MCR LOAD/UNLOAD.
Note however,
that these symbols are
reserved for future use by the MCR LOAD and UNLOAD commands.
VMR -- EXECUTIVE IS TOO LARGE
The system image indicates that the Executive is larger than 16K
words,
but 20K Executive support was not included during SYSGEN
or, if 20K Executive support was included,
the Executive is
larger than 20K. The system is unusable.
VMR -- FILE filename HAS ILLEGAL FORMAT
The specified symbol table file has
RSX-llM/RSX-llS symbol table file.

invalid

format

for

VMR -- FILE filename HAS INCONSISTENT DATA
The driver has an invalid loadable data base.
When loading a
common library,
the partition extended beyond the size of the
task image file and thus could not be loaded.
See the RSX-llM
Guide to writing a Device Driver.
VMR -- FILE name NOT A VALID DRIVER TASK IMAGE
The driver's task image was either overlaid, had a
or referenced a resident library.

task

header,

VMR -- FILE NOT CONTIGUOUS
The command tried to install a task or load a driver
from a
non-contiguous file.
Task and loadable driver images must be
contiguous files.
VMR -- FILE NOT FOUND
The requested file is not
volume.

the