Digital PDFs

AA-2669H-TC

June 1985

459 pages

Original

15MB

Document:	RSTS/E V9.0 System Installation and Update Guide
Order Number:	AA-2669H-TC
Revision:	0
Pages:	459
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsts_e/V09/1_General_Information_and_Installation/AA-2669H-TC_RSTS_E_V9.0_System_Installation_and_Update_Guide_Jun85.pdf

OCR Text

RSTS/E
System Installation and Update Guide
Order No. AA-2669H- Te

RSTS/E
System Installation and Update Guide
Order No. AA-2669H-Te

June 1985
This guide describes how to install and update a RSTS/E V9.0 system.

OPERATING SYSTEM AND VERSION:

RSTS/E

V9.0

SOFTWARE VERSION:

RSTS/E

V9.0

digital equipment corporation. maynard. massachusetts

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

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

The following are trademarks of Digital Equipment Corporation:

~D~DDmDTM
DEC
DECmail
DECmate
DECnet
DECtape
DECUS
DECwriter

DIBOL
FMS-11
LA
MASSBUS
PDP
P/OS
Professional
Q-BUS
Rainbow

ReGIS
RSTS
RSX
RT
UNIBUS
VAX
VMS
VT
Work Processor

Page

Preface

xiii

Summary of Technical Changes

Introduction to System Installation
What Is System Installation?

RSTS/E Monitor .
Run-Time Systems
System Programs .
Layered Products .

.2
.2
.3

Types of System Installation
How to Use This Guide . .

.3
.3

Part I

Installing RSTS/E V9.0 on a New System

Structure of Part I . . . . . .
System Installation Flowchart .

Phase 1

.6
.7

Getting Started

Task 1: Collect Distribution Kits and Documentation .
Task 2: Physically Mount and Bootstrap Installation Media .
Tape Mount Session . . . . . .
Disk Mount Session . . . . . .
Bootstrap V9. 0 Installation Media

12
14
14
15
15

Phase 2 Prepare System
Task 1: Physically Mount Target System Disk.
Task 2: Answer Preliminary INIT.SYS Questions
Terminal Session . . . . . . . . .
Task 3: Initialize System Disk (DSKINT)
Terminal Session . . . . . . . . .
Task 4: Start SYSGEN Monitor (START)
Terminal Session . . . . . . . .

21
21
23
23
35
35

Phase 3 Configure RSTS/E Monitor
Task 1: Answer Preliminary Configuration Questions
Terminal Session . . . . . . . . . . . . . . .

39
39

iii

Task 2: Answer Terminal Interface Configuration Questions
Terminal Session . . . . . . . . . . . . . .
Task 3: Answer Disk Units Configuration Questions
Terminal Session . . . . . . . . . . . . . .
Task 4: Answer Peripheral Devices Configuration Questions
Terminal Session . . . . . .
Task 5: Calculate Number of Jobs
Preparation Session
Task 6: Answer Software Tuning and Features Configuration Questions
Terminal Session . . . . . . . . . . . .

43
.43
50
50
55
55
62
62
64
64

Phase 4 Select RSTS/E System Programs
Task 1: Answer System Program Installation Questions

Terminal Session . . . . . . . . . . . . . . .

Task 2: Answer Layered Product-Related Questions.

74
74

Terminal Session . . . . . . . .

Phase 5 Generate RSTS/E System
Task 1: Create Additional System Files
Terminal Session . . . . .
Task 2: Create RSTS/E Monitor
Terminal Session . . . . .
Task 3: Install System Programs from the Installation Media

78
78
82
82
84

Terminal Session . . . . . . . . . . .

Task 4: Physically Mount V9 Library Media.

87
87
88
88
90
90

Terminal Session . . . . . . . . . . .
Task 5: Install System Programs from the V9 Library Media.
Terminal Session . . . . . . . . . . . . . . .
Task 5A: Answer BASIC-PLUS Installation Questions
Terminal Session . . . . . . . . . . . . . . .
Task 5B: Answer SORT/MERGE Installation Questions
Terminal Session . . . . . . . . . . . . . . . .

94
94

Phase 6 Create Accounts and Edit System Start-Up File
Task 1: Create the System Management Account (CREATE/ACCOUNT) .
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . .

102
102

Task 2: Create User Accounts (CREATE/ACCOUNT)
Terminal Session . . . . . .
Task 3: Edit System Start-Up File
Terminal Session . . . . .

Phase 7

104
104
105
106

Start RSTS/E Monitor

Task 1: Shut Down SYSGEN Monitor (SHUTUP) .
Terminal Session . . . . . . . . .
Task 2: Start RSTS/E Monitor (START)
Terminal Session . .

108
108
110
112

Phase 8 Optional Tasl<s
Task 1: Reposition System Program Packages.
Terminal Session . . . . . .
Task 2: Apply a Mandatory Patch

118
119
122

System Installation Example
Part II

Installing RSTS/E V9.0 on a Pre-V9.0 System

Part III

Performing an Online System Installation

INSTAL.COM Entry Points.
Online Installation Example . . . . . . . . .

Part IV

Updating a RSTS/E V9.0 System

Structure of Part IV . . .
System Update Flowchart

Phase 1

147
148

Getting Started

Task 1: Back Up System Disk (BACKUP) .
Task 1A: Back Up Nonsystem Disk (BACKUP) .
Task 2: Shut Down Current Monitor (SHUTUP)
Terminal Session . . .

Phase 2

142
144

152
153
154
154

Prepare System

Task 1: Physically Mount and Bootstrap Installation Media.
Tape Mount Session . . . .
Disk Mount Session . . . . . . . .
Bootstrap Installation Media. . . . .
Use the INIT. SYS BOOT Option
Use the Hardware Bootstrap Loader .

158
158
158
159
159
160

Task 2: Copy Files to System Disk '(COPY)
Terminal Session

162
162
165
165

Task 3: Start SYSGEN Monitor (START)
Terminal Session

Phase 3

Configure New Monitor and Select Software Updates

Task 1: Answer Preliminary Questions
Terminal Session

Task 2: Use Information from a Template Monitor
Terminal Session

Task 3: Answer System Program Update Questions
Terminal Session

.Task 4: Answer Layered Product Update Questions
Terminal Session

Phase 4

Generate New System

Task 1: Create RSTS/E Monitor
Terminal Session

Task 2: Update System Programs and Transfer Layered Product Updates
Terminal Session

Phase 5

Terminal Session

•

Task 2: Start New RSTS/E Monitor (START)
Terminal Session

198
198
200

UPDATE. COM Entry Points
Selective Update Example

Offline Options

BOOT -

Bootstrap Devices

BOOT Dialogue
COpy -

DATE -

•

Copy System Installation-Related Files to Disk

COpy Dialogue

•

Set the Date and Time Format

DATE Dialogue
vi

190
190
192
193

Optional1asl(s

Task 1: Perform a Selective Update

Part V

182
182
186
186

Start New Monitor

Task 1: Shut Down SYSGEN Monitor (SHUTUP)

Phase 6

168
168
171
171
173
174
178
178

•

205
205
207
207
209
209

DEFAULT -

Change RSTS/E Monitor Defaults

211

. . . . . . . . . . .

211

Adjust the Memory Allocation Table.

215

LIST - List the Memory Allocation Table. . . .
LIST Dialogue . . . . . . . . . . . . . . . . .
PARITY - List the Parity Memory Configuration
PARITY Dialogue . . . . . . . . .
LOCK - Lock a Portion of Memory
LOCK Dialogue . . . . . . . . . .
Using the LOCK Suboption. . . . .
UNLOCK - Unlock a Portion of Memory
UNLOCK Dialogue. . . . . . . . . . . .
RTS - Position the Primary Run-Time System
RTS Dialogue . . . . . . . . . . . . . . . .
RESET - Reset the Memory Allocation Table .
RESET Dialogue . . . . . . . . . . . . . . .
XBUF - Allocate Memory to the Extended Buffer Pool
XBUF Dialogue . . . . . . . . . . . . . . .
Extended Buffer Pool Background Information. . . . .
Extended Buffer Pool Worksheet . . . . . . . . . . .
BUFFERS - Allocate Memory to the Small Buffer Pools
BUFFERS Dialogue . . . . . . . . . . . . .
Small Buffer Pool Background Information . . .
General and FIP Small Buffer Pool Worksheet. .
VIRTUAL - Allocate Memory to the Virtual Disk
VIRTUAL Dialogue. . . . . . . . .
Virtual Disk Background Information

216
216
218
219
220
220
221
223
223
225
225
227
227
229
229
230
235
237
237
239
246
248
248
249

DEFAULT Dialogue
DEFAULT Suboptions -

DSKINT -

Initialize RSTS/E Disks
. . . . .

251

Adjust the Hardware Configuration

263

DSKINT Dialogue
HARDWR -

251

HARDWR LIST - List the Hardware Configuration Table.
LIST Dialogue . . . . . . . . . . . . . . . . . .
HARDWR DISABLE - Disable a Device Controller
DISABLE Dialogue. . . . . . . . . . . . . . . .
HARDWR ENABLE - Enable a Device Controller
ENABLE Dialogue . . . . . . . . . . . . . . . .
HARDWR CSR - Declare a Nonstandard Controller Address
CSR Dialogue . . . . . . . . . . . . . . . . . . . . . . .
HARDWR VECTOR - Declare a Nonstandard Vector Assignment .
VECTOR Dialogue . . . . . . . . . . . . . . . . . . . . . . . .
HARDWR RESET - Set All Vector and CSR Addresses to the Standard,
and Enable All Devices . . . . . . . . . . . . . . . . . . .
RESET Dialogue . . . . . . . . . . . . . . . . . . . . . .
HARDWR DM - Declare DMII-BB and DHll Associations
DM Dialogue. . . . . . . . . . . . . . . . . . .
HARDWR HERTZ - Specify AC Line Frequency . . . . . .
HERTZ Dialogue . . . . . . . . . . . . . . . . . . . . . .
HARDWR SWITCH - Specify CPU Switch Register Characteristics
SWITCH Dialogue . . . . . . . . . . . . . . . . . . . . . . . .

265
265
270
270
273
273
275
275
277
278
280
280
281
281
283
283
284
284

vii

IDENT -

List the Version Number and Patch Information

IDENT Dialogue . .
PATCH -

Install a Patch

PATCH Dialogue . .
REFRESH -

Perform File-Related Tasks .

System File Background Information
REFRESH LIST - List File Status Table
LIST Dialogue . . . . . . . . . . . . .
REFRESH FILE - Change Account [0,1] File Characteristics
FILE Dialogue . . . . . . . . . . . . . . . . .
REFRESH BADS - Expand the Bad Block File .
BADS Dialogue . . . . . . . . . . . . .
SAVRES -

Back Up and Copy Disks . . . . . .

SAVE - Back Up a Disk to Tape or Disk.
SAVE Dialogue . . . . . . . . . . . . .
RESTORE - Recreate a Disk From Tape or Disk.
RESTORE Dialogue . . . . . . . . .
IDENTIFY - Extract Label Information .
IDENTIFY Dialogue . . . . . . .
IMAGE - Make a Copy of a Disk
IMAGE Dialogue . . . . . . .
START -

Start a RSTS/E Monitor .

START Dialogue.

287
287
289
289
293
293
302
302
305
305
307
307
309
312
312
316
317
321
321
323
323
327
327

Appendixes
A

System Installation Error Messages
Initialization Code Error Messages . . .
RTll Run-Time System Error Messages

Address and Vector Assignments
Aoating Addresses . . . . . . . .
Aoating Address Worksheet .
Aoating Vectors . . . . . . . .
Fixed Addresses and Vectors . .
RH70 BAE and CS3 Addresses

RSTS/E System Files

Bootstrapping the Distribution Medium
Bootstrapping Magnetic Tape Distribution.
Bootstrapping Disk Distribution . . . . . .

viii

331
343

345
346
353
355
356

366
366

Hardware Bootstrap Procedures
BM873-YA Procedure ..
BM873-YB Procedure ..
H324 Pushbutton Panel Procedure
MRll-DB Procedure . . . . . . .
BM792-YB Procedure . . . . . .
M930l-YA and M930l-YB Procedures
M930l-YC Procedure
M930l-YF Procedure . . . . . . . . .
M93l2Procedure . . . . . . . . . .
Using the M93l2 Console Emulator.
Determining the M93l2 Bootstrap ROM Configuration
Bootstrapping with the M93l2 . . . . . . . . . . .
Load Program Bootstrap for the RLOllRL02 and RK06/RK07
Load Program Bootstrap for the TUlO, TElO, or TS03

367
369
369
370
370
370
371
371
372
373
374
375
378
379
381

Additional System Installation-Related Programs
Using the BUILD/PATCH Program . . . . . . . . . . . . .
Using the DSKCVT Program . . . . . . . . . . . . . . . .
Using the ONLPAT Program to Patch RSTS/E Binary Code.
Using ONLPAT in Keyboard and Command File Mode
Patching a Running Monitor with ONLPAT . . . . .
Building ONLPAT Command Files . . . . . . . . .
Using the CPATCH Program to Patch ASCII Source Code
General Operating Procedures
Running the PBUILD Program . . .
PBUILD Dialogue . . . . . . . .
PBUILD/BUILD Terminal Output
Building CPATCH Command Files
Building the Patching Command File
File Naming Convention . . . .
Creating the CPATCH Command File.
Editing with CPATCH

......... .

CPATCH Editor Terms and Definitions
CPATCH Editor Commands ..
Verifying the Patch . . . . . . . . .
Building the PBUILD Command File
Using Comments . . . . . . . .
Using Indirect Command Files. .
Using the Underscore as a Quote Character
Command File Statements .. .
Sample PBUILD Command File .
Error Messages . . . . . . . . . . .

383
384
386
386
390
390
391
392
393
393
396
398
398
398
398
399
399
401
404
405
405
406
406
406
409
409

Mixed Disl< Drives on the Same Controller
Mixing RP04/RPOS/RP06 Drives on the Same Controller
Mixing RK06 and RK07 Drives on the Same Controller
Mixing RLOI and RL02 Drives on the Same Controller .
Mixing RM02/RM03/RMOS/RM80 Drives on the Same Controller
Mixing RM02/RM03/RMOS/RM80 and RP04/RPOS/RP06 Drives on
Separate Controllers . . . . . . . . . . . . . . . . . . . . . . .
Mixing RM02/RM03/RMOS/RM80 and RP04/RPOS/RP06 Drives on. the
Same Controller . . . . . . . . . . . . . . . . . . . . . .
Multiple RH Controllers for the Same Type of Disk . . . . . . . . . .
Random Mixing of RP and RM Disks on Multiple Controllers . . . . .
Booting Mixed RM02/RM03/RMOS/RM80 and RP04/RPOS/RP06 Disks .
Avoiding Bootstrap Conflicts . . . . . . . . . . . . . . . . . . . . .

415
415
415
416
416
416
417
417
417
417

Index
Figures
1
2

3
4
S

6
7
8
9
10
B-1
D-l

System Installation Flowchart .
Job Calculation Worksheet .
System Upgrade Flowchart. .
System Update Flowchart . .
Extended Buffer Pool for Example RSTS/E System
Extended Buffer Pool Worksheet . . . . . . . .
Example Small Buffer Table Printed DUring System Installation
General and FIP Small Buffer Pools . . . . .
General and FIP Small Buffer Pool Worksheet
System File Creation Worksheet
Floating Address Worksheet
M9312 ROM Arrangement . . .

.. 9

. 63
135
149
231
236
239
240
247
301
349
373

Tables
1
2
3
4
S

6
7
8
9
10
11
12
13
14
IS
16
17
18
19

Tape Device Designators . . . . .
Bootable Disk Device DeSignators
Disk Pack Cluster Sizes .. . . .
Device Cluster Sizes and Total Device Sizes .
DSKINT Error Messages . . . . . . . .
System Program Packages . . . . . . .
System Program Package Logical Names
BASIC-PLUS Optional Features . . . .
Monitor Defaults . . . . . . . . . . . .
System Program Package Logical Names
INSTAL. COM Entry Points. . . .
Tape Device Designators . . . . .
Boatable Disk Device DeSignators
COPY Error Messages . . . . . .
System Program Package Logical Names
INIT.SYS Selected Defaults
UPDATE. COM Entry Points
INIT.SYS Options . .
BOOT Error Messages . . .

16
17
26
27
34
68
84
90

111
118
143
161
161
164
173
192
199
203
205

20
21
22
23

25
26
27

28
29
30
31
32
33
A-1
A-2
A-3
B-1
B-2
B-3
D-1
D-2
D-3
D-4
D-5
D-6

D-7
D-8

D-9
E-1
E-2
E-3
E-4

COpy Error Messages . . . . . . . . . . . . . . . . .
DEFAULT and Memory Allocation Table Error Messages
Disk Pack Cluster Sizes . . . . . . . . . .
Device Cluster Sizes and Total Device Sizes .
DSKINT Error Messages . .
HARDWR Error Messages . . . . . . .
Hardware Comments Table . . . . . .
Summary Hardware Configuration Table
Reserved Hardware Locations . . .
Possible Input to the PATCH Option
PATCH Error Messages . . . . .
REFRESH Error Messages . . . .
Summary of System File Creation
Swap Times . . . . . . . . . . .
Initialization Code Error Messages
Recoverable RT11 Run-Time System 'Errors
RT11 Run-Time System Fatal Execution Errors
Device Vector Assignments . . . . . . . .
Devices with Fixed Addresses and Vectors .
RH70 BAE and CS3 Addresses . . . . . .
Summary of Hardware Bootstrap Addresses
Device Codes for M9301-YA and M9301-YB Bootstraps
Device Codes for M9301-YC Bootstrap
Device Codes for M9301-YF Bootstrap.
ROM Locations . . . . . . . . . . .
M9312 Bootstrap ROM Configuration
Device Name and Mnemonic. .
Switch Register Codes (SWR) . .
Console Switch Register Settings .
Responses to ONLPAT Questions
ONLPAT Dialogue Questions
PBUILD Error Messages .
CPATCH Error Messages ..

208
214
253
255
261
264
267
268
278
291
292
293
295
299
332
343
344

353
355
356
368

371
372
373
375
376
377
379
379
387
388

411
412

Objective
This gUide provides a task-oriented procedure for RSTS/E system installation and
update.

Audience
The audience for this guide includes:
o Anyone installing RSTS/E for the first time.
o Anyone upgrading to RSTS/E V9. 0 from a previous version of RSTS/E.
o Anyone updating an existing RSTS/E V9. 0 system.
o Anyone performing an online or partial system installation.

In addition, the Offline Options section of this guide provides reference material on all
the INIT.SYS options and sub options. System managers will find this section useful
for system tuning.

Document Structure
The guide is divided into six parts:
Part I

Tells how to build a new RSTS/E system. It is divided into seven phases
plus one optional phase, each consisting of one or more tasks. A summary
of the installation procedure is printed on beige paper at the end of Part I.

Part II

Explains how to perform a system intallation to upgrade an existing
RSTS/E system to V9.0.

Part III

Explains how to perform an online system installation to create a new
monitor, install system programs, or perform a full installation.

Part IV

Explains how to update an existing V9.0 system to a new release. It is
divided into five phases plus one optional phase, each consisting of one or
more tasks.

xiii

Part V

Is a reference section that describes the INIT.SYS offline options.

Appendixes A through F contain supplemental information that you may need for
your particular installation.

Related Documents
You may find the following documents useful while performing a system installation:
• RSTSIE V9.0 Release Notes
• RSTSIE System Manager's Guide
• RSTSIE Software Dispatch

Conventions
This gUide uses the following symbols and conventions:
Represents a carriage-returnlline-feed combination. Press the
RETURN key on your keyboard to produce this combination.
Indicates the circumflex key.
Italics

Indicates that a definition follows the italicized technical term.

(CTRUx]

Represents the CTRL key and some other keyboard character.
For example, to enter < CTRL/U > , hold down the CTRL key and
press the key labeled "U". RSTS/E echoes or displays the
character at your terminal as AU.

dot

fll a t r i x

color

Ihformation in this typeface indicates text displayed on the console
terminal.
Red dot matrix indicates the response made in the example
installation. Your response may differ from the response given in
the example installation.
Tells what task or phase you should perform next.

xiv

Summary or Technical Changes
The system installation and update process for RSTS/E V9.0 is quicker and easier
than in previous releases. The guide is renamed and reorganized to reflect these
changes, while still retaining the basic approach of the V8.0 manual.
The following is a summary of changes to this gUide for RSTS/E V9.0:
• V9.0 supports the following hardware: DHUIl1DHVll multiplexer, RD52 disk,
VT220/240 and LA200 terminals, RC25 disk, PDP-11173 and PDP-11184
systems, TK25 streaming tape, LN03 Laser printer, and LQP03 printer.
• V9. 0 no longer supports the following hardware: RFll disks, RS03/RS04 disks,
RK05 as a system disk, VT05 and VT50 terminals, and TU58 DECtape-II. See
the RSTS/E V9.0 Release Notes for a complete list of unsupported hardware.
V9.0 no longer supports the following devices as distribution devices: RLOl,
RK05, and RK06 disks; 800 bpi, 600 foot magnetic tape used on TS03
magnetic tape dirves.
o The following disk format restrictions apply to V9. 0:

- RDSO.O disks (pre-V8.0) can only be mounted read-only. They cannot be
mounted as system or public disks.
- RDS1.1 disks (V8.0) can be mounted read/write as private disks. They
cannot be mounted as system or public disks.
- RDS1.2 disks (V9.0) can be mounted read/write as system, public, or private
disks.
o The RSX emulator is now a permanent feature of the monitor. The RSX

run-time system is no longer necessary, because the monitor can now perform
all functions. The default keyboard monitor is DCL.
o The V9.0 system installation process makes system start-up quicker and easier.

The major changes are:
- You no longer need to configure the SYSGEN monitor.
- Indirect command files do much of the work for you.
- Many features are now automatically enabled, including directory caching,
some monitor feature patches, allocation of memory to XBUF, and creation
of SWAP.SYS and CRASH.SYS system files.
- The distribution kit contains two sets of media that you need for the
installation:
V9.0 Installation Media
V9 Library Media
You begin the system installation by mounting the Installation media.

- You press RETURN rather than LINE FEED to accept the default choice in
the system installation dialogue. You type a question mark (?) to obtain
online assistance.
- After you install you V9.0 monitor, you can use some or all of the
information from that monitor to configure future monitors during updates.
• The process to update an existing V9.0 system is now standardized. This gUide
describes how to update your system when you receive new releases of
RSTS/E from DIGITAL.
o The following changes have been made to INIT.SYS:

- The SET option is replaced by DCL commands. See the RSTS/E System
Manager's Guide for details.
- The CHANGE sub option of REFRESH is replaced by the DCL INSTALL
FILE/SYSTEM command. See the RSTS/E System Manager's Guide for
details.
- A new VIRTUAL suboption of DEFAULT lets you allocate memory to a
virtual disk. See the Offline Options section of this guide for details.
- A streamlined DEFAULT option selects more defaults automatically. You can
now set others online. See the Offline Options section of this gUide for
details.
- A new DATES option eliminates the need for INIT.SYS to unnecessarily
prompt you for the date and time. See the Offline Options section of this
gUide for details.
- The HARDWR UNITS sub option has been removed (except for RK05F
disks).
- The INSTALL option is now obsolete. Use the START option instead.
o The configuration questions in Phase 3 of Part I have been updated. In

addition, the LOAD/OVERLAY command replaces the four questions that
pertain to making certain sections of code permanently resident. See the
RSTS/E System Manager's Guide for details.

xvi

~n~roduction 10 Sys~em ~n$~aIlO1tion

This section explains some basic concepts about system installation. It also explains
how to use this gUide.

What Is System Installation?
System installation is the process by which you build:
o A RSTS/E monitor

o One or more run-time systems
o System programs
o Layered products

The following sections briefly explain each of these items.

RSTS/E Monitor
The RSTS/E monitor is a set of routines that controls:
• System scheduling - RSTS/E stands for Resource Sharing Time
Sharing/Extended. This means the monitor makes sure that all users can work
Simultaneously without interruption or interference; for example: running
programs, creating programs, accessing data files, or working with a text editor.
• Memory management used efficiently.

The monitor makes sure that computer memory is

• Input/output (I/O) services - The monitor handles requests to and from I/O
devices.
• Device management - Your installation probably has a variety of hardware,
such as tape drives, line printers, and disk drives. The monitor controls the
software that transfers data between these hardware devices and computer
memory.

o System program management -

A system program is software that provides
you with a set of tools for performing common tasks, such as copying or
deleting files. PIP and SYSTAT are examples of system programs. The monitor
keeps track of who is using these system programs.

DIGITAL sells RSTS/E to a diverse audience; therefore, each installation requires a
monitor suited to individual needs. During system installation, you build a RSTS/E
monitor that reflects the hardware you have (number and types of tape drives, disk
drives, and other peripheral deVices), and the software you choose (number of jobs,
number of small buffers, resident libraries, and so forth).
To get you started, DIGITAL supplies a temporary RSTS/E monitor (called the
SYSGEN monitor) on the installation tape or disk. This monitor is prebuilt and
requires no tailoring during system installation. You use it to build your RS,TS/E
monitor. After you build your RSTS/E monitor, you do not need the SYSGEN
monitor anymore. You will be instructed when to "shut it down."

Run-Time Systems
A run-time system is software that provides an environment for people to work in.
The primary run-time system controls system start-up and shut-down. Any additional
run-time systems you build are called auxiliary run-time systems.
The run-time systems that DIGITAL supplies with RSTS/E are:
o

Del

o RSX
o BASIC-PLUS
o

RTII

RSX is the default primary run-time system and Del is always the default keyboard
monitor.
The RSTS/E V9.0 monitor has RSX emulation. Because the monitor can now
perform all tasks previously associated with the RSX run-time system, you are no
longer required to use the RSX run-time system. For example, you can choose Del
as the primary run-time system and not even have RSX on your system.
You can specify a primary run-time system other than RSX during system installation
by using the INIT.SYS DEFAULT option. DCl and RSX are the only valid options.
See the Offline Options section for details.

System Programs
System programs provide you with tools for performing common tasks. For example,
system programs allow you to efficiently develop programs, manage files, and
perform special system management-related tasks. These system programs run under
the control of a run-time system. DIGITAL distributes RSTS/E system programs on
container files, located on the V9 library tapes or disks. You restore these container
files during system installation to obtain the system programs you need.

Introduction

Layered Products
A layered product, also called optional software, is software that you must purchase
from DIGITAL. You can build layered products after you complete the system
installation by processing the appropriate command file. Examples of optional
software are BASIC-PLUS-2, COBOL-S1, and DIBOL.

Types of System Installation
This gUide describes four types of system installations:
o

New - In this type of system installation you build a RSTS/E monitor, one or
more run-time systems, the required system programs, and any other optional
system programs.

Upgrade - In this type of system installation you upgrade a VS.O or earlier
version of the monitor to a V9. 0 monitor. This system installation is almost
identical to the previous one, except for some additional tasks.

o Online -

In this type of system installation you build a RSTS/E monitor during
timesharing on a previously installed V9.0 system. Note that you cannot
perform an online system installation to install a V9. 0 system from a VS.O or
earlier system.

Update - In this type of system installation, you update an existing V9.0
system to a new release. When you receive new V9.x Installation Kits from
DIGITAL (x= 1, 2, 3, and so on), use these procedures to update your V9.0
system to a V9. x system.

Another type of system installation is:
o System installation for another PDP-11 -

In this type of installation you build a
RSTS/E monitor on one PDP-11 fer use on another PDP-11. This means you
must know the hardware characteristics of the PDP-11 for which you are
building the RSTS/E monitor.

How to Use This Guide
The RSTSIE System Installation and Update Guide focuses on the tasks you must
perform to install or update your monitor, rather than the option or program used to
complete the task. The guide is divided into six parts:
• Part I tells how to build a new RSTS/E system. It is divided into seven phases
plus one optional phase, each consisting of one or more tasks. This logical
division of phases makes it easier to understand the complex process of system
installation. A summary of the installation procedure is printed on beige paper
at the end of Part I.
• Part II explains how to perform a system installation to upgrade an existing
RSTS/E system to V9.0.

Introduction

• Part III explains how to perform an online system installation to create a new
monitor or perform a partial installation.
• Part IV explains how to update an existing V9.0 system to a new release. It is
divided into five phases plus one optional phase, each consisting of one or
more tasks.
• Part V is a reference section that describes the INIT.SYS offline options.
• Appendixes A through F contain supplemental information that you may need
for your particular installation.

Introduction

~ns~alling RS1S/E V9.0 on Ol New Sys~em

Part'I describes the tasks you must perform to install a new RSTS/E V9.0 system.
This part of the gUide is for users who are less experienced and knowledgeable about
performing a system installation. It also provides an example installation for use as an
aid in explaining the tasks.
Some tasks require you to load and unload tapes or disks, depending on the RSTS/E
installation kit you received. Other tasks require you to answer questions and to make
decisions about some of the questions you need to answer.
The method of explanation depends on the type of task you perform. In tasks
requiring you to load a tape or disk, the gUide gives you general load instructions.
In tasks requiring you to answer questions and make decisions about the answers to
those questions, this guide first gives you any necessary background information,
followed by a terminal session. Each terminal session explains the question and gives
some possible responses. The question appears in dot matrix type. The response in
red next to the question is from an example installation. Use the example installation
as a gUide when you are bUilding your RSTS/E monitor. The example installation has
the following characteristics:
• CPU: PDP-11/44
• Memory: 512K words
• System Disk: RA80
• RSTS/E Distribution Kit: 1600 bpi magnetic tape
• Installation Kit: V9.0

Your responses may differ from the ones you see in the example installation. The
following example question is from a terminal session:

Explanation - This question asks for the device designator of your system disk.
Response - Acceptable responses for the system disks are: DL, OM, DP, DR,
DB, or DU.. In the example installation, the response is DU because the system
disk is an RABO.
In addition to the explanation in the guide, you also have access to online explanations. To print the online explanation of a question on your console terminal, type a
question mark (?).

Structure of Part I
Part I of this guide divides system installation into seven phases plus one optional
phase, where each phase consists of one or more tasks. For convenience, all the tasks
in a phase appear at the start of that section.
The contents of each phase follow:

Phase 1: GeHing Started
Provides instructions on collecting the required installation kits and documentation,
checking the kit order numbers, and physically mounting and bootstrapping the
Installation tape or disk.
Bootstrap instructions are in Appendix D. However, Phase 1 contains an example of
bootstrapping.

Phase 2: Prepare System
Describes how to mount, initialize, and copy files to your system disk. It also explains
how to start the SYSGEN monitor.

Phase 3: Configure RSTS/E Monitor
Explains how to answer the configuration questions that determine the hardware and
software your RSTS/E monitor will support.

Phase 4: Select RSTS/E System Programs
Describes how to select system programs. It also explains how to select layered
product updates that will be transferred later.

Installing RSTS/E V9.0 on a New System

Phase 5: Generate RSTS/E System
Explains how to generate the RSTS/E monitor. It also describes how to install system
programs and transfer layered product updates. Finally, it describes the dialogue to
install BASIC-PLUS and SORT/MERGE.

Phase 6: Create Accounts and Edit System Start-Up File
Describes how to tailor the START. COM file and create user accounts.

Phase 7: Start RSTS/E Monitor
Explains how to shut down the SYSGEN monitor and start the new RSTS/E monitor.

Phase 8: Optional Tasks
An optional phase that explains how to relocate system program packages or apply a
mandatory patch.

System Installation Flowchart
Figure 1, the System Installation Flowchart, summarizes the installation phases and
tasks. You may want to use this flowchart while you perform the system installation.

Installing RSTS/E V9.0 on a New System

PHASE 5
Generate RSTS,E
System

PHASE 3
Configure RSTS E
Monitor

PHASE 1
Getting Started

Task 1

Task 1
Collect
distribution kits
and documentation

Physically mount
and bootstrap
Installation media

Physically
mount target
system disk

Answer
configuration
questions

Task 1

Answer
preliminary
INIT.SYS
questions

PHASE 4
Select RSTS/E
System Programs

Create additional
system files

Task 2
Create RSTS/E
monitor

Answer system
program
installation
questions

DSKINT
Initialize
system disk

Task 3

Answer
layered product
update transfer
questions

COpy
Copy files to
system disk

Task 1

SHUTUP
Shut down
SYSGEN
monitor

CREATE/ACCOUNT

Task 2

START

Create user
accounts
Answer
SORT/MERGE
installation
questions

Install system
programs (and
layered product
updates) from the
Installation media

CREATE/ACCOUNT
Create system
management
account

Answer
BASIC-PLUS
installation
questions

Task 2

Task 1
Task 3

PHASE 7
Start RSTS/E
Monitor

Install system
programs from
the V9
Library media

Task 1

Tasks 1-6

Task 2

Task 5

Start RSTS/E
monitor

Task 3
End of RSTS/E
System Installation

Edit system
start-up file

Task 4
Physically
mount V9
Library media

HARDWR
Task 1

.--------,

Perform
hardware-related
tasks

START
Start
SYSGEN monitor

Reposition
system program
packages

PHASE 8
Optional Tasks

2
, , Task.----------,
,,
Apply a

mandatory patch

MK-01605-00

Figure 1:

System Installation Flowchart

Installing RSTS/E V9.0 on a New System

Phase
GS'lYing S~Olrteo]

This phase describes the tasks you must perform to prepare for a RSTS/E system
installation.
The tasks in this phase are:
o Task 1: Collect Distribution Kits and Documentation
o Task 2: Physically Mount and Bootstrap Installation Media

Task 1: Collect Distribution Kits and Documentation
DIGITAL sends you one of the following distribution kits:
• A Kit - for new RSTS/E customers. Contains complete RSTS/E documentation, RSTS/E V9 Library Kit, RSTS/E V9.0 Installation Kit, and all purchased
optional software kits.
• H Kit - for those whose service contract or warranty has expired or for those
who have purchased additional CPUs. Contains complete RSTS/E documentation, RSTS/E V9 Library Kit, RSTS/E V9. 0 Installation Kit, and all purchased
optional software kits.

• W Kit - for those under warranty or software product service contract.
Contains complete RSTS/E documentation, RSTS/E V9 Library Kit, RSTS/E
V9.0 Installation Kit, and all purchased optional software kits (only if the
original version has changed).
To perform a system installation, collect the following items from the A, H, or W kit:

• RSTSIE V9 Library Kit - Consists of the tape or disk that contains most of
the programs and files you need to perform a system installation.

• RSTSIE V9.0 Installation Kit - Consists of the tape or disk that contains
feature and mandatory patches and replacement modules. It also contains some
of the programs and files you need to perform a system installation and all the
programs and files you need to perform a system update. You receive this kit
for every new release of RSTS/E. The kits are labeled V9.I, V9.2, V9.3, and so
forth. Because each kit is cumulative, use the most current one. For example,
the V9.3 Installation Kit would contain all the patches and replacement modules
that were on Kits V9.I and V9.2, plus some new patches and replacement
modules.

• Optional Software Kit(s) - Optional software, also called layered products, is
purchased separately from the RSTS/E Distribution Kit. Examples of optional
software are COBOL-8I, BASIC-PLUS-2, and DIBOL. You purchase optional
software from an original equipment manufacturer or directly from DIGITAL.
Each optional software kit consists of the disk or tape that contains the
programs and files you need to install the optional software, along with the
appropriate documentation and installation gUide.

• RSTSIE V9.0 Release Notes - Explains the differences between the most
current and previous version of RSTS/E. You refer to this document during
system installation.
You may want to keep the following items nearby for use as reference material:

• RSTSIE System Manager's Guide - Describes how to operate and manage a
RSTS/E system. You refer to this manual during system installation for more

Geffing Started

information about creating accounts and editing the system start-up file. You
also use this manual to help manage your system on a day-to-day basis.

• RSTSIE Software Dispatch - Contains new and revised software product
descriptions (SPD), programming notes, patches and replacement modules for
system programs and optional software, and documentation corrections.
If one or more of these items is missing, contact your local DIGITAL software support
specialist.
Check the order numbers that appear on the tapes or disks that make up your
RSTS/E V9 Library Kit and RSTS/E V9.0 Installation Kit to be sure they match the
order numbers that appear in the RSTSIE Release Notes. The RSTSIE Release Notes
also contains the order numbers for the DECnetiE Software Kit and the RJ2780
Software Kit. To check the order numbers of any other optional software kits, refer to
the bill of materials.

Go to Task 2.

GeHing Started

Task 2: Physically Mount and Bootstrap Installation Media
This task requires you to mount and bootstrap the appropriate tape or disk from your
RSTS/E Distribution Kit. First, the task provides instructions for mounting the tape on
a tape· drive, or mounting a disk on a disk drive. Choose the appropriate section for
your type of installation media. Second, the task provides an example of
bootstrapping the tape or disk.
In the example installation, the kit is a RSTS/E V9.0 Installation Kit, consisting of a
9-track, 1600 bits per inch (bpi) tape.
Tape Mount Session

Mount the 800 or 1600 bpi 9-track tape from your RSTS/E Distribution Kit that has
the label V9.0 Installation. This tape contains the system installation files and
programs. Note that there may be other programs and files on this tape. The chart in
the RSTSIE Release Notes shows the contents of each tape.
To load the tape on the drive:

Physically mount the tape on drive unit 0 or 1 with the write-enable ring
removed. If you have a combination of TU10, TE10, TU16, TE16, TU45 , and
TU77 tape drives, load the 800 bpi distribution tape onto unit 0 or 1 of the
TU10 or TEla tape drive. If you have a combination of TU16, TE16, TU45,
TU77, TS11, TSV05, and TU80 tape drives, load the 1600 bpi distribution
tape on unit a or 1 of the TS 11 drive.

Press the LOAD indicator.

The drive autolJ1atically winds the tape until the beginning of tape (BOT)
indicator light comes on. This indicates the tape is at its load point.

Make sure that the write-lock (WR) indicator light is on. (If not, dismount the
tape, remove the write-enable ring, and then remount the tape.)

Press the ONLINE indicator. The indicator light comes on.

Make sure the console terminal is on line. The console terminal is usually a
hard-copy terminal that you use during system installation.
Note _ _ _ _ _ _ _ _ _ __

The previous instructions may not apply to your tape drive. If so, see
the hardware manual supplied with your tape drive for the load
instructions.

Getting Started

Disk Mount Session
Mount the disk from your RSTS/EDistribution Kit that has the label V9.0 Installation.
This disk contains the system installation programs and files. Note that this disk may
also contain other files and programs. The chart in the RSTSIE Release Notes shows
the contents of each disk.
To load the disk onto the disk drive:

Physically mount the disk in drive unit 0 or 1. If you have an RL02 disk, you
can mount the disk in any drive unit.

Make sure that the READY light is on.

Make sure that the write-protect (WR PROT) light is on.

Make sure that the console terminal is on line. The console terminal is usually a
hard-copy terminal that you use during system installation.
---------------------- Note -----------------------

The previous load instructions may not apply to your disk drive. If so,
see the hardware manual supplied with your disk drive for the load
instructions.

Bootstrap V9.0 Installation Media
Now you must bootstrap the tape or disk, which means using the PDP-II Central
Processing Unit (CPU) switches to activate a hardware bootstrap loader. There are
different types of hardware bootstrap loaders; the type you have on your PDP-II
determines which CPU switches you should tise.
The hardware bootstrap loader is a device inside your PDP-II that reads a bootstrap
record from the tape or disk into memory. This bootstrap record contains a program
that loads and executes additional program code from the tape or disk.
Your DIGITAL field service representative or software support specialist should
already have identified the type of hardware bootstrap loader on your PDP-II. The
representative should also have given instructions for bootstrapping your tape or disk.
If you do not know how to bootstrap the V9.0 Installation media, see Appendix 0,
which contains bootstrap instructions for the different types of hardware bootstrap
loaders.

The example installation shows how to bootstrap the 1600 bpi tape from a TU80
tape drive, by activating switches on a PDP-ll144. These bootstrap instructions are:

Move the control switch (CONT) to the HALT position.

Move the control switch to the BOOT position.

GeHing Started

The CPU prints some octal numbers on the console terminal, followed by three angle
brackets:
»>5 MSO

The »> prompts for a command. Type B to indicate a BOOT operation, followed
by the device designator or device specification of the drive on which your tape or
disk is mounted. A device designator consists of two letters that identify the device
type, followed by the decimal unit number of the drive and a colon. (However, do
not specify a colon here.) The example installation uses a TU80 tape drive: thus, the
tape device designator is MSO.
Table 1 lists the tape device designators. Table 2 lists the boatable disk device
designators. Enter the appropriate device designator for your instqllation.
About 30 seconds after you type the device designator, the following prints on the
console terminal:
Enabling only consolet disKst and tapes.
RSTS 1.18.0 (MSO)

INIT 1.18.0-14

Current date <DD-MMM-YY>?

The Current date prompt means that INIT.SYS is loaded into memory. You have
successfully bootstrapped your installation media. Note that the· device designator of
the tape or disk drive you bootstrapped appears within parentheses. In the example
installation, the device designator is MSO.
Table 1: Tape Device Designators
Designator

Device

MMO: to MM7:

TE16ffU16ffU4SffU77 magnetic tape units 0 to 7

MSO: to MS3:

TSllffSVOSffU80ffK2S magnetic tape units 0 to 3

MTO: to MT7:

TEIOffUIOffS03 magnetic tape units 0 to 7 *

*Note: You cannot use a TS03 drive for system installation.

Getting Started

Table 2 lists the bootable disk device designators.
Table 2:

Bootable Disk Device Designators

Designator

Device

DBO: to OB7:

RP04/RPOS/RP06 disk drive units 0 to 7 *

DKO: to OK7:

RKOS/RKOSF disk drive units 0 to 7

OLO: to OL3:

RLOllRL02 disk drive units 0 to 3

OMO: to OM7:

RK06/RK07 disk drive units 0 to 7

OPO: to OP7:

RP02/RP03 disk drive units 0 to 7

ORO: to OR7:

RM02/RM03/RMOS/RM80 disk drive units 0 to 7 *

OUO: to OU7:

RA60/RA80/RA811RCF2S,RC2S/ROSlIROS2/RX50 disk drive units 0 to 7

*See Appendix F for more information on multiple RH controller configurations.

Go to Phase 2.

GeHing Started

Pho]se

PrepOlre Sysvern

After you bootstrap the V9.0 Installation tape or disk, you are ready to prepare your
system for the installation. First you prepare your system disk. The system disk is the
disk on which your RSTS/E monitor will reside. Nonsystem disks store other files and
programs that might not fit on the system disk. Next you start the SYSGEN monitor,
a prebuilt monitor supplied by DIGITAL. You use the SYSGEN monitor to generate
your new monitor.
The tasks in this phase are:
o Task 1: Physically Mount Target System Disk
o Task 2: Answer Preliminary INIT.SYS Questions
o Task 3: Initialize System Disk (DSKINT)
o Task 4: Start SYSGEN Monitor (START)

Task 1: Physically Mount Target System Disk
Mount your system disk on a free drive, either 0 or 1. If you are performing an
installation for another system, mount the target system disk instead.
---------------------- Note -----------------------

Unless your system disk is a DU or DL class device, you must mount
your system disk (as well as your V9.0 Installation tape or disk) on
drive 0 or 1 because the SYSGEN monitor recognizes only units 0
and 1 of each device type. For example, if you mount your system
disk on drive 2 at this stage, the SYSGEN monitor fails during
start-up.

If your disk is a DU or DL class device, you can mount it on disk drive
0, 1, 2, or 3. See Table 2 for a list of disk device designators.

Follow either the disk mount instructions in Task 2 of Phase 1 or the disk mount
instructions in the appropriate hardware manual. Do not remove the V9.0 Installation
tape or disk that contains the system installation programs and files.

Prepare ~y~t~m

Go to Task 2.

Task 2: Answer Preliminary INIT.SYS Questions
Your next task is to answer the Date and Time questions, and then to answer the
preliminary INIT.SYS questions.

Terminal Session
You have now successfully bootstrapped your V9. 0
Installation media, and the INIT.SYS program is loaded into
memory. INIT.SYS prints its banner, and prompts you for the
date and time.

RSTS V9.0 (MSO) INIT V9.0-14
Current date <DD-MMM-YY>? 31-MaY-85
Current tiMe <HH:MM AM/PM>? 05:00 AM

Explanation - INIT.SYS prompts you for a valid date and time. You see the date
and time prompts when you bootstrap a disk from the console boot/restart switch.
If you specified the date and time at some earlier point and you used the BOOT
option of INIT.SYS to bootstrap the disk, then INIT.SYS simply displays the current
date and time before proceeding to the next prompt.

Response - Type the current date and time in the alphabetic format.
Installin9' RSTS on a nel,..l SYstelTl dis.,? <Yes>

Explanation - INIT.SYS asks this question whenever you bootstrap a tape. or disk
read-only. (RSTS/E Distribution Kits are always read-only). If you answer YES,
INIT.SYS assumes you are performing a new V9.0 system installation and want to
use the DSKINT option to initialize your system disk. INIT.SYS then prompts you for
the location of the system disk.
If you answer NO, INIT.SYS asks if you are updating an existing RSTS system disk
before proceeding with a COpy operation.

---------------------- Note
In V9.0, any system or public disk must be a RDS1.2 format disk.
Answer YES to this question if you are performing a new installation.
If you are upgrading to V9. 0 from a previous release of RSTS/E, see
Part II of this gUide for instructions.

Prepare System

Type YES or press RETURN to proceed with the disk initialization.
Because the example installation is a new RSTS/E V9.0 installation, the response is
RETURN to accept the default of YES.

Response -

If you answered YES to the previous question, go to Task 3.

If you answered NO to the previous question, go to Task 4.

Prepare System

Task 3: Initialize System Disk (DSKINT)
Your next task is to initialize the system disk with DSKINT, an INIT.SYS program
option. DSKINT:
• Optionally formats the disk. DSKINT writes timing and sense marks on the disk
and destroys any previously stored information.
o Optionally checks the disk for bad blocks. DSKINT locates bad blocks on the

disk and allocates them to the bad block file (BADB.SYS).
o Writes a minimum RSTS/E file structure on the disk. The minimum RSTSIE file
structure contains a pack label and three directories:

- The Master File Directory (MFD)
- The Group File Directory (GFD)
- The User File Directory (UFD) for account [0,1].
o Prepares the disk to accept RSTS/E system and other files.

Terminal Session
To initialize your system disk, you must answer the DSKINT
questions. This terminal session lists the questions, explains
them, and gives you some possible responses. After you
understand the question, type the response at your console
terminal. In some cases, your response will differ from the
response shown in red in the example installation.

These responses have special meaning:
Response

DeSCription

(0)

Accept the default response

Obtain an online explanation of the question
Return to the previous question
Restart DSKINT dialogue
Abort DSKINT and return to the Option: prompt

The common DSKINT dialogue error messages appear in Table 5, at the end of this
task. If you receive an error message that does not appear there, see Appendix A.
31-MaY-85 - 05:02 AM
Dis~n

Prepare System

Explanation - After you answer YES to the Installing RSTS on a new system disk?
question, INIT.SYS automatically begins the DSKINT dialogue. DSKINT prints the
current date and time, and then asks for the device designator of your system disk.
Response - Type one of the acceptable responses for system disks: DL, DM, DP,
DR, DB, or DU. In the example installation, the response is DU because the system
disk is an RA80.
Un it? 0

Explanation - DSKINT asks for the unit number of the disk drive on which your
system disk is mounted.
Response - Type one of the acceptable responses at this stage of system
installation: 0 or 1. (If your system disk is a DL or DU class device, acceptable
responses are 0, 1, 2, or 3.) The response is 0 in the example installation.
This disK appears to be a RSTS/E forMatted
disK with the following characteristics:
PacK 10:
PacK Cluster Size:
PacK is currently:

NATHAN
8

Private t
Update access date on writest
Level: 1.1

Pad, IO? SYSOSK

Explanation - After you type the unit number, DSKINT prints the disk's pack label
information, if the disk has been initialized before. If the disk has not been initialized
before, DSKINT does not print the identifying information. The pack label information
lists:
• Pack ID
• Pack cluster size
• Pack status (public or private)
• Whether files are catalogued with the date they were last modified (written to)
or accessed (read, opened, closed, and so forth)
• New files first information
• Whether the disk is read-only
• Format level.
This private disk could be a system disk; DSKINT cannot determine whether a private
disk is also a system disk. In the example installation, the pack ID is NATHAN, the
pack cluster size is 8, the pack status is private, the files are catalogued with the date
they were last written to, and the format level is RDS 1.1.
This information lets you decide whether to initialize the disk. When you initialize a
disk, you destroy any information stored on it. Because this disk is a format level
RDS 1.1 disk and contains no vital information, it will be initialized and used as the

Prepare System

new system disk. If your disk contains vital information, see Part II, Installing RSTS/E
on a Pre-V9.0 System, for information on how to preserve the information.
After printing the pack label information, DSKINT asks for a pack 10. The pack ID is
a system-wide logical name. You must specify this pack 10 when you logically mount
the disk.
Response - Type a one- to ·six-character alphanumeric pack 10. The pack ID in the
example installation is SYSDSK.
Pad\ cluster size <4>?

m
Note -----------------------

Some questions show a response within brackets, like the one in this
question «4>?). This is the default response. To accept any default
response, press RETURN. The RETURN response does not print on
your console terminal. The
symbol appears in the example
installation to show you that the RETURN key was chosen as a
response.)

Explanation - A cluster is a fixed number of 512-byte blocks of storage area
allocated contiguously on a disk. The pack cluster size is the minimum number of
blocks that your RSTS/E monitor can allocate to a file on the disk.
Your answer to this question depends on the type of processing and the disk
requirements of your installation. The pack cluster size affects disk space and speed of
file creation and access. A large pack cluster size improves access time to programs
and user files because the monitor allocates space for data in cluster units. For
example, if the pack cluster size is 16, the monitor allocates 16 blocks at a time.
However, if the pack cluster size is two, the monitor allocates only two blocks at a
time. Thus, more disk accesses are needed to allocate the same amount of space.
On the other hand, a large pack cluster size. may waste disk space. For example, if
you assign a pack cluster size of 16, the monitor allocates one cluster of 16
contiguous blocks (8,192 bytes) to a file that contains only one block (512 bytes) of
information. Fift~en blocks (7,680 bytes) are wasted. Likewise, the monitor allocates
one cluster of 16 contiguous blocks to a 15-block (7,680 bytes) file. In this case, only
one block (512 bytes) is wasted.
Response - Type the disk pack cluster size. For system disks, DlGITAL
recommends a pack cluster size of 4 or greater. In the example installation, the
response is RETURN to accept the default cluster size of 4.

Prepare System

Table 3 lists the disk cluster sizes.
Table 3:

Disk Pack Cluster Sizes

Disk
Type

Pack Cluster
Size

RX50*

1,2,4,8,16

. RC25

1,2,4,8,16

RD51

1,2,4,8,16

RD52

1,2,4,8,16

RK05*

1,2,4,8,16

RK05F*

1,2,4,8,16

RL01

1,2,4,8,16

RL02

1,2,4,8,16

RK06

1,2,4,8,16

RK07

1,2,4,8,16

RP02

2,4,8,16

RP03

2, 4, 8, 16

RM02

4,8,16

RM03

4,8,16

RP04

4, 8, 16

RP05

4,8,16

RA80

4,8,16

RM80

4, 8, 16

RP06

8, 16

RA60

8, 16

RM05

8, 16

RA81

*You cannot use these disks as system disks.
MFD cluster size <18>?

Explanation - The master file directory (MFD) stores information about all accounts on a disk. The monitor accesses the MFD each time you add or delete
accounts and files from the disk.
This question asks for the MFD c/ustersize, which is the maximum number of
512-byte blocks that each cluster allocated to the MFD can contain. The MFD can
have a maximum of seven clusters (if you answer YES to the Pre-extend directories?
question later in this task), and each directory is the size that you specify here.

Prepare System

The MFD cluster size must be greater than or equal to the pack cluster size and must
not be greater than 16. Legal values for the MFD cluster size are 4, 8, or 16.

Response - Type 4,8, or 16. Or, press RETURN to accept the default response of
16, as in the example installatiory.
SATT.SYS base <118585>? (!!ffi

Explanation - The SA IT.SYS file controls the use of storage space on a disk
through a storage allocation table (SAT). The monitor accesses this file each time you
extend or delete files. This question asks where you want to position this file on the
disk. It is advantageous to position the SATT.SYS file near the center of the disk to
reduce average seek times for the disk heads. On the other hand, if you use only the
first half of a disk or need to create large contiguous files, you may want to locate
SATT.SYS in a place other than the center. This reduces fragmentation of the disk.
The position of the SATT.SYS file is also important because its position determines
the default placement of the monitor and the primary run-time system, as well as the
SWAP.SYS system file.
The number that appears within brackets is the center of the disk as calculated by
DSKINT. (DSKINT may calculate a different number for your disk.) The device
cluster number can range from 1 to the total device size divided by the device cluster
size. See Table 4 for a list of disk device cluster sizes and total device sizes.

Response - Press RETURN to have DSKINT position the file near the center of the
disk. In the example installation, the response is RETURN.
Or, type the device cluster number where you want the file placed.
Table 4 lists the disk device cluster sizes and total device sizes. Note that the table
shows the total blocks that are available for use, not the total size of the disk. In
addition, the number of available blocks may vary if your system has a different
device cluster size.
Table 4:

Device Cluster Sizes and Total Device Sizes

Disk
Type

Device
Cluster
Size

RX50*

799

RC25

50901 per unit;
2 units per spindle

RD51

21599

RD52

60479

RK05*

4800

RK05F*

4800 per unit;
2 units per drive

RL01

10220

Total Available
Blocks

(continued on next page)

Prepare System

Table 4:

Device Cluster Sizes and Total Device Sizes (Cont.)

Disk
Type

Device
Cluster
Size

RL02

20457

RK06

27104

RK07

53761

RP02

39998

RP03

79998

RM02

131648

RM03

131648

RP04

171796

RP05

171796

RA80

237208

RM80

242572

RP06

340664

RA60

400168

RM05

500352

RA81

891056

Total Available
Blocks

*You cannot use these disks as system disks.

Pre-extend directories <NO>?

Explanation - This question asks if you want DSKINT to allocate automatically a
maximum of seven clusters to the system account [0,1], the LB: library account [1,1],
the system library account [1,2], and the MFD and GFDs for groups 0 and 1. The
number of blocks each of these seven clusters contain depends on how you answered the cluster size questions for each of these accounts. For example, if you
specify 16 as the cluster size for account [1,2] and answer YES to this question,
DSKINT allocates the maximum of seven clusters to this account. Each cluster is
8,192 bytes (16 times 512 bytes).
Response - Type YES to have DSKINT automatically allocate a maximum of
seven adjacent clusters to these accounts. In the example installation, the response is
RETURN.
I

Or, type NO or press RETURN if you want DSKINT to allocate only the minimum of
o or 1 clusters.
PUB t PRI tor SYS <SYS>? m

Prepare System

Explanation - This question asks you to designate the disk you are initializing as
either public, private, or system. The system disk is the disk on which the RSTS/E
monitor resides. It always contains account [1,2].
Response - Type SYS or press RETURN, because you are initializing a system disk
in this task. In the example installation, the response is RETURN.
[ltl] cluster size <18>? ~

Explanation - This question asks for the cluster size of the User File Directory
(UFD) for account [1,1]. The UFO is an area on the disk that stores information
about the files created under a particular user account number. The cluster size for
account [1,1] is the maximum number of 512-byte blocks that each cluster allocated
to this account can contain.

Response - Press RETURN to accept the default response of 16. In the example
installation, the response is RETURN.
Or, type the cluster size for account [1,1]: 1, 2,4, 8, or 16. It must be greater than or
equal to the pack cluster size and must not be greater than 16. Specifying a large
cluster size improves disk access time.
Because the example installation's answer to the Pre-extend directories? question was
NO, OSKINT allocates one cluster containing 8,192 bytes (16 times 512 bytes) to this
account.
[1,2] cluster size <18>? ~

Explanation - This question asks for the cluster size of the UFO for account [1,2].
The cluster size for account [1,2] is the maximum number of 512-byte blocks that
each cluster allocated to this account can contain.
Response - Type the cluster size for account [1,2]: 1, 2, 4, 8, or 16. It must be
greater than or equal to the pack cluster, size and must not be greater than 16.
OIGITAt recommends that the cluster size for account [1,2] be 16, to improve disk
access time. Press RETURN to accept the default response of 16, as in the example
installation.
Because the example installation's answer to the Pre-extend directories? question was
NO, OSKINT allocates one cluster containing 8192 bytes (16 times 512 bytes) to this
account.
[1 tlJ and [1,2] account base <118595>? ~

Explanation - This question asks whether you want to place accounts [1,1] and
[1,2] near the center of the disk or in some other place. The number that appears
within brackets is the position of SATT.SYS, that is, the number you specified to the
SATT.SYS base? question, or the middle of the disk as calculated by OSKINT if you
specified RETURN to that question. OSKINT may show a different number for your
disk.
Response - Press RETURN to place these accounts near the center of the disk. In
the example installation, the response is RETURN.

Prepare System

Or, type the device cluster number where you want these files placed. The device
cluster number can range from 1 to the total device size divided by the device cluster
size. See Table 4 for a list of device cluster sizes and total device sizes.
Date

last modified <YES)?

Explanation - This question asks whether you want to retain the date on which
files were last modified (written to) or last accessed (written to, opened, read from,
closed, and so forth).
Response - Type YES or press RETURN to retain the date on which files were last
modified. This response is useful if you plan to use the BACKUP system program to
back up files that have changed since the last backup. This response also decreases
disk activity because the RSTS/E monitor updates the date only if the files are written
to. In the example installation, the response is RETURN, which means the monitor
updates the date each time the files are modified.

Or, type NO to retain the date on which files were last accessed. This response is
useful for reordering the files, so the most frequently accessed files can be placed at
the beginning of the directory. This response increases disk activity because the
RSTS/E monitor updates the date no matter how the file is accessed for reads or
writes.
Nel,..l files first <NO)?

Explanation - This question asks if you want newly created files placed at the
beginning or end of the directory of the account in which they are created.
Response - DIGITAL recommends that you type NO or press RETURN to place
newly created files at the end of the directory, giving you overall faster access time. In
the example installation, the response is RETURN.

Or, type YES to place newly created files at the beginning of the directory. This
response is useful when you have a private disk on which the files you most
frequently access are new files.
Read-onh' <NO)?

Explanation - This question asks if you want this disk to be, by default, a readonly or a read/write device when it is logically mounted. You can write to a read-only
disk when you logically mount it with the !WRITE qualifier.
Response - Press RETURN to make your system disk read/write. In the example
installation, the response is RETURN.
Use previolls bad

bloc~\

info <YES)?

Prepare System

Response - DIGITAL recommends that you type YES or press RETURN to create
the new bad block file, using information from the existing bad block file. In the
example installation, the response is RETURN.
Or, type NO to have DSKINT ignore the current bad block file when creating the
new one. You may want to answer NO, for example, if you are reinitializing a disk to
decrease the pack cluster size. In this case, you want to obtain new bad block
information.
Fa rlTlat <NO)?

Explanation - This question asks if you need to format your disk. Formatting a
disk means that DSKINT writes timing and sense marks onto the disk and destroys
any information that previously existed on the disk. You must format the following
disks if you are initializing them for the first time: RK05, RK05F, RP02, RP03, RP04,
RP05, RP06.
You can optionally reformat these disks: RK06, RK07, RM02, RM03, RM05.
You cannot format or reformat (in which case this question would not appear) these
disks: RL01, RL02, RA60, RA80, RA81, RC25, RM80, RD51, RD52, RX50.
----------------------- Note

If you are formatting a disk, DIGITAL recommends that you mount
the disk on the drive and leave it spinning for 20-30 minutes before
initializing it. This ensures that the disk temperature is stable and
uniform during the formatting. Failure to do this may cause unreliable
data storage on the disk.

Response - Type YES to format the disk; type NO or press RETURN if you do not
need to format the disk. This question does· not appear in the example installation.
Patterns <3)? @

Explanation - This question asks for the number of patterns DSKINT should use in
checking for bad blocks. You can select a number from 0 to 3. If you select 0
'patterns, DSKINT also prints the Erase disk? prompt.
DSKINT writes a pattern to the disk, and then reads it to check that the data was
written correctly. The time DSKINT takes to run these pattern checks for bad blocks
depends on the disk you are initializing. Type a question mark (?) to have DSKINT
print the time (in minutes) required for the different disks to complete one format
check for bad blocks.
For DU class disks, with the exception of RX50, bad blocks are handled transparently
by the hardware. No blocks are ever added to the BADB.SYS file, since the
hardware simply replaces the bad block 'with a new one. DIGITAL still recommends
that you run 3 patterns the first time you initialize a DU class disk.

Prepare System

Response - Type the number of patterns (0 to 3). DIGITAL recommends you run
3. Any bad blocks discovered during pattern checking are added to the bad block file
(BADB.SYS) so that data will not be written to these blocks. If you specify 0,
DSKINT then asks the next question. In the example installation, the response is
RETURN.
Erase disK (YES>?

Explanation - This question, which appears only if you answered 0 to the Patterns? question, asks if you want to erase the disk. If you answer YES, DSKINT wipes
out all data on the disk. This is usually done for security purposes.
If you answer NO, DSKINT writes only the basic RSTS/E file structure on the disk.
Use the NO response under the following conditions:
o

You are initializing a disk that has been initialized before.

o You answered YES to the Use previous bad block info? question.
o You are confident no additional bad blocks are on the disk.
o

You are not concerned about the security of old data that could still be
accessed.

Response - The example installation did not see this question, because it did not
answer 0 to the Patterns? question.
Proceed (Y or N)? Y

Explanation - This question allows you to check your responses to the dialogue
questions and abort the initialization if you have made any errors.
Response - Type Y to proceed with the disk initialization. In the example
installation, the response is Y.

Or, type N to abort the initialization and return to the Option: prompt.
DSKINT formats the disk; then begins pattern checking with pattern 3 and ends with
pattern 1. If DSKINT prints a block and device cluster number during pattern
checking, it adds the device cluster number (not the block number) to the BADB.SYS
file. Note that this disk (a DU class disk) did not contain any bad blocks.

Prepare System

Note -----------------------

When you are formatting RP02 or RP03 disks, DSKINT prints two
requests after the Starting and Ending format pass messages:
SET FORMAT ENABLE SWITCH, THEN TYPE <RET>:

Set the RPll controller FORMAT ENABLEINORMAL switch to
ENABLE, then press RETURN.
SET FORMAT SWITCH TO NORMAL, THEN TYPE <RET>:

Set the RPll controller FORMAT ENABLE/NORMAL switch to
NORMAL, then press RETURN.

31-MaY-85 - 05:17 AM
Enabling only consolet diskst and tapes.
RSTS V9.0 (DUO) INIT V9.0-14
Start tiMesharing? <Yes>

Explanation - The disk initialization is complete. INIT.SYS now uses the COpy
option to transfer files that are required for the installation to your new system disk.
When the COpy operation is complete, INIT.SYS automatically bootstraps your
system disk, prints a message on your console terminal, and prints the Start
timesharing? question.
Table 5 lists the DSKINT error messages. If your error message does not appear
there, see Appendix A.

Prepare System

Table 5:

DSKINT Error Messages

Message and Meaning
BLOCK NUMBER TOO BIG
The block number you typed is greater than or equal to the maximum logical block number for
the disk.
DRIVE NOT READY
The initialization cannot proceed because the disk to be initialized is not on line and ready. You
can make the drive ready and press RETURN to proceed, or you can press CTRUC to abort the
initialization.
DSKINT NOT LEGAL ON SYSTEM DISK
You specified the disk from which the initialization code was bootstrapped. You cannot initialize
this disk now because the initialization code would be destroyed.
ILLEGAL DISK NAME
The string you typed is not the name of a valid RSTS/E disk device. Enter a valid name.
ILLEGAL NUMBER, TRY AGAIN
The number you typed is not a valid octal number between 1 and 177777.
SORRY, BUT THAT DISK DOESN'T EXIST
The string you typed is a valid RSTS/E disk name, but that disk controller or the unit number
does not exist on this system.

Prepare System

Go to Task 4.

Task 4: Start SYSGEN Monitor (START)
DIGITAL supplies a prebuilt HSTS/E monitor, called the SYSGEN monitor, on the
Installation tape or disk. It resides in account [0,1] with the file name SYSGEN.SIL.
The SYSGEN monitor is a temporary monitor; you use it only to build your RSTS/E
monitor. (Phase 7 describes how to shut down the SYSGEN monitor when it is no
longer needed.)
You must now decide whether you are ready to start the SYSGEN monitor. You may
need to perform some hardware-related tasks first.
You must perform a hardware-related task if you have hardware that has
nonstandard CSR addresses. If so, go to the Offline Options section, HARDWR CSR
- Declare a Nonstandard Controller Address, before you start the SYSGEN monitor.
If your installation does not require you to perform any hardware-related tasks, then
you are ready to begin Task 4 and start timesharing under the SYSGEN monitor.
The example installation is ready to start the SYSGEN monitor.

Terminal Session
This terminal session lists the INIT.SYS questions, explains
them, and gives you some possible responses. After you
understand a question, type the response at your console
terminal. In some cases, your response will differ from the
response printed in red in the example installation.

Start tiirlesharing? <Yes)

Explanation - You stopped here in .Task 3. INIT.SYS asks if you are ready to start
timesharing.
If you answer YES to this question, INIT.SYS starts timesharing under the SYSGEN
monitor.
If you answer NO to this question, INIT.SYS prints its Option: prompt. You can then
perform any necessary offline options. When you are then ready to start timesharing,
type START at the Option: prompt.

Prepare System

Response - The example installation is ready to start the SYSGEN monitor.
Therefore, the response is RETURN.
Starting SYSGEN.SIL
Rebooting
RSTS V8.0 (DUO)

INIT V8.0-1a

31-MaY-85 - 05:17 AM
Creating SWAP.SYS file with MiniMuM. size of 128 blocks
MeMOry allocation table:
OK:
GGK:
G7K:
aG2K:
512K:

00000000 - 00a07777
00al0000 - 00a13777
OOalaOOO - 03aG7777
03a70000 - 03777777
oaoooooo - End

GGK)
1 K)
385K)
50K)

E}-{EC
RTS (RS}{ )
USER
}-{BUF
N}-{M

Creating CRASH.SYS file with MiniMuM size of 320 blocks
31-MaY-85 - 05:18 AM
8 devices disabled

Explanation - INIT.SYS prints these messages as it starts the SYSGEN monitor.
The system then prints the following prompt:
DO }'OU 1",lant to perforlTI an installation or an update? <installation> m

Explanation - The system asks if you are performing a first time V9.0 installation
or are updating an existing V9.0 monitor.
Response - Type IN or press RETURN because you are installing V9. 0 for the first
time. In the example installation, the response is RETURN.
Please Mount the RSTS/E Installation Media and enter the naMe
and unit nUMber of the device.
lhllid device t}'pes are: 'MM't 'MS't 'MT't 'OM' or 'DL'
Installation device:

Go to Phase 3.

Prepare System

P;10lse
Co~¥igure ~5uS/~ Moni'i'ow

You now have a temporary monitor to use in building your RSTS/E monitor. Unlike
the SYSGEN monitor, which comes prebuilt, you must configure your RSTS/E
monitor. To configure a monitor means to select the hardware and software it will
support. You select the hardware and software by answering configuration questions.
These questions ask you what hardware (controllers, disk drives, tape drives, and so
forth) and software features (EMT logging, extended data buffering, and so forth)
your RSTS/E monitor will support.
This phase discusses the tasks you must perform to configure your RSTS/E monitor.
The tasks in this phase are:
o Task 1: Answer Preliminary Configuration Questions
o Task 2: Answer Terminal Interface Configuration Questions
o Task 3: Answer Disk Units Configuration Questions
o Task 4: Answer Peripheral Devices Configuration Questions
o Task 5: Calculate Number of Jobs

o Task 6: Answer Software Tuning and Features Configuration Questions

Each question in Phase 3 prints a default answer within brackets. If the system cannot
determine a default response, it prints ?? within the brackets. Answer the questions
based on the configuration of your system. If you are building a RSTS/E monitor for
another PDP-II, answer the questions based on the configuration of the other
PDP-I 1.
Note that you may see different default responses than the ones provided in the
example installation.
If you want to start over at any time while answering the configuration questions,
enter CTRL/Z. You return to the beginning of the task.

These responses have special meaning:
Response

Description

llim

Accept the default response

Obtain an online explanation of the question
Return to the previous question
Return to the beginning of the dialogue section
Abort the dialogue and return to the DeL $ prompt

Configure RSTS/E Monitor

Task 1: Answer Preliminary Configuration Questions
Your next task is to answer the preliminary questions asked by the the INSTAL.COM
command file. The system executes INSTAL. COM immediately after it starts the
SYSGEN monitor.
Before INSTAL. COM asks any questions, it opens a log file named INSTAL. LOG in
the account from which you are running the installation ([1,2] in the example).
INSTAL. COM closes this log file at the end of the installation. You can then print
INSTAL. LOG to obtain a record of the installation session.

Terminal Session
This terminal session lists the preliminary configuration
questions and provides some possible responses. In some
cases, your response will differ from the response shown in
red in the example installation.

Please Mount the RSTS/E Installation Media and enter the naMe
and unit nUMber of the device.
Valid device t}'pes are: 'MM', 'MS', 'MT', 'OM' or 'OL'
Installation device: MSO

Explanation - You stopped here in Phase 2. This question asks for the location of
your Installation media.
Response - Type the device name and unit number of the drive on which your
Installation media is mounted. The question lists the valid devices. In the example
installation, the response is MSO.
Restorin~

Oeletin~

r~quired

all

~lobal

_SY:[O,IJ COMPonents
SYMbols

31-MaY-85 05:21 AM
Be~innin~

of the RSTS/E Software Installation Procedure

Type '?' for help
Type ,A, to ~o bacK to the previous question
Type CTRL/Z to return to the be~innin~ of the present section

* Startin~ dialo~ue phase *
Are YOU read}' to proceed? <}'es> m

Explanation - This question asks if you are ready to continue. If you type YES or
press RETURN, the dialogue continues. If you type NO, you see the $ prompt.

Configure RSTS/E Monitor

Answer NO, for example, if you need to recover a corrupted system disk by issuing
the $RESTORE command. You resume the installation procedure by typing
PROCEED.

Response - Type YES or press RETURN to continue with the installation. In the
example installation, the response is RETURN.
Please enter the naMe and unit nUMber of the disK to
which YOU want to install the software. This disK
should be physicallY Mounted and write-enabled.

Explanation - This question is for anyone building a RSTS/E system for another
PDP-I1. Your response to this question determines the disk where the new RSTS/E
monitor and system programs will be installed.
If you specify a disk other than the system disk (SY:), physically mount and
write-enable the disk before you answer this question. The disk does not need to be
initialized at this time, because the next question asks if you want to initialize it.

Response - Type the disk name and unit number of the target disk if you are
installing RSTS/E for another PDP-I1. You then see the Do you want to initialize the
target disk? question.
Type SY or press RETURN to install RSTS/E on your present system disk, the disk
you initialized in Phase 2. In the example installation, the response is RETURN.
Restoring' required _SY:[l ,2] COIT1POnents
Assig'ning' SYsteM log'icals

** Starting' Monitor Section **
Do }'OU IAlant to install the RSTS/E ITlonitor? <}'es> ill§)

Explanation - This question asks if you want to install the monitor. Answer NO to
this question if you want to install only system programs and/or layered product
updates. You then skip the monitor installation.
If you answer YES or press RETURN to this question, you continue with the dialogue
to install a RSTS/E V9.0 monitor.
If you answer NO to this question, go to Phase 4.

Response - Type YES or press RETURN to proceed with the RSTS/E monitor
installation. In the example installation, the response is RETURN.
Restoring' required SYSGEN COMPonents

Explanation - The system now copies files that you need to continue the installation. Then you begin the monitor configuration dialogue.
Use teMPlate Monitor? <N> NO

Explanation - This question asks if you want the system to obtain information it
needs from a previous monitor. If you do have a previous V9. 0 monitor and want to

Configure RSTS/E Monitor

use information from it, type YES and then follow the steps in Phase 3, Task 2 of
Part IV. Type NO if you do not have a previous V9.0 monitor to serve as a template.
The default response to this question is NO if the SYSGEN monitor is the previous
monitor, and YES if it is not.
Response - Type NO or press RETURN, because you do not have an existing
V9.0 monitor to use as a template. In the example installation, the response is NO.
New Monitor naMe? <RSTS) RSTSSO

Explanation - This question asks for the name of your new RSTS/E monitor,
which will be stored as a save image library (SIL) in account [0,1] on your system
disk. The installation procedure performs a lookup to see if the monitor name you
specify already exists. If it already exists and it is the currently installed SIL, the
procedure returns an error message and then reprompts.
Response - Type a one- to six-character alphanumeric name for your RSTS/E
monitor. The default response is RSTS. In the example installation, the response is
RSTS90.
Supersede existing Monitor? <N)

Explanation - You see this question only if the monitor name specified already
exists and is not the currently installed SIL. If you type NO or press RETURN to
accept the default, the program returns to the New monitor name? prompt. If you
type YES, your new monitor supersedes the existing monitor.
Response - In the example installation, this question does not appear because no
previous monitor named RSTS90 exists.
Accept defaults ? (N) NO

Explanation - This question gives you the opportunity to modify the configuration
of your new SIL. If you answer NO, the installation procedure gives you the opportunity to make changes at the beginning of each specific configuration section (Tasks 2,
3,4,6).

If you answer YES, the installation procedure chooses the default configuration and
asks no configuration questions.
If you are using a template monitor, you can type a ? to list the defaults that will be
selected if you answer YES to this question.

Configure RSTS/E Monitor

Type NO to continue with the configuration questions, as in the
example installation. DIGITAL recommends that you answer NO if:

Response -

o You are performing a first time V9. 0 system installation
o You are not using a template monitor.

Type YES if you want accept the default configuration.
If you are using a template monitor, type a ? to list the defaults that will be selected if
you answer YES.

Go to Task 2.

Configure RSTS/E Monitor

Task 2: Answer Terminal Interface Configuration Questions
Your next task is to answer the terminal interface configuration questions. These
questions deal with the number and types of hardware that connect your terminals to
the PDP-11 and the software features related to these terminals. The RSTS/E monitor
supports a maximum of 128 terminals and pseudo keyboards. Therefore, the total
number of terminal interfaces and pseudo keyboards cannot exceed 128.

Terminal Session
This terminal session lists the terminal interface configuration
questions, explains them, and gives· some possible responses
(printed in red). After you understand the question, type the
response at your console terminal.
If you are generating a monitor for another PDP-11, answer
the questions based on the configuration of the target system.

Now YOU MUst specify the hardware confi~uration on which this RSTS/E SYsteM
will run.
The followin~ questions deal with the
nUMbers and types of terMinal interfaces
on the Systefrl.
Accept TerfTlinal defaults? <N)

Explanation - You see this question only if you answered NO to the Accept
defaults? question in Task 1.
If you answer YES to this question, you receive the default terminal configuration,
and skip to the disk configuration questions (Task 3). If you answer NO or press
RETURN, you see these terminal configuration questions:

DL11A compatible lines?
DL11e, DL11D's?
DL11E, DLV11E's ?
DJ11's?
DH11's?
DZ111DZV11/DZQ11's?
DHU11/DHV11's?
Pseudo keyboards ?
Multi-terminal service?
Echo control ?
One-line status report ?
FMS-11 support ?
Multiple private delimiters ?

Configure RSTS/E Monitor

Type NO or press RETURN to begin the terminal configuration
questions. In the example installation, the response is RETURN.

Response -

Or, type YES to accept the default configuration.
DLllA cOfrlPatible

lines? <01> ~

Explanation - The OL11A single-line interface is a device that allows communication between serial ASCII terminals and your POP-11. The OL11A single-line
interface can connect a terminal either directly to the PDP-II or indirectly through
leased private telephone lines. The RSTS/E monitor can support a maximum of 16
OL11A single-line interfaces.
Type the number (1 to 16) of OL11A Single-line interfaces you need to
configure. In the example installation, the default number of OL11A compatible lines
is 1; thus, the response is RETURN. You may see a different default answer on your
console terminal.
Response -

DL 11 C t DL 11 D's ?

< 00 >-

Explanation - The OL11C and OL110 are another class of Single-line interfaces
that allow communication between serial ASCII terminals and your POP-11. The
OL11C and OL110 single-line interfaces can connect a terminal either directly to the
PDP-II or indirectly through leased telephone lines. Your RSTS/E monitor can
support a maximum of 31 OL11C and OL110 single-line interfaces.
Type the number (0 to 31) of OL11C and OLI10 Single-line interfaces
you want to configure ..

Response -

In the example installation, the program prints 0 as the number of OL11C and
OL110 single-line interfaces to enable; thus, the response is RETURN. You may see
a different default answer on your console terminal.
DLllEt DL 1.J11E's ?

<00> ~

Explanation - The OLlIE Single-line interface connects terminals to the POP-11.
These terminals transfer automatic answer datasets on the dial-up telephone network.
The RSTS/E monitor can support a maximum of 31 OLlIE single-line interfaces.
Note -----------------------

You should not use OL11 type interfaces at baud rates over 2400.
Exceptions to this are VT102 and VT200-family terminals when
operated in "PACE" mode.

Type the number (0 to 31) of OLlIE single-line interfaces you need to
enable. If you configure more than 31 of any combination of OL11A, OLIIC,
OLIIO, or OLlIE Single-line interfaces, the program returns to the OL11A compatible lines? question.

Response -

Configure RSTS/E Monitor

In the example installation, the default number of OLlIE single-line interfaces is 0;
thus, the response is RETURN. You may see a different default answer on your
console terminal.

Explanation - The DJ11 multiplexer can connect 1 to 16 terminals to your
PDP-11. A RSTS/E monitor can support a maximum of 16 DJ11 multiplexers.
Response PDP-11.

Type the number (0 to 16) of DJ11 multiplexers attached to your

In the example installation, the number of DJ11 multiplexers is 0; thus, the response
is RETURN. You may see a different default answer on your console terminal.
If you type 0, you skip the next question and go to the DH11' s? question.
DJll unit xx lines enabled?

Explanation - This question appears for each DJ11 multiplexer supported by your
RSTS/E monitor. For example, if you type 3 to the previous question, this question
appears three times. (The guide shows this question only once.)
Response - Type the number (1 to 16) of lines you need to enable for this DJ11
multiplexer. DIGITAL recommends you configure the maximum number of lines, as
long as you have enough memory and you do not exceed the maximum of 128
lines. Because the example installation does not support any DJ11 multiplexers, there
is no response to this question.
DHI1's ? <00>

Explanation - The DH11 multiplexer can connect 1 to 16 terminals to your
PDP-11. A RSTS/E monitor can support a maximum of 16 DH11 multiplexers.
Response - Type the number (0 to 16) of OH11 multiplexers attached to your
PDP-11. In the example installation, the program prints 0 as the number of DH11
multiplexers to enable; thus, the response is RETURN.
If you type 0, you skip the next two questions and go to the DZ1110ZV11/DZQ11's?
question.
DHII unit xx lines enabled? <16>

Explanation - You see this question for each DH11 multiplexer supported by your
RSTS/E monitor. For example, if you typed 4 to the previous question, this questionappears four times. (The guide shows this question only once.)
Response - Type the number (1 to 16) of lines you want to enable for this DH11
multiplexer. DIGITAL recommends you configure the maximum number, as long as
you have enough memory and you do not exceed the maximum of 128 lines.
Dataset support for DH11's ? <N>

Explanation - A DH11 multiplexer can support automatic answer datasets. A
DM11-BB modem controller connects a DH11 multiplexer to an automatic answer
dataset.

Configure RSTS/E Monitor

Response- The installation procedure determines whether your machine has a
OM11-BB modem controller. If it does, the default is Y. In this case, type Y for
dataset support; type N or press RETURN for no dataset support.
DZll/DZt.lll/DZQll's ? <03>

Explanation - The OZll multiplexer can connect one to eight terminals to a
RSTS/E UNIBUS PDP-II; the OZV11 or OZQ11 multiplexer can connect one to four
terminals to a RSTS/E Q-BUS PDP-II.
Response - Type the number (0 to 16) of OZll, OZV11, or OZQ11 multiplexers
attached to your PDP-II. A RSTS/E monitor can support a maximum of 16
OZll/0ZV1110ZQ11 multiplexers.

In the example installation, the program shows that there are 3 OZll/0ZV1110ZQ11
multiplexers attached to this PDP-II; thus, the response is RETURN. You may see a
different default answer on your console terminal.
If you type 0, you skip the next two questions and go to the OHU11/0HV11' s?

question.
DZll/DZt.lll/DZQll unit xx lines enabled? <08>

Explanation - This question asks for the number of lines to enable for the OZll,
OZV11, or OZQ11 multiplexer. (Note that this question shows either OZll, DZV11,
or OZQ11, depending on the hardware on your system.) You see this question for
each OZll, DZV11, or OZQ11 multiplexer supported by your RSTS/E monitor. For
example, if you type 6 to the OZll/0ZVII/0ZQ11's? configuration question, this
question appears six times. (The guide shows this question only once.)
Response - Type the number (1 to 8 for OZll, 1 to 4 for OZV11, or 1 to 4 for
OZQ11) of lines you need to enable for this OZll, OZV11, or OZQ11 multiplexer.
DIGITAL recommends you configure the maximum as long as you have enough
memory and do not exceed the maximum of 128 lines. In the example installation,
the response is 8 to each question.
Dataset support for DZll/DZI.'ll/DZQll's ? <N>

Explanation - This question appears only if you answered the previous two
questions. (Note that this question shows either OZll, DZV11, or OZQ11, depending
on the hardware on your system.) It asks if you want to connect dial-up telephone
lines to a OZll, OZV11, or OZQ 11 multiplexer. The connection is established
through an automatic answer dataset connected to the multiplexer.

There are four models of OZlls: OZll-A and OZll-B, which support partial modem
control and, therefore, can support automatic answer datasets; and OZll-C and
OZll-0, which do not support modem control and, therefore, cannot support
automatic answer datasets.
The OZV11 and OZQ11 support partial modem control and, therefore, can support
automatic answer datasets.
i

Configure RSTS/E Monitor

Response - Type Y if you have a DZII-A, DZII-B, DZVll, or DZQll and you
want automatic answer dataset support; type N if you do not want automatic answer
dataset support, or if you have the DZII-C or DZ11-D models. In the example
installation, the response is RETURN.
DHU11/DHt.J11's ? <01>

Explanation - The DHUll multiplexer can connect 1 to 16 terminals to a RSTS/E
UNIBUS PDP-II; the DHVll multiplexer can connect 1 to 8 terminals to a RSTS/E
Q-BUS PDP-II. (Note that this question shows either DHUll or DHVll, depending
on the hardware on your system.)
Response - Type the number (0 to 16) of DHUll or DHVll multiplexers attached
to your PDP-l1. A RSTS/E monitor can support a maximum of 16 DHUIl1DHVll
multiplexers.

In the example installation, the program shows that there is 1 DHUIl1DHVll
multiplexer attached to this PDP-II; thus, the response is RETURN. You may see a
different default answer on your console terminal.
If you type 0, you skip the next two questions and go to the Pseudo keyboards?
question.
DHU11/DHt)11

unit xx

lines enabled? <18>

Explanation - This question asks for the number of lines to enable for the DHUll
or DHVll multiplexer. (Note that this question shows either DHUll or DHVll,
depending on the hardware on your system.) You see this question for each DHUll
or DHVll multiplexer supported by your RSTS/E monitor. For example, if you typed
6 to the DHUII/DHVII' s? configuration question, this question appears six times.
(The guide shows this question only once.)
Response - Type the number (1 to 16 for DHUll or 1 to 8 for DHVll) of lines
you need to enable for this DHUll or DHVll multiplexer. DIGITAL recommends
you configure the maximum as long as you have enough memory and as long as you
do not exceed the maximum of 128 lines. In the example installation, the response is
RETURN.
Dataset support

for DHU11/DHt)11's ? <N> (![f)

Explanation - This question appears only if you answered the previous two
questions. It asks if you want to connect dial-up telephone lines to a DHUll or
DHVll multiplexer. The connection is established through an automatic answer
dataset connected to the multiplexer. (Note that this question shows either DHUll or
DHVll, depending on the hardware on your system.)
Response - Type Y if you have a DHUll or DHVll and you want automatic
answer dataset support; type N if you do not want automatic answer dataset support.
In the example installation, the response is RETURN.
Pseudo keyboards? <oa> 8

Configure RSTS/E Monitor

Explanation - A pseudo keyboard is a logical device that has the characteristics of
a terminal, but has no physical terminal associated with it. Pseudo keyboards are
useful for batch and network applications. See the RSTSIE Programming Manual for
more information about pseudo keyboards. This question asks you to type the
number of pseudo keyboards supported by your RSTS/E monitor.
Response - Type the number (1 to 127) of pseudo keyboards you want on your
system. In the example installation, the response is 6.
---------------------- Note

A RSTS/E monitor permits a maximum of 128 single-line interfaces,
enabled multiplexer lines, and pseudo keyboards. (The console
terminal is always enabled.) If you configured more than 128
single-line interfaces, multiplexers, and pseudo keyboards, the
program prints an error message and returns to the DL11A compatible
lines? question.

Multi-terlylinal service? {Y>

ffiill

Explanation - The multiterminal service feature allows one program to interact
simultaneously with several terminals on one liD channel instead of opening each
terminal for input or output.
This feature is useful with applications such as order entry, inventory control,
query-response, or any other application where the same function is performed on
several terminals. It eliminates the need to run separate copies 'Of the same program
at each terminal when several terminals perform a similar function. The RSTSIE
Programming Manual explains the procedures for programming multiterminal service.
Response - Type Y or press RETURN to support this feature; type N if you do not
want to support it. In the example installation, the response is RETURN.
Echo control? {Y>

ffiill

Explanation - Echo control affects the way the terminal screen displays characters.
Normally, the terminal screen displays characters just as you type them. In echo
control mode, the monitor handles characters differently. The echo control feature lets
you use echo control mode in an application program, as described in the RSTSIE
Programming Manual.
The echo control feature is useful for data entry and other applications where you
need to define fixed-length fields for user input, accept input from only one field at a
time, define special characters for character deletion sequences within a field, and
control the appearance of terminal output.
Response - Type Y or press RETURN to enable echo control; type N if you do not
want to enable this feature. In the example installation, the response is RETURN.
One-line status

Configure RSTS/E Monitor

report? {Y>

ffiill

Explanation - This question asks if you want the ability to display a one-line status
report at your terminal by pressing CTRLff. For more information on this feature, see
the RSTSIE System User's Guide.
Response - Type Y or press RETURN if you want one-line status reports; type N if
you do not want these reports.
FMS-ll

support? <N>

Explanation - The Forms Management System (FMS-11) is a DIGITAL software
product that provides tools for developing form applications that run only on VT200
series, VT100, or VT52 terminals. If you want to develop form applications with
FMS-11, you must order the FMS-11 Software Kit separately from the RSTS/E
Distribution Kit.

This question asks if you plan to use FMS-11. If so, the RSTS/E code needed to
support FMS-11 adds approximately 2K words to the size of your resident monitor.
Response - Type Y to add the RSTS/E code required to support FMS-11; type N
or press RETURN if you do not plan to support FMS-11. If you type Y, then you can
install FMS-11, using the instructions in the FMS-ll Installation Guide. In the
example installation, the response is RETURN.
Multiple private delifrliters ? <N>

Explanation - A delimiter is a character that separates and organizes elements of
data. A private delimiter is a delimiter used within a program. You can define a letter,
a function key such as DELETE, a control character such as CTRL/Z, or even a
standard delimiter such as LINE FEED as a private delimiter. A private delimiter is
useful on a data entry terminal with a specialized keyboard. You can use a large or
conveniently located key as the private delimiter. Private delimiters are also useful in
keypad applications.

All RSTS/E monitors support the use of one private deli1J1iter in a program. Answer Y
to this question to include support for multiple private delimiters. You can declare up
to 256 multiple private delimiters in a single program by answering Y to this question
and a maximum of 1 by answering NO. Multiple private delimiters allow you to do
special character processing without using .single character I/O strokes. For example,
by combining escape sequences with multiple private delimiters, you can define your
own function keys in keypad applications. Note that you cannot declare multiple
private delimiters in BASIC-PLUS.
For more information on this feature see the RSTSIE Programming Manual and the

RSTSIE System Directives Manual.
Response - Type Y if you want your RSTS/E monitor to support multiple private
delimiters; type N or press RETURN if you do not want your RSTS/E monitor to
support them. In the example installation, the response is RETURN.

Go to Task 3.

Configure RSTS/E Monitor

Task 3: Answer Disk Units Configuration Questions
Your next task is to answer the disk units configuration questions. These questions
deal with the number and types of disk drives supported by your RSTS/E monitor.

Terminal Session
This terminal session lists the disk units configuration
questions, explains them, and gives some possible responses
(printed in red). After you understand the question, type the
response at your console terminal.
If you are generating a monitor for another PDP-II, answer
the questions based on the configuration of the target system.

The followins questions deal with the
nUMbers and Kinds of disK units on this
s}'sterrl.
Accept Dis~\ defaults? <N> m

Explanation - You see this question only if you answered NO to the Accept
defaults? question in Task l.
If you answer YES to this question, you receive the default disk configuration, and
skip to the peripheral device configuration questions (Task 4). If you answer NO or
press RETURN, you see these disk configuration questions:
RK05's?
RLOI/RL02's ?
RK06/RKOTs ?
RP02/RP03's?
Number of disks on DR controller?
Number of disks on DB controller?
MSCP controllers ?

Response - Answer NO or press RETURN to see the disk configuration questions.
In the example installation, the response is RETURN.
RK05's ? <00> m

Explanation - The RK05 disk system consists of an RKII controller and from one
to eight RK05 mOving-head cartridge disk drives. The RK05F counts as two units.
Note that the program always prints a default of 0 or 8, unless you are using a
template monitor. If you use a template monitor, the default is the actual number of
units that the template monitor is configured to support.

Configure RSTS/E Monitor

Response - Type the number (0 to 8) of RK05 disk drives that your RSTS/E
monitor supports. In the example installation, the default answer indicates that there
are none of these drives; thus, the response is RETURN.
If you type 1 or 0, you skip the next question and go to the RLOllRL02's? question.
Overlapped seeK? <V>

Explanation - The overlapped seek driver is software that increases the efficiency
of RK05 disk I/O at the expense of some memory.
Response - Type Y or press RETURN to use the overlapped seek driver; type N to
use the non-overlapped seek driver. DIGITAL recommends you type N to this
question if you have a single RK05F disk and no RK05 disks. Overlapping cannot
occur on the RK05F disk. Because the example installation does not have any RK05
disk drives, there is no response to this question.
RL01/RL02's ? <00> ®]

Explanation - The RL01/RL02 disk system consists of an RL11 controller and any
combination of up to four RL01 and RL02 disk drives.
Response - Type the number (0 to 4) of RL01 and RL02 disk drives that your
RSTS/E monitor supports. In the example installation, the program indicates that
there are none of these drives; thus, the response is RETURN.
If you type 0 or 1, you skip the next question and go to the RK06/RKOTs? question.
Overlapped seeK? <V>

Explanation - The overlapped seek driver increases the efficiency of RLOllRL02
disk 1/0, at the expense of some memory.
Response - Type Y or press RETURN to use the overlapped seek driver; type N to
use the non-overlapped seek driver. DIGITAL recommends you choose the
overlapped seek driver if you have more than one RL01/RL02 disk drive.
RKOG/RK07's ? <02) ®]

Explanation - The RK06/RK07 disk system consists of an RK611 or RK711
controller and any combination of up to eight RK06 and RK07 disk drives.
Response - Type the number (0 to 8) of RK06 and RK07 disk drives that your
RSTS/E monitor supports. In the example installation, the program indicates that
there are two of these drives; thus, the response is RETURN.
If you type 0 or 1, you skip the next question and go to the RP02/RP03? question.
Overlapped see~~? <v> ®]

Explanation - The overlapped seek driver increases. the efficiency of RK06/RK07
disk input/output at the expense of some memory.

Configure RSTS/E Monitor

Response - Type Y or press RETURN to use the overlapped seek driver; type N to
use the non-overlapped seek driver. DIGITAL recommends you choose the
overlapped seek driver if you have more than one drive. In the example installation,
the response is RETURN.
RPOZ/RP03's ? <00>

Explanation - The RP02/RP03 disk system consists of an RP11 controller and any
combination of up to eight RP02 and RP03 disk drives.

Note that the program always prints a default of 0 or 8, unless you are using a
template monitor. If you use a template monitor, the default is the actual number of
units that the template monitor is configured to support.
Response - Type the number (0 to 8) of RP02 and RP03 disk drives supported by
your RSTS/E monitor. In the example installation, the program indicates that there
are none of these drives; thus, the response is RETURN.
If you type 0 or 1, you skip the next question and go to the Number of disks on DR
controller? question.
Overlapped seeK? <V>

Explanation - The overlapped seek driver increases the efficiency of RP02/RP03
disk input/output at the expense of some memory.
Response - Type Y or press RETURN if you want your RSTS/E monitor to use the
overlapped seek driver; type N if you want your RSTS/E monitor to use the
non-overlapped seek driver. DIGITAL recommends you choose the overlapped seek
driver if you have more than one RP02/RP03 drive. Because the example installation
has no RP02/RP03 disk drives, there is no response to this question.
NUITlber of

dis~~s

on DR controller? <00>

Explanation - The RH70 controller supports any combination of up to eight
RM02, RM03, RM05, RM80, RP04, RP05, and RP06 disk drives. The RH11
controller supports any combination of up to eight RM02, RP04, RP05, and RP06
disk drives. This question asks you to type the number of RM02/RM03/RM05/RM80
and RP04/RP05/RP06 drives your RSTS/E monitor supports on this controller.
(RSTS/E supports a maximum of two disk RH70/RH11 controllers.) See Appendix F
for more information on mixing RM and RP type disks on the same controller.
Response - Type the number (0 to 8) of RM02/RM03/RM05/RM80 and
RP04/RP05/RP06 disk drives that your RSTS/E monitor supports on this controller.
In the example installation, the program indicates that there are none of these drives;
thus, the response is RETURN.
If you type 0 or 1, you skip the next question and go to the Number of disks on DB
controller? question.
.
Overlapped seeK? <V>

Explanation - The overlapped seek driver increases the efficiency of
RM02/RM03/RM05/RM80 and RP04/RP05/RP06 disk input/output, at the expense of
some memory.

Configure RSTS/E Monitor

In addition, answering YES to this question allows those disks to be accessed in
"dual-port" mode. When two systems are connected to these disks, they can be
accessed read-only by both systems at the same time.
Response - Type Y or press RETURN to use the overlapped seek driver; type N to
use the non-overlapped seek driver. DIGITAL recommends you choose the
overlapped seek driver if you have more than one RM02/RM03/RM05/RM80 and
RP04/RP05/RP06 disk drive. In the example installation there is no response because
there are none of these drives.
NUITlber of dis~\s on DB controller? <00> @

Explanation - The RH70 controller supports any combination of up to eight RP04,
RP05, RP06, RM02, RM03, RM05, and RM80 disk drives. The RHll controller
supports any combination of up to eight RP04, RP05, RP06, and RM02 disk drives.
This question asks you to type the number of RP04/RP05/RP06 and
RM02/RM03/RM05/RM80 drives your RSTS/E monitor supports on this controller.
(RSTS/E supports a maximum of two disk RH70/RHl1 controllers.) See Appendix F
for more information on mixing RP and RM type disks on the same controller.
Response - Type the number (0 to 8) of RP04/RP05/RP06 and
RM02/RM03/RM05/RM80 disk drives that your RSTS/E monitor supports on this
controller. In the example installation, the program indicates that there are none of
these drives; thus, the response is RETURN.
If you type 0 or 1, you skip the next question and go to the MSCP controllers?
question.
Overlapped seeK? <V>

Explanation - The overlapped seek driver increases the efficiency of
RP04/RP05/RP06 and RM02/RM03/RM05/RM80 disk input/output at the expense of
some memory.

In addition, answering YES to this question allows those disks to be accessed in
"dual-port" mode. When two systems are connected to these disks, they can be
accessed read-only by both systems at the same time.
Response - Type Y to support the overlapped seek driver; type N to support the
non-overlapped seek driver. DIGITAL recommends you choose the overlapped seek
driver if you have more than one RP04/RPOS/RP06 and RM02/RM03/RM05/RM80
drive. Because the example installation has none of these disk drives, there is no
response to this question.

Configure RSTS/E_ Monitor

MSCP controllers? <01)

Explanation - This question asks you to type the number of MSCP class controllers that your RSTS/E monitor supports. The MSCP controller is made up of the
UDA50, RC25, RQDXl, and RUX50 controllers. The UDA50 controller controls a
maximum of four RA60, RA80, and RA81 disk drives. The RC25 controller controls
a maximum of two RC25 drives (for 4 units). The RQDXl controller controls a
maximum of either two RD51 or two RD52 (or one of each), plus two RX50 disk
drives. The RUX50 controller supports a maximum of four RX50 drives.
Response - Type the number (0 to 2) of MSCP controllers that your RSTS/E
monitor supports. Remember, this question asks for the number of MSCP controllers,
not the total number of disks. In the example installation, the program indicates there
is one MSCP class controller; thus, the response is RETURN.

Go to Task 4.

Configure RSTS/E Monitor

Task 4: Answer Peripheral Devices Configuration Questions
Your next task is to answer the peripheral devices configuration questions. These
questions deal with the number and types of tape drives, printers, and card readers
that your RSTS/E monitor supports. There are also questions related to DECnetlE,
RJ2780, 3271, and 2780/3780.

Terminal Session
This terminal session lists the peripheral devices configuration
questions, explains them, and gives some possible responses
(printed in red). After you understand the question, type the
response at your console terminal.
If you are generating a monitor for another PDP-II, answer
the questions based on the configuration of the target system.

The following questions deal wi~h the
peripheral devices attached to this
RSTS/E systelTl.
Accept Peripheral defaults? <N) ffiTI)

Explanation - You see this question only if you answered NO to the Accept
defaults? question in Task 1.
If you answer YES to this question, you receive the default peripheral devices
configuration, and skip to the software tuning and features configuration questions
(Task 6). If you answer NO or press RETURN, you see these peripheral devices
configuration questions:

TU16ITE16ITU45ITU77's ?
TUlOITElOITS03's ?
TSlllTK25ITSV05ITU80's?
DECtapes?
Printers?
RXOl/RX02's ?
CRll/CMll card reader?
CD 11 card reader?
P. T. reader/punch ?
DEC net network support ?
DMCll's/DMRll's?
KMCll's?
Extended buffering for LP ?
RJ2780 support ?

Response - Type NO or press RETURN to see the peripheral configuration
questions. In the example installation, the response is RETURN.
TU16/TE16/TU45/TU77's ? <00) ®]

Configure RSTS/E Monitor

Explanation - The TU16rrE16rrU45rrU77 magnetic tape system consists of an
RH11 or RH70 massbus interface, a TM02 or TM03 controller, and a maximum of
eight TU16, TE16, TU45, or four TU77 magnetic tape drives.

<00> (@)

Explanation - The TU10rrE10rrS03 magnetic tape system consists of a TM11,
TMA11, or TMB11 magnetic tape controller and a maximum of eight TU10, TE10,
or TS03 magnetic tape drives.

Note that the program always prints a default of 0 or 8, unless you are using a
template monitor. If you use a template monitor, the default is the actual number of
units that the template monitor is configured to support.
Response -Type the number (0 to 8) of these tape drives that your RSTS/E
monitor supports. In the example installation, the response is RETURN.
TS11/TK25/TSI.J05/TUBO / s ? <01> (@)

Explanation - The TS 11 magnetic tape system consists of a TS 11 controller and
one TS11, TK25, TSV05, or TU80 magnetic tape drive.
Response - Type the number (0 to 4) of TS11, TK25, TSV05, or TU80 tape
drives supported by your RSTS/E monitor. In the example installation, the response is
RETURN to accept the default of 1.
DECtapes ? <00> (@)

Explanation - The DECtape system consists of a TC11 controller, a maximum of
eight DEC single-tape drives and/or a maximum of four TU56 DEC dual-tape drives.
(Note that these are dual drives; thus, if you have four TU56 units you actually have
eight drives.) This question asks for the number of DECtape drives (counting each
TU56 unit as two drives) your RSTS/E monitor will support.

Explanation - A RSTS/E monitor can support a maximum of eight LP11, LA11,
or LPV11 printers.
Response - Type the number of LP11, LA11, or LPV11 line printers (0 to 8) that
your RSTS/E monitor supports. In the example installation, the response is RETURN

Configure RSTS/E Monitor

to accept the default of 1. (Note that the LP11 line printer includes the LP25, LP26,
LP27, and so forth.)
RH01/RH02's ? <00>

Explanation - The RX11 or RX211 flexible diskette system consists of an interface
and an RX01 single-density or RX02 double-density flexible diskette subsystem. The
RXV11 flexible diskette system consists of an interface and an RX01 single-density
subsystem. The RX01 and RX02 flexible diskette subsystems each consist of a disk
controller and two flexible diskette drives. The RSTS/E monitor supports a maximum
of four RX11 or RX211 flexible diskette systems, for a maximum of eight RX01 or
RX02 flexible diskette drives.

Note that the program always prints a default of 0 or 8, unless you are using a
template monitor. If you use a template monitor, the default is the actual number of
units that the template monitor is configured to support.
Response - Type the number (0 to 8) of RX01 or RX02 flexible diskette drives that
your RSTS/E monitor supports. The example installation has none of these drives;
thus, the response is RETURN.
CRll/CMll

card

reader? <N>

Explanation - This question asks if your RSTS/E monitor supports the CR11
punched card reader or the CM11 marked card reader.
Response - Type Y if your RSTS/E monitor supports either of these devices; type
N if it does not support either of these devices. In the example installation, the
response is RETURN.
COli

card

reader? <N>

Explanation - This question asks if your RSTS/E monitor supports the COlI
high-speed punched card reader.
Response - Type Y if your RSTS/E monitor supports this device; type N if your
RSTS/E monitor does not support this device. In the example installation, the
response is RETURN.
Card decode?

Explanation - This question appears only if you answered Y to the CR111CM11
card reader? or the CD 11 card reader? questions. The RSTS/E monitor interprets
cards through the use of an ANSI standard card decoder. However, it is possible that
your installation uses some other card decoder. This question asks you to type the
card decoder you want your RSTS/E monitor to support. See' the RSTSIE Programming Manual for more information on the card codes.

Configure RSTS/E Monitor

Response - In the example installation, there is no response because N was the
response to the previous card reader questions. Possible responses are:

• ANSI
• 029 for cards punched in DEC 029
• 026 for cards punched in DEC 026
• 1401 for cards punched in IBM 1401
P.T.

reader/punch? <N> ru

Explanation - This question asks if your RSTS/E monitor supports the high-speed
paper tape reader and the high-speed paper tape punch.
Response - Type Y if your RSTS/E monitor supports these devices; type N if your
RSTS/E monitor does not support these devices. In the example installation, the
response is RETURN.
DECnet networK support? <V> N

Explanation - DECnetiE is a DIGITAL software product that lets you communicate
with two or more DIGITAL computer systems. If you want the features provided by
DECnetlE, you must order the DECnetiE software kit separately from the RSTS/E
Distribution Kit. This question asks if you want to add the code needed to support
DECnetiE. The DECnetiE documentation set describes the concepts and capabilities
of DECnetiE. Before you install DECnetlE, consult the DECnetlE Network Installation

Guide.
Note ----------------------

DECnetiE requires data caching. Therefore, if you answer YES to the
DECnet question, you also automatically enable data caching on your
system. DUring Task 6 you see an informational message instead of
the Data Caching? question.

Response - Type Y to add the code needed to support DECnetlE; type N if you
do not plan to use DECnetiE. If you type Y, then you will be asked to mount the
tape or disk that contains the DECnetiE software in Phase 5. The example installation
does not plan to install DECnet. Therefore, the response is N.
DMCll's/DMRll's ? <00> ru

Explanation - The DMC11 and DMR11 network links are synchronous communication line interfaces that implement the DDCMP line protocol in the hardware. These
interfaces are used primarily with DECnetiE but can be used without it.

Configure RSTS/E Monitor

Response - Type the number (0 to 16) of DMCll or DMRll network links
attached to your PDP-II. Because the example installation does not plan to use
DECnetJE or the DMC's by themselves, the response is RETURN.
OMI.lll's/OMPll's ?

Explanation - You see this question only if you typed Y to the DECnet network
support? question. (Note that this question shows either DMVl1 or DMPl1, depending on the hardware on your system.) The DMVll and DMPll network links are
synchronous communication line interfaces that implement the DDCMP line protocol
in the hardware. The DMVll and DMPll links can be used only by DECnet. This
question asks for the number of DMVll or DMPl1 network links attached to your
PDP-II.
Response - Type the number (0 to 16) of DMVll or DMPl1 network links
attached to your PDP-II. If you type 0, you go to the KMCll's? configuration
question. Because the example installation does not use DECnetJE, there is no
response to this question.
OMVll/0MPll unit xx tributaries?

Explanation - This question asks for the number of tributaries you will activate at
one time. The program prints this question for each DMVI1/DMPl1 supported by
your RSTS/E monitor. For example, if you type 5 to the DMVI1/DMPl1' s? question,
this question appears five times. (The guide shows this question only once.) The
question refers to either DMVll or DMPll, depending on the hardware on your
system.

The program repeats the DMVll's/DMPll's? configuration 'question if you specified
more than 128 tributaries. See the DECnetlE Installation Guide and DECnetlE
Release Notes for information on this question.
Response - Type the number (1 to 12) for the DMVll, or type the number (1 to
32) for the DMPII. Because the example installation does not use either of these line
interfaces, there is no response to this question.
KMCll's ? <00> ffiffi

Explanation - The KMC-l1 is a microprocessor that attaches to the UNIBUS of a
PDP-II. The KMC-l1 runs asynchronously with the PDP-II. When loaded with the
appropriate microcodes, the KMC-ll controls the 3271 or 2780/3780 IBM protocol
emulators.
Response - Type the number (0 to 16) of KMC-ll microprocessors attached to
your PDP-II. In the example installation, the response is RETURN.
If you type 0, you skip the next two questions and go to the Extended buffering for
LP? question.
KMC IBM protocol support?

Explanation - The KMC-l1 microprocessor can emulate different IBM protocols.
For example, the KMC-l1 can handle IBM 3271 protocol emulation. This reduces
PDP-II central processor overhead because the KMC-l1 eliminates almost all binary

Configure RSTS/E Monitor

synchronous communication character interrupts. and protocol processing. IBM
protocol emulator products (the 3271 and high performance 2780/3780) use the
extended buffer pool rather than small buffers.
Response - Type Y to add this support; type N if you do not want to add this
support. If you type N, you see the Extended buffering for LP?· question. Because the
example installation does not support KMC-lls, there is no response to this question.
3271 or 2780/3780 siMultaneous linKs?

Explanation - Each KMC-ll microprocessor controls one DUPll synchronous line
interface to the 3271 or 2780/3780 host. The 3271 is a terminal; the 2780/3780 is a
remote batch job entry device. An IBM host connected to a RSTS/E computer system
can communicate with these devices as though they were actually present because
the RSTS/E monitor emulates them. This question asks for the number of 3271 or
2780/3780 simultaneous links you want.
Response - Type the number (0 to 16) of KMC-1113271 or' KMC-1112780/3780
simultaneous links you want attached to your PDP-II. Because the example
installation does not support KMC-lls, there is no response to this question.
Extended bufferin!1 for LP ? <Y>

Explanation - The extended buffer pool (XBUF) is an area of memory reserved
for data. This question appears only if you type 1 or more in response to the Printers? peripheral devices configuration question. It asks if you want to use the extended
buffer pool instead of the small buffer pool to store character output from the line
printer.
Each line printer driver uses a maximum of 2.SK words of XBUF while it is running.
In addition, the driver is about 70 words longer if you choose this feature.
This feature improves line printer performance and reduces line printer impact on the
small buffer pool; therefore, it is more useful for large systems.
Response - Type Y if you want to use XBUF to store character output from the
line printer; type N if you do not want to use XBUF. In the example installation, the
response is RETURN.
RJ2780 support? <N>

Explanation - The RJ2780 Emulator Package is a DIGITAL software product that
emulates the IBM RJ2780 Model 1 data transmission terminal. This software lets a
RSTS/E monitor communicate with any IBM computer that supports your terminal, or
with another DIGITAL computer running the RJ2780 terminal emulator package.
Transmission of data can originate from a card reader or disk files. Received data can
be directed to a line printer or disk files. All data is transmitted in EBCDIC or binary
code, and communication is supported over synchronous, point-to-point contention
mode only, at up to 4800 baud. This package also supports a spooling operation that
allows RSTS/E users to queue files for transmission.

Configure RSTS/E Monitor

If you want to support the RJ2780, you must order the RJ2780 software kit
separately from the RSTS/E Distribution Kit. For more information on this software
package, see the RSTSI2780 User's Guide. In Phase 5, the system will tell you when
to mount the tape or disk that contains the RJ2780 software.

Type Y to add the code needed by the RSTS/E monitor to support
this optional software; type N if you do not want to add this optional software. In the
example installation, the response is RETURN.
Response -

Go to Task 5.

Configure RSTS/E Monitor

Task 5: Calculate Number of Jobs
This task helps you calculate the maximum number of jobs your system needs. You
need to know the number of jobs in order to answer the Maximum jobs? question in
Task6 of this phase. There is no terminal session in this task, only a preparation
session.

Preparation Session
The RSTS/E monitor assigns jobs to keep track of all user
activities.

To calculate the maximum number of jobs your system needs, add the following:
• Number of physical terminals you have or plan to have.
• Number of pseudo keyboards you need. A pseudo keyboard is a logical device
that has the characteristics of a terminal, but has no physical terminal associated
with it.
• One detached job for ERRCPY, the error logger program that reads
error-related information stored in the monitor area of memory. A detached job
is a job that is not associated with a terminal. See the RSTSIE System
Manager's Guide for information on ERRCPY.
o Number of detached jobs for printlbatch requests. For the Print/Batch Services

(PBS) package, allow one detached job for each copy of the PRINT and
BATCH server programs. For the OPSER-based spooling package, allow two
detached jobs plus one job for each line printer and batch server. See the
RSTSIE System Manager's Guide for more information on these programs.
• Two to five jobs if your installation uses dial-up terminals. These terminals may
become detached as a result of a faulty phone connection. See the RSTSIE
System Manager's Guide for more information.
• A number of detached jobs for optional software like DECWORD/DP and
DECnet/E. See the appropriate installation gUide for more information on job
requirements.

Configure RSTS/E Monitor

The example installation calculates a total of 40 jobs:
o Terminals - 30
o Pseudo keyboards - ·6

o System programs - 4 (1 for Print/Batch Services requests; 3 for OPSER

requests).
Figure 2 provides a job calculation worksheet to allow you to write the number of
jobs needed by your installation. The maximum number of jobs allowed by the
RSTS/E monitor is 63.

How many terminals do you plan to support?
How many pseudo keyboards does your software require at any
one time?
How many detached jobs do you need for ERRCPY, Print/Batch
Services (PBS), and/or the OPSER-based spooling package?
How many jobs do you need to accommodate detached dial-up
jobs?
.
How many detached jobs do you need for optional software?

Total # of jobs

Figure 2:

Job Calculation Worksheet

MK·01092·01

Go to Task 6.

Configure RSTS/E Monitor

Task 6: Answer Software Tuning and Features Configuration Questions
Your next task is to answer the software tuning and features configuration questions.
These questions deal with RSTS/E monitor software features, such as maximum
number of jobs, small buffers, data caching, and so forth.

Terminal Session
This terminal session lists the software tuning and features
configuration questions, explains them, and gives you some
possible responses (printed in red). After you understand the
question, type the response at your console terminal.
If you are generating a monitor for another PDP-II, answer
the questions based on the configuration of the target system.

The following ~uestions deal with the
capacity and features of this RSTS/E
SYsteM provided at the SYsteM Manager's
option.
Accept Softl,.Iare defaults? <N>

Explanation - You see this question only if you answered NO to the Accept
defaults? question in Task 1.
If you answer YES to this question, you receive the software tuning and features
defaults, and skip to the Proceed? prompt at the beginning of Phase 4. If you answer
NO or press RETURN, you see these software tuning and features configuration
questions:

Maximum jobs?
Small buffers ?
Monitor statistics ?
EMT logging?
Data Caching?
Response - Answer NO or press RETURN to see the software tuning and features
configuration questions. In the example installation, the response is RETURN.
MaxiMuM Jobs? <25>

Explanation - In Task 5 you used the Job Calculation Worksheet to calculate the
number of jobs your RSTS/E monitor supports. Once you establish the maximum
number of jobs, you cannot increase the number unless you perform another system
installation. However, you can decrease the number you enter here online during
timesharing by using the SET LOG INS command (see the RSTSIE System Manager's
Guide).

Configure RSTS/E Monitor

Response - Check your Job Calculation Worksheet (Task 5, Figure 2) and enter
the maximum number of jobs (2 to 63) your RSTS/E monitor supports. In the
example installation, the response is 40.
SMall buffers? <aaO) 550

Explanation - A small buffer is a 16-word storage area located in the monitor area
of memory. There are two types of small buffers: general small buffers and FIP small
buffers. You allocate the minimum number of general small buffers now by answering
this question. Note that the installation procedure automatically calculates a recommended number of general small buffers you need for your installation. In the
example installation, the installation procedure calculates a total of 440 general small
buffers.

Your default may differ from the default in the example installation. Your installation
may also need more than the number printed in the default. A more detailed
explanation of how to add general and FIP small buffers is provided in the BUFFERS
sub option of the DEFAULT option, located in the Offline Options section of this
guide.
Response - Press RETURN to accept the default. In the example installation, the
response is 550.

Or, type the number of small buffers (1-999) you want on your system. In general, a
response within the range of 600 small buffers is acceptable for most systems.
----------------------- Note -----------------------

If the number of small buffers you specify is too high for your system,
the command procedure may lower the number when it creates your
new monitor (see Task 2 of Phase 5).
If you specify many more buffers than can fit on your system, the
command procedure asks the configuration questions again before it
creates your new monitor.

Monitor statistics? <N)

Explanation - Monitor statistics is a software feature that provides tables that
record job, disk, and directory (or data) cache statistics. DIGITAL does not provide
support for this feature unless you have it in a DIGITAL Software Services Consultation contract. The type of data accumulated and the way the data is accessed may
change in future releases.
Response - Type Y if you want this feature; type N if you do not want this feature.
In the example installation, the response is RETURN.
EMT logging? <N) m

Explanation - EMT logging is a feature that allows you to pass information on
selected monitor directives by means of send/receive to a program that you write after

Configure RSTS/E Monitor

you build your monitor. Your program can then make use of these monitor
directives to log selected kinds of system activity. See the RSTSIE System Manager's
Guide for more information on EMT logging.
Type Y if you want your monitor to support EMT logging, in which
case you will have to write a program (the UNSUPP system program package
contains a demonstration program); type N if you do not want this support. In the
example installation, the response is RETURN, which accepts the default of NO.

Response -

Data Caching? (N) Y

Explanation - Extended data buffering (more frequently called data caching) is a
software feature that reduces the number of data transfers from disk to memory,
thereby improving response time. This improved response time makes data caching
useful for speeding up read operations. See the RSTSIE System Manager's Guide for
more information on data caching.
Data caching uses only extended buffers, unlike directory caching, which uses both
extended buffers and small buffers. (Directory caching is automatically installed on
V9.0 systems.)
You do not see the Data Caching? question if you answered YES to DECnetlE in
Task 4. Since DECnetlE requires data caching, the installation procedure
automatically enables the feature. Instead, you see the message:
Data caching is

alw~Ys

enabled with DECnet/E

DIGITAL recommends you type N if your PDP-II has 128K words of
memory or less, because you cannot afford to allocate enough memory to the
extended buffer pool to make data caching effective. Type Y if you have enough
memory. In the example installation, the PDP-ll144 has 512K words of memory;
thus, the response is Y.

Response -

Restoring DECnet/E update COMPonents
Use RMS resident libraries in NFT and FAL? (yes)

Explanation - You see this question only if you answered Yes to the DECnet
network support? question in Task 4. The resident library versions of the NFT and
FAL DECnetiE utilities use the RMS resident library. The overlaid versions of NFT
and FAL use disk overlays. The resident library version executes faster than the disk
overlay version but requires more memory.
Type YES or press RETURN to receive the resident library versions of
NFT and FAL. Type NO to receive the overlaid versions. Because the example
installation does not use DECnetlE, there is no response to this question.

Response -

* * End of Monitor Section * *

Go to Phase 4.

Configure RSTS/E Monitor

Pho]se
Selec'{ RSlS/rE Sys'~ern ProgrO]MS

Now that you have finished answering the configuration questions, you are ready to
perform the second part of configuring your RSTS/E system. In this phase, you
specify which system programs to install on your system.
The tasks in this phase are:
o Task 1: Answer System Program Installation Questions
o Task 2: Answer Layered Product-Related Questions

These responses have special meaning:

Response

Description

Accept the default response

Obtain an online explanation of the question
Return to the previous question
Return to the beginning of a dialogue section

Task 1: Answer System Program Installation Questions
Your next task is to answer the system program installation questions.
System programs provide you with tools for performing common tasks during

timesharing. For example, system programs allow you to efficiently develop programs,
manage files, and perform special system management-related tasks.
DIGITAL supplies RSTS/E system programs on the V9 Library media. The programs
are grouped into the packages listed in Table 6. See Appendix C for a complete list
of system programs contained in each package as well as package sizes.
Table 6:

System Program Packages
Description

Package
System Library

The standard system library. You automatically receive this package.

RSX Utilities

Programs that allow you to use RSX from a programming environment, or use
the DCl LINK command from any language.

Help

Programs that display online help text.

Error

Programs that detect, log, and display errors, as well as perform crash analysis.
You automatically receive this package.

Update

Programs you may need when installing optional software. This package
contains the BUILD program. If you plan to install any layered products, you
should select this package.

Device Testing

The Device Testing Package. See the RSTSIE System Manager's Guide for
more information.

Print/Batch Services
(PBS)

The RSTS/E V9.0 Print/Batch Services package. See the RSTSIE System
Manager's Guide for more information.

File Restore

The pre-V9.0 BACKUP package. See the RSTSIE Utilities Reference Manual
for more information.

OPSER-based
Spooling
Unsupported Utility

The pre-V9.0 OPSER-based spooling package. See the RSTSIE System

Manager's Guide for more information.
Utility programs that are unsupported by DIGITAL. See the RSTSIE Release

Notes for more information.
Auxiliary Library

System programs and data files used with certain peripheral devices and
optional software.
(continued on next page)

Select RSTS/E System Programs

Table 6:

System Program Packages (Cont.)

Package
RMS-ll

Description
A set of routines that allows your programs to gain access to and process (add,
modify, and delete) records and files. For information about RMS-II, see the
following manuals:

• RSTS/E RMS-ll: An Introduction and the RSTS/E RMS-ll User's Guide
provide introductory and user information (MACRO-II and high-level
language programmer).

• RSTS/E RMS-ll Macro Programmer's Guide contains reference
information on the RMS-ll operation routines for MACRO-II
programmers.

• RSTS/E RMS-ll Utilities manual provides usage and reference
information on the RMS-II utility programs.
RMS DAP

RMS DECnet Access Package, a set of routines that provides DECnet support
for RMS-I1. See the RSTS/E RMS-ll User's Guide and the RSTS/E Release
Notes for more information.

EDT

A text editor that provides line and character editing, screen editing, and
journaling capabilities. See the Introduction to the EDT Editor and the EDT
Editor Manual for more information.

TECO

TECO (Text Editor and COrrector), a text editing program that you can use to
edit any form of ASCII text. DIGITAL does not support TECO. See the
PDP-ll TECO User's Guide for more information.

SORT/MERGE

SORT/MERGE V3.0, a set of routines that allows you to read an input file, sort
it, and write the data to an output file. See the PDP-ll SORT/MERGE User's
Guide for more information. (You answer the SORT/MERGE configuration
questions in Task 5B of Phase 5.)

BASIC-PLUS

BASIC-PLUS, a BASIC interpreter that lets you perform interactive BASIC
programming and also gives you access to system programming features such
as system function calls and block I/O. See the BASIC-PLUS Language Manual
for more information. (You answer the BASIC-PLUS configuration questions in
Task 5A of Phase 5.)

Note that the System Library and Error packages are automatically installed on your
V9.0 system.

Select RSTS/E System Programs

Terminal Session
This terminal session explains the system program installation
dialogue and provides some possible responses. In some
cases, your response will differ from the response shown in
red in the example installation.

** Startin~ SYsteM Pro~raMs Section **
Do )'OU

Jant to install the S)'sterll Pro~rarTl pad\a~es? ()'es>

1••

Explanation - You are at the beginning of the System Programs Section. If you
answer YES, you begin the dialogue to install system programs.
Answer NO if you are only creating a RSTS/E monitor and do not want to install
system programs. You then skip this phase and go to the Are you ready to proceed?
question in Task 1 of Phase 5.

Response - Type YES or press RETURN to begin the dialogue. In the example
installation, the response is RETURN.
PacKa~es

to install: ?

Explanation - This question asks for the names of the packages you want to install
on your system.
Response - Type a question mark to list the packages that are available.
The valid responses are:
DIALOGUE
ALL
ALL ,Nop~\~[, ••• ]

Switches YOU to the lon~ forM of the SYsteM
Software PacKa~es dialo~ue where a More
detailed description of each pacKa~e is provided
Selects all pacKaSes
Selects all pacKases except pK~

Use a COMMa as a separator.
Pac~\a~e

EDT
HELP
oPSER
PBS
RESTORE

RSX,PBS,RMS

narTles:

AU}'{L I B
BASIC
DAP

PacKa~es

e.~.:

Auxilian' Libran'
Basic-Plus
RMS DECnet Data Access
<includes RMS-ll)
EDT Editor
Help PacKa~e
opser-based Spooler
Print/Batch Services
File Restore

RMS
Pad\a~e

RS}{
SORT
TECo
TEST
UNSUPP
UPDATE

to install: ALL,NoDAP,NoUNSUPP,NOSoRT

Select RSTS/E System Programs

RMS-ll
<includes RS}{ Utilities)
RS}{ Utilities
Sort/Mer~e

<includes RMS-ll)
TECo Editor
De\,!ice Testin~
Unsupported Utilities
Update Pac~\a~e

Explanation - After you type a ?, you see the list of available system program
packages. Then the system reprompts for the packages to install. Note that the RMS,
DAP, and SORT packages need other packages to work properly. If you specify any
of these packages, you automatically receive the associated package.
Response - If you know what packages you want to install, type a list of the
package names, separated by commas. Remember, if you make a mistake you can
type ,.. to return to the previous question, or enter CTRL/Z to return to the beginning
of the section.
If you want more information before deciding whether to install a package, type
DIALOGUE to see the long form of the dialogue.

Type ALL to install all the packages. If you plan to install nearly all of the packages,
type:
ALL,NOnnnnnn,NOnnnnnn
where nnnnnn refers to a package you want to exclude.
In the example installation, the response is ALL,NODAP,NOUNSUPP,NOSORT.
The following will be installed:
RS}-{
RMS
PBS
EDT
UPDATE
TEST
TECO
AW-{L I B
RESTORE
OPSER
HELP
BASIC
Proceed?

(}'es>

Explanation - The system lists the packages it will install and prompts you to
proceed. If you answer NO to this question, you return to the Packages to install:
prompt.
Response - Type YES or press RETURN to continue with the installation. Or, type
NO if you want to change the packages to install on your system. In the example
inst~llation, the response is RETURN.
Do

}'Oll

.Iant the IB:D versions of

1,•

tas~\s?

<no>

Explanation - The system copies some required files and then asks if you want the
1&0 versions of tasks. You see this question only if you specified RSX andlor
AUXLIB in response to the Packages to install: question.
Instruction and Data (1&0) space is available on the PDP-ll144, 45, 50, 55, 70, 73,
83, or 84. DIGITAL does not recommend that systems with less than 256K words of
memory (PDP-11145, 50, or 55) use 1&0 space. If your system has more than 256K
words of memory (PDP-11/44, 70, 73,83, or 84.), you may want to take advantage

Select RSTS/E System Programs

of this hardware feature which yields better performance from -the following tasks:
TKB, MAC, STK, and REORDR.
Note that if you answer YES to this question, you must specify a SWAP MAX of 64K
words to accomodate the larger amount of physical memory required by the tasks.
Use the INIT.SYS DEFAULT option to change the SWAP MAX. See the Offline
Options section for details.
The system uses your response to this question later in the installation when it asks
whether you want to create a SWAP1.SYS file (see Task 1 of Phase 5). If you
answer YES to this question, the system assumes a SWAP MAX of 64K words.
Otherwise, the system assumes a SWAP MAX of 32K words.
Response - Type YES to receive the 1&0 versions of tasks. Type NO or press
RETURN to receive the normal versions. The example installation does not plan to
use 1&0 space; thus, the response is RETURN.
Use resident library ~Iersion of RMS? <>'es> (BTI)
Use RMS resident libraries in DAP? (yes>
Use RMS resident libraries in PBS? <>'es> (BTI)
Use resident librar>' version of EDT? <>'es> (BTI)

Explanation -If you choose RMS, DAP, PBS, or EDT, the system asks you to
choose either the resident library or overlaid version. The example installation sees
the RMS, PBS, and EDT resident library questions. In general, the overlaid version
requires less memory, but can impact performance. The resident library version
requires less disk space, but requires more memory. Choose the resident library
versions if your system has sufficient memory and you have more than one user
accessing a program simultaneously.
Response - Type YES or press RETURN to install the resident library version.
Type NO to install the overlaid version. The response in the example installation is
RETURN because it has sufficient memory to install the resident library versions.
Durins the build phase there will be further 9uestions
for BASIC-PLUS and SORT/MERGE

Explanation - You see these messages if you chose the BASIC-PLUS and/or
SORT/MERGE packages. You answer the BASIC-PLUS configuration questions in
Task 5A of Phase 5. You answer the SORT/MERGE questions in Task 5B of Phase

** End of SYsteM ProSraMs Section **
** Startins Layered Products Section **
Do YOU want to transfer the layered product update COMPonents
frOM the Installation Kit? <Yes> NO

Explanation - You are finished with the System Programs Section. This question
asks if you want to transfer any layered product updates from the Installation kit while

Select RSTS/E System Programs

it is still mounted. Answer YES to this question if you plan to install any layered
products on your system. If you answer YES, you continue the Layered Products
Section.
Response - Type YES or press RETURN to continue the Layered Products
Section. Type NO to skip the section. In the example installation, the response is NO.

If you answered YES to the previous question, go to Task 2.

If you answered NO to the previous question, go to Phase 5.

Select RSTS/E System Programs

Task 2: Answer Layered Product-Related Questions
You perform this task if you plan to install layered products on your RSTS/E system.
A layered product, also called optional software, is software that you must purchase
from DIGITAL. Examples of layered products are BASIC-PLUS-2, COBOL-8I, and
DIBOL.
In this task, you specify which layered products you plan to install on your system, so
that the installation procedure can transfer updates for those products from the
Installation kit.
------------------------- Note ----------------------

The RSTS/E Installation Procedure does not perform a layered
product installation. See the individual layered product installation
guide for the procedures to perform the installation.

Terminal Session
This terminal session explains the layered product-related
questions and provides some possible responses.

** Starting' Layered Products. Section**
Do YOU want to transfer the layered product update COMPonents
froM the Installation kit? (yes)

Explanation - You see this question at the end of Task 1.
Response - Type YES or press RETURN to begin the dialogue to transfer layered
products updates. Type NO to skip this section. The example installation does not
plan to transfer any layered product updates.
Product updates to transfer: ?

Explanation - This question asks for the names of the layered product updates
you want to transfer to your. system.

Select RSTS/E System Programs

Response - Type a ? to list the layered product packages that are available with

RSTS/E.
The valid responses are:
ALL
ALL,NOprod[ , ••.• ]

Transfers all product updates
Transfers all product updates except prod

Use a COMMa as a separator. e.g.: BP2,C81
Product nalTles:
ADE
BP2
COBOL
C81

DECD}·{
DECGRAPH
DECWORD
DIBOL

DrBS
DMS500
DTR
FMS

FORTRAN
FRTRN77
F77DBG
INDENT

MAIL
MENU
MSGROUTER
PL}{Y

PROIV
2780 3780
REGIS CAl 3271
RJ2780
RPG

Product updates to transfer:

Explanation - After you type a ?, you see the list of available layered products.
Then the system reprompts for the product updates to transfer.
Response - Type a list of the product names, separated by commas. Remember, if
you make a mistake you can type " to return to the previous question, or enter
CTRL/Z to return to the beginning of the section.
Type ALL to transfer all the updates. If you plan to transfer nearly all of the product
updates, type:
ALL,NOnnnnnn,NOnnnnnn
where nnnnnn refers to a product update you want to exclude.
The following will be transferred:
<list of products)
Proceed? <yes)

Explanation - The system lists the product updates it will transfer to your system
and then asks if you want to continue. If you type NO, you return to the Product
updates to transfer: prompt.
Response - Type YES or press RETURN to continue the layered product update
transfer. Type NO if you want to specify a different list of layered product updates to
transfer to your system.
Note: Any files currently in the PATCH ACCOUNT will be deleted
Since SOMe layered products May require the Update package
(frOM the SYsteM PrograMs section>, it will be included.
To install a layered product please refer to the individual
layered product installation guide.
Patch account <PATCH$:) :

Select RSTS/E System Programs

Explanation - Now you must specify the account in which you want the layered
product update information placed. The default account is PATCH$:.

After you complete the RSTS/E installation, you must follow the installation
procedures outlined in the specific layered product installation gUide to install that
layered product. Some of the layered products use the BUILD program to perform
the installation. See Appendix E for a description of BUILD.
Response - Press RETURN to accept the default patch account, PATCH$. Or
specify a different account.

** End of Layered Products Section **
Explanation - You are finished with Phase 4. If any error messages appear in the
printout, see Appendix A.

Go to Phase 5.

Select RSTS/E System Programs

Pho]se
Genero]'~e ~SlS/[E Sys'{em

You have answered all the configuration questions and are ready to install your
RSTS/E system. In this phase, you create some required system files if they do not
already exist. Then you create the RSTS/E monitor and install the system programs
you selected in Phase 4. See the appropriate installation guides for instructions on
building optional software such as BASIC-PLUS-2.
The tasks you perform in this phase are:
o Task 1: Create Additional System Files
o Task 2: Create RSTS/E Monitor
o Task 3: Install System Programs from the Installation Media
o Task 4: Physically Mount V9 Library Media
o Task 5: Install System Programs from the V9 Library Media
o

Task 5A: Answer BASIC-PLUS Installation Questions

o Task 5B: Answer SORT/MERGE Installation Questions

These responses have special meaning:
Response

Description

(Bill

Accept the default response

Obtain an online explanation of the question

Task 1: Create Additional System Files
System files are files of special use to the system itself. They reside in account [0,1].
SWAP files are the most important system files. They store jobs transferred out of
memory. Without at least one SWAP file, the system cannot swap jobs out of
memory and will not work. There are four available SWAP files: SWAPO.SYS,
SWAP1.SYS, SWAP2.SYS (always referred to as SWAP.SYS), and SWAP3.SYS.
During system start-up, INIT.SYS automatically creates the SWAP.SYS file at a size
large enough to store one job at the maximum size of 32K words. In addition,
INIT.SYS automatically creates the system files ERR.SYS and CRASH.SYS during
system start-up.
In this task, the installation procedure creates the SWAP1.SYS file at a size large
enough to hold the number of jobs you specified when you answered the Maximum
jobs? question in Task 6 of Phase 3. If necessary, the system also creates the
BUFF.SYS file which is required if you have TU56 DECtapes on your system. You
answered the DECtapes? question in Task 4 of Phase 3.
You can create other system files later by using the INIT.SYS REFRESH option or
the DCL INSTALL command. For a detailed description of system files, see the
REFRESH Option section in the Offline Options.

Terminal Session
This terminal session explains how to create additional system
files. First, you must specify a password for account [1,2].

You Must now set the password for account _SY:El ,2]
Nel. .1 passl. .lo rd:
New password afain, for verification:
Pass . . lord set for account _SY:El ,2]

Explanation - This question asks you to specify a password for the system library
account, [1,2]. This is a precautionary measure to provide you with an account that
you can log in to in case of unforseen problems. DIGITAL does not recommend that
you log in to and use account [1,2] on a regular baSis, because of the importance of
the files that reside in the account.

Generate RSTS/E System

Response - Type a password from 6 to 14 characters. You can specify any ASCII
character except the ? character. Retype the password when prompted.

* End of dialogue phas~ *
* Starting build phase *
Are

}'OU

ready to proceed? (}'es)

Explanation - The system asks if you are ready to generate your RSTS/E system.
If you· are ready to proceed, type YES or press RETURN.
If you are not ready, type NO. You then see the dollar sign ($) prompt. You may
need to answer NO, for example, if you want to modify the SYSGEN.COM or the
CONFIG.MAC configuration files, which generate the RSTS/E monitor. EDT is
available at this point for unsupported modifications. After making any modifications,
type PROCEED to continue the installation.

Response - Type YES or press RETURN to begin the build phase of the
installation. In the example installation, the response is RETURN because it is ready
to proceed.
31-MaY-85 05:31 AM
Do

}'OU

""Iant _SYO:SWAP1.SYS created? <}'es)

Creating _SYO:[O,IJSWAP1.SYS at 4882 blocKs

Explanation - The system checks for a SWAP1.SYS file on your system. If it does
not find SWAP1.SYS, the system asks if you want to create a SWAP1.SYS file at a
size large enough to hold all the jobs on your system. It automatically creates
SWAP1.SYS as close to the center of the system disk as possible. The system
determines the size of SWAPl.SYS according to this formula:

(JOB MAX-I) * SWAP MAX * 4
where:
JOB MAX-l

is the number of jobs you specified in Task 6 of Phase 3, minus 1.

SWAP MAX

is 32K words if you did not see or answered NO to the Do you
want the 1&0 versions of tasks? question in Task 1 of Phase 4.
is 64K words if you answered YES to the Do you want the 1&0
versions of tasks? question in Tas~ 1 of Phase 4.

You do not see this message if your system has a SWAP1.SYS file.
If the system is unable to create SWAP1.SYS, it prints an error followed by the
message Can not create SWAP1.SYS. If you see this message, you must use the
INIT.SYS REFRESH option to create SWAP1.SYS before you start timesharing. See
the Offline Options section for more information on REFRESH.

Generate RSTS/E System

Response - Type YES or press RETURN to create SWAP1.SYS. Type NO to skip
the creation of SWAP1.SYS. Type a ? if you want to know the size of SWAP1.SYS
before you answer the question. In the example, the response is RETURN. The
system then creates SWAP1.SYS at a size of 4992 blocks.
Creating _SYO:[OtlJ5UFF.SYS at xx blocKs

Explanation - You see this message only if you have TU56 DECtapes on your
system. You must have a BUFF.SYS file for your RSTS/E monitor to support one or
more TU56 DECtapes.
The system automatically creates BUFF.SYS as close to the center of the system disk
as possible. It determines the size of BUFF.SYS (shown as xx blocks) according to
this formula:
4 blocks for each TU56 DECtape
Response - In the example installation, you do not see this message because there
are no DECtapes on the system.
Please Mount the OECnet/E Installation Media and enter the naMe
and unit nUMber of the device.
I.Jalid device t}'pes are: 'MM't 'MS't 'MT't 'OM' or 'OL'
OECnet/E installation device <dev:>

Explanation - You see this question only if you answered YES to the DECnet
network support? question in Task 4 of Phase 3. Mount the DECnetiE Installation
media on a free drive when prompted. You may have to dismount the RSTS/E
Installation media to make room for the DECnetiE kit, if you do not have a free drive
available. The system prompts you to remount the RSTS/E Installation media later.
Response - After you have mounted the DECnet Installation media, type the
device name and unit number of the drive on which it is mounted. Or, press
RETURN to accept the default <dev: >.
The example installation does not see this question, because it does not plan to install
DECnetiE.
Restoring re9uired COMPonents
Enabling OECnet/E Monitor COMPonents
Please ensure that the Installation Media is Mounted
on dev: and press RETURN when ready:

Explanation - You see these messages only if you are installing DECnetiE. After
the system has transferred the DECnet files, it prompts you to remount the Installation tape or disk.

Generate RSTS/E System

Dismount the DEC net media and mount the Installation tape or disk
on the drive indicated by dev:. Make sure the tape or disk is on line. Then press
RETURN when you are ready to proceed.

Response -

Creating RSTS/E Monitor

Go to Task 2.

Generate RSTS/E System

Task 2: Create RSTS/E Monitor
The command procedure now creates your RSTS/E monitor. The entire process
should take 30 to 45 minutes, depending on the size of your monitor.
If the command procedure encounters an error during the monitor build, it prints the
error and returns to the configuration questions in Phase 3. You see the Beginning of
RSTS/E system generation message. If you see this message, return to Phase 3 and
answer the configuration questions again. For example, you may have to answer the
configuration questions again if the monitor you configured is too big for your system;

Terminal Session
This terminal session explains the procedures that generate
the RSTS/E monitor. The procedures will differ depending on
your response to certain configuration questions in Phase 3.

Creating R8T8/E Monitor
31-MaY-85

05:32 AM

Explanation - The command procedure now begins the RSTS/E monitor
generation.
If you answered YES to the RJ2780 support? question in Task 4 of Phase 3, the
program prompts you to mount the RJ2780 Software Kit at this time. Mount the
RJ2780 kit when you see this prompt:
Please Mount the RJ2780 Installation Kit and enter the naMe
and unit nUMber of the device • .
1•.Jalid de~dce t}'pes are:
'MM', 'M8', 'MT't 'DM', 'DL', or '8'('
Installation device <dev:> :

You may have to dismount the RSTS/E Installation media to make room for the
RJ2780 kit, if you do not have a free drive available. The system prompts you to
remount the RSTS/E Installation media later. Remount the installation media on the
indicated drive when prompted.
%8Mall buffers lowered by xxx buffers
This will leave YOU with yyy buffers

Explanation - The command procedure checks whether the number of small
buffers you specified in Task 6 of Phase 3 will fit on your system. If the number you
specified is too high, the command procedure attempts to decrease the number of
buffers so that the monitor fits on your system.

Generate RSTS/E System

If the number of small buffers you specified in Task 6 of Phase 3 is much too high for
the maximum number allowed for your system, you see the message:
?LINK-F-Address space exceeded
Beginning of RSTS/E SYsteM generation

In general this indicates that the system you configured is too big. Rather than make
such a radical adjustment to your monitor by significantly decreasing the small
buffers, the command procedure returns to the configuration questions in Phase 3 of
Part I. If you see this message, return to Phase 3 and answer the configuration
questions. You may want to decrease the size of your system by changing the
answers to some of the questions (for example, fewer devices, terminals, or pseudo
keyboards). Also, specify a much smaller number to the Small buffers? question in
Task 6. In general, 600 is a good response to the Small buffers? question.
See the BUFFERS suboption of DEFAULT in the Offline Options part of this gUide
for more information on small buffers.
The command procedure did not lower the number of small buffers in the example
installation.
This Monitor will fit OK

Explanation - You see this message if your new monitor is an acceptable size.
Next the command procedure prints a table that shows how many general and FIP
small buffers you currently have. In addition, the table tells you how many general
and FIP small buffers you can add if you have data space and how many FIP small
buffers you can add if you do not have data space. See the section, BUFFERS
Dialogue, in the Offline Options for an example buffer table.

Go to Task 3.

Generate RSTS/E System

Task 3: Install System Programs from the Installation Media
The system now installs the system programs according to the instructions you gave
in Phase 4. First, the system transfers the remaining files from the Installation tape or
disk. The system also transfers any layered product updates you specified in Phase 4.
This task should take ten to fifteen minutes, depending on the size of the installation.
The system installs each package at the location pointed to by its associated logical
name. If the program finds no associated logical name, it installs the package at the
default location. This is the case in a new installation.
Table 7 lists the logical names and default locations for each package.
Table 7:

System Program Package Logical Names
Package

Logical Name

Location

System Library

SYSLIB$:

[1,2]

RSX Utilities

LB:

[1,1]
[1,2]

Help

HELP$:

[0,2]

Error

ERROR$:

[0,3]

Update

UPDATE$:

[0,4]
[1,2]

Device Testing

TEST$:

[0,5]

Print/Batch Services
(PBS)

PBS$:

[0,6]

File Restore

RESTOR$:

[0,7]

OPSER-based Spooling

OPSER$:

[0,8]

Unsupported Utility

UNSUPP$:

[0,9]

Auxiliary Library

AUXLIB$:

[0,14]

RMS-11

RMS$:

[0,10]

EDT

EDT$:

[0,11]

TECO

TECO$:

[0,13]

SORT/MERGE

SORT$:

[0,15]

BASIC-PLUS

BASIC$:

[0,12]

Generate RSTS/E ~ystem

Terminal Session
This terminal session explains the procedures that transfer the
system programs from the Installation media.

31-MaY-85 05:48 AM
Restorin~

the xxxxxx

pacKa~e

froM the Installation Kit

There are no updates for the xxx xxx

pacKa~e

Explanation - The system now installs the system programs. First it installs updates
for the three packages that are automatically installed on all systems: System Startup,
System Library, and Error. Then, as the system installs each optional package, it
prints one of the above messages. In both messages, xxxxxx is the name of the
specific software package.
In the example installation, the system prints the following messages. The messages.
for your installation may vary depending on how you answered the system program
questions in Phase 4.
There
There
There
There
There

are
are
are
are
are

Restorin~

Regtorin~

There
There
There
There
There
There
There

are
are
are
are
are
are
are

Restorin~

There are
Restorin~

no updates for the SYsteM Startup files
no updates for the SYsteM Library Packa~e
no updates for the Error Packa~e
no updates for the RSX Libraries
no updates for the RSX Utilities
the RMS-ll pacKa~e froM the Installation kit
the RMS Libraries froM the Installation kit
the Print/Batch Services packa~e froM the Installation Kit
no updates for the EDT pacKa~e
no updates for the Update pacKa~e
no updates for the Device Testin~ pacKa~e
no updates for the TECD packa~e
no updates for the Auxiliary Library pacKa~e
no updates for the File Restore pacKa~e
no updates for the Opser-based Spoolin~ pacKa~e
the Help packa~e froM the Installation Kit
no updates for the BASIC-PLUS packa~e
the Resident Libraries froM the Installation kit

After the system completes the system program file transfers, it restores the layered
product updates you specified in Phase 4. As the system transfers each layered
product update, it prints the message:
Restorin~

the xxx xxx update COMPonents froM the Installation Kit

where xxxxxx is the name of the layered product.

Generate RSTS/E System

Then the system prompts you to mount the V9 Library tape or disk.
31-MaY-85 05:52 AM
Please Mount the RBTB/E Library Media and enter the
naMe and unit nUMber of the device.
IJalid del.dce t}'pes are: 'MM't 'MB't 'MT't 'DM' or 'DL'
Library device <_MBO:>

Go to Task 4.

Generate RSTS/E System

Task 4: Physically Mount V9 Library Media
You no longer need the Installation tape or disk. In this task, you mount the V9
Library media.

Terminal Session
This terminal session explains how to mount the V9 Library
media.

Please Mount the RSTS/E Library Media and enter the
naMe and unit nUMber of the device.
IJalid device t}'pes are: 'MM't 'MS't 'MT't 'DM' or 'DL'
Library device <_MSO:> ru

Explanation - After the system copies files from the Installation media, it prompts
you to mount the V9 Library media. Remove the Installation media from its drive and
mount the V9 Library media. Follow the tape or disk mount instructions in Task 2 of
Phase 1.
Response - Type the device name and unit number of the drive on which the V9
Library media is mounted. The device name within the brackets (MSO in the example
installation) is the drive on which the Installation media was mounted. In the example
installation, the response is RETURN to indicate. the drive MSO.

Go to Task 5.

Generate RSTS/E System

Task 5: Install System Programs from the V9 Library Media
The system now transfers the rest of the system programs from the V9 Library media,
according to the instructions you gave in Phase 4. This task should take 20 to 30
minutes, .depending on the size of the installation.

Terminal Session
This terminal session explains how to transfer the system
programs from the V9 Library media.

Restorins the xxxxxx pacKase froM the Library Kit

Explanation - The command procedure now installs the system programs. First it
installs the three packages that are automatically installed on all systems: System
Startup, System Library, and Error. As the command procedure installs each optional
package, it prints the above message, where xxxxxx is the name of the specific
software package.

The system also prints the message File not replaced for files that were already
transferred from the Installation kit. You should see this message only for packages
that had updates restored from the Installation kit.
In the example installation, the system prints the following messages. The messages
for your installation' may vary depending on how you answered the system program
questions in Phase 4.
Restoring'
Restorins
Restorins
Restorins
Restorins
Restorins
Restorins
Restorins
RestorinS
Restorins
Restorins
RestorinS
RestorinS
Restorins
Restorins
Restorins
Restorins
Restoring'

the
the
the
the
the
the
the
the
the
the
the
the
the
the
the
the
the
the

31-MaY-85

06:10 AM

SYsteM Startup files frOM the Library Kit
SYsteM Library PacKase frOM the Library Kit
Error PacKase frOM the Library Kit
RSX Libraries frOM the Library Kit
RSX Utilities frOM the Library Kit
RMS-11 pacKaSe frOM the Library Kit
RMS Libraries frOM the Library Kit
Print/Batch Services pacKase frOM the Library Kit
EDT pacKase frOM the Library Kit
Update pacKase frOM the Library Kit
Device Testins pacKase frOM the Library Kit
TECD pacKase frOM the Library Kit
Auxiliary Library pacKase frOM the Library Kit
File Restore pacKase frOM the Library Kit
Dpser-based SpoolinS pacKase frOM the Library Kit
Help pacKase frOM the Library Kit
BASIC-PLUS pacKag'e frOM the Library Kit
Resident Libraries frOM the Library Kit

Installins software pacKases

Generate RSTS/E System

Explanation - After the system completes the file transfers, it prints these messages. Then, if you specified BASIC-PLUS as one of the packages to install, the
system begins the BASIC-PLUS dialogue. Otherwise, you continue with the rest of
the installation dialogue.
Be~innin~

of RSTS/E Basic-Plus

~eneration.

BASIC-PLUS RTS naMe? (BASIC>

Explanation - You see this question only if you specified BASIC-PLUS as one of
the packages to install on your system (see Task 1 of Phase 4). You now see a series
of questions that determine the configuration of BASIC-PLUS for your system.

Go to Task SA for a complete description of the BASIC-PLUS dialogue. Otherwise,
continue with this task.
Be~innin~

SORT/MERGE installation

Explanation - You see this question only if you specified SORT/MERGE as one of
the packages to install on your system (see Task 1 of Phase 4). You now see a series
of questions that determine the configuration of SORT/MERGE for your system.

Go to Task 5B for a complete description of the SORT/MERGE dialogue. Otherwise,
continue with this task. The example installation does not plan to install
SORT/MERGE.
To install/update layered productst please see the individual layered
product installation ~uides.

Explanation - You see this question only if you transferred layered product
updates to your system (see Task 2 of Phase 4).

See the installation instructions that came with each layered product for a complete
description of the installation procedures.

* End of build phase *
The RSTS/E Software Installation Procedure is COMPlete
Deletin~

all

~lobal

SYMbols

31-MaY-85 06:17 AM
SysteM tape label default set to DOS
SY:[1 tZJINSTAL.LoG is a

lo~

file of this session

Explanation - You have completed the installation. The command procedure
prints informational messages and reminds you that the INSTAL.LOG file is a record
of the installation.

Go to Phase 6.

Generate RSTS/E System

Task 5A: Answer BASIC-PLUS Installation Questions
You perform this task if you are installing BASIC-PLUS on your system. In this task
you specify the particular BASIC-PLUS configuration for your system. The
BASIC-PLUS installation questions relate to optional features of the BASIC-PLUS
run-time system such as math precision, logarithmic functions, and trigonometric
functions.
Certain combinations of features will cause your BASIC-PLUS run-time system to
exceed 16K words. This limits programs running under BASIC-PLUS to a maximum
size of 12K words.
If you select double-precision floating point math precision (see Math precision?
question) and do not select FPP (see FPP? question), then you must omit some
optional features.

Table 8 lists the BASIC-PLUS optional features. If you must omit some optional
features, use Table 8 to determine which combinations you can select. You can
include features with a total size of up to 6.
Table 8:

BASIC-PLUS Optional Features

Feature

Size

Log functions

Trig functions

Print using

Matrices

String arithmetic

Terminal Session
This terminal session explains the BASIC-PLUS installation
questions and provides some possible responses. For more
information on any of these features, see the BASIC-PLUS
Language Manual. In some cases, your response will differ
from the response shown in red in the example installation.

BASIC-PLUS RTS nairle? <BASIC> m:ru

Explanation - This question asks for a BASIC-PLUS run-time system name. The
system automatically assigns a file type of .RTS to this name. Your run-time system
will be stored as a save image library (SIL) in account [0,1] on your system disk.

Generate RSTS/E System

Response - Type a one- to six-character alphanumeric name for your BASICPLUS run-time system or press RETURN to accept the default of BASIC, as in the
example installation.
FPP? <'I'>

Explanation - The floating point processor (FPP) is hardware that supports both
single-precision (2-word) or double-precision (4-word) floating point instructions. FPP
is available for the PDP-ll/23 PLUS, 11124, 11134, 11/44, 11145, 11150, 11/55, and
11/70. It is standard hardware on the 11/60, 11173, 11/83, and 11184.
Response - You see a Y default if your PDP-II has FPP; yOU see a N default if
your PDP-II does not have FPP. Type YES or press RETURN if your PDP-II has
FPP; type NO or press RETURN if it does not. If you type YES, the program goes to
the Math precision? question. In the example installation, the response is RETURN.
Math precision? <02>

Explanation - This question asks if you want your math package to support
single-precision or double-precision floating point instructions. The single-precision
floating point instructions provide floating-point numbers that are precise to 6
significant digits; the double-precision floating point instructions provide floating point
numbers that are precise to 15 significant digits. In addition, the double-precision
floating-point instructions provide a scaled arithmetic feature. Scaled arithmetic is
useful for calculating sums that cannot be easily expressed as integer quantities, such
as dollars and cents.
Response - Type 2 or press RETURN if you want the single-precision floating point
instruction; type 4 if you want the double-precision floating point instruction. In the
example installation, the response is 4.
Los' functions? <'I'>

Explanation - This question asks if you want the BASIC-PLUS run-time system to
use the logarithmic functions SQR, EXP, LOG, and LOGI0. Some installations may
not need this feature, in which case you can reduce the size of the BASIC-PLUS
run-time system by answering N to this question. (The polynomial calculation portion
of the math functions is present if you include either this feature or the trigonometric
feature.) Operations such as X"'Y require the log functions if Y is not an integer.
Response - Type YES or press RETURN to add the logarithmic functions; type NO
if you do not want to add the logarithmic functions. In the example installation, the
response is RETURN.
Tris' functions? <'I'> ~

Explanation - This question asks if you want the BASIC-PLUS run-time system to
use the trigonometric functions SIN, COS, TAN, and ATN. Some installations may
not need this feature, in which case you can reduce the size of the BASIC-PLUS
run-time system by answering N to this question. (The polynomial calculation portion
of the math functions is present if you include either this feature or the logarithmic
feature.)

Generate RSTS/E System

Response - Type YES or press RETURN if you need to add these functions; type
NO if you do not need to add these functions. In the example installation, the
response is RETURN.
Print using?

<y> m

Explanation - This question asks if you want special output formatting with the
PRINT-USING statement of BASIC-PLUS. Some layered products require this
feature. You can reduce the size of the BASIC-PLUS run-time system by answering
N to this question.
Response - Type YES or press RETURN if you need this feature; type NO if you
do not need this feature. In the example installation, the response is RETURN.
Matrices?

<N> Y

Explanation - This question asks if you want BASIC-PLUS to operate on an entire
matrix using single MAT statements.
Response - Type YES if you need this feature; type NO or press RETURN if you
do not need this feature. In the example installation, the response is Y.
String arithlrletic?

<N> m

Explanation - The BASIC-PLUS run-time system can use special string arithmetic
functions like SUM$, DIF$, PROD$,QUO$, PLACE$, and COMP%. These functions
perform arithmetic functions on strings of numeric characters, minus signs, and
decimal points with an accuracy of up to 56 significant digits. The string arithmetic
functions, although slow to execute, are useful for applications that involve large
numbers, such as monetary conversions.
Response - Type YES if you need this feature; type NO or press RETURN if you
do not need this feature. In the example installation, the response is RETURN to
accept the default of NO.
Beginning SORT/MERGE installation

'92

Generate RSTS/E System

Go to Task 53 for a complete description of the SORT/MERGE dialogue. Otherwise,
continue with this task.

* End of build phase *
The RSTS/E Software Installation Procedure is cOMPlete
Deleting all global SYMbols

31-MaY-85 06:17 AM
SYsteM tape label default set to DOS
SY:[1 tZJINSTAL.LOG is a log file of this session
$

Explanation - You have completed the installation. The command procedure
prints informational messages and reminds you that the INSTAL.LOG file is a record
of the installation.

Go to Phase 6.

Generate RSTS/E System

Task 58: Answer SORT/MERGE Installation Questions
This task describes the SORT/MERGE installation questions. You see these questions
if you specified SORT/MERGE in response to the Packages to install: prompt in Task
1 of Phase 4. See the PDP-ll SORT/MERGE User's Guide for more information on
SORT/MERGE.

Terminal Session
This terminal session describes the SORT/MERGE installation
questions and provides some possible responses.

Note

In the following section, the expression <SWAP-MAX-SIZE> means
the SWAP MAX size for your system. During the installation
procedure, the actual SWAP MAX size (for example, 28K words) is
displayed in place of <SWAP-MAX-SIZE>.

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

*
This is the beginning of the dialogue to
* definB the attributes of your SORT/MERGE utility.

*
*

******************************************************
This procedure will t by defaultt build and install
SORT and MERGE for oPtiMUM perforMance. The utility
SORT and MERGE tasKs will have the following attributes:
SORT built at <SWAP-MAX-SIZE)/ MERGE built at <SWAP-MAX-SIZE)
Have ASCII as the default character collating sequence
Process duplicate records
Do a nonstable SORT and MERGE
Retry 2000 tiMes when trying to read a locKed bucKet
Allow 55% of the SORT worK area for SORT tree structure
Allow 30% of the MERGE worK area for MERGE data structure
Use five (5) worK files for SORT
Use the RECORD sort process
Sequence checK the input files for MERGE
AdditionallYt the default will NOT build the
SORT and MERGE callable subroutines as a resident library,
If yOU want the installation to proceed using
these defaultst answer YES. If yOU want to
change any of these defaultst answer NO.
Do you want to proceed with the default installation <Yes)?

Generate RSTS/E System

If you answer YES, go to Question 22 to verify your selection of attributes. If you
answer NO, go to Question 1.
1. If YOU want to chan~e the ~efault size of the SORT
or MERGE tasK, answer YES, otherwise answer NO.
00 YOU want to

chan~e

the default tasK size

<NO>?

If you answer NO, go to question 5. If you answer YES, go to Question 2.
2. The size of the final SORT and MERGE tasKs can be
varied by chan~in~ the default size of the worK
area. The worK area is currently set to be the
MaxiMuM allowed by your operatin~ SYsteM in order
to ~ive SORT/MERGE the OPtiMuM perforMance.
Which tasK size do YOU want to chan~e
SORT
MERGE
BOTH
NEITHER

<BOTH>?

If your answer is either BOTH or SORT, go to Question 3. If your answer is MERGE,
go to Question 4. If your answer is NEITHER, go to Question 5.
3. The MaxiMuM SORT tasK size is the SWAP MAX on your SysteM.
The MiniMuM SORT tasK size is 17K words.
the chosen size MUSt be a whole nUMber between these
inclusive liMits. DeciMals will be truncated.
What size do YOU want your SORT tasK to be

«SWAP-MAX-SIZE»?

If you answered SORT to Question 2, go to Question 5. If you answered BOTH to
Question 2, go to Question 4, then go to Question 5.
4. The MaxiMuM MERGE tasK size is the SWAP MAX on your SysteM.
The MiniMuM MERGE tasK size is 17K words.
The chosen size MUSt be a whole nUMber between these
inclusive liMits. DeciMals will be truncated.
What size do YOU want your MERGE tasK to be «SWAP-MAX-SIZE»?
5.

If YOU want to chan~e any of the default runtiMe options, answer
YES, otherwise, answer NO.
Do YOU want to

chan~e

any of the default runtiMe oPtions

<NO>?

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

*
*
*

IF YOU CHANGE ANY OF THE DEFAULTS, BE SURE TO
INFORM YOUR USERS, SINCE THOSE DEFAULTS MAY
NOW BE DIFFERENT FROM THE DEFAULTS STATED IN
THE SORT/MERGE DOCUMENTATION!

*
*
*
*

******************************************************
If you answer NO, go to Question 21. If you answer YES, go to Question 6.
6. By default, SORT/MERGE will use the ASCII
when operatin~ on character data Keys.
Do YOU want to

chan~e

the default

collatin~

sequence

sequence
<NO>?

Generate RSTS/E System

If you answer NO, go to Question 8. If you answer YES, go to Question 7, then go
to Question 8.
7. The choices are ASCII, EBCDIC, or MULTINATIONAL.
What do YOU want the default character Key collating
sequence to be?
ASCII

EBCDIC

MULTI

<ASCII>?

8. By default, SORT/MERGE will process records which are
found to have duplicate Key fields.
If yOU wish to have SORT/MERGE eliMinate records with
duplicate Keys by default, answer YES.
If yOU wish to have SORT/MERGE Keep all
duplicate Keys by default, answer NO.

records with

Should SORT/MERGE eliMinate duplicate records by default

<NO>?

If you answer NO, go to Question 9 and then Question 10. If you answer YES, you
see the following message:

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

* YOU HAVE CHOSEN TO ELIMINATE DUPLICATE RECORDS BY DEFAULT. *
* STABLE SORT/MERGE AFFECTS DUPLICATE RECORDS. THEREFORE, THE *
*
* STABLE AND NODUPLICATES OPTIONS ARE MUTUALLY EXCLUSIVE.
* YOUR DEFAULT FOR THE STABLE OPTION MUST BE NOSTABLE.
*

***************************************************************
If you answered YES, go to Question 10.
8.

Stable SORT/MERGE iMPoses extra overhead during the
~\e}' 'colTIParison process. For this
reason, the default is
for a nonstable SORT/MERGE. If yOU wish to change this
defailt, answer YES, otherwise answer NO.
Do yOU wish the defaul·t to be a stable SORT/MERGE

(NO>?

10. The SORT worK area is divided into two areas, one
for the SORT tree data structure, and one for the
RMS I/O data ~t·ructures. For SORT, the default division
giving optiMuM perforMance is 55% to the tree and 45% to I/O.
If the Majority of the files you are sorting requires
a large nUMber of I/O data structures (for exaMPle, INDEXED
files with Many Keys, or a consistently large nUMber
of input files), yOU May want to alter the sPlit so that
there will be enough rOOM for the I/O reqUireMents.
If you want to change the default split, answer YES,
otherwise answer NO.
Do yOU want to change the SORT default sPlit

(NO>?

If you answer NO, go to Question 12. If you answer YES, go to Question 11 and
then 12.
11. What percentage of the worK area should be allotted to the
SORT tree data structure? The lower liMit is 45%.
The upper liMit is 85%.
Your answer MUSt be in whole nUMbers.
<55>?

Generate RSTS/E System

12. The MERGE worK area is divided into two areast one
for the MERGE data structure and one for the
RMS lID data structures. For MERGEt the default division
giving optiMUM perforMance is 30% to the data structure and
70% to the RMS data structures.
If the Majority of the files you are Merging re~uires
a large nUMber of lID data structures (for exaMPlet INDEXED
files with ·Many Keyst or a consistently large nUMber
of input files). YOU May want to alter the sPlit so that
there will be enough rOOM for lID re9uireMents.
If yOU want to change the default sPlitt answer YESt
otherwise answer NO.
Do yOU wish to change the MERGE default sPlit

<NO)?

If you answer NO, go to Question 14. If you answer YES, answer Question 13 and
then go to Question 14.
13. What percentage of worK area should be allotted to the
MERGE data structure? The lower liMit is' 20%.
The upper liMit is 40%.
Your answer MUSt be in whole nUMbers.
<30)?
14. The OPtiMUM nUMber of worK files for SORT is 5.
If yOU wish to change this defaultt answer YES.
otherwise answer NO.
<NO)?

If you answer NO, go to Question 16. If you answer YES, go to Question 15 and
then to Question 16.
15. The MiniMUM nUMber of worK files is 3t the MaxiMuM is 10.
How Many worK files should SORT use by default? <5)?
lB. By defaultt SORT will carry cOMPlete records throughout
the process and output cOMPlete records. If you are sorting
large records with sMall Keys and wish to conserve disK spacet
you May change this default.

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

PLEASE NOTE THAT FOR SORTS USING OTHER THAN THE RECORD
PROCESSt ALL INPUT FILES MUST RESIDE ON DISK.

****************************************************************
If yOU wish to change the default sort process. answer YES.
otherwise answer NO.
Do yOU wish to change the default sort process

<NO)?

If you answer NO, skip Question 17 and answer Questions 18 and 19. If your answer
is YES, answer Questions 17-19.
17. What should the default sort process be?
RECORD TAG ADDRESS INDEX
<RECORD)?
18. By default. MERGE will se9uence checK the input records.
If you want to change this default. answer YESt
otherwise answer NO.
<NO)?
/

Generate RSTS/E System

19. SORT/MERGE will read input files which are in use
and opened in a shareable Mode. If SORT/MERGE
encounters a locked bucket, the operation will be
retried a MaxiMUM of 2000 tiMes before a fatal error
is returned. If YOU want to chan~e the nUMber of
retries, answer YES, otherwise answer NO.
Do YOU want to

chan~e

the nUMber of retries

<NO)?

If you answer NO, go to Question 21. If you answer YES, go to Question 20 and
then to Question 21.
20. The MaxiMuM nUMber of retries allowed is 9999.
The MiniMuM nUMber of retries allowed is 1.
How Many tiMes should SORT/MERGE try to
re-read a locked bucket (2000)?
21. By default, the callable SORT and MERGE subroutines will
be available via two object libraries. Additionally, if
you want to build a cOMbined callable SORT and MERGE
resident library answer YES, otherwise answer NO.
Do YOU want to build a cOMbined callable SORT and MERGE
cluster library <NO)?

This completes the selection of attributes for your SORT/MERGE utility. The installation procedure now shows you the attributes that you have selected, and you have
the opportunity to change the attributes. (The attributes shown in this example are
not necessarily the default attributes, nor does DIGITAL necessarily recommend them
for your system - they are only a sample.)
22.

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

* Your SORT and MERGE product will be built *
* accordin~ to the followin~ specificatfons: *
***********************************************
SORT TASK SIZE IS 32K WORDS
MERGE TASK SIZE IS 32K WORDS
YOU HAVE THE FOLLOWING RUNTIME DEFAULTS:
ASCII CHARACTER COLLATING SEQUENCE
RECORDS WITH DUPLICATE KEYS ELIMINATED
NO STABLE PROCESS
2000 LOCKED BUCKET RETRIES
55% OF WORK AREA FOR SORT DATA STRUCTURES
45% OF WORK AREA FOR SORT RMS DATA STRUCTURES
30% OF WORK AREA FOR MERGE DATA STRUCTURES
70% OF WORK AREA FOR MERGE RMS DATA STRUCTURES
03 WORK FILES
RECORD SORT
DO NOT SEQUENCE CHECK MERGE INPUT
A SORT/MERGE RESIDENT/CLUSTER LIBRARY WILL BE BUILT
ARE THE ABOVE DEFAULTS THE DESIRED ONES <YES or NO)

<YES)?

If you answer NO, go back to Question 1 and repeat the dialogue procedure. If you
answer YES, you see the following message:

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

*
*
*

This is the end of the installation dialo~ue.
The installation will now proceed without
further operator intervention.

*
*
*

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

Generate RSTS/E System

The installation procedure then continues without operator intervention. It will task
build and install the utilities, place the callable overlay description files in the system
directory, and then make a verification pass to ensure that the utility has been
properly installed. If an error is encountered, you see the following message:
????????????????????????????????????????????
?

?
?
?
?

?
Either SORT or MERGE did not install
properly. Contact your software
?
specialist for further assistance!
?
????????????????????????????????????????????
I

If no errors are encountered, you see the following messages and the installation is
complete:
PDP-11 SORT/MERGE V3.0 is now built.
END STMGV3.CMD - PDP-11 SORT/MERGE VERSION 3.0

* End of build phase *
The RSTS/E Software Installation Procedure is COMPlete
Deleting all global SYMbols

31-MaY-85 08:17 AM
SYsteM tape label default set to DOS
SY:[1 tZJINSJAL.LOG is a log file of this session
$

Explanation - You have completed the installation. The command procedure
prints informational messages and reminds you that the INSTAL. LOG file is a record
of the installation.
Go to Phase 6.

Generate RSTS/E System

PhOlse
Cwecr~e Accou~,r~s OlrtO] [EoH~ Sys19m Svolri-Up ~ile

After you finish Phase 5, you are ready to tailor your new RSTS/E system.
The tasks in this phase are:
o Task 1: Create the System Management Account (CREATE/ACCOUNT)
o Task 2: Create User Accounts (CREATE/ACCOUNT)
o Task 3: Edit System Start-Up File

101

Task 1: Create the System Management Account (CREATE/ACCOUNT)
In this task you create the system management account on your system disk with the

CREATEIACCOUNT command. The system management account is the account you
use to perform system management tasks. DIGITAL recommends that you make this
account different from the account you are currently working in, [1,2]. Normally you
grant all privileges to the system management account.
You use qualifiers with the CREATElACCOUNT command to establish such things as
disk quotas and privileges. If you are not familiar with the qualifiers for the
CREATE/ACCOUNT command, see the RSTSIE System Manager's Guide.

Terminal Session
This terminal session explains how to use the
CREATEIACCOUNT command to create the sY$tern
management account.

The RSTS/E Software Installation Procedure is cOMPlete

Explanation - The software installation is finished. You now see the DCl $
prompt.

Type a command of the following format:
CREATE/ACCOUNT dev: [p tpn] /PRIVILEGES= (abc tdef t ••• )
Password: (password>
Password againt for verification: (password>

Explanation - The CREATEIACCOUNT command establishes accounts on your
RSTS/E system. If you omit the device specification, the default is the system disk,
SYO: . You specify the account privileges as a list following the IPRIVIlEGES qualifier.
See the RSTSIE System Manager's Guide for more information about privileges. The
password can be any combination of ASCII characters except the ? character, and
can be from 6 to 14 characters long. By default in V9.0, the password is
INOlOOKUP. This makes it impossible to look up the password, thus providing
additional account security.

102

Create Accounts and Edit System Start-Up File

The example installation plans to create a fully privileged system management
account [1,4] on the system disk. The command line in the example installation looks
like:
CREATE/ACCOUNT [1 fa]/PRIVILEGES=ALL
Passl"lo rd:
Password a~ainf for verification:
Account _SYO:[1 fa] created at DCN 273a5

Explanation - These commands create a new account [1,4] on the system disk,
SYO:. The account has all privileges. The account password cannot be looked up.

Go to Task 2.

Create Accounts and Edit System Start-Up File

103

Task 2: Create User Accounts (CREATE/ACCOUNT)
In this task you create user accounts on your system disk with the

CREATEIACCOUNT command. You use qualifiers with the command to establish
such things as disk quotas and privileges. If you are not familiar with the qualifiers of
the CREATEIACCOUNT command, see the RSTSIE System Manager's Guide.

Terminal Session
This terminal session explains how to use the
CREATE/ACCOUNT command.

Type a command in the following format:
CREATE/ACCOUNT dev:[ptpn][/QUALIFIERS]
Password: (password>
Password araint for verification: (password>

Explanation - The CREATEIACCOUNT command establishes accounts on your
RSTS/E system. If you omit the device specification, the default is the system disk.
SYO:. The password can be any combination of ASCII characters except the ?
character, and can be from 6 to 14 characters long.

Go to Task 3.

104

Create Accounts and Edit System Start-Up Ff:'~

Task 3: Edit System Start-Up File
Your next task is to edit START.COM, the system start-up file. This command file
must contain the information required to properly initialize the system for both normal
time-sharing operations and system recovery after a crash.
DIGITAL provides this file in the system account [0,1]. Edit this file as your
installation requires. You may need to edit START.COM for one or more of these
reasons:
o Add start-up commands for terminals and line printers.

• Add system logical definitions or commands associated with optional products
such as DECnet. See the installation guide for the particular optional product
for specific information.
o Add start-up commands for the OPSER-based spooling package.
o Add system logical definitions or commands associated with third-party

software.
See the RSTSIE System Manager's Guide for more information about editing the
START.COM file.
---------------------- Note

The START.COM file provided by DIGITAL contains sufficient
commands to start your new V9. a monitor. If you are using a
hard-copy terminal to perform your installation, you may prefer to
wait until you have started timesharing under your new monitor to
edit START. COM. Then you can log in to a video terminal to edit the
file.
If you choose to edit START. COM later, be sure to shut the system
down after you make your edits. Then start timesharing again to make
sure your new START. COM file works properly.

This session uses EDT to edit the system start-up file. If you do not have EDT on
your system, use the editor you have.

Create Accounts and Edit System Start-Up File

105

Terminal Session
This terminal session explains how to edit the DIGITALprovided START.COM command file. First you make a
backup copy of START. COM. Responses in the example
installation are printed in red.

SCOPY [O,lJSTART.COM [O,lJSTART BAK

Explanation - Use the DCL COpy command to make a backup copy of
START. COM. This provides additional protection in case something goes wrong
during your editing session. You can delete the backup version after you successfully
start your system using START. COM.
Response - Type a command in the format shown. The example installation
creates a copy of START.COM named START.BAK in account [0,1].
STYPE [O,lJSTART.COM

Explanation - Use this command to print the START.COM command file at your
terminal. You may· want to study the file before deciding where to make your edits. If
you are not using a hard-copy terminal and want to get a printed copy of
START. COM, type PRINT [O,l]START.COM.
Response - Type the command as shown to list the START. COM file.
SEDIT/EDT [O,lJSTART.COM

Explanation - Use this command to start the EDT editor. The text of the file
appears on your screen. Edit the file according to the needs of your installation. For
more information on EDT, see the Introduction to the EDT Editor and the EDT

Editor Manual.
Response - Type the command as shown. Note that you need the SYSIO and
WWRITE privileges to alter files in account [0,1].

Response - Type EXIT and then press the ENTER key on the keypad when you
are ready to exit EDT.

When you use EDT to edit a file, the monitor replaces the sample file in account
[0,1] with your version.
Go to Phase 7.

106

Create Accounts and Edit System Start-Up File

Pho]se
S'~ari ~S1S/E Moni"ior

This phase describes the tasks you must perform to start your RSTS/E monitor.
The tasks in this phase are:
o Task 1: Shut Down SYSGEN Monitor (SHUTUP)
o Task 2: Start RSTS/E Monitor (START)

These responses have special meaning:
Response

Description

Accept the default response

Obtain an online explanation of the question

107

Task 1: Shut Down SYSGEN Monitor (SHUTUP)
Now that you have built your RSTS/E monitor, you no longer need the SYSGEN
monitor. To shut down your monitor, run the SHUTUP program. Make sure you are
logged in to the console terminal when you run SHUTUP.

Terminal Session
This terminal explains how to use SHUTUP to shut down
your SYSGEN monitor.

$RUN $SHUTUP

Explanation - You are logged in to the console terminal and you see the Del $
prompt on your screen. You can now shut down the SYSGEN monitor.
Response - Type RUN $SHUTUP to shut down the monitor.
SHUTUP V9+0-14 RSTS V9+0-14 SYSGEN
8:19 AM 31-MaY-85
Type

Iftl

########

Set-up Dialogue Phase

to any query to bacKup one question

Minutes until SYsteM shutdown (0-99)

(5)?

Explanation - SHUTUP prints a header and some preliminary information. It then
asks you to type the minutes to wait before the RSTS/E monitor shuts down. This
question is useful for giving system users fair warning when shutting down the system.

108

Start RSTS/E Monitor

Response -

Type O.

6:18 AM 31-MaY-85 ########
Warning Message Phase
Further LOGINs are now disabled

########

6:18 AM 31-MaY-85

########

Initial Job Killing Phase

########

6:18 AM 31-MaY-85

########

ReMove RTS/RES LIB Phase

########

6:18 AM 31-MaY-85

########

SWAP File ReMoval Phase

########

6:18 AM 31-MaY-85

########

DisK DISMOUNT Phase

########

6:18 AM 31-MaY-85

########

Final Shutdown Phase

########

Please wait for SYsteM to re-boot itself
RSTS V8.0-14 SYSGEN (DUO)

INIT V8.0-14

31-MaY-85 - 6:20 AM
Start tiMesharing <Yes)?

Explanation - SHUTUP prints several messages before shutting down your system.
It then returns to the Start timesharing? question. See the RSTSIE System Manager's
Guide for more information on SHUTUP.

Go to Task 2.

Start RSTS/E Monitor

109

Task 2: Start RSTS/E Monitor (START)
In Task 1 you ran the SHUTUP program to shut down the SYSGEN monitor. Now
you need to start your RSTS/E monitor. You must first decide whether to perform
any of these additional preparatory tasks:
• Change monitor defaults (lNIT.SYS DEFAULT option)
• Save system disk onto another disk or tape (lNIT.SYS SAVRES option)

Change Monitor Defaults (DEFAULT Option)
You can set RSTS/E monitor defaults in two ways:
o Accept preselected defaults (START option). INIT.SYS sets defaults for your

RSTS/E monitor and then starts timesharing.
o Set your own RSTS/E monitor defaults (DEFAULT option).

INIT.SYS can determine many of your RSTS/E monitor defaults, based on the
configuration of your system. You can set the others online during timesharing.

110

Start RSTS/E Monitor

Table 9 shows the default settings of your new monitor.
Table 9:

Monitor Defaults
Current Setting

Default

INIT.SYS Settable Defaults
SWAP MAX

32K words

Primary run-time system

RSX

Swap file

SWAP.SYS

Error message file

ERR. ERR

Crash dump file

CRASHSYS, if enough space is present

Extended buffer pool
memory (XBUF)

15% of USER memory is allocated to XBUF, if the total
amount of system memory exceeds 128K words.
Otherwise, 10% of USER memory is allocated to XBUF.
USER memory is memory that is not allocated to any other
entity, such as the monitor or run-time system. The
minimum size of XBUF is 2K words. The maximum size is
496K words.

Small buffer pool memory

The maximum allowed for your system, over and above the
minimum number you specified in Task 6 of Phase 3: 11K
words for PDP-lIs with I&D space; 3K words for PDP-lIs
without I&D space.

System clock

KW11-L Line Time Clock
Online Settable Defaults

Cache cluster size

Magtape labeling

DOS

Date and time format

If the line frequency is 60 Hz, the American standard date
and time format is selected. If the line frequency of the
clock is 50 Hz, the European standard date and time format
(numeric date and 24-hour time) is selected.

Power fail delay

300 seconds

Installation name

The six-character SIL name

If you do not plan to change any of the defaults selected by INIT.SYS, or if the
defaults you do plan to change can be altered on line, then you do not need to use
the DEFAULT option before you start timesharing under your RSTS/E monitor.

Start RSTS/E Monitor

111

On the other hand, if you want to perform any of the following operations, you need
to use the DEFAULT option before you start timesharing:
• Allocate memory for the virtual disk (VIRTUAL suboption of DEFAULT).
• Change the amount of memory allocated to the extended buffer pool (XBUF
suboption of DEFAULT).
• Change the amount of memory allocated to the small buffer pool (BUFFERS
suboption of DEFAULT).
o

Change the primary run-time system (DEFAULT option).

o Change the SWAP MAX (DEFAULT option).

See the Offline Options section of this gUide for a complete description of DEFAULT.
Choose the monitor defaults that are suited to your needs. The example installation
plans to accept the INIT.SYS selected defaults.

Save System Disk Onto Another Disk or Tape (SAVRES Option)
You may want to create a backup copy of your system disk at this time. If so, use the
INIT.SYS SAVRES option to copy your system disk before you start your RSTS/E
monitor. See the Offline Options section of this gUide for a complete description of
SAVRES.
As an alternative to using the offline SAVRES option, you can later use the online
V9.0 BACKUP utility to copy your system disk. See the RSTSIE System Manager's
Guide for more information.
The example installation does not plan to make a backup copy of the system disk at
this time.
If you are ready to start your RSTS/E monitor, continue with this task.
If you need to change the monitor defaults or back up your system disk, answer NO
to the Start timesharing? question. Then go to the Offline Options section before
continuing with this task.

Terminal Session
To start your RSTS/E monitor, you must answer the START
questions. This terminal session lists the START questions,
explains them, and gives you some possible responses. After
you understand the question, type the response at your
console terminal. In some cases, your response will differ
from the response shown in red in the example installation.

Start tiMesharinr? <Yes) START

112

Start RSTS/E Monitor

RST~80

Explanation - This question asks if you are ready to start timesharing. If you
answer YES to this question, INIT.SYS starts the currently installed monitor,
SYSGEN.SIL, and starts timesharing under it. To start timesharing under your new
V9.0 monitor, type START <monitor name>, where <monitor name> is the name
of the new monitor.
If you answer NO to this question, INIT.SYS prints its Option: prompt. You can then
use the INIT.SYS offline options to perform additional preparatory tasks. Finally,
when you are ready to start your RSTS/E monitor, use the INIT.SYS START option.
Response - Type START <monitor name> where <monitor name> is the name
of your new RSTS/E monitor. In the example installation, the response is START
RSTS90 because RSTS90 is the name of the new V9.0 RSTS/E mo"nitor.

If you do not specify a monitor name, START installs and starts the monitor that was
used in the previous timesharing session.
MelrlO f}' allocation table:
OK: 00000000 87K: OOalaOOO
8BK: 00a20000 aa8K: 03370000
512K: oaoooooo -

OOa13777
00a17777
03387777
03777777
End

87K)
1 K)
37BK)
88K)

E}-{EC
RTS (RS}O
USER
)-{BUF
N}-{M

Explanation - START prints the current memory allocation table. Then START
checks that the SWAP.SYS file exists in account [0,1] on the system disk, is large
enough to hold one job at the current SWAP MAX, and is contiguous. If the file does
not exist, START attempts to create SWAP.SYS at the required size. If the file exists
but is not contiguous or large enough, START deletes the current SWAP.SYS file and
attempts to create a new SWAP.SYS file that is both contiguous and large enough
(SWAP MAX * 4). If START cannot find enough free contiguous disk space to create
a minimum SWAP.SYS file, it prints the following error message:
?Not enough contiguous disK space to create MiniMuM SWAP.SYS file

START then attempts to create a SWAP.SYS file that is smaller than the one you
specified yet still meets the minimum requirements. This may take up to one minute.
If START finds it can create a SWAP.SYS file, it prints these messages:
SWAP.SYS can be created if SWAP MAX is reduced to xxK
New SWAP MAX <xxK>?

Press RETURN to accept the default value, indicated by xx in the example. Or enter

CTRL/C to return to the Option: prompt. You can then use the FILE suboption of
REFRESH to create more disk space.
If START cannot ·find enough contiguous disk space to create a minimum SWAP.SYS
file, it prints these messages:
You Must free SOMe disK space to start tiMesharing.
Option:

Start RSTS/E Monitor

113

Use the FILE sub option of REFRESH to create more contiguous disk space.
Re-creatin~

CRASH.SYS file with MiniMuM size of 380 blocKs

Explanation - START now checks that the CRASH.SYS file exists in account [0,1]
on the system disk, is large enough for the installed RSTS/E monitor and extended
buffer pool allocation, and is contiguous. If the file does not exist, START attempts to
create CRASH.SYS at the required size. If the file exists but is not contiguous or large
enough, START deletes the current CRASH.SYS file and attempts to create a new
CRASH.SYS file that is both contiguous and large enough. If START is successful it
prints the previous message. If START is unsuccessful it prints the following error
messages:
?Not

enou~h

conti~uous

disK space to create MiniMuM CRASH.SYS file

Crash dUMP autoMatically disabled

The CRASH.SYS file is important because it protects you from losing information
during a system crash. When a crash occurs, the RSTS/E monitor dumps the contents
of the read/write area of monitor memory into CRASH.SYS. Because the crash dump
facility preserves the state of the system at the time of the crash, CRASH.SYS
contains important diagnostic information. For these reasons, DIGITAL recommends
that you always have crash dump enabled during timesharing.
Therefore, if you see the error message, Crash dump automatically disabled, follow
these steps to enable crash dump:
1.

After you begin timesharing, delete unnecessary files to create more contiguous
disk space. Or, move some files to a nonsystem disk.

Shut down the RSTS/E monitor using the SHUTUP pr9gram.

Use the START option to start timesharing. If you do not see the Crash dump
disabled message, you know that INIT.SYS was able to create the
CRASH.SYS file.

31-Mav-85 08:22 AM
8 devices disabled
Proceed I"lith s}'steITl startup? <YES>

Be~innin~ RSTS/E startup •••
31-Mav-85 08:22 AM
Mountin~ disKs
31-Mav-85 08:22 AM
Assi~nin~ lo~ical naMes
31-Mav-85 08:22 AM
Startin~ error lo~~in~'
31-Mav-85 08:22 AM
SettinS SYsteM characteristics
31-Mav-85 08:22 AM
Installin~ run-tiMe SYsteMS
31-MaY-85 08:23 AM
Settin~ terMinal characteristi~s
31-Mav-85 08:23 AM
Definin~ SYsteM cOMMands
31-Mav-85 08:23 AM
SettinS printer characteristics
31-Mav-85 08:23 AM
Starting spoolers
Print/Batch Services started at 08:23 AM

Explanation - START prints the current date and time and pauses for several
seconds while it performs the necessary tasks to start timesharing. Then START
transfers control to the START.COM command file. START.COM asks if you are

114

Start RSTS/E Monitor

ready to proceed with the start up. Then START. COM prints a message as it enters
each section of commands. See the RSTSIE System Manager's Guide for more
information on the START. COM command file.

Response - Type YES or press RETURN to start timesharing. Or, type NO if you
are not ready to start timesharing. You then see the DCL $ prompt. In the example
installation, the response is RETURN.

*** FrOM [112] on KBO: at 06:23 AM on 31-Mav-85
** RSTS/E is on the air •••
RSTS V8.0-14 31-Mav-85 06:24 AM
Us e r:

Explanation - You are finished with the installation. You can now press RETURN
to log in to the system. RSTS/E then prints its banner followed by the User: prompt.
Phase 8 lists some optional tasks that you may want to perform.
If you plan to install layered products, see the individual layered product installation
guides for instructions.

Start RSTS/E Monitor

115

This phase describes optional tasks you may want to perform to tune your RSTS/E
system to your needs.
The tasks in this phase are:
o Task 1: Reposition System Program Packages

o Task 2: Apply a Mandatory Patch

117

Task 1: Reposition System Program Packages
This task describes the procedures for moving system program packages to another
disk. You may want to perform this task if your system disk is full.
If you have a two disk system and receive your RSTS/E Distribution Kits on disk
distribution, DIGITAL does not recommend that you move any system program
packages to a second disk. During updates you will not have a free drive on which to
mount the second disk.

You selected the system program packages in Phase 4. Then the system installed
each package at the default location on your system disk. The system also associated
a logical name with each package.
Table 10 lists the logical names and default locations of the RSTS/E system programs.
Table 10:

System Program Package Logical Names
Package

. Logical Name

Location

RSX Utilities

LB:

[1,1]
[1,2]

Help

HELP$:

[0,2]

Error

ERROR$:

[0,3]

Update

UPDATE$:

[0,4]
[1,2]

Device Testing

TEST$:

[0,5]

Print/Batch Services (PBS)

PBS$:

[0,6]

File Restore

RESTOR$:

[0,7]

OPSER-based Spooling

OPSER$:

[0,8]

Unsupported Utility

UNSUPP$:

[0,9]

Auxiliary Library

AUXLIB$:

[0,14]

RMS-11

RMS$:

[0,10]

EDT

EDT$:

[0,11]

TECO

TECO$:

[0,13]

SORT/MERGE

SORT$:

[0,15]

You can increase performance by moving the RSX Object Libraries and the Help
packages to a nonsystem disk.

118

Optional Tasks

If you need to free space on your system disk, you should consider moving any of
the following packages to a nonsystem disk: Unsupported Utility, Auxiliary Library,
SORT/MERGE, EDT, Error Reporting, Device Testing, Print/Batch Services,
Opser-based spooling, and RMS-l1.

Terminal Session
This terminal session outlines the procedures you use to
reposition a system program package. For more information
on a particular step in the process, see the manual or the task
and phase referenced.

Step 1: Mount and Initialize a Nonsystem Disk

Mount and initialize the disk on which you intend to reposition the system program
packages. Use the mount procedures described in Task 1 of Phase 2. To initialize the
disk, use the INITIALIZE command. The INITIALIZE dialogue is identical to the
INIT.SYS DSKINT dialogue, which is described in the Offline Options.
Step 2: List the System Logical Names

Type SHOW LOGICAL/SYSTEM/ALL to list the logical names on your system.
Step 3: Create a New Directory

Create a new directory for the system package by typing a command of the format:
CREATE/ACCOUNT/NOUSER dev:[ptpn]

where:
dev:

specifies the new disk

[p,pn]

specifies the new directory. Use the same [p,pn] as the existing directory.

See the RSTS/E System Manager's Guide for more information on the
CREATE/ACCOUNT command.

Optional Tasks

119

Step 4: Copy the Package to the New Location

Transfer the package to the new location by typing a command of the format:

where:
<logical name>*.*

specifies all the files in the current location of the system
program package

dev:[p,pn]*.*

specifies the new location of the system program package.

See the RSTSIE System User's Guide for more information on the COpy command.
Step 5: Reassign the System Logical Name

Deassign the current logical name by typing a command of the format:
DEASSIGN/SYSTEM (logical naMe>

where <logical name> refers to the current logical name you listed in Step 2.
Assign the new logical name by typing a command of the format:
ASSIGN/SYSTEM dev:[ptpn] (logical naMe>

where:
dev:[p,pn]

refers to the new directory you created in Step 3

is the name you listed in Step 2.

----------------------- Note -----------------------

The logical name associated with a system program package is
reserved for use by RSTS/E. If you assign a different name to a
package, you will not be able to update that package in the future.

See the RSTSIE System Manager's Guide for more information on the DEASSIGN
and ASSIGN commands.
Step 6: Point the Logical Name at the New Location

Edit the START.COM system start-up file to point'the logical name at the new
location. See Task 3 of Phase 6 for more information on editing the START. COM file.

,120

Optional Tasks

Step 7: Delete the Old Directory

If you have no further use for the old account, delete the directory by typing a
command of the format:
DELETE/ACCOUNT

[ptpn]

where [p,pn] refers to the old location of the system package on the system disk.
The system then asks if you want to delete the files in the directory. Type YES.

Optional Tasks

121

Task 2: Apply a Mandatory Patch
A ·mandatory patch applies an emergency correction to software that might otherwise
cause a serious malfunction to your system. For example, DIGITAL would issue an
emergency patch to the monitor if in certain instances you could not boot your
system after an installation.
The RSTSIE Software Dispatch contains the latest software changes between releases.
Published monthly, it also contains descriptions of mandatory patches.
You have to apply patches manually if you install:
o Paper patches from articles in the RSTSIE Software Dispatch.

• Patches to non-DIGITAL software.
There are several dangers when you type in a mandatory patch:
• You could enter incorrect values, causing new problems to occur, which you
may not recognize as yours.
• You may not be able to "undo" an incorrect patch because you may not know
the value that was there before you replaced it· with a new value. (Because of
the possibility of errors, you should keep a hard-copy log of patches installed
manually.)
For example, if you entered an instruction incorrectly, the software could fail,
and you may not be able to find the instruction you mistyped. Sometimes the
only way to "undo" a bad patch is to reinstall the distributed version of the
software. In the case of a monitor patch, you would have to do another
monitor installation.
When you use ma~"lUal patching to install a paper patch, follow the directions in the

RSTSIE Software Dispatch, and type exactly what is printed. This way you do not
need to understand fully the commands used' for manual patching. If you catch a
mistake before pressing the RETURN key on each line, you can use the standard
keyboard editing characters, such as CTRL/R, CTRL/U, and the DELETE key.
Furthermore, you can reenter input if you cause an error message and are
reprompted.
You may need to use a RSTS/E program such as ONLPAT to install patches. See
Appendix E for information on RSTS/E patching programs.

122

Optional Tasks

This section summarizes the example RSTS/E system installation. This summary
shows only those points in the installation where you type a command, respond to a
prompt, or take an action. It does not show everything you see on your terminal
during the installation. For more information on a question or procedure, see Part I of
this guide.
Note the use of callouts in the right margin of the example. The purpose of these
callouts is to direct your attention to points in the installation where you are required
to perform an action, such as mounting a tape or disk.
This is only a sample. Your responses and output will probably differ from this
example because your hardware and software requirements are not the same.
Remember that you can type a question mark (?) in response to any question or
prompt to obtain an online explanation.
The example installation has the following characteristics:

• CPU: PDP-11/44
• Memory: 512K words
• System Disk: RA80
• RSTS/E Distribution Kit: 1600 bpi magnetic tape
• Installation Kit: V9. 0

123

Phase 1
Mount V9.0 Installation Media
Bootstrap V9.0 Installation Media

»>B MSO
Enablins only console, disKs, and tapes.
RSTS V9.0

(MSO)

INIT V9.0-14

Phase 2
Mount Target System Disk

Current date <DD-MMM-YY>? 31-May-85
Current tiMe <HH:MM AM/PM>? 05:00 AM
InstallinS RSTS on a nelAI S}'stefrl dis.~? <Yes>

31-MaY-85 - 05:02 AM
Dis.~?

DU
Un it? 0

This disK appears to be a RSTS/E forMatted
disK with the followins characteristics:
Pac., I D:
Pad~ cluster s i z e:
Pac ., is currentl}':

NATHAN
8
Pril.late,
Update access on IAlrites,
Level: 1 • 1

Pad~ ID? SYSDSK
Pad, cluster size <4>?
MFD cluster size <18>?
SATT.SYS base <118595>?
Pre-extend directories <NO>?
PUB, PRI, 0 r SYS <SYS>?
[ 1 , 1] c Ius' t e r s i z e < 1 8 >?
[1,2] cluster size <18>?
[1,1] and [1,2] account base <118595>?
Date last frlodified <YES>?
NelAI files first <NO>?
Read-onl}' <NO>?
Use prel.liOtlS bad blod, info <YES>?
Patterns <3>?

m
m

m
m
m

m
m

(continued on next page)

124

System Installation Example

Proceed (Y or N)? Y
31-MaY-85 - 05:17 AM
Enablin~

only console, disks, and tapes.

RSTS V8.0 (DUO)

IN IT V8.0-14

Start tiITlesharin~? <Yes>
Startin~ SYSGEN.SIL • • •
Rebootin~ • • •
RSTS V8.0 (DUO)

INIT V8.0-14

31-MaY-85 - 05:17 AM
Creatin~

SWAP.SYS file with MiniMuM size of 128 blocks

MeMOry allocation table:
OK:
66K:
67K:
462K:
512K:

00000000 - 00407777
00410000 - 00413777
00414000 - 03467777
03470000 - 03777777
04000000 - End

Creatin~

66K)
1 K)
385K)
50K)

E)-{EC
RTS (RS>{ )
USER
XBUF
NXM

CRASH.SYS file with MiniMUM size of 320 blocks

31-MaY-85 - 05:18 AM
8 devices disabled
Do }'OU . . Iant to perforlTI an installation or an update? <installation>

Phase 3
PI.ease Mount the RSTS/E Installation Media and enter the naMe
and unit nUMber of the device.
I,lalid device t}'pes are: 'MM', 'MS', 'MT', 'OM' or 'DL'
Installation device: MSO
Restorin~

Deletin~

31-MaY-85

required _SY:[O,IJ COMPonents
all

~lobal

SYMbols

5:21 AM

Be~innin~

of the RSTS/E Software Installation Procedure

Type '?' for help
Type ,A, to ~o back to the previous question
Type CTRL/Z to return to the be~innin~ of the present section

* Startin~ dialo~ue phase *
Are }'OU ready to proceed? <}'es)

Please enter the naMe and unit nUMber of the disk to
which YOU want to install the software. This disk
should be physicallY Mounted and write-enabled.

(continued on next page)

System Installation Example

125

Tar set dis ~~? < _SY: > :

Restorins requi red SY: [1 t2J CO/rlPonents
Assisnins SYsteM losicals

** Startins Monitor Section **
Do }'OU 1"lant to install the RSTS/E Irlonitor? <}'es>

Restorins required SYSGEN COMPonents
Use teMPlate Monitor? <N> NO
New Monitor naMe? <RSTS> RSTS80
Accept defaults? <N> m
Now YOU MUSt specify the hardware confisuration on which this RSTS/E SYsteM
",Jill run.
The followins questions deal with the
nUMbers arid types of terMinal interfaces
on the s}'stelrl.
Accept terlrlinal defaults ?
DLllA cOlrlPatible lines ?
DLllCt DLllD's ?
DLllEt DLl.lllE's ?
DJ 11 ' s ?
DH 11 ' s ?
DZll IDZ 1.J11 IDZQ 11' s ?
DZll unit 00 lines enabled ?
DZll unit 01 lines enabled ?
DZll unit 02 lines enabled ?
Dataset support for DZ 11 ' s ?
DHU 11 ' s ?
DHUll unit 00 lines enabled ?
Dataset support for DHU 11 ' s ?
Pseudo ~~e}'boards ?
Mu I t i - t e rlrl ina I serl.Jice ?
Echo control ?
One-line status report ?
FMS-ll sUPPO rt ?
Multiple pril.late delilrliters ?

m
m
m
m
m
m
m
m
m
m
m
m
m
m
6
<1' .. m
m
><Y > m
<N .'. m
<N >- m

<N >
<01>
<00>
<00>
<00>
<00>
<03>
<08>
<08>
<08>
<N >
<01>
<16>
<N ><oa>
'

",-\/

The followins questions deal with the
nUMbers and Kinds of disK units on this
S}'stelrl.
Accept DisK defaults ?
RK05's ?
RL01/RL02's ?
RK06/RK07's ?
Overlapped see ~~ ?
RP02/RP03's ?
NU/rlb e r of dis ~~ s on DR controller ?
NU/rlber of dis ~~ s on DB controller ?
MSCP controllers ?

m
m
m
m
m
m
m
m
m

The following questions deal with the
peripheral devices attached to this
RSTS/E s}'steITI.
(continued on next page)

126

System Installation Example

m
m
(01»
m
<01> m
<00> m
<01> m
<00> m
<N > m
<N > m
<N > m
<y > N
<00> m
<00> m
<'I' > m
<N > m

Accept Peripheral defaults ?
TU16/TE16/TU45/TU77 / s ?
TU10/TE10/TS03 / s ?
TSll./TK25/TSV05/TUBO / s ?
DECtapes ?
Printers ?
R}{O 1/ R}{02 IS ?
CRll/CMll card reade r ?
CDll card reader ?
P. T. reader/punch ?
DECnet netl"IO d, support ?
DMCll / s/Dl'lRll / s ?
KMCll / s ?
Extended bufferins' for LP ?
RJ27BO suppo rt ?

The followins' 9uestions deal with the
capacity and features of this RSTS/E
SYsteM provided at the SYsteM Manas'er1s
option.
<N > m
<25> 40
<440> 550
<N :::- m
<N > m

Accept Software defaults?
MaxiiTluiTl jobs?
SiTlall buffers?
Monitor statistics?
EMT 10s's'ins' ?
Data cachins' ?

<N >

** End of Monitor Section **
Phase 4

** Startins' SYsteM Pros'raMs Sections **
Do )'01.1 1"lant to install the S)'steiTl Pros'raiTl pad,as'es? <)'es>

Packas'es to install: ?
The valid responses are:
DIALOGUE
ALL
ALLtNop~,s'[ t ••• ]

Switches YOU to the Ions' forM of the SYsteM
Software PacKas'es dialos'~e where a More
detailed description of each pacKas'e is provided
Selects all pacKas'es
Selects all pacKas'es except pKs'

Use a COMMa as a separator. e.s'.: RSXtPBStRMS
Pad,as'e naiTles:
AU}-{L I B
BASIC
DAP
EDT
HELP
oPSER
PBS
RESTORE

Auxilian' Libran'
Basic-Plus
RMS DECnet Data Access Pad,as'e
(,i n c 1 Udes Rl'lS-11)
EDT Editor
Help Pac~,as'e
opser-based Spooler
Print/Batch Services
File Restore

RMS
RSX
SORT
TECo
TEST
UNSUPP
UPDATE

RMS-ll
(includes RS}-{ Utilities)
RS}{ Utilities
Sort/Mers'e
(includes RMS-ll)
TECo Editor
Del.lice Testins'
Unsupported Utilities
Update Pad,as'e

Packas'es to install: ALLtNoDAPtNoUNSUPPtNoSoRT

(continued on next page)

System Installation Example

127

The followinf will be installed:
RS}-{
RMS
PBS
EDT
UPDATE
TEST
TECO
AU}-{LI B
RESTORE
OPSER
HELP
BASIC
Proceed? <}'es> 00
Do }'OU ',,'ant the I&:D versions of tas~\s? <no>

Use resident librar>' ~lersion of RMS? <}'es> 00
Use RMS resident libraries in PBS? <}'es> 00
Use resident librar>' l.lersion of EDT? <}'es> 00
Durinf the build phase there will be further questions
for BASIC-PLUS.

** End of SYsteM ProfraMs Section **
** Startinf Layered Products Section **
Do you want to transfer the layered product update COMPonents
froM the Installation Kit? <Yes> NO

** End of Layered Products Section **
Phase 5
You Must now set the password for account _SY:[1 ,2J
Ne',,' pass',,'o rd:
New password afain, for verification:
Pass',,'o rd set fo r account _SY: [1 ,2]

* End of dialofue phase *
* Startinf build phase *
Are }'OU read}' to proceed? <}'es> 00
31-MaY-85

05:31 AM

Do }'OU ',,'ant _SYO:SWAP1.SYS created? <}'es> 00
Creatinf _SYO:[O,IJSWAP1.SYS at 4882 blocKs
31-MaY-85

05:32 AM

Creatinf RSTS/E Monitor
This Monitor will fit OK
(continued on next page)

128

System Installation Example

31-May-S5

05:4S AM

Th ere are
There are
There are
There are
There are
Restoring
Restoring
Restoring
Th ere are
There are
There are
There are
There are
There are
There are
Restoring
There are
Restoring

no updates for the SysteM Startup files
no updates for the SYsteM Library PacKage
no updates for the Error PacKage
no updates for the RSX Libraries
no updates for the RSX Utilities
the RMS-ll pacKage froM the Installation Kit
the RMS Libraries froM the Installation Kit
the Print/Batch Services pacKage froM the Installation Kit
no updates for the EDT pacKage
no updates for the Update pacKage
no updates for the Device Testing pacKage
no updates for the TECD pacKage
no updates for the Auxiliary Library pacKage
no updates for the File Restore pacKage
no updates for the Dpser-based Spooling pacKage
the Help pacKage frOM the Installation Kit
no updates for the BASIC-PLUS pacKage
the Resident Libraries frOM the Installation Kit

31-May-S5

05:52 AM

Please Mount the RSTS/E Library Media and enter.the
naMe and unit nUMber of the device.
I.lalid del.Jice t}'pes are: 'MM't 'MS't 'MT't 'DM' or 'DL'
Dismount V9.0 In?tallation Media
Mount V9 Library Media

Libran' del.lice <_MSO:> ru
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring
Restoring

the
the
the
the
the
the
the
the
the
the
the
the
the
the
the
the
the
the

SYsteM Startup files frOM the Library Kit
SYsteM Library pacKage frOM the Library Kit
Error pacKage frOM the Library Kit
RSX Libraries frOM the Library Kit
RSX Utilities frOM the Library Kit
RMS-ll pacKage frOM the Library Kit
RMS Libraries frOM the Library Kit
Print/Batch Services pacKage frOM the Library Kit
EDT pacKage frOM the Library Kit
Update pacKage frOM the Library kit
Device Testing pacKage frOM the Library Kit
TECD pacKage frOM the Library Kit
Auxiliary Library pacKage frOM the Library Kit
File Restore pacKage frOM the Library Kit
Dpser-based Spooling pacKage frOM the Library Kit
Help pacKage frOM the Library Kit
BASIC-PLUS pacKage frOM the Lib~ary Kit
Resident Libraries frOM the Library Kit

(continued on next page)

System Installation Example

129

31-MaY-85

06:06 AM

Installing software packages
31-MaY-85

06:10 AM

Beginning of RSTS/E Basic-Plus generation.
BASIC-PLUS RTS nalTle? <BASIC)
FPP? <Y)
Math precision? <02) 4
Log functions? <Y)
Trig functions? <Y> m
Print using? <Y)
Matrices? <NO> Y
String arithlTletic? <NO) m

ru
m

* End of build phase *
The RSTS/E Software Installation Procedure is cOMPlete
Deleting all global SYMbols
Deassigning SYsteM logicals
31-MaY-85 06:17 AM
SYsteM tape label default set to DOS
SY:[1 t2]INSTAL.LOG is a log file of this session
$

Phase 6
$ CREATE/ACCOUNT [1 t4] /PR!l.IILEGES=ALL m
Passl"lo rd:
Password againt for verification:
Account _SYO:[1 t4] created at DCN 27345

Phase 7
$RUN $SHUTUP
SHUTUP V8.0-14 RSTS V8.0-14 SYSGEN
6:18 AM 31-MaY-85
Type

Iftl

########

Set-up Dialogue Phase

########

to any query to backup one question

Minutes until SYsteM shutdown (0-88) <5)? 0
6:18 AM 31-MaY-85 ########
Warning Message Phase
Further LOGINs are now disabled

########

6:18 AM 31-Mav-85

########

Initial Job Killing Phase

########

6:18 AM 31-Mav-85

########

ReMove RTS/RES LIB Phase

########

6:18 AM 31-MaY-85

########

SWAP File ReMoval Phase

########

(continued on next page)

130

System Installation Example

6:18 AM 31-MaY-85

########

Disk DISMOUNT Phase

########

6:18 AM 31-MaY-85

########

Final Shutdown Phase

########

Please wait for SYsteM to re-boot itself
RSTS V8.0-14 SYSGEN (DUO)

INIT V8.0-14

31-MaY-85 - 6:20 AM
Start

tiMesharin~

<Yes)? START RSTS80

MeMOry allocation table:
OK:
67K:
68K:
446K:
512K:

00000000 - 00413777
00414000 - 00417777
00420000 - 03367777
03370000 - 03777777
04000000 - End

R~-creatin~

67K)
1 K)
378K)
66K)

E}{EC
RTS (RSX)
USER
}{BUF
N}{M

CRASH.SYS file with MiniMUM size of 380 blocks

31-MaY-85 - 06:22 AM
8 devices disabled
Proceed I"lith S}'stelrl startup? <YES)

Be~innin~ RSTSIE startup •••
31-MaY-85 06:22 AM
Mountin~ disKs
31-MaY-85 06:22 AM
Assi~nin~ lo~ical naMes
31-MaY-85 06:22 AM
Startin~ error lo~~in~
31~May-85 06:22 AM
Setting SYsteM characteristics
31-MaY-85 06:22 AM
Installin~
run-tiMe SYsteMs
31-MaY-85 06:23 AM
Setting terMinal characteristics
31-MaY-85 06:23 AM
Definin~ SYsteM cOMMands
31-MaY-85 06:23 AM
Setting printer characteristics
31-MaY-85 06:23 AM
Startin~ spoolers
Print/Batch Services started at 06:23 AM

*** FroM [1 t2J on KBO: at 06:23 AM on 31-MaY-85
** RSTSIE is on the air •••
RSTS V8.0-14 31-MaY-85 06:24 AM
Us e r:

System Installation Example

131

~nsialling RS1S/lE V9.0 On OJ Pre-V9.0 Sys1em

Upgrading a previous version of RSTS/E (V7.2, V8.0, or earlier) to RSTS/E version
9.0 is similar to building a new RSTS/E monitor, which is described in Part I of this
gUide. Part II of this guide outlines a number of tasks you perform to upgrade a
previous version of RSTS/E to version 9.0,9.1,9.2, and so forth. You should be
familiar with the following V8.0 INIT.SYS program options, which are discussed in
the V8.0 RSTSIE System Generation Manual:
• SET LIST
• HARDWR LIST
• DEFAULT
• START
Figure 3 is a flowchart that outlines how to do a system installation to upgrade an
existing RSTS/E monitor. Keep the flowchart handy when you are performing the
upgrade.

133

4.
Collect
distribution kits
and documentation

List status of
all devices

5.
Check distribution
kit order
numbers

SHUTUP

SET LIST

Physically mount
the RSTS
V9.0
Installation tape
or disk

HARDWR LIST

Shutdown
RSTS/E monitor

Restore selected
accounts from
backup tape or disk
to new system disk

Remove old
system disk and / or
backup tape or disk

SAYRES
SET/ACCOUNT

List hardware
configuration
table

BACKUP (V9.0)
No

Physically and
logically mount
V8.0 system disk

Make copy of
system disk

Establish account
quotas, privileges
(after last step)

Perform Phase 7
and, optionally,
Phase 8
(See Part I)

DEFAULT LIST
Check defaults
on old system disk
and list memory
allocation table

Bootstrap V9.0
Installation tape
or disk

Perform Phases
2 through 6
(See Part I)

Bootstrap
V9.0 Installation
tape or disk

Answer preliminary
INIT. SYS.
questions (See
step 3 on page 138)

Option 1

CREATE/ACCOUNT

DSKCVT

Recreate
selected
accounts

Convert disk
to RDS1.2 format

COpy

BACKUP (V9.0)

Copy selected
accounts to V9.0
system disk

Back up selected
accounts to
backup tape or
disk

START
Start SYSGEN
monitor
(See step 4 on
page 138)

BACKUP (V9.0)
Restore selected
accounts to
V9.0 system disk

BACKUP (V9.0)
Back up selected
accounts to
tape or disk

MK-01606-00

Figure 3:

System Upgrade Flowchart

Installing RSTS/E V9.0 On a Pre-V9.0 System

135

Follow these steps to upgrade your system:

Preliminary Steps

Collect distribution kits and documentation. (See Task 1 of Phase 1 in Part I of
this gUide.)

Check distribution kit order numbers. (See Task 2 of Phase 1 in Part I of this
gUide.)

Shut down your RSTS/E monitor, using the SHUTUP system program.

Use the LIST suboption of SET to list all of your devices. This list may be
useful when you specify device characteristics on your new system disk.

Use the LIST sub option of HARDWR to list the hardware configuration table.
The hardware configuration table may be useful when you specify hardware
characteristics on your new system disk.

Use the DEFAULT option to check the defaults of your old monitor. When you
get to the Any memory allocation changes? prompt, answer YES. Then use the
memory allocation table suboption LIST to list the current memory allocation
table. Exit from the memory allocation table sub options and complete the
DEFAULT questions. You can use these lists to help you establish defaults and
make changes to the memory allocation table for the new system disk.

Physically mount your RSTS/E V9.0 Installation tape or disk. (See Task 2 of
Phase 1 in Part I of this guide for instructions and an example of how to mount
the Installation media.) If you do not have multiple removable disk drives, you
should wait until Step. 2 of the next section to mount the Installation media.

If you do not have multiple removable disk drives, continue with the next section, No
Multiple Removable Disk Drives. If you have multiple removable disk drives, go to
the section, Multiple Removable Disk Drives.

No Multiple Removable Disk Drives
This section lists the steps you perform if your system does not have multiple
removable disk drives.
Note----------Though these upgrade steps may seem unorthodox, they provide the
best method for you to recreate your current accounts on your V9.0
system. However, do not use these procedures until you have made a
copy of your system disk (see Step 1).

Installing RSTS/E V9.0 On a Pre-V9.0 System

137

Use the SAVRES SAVE option of INIT.SYS to make a copy of your system
disk. See the Offline Options section for more information.

Bootstrap your RSTS/E V9.0 Installation tape or disk. (See Task 2 of Phase 1
in Part I of this gUide for instructions and an example of how to bootstrap the
installation media.)

INIT.SYS prompts for the date and time, and then asks the following questions.
Type the response as indicated:
Installing RSTS on a new SYsteM disK <Yes)? NO
Are YOU updating an existing RSTS SYsteM disK <Yes)? YES
To which disK? current SYsteM disK

-After you answer these questions, INIT.SYS performs a COpy operation to
transfer the components you need to perform the installation. One of these
components is the V9.0 BACKUP program.
4.

Answer START SYSGEN to the Start timesharing? question. This starts the
SYSGEN monitor, a prebuilt monitor supplied by DIGITAL.
The installation cannot continue at this point because your disk is not yet
RDSI.2 format and therefore RSTS/E mounted your disk read-only. You see a
number of DCl errors, followed by the $ prompt. You are now running under
the SYSGEN monitor, with DCl as the keyboard monitor.

Physically mount a backup tape or disk. Then use the V9.0 BACKUP program
to do a full backup of your system. Use a command of the format:
BACKUP/ACCOUNT/FilE [*,*]*.*/EXClUDE= [O,I]*.SYSxx:OlDSYS.BCK
You may want to include the INOlIST qualifier to suppress the listing of
backed-up files.
See the RSTS/E System Manager's Guide for more information on BACKUP.

When BACKUP completes, reboot your Installation tape or disk. Use the
hardware bootstrap loader on your PDP-II to halt the system and boot the
media. (At this point you do not need to run SHUTUP, since your disk is
mounted read-only.) See Task 2 of Phase 1 in Part I of this guide for
instructions and an example of how to bootstrap the installation media.

See Part I of this gUide and perform all of the tasks associated with Phases 2
through 6. This time answer the questions correctly as if you are performing a
new installation.

Mount your backup tape or disk and use the RESTORE command to restore
the accounts you 'saved earlier to your new system disk. Use a command of the
format:
RESTORE/ACCOUNT/FIlEINOREPLACE xx: = OlDSYS.BCK [*,* ]*.*

138

Installing RSTS/E V9.0 On a Pre-V9.0 System

You may want to include the /NOLIST qualifier to suppress the listing of
restored files.
Note that when BACKUP restores account [1,2] it changes the password back
to whatever it was in VS. O.
9.

Remove your backup tape or disk.

10.

See Part I of this guide and perform all of the tasks associated with Phase 7
and, optionally, Phase S.

11.

The last step uses the SET ACCOUNT command to establish V9.0 quotas and
privileges. Use the following command format:
SET ACCOUNT [l,*]/JOB=a/DETACH=b/INQUOTA=cIPRIV = (ALL,NOSYSMOD,NOEXQTA}/NOEXPIRE
SET ACCOUNT [2-254, *]/JOB = w/DETACH = xllNQUOTA = y/NOEXPIRE
You may want to use other qualifiers such as IPRIV to set different account
privileges, or /NAME = to set the accounts name. The above commands (with
appropriate values for a,b,c,w,x,y} make your accounts VS.O compatible. See
the RSTSIE System Manager's Guide for more information on SET
ACCOUNT.

Multiple Removable Disk Drives
This section lists the steps you perform if your system has multiple removable disk
drives.
1.

Physically mount and bootstrap your RSTS/E V9.0 Instc;lllation tape or disk.
(See Task 2 of Phase 1 in Part I of this gUide for instructions and an example
of how to mount and bootstrap the installation media.)

See Part I of this gUide and perform all of the tasks associated with Phases 2
through 6.

Physically and logically mount your original system disk. You can then create
accounts on your new system disk with one of two options:
Option 1:
a.

Recre9-te selected accounts on your new system disk, using the
CREATE/ACCOUNT command. See the RSTSIE System Manager's Guide
for instructions on how to use CREATEIACCOUNT.

After you recreate all of your selected accounts, GOpy the accounts from
your old system disk to your new system disk, using the COpy command.
Use the /NOREPLACE qualifier to ensure that it does not copy a file that
already exists. See the RSTSIE System User's Guide for instructions on
how to use COpy.

Installing RSTS/E V9.0 On a Pre-V9.0 System

139

Option 2:
a.

Use the DSKCVT program to convert your old system disk to RDS1.2
format. See Appendix E for instructions on how to use DSKCVT.

Back up selected accounts to a tape or disk using the BACKUP (.lJ9.0)
program. To copy all the accounts, type a command of the format:
BACKUP/ACCOUNT/FILE [*,*]*.4EXCLUDE= [O,l]*.SYS xx: OLDSYS.BCK
You may want to include the INOLIST qualifier to suppress the listing of
backed-up files.
See the RSTS/E System Manager's Guide for more information on
BACKUP.

Restore selected account to your V9.0 system disk using the RESTORE
command of the BACKUP program. To restore all accounts, type a
command of the format:
RESTORE/ACCOUNT/FILEINOREPLACE xx:OLDSYS.BCK [*,*]*.*
You may want to include the INOLIST qualifier to suppress the listing of
restored files.

140

Remove your old system disk (if used) and backup tape or disk.

See Part I of this gUide and perform all of the tasks associated with Phase 7
and, optionally, Phase 8.

Installing RSTS/E V9.0 On a Pre-V9.0 System

You can use the INSTAL. COM command file to perform an online RSTS/E installation, without disturbing your existing system.
You used the INSTAL.COM command file to perform your original V9.0 installation.
INSTAL. COM resides in account [0,1]. You can also use it to:
o Generate a new monitor
o Install one or more system program packages
o Install· layered products (integrated layered products only)
o Transfer layered product updates to your system
o Perform a full installation

---------------------- Note ----------------------

You cannot perform an online system installation to build a V9. 0
RSTS/E monitor from a V8.0 or earlier monitor.

In order for the installation to succeed, you must be logged in to an account with the
following privileges: MOUNT, INSTAL, TUNE, WREAD, WWRITE, and WACNT. In
addition, if you have DATES privilege, the creation date of the new files will be the
date the files were placed on the installation kit. If you do not have DATES privilege,
the file creation date will be the current date.

141

To access INSTAL. COM, type a command of the following format:
@[O,I]1NSTAL function [package,; .. ]
where:
@[O,I]1NSTAL

invokes the INSTAL. COM command procedure.

function

specifies the operation to perform. Legal functions are: ALL (the
default), MONITOR, SYSTEM_PROGRAMS, and
LAYERED _PRODUCTS.

[package, ... ]

specifies the software package(s} to install when performing a
SYSTEM_PROGRAMS, LAYERED_PRODUCTS, or
COPYUP operation (see Table II). See Task 1 of Phase 4 in
Part I for a complete list of RSTS/E system program packages.
See Task 2 of Phase 4 in Part I for a list of layered products.

INSTAL.COM Entry Points
When you use INSTAL. COM to perform an installation, you enter the installation
process at different points depending on the command format. Table' 11 lists the
INSTAL. COM commands and the resulting entry points into the installation process.
See the appropriate Phase and Task in Part I for details on the actual installation
procedures.
When you use INSTAL. COM to perform an online installation, you first see this
question:
Please Mount the Installation Media and enter the naMe
and unit nUMber of the device.
Valid device types are: 'MM', 'MB', 'MT', 'OM', 'OL' or 'BY'
(a response of BY allows Monitor only)
Installation device:

This question prompts you tomotint the Installation tape or disk and specify its
location. See the example later in this section if you need help answering this
question.
Table 11 lists the INSTAL. COM commands and the resulting entry points into the
installation process.

142

Performing an Online System Installation

Table 11:

INSTAL.COM, Entry Points

Command

Installation
Entry Point

Comment

@[O,l]lNSTAL

Phase 3, Task 1

Performs new installation
(same as INSTAL ALL).

@[O,l]lNSTAL ALL

Phase 3, Task 1

Performs new installation (the
default).

@[O,l]lNSTAL SYSTEMFROGRAMS

Phase 4, Task 1

Begins system program
installation questions.

@[O,l]lNSTAL
SYSTEMFROGRAMS [pkg, ... ]

Phase 5, Task 3

Installs specified package
while preserving existing
software packages.

@[O,l]lNSTAL MONITOR

Phase 3, Task 1

Begins monitor installation
section. Skips system
program and layered product
sections.

@[O,l]lNSTAL
LAYERED~RODUCTS

This function is available only
to integrated layered
products. Use this function
only if you are directed to do
so by a specific layered
product installation guide.

@[O,l]lNSTAL
LAYERED~RODUCTS [pkg, ... ]

This function is available only
to integrated layered
products. Use this function
only if you are directed to do
so by a specific layered
product installation guide.

@[O,l]COPYUP

Phase 4, Task 2

Begins dialogue to transfer
layered product updates from
the Installation kit

@[O,l]COPYUP [pkg, ... ]

Phase 5, Task 3

Transfers specific layered
product updates from the
Installation kit.

,Performing an Online System Installation.

143

Online Installation Example
This example uses INSTAL. COM to install the RSX system program package. BeforE
you run INSTAL. COM, you must mount the Installation media. Mount the tape or
disk on a free drive. Follow the tape or disk mount instructions in Task 2 of Phase 1
in Part I.
$

@[O,lJINSTAL SYSTEM_PROGRAMS RSX

* Startin~ dialo~ue phase *
Please Mount the RSTS/E Installation Media and enter the naMe
and unit nUMber of the device.
Valid device types are: 'MM', 'MS', 'MT", 'OM', 'OL' or 'SY'
(a response of SY allows Monitor only)
Installation device: MMO:
Please enter the naMe and unit nUMber of the disK to
which you want to install the software. This disK
should be physicallY Mounted and write-enabled.
Tar~et

disK? <SY:> :

Assi~nin~

The

SYsteM

followin~

®ill

lo~icals

will be installed:

RSX
Proceed? <Yes>
00

®ill

)'OU want the 1&:0 versions of tas.'s? <no>

* End of dialo~ue phase *
* Startin~ build phase *
31-MaY-85 11:43 AM
Restorin~

Restorin~

the RSX Libraries froM the Installation Kit
the RSX Utilities frOM the Installation Kit

31-May-85 11:45 AM
Please Mount the RSTS/E Library Media and enter the
naMe and unit nUMber of the device.
Valid device types are: 'MM', 'MS', 'MT', 'OM' or 'OL'
Library device <MMO:> :
Restorin~
Restorin~

the RSX Libraries froM the Library Kit
the RSX Utiliti~s frOM the Library Kit

31-MaY-85 11:49 AM
(continued on next page)

144

Performing an Online System Installation;

Installing software packages

'* End of build phase *
Deleting all global SYMbols

31-MaY-85 11:50 AM

SYsteM tape label default set to DOS
SY:[I,ZJINSTAL.LOG is a log file of this session
$

You have successfully installed the RSX package on your system. Type DIR RSX$: to
list the files in the directory.

Performing an Online System Installation

145

U[odoriing 0] RS1S/[E V9.0 Sys~em

Part IV describes how to update a RSTS/E V9.0 system to a new release.
DIGITAL supplies an Installation Kit with each new release of RSTS/E. After V9.0,
subsequent kits are labeled in numeric sequence. For example, the first kit distributed
after the V9.0 release is called V9.1; the second kit is V9.2.
Each new Installation Kit contains new software features as well as updates to existing
software. In addition, the kit may contain mandatory corrections to RSTS/E software.
The contents of each Installation Kit are cumulative. This means that each new
installation kit includes updates from all previous kits, as well as any new ones. For
example, the V9.3 Installation Kit would include all features of the V9.0, V9.1, and
V9.2 kits.
Each new release of RSTS/E also contains the RSTSIE Release Notes. The RSTSIE
Release Notes describes new features of RSTS/E and explains differences between
the latest version and previous version. Read the RSTSIE Release Notes before
performing a system update.

Structure of Part IV
Part IV divides the system update into five phases plus one optional phase, each
consisting of one or more task{s).
For convenience, a summary of all the tasks in a phase appears at the start of that
section. The option, program, or command file you use in a task (such as DSKINT or
COPY) appears in parentheses next to the task.
The contents of each phase follow:

Phase 1: Geffing Started
Explains how to make backup copies of your system disk and shut down your current
monitor.

147

Phase 2: Prepare System

Describes how to mount your Installation media, copy files to your system disk, and
start the SYSGEN monitor.
Phase 3: Configure New Monitor

Explains how to use information from a template monitor to configure your new
monitor. It also explains how to answer the software update questions.
Phase 4: Generate RSTS/E System

Explains how to create the new RSTS/E monitor. It also describes how to update
system programs and layered products.
Phase 5: Start New Monitor

Explains how to shut down the SYSGEN monitor and start the new RSTS/E monitor.
Phase 6: Optional Tasks

Explains how to use the UPDATE. COM command procedure to perform a selective
update.

System Update Flowchart
Figure 4, the System Update Flowchart, summarizes how to update a V9.0 RSTS/E
system. You may want to use this flowchart while you perform the update.

148

Updating a RSTS/E V9.0 System

PHASE 1
Getting Started

Task 1

PHASE 3
Configure New Monitor
and Select
Software Updates

PHASE 2
Prepare System

PHASE 4
Generate New
System

PHASE 5
Start New
Monitor

Task 1

BACKUP

Task 1
Physically
mount and
bootstrap
Installation media

Back up
system disk

Task 2

COpy

Shut down
SYSGEN monitor

BACKUP
Back up
nonsystem disk

Physically
mount
nonsystem disk

SHUTUP

INIT.SYS

Tasks 1-2
Copy files
to system disk

Assign system
logicals

Answer
configuration
questions

Perform
offline options

HARDWR
SHUTUP

START
Perform
hardware-related
tasks

Shut down
current monitor

Start RSTS/E
monitor

MK-01607-00

Figure 4:

System Update Flowchart

Updating a RSTS/E V9.0 System

149

Pho]se
G9~)·~ing SI~C~r{eo]

This phase describes the tasks you must perform to prepare for a RSTS/E system
update. In order for the update to succeed, you must be logged in to an account
with the following privileges: SHUTUP, MOUNT, WREAD, WWRITE, WACNT,
INSTAL, and TUNE. In addition, if you have DATES privilege, the creation date
of new files will be the date they were placed on the Installation media. If you do
not have DATES privilege, the creation date will be the current date.
The tasks in this phase are:
o Task 1: Back Up System Disk (BACKUP)
o Task 1A: Back Up Nonsystem Disk (BACKUP)
o Task 2: Shut Down Current Monitor (SHUTUP)

151

Task 1: Back Up System Disk (BACKUP)
In this task you use the RSTS/E BACKUP utility to make a backup copy of your
system disk. (See the RSTSIE System Manager's Guide for a full description of
BACKUP.)
This example backs up a RABO system disk to 1600 bpi tape, mounted on a TU77
tape drive.
$

BACKUP DUO:[*,*J*.* MMO:SYSBAK

Explanation - You see the DCL $ prompt. Type a ~ommand of the format:
BACKUP <input-file-spec> <output-file-spec>
where:
BACKUP

invokes the RSTS/E BACKUP utility

<input-file-spec>

specifies the disk, accounts, and files to back up

<output-file-spec>

specifies the disk or tape on which to copy the data, and
the save set name

Response - Type an appropriate BACKUP command line for your system. The
example BACKUP command line backs up all files in all accounts on the system disk
(DUO:) to a magnetic tape mounted on drive MMO:.
Please Mount volUMe 1 of BacKup set SYSBAK.BCK
Where can this voluMe be located? (MMO:/NOINITIALIZE> MMO:/INITIALIZE

Explanation - BACKUP asks for the location of your save set volume. BACKUP
prints the device deSignator you specified in the command line as the default answer
(MMO in this example).
Response - Type the device designator and unit number of the drive on which the
output volume is mounted. If you want to initialize the tape, append IINITIALIZE to
your response. In the example, the response is MMO:/INITIALIZE.

152

Go to Task 1A if you want to back up your nonsystem disk(s}.

Go to Task 2 if you do not want to back up your nonsystem disk(s}.

Getting Started

Task 1A: Back Up Nonsystem Disk (BACKUP)
You should perform this task if you intend to update system prograp1s and you have
moved any system programs packages to a nonsystem disk.
To back up your nonsystem disk, follow the procedl..lres described in Task 1.

Go to Task 2.

Getting Started

153

Task 2: Shut Down Current Monitor (SHUTUP)
In this task, you run the SHUTUP program to shut down your current monitor. To
run SHUTUP, you must have SHUTUP privilege and be logged in to the console
terminal.

Terminal Session
This terminal session shows how to run SHUTUP to shut
down your system.

$RUN $SHUTUP

Explanation - You are logged in to the console terminal and see the DeL $
prompt on your screen. You can now shut down the current monitor.
Response - Type RUN $SHUTUP to shut down the monitor.
SHUTUP V8.0-14 RSTS V8.0-14 (Monitor naMe)
11:55 AM 31-MaY-85
Type

IAI

########

Set-up DialoSue Phase

########

to any query to backup one question

Allow Print & Batch entries to cOMPlete (YES/NO) <Yes)?

Explanation - SHUTUP prints a header and some preliminary information.
SHUTUP then asks you whether to allow print and batch entries to complete.
Response - Type YES or press RETURN to allow the entries to complete. Type
NO to shut down the print and batch queues immediately.
Minutes until SYsteM shutdown (0-88) (5)?

Explanation - SHUTUP asks you to type the minutes to wait before the RSTS/E
monitor shuts down. This question is useful for giving system users fair warning when
shutting down the system.

154

Getting Started

Response - Type a number from 0 to 99. Or, press RETURN to accept the default
of 5 minutes.
11:55 AM 31-Mav-85 ########
Further LOGINs are now disabled
11:55 AM 31-Ma}'-85

Warnin~

Messa~e

Initial Job

Phase

########

Phase

########

11 : 55 AM 31-Mav-85 ########
Print/Batch Shutdown Phase
Print/Batch Services shutdol..Jn cOIT1PIete at 11:55 AM.

########

Killin~

11:55 AM 31-Mav-85

########

11 : 55 AM 31-Mav-85

########

, EI)TLOG , Shutdown Phase
, ERRCPY , Shutdol..Jn Phase

11:55 AM 31-Ma}'-85

########

Relrlove RTS/RES LIB Phase

########

11:55 AM 31-Ma}'-85

########

SWAP File RelTloval Phase

########

11:55 AM 31-Mav-85

########

Dis ~\ DISMOUNT Phase

########

11 : 55 AM 31-Ma}'-85

########

Final Shutdown Phase

########

Please wait for SYsteM to re-boot itself
RSTS V9.0-14 RSTS/E V9.0 (dev) INIT V9.0-14
31-Mav-85 - 11:58 AM
Start

tiMesharin~

<Yes)? NO

Option:

Go to Phase 2.

Geffing Started

155

Pho]se
~re[oo]re 5Y51em

This phase describes the tasks you must perform to bootstrap the installation tape or
disk and prepare your system disk for a RSTS/E system update. It also explains how
to start your SYSGEN monitor.
The tasks in this phase are:
o Task 1: Physically Mount and Bootstrap Installation Media
o Task 2: Copy Files to System Disk (COPY)
o Task 3: Start SYSGEN Monitor (START)

These responses have special meaning:
Response

Description

Accept the default response

Obtain an online explanation of the question

157

Task 1: Physically Mount and Bootstrap Installation Media
This task requires you to mount and bootstrap the appropriate tape or disk from your
RSTS/E Installation Kit. First, the task provides instructions for mounting the tape on
a tape drive, or mounting a disk on a disk drive. Choose the appropriate section
depending on the type of media for your installation. Second, the task provides an
example of bootstrapping the tape or disk.

Tape Mount Session
Mount the 800 or 1600 bpi 9-track Installation tape. To load the tape on the drive:
1.

Physically mount the tape on drive unit 0 or 1 with the write-enable ring
removed. If you have a combination of TU10, TE10, TU16, TE16, TU4S, and
TU77 tape drives, load the 800 bpi distribution tape onto unit 0 or 1 of the
TU10 or TE10 tape drive. If you have a combination of TU16, TE16, TU4S,
TU77, TS11, TSVOS, and TU80 tape drives, load the 1600 bpi distribution
tape on unit 0 or 1 of the TS 11 drive.

Press the LOAD indicator.

The drive automatically winds the tape until the beginning of tape (BOT)
indicator light comes on. This indicates the tape is at its load point.

Make sure that the write-lock (WR) indicator ,light is on. (If not, dismount the
tape, remove the write-enable ring, and then remount the tape.)

Press the ONLINE indicator. The indicator light comes on.

Make sure the console terminal is on line.
Note ----------------------

The previous instructions may not apply to your tape drive. If so, see
the hardware manual supplied with your tape drive for the load
instructions.

Disk Mount Session
Mount the RSTS/E Installation disk. To load the disk onto the disk drive:

158

Physically mount the disk in drive unit 0 or 1. For an RL02 disk, you can use
drive units 0, 1, 2, or 3.

Make sure that the READY light is on.

Make sure that the write-protect (WR PROT) light is on.

Make sure that the console terminal is on line.

Prepare System

Note - - - - - - - - - - - -

The previous load instructions may not apply to your disk drive. If so,
see the hardware manual supplied with your disk drive for the load
instructions.

Bootstrap Installation Media

Now you must bootstrap the installation tape or disk. You can use either of these
methods:
o

Use the INIT.SYS BOOT option.

Use the PDP-II Central Processing Unit (CPU) switches to activate a hardware
bootstrap loader.

Both bootstrap methods a"re described in the following sections.
Use the INIT.SYS BOOT Option

The INIT.SYS BOOT option bootstraps magnetic tape and disk devices.
Option: BOOT

Explanation - After you shut down the system, answer NO to the Start timesharing? question. INIT.SYS returns to the Option: prompt.
Response -

Type BOOT or BO.

Boot delJice:
Boot unit:

Explanation -

BOOT asks for the device designator of the unit.

Response - Type the device designator and unit number of the drive on which you
mounted the Installation tape or disk. If you type both a device designator and a unit
number, BOOT does not print the Boot unit: prompt. Table 12 lists the tape device
designators. Table 13 lists the disk device designators.

About 30 seconds after you type the device designator, the following prints on the
console terminal:
EnablinS only consolet disKst and tapes.

RSTS V8.x (dev) INIT V8.x
Current date <DD-MMM-YY>?

The Date prompt means that INIT.SYS is loadeo into memory. You have successfully
bootstrapped your Installation media. Note that the device designator of the tape or
disk drive you bootstrapped appears within parentheses.

Prepare System

159

Go to Task 2.

Use the Hardware Bootstrap Loader
The hardware bootstrap loader is a device inside your PDP-II that reads a bootstrap
record from the tape or disk into memory. This bootstrap record contains a program
that loads and executes additional program code from the tape or disk. There are
different types of hardware bootstrap loaders; the type you have on your PDP-II
determines which CPU switches you should use.
Your DIGITAL field service representative or software support specialist should
already have identified the type of hardware bootstrap loader on your PDP-II. The
representative should also have given instructions for bootstrapping your tape or disk.
If you do not know how to bootstrap the Installation media, see Appendix 0, which
contains bootstrap instructions for the different types of hardware bootstrap loaders.

This example shows how to bootstrap the 1600 bpi tape from a TUBO tape drive, by
activating switches on a PDP-11/44. These bootstrap instructions are:

Move the control switch (CONT) to the HALT position.

Move the control switch to the BOOT position.

The CPU prints some octal numbers on the console terminal, followed by three angle
brackets:
»>5 MSO

The »> asks for a command. Type B to indicate a BOOT operation, followed by
the device designator of the drive on which your tape or disk is mounted. A device
designator consists of two letters that identify the device type, followed by the decimal
unit number of the drive and a colon. (However, do not specify a colon here.) The
example uses a TUBO tape drive: thus, the tape device designator is MSO.
Table 12 lists the tape device designators. Table 13 lists the bootable disk device
designators. Enter the appropriate device designator for your installation.
About 30 seconds after you type the device designator, the following prints on the
console terminal:
.
EnablinS only consolet diskst and tapes.

RSTS

V9~x

(MSO) INIT

V9.x

Current date <DD-MMM-YY>?

160

Prepare System

The Current date prompt means that INIT.SYS is loaded into memory. You have
successfully bootstrapped your Installation media. Note that the device deSignator of
the tape or disk drive you bootstrapped appears within parentheses. In the example,
the device designator is MSO.

Go to Task 2.

Table 12 lists the tape device designators.
Table 12: Tape Device Designators
Designator

Device

MMO: to MM7:

TE16rrU16rrU4SrrU77 magnetic tape units 0 to 7

MSO: to MS3:

TSllrrSVOSrrUSOrrK2S magnetic tape units 0 to 3

MTO: to MT7:

TEIOrrUIOrrS03 magnetic tape units 0 to 7 *

*Note: You cannot use a TS03 drive for system installation.

Table 13 lists the bootable disk device designators.
Table 13: Bootable Disk Device Designators
Designator

Device

OBO: to OB7:

RP04/RPOS/RP06 disk drive units 0 to 7 *

OKO: to OK7:

RKOSIRKOSF disk drive units 0 to 7

OLO: to 0L3:

RLOllRL02 disk drive units 0 to 3

OMO: to OM7:

RK06IRK07 disk drive units 0 to 7

OPO: to OP7:

RP02/RP03 disk drive units 0 to 7

ORO: to OR7:

RM02/RM03IRMOS/RMSO disk drive units 0 to 7 *

OUO: to OU7:

RA60IRASO/RASlIRCF2S,RC2SIROSlIROS2IRXSO disk
drive units 0 to 7

*See Appendix F for more information on multiple RH controller configurations.

Prepare System

161

Task 2: Copy Files to System Disk (COPY)
Your next task is to answer the preliminary INIT.SYS questions. Then the INIT.SYS
COpy option transfers some necessary files from the Installation media to your
system disk.

Terminal Session
This terminal session lists the preliminary INIT.SYS questions,
explains them, and gives you some possible responses. After
you understand the question, type the response at your
console terminal.
The common error messages appear in Table 14, at the end
of this task. If your error message does not appear there, see
Appendix A.

You have now successfully bootstrapped your Installation media, and the INIT.SYS
program is loaded into memory.
RSTS V9.x (dev:) INIT V9.x
Current date <DD-MMM-YY>?
Current tiMe <HH:MM AM/PM>?

Explanation - INIT.SYS searches for a valid date and time and prompts you if it
cannot find one. You see the date and time prompts, for example, when you
bootstrap a tape or bootstrap a disk from the console boot/restart switch.
Response -

Type the current date and time in the alphabetic format.

Installin~

RSTS on a new SYsteM disk <Yes> ? NO

Explanation - INIT.SYS asks this question whenever you bootstrap a tape or disk
read-only. (RSTS/E Distribution Kits are always read-only.) If you answer YES,
INIT.SYS assumes you are performing a first time V9.0 system installation and want
to use the DSKINT option to initialize your system disk.
If you answer NO, INIT.SYS assumes that you are bootstrapping the Installation
media to perform an update on the current system disk. INIT.SYS then asks the next
question.
Response Are

}'OU

Type NO because you are updating an existing RSTS/E V9.0 system.

updatin~

an existin~ RSTS S}'stelrl dis~~? <Yes> ffiTI)

Explanation - This question asks if you are updating a previously generated V9.0
monitor. If you answer YES, INIT.SYS executes the COpy operation with forced
supersede of all. files found on the system disk.
If you answer NO, INIT.SYS prints its Option: prompt.

162

Prepare System

Response - Type YES or press RETURN.
Dis~\

to update?

Explanation - INIT.SYS asks you to specify the device designator and unit number
of your system disk. Possible device designator responses are: DL, OM, DP, DB, DR,
or DU.
Response - Type the device designator of your system disk.
Supersedin~
Enablin~

file xxxxxx

only consolet disKst and tapes.

RSTS V8.x (dev:) INIT V8.x
Start

tiMesharin~?

<Yes)

Explanation - After you type the system disk device designator and unit number,
COpy transfers the files to the system disk. Because you answered YES to the Are
you updating an existing RSTS system disk? question, COpy automatically supersedes existing files. COpy prints a message on your terminal as it supersedes each
file.

On completion, INIT.SYS bootstraps your system disk, prints a message on your
console terminal, and returns to the Start timesharing? question.
Note

At this point in system installation you might have to manually install a
patch to the SYSGEN monitor or the INIT.SYS program before
continuing with system installation. Should this ever occur, your
DIGITAL software support representative or the RSTSIE Release
Notes will provide you with the patch installation instructions. See
Task 2 of Phase 8 in Part I for more information on applying a patch.

Go to Task 3.

Prepare System

163

Table 14 lists the COpy error messages.
Table 14:

COpy Error Messages
Message and Meaning

CANNOT COpy TO THE SYSTEM DISK
You specified the RSTS/E Installation media, which is invalid as an output disk for the COpy
option. Specify another disk.
ILLEGAL DISK NAME
You typed an invalid disk name. All DF, DK, and DS disks are i1iegal.
INVALID UNIT NUMBER
The disk unit number you specified does not exist on this system.
INVALID RESPONSE
The only valid responses to the FILE FILNAM.TYP EXISTS: prompt are Y, N, or CTRUC, and
you typed something else.
SORRY, BUT THAT DISK DOESN'T EXIST
The disk type you specified does not exist on this system.

164

Prepare System

Task 3: Start SYSGEN Monitor (START)
In this task you use the INIT. SYS START option to start your SYSGEN monitor.
Your system must run under the SYSGEN monitor during the update.

If you have hardware that has nonstandard CSR addresses, you must first perform a
hardware task. Because the COpy operation in Task 2 transferred a new copy of
INIT.SYS, you must use the HARDWR CSR sub option (Declare a Nonstandard
Controller Address) before you install the monitor. See the Offline Options section for
information on the CSR suboption of HARDWR.

If you are in a country that uses 50 Hz power, you must use the HERTZ suboption of
HARDWR before you install the monitor. See the Offline Options section for
information on the HERTZ suboption of HARDWR.

If your installation uses 60 Hz power and does not have hardware with nonstandard
controller addresses, then you are ready to begin Task 3 and start timesharing under
the SYSGEN monitor.

Terminal Session
This terminal session lists the START questions, explains
them, and gives you some possible responses. After you
understand a question, type the response at your console
terminal.

Start tirtlesharing? <Yes> @

Explanation -

INIT.SYS asks if you are ready to start timesharing.

If you answer YES to this question, INIT.SYS prompts for the monitor name to start.
If you answer NO to this question, INIT.SYS prints its Option: prompt.
Response - Type YES or press RETURN.
Monitor naMe to START <xxxxxx>? SYSGEN
Rebooting • • •

Explanation - When you answer YES to the Start timesharing? question, INIT.SYS
searches the list of monitors, which are stored in account [0,1] with the file type of
.SIL. SIL stands for save image library, which is a file that stores the monitor code.

If INIT.SYS finds only one SIL, it installs that SIL and prints the message Starting
xxxxxx monitor. If IN IT. SYS finds more than one SIL, it prompts for the monitor
name instead. The name inside the brackets refers to the first monitor name it found
in the directory.

Prepare System

165

Response - Type SYSGEN to start the SYSGEN monitor.
Caution

Do not press RETURN to accept the default response to this question
(first monitor SIL in the directory). The update process must run
under the SYSGEN monitor. If you press RETURN, INIT.SYS restarts
your current monitor, causing the system update to fail later.

RSTS V8.x

(del,l:)

dd-MMM-YY

hh:MM AM/PM

INIT 1•.J8.x

Explanation - START now starts the SYSGEN monitor. At this time START may
also print the memory allocation table. Then START transfers control to the
INSTAL. COM command file. INSTAL. COM prints this prompt:
Do YOU want to perforM an installation or an update? <installation>

166

Prepare System

Go to Phase 3.

w-'ho]se
Corr{iguwe Ne'.J'V MOfi1i'l©r Oln1<ol 0)
Se~ec'~ 50'fhrt?~we Upc](Qries ~

This phase describes the tasks you must perform to configure your RSTS/E monitor.
In this phase you also select the software packages you want to update.
The tasks in this phase are:
o Task 1: Answer Preliminary Questions
o Task 2: Use Information from a Template Monitor
o Task 3: Answer System Program Update Questions
o Task 4: Answer layered Product Update Questions

These responses have special meaning:
Response

Description

(0)

Accept the default response

Obtain an online explanation of the question
Return to the previous question
Return to the beginning of the dialogue section
Abort the operation and return to the Del $ prompt

167

Task 1: Answer Preliminary Questions
Your next task is to answer the questions asked by the the INSTAL. COM command
file. The system executes INSTAL. COM immediately after it starts your monitor.
Before INSTAL. COM asks any questions, it opens a log file named UPDATE. LOG in
the account from which you are running the update ([1,2] in most cases).
INSTAL. COM closes this log file at the end of the update. You can then print
UPDATE.LOG to obtain a record of the ~pdate session.
Note - - - - - - - - - - -

The update procedure does not replace your existing
[O,l]START.COM and [O,l]LOGIN.COM files. If START.COM and
LOGIN. COM already exist on your system, the update procedure
, copies new versions of the files to account [0,1] with the names
START.09x and LOGIN.09x, where x refers to the specific release of
RSTS/E.
You may want to examine these files for any new ideas, then delete
the files if you do not need them.

Terminal Session
This terminal session lists the preliminary installation
questions, and provides some possible responses. In some
cases, your response will differ from the response shown in
red in the example.

Do YOU want to perforM an installation or an update? <installation> UP

Explanation - You stopped here in Phase 2. The system asks if you are performing an installation or are updating an existing V9.0 monitor.
Response - Type UP because you are updating an existing V9.0 monitor.
Please Mount the Installation Media and enter the naMe
and unit nUMber of the device.
Valid device types are: 'MM't 'MS't 'MT't 'OM' or 'DL'
Installation device:

Explanation - This question asks for the location of your Installation media.

168

Configure New Monitor and Select Software Updates

Response - Type the device name and unit number of the drive on which your
Installation media is mounted.
Restorin~
Deletin~

required _SYO:[O,l] COMPonents
all

Be~innin~

~lobal

SYMbols

of the RSTS/E Software Update Procedure

Type '?' for help
Type ,A, to ~o bacK to the previous section
Type CTRL/Z to return to the be~innin~ of the present section

* Startin~ dialo~ue phase *
Are YOU ready to proceed? <yes)

Explanation - This question asks if you are ready to continue with the installation
procedure. If you type YES or press RETURN, you continue the dialogue. If you type
NO, INSTAL exits, returning you to the $ prompt. You can then:
o Start normal timesharing under the current monitor by typing @[O,I]SYSINI.
o Recover a corrupted system disk by issuing the $RESTORE command.
o Continue the installation procedure by typing PROCEED.

Response - Type YES or press RETURN to continue the installation. Type NO to
exit INSTAL. COM.
Please enter the naMe and unit nUMber of the disK to
which YOU want to install the software. This disK
should be physicallY Mounted and write-enabled.
Tar~et

disK? <SY:) :

Explanation - This question is for anyone updating a RSTS/E system for another
PDP-I!. Your response to this question determines the disk where the new RSTS/E
monitor and updated system programs will be installed.
If you specify a disk other than the system disk (SY:), physically mount and
write-enable the disk before you answer this question. The disk does not need to be
initialized at this time, because the next question asks if you want to initialize it.

Response - Type the disk name and unit number of the target disk if you are
updating RSTS/E for another PDP-I!. You then see the Do you want to initialize the
target disk? question.

Type SY or press RETURN to update RSTS/E on your present system disk.
Restorin~

required _SY:[l ,2] COITlPOnents

Assi~nin~

SYsteM

lo~icals

** Startin~ Monitor Section **
Do YOU want to update the RSTS/E Monitor? <yes)

Configure New Monitor and Select Software Updates

169

Explanation - This question asks if you want to update the monitor. Answer NO to
this question if you want to update only the system programs. You then skip the
monitor generation.
If you answer YES or press RETURN, you continue with the dialogue to update a
RSTS/E V9.0 monitor.
If you answer NO to this question, go to Task 3.

Response - Type YES or press RETURN to proceed with the RSTS/E monitor
generation.

170

Go to Task 2.

Configure New Monitor and Select Software Updates

Task 2: Use Information from a Template Monitor
In this task you use a template monitor to help configure your new monitor. A
template monitor is a previous V9. 0 monitor that you use as a model for another
monitor.

Terminal Session
This terminal session lists the configuration questions, explains
them, and gives you some possible responses (printed in red).
After you understand the question, type the response at your
console terminal.
If you want to start over at any time while answering the
configuration questions, press CTRL/C. Then type
@[O,l]lNSTAL when you see the DCL $ prompt. You return
to the beginning of Phase 3.
Restoring

re~uired

SYSGEN COMPonents

Use teMPlate Monitor? <Y>

Explanation - You now begin the monitor section of dialogue. This question a$ks
if you want the program to obtain the information it needs from a template monitor.
If you answer YES to this question, you need to answer only the remaining questions
in this task to complete Phase 3. You can still answer YES to this question, even if
you intend to make some changes to your new monitor's configuration. You have the
opportunity to make changes later in this task.
Response - Type YES to use an existing monitor as the template. Or, type NO to
this question. You then see the configuration questions in Phase 3 of Part I of this
guide.

If you answer YES to this question, continue with this task.
If you answer NO to this question, perform Tasks 1 through 6 of Phase 3 in Part I of
this guide. Then proceed to Task 3 of this section.
TeMPlate Monitor's naMe?

Explanation - You can use an existing V9.0 monitor as a template. The template
monitor can be in any account on any disk that is both physically and logically
mounted. If you do not specify the location, the default location is account [0,1] on
the system disk. The program looks up the file and reads the necessary information
from it. If the file does not exist, the program returns an error message and reprompts
you.
Response monitor.

Type the name of the installed SIL you want to use as a template

New Monitor naMe? <RSTS>

Configure New Monitor and Select Software Updates

171

Explanation - This question asks for the name of your new RSTS/E monitor,
which will be stored as a save image library (SIL) in account [0,1] on your system
disk. The program performs a lookup to see if the monitor name you specify already
exists. If it already exists and it is the currently installed SIL, the program returns an
error message and reprompts you.
Response - Type a one- to six-character alphanumeric name for your RSTS/E
monitor. The default response is RSTS.
A Monitor by that naMe already exists.
Do YOU wish to supersede this Monitor?
Supersede

existin~

Monitor? <N)

Explanation - You see this question only if the monitor name specified already
exists and is not the currently installed SIL. If you type NO or press RETURN to
accept the default, the program returns to the New monitor name? question. If you
type YES, the program supersedes the existing monitor.
Response - Type NO or press RETURN to return to the New monitor name?
prompt. Type YES to supersede the existing monitor.
Accept defaults? <N)

Explanation - This question lets you modify the configuration of your new
monitor. If you answer NO, you have the opportunity to make changes at the
beginning of each configuration section. If you answer YES, the program selects the
entire configuration from the template monitor and asks no configuration questions.
If you type a ?, you see a list of the default configuration you will receive if you
answer YES to the question.

Answer YES if you do not need to change the configuration.
Answer NO if you need to make configuration changes. This can occur, for instance,
when you perform a monitor update to add support for new hardware.
Response - Type NO or press RETURN if you want to make changes. Type YES if
you do not want to make changes.

If you answered YES to the Accept defaults? question, go to Task 3.

If you answered NO to the Accept defaults? question, perform Tasks 2
through 6 of Phase 3 in Part I of this guide. Then proceed to Task 3 of
this section.

172

Configure New Monitor and Select Software Updates

Task 3: Answer System Program Update Questions
Your next task is to answer the system program update questions. Your responses
determine which system programs are updated on your system. DIGITAL
recommends that you update all the system programs you selected during system
installation. For a complete description of the system programs available with
RSTS/E, see Phase 4 in Part I of this guide.
DIGITAL supplies updates to RSTS/E system programs on the Installation media. The
programs are grouped into the packages listed in Table 15. See Appendix C for a
complete list of system programs contained in each package.
The system updates each package at the location pointed to by its associated logical
name. The update occurs in Phase 4.
Note - - - - - - - - - - If you have moved a software package from its default location to a
disk other than the system disk, you will need to mount the other disk
on a free drive at the beginning of Phase 4.

Table 15 lists the logical names for each system program package.
Table 15: System Program Pacl<age Logical Names
Package

Logical Name

System Library

SYSLIB$:

RSX Utilities

LB:

Help

HELP$:

Error

ERROR$:

Update

UPDATE$:

Device Testing

TEST$:

PrintlBatch Services (PBS)

PBS$:

File Restore

RESTOR$:

OPSER-based Spooling

OPSER$:

Unsupported Utility

UNSUPP$:

AUxiliary Library

AUXLIB$:

RMS-ll

RMS$:

EDT

EDT$:

TECO

TECO$:

SORTIMERGE

SORT$:

BASIC-PLUS

BASIC$:

Configure New Monitor and Select Software Updates

173

Terminal Session
This terminal session explains the procedures to update
system programs.

** End of Monitor Section **
** Starting SYsteM PrOgraMS Section **
Do YOU want to update the SYsteM PrograM packages? (yes)

Explanation - You are finished with the monitor update section. You now begin
the system programs section.

Type YES or press RETURN to begin the dialogue to update system
programs. Type NO if you are only updating a RSTS/E monitor and do not want to
update system programs. You then skip this task.

Response -

If you answer NO to this question, go to Phase 4.
PacKages to update: ?

Explanation - This question asks for the names of the packages you want to
update on your system.
Response -

Type a ? to list the packages that are available.

The valid responses are:
DIALDGUE
ALL
ALL ,NOp.,g[, ••• ]

Switches YOU to the long forM of the SYsteM
Software Packages dialogue where a More
detailed description of each package is provided
Selects all pacKages
Selects all pacKages except pKg

Use a COMMa as a separator. e.9.: RSX,PBS,RMS
Pad,age nalrles:
AUXLIB
BASIC
DAP

Auxiliar)' Librar)'
Basic-Plus
RMS DECnet Data Access Pac.'age
(includes RMS-ll)
EDT
EDT Editor
Help Package
HELP
OPSER
Opser-based Spooler
PBS
Print/Batch Services
RESTORE File Restore

RMS
RS}-{
SORT
TECO
TEST
UNSUPP
UPDATE

PacKages to update:

174

Configure New Monitor and Select Software Updates

RMS-ll
(includes RSX Utilities)
RS}-{ Utilities
Sort/Merge
(includes RMS-ll)
TECO Editor
Device Testing
Unsupported Utilities
Update Padtage

Explanation - After you type a ?, you see the list of available system program
packages. Then the system reprompts for the packages to update.
Response - If you know what packages you want to update, type a list of the
package names, separated by commas. Remember, if you make a mistake you can
type" to return to the previous question, or enter CTRL/Z to return to the beginning
of the section. Do not specify any package that is not currently installed on your
system.
If you want more information before deciding whether to update a package, type
DIALOGUE to see the long form of the dialogue.

Type ALL to update all the packages. If you plan to update nearly all of the
packages, type:
ALL,NOnnnnnn,NOnnnnnn
where nnnnnn refers to a package you want to exclude.
The following will be installed:
<list of pacKages>
Proceed? <)'es>

Explanation - The system lists the packages it will update on your system and then
asks if you want to continue. If you type NO, you return to the Packages to update:
prompt.
Response - Type YES or press RETURN to continue the system program update.
Type NO if you want to specify a different list of packages to update on your system.
Do

YOU

want the 1&0 versions of tasKs? <no> ?

Explanation - The system copies some required files and then asks if you want the
I&D versions of tasks. You see this question only if you specified RSX andlor
AUXLIB in response to the Packages to update: question.

Instruction and Data (I&D) space is available on the PDP-11/44, 45, 50, 55, 70, 73,
83, and 84. DIGITAL does not recommend that systems with less than 256K words
of memory (PDP-11/45, 50, or 55) use I&D space. If your system has more than
256K words of memory (PDP-11/44, 70, 73, 83, or 84), you may want to take
advantage of this hardware feature which yields better performance from the
following tasks: TKB, MAC, STK, and REORDR.

Configure New Monitor and Select Software Updates

175

Note that if you answer YES to this question, you must specify a SWAP MAX of 64K
words to accommodate the larger amount of physical memory required by the tasks.
Use the INIT.SYS DEFAULT option to change the SWAP MAX. See the Offline
Options section for details.
The system uses your response to this question later in the update when it asks
whether you want to create a SWAP1.SYS file (see Task 1 of Phase 4). If you
answer YES to this question, the system assumes a SWAP MAX of 64K words.
Otherwise, the system assumes a SWAP MAX of 32K words.
Response - Type YES to receive the 1&0 versions of tasks. Type NO or press
RETURN to receive the normal versions.
Use resident library version of RMS? (yes)
Use RMS resident libraries in DAP? (yes)
Use RMS resident libraries in PBS? (yes)
Use resident library version of EDT? (yes)

Explanation - If you choose RMS, DAP, PBS, or EDT, the system asks you to
choose either the resident library or overlaid version. In general, the overlaid version
requires less memory, but can severely impact performance. The resident library
version requires less disk space, but requires more memory. Choose the resident
library versions if your system has sufficient memory and you have more than one
user accessing a program simultaneously.
Response - Type YES or press RETURN to use the resident library version. Type
NO to use the overlaid version.
Durinf the build phase there will be further questions
for BASIC-PLUS and SORT/MERGE

Explanation - You see these messages if you specified the BASIC-PLUS and/or
SORT/MERGE packages. You answer the BASIC-PLUS and SORT/MERGE questions in Phase 4.

** End of SYsteM ProfraMs Section **
** Startin~ Layered Products Section **
Do YOU want to transfer the layered product update COMPonents
frOM the Installation Kit? (yes)

176

Configure New Monitor and Select Software Updates

Explanation - You are finished with the System Programs Section. This question
asks if you want to transfer any layered product updates from the Installation kit while
it is still mounted. Answer YES to this question if you plan to update any layered
products on your system. If you answer YES, you continue the Layered Products
Section.
Response - Type YES or press RETURN to continue the Layered Products
Section. Type NO to skip the section.

If you answered YES to the previous question, go to Task 4.

If you answered NO to the previous question, go to Phase 4.

Configure New Monitor and Select Software Updates

177

Task 4: Answer Layered Product Update Questions
You perform this task if you plan to update layered products on your RSTS/E system.
A layered product, also called optional software, is software that you must purchase
from DIGITAL. Examples of layered products are BASIC-PLUS-2, COBOL-81, and
DIBOL.
In this task, you specify which layered products you plan to update on your system,
so that the installation procedure can transfer updates for those products from the
Installation kit.
----------------------- Note

The RSTS/E Update Procedure does not perform a layered product
installation. See the individual layered product installation guide for
the procedures to perform the layered product update.

Terminal Session
This terminal session explains the layered product update
questions and provides some possible responses.

** Startinr Layered Products Section **
Do yOU want to transfer the layered product update COMPonents
froM the Installation Kit?'(yes)

Explanation -

You see this question at the end of Task 1.

Response - Type YES or press RETURN to begin the dialogue to transfer layered
products updates. Type NO to skip this section.
Product updates to transfer:

Explanation - This question asks for the names of the layered product updates
you want to transfer to your system.
Response - Type a ? to list the layered product packages that are available with

RSTS/E.
Type a list of the product names, separated by commas. Remember, if you make a
mistake you can type " to return to the previous question, or enter CTRL/Z to return
to the beginning of the section.

178

Configure New Monitor and Select Software Updates

Type ALL to transfer all the updates. If you plan to transfer nearly all of the product
updates, type:
ALL,NOnnnnnn,NOnnnnnn
where nnnnnn refers to a product update you want to exclude.
The following will be transferred:
<list of products>
Proceed?

<Yes>

Explanation - The system lists the product updates it will transfer to your system
and then asks if you want to continue. If you type NO, you return to the Product
updates to transfer: prompt.
Response - Type YES or press RETURN to continue the layered product update
transfer. Type NO if you want to specify a different list of layered product updates to
transfer to your system.
Note: Any files currently in the PATCH ACCOUNT will be deleted
Since SOMe layered products May require the Update pacKage
(froM the SYsteM PrOgraMS section) t it will be included.
To install a layered product please refer to the individual
layered product installation guide.
Patch account <PATCH$:> :

Explanation - Now you must specify the account in which you want the layered
product update information placed. The default account is PATCH$:. Note that the
update procedure deletes any existing files in the current PATCH account before it
transfers the updates. If you have files in the PATCH account that you want to keep,
specify a different account for PATCH$:.

After you complete the RSTS/E update, you must follow the update procedures
outlined in the specific layered product installation gUide to update a layered product.
Some of the layered products use the BUILD program to perform the update. See
Appendix E for a description of BUILD.
Response - Press RETURN to accept the default patch account, PATCH$. Or,
specify a different account.

** End of Layered Products Section **
Explanation - You are finished with Phase 3.

Go to Phase 4.

Configure New Monitor and Select Software Updates

179

PhOlse

Generoris New Sys'iem

You are now ready to generate your updated RSTS/E system. In this phase, you
create the new RSTS/E monitor and update the system programs you specified in
Phase 3. See the appropriate installation gUides for instructions on updating optional
software such as COBOL-81 or DIBOL.
The tasks you perform in this phase are:
o Task 1: Create RSTS/E Monitor

o Task 2: Update System Programs and Transfer Layered Product Updates

181

Task 1: Create RSTS/E Monitor
The system now generates your new monitor according to the instructions you gave it
in Phase 3.

Terminal Session
This terminal session explains the procedures that generate
the RSTS/E monitor. The procedures will differ depending on
your response to certain configuration questions in Phase 3.

You Must now set the password for account _SY:[l ,2]
Ne . . 1 pas SI"IO rd:
New passwor~ a~aint for verification:
Passl"lord set for account _SY: [1,2]

Explanation - This question asks you to specify a password for the system library
account, [1,2]. This is a precautionary measure to provide you with an account that
you can log in to in case of unforseen problems. DIGITAL does not recommend that
you log in to and use account [1,2] on a regular basis, because of the importance of
the files that reside in the account.
Response - Type a password from 6 to 14 characters. You can specify any ASCII
character except the ? character. Retype the password when prompted.

* End of dialo~ue phase *
* Startin~ build phase *
Are

YOU

ready to proceed? (yes)

Explanation - This question asks if you are ready to generate your RSTS/E
system. You are not ready to proceed if you need to mount a disk other than the
system disk on which any of the software packages targeted for update reside. Before
you proceed you must:

Physically mount the nonsystem disk

Issue the MOUNT command to logically mount the disk

Assign the appropriate system logicals

If you are ready to proceed, type YES or press RETURN. If you are not ready, type
NO. You then see the $ prompt. When you are ready to proceed, type PROCEED.

182

Generate New System

Response - Type YES or press RETURN to proceed.
Do YOU want _SYO:SWAP1.SYS created? (yes>
Creatin~

_SYO:[O,lJSWAP1.SYS at xxxx blocKs

Explanation - The command procedure asks if you want to create a SWAP1.SYS
file at a size large enough to hold all the jobs on your system. It creates SWAP1.SYS
as close to the center of the system disk as possible. The system determines the size
of SWAP1.SYS according to this formula:

(JOB MAX-I) * SWAP MAX * 4
where:
JOB MAX-I

is the number of jobs you specified in Task 6 of Phase 3 in Part I,
minus 1.

SWAP MAX

is 32K words if you did not see or answered NO to the Do you
want the 1&0 versions of tasks? question in Task 3 of Phase 3.
is 64K words if you answered YES to the Do you want the 1&0
versions of tasks? question in Task 3 of Phase 3.

If your system already has a SWAP1.SYS file and it is protected, the command
procedure prints the error:
SWAP1.SYS already exists and is protected, can not re-create

If you see this message, you also see a message later in the installation that informs
you how much swap file space you need on your updated system. If you need to
recreate SWAP1.SYS, use the INIT.SYS REFRESH option before you start timesharing. See the Offline Options section for more information on REFRESH.

Response - Type YES or press RETURN to create SWAP1.SYS. Type NO to skip
the creation of SWAP1.SYS. Type a ? if you want to know the size of SWAP1.SYS
before you answer the question.
Creatin~

_SYO:[O,lJBUFF.SYS at xx blocKs

Explanation - You see this message only if you have TU56 DECtapes on your
system and do not already have a BUFF.SYS file. You must have a BUFF.SYS file
for your RSTS/E monitor to support one or more TU56 DECtapes.

The system automatically creates BUFF.SYS as close to the center of the system disk
as possible. It determines the size of BUFF.SYS (shown as xx blocks) according to
this formula:
4 blocks for each TU56 DECtape
Please Mount the DECnet/E Installation Media and enter the naMe
and unit nUMber of the device.
1.lalid del.Jice t}'pes are: 'MM', 'MS', 'MT', 'DM' or 'DL'
DECnet/E installation device <dev:>

Generate New System

183

Explanation - You see this question only if your template monitor supports
DECnetiE or you answered YES to the DECnet network support? question in Phase
3 of Part I. Mount the DECnetiE Installation media on a free drive when prompted.
You may have to dismount the Installation media to make room for the DECnetiE
kit, if you do not have a free drive available. The system prompts you to remount the
Installation media later.
Response - After you have mounted the DECnetiE Installation media, type the
device name and unit number of the drive on which it is mounted. Or, press
RETURN to accept the default <dev: >.
Please ensure that the Installation Media is Mounted
on dev: and press RETURN when ready:

Explanation - After the system has transferred the DECnetiE files, it prompts you
to remount the Installation tape or disk.
Response - Dismount the DECnetJE media and mount the Installation tape or disk
on the drive indicated by dev:. Make sure the tape or disk is on line. Then press
RETURN when you are ready to proceed.
CreatinS RSTS/E Monitor

Explanation - The command procedure now begins the RSTS/E monitor generation. The entire process should take 30 to 45 minutes, depending on the size of your
monitor.
If your template monitor supports RJ2780 or you answered YES to the RJ2780
support? question in Phase 3 of Part I, the program prompts you to mount the
RJ2780 Software Kit at this time. Mount the RJ2780 kit when you see this prompt:
Please Mount the RJ2780 Installation kit and enter the naMe
and unit nUMber of the device.
IJalid device types are: 'MM', 'MS', 'MT', 'DM', 'DL', or 'SY'
Installation device <dev:> :

You may have to dismount the Installation media to make room for the RJ2780 kit, if
you do not have a free drive available. The system prompts you to remount the
Installation media later. Remount the installation media on the indicated drive (dev: in
the example) when you see this prompt:
Please ensure that the Installation Media is Mounted
on dev: and press RETURN when ready:
%SMall buffers low~red by xxx buffers
This will leave you with yyy buffers

Explanation - The command procedure checks whether the number of small
buffers you specified in Task 6 of Phase 3 in Part I will fit on your system. If the
number you specified is too high, the command procedure attempts to decrease the
number of buffers so that the monitor fits on your system.

184

Generate New System

In general this indicates that the system you configured is too big. Rather than make
such a radical adjustment to your monitor by significantly decreasing the small
buffers, the command procedure returns to the configuration questions in Phase 3 of
Part I. If you see this message, return to Phase 3 in Part I of this guide and answer
the configuration questions. You may want to decrease the size of your system by
changing the answers to some of the questions (for example, fewer devices, terminals,
or pseudo keyboards). Also, specify a much smaller number to the Small buffers?
question in Task 6. In general, 600 is a good response to the Small buffers? question.
See the BUFFERS sub option of DEFAULT in the Offline Options part of this gUide
for more information on small buffers.
This Monitor will fit OK

E"planation - This message indicates that the new monitor is an acceptable size
for your system.
Next the command procedure prints a table that shows how many general and FIP
small buffers you currently have. In addition, the table tells you how many general
and FIP small buffers you can add if you have data space and how many FIP small
buffers you can add if you do not have data space.

Go to Task 2.

Generate New System

185

Task 2: Update System Programs and Transfer Layered Product Updates
The installation procedure now updates the system programs and layered products
according to the instructions you gave in Phase 3. The procedure can take 10 to 15
minutes, depending on the size of the update. If the Installation media contains
multiple volumes, the program prompts you to change media at the appropriate time.

Terminal Session
This terminal session explains the procedures that update the
system programs.

RestorinS the xxxxxx packaSe froM the Installation kit
There are no updates for the xxxxxx packase

Explanation - The system now updates the system programs. As the system
updates each system program package, it prints one of the above messages. In both
messages, xxxxxx is the name of the specific software package.
RestorinS the xxxxxx update COMPonents froM the Installation kit

Explanation - After the system completes the system program file transfers, it
restores the layered product updates you specified in Phase 3. As the system transfers
each layered product update, it prints the above message, where xxxxxx is the name
of the layered product.
Updatins software packases
BeSinnins of RSTS/E Basic-Plus Seneration
BASIC-PLUS RTS naMe? <BASIC)

Explanation - You see this question if you are updating BASIC-PLUS. You must
now answer the BASIC-PLUS questions. See Task 5A of Phase 5 in Part I for a
description of the dialogue. Otherwise, continue with this task.
BeSinnins SORT/MERGE installation

Explanation - You see this question if you are updating SORT/MERGE. You must
now answer the SORT/MERGE questions. See Task 5B of Phase 5 in Part I for a
description of the dialogue. Otherwise, continue with this task.
To install/update layered productst please see the individual layered
product installation suides.

186

Generate New System

Explanation - You see this message only if you transferred layered product
updates to your system (see Task 4 of Phase 3).
See the installation instructions that came with each layered product for a complete
description of the installation procedures.

* End of build phase *
The RSTS/E software update procedure is COMPlete
Deleting all global SYMbols
Deassigning SYsteM logicals
dd-MMM-YY

hh:MM AM/PM

SYsteM tape label default set to DOS
SY:[p,pnJUPDATE.LOG is a log file of this session
$

Explanation - You have completed the update. The command procedure prints
informational messages and reminds you that the UPDATE.LOG file is a record of
the installation.
Go to Phase 5.

Generate New System

187

Pho]se
5'~Olri New Moniior

This phase describes the tasks you must perform to start your new RSTS/E monitor.
The tasks in this phase are:
o Task 1: Shut Down SYSGEN Monitor (SHUTUP)
o Task 2: Start New RSTS/E Monitor (START)

189

Task 1: Shut Down SYSGEN Monitor (SHUTUP)
Now that you have built an updated RSTS/E monitor, you no longer need the
SYSGEN monitor. To shut down your monitor, run the SHUTUP program.

Terminal Session
This terminal explains how to use SHUTUP to shut down
your SYSGEN monitor.

$RUN $SHUTUP

Explanation - You see the DeL $ prompt on your screen. You can now shut
down the SYSGEN monitor.
Response - Type RUN $SHUTUP to shut down the monitor.
SHUTUP V9.x RSTS V9.x <SYSGEN>
12:5a PM 31-MaY-85

Type

IAI

########

Set-up Dialogue Phase

########

to any query to bacKup one question

Allow Print & Batch entries to cOMPlete (YES/NO) <Yes>?

Explanation - SHUTUP asks you to type the minutes to wait before the RSTS/E
monitor shuts down. This question is useful for giving system users fair warning wher
shutting down the system.

190

Start New Monitor

Response - Type a number from 0 to 99. Or, press RETURN to accept the default
of 5 minutes.
.
12:55 PM 31-MaY-85 ########
Warning Message Phase
Further LOGINs are nO . . 1 disabled

########

12:55 PM 31-MaY-85

########

Initial Job Killing Phase

12:55 PM 31-MaY-85 ########
Print/Batch Shutdown Phase
Print/Batch Services shutdown cOIT1Plete at 12:55 PM.

########

12:55 PM 31-MaY-85

########

, EI)TLOG , Shutdo . . ln Phase

########

12:55 PM 31-Ma}'-85

########

, ERRCPY , Shutdown Phase

########

12:55 PM 31-MaY-85

########

ReIT1OI)e RTS/RES LIB Phase

########

12:55 PM 31-MaY-85

########

SWAP File RelTloval Phase

########

12:55 PM 31-MaY-85

########

o is., DISMOUNT Phase

########

12:55 PM 31-MaY-85

########

Final Shutdown Phase

########

RSTS V8.x <SYSGEN) (dev:) INIT V8.x
dd-MMM-YY - hh:MM AM/PM
Start tiMesharing <Yes)?

Go to Task 2.

Start New Monitor

191_

Task 2: Start New RSTS/E Monitor (START)
In Task 1 you ran the SHUTUP program to shut down the SYSGEN monitor. Now
you need to start your updated RSTS/E monitor. You must first decide whether to
perform any of these additional preparatory tasks:
• Change monitor defaults (lNIT.SYS DEFAULT option)
• Save system disk onto another disk or tape (lNIT.SYS SAVRES option) ,

Change Monitor Defaults (DEFAULT Option)
When you start your new monitor, it will receive the standard monitor defaults.
Table 16 shows the defaults that INIT.SYS selects.
Table 16:

INIT.SYS Selected Defaults
Current Setting

Default
SWAP MAX

32K words

Primary run-time system

RSX

Swap file

SWAP.SYS

Error message file

ERR. ERR

Crash dump file

CRASH.SYS, if enough space is present

Extended buffer pool
memory (XBUF)

15% of USER memory is allocated to XBUF, if
the total amount of system memory exceeds
128K words. Otherwise, 10% of USER memory
is allocated to XBUF. USER memory is memory
that is not allocated to any other entity, such as
the monitor or run-time system. The minimum
size of XBUF is 2K words. The maximum size is
496K words.

Small buffer pool memory

The maximum allowed for your system, over
and above the minimum number you specified
during system installation (see Part I, Phase 3,
Task 6): 11K words for PDP-lIs with 1&0
space; 3K words for PDP-lIs without 1&0
space.

System clock

KW11-L Line Time Clock

If you do not plan to change any of the defaults selected by INIT.SYS, then you do
not need to use the DEFAULT option before you start timesharing under your
RSTS/E monitor. See the Offline Options section of this gUide for a complete
description of DEFAULT.

192

Start New Monitor

As an alternative to using the offline SAVRES option, you can later use the online
V9.0 BACKUP utility to copy your system disk. See the RSTSIE System Manager's
Guide for more information.
If you need to perform additional preparatory tasks, go to the Offline Options section
of this guide. Then continue with this task.

Terminal Session
To start your RSTS/E monitor, you must answer the START
questions. This terminal session lists the questions, explains
them, and gives you some possible responses. After you
understand the question, type the response at your console
terminal.

Start tiMesharing? <Yes) START <Monitor naMe)

Explanation - You see this question at the end of Phase 4. This question asks if
you are ready to start timesharing. If you answer YES to this question, INIT.SYS
restarts timesharing under the currently installed monitor.
If you answer NO to this question, INIT.SYS prints its Option: prompt. You can then
use the INIT.SYS offline options to perform additional preparatory tasks. Finally,
when you are ready to start your RSTS/E monitor, use the INIT.SYS START option.
Response - Type START <monitor name>, where <monitor name> is the name
of your new RSTS/E monitor.
If you do not specify a monitor name, START starts the monitor that was used in the
previous timesharing session.
MelTlo r}' allocation table:
OK:
87K:
8BK:
11118K:
512K:

00000000 0011111000 001120000 03370000 011000000 -

001113777
001117777
03387777
03777777

End

87K)
1K)
37BK)
88K)

E}-{EC
RTS (RS}{)
USER
}{BUF
N}-{M

Explanation - START prints the current memory allocation table. The sample
memory allocation table is from the example installation in Part I. Then START
checks that the SWAP.SYS file exists in account [0,1] on the system disk, is large
enough to hold one job at the current SWAP MAX, and is contiguous. If the file does
not exist, START attempts to create SWAP.SYS at the required size. If the file exists
but is not contiguous or large enough, START deletes the current SWAP.SYS file and
attempts to create a new SWAP.SYS file that is both contiguous and large enough
(SWAP MAX * 4). If START cannot find enough free contiguous disk space to create
a 'minimum SWAP.SYS file, it prints the following error message:
?Not enough contiguous disK space to create MiniMUM SWAP.SYS file

Start New Monitor

193

Press RETURN to accept the default value, indicated by xx in the example. Or, enter
CTRL/C to return to the Option: prompt. You can then use the FILE suboption of
REFRESH to create more disk space.

If START cannot find enough contiguous disk space to create a minimum SWAP.SYS
file, it prints these messages:
You Must free SOMe disk space to start tiMesharing.
Option:

Use the FILE suboption of REFRESH to create more contiguous disk space.
Re-creating CRASH.SYS file with MiniMuM size of xxx blocks

Explanation - START now checks that the CRASH.SYS file exists in account [0,1]
on the system disk, is large enough for the RSTS/E monitor and extended buffer pool
allocation, and is contiguous. If the file does not exist, START attempts to create
CRASH.SYS at the required size. If the file exists but is not contiguous or large
enough, START deletes the current CRASH.SYS file and attempts to create a new
CRASH.SYS file that is both contiguous and large enough. If START is successful it
prints the previous message. If START is unsuccessful, it prints the following error
messages:
?Not enough contiguous disk space to create MiniMuM CRASH.SYS file
Crash dUMP autoMatically disabled

When a crash occurs, the RSTS/E monitor dumps the contents of the read/write area
of monitor memory into CRASH.SYS. Because the crash dump facility preserves the
state of the system at the time of the crash, CRASH.SYS contains important diagnostic information. For these reasons, DIGITAL recommends that you always have crash
dump enabled during timesharing.
Therefore, if you see the error message Crash dump automatically disabled, follow
these steps to enable crash dump:

194

After you begin timesharing, delete unnecessary files to create more contiguous
disk space. Or, move some files to a nonsystem disk.

Shut down the RSTS/E monitor using the SHUTUP program.

Start New Monitor

Use the START option to start timesharing. If you do not see the Crash dump
disabled message, you know that INIT. SYS was able to create the
CRASH. SYS file.

*** Frolrl [1,2] on KBO: at hh:lrlfrl AM/PM dd-Irlfrlfrl-}'}'
** RSTS/E is on the air •••
RSTS V9.x
User:

dd-MMM-YY

hh:MM

AM/PM

Explanation - You are finished with the update. You can now press RETURN to
log in to the system.

Remember, if you are updating layered products, see the individual layered product
documentation for instructions on completing the installation.

Start New Monitor

195

Pho]se
Op'~ional las~{s

This phase describes an optional task you may want to perform to tune your RSTS/E
system to your needs.
The task in this phase is:
o Task 1: Perform a Selective Update

197

Task 1: Perform a Selective Update
You can use the UPDATE. COM command file to perform a selective RSTS/E update,
without disturbing your existing system. UPDATE. COM resides in account [0,1]. You
can use it to:
o

Generate an updated monitor

o Update one or more system program packages
o Update layered products (integrated layered products only)
o Copy layered product updates to your system
o

Perform a· full system update
Note - - - - - - - - - - -

You cannot perform a system update on a pre-V9. 0 system. You must
first perform a V9. 0 installation.

In order for the update to succeed, you must be logged in to an account with the
following privileges: MOUNT, INSTAL, TUNE, WREAD, WWRITE, and WACNT. In
addition, if you have DATES privilege, the creation date of the new files will be the
date the files were placed on the Installation kit. If you do not have DATES privilege,
the file creation date will be the current date.
To access UPDATE.COM, use the following command format:
@[O,l]UPDATE function [package, ... ]
where:
@[O,l]UPDATE

invokes the UPDATE.COM command procedure.

function

specifies the operation to perform. Legal functions are: ALL
(the default), MONITOR, SYSTEM_PROGRAMS, and
LAYERED _PRODUCTS.

[package, ... ]

specifies the software package(s) to install when performing a
SYSTEM_PROGRAMS, LAYERED_PRODUCTS, or
COPYUP operation (see Table 17). See Phase 4 in Part I for a
complete list of RSTS/E system program packages and layered
products.

UPDATE.COM Entry Points
When you use UPDATE. COM to perform an update, you enter the update process at
different points depending on the command format. Table 17 lists the UPDATE. COM
commands and the resulting entry points into the update process. See the appropriate
Phase and Task in Part IV for details on the actual installation procedures.

198

Optional Tasks

When you use UPDATE. COM to perform an online installation, you first see this
question:
Please Mount the Installation Media and enter the naMe
and unit nUMber of the device.
Valid device types are: 'MM', 'MS', 'MT', 'DM', 'DL' or 'SY'
(a response of SY allows Monitor only)
Installation device:

This question prompts you to mount the Installation tape or disk and specify its
. location. See the example later in this section if you need help answering this
question.
Table 17 lists the UPDATE. COM commands and the resulting entry points into the
update process.
Table 17:

UPDATE.COM Entry Points

Command

Update
Entry Point

Comment

@[O,l]UPDATE

Phase 3, Task 1

Performs full update (same as
UPDATE ALL).

@[O,l]UPDATE ALL

Phase 3, Task 1

Performs full update (the default).

@[O,l]UPDATE
SYSTEM_ PROGRAMS

Phase 3, Task 3

Begins system program update
questions.

@[O,l]UPDATE
SYSTEM_ PROGRAMS [pkg, ... ]

Phase 4, Task 2

Updates specified package.

@[O,l]UPDATE MONITOR

Phase 3, Task 1

Begins monitor update section.
Skips system section. Skips system
program and layered product
sections.

@[O,l]UPDATE
LAYERED _ PRODUCTS

This function is available only to
integrated layered products. Use this
function only if you are directed to
do so by a specific layered product
installation guide.

@[O,l]UPDATE
LAYERED_PRODUCTS [pkg, ... ]

This function is available only to
integrated layered products. Use this
function only if you are directed to
do so by a specific layered product
installation guide.

@[O, l]COPYUP

Phase 3, Task 4

Begins dialogue to transfer layered
product updates from the Installation
kit.

@[O.l]COPYUP [pkg, ... ]

Phase 4, Task 2

Transfers specific layered product
updates from the Installation kit.

Optional Tasks

199

Selective Update Example
This example uses UPDATE. COM to update the File Restore system program
package. Before you run UPDATE. COM, you must mount the Installation media.
Mount the tape or disk on a free drive. Follow the tape or disk mount instructions in
Task 1 of Phase 2.
$

@[O,lJUPDATE SYSTEM_PROGRAMS RESTOR

* Startin~ dialofue phase *
Please Mount the RSTS/E Installation Media and enter the naMe
and unit nUMber of the device.
Valid device t}'pes are: 'MM', 'MS', 'MT', 'DM', 'DL' or 'SY'
(a response of SY allows Monitor only)
Installation device: MSO:
Please enter the naMe and unit nUMber of the disk to
whibh you want to update the software. This disk
should be physicallY Mounted and write-enabled.
Tarfet dis~\? <SY:) : @
Assifninf SYsteM 10ficals
The follo',Jinf . . . ill be' updated:
RESTORE
Proceed? <}'es) @

* End of dialofue phase *
* Startin~ build phase *
31-May-85 01:56 PM
Restorinf the File Restore pacKafe froM the Installation Kit
31-MaY-85 01:58 PM
Updatinf software pacKafes

* End of build phase *
Deletinf all flobal SYMbols
(continued on next page)

200

Optional Tasks

31-MaY-85 01:58 PM

SysteM tape label default set

DOS

SY:[l,ZJUPDATE.LOG is a log file of this session
$

You have successfully updated the File Restore package. You can now type DIR
RESTOR$: to list the files in the directory.

Optional Tasks

201

Part V describes the offline INIT.SYS options you may need to use in the management and maintenance of your RSTS/E system.
Table 18 lists the offline INIT.SYS options and sub options.
Table 18:

INIT.SYS Options

Option

Suboption

Function

BOOT

None

Bootstrap magnetic tape and disk devices.

COpy

None

Copy installation-related files from a distribution medium to
the system disk, ann bootstrap the system disk.

DATE

None

Reset the current date and time; establish default date and
time format.

DEFAULT

Memory Table
Suboptions:

Change RSTS/E monitor defaults or allocation of memory
entities.

LIST
PARITY
LOCK
UNLOCK
RTS
RESET
XBUF
BUFFERS
VIRTUAL
(continued on next page)

203

Table 18:

INIT.SYS Options (Cont.)

Option

Suboption

Function

DSKINT

None

Initialize disks.

HARDWR

LIST

Perform hardware-related tasks.

DISABLE
ENABLE
CSR
VECTOR
RESET
DM
HERTZ
SWITCH
IDENT

None

Print INIT.SYS creation .date plus list of patches.

PATCH

None

Alter RSTS/E system code to correct program errors.

REFRESH

LIST

Create and list system files; add bad blocks to the bad
block file.

FILE
BADS
SAVRES

SAVE
RESTORE

Back up and reconstruct RSTS/E disks; make an image
copy of a RSTS/E disk.

IMAGE
IDENTIFY
START

None

Start a RSTS/E monitor.

The offline options are arranged in alphabetical order, and each is presented in a
separate section. In most cases, the common error messages associated with an
option appear at the end of the option description. If your error message does not
appear there, see Appendix A.
In general, these responses have special meaning when using INIT.SYS:

Response

Description

Accept the default response

Obtain an online explanation of the question
Abort the operation and return to the Option: prompt

Option: m

204

Offline Options

Invoke the INIT.SYS START option

BOOT

BOOT -

Bootstrap Devices
The BOOT option bootstraps magnetic tape and disk devices. Use the BOOT option
if:
o You need to bootstrap another disk or tape.
o You need to reload INIT.SYS after you have patched it on disk.

BOOT Dialogue
Option: BOOT

Response - Type BOOT or BO to the Option: prompt.
Boot device:
Boot unit:

Explanation - BOOT asks for the device designator and unit number of the tape
or disk you want to boot.
Response -Type a ? in response to the Boot device: prompt to get a list of
bootable devices. Or, press RETURN to bootstrap the system disk, in which case
BOOT automatically determines the system device and unit number.
RSTS V8.0 (dev) INIT V8.0-14
dd-MMM-YY - hh:MM AM/PM
Start

tiMesharin~?

<Yes)

Explanation - After booting the deVice, INIT.SYS displays its banner, the date, and
the time. INIT.SYS prints the device name within parenthesiS in the banner. If you
booted a tape device, INIT.SYS prompts you for the date and time instead.
INIT.SYS then returns to the Start timesharing? prompt.
Table 19 lists the BOOT error messages. If your error message does not appear
there, see Appendix A.
Table 19:

BOOT Error Messages
Message and Meaning

NOT A VALID BOOT DEVICE

The device you named is not a valid bootable device. Type a question mark (?) for a list of
devices that you can bootstrap.
SORRY, BUT THAT DEVICE DOESN'T EXIST

The device name you typed is valid, but the device does not exist on your PDP-II.

Offline Options

205

COpy

COpy -

Copy System Installation-Related Files to Disk
The COPY option copies files related to system installation from a booted disk or
tape to a disk. COpy transfers all files with the following file types:
Type

Meaning

.SYS

Usually the INIT.SYS file, which contains options you need to generate a
RSTS/E monitor.

.SIL

A file that stores monitor code .

. RTS

A file that stores a run-time system.

.ERR

A file that stores the system error messages .

.TSK

Usually the BACKUP.TSK file, which contains the programs to back up
and restore files .

.COM

Usually the SYSINI.COM file, which stores the system start-up file.

COpy Dialogue
Opt i on:

COpy

Response - Type COpy or CO to the Option: prompt.
dd-MMM-YY - hh:MM AM/PM
To '. . hich

dis~\?

Explanation - COpy prints the date and time, and then asks for the device
designator of the target disk.
Response -

Possible responses are: DL, OM, DP, DB, DR, or DU.

Physical unit nUMber?

Explanation - This question asks for the unit number of the drive on which your
disk is mounted.
Response - Type the unit number of the drive on which the disk is mounted.
Enablin~

only consolet disKst and tapes.

RSTS V9.0 (deu) INIT V9.0-14
Start

tiMesharin~?

<Yes)

Explanation - After you type the unit number, COpy transfers all the the files to
the destination disk. COpy then reboots the destination disk, which prints the Start
timesharing? prompt.
If you already have a file with the same name on your destination disk, you see the
message: FILE filnam.type EXISTS: SUPERSEDE? Type Y to replace the file with

Offline Options

207

COpy

the new file of the same name; type N to retain the file on the disk; press CTRL/C <to
abort COpy and return to the Option: prompt.
Table 20 lists the COpy error messages. If your error message does not appear there,
see Appendix A.
Table 20:

COpy Error Messages
Message and Meaning

CANNOT COpy TO THE SYSTEM DISK
You specified the RSTS/E Installation media, which is invalid as an output disk for the COPY
option. Specify another disk.
.
ILLEGAL DISK NAME
You typed an invalid disk name. All DF, DK, and DS disks are illegal.
INVALID UNIT NUMBER
The disk unit number you specified does not exist on this system.
INVALID RESPONSE
The only valid responses to the FILE FILNAM.TYP EXISTS: prompt are Y, N, or CTRUC, and
you typed something else.
SORRY, BUT THAT DISK DOESN'T EXIST
The disk type you specified does not exist on this system.

208

Offline Options

DATE

DATE- Set the Date and Time Format
The DATE option sets the date and time. Use the DATE option if:
• You need to reset or display the date.
• You need to reset or display the time.

DATE Dialogue
Option: DATE

Response -

Type DATE or DA to th~ Option: prompt.

Current date <DD-MMM-YY>?
Current tiMe <HH:MM AM/PM>?

Explanation brackets.
Response formats:

DATE asks for the new date and time. It prints the default format in

Type the date and time. You can enter the date in either of these

o DD-MMM-YY (day, month, year)
o YY.MM.DD (year, month, day)

You can enter the time in either of these formats:
o HH:MM AM/PM (hour, minute, AM or PM)
o HH:MM (24 hour clock)
Option:

Explanation -

INIT.SYS returns to the Option: prompt.

Offline Options

209

DEFAULT

DEFAULT -

Change RSTS/E Monitor Defaults
You can set the following defaults for your RSTS/E monitor with the DEFAULT
option of INIT.SYS:
• SWAP MAX - The maximum storage space a job can occupy in memory and
in the swap files. You can accept the default choice of 32K or choose a
different size.
o Primary run-time system -

You can accept the default choice (RSX) or
establish DCL as the primary run-time system.

o Memory for the extended buffer pool- INIT.SYS automatically allocates

memory to the extended buffer pool. You can change the amount by adjusting
the memory allocation table with the XBUF sub option.
o

Memory for the small buffer pool- INIT.SYS automatically allocates as much
memory as it can to the small buffer pool, depending on the monitor size. You
can change the amount by adjusting the memory allocation table with the
BUFFERS suboption.

o Memory for the virtual disk -

You allocate space by adjusting the memory
allocation table with the VIRTUAL suboption.

o System clock -

Choose the KW11-L line time clock or the KW11-P clock as

the system clock.

DEFAULT Dialogue
Opt i on : DEFAULT

Response - Type DEFAULT or DE to the INIT.SYS Option: prompt.
SWAP

ItlaX

<xxK>?

Explanation -

DEFAULT asks if you want to change the SWAP MAX.

The RSTS/E monitor constantly moves jobs from memory to disk. For a job to move
to disk, a special file must exist to store the job. This file is called a swap file. The
SWAP MAX or swap maximum is the maximum amount of disk storage space that a
job can occupy in a swap file when the job is swapped from memory to disk during
timesharing. The size of your SWAP MAX depends on the run-time systems you plan
to use, and whether you plan to write programs using Instruction and Data (1&0)
space.
The current setting is shown within angle brackets as the default answer to this
question.
Response - Type a number from 16K to 64K. To keep the value printed by
DEFAULT, press RETURN. Note that a SWAP MAX in the range 16K to 32K will
disable most DIGITAL system programs.
Run-tiMe SysteM <RSX>?

Offline Options

211

DEFAULT

Explanation - This question asks for the name of the primary run-time system
associated with your installed RSTS/E monitor. In V9.0, the primary run-time system
should be DCL or RSX. All run-time systems are stored as files in account [0,1] with
the file type .RTS. INIT.SYS establishes the default run-time system by searching the
directory for RSX and DCL, in that order.
Type the name of your primary run-time system, either RSX or DCL.
Or, press RETURN to accept the default (RSX in the example).

Response -

Any MeMOry allocation changes?
Table suboption? LIST
MeMOry allocation table:
OK: 00000000
53K: 003zaooo
5aK: 00330000
aa5K: 033SaOOO
512K: oaoooooo

- 00323777

- 00327777

- 03383777
- 03777777
- End

53K)
lK)
381K)
87K)

E}{EC
RTS ( RS}{)
USER
}{BUF
NXM

Explanation - DEFAULT now prints the memory allocation table prompt. At this
point you may want to adjust the memory allocation table. If so, answer YES to
this question, then go to the DEFAULT sub option sections that follow. Note that
DEFAULT automatically allocates memory to the Extended Buffer Pool and Small
Buffer Pool, based on the size and configuration of your system. Use the XBUF
suboption to change the amount of memory allocated to the Extended Buffer Pool,
and the BUFFERS sub option to change size of the Small Buffer Pool.
Type YES if you want to use one of the memory table sub options to
list or change the memory allocation table. Type NO to accept the current table.

Response -

If you want to list the current table, type YES to this question and then type LIST at
the Table suboption? prompt. Press RETURN at the Table suboption? prompt to
continue with the DEFAULT dialogue.
Preferred clocK <L)?

Explanation - Your hardware configuration can include one or both of these
system clocks: the KWII-L line time clock or the KWII-P programmable real-time
clock. The KWll-L line time clock divides system time into intervals based on the AC
line frequency of the power source used to run your PDP-II computer system. AC
line frequency can be either 50 Hz (the standard in many European countries) or
60 Hz (the standard in the United States).
The KWll-P programmable real-time clock can use the AC line frequency of the
power source to provide a system time base, or it can be set to provide a
crystal-controlled time base independent of the power source. This clock is useful in
areas where fluctuations in AC line frequency would adversely affect system timing.
Press RETURN to accept the default. If you have both clocks and the
default is not the clock you want, type L to use the KWII-L line time clock, or, type

Response -

212

Offline Options

DEFAULT

P to use the KW11-P programmable real-time clock. If you type L, DEFAULT goes
to the Option: prompt.
Interrupt frequency?

Explanation - This question appears only if you chose the KW11-P programmable
real-time clock. It asks for the frequency (AC line frequency or the crystal oscillator)
you will use for the time base.
Response - Type LINE to use the AC line frequency, unless you live in an area
where the line frequency is not accurately maintained by the power supplier (for
example, if diesel generators supply the power). In many areas, the AC line
frequency is more accurate than the crystal oscillator.

Or, type a number (a multiple of 50 ranging from 50 to 1000 interrupts/second) to
use the KW11-P's crystal oscillator for the time base.
Option:

Explanation - After you specify defaults for your RSTS/E monitor, DEFAULT
returns to the Option: prompt.

Table 21 lists the DEFAULT error messages. If your error message does not appear
there, see Appendix A.

Offline Options

213

DEFAULT

Table 21:

DEFAULT and Memory Allocation Table Error Messages
Message and Meaning

EXTENDED BUFFER SPACE NOT IN A VALID RANGE
The extended buffer space (XBUF) must fit entirely within the specified range. The legal ranges
for locating XBUF are between 16K and 512K (words), 528K and 1024K, 1040K and 1536K,
and 1542K and 2048K.
FILE NOT CONTIGUOUS
The file you specified is not contiguous on disk. The primary run-time system file and error
message file must be contiguous.
FILE NOT FOUND
The initialization code did not find the file you specified on disk.
ILLEGAL FILE NAME
The file name you specified is not one- to six-alphanumeric characters. Specify the correct
file name.
ILLEGAL 1K SECTION ADDRESS SPECIFIED
The address you specified is not a multiple of 4000(8) or is greater than 1919K (16774000(8)).
If you specified a range of addresses, the second of the two addresses must be greater than
the first.
ILLEGAL SUBOPTION GIVEN
Your response to the Table sub option? prompt is not a valid suboption name. Specify a valid
sub option name.
INVALID FILE FORMAT
The error message file you specified is not exactly sixteen blocks long. Make sure you copied
from the correct RSTS/E Distribution Kit.
INVALID MODULE FORMAT
The run-time system SIL module is too long, too short, or has an upper limit other than
177776(8). Make sure you copied from the correct RSTS/E Distribution Kit.
INVALID SIL FORMAT
The run-time system file does not contain a valid SIL index. Make sure you copied from the
correct RSTS/E Distribution Kit.
PART OF THAT AREA IS ALREADY IN USE
The region you specified is unavailable for use. Specify another area in memory for that region
or move the region currently occupying that area. (You can allocate space marked RTS to the
run-time system.)
PART OF THAT AREA IS NOT LOCKED
Part of the region you specified is not locked; therefore, you cannot unlock it.
RTS IS NOT A KEYBOARD MONITOR
The run-time system you specified is not a keyboard monitor. RSTSIE requires the primary
run-time system be a keyboard monitor (for example, DCL or RSX for the RSTS/E monitor).
Make sure you copied from the correct RSTS/E Distribution Kit.
TOO MANY MODULES
The run-time system SIL contains more than one module. If DIGITAL supplied the run-time
system, submit a SPR.

214

Offline Options

DEFAULT

DEFAULT Suboptions -

Adjust the Memory Allocation Table

The following sections describe the memory allocation suboptions of DEFAULT.
These suboptions allow you to adjust the memory allocation table of your installed
monitor.

If you install a new monitor, you may need to use the memory allocation sub options
again to adjust the new monitor's memory allocation table.
The memory allocation table sub options of DEFAULT are:
o LIST -

List the Memory Allocation Table
L~st the Parity Memory Configuration

o PARITY o LOCK o

Lock a Portion of Memory

UNLOCK -

o RTS -

Unlock a Portion of Memory

Position the Primary Run-Time System

o RESET -

Reset the Memory Allocation Table

o XBUF -

Allocate Memory to the Extended Buffer Pool

o BUFFERS -

Allocate Memory to the Small Buffer Pools

o VIRTUAL -

Allocate Memory to the Virtual Disk
\

Offline Options

215

DEFAULT

LIST -

List the Memory Allocation Table
The LIST sub option of DEFAULT lists the memory allocation table, which shows the
allocation of each block of memory.
Use the LIST sub option if:
o You want to print the most current memory allocation table.

• You want to print the table after adjusting the memory allocation table with one
of the other DEFAULT suboptions.

LIST Dialogue
Any MeMOry allocation

chan~es

(NO)? YES

Explanation - This is one of the DEFAULT dialogue questions. If you answer YES,
DEFAULT prompts for the table suboption.
Response - Type YES to adjust or list the memory allocation table. Or, type NO or
press RETURN to continue with the DEFAULT dialogue.
Table suboption? LIST

Explanation - You seethe Table suboption? prompt after you answer YES to the
Any memory allocation changes? question.
Response - Type LIST or LI to see the memory allocation table. Type EXIT or
press RETURN to continue with the DEFAULT dialogue.
MerrIOr}' allocation -table:
OK:
53K:
54K:
445K:
512K:

00000000
00324000
00330000
03384000
04000000

00323777
00327777
03383777
03777777
End

53K)
1K )

391K)
87K)

EXEC
RTS (RSX)
USER
>{BUF

Table suboption?

Explanation - Your table may not show the same values as the one in the
example. You read'this table as follows:
• Column one contains the start range (in K words) of memory. You read this
column vertically. In the example, the range starts at OK words and ends at
512K words.
• Columns two and three contain the starting and ending octal addresses for the
range of memory. In the example, 00000000 to 00323777 are the starting and
ending octal addresses for the RSTS/E monitor (EXEC).

216

Offline Options

DEFAULT

• Column four contains the amount of memory this range occupies in K words.
In the first line of the example, the RSTS/E monitor (EXEC) occupies 53K
words of memory.
• Column five specifies what occupies a particular range of memory:
- EXEC -

Represents the RSTS/E monitor, which always starts at OK words.

- RTS - Represents the primary run-time system; LIST prints your primary
run-time system in parentheses. In the example, the primary run-time system
is RSX.
- USER -

Represents I11emory available for user jobs.

- LOCKED - Represents memory unavailable for use (appears if you use the
LOCK suboption).
- XBUF -

Represents memory reserved for the extended buffer pool

- NXM -

Represents memory that does not exist on this PDP-II.

- VIRTUAL - Represe.nts memory reserved for the virtual disk (appears if you
use the VIRTUAL suboption).
Response - After DEFAULT lists the memory allocation table, it returns to the
Table sub option? prompt. Press RETURN to continue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table suboptions.

Offline Options

217

DEFAULT

PARITY -

List the Parity Memory Configuration
The PARITY sub option of DEFAULT identifies and locates the types of parity
memory. These types are parity memory and interleaved parity memory.
Use the PARITY suboption if you are a DIGITAL Field Service representative who
needs to verify the memory configuration during the installation of a PDP-1I.

Parity memory is memory that can detect certain errors. Interleaved parity memory is
memory in which alternate banks respond to sequential memory addresses, as in the
following:
Parity Register

Parity Register

BANKO

BANK 1

Addresses

000000

000002

000004

000006

000010

000012

Note that parity register 00 responds to the first address (000000), parity register 02
responds to the next address (000002), and so forth.
Core memory might have interleaved parity memory because it is a destructive
read-out device. The central processor or DMA device requests data. The RSTS/E
monitor reads the requested data from a memory bank located in core memory. After
the central processor or DMA device receives the requested data, this memory bank
remains busy until the memory hardware restores to it the original data. DUring this
restore cycle, the RSTS/E monitor can perform other functions, including another
read memory access in another bank.

If core memory has interleaved parity memory, the probability is low that the RSTS/E
monitor will access the same bank of memory on the next memory cycle. This allows
some overlap of memory read operations, resulting in faster program execution.
Some ECC MOS memory can be interleaved because on a write operation it takes
time for the memory controller to determine what error-correction bits to store with
the data. After the memory bank has accepted the data and the RSTS/E monitor
allows the central processor or DMA device to continue, the memory bank remains
busy until it has stored the data and new ECC bits. Because ECC MOS memory
exhibits the same characteristics as interleaved parity memory, the probability is low
that the RSTS/E monitor will access the same bank of memory on the next memory
cycle. This allows some overlap of memory write operations, thus resulting in faster
program execution.
Nonparity memory is not supported by the RSTS/E monitor.

218

Offline Options

DEFAULT

PARITY Dialogue
Table suboption?

PARITY

Explanation - You see the Table suboption? prompt after you answer YES to the
Any memory allocation changes? DEFAULT question.
Response - Type PARITY or PA.
Parity register usage:
OK:
128K:
25GK:
384K:

00000000
01000000
02000000
03000000

00777777
01777777
02777777
03777777

128K)
128K)
128K)
128K)

OO(ECC)
02(ECC)
04(ECC)
OG(ECC)

Table suboption?

Explanation - In the example, PARITY shows the memory configuration for a
PDP-11/44. Your parity memory depends on the type of PDP-II you have. After
PARITY prints the parity memory configuration, it returns to the Table suboption?
prompt.
The following defines the parity type codes you might see listed. The values nn and
mm are the last two octal digits of the address of the parity register that controls that
section of memory. Up to sixteen parity registers can exist. They are in the address
range 772100 to 772136. When the system detects a parity error, the parity register
responsible for that section of memory usually contains information on the location of
the last error discovered. The code NA indicates that the parity register contains no
error address information.
Symbol

Meaning

Nonparity memory.

NXM

Nonexistent memory.

nnmm

Interleaved parity memory with address information.

Parity memory with address information.

nn(NA)

Parity memory with no address information.

nn(ECC)

Memory with ECC hardware.

nn(ECC) mm(ECC)

Interleaved memory with ECC hardware.

Response - After DEFAULT lists the parity memory configuration, it returns to the
Table suboption? prompt. Press RETURN to continue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table suboptions.

Offline Options

219

DEFAULT

LOCK -

Lock a Portion of Memory

The LOCK sub option of DEFAULT locks certain portions of memory, which prevents
the use of that memory during timesharing.
Use the LOCK suboption only if:
o You need to lock a portion of defective memory. If sufficient undamaged

memory remains, you can start the monitor for normal timesharing.
o You want to start the RSTS/E monitor with less memory than is physically

available. This could be useful for developing applications that can run on a
smaller memory configuration.
Four examples of using the LOCK sub option are provided later in this section.
LOCK Dialogue
Table suboption? LOCK

Explanation - You see the Table sub option? prompt after you answer YES to the
Any memory allocation changes? DEFAULT question.
Response - Type LOCK or LO.
Loc~\

address is? 80K+l

Explanation want to lock.

LOCK asks you to specify the address or range of addresses you

Response - Type the address as a decimal number followed by the letter K. The
decimal number must in the range from 0 to 1919. In the example, the response is
90K+ 1.

Or, type the absolute address as a four- to eight-digit octal address. The octal number
must be a multiple of 4000 (8) that is less than or equal to 16774000.
Or, specify a range of addresses by typing either two addresses separated by a
hyphen (for example, 45K-47K) or an address followed by a plus sign and a number
that represents the size of the range (for example, 45K + 3).
Table suboption? LIST

Explanation - After you specify an address, LOCK returns to the Table suboption?
prompt.

220

Offline Options

DEFAULT

Response - Type LIST or LI to list the memory allocation table and check that you
have locked the correct area of memory.
MerTlo ry allocation table:
OK:
53K:
54K:
80K:
81K:
445K:
512K:

00000000
00324000
00330000
00550000
00554000
03364000
04000000

- 00323777
- 00327777

- 00547777
- 00553777
- 03363777
- 03777777

- End

53K)
1 K)
36K)
1 K)
354K)
67K)

EXEC
RTS (RS}-{)
USER
LOCK
USER
XBUF
NXM

Table 5uboption?

Explanation - The memory allocation table shows that 1K of memory is now
locked.
Respc.nse - After DEFAULT lists the memory allocation table, it returns to the
Table suboption? prompt. Press RETURN to continue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table suboptions.

Using the LOCK Suboption
Certain types of memory failures affect only one word of memory; other types affect
larger sections or even the entire hardware bank. You must carefully analyze any
memory failure to determine the 1K section of memory to lock. Additionally, after
you lock memory, list the memory allocation table to make sure that sufficient
contiguous user memory is available to run your installation's programs.
Before you lock a portion of memory, you should be aware of the following
restrictions:
o You cannot lock memory used by the monitor.
o You cannot lock memory currently allocated to the primary run-time system

until you relocate it to a usable area of memory (memory that is unlocked and
available for use). You relocate the primary run-time system by using the RTS
memory allocation table sub option.
• You cannot lock memory currently reserved for the extended buffer pool
(XBUF) until yoy. relocate it to a usable area of memory.
• You cannot lock a full bank of memory, until you locate all of the 4, 8, 16, 32,
64, or 128 contiguous 1K sections that make up the hardware bank. If the bad
memory is interleaved, you must lock an amount of memory equal to twice its
length. On a PDP-11170 with external interleaving, you must lock an amount of
memory equal to four times its length.
If you attempt to lock any of these areas of memory, LOCK prints the message: Part
of that area is already in use.

Offline Options

221

DEFAULT

RSTS/E can continue running with certain types of memory failures. The error
handling routines in the monitor log parity errors when they are detected by the
hardware. The recovery procedures depend on the use of the section of memory that
failed. Consider the following four cases of memory failure and recovery procedures.

Case 1: A parity error occurs when the monitor is running. Since continued system
operation would be risky, the monitor logs the error, takes a crash dump (if the crash
dump facility is enabled), and reloads the system. When the system restarts, you
should use the ANALYS program to extract the error log information from the
CRASH.SYS file.
The ERRDIS report, which the monitor automatically appends to the ANALYS report,
provides sufficient information to identify the section that should be locked out. If the
error occurred in the primary run-time system or extended buffer area of memory,
you can relocate these items and lock the section. If the error was in monitor
memory, the hardware must be repaired or reconfigured. In either case, a hard failure
may prevent the system from running at all; thus, you can run neither ANALYS nor
ERRDIS. The only recourse in such cases is to run memory diagnostics to locate the
problem. If the failure was transient, you can shut down the system to lock out
memory or you can continue timesharing. If possible, you should run memory
diagnostics to reproduce the failure.
Case 2: A parity error occurs when a user job is running. The parity error handling
routines determine whether a single user job is affected (that is, resides in the
malfunctioning section) or more than one user job is affected. If more than one user
job is affected, the system is reloaded as Case 1 describes. If a single user job is
affected, the system aborts that user job with the error message?Memory parity
failure. The monitor logs the error, automatically locks out the section of memory
from future use (for the duration of the timesharing session), and the system
continues running. You should lock out the bad section of memory (until repaired),
using the LOCK suboption the next time you start the system.
Case 3: Multiple parity errors occur in rapid succession. RSTS/E halts at location 54
(the program counter displays 56) if a second parity error occurs while the system is
processing the first parity error. A DIGITAL Field Service representative will use
memory diagnostics to locate the failing memory.
Case 4: A memory cache parity error occurs. If the hardware memory cache
malfunctions and causes a parity error, the hardware again retrieves the needed word
from main memory and causes a warning parity trap to occur. RSTS/E logs this type
of error. If the error occurs twice within one minute, RSTS/E disables the part of the
cache causing the malfunction. RSTS/E continues running, but with degraded
performance. The system does not print a message, but two successive errors within
the same minute in the ERRDIS print-out should alert you.
On systems without parity or ECC memory, the software cannot detect or locate a
memory failure. Programs may get incorrect results, memory management errors may
occur, or any number of random problems may happen. At worst, the system may
crash with misleading clues as to the cause. It is for these reasons that RSTS/E is not
supported on systems that use nonparity memory.

222

Offline Options

DEFAULT

UNLOCK -

Unlock a Portion of Memory
The UNLOCK sub option of DEFAULT unlocks certain portions of memory to make
the memory available for use during timesharing by user jobs, the primary run-time
system, or the extended buffer pool (XBUF).
Use the UNLOCK sub option if you need to unlock a portion of memory you
previously locked with the LOCK sub option.

UNLOCK Dialogue
Table suboption? UNLOCK

Explanation - You see the Table suboption? prompt after you answer YES to the
Any memory allocation changes? DEFAULT question.
Response - Type UNLOCK or UN.
UnlocK address is? 80K+l

Explanation - UNLOCK asks you to specify the address or range of addresses you
want to unlock.
Response - Type the address as a decimal number followed by the letter K. The
decimal number must be in the range from 0 to 1919. In the example, the response
is 90K+ 1.

Explanation - After you specify an address, UNLOCK returns to the Table
sub option? prompt.

Offline Options

223

DEFAULT

Response - Type LIST or LI to list the memory allocation table and check that you
have unlocked the correct area of memory.
MeMOry allocation table:
OK:
53K:
54K:
445K:
512K:

00000000
00324000
00330000
03364000
04000000

00323777
00327777
03363777
03777777
End

53K)
1 K)

391K)
67K)

EXEC
RTS (RS){)
USER
){6UF

NXM

Table 5uboPtion?

Explanation - Note that UNLOCK removes the lK area of memory that was
locked in the previous example.
Response - After DEFAULT lists the memory allocation table, it returns to the Table sub option? prompt. Press RETURN to continue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table suboptions.

224

Offline Options

DEFAULT

RTS -

Position the Primary Run-Time System
The RTS sub option positions the primary run-time system anywhere in the first 124K
of memory. Normally, DEFAULT automatically positions the primary run-time system
immediately after the RSTS/E monitor, in the lowest physical memory addresses.
Use the RTS suboption if:
o You need to position the primary run-time system to avoid defective memory.

• You want to position the BASIC-PLUS primary run-time system in high-speed
memory, if your system has different types of memory. This is primarily used
with PDP-11/45s, 11150s, and 11/55s.

RTS Dialogue
Table suboPtion? LIST

Explanation - You see the Table suboption? prompt after you answer YES to the
Any memory allocation changes? DEFAULT question.
Response - Before you position the primary run-time system, it is useful to list the
memory allocation table. Type LIST or LI.
MetTlo ry allocation table:
OK:
53K:
5l1K:
lIlI5K:
512K:

00000000
00323777
003211000 - 00327777
00330000
03383777
033811000
03777777
OllOOOOOO - End

53K)
lK)
381K")
87K)

E}{EC

RTS (RSX)
USER
XBUF
N}{M

Table suboption? RTS

Response - Type RTS.
New Run TiMe SYsteM address is? 115K
Table suboption? LIST

Explanation - RTS asks you to specify the address where you want to position the
primary run-time system.
Response - Type the address as a decimal number followed by the letter K. The
decimal number must be in the range from 0 to 124 minus the size of the run-time
system. In the example, the response is 115K.
There must be enough free contiguous space for the primary run-time system
between the starting address you specify and 124K.

Offline Options

225

DEFAULT

After you specify the address, RTS returns to the Table suboption? prompt. Type
LIST to list the memory allocation table again to see that the monitor positioned the
primary run-time system correctly.
MeMOry allocation table:
OK:
53K:
115K:
118K:
llll5K:
512K:

00000000
003211000
007111000
00720000
033811000
OllOOOOOO

- 00323777
- 00713777
- 00717777
- 03383777
- 03777777
- End

53K)
82K)
1 K)
329K)
87K)

EXEC
USER
RTS ( RS}{)
USER
}{BUF
NXM

Table 5uboption?

Explanation - The memory allocation table shows that the primary run-time
system now resides at 115K.
Response - After DEFAULT lists the memory allocation table, it returns to the
Table suboption? prompt. Press RETURN to continue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table suboptions.

226

Offline Options

DEFAULT

RESET -

Reset the Memory Allocation Table
The RESET suboption removes any changes made to the memory allocation table;
for example, locked portions of memory, reserved memory for the extended buffer
pool, and nonstandard placement of the run-time system.
Use the RESET suboption only if you want to set up the memory allocation table in
the following way:
o Place the primary run-time system in low memory, immediately after the

monitor.
o Release any memory previously allocated to the extended buffer pool (reduces

the extended buffer pool to 2K words).
o Release any memory you previously locked.
o Release any memory you previously allocated to the virtual disk.

RESET Dialogue
Table 5uboption? LIST

Explanation - You see the Table sub option? prompt after you answer YES to the
Any memory allocation changes? DEFAULT question.
Response - Before you reset the memory allocation table, it is useful to list the
current one. Type LIST or LI.
MeMOry allocation table:
OK: 00000000 - 00327777
saK: 00330000 - 00333777
SSK: 0033aooo - 03363777
aaSK: 0336aooo - 03777777
S12K: oaoooooo - End

SaK)
1K )

380K)
67K)

EXEC
RTS (RS}{)
USER
}{BUF

NXM

Table 5uboption? RESET

Explanation - LIST shows a memory table for an example installation. Note that
the example table allocates 67K words of memory to XBUF.
Response - Type RESET or RE.
Table 5uboption? LIST

Explanation - DEFAULT immediately resets the memory allocation table and
returns to the Table suboption? prompt.

Offline Options

227

DEFAULT

Response - It is useful to list the current memory allocation table after you use the
RESET suboption. Type LIST or LI.
MerTlo r>' allocation table:
OK:
511K:
55K:
510K:
512K:

00000000
00330000
003311000
03770000
011000000

- 00327777
- 00333777
- 03787777

- 03777777
- End

511K)

lK)
1155K)
2K)

E}{EC
RTS (RS}{)
USER

}-{BUF
N}{M

Table suboption?

Explanation - Note that RESET deallocated all memory previously allocated to
XBUF and returned it to USER memory.
Response - After DEFAULT lists the memory allocation table, it returns to the
Table suboption? prompt. Press RETURN to continue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table suboptions.

228

Offline Options

DEFAULT

XBUF -

Allocate Memory to the Extended Buffer Pool

The XBUF sub option reserves memory for the extended buffer pool.
INIT.SYS automatically allocates memory to the extended buffer pool during system
installation. INIT.SYS determines how much memory to allocate based on the
amount of USER memory available on the system. USER memory is memory that is
not allocated to any other entity. It contains memory that is not locked, not allocated
to the monitor, and not allocated to the run-time system.
INIT.SYS determines the size and position of XBUF based on the following
guidelines:
o If the amount of USER memory exceeds 128K words, then INIT.SYS allocates

15% of that memory (rounded down to the nearest whole number) to XBUF.
o If the amount of USER memory is less than 128K words, then INIT.SYS

allocates 10% of that memory (rounded down to the nearest whole number) to
XBUF.
o INIT.SYS first attempts to position XBUF at the highest possible memory

address. If for some reason INIT.SYS cannot allocate a sufficient amount of
contiguous high memory, it positions XBUF at the lowest possible address.
o The minimum amount of memory allocated to XBUF is 2K words. The

maximum is 496K words.
o The legal ranges for locating XBUF are between 16K and 512K (words), 528K

and 1024K, 1040K and 1536K, and 1542K and 2048K.
If you are not familiar with the use of extended buffers on RSTS/E you should read
the section, Extended Buffer Pool Background Information, before proceeding.
XBUF Dialogue
Table suboption? XBUF

Explanation - You see the Table sub option? prompt after you answer YES to the
Any memory allocation changes? DEFAULT question.
Response - Type XBUF.
Enter new extended buffer address size (lK-4S6K) (8K)? 67K

Explanation - XBUF asks for the amount of memory you want to reserve for the
extended buffer pool (XBUF). You do not need to specify the location of XBUF,
because INIT.SYS automatically pOSitions it according to the gUidelines given at the
beginning of this section.
Response - Specify the new size of XBUF, followed by K to indicate K words. In
the example, the response is 67K.

Offline Options

229

DEFAULT

To release previously allocated memory for the extended buffer pool h... user memory,
type RESET.
Table 5uboption? LIST

Explanation - After DEFAULT adjusts the memory allocation table, it returns to
the Table suboption? prompt.
Response - Type LIST or LI to list the memory allocation table and check that you
have reserved the correct area in memory.
MehlO ry allocation table: .
OK:
53K:
54K:
445K:
512K:

00000000
00324000
00330000
03364000
04000000

- 00323777

- 00327777
- 03363777
- 03777777
- End

53K)
lK)
381K)
67K)

EXEC
RTS (RS}{)
USER
XBUF
NXM

Table 5uboption?

Explanation - The memory allocation table shows the size and location of the
memory you have reserved for the extended buffer pool. For example, in this table
67K words are reserved for XBUF.
Response - After DEFAULT lists the memory allocation table, it returns to the
Table suboption? prompt. Press RETURN to continue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table sub options.

Extended Buffer Pool Background Information
Figure 5 shows an example RSTS/E system. It shows that memory is divided into:
• Monitor memory (EXEC) - an area of memory reserved for your RSTS/E
monitor. Monitor memory in the example occupies 53K words.
• Run-time system memory (RTS) - an area of memory reserved for your
primary run-time system. In the example, the primary run-time system is RSX
and occupies lK word.
• User memory (USER) - an area of memory reserved for user jobs. In the
example, user memory occupies 391K words.
• Extended buffer pool (XBUF) - an area of user memory reserved for
extended buffers. An extended buffer is a block of storage located in the
extended buffer pool that can range in size from 32 words to the maximum size
of the extended buffer pool. In the example, the size of the extended buffer
pool is 67K words. The extended buffer pool occupies USER memory; thus,
releasing 67K words from the extended buffer pool would increase USER
memory to 458K words.

230

Offline Options

DEFAULT
OK

EXEC
(RSTS/E
Monitor)

53K Words
53K
54K

RTS (RSX)
USER

1K Word

391 K Words

445K ,-==-----=======---::::=====-T XBUF

<§wor~

extended
buffer
pool

CKword00Kwor0

~I~

512K _______________E_x_te_n_de_d_b_u_ffe_r_s_______________
MK-01095-02

Figure 5:

Extended Buffer Pool for Example RSTS/E System

Offline Options

231

DEFAULT

When the monitor needs an extended buffer to store information, it looks in the
extended buffer pool. When the information stored in the extended buffer is no
longer needed, the monitor returns the buffer to the extended buffer pool for reuse.
The size of the extended buffer pool depends on the type of processing and the
amount of memory on your system. Allocating enough memory to the extended
buffer pool increases the number of available extended buffers, which has the
following advantages:
o The monitor can output more data and/or directory information. This means

the monitor stores certain data and directory-related information in the
extended buffers. This reduces the number of times disk input/output occurs,
which results in improved system response.
• The monitor can output more line printer data (if you selected the line printer
caching feature). This means the monitor stores line printer output in the
extended buffers. This reduces the stalling frequency of the line printer when
printing data.
o The monitor can store some kinds of information in either extended buffers or

in general small buffers (see the following BUFFERS suboption). Because the
number of general small buffers is limited, the monitor uses extended buffers
whenever they are available to reduce the demand for general small buffers.
Keep the following memory constraints in mind when you are deciding how much
memory to allocate to the extended buffer pool:
• You should be able to fit at least two jobs at SWAP MAX (or the average job
size, if known) in memory. If you cannot do this, then you may have to reduce
the amount of memory you allocated to the extended buffer pool.
• During start-up, INIT.SYS uses an 8K-word area of memory to complete the
loading of the monitor. This 8K-word area is allocated from either RTS or
USER (see the memory allocation table) and must be above the INIT.SYS
image. If INIT.SYS cannot find an 8K word area of memory above the
INIT.SYS image (68K words) and below 124K words, it prints the error
message: Need at least 8KW nonmonitor memory below 124K to start.
If your primary run-time system is 8K words or larger (Del), there is no
problem. If your primary run-time system is smaller than 8K words (RSX), then
the monitor uses any combination of RTS and USER memory, if the RTS
memory is adjacent to user memory. Otherwise, the monitor uses USER
memory.

232

Offline Options

DEFAULT

The following sections discuss guidelines for determining the amount of user memory
you should reserve for the extended buffer pool with respect to:
o Message send/receive code
o

Line printers

Data caching

Directory caching

o DCL indirect command file I/O and/or terminal logging
o System logicals
o DECnet/E software
o RJ2780 software
o 2780/3780 software
o

Statistics

o Quota information .
o Resident overlay code

Message Send/Receive Code
The RSTS/E monitor uses extended buffers to store messages generated by programs
that use the message send/receive code. You might want to use the following as a
guide in determining how many messages are generated for a typical system:
o Error logger -

2 messages

o OPSER-based spooling package:

- OPSER -

2 messages

- QUEMAN -

2 messages

- 1 line printer spooler - 2 messages
- 1 batch spooler -

2 messages

o Print/Batch services package -

3 messages

Each message requires N words of extended buffers where N is the length of the
message in words plus 4 words, rounded to the next multiple of 32 words. A mes. sage always uses at least 32 words of extended buffers. Each message can range
from 32 to 288 words.

Offline Options

233

DEFAULT

Line Printers
The RSTS/E monitor uses extended buffers (or general small buffers) to store
characters awaiting printing on a line printer. (You must have answered YES to the
Extended data buffering for LP? question in Phase 3 of Part I.) You should allow
2.5K words of memory for the extended buffer pool for each line printer.

Data Caching
The monitor uses extended buffers to store the activities resulting from data caching.
Data caching is a software feature that reduces the number of data transfers from disk
to memory, thereby improving response times. (You have data caching only if you
.
answered YES to the Data caching? question in Phase 3 of Part I.)
A general gUideline is to allocate about 15 % of total USER memory to the extended
buffer pool to accommodate data caching. However, the monitor cannot use more
than the following maximum values. If you allocate more memory than the maximum
amount, it is used by LPDVR, DEC net, RJ2780, logicals, DCL commandllog buffers,
or others from the previous list.

Cache
Cluster Size

Maximum XBUF Usage

130K words

257K words

496K words

496K words
Note - - - - - - - - - - - -

The monitor uses extended buffers (or general small buffers) for
directory caching only when they are not needed for other purposes.
If you also have data caching on your system, the monitor uses only
extended buffers.

Directory Caching
The monitor uses extended buffers to store the activities resulting from directory
caching, a software feature that accelerates file processing. In V9.0, you automatically
have directory caching. Directory caching uses extended buffers that are 256 words in
size, and at most can occupy 173K words of memory in the extended buffer pool.
If you allocate more than 8K words to the extended buffer pool, the monitor will not
use general small buffers for directory caching, thereby reducing CPU overhead. A
general gUideline is to allocate about 10% of total USER memory to the extended
buffer pool to accommodate directory caching.
'

234

Offline Options

DEFAULT

DCl Indirect Command File 1/0 and Terminal logging

The monitor uses extended buffers to store messages generated by indirect command
file liD and terminal logging. You should allow 1/4K word per simultaneous
command file liD andlor terminal logging.
System logicals

The monitor uses extended buffers to store system logicals. You should allow 1K
word per 320 logicals.
DECnetiE Software

The monitor uses extended buffers to store messages generated by DECnetiE
software. See the DECnetlE Installation Guide for information on how much memory
to reserve for the extended buffer pool.
RJ2780 Software

The monitor uses extended buffers to store messages generated by the RJ2780
software. This software requires 1K word of memory for the extended buffer pool.
See the RJ2780 documentation.
2780/3780 Software

See the 2780/3780 documentation for extended buffer pool considerations.
Statistics

The monitor uses approximately 1K word per 14 disk units. If insufficient extended
buffer space is available at system startup, the monitor disables statistics with no
message.
Quota Information

The monitor requires 1K word of extended buffer space for every 96 different
accounts for which there are open files or to which a user is logged in, on a per user
basis. Note that the monitor considers a logged-in user as an open file on the system
disk.
.
Resident Overlay Code

The monitor uses extended buffer space for resident overlay code. The amount can
vary, depending on the overlay. After you load an overlay, use the SHOW CACHE
command to see the extended buffer usage, and adjust XBUF accordingly.

Extended Buffer Pool Worksheet
Figure 6 summarizes the items requiring extended buffers, and the approximate
amounts of memory each requires. Space is provided to enter the size needed for
your system. Use this worksheet as a guide to reserving memory for the extended
buffer pool. Remember, you can determine the optimal size only through
experimentation. Use the SHOW CACHE command to show some of the extended
buffer pool usage for your system.

Offline Options

235

DEFAULT

Items Requiring Extended Buffers

Your Size

Contents of messages sent and waiting to be received'"
Line printer driver*
Data caching
Directory caching*
DCl indirect command file 110 and terminal logging
System logicals
DECnetJE
RJ2780

2780/3780 software
Statistics
Quota information
Resident overlay code

Total**

* The RSTSIE monitor can also use general small buffers to store these items.
** Reduce the extended buffer pool if two jobs at SWAP MAX will not fit in the USER area
of memory.

MK-01096-01

Figure 6:

236

Offline Options

Extended Buffer Pool Worksheet

DEFAULT

BUFFERS -

Allocate Memory to the Small Buffer Pools
The BUFFERS sub option reserves more memory for the small buffer pools. Use the
BUFFERS sub option if your RSTS/E monitor needs more small buffers to run
efficiently.
Before you decide whether to change the amount of memory allocated to the small
buffer pool, you should read the information in the section, Small Buffer Pool
Background Information.
Consider the following when deciding when to increase the memory reserved for the
small buffer pool:
o You should provide an adequate supply of small buffers for periods of heavy

system use. Thus, you should assume that the system is using the maximum
number of jobs, all terminals, and all printers.
o The number of small buffers a program uses depends on what it is doing. For

example, a program that opens 12 files at once requires more buffers than
other programs. This guide offers gUidelines, which you must follow and adjust
according to the needs of your installation.
o Some software features use buffers momentarily, but it is difficult to ca!culate

how many small buffers you will need for momentary use. DIGITAL
recommends that you add 100 to 150 small buffers to your final figure.
Seventy-five of these buffers go towards keeping the number above 75 most of
the time.

BUFFERS Dialogue
Table suboption? BUFFERS

Explanation - You see the Table suboption? prompt after you answer YES to the
Any memory allocation changes? DEFAULT question.
Response - Type BUFFERS or BU.
HOI,.! Itlany K-I. . lords of extra buffer space (OK-2K) <OK)? 2K
You have 472 ~eneral + 132 FIP SMall buffers.
AdJustin~ MeMOry table
MeMory allocation table:
OK:
55K:
58K:
445K:
512K:

00000000 - 00333777
00334000 - 00337777
00340000 - 03383777
03384000 - 03777777
04000000 - End

55K)
1 K)

388K)
87K)

E~{EC

RTS (RS~-{)
USER
XBUF

Table suboption?

Offline Options

237

DEFAULT

Explanation - BUFFERS prints the range you can specify for your system. In the
example, the range is OK words to 2K words. The default value is OK when you
answer this question for the first time. The next time you select the BUFFERS
suboption, the default value is the value you selected the last time you answered the
question.

The range is larger for systems with processors that have data space. If you have data
space, you can use the BUFFERS suboption to -increase the memory reserved for the
small buffer pool to accommodate more general and FIP small buffers. If you do not
have data space, you can increase the memory reserved for the small buffer pool to
accommodate only FIP small buffers. (You must perform another system installation
to add more general small buffers if you do not have data space.)
Response - Type the number of K words to reserve for the small buffer pool.
DIGITAL recommends you specify the maximum. You can lower this later if you
discover your system continually has over 250 free general small buffers.

After your response, BUFFERS prints the number of general and FIP small buffers
that your system will have available for use during timesharing. Of the memory
added, BUFFERS creates as many general small buffers as it can (if you have data
space) and gives the remaining space to FIP small buffers. In the example, the
response of 2K accommodates 132 FIP small buffers.
When you increase memory for the small buffer pool, the size of the monitor
increases and the size of USER memory decreases. DEFAULT then lists the new
memory allocation table.
The following should help you further in answering this question. Remember that in
Task 6 of Phase 3 in Part I you answered the Small buffers? configuration question.
The question printed a default response, which indicated how many general small
buffers you currently had. Because the size of the RSTS/E monitor is always rounded
up to a multiple of lK word, there is usually some extra space. The RSTS/E monitor
fills this extra space with FIP small buffers.
Remember also that during system installation you saw a buffer table that shows how
many general and FIP small buffers you currently have. In addition, the table tells
you how many you can add. Figure 7 shows a sample table. The table tells how
many general and FIP small buffers you can add if you have data space and how
many FIP small buffers you can add if you do not have data space. Because the
PDP-II in this example installation has data space, it can increase memory for the
FIP small buffer pool to accommodate more FIP small buffers.

238

' Offline Options

DEFAULT

Resident Monitor size is 51K. By increasin~ this size
with the DEFAULT option of INIT, YOU can ~et additional
sMall buffers. This table shows the nUMber and type of
sMall buffers YOU can ~et with each size change.
Additional
K-INords of
buffer space

NUMber of buffers
With Data Space
Without Data Space
General
FIP
General
FIP

aaa
a72
a72

OK
lK
2K
3K
aK
5K
6K
7K
SK
8K
10K
11K

620
6aS
6aS
6aS
6aS
6aS
6as
6aS
6aS

2
36
100
lS
52
116
lS0

aaa
aaa
aaa

2
66
lOS

2aa

30S
372

a36
.l8a

If }' a u choose to pe rf 0 rlTI another installation, }' 0 u ITla }' specif}' UP
to 572 SITla 11 buffers for this systelTI. Doing so 1...1i 11
increase SOITle of the buffer counts in the table.

Figure 7:

Example Small Buffer Table Printed During System Installation

A K word is equal to 64 small buffers; however, when you select the maximum
number, the last K word generally contains fewer than the 64 maximum. When
selecting the amount of extra buffer space, you should determine how many buffers
the last K word contains and decide if you want to allocate 1 K word of memory for
the number of buffers you gain. For example, if the difference between specifying 2K
or 3K word~ of extra buffer space gives you only 10 more small buffers, it may not
be worth the cost of lK word of physical memory.
Table suboption?

Response - After DEFAULT lists the memory allocation table, it returns to the
Table sub option? prompt. Press RETURN to continue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table suboptions.
Small Buffer Pool Background Information

Figure 8 shows an example RSTS/E installation. It shows that memory is divided into:
o Monitor memory (EXEC) -

An area of memory reserved for the RSTS/E
monitor. Monitor memory in the example installation occupies 53K words. Note
that the size of the monitor increases to 55K words after the example
installation allocates 2K words for the FIP small buffer buffer pool. The size of
your monitor may differ.

Offline Options

239

DEFAULT
OK
general small
buffer pool
(resulting from
data space)
general small
buffer pool
(resulting from
SYSGEN question)

{

general
~wor~~wor~ 16wor~ small buffers

~wor~@Wor~

{

EXEC
(RSTS/E
Monitor)

16 wor~

~wor~@wo~ 16wor~ FI P small buffers
{
FIP small {
~wor~~wor~ 16wor~
55K
buffer pool

FIP small
buffer pool

(resulting from
data space)

RTS (RSX)

1K Word
56K

USER

389K Words

445K
extended
buffer pool

XBUF
67K Words

512K
MK-01097-01

Figure 8:

General and FIP Small Buffer Pools

240

Offline Options

DEFAULT

o Run-time system memory (RTS) -

An area of memory reserved for your
primary run-time system. In the example installation, the primary run-time
system is RSX and occupies lK word.

o User memory (USER) -

An area of memory reserved for user jobs. In the
example installation, USER memory occupies 391K words. Note that the size of
USER memory decreases to 389K words after the example installation allocates
2K words for the FIP small buffer pool. The size of your USER memory may
differ.

o Extended buffer pool (XBUF) -

An area of memory reserved for the extended
buffer pool. In the example, XBUF memory occupies 67K words. (See the
previous section for a discussion of the extended buffer pool.)

Figure 8 also shows that monitor memory contains the:
o General small buffer pool -

an area of monitor memory that contains general
small buffers. Note that there are two types of general small buffer pools: one

that is created as a result of answering the Small buffers? configuration question
in Phase 3 of Part I, and one that is created using the BUFFERS suboption.
You can create this second small buffer pool only if you have a hardware
feature on your CPU called data space. Data space is available on the
PDP-11/44, 11/45, 11/50, 11155, 11170, 11/73, 11/83, or 11184 and only if
you do not use RJ2780 software.
o FIP small buffer pool -

an area of monitor memory that contains FIP small
buffers. There are also two types of FIP small buffer pools: one that you can

create with the BUFFERS sub option alone, and the other you can create with
the BUFFERS sub option and with data space. Figure 8 illustrates these two FIP
small buffer pools.
The RSTSIE monitor uses general small buffers as.a temporary storage area for such
things as:
o The input and output of characters

• Data transfers
o Send/receive messages
o File processing requests

• Information on open files and DCL file information
• CCL command definitions
• Asynchronous liD requests
• Run-time system and library deSCriptions

Offline Options

241

DEFAULT

In contrast to general small buffers, FIP small buffers are used only to store open files
information, eel command definitions, and Del file information. When the monitor
needs a small buffer to store open files or eel command definitions information, it
looks in the FIP small buffer pool for a FIP small buffer. This leaves the supply of
general small buffers free to store other kinds of activity that the FIP small buffers
cannot handle. If there are no free FIP small buffers, the monitor uses general small
buffers to store the open files information and eel command definitions. When the
information stored by either small buffer is no longer needed, the monitor returns the
small buffer to the appropriate small buffer pool for reuse.
The general small buffer supply is critical to your system's performance. The number
of free general small buffers varies from second to second. When this number is less
than 75, the following occurs:
o Jobs begin to stall, until some small buffers become available to process the

jobs' requests. Thus, performance begins to suffer.
o The monitor discards error information destined for the error logger.
o The error message ?No logins appears when users try to log in. (This happens

when the number of general small buffers falls below 40.)
o Batch jobs do not start. (This happens when the number of general small

buffers falls below 40.)
o Programs begin to fail with the message ?No buffer space available.

The number of general small buffers should stay well above 75 for good system
performance. Because FIP small buffers reduce the demand on general small
buffers, the number of FIP small buffers may drop to zero without any loss to
system performance.
The IF (Free) switch of the SYSTAT program displays the number of available
general small buffers and FIP small buffers as well as other system statistics. The
SHOW BUFFERS command gives the same display as the SYSTAT program. The
RSTSIE Utilities Reference Manual describes SYSTAT.
The rest of this section discusses gUidelines for determining how many small buffers
you need with respect to:
o Jobs
o eel command definitions
o AUxiliary run-time systems
o Resident libraries
o Open files and Del file information
o Message receivers
o list of messages sent and waiting to be received

242

Offline Options

DEFAULT

o Contents of messages sent and waiting to be received

o Terminals
o line printers
o Paper tape punches
o

EMT logger

o Outstanding I/O requests
o BACKUP program
o Margin of safety

Jobs
The monitor uses general small buffers to store information about each job. Allow
three general and two FIP or general small buffers per job.
eeL Command Definitions
The monitor uses general or FIP small buffers to store CCl command definitions.
Allow one general or FIP small buffer for each defined CCl command. See the
RSTS/E System Manager's Guide for a description of CCl command definitions and
the Del DEFINE command, which you use to define eCl commands.
Auxiliary Run-Time Systems
The monitor uses general small buffers to store information about auxiliary run-time
systems that you add with the Del INSTALL command. Allow one general small
buffer for each aUxiliary run-time system.
Resident Libraries
The monitor uses general small buffers to store resident libraries. Allow one general
small buffer for each resident library and each dynamic region. Allow one to four
general small buffers for each program that uses libraries. Allow two buffers for
programs that use RMS libraries.
Open Files and DeL File Information
The monitor uses general or FIP small buffers to store descriptions of open files. The
monitor uses FIP small buffers first, if they are available. A program can open a file
on more than one I/O channel, and more than one program can open the same file
at the same time.

Offline Options

243

DEFAULT

For each program allow:
o One general or FIP small buffer for each open file.
o One general or FIP small buffer for each channel on which the file is open;

however, you need two general or FIP small buffers for each channel on which
the file is open if you use update mode. See the RSTS/E Programming Manual
for a discussion of update mode.
o One FIP or general small buffer per open file on DCl's I/O channel.
o One FIP or general small buffer for each active command file or terminal

command file.
List of Message Receivers
The monitor uses general small buffers to store a list of message receivers. Many
system programs (including Print/Batch Services, QUEMAN, ERRCPY, and OPSER)
receive messages through the send/receive system function calls. These system
function (SYS) calls need one general small buffer for each message receiver.
Messages Sent and Waiting To Be Received
You need one general small buffer for each message sent and two general small
buffers for each receiving job.
Contents of Messages Sent and Waiting to be Received
The monitor stores the contents of messages sent in general small buffers if it cannot
use extended buffers. If you did not include this item when you reserved memory for
the extended buffer pool, you should include it in your general small buffers
calculation. The number of messages that the monitor can store in the general small
buffer pool depends on the size of the messages and the speed with which the
receiving job processes them.
You need N general small buffers for each message
where:
N = (length of message in bytes + 8)

32
For example, you might figure that the average message contains 25 to 56 bytes,
which occupies two general small buffers. If your system processes many messages,
you can improve system performance by allocating memory to the extended buffer
pool for these messages.

244

Offline Options

DEFAULT

Terminals
The monitor uses general small buffers to store:
o Characters written by a job and awaiting display on a terminal
o Characters typed by a user and waiting to be read by a job
o Characters written by a job and awaiting printing on a hard-copy terminal

You should allow:
o Five general small buffers for each interactive terminal, several more if you use

echo control and FMS
o Ten general small buffers for each hard-copy terminal

Line Printers
The RSTS/E monitor uses general small buffers (or the extended buffer pool) to store
characters awaiting printing on a line printer. (You must have answered YES to the
Extended data buffering for LP? question in Phase 3 of Part I.) If you reserved
memory in the extended buffer pool for line printers, you need not specify any small
buffers. If you need general small buffers for this purpose, specify 20 for each line
printer.
Paper Tape Reader/Punch
The monitor uses general small buffers to store characters awaiting punching or
reading on a paper tape reader/punch. Allow for 10 general small buffers for the
paper tape punch.
EMT Logging
The monitor uses general small buffers to store messages generated by EMT logging.
(You are concerned with this only if you answered YES to the EMT logging? question
in Phase 3 of Part I. ) You should specify 1 general small buffer if you have EMT
logging.
Outstanding I/O Requests
Each outstanding I/O request needs one small buffer plus the follOWing driver
requirements:
• Asynchronous tape drivers -

one general small buffer per outstanding request

• DiSk drivers - at least one general small buffer per request. The number may
be higher if the request is for multiple disk blocks, depending on the
fragmentation of the directory structure.

Offline Options

245

DEFAULT

BACKUP Program
BACKUP makes extensive use of asynchronous I/O and therefore general small
buffers. Depending on the qualifiers used and the device speed, BACKUP can use
hundreds of buffers.

Margin of Safety
After you finish calculating how many small buffers you will need, you should add
100 to 150 general small buffers to assure that the number of general small buffers
remains above 75.
General and FIP Small Buffer Pool Worksheet
Figure 9 summarizes the items requiring general and/or FIP small buffers and the
approximate number each requires. Space is provided to enter the number you need
for your installation. Use the worksheet as a gUide for calculating the number of
general and FIP small buffers. You can determine the optimal number only through
experimenting with your system.

246

Offline Options

DEFAULT

Items Requiring General or FIP Small Buffers

Your Number

Jobs
CCl commands
Auxiliary run-time systems
Resident libraries
Open files and DCl file information
List of message receivers
List of messages sent by one job waiting to be received
by another job
Contents of messages sent and waiting to be received:::
Terminals
Line printers*
Paper tape reader/punch
EMT logging
Outstanding 110 requests
BACKUP program
Margin of safety

Total

* The RSTS/E monitor can also use extended buffers to store these items.

MK-01096-02

Figure 9:

General and FIP Small Buffer Pool Worl(sheet

Offline Options

247

DEFAULT

VIRTUAL -

Allocate Memory to the Virtual Disk

The VIRTUAL sub option allocates memory to the virtual disk, a software structure
that supports the storage of temporary data within the system's memory. Even
though the virtual disk is not a physical device, it contains the same structures
as a physical disk device. You can use the virtual disk for file-structured or nonfile- structured 1/0 in the same way you use any other disk device, with one exception: all data written to the virtual disk is lost when the RSTSIE system shuts down or
if the system should crash. The device designator for the virtual disk is DVO:.
Use the VIRTUAL suboption if you have a system with a large amount of memory
and you want to establish a region of memory for temporary data storage.
Before you decide whether to allocate memory to the virtual disk, you should read
the information in the section, Virtual Disk Background Information.
VIRTUAL Dialogue
Table suboption? VIRTUAL

Explanation - You see the Table suboption? prompt after you answer YES to the
Any memory allocation changes? DEFAULT question.
Response - Type VIRTUAL or VI.
Enter new virtual disk size <OK)?

Explanation - VIRTUAL asks for the amount of memory you want to reserve for
the virtual disk (DVO:). You do not need to specify the location of the virtual disk,
because INIT.SYS automatically positions it according to the procedures outlined in
the next section.
Response - Specify the size of VIRTUAL, followed by K to indicate K words.
To release previously allocated memory for the virtual disk to USER memory, type
RESET.
Table suboption?

Explanation - After you specify the virtual disk size, VIRTUAL returns to the Table
sub option ? prompt.
Response - Type LIST or LI to list the memory allocation table and check that you
have reserved the correct area in memory. Then, press RETURN at the next Table
sub option? prompt to continue with the DEFAULT dialogue. Or, type one of the
other DEFAULT table suboptions.

248

Offline Options

DEFAULT

Virtual Disk Bacl(ground Information

You allocate memory to the virtual disk with the VIRTUAL (or VI) table suboption of
the INIT.SYS DEFAULT option. If you do not specifically allocate any memory to the
virtual disk, then INIT.SYS defaults the virtual disk to OK words, which in fact disables
the use of the virtual disk during timesharing.
You can use the virtual disk to store temporary files or any file that has a very short
lifespan. Examples of temporary files are work files created by an application program
like SORTIMERGE that are later deleted, or a temporary file used for entering data in
applications that give the user a last chance to edit the data before updating the
permanent file.
You can also place copies of read-only files that never change and are frequently
accessed on the virtual disk. For example, you can place a copy of an index file that
is used to access other files in virtual memory.
If you intend to use the virtual disk as a file-structured device, then you must also
initialize it. Initializing the virtual disk places the" system account [0,1] on the disk with
the same required system files as needed for any other disk (SATT.SYS and
BADB.SYS). To initialize the virtual disk, use the DCL INITIALIZE command. (You
cannot use the INIT.SYS DSKINT option.) See the RSTSIE System Manager's Guide
for information on initializing disks.

Large memory systems will find a big advantage in using the virtual disk. Because the
virtual disk never requires physical 1/0, it becomes the fastest disk on your system. It
is even faster than data caching for these reasons:
o A file placed on the virtual disk always remains in memory. A cached file, on

the other hand, remains in memory based on frequency of access.
o When you write to a file on the virtual disk, no physical 1/0 takes place. When

you write to a cached file, physical 1/0 takes place. The file processor first
performs a physical write, then it updates memory.
On the other hand, the virtual disk requires CPU time and takes memory away from
user space. If you have a CPU bound or small memory system, you may find this
detracts from overall performance. In addition, you cannot use the virtual disk for any
permanent files because all data is lost when the system shuts down or if the system
should c"rash.
Keep these facts in mind when deciding the amount of memory to allocate to the
virtual disk:
o You reserve memory for the virtual disk from a minimum size of 1K word up to

the amount of available memory not allocated to any other RSTS entity
(EXEC, RTS, and so forth).
o The Memory Table sub option allows you to allocate memory in 1K-word

increments. Since 1K word of memory equals 4 blocks on the virtual disk, the
size of the virtual disk is always a 4 block multiple.

Offline Options

249

DEFAULT

o The minimum amount of disk space needed for directory information on any

file-structured disk is 12 blocks. Therefore, if you intend to use the virtual disk
as a file-structured device, you must allocate a minimum of 4K words (16
blocks) of memory to it. This provides 12 blocks for the directory information
and 4 blocks for user space.
o Small memory systems such as PDP-11/34s can consider allocating 1K word to

2K words of memory for the· virtual disk in non-file-structured mode. This
provides user programs with a 4 to 8 block system common area.
You do not need to specify the position of the virtual disk. INIT.SYS automatically
positions the virtual disk based on the size and location of other memory components. INIT.SYS follows these gUidelines:
o The minimum amount of memory allocated to the virtual disk is 1K word. The

maximum is the amount of free USER memory on the system.
o The legal ranges for locating the virtual disk are between the end of the EXEC

portion of memory and 2048K words.
o INIT.SYS first attempts to position the virtual disk at the highest possible

memory address. If for some reason INIT.SYS cannot allocate sufficient
contiguous high memory (see Note), it positions the virtual disk at the lowest
possible address.
Note ----------------------

During start-up, INIT.SYS uses an 8K-word area of memory to
complete the loading of the monitor. This 8K-word area is allocated
from either RTS or USER (see your memory allocation table) and
must be above the INIT.SYS image. If INIT.SYS cannot find an 8K
word area of memory above the INIT.SYS image (68K words) and
below 124K words, it prints the error message Need at least 8KW
nonmonitor memory below 124K to start.
If your primary run-time system is 8K words or larger (DCl), there is
no problem. If your primary run-time system is smaller than 8K words
(RSX), then the monitor uses any combination of RTS and USER
memory, if the RTS memory is adjacent to USER memory. Otherwise,
the monitor uses USER memory.

250

Offline Options

DSI<INT

DSKINT -

Initialize RSTS/E Disks
The DSKINT option initializes a RSTS/E disk. DSKINT:
o Optionally formats the disk -

DSKINT writes timing and sense marks on the
disk and destroys any previously stored information.

o Optionally checks the disk for bad blocks -

DSKINT locates bad blocks on the

disk and allocates them to the bad block file (BADB.SYS).
o Writes a minimum RSTS/E file structure on the disk -

The minimum RSTSIE

file structure contains a pack label and three directories:
- The Master File Directory (MFD).
- The Group File Directory (GFD).
- The User File Directory (UFD) for account [0,1].
o Prepares the disk to accept RSTS/E system and other files.

For the DSKINT option, these responses have special meaning:
Response

Description

OOJ

Accept the default response

Obtain an online explanation of the question
Return to the previous question
Restart DSKINT dialogue
Abort DSKINT and return to the Option: prompt

DSKINT Dialogue
Option: DSKINT

Response - Type DSKINT to the INIT.SYS Option: prompt.
dd-MMM-YY

hh:MM

AM/PM

DisK?

Explanation - DSKINT prints the current date and time, and then asks for the
device designator of your disk.
Response mounted.

Type the device designator of the drive on which your disk is

Unit?

Explanation - DSKINT asks for the unit number of the disk drive on which your
disk is mounted.

Offline Options

251

DSKINT

Response - Type the device unit number.
This disK appears to be a RSTS/E forMatted
disK with the followin~ characteristics:
Pad~

ID:

PacK Cluster Size:
PacK is currently:

Pad~

PATTIE
8

Private,
Update access date on writes.
Lel)el: 1.1

ID?

Whether files are catalogued with the date they were last modified (written to)
or accessed (read, opened, closed, and so forth)

New files first information

o Whether the disk is read-only
o

Format level

This private disk could be a system disk; DSKINT cannot determine whether a private
disk is also a system disk. In the example, the pack 10 is PATTIE, the pack cluster
size is 8, the pack status is private, the files are catalogued with the date they were
last written to, and the format level is RDS 1.1.
This information lets you decide whether to initialize the disk. When you initialize a
disk, you destroy any information stored on it.
After printing the pack label information, DSKINT asks for a pack 10. The pack 10 is
a system-wide logical name. You must specify this pack ID when you logically mount
the disk.
Response - Type a one- to six-character alphanumeric pack 10.
PacK cluster size <4>?

252

Offline Options

DSKINT

Your answer to this question depends on the type of processing and the disk
requirements of your system. The pack cluster size affects disk space and speed of file
creation and access. A large pack cluster size improves access time to programs and
user files because the monitor allocates space for data in cluster units. For example, if
the pack cluster size is 16, the monitor allocates 16 blocks at a time. However, if the
pack cluster size is two, the monitor allocates only two blocks at a time. Thus, more
disk accesses are needed to allocate the same amount of space.
On the other hand, a large pack cluster size may waste disk space. For example, . if
you assign a pack cluster size of 16, the monitor allocates one cluster of 16
contiguous blocks (8,192 bytes) to a file that contains only one block (512 bytes) of
information. Fifteen blocks (7,680 bytes) are wasted. Likewise, the monitor allocates
one cluster of 16 contiguous blocks to a 15-block (7,680 bytes) file. In this case, only
one block (512 bytes) is wasted.

Response - Type one of the disk pack cluster sizes shown in Table 22. Or, press
RETURN to accept the default value (4, in this example).
Table 22:

Disk Pack Cluster Sizes

Disk
Type

Pack Cluster
Size

RX50*

1,2,4,8,16

RC25

1,2,4,8,16

RD51

1,2,4,8,16

RD52

1,2,4,8,16

RK05*

1,2,4,8,16

RK05F*

1,2,4,8,16

RLOI

1,2,4,8,16

RL02

1,2,4,8,16

RK06

1,2,4,8,16

RK07

1,2,4,8,16

RP02

2,4,8,16

RP03

2,4,8,16

RM02

4,8,16

RM03

4,8,16

RP04

4, 8, 16

RP05

4,8,16

RA80

4,8,16

RM80

4,8,16
(continued on next page)

Offline Options

253

DSKINT

Table 22:

Disk Pack Cluster Sizes (Cont.)

Disk
Type

Pack Cluster
Size

RP06

8, 16

RA60

8, 16

RMOS

8, 16

RA81

* You cannot use these disks as system disks.
MFD cluster size <IS)?

Explanation - The master file directory (MFD) stores information about all groups
on a disk. The monitor accesses the MFD each time you add or delete accounts and
rarely when you add or delete files from the disk.
This question asks for the MFD cluster size, which is the maximum number of
512-byte blocks that each cluster allocated to the MFD can contain. The MFD can
have a maximum of seven clusters (if you answer YES to the Pre-extend directories?
question later), and each directory is the size that you specify here.
The MFD cluster size must be greater than or equal to the pack cluster size and must
not be greater than 16. Legal values for the MFD cluster size are 4, 8, or 16.

Response - Press RETURN to accept the default response, (16, in this example).
Or, specify the value 4, 8, or 16.
SATT.SYS base <13S43)?

Explanation - The SA1T.SYS file controls the use of storage space on a disk
through a storage allocation table (SAT). The monitor accesses this file each time you
extend or delete files. This question asks where you want to position this file on the
disk. It is advantageous to position the SATT.SYS file near the center of the disk to
reduce average seek times for the disk heads. On the other hand, if you use only the
first half of a disk or need to create large contiguous files, you may want to locate
SATT.SYS in a place other than the center. This reduces fragmentation of the disk.
The number that appears within brackets is the center of the disk as calculated by
DSKINT (13543, in this example). The device cluster number can range from 1 to
the total device size divided by the device cluster size. See Table 23 for a list of
device cluster sizes and total device sizes.

Response - Press RETURN to have DSKINT position the file near the center of the
disk.
Or, type the device cluster number where you want the file placed.

254

Offline Options

DSKINT

Table 23:

Device Cluster Sizes and Total Device Sizes

Disk
Type

Device
Cluster
Size

RX50*

799

RC25

50901 per unit;
2 units per spindle

RD51

21599

RD52

60479

RK05*

4800

RK05F*

4800 per unit;
2 units per drive

RL01

10220

RL02

20457

RK06

27104

RK07

53761

RP02

39998

RP03

79998

RM02

131648

RM03

131648

RP04

171796

RP05

171796

RA80

237208

RM80

242572

RP06

340664

RA60

400168

RM05

500352

RA81

891056

Total Available
Blocks

* You cannot use these disks as system disks.

Pre-extend directories <NO)?

Explanation - This question asks if you want DSKINT to automatically allocate a
maximum of seven clusters to the system account [0,1], the LB: library account [1,1],
the system library account [1,2], and the MFD and GFDs for groups 0 and 1. The
number of blocks each of these seven clusters contain depends on how you answered the cluster size questions for each of these accounts. For example, if you

Offline Options

255

DSKINT

specify 16 as the cluster size for account [1,2] and answer YES to this question,
DSKINT allocates the maximum of seven clusters to this account. Each cluster is
8,192 bytes (16 times 512 bytes).
Response - Type YES to have DSKINT automatically allocate a maximum bf
seven adjacent clusters to these accounts. Or, type NO or press RETURN if you want
DSKINT to allocate only the minimum of 0 or 1 clusters.
PUB, PRI, or SYS <PRI)?

account <NO)?

Explanation - This question appears only if you type PUB or PRI to the previous
question. It asks if you want to create account [1,1]. OSKINT automatically creates
account [1,1] if you typed SYS to the previous question.
Response - Type YES to create this account. DSKINT then prints the next
question.

Or, type NO or press RETURN if you do not want to create account [1,1] at this
time. OSKINT then skips the next question. You can also use the
CREATEIACCOUNT command to create, pre-extend, and position account [1,1] on
line during timesharing.
[ltl] cluster size (18)?

Explanation - This question asks for the cluster size of the User File Directory
(UFO) for account [1,1]. The UFO is an area on the disk that stores information
about the files created under a particular user ac~ount number. The cluster size for
account [1,1] is the maximum number of 512-byte blocks that each cluster allocated
to this account can contain.
Response -

Press RETURN to accept the default response of 16.

Or, type the cluster size for account [1,1]: 1, 2, 4, 8, or 16. It must be greater than or
equal to the pack cluster size and must not be greater than 16. DIGITAL recommends a cluster size of 16 to improve disk access time.
Create [1,2] account <NO)?

Explanation - This question appears only if you type PUB or PRI to the PUB, PRI,
or SYS? question. It asks if you want to create account [1,2]. DSKINT automatically
creates account [1,2] if you typed SYS to the PUB, PRI, or SYS? question.
Response - Type YES to create this account. DSKINT then prints the next
question.

256

Offline Options

DSKINT

Or, type NO or press RETURN if you do not want to create account [1,2] at this
time. OSKINT then skips the next question. You can also use the
CREATE/ACCOUNT command to create, pre-extend, and position account [1,2] on
line during timesharing.
[1,2] cluster size <18)?

and [1,2] account base <135£11)?

Explanation - This question asks whether you want to place accounts [1,1] and
[1,2] near the center of the disk or in some other place. The number that appears
within brackets is the position of SATT.SYS, that is, the number you specified to the
SATT.SYS base? question, or the middle of the disk as calculated by OSKINT if you
specified RETURN to that question (13541, in the example). OSKINT may show a
different number for your disk.
Response -

Press RETURN to place these accounts near the center of the disk.

Or, type the device cluster number where you want these files placed. The device
cluster number can range from 1 to the total device size divided by the device cluster
size. See Table 23 for a list of device cluster sizes and total device sizes.
Date last Modified <YES>?

Offline Options

257

DSKINT

Explanation - This question asks if you want newly created files placed at the
beginning or end of the directory of the account in which they are created.
Response - DIGITAL recommends that you type NO or press RETURN to place
newly created files at the end of the directory, giving you overall faster access time.
Or, type YES to place newly created files at the beginning of the directory. This
response is useful when you have a private disk on which the files you most
frequently access are new files.
Read-onb' <NO>?

Explanation - This question asks if you want this disk to be by default a read-only
or a read/write device when it is logically mounted. You can write to a read-only disk
when you logically mount it with the !WRITE qualifier.
Response - Press RETURN to make the disk read/write.
Use previous bad block info <YES>?

Explanation - This question does not appear if you are initializing a new disk. The
question asks if you want DSKINT to create a new bad block file (BADB.SYS) in
system account [0,1] by using information from the existing bad block file. DSKINT
checks each block on the disk (if you answer 1, 2, or 3 to the Patterns? question that
comes later). If DSKINT finds unreliable blocks, it allocates the pack cluster in which
the block resides to the BADB.SYS file.
Response - DIGITAL recommends that you type YES or press RETURN to create
the new bad block file, using information from the existing bad block file.
Or, type NO to have DSKINT ignore the current bad block file when creating the
new one. For example, you may want to answer NO if you are reinitializing a disk to
decrease the pack cluster size. In this case, you will also obtain new bad block
information using 3 patterns as explained in the Patterns? question later.
Fo rlTlat <NO)?

258

Offline Options

DSKINT

---------------------- Note

If you are formatting a disk, DIGITAL recommends that you mount
the disk on the drive and leave it spinning for at least 20-30 minutes
before initializing it. This ensures that the disk temperature is stable
and uniform during the formatting. Failure to do this may cause
unreliable data storage on the disk.

Response - Type YES to format the disk. Or, type NO or press RETURN if you do
not need to format the disk.
Patterns <3)?

Explanation - This question asks for the number of patterns DSKINT should use in
checking for bad blocks. DSKINT writes a pattern to the disk, and then reads it to
check that the data was written correctly. The time DSKINT takes to run these pattern
checks for bad blocks depends on the disk you are initializing. Type a ? to have
DSKINT print the time (in minutes) required for the different disks to complete one
format check for bad blocks.
Response - Type the number of patterns, from 0 to 3. DIGITAL recommends you
run 3. Any bad blocks discovered during pattern checking are added to the bad block
file (BADB.SYS) so that data will not be written to these blocks. If you specify 0,
DSKINT then asks the next question.
Erase disK <YES>?

Explanation - This question, which appears only if you answered 0 to the Patterns? question, asks if you want to erase the disk. If you answer YES, DSKINT wipes
out all data on the disk: this is usually done for security purposes.
If you answer NO, DSKINT writes only the basic RSTS/E file structure on the disk.
Use the NO response under the following conditions:

• You are initializing a disk that has been initialized before.
• You answered YES to the Use previous bad block info? question.
• You are confident no additional bad blocks are on the disk.
• You are not concerned about the security of old data that could still be
accessed.
Response - Type YES or press RETURN to erase the disk. Or, type NO to write
only the basic RSTS/E file structure on the disk.
Proceed (Y or N)?

Explanation - This question allows you to check your responses to the dialogue
questions and abort the initialization if you have made any errors.

Offline Options

259

DSKINT

. Response - Type Y to proceed with the disk initialization.
Or, type N to abort the initialization and return to the Option: prompt.
---------------------- Note ----------------------

When you are formatting RP02 or RP03 disks, DSKINT prints two
requests after the Starting and Ending format pass messages:
SET FORMAT ENABLE SWITCH, THEN TYPE <RET>:

Set the RPll controller FORMAT ENABLEINORMAL switch to
ENABLE, then press RETURN.
SET FORMAT SWITCH TO NORMAL, THEN TYPE <RET>:

Set the RPll controller FORMAT ENABLEINORMAL switch to
NORMAL, then press RETURN.

Option:

Explanation prompt.

INIT.SYS completes the disk initialization. Then it prints the Option:

Table 24 lists the DSKINT error messages. If your error message does not appear
there, see Appendix A.

260

Offline Options

DSKINT

Table 24:

DSKINT Error Messages
Message and Meaning

BLOCK NUMBER TOO BIG
The block number you typed is greater than or equal to the maximum logical block number
for the disk.
DRIVE NOT READY
The initialization cannot proceed because the disk to be initialized is not on line and ready.
You can make the drive ready and press RETURN to proceed, or you can press CTRUC to
abort the initialization.
DSKINT NOT LEGAL ON SYSTEM DISK
You specified the disk from which the initialization code was bootstrapped. You cannot initialize
this disk now because the initialization code would be destroyed.
ILLEGAL DISK NAME
The string you typed is not the name of a valid RSTS/E disk device. Enter a valid name.
ILLEGAL NUMBER, TRY AGAIN
The number you typed is not a valid octal number between 1 and 177777.
SORRY, BUT THAT DISK DOESN'T EXIST
The string you typed is a valid RSTS/E disk name, but that disk controller or the unit number
does not exist on this system.

Offline Options

261

HARDWR

HARDWR -

Adjust the Hardware Configuration

The HARDWR option performs tasks related to the hardware your RSTS/E monitor
supports. The following sections describe the HARDWR sub options. These sub options
affect your system disk, not your installed monitor. Thus, if you add or remove
non-standard hardware, you may need to use these suboptions again. However, if
you only install a different monitor, you do not need to use these sub options again.
The HARDWR sub options are:
o HARDWR LIST -

List the Hardware Configuration Table

HARDWR DISABLE - Disable a Device Controller

HARDWR ENABLE - Enable a Device Controller

o HARDWR CSR - Declare a Nonstandard Controller Address
o HARDWR VECTOR - Declare a Nonstandard Vector Assignment
o

HARDWR RESET - Set All Controller Addresses and Vector Assignments to
the Standard, and Enable All Devices

o HARDWR OM - Declare DMII-BB and DHll Associations
o HARDWR UNITS - Associate an RK05 Disk Type With a Controller
o

HARDWR HERTZ - Specify AC Line Frequency

HARDWR SWITCH - Specify CPU Switch Register Characteristics

Table 25 lists the error messages for the various HARDWR suboptions. If your error
message does not appear there, see Appendix A.

Offline Options

263

HARDWR

Table 25:

HARDWR Error Messages

Suboption

264

Message and Meaning

CSR

ADDRESS MUST BE AN EVEN OCTAL NUMBER GREATER THAN 160000.
You specified an invalid address. Type an address that meets the
requirements.

DISABLE

CANNOT DISABLE CONSOLE TERMINAL
You tried to disable the console terminal.

DISABLE

CONTROLLER ALREADY DISABLED
You tried to disable a disabled controller.

ENABLE

CONTROLLER NOT DISABLED
You tried to enable an enabled controller.

DISABLE,
ENABLE,
CSR,
VECTOR

CONTROLLER NUMBER MISSING
You did not specify a controller number for a device that has multiple
controllers.

DISABLE,
ENABLE,
CSR,
VECTOR

CONTROLLER NUMBER MUST BE LESS THAN nn
The controller number you typed is larger than the maximum of nn.

DH11 ALREADY ASSIGNED TO A DM11-BB
The DH11 unit you specified is already assigned to a DM11-BB.

DISABLE,
ENABLE,
CSR,
VECTOR

INVALID CONTROLLER NAME
The first two characters you typed did not name a valid device controller.
Type? to obtain a list of valid controller names and try again.

DISABLE,
ENABLE,
CSR,
VECTOR

INVALID CONTROLLER NUMBER
The controller number you typed is not an integer. Type the number in the
correct format.

INVALID RESPONSE
The unit number you specified is not a decimal number from 0 to 15.

VECTOR

VECTOR MUST BE AN EVEN OCTAL NUMBER LESS THAN 1000.
You specified an invalid address. Type an address that meets the
reqUirements.

Offline Options

HARDWR

HARDWR LIST -

List the Hardware Configuration Table

The LIST sub option lists the hardware configuration table. This table shows the
current hardware configuration and allows you to verify any changes you have made.
Use the LIST suboption if:
o You want to list the current hardware configuration table.
o You need to list the table to see what changes you have made to your

hardware configuration.

LIST Dialogue
OPt i on:

HAROWR

Response - Type HARDWR or HA to the INIT.SYS Option: prompt.
HAROWR suboption? LIST

Response - Type LIST or LI to list the hardware configuration table.
NalTle
TTO:
RK:
RL:
RM:
RR:
RUO:"
TU:
LPO:
010:
}-{MO:
OZO:
OZl:

Address
177560
177400
174400
177440
176700
172150
172440
177514
160050
160100
160120
160130

I,lector
060
220
160
210
254
340
224
200
300
310
320
330

KWllL
SR
OR

177546
177570
177570

100

COITliTlents
RK05F units: none
Units: 0(RL02)
Units: 2(RK07)
Units: 0(RM02 DP)
Units: 2(RABO)
Units: 0(TU16 @TM02 #0)

Hertz = GO.
Other: FPU, CIS, 22-Bit, Oata space, Cache
HAROWR suboption?

Explanation - In this example, taken from a PDP-11/44, LIST prints the hardware
configuration. (Note that LIST prints only a partial list of the hardware configuration
table if you have not installed a monitor.)
If you have changed any of the configured hardware, LIST prints the number of
changes that HARDWR will make when you exit from the option. When you exit
from the HARDWR suboption? prompt, INIT.SYS scans the entire hardware

Offline Options

265

HARDWR

configuration and reboots the disk. Because there are no changes pending in the
example, LIST does not print anything.
The hardware configuration table contains one line for each device controller that
exists on the system. The table also contains an additional line, printed in
parentheses, for each controller that has changes pending. This line appears whether
or not the controller has a listing line. Thus, if you declare a nonstandard
characteristic for a controller that does not yet exist on the system, HARDWR prints a
parenthetical change line noting the change. In addition, the table contains a line for
controllers that are currently disabled or nonexistent.
Each line has four columns:
Name

The name and number of the device controller.

Address

The address of the controller's CSR set.

Vector

The controller's vector address. If the device has two vectors,
HARDWR prints the lower address; an asterisk (*) precedes a
nonstandard CSR or vector address.

Comments

Information about the controller or devices on that controller.
Table 26 summarizes the comments that may be in the listing for each
controller.

In a parenthetical change line, the Address column contains either a nonstandard
address or the word SYSTEM. SYSTEM means that INIT.SYS will find the CSR set
according to the standard fixed and floating address rules when it bootstraps the
system disk. (See Appendix B for a discussion of fixed and floating address rules.)
The Vector column in a change line is blank or contains the nonstandard vector
address that you specified.
Following the hardware configuration table, LIST prints several lines of information.
The information reported depends on what hardware your system supports. Table 27
summarizes what you might see on your hardware configuration table.
Response -

Type EXIT or press RETURN to return to the Option: prompt.

Table 26 lists the comments that you may see in a controller listing.

266

Offline Options

HARDWR

Table 26:

Hardware Comments Table
Comment and Meaning

Device
ALL

Disabled
Device is {or will be} disabled.

ALL

Not found
Device was not found.

RK05F units: n/m
nand m are the even and odd unit numbers of the RK05F drive.
RK05F units: none
No RK05F units are on the system.

units:

m{RLOl} ...
p{RLOl}

m through p are unit numbers of drives that exist on the controller {4 are possible}. The
disk type appears in parentheses after each unit number.
RM

units:

m{RK07} ...
t{RK07}

m through t are unit numbers of drives that exist on the controller (8 are possible). The
disk type appears in parentheses after each unit number.
RP

RP03 units: m... t
m through t are unit numbers of RP03 disks that exist on the controller (8 are possible).
Unit numbers of RP02 drives are not listed.

RB,RR

BAE= + xxx
BAE indicates that the device controller supports 22-bit addressing and has a Bus
Address Extension register at the specified offset from its CSR base.
units:

m{RM02, RM03, RM05, RM80, RP04, RP05, RP06} ...
t{RM02, RM03, RM05, RM80, RP04, RP05, RP06}

m through t are unit numbers of drives that exist on the controller {8 are possible}. The
disk type appears in parentheses after each unit number. Following the disk type is DP,
if that unit is a dual-ported disk.
RU

units:

m{RA60, RA80, RA8l }...
t(RA60, RA80, RA8l}

units:

m(RCF25, RC25} ...
t(RCF25, RC25}

unit:

m{RD5l, RD52, RX50}

m through t are unit numbers of drives that exist on the controller {4 are possible}. The
disk type appears in parentheses after each unit number.
TS

units: m(TSll,TK25,TS05,TU80} ...
m is the unit number of the drive that exists on the controller. The tape type appears in
parenthesis after the drive type.
{continued on next page}

Offline Options

267

HARDWR

Table 26:

Hardware Comments Table (Cont.)
Comment and Meaning

Device

BAE= + xxx
BAE indicates that the device controller supports 22-bit addressing and has a Bus
Address Extension register at the specified offset from its CSR base.

units:

m(TU16@TM02#X) ...
t(TU16@TM02#X)

m through t are unit numbers of drives that exist on the controller (8 are possible). The
tape type, fomiatter type, and the formatter number appear in parentheses after each
unit number. The TU16, TE16, TU45, and TU77 represent the valid device types for
the TU controller and the TM02 and TM03 are the valid formatter types. The formatter
number (#X) can be any number from 0 to 7.
DM

DHn
DH11 controller number n is logically associated with this DM11-BB unit.
No DH11
No DH11 controller is logically associated with this DM11-BB unit.

Table 27 lists what you may see on your hardware configuration table.
Table 27:

Summary Hardware Configuration Table

Mnemonic

Line and Meaning

KW11-L

177546 100
Reports the address and vector of the KW11-L line clock.

KW11-P

172540 104
If the system has a KW11-P clock, reports its address and vector.

177570
VOLATILE
DISABLED
If the CPU has a switch register, reports its address. If you have used the
SWITCH suboption to specify that the switch register is VOLATILE or
DISABLED, it reports that choice.

VOLATILE
DISABLED
The CPU does not have a switch register, but you have used the SWITCH
sub option to ENABLE or DISABLE it.

(SR

DISABLED )
ENABLED
VOLATILE
There is a pending change from the SWITCH suboption.

177570
If the CPU has a display register, its address is reported.
(continued on next page)

268

Offline Options

HARDWR

Table 27:

Summary Hardware Configuration Table (Cont.)

Mnemonic

Line and Meaning

HERTZ

50
60

The system's AC line frequency is always reported.

(HERTZ

= 50)

There is a pending change to the system's AC line frequency.

60
CIS

The CPU has the Commercial Instruction Set (CIS) option.

FPU
with FPA

The CPU has the Floating Point Processor (FPP) option. FPA indicates
that the CPU also includes the Floating Point Accelerator. You only see
the with FPA on J11 or Fll CPUs.

FIS

The CPU has the Floating Instruction Set (FIS) option (PDP-11135 and
11140 only).

The CPU has a stack limit register.

MED

The CPU has the Maintenance Examine/Deposit instruction (PDP-11160
only).

CACHE

The CPU has main memory cache.

CACHE W/ADDRESS

The CPU retains address information on a memory fault.

22-BIT

The CPU supports more than 124KW of memory.

SYSTEM 10 = nnnnn

The contents of the CPU identification register are reported, if the
register exists.

F11 CPU

The processor type is Fll (PDP-11123 or 11124).,

J11 CPU

The processor type is J11 (PDP-11173, 11183, or 11184).

11144 CPU

The processor type is a PDP-ll144.

Offline Options

269

HARDWR

HARDWR DISABLE -

Disable a Device Controller

The DISABLE sub option disables a device controller; that is, makes it unavailable for
use. For example, the RM controller controls all RK06 and allRK07 disk drives. If
you disable the RM controller, you disable all RK06 and RK07 disk drives.
Use the DISABLE sub option if:
o You need to disable a controller that needs repairs.
o You need to disable an erroneously detected controller. For example, you may

have installed a TS 11 magnetic tape drive at a nonstandard CSR address of
177170. However, INIT.SYS expects to find the RXOI/RX02 flexible diskette
controller at this address. If you do not use the CSR suboption to declare the
TS 11 as having a nonstandard CSR, then you must disable the device by
disabling the RX (really TS 11) controller.
In some cases, INIT.SYS interprets a nonstandard device (a device not
supported by RSTS) as a normal PDP-II device. This means INIT.SYS enables
the nonexistent PDP-II device.

DISABLE Dialogue
Option: HARDWR

Response - Type HARDWR or HA to the the INIT.SYS Option: prompt.
HARDWR suboption? DISABLE

Response - Type DISABLE or DI to disable a controller..
Controller to disable? ?

Explanation - DISABLE asks for the name of the controller to disable. Before you
do that, however, it may be useful to list the valid controller names.
Response - Type a ? to list the valid controller names.
NafTle

Max no

TT
RK
RL
RM
RP
RB
RR
RU
. TC
TS
TM
TU

1
1
1
1
1
1
1
Z
1

a
1
1

Description
Console terfTlinal
RK05/RK05F disK
RL01/RLOZ dis ~\
RKOG/RK07 dis ~\
RPOZ/RP03 dis ~\
RPOQ/RP05/RPOG dis ~\
RMOZ/RM03/RM05/RMBO dis ~\
MSCP class dis~\s
TCll DECtape
TSll/TSV05/TKZ5/TUBO fTlagtape
TU1O/TE1O/TS03 Magtape
TU1G/TE1G/TUa5/TU77 fTlastape
(continued on next page)

270

Offline Options

HARDWR

PR
PP
LP
R}{

CR
CD
KL
DL
DE
DP
DC
KG
DM
DJ
DH
DU
Dl
}{M

8
8
8

8
8

16
31
31
31

32
8

16
16
16
16
16
16
16
16
16
16
16
16

Paper tape reader
Paper tape punch
Line printer
RXll flexible diskette
CRll/CMll card reader
CDll card reader
KLll/DLllA/DLl15 single-line interface
DLllC/DLllD single-line interface
DLllE single-line interface
DPll synchronous line interface
DCll single-line interface
KGll CRC arithMetic unit
DMll-55 ModeM control for DHll
DJll 16 line Multiplexer
DHll 16 line Multiplexer
DUll single-line synchronous interface
DUPll single-line synchronous interface
DMCll/DMRll interprocessor link
DZll/DZVll 8 line Multiplexer
KMC-ll Microprocessor
DMPll/DMVll interprocessor link
DNll autoMatic calling unit interface
DEUNA Ethernet controller
DHVll/DHUll 8/16 line Multiplexer

Controller to disable?

Explanation - The first column of this list contains the name of the controller. The
second column shows the maximum number of each type of controller that a RSTS/E
monitor can support. The third column describes the devices controlled by the
controller.
After DISABLE prints the list of valid controllers, it asks for the name of the controller
to disable.
Response - Type the two-character name and unit number of the controller you
need to disable. Controllers are numbered from 0 to the maximum number possible,
minus 1. You can omit the controller number only if the maximum number of that
controller is 1. For example, you could type RL to this question rather than RLO
because the maximum number of RL controllers that a RSTS/E monitor can support
is 1. On the other hand, if you need to disable the line printer controller, you have to
include the number because the RSTS/E monitor can support more than one line
printer controller.
Press CTRL/Z or the RETURN key to exit from this suboption without specifying a
controller name.
HARDWR suboption?

Explanation - HARDWR does not immediately disable the controller specified in
the previous question, but returns to the HARDWR sub option? prompt. This lets you
check your responses by listing the current hardware configuration table.

Offline Options

271

HARDWR

Type LIST or LI. Type EXIT or press RETURN to return to the
Option: prompt. Press CTRL/C to cancel any changes and return to the Option:
prompt.

Response -

HARDWR makes the indicated changes, bootstraps· your system disk, and prints one
of three messages:
o Option:

The Option: prompt indicates you have made no hardware changes or that
INIT.SYS has previously completed a scan of the hardware configuration.
o nn

chan~es

bein~

Made

Rebootin~ •••

The value nn represents the number of changes that INIT.SYS will make after it
bootstraps the system disk. INIT.SYS scans the entire hardware configuration as
it reboots the system disk.
o

Enablin~

all devices.

chan~es

pendin~

Rebootin~ •••

This message indicates that INIT.SYS previously completed only a partial scan
of the hardware configuration. The value nn represents the number of changes
you have indicated {or it means you have used the RESET suboption}.
INIT.SYS makes the changes and scans the entire hardware configuration as it
reboots the system disk.

)

272

Offline Options

HARDWR

HARDWR ENABLE -

Enable a Device Controller

The ENABLE suboption of HARDWR enables a device controller; that is, makes it
available for use. For example, the RM controller controls all RK06 and RK07 disk
drives. If you enable the RM controller, you enable all RK06 and RK07 disk drives.
This suboption is related to the HARDWR DISABLE suboption. Just as you use the
ENABLE sub option to enable a controller, you use the DISABLE sub option to
disable a controller.
Use the ENABLE suboption if:
o You need to enable a controller that was previously disabled.
o You need to enable a controller automatically disabled by INIT.SYS.

ENABLE Dialogue
Option:

HARDWR

Response - Type HARDWR or HA to the INIT.SYS Option: prompt.
HARDWR suboption? ENABLE

Response - Type ENABLE or EN to enable a controller.
Controller to

enable~

Explanation - ENABLE asks for the name of the controller to enable. Before you
do that, however, it may be useful to list the valid controller names by typing a
question mark (?). The list you receive contains the name of the controller, the
maximum number of each type that the RSTS/E monitor can support, and a description of the controller. See the previous section for an example of this list, or print it
on your console terminal.
Response - Type the two-character name of the controller you need to enable.
Controllers are numbered from 0 to the maxim urn number possible, minus 1. You
can omit a controller number orily if the maximum number supported by the RSTS/E
monitor is 1. For example, you could type RL to this question rather than RLO
because the maximum number of RL controllers that a RSTS/E monitor can support
is 1. On the other hand, if you need to enable the line printer controller, you have to
include the number because the RSTS/E monitor can support more than 1 line
printer controller.

Or, press· CTRL/Z to exit from this sub option without specifying a controller name.
HARDWR suboption?

Offline Options

273

HARDWR

Explanation - HARDWR does not immediately enable the controller, but returns
to the HARDWR subbption? prompt. This lets you check your responses by listing
the current hardware configuration table.
Response - Type LIST or LI to see the current hardware configuration table. Type
EXIT or press RETURN to return to the Option: prompt. Press CTRL/C to cancel any
changes and return to the Option: prompt.
After you type EXIT or press RETURN, HARDWR makes the specified changes,
bootstraps your system disk, and prints one of three messages (see the previous
section, Disable a Device Controller).

274

Offline Options

HARDWR

HARDWR CSR -

Declare a Nonstandard Controller Address

The CSR suboption of HARDWR sets a nonstandard controller address for a device
controller's Control Status Register (CSR) set. The CSR set is the unique set of
addresses on the UNIBUS associated with a particular device controller.
When you bootstrap the INIT.SYS program, it checks the number of each type of
controller on the system by applying standard rules for locating the CSR set. See
Appendix B for a discussion of the checks performed by INIT.SYS.
Use the CSR sub option only if:
o You need to install a controller at another address because you have

nonstandard hardware.
o You need to rearrange device controller addresses.

However, in general it is not a good idea to assign controllers nonstandard addresses.
Perform this task only as a temporary measure until you have the address assignment
corrected.
CSR Dialogue
Option: HARDWR

Response - Type HARDWR or HA to the INIT.SYS Option: prompt.
HARDWR suboption? CSR

Response - Type CSR to specify a nonstandard address for a device controller.
Controller with non-standard address?

Explanation - This question asks for the name of the controller that requires a
nonstandard CSR address.
Response - Type the two-character controller name and its number. Controllers
are numbered from 0 to the maximum possible number of controllers, minus 1. You
can omit the controller number only if the maximum number of that controller is 1.
For example, you could type RL to this question rather than RLO because the
maximum number of RL controllers that the RSTS/E monitor can support is 1.

You can also type a ? to have HARDWR print a list of valid controller names. This list
contains the name of the controller, the maximum number of each type that the
RSTS/E monitor can support, and a description of the devices controlled by the
controller. (See the section, Disable a Device Controller, for an example of this list, or
print it on your console terminal.)
New controller address?

Offline Options

275

HARDWR

Explanation - This question asks for the nonstandard CSR address for the
controller you specified in the previous question.
Response - Type the address of the lowest register in the controller's CSR set. The
address must be an even 6-digit octal number greater than 160000.

Or, type REMOVE or RE to remove the nonstandard address {if you have used this
option before} and return to the standard setting.
Press CTRL/Z to return to the HARDWR suboption? prompt without specifying a new
CSR address.
HARDWR suboption?

Explanation - HARDWR does not immediately assign the address you specified to
the nonstandard controller, but returns to the HARDWR sub option? prompt. This lets
you check your responses by listing the current hardware configuration table.
Response - Type LIST or LI to list the current hardware configuration table. Type
EXIT or press RETURN to return to the Option: prompt.

After you type EXIT or press RETURN, HARDWR makes the specified changes,
bootstraps your system disk, and prints one of three messages {see the previous
section, Disable a Device Controller}.

276

Offline Options

HARDWR

HARDWR VECTOR -

Declare a Nonstandard Vector Assignment

The VECTOR suboption of HARDWR specifies a nonstandard vector address for a
device controller.
- - - - - - - - - - - - Note

This task is for DIGITAL Field Service representatives who might have
to perform it during hardware installation.

Use the VECTOR sub option only if:
o You need to specify a nonstandard vector address for a device controller

because INIT.SYS cannot determine its vector.
o The hardware configuration includes more than one card reader.
o The hardware configuration includes a card reader that has a nonstandard

vector.
In all other circumstances, INIT.SYS attempts to find the correct interrupt vector for
the device and uses what it finds, regardless of what is specified with the VECTOR
suboption.
A controller's vector address directs the central processor to the proper routines when
that controller requests an interrUpt. When you bootstrap the system, INIT.SYS
checks e~ch device controller's vector address assignment by forcing each device to
interrupt. INIT.SYS checks these addresses against a table of reserved locations. If a
device does not respond, INIT.SYS prints a message at your console terminal and
disables the device.
INIT.SYS also checks whether more than one device has the same vector address. If
so, INIT.SYS prints a message:
Vector for Device XXn:

(vvv) already in use - device disabled.

where vvv represents the octal address of the incorrect vector.
Table 28 lists the locations reserved for hardware. You cannot use these locations as
device vector assignments.

Offline Options

2Tl

HARDWR

Table 28:

Reserved Hardware Locations

Address

RSTS/E Usage

0-2

Detection of jumps to 0 and traps to 0

4-36

System trap vectors

40-56

Reload start addresses, failure HALT

100-102

KW11-L line frequency clock vector

104-106

KW11-P programmable crystal clock vector

110-112

Jump to 0 handling

114-116

Memory parity trap vector

144-146

Crash dump handling

234-236

Statistics handling

240-242

PIRQ trap vector

244-246

FPP or FIS exception trap vector

250-252

Memory Management Unit trap vector

VECTOR Dialogue
Option: HAROWR

Response - Type HARDWR or HA to the INIT.SYS Option: prompt.
HARDWR suboption? VECTOR

Response - Type VECTOR or VEC.
Controller with non-standard vector?

Explanation - This question asks for the name of the controller that requires a
nonstandard vector address.
Response - Type the two-character controller name and its number. Controllers
are numbered from 0 to the maximum possible number of controllers, minus 1. You
can omit the controller number only if the maximum number of that kind of
controller is 1. For example, you could type RL to this question rather than RLO
because the RSTS/E monitor supports only 1 RL controller.
You can also type a ? to have HARDWR print a list of valid controller names. This list
contains the name of the controller, the maximum number of each type that the
RSTS/E monitor can support, and a description of the controller. See the section,
Disable a Device Controller, for an example of this list, or print it on your console
terminal.
New vector address?

278

Offline Options

HARDWR

Explanation - This question asks for the nonstandard vector address for the
controller you specified in the previous question.
Response - Type the nonstandard vector address, which is the 3-digit octal address
of the lowest vector for the device controller. The address must be an even number.
See Table 28 for the reserved addresses.

Or, type REMOVE or RE to remove a nonstandard vector address and return to the
standard address.
Press CTRL/Z to return to the HARDWR sub option? prompt without specifying a new
vector address.
HARDWR 5uboPtion?

Explanation - HARDWR does not immediately assign the nonstandard vector
address to the controller, but returns to the HARDWR suboption? prompt. This lets
you check your responses by listing the current configuration table.
Response - Type LIST or LI to list the current hardware configuration table. Type
EXIT or press RETURN to return to the Option: prompt.

After you type EXIT or press RETURN, HARDWR makes the specified changes,
bootstraps your system disk, and prints one of three messages (see the section, .
Disable a Device Controller).

Offline Options

279

HARDWR

HARDWR RESET -

Set All Vector and CSR Addresses to the Standard,
and Enable All Devices.

The RESET sub option of HARDWR causes INIT.SYS to reboot your system disk and
perform a complete hardware scan. Thus, INIT.SYS returns all CSR and vector
addresses to their standard addresses, enables all devices, and associates each
DMII-BB unit with the DHll multiplexer that has the same unit number.
Use the RESET sub option only if you have made no changes to your hardware; that
is, you have not assigned any nonstandard CSR or vector addresses.

RESET Dialogue
Opt i on:

HARDWR

Response - Type HARDWR or HA to the INIT.SYS Option: prompt.
HARDWR 5uboption? LIST

Explanation - Before using RESET, always list the current hardware configuration
to see if there are any CSR or VECTOR. changes. See the section, HARDWR LIST,
for an example of the hardware configuration table.
Response - Type LIST or LI. Or, type EXIT or press RETURN to return to the
Option: prompt.
HARDWR 5uboption? RESET

Explanation - After LIST prints the current hardware configuration, it returns to
the HARDWR sub option ? prompt.
Response - Type RESET or RE.
HARDWR 5uboption?

Explanation - RESET returns all device characteristics to the standard CSR and
VECTOR addresses. Then it returns to the HARDWR sub option? prompt.
Response - Type LIST or LI to list the current hardware configuration table. See
the section, HARDWR LIST, for an example of the hardware configuration table.
After you list the hardware configuration table, type EXIT or press RETURN to return
to the Option: prompt.

280

Offline Options

HARDWR

HARDWR DM -

Declare DM11-BB and DH11 Associations

The OM sub option of HAROWR associates each OMII-BB modem controller with
the correct OHll multiplexer.
Use the OM sub option if the OMII-BB modem controllers are not associated with the
correct OHll multiplexers.
The OHll multiplexer allows you to connect from 1 to 16 terminals to your POP-l1.
In other words, the OHll multiplexer has 16 lines, numbered from 0 to 15.
The OMII-BB modem controller allows you to connect a dial-up telephone to the
OHll multiplexer. A OMII-BB modem controller also has 16 lines. A one-to-one
relationship exists between these two pieces of hardware; thus, a PDP-II can have
only as many OMII-BB modem controllers as there are OHll multiplexers.
Therefore, a PDP-II can support a maximum of 16 OHll multiplexers.

OMII-BB modem controllers and OHll multiplexers must meet the following
conditions:
o A OMII-BB controller's lines can be connected to modem lines on only one

OHll multiplexer. For example, you could not connect the OMII-BB
controller lines to OHll units 0 and 1.
o

A OMII-BB controller's line numbers must be the same as the line numbers of
its associated OHll multiplexer. For example, OMII-BB line number 4 can be
connected only to OHll line number 4.

The RSTS/E monitor cannot determine which OMII-BB modem controller is
associated with a specific OHll multiplexer (assuming of course that there is more
than one OHll multiplexer). Therefore, the RSTS/E monitor assumes that OMII-BB
unit number 0 is associated with OHll multiplexer unit O. The RSTS/E monitor does
not require that OMII-BB and OHll unit numbers be the same. For example, you
could connect OMII-BB unit number 2 to OHll unit number 4.
OM Dialogue
Option: HARDWR

Response - Type HAROWR or HA to the INIT.SYS Option: prompt.
HARDWR 5uboption? DM

Response -

Type OM.

DH for DMO (0, NX)?

Explanation - This question asks for the unit number of the OHll multiplexer you
want to associate with OMII-BB unit O. NX means that the unit is nonexistent. The
OM suboption requests OHll unit numbers for all 16 possible OMJ.I-BB units,
whether or not the system includes 16 units. Therefore, you can logically associate a

Offline Options

281

HARDWR

DHll unit number with a DMII-BB unit that is not on the system, but is expected in
the future.
Response - Type the unit number or press RETURN to accept the default.

Or, press CTRL/Z to return to the HARDWR suboption? prompt without declaring
any DMII-BB and DHll associations.
HARDWR 5uboption?

Explanation - DM does not immediately assign the unit numbers of any OHll
multiplexers to their associated DMII-BB modem controllers, but returns to the
HAROWR sub option ? prompt. It is useful to list the hardware configuration table to
verify that these changes will occur.
Response - Type LIST or LI to list the current hardware configuration table. (The
hardware configuration table is not repeated in here.) After you list the hardware
configuration table, type EXIT or press RETURN to have OM make the changes and
return to the Option: prompt.

282

Offline Options

HARDWR

HARDWR HERTZ -

Specify AC Line Frequency

The HERTZ suboption of HARDWR specifies AC line frequency for your system.
Use the HERTZ suboption only if you need to specify the correct AC line frequency
for your system.

HERTZ Dialogue
Opt i on:

HARDWR

Response - Type HARDWR or HA to the INIT.SYS Option: prompt.
HARDWR suboption? LIST

Explanation - HARDWR prints the HARDWR sub option? prompt. Before using
HERTZ, always list the current hardware configuration to see if the AC line frequency
is correct for your installation. (See the section, HARDWR LIST, for an example of
the hardware configuration table.)
Response - Type LIST or LI. Or, type EXIT or press RETURN to return to the
Option: prompt.
HARDWR suboption? HERTZ

Explanation - If the table shows an incorrect AC line frequency for your installation, then you must correct it. The AC line frequency is the basis for all system
timing.
Response - Type HERTZ or HE.
New AC line hertz?

Explanation -

The question asks for the AC line frequency for your installation.

Response: Type 50 if your AC line frequency is 50 Hz (commonly used in Europe);
type 60 if your AC line frequency is 60 Hz (commonly used in the United States).
The line frequency always defaults to 60 Hz when you install a new monitor. If your
installation requires an AC line frequency of 50 Hz, then every time you install a new
monitor, you need to use the HERTZ suboption to change the frequency from 60 to
50 Hz.

If you have both a KWI1L and KWIIP clock, INIT.SYS properly determines the
frequency of your power.
HARDWR suboption?

Explanation - After you indicate the AC line frequency, you should list the
hardware configuration table, to verify that the change will occur.
Response - Type LIST or LI to list the hardware configuration table. Type EXIT or
press RETURN to return to the Option: prompt.

Offline Options

283

HARDWR

HARDWR SWITCH -

Specify CPU Switch Register Characteristics

The SWITCH suboption of HARDWR specifies the characteristics of your CPU's
console switch register. The console switch register controls:
• The automatic restart feature of RSTS/E during system crashes
• The RSTS/E statistics package
When the monitor crashes, except for power failures, it looks at the switch register. If
bit 0 is set to 1, the system performs an autorestart. If bit 0 is not set to 1, (regardless
of the setting of the other switches), the system does not start automatically because it
looks at the contents of bit O.
Statistics gathering in the monitor, which you select by answering Y to the Monitor
statistics? configuration question, depends on bits 15 and 14 in the switch register
(values 100000 and 040000, respectively). These bits have the following meaning:
Bit 15 = 1

Statistics are gathered. Bit 14 is ignored.

Bit 15 = 0

Statistics are not gathered. Bit 14 is not ignored but instead affects the
contents of the statistics counters. If bit 15 equals 0 and bit 14 equals
1, the system leaves the values of the current statistics counters
untouched (frozen). If bit 15 equals 0 and bit 14 equals 0, the system
resets all statistical counters to zero.

Use the SWITCH suboption only if you want to specify the characteristics of your
CPU's console switch register.
SWITCH Dialogue
Opt i on: HARDWR

Response - Type HARDWR or HA to the INIT.SYS Option: prompt.
HARDWR suboption? SWITCH

Response - Type SWITCH or SW.
Sl,..litch

resister?

Explanation - Because some CPUs do not have switch registers or have switch
registers that cannot retain the original register contents after a power failure,
SWITCH lets you put the switch register contents in one of three logical positions:
ENABLE, DISABLE, or VOLATILE.

The response you select and your console switch register setting determine how your
system recovers after a system crash. Systems that crash due to power failure have
restart capabilities only if they are configured with both nonvolatile memory memory that is not destroyed during power failure - and a nonvolatile switch
register.

284

Offline Options

HARDWR

Response - Type DISABLE, ENABLE, or VOLATILE:
o DISABLE means RSTS/E does not look at the switch register. This means your

system, by default, automatically restarts and continues to gather statistics as
well. (Note that you must answer Y to the Monitor statistics? configuration
question in Task 6 of Phase 3 in Part I if you want this feature.)
o ENABLE means statistics gathering during timesharing responds to the setting

of bits 14 and 15 in the switch register. This means that when the system
crashes, RSTS/E looks at the switch register after the crash to see if it should
restart.
o VOLATILE means statistics gathering during timesharing responds to the setting

of bits 14 and 15 in the switch register. VOLATILE has the same meaning as
ENABLE except that when power fails, RSTS/E always tries to restart
automatically. The ability to restart a RSTS/E system after a power failure
depends on the hardware memory configured on your system. Systems with
volatile memory cannot perform autorestart, regardless of the switch contents.
By specifying VOLATILE, systems with a volatile switch register but with
nonvolatile memory can perform restarts after power failure.
HARDWR 5uboption?

Explanation - After you specify the switch register characteristics, you should list
the hardware configuration table to verify that the change will occur.
Response - Type LIST or LI to list the hardware configuration table. Type EXIT or
press RETURN to return to the Option: prompt.

Offline Options

285

IDENT

IDENT -

List the Version Number and Patch Information
The IDENT option lists the INIT.SYS version number and information about the
patches installed on your system. Use the IDENT option if you are submitting an SPR
to DIGITAL and need to obtain this information.

IDENT Dialogue
Option: IDENT

Response - Type IDENT or ID to the INIT.SYS Option: prompt.
INIT VS.O-1Q [Built DD-MMM-YYJ
Option:

Explanation - IDENT prints the INIT.SYS version number, then returns to the
Option: prompt.

Offline Options

287

PATCH

PATCH -

Install a Patch
The PATCH option provides a method for altering RSTS/E system code. Use the
PATCH option if you need to correct errors in the system code. Use the PATCH
option only as directed by DIGITAL.
Patching makes permanent changes to the code on disk and has no effect on the
code currently in memory. Therefore, after patching the initialization code, you must
bootstrap the system disk to load the corrected initialization code into memory.
DIGITAL publishes mandatory corrections to code in the RSTSIE Release Notes if the
changes are concurrent with the release of the distribution kits. Between releases,
patches are published in the monthly RSTSIE Software Dispatch. The following
procedures describe the PATCH option in detail. In general, however, published
patches include the necessary instructions.
Patches take many different forms. Some are in-place patches to one or more words
in one or more modules. Others require patch space in the affected areas. The
RSTS/E monitor, initialization code, and run-time systems always include patch space.
You can patch the overlay code by using free space in overlay segments or monitor
patch space. Sometimes, patches affect fixed addresses and are straightforward.
Usually, however, the exact octal address of a patch varies from system to system
according to the system configuration. Published patches describe in detail the
procedures required to make the alterations correctly.
When you install a new RSTS/E system, refer to the RSTSIE Release Notes and the
RSTSIE Software Dispatch for patches and patching information. Unless instructed
otherwise, you should install all required patches immediately after installing your
RSTS/E monitor.
Table 30 lists the PATCH error messages. If your error message does not appear
there, see Appendix A.

PATCH Dialogue
Option:

PATCH

Response - Type PATCH or PA to the INIT.SYS Option: prompt.
File to patch?

Explanation - PATCH asks for the file to patch. You can patch any file in account
[0,1]. This directory includes the initialization code (INIT.SYS) and any .SIL, .RTS, or
.LIB file.

Offline Options

289

PATCH

Response - Type the name and extension of the file that requires patching. Or,
press RETURN to patch the installed monitor SIL. In some cases you may need to
append the IN qualifier to the name of any file that is not a SIL.
File found in account [PfPn]

Explanation -

PATCH prints this message if it finds the file.

Module na/Tle?

Explanation - The module name designates the SIL module to be patched. You
can obtain a list of SIL modules by typing a ? in response to this question.
Response - Type the module name you want to patch.
Base address?

Explanation - The base address defines the actual locations to be patched. For
instance, if you are patching the PRINT USING section of BASIC-PLUS, you would
enter the symbol PU as the base address.
Response - Type the base address of the file you want to patch. Responses can be
numbers or expressions. Valid octal numbers are 0 to 177777, and leading zeros are
optional. Valid decimal numbers are O. to 65535., and are distinguished from octal
numbers by the presence of a trailing decimal point.

When patching a SIL, you can substitute a global symbol name for an octal number.
The symbol table for the module being patched may be part of the SIL file. If the
symbol table exists, it contains that module's global symbol names and their values. A
global symbol name must be one- to six-alphanumeric characters and must be
defined in the symbol table. To refer to a global symbol in another module of the
current SIL, type the symbol name followed by the commercial at sign (@) and the
name of the module in which the symbol is defined. For example, DISK@ERR refers
to the symbol DISK in the module ERR.
An expression consists of one or more numbers or global symbols, separated by
arithmetic operators (+, -, *, and f). You can use parentheses to group portions of an
expression.
Offset address?

Explanation - The offset address is the first location to be patched relative to the
specified base. For instance, a PRINT USING patch may begin at offset of 100 octal
bytes from the beginning of PRINT USING.
Response - Type the offset address of the file you want to patch. See the previous
response for a description of legal values.
Base
128488

290

Offline Options

Offset
001010

Old
000034

New?
?

PATCH

Explanation - After you specify the base and offset addresses, PATCH opens the
specified locations, prints the old contents, and accepts input. If the old contents do
not match what is shown under "Old" in the published patch, then you may have
made an error. Remove any changes you have already made and try again.
Response - Table 29 summarizes the possible responses to this prompt.
Table 29:

Possible Input to the PATCH Option
Input

Meaning

Number, symbol, or expression

Enter the number, symbol, or expression as the new contents
of the current location.

Advance to the next location without altering the contents of
the current location.

,.. (circumflex)

Return to the previous location without altering the contents of
the current location.

(CTRUZ)

Return to the previous question.

(CTRUC)

Finish all patching and return to the Option: prompt.

PATCH makes each specified change immediately after you press RETURN. Therefore, if you make an error, you must patch the location again to correct your mistake.
To check that an entire patch is correct, type CTRL/Z to return to the Offset address?
question. Type the same offset, then press RETURN to examine all the patched
locations. If the old contents listed for any location do not match the "New" column
in the published patch, restore all locations to their original contents and install the
patch again. If you have followed the published patch procedures correctly and the
old contents do not match the published patch, consult your software support
representative.
126466

001012

010523

Patch cOMPlete
Option:

Explanation - You terminate a PATCH operation by entering CTRL/C. PATCH
then finishes all patching and returns to the Option: prompt.
If you patch the initialization code, you must reboot the system. Rebooting loads the
changed version of the initialization code into memory. To perform the bootstrap
procedure, follow the instructions in the published patch and use the INIT.SYS
BOOT option.

Response - Type CTRL/C when you have finished the PATCH operation.
Table 30 lists the PATCH error messages. If your error message does not appear
there, see Appendix A.

Offline Options

291

PATCH

Table 30:

PATCH Error Messages
Message and Meaning

ADDRESS ABOVE MODULE BOUNDS
The address you specified exceeds the upper bound of the module.
ADDRESS BELOW MODULE BOUNDS
The address you specified is below the lower bound of the module.
BLOCK OFFSET BEYOND EOF
The block offset address you typed is greater than or equal to the number of blocks in the file.
FILE NOT FOUND
The initialization code did not find the file you specified in account [0,1] on the system disk.
ILLEGAL FILE NAME
The file name you typed is in an incorrect format. Or, you pressed RETURN and no monitor SIL
is installed.
INVALID MODULE NAME
The module name you typed is in an incorrect format. The name must be one- to sixalphanumeric characters.
INVALID CHARACTER
The expression line contains an illegal character.
INVALID EXPRESSION
The expression contains an illegal symbol name or an invalid operator. Symbol names must be
one- to six-alphanumeric characters. Valid operators are +, -, *, and I.
INVALID SIL FORMAT
The file you specified does not contain a valid SIL directory. If the file is not a SIL, append the
IN qualifier to the file name.
MODULE NOT FOUND IN SIL
The module you specified is not in the SIL. Type a ? in response to the MODULE NAME
question for a directory of SIL modules.
SYMBOL NOT FOUND IN STB
A symbol you typed is not in the symbol table for the module.

292

Offline Options

REFRESH

REFRESH -

Perform File-Related Tasks
The REFRESH option performs tasks as~ociated with system files. System files are
files that are of particular use to the system itself. They reside in account [0,1]. The
following sections describe the REFRESH suboptions.
The REFRESH suboptions are:
o REFRESH LIST -

List File Status Table

o REFRESH FILE -

Change Account [0,1] File Characteristics

o REFRESH BADS -

Expand the Bad Block File

Table 31 lists the REFRESH error messages. If your error message does not appear
there, see Appendix A.
Table 31:

REFRESH Error Messages
Message and Meaning

CANNOT REFRESH THIS DISK
Rerun DSKINT and then try REFRESH again.
CANNOT CHANGE OR MOVE .RTS OR .SIL WITH REFRESH
You cannot move or change any files with a .RTS or .SIL file type.
ILLEGAL DISK NAME
The response you typed is not a valid disk name. Valid disk names are OK, DL, OM, DP, DR,
DB, and DU. Press RETURN to use the system disk.
ILLEGAL SUBOPTION
The response you typed is not a valid sub option name.
SORRY, BUT THAT DISK DOESN'T EXIST
The disk device or unit number you specified does not exist on this PDP-l1. Use the HARDWR
option to list the hardware configuration.
THAT FILE CANNOT BE CHANGED
You cannot modify the file.
THAT FILE IS THE CURRENTLY INSTALLED SIL AND CANNOT BE MOVED OR DELETED
You cannot move or delete the installed monitor SIL.
TOO MANY BAD BLOCKS
There can be no more than 161 clusters in the bad block file.

System File Background Information
System files need contiguous space on the disk. It is better to create system files
during system installation when there is sufficient contiguous space on the disk. If you
initialized a nonsystem disk, you can create some of these files on the nonsystem
disk, freeing space on the system disk.

Offline Options

293

REFRESH

This section explains the system files. It groups the files into two sets: those files that
are automatically created during system installation, and those optional files that you
can create according to the needs of your installation.
Automatically created during installation
• SWAP.SYS
o SWAPl.SYS
o BUFF.SYS
o CRASH.SYS

Optional
o

SWAPO.SYS

o SWAP3.SYS

.OVR.SYS
• ERR.SYS
Use the INSTALL FILE/SYSTEM command (see the RSTS/E System Manager's
Guide) if you need to recreate some files at different sizes, or create optional files

according to the needs of your particular installation.
Table 32 shows the system files, whether they are automatically created or optional,
their optimal location, and a formula for calculating the size. The following sections
explain this table in more detail.

294

Offline Options

REFRESH

Table 32:

Summary of System File Creation

System
File

Location

Status

Size

Automatically Created Files
SWAP.SYS

INIT.SYS creates this
file at the minimum
size. (See Task 2 of
Phase 7 in Part I.)

First available location,
starting from beginning
of disk.

1 job * SWAP MAX * 4

SWAP1.SYS

INSTAL.COM creates
this file at a size large
enough to hold all the
jobs on your system.
(See Task 1 of Phase
5 in Part I.)

Near SATT.SYS file,
usually center of
system disk.

(# of jobs - 1) * SWAP
MAX * 4

BUFF.SYS

Required for TU56
DECtape.
INSTAL.COM creates
this file, if needed.
(See Task 1 of Phase
5 in Part I.)

Near SATT.SYS file,
usually center of
system disk.

4 blocks * # of TU56
DECtapes

CRASH.SYS

INIT.SYS creates this
file. (See Task 2 of
Phase 7 in Part I.)

First available location
on system disk.

Sum of low core data
region, XBUF pool, FIP
buffer pool, MSCP
region (cannot be
calculated)

Optional Files
SWAPO.SYS

Optional

Center of nonsystem
disk.

# of highly interactive
jobs * SWAP MAX * 4

SWAP3.SYS

Optional

Center of nonsystem
disk.

#of event-driven jobs *
SWAP MAX * 4

OVRSYS

Optional

Center of system or
nonsystem disk.

Maximum of 128 blocks

ERRSYS

Optional

Center of system or
nonsystem disk.

Same size as ERR ERR
(16 blocks)

The SWAP.SYS File

Definition - The SWAP. SYS file is one of four available swap files, which stores
jobs transferred out of memory.

Offline Options

295

REFRESH

Status - The SWAP.SYS file is required. Without this file, the monitor cannot swap
jobs out of memory; your system will not work. INIT.SYS automatically creates a
minimum SWAP.SYS file during system installation at a size large enough to hold 1
job. (See Task 2 of Phase 7 in Part I.)
Location - INIT.SYS positions the SWAP.SYS file on the system disk at the first
available location, starting at the beginning of the disk.
Size - The size of the SWAP.SYS file is:
1 job * SWAP MAX * 4

The SWAPl.SYS File
Definition - The SWAP1.SYS swap file performs the same function as
SWAP.SYS. The monitor uses this file to store highly interactive jobs - jobs that get
transferred in and out of memory frequently.
Status - The INSTAL. COM command file automatically creates a SWAP1.SYS file
during system installation (see Task 1 of Phase 5 in Part I).
Location - INSTAL. COM places this file as close to the SATT.SYS file as possible,
usually the center of the system disk.
Size - INSTAL. COM creates the SWAP1.SYS file at a size large enough to hold all
the jobs on your system, according to this formula:
(# of jobs - 1) * SWAP MAX * 4

Reasons for Creating - This file provides enough swap file space to accommodate
all the jobs on your system. When the monitor transfers a highly interactive job out of
memory, it places the highly interactive job in the first available space in a swap file,
starting with SWAPO.SYS. If it does not find any space (or SWAPO.SYS does not
exist), the monitor looks for space on SWAP1.SYS, then SWAP.SYS, then
SWAP3.SYS.
The BUFF.SYS File
Definition - The BUFF.SYS file stores the DECtape directory buffers.
Status - You must have this file for your RSTS/E monitor to support one or more
TU56 DECtapes. The INSTAL.COM command file automatically creates BUFF.SYS
during system installation, if it is needed. (See Task 1 of Phase 5 in Part I.)
Location - INSTAL. COM creates BUFF.SYS as close to the SATT.SYS file as
possible, usually the center of your system disk.
Size - The size of this file depends on how many TU56 DECtapes you plan to
support. INSTAL. COM allocates four blocks for each TU56 DECtape.

296

Offline Options

REFRESH

The CRASH.SYS File
Definition - The CRASH.SYS file stores information about the read/write area of
the monitor and the extended buffer pool (often called XBUF) when a system crash
occurs.
Status - You must have CRASH.SYS to enable the crash dump feature. This
feature causes the read/write area of the monitor and the extended buffer pool to be
dumped into CRASH.SYS when a system crash occurs. INIT.SYS automatically
creates this file during system startup. (See Task 2 of Phase 7.)
Location - INIT.SYS positions the CRASH.SYS file at the first available location on
the system disk.
Size - INIT.SYS creates CRASH.SYS at a size equal to the sum of these four
regions:
o

Low core data region of the monitor

o FIP buffer pool
o XBUF pool
o MSCP region, if it exists on the system

Planning the SWAPO.SYS File
Definition - The SWAPO.SYS swap file performs the same function as
SWAP1.SYS. The monitor uses this file to store h!ghly interactive jobs.
Status - SWAPO.SYS is an optional system file.
Location - This file is usually located at the center of a nonsystem disk.
Reasons for Creating - Create this file if you have a system and a nonsystem
disk, and you want more swap file space. There is no point in having this file on the
system disk. When the monitor transfers a highly interactive job out of memory, it
places the highly interactive job in the first available space in a swap file, starting with
SWAPO.SYS. If it does not find any space (or SWAPO.SYS does not exist), the
monitor looks for space on SWAP1.SYS, then SWAP.SYS, then SWAP3.SYS.
Thus, you can increase the speed of swapping highly interactive jobs by creating
SWAPO.SYS at the center of the nonsystem disk. The SWAP1.SYS file would then
not need to exist on your system disk, freeing valuable space and balancing the I/O
load on your disks.

Size - Estimated # of highly interactive jobs * SWAP MAX * 4
Planning the SWAP3.SYS File
Definition - SWAP3.SYS is a swap file that performs the same function as
SWAP.SYS. The monitor uses this file to store event-driven jobs - jobs that do not
get transferred in and out of memory frequently. Examples of event-driven jobs are
QUEMAN, ERRCPY, OPSER, and SPOOL.

Offline Options

297

REFRESH

Status - The SWAP3.SYS file is an optional system file.
Location - This file is usually located at the center of a nonsystem disk.
Reasons for Creating - Create SWAP3.SYS if you have a system and a
nonsystem disk, and you want more swap file space. There is no point in creating this
file on the system disk. The monitor uses a different method to swap event-driven
jobs than it does for highly interactive jobs. Instead of starting with SWAPO.SYS, the
monitor places the event-driven job in the first available space starting with
SWAP3.SYS. If it does not find any space, the monitor looks for space on
SWAP.SYS, then SWAP1.SYS, then SWAPO.SYS.
Thus, you can speed up the swapping of event-driven jobs by creating SWAP3.SYS
at the center of the nonsystem disk. The SWAP1.SYS file would then not need to
exist on your system disk, freeing valuable space and balancing the lID load on your
disks.

Size - Estimated # of event-driven jobs * SWAP MAX * 4
Table 33 shows the approximate amount of time in seconds needed to transfer
different size job images for different disks. Use this information to create swap files
on the disks that you feel will give you optimum performance.

298

Offline Options

REFRESH

Table 33:

SWap Times

Disk

Job Size (in words)
16K

28K

32K

64K

RL01/02

.13

.1S

.19

.32

RK05

.25

.3S

.43

.7S

RK06/07

.11

.15

.17

.29

RP02/03

.16

.24

.27

.50

RP04

.OS

.11

.12

.20

RP05/06

.OS

.11

.12

.20

RM02

.OS

.11

.12

.20

RM03/05

.06

.OS

.09

.14

RMSO

.06

.OS

.09

.14

RA60

.07

.OS

.11

RASO

.06

.OS

.09

.14

RAS1

.05

.06

.07

.10

RC25

.06

.07

.OS

.13

RD51

.14

.17

.19

.29

RD52

.10

.14

.15

.26

The swap times for each disk were calculated using the formula:
Job size * 2
Swap time = Avg access time + - - - - Transfer speed
where:
Average access time

measured in seconds, is defined as the sum of the
average seek time and the average latency time.

Transfer speed

is measured in kilo-bytes per second (KB/S).

Job size

is measured in kilo-words (KW).

See the appropriate Peripherals Handbook for the average access time and transfer
speed of a particular disk.

Offline Options

299

REFRESH

Planning the OVR.SYS File
Definition - The OVR.SYS file can store a copy of certain parts of the currently
installed monitor save image library (SIL).
Status - You do not need to create OVR.SYS. It is an optional system file.
Location - You can create OVR.SYS on either the system or nonsystem disk. You
should locate OVR.SYS as close as possible to the center of the disk, so that the
monitor can access it qUickly.
Reasons for Creating OVR.SYS - OVR.SYS stores part of the monitor code that
is located in the installed monitor SIL. Since your RSTS SIL is now located at the
center of the disk, the OVR.SYS file is no longer useful. Create it only if you position
the RSTS SIL at the beginning of the disk, or create it in the center of a nonsystem
disk to balance the 1/0 load.
Size - The maximum size of the OVR.SYS file is 182 blocks.
Planning the ERR.SYS File
Definition - The ERR.SYS file stores a copy of the system error messages, which
are located in the ERR. ERR file. You copied ERR. ERR to your system disk in Phase
2 of Part I.
Status - You do not need to create ERR.SYS; it is an optional system file.
Location - Create ERR.SYS on a nonsystem disk if you have one. Otherwise,
create ERR.SYS on the system disk. Locate ERR.SYS as close as possible to the
center of the system or nonsystem disk to improve access and response time for error
messages.
Reasons for Creating ERR.SYS - ERR.SYS is merely a copy of ERR. ERR, but
ERR. ERR may be located at the beginning of the disk rather than at the center. Files
are more qUickly accessed when they are located in the center of the disk. You
cannot move ERR. ERR, but you can locate ERR.SYS as close to the center of the
disk as possible. Thus, when the monitor needs to access system error messages, it
will access ERR.SYS instead of ERR. ERR, thereby increasing system performance.
If you are not worried about error messages taking a few milliseconds longer, then
you do not need to create ERR.SYS.

Size - ERR.SYS should be the same size as ERR. ERR. Use the LIST suboption of
REFRESH to see the size of ERR.ERR (16 blocks).
Figure 10 provides a system file creation worksheet that allows you to write the sizes
and locations of the system files you need to create or change. Note that the formula
for calculating the center of the disk for these files is based on the assumption that
you placed the SATT.SYS file at the center of your disk during disk initialization.

300

Offline Options

REFRESH

FORMULA FOR LOCATION:
(STARTING LBN FOR SATI.SYS) - (X TOTAL BLOCKS) = STARTING LOCATION OF FILES
2

where:
STARTING LBN
FOR SATT.SYS

is the starting logical block number for the SATT.SYS
file. You can find this. by looking at the file status table
in the LBN column.

X TOTAL
BLOCKS

is the total number of blocks for the system files you
want to create on that disk.

System File

Size (in blocks)

Location

SWAP.SYS
SWAPO.SYS
SWAPl.SYS
SWAP3.SYS
OVR.SYS
ERR.SYS
BUFF.SYS
CRASH.SYS

MK-01094-00

Figure 10: System File Creation Worksheet

Offline Options

301

REFRESH

REFRESH LIST -

List File Status Table

The LIST suboption of REFRESH lists the file status table. The file status table lists all
the files that can reside in account [0,1] of your system and nonsystem disk. You
should list the file status table before and after creating or changing any system files.

LIST Dialogue
Option: REFRESH

Response - Type REFRESH or RE to the INIT.SYS Option: prompt.
dd-MMM-YY - hh:MM AM/PM

Explanation - REFRESH prints the current date and time, then asks for the device
designator of your disk.
Response - Possible responses for your disk are: OK, DL, OM, DP, DR, DB, or
DU.
Unit?

Explanation - This question asks for the number of the drive on which your
system disk is mounted.
Response - Type the unit number of the drive on which your disk is mounted.
Rebuild?

Explanation - This question asks if you want to force a rebuild of a disk that you
think might be corrupt. The rebuild feature of REFRESH rebuilds the SATT.SYS file
and checks the consistency of directories. Normally, you rebuild a disk if it was
dismounted improperly.
Response - Type YES to force a rebuild of the disk; type NO if you do not want to
force a rebuild of the disk. Even if you type NO, REFRESH rebuilds the disk if it is
necessary.
REFRESH suboption?

LIST

Explanation - You are now finished with the questions asked by REFRESH and
are at the REFRESH suboption? prompt. Now you can list the file status table for the
system disk.

302

Offline Options

REFRESH

Response -

Type LIST or LI.

File
NatTie

Required?

File
Flags

Status

Current
Size

Min i tTlLltrl
Size

Start
lBN

128

la09

SYstetTI files:
SWAP
SWAPO
SWAPl
SWAP3
OVR
ERR
BUFF
CRASH

.SYS
.SYS
.SYS
.SYS
.SYS
.SYS
.SYS
.SYS

YES
NO
NO
NO
NO
NO
NO
NO

NOD CTG
CTG

NOD CTG

OK
OK
OK
OK
OK
OK
OK
OK

a992

a865

85
16
313

1537

Others:
BADB .SYS
SATT .SYS
ERR
.ERR
BACKUP.TSK
IN IT .SYS
SYSGEN.SIl
.RTS
DCl
UPDATE.COM
RT 11
.RTS
RS~·{
.RTS
DDT
.SYS
INSTAl.COM
SYSINI.COM
RSTS90.SIl
START .COM
ANAlYS.COM
lOGIN .COM
BASIC .RTS

NOD
NOD CTG
NOD eTG
CTG
NOD CTG
CTG
CTG
CTG
CTG
NOD CTG
CTG
CTG
CTG
NOD CTG
CTG
CTG
CTG
CTG

REFRESH suboption?

20
a

26873

16
100

55a

165
721
1281

557
128
2

20
6

1873
1893

la
2a

1917

3
57a

13
1

12a17
a061

2101

11201

Option:

Explanation -

LIST prints the file status table, which has seven colurn'!ls:

o File Name -

This column lists all of the files that can or currently reside in
account [0,1]. The table lists the files in two categories: System Files and
Others.

• Required? - This column has two possible entries: YES, which means the files
are required for the operation of the current monitor; NO, which means the
files are not required for the operation of the current monitor. This column is
always blank for nonsystem files, which are listed under the Others column.
The System File Background section explains how to determine what system
files you need to create.
o File Flags -

This column has two possible entries: NOD, which means you
cannot delete the file during timesharing; CTG, which means the file is
contiguous on the disk.

Offline Options

303

REFRESH

• Status - This column has three possible entries: OK, which means you do not
have to change the file's characteristics; CRE, which means you must create the
file; DIC, which means you must delete and then recreate the file.
G

Current Size - This column shows the current file size in blocks. If the column
is blank, it means the file has not been created. The column also shows the
current size of the nonsystem files.

o Minimum Size -

This column shows the minimum sizes, in blocks, of the

system files.
o Start LBN -

This column shows the logical block number n at which each
contiguous file starts. Disk logical blocks are numbered from 0 to the disk size
minus 1. If the column is blank, it means either the file is not contiguous, or if it
is contiguous, it might be extended and become noncontiguous.

Response - After LIST prints the file status table, it returns to the REFRESH
suboption? prompt. Type EXIT or press RETURN to return to the Option: prompt.

304

Offline Options

REFRESH

REFRESH FILE -

Change Account [0,1] File Characteristics

The FILE suboption of REFRESH creates, deletes, or marks as deletable (or nondeletable) the files that reside in account [0,1].
Use the FILE suboption if:
o You need to delete obsolete run-time system files (files with file types of RTS).
o You need to mark other files (usually application files that you create) as

deletable or nondeletable. You can also do this on line with the IDELETABLE
and /NODELETABLE qualifiers of the SET FILE command.
---------------------- Note -----------------------

You can never modify the characteristics of the INIT. SYS, ERR. ERR,
and installed monitor SIL files, which are located on the system disk.

FILE Dialogue
Opt i on: REFRESH
dd-MMM-YY - hh:MM AM/PM
Di s.'?
Unit?
Rebuild?
REFRESH suboPtion?

FILE

Explanation - Answer the preliminary REFRESH questions. You then see the
REFRESH suboption? prompt.
Response - Type FILE or FI.
File natTle?
File exists. Delete it?

Explanation - The next question asks for the name of the file whose characteristics
you want to change.
Response - Respond with a file name and type. If the file exists in account [0,1],
FILE asks if you want to delete it. Type YES or NO. If your response is NO, FILE
asks the next question.
Size?

Response - To retain the current size, type OLD or press RETURN. Note that if
you type any other response to this question, REFRESH may reallocate the file and
you will lose the data.
Base?

Offline Options

305

REFRESH

Response - To retain the current location, type OLD or press RETURN. Note that
if you type any other response to this question, REFRESH may reallocate the file and
you will lose the data.
Deletable?

Explanation - This question asks if you want to mark a file as deletable or nondeletable. This feature is useful for installations that need to create other files. For
example, you may want to mark some important accounting files as nondeletable.

DUring day-to-day system management you use the SET FILE/DELETABLE and SET
FILEINODELETABLE commands to mark files. See the RSTSIE System Manager's
Guide for details.
Response - Type NO if you want to mark the file as nondeletable; type YES if you
want to mark the file as deletable. Or, type OLD or press RETURN to retain the
current status.
File name? @TIl
REFRESH suboption?

Response - Type another file name or press RETURN to return to the REFRESH
suboption? prompt. Press RETURN once more to return to the Option: prompt. Or,
specify another REFRESH suboption.

306

Offline Options

REFRESH

REFRESH BADS -

Expand the Bad Block File

The BADS suboption of REFRESH lists the bad blocks currently in the bad block file
(BADB.SYS) and adds bad blocks to this file.
Use the BADS sub option if you need to remove blocks from service because they
have gone bad.
Do not use the BADS sub option for any DU class disk, except RX50 floppies. In DU
disks, the hardware automatically handles bad blocks and transparently replaces them
with good blocks.

BADS Dialogue
Option: REFRESH
dd-MMM-YY

hh:MM

AM/PM

Dis~\?

Unit?
Rebuild?
REFRESH suboption? 6ADS

Explanation - Answer the preliminary REFRESH questions. You then see the
REFRESH sub option? prompt.
Response - Type BADS, BAD, or BA.
Bads?

LIST

Explanation - This question asks if you want to list the bad blocks or add bad
blocks to the bad block file.
Response - To list the current contents of BADB.SYS, type LIST. BADS prints the
contents or a message declaring that there are no bad blocks on the disk.
Bads?

Explanation -

BADS returns to the Bads? question.

Response - Type ADD to add bad blocks to BADB.SYS.
Bloc~\

nUITlbe r?

Response - BADS then asks for the bad bloclk number. Type the logical block
number (in decimal) of the bad block. This number can range from 2 to the disk size
minus 1. You can obtain the logical block number of a bad block from the ERRDIS
printout of the disk error.
Really add logical blocK XXXX to BADB.SYS?

Response - This question asks if the number you specified is the one you want
added to BADB.SYS. Type YES to add it. If your response is YES, BADS allocates

Offline Options

307

REFRESH

the pack cluster in which the block resides to BADB.SYS. Use caution, because the
allocation of a cluster to BADB.SYS is irrevocable.
Type NO if you do not want to add it to this file. If you type NO, BADS repeats the
Block numbers? question.
Bads?
Disk is

ID
bein~

rebuilt - wait

ttt

REFRESH suboption?

Press RETURN to exit the BADS suboption. Press RETURN again to
return to the Option: prompt. If you added any bad blocks, REFRESH rebuilds the
disk. The rebuilding operation allows you to delete all files that contain bad blocks.

Response -

308

Offline Options

SAVRES

SAVRES -

Back Up and Copy Disks
The SAVRES option is a disk backup and copy utility. SAVRES has four operational
functions:
o SAVE -

Back up a disk to tape or disk

RESTORE -

IMAGE -

Recreate a disk from tape or disk

Make a copy of a disk

o IDENTIFY -

Extract label information from a SAVRES volume or RSTS/E

disk.
SAVRES provides a nonselective, fast-volume restore and copy capability that
requires few operator responses during the operational dialogue. Unlike the DCL
BACKUP utility, SAVRES processes entire volumes only and does not allow selective
file transfers. When SAVRES encounters bad blocks, it requires no operator intervention. For these reasons, use SAVRES when you need to:
o Create a fast, reliable copy of an entire RSTS/E disk.
o

Make a fast copy to a disk containing bad blocks that may not be reflected in
the BADB.SYS file.

o Make a recovery medium (bootable) for a system disk in case of catastrophic

errors. You can also use BACKUP for this task (see the RSTSIE Release

Notes).
To l:lnderstand SAVRES, you should know these terms:
SAVE format

The format of the output written by a SAVE operation and read
by a RESTORE operation.

SAVE set

The set of magnetic tapes or disks created by a SAVE operation.
A SAVE set must be composed entirely of disks or tapes; it
cannot be a combination of the two device types. However, you
can mix different drive types within one set, for example, two
RK05's and one RK06.

SAVE volume

One of the magnetic tapes or disks of a SAVE set.

SAVE set name

One- to six-alphanumeric characters used to identify a SAVE set.
By default, the SAVE set name is the same as the pack 10 from
which it was created. However, you can specify another name for
the SAVE set.

Offline Options

309

SAVRES

Like disks

Like disks are units of the same device size (that is, the same
number of data blocks). SAVRES considers the following devices
alike:
- Two RP06 disks
- An RM02 and an RM03
- An RP04 and an RP05
- An RK05 (RKOSJ) and one unit of an RK05F
Therefore, if you copied an RM02 to a SAVE set, the SAVE set
can later be restored either to an RM03 or another RM02.

Normally, you use the SAVRES program off line while running INIT.SYS. You can
also use SAVRES on line, during timesharing. See the RSTSIE System Manager's
Guide for more information about running SAVRES on line.
Note -----------------------

You must run SAVRES off line to copy (SAVE or IMAGE) or restore
(RESTORE) the system disk with which you are currently running on
line. To restore the system disk, you must boot the save set or image
copy and select the SAVRES option.

SAVRES prints messages on your terminal during an operation to tell you its status.
Some messages are for information only; other messages are error conditions that
may require your attention during the dialogue, mount, transfer, or verification phases
of SAVRES.
When the program encounters an error during a dialogue or mount operation, it asks
you to correct the problem and to retype the appropriate command. Such errors
never affect the integrity of the data being transferred.
Errors that occur while SAVRES is transferring or verifying data can, however,
jeopardize data. In this case, SAVRES resolves the problem, aborts the run, or asks
you to continue or to abort the program. The program gives you information to help
you protect your data by printing informational messages and error messages on your
terminal.

310

Offline Options

SAVRES

When SAVRES completes a SAVE, RESTORE, or IMAGE operation, it prints an
optional summary report. This report describes:
• The operation performed
• Device information
G

Start date and time statistics

• Run total statistics
The run statistics include the number of errors encountered during the operation.

If you are not familiar with SAVRES or want more detailed information about it, see
the RSTSIE System Manager's Guide.

Offline Options

311

SAYRES

SAVE -

Back Up a Disk to Tape or Disk
The SAVE function backs up an entire RSTS/E formatted disk to either tape or disk.
The output volumes created by this operation are collectively called the SAVE set and
are written by SAVRES in the SAVE format. You can recreate the original disk only
by using the RESTORE operation. You cannot use other RSTS/E software, such as
BACKUP or PIP.SAV, to restore a SAVE set. Note that you must use SAVE if the
output medium is different from the input medium.
When SAVRES creates a SAVE set, it includes on the output volume an extra set of
directory blocks in case some directory blocks are found to be bad during a
RESTORE operation. These additional blocks are reflected in the total block count for
a SAVE Summary Report. Because the extra blocks are needed only when bad
blocks are encountered during a RESTORE operation, it is unnecessary for SAVRES
to transfer these blocks to the restored volume.
Thus, you will notice a discrepancy between the number of blocks transferred for a
SAVE operation and the number transferred during a RESTORE. Furthermore,
because the extra directory blocks are not transferred to the restored volume, under
certain circumstances you may restore your data to one less volume than existed in
the SAVE set.
The following example illustrates the backup of an RM03 disk to tape. The RM03
source disk is mounted on drive DR1:, write-locked. The destination tape is mounted
on drive MM1: write-enabled.

SAVE Dialogue
Opt i on: SAtJRES

Response - Type SAVRES to the INIT.SYS Option: prompt.
31-Mav-85 - 08:13 AM
SAV/RES Function: SAVE

Explanation - SAVRES prints the current date and time, then asks for the particular function you want to use.
Response - Type SAVE to begin the SAVE operation. The example plans to
perform a backup operation of an RM03 disk.
FrOITl RSTS

dis~\?

DR1:

*** PacK ID/default SAVE Set Name is TOMBAR
Explanation - SAVE asks for the disk you want to back up. SAVE then reads the
pack 10 from the input medium and displays it.

312

Offline Options

SAVRES

Response - Specify the device name and unit number of the source disk. If you
include a pack ID in the device specification, SAVE checks it against the name
already on the disk. If the names do not match, SAVE issues a warning message
informing you of the discrepancy. In the example, the response is DR1:.
To Device? MM1:SAVSET

*** SAVE Set NaMe is SAVSET
Explanation - You specify the medium to which SAVE copies the input data. You
can also include a SAVE set name in the device specification, rather than allow SAVE
to give the SAVE set the same name as the input disk. If you assign the input and
output media separate names, you can better differentiate their identity (with
IDENTIFY) at a future date.
Response - Type the device name, unit number, and Save set name of your
output media (if you want to change the name). In the example, the response is
MM1:SAVSET because it is saving the data onto magnetic tape mounted on drive
MM1:. The new Save set name is SAVSET.
Expiration Date <1-Jun-8G>? ~

Explanation - SAVE creates a default expiration date equal to the current date
plus one year. This represents the date after which you can write over the data
without receiving a warning message and a confirmation prompt.
Response - Press RETURN to accept the default expiration date (1-Jun-86 in the
example.) Or, type a new date. In the example, the response is RETURN.
l.le ri f}' (Yes

0 r

No) <NO>? ~

Explanation - A YES or Y response to this question causes SAVE to perform a
verify pass after it completes the data transfer process. In the verify pass, SAVE
compares the input data with the data it transfers to the output medium. As an
alternative, if you know that you need to verify the transferred data, you can attach
the NERIFY switch to your response to the SAVIRES Function: prompt and thus
suppress the Verify (Yes or No) question.
Response - Type YES to have SAVRES verify the transfer. Type NO or press
RETURN to skip the verification. In the example, the response is RETURN.
Proceed (Yes or No)? YES

*** Initializin~ first SAVE volUMe
*** Be~in

SAVE frOM DR1: to MM1: at 08:20 AM

Explanation - SAVE asks if you are ready to proceed. Type YES to proceed with
the SAVE operation. SAVE then notifies you that it is initializing the first SAVE
volume. Only the first volume of the SAVE set is initialized. When that operation is
complete, SAVE prints a message indicating that the transfer process has begun,
which devices are involved, and the time the operation began.

Offline Options

313

SAVRES

Response - Type YES to proceed with the SAVE operation. Or, type NO to cancel
the operation and return to the SAVIRES Function: prompt.
DisMount Device:
Set NaMe:
Seq #:
Creation date:
Expiration date:

MM1:
SAVSET
1

Friday, 31-MaY-85
Sunday, l-Jun-86

Please label this voluMe!
Mount voluMe

2 of SAVE Set SAVSET

Explanation - The dismount report summarizes the label information found on the
initial SAVE set volume. If SAVRES requires another volume, it asks you to mount
the next volume in the SAVE set after the first volume is exhausted.
Device? MM2:

Explanation - You see this question if the SAVE operation requires multiple
volumes tc? complete the data transfer.
Response - Type the device name and unit number of the second SAVE set
volume. In the example, the second tape is mounted on drive MM2:
Proceed (Yes or No)? YES

*** Be~in SAVE frOM DR1: to MM2: at 08:25 AM
DisMount Device:
Set NaMe:
Seq #:
Creation date:
Expiration date:

MM2:
SAVSET
2

Friday, 31-MaY-85
Sunday, l-Jun-86

Please label this voluMe!
--- SAVE operation cOMPleted at 08:30 AM

Explanation - Again, you have the option to proceed or to abort the operation. If
you type YES, SAVE then notifies you, as it did for the first volume, that the SAVE
operation has begun, that the data is being transferred, and that 08:25 was the time
the SAVE operation began. As soon as SAVE finishes the transfer, it issues the
dismount message for the second volume of the SAVE set, and prompts you for the
next volume.
This example shows only the first two magnetic tapes; however, an actual SAVE
operation may require several more tapes. When SAVE is finished, it informs you that
the SAVE operation is complete, and prints the time it finished.

314

Offline Options

SAVRES

Response - Type YES to proceed. Or, type NO to cancel the SAVE operation and
return to the SAV/RES Function: prompt.
SUITIlTla r~' Re PO rt
SAVE of DR1:TOMBAR to SAVE Set SAVSET
Input Device:
Pac ~\ Clustersize:
Creation date:
Output device:
Set NalTle:
# of VolulTles:

DRI :
8
Frida~'t

31-MaY-85

Magtape
SAI)SET
2
800

Densit~':

Creation date:
Expiration date:

Frida~'t
Sunda~' t

31-MaY-85
1-Jun-86

SAVE started on FridaYt 31-MaY-85t at 08:20 AM

Explanation - The Summary Report prints information for both the input and
output medium, in addition to the date and time of the SAVE operation.
Run Statistics
Transfer Totals:
Total of 54184 blocKs transferred
Error Totals:
Total of

o new bad blocKs encountered on destination.

o files structurally altered.
TilTling Totals:
Total elapsed t i ITle:

0 h rs. t

9 ITlins. t

36 secs.

a it

t i ITle :

0 h rs • t

0 ITIi n s • t

16 secs.

Total process t i ITI e :

0 h rs. t

9 ITIi n s. t

20 secs.

Total

1...1

SAl) / RES Function: (B@
Option:

Explanation - The RUrl Statistics Report prints the number of blocks transferred,
the number of bad blocks encountered, and the times required to perform various
operations. RESTORE returns to the SAV/RES Function: prompt when the operation
has ended.
Response -

Press RETURN or CTRL/Z to return to the INIT.SYS Option: prompt.

Offline Options

315

SAVRES

RESTORE -

Recreate a Disk From Tape or Disk
The RESTORE function recreates a RSTS/E file-structured disk from a SAVE set.
Because SAVRES writes the SAVE set in the SAVE format, no other RSTS/E
software can perform this rebuild process. Before transferring any data, SAVRES tries
to extract bad block information from the destination disk and, if it finds any bad
blocks, incorporates them into the new BADB.SYS file.
The SAVRES program may encounter bad blocks during a RESTORE run. If it does,
it scans the SAIT.SYS file to determine if there is a place where the block
corresponding to a bad block can be relocated. If a large enough area exists on the
destination disk, the program simply moves the data to the new location and modifies
the directory information accordingly.
The relocation of blocks may require RESTORE to change a file's characteristics. This
can occur, for example, if the program encounters a bad cluster while transferring a
contiguous file. To relocate the cluster that falls on the bad block, RESTORE must
make the file noncontiguous. Changes of this type can cause a few problems, but
RESTORE preserves the data and informs you of these adjustments.
The operation ends if there is no way RESTORE can relocate the data cluster. This
can occur if:
o No unallocated pack cluster remains on the disk.
o The file cluster size is larger than the pack cluster size and there is not an

equivalent number of contiguous pack clusters left on the disk.
When SAVRES creates a SAVE set, it includes on the output volume an extra set
of directory blocks in case some directory blocks are found to be bad during a
RESTORE operation. These additional blocks are reflected in the total block count for
a SAVE Summary Report. Because the extra blocks are needed only when bad
blocks are encountered during a RESTORE operation, it is unnecessary for SAVRES
to transfer these blocks to the restored volume.
Thus, you will notice a discrepancy between the number of blocks transferred for a
SAVE operation and the number transferred during a RESTORE. Furthermore,
because the extra directory blocks are not transferred to the restored volume, under
certain circumstances you may restore your data to one less volume than existed in
the SAVE set.
The following example illustrates the restoration of an RM03 disk from the tape SAVE
set created in the previous example. The two SAVE set volumes are mounted on
drives MMl: and MM2:, write-locked. The destination disk is mounted on drive DRl:,
write-enabled.

316

Offline Options

SAVRES

RESTORE Dialogue
Option: SA1.JRES

Response - Type SAVRES to the INIT.SYS Option: prompt.
SAV/RES Function: RESTORE

Explanation - SAVRES asks for the particular function you want to use.
Response - Type RESTORE to begin the RESTORE operation. The example plans
to recreate an RM03 disk from a tape SAVE set.
FroM device? MM1:

Explanation - RESTORE prints the From device? question. Specify the device
name and the unit number of the SAVE set medium. If you include a SAVE set
name in the device specification, RESTORE checks it against the name already on
the set. If they do not match, RESTORE issues a warning message informing you of
the discrepancy.
Response - Type the device name and unit number of the input medium. In
the example, the response is MM1: because the input medium is tape mounted on
drive 1.

***

SAVE Set NaMe/default PacK 10 is SAVSET

Explanation - RESTORE reads the SAVE set name from the input medium and
displays it. Normally, RESTORE uses the name of the input SAVE set as the Pack 10
of the output volume. If you want to use a different pack 10, you can include a new
pack 10 in your answer to the next question.
To RSTS DisK? DR1:TSTPAK

Explanation - RESTORE asks for the output disk of the RESTORE operation. DR
indicates the device mnemonic of the RM03 disk.
Response - Type the device name, unit number, and pack 10 of your output disk
(if you want to change the pack 10 name). In the example, the response is
DR1:TSTPAK because it is recreating an RM03 disk mounted on drive 1. The new
pack 10 is TSTPAK.

*** The voluMe on DR1: is a RSTS disK
*** PacK 10 is MYPAK
*** PacK will be reinitialized
Mount it anyway <NO)? Y

*** PacK 10 is TSTPAK
Explanation - RESTORE checks the pack 10 of the output disk. It then prints a
message showing you that the disk is a RSTS/E disk, has a Pack 10 of MYPAK, and
that RESTORE will reinitialize it. RESTORE issues a mount question that gives you
the option to mount the disk or not.

Offline Options

317

SAYRES

Response - Type Y to mount the disk and reinitialize it. Type N or press RETURN
to cancel the instruction. RESTORE then returns to the To RSTS Disk? question. In
the example, the response is Y because the data on the disk is no longer valuable.
RESTORE then initializes the disk and prints a message showing the new pack ID.
Verify <Yes or No) <NO)? (ff@

Explanation - RESTORE asks if you want to verify the accuracy of the data
transfer. When RESTORE verifies the transferred data, it performs two operations
rather than one. That is, the program performs two passes on the data: once for the
transfer and once for the comparison.
Response - Type N or press RETURN to skip the verify pass. Or, type Y to
perform the data verification. In the example, the response is RETURN because the
comparison of the input data to the data already transferred to the destination disk is
not essential during this particular run.
Proceed <Yes or No)? Y

Explanation -

RESTORE asks if you are ready to proceed.

Response - Type Y to proceed. Or, type N to cancel the operation and return to
the SAV/RES Function: prompt. In the example, the response is Y.

*** Be~in RESTORE froM MM1: to DR1: at 08:28 PM
DislTlount Device:
Set NaMe:
Seq #:
Density:
Creation date:
Expiration date:
Mount voluMe

MM1:
SAVSET
1

800
FridaYt 31-MaY-85
SundaYt l-Jun-8G

2 of SAVE Set SAVSET

Device? MM2:
Proceed <Yes or No)? Y

*** Be~in RESTORE froM MM2: to DR1: at 08:32 PM
Dislrlount Device:
Set NalTle:
Seq #:
Densit}':
Creation date:
Expiration date:

MM2:
SAVSET
2
800
Frida}'t 31-MaY-85
Sunday t l-Jun-8G

Dislrlount Device:
PacK ID:
Pac., Clustersize:
Creation date:

DR1:
TSTPAK
8
Frida}' t 31-MaY-85

Please label this voluMe!
RESTORE operation cOMPleted at 08:37 PM

318

Offline Options

SAYRES

Explanation - RESTORE displays a message to indicate it has begun the transfer.
If the transfer involves multiple volumes, RESTORE transfers the first volume, prints
input medium information and prompts you for the next volume. After you mount
the next volume, specify its device location, and type Y at the Proceed? prompt,
RESTORE continues with the data transfer. RESTORE continues in this manner for
each SAVE set volume. When RESTORE finishes the final volume, it prints an output
dismount message and informs you that the operation is completed.
Response - Mount the additional Save set volumes when prompted. Type the
device location and unit number of the drive on which the next volume is mounted.
Type Y to the Proceed? prompt when you are ready to continue.

In the example, volume 2 of SAVE set SAVSET is mounted on tape drive MM2:.
Volume two is the final volume in the SAVE set.
SUlTllTla ry Repo rt
RESTORE of SAVE Set SAVSET to DR1:TSTPAK
Input Device:
Set NaiTle:
# of IJOIUITles:
Density:
Creation date:
Expiration date:

Ma9'tape
SAVSET
2
800
Friday, 31-MaY-85
Sunday, l-Jun-88

Output Device:
PacK I D:
Pad, Clustersize:
Creation date:

DR1:
TSTPAK
8
Friday, 31-MaY-85

RESTORE started on Friday, 31-MaY-85, at 08:28 PM

Explanation - The Summary Report prints the SAVE set name, the pack 10, and
label information for both the input and output medium, in addition to the date and
time of the RESTORE operation.
Run Statistics
Transfer Totals:
Total of 54184 blocKs transferred
Error Totals:
Total of

o new bad blocKs encountered on destination.

o files structurally altered.
TilTlin9' Totals:
Total elapsed t i ITle:

0 h rs. ,

8 ITI ins. ,

38 sees.

t i ITle:

0 h rs. ,

0 ITI ins. ,

18 sees.

Total process t i ITI e :

0 h rs. ,

8 ITI ins. ,

20 sees.

Total wait

SAlJ/RES Function: @
Option:

Offline Options

319

SAYRES

Explanation - The Run Statistics Report prints the number of blocks transferred,
the number of bad blocks encountered, and the times required to perform various
operations. RESTORE returns to the SAVIRES Function: prompt when the operation
has ended.
Response - Press RETURN or CTRL/Z to return to the INIT.SYS Option: prompt.
---------------------- Note ----------------------

If you are using the output of a RESTORE operation as a system disk,
you must use the INIT.SYS START option to reinstall the desired
monitor Save Image Library (SIL). Before you use START, you must
also redo any necessary HARDWR sub options (such as changing
Hertz) because the START option clears various items set up by the
HARDWR suboptions. This procedure is necessary because a disk can
be saved with SAVE from one system disk and restored with
RESTORE on a system with a different hardware configuration.

. 320

Offline Options

SAVRES

IDENTIFY -

Extract Label Information
The IDENTIFY function obtains label information from a SAVE set volume or a
RSTS/E file-structured disk.
The following example lists the label characteristics of both a SAVE set and a RSTS/E
disk. The SAVE set volume is mounted on drive MMl:, write-locked. The RSTS/E
disk is mounted on drive DRl:, write-locked.

IDENTIFY Dialogue
Option: SAVRES

Response - Type SAVRES to the INIT.SYS'Option: prompt.
SAV/RES Function: IDENTIFY

Explanation - SAVRES asks for the particular function you want to use.
Response - Type IDENTIFY or ID to begin .the IDENTIFY operation. The example
plans to identify a SAVE set volume mounted on drive MMl:.
From device? MM1:

Explanation - IDENTIFY prints the From device? question. Specify the device
'name and the unit number of the SAVE set you want to identify. If you include a
SAVE set name or pack ID in the device specification, IDENTIFY checks it against the
name already on the set. If the names do not match, RESTORE issues a warning
message informing you of the discrepancy and then prints the From device? question
again.
Response - Type the device name and unit number of the medium you want to
identify. In the example, the response is MMl:, because the input medium is tape,
mounted on drive number 1.
Device:
Set Name:
Seq #:
Density:
Creation date:
Expiration date:

Explanation -

MM1:
SAVSET
1

1600
Friday, 31-May-85
Sunday, 1-Jun-86

IDENTIFY prints label information for the tape SAVE set.

SAV/RES Function: IDENTIFY DR1:

Explanation -

IDENTIFY returns to the SAVIRES Function: prompt.

Response - Type the name of the next medium to identify. You can also include
the device name and unit number of the medium in your response. IDENTIFY then
skips the From Device? question.

Offline Options

321

SAVRES

If you do not need to identify any more media, press RETURN to return to the
INIT.SYS Option: prompt.
In the example, the response is IDENTIFY DR!:. This requests SAVRES to identify
the disk pack mounted on DR1:.
Device:
ID:
Pack Clustersize:
Creation date:
Pac~\

DR1:
TSTPAK
8

Friday, 31-MaY-85

SAV/RES Function: @ill
Option:

Explanation - IDENTIFY prints the label information of the disk pack mounted on
DR!:. IDENTIFY returns to the SAVIRES Function: prompt when the operation has
ended.
Response - If you do not need to identify any more media, press RETURN or
CTRUZ to return to the INIT.SYS Option: prompt.

322

Offline Options

SAVRES

IMAGE -

Make a Copy of a Disk
The IMAGE function makes an equivalent copy of a RSTS/E file-structured disk;
however, only transfers from disk to like disk are legal when using the IMAGE
operation. Like disks are units that have exactly the same device size. The SAVRES
program handles bad block recovery during an IMAGE operation in the same way as
RESTORE.
Note - - - - - - - - - - -

If you are using the output of a RESTORE operation as a system disk,
you must use the INIT.SYS START option to reinstall the desired
monitor Save Image Library (SIL). Before you use START, you must
also redo any necessary HAROWR suboptions (such as changing
Hertz) because the START option clears various items set up by the
HAROWR suboptions. This procedure is necessary because a disk can
be saved with SAVE from one system disk and restored with
RESTORE on a system with a different hardware configuration.

The following example shows an IMAGE operation that copies an RP04 disk to an
RP04 disk and verifies the transfer in the same pass. The source disk is mounted on
drive DBa:, write-locked. The destination disk is mounted on drive OBI:, writeenabled.

IMAGE Dialogue
Opt i on: SAVRES

Response - Type SAVRES to the INIT.SYS Option: prompt.
SAV/RES Function: IMAGE/NOERROR

Explanation - SAVRES asks for the particular function you want to use.
Response - Type IMAGE to begin the IMAGE operation. The /NO ERROR switch
causes SAVRES to end the operation whenever the program encounters a run-time
error. Before the program aborts, it prints an error message indicating the source of
the problem.
FrOfrl

RSTS

dis~~?

060:

Explanation - IMAGE prints the From RSTS disk? question. Specify the disk from
which you want to copy the data. If you include a pack 10 in the device specification,
SAVRES checks to see if it matches the actual pack 10 on the disk. If the pack IDs do
not match, SAVRES issues a warning message and prints the From RSTS Disk?
question again.

Offline Options

323

SAYRES

Response - Type the device name and unit number of the disk you want to copy.
In the example, the response is DBa: because the source disk is mounted on drive
DBa:.

*** Input Pack ID/default Dutput Pack ID is SOURCE
Explanation - IMAGE reads the pack ID from the input disk and displays it on
your terminal.
To RSTS DB: Disk? DB1:NICOLA

Explanation - IMAGE requests the device name and unit number of the output
disk. DB indicates the device mnemonic of the RP04 disk.
Response - Type the device name, unit number, and pack ID of your output disk
(if you want to change the pack ID name). In the example, the response is
DBl:NICOLA because it is copying to an RP04 disk mounted on drive 1. Th'2 new
pack ID is NICOLA.

*** The volUMe on DB1: is a RSTS disk
*** Pack ID is OUTPUT
*** Pack will be reinitialized
Mount it anyway (NO)? Y

*** Output PacK ID is NICOLA
Explanation - IMAGE checks the pack ID of the output disk. It then prints a
message showing you that the disk is a RSTS/E disk, has a pack ID of OUTPUT and
that IMAGE will reinitialize it. IMAGE issues a mount question that gives you the
option to mount the disk or not.
Response - Type Y to mount the disk and reinitialize it. Type N or press RETURN
to cancel the instruction. IMAGE then returns to the To RSTS DB: Disk? question. In
the example, the response is Y because the data on the disk is no longer valuable.
IMAGE then initializes the disk and prints a message showing the new pack ID.
Verify (Yes or No) (NO)? Y

Explanation - IMAGE asks if you want to verify the accuracy of the data transfer.
When IMAGE verifies the transferred data, it performs two operations rather than
one. That is, the program performs two passes on the data, once for the transfer and
once for the comparison.
Response - Type N or press RETURN to skip the verify pass. Or, type Y to
perform the data verification. In the example, the response is Y.
Proceed (Yes or No)? Y

Explanation -

324

Offline Options

IMAGE asks if you are ready to proceed.

SAVRES

Response - Type Y to proceed. Or, type N to cancel the operation and return to
the SAV/RES Function: prompt. In the example, the response is Y.
Be~in

IMAGE COpy froM DBO: to OBI: at 11:02 AM

Be~in

VERIFY pass froM DBO: to OBI: at 11:0a AM

o differences found
DisMount Device:
Set Nalrle:
Pack clustersize:
Creation date:

DB 1 :
NICOLA
8

Friday, 31-MaY-85

Please label this voluMe!
IMAGE COpy operation cOMPleted at 11:07 AM

Explanation - IMAGE displays a message when it begins to transfer data and
when it begins the verify pass. After completing the data comparison, IMAGE prints
the number of differences found between the two devices. It then issues the output
device dismount message. Immediately after IMAGE prints the dismount request, it
prints a message to show you the copy operation ended successfully.
SUITllrlary Report
IMAGE COpy of DBO:SOURCE to DB1:NICOLA
Input Device:
Set NaiTle:
Pack clustersize:
Creation date:

DBO:
SOURCE
8
Friday, 31-May-85

Output Device:
Pack 10:
Pack Clustersize:
Creation date:

OBI:
NICOLA
8
Frida}' , 31-MaY-85

RESTORE started on Friday, 31-MaY-85, at 11:02 AM

Offline Options

325

SAYRES

Explanation - IMAGE prints the Summary Report unless you suppress it by using
the !NaSTATS switch. The report includes the pack 10 and label information of each
disk, in addition to the date and time that the IMAGE operation was run.
Run Statistics
Transfer Totals:
Total of 24400 blocks transferred
Error Totals:
Total of

o bad compares.

Total of

o new bad blocks encountered on source.

Total of

o new bad blocks encountered on destination.

o files structurally altered.
TilTlin9' Totals:
Total elapsed time:

0 h rs. f

5 min s • f

22 secs.

Total wait

time:

0 h rs. f

0 min s. f

0 secs.

Total process time:

0 h rs. f

5 min s • f

22 secs.

SAV/RES Function: ~
Option:

Explanation - The Run Statistics Report prints the number of blocks transferred,
the number of bad blocks encountered, and the times required to perform various
operations. IMAGE returns to the SAVIRES Function: prompt when the operation has
ended.
Response - Press RETURN or CTRL/Z to return to the INIT.SYS Option: prompt.

326

Offline Options

START

START -

Start a RSTS/E Monitor
The START option activates a RSTS/E monitor. Use the START option if you need
to start timesharing.
.

START Dialogue
Option: START

Response - Type START or START <monitor name> to the INIT.SYS Option:
prompt.

If you do not specify a monitor name or press RETURN to the Option: prompt,
START starts the monitor that was used in the previous timesharing session. START
then prints a series of questions that let you override SWAP MAX and memory
allocation defaults for one time-sharing session. You can make permanent changes to
these defaults only by using the DEFAULT option.
If you are starting timesharing for the first time on this system disk, INIT.SYS searches
the list of monitors, which are stored in account [0,1] with the file type of .SIL. SIL
stands for save image library, which is a file that stores the monitor code.
If INIT.SYS finds only one SIL, it installs that SIL and prints the message:
Startin~

XXXXXX

Monitor

If INIT.SYS finds more than one SIL, it prompts for the monitor name instead:
Monitor naMe to START <xxxxxx>?

Type the name of the monitor you want to install.
SWAP rTlax <32K)?

Explanation - You see this question only if your system has 1&0 space. START
asks if you want to make any SWAP MAX changes. You can specify a size up to
64K.

Response - Type YES if you need to change the SWAP MAX. Type NO or press
RETURN if you do not want to make any changes.
START now checks that the SWAP.SYS file exists in account [0,1] on the system
disk, is large enough to hold one job at the current SWAP MAX, and is contiguous. If
the file does not exist, START attempts to create SWAP.SYS at the required size. If
the file exists but is not contiguous or large enough, START deletes the current
SWAP.SYS file and attempts to create a new SWAP.SYS file that is both contiguous
and large enough (SWAP MAX * 4). If START cannot find enough free contiguous
disk space to create a minimum SWAP.SYS file, it prints the following error message:
?Not

enou~h

conti~uous

disK space to create MiniMuM SWAP.SYS file

Offline Options

327

START

START then attempts to create a SWAP.SYS file that is smaller than the one you
specified yet still meets the minimum requirements. This may take up to one minute.
If START finds it can create a SWAP.SYS. file, it prints these messages:
SWAP.SYS cari be created if SWAP MAX is reduced to xxK
New SWAP

MAX <xxK>?

Press RETURN to accept the default value, indicated by xx in the example. Or type
CTRL/C to return to the Option: prompt. You can then use the FILE sub option of
REFRESH to create more disk space.
If START cannot find enough contiguous disk space to create a minimum SWAP.SYS
file, it prints these messages:
You Must free SOMe disK space to start

tiMesharin~.

Option:

Use the FILE sub option of REFRESH to create more contiguous disk space.
Any MeMOry allocation

chan~es?

Explanation - START asks if you want to make changes to the memory allocation
table for this timesharing session.
Response - Type YES to make changes to the memory allocation table. (See the
section, DEFAULT Option.) Type NO or press RETURN if you do not want any
changes.

START now checks that the CRASH.SYS file exists in account [0,1] on the system
disk, is large enough for the installed RSTS/E monitor and extended buffer pool
allocation, and is contiguous. If the file does not exist, START attempts to create
CRASH.SYS at the required size. If the file exists but is not contiguous or large
enough, START deletes the current CRASH.SYS file and attempts to create a new
CRASH.SYS file that is both contiguous and large enough. If START is unsuccessful
it prints these error messages:
?Not

enou~h

conti~uous

disK space to create MiniMuM CRASH.SYS file

Crash dUMP autoMatically disabled

328

Offline Options

START

Therefore, if you see the Crash dump automatically disabled message, follow these
steps to enable crash dump:
1.

After you begin timesharing, delete unnecessary files to create more contiguous
disk space. Or, move some files to a nonsystem disk.

Shut down the RSTS/E monitor using the SHUTUP program.

Use the START option to start timesharing. If you do not see the Crash dump
disabled message, you know that INIT.SYS was able to create the
CRASH.SYS file.

dd-MMM-YY

hh:MM

AM/PM

Explanation - START prints the current date and time. Then it pauses for several
seconds to prepare the system for timesharing. START performs many preparatory
tasks, among the more important being:
o Verify that all configured hardware exists and that it responds properly.
o Disable any device it cannot find or that you have disabled with the HARDWR

option. If this is the case, START prints the devices it disables.
o Enable all configured terminal controllers and disable any that do not respond.
o Set up monitor, cache, and device tables.
o Load the installed monitor into memory.

START then transfers control to the SYSINI. COM command file, which executes the
START.COM command file. See the RSTSIE System Manager's Guide for details
about START.COM.

Offline Options

329

Initialization Code Error Messages
The RSTS/E system initialization code routines make many checks to ensure the
consistency of system structures. Initialization routines compare existing structures with
their definitions and with references in other parts of the system. The checks must be
successful; if not, the routines detect a consistency error, which indicates that the
system is corrupted.
The initialization routines may also encounter errors while attempting to execute
initialization options. The error text for many of these errors is preceded by the
message FATAL RSTS/E SYSTEM INITIALIZATION ERROR. The initialization code
prints a descriptive error message and returns to the Option: prompt. If such an error
occurs, follow the error recovery procedures in Table A-I. If these procedures are
unsuccessful, consult your DIGITAL Software Support Specialist.
For many of the errors, no recovery procedures exist. If such an error occurs, you
should submit a Software Performance Report (SPR) as noted in the recovery
procedures column for that error message.

331

Table A-1:

Initialization Code Error Messages
Message and Recovery Proce4ure

ACCOUNT [1,2] MISSING FROM OUTPUT DISK
Reinitialize the disk as a system disk and create the library account.
BAD [0,1] DIRECTORY
Reboot the system disk and retry the operation. If the retry fails, use DSKINT to reinitialize the
disk.
BADB.SYS NOT FOUND - RESULTS UNPREDICTABLE
Reboot the system disk and retry the operation. If the retry fails, use DSKINT to reinitialize the
disk.
BUFF.SYS NOT FOUND OR TOO SMALL-DECTAPE DISABLED
Warning message only. Shut down the system and use REFRESH to create the file at the
required size.
CANNOT REFRESH THIS DISK
Reinitialize the disk.
CANNOT START WITH THIS SWAP MAX AND MEMORY TABLE
Use DEFAULT to change the SWAP MAX and/or memory allocation table.
CLUSTER 1 (REQUIRED FOR MFD) CONTAINS A BAD BLOCK
If the pack cluster size for the disk is greater than the device cluster size, use DSKINT to
reinitialize the disk with a lower pack cluster size. If the error recurs, use a different disk.
CLUSTER ALLOCATED TO [P,PN] filnam.typ IS NOT ON A PACK CLUSTER BOUNDARY
REBUILD asks whether to delete the file, then confirms your response.
[P,PN] CLUSTER MAP IN UFD DISAGREES WITH MFD
REBUILD asks whether to zero the account and confirms your response.
DEFAULT RTS HAS INVALID SIZE PARAMETERS
Recopy the run-time system from the distribution kit.
DEFAULT RTS NOT FOUND OR INVALID
Make sure that a valid run-time system is on the system disk. Recopy the run-time system from
the distribution kit if necessary.
DEVICE xx: DOES NOT INTERRUPT - DEVICE DISABLED
Use HARDWR to set the correct vector address for xx. Or the device may be broken. Call your
DIGITAL Field Service engineer. If the disk is an RC25, a cable may be disconnected.
DEVICE CONTROLLER TABLE (DDCTBL) DECLARES TOO MANY UNITS FOR CONTROLLER
SIL CANNOT BE INSTALLED
Submit an SPR with a copy of the SIL and INIT.SYS.
DEVICE CONTROLLER TABLE (DDCTBL) HAS AN ILLEGAL FORMAT
SIL CANNOT BE INSTALLED
Submit an SPR with a copy of the SIL and INIT.SYS. You may have a corrupt Distribution Kit.
DEVICE ERROR WHEN TRYING TO BOOTSTRAP DEVICE
Make sure that the device is on line and ready. If the error recurs, try a different device.
(continued on next page)

332

System Installation Error Messages

Table A-1:

Initialization Code Error Messages (Cont.)
Message and Recovery Procedure

DEVICE HUNG OR WRITE-LOCKED
Make sure that the device is on line and ready. If the error recurs, try a different device.
DEVICE XDO: CSR MUST BE DECLARED WITH HARDWR, CSR SUB-OPTION - DEVICE
DISABLED
Use the CSR sub option of HARDWR to set the correct CSR address for XDn:. The XD device is
not located at a DIGITAL standard CSR assignment.
DEVICE XDO: TIMED-OUT ON INTERNAL MICRO-DIAGNOSTIC CHECK - DEVICE DISABLED
Call your DIGITAL Field Service engineer. The error message indicates that INIT encountered a
device time-out error.
DIRECTORY ENTRY FOR [P,PN] filnam.typ CONTAINS PACK CLUSTER NUMBER WHICH IS
TOO BIG
REBUILD asks whether to delete the file and confirms your response.
DIRECTORY ERROR DETECTED IN RDB
Reinitialize the disk.
DIRECTORY ERROR - FILE NOT FOUND
Reinitialize the disk.
[0,1] DIRECTORY NOT FOUND
Reinitialize the disk.
DISK BLOCK 0 (REQUIRED FOR BOOTSTRAPS) IS BAD
Reinitialize the disk. If the error recurs, use a different disk.
DISK ERROR DURING DSKINT BUILD PHASE
Reinitialize the disk. If the error recurs, use a different disk.
DISK HUNG OR DATA ERROR DURING OVERLAY
Make sure that the device is on line and ready. If the error recurs, try a different device.
DISK STRUCTURE CANNOT BE REBUILT
Reinitialize the disk.
DOUBLY ALLOCATED BLOCK FOUND AT DEVICE CLUSTER nn. THE BLOCK IS ALLOCATED
TO [p,pn] filnam.typ AND [p,pn] filnam.typ
REBUILD lets you choose the file to delete, then confirms your response.
DRIVE NOT READY:
. Make sure that the disk drive is on line and READY. Press RETURN to retry the operation. Type
any other character to abort the operation.
DSKINT ERROR - ATTEMPT TO FORMAT UNFORMATTABLE DISK
Submit an SPR.
DSKINT OR SYSGEN ERROR - DSKINT ALLOCATION FAILURE
Submit an SPR.
EOF READING INIT.SYS
Submit an SPR.
(continued on next page)

System Insta"ation Error Messages

333

Table A-1:

Initialization Code Error Messages (Cont.)
Message and Recovery Procedure

ERR FILE INVALID
Copy the file ERRERR from the distribution medium to the system disk.
ERR FILE NOT FOUND
Copy th~ file ERRERR from the distribution medium to the system disk.
ERROR DETECTED WHILE READING ERROR RECORD SECTOR #n
Warning message only. Error occurred during reading of factory error records. Disregard the
error message.
ERROR - KB INTERFACES OUT OF SEQUENCE
Regenerate your monitor. If the problem recurs, submit an SPR
ERROR - NO SETUP FOR DISK xx:
Regenerate your monitor. If the problem recurs, submit an SPR
ERROR - UNKNOWN DISK xx:
Regenerate your monitor. If the problem recurs, submit an SPR
EXCESSIVE BAD CLUSTERS
If you need to use the current disk, use DSKINT to increase the pack cluster size. If the error
recurs, use a different disk.
FATAL DISK ERROR DURING CONTROL RESET
Retry the DSKINT. If the error recurs, call the DIGITAL field service engineer to repair the disk
drive.
FATAL ERROR - NO SMALL BUFFERS LEFT
Regenerate the system and configure more small buffers.
FATAL I/O DURING OVERLAY
Make sure that the device is on line and ready. If the error recurs, try a different device.
xxx FILE NOT FOUND WHEN REMOVING IT
Warning message only. xxx is SIL, RTS, or ERR The initialization code did not find a file when
trying to make it deletable.
[P,PN] filnam.typ HAS A BAD BLOCK
REBUILD asks whether to delete the file and confirms your response.
[P,PN] filnam. typ HAS FIRST DCN OUT OF RANGE
REBUILD asks whether to zero the account and confirms your response.
[P,PN] filnam.typ HAS INVALID ACCOUNTING ENTRY LINK
REBUILD asks whether to delete the file and confirms your response.
filnam. typ HAS ILLEGAL FORMAT AND CANNOT BE COPIED
Submit an SPR if DIGITAL supplied the file on the distribution medium. Regenerate your system
monitor if the system installation process created the file.
FORMATTING FAILURE:
Press RETURN to retry. Type anything else to abort the DSKINT and return to the Option:
prompt. Make sure that the disk drive is write enabled. This error may indicate a bad disk pack
or a bad disk drive.
(continued on next page)

334

System Installation Error Messages

Table A-1:

Initialization Code Error Messages (Cont.)
Message and Recovery Procedure

[P,PN] HAS A BAD BLOCK
REBUILD asks whether to delete the account and confirms your response.
[P,PN] HAS HOLES IN CLUSTER MAP
REBUILD asks whether to zero the account and confirms your response.
[P,PN] HAS INCONSISTENT CLUSTER MAPS
REBUILD asks whether to zero the account and confirms your response.
[P,PN] HAS INVALID CLUSTER SIZE
REBUILD asks whether to delete the account and confirms your response.
ILLEGAL INTERFACE INDEX nn
Regenerate your monitor. If the error recurs, submit an SPR..
INIT BUG - BAD DISK INDEX
Submit an SPR and a copy of INIT.SYS.
INIT BUG - CAN'T ALLOCATE FILE 2ND TIME
Submit an SPR and a copy of INIT.SYS.
INIT BUG - CAN'T CHECK PARITY
Submit an SPR and a copy of INIT.SYS.
INIT BUG - CAN'T FIND [0,1] AGAIN
Submit an SPR and a copy of INIT.SYS."'
INIT BUG - CAN'T FIND FILE TO DELETE
Submit an SPR and a copy of INIT.SYS.
INIT BUG - REBUILD FAILED TO FIND ALLOCATION ERROR
Submit an SPR and a copy of INIT.SYS.
INIT BUG - DIDN'T GET SAME CLUSTER 2ND TIME
Submit an SPR and a copy of INIT.SYS.
INIT BUG - DIDN'T GET SAME FILE CLUSTER 2ND TIME
Submit an SPR and a copy of INIT.SYS.
INIT BUG - DON'T KNOW HOW TO START
Submit an SPR and a copy of INIT.SYS.
INIT BUG - FAILED TO CREATE FILE
Submit an SPR and a copy of INIT.SYS.
IN IT BUG - FAILED TO FIND FILE AGAIN
Submit an SPR and a copy of INIT.SYS.
INIT BUG - FAILED TO FIND FILE JUST CREATED
Submit an SPR and a copy of INIT.SYS.
IN IT BUG - FILE EXISTS WHEN TRYING TO CREATE
Submit an SPR and a copy of INIT.SYS.
-[NIT BUG - xxx - file type FILE NOT FOUND 2ND TIME
Submit an SPR and a copy of INIT.SYS.
(continued on next page)

System Installation Error Messages

335

Table A-1:

Initialization Code Error Messages (Cont.)
Message and Recovery Procedure

INIT BUG - xxx - FILE NOT FOUND WHEN REMOVING IT
Submit an SPR and a copy of INIT.SYS.
INIT BUG - FILE SIZE COMPUTED WRONG
Make sure that the system device you are using contains valid system files from the distribution
medium. If so, submit an SPR and a copy of INIT.SYS.
INIT BUG - FLOAT TABLE ERROR
Submit an SPR and a copy of INIT.SYS.
INIT BUG - INSTALL NOT SYNCHRONIZED at xxxxxx
Submit an SPR and a copy of INIT.SYS.
INIT BUG - NO SATT.SYS AT WIPEOUT TIME
Submit an SPR and a copy of INIT.SYS.
INIT BUG - NO UFD FOUND IN CREATE
Submit an SPR and a copy of INIT.SYS.
INIT BUG - RNB TO WRONG DISK
Submit an SPR and a copy of INIT.SYS.
IN IT BUG - SATT.SYS NONEXISTENT AT TIME OF WOMP
Submit an SPR and a copy of INIT.SYS.
INIT BUG - SET NEW TABLE TOO SMALL
Submit an SPR and a copy of INIT.SYS.
IN IT BUG - UNKNOWN BAE DEVICE
Submit an SPR and a copy of INIT.SYS.
INIT BUG - START LINKED TOO LOW
Submit an SPR and a copy of INIT.SYS.
INIT LINK BUG - DEFBUF NOT ALIGNED
Submit an SPR.
IN IT LINK BUG - DSTBL TOO LOW
Submit an SPR.
INIT LINK BUG - FIBUF NOT ALIGNED
Submit an SPR.
INIT LINK BUG - INSBUF NOT ALIGNED
Submit an SPR.
IN IT LINK BUG - SATBUF NOT ALIGNED
Submit an SPR.
INIT.SYS NOT FOUND - RESULTS ARE UNPREDICTABLE
Reboot the system disk and retry the operation. If the retry fails, reinitialize the disk.
INPUT FILE MISSING FROM SYSTEM DEVICE
Retry the procedure that generated the error. If the error recurs, submit an SPR.
(continued on next page)

336

System Insta"ation Error Messages

Table A-1:

Initialization Code Error Messages (Cont.)
Message and Recovery Procedure

INSTALLED MONITOR DOES NOT SUPPORT THIS SYSTEM DISK
Regenerate a monitor that supports the system disk or use the COpy option to transfer the
monitor to a disk it supports.
INSTALLED SIL INVALID
The installed SIL is invalid as a monitor SIL. Use the START option to install a valid SIL.
INVALID DATA IN ERROR RECORD SECTOR #n
Warning message only. The error occurred during reading of factory error records. Disregard the
error message.
INVALID RETRIEVAL ENTRIES FOR FILE [p,pn] filnam.typ Warning message. REBUILD truncates the file.

FIXED BY REBUILD

VO TO UNOPENED FILE
Submit an SPR.
[P,PN] IS NOT A VALID ACCOUNT NUMBER
REBUILD asks whether to delete the account and confirms your response.
MEMORY ADDRESSING PROBLEM
Either the memory subsystem or the memory management hardware failed.
MFD NAME ENTRY CONTAINS A BAD LINK. REBUILD WILL DELETE ALL [1,1] FILES AND
ALL ACCOUNTS BEYOND [p,pn] filnam.typ
REBUILD confirms your response.
MONITOR SIL CHANGED - REINSTALL IT
. Use the START option to install the monitor SIL.
MONITOR SIL NOT FOUND
Use the START option again to install the SIL. If the errC?r recurs, submit an SPR.
MT, MS, MM ERROR OR INVALID FORMAT ON TAPE
Make sure that the tape drive heads are clean and correctly aligned. If the error recurs, try using
a different drive.
NO LIBRARY ACCOUNT ON THIS DISK
Reinitialize the disk and create a library account, or create account [1,2] on the disk.
NO ROOM FOR DIRECTORY ON OUTPUT DISK
Delete files, reinitialize the disk to create sufficient contiguous space on the disk for the file, or use
a different disk.
NO ROOM FOR FILE ON OUTPUT DISK
Delete files, reinitialize the disk to create sufficient contiguous space on the disk for the new file,
or use a different disk.
NOT ENOUGH ROOM IN LOW MEMORY FOR MONITOR
Generate a smaller monitor. INIT cannot find enough contiguous, physical memory to place the
monitor in low memory. Before printing this message, INIT attempts to position the monitor in
the memory table, tries to reset the table, and prints the message ADJUSTING MEMORY
TABLE at your terminal. When INIT cannot find enough space for the monitor, it prints the
"NOT ENOUGH ROOM" message and returns to the Option: prompt. You can then begin to
generate a smaller monitor.
(continued on next page)

System Installation Error Messages

337

Table A-1:

Initialization Code Error Messages (Cont.)
Message and Recovery Procedure

NOT ENOUGH ROOM IN MEMORY FOR RUN TIME SYSTEM
Generate a smaller monitor or use RSX as the run-time system. INIT cannot find enough
physical memory for the run-time system. Before printing this message, INIT attempts to position
the run-time system in the memory table, tries to reset the table, and prints the message
ADJUSTING MEMORY TABLE at your terminal. When INIT cannot find enough space, it prints
the "NOT ENOUGH ROOM" message and returns to the Option: prompt. The prompt allows
you to begin generating a smaller monitor or use RSX as the run-time system.
NOT EVERYTHING FITS IN MEMORY WITH THIS MEMORY TABLE. RESETTING MEMORY
TABLE AND ELIMINATING EXTRA BUFFERS
This message can occur after you select a bigger primary run-time system, allocate extra small
buffers, or install a monitor patch that increases monitor size.
ONE OR MORE SYSTEM FILES MISSING'
Reinitialize the disk.
OPTION ATTEMPTED DURING BOOTSTRAP PHASE
Reboot the system and retry the ~peration. If the retry fails, submit an SPR.
OPTION NOT AVAILABLE
The option you requested is not available until you bootstrap the system disk.
OUTPUT DISK IS DIRTY - CANNOT PROCEED
Use REFRESH to rebuild the disk or use DSKINT to reinitialize the disk.
OUTPUT DISK IS NOT A SYSTEM DISK
Reinitialize the disk as a system disk.
OVERLAY HANDLER IN ERROR
Submit an SPR and a copy of the SIL.
OVR NOT IN SIL
Regenerate the monitor.
PACK CLUSTER SIZE IS NOT 1, 2, 4, 8, OR 16
Reinitialize the disk.
PARITY CSR FOUND, BUT NOT RELATING TO MEMORY
Call your DIGITAL Field Service engineer.
PARITY CSR CONTROLS MORE THAN 31K
Call your DIGITAL Field Service engineer.
PERMANENTLY MAPPED REGION OF MONITOR IS TOO LARGE
Regenerate to create smaller monitor. Configure fewer small buffers or fewer devices.
PRIORITY OF xx: INTERRUPT (PRn) IS TOO HIGH - DEVICE DISABLED
Call the DIGITAL field service engineer to install the device correctly.
QUESTION ATTEMPTED DURING AUTO-RESTART
If the system disk needs rebuilding, start the system by typing START or pressing RETURN,
thereby rebuilding the disk. If any other problem occurs, submit ,an SPR.
REQUESTED DISK DRIVE NOT FOUND
Request a disk that is on the system.
(continued on next page)

338

System Installation Error Messages

Table A-1:" Initialization Code Error Messages (Cont.)
Message and Recovery Procedure
REQUIRED MODULE xxxxxx HAS INVALID LENGTH
Regenerate the monitor. If the error recurs, submit an SPR.
REQUIRED MODULE xxxxxx HAS INVALID TRANSFER ADDRESS
Regenerate the monitor. If the error recurs, submit an SPR.
REQUIRED MODULE xxxxxx HAS WRONG LOAD ADDRESS
Regenerate the monitor. If the error recurs, submit an SPR.
REQUIRED MODULE xxxxxx IS IMPROPERLY LINKED
Regenerate the monitor. If the error recurs, submit an SPR.
REQUIRED MODULE xxxxxx IS MISSING A REQUIRED SYMBOL
Regenerate the monitor. If the error recurs, submit an SPR.
REQUIRED MODULE xxxxxx NOT FOUND IN SIL
Regenerate the monitor. If the error recurs, submit an SPR.
REQUIRED MODULE xxxxxx OUT OF SEQUENCE IN SIL
Regenerate the monitor. If the error recurs, submit an SPR.
REQUIRED MODULE xxxxxx TOO LARGE
Regenerate the monitor. If the error recurs, submit an SPR.
REQUIRED MODULE xxxxxx TOO SMALL
Regenerate the monitor. If the error recurs, submit an SPR.
REQUIRED SYMBOL xxxxxx MISSING FROM MONITOR
Regenerate the monitor. If the error recurs, submit an SPR.
RL DISK MUST BE STRAPPED FOR 22-BIT ADDRESSING
The Q-BUS system has more than 256KB of memory, thus requiring 22-bit addressing. The
system also contains an RL disk controller, but the controller is not set up for 22-bit addressing.
The controller must be an RLV12, and it must be strapped for 22-bit addressing.

RSTS/E REQUIRES AT LEAST 96K WORDS OF MEMORY
Your configuration is too small for the system.
RSTS/E REQUIRES EIS!
Correct the hardware configuration to include EIS instructions.
RSTS/E REQUIRES A CLOCK!
Correct the hardware configuration to include a KW11P or KW11L clock.
RSTS/E REQUIRES MEMORY MANAGEMENT HARDWARE!
Correct the hardware configuration to include a memory management unit.
SATT.SYS IS OVER 16 BLOCKS LONG
If the file structure on the disk is sound, submit an SPR and a copy of the disk. Otherwise,
reinitialize the disk.
SATT.SYS NON-EXISTENT AT TIME OF READ
If the file structure on the disk is sound, submit an SPR. Otherwise, reinitialize the disk.
SATT.SYS NOT FOUND - RESULTS UNPREDICTABLE
Reboot the system and retry the operation. If the error recurs, reinitialize the disk.
(continued on next page)

System Installation Error Messages

339

Table A-1:

Initialization Code Error Messages (Cont.)
Message and Recovery Procedure

filnam.SIL NOT FOUND - PLEASE INSTALL A SIL
The SIL that you previously installed is not on the disk. Use the START option to install a
monitor SIL.
SYMBOL xxxxxx NOT FOUND IN MONITOR SYMBOL TABLE
Regenerate the monitor. If the problem recurs, submit an SPR.
SYSTEM DISK DISABLED IN MONITOR
Use the SET option to enable the system disk device.
TOO MANY BAE DEVICES
Submit an SPR.
TOO MANY BLOCKS IN DEVICE CONFIGURATION TABLE
Regenerate the monitor.
TOO MANY xx: CONTROLLERS GENERATED
Make sure that any edits to CONFIG.MAC are correct. If there are no editing errors, regenerate
the system.
TOO MANY RH OR UNIBUS DEVICES
Submit an SPR.
TOO MANY SUBLINES FOR nn:
Make sure that any edits to CONFIG.MAC are correct. If there are no editing errors, regenerate
the system. This message is a warning if the monitor generated for DHU (16 lines) or DZ11 (S
lines) is started on a QBUS system (DHU has only S lines and DZ11 has only 4 lines).
TOO MANY UNIBUS DEVICES ON THIS 11/70
First, disable unnecessary devices with HARDWR or SET. If the error condition persists, use
DEFAULT to lock all memory addresses above 124K. (The computer runs in IS-bit addressing
mode instead of 22-bit addressing mode~) If the error condition is present after you lock memory,
or if the computer has 124K or fewe~ words of memory, submit an SPR.
TOO MUCH MODIFICATION TO MONITOR REQUIRED
Regenerate to produce a monitor that is more closely configured to your system hardware.
TWO MAGTAPE UNITS HAVE THE SAME UNIT NUMBERS
Examine unit switches on magnetic tape drives and make sure that no two have the same unit
number.
UFO HAS SIZE TOO LARGE FOR FILE [P,PN] filnam. typ - FIXED BY REBUILD
Warning message only. REBUILD corrects the condition.
UFD HAS SIZE TOO SMALL FOR FILE [P,PN] filnam.typ - FIXED BY REBUILD
Warning message only. REBUILD corrects the condition.
[0,1] UFD NOT FOUND
Reinitialize the disk.
UNABLE TO CREATE REQUESTED FILE(S)
Delete some files and retry the procedure, or request smaller files. Also, try using the FILE
suboption of REFRESH to create files one at a time.
UNEXPECTED OVERLAY TRAP
Submit an SPR.
(continued on next page)

340

System Installation Error Messages

Table A-1:

Initialization Code Error Messages (Cont.)
Message and Recovery Procedure

UNEXPECTED TRAP THROUGH THE VECTOR AT nnn. TRAP OCCURRED FROM PC =
nnnnnn.
Submit an SPR.
UNKNOWN DEVICE BOOTED
Submit an SPR.
UNKNOWN RH CONTROLLER PRESENT
Call the DIGITAL field service engineer to correct the hardware configuration.
UNRECOVERABLE DISK ERROR ON xxn:
Make sure that the disk is mounted and write enabled (if necessary). If the disk is properly
mounted, this error indicates a fatal disk error. Reformat and reinitialize the disk, or use a
different disk.
USER-DEFINED ADDRESS FOR DEVICE xxn: NOT FOUND - DEVICE DISABLED
Use HARDWR to set the correct CSR address for XX:, or call the DIGITAL field service engineer.
USING KWIIL CLOCK
Warning message only. The installed SIL's defaults indicate a KWIIP clock is preferred, but the
KWIIP clock is not present. RSTS/E uses the KWIIL clock instead.
USING KWIIP CLOCK AT LINE FREQUENCY
Warning message only. The installed SIL's defaults indicate a KWIIL clock is preferred, but the
KWIIL clock is not present. RSTS/E uses the KWI1P clock instead.
VECTOR FOR DEVICE xx: (nnnn) ALREADY IN USE - DEVICE DISABLED
Use HARDWR to set the correct vector address for xx:, or call the DIGITAL field service
engineer.
VECTOR TABLE FULL
Submit an SPR.
WARNING - BAD BLOCK DOUBLY ALLOCATED TO BADB.SYS
Warning message only.
WARNING - BOOTED DEVICE IS AT A NON-STANDARD CSR ADDRESS
The initialization code successfully bootstrapped the device. The device is at a DIGITAL
non-standard CSR address, but the device has not been declared at the non-standard CSR
address. Before starting your RSTS/E monitor, use CSR (a HARDWR suboption) to declare this
device at the non-standard address.
WARNING - DCN IN BADB.SYS TOO BIG
Warning message only. The file structure on the disk being rebuilt appears invalid.
WARNING - DBn: IS DUAL PORTED
Warning message only.
WARNING - DCN IN BADB.SYS NOT ON PACK CLUSTER BOUNDARY
Warning message only.
WARNING - xxx FILE NOT FOUND - PLEASE SET DEFAULTS
The SIL you are installing specifies a primary run-time system or error message file that is not
present. Use the DEFAULT option to specify a valid file.
(continued on next page)

System Installation Error Messages

341

Table A-1:

Initialization Code Error Messages (Cont.)
Message and Recovery Procedure

WARNING - FILE filnam.typ NOT FOUND WHEN REMOVING OLD SIL
Warning message only.
WARNING - LINK IN BADB.SYS IS BAD. BAD BLOCKS MAY BE LOST.
Warning message only.
WARNING - MAIN MEMORY (cache) DISABLED AT STARTUP. RSTS/E WILL NOT USE (cache).
SYSTEM MAY RUN SLOWLY.
Warning message only. (cache) is CACHE, CACHE GROUP 0, or CACHE GROUP 1.
WARNING - MAIN MEMORY (cache) IS FAILING REPEATEDLY. RSTS/E WILL NOT USE
(cache). SYSTEM MAY RUN SLOWLY.
Warning message only. (cache) is CACHE, CACHE GROUP 0, or CACHE GROUP 1.
WARNING - NO SET UP FOR DEVICE xx
Submit an SPR. You may have either a corrupt distribution kit or incompatible versions of
INIT.SYS and the monitor .SIL.
WARNING - ODT IN THE SIL IS IN AN ILLEGAL FORMAT
Warning message only.
WARNING - SUBLINES FOR xx: ARE OUT OF SEQUENCE
Warning message only, but the system may crash. Regenerate the monitor.
XDn: DISABLED - LINE EXCEEDS CONTROLLER (XDn:) MAXIMUM
This is an informational message only. No action is necessary. With the XD controller, it is
possible to generate a monitor with DMPs and run the monitor on a system that has DMVs
instead of DMPs. While the DMV physically supports a maximum of 12 lines, any RSTS/E
system that was generated with DMPs could exceed this maximum. This error message tells you
that the limit was exceeded.

342

System Installation Error Messages

RT11 Run-Time System Error Messages
The RTII run-time system can generate the errors described in Tables A-2 and A-3.
Table A-2:

Recoverable RT11 Run-Time System Errors
Message and Meaning

?ADDR?
You specified an illegal address with an E, D, or B command.
?BAD LOAD?
RTll encountered an error when reading the program into memory.
?BAD PPN?
You typed an illegal PPN in response to a LIB or PPN command.
?BAD START ADDRESS?
The program start address was odd or out of bounds.
?FIL NOT FND?
The specified file cannot be found.
?FILE?
You specified no file name or an illegal file name with the R, RUN, or GET command.
?ILL CMD?
You typed an illegal command. The command includes an unrecognized command, a syntax
error in a command string, a command line longer than 510 characters, or an attempt to change
to an illegal size (2 <size> swap max for this job).
?ILL DEV?
The command string includes an illegal device name.
?NO RESTART?
You typed the RESTART command, but the program cannot be restarted.
?OVR CORE?
The program is too large to fit into memory.

System Installation Error Messages

343

Table A-3:

RT11 Run-Time System Fatal Execution Errors
Message and Meaning

?M-BPTTRAP
The program issued a BPT instruction, but the job has an illegal vector location.
?M-FP TRAP
A floating point trap occurred.
?M-HALT
The program halted.
?M-ILL EMT
The program issued an invalid monitor call.
?M-IOTTRAP
The program issued an lOT instruction, but the job has an illegal vector location.
?M-OVLY ERR
The RT11 run-time system encountered an error while reading a program overlay. This message
may indicate a hardware error.
?PROGRAM LOST - SORRY
An unrecoverable error occurred. The run-time system resets user core image.
?M-TOO MANY OPEN CHANNELS
The job attempted to open more than 15 channels or attempted to open two DECtape files at
once.
?M-TRAPTO 4
The program trapped to the vector at location 4.
?M-TRAP TO 10
The program trapped to the vector at location 10.
?M-TRAP TRAP
The job issued the TRAP instruction, but the job has an illegal vector location.

344

System Installation Error Messages

The RSTS/E system initialization code performs a hardware configuration check each
time the system disk (or distribution medium) is bootstrapped. In the absence of any
information to the contrary, the initialization code assumes that all devices attached to
the UNIBUS have been assigned addresses according to the manufacturing standards.
The initialization code determines interrupt vectors automatically by forcing each
supported device to interrupt. Although the HARDWR initialization· option allows you
to declare nonstandard address and vector assignments, DIGITAL recommends that
you follow the standard configuration rules whenever possible.
Several devices have floating addresses. This means that the pres'ence or absence of
any floating address device will affect the assignment of addresses to other floating
address devices. Similarly, many devices have floating vectors. According to the
standard, interrupt vectors must be assigned in a specific sequence and the presence
of one type of device will affect the correct assignment of interrupt vectors for other
devices. Finally, there are many options that have fixed addresses and vectors. This
appendix presents the algorithms for assignment of floating addresses and vectors. It
also lists the fixed assignments for devices supported by RSTS/E.

Floating Addresses
Currently the floating address devices include the devices listed in Table B-1. The
following ground rules apply to these devices and future floating address devices:
• Only new devices will be assigned floating addresses. Devices now in
production will keep their old addresses.
• Future devices may float both their address and interrupt vectors.
• The floating address space starts at 760010(8) and proceeds upward to
764000(8).
'
• A gap in the address space (no SLAVE SYNC) implies that a device does not
exist.

345

• The first address of a new device type will always be on a 2AN word boundary,
where N is the first integer greater than or equal to LOG2 M and M is the
number of device registers.

Number of
Registers
in Device

Possible Boundaries

Any Word·

3,4

XXXXXO,XXXXX4
XXXXXO

5,6,7,8
9 thru 16

XXXXOO, XXXX20, XXXX40,XXXX60
XXXXOO,XXXX40

o A "gap" of at least one word will be left after each type of device, starting on

the same boundary the device would start on. Note that the gap must be at
least one word in length but may be longer than one word. Gap length is
determined by the boundary on which the next must be addressed
contiguously.
Address 760010 is reserved for the first OJ11. Since the OJ11 has four registers,
additional OJ11s are assigned addresses modulo 10 (base 8) immediately following
the first OJ11 (for example, 760010, 760020, and so forth). The modulo 10 (base 8)
address following the last OJ11 is left empty arid is known as the OJ11 gap. If there
are no OJ11s, the gap is at 760010. If there is one OJ11, the gap will be at 760020.
All gaps must be at least one word in length.
.
After all OJ11 addresses and the OJ11 gap are defined, the address for the first
OH11 can be assigned. OH11s have eight registers,. which implies a modulo 20 (base
8) boundary. The address of the first OH11 is the first modulo 20 address following
the OJ11 gap. If there are no OJ11s (OJ11 gap at 760010), the first OH11 is
assigned address 760020. Similarly, if there is one OJ11, the OJ11 gap will begin at
760020 and the next available modulo 20 boundary is 760040. All additional OH11s
are assigned addresses modulo 20 immediately after the first OH11. The OH11 gap
begins on the 20 boundary following the last OH11.
After all OHl1 addresses and the OHl1 gap are defined, OQ11, OU11, OUP11,
LK11, OMC11, OZll, and KMC11 through OMV11-AO addresses and the required
gaps can be assigned in sequence by their rank. Addresses for any future floating
address devices will be assigned in a similar manner~

. Floating Address Worksheet
The algorithm for assignment of floating addresses is confuSing for a configuration
that consists of several types of floating address devices. The floating address
worksheet is a graphic aid that allows you to assign floating addresses to a device
quickly, without referring to the formal rules.
.

346

Address and Vector Assignments

The floating address worksheet consists of 33 columns. The first column contains the
floating addresses, from 760010 to 762000. The worksheet continues on for four
pages, to accommodate all of the addresses. Note that the last address on the
worksheet also appears as the first address of the worksheet on the following page.
For example, the last address of the first worksheet is 760400. The first address of the
worksheet on the next page is 760400. This allows you to carry over the information
from the previous page.
---------------------- Note -----------------------

The floating address area continues to address 764000. If your
configuration continues to this address, you can create an addition to
the worksheet by adding 2000 to the last address listed on the
worksheet, which is 762000.

Columns 2 through 33 contain the floating address device names. To the right of the
worksheet is a List of Devices. Here you can enter the number of devices in your
configuration. Below the List of Devices is a Record of Floating Addresses. Here you
can record the device, the unit number, and the floating address.
You can also produce the information contained in this worksheet by running the
FLOAT program. The FLOAT program is contained in the Unsupp system program
package (see Phase 4 in Part I).
To use the worksheet:

In the spaces prOVided in the List of Devices, record the quantity of each type
of floating address device in your configuration. For example, if you have two
DJ11 and two DH11 devices, enter 2 in the spaces provided adjacent to the
DJ11 and the DH11 in the List of Devices.

Begin at address 760010 of the worksheet under the DJ11 column and record
the unit number for all DJ11s in your configuration. Begin with unit 0 and end
with unit n-1, where n represents the number of DJ11s in your configuration.
For example, if you have two DJ11 devices, enter a device unit of 0 in the
unshaded box to the right of address 760010. Enter a device unit of 1 in the
unshaded box to the right of address 760020. Use only the unshaded boxes
when you enter the device unit number. The shaded boxes represent illegal
addresses for a particular device unit.
---------------------- Note -----------------------

Where you begin in the worksheet depends upon what devices
you have in your configuration. Suppose you have LPP11 and
DWR70 devices. In this case you would start at address 760130
under the first unshaded box under the LPP11 column.

Address and Vector Assignments

347

348

Immediately below the last device unit, mark an X for the required address
gap. For example, the last OJll unit in the previous example is at address
760020. You would mark an X in the unshaded box to the right of address
760030. Use only the unshaded boxes when you mark the address gap. The
shaded boxes also indicate an illegal address gap.

To the immediate right of the address gap, mark a Y. For example, you would
enter Y in the shaded box to the right of the X at address 760300. When you
mark a Y to the right of an address gap, use either the shaded or the unshaded
boxes, depending on which is to the right of the address gap. If there are no
units of a particular device type, enter an X to indicate the gap addresses; then
enter a Y to the right of this. For example, if you have no OJll devices, you
mark an X in the unshaded box to the right of address 760010. You would
then mark a Y to the right of this. The Y is a marker that tells you which
address to start at for the next device.

Continue below the Y in the previous column and enter the unit number of the
next device in your configuration. Start with unit 0 and continue to unit n-l.
(The first MSCP controller has a fixed address. This means you should fill in
floating addresses starting with controller 1, not controller 0.) Skip the shaded
boxes in numbering down the column. In the first unshaded box below the last
OHll unit, mark an X for the DHll gap. Then mark a Y to the right of the
address gap.

Continue with the remaining floating address devices. In each case, number the
units from 0 to n-l down the column, beginning in the first unshaded box
below the X. Mark an X in the next unshaded box below the last unit and a Y
in the box immediately to the right of the last unit.

After you complete the worksheet, you can record the device, the unit number,
and its associated floating address in the spaces provided in the Record of
Floating Addresses.

Address and Vector ASSignments

DEVICE

ADDRESS

~
1
1

D
H
1
1

D
Q
1
1

D
U
P
1
1

L
K
1
1

D
M
C
1
1

K
M
C
1
1

L
P
P
1
1

V
M
V
2
1

V
M
V
3
1

D
W
R
7
0

R
L
1
1

L
P
A
1
1

K
W
1
1

s
r

R
X
1
1

D
R
1
1
W

D
R
1
1
6

D
M
P
1
1

D
P
V
1
1

I
S
6
1
1

D U
M N
V A
1
1

D
M

K
M

® 3F S1
2

V
S
1 @
0
0

K
M
V@
1
1

760000
760004
760010
760014
760020
760024
760030
760034
760040
760044
760050

<D = DUll, DUVll

760054

760060

® = MSCP devices

760064

760070

@ = DHU11, DHVll

= DZll, DZVll, DZ011

= TMSCP devices

760074
760100
760104
760110

LIST OF DEVICES

760114
760120
760124

1ft

760130
760134
760140
760144
760150
760154
760160
760164

...:,..

760170
760174

OJl1
OH11
0011
DU11/DUV11
DUP11
LK11
DMCll
DZ11/DZV11/DZOll_

DRll-W_
DR11-B_
DMP11
DPVll
IS611
DMV11
UNA
MSCP

KMCll
LPP11
VMV21
VMV31 _
DWR70 _
RLll
KW11
RXll

DMF32
KMSll
VSloo
TMSCP
KMVll
_
DHUll/DHVll _

760200
760204
760210

760214

RECORD OF FLOATING ADDRESSES

760220
760224
760230

760240

760244
760250

760254
760260
760264

UNIT

ADDRESS

DEVICE

UNIT

ADDRESS

760234

DEVICE

760270
760274

760300

. :.:

760304

760310

760314

760320

',"

760324
760330

760334

,d:

760340

760344

...:..

.:.

t:<

760350

,;':

760354

~; .. ;

760360
760364

:',i,

l'-

>:,

760370

,'.'

760374

,;:: ,I' :

760400
D

J
1
1

D
H
1
1

D
Q
1
1

D
U

Figure B-1:

L
K

D
M

K
M

L
P

V
M

D
W

R
L

L
P

K
W

R
X

D
R

D
M

D
P

I
S

D
M

U
N

M M

V
S

K
M

<D P1 11 C1 ® C1 P1 V2 V3 R7 11 A1 11 vr 11 11 11 P1 V1 61 V1 A ® 3F S1 01 @V1 @
1

Floating Address Worksheet (Cont.)
Address and Vector AsSignments

349

DEVICE
D
ADDRESS
J

D
H

D
Q

1
1

D
U
P

CD 1

L
K

1
1

K
D
M
M
C@ C

L
P
P

V
M
V

V D
M W
V R

1
1

2
1

3
1

1
1

7
0

R
L

1
1

L
P
A

1
1

K
W
1
1

X
1
1

r
v
d

D
R

1
1
W

1
1
B

D
M
P

D
P
V

I
S
B

D
M
V

1
1

U
N
A

D
M
F

® 3

K
M
S
1
1

V
S

1
0
0

K
M

0v@
1
1

760400
760404
760410
760414
760420
760424
760430
760434

760440
760444
760450
760454
760460
760464
760470
760474
760500

<D = DUll, DUVll

760504

760514

® = DZll, DZVll, DZQll
® = MSCP devices

760520

@ = TMSCP devices

760524

® = DHUll, DHVll

760510

760530
760534
760540
760544

RECORD OF FLOATING ADDRESSES

760550
760554
DEVICE

UNIT

ADDRESS

DEVICE

UNIT

ADDRESS

760560
760564
760570
760574
760600
760604
760610
760614
760620
760624

760630
760634

760640
760644
760650
760654
760660
760664
.

760670
760674
760700
760704

760710
760714
760720
760724
760730

:.•

760734
760740
760744
760750
760754

..
.

760760
760764

I·

..:

760770
.

760774

761000
D
J

D
H

D
Q

1
1

D
U
P

CD 1
1

Figure B-1:

350

L
K
1
1

D
K
M
M
C@ C

L
P
P

V
M
V

V 0
M W
V R

1
1

2
1

3
1

1
1

7
0

R
L

1
1

L
P
A

1
1

K
W
1
1

X
1
1

r
v
d

D
R

1
1
W

1
1
B

D
M
P

D
P
V

I
S
B

D
M
V

1
1

Floating Address Worksheet (Cont.)

Address and Vector Assignments

U
N
A

D
M

® 3F
2

K
M
S

1
1

V
S

1
0
0

K
M

0 v@
1
1

DEVICE

ADDRESS

~
1
1

D
H
1
1

L
K

D
M

V D R
M W L

V
M

~<D P1 11 C1 ® C1 P1 V2 V3 R7 11
M

L
P
A
1
1

K R
W s

1
1

D
R
1
1

D
M
P
1
1

D
P

I
S

B V

D
M

1
1

U
N
A

D
M

V
S
1
0
0

M
S

® F

3
2

K
M

CD V@
1
1

761000
761004
761010
761014
761020
761024
761030
761034
761040
761044
761050
761054
761060
761064
761070
761074
761100
761104
761110

<D = DUll, DUV11

761114

761120

= DZll, DZVll, DZOll

® ~ MSCP devices

761124

CD = TMSCP devices

761130

@= DHUll, DHVll

761134
761140
761144
761150

RECORD OF FLOATING ADDRESSES

761154
761160
761164

DeVICE

UNIT

ADDRESS

DeVice

UNIT

ADDRess

761170
761174
761200
761204
761210

761214
761220
761224
•

761230
761234
761240
761244
761250 .
761254
761260
761264
761270
•

761274

761300
761304
761310
761314
761320
761324
761330
761334

761340
761344

761350

, I

761354
761361
761364

.1.

I.·

761370

761374
761400
D

J
1
1

D
H
1
1

D
U

L
K

D
M

CD P1 11 C1 ®
1
1

Figure B-1:

M
c
1
1

P
P
1
1

V
M
V

M
V

1
1

R
7
0

P
A
1
1

K R
W s
1
1

v
d

1
1

D
R
1
1

X R
1
1

D
M
P
1
1

D
P
V
1
1

I
S

D
M

B V
1
1

1
1

U
D
N
M
A@ F
3
2

K
M
S
1
1

V
S
1
0
0

K
M

CD V@
1
1

Floating Address Worksheet (Cont.)
Address and Vector Assignments

351

DEVICE

0
ADDRESS

J
1
1

D
H
1
1

D
Q
1
1

D
U
P
1
1

L
K
1
1

D
M
C @
1
1

M
C
1
1

P
P
1
1

V
M
V
2
1

V
M
V
3
1

W L

R
7
0

1
1

K R
W s

1
1

D
R
1
1

D
M
P
1
1

I
S

D
P
V
1
1

B
1
1

D
M
V
1
1

D
M

3
2

1
1

~'3' F S
~

V
S
1
0
0

0 v@
1
1

761400
761404

'.'

761410
761414

761420

761424

761430
,

761434
761440
761444
761450

761454

.".

761460
761464

761470

761474

,,',

CD = DUll, DUVll

761500

® = DZll, DZV11, DZQ11
® = MSCP devices

761504
761510
761514

761520

@= DHU11, DHVll

TMSCP devices

761524
761530
.

761534

RECORD OF FLOATING ADDRESSES

761540
761544

761550

DEVICE

UNIT

ADDRESS

DEVICE

UNIT

ADDRESS

761554
761560
761564

....

761570
761574
761600
761604

761610
761614

761620
761624
761630

,,'

761634
761640

761644

761650
761654
761660
761664

761670
,

761674
761700
761704
761710
761714
761720

761724
761730
761734
761740
,

761744

I"
.

761750

761754

761761

Ii
..

761764

....

' .

761770

.
,

761774

.....

762000
D

J
1
1

D
H
1
1

D
Q
1
1

Figure B-1:

352

D
U
P
1
1

L
K
1
1

D
M
C@
1
1

M
C
1
1

P
P
1
1

V
M
V
2
1

V
M
V
3
1

R
7
0

1
1

A
1
1

K
W

1
1

v
d

Floating Address Worksheet

Address and Vector Assignments

D
R
1
1

W B

D
M
P
1
1

D
P
V
1
1

I
S

B
1
1

D
M
V
1
1

D
M

~ 1=
113' F
3
2

K
M
S
1
1

V
S
1
0
0

K
M

0 v@
1
1

MK-01604-00

Floating Vectors
Many devices have floating vectors. The vector assignment sequence is normally the
same sequence as that in which the devices enter production. A vector for a new
hardware option is not inserted before the vector for a device that is already in
production. Gaps in the vector assignments are not required. The floating vectors
begin at address 300 and proceed continuously upwards.
Table B-1 lists the vector assignment sequence for current devices.
Table B-1:

Device Vector Assignments
First
Address

Next
Addr.

Vector
Size

Max#
Units

BR
Level

OC11

174000

+10

BR5

Not supported

OL11A,B

176500

+10

BR4

Non-console

OP11

174770

-10

BR5**

2780 only

OM11A

175000

+10

BR5

Not supported

ON11

175200

+10

BR5

Not supported

OM11BB

170500

+10

BR4

OH11 modem control

OR11A,C

167770

-10

10*

BR5

Not supported

PA611 Reader

172600

BR4

Not supported

PA611 Punch

172700

BR4

Not supported

Device

LP011

RSTS/E Notes

Not supported

OT11
(OT03_FP)

174200

10*

BR7

Not supported

OX11

176200

+40

10*

BR4

Not supported

OL11C,O,E

175610

+10

10*

BR4

OJ11

FLOAT

+10

10*

BR5

OH11

FLOAT

+20

10*

BR5

GT40

172000

VSV11

172000

+10

LPS11

170400

+40

30*

BR5,6

Not supported

OQ11

FLOAT

+10

10*

BR5

Not supported

KW11W

172400

10*

DUll

FLOAT

+10

10*

BR5**

2780 only

OUP11

FLOAT

+10

10*

BR5**

2780, HP2780,3271

OV11

175000

+40

20*

BR5,6

Not supported

BR5

20*

Not supported
Not supported

Not supported

(continued on next page)

Address and Vector Assignments

353

Table B-1:

Device Vector Assignments (Cont.)
First
Address

Next
Addr.

Vector
Size

Max#
Units

BR
Level

LK11

FLOAT

+10

10*

BR4

DMC11

FLOAT

+10

10*

BR5

DMR11

FLOAT

+10

BR5

DZ11

FLOAT

+10

10*

BR5

DZV110r
DZQ11

FLOAT

+10

10*

BR5

KMC11

FLOAT

+10

10*

BR5

LPP11

FLOAT

+10

Not supported

VMV21

FLOAT

+10

Not supported

VMV31

FLOAT

+20

Not supported

VTV01

172600

DWR70

FLOAT

+10

RL11

FLOAT

+10

TS11

172520

LPA11-K

170460

IP11

171000

KW11-C

FLOAT

+10

RX11, RX211,
RXV11

FLOAT

+10

DR11-W

FLOAT

+10

Not supported

DR11-B

FLOAT

+10

Not supported

DMP11

FLOAT

+10

DPV11

FLOAT

+10

ML11

176400

ISB11

FLOAT

+10

DMV11

FLOAT

+20

BR5

DHV111DHUll

FLOAT

+20

BR5

Device

RSTS/E Notes
Not supported

Not supported
Not supported
BR5

Not supported after
1st

BR5

Not supported
Not supported

BR5

After 1st only

BR5

DECnetiE only

BR5

Not supported

Not supported
Not supported
DECnetiE only

* The first vector for the first device of this type must always be on a 10(8) boundary.
** Also supported at BR6 under RSTS/2780.

354

Address and Vector Assignments

Fixed Addresses and Vectors
Table B-2 lists the devices supported under RSTS/E that have fixed addresses and
vectors.
Table B-2:

Device with Fixed Addresses and Vectors

Device

Address

Vector

BR Level

MSCP

1721S0

BRS

1st controller only

TMSCP

774S00

BRS

1st unit only

RFll

177460

204

BRS

Not supported

RS03/RS04

172040

204

BRS

Not supported

RKOS/RKOSF**

177400

220

BRS

Up to 8 drives

RLOllRL02

174400

160

BRS

Up to 4 drives

RK06/RK07

177440

210

BRS

Up to 8 drives

RP02/RP03

176710

2S4

BRS

Up to 8 drives

Second RHl1170
RM02/RM03/RMOS/RM80
RP04/RPOS/RP06

176300

ISO

BRS

Up to 8 drives

First RHl1170
RP04/RPOS/RP06
RM02/RM03/RMOS/RM80

176700

2S4

BRS

Up to 8 drives

RXOllRX02

177170

264

BRS

First only

DECtape

177340

214

BR6

Up to 8 drives

TUI0ITEI0ITS03ITSll

172S20

224

BRS

First TS 11 drive only

TU16ITE16ITU4SITU77t

172440

224

BRS

Up to 8 drives

LPll

(LPO)

177S14

200

BR4

(LPl)

164004

170

BR4

(LP2)

164014

174

BR4

(LP3)

164024

270

BR4

(LP4)

164034

274

BR4

(LPS)

164044

774

BR4

(LP6)

1640S4

770

BR4

(LP7)

164064

764

BR4

RSTS/E Notes

* These controllers have programmable vectors; INIT.SYS finds an available vector address
and assigns it to them.
** Each RKOSF must be counted as two drives.

t Maximum of 4 TU7T s
(continued on next page)

Address and Vector Assignments

355

Table B-2:

Oevicec with Fixed Addresses and Vectors (Cont.)
Address

Vector

BR Level

CR11,CM11

177160

230

BR5

COlI

177160

230

BR4

KW11L

177546

100

BR6

KW11P

172540

104

BR6

KG11

170700

NONE

2780 only

DL11A,DL11B

177560

BR4

Console interface

XHO

774440

BR5

Not supported

XH1

774460

BR5

Not supported

XEO

774510

120

Device

DEQNA

DEUNA

RSTS/E Notes

* These controllers have programmable vectors; INIT.SYS finds an available vector address
and assigns it to them.

** Each RKOSF must be counted as two drives.
t Maximum of 4 TU77' s

RH70 BAE and eS3 Addresses
Table B-3 lists the four possible RH70 High Speed I/O Controller addresses, their Bus
Address Extension (BAE) and Control addresses, their BAE Control Status 3 (CS3)
addresses, and their uses.
Table B-3:

356

RH70 BAE and CS3 Addresses
Device

Address

BAE

CS3

RS03/RS04 (Not supported)

172040

172070

172072

TU16ITE16ITU45ITU77

172440

172474

172476

Mixed/nonstandard

176300

176350

176352

RP04/RP05/RP06 or
RM02/RM03/RM05/RM80

176700

176750

176752

Address and Vector Assignments

This appendix shows a directory listing of the RSTS/E system programs. The directory
listing for your installation may differ, depending on the packages you selected.

Account [0,1]
Name .Typ
BADB .SYS
ERR
.ERR
DCL
.RTS
BACKUP.TSK
SWAP .SYS
ODT
.SYS
INSTAL .COM
COPYUP.COM
CSPHLP.COM
LISTER .COM
MONITR.COM
ASSLOG.COM
INSPKG .COM
DECNT2.COM
DELLOG.COM
RECOVR.COM
LP
.HLP
CSPRES .COM
CSP
.COM
BEGIN .COM
RSTS90 .SIL
LOGIN .COM
CRASH .SYS

Size
Prot
5 P < 63>
16CP < 40>
132C <232>
102
<124>
128CP < 63>
14
< 60>
3C <104>
2C <104>
9C <104>
3C <104>
16C <104>
l!5C <104>
11C <104>
7C <104>
4C <104>
7C <104>
2C <104>
18C <104>
25C <104>
16C <104>
632CPL< 60>
4
< 40>
380CP < 63>

Name .Typ
SATT
.SYS
SYSGEN .SIL
RSX
.RTS
INIT
.SYS
RT11
.RTS
CSPLIB .LIB
UPDATE .COM
MAIN
.COM
LPRES .COM
CHECK .COM
CSPLNG .COM
MONBLD.COM
DECNT1.COM
FLAG
.COM
SYSINI .COM
CSP
.HLP
CSPLST .DAT
LP
.COM
SETPAS .COM
SWAP 1 .SYS
START .COM
BASIC .RTS

Prot
Size
14CP < 63>
636C < 60>
6CP < 60>
558CP < 60>
20C < 60>
41C < 60>
3C <104>
12C <104>
10C <104>
3C <104>
21C <104>
8C <104>
14C <104>
3C <104>
6C <104>
2C <104>
1C <104>
17C <104>
1C <104>
4992CPL < 60>
14C <104>
73C < 60>

SYO:[O,l]

Total of 8007 blocks in 45 files in SYO: [0, 1]

357

Help Package
Name .Typ
HELP
.TSK
BPHELP .HLP
BPSTAT .HLP
BPCHLP .HLP
FILNAM .HLP
KEYBRD .HLP
PIPHLP .HLP
PLEASE .HLP
PLEBAT .HLP
PLESPL .HLP
RSTS
.HLP
MAGTAP .HLP
RSX
.HLP
SETHLP .HLP
TECO
.HLP
TECOMD.HLP
UTHELP .HLP
DIRECT .HLP
COpy
.HLP
FIT
.HLP
DCALLO.HLP
DCASSI .HLP
DCATTA .HLP
DCBASI .HLP
DCBYE .HLP
DCCLOS.HLP
DCCREA.HLP
DCDEAS .HLP
DCDELE .HLP
DCDIBO .HLP
DCDIRE .HLP
DCDUMP.HLP
DCEOD .HLP
DCEXPR .HLP
DCFORT .HLP
DCGOTO.HLP
DCHELP .HLP
DCINIT .HLP
DCINST .HLP
DCLC81 .HLP
DCLSRT .HLP
DCLOAD.HLP
DCLOGO.HLP
DCMACR.HLP
DCON
.HLP
DCOPER .HLP
DCREAD.HLP
DCRENA.HLP
DCREST .HLP
DCSET .HLP
DCSTAR .HLP
DCSUBM.HLP
DCTYPE .HLP
DCWRIT .HLP

Size
29C
1
26
3
12
5
29
5
4
5
17
8
3
19
4
11
16
4
3
9
2
4
1
2
2
3
5
3
8
2
2
1
1
3
5
1
2
7
7
1
1
4
2
2
3
7
2
2
4
35
4
2
3
2

Prot
<104>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

Name .Typ
HELP
.HLP
BPCOMM.HLP
BPFUNC .HLP
DIRHLP .HLP
FITHLP .HLP
CTRLT .HLP
PIPDIR .HLP
PLEBAC .HLP
PLEQUE .HLP
QUEHLP .HLP
DISK
.HLP
TERMNL .HLP
RT11
.HLP
SYSHLP .HLP
TECOFL .HLP
TYPE
.HLP
VfEDIT .HLP
ERRDIS .HLP
BPCREF .HLP
DCL
.HLP
DCAPPE .HLP
DCAT
.HLP
DCBACK .HLP
DCBROA .HLP
DCCCL .HLP
DCCOPY .HLP
DCDEAL .HLP
DCDEFI .HLP
DCDETA .HLP
DCDIFF .HLP
DCDISM .HLP
DCEDIT .HLP
DCEXIT .HLP
DCFORC .HLP
DCFUNC .HLP
DCHANG .HLP
DCIF
.HLP
DCINQU .HLP
DCLABE .HLP
DCLMRG.HLP
DCLINK .HLP
DCLOGI .HLP
DCMAIL .HLP
DCMOUN.HLP
DCOPEN .HLP
DCPRIN .HLP
DCREMO .HLP
DCREQU .HLP
DCRUN .HLP
DCSHOW.HLP
DCSTOP .HLP
DCSYMB .HLP
DCUNLO.HLP
MAIL
.HLP

Total of 642 blocks in 108 files in SYO:[0,2]

358

RSTS/E System Files

Size
16
12
21
4
10
6
2
5
3
6
9
3
13
22
4
3
3
6
7
5
2
2
4
2
2
3
1
2
1
2
3
2
1
2
25
1
1
2
2
1
4
2
2
3
5
3
6
1
1
23
5
12
4
2

Prot
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

SYO:[0,2]

Error Reporting Package
Name .Typ
ERRDAT .FIL
ERRCPY .TSK
ERRDET .TSK
ANALY1 .TSK
ANALY3 .TSK

Size
95C
14C
4OC
52C
44C

Prot
< 60>
<124>
<124>
<124>
<124>

Name .Typ
ERRINT .TSK
ERRDIS .TSK
ANALYS .TSK
ANALY2 .TSK
ERRLOG .FIL

Size
18C
39C
47C
46C
2

Prot
<124>
<124>
<124>
<124>
< 60>

SYO:[0,2]

Size
2OC
11C
2OC
28C
16C
19C

Prot
<124>
<124>
<124>
<124>
<124>
<124>

SYO:[0,5]

Size
298C
2

Prot
<232>
< 40>

SYO:[0,6]

Size
12
54C
56C
44C
46C
40C

. Prot
< 60>
<232>
<232>
<232>
<232>'
<232>

SYO:[0,7]

Total of 397 blocks in 10 files in SYO:[0,3]

Device Testing Package
Name .Typ
DSKSEK .TSK
LPEXER .TSK
PREXER .TSK
DTEXER .TSK
CPUTST .TSK
MTEXER .TSK

Size
16C
14C
12C
19C
28C
25C

Prot
<124>
<124>
<124>
<124>
<124>
<124>

Name .Typ
DSKEXR .TSK
PPEXER .TSK
DXEXER .TSK
CPEXER .TSK
KBEXER .TSK
DDEXER .TSK

Total of 228 blocks in 12 files in SYO:[0,5]

Print/Batch Services Package
Name .Typ
PBS
.TSK
PBS ERR .ERR
PBS
.SYS

Size
97C
57
32

Prot
<232>
< 40>
<188>

Name .Typ
PBSMGR .TSK
FORMS .SYS

Total of 486 blocks in 5 files in SYO:[0,6]

File Restore Package
Name .Typ
BACKUP .PRM
RESTOR .TSK
BACCON.TSK
BACMNT .TSK
BACDSK. TSK
BACLOD .TSK
BACFRM .TSK

Size
5
SOC
29C
6OC
36C
SIC
SIC

Prot
< 60>
<232>
<232>
<232>
<232>
<232>
<232>

Name .Typ
BACKUP .HLP
BACLST .TSK
BACDIR .TSK
BACLAB .TSK
BACCOM.TSK
BACENT .TSK

Total of 534 blocks in 13 files in SYO:[0,7]

RSTS/E System Files

359

OPSER-based Spooling Package
Name .Typ
CHARS .QUE
QUEMAN.TSK
OPSER .TSK
SPOOL .TSK
SPLRUN .TSK
BATIDL .TSK
BATRUN .TSK

Size
2
32C
24C
54C
59C
50C
55C

Prot
< 60>
<232>
<232>
<232>
<232>
<232>
<232>

Name .Typ
BATCH .DCD
QUMRUN.TSK
OPSRUN .TSK
SPLIDL .TSK
BATCH .TSK
BATDEC .TSK

Size
12C
61C
59C
61C
52C
62C

Prot
< 60>
<232>
<232>
<232>
<232>
<232>

SYO:[O,8]

Size
26
63
105C
6
14
20
46
102
46
22C
21C
37C
43C
43C
22C
72C
2
6
5
11
26
11
22
5
8
17C

Prot
< 40>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
<124>
<124>
<124>
<124>
<124>
<124>
<104>
< 40>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
<104>

SYO:[O,9]

Total of 583 blocks in 13 files in SYO:[O,8]

Unsupported Utility Package
Name .Typ
DSKPEK .MAC
QSTATS .DOC
RSTSFL .OBJ
RSTSFL .DOC
MONEY .BAS
FLOAT .BAS
BPDA
.BAS
DIALER .BAS
STATUS .B2S
LQSTAT .BAS
MEMORY.TSK
DSKDMP .TSK
CONNEC.TSK
EMTCPY .TSK
QSTATS .TSK
B2CREF .TSK
B2CREF .HLP
.RNO
RNO
RNOBLD.ODL
COMND .MAC
ERMSG .MAC
HYPHEN .MAC
PINDX .MAC
RNFIO .MAC
RUNOFF .MAC
DUMP
.SAV

Size
4
32
42
2
51
19
59
85
69
19
12C
18C
28C
37C
23C
113C
12
. 85
2
7
10
54
9
9
71
10C

Prot
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
<124>
<124>
<124>
<124>
<124>
<104>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
<104>

Name .Typ
DSKDMP .HLP
DIALER .DOC
RSTSFL .OLB
RSTSFL .HLP
MEMORY.BAS
DSKDMP .BAS
CONNEC .BAS
EMTCPY.BAS
QSTATS .B2S
MONEY .TSK
FLOAT .TSK
BPDA
.TSK
DIALER .TSK
STATUS .TSK
LQSTAT .TSK
RNO
.TSK
B2CREF .DOC
RNOBLD .CMD
RNPRE .MAC
CMTAB .MAC
FMTCM .MAC
INDEX
.MAC
RNCMD .MAC
RNORSX .MAC
START .MAC
SRCCOM .SAV

Total of 1683 blocks in 52 files in SYO:[O,9]

360

RSTS/E System Files

RMS-ll Package
Name .Typ
RMSBCK .TSK
RMSDEF .TSK
RMSCNV.TSK
RMSIFL .TSK
RMSLBA .LIB
RMSLBC .LIB
RMSLBE .LIB
DAPRES .LIB

Size
95C
79C
82C
88C
17C
9C
13C
41C

Prot
<104>
<104>
<104>
<104>
< 42>
< 42>
< 42>
< 42>

Name .Typ
RMSRST .TSK
RMSDSP .TSK
RMSDES .TSK
RMSRES .LIB
RMSLBB .LIB
RMSLBD .LIB
RMSLBF .LIB

Size
113C
79C
116C
17C
13C
9C
17C

Prot
<232>
<104>
<104>
< 42>
< 42>
< 42>
< 42>

SYO:[O,10]

Size
3
39
49C

Prot
< 60>
< 60>
<104>

SYO:[O,II]

Prot
< 60>
< 60>
<104>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 40>
< 60>
<124>
<104>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>

SYO:[O,12]

Total of 788 blocks in 15 files in SYO:[O,10]

EDT Package
Name
EDT52
EDT200
EDT

.Typ
.DOC
.DOC
.LIB

Size
3
4
162C

Prot
< 60>
< 60>
< 42>

Name
EDTI00
EDTKIT
EDT

.Typ
.DOC
.DOC
.TSK

Total of 260 blocks in 6 files in SYO:[O,II]

SYSGEN Components and BASIC-PLUS Package
Name .Typ
MONITR .CMD
RJ2780 .CMD
RSXRTS .CMD
CHECK .MAC
KBDEF .MAC
TTDVR .MAC
CRA
.OBJ
DSK
.OBJ
BBR
.OBJ
XVR
.OBJ
EMT
.OBJ
GEN
.OBJ
FIPLRG .OBJ
OVRLRG .OBJ
DEFALT .SAV
SYSGEN .SAV
.TSK
EDT
BPLGEN .SAV
MA2
.OBJ
MA2F
.OBJ
MA4F
.OBJ
XL2
.OBJ
XL2F
.OBJ
XL4F
.OBJ
XT21
.OBJ
XT4
.OBJ
.OBJ
SF
PU
.OBJ
SN
.OBJ
VE
.OBJ

Size
3
21
1
19
19
407
7
5
2
2
3
3
4
4
3C
140C
237C
60C
18
16
18
3
2
2
3
4
6
6
3
2

Prot
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
<124>
<124>
<104>
<124>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>

Name .Typ
DECNTD .CMD
BASIC
.CMD
HOOK
.SAV
TBL
.MAC
TTDINT .MAC
RSTS
.OBJ
TER
.OBJ
MCP
.OBJ
OPN
.OBJ
MVR
.OBJ
EM2
.OBJ
RSX
.OBJ
FMS
.OBJ
OVLHD .OBJ
DEFALT .STB
BUFCHK .TSK
BASIC
.COM
RTS
.OBJ
MA21
.OBJ
MA4
.OBJ
MA40
.OBJ
XL21
.OBJ
XL4
.OBJ
XT2
.OBJ
XT2F
.OBJ
XT4F
.OBJ
10
.OBJ
MX
.OBJ
OBG
.OBJ

Size
1
1
28C
107
34
654

5
3
3
3
3
2
3
1
1
21C
lC
93
16
22
16
3
4
3
2
2
6
9
2

Total of 2072 blocks in 59 files in SYO:[O,12]

RSTS/E System Files

361

TECO Package
Name .Typ
TECO
.RTS
TYPE
.TEC
TECO
.HLP
TECOFL .HLP
VTEDKP .HLP
TECORN .DOC
TECKBM .TEC
SEARCH .TEC
.TES
TECO
VTEDIT .TES
TECKBM .TES
SEARCH .TES
TECOLB .OBJ
SCREEN .OBJ
SCROLL .OBJ
CRTRUB.MAC

Size
48C
7C
4
4
6
108
3C
5C
28C
34C
3C
9C
68
13
4
65

Prot
< 60>
<104>
< 60>
< 60>
< 40>
< 40>
<104>
<104>
<104>
<104>
<104>
<104>
< 60>
< 60>
< 60>
< 60>

Name .Typ
TECO
.TEC
VTEDIT .TEC
TECOMD .HLP
VTEDIT .HLP
VTEDIT .OOC
TECO
.INI
LOCAL .TEC
SQU
.TEC
TYPE
.TES
TECOIN .TES
LOCAL .TES
SQU
.TES
GEXIT
.OBJ
SCRINS .OBJ
CRTRUB .OBJ

Size
10C
24C
11
3
118
8
3C
10C
17C
18
3C
15C
3
4
8

Prot
<104>
<104>
< 60>
< 60>
< 40>
< 40>
<104>
<104>
<104>
< 40>
<104>
<104>
< 60>
< 60>
< 60>

SYO:[0,13]

Size
27C
11C
61C
40C
24C
58C
56

Prot
<104>
<232>
<232>
<104>
<104>
<104>
< 60>

SYO:[0,14]

Size
11
10
5
11
9
16
5
194
81
33
31
3
5
370C

Prot
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
<104>

SYO:[0,15]

Total of 664 blocks in 31 files in SYO:[0,13]

Auxiliary Library Package
Name .Typ
REORDR.TSK
COPY
.TSK
GRIPE .TSK
FIT
.TSK
PMDUMP.TSK
BPCRF1 .TSK
DSKCVT .TSK

Size
74C
25C
16C
60C
47C
49C
57C

Prot
<232>
<104>
<232>
<232>
<104>
<104>
<232>

Name .Typ
ODT
.TSK
TALK
.TSK
DISPLY .TSK
FLINT
.TSK
BPCREF .TSK
RUNOFF .TSK
RUNOFF .RNO

Total of 605 blocks in 14 files in SYO;[0,14]

SORT/MERGE Package
Name .Typ
SRTLIB .OLB
MGELIB .OLB
SRTMRG .001
SRTMRG .004
SRTREC .ODL
MGEREC.ODL
SRTMRG .006
SRTSHR .OLB
SRTMRG .008
SRTMGE .MST
SRTMRG .010
SRTMRG .012
SORT
.COM
SRTUTL .TSK
SRTTRN .TSK

Size
209
189
2
179
10
9
15
214
10
81
48
26
10
388C
103

Prot
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
<104>
<104>

Name .Typ
SRTUTL .ODL
MGEUTL .OOL
SRTMRG .003
SRTFIL .. ODL
MGEFIL .OOL
SRTMRG .005
SRTMRG .007
MGESHR .OLB
SRTTST .DAT
SRTMRG .009
SRTMRG .011
SRTMRG .013
SRTMRG .002
MGEUTL .TSK

Total of 2277 blocks in 29 files in SYO:[0,15]

362

RSTS/E System Files

RSX Utilities Package
Name .Typ
SYSLIB .OLB
BP2
.LNK
OIBOL .LNK
.LNK
F77
RMSMAC.MLB
RMS11 .OOL
RMS11S .OOL
RMS11X .OOL
RMSRLX .OOL
OAPRLX .OOL
RMSRES .STB
OAPRES .STB
OOTIO .OBJ

Size
250
2
3
3
185
83
3
5
2
2
4
3
13

Prot
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

Name .Typ
RSXMAC .SML
C81
.LNK
OMS
.LNK
RSX11
.LNK
RMSLIB .OLB
RORMS1 .MAC
RMS12S .OOL
RMS12X .OOL
OAP11X .OOL
RMSRES .TSK
OAPRES .TSK
OOT
.OBJ
EOTHEL .HLP

Size
264
1
1
2
271
12
3
4
5
19
43
8
223

Prot
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

SYO:[l,l]

Size
64C
124C
289C
55C
8C
22C
68C
133
0
1
6
20C
53C
13C
46
131C
29
52C
189C
65C
47C
58C
23C
26C
0
14

Prot
<232>
<124>
<232>
<232>
<104>
<104>
<104>
< 60>
<60>
< 60>
< 40>
<232>
<232>
<232>
< 40>
<232>
< 40>
<104>
<104>
<104>
<104>
<124>
<124>
<124>
< 60>
< 60>

SYO:[1,2]

Total of 1414 blocks in 26 files in SYO:[l,l]

System Library Package
Name .Typ
INSTAL .LOG
UTLMGR .TSK
ONLCLN .TSK
SILUS
.SAV
MACRO .SAV
LINK
.SAV
ERR
.STB
COMMON. MAC
OCLUTL .TSK
CONFIG .MAC
SYSGEN .COM
LOGIN
.TSK
OIRECT .TSK
FILCOM .TSK
SWITCH .TSK
SAVRES .SAV
UTILITY .TSK
PAT
.SAV
TKB
.TSK
MAC
.TSK
PAT
.TSK
PRELIN .TSK
ATPK
.TSK
CPATCH .. TSK
QUE
:TSK
BPLGEN .COM

Size
31
231C
109C
41C
60C
57C
3
41
24C
7
9
37C
52C
48C
10C
206C
48C
11C
191C
103C
SSC
43C
29C
24C
56C
3

Prot
< 60>
<232>
<232>
<104>
<104>
<104>
< 40>
< 40>
<232>
< 60>
< 60>
<232>
<232>
<104>
<232>
<124>
<124>
<104>
<104>
<104>
<104>
<232>
<252>
<124>
<232>
<: 60>

Name ·.Typ
SHUTUP .TSK
OKSINT .TSK
ACTMGR .TSK
.SAV
PIP
CREF
.SAV
.SAV
LIBR
ONLPAT .SAV
KERNEL .MAC
TST090 .SYS
GLOBAL .COM
SYSLIB .OBJ
LOGOUT .TSK
SYSTAT .TSK
PLEASE .TSK
SYSMAC .SML
TERMGR .TSK
PIPSAV .TXT
MAKSIL .TSK
.TSK
STK
.TSK
LBR
.TSK
CRF
BUILD
.TSK
PBUILO .TSK
AUTO EO .TSK
QUIT
START .LOG

Total of 3065 blocks in 52 files in SYO:[1,2]

RSTS/E System Files

363

The distribution medium is the tape or disk on which DIGITAL supplies the RSTS/E
system. To bootstrap the distribution medium, use the switches on the Central
Processing Unit (CPU) or type a command to the console emulator to activate a
hardware loader that contains machine instructions for reading the first record of the
distribution medium into memory. This record, called a bootstrap record, is a program that loads additional program code from the distribution medium into memory
and executes that code. The code then prints a message on the console terminal,
marking the successful completion of the bootstrap procedure. For example:
Enablin~

only consolet disKst and tapes.

RSTS V8.0 (MTO) INIT V8.0-1Q
Current date: <DD-MMM-YY>?
Current tiMe: <HH:MM AM/PM>?
Installing RSTS on a new SYsteM disK? <Yes>

For the bootstrap operation to succeed, the distribution medium must be on line and
ready; the medium accessed must contain a proper bootstrap record; the console
terminal must be on line. The following two sections describe the bootstrap procedures for each of the distribution media. The section, Hardware Bootstrap Procedures, details hardware bootstrap procedures.

365

Bootstrapping Magnetic Tape Distribution
I

The operation of the magnetic tape devices is described in the RSTS/E System User's
Guide. To bootstrap the magnetic tape, do the following:

Physically mount the system installation tape on unit 0 with the write enable
ring removed.
.
- - - - - - - - - - - Note

The 9-track, 800 bpi magnetic tape bootstrap in the system
initialization code will not use a TU16, TE16, TU45, or TU77 tape
drive if a TU10, TE10, or T503 drive is present. Therefore, if your
system includes drives of both types (TU10rrE10rrS03 and
TU16rrE16rrU45rrU77), bootstrap the 800 bpi distribution tape on
the TU10, TE10, or TS03 drive. Similarly, the 1600 bpi magnetic tape
bootstrap will not use a TU16, TE16, TU45, or TU77 tape drive if a
tape is mounted and on line on a TS 11 drive.

Make sure that the tape is at its load point. (The BOT indicator light comes
on.) The computer does not bootstrap the device unless the tape is at its load
point.

Set the ONLINE/OFFLINE switch on the tape unit to ONLINE and make sure
that the ROY indicator is lit.

Make sure that the console terminal is on line.

Follow the bootstrap instructions in the section, Hardware Bootstrap
Procedures, for the type of hardware bootstrap device that is on the system.

Bootstrapping Disk Distribution
To bootstrap the disk cartridge, proceed as follows:

366

Insert the disk cartridge in a free unit.

Make sure that the RDY light is on.

Make sure that the WR PROT light is on.

Make sure that the console terminal is on line.

Follow the instructions in the section, Hardware Bootstrap Procedures, for the
type of hardware bootstrap device that is on the system.

Bootstrapping the Distribution Medium

Hardware Bootstrap Procedures
Bootstrapping a device involves using the Central Processor Unit (CPU) console
switches or typing a command to the console emulator to access and activate a
hardware loader. The hardware loader contains machine instructions for reading a
bootstrap record from the device. The bootstrap record is transferred into memory
and executes a specially designed software program. For the bootstrap operation to
succeed, the device accessed must be on line and ready; the medium accessed must
contain a proper bootstrap record; and the console terminal must be on line.
The PDP-II console switches and their use are described in the various processor
handbooks. The bootstrap procedure that you should use depends upon the type of
hardware bootstrap device on the system.
Table 0-1 summarizes the addresses needed to bootstrap each device. The detailed
procedures to bootstrap a device are presented according to the types of hardware
bootstrap devices available.

Bootstrapping the Distribution Medium

367

Table 0-1:

Summary of Hardware Bootstrap Addresses
Bootstrap Type

Device to Bootstrap

BM873·YA BM873·YB* MRll·DB BM792-YB M9301·YA M9301·YB M9301·YC M9301·YF M9312

RKOS disk cartridge
unit 0

773010

773030

773110

777406

RP02 or RP03 disk
pack unit 0

773100

7733S0

773154

776716

DKn

30+n

DKn

RP04,RPOS, RP06,
RM02, RM03, RMOS, or
RM80 disk pack unit
o at 176700 CSR

773320

RKOS disk (unit n)

773032

DKn

RLOllRL02 disk (unit n)

DLn

RK06 disk (unit n)

DMn

RK07 disk (unit n)

DMn

RP02 or RP03 disk
pack (unit n)

7733S2

RP04,RPOS, RP06,
RM02,RM03,RMOS,or
RM80 disk (unit n)
at 176700 CSR

773322

TUlOffElO and TS03
magnetic tape
TUlI6ffE16ffU4SffU77
magnetic tape

DMn

7730S0

773110

DPn

773136

7731S0

DPn

40+n

DPn

DBn

70+n

DBn

MTn

MMn

TS 11ffSVOSffK2SffU80
magnetic tape

MSn

MSCP devices***
at 172150 CSR

DUn

* To bootstrap a nonzero disk unit, set the address in the Switch Register, press the LOAD ADRS switch, set the unit number in the Switch
Register, and press the START switch.
** To bootstrap a TUlOffElO or TS03 magnetic tape, use the loading routine described in the section, Load Program Bootstrap for the TUlO,
TElO, OR TS03.
*** MSCP devices include the RA60, RA80, RA81, RC2S, RXSO, RDSI and RDS2 disk drives.

368

Bootstrapping the Distribution Medium

BM873-YA Procedure
If the BM873-YA Restart/Loader is on the system, perform the following steps:
1.

Move the CPU Console ENABLE/HALT switch to its HALT position and back
to its ENABLE position.

Set the CPU Switch Register to one of the following values:
773010 for RKOS disk cartridge
773100 for RP02 or RP03 disk pack
7730S0 for TU10ITE10ITS03 magnetic tape

Press the CPU LOAD ADRS switch.

Press the CPU START switch.

BM873-YB Procedure
If the BM873-YB Restart/Loader is on the system, perform the following steps:
1.

Move the CPU Console ENABLE/HALT switch to its HALT position and back
to its ENABLE position.

Set the CPU Switch Register to one of the following values:
773030 for RKOS disk cartridge
7733S0 for RP02 or RP03 disk pack
773320 for RP04, RPOS, RP06, RM02, RM03, RMOS, or RM80 disk pack
773032 for RKOS disk unit specified in the Switch Register
773352 for RP02 or RP03 disk unit specified in the Switch Register
773322 for RP04, RPOS, RP06, RM02, RM03; RMOS, or RM80 disk unit
specified in Switch Register
773110 for TU10ITE10ITS03 magnetic tape
773150 for TU16ITE16ITU45ITU77 magnetic tape

Press the CPU LOAD ADRS switch.

If necessary, set the CPU Switch Register to the unit number of the disk drive
being bootstrapped.

Press the CPU START switch.

Bootstrapping the Distribution Medium

369

H324 PushbuHon Panel Procedure
If the system includes the H324 Pushbutton Panel option for the BM873
Restart/Loader, perform the following steps:

Move the CPU Console ENABLE/HALT switch to its HALT position and back
to its ENABLE position.

'While holding down the UNLOCK switch, press the appropriate switch to
bootstrap the desired device. The DIGITAL Field Service engineer who
installed the computer should have informed you of the device that each switch
bootstraps.

Press the CPU START switch.

MR11-0B Procedure
If the MR11-DB Bulk Storage Loader is on the system, perform the following steps:

Move the CPU Console ENABLE/HALT switch to its HALT position and back
to its ENABLE position.

Set the CPU Switch Register to one of the following values:
773110 for RK05 disk cartridge
773154 for RP03 disk pack
773136 for TU10ITE10ITS03 magnetic tape

Press the CPU LOAD ADRS switch.

Press the CPU START switch.

BM792-YB Procedure
If the BM792-YB Hardware Loader is on the system, perform the following steps:

Move the CPU Console ENABLE/HALT switch to· its HALT position and back
to its ENABLE position.

Set the CPU Switch Register to 773100.

Press the CPU LOAD ADRS switch.

Set the CPU Switch Register to one of the following values:
777406 for RK05 disk cartridge
776716 for RP03 disk pack

370

Press the CPU START switch.

Bootstrapping the Distribution Medium

M9301-YA and M9301-YB Procedures
If the M9301-YA or M9301-YB Bootstrap Terminator is on the system, perform the
following steps:
1.

While holding down the CTRL switch, press the BOOT switch on the front of
the computer.
The bootstrap prints the contents' (in octal) of registers RO, R4, and the Stack
POinter, and the Program Counter at the console terminal. It then prints a
dollar sign ($) prompt.

In response to the prompt, type the two-character device code and the unit
number of the device to be bootstrapped. Terminate your response by pressing
RETURN.

Table 0-2 describes the device codes.
Table 0-2:

Device Codes for M9301-YA and M9301-YB Bootstraps
Device

Code

TU10rrEIOrrS03 Magnetic Tape

TU16rrE16rrU4SrrU77 Magnetic Tape*

RKOS Disk Cartridge

RP02/RP03 Disk Pack

RP04/RPOS/RP06/RM02/RM03/RMOS/RM80
Disk Pack* at 176700 CSR

* M9301-YB Bootstrap Terminator only.

M9301-YC Procedure
If the M9301-YC bootstrap is on the system, perform the following steps:
1.

Move the CPU ENABLE/HALT switch to its HALT position and back to its
ENABLE position.

Set the start address of 17765000 in the console switches.

Press the CPU LOAD AD DR switch.

Set the device unit number in switches 0 through 2.

Set the device code for the device to be bootstrapped in switches 3 through 6.
Table 0-3 lists the device codes.

Make sure that switches 7 through 21 are off (down).

Press the CPU START switch.

Table 0-3 lists the device codes.

Bootstrapping the Distribution Medium

371

Table 0-3:

Device Codes for M9301-YC Bootstrap
Device

Code

TU10rrE10rrS03 Magnetic Tape

RKOS Disk Cartridge

RP02/RP03 Disk Pack

RK06 Disk Cartridge

TU16rrE16rrU4SrrU77 Magnetic Tape

RP04/RPOS/RP06/RM02/RM03/RMOS/RM80
Disk Pack at 176700 CSR

---------------------- Note

Before the M9301-YC bootstrap actually bootstraps the system, it
performs CPU tests, instruction and addressing tests, and memory and
cache tests. If a hardware failure is detected, the diagnostic program
halts. The lights contain the ROM address of the halt. If this occurs,
call your DIGITAL Field Service engineer.
It may, however, be possible to continue with the bootstrap operation
if the lights contain the address 1773764, which indicates a cache
failure. To continue in this case, press CaNT. This is the ONLY case
in which it is possible to continue bootstrapping after the diagnostic
program detects an error.

M9301-YF Procedure
If the M9301-YF Bootstrap Terminator is on the system, perform the following steps:

While holding down the CTRL switch, press the BOOT switch on the front of
the computer.
The bootstrap prints the contents (in octal) of registers RO, R4, the Stack
Pointer, and R5 at the console terminal. It then prints a dollar ($) prompt.

372

In response to the prompt, type the two-character device code and the unit
number of the device to be bootstrapped. Terminate your response by pressing
RETURN.

Bootstrapping the Distribution Medium

Table 0-4 lists the device codes.
Table 0-4:

Device Codes for M9301-YF Bootstrap
Device

Code

TU10rrE10rrS03 Magnetic Tape

TU16rrE16rrU4SrrU77 Magnetic Tape

RKOS Disk Cartridge

RK06 Disk Cartridge

RP02/RP03 Disk Pack

RP04/RPOS/RP06/RM02/RM03/RMOS/RM80

Disk Pack at 176700 CSR

M9312 Procedure
The M9312 Bootstrap Module has five sockets that accommodate one CPU ROM
and up to four peripheral boot ROMs. Each CPU and boot device has a unique ROM
developed for it. The CPU ROM plugs into a specific socket location within the
module. The peripheral ROMs, however, may be placed in any of the four peripheral
socket locations as long as the sockets are filled in sequential order with no vacancies
between loaded ROM sockets. Since a particular peripheral ROM has a different boot
start address in each of the four sockets, it is sometimes important to know the
locations of the ROMs in the bootstrap module. The ROM configuration is a diagram
of where specific boot ROMs are located. This information must be known before the
bootstrap procedure can begin. The following sections explain how to determine the
ROM configuration if it is not known and how to bootstrap a device when the ROM
configuration is known.
Figure 0-1 is a diagram of the ROM arrangement for the M9312 Bootstrap Module.

CPU

ROM
BOOT #1 ROM
BOOT #2 ROM
BOOT #3 ROM
BOOT #4 ROM

Figure 0-1:

M9312 ROM ARRANGEMENT

Bootstrapping the Distribution Medium

373

If the M93I2 Bootstrap/Terminator is on the system, perform one of the following
procedures:
• If you have the M93I2 console emulator on your system, follow the procedures
in the section, Using the M93I2 Console Emulator (PDP-II/60s and
PDP-I1170s usually do not have console emulators). If that procedure does not
work, perform the next step to verify that you have a console emulator.
• If you have a CPU equipped with switch registers and do not know what
devices the M93I2 will boot, perform the procedures in the section,
Determining the M93I2 Bootstrap ROM Configuration.
• If you have a CPU equipped with switch registers, know what device ROMs are
on the M93I2 Bootstrap Module, but do not have a console emulator, follow
the procedures in the section, Bootstrapping With the M93I2.
• If you do not have the M93I2 Bootstrap/Terminator Module on your system
and need to boot the RLOI, RL02, or the RK07 disk device, perform the
manual load routine described in the section, Load Program Bootstrap for the
RLOllRL02 and RK07.
Using the M9312 Console Emulator

The M93I2 console emulator can be initiated in two ways depending on the type of
CPU (pushbutton or switch register) on the system.

Pushbutton boot procedures with the M93I2 console emulator.

While holding down the CTRL button, press the BOOT button on the CPU.
The bootstrap prints the contents (in octal) of registers RO, R4, the Stack
Pointer~ and R5 at the console terminal. It then prompts you with the
commercial at sign (@).
In response to the @ character, type the two-character device code and the
\ unit number of the device to be bootstrapped. Terminate your response by
pressing RETURN. If the unit number is not entered, it is assumed to be zero.
Table 0-7 contains the device codes.
Successful completion of these pushbutton bootstrap procedures produces
header information on the console terminal, similar to the following example:
Enablin~

only consolet disKst and tapes

RSTS V8.0 (MTO) INIT V8.0-14
Installin~

RSTS on a new sYstem disK? <Yes)

Begin the system installation process in Phase 2, Prepare System Disk.
2.

Switch register boot procedures with the M93I2 console emulator.

Move the CPU console ENABLE/HALT switch to its Halt position, then back to
its ENABLE position.
Set the CPU switch register to 765020.

374

Bootstrapping the Distribution Medium

Press the start switch. The bootstrap prints the contents (in octal) of registers
RO, R4, the Stack Pointer, and R5 at the console terminal. It then prompts you
with the commercial at sign (@).
In response to the @ character, type the two-character device code (in
uppercase) and the unit number of the device to be bootstrapped. Terminate
your response by pressing RETURN. If the unit number is not entered, it is
assumed to be zero. Table 0-7 contains the device codes.
----------------------- Note -----------------------

The @ sign returns at this point if the correct boot ROM was not
installed, or if a nonexistent device code is entered. If the contents of
the registers RO, R4, the Stack Pointer, and R5 appear before the @
sign, this indicates that at least one boot ROM socket is empty and
can accommodate another boot ROM.

Successful completion of the switch register bootstrap procedure produces
header information on the console terminal, similar to the example given for
the pushbutton bootstrap. After the message appears, begin the system
installation process in Phase 2, Prepare System Oisk.
Determining the M9312 Bootstrap ROM Configuration
If you do not know the M9312 ROM configuration, it can be determined by using
Tables 0-5 and 0-7 and performing the instructions that follow Table 0-5.
Table 0-5:

ROM Locations

ROM Address

ROM Location

765774

Diagnostic ROM

773000

ROM 1

773200

ROM 2

773400

ROM 3

773600

ROM 4

Repeat the following steps for each of the ROM addresses shown in Table 0-5. After
gou have completed this process, you will know the M9312 bootstrap ROM configuration of your system. With this information, you can boot any device having a boot
ROM in the M9312 Bootstrap Module.
Table 0-6 lists the M9312 bootstrap ROM configurations.

Bootstrapping the Distribution Medium

375

Table 0-6:

M9312 Bootstrap ROM Configuration

ROM Location

Bootable
Device

Device
Mnemonic

Diagnostic ROM

ROMI

ROM 2

ROM 3

ROM 4

If you do not know the M9312 ROM configuration, use Tables 0-5, 0-6, and 0-7
and follow these instructions:

376

Select a six-digit ROM address from Table 0-5.

Set the CPU switches to the selected number.

Press the LOAO AORS switch to set the ROM address.

Press the EXAM switch. The contents of the ROM address just loaded will
appear in the CPU data register.

Match the octal number represented in the CPU data register with the octal
data number shown in Table 0-7.

Locate the device mnemonic in Table 0-7 and the device name associated
with the matching number. The ROM you have just investigated can boot the
device(s) you located in Table 0-7. Write the retrieved device information from
Table 0-7 with the appropriate ROM location in Table 0-6. For example, if
you selected a six-digit ROM address for ROM 1 from Table 0-5, place the
device mnemonic and name you located in Table 0-7 with ROM 1 in Table
0-6. Oocumenting the ROM configuration in Table 0-6 will prevent performing
the above procedure again.

Bootstrapping the- Distribution Medium

Table 0-7:

Device Name and Mnemonic
Mnemonic

Unit

Octal Data

RLOI

0-3

042114

RK06/RK07

0-7

042115

RXOI

0-1

042130

RX02

0-1

042131

RP02/RP03
RP04/RP05/RP06
RM02/RM03/RM05/RMSO
at CSR 176700

DP
DB
DB*

0-7
0-7

042120

RK05

0-7

042113

TU56

0-7

TU16ITE16ITU45ITU77

0-7

046515

TUI0ITEI0ITS03

0-7

046524

TSIIITSV05ITUSO

0-7

046523

RA60/RASO/RASlIRC25
IRD511RD52/RX50
(MSCP controller
devices) at CSR 172150

0-7

042125

Console Emulator
CPU ROM

N/A

040460

Diagnostic ROM
PDP-11160170

N/A

041060

Device to Be Booted

177776**
xxx777***
* Type DB rather than DR if you are booting the RM02, RM03, or
RM05 disk.
** This is a continuation ROM of a multiple ROM boot.
*** Bad ROM or NO ROM present.

After you have determined the ROM configuration, perform the procedures in the
section, Using the M9312 Console Emulator, if you find you have a console emulator; otherwise, perform the procedures in the section, Bootstrapping With the M9312.
The following section explains how to bootstrap with the M9312 module using a
switch register controlled CPU.

Bootstrapping the Distribution Medium

377

Bootstrapping with the M9312

The following procedure describes how a device is bootstrapped when the M9312
bootstrap ROM configuration is known. Table D-8 provides the data needed to
bootstrap a device.
1.

Locate in Table D-8 the name of the device to be booted.

Determine from the ROM configuration in Table D-6 the location (ROM
1/2/3/4) of the device boot ROM.

Select the three-digit Switch Register Code (SWR) from Table D-8 for the
particular ROM location.

Move the CPU console Enable/Halt switch to its Halt position, then back to its
Enable position.

Set the CPU switch register to 765744 (or 17765744 for PDP-11/70).

Press the CPU LOAD ADRS switch.

Set the Switch Register Code (SWR) selected from Table D-8 in CPU switches
0-8, as shown in Table D-9.

Set the unit number of the boot device in CPU switches 9-11 (see Table D-9).

Press the CPU START switch.

Successful completion of this process boots the device. A message, similar to the
folloWing example, appears on the console terminal. At this point, you may begin the
system installation process in Phase 2, Prepare System Disk.
Enablin~

only console, disKs, and tapes.

RSTS V8.0 (MTO) IN IT V8.0-14
Installin~

RSTS on a new SYsteM disK? <Yes)

Table D-8 lists the switch register codes.

378

Bootstrapping the Distribution Medium

Table 0-8:

Switch Register Codes (SWR)
Switch Register Code (SWR)
ROM 1

ROM 2

ROM 3

ROM 4

RLOllRL02

012

212

412

612

RK06/RK07

012

212

412

612

RXOI

012

212

412

612

RX02

012

212

412

612

RP02/RP03

012

212

412

612

RP04/RP05/RP06
RM02/RM03/RM05/RM80
at CSR 176700

056

256

456

656

RA80/RA81/RA60
RC25/RX50/R051/R052
(MSCP controller
devices) at CSR
172150

012

212

412

612

RK05

012

212

412

612

TU56

042

242

442

642

TU16ITE16ITU45ITU77

012

212

412

612

TUI0ITEI0ITS03

012

212

412

612

Device to Be Booted

Table D-9 lists the console switch register settings.
Table 0-9:

Console Switch Register Settings

15 - 12

11 - 09

08 - 00

Octal Unit
Number

Switch Register Code (SWR) from
Table 0-8

Load Program Bootstrap for the RL01/RL02 and RK06/RK07
To bootstrap an RLOl, RL02, RK06, or RK07 device when the system does not have
the M9312 Bootstrap Module, you must manually enter a bootstrap load routine
using the CPU console. The following procedure describes the manual load process
using the PDP-ll/34. A similar procedure is followed using the CPU LOAD ADRS,
DEP, and EXAM switches for the PDP-11170 computer.
1.

While holding down the CTRL button, press the HLT/SS button on the CPU.

Set address 1000 in the console register by using the numbered console
buttons.

Press the LAD (load address) button.

Press the CLR button to clear the register.

Bootstrapping the Distribution Medium

379

Load the contents that appear below into memory, using the numbered
buttons and the DEP button. Press the CLR button after you have placed the
contents in the CPU register and pressed the DEP button.
RLOI/RL02 Bootstrap
Routine

RK06/RK07 Bootstrap
Routine

Contents
12700
174400
12760
13
4
12701
4**
10110
105710
100376
12760
177601
4
5721
10110
105710
100376
12760
177400
6
5060
4
62701
6
10110
105710
100376
5710
100001
0
5007

Contents
12700
177440
12760
0*
10
12701
2003***
10110
105710
100376
12760
177400
2
62701
16
10110
105710
100376
5710
100001
0
5007

Address.
1000
1002
1004
1006
1010
1012
1014
1016
1020
1022
1024
1026
1030
1032
1034
1036
1040
1042
1044
1046
1050
1052
1054
1056
1060
1062
1064
1066
1070
1072
1074

* Select drive number 0-7 for the RK07
** Load 4 for unit 0, 404 for unit 1, 1004 for unit 2, and 1404 for unit 3.
*** Load 3 for RK06.

After the contents are loaded, perform the following steps:

380

Place address 1000 in the console register again by using the numbered
buttons.

Press the CPU LAD (load address) button to load the address.

While holding the CTRL button down, press the START button on the CPU to
boot the device.

You can verify the accuracy of the load routine by using the CPU EXAM
button. Place address· 1000 in the register and press the LAD button. Press the
EXAM button to reveal the contents of address 1000. It should be 12700 for
both the RLOllRL02 and RK07 routines. Continue to press the EXAM button
to check the contents of the remaining addresses in the load routine. Use the
LAD and the DEP buttons to correct any erroneous contents.

Bootstrapping the Distribution Medium

Load Program Bootstrap for the TU10, TE10, or T503
To bootstrap a TU10rrE10rrS03 magnetic tape when the system does not have a
bootstrap that handles it, you must manually enter a load routine into memory using
the CPU Console Switch Register and the DEP switch.
To load the routine, perform the following steps:

Move the CPU C:onsole ENABLE/HALT Switch to its HALT position and back
to its ENABLE position.

Set the CPU Switch Register to 010000.

Press the CPU LOAD ADRS switch.

Load the following contents into memory using the Switch Register and DEP
switch.
Address

Contents

010000
010002
010004
010006
010010
010012
010014
010016
010020
010022
010024
010026
010030
010032
010034
010036

012700
172524
005310
012740
060011
105710
100376
005710
100767
012710
060003
105710
100376
005710
100777
005007

Set the Console Switch Register to 010000.

Press the CPU LOAD ADRS switch.

Press the CPU START switch.

If the system reads the tape but halts at address 010034, the magnetic tape generated
a parity error. Try another drive and make it unit O. If the system appears to take no
action and halts, verify the accuracy of the routine by using the CPU Console EXAM
switch. Use the Switch Register and the DEP switch to correct any erroneous contents. Rewind the tape to its load point before executing the routine again. If no
recovery is successful, you should have a DIGITAL field service representative check
the device. If the hardware is working properly, you should use a new magnetic tape
reel.

Bootstrapping the Distribution Medium

381

This appendix contains programs you may need to use during your installation or
update. It also contains programs related to patching RSTS/E code. The BUILD
program perform system installation-related tasks. The DSKCVT program converts a
disk to RDS1.2 format. The ONLPAT program allows you to patch binary code. The
CPATCH and PBUILD programs patch ASCII source code.

Using the BUILD/PATCH Program
The BUILD program builds new software. The IPATCH qualifier of the BUILD
program automatically installs updates as you build new software. (If there are no
update files for the software you build, then BUILD does not attempt the update
procedure. )
BUILD is a privileged program that is installed with a protection code of <232>. To
use the various BUILD functions, you need all privileges except:
o SYSMOD
o

EXQTA

USERl-8

The BUILD program requires that the patches and replacement modules be on disk.
If your media is tape, you must first use the layered product installation procedures.
See Part III for more information.
To run BUILD, type:
$ RUN UPDATE$:BUILD

383

BUILD then asks the following questions: .
BUILD VS.O-14 RBTB VS.O-14
Input device <BY:> ?
Output device <BYO:> ?
Control File is ?
Function (Build/Patch, Patch, Build) <Build/Patch> ?
Patch file input location <PATCH$:>

!*** BUILD COMPlete ***
!*** Processing ended on 31-MaY-85 at 11:13 AM ***
During most installations, BUILD asks additional questions that are specific to the
individual layered product. See the installation guide for the individual product for
gUidelines on answering specific questions.
You can create a log file of the build procedure and also specify that the build is to
run detached, in the format shown after the Input device? prompt in the BUILD
dialogue:
logfile = dev:/det
For example:
Input device <BY:>: ? <file naMe>=MMO:/DET

Note that the Input device? prompt also accepts a IDOS or IANSI qualifier.

Using the DSKCVT Program
The DSKCVT (Disk Convert) utility converts VS.O and older disks to the new V9.0
RDS1.2 format. Specifically, DSKCVT performs the following functions:
• Convert RDSO.O disks to RDS1.2 format
• Convert RDS1.1 disks to RDS1.2 format
• Convert accounts with "LOOKUP" passwords to "NOLOOKUP" at any time,
on any RDS1.2 disk (optional)
To run DSKCVT, you must start with a disk that does not need rebuilding. (Use the
MOUNT command if necessary to rebuild the disk first.) As a precaution, DIGITAL
recommends that you back up any disk before conversion.
DSKCVT requires some work space if the pack being converted is RDSO.O format.
Therefore, you must make sure that there are 32 blocks times the number of different
group numbers used on the pack, in order to allow conversion. (For example, if there
are ten group numbers, then the pack should have 320 blocks of free space for
conversion. )
DSKCVT accepts either logically mounted or logically dismounted packs. However,
the pack should not be in use when you run OS KCVT. To verify that no one is using
the pack, DSKCVT dismounts and remounts it at the start of processing.

384

Additional System Installation-Related Programs

The following is an example of the DSKCVT program:
$ RUN $DSKCVT
DSKCVT V8.0-14

RSTS

V8.0-14

SYSTEM

DisK to convert? DMO:
is this a SysteM DisK <NO)? YES
Generate NOLOOKUP passl,.,lords <YES)?
Displa}' accounts <YES)? 00

(B@

** CURRENT DISK ATTRIBUTES **
Dis ~\ :
Label:
Level:

_DMO:
SYSDSK
1•1

Proceed (Y or N)? Y
Converting _DMO:SYSDSK froM level 1.1 to 1.2 •••
[Otl] Converted
[1t1] ConlJerted
[1 ,2] COl"we rted

_DMO: conversion to 1.2 cOMPleted 31-MaY-85 11:05 AM
Converting _DMO: passwords to NOLOOKUP
[0,1] Converted
[1 tI] Converted
[1 ,2] Conl.le rted

_DMO: Password conversion cOMPleted 31-MaY-85 11:08 AM

In the example, DMO: is the disk pack to convert to RDS1.2: When you type DMO: in
response to the prompt, DSKCVT displays the pack ID DMO:SYSDSK. This lets you
verify that you are converting the proper pack. If the pack was already converted,
DSKCVT displays an error message and then repeats the Disk to convert: prompt.
Otherwise, DSKCVT continues with the dialogue.
When you answer Y to the Proceed (Y or N)? prompt, DSKCVT begins the
conversion. DSKCVT processes the accounts in ascending order. When the pack is
converted, DSKCVT dismounts. it and updates the pack label. The pack is now in
RDS1.2 format. However, the storage allocation table (SAT) does not yet reflect the
free disk space on the pack. Therefore, the pack is marked "dirty" until DSKCVT
updates the SAT. Then the pack label is updated to show that the pack is now
rebuilt. If the pack was mounted when DSKCVT started, it will be mounted once
again, with the pack ID as its logical name.
DSKCVT will not lose data even if the program aborts because of lack of work space,
a system crash, or a disk hardware problem. If there is a problem during the
conversion, you need only correct the problem and rerun the conversion. In such a
case, it is not necessary to restore the pack from a backup pack.

Additional System Installation-Related Programs

385

If the conversion proceeded far enough that DSKCVT was able to convert the pack,
it is then necessary only to mount it. Otherwise, DSKCVT restarts the conversion
from the beginning, after deleting the work files that were left behind from the first
attempt at conversion.
When you convert an RDSO.O (pre-V8.0) disk, DSKCVT makes two passes. In the
first pass, DSKCVT converts the RDSO.O pack to RDS 1.1. The second pass converts
the RDS1.1 pack to RDS1.2.
In converting RDS1.1 disks to RDS1.2 format, DSKCVT adds several new attribute
blocks to each account. Since some of the new attributes are only relevant on system
disks, DSKCVT asks you whether the disk being converted is a system disk. DSKCVT
adds the following new attribute blocks:
• Disk quota/usage block
• Privilege block, for system disks
• Non-disk quota block, for system disks
In creating the privilege attribute block, DSKCVT uses the following rules:
• For account [1,1], it assigns all privileges, except EXQTA
• For all other [1,*] accounts, it assigns all privileges, except SYSMOD and
EXQTA
• For accounts not in the [1, *] group, it assigns no privileges.
This scheme assigns privileges that are compatible with previous versions of RSTS/E.

Using the ONLPAT Program to Patch RSTS/E Binary Code
The need for manual file patching has greatly decreased. However, you may still
have to use ONLPAT to make emergency corrections.
The ONLPAT.SAV program allows you to patch binary code. You can run ONLPAT
in either the keyboard mode or the command file mode. In the keyboard mode, you
enter patch information on your terminal. In the command file mode, the patch
information is read from a command file.

Using ONLPAT in Keyboard and Command File Mode
ONLPAT gives you a choice. You can make patches to the software by entering the
corrections manually at your keyboard or you can use a previously created command
file to apply the patches for you. You make the choice at the beginning of the
ONLPAT dialogue when the program asks for the name of the command file you
want to use (if one exists). Your response determines how ONLPATgets the patch
information.

If you enter a command file name, ONLPAT uses the command to make the
corrections. When you press the RETURN or LINE FEED key, ONLPAT assumes the
patch information comes from the keyboard. ONLPAT expects keyboard input when

386

Additional System Installation-Related Programs

you enter a file name followed by an equal sign (=) symbol. This indicates you want
ONLPAT to create a log file of the patch. The remainder of this section describes
how to patch software using either of these methods.
When you enter patches at the keyboard, follow procedures similar to those you use
for the PATCH option of INIT.SYS. Unlike the PATCH option, ONLPAT does not
install a patch until you enter a circumflexiC (AC) at the end of the last line in the
patch. Do not press CTRL/C unless you want to abort the patching operation.
Because the program waits while you enter all the patch information, you can review
the entire patch and make changes before installing the patch.
The ONLPAT program can apply patches to the monitor or to programs written in
MACRO, such as PIP.SAV. To install a published patch, you must first look in the
RSTSIE Maintenance Notebook or the RSTSIE Software Dispatch for the article
containing the patch you want to install. After reading the article thoroughly, you can
create a command file or install the patch manually.
An ONLPAT example follows:
RUN $oNLPAT
COITlirland file nalrle?
File to patch? [O,l]BASIC.RTS
File found in account [0,1]
Base address? •• XTN
Offset address? 0
Base
Offset Old
New?
?????? 000000 020000 ? 0
?????? 000002 ?????? ? AC

Table E-l lists and describes the types of responses ONLPAT accepts in the program
dialogue.
Table E-1:

Responses to ONLPAT Questions

Response

Meaning

Number

Enter an octal number from 0 to 177777; leading zeros are optional. Or, enter
a decimal number in the range O. to 65535., making sure to include a trailing
decimal point to distinguish it from an octal number. The octal or decimal
number you enter becomes the new contents of the current location.

Symbol

Substitute a global symbol name for an octal number as the new contents of
the current location. The symbol table for the module being patched is part of
the SIL file. It contains that module's global symbol names and their values. A
global symbol name must be one- to six-alphanumeric characters and must be
defined in the symbol table for the current module.

Expression

Use an expression as a substitute for an octal number. An expression consists
of one or more numbers or global symbols, separated by arithmetic operators
(+ ,-, and *). You can use parenthesers to group portions of an expression.

RETURN or
LINE FEED key

Advance to the next location without altering the contents of the current
location.

circumflex

Return to the previous location without altering the contents of the current
location.

CTRLlZ

Enter CTRLlZ to return to the previous question.

CTRLlC

Enter CTRLlC to abort all patching and return to the program prompt.

Additional System Installation-Related Programs

387

Table E-2 describes the questions asked by ONLPAT.
Table E-2:

ONLPAT Dialogue Questions
Question and Response

COMMAND FILE NAME?
• Enter a command file name to have ONLPAT install patches using commands in the
command file. You can have ONLPAT make a record of the patches as well as install them if
you include a log file name with the command file name in the command line:
Command file name? log file = command file name
If you do not include a file type for the command file, ONLPAT selects .CMD. The default file
type for the log file is .LOG.

• Press the RETURN or LINE FEED key if you do not have a command file to apply the
patches. ONLPAT assumes you want to enter the patches manually from the keyboard. If you
want a record of the patches that you apply manually from the keyboard, include only the log
file name in the command line:
Command file name? log file =
You must place an equal sign after the log file name to make sure ONLPAT does not interpret
the file you specify as being a command file. Again, ONLPAT uses .LOG as the file type if you
do not specify one with the file name.
FILE TO PATCH?
Press the RETURN or LINE FEED key if you are applying a patch to the installed monitor SIL.
However, another response may be necessary If so, enter the response suggested either by the
RSTSIE Maintenance Notebook or the RSTSIE Software Dispatch article.
MODULE NAME?
Enter the module name included with the patch described either in the RSTSIE Maintenance

Notebook or the RSTSIE Software Dispatch article.
BASE ADDRESS?
Type the base address included with the patch described either in the RSTSIE Maintenance

Notebook or in the RSTSIE Software Dispatch article.
OFFSET ADDRESS?
Type the offset address included with the patch described either in the RSTSIE Release Notes
article or the RSTSIE Software Dispatch article. The offset address is the first location to be
patched relative to the specified base. The response suggested in the patch article will be a
number, symbol, or expression as described in Table E-l.

Use the information in Table E-2 and the following procedures to apply patches
manually:

388

Gather the articles that contain the patches you need. You can find the articles
either in the RSTSIE Maintenance Notebook or the RSTSIE Software Dispatch.

Additional System Installation-Related Programs

Run the ONLPAT program by typing RUN $ONLPAT. The program begins by
displaying the first of a set of dialogue questions:
COMMand file naMe?

At this point you:

Press the RETURN key to enter the patch manually from your terminal.

Type the name of a file, followed by an equal sign (=) symbol. This
instructs ONLPAT to create a log file of the patch. The patch is also
displayed on your terminal.

You then answer the remaining ONLPAT dialogue questions, following
the instructions in the RSTSIE Maintenance Notebook or the RSTSIE
Software Dispatch. Remember that ONLPAT does not install the patch
until you type "C (not CTRL/C) to end the program. Typing "C is entirely
different than entering CTRL/C: "C ends the patch successfully; CTRL/C
stops execution of ONLPAT without making any patches.
.

After installing the patch, ONLPAT displays a message informing you that
the patch has been installed:
PATCH COMPLETE
1 PATCH INSTALLED

ONLPAT then returns to the command file question. You can then either exit
the program or enter another patch.
To install a patch with a command file:

Create a command file. See the section, Building ONLPAT Command Files.

Run the ONLPAT program, by typing RUN $ONLPAT, and then press the
RETURN key. The program displays a question asking for the name of the
command file that contains the patches. Enter a command file in the following
format:
log file = command file

If you want a record of the patch, type the name of a log file. The default file
type for a log file is .LOG. ONLPAT does not create a log file by default.
3.

Type the name of the file that contains the commands ONLPAT uses to install
the patch. The default file type for a command file is .CMD. ONLPAT then
executes the command file. If you did not include in the command file the
name of the file you want to patch, ONLPAT pauses, letting you enter the file
name.

When ONLPAT finishes processing, the program displays a summary of the
patches installed and any patches skipped, and then returns to your keyboard
monitor.

Additional System Installation-Related Programs

389

Patching a Running Monitor with ONLPAT
Usually you can patch the installed monitor Save Image Library (SIL). The monitor is
modified on disk, and only after you shut down, and then restart the system, do the
patches become effective. However, patches to monitor overlay code (OVR) are a
special case. If you use patched code from OVR along with an unpatched monitor in
memory, your system may crash, or not work properly. This is because monitor
overlays are read in from the monitor SIL (from disk) as they are needed, and
changes to the monitor do not take place until the system is brought down and then
restarted.
When ONLPAT detects that the file being patched is the installed monitor SIL, the
program imposes certain restrictions:
• Installs the patch if the patch does not involve OVR. That is, ONLPAT applies
the patch to the monitor image on disk. The patch takes affect only after you
shut down the system and then restart it.
• If only one block of OVR is involved in the patch, ONLPAT installs the patch.
Because the patch affects only one block, ONLPAT can make all monitor
modifications with a single disk write.

• If the patch involves more than one OVR block, ONLPAT does not modify the
monitor, and displays the following error message:
?Patch to Module our too long for installed sil

• If the patch involves both OVR and some other module of the monitor,
ONLPAT displays the following error message:
?Patch to installed sil spans our and other Module(s)

The way to install a patch of this type is to copy your installed SIL, patch the
copy, shut down the system, start the patched copy, and delete the old
unpatched SIL.

Building ONLPAT Command Files
Create ONLPAT command files as follows:

Run ONLPAT from any logged-in terminal by typing RUN $ONLPAT. The
program then displays the COMMAND FILE NAME? question.

Respond to the command file question in the following format:
Patchfile = KB:
First type the file name of the patch file you want to create and then KB: to
indicate you are creating the patch file from the keyboard.

390

Additional System Installation-Related Programs

Press the RETURN key after you finish entering the command string. ONLPAT
then asks:
FILE TO PATCH?

Type the name of the file you want to patch, press the RETURN key,
and enter the text of the patch described in the RSTSIE Maintenance
Notebook or the RSTSIE Software Dispatch article.
After creating the command file, you may want to modify it. If modifications are
necessary, apply the following rules:
o

End each individual command in the patch by pressing RETURN.

o When ONLPAT executes the command file, the program changes all lowercase

characters to uppercase and reduces all tabs and spaces to a single space.
o Blanks are significant. Use them exactly as shown for individual command lines.
~

You can include comment lines at the beginning of a patch. A comment line
must begin with an exclamation mark (!).

o You must include a line that specifies the file you want to patch. The format of

this line is:
FILE TO PATCH? filename. type
Type the name of the file that you want ONLPAT to patch. If you do not
include a file name, ONLPAT prompts you for the file name during program
execution. ONLPAT uses the file name to specify any subsequent patches in
the command file that do not specify the file name.
o Subsequent command lines in a patch are identical to the formats used in the

RSTSIE Software Dispatch or the RSTSIE Maintenance Notebook. The
following command line is optional, but must appear with spacing exactly as
shown in the RSTSIE Software Dispatch or the RSTSIE Maintenance Notebook
articles:
BASE OFFSET OLD NEW?

Also, do not use any parenthetical comments.
o You must use the following notation:

is a circumflex, then Z; or CTRL/Z

is a circumflex, then C; not CTRL/C

<LF> is the LINE FEED key

Using the CPATCH Program to Patch ASCII Sou.rce Code
With the advent of prebuilt tasks and other replacement modules, the need for
manual patching has greatly decreased.

Additional System Installation-Related Programs

391

Use the CPATCH program to install patches to the source code of the BASIC-PLUS
library programs. CPATCH can patch individual programs, as described in this section
or build patching command files (see the section, Building CPATCH Command
Files).

General Operating Procedures
The general procedures to patch a BASIC-PLUS source file are:

Run the program by typing RUN UPDATE$:CPATCH. After printing a header
line, CPATCH prints:
FILE TO PATCH-

Respond in the format:
out-filespec = in-filespec
Enter the file name for the unpatched source file on the input side of the
command line and any file specification you want on the output side. The
default file type for both files is .BAK. If you do not include an output file,
CPATCH assumes the file has the same name as the input file and gives it a
.BAK file type.

Press the RETURN key in response to the number sign (#) prompt. The
prompt printed by CPATCH indicates that it is ready to patch the source
program.

Edit the source program, using the instructions in the RSTSIE Maintenance
Notebook or the RSTSIE Software Dispatch. CPATCH prints an * prompt to
show when to begin editing the source.

Type EXIT in response to the * prompt when you finish editing. CPATCH
prints a message indicating the patch is installed:
PATCH FROM file specification COMPLETE.

CPATCH returns to the # prompt. If there are other patches to the
current file, do them now, or enter CTRL/Z. If you enter CTRL/Z,
CPATCH returns to the prompt:
FILE TO PATCH-

Return to Step 2 in this procedure if there are other files to patch.

Enter CTRL/Z to exit the program if there are no more files to patch.

Follow instructions in either the RSTSIE Maintenance Notebook or the RSTSIE
Software Dispatch for including the patched source program in the system
library.

392

Additional System Installation-Related Programs

Running the PBUILD Program
After you build the patching and PBUILD command files (see the section Building
CPATCH Command Files), run the PBUILD program to install the patches.
Note -----------------------

References in these sections to BP2COM are for VI.6 of BASICPLUS-2. VI. 6 is no longer supported or available.

PBUILD Dialogue

Type RUN UPDATE$:PBUILD, and press the RETURN key to begin the PBUILD
dialogue:
READ FILES TD PATCH FROM <SY:[l 12]):

Enter the device and account that contains the unpatched versions of the text files.
The device and project-programmer number (PPN) in angle brackets is the default
value. If either the device or the PPN is incorrect, enter the correct values in the
following format:
logfile = commandfile[ -]
Logfile is the name of the file in which the entire patching procedure is recorded.
Device represents the input device name and unit number and is followed by the
project-programmer number (account number). The DETACH switch causes PBUILD
to detach from the keyboard while performing the patching operation. If you specify
both a log file and the DETACH switch, some patching operations are faster because
they are not limited by the speed of the terminal.
For example, if the files are on the public structure under account [120,5], the correct
response is [120,5]. If the files are on magnetic tape drive MMO: on account [1,2],
the correct response is MMO:. If both the account and the device are wrong, you
must enter both, such as MMO:[120,5]. If both are correct, then just enter a carriage
return.
After you specify the input device, PBUILD prints:
COMPILE PATCHED PROGRAMS<YES):

If you press the RETURN key, PBUILD compiles the resulting patched file and prints
additional patch questions. If you Type NO and PBUILD does not ask the next three
patch questions.
If you want PBUILD to compile the files, it asks where to store the compiled
programs:
LIBRARY DEVICE <SY:[l 12]):
SYSTEM DEVICE <SYO:[l 12]):

Additional System Installation-Related Programs

393

The library device is the device and account that PBUILD uses for the programs that
normally go to the library account. The system device re~ers to the disk that contains
the RSTS/E system. The compiled programs normally reside in the library account.
If you want to have PBUILD save the patched sources, type YES in response to the
following question:
SAVE PATCHED SOURCES<NO>:

If you type NO or press the RETURN key, PBUILD skips the next question and
deletes the patched sources after compiling.
If you choose to retain the patched sources, the program prints:
WRITE PATCHED SOURCES TO (SY:[200t200]>:

Your response indicates on which device and in which account you want the patched
sources to reside. DIGITAL recommends that you not place the patched sources in
account [1,2]. If you have no particular device or account for the sources, you can
accept the default. This allows PBUILD to place the sources in account [200,200] of
the public disk structure.
When PBUILD prints the # prompt, type a command line in the format:
logfile = commandfile[ -]
CPATCH uses the log file to write the log of the actual text file edits as they take
place. If you do not specify a log file, CPATCH uses the file name KB:PBUILD.CMD.
If you specify a file, the default file type is .LOG. The command file field is the name
of the file containing the commands to PBUILD. The default file type is .CMD. In
both the log and command files, the default device is SY: and the default account
number is the current user account. As an option, you can place a hyphen (-) after
the command file specification t6 cause PBUILD to prompt you for additional
command files. Because the prompting of the additional control file question is also
dependent on other factors, PBUILD may ask for additional control files if you do not
attach a hyphen to the command file specification. After you press LINE FEED,
PBUILD chains to the BUILD program, which controls the remainder of the dialogue.
Once you enter a correct command file name, BUILD prints a message to indicate it
is copying the specified command file to the public disk structure. The variable
[nnn,nnn] represents the command file account number, and the nn in the
PBLDnn. TMP specification is the job number. The format of the message is:

*** COPYING FILE dev:[nnntnnn]cororoandfile TO SY:PBLDnn.TMP ***
BUILD then preprocesses the command file. Normally at this point, during the
preprocessinOg of the first command file, BUILD prints a run-time systtm question that
asks you for the name of the run-time system under which you want the executable
programs to run. The format of the question is:
Run-Tiroe SYstero <xxxxxx>?

BUILD prints the name of the system primary run-time system in angle brackets.
Press the LINE FEED key to accept the default, or enter the name of another
run-time system. If you decide not to accept the default, note that the run-time

394

Additional System Installation-Related Programs

system you specify includes a keyboard monitor and has a default executable file type
of . BAC or .TSK. If BUILD does not accept your response, it prints an error message:
o Xxxxxx is not a Keyboard monitor

• Run-time sYstem must have a default extension of .BAC or .TSK
• Xxxxxx is not installed
Attempt to install xxxxxx <Yes or No>?

After BUILD prints either of the first two messages, it prints the RUN-TIME SYSTEM
question again. Enter a new run-time system name that conforms to the run-time
system restrictions indicated in the error message. If BUILD prints the XXXXXX IS
NOT INSTALLED message, it has found the specified run-time system in account
[0,1] but has discovered the run-time system is not installed. After printing the
message, BUILD asks if you want to install the run-time system:
ATTEMPT TO INSTALL XXXXXX<No>?

BUILD inserts the run-time system name in the XXXXXX field, which represents the
run-time system that BUILD will attempt to install. Type NO if you want BUILD to
return to the RUN-TIME SYSTEM prompt. One of the following cases occurs if you
type YES:
o BUILD installs the run-time system successfully and prints the message,

XXXXXX INSTALLED. BUILD asks the CUSP COMPILER question if you
selected RSX or BP2COM as your run-time system.
o BUILD installs the run-time system, determines whether it includes a keyboard

monitor and has the correct file type, and then prints one of the following two
error messages:
Xxxxxx is not a Keyboard monitor
- Run-time sYstem must have a default extension of .BAC or
.TSK.

After printing either of these messages, BUILD tells you it is removing the
previously installed run-time system by printing the XXXXXX WILL BE
REMOVED message. The program returns to the RUN-TIME SYSTEM
question.
• BUILD may detect errors other than those already described. When it does, it
prints:
Run-time sYstem operation failed<text>

The text can be any valid RSTS/E error message. After printing the error,
BUILD returns to the RUN-TIME SYSTEM prompt.

If you selected either the BP2COM or RSX run-time system, BUILD asks the following CUSP COMPILER question:
USE THE CUSP COMPILER 'CSPCOM'<YES>?

Type YES if your run-time system is RSX; type NO if it is BP2COM.

Additional System Installation-Related Programs

395

After the preprocessing of the first command file, BUILD may prompt you for the
name of another command file by printing:
ADDITIONAL CONTROL FILE IS (process file>?

Type another command file specification and terminate the response by pressing the
LINE FEED key. Like the previous command file procedure, BUILD prints the
COPYING FILE message and then preprocesses the file. BUILD continues to print
the ADDITIONAL CONTROL FILE IS question until the default is selected. Press the
LINE FEED key to accept the default. BUILD prints the current date and time and
begins executing the command files. If you did not attach a hyphen to the original
command file specification, PBUILD may not ask for additional control files. Therefore, if you need to process more than one command file, attach a hyphen to the
logfile = commandfile[ -] specification to ensure BUILD asks the ADDITIONAL
CONTROL FILE question. Note that PBUILD prints the COPYING FILE message
and preprocesses the command files; it does not execute any command file until you
specify all files.
During the preprocessing phase, BUILD may ask additional dialogue questions. These
questions cannot be listed here; they are initiated by the particular command file that
BUILD is processing. There are many control files that might be processed, each with
its own unique set of questions. You must therefore see documentation regarding the
particular command file to answer these questions.
PBUILD/BUILD Terminal Output

PBUILD/BUILD performs all patch operations by printing the required commands on
a pseudo keyboard and echoing them to the user's terminal. Every operation causes
an output to the terminal to provide an accurate log of all operations. The steps that
occur in a patch operation are summarized in the following list. Note that the
commands described are those which are printed on the pseudo keyboard and thus
require no user input:
1.

RUN UPDATE$:CPATCH
This runs the CPATCH program.

outfile = infile
This string is typed to the prompt FILE TO PATCH issued by CPATCH. Infile
is the program to be patched, with the input device and account number being
that which is entered at the beginning of the dialogue. The output file can be
one of two possible values. If the patched sources are going to be saved, and
the device is a file-structured disk, the output file will be the same as input file
but with the device and account number selected in answer to the WRITE
PATCHED SOURCES TO question. If the sources are not to be saved, or if
they will be saved on a device other than disk, the device and account number
will be the library account.

logfile = commandfile
A command line in this format is typed in response to the CPATCH # prompt.
CPATCH uses the command file to perform the patch to the text file. The file
name is obtained from the command file currently being executed by PBUILD.

396

Additional System Installation-Related Programs

If the name as specified within the command file is missing either a device or
an account number specification, the device and/or account number that
contained the command file executing is used. The log file in this command
line represents the log file you enter in response to the PBUILD # prompt.
This step is repeated for each patch to the particular source program.

"Z (CTRL/Z)
This character combination is forced to the keyboard after all patches have
been applied. It causes CPATCH to print the FILE TO PATCH prompt.

"Z
A second CTRL/Z causes the program to return to the RSTS/E keyboard
monitor.

OLD outfile
This is typed only if the compile option was selected in the dialogue. It causes
the source file to be compiled.

COMPILE comfile
This is typed if the compile option was selected. It causes the compiled version
of the program to be saved as the file named comfile. The file to compile
normally has the same file name as the output file but has the same device and
account number as the library device entered in the dialogue. If a new name
was provided in the PBUILD command file, that name appears as the file to
compile.

RUN [1,2]PIP.SAV
*<permfile> = <outfile>

"Z
If the patched sources are to be saved and the save device is not a disk, then
these commands are printed on the pseudo keyboard. The permanent file has
the same file name as output file but has the same device and PPN as the
response to the WRITE PATCHED SOURCES TO question.

RUN [1,2]PIP.SAV
*<outfile>/DE:NOWARN

"Z
This command is used to delete the output file that was created in the library
account. It only appears if the previous copy operation was performed or if the
current patched sources were not to be saved.
10.

RUN [1,2]PIP.SAV
*< backfile>/DE:NOWARN

"Z
If the output file and the input file are the same file name, CPATCH creates a
backup file (backfile). If that occurs, this command deletes it.

Additional System Installation-Related Programs

397

In a normal patch operation only some of the CPATCH commands actually appear.
However, CPATCH does perform some combination of the previous commands for
each patch in the PBUILD command file.

Building CPATCH Command Files
This section describes how to create new files used by CPATCH to perform the
actual edit of your source programs.

Building the Patching Command File
To make a new patch, you must create a CPATCH command file by running the
CPATCH program. Enter the commands at your terminal and use a file as the log.
The output log becomes the new CPATCH command file.
File Naming Convention

Patch files are much easier to manage if you adopt a consistent file naming
convention. The convention used for all patches to the Commonly Used System
Program (CUSP) Library is presented here as an example.
A typical example might be the program QUMRUN. Assume the first article in the

RSTSIE Software Dispatch concerning QUMRUN describes a patch. The article's
sequence number is 14.6.1, where the number 14 is the component number
(Spooler and Operator Services Package), 6 is the subcomponent number, and 1
indicates it is the first article published about QUMRUN. The corresponding patch file
name would be PA1406.001.
Creating the CPATCH Command File

Run the CPATCH program to create the CPATCH command file. The file for which
the patch file is being created is specified at the FILE TO PATCH prompt, and the
keyboard is specified as the command file with the CPATCH command file ·being
created as the log file. The patch is then manually applied. Note, however, that
CPATCH is a line editor which means its text buffer contains only a single line of text
at anyone time. When the patch is completed, the log file contains a CPATCH
command file that performs the same patch when applied using CPATCH. The
commands to create the CPATCH command file to perform the first patch to
QUMRUN is an example.
You first start the program by typing:
RUN UPDATE$:CPATCH

After printing a header line, CPATCH prints:
FILE TO PATCH-

The response to this prompt would be:
Qut:QUMRUN.BAS=in:QUMRUN.BAS

. 398

Additional System Installation-Related Programs

You place on the input side of the command line the device name and PPN that
contains the unpatched source file QUMRUN.BAS. On the output side, specify any
device and PPN. Use a different device name and PPN from the one used for the
input specification. Then you can test the patched program before replacing the
original source.
CPATCH prints a # prompt to which the correct response for the example patch
would be:
PA1110G.001=

With PA1406.001 on the output side of the command line, CPATCH uses it as the
log file. There is no specification on the input side, and thus CPATCH uses the
terminal (KB:) as the default command file. Note, however, that you may want to
check or determine the patch checksum by including the ICS switch (see the section
Verifying the Patch).
CPATCH prints the * prompt again. At this point, use CPATCH editing commands to
perform the patch on the file. The following sections introduce you to the editing
capabilities of the CPATCH program.

Editing with CPATCH
After CPATCH prints the * prompt, you are ready to use the CPATCH line tzditor to
perform the patch. When the patch is complete, use the EX command to return to
the # prompt. A CTRL/Z returns the FILE TO PATCH prompt, and another CTRL/Z
exits the program. The file PA1406.001 (from the example in the previous section)
then becomes the CPATCH command file required to perform the patch.
The CPATCH editor is a character-oriented text editing program written in
BASIC-PLUS for use on the RSTS/E operating system. It reads ASCII files from any
input device, makes specified changes, and writes on any output device. You operate
the editor through the use of commands typed at your terminal. The basic editing
process can be divided into three parts:
1.

Reading the input text into an internal buffer

Changing the text stored in the buffer

Transferring the revised text to a new file

The following sections list terms and definitions and describe the commands used
with the CPATCH editor.
CPATCH Editor Terms and Definitions

The CPATCH editor enables you to perform editing operations on ASCII text. The
program stores the text to be edited in an intermediate area of memory called a
buffer. It does not alter text in the input files.
The editor refers to text in the buffer by using a character location pointer called a
cursor. The cursor is considered to reside between any two characters. At the start of
editing operations, the cursor precedes the first character in the buffer. You move the

Additional System Installation-Related Programs

399

cursor during editing operations according to the type of editing being performed.
You can refer to text in the buffer as so many characters or lines preceding or
following the cursor.
To edit text, you must specify a command or series of commands in response to the *
prompt printed by the CPATCH program. The commands are classed according to
the type of operation they· perform:
Cursor Manipulation

Moves the cursor without altering text within the buffer.

Character Search

Finds a specified occurrence of text within the buffer to
facilitate editing.

Character Manipulation

Adds to and removes characters or a line of text from the
buffer.

Many editor commands are character-oriented. That is, they affect a specified number
of characters preceding or following the cursor. The argument of these commands
specifies the number of characters in the buffer on which to operate. The number of
characters you specify with the argument n is the same forward (n) as backward (-n).
The LF, CR, and NUL characters, although not printed, are embedded in text lines,
counted as characters in character-oriented commands, and treated as any other text
characters.
Some commands are line-oriented. The argument of these commands specifies the
number of lines on which to operate. Because the editor counts the line-terminating
characters to determine the number of lines on which to operate, an argument n does
not affect the same number of lines forward (positive number n) as it affects
backward (negative number -n).
For example, the argument -1 applies to the line beginning with the first character
following the second previous end-of-line and ending with the character preceding the
cursor. The argument 1 in a line-oriented command, however, applies to the text
beginning with the first character following the cursor and ending at the first
end-of-line. Thus, if the cursor is at the center of the line, the argument -1 affects one
and one-half lines backwards from the cursor and the argurhent 1 affects one-half line
beyond the cursor.
Character search and manipulation commands operate in command mode. The text
used to search or being manipulated can be a single character or a group of
characters (called a string). If the text does not contain a CR or LF character and is
small enough to fit on a single typed line, command mode can be used to specify the
text. In command mode, the editor expects the first character following a search or
manipulation command to be a delimiting character for the desired text. The editor
uses as the text the characters between delimiters. The delimiting character, therefore,
cannot appear in the text, nor can the characters CR and LF.
To specify the word INPUT as the text in command mode, you can use the following
string with the search or manipulation commands:
IINPUTI

400

Additional System Installation-Related Programs

The editor uses the characters between the slash delimiters (I) as the text. In
command mode, you can use any printable character that does not appear in the text
as a delimiter. If the delimiting character appears in the text, the editor attempts to
interpret the remaining characters as commands.
To prevent ambiguities when a file is used for command input, CPATCH requires all
"invisible" characters, (ESCAPE, LINE FEED, and so forth) to be translated to a
visible form. This translation is always done on log file output to permit log files to be
used for command input with no modification. Because the output is used for patch
verification, it must be typed exactly. An error causes a rejection of the patch.
The translation is:

Command File
Format

Control Characters

<TAB>

ASCII 9 (horizontal tab)

<FF>

ASCII 12 (form feed)

<ESC>

ASCII 27 (escape)

<LF>

ASCII 10, 13, 0 (line feed sequence)

<CR>

ASCII 13, 10 (carriage return sequence)

<null>

ASCII 0 (isolated null character)

<13>

ASCII 13 (isolated carriage return sequence)

<10>

ASCII 10 (isolated line feed character)

CPATCH Editor Commands

·The commands you can use with the CPATCH editor are:

Advance Command (nA)
The Advance command is a line-oriented command that moves the cursor to a point
preceding the first character of a line. depending on the size of the argument used. If
you do not include an argument, the editor selects one line forward as the· default.
That is, the A command moves the cursor to the beginning of the next line.
Arguments and their effect on the Advance command are listed as follows:
nA
OA

Advances the cursor n lines and positions the cursor at the beginning of the line.
Moves the cursor to the beginning of the current line.

Additional System Installation-Related Programs

401

Change Command (nC/xxxxI)
The Change command changes a specified number of characters following the
location of the cursor. The text </xxxx/> must be set off by delimiters. The C
command is equivalent to an Insert command followed by a Delete command.
Arguments and their effect on the C command are described as follows:
nC

Replaces n characters following the cursor with the specified text. The cursor is
placed after the inserted text. The C command does not affect text beyond the
current line.
-nC Replaces n characters preceding the cursor with the specified text. The cursor
is placed after the inserted text. The C command allows you to make changes
to the current line only.
OC Replaces the current line up to the cursor with the specified text.

Delete Command (nD)
The Delete command is a character-oriented command that deletes n characters in
the page buffer beginning at the cursor. If you do not include a value for n, the editor
deletes the character immediately following the cursor. After executing the command,
the editor places the cursor at the first character following the deleted text. The
following list describes each argument and its effect on the Delete command:
nO

Deletes n character following the cursor. The D command does not allow you
to delete text beyond the current line.
-nO Deletes n characters preceding the cursor. You cannot use the D command to
delete text other than on the current line.
00 Deletes the current line up to the cursor. The editor positions the cursor at the
first character following the deleted text.

Get Command (nG/xxxxI)
The Get command is a search command that allows you to search for the nth
occurrence of the specified text (/xxxxl) starting at the current cursor location. If you
do not include a value for n, the editor searches for the first occurrence of the text.
The search ends when the editor either finds the nth occurrence or encounters the
end of the buffer. If the search is successful, the editor places the cursor at the end of
the searched text. The editor prints the G command followed by a question mark (?)
to indicate an unsuccessful search. In that case, the cursor follows the last character in
the buffer.

Whole Command (nH)
The Whole command reads each page of the primary input file into the buffer until
the nth occurrence of the specified text object is found. The editor begins at the
cursor and searches the current buffer until the nth occurrence of the text is found or
the end of the buffer is reached. If the search is successful, the editor positions the
cursor immediately following it. If the editor does not find the nth occurrence in the
current buffer, it writes the buffer to the primary output file, clears the buffer, reads
the next page of the primary input file into the buffer, and continues the search. The
search is unsuccessful when the nth occurrence is not found and the end of the
primary input file is reached. The H command followed by a question mark indicates

402

Additional System Installation-Related Programs

an unsuccessful search. When this occurs, the editor copies the entire contents of the
primary input file to the primary output file and places the cursor at the beginning of
an empty buffer. The H command operates in a forward direction only; negative
arguments are not allowed.

Insert Command (I/xxxxl)
The Insert command allows you to insert text (/xxxxl). The editor inserts the text and
places the cursor after the last character of the inserted text. You cannot use an
argument with the Insert command. Up to 80 characters per line can be specified by
typing the letter I on one line followed by the RETURN key and the text to be
inserted on the following line{s). Execution of the command occurs when you press
the LINE FEED key. If the text does not contain a carriage return or a line feed
character, it can be typed on the same line as the I command but must be set off by
delimiters.

Jump Command (nJ)
The Jump command moves the cursor over a specified number of character
locations. If you do not include an argument, the J command moves the cursor one
character position forward. Arguments and their effects upon the Jump command are
described as follows:
nJ

Moves the cursor forward one character. The J command does not affect any
text beyond the current line; that is, a command such as - 400J only moves the
cursor to the beginning of the current line.
-nJ Moves the cursor backward n characters. The J command does not affect
any text beyond the current line; that is, you cannot move the cursor
further than the end of the current line.
OJ Moves the cursor to the beginning of the current line.

Kill Command (nK)
The Kill command removes n lines of text (including the carriage return and line feed
characters) from the page buffer beginning at the cursor and ending with the nth
end-of-line. The editor places the cursor at the beginning of the line following the
deleted text. The following list describes each argument and its effect on the Kill
command:
nK
OK

Removes the character string (including the CR and LF sequence) beginning at
the cursor and ending at the nth end-of-line.
Removes the current line up to the cursor location.

List Command (nL)
The List command prints at your terminal lines of text as they appear in the buffer.
An argument preceding the L command indicates the portion of the text to print. For
example, the command 2L prints on your terminal the text beginning at the cursor
and ending with the second end-of-line character. The cursor is unaffected by the L
command. Arguments and their effect on the List command are described as follows:
nL
OL

Prints one line of text at the terminal. The L command accepts only zero and
one as arguments.
Prints the current line up to the cursor.

Additional System Installation-Related Programs

403

Verify Command (V)
The Verify command (V) prints at your terminal the entire line in which the cursor is
located. It provides an easy means of determining the location of the cursor after a
search is completed and before any editing commands are given. You can also use
the V command after you have typed an editing command to allow you to check
your input. The V command does not take arguments.

EX Command (EX)
To end an editing session, you use the EX command. It writes the buffer to the
primary output file, transfers the remainder of the primary input file to the output file,
closes all open files, and renames the temporary file as the edited, primary output file.
The following dialogue shows the procedure:
*EX
#"Z
The editor prints the # prompt (in response to which you can enter more input and
output specifications). Entering CTRL/Z ends the editing session and control returns
to your keyboard monitor.
You should periodically use the EX command to end the editing session. The primary
input file remains intact while you are editing. The temporary file retains the revised
text as edits are made. If the system crashes during the editing session, the primary
input file is not disturbed, but the edits you are making are lost. Therefore, it is
recommended that you frequently exit to update the primary output file. In the event
of a system crash, the amount of editing lost is limited to those edits made since the
beginning of the latest session.

Verifying the Patch
The CPATCH program provides two switches to verify the accuracy of the patching
operation. To make sure CPATCH applies a patch correctly, you must specify the
ICS switch while creating a patch file and the ICS:n switch when you are applying the
patch.
To create a patch file, run CPATCH and answer the FILE TO PATCH prompt. After
you enter the name of the file to patch and press the RETURN key, CPATCH prints
a # prompt. Because you are creating a file to store the patches, enter its file
specification followed by an equal sign, attach the ICS switch, and press the RETURN
key. CPATCH prints an * prompt to indicate its readiness to accept the patch.
After you enter the patch and terminate your input by typing EX, ·CPATCH calculates
a number, called a checksum, and prints it on your terminal. CPATCH uses this
number while applying the patch to verify the patch was correctly incorporated.
CPATCH prints the patch complete message to mark the end of the operation and
returns to the # prompt. You can then enter the name of anew patch file or enter
CTRL/Z to return to the FILE TO PATCH prompt. If you also enter CTRL/Z in
response to the FILE TO PATCH prompt, CPATCH terminates and returns control to

404

Additional System Installation-Related Programs

your keyboard monitor. The following terminal output illustrates the use of the ICS
switch and the creation of a checksum number:
RUN UPDATE$:CPATCH
<CPATCH's header line>
File to patch - PATCHA.BAS=PATCHA.BAS
# PA2325. 001 = ICS
*G/-10/-1D

* EH

Ched\sulTI = 53437
Patch froM _KB:[l ,247JCPATCH.CMD cOMPlete.
#"Z

File to patch -

After creating the patch file, you can use CPATCH again to apply the patch. As
before, run CPATCH, specify the file to patch, and press the RETURN key to receive
the # prompt. In response, attach the ICS:n switch, replacing n with the checksum
number that CPATCH calculated previously (53437). Press the RETURN key, enter
the patch, and exit by typing EX. If you enter the patch correctly, CPATCH calculates
the same checksum number, applies the patch, and prints the patch complete
message. Otherwise, it prints an error message:
?Actual checKsUM of 53437 does not Match 53537
i..Patch f rOITI _KB: [1 ,247JCPATCH.CMD s~\ipped.

You must retrace your steps and try again. An example of a successful attempt to
apply a patch follows:
RUN UPDATE$:CPATCH
<CPATCH's header line>
File to patch - PATCHA.BAS=PATCHA.BAS
#PA2325.001/CS:53437
*G/-10/-1D

* E}"

Patch froM _SY:[1,247JPA2325.001 cOMPlete.

#"'Z

File to patch -

The ICS: n switch, n representing a number from 0 to 65535, causes CPATCH to
recalculate the checksum as a result of your new input and to compare it to the
original calculation. In this case, you entered the patch accurately; CPATCH was able
to calculate the same checksum and then apply the patch.
Building the PBUILD Command File

After bUilding a command file of patches, the next step is to build 'another command
file that contains the instructions to PBUILD for installing the patches.

Using Comments
Comments may appear anywhere in a PBUILD command file. PBUILD treats any
line of text with an ! character as its first character as a comment. If you use the !
character as an account specifier, you must place it in a column other than the first.
One or more blanks before the ! character is sufficient.

Additional System Installation-Related Programs

405

Using Indirect Command Files

Any command line beginning with an at sign character (@) is used as a file that
contains the next commands. The position in the current command file is saved, and
all subsequent input comes from the file specified until an end-of-file is reached.
Command input then resumes from the saved position in the command file. You can
nest indirect command files up to 15 levels deep.
You must observe the following rules when using indirect files.
o The default file type for indirect command files is .CMD. Therefore, you must

specify explicitly any other file type.
• If either the device or the PPN is absent from an indirect file name, the device
and/or PPN is obtained from the command file name at the previous level. To
avoid ambiguity in device specification, place all command files in the same
account; make sure they they do not include a device and PPN. Instead, the
device and /PPN for all indirect command files should be specified at PBUILD's
# prompt, setting the default value for all subsequent indirect command files.
Using the Underscore as a Quote Character

You can quote any character or command with the underscore (_) character. For
example, if it is necessary to have the text "$FORCE" not interpreted as a $FORCE
command, prefix the command with the underscore character by typing: _ $FORCE.
In doing so, you alter the way in which the system responds to data following the
underscore.
Command File Statements

There are four types of PBUILD command file statements:
$FORCE

Forces command lines to the keyboard until the next $PATCH or $END
statement.

$PATCH

Identifies the file to be patched.

patchfile

Contains the specification for a patching file.

$END

Indicates the end of patching for one file.

Comment lines can appear anywhere in a PBUILD command file but usually appear
at the beginning of the file to identify its content. PBUILD treats any line of text
beginning with an ! character as a comment.

406

Additional System Installation-Related Programs

To patch a file, the PBUILD command lines must be in the following order:
$PATCH statement
patchfile statement

patchfile statement
$END statement
$FORCE statement
(commands to be forced)
$END statement

$FORCE Statement
The $FORCE statement is not required for patching BASIC-PLUS programs. It allows
you to batch commands into the file (to run programs, delete files, and so forth). For
example, ONLPAT is run in this manner to patch binary files. If $FORCE is used, it
and its related command lines must be placed outside the bounds of a
$PATCH/$END set, either before a $PATCH staten1ent or after an $END statement.
The command lines following a $FORCE statement use logical names to allow device
and PPN assignments (those made during the PBUILD dialogue). The substitutions
are:
-SYSTEM:

Is· the value for the device and PPN specified as the library device.

-SYSDSK:

Is the value for the device and PPN specified as the library or the
system device.

-INPUT:

Is the value for the device PPN specified as the unpatched source file.

-SAVDEV:

Is the value for the device and PPN specified as the patched source
file. If sources are not to be saved, SAVDEV defaults to the system
value.

CHR$(26%)(CTRL/Z)

CHR$(3%)(CTRL/C)

The $FORCE statement is in effect until a $PATCH statement or end-of-file is
encountered. Any command line beginning with an @ character is treated as an
indirect command file.

$PATCH Statement
The $PATCH statement is the first statement in a sequence of statements to perform
a patch. The format of the statement is: $PATCH filename. You must specify the file
name. The default value for the file type is .BAS and the qefault device and PPN is
the one specified in the opening question of the dialogue. If a file type or a device
and PPN is specified with file name, it overrides the default. For example, suppose
the input device entered at the beginning of the dialogue is MM:[120,51], The

Additional System Installation-Related Programs

407

following list shows various values for file name in the $PATCH statement and the
resulting file name after filling in the defaults:

SPATeH File Name - Name Actually Used
TEST

MM:[120,51]TEST.BAS

TEST.

MM:[120,51]TEST.

SY:TEST

SY:[120,51]TEST.BAS

SY:TEST.FIL

SY: [1,2]TEST.FIL

The statement consists of a single file name, which is the name of a command file to
be used by CPATCH to perform the source text editing. Any number of $Patch file
statements are permitted. There is one patch file statement for each patch to the
program.
The default file type for the Patch files is .CMD. The default device and PPN is that
of the current PBUILD command file which is open. To avoid confusion, make sure
all command files include indirect files and patch files, are in the same account, and,
have neither device, nor PPN specified.

SEND Statement
The $END statement indicates the end of a patch. It also selects a number of options
for the operations that override those entered in the dialogue. The format of the end
statement is:
$END [INC] [newname]
When PBUILD encounters the $END statement, it normally performs the OLD and
COMPILE operations. However, you can change the operation by providing either
(but not both) of two optional arguments. The first is the INC switch. When you
include this switch, no compile operation is performed. The patched source is saved
on the account specified as the library in the opening dialogue.
The newname option allows the name of the file to be changed after it is compiled.
The default name for the compiled program is rvSYSTEM:file.BAC; rvSYSTEM: is
replaced by the library device and PPN specified in the opening dialogue, and file is
the file name specified in the $PATCH statement. The protection code is always
<124>. If any of these values is to be changed, the new value is included as the
newname argument. Only those values that are different from the default must be
included. For example, if the file name is to be rvSYSTEM:file.BAC<232>, only the
protection code is different from the default, therefore the argument would be
<232>, for example, "$END <232>"
If you want to have a file compiled and stored on the system device instead of the
library device, use the newname option. PBUILD substitutes the system device and
PPN for the string rvSYSDSK:. For example, if the system device specified in the
opening dialogue is SYO:[1,2], the new name string rvSYSDSK:<232> results in the
file name SYO:[1,2]file.BAC<232>.

408

Additional System Installation-Related Programs

Sample PBUILD Command File

The PBUILD command file must reference the CPATCH file created in the section
"Creating the CPATCH Command File." You can create a new PBUILD file with the
required PBUILD commands, or you can insert the commands in an existing file. In
either case, use an editor to edit the file.
In the example, the CPATCH file for the first patch to QUMRUN was created. Now
the commands to reference this file are inserted in the PBUILD file (either new or
existing). The commands required are:
$PATCH QUMRUN
PA140G.OOl

$END

Because this is the first patch to QUMRUN, all three of the commands must be
added. If there were already existing patches to QUMRUN, you must add the
reference to the new patch before the $END statement of any previous patches to
QUMRUN. For example, if the second article concerning QUMRUN is also a patch
article, the CPATCH command file for that patch would be PA1406.002. A patch
already exists for this program (PA1406.001), therefore you insert PA1406.002
immediately before the $END statement in the .sequence of commands that apply the
previous patch. The resulting command sequence is:
$PATCH QUMRUN
PA140G.OOl
PA140G.002

$END

These commands cause PA1406.001 to be applied to QUMRUN. The file
PA1406.002 would be applied to the patched file resulting from first applying
PA1406.001.
If you want to include checksums, add the /CS:n switch after each patch file
reference. For example:
$PATCH QUMRUN
PA140G.001/CS:57315
PA140G.002/CS:1234S

$END

Error Messages
This section describes the errors that can occur when running the patching programs.
Error messages can originate either from the PBUILD program, Table E-3 or the
CPATCH program, Table E-4.

Additional System Installation-Related Programs

409

Errors can occur in PBUILD when:
• You enter information required to run the program but the information is
incorrect. In this case, PBUILD displays the incorrect input with a text error
message and prints the prompt requesting the input again.
• You enter an incorrect command in a command file. Errors occurring in
PBUILD while it is running from the command file are always fatal. PBUILD
prints the error message and return control to your keyboard monitor.
o CPATCH, which is run by PBUILD, attempts to apply an invalid CPATCH

command file as a patch to a program. The program will continue to run.
CPATCH error messages appear at the user's terminal. If they occur while running
under PBUILD, PBUILD continues to run. If they occur running CPATCH standalone, they may cause CPATCH to terminate execution.
Table E-3 lists the PBUILD error messages. When running CPATCH under PBUILD
using patch files supplied by DIGITAL, the first error message in Table E-3 should be
the only one which will ever occur.

410

Additional System Installation-Related Programs

Table E-3:

PBUILD Error Messages
Message and Meaning

MUST BE PRIVILEGED TO RUN PBUILD
An attempt was made to run PBUILD from a nonprivileged account.
?FILE NAME ERROR
This error indicates that a bad file name was found in the command file currently executing.
?BAD FILE NAME: <filename>
Filename does not follow proper syntax rules. This error can occur during the dialogue.
?<file string> NOT PERMITTED
File string is valid but contains a feature that is not permitted for the operation, such as wild card
characters, or a file name when only a device and PPN was expected.
FILE NOT FOUND: <filename>
The syntax of the file name is correct, but refers to a nonexistent file.
?<file string> ERR = <error number>
The file string is invalid for a reason other than the previous three error messages. The number
returned by the message represents the error number produced by the BASIC-PLUS run-time
system.
?COMMAND FILE MUST BE ON DISK
A command file name was entered with a device speCifier other than a file-structured disk.
Command files must be copied from the device to disk before running PBUILD.
?CAN'T COpy <filel> TO <file2>
<BASIC-PLUS error message>
Occurs after the message !COPYING TEMP FILE <filel> TO <file2>. PBUILD was attempting
to copy the source file from the current account to the permanent account. The copy failed for
the reason given in the BASIC-PLUS error message. The BASIC-PLUS errors that are most
likely are ?No room for user on device and ?Device not available. Others are various magnetic
tape errors or hardware 110 errors.
?FATAL ERROR NO. <error number> ON LINE <error line> LEAVING PROGRAM
The program was terminated by an unexpected error, which may indicate a system error or a
hardware failure. The error returns the BASIC-PLUS error number and line number.

Additional System Installation-Related Programs

411

Table E-4lists the CPATCH error messages.
Table E-4:

CPATCH Error Messages
Message and Meaning

?MISMATCH
Occurs when editing a version of the file that was not correct, for example, attempting to patch a
file that was already patched. When this happens, the patch is ignored, and the file is restored to
the state before attempting to apply the patch. The log file (or KB: if that is the log) shows the
cause of the mismatch by printing:

= cmd = > string
= log = > string!
?mismatch?
String is the contents of the command file that is the correct program response to the previous
command in the command file; string! is the actual program response produced. It can be a
verification message on a line that has been modified or a CPATCH error message, such as
?Srch fail when a string that was expected has been deleted.
This is a nonfatal error when running under PBUILD. PBUILD continues to run normally but the
source file used for any commands to follow will be the original, unmodified source.
$SRCH FAIL
The string searched for with the G command was not found.
?EOF
If the error occurs in response to the H command, it indicates that the string was not found, and
the source input file has been read to the end of file. If it occurs while running from a command
file, it indicates that an end of file occurred in the command file before an EX command was
encountered.

?BAD ARG FOR <command>
The argument provided with command is invalid for that command. For example, the L
command only permits 0 and 1 as valid arguments.
?BAD COM: <command>
Command is not a valid command string.
?CAN'T BE THE SAME <log> = <command>
Unless the log file and the command file are both the keyboard, they must be different files. If
they are not, this message is printed:
FATAL ERROR NO. <err> ON
LINE <error line>
LEAVING PROGRAM
The same as in PBUILD. However, err = 10 is possible in normal operation. That error number
indicates a protection violation, which can occur because CPATCH does not hcve to be run in a
privileged account.
?FATAL ERROR NO.<error number>ON LINE <error line> IN AUTOED
The same as above, however, the error occurred in the program AUTO ED which is chained to
by CPATCH. This error does not terminate CPATCH, however. It has the same effect as a
?Mismatch error, but it may still indicate the need for to send DIGITAL an SPR.
(continued on next page)

412

Additional System Installation-Related Programs

Table E-4:

CPATCH Error Messages (Cont.)
Message and Meaning

?Please 'RUN CPATCH'
An attempt was made to run AUTOED as a stand-alone program.
?<file string> NOT PERMITTED
?BAD FILE NAME: <file string>
?<file string> ERR = <error number>
?FILE NOT FOUND
?CAN'T COpy <file 1 > TO <file2>
These messages have the same meaning as they do for PBUILD: see Table E-3.

Additional System Installation-Related Programs

413

RSTS/E V9.0 supports many types of mixed disk configurations. Usually, each type of
disk requires a separate controller. Frequently, however, similar disks may share the
same controller. The following sections describe the level of support for each possible
disk combination.

Mixing RP04/RPOS/RP06 Drives on the Same Controller
The RP04/RP05/RP06 drives all use the RH11 interface (RH70 for PDP-11/70s). You
can mix up to eight of these drives on a given controller, as long as each drive in the
combined set has a unique drive number. The RSTS/E monitor distinguishes which
type of disk is on a given controller and uses it appropriately. The RP05 is
functionally identical to the RP04.

Mixing RK06 and RI{07 Drives on the Same Controller
The RK06 and RK07 drives use the RK611 and RK711 controllers. You can mix up
to eight of these drives on a given controller, as long as each drive in the combined
set has a unique drive number. The RSTS/E monitor distinguishes which type of disk
is on a given controller and uses it appropriately. (Some older RK611 controllers
need an ECO to have this capability.)

Mixing RL01 and RL02 Drives on the Same Controller
The RL01 and RL02 drives use the RL11 controller. You can mix up to four of these
drives on a given controller, as long as each drive in the combined set has a unique
drive number. The RSTS/E monitor distinguishes which type of disk is on a given
controller and uses it appropriately.

415

Mixing RM02/RM03/RMOS/RM80 Drives on the Same Controller
The RM02, RM03, RM05, and RM80 disks are very similar to the RP04, RP05, and
RP06 disks. They also use the RH controllers. The RM02 disk uses the RH70 (for ..
PDP-II/70s) or the RH11 interface (for other PDP-lIs). The RM03, RM05, and
RM80 disks only use the RH70 interface and are supported only on PDP-11170
systems.
On a PDP-11/70 system, RM02, RM03, RM05, and RM80 disks may share the same
RH70 controller. You can mix up to eight of these drives on a given controller, as
long as each drive in the combined set has a unique drive number. The RSTS/E
monitor distinguishes which type of disk is on a given controller and uses it
appropriately.

Mixing RM02/RM03/RMOS/RM80 and RP04/RPOS/RP06 Drives on Separate
Controllers
To use both the RM and RP disks on a single system configuration, DIGITAL
recommends using a separate RH controller for each kind of disk. The normal
arrangement is to have the RH controller for the RP disks at the standard CSR
address of 176700 and the RH controller for the RM disks at the nonstandard CSR
address of 176300. However, with this arrangement you cannot bootstrap the RM
disks with any hardware bootstraps, although you can use the BOOT option of
INIT.SYS.
If you would rather use the hardware bootstrap with the RM disks, you should
reverse the CSR assignments so that the RP disk controller is at the nonstandard
address (176300) and the RM disk controller is at the standard address (176700).

Note that if the hardware bootstrap requires you to type a device name at the
console keyboard, typing either DB (the name used for RP disks) or DR (the name
used for RM disks) will bootstrap a disk controlled through the standard CSR address,
regardless of which type it actually is. However, most bootstraps require that you type
DB, regardless of the actual type of drive.

Mixing RM02/RM03/RMOS/RM80 and RP04/RPOS/RP06 Drives on the Same
Controller
It is possible to mix RM02/RM03/RM05/RM80 drives with RP04/RP05/RP06 drives
on the same RH controller. Up to eight drives are allowed per RH, and each drive
must have a unique drive number. The monitor knows which type of disk is on a
given drive and uses it appropriately. Note that RM03, RM05, and RM80 disks are
supported only on PDP-II/70s.
The unusual aspect of this arrangement is the device naming scheme. The lowest
numbered drive on the RH determines whether all drives on this RH are known as
DBn: or DRn:. For example, if the lowest numbered drive is an RP04, RP05, or
RP06, then the device name DB is used for all drives. If the lowest numbered drive is
an RM02, RM03, RM05, or RM80, then the device name DR is used for all drives.

416

Mixed Disk Drives on the Same Controller

The RSTS/E monitor can determine the identity of the disks, although the naming
scheme is not obvious.

Multiple RH Controllers for the Same Type of Disk
RSTS/E supports two similar RH controllers on the same system. These two RH
controllers can both be controlling the same kind of disk, either RP or RM. Only one
of these two RH controllers can be at the standard CSR address. The other controller
must be at the nonstandard CSR address. Each RH can control up to eight drives,
giving a possible combined total of 16 drives.
The naming scheme for the above arrangement is as follows: the drives interfaced at
the standard CSR address are known by the device name that corresponds to the
lowest numbered drive type (DB or DR). The drives interfaced at the nonstandard
CSR addresses are known by the other name.

Random Mixing of RP and RM Disks on Multiple Controllers
RSTS/E supports two RH controllers with a combination of RP and RM disks on both
RH controllers. If the respective lowest numbered drives on the two RH controllers
are of different types, then the previous rule of "lowest numbered drive determines
the device name" applies. If both lowest numbered drives are of the same type, then
the deciding rule is: the RH at the standard CSR address gets the device name that
corresponds to the lowest numbered drive type, and the RH at the nonstandard CSR
address gets the other device name.

Booting Mixed RM02/RM03/RMOS/RM80 and RP04/RPOS/RP06 Disks
RSTS/E supports mixed RP and RM disks combinations as described in the previous
section. However, you can hardware boot disks only at the primary controller address
(176700). You can use the INIT.SYS BOOT option to boot all disks.

Avoiding Bootstrap Conflicts
Because of possible bootstrap conflicts, DIGITAL does not recommend configuring
systems that contain both RP03 and secondary CSR RHl1170 disk drives.

Mixed Disk Drives on the Same Controller

417

A kit
contents, 12
type of RSTS/E distribution kit, 12
AC line frequency, 212
50 Hz, 212
60 Hz, 212
specifying, 283
Accept defaults?
explanation, 41
general configuration question, 41
possible responses, 42
Accept defaults? (update)
explanation, 172
general configuration question, 172
possible responses, 172
Accept Disk defaults?
disk interface configuration question, 50
explanation, 50
possible responses, 50
Accept Peripheral defaults?
explanation, 55
peripheral interface configuration question, 55
possible responses, 55
Accept Software defaults?
explanation, 64
possible responses, 64
software configuration question, 64
Accept Terminal defaults?
explanation, 43
possible responses, 44
terminal interface configuration question, 43

Account [0,1]
directory listing, 357
Account [1,2]
setting password on update, 182
Account base?
DSKINT question, 29, 257
explanation, 29, 257
possible responses, 29, 257
use with accounts [1,1] and [1,2], 29, 257
use with system disk, 29
Account creation
using CREATE/ACCOUNT command 102
104
'
,
Address space
gap, 345
Any memory allocation changes?
explanation, 328
possible responses, 328
START question, 328
Automatic answer dataset
supporting, 46, 47
Auxiliary Library package
directory listing, 362
Auxiliary run-time system
definition, 2
number of general small buffers, 243
use of general small buffers, 243

BACKUP program
comparison with SAVRES, 309
number of general small buffers, 246

Index-1

Bad block file (BADB.SYS)
adding blocks, 307
definition, 23, 251
Bad blocks
during RESTORE, 316
BADB.SYS
adding blocks, 307
BADS, REFRESH suboption, 307
Bads?
BADS question, 307
explanation, 307
possible responses, 307
Base?
possible responses, 306
REFRESH FILE question, 305
BASIC-PLUS
FPP feature, 91
installing, 90
log functions feature, 91
math precision question, 91
matrices feature, 92
optional features, 90t
patches to library programs, 392
print using feature, 92
string arithmetic feature, 92
trig functions feature, 91
BASIC-PLUS package
directory listing, 361
BASIC-PLUS RTS name?
explanation, 90
installation question, 90
possible responses, 91
BASIC-PLUS run-time system
size constraints, 90
supplied by DIGITAL, 2
Binary code
ONLPAT patching, 386, 387
Block number?
possible responses, 307
REFRESH BADS question, 307
BM792-YB loader, 370
how to bootstrap with, 370
BM873 restart/loader, 370
how to bootstrap with H324
pushbutton panel, 370
BM873-YA restart/loader, 369
how to bootstrap with, 369
BM873-YB restart/loader, 369
how to bootstrap with, 369
BOOT
BOOT error messages, 205t
INIT.SYS program option, 205
Boot device:
BOOT prompt, 205

Index-2

Boot device: (Cont.)
possible responses, 205
Boot unit:
BOOT prompt, 205
possible responses, 205
Bootstrap
definition, 15
instructions in example installation, 15
Bootstrap record
definition, 15, 365
BUFF.SYS file
creating during installation, 80
creating during update, 183
definition, 296
location, 296
size, 296
status, 296
BUFFERS
memory allocation table suboption, 237
use with data space, 238
BUILD
install run-time system, 394
preprocessing phase, 394
privileges required, 383
running, 383
terminal output, 396, 398
BUILDIPATCH program, 383

c
Card decode?
explanation, 57
peripheral devices configuration question, 57
possible responses, 58
CCL command definitions
number of FIP small buffers, 243
number of general small buffers, 243
use of FIP small buffers, 243
use of general small buffers, 243
CD 11 card reader?
explanation, 57
peripheral devices configuration question, 57
possible responses, 57
Central processor unit console switches
bootstr~pping a device, 366
Checksurn
CPATCH, 405
creation, 405
example of CPATCH, 405
Cluster size?
/
DSKINT question, 29, 256, 257
explanation, 29, 256, 257

Cluster size? (Cont.)
possible responses, 29, 256, 257
use with account [1,1], 29, 256
use with account [1,2], 29, 257
use with system disk, 29
Cluster sizes
device cluster sizes and total device sizes, 27t,
255t
for disk packs, 26t, 253t
Cluster
definition, 25
Command file
building for ONLPAT, 390
create CPATCH, 398
modifying, for patches, 391
PBUILD, 405
sample PBUILD, 409
statements (CPATCH), 408
using indirect, 406
Command file mode
using ONLPAT in, 386
Command format
for SHUTUP, 108, 154, 190
Configuration questions
definition, 37
explanation of default responses, 37
Configuration rules
recommendation, 345
Configure a monitor
definition, 37
Console emulator
activating hardware bootstrap loader, 365
to bootstrap a device, 366
Console switch register
explanation, 284
settings, 379t
using, 284
Console terminal
definition, 14, 15
Contents of messages
number of general small ,buffers, 244
use of extended buffers, 244
use of general small buffers, 244
Control characters
CPATCH, 401
Control status register (CSR) set
definition, 275
Controller .
booting mixed RM and RP type disks, 417
disabling, 270
enabling, 273
resetting CSR address to standard, 280
resetting vector address to standard, 280
specifying nonstandard controller address, 275

Controller (Cont.)
specifying nonstandard vector address, 277
support of mixed RK06 and RK07 disks, 415
support of mixed RL01 andRL02 disks, 415
support of mixed RM and RP type disks, 416
support of mixed RM and RP type disks on
multiple, 417
support of mixed RM02/RM03/RM05/RM80
disks, 416
support of mixed RP04/RP05/RP06 disks, 415
support of mixed type drives, 415
Controller names
example list, 270
Controller to disable?
explanation, 270, 271
HARDWR DISABLE question, 270, 271
possible responses, 270, 271
Controller to enable?
explanation, 273
HARDWR ENABLE question, 273
possible responses, 273
Controller with non-standard address?
explanation, 275
HARDWR CSR question, 275
possible responses, 275
Controller with non-standard vector?
explanation, 278
HARDWR VECTOR question, 278
possible responses, 278
Controller, RH
support of multiple for same type disks, 417
Converting disk formats
with DSKCVT, 384
COPY
error messages, 164t, 208t
Core memory
with interleaved parity memory, 218
CPATCH
checksum, 405
command file, 398
control characters, 401
creating command files, 398
ICS switch, 404, 405, 409
edit with, 401
editing with, 399
editor, 399
editor commands, 401 to 404
error messages, 409, 410, 41lt
file naming convention, 398
patch complete message, 405
patches for source code, 392
patching with, 396, 398
prompt, 398
prompt response, 398

Index-3

CPATCH (Cont.)
recalculate checksum, 405
running stand alone, 410
verify patching, 404
verify patching example, 405
CPU switch register
specifying, 284
CPU switches
activating hardware bootstrap loader, 15, 160,
365
CR111CM11 card reader?
explanation, 57
peripheral devices configuration question, 57
possible responses, 57
Crash dump?
explanation, 114, 328
for RSTS/E monitor, 114, 328
CRASH.SYS file
creating during installation, 114
definition, 297
disabled by system, 114
location, 297
size, 297
status, 297
CREATE/ACCOUNT command
creating accounts, 102, 104
Crystal oscillator
use with KW1I-P programmable real-time
clock, 213
/CS switch
CPATCH, 404, 405, 409
CSR
HARDWR suboption, 275
CTRL/C
abort patching (ONLPAT), 387
to terminate a patch, 387
CTRLIT
one-line status report, 49
CTRL/Z
in ONLPAT, 387
to CPATCH, 392
CUSP (Commonly Used System Program)
See also System program
patches to, 398

Data caching
comparing with directory caching, 66
definition, 66, 234
number of extended buffers, 234
use with extended buffers, 234

Index-4

Data caching?
explanation, 66
possible responses, 66
software tuning configuration question, 66
Data space
creating general small buffer pool, 241
definition, 241
with BUFFERS sub option, 238
Dataset support for DH1l' s?
explanation, 45
possible responses, 46
terminal interface configuration question, 45
Dataset support for DHUIl1DHVl1's?
explanation, 47
terminal interface configuration question, 47
Dataset support for DZ111DZV111DZQ1l's?
explanation, 46
possible responses, 47
terminal interface configuration question, 46
DATE
INIT.SYS program option, 209
Date
how to change, 209
Date last modified?
DSKINT question, 30, 257
explanation, 30, 257
possible responses, 30
use with system disk, 30
DCL run-time system
supp~ied by DIGITAL, 2
DDCMP line protocol
implemented by DMC11, 58
implemented by DMP11, 59
implemented by DMRll, 58
implemented by DMVll, 59
DECnet network support?
explanation, 58
peripheral devices configuration question, 58
possible responses, 58
DECnetiE software
definition, 58
installing, 80
mounting installation media, 80
mounting installation media for update, 183
updating, 183
use of extended buffers, 235
DECtape system
definition, 56
DECtapes?
explanation, 56
peripheral devices configuration question, 56
possible responses, 56

DEFAULT
DEFAULT and memory allocation table error
messages, 214t
INIT.SYS program option, 211
questions, 211
Default line frequency
60 Hz, 283
Default response
definition, 25
Deletable?
explanation, 306
possible responses, 306
REFRESH FILE question, 306
Delimiter
definition, 49
/DETACH switch
PBUILD, 393
Detached job
affecting number of jobs, 62
definition, 62
run with BUILDIPATCH, 384
Device designator, 16t, 377t
definition, 16
Device Testing package
directory listing, 359
Device vector assignments, 353t
Devices
with fixed addresses, 355
with fixed addresses and vectors, 355t
with fixed vectors, 355
DH for DMO?
explanation, 281
HARDWR OM question, 281
possible responses, 282
DH11 multiplexer
address considerations, 346
connected to DMII-BB modem controller, 281
declaring DM11-BB modem associations, 281
definition, 45
rules for connecting, 281
DH11 unit 00 lines enabled?
explanation, 45
possible responses, 45
terminal interface configuration question, 45
DH11's?
explanation, 45
possible responses, 45
terminal interface configuration question, 45
DHU111DHV11 unit lines enabled?
explanation, 47
possible responses, 47
terminal interface configuration question, 47
DHU111DHV11?
explanation, 47

DHU11/DHV11? (Cont.)
possible responses, 47
terminal interface configuration question, 47
Dial-up terminal
affecting number of jobs, 62
Directory caching
amount of memory to extended buffer pool,
234
definition, 234
use of extended buffers, 234
Directory listing
account [0,1], 357
AUxiliary Library package, 362
BASIC-PLUS package, 361
Device Testing package, 359
EDT package, 361
Error Reporting package, 359
File Restore package, 359
Help package, 358
OPSER-based Spooling package, 360
Print/Batch Services package, 359
RMS-11 package, 361
RSX Utilities package, 363
SORT/MERGE package, 362
SYSGEN components, 361
System Library package, 363
system program packages, 357
TECO package, 362
Unsupported Utility package, 360
DISABLE
HARDWR suboption, 270
meaning, 285
switch register position, 284
Disk
bootstrapping with BOOT, 205
calculating center, 300
converting to RDS1.2 format, 384
copying files, 207
copying to one that contains bad blocks, 309
copying with IMAGE, 323
creating bootable system, 309
creating fast copy, 309
device designators, 17t, 16lt
example of DSKCVT conversion, 385
for SAVE set, 309
formatting RP02/RP03, 33
IMAGE output as system, 323
initializing, 251
legal with IMAGE, 323
mixing different types on controller, 415
mount instructions, 15, 158
restoring, 316
Disk units configuration questions
definition, 50

Index-5

Disk?
DSKINT question, 23, 251
explanation, 24, 302
possible responses, 24, 251,302
REFRESH question, 302
use with system disk, 24
Distribution disk
disk mount session, 15
Distribution kit
collecting, 12
order numbers, 13
types, 12
use of RSTS/E Release Notes, 13
DJ11 multiplexer
definition, 45
reserved address, 346
DJ11 unit lines enabled?
explanation, 45
possible responses, 45
terminal interface configuration question, 45
DJ11's?
explanation, 45
possible responses, 45
terminal interface configuration question, 45
DL11A compatible lines?
explanation, 44
possible responses, 44
terminal interface configuration question, 44
DL11A single-line interface
definition, 44
DL11C single-line interface
definition, 44
DL11C,DL11D's?
explanation, 44
possible responses, 44
terminal interface configuration question, 44
DL11D single-line interface
definition, 44
OLlIE single-line interface
definition, 44
DL11E,DLV11E's?
explanation, 44
possible responses, 44
terminal interface configuration question, 44
DLV11E single-line interface
definition, 44
OM
HARDWR suboption, 281
DM11-BB modem
declaring DH11 associations, 281
to connect DH11 multiplexer, 45
DM11-BB modem controller
connected to DH11 multiplexer, 281
rules for connecting, 281

Index-6

DM11-BB modem controller (Cont.)
using, 281
DMC11 line interface
implementing DDCMP line protocol, 58
DMC11's/DMR11's?
explanation, 58
peripheral devices configuration question, 58
possible responses, 59
DMP11 line interface
implementing DDCMP line protocol, 59
DMR11 line interface
implementing DDCMP line protocol, 58
DMV11 line interface
implementing DDCMP line protocol, 59
DMV11' s/DMP11' s?
explanation, 59
peripheral devices configuration question, 59
possible responses, 59
DMV111DMP11 unit tributaries?
explanation, 59
peripheral devices configuration question, 59
possible responses, 59
Double-precision
BASIC-PLUS scaled arithmetic feature, 91
DSKCVT program
convert disk formats, 384
example, 385
running, 384
using in system upgrade, 140
work space requirements, 384
DSKINT
checking for bad blocks, 23, 251
error messages, 34t, 26lt
formatting disks, 23, 251
formatting RP02 or RP03 disks, 260
INIT.SYS program option, 23, 251
initializing disks, 23, 251
writing minimum RSTS/E file structure, 23, 251
0211 multiplexer
definition, 46
models, 46
using with RSTS/E UNIBUS PDP-II, 46
D211-A
multiplexer model, 46
support of automatic datasets, 46
D211-B
multiplexer model, 46
support of automatic datasets, 46
D211-C
multiplexer model, 46
nonsupport of automatic datasets, 46
0211-0
multiplexer model, 46
nonsupport of automatic datasets, 46

DZ111DZV111DZQ11 unit lines enabled?
explanation, 46
possible responses, 46
terminal interface configuration question, 46
DZ111DZV111DZQ11 's?
explanation, 46
possible responses, 46
terminal interface configuration question, 46
DZQ11 multiplexer
definition, 46
support of automatic answer datasets, 46
using with RSTS/E Q-BUS PDP-II, 46
DZV11 multiplexer
definition, 46
support of automatic answer datasets, 46
using with RSTS/E Q-BUS PDP-II, 46

:E
ECC MOS memory, 218
Echo control
definition, 48
Echo control?
explanation, 48
possible responses, 48
terminal interface configuration question, 48
EDT editor
definition, 69
to edit contents of START.COM, 106
EDT package
directory listing, 361
EMT logging
definition, 65
number of general small buffers, 245
use of general small buffers 245
EMT logging?
'
explanation, 65
possible responses, 66
software tuning configuration question 65
ENABLE
'
HARDWR suboption, 273
meaning, 285
switch register position, 284
END statement
example, 409
PBUILD, 406, 408
Enter new extended buffer address size?
XBUF question, 229
Enter new virtual disk size?
explanation, 248
possible responses, 248
VIRTUAL question, 248

Erase disk?
DSKINT question, 32, 259
explanation, 32, 259
possible responses, 32, 259
ERR.SYS file
creation, 300
definition, 300
location, 300
size, 300
status, 300
ERRCPY
definition, 62
Error messages
CPATCH, 410, 41lt
PBUILD, 41lt
Error Reporting package
directory listing, 359
Errors
checking in software updates, 122
in PBUILD, 410
Example installation
characteristics, 5
dialogue summary, 123 to 133
explanation, 5
memory allocation table, 113
parity memory configuration, 219
parity register usage, 219
sample SHUTUP output, 109
type of installation kit, 14
Extended buffer
definition, 230
number for data caching, 234
number for line printers, 234
storage of contents of messages, 244
use of indirect command file 110, 235
use with data caching, 234
use with directory caching, 234
use with line printers, 234
use with system logicals, 235
use with terminal logging, 235
Extended buffer address range is?
explanation, 229
possible responses, 229
Extended buffer pool
amount of memory for directory caching, 234
definition, 60, 230, 241
for example installation, 231f
guidelines for allocating memory, 233
items stored in, 233
minimum allocation for data caching, 66
reserving memory, 229
storage of line printer characters, 245
using with line printer, 60
worksheet, 236f

Index-7

Extended buffering for LP?
explanation, 60
peripheral devices configuration question, 60
possible responses, 60
Extended data buffering
See also data caching
definition, 66

F
FILE
REFRESH suboption, 305
File
bad cluster while transferring contiguous, 316
changing characteristics, 305
PBUILD command lines to patch, 406
File name?
explanation, 305
possible responses, 305
REFRESH FILE question, 305
File Restore package
directory listing, 359
File status table
definition, 302
example, 302
explanation, 303
listing, 302
File status table item
. current file size, 304
file flags, 303
file name, 303
file status, 304
minimum file size, 304
required files, 303
start logical block number, 304
FIP small buffer
definition, 65, 241
items stored in, 242
number for CCL command definitions, 243
number for open files, 244
storage of CCL command definitions, 243
storage of open files information, 243
use with update mode, 244
FIP small buffer pool
definition, 241
reserving memory, 237
types, 241
Floating address devices
rules, 345
Floating address worksheet
aid to assign floating addresses, 346
explanation, 347

Index-8

Floating address worksheet (Cant.)
how to use; 347
Floating addresses
assigning, 346
definition, 345
Floating point processor
definition, 91
Floating vector
definition, 345
explanation, 353
FMS-11 software kit, 49
FMS-11 support?
explanation, 49
possible responses, 49
terminal interface configuration question, 49
FORCE statement
PBUILD, 406, 407
Format?
considerations for specifying 0, 32, 259
DSKINT question, 31, 258
explanation, 31, 258
possible responses, 31, 32, 259
use with system disk, 31, 258
Forms Management System (FMS-11)
definition, 49
FPP?
BASIC-PLUS configuration question, 91
explanation, 91
'
possible responses, 91

G
Gap length
determination, 346
General and FIP small buffer
pools, 240f
General small buffer
critical to system performance, 242
definition, 65, 241
items stored in, 241, 242
minimum number, 242, 246
number for aUxiliary run-time systems, 243
number for BACKUP program, 246
number for CCL command definitions, 243
number for contents of messages, 244
number for dynamic regions, 243
number for EMT logging messages, 245
number for line printer characters, 245
number for message receivers list, 244
number for messages waiting to be received,
244
number for open files, 244

General small buffer (Cont.)
number for outstanding 110 requests, 245
number for paper tape reader characters, 245
number for resident libraries, 243
number for sent messages, 244
number for terminal information, 245
number per job, 243
storage of auxiliary run-time systems, 243
storage of CCL command definitions, 243
storage of contents of messages, 244
storage of EMT logging messages, 245
storage of line printer characters, 245
storage of message receivers list, 244
storage of messages waiting to be received,
244
storage of open files information, 243
storage of paper tape reader characters, 245
storage of resident libraries, 243
storage of sent messages, 244
storage of terminal-related information, 245
use with jobs, 243
General small buffer pool
created from data space, 241
created from Small buffers? question, 241
definition, 241
reserving memory, 237

H
H kit
contents, 12
type of RSTS/E distribution kit, 12
H324 pushbutton panel option
with BM873 restartlloader, 370
Hardware bootstrap addresses, 368t
Hardware bootstrap loader
BM792-YB loader, 370
BM873-YA restartlloader, 369
BM873-YB restartlloader, 369
definition, 15
M9301-YA bootstrap terminator, 371
M9301-YB, 371
M9301-YC bootstrap, 371
M9301-YF bootstrap terminator, 372
M9312 bootstrap terminator, 374
M9312 console emulator, 374
MRII-DB bulk storage loader, 370 '
Hardware configuration table
definition, 265
example, 265
explanation, 265
listing, 265

Hardware-related tasks
HARDWR suboptions, 263
HARDWR
error messages, 264t
explanation of messages, 272
hardware comments, 267t
hardware configuration summary, 268t
INIT.SYS program option, 263
list of messages, 272
to declare nonstandard address assignments,
345
to declare nonstandard vector assignments, 345
HARDWR suboption?
CSR question, 275
DISABLE question, 270
OM question, 281
ENABLE question, 273
explanation, 280, 283
HERTZ question, 283
possible responses, 270, 273, 275, 278, 280,
281,283,284
RESET question, 280
SWITCH question, 284
VECTOR question, 278
HARDWR suboptions
CSR, 275
DISABLE, 270
DM,281
ENABLE, 273
HERTZ; 283
LIST, ·265
list, 263
RESET, 280
SWITCH, 284
VECTOR, 278
Help package
directory listing, 358
HERTZ
HARDWR suboption, 283
How many K-words of extra buffer space?
BUFFERS question, 237
explanation, 238
possible responses, 238

I&D versions of tasks?
explanation, 71
general configuration question, 71
possible responses, 71
I&D versions of tasks? (update)
explanation, 175

Index-9

1&0 versions of tasks? (update) (Cont.)
general configuration question, 175
possible responses, 175
IDENT
INIT.SYS program option, 287
IDENTIFY
dialogue, 321
example, 321
extracting pack 10, 321
SAVRES function, 321
IMAGE
dialogue, 323
example, 323 to 326
output from, as system disk, 323
SAVRES function, 323
Indirect command file 1/0
use of extended buffers, 235
INIT.SYS program
determination of interrupt vectors, 345
performing hardware configuration check, 345
update questions, 162 to 163
use of memory, 232, 250
INIT.SYS program options
BOOT, 205
COPY, 207
DATE, 209
DEFAULT, 211
DSKINT, 23, 251
HARDWR, 263
IDENT, 287
PATCH, 289
REFRESH, 293, 305
START, 112, 113, 192, 193,327
summary,203t
used in upgrade system installation, 133
Initialization code error
messages, 332t
Initialization code, See INIT.SYS program
INSTAL.COM command file
command format, 142
definition, 39
entry points, 142, 143t
in updates, 168
preliminary questions, 39
using, 39
using to build another monitor, 141
using to install full system, 141
using to install layered product updates, 141
using to install system programs, 141
INSTAL. LOG
installation log file, 39, 89, 93, 99
Installation disk
bootstrapping, 15
bootstrapping for update, 160

Index-10

Installation disk (Cont.)
disk mount session, 158
mounting, 15
mounting for update, 158, 160
Installation Kit
contents, 12
updating a V9.0 system, 147
using for system installation, 12
Installation questions
for layered product updates, 74
for system programs, 70
Installation tape
bootstrapping, 15
bootstrapping for update, 158, 160
mounting, 15
mounting for update, 158, 160
Interleaved parity memory
definition, 218
Interrupt frequency?
DEFAULT question, 213
explanation, 213
for RSTS/E monitor, 213
possible responses, 213

J
Job
calculating number, 62
calculation worksheet, 63f
definition, 62
detached, 62
event-driven, 297
highly interactive, 296, 297
items used in calculating number of, 62
maximum number, 63, 65
total number in example installation, 63
use of general small buffers, 243

Keyboard mode
ONLPAT procedures, 389
using ONLPAT in, 386
KMC IBM protocol support?
explanation, 59
peripheral devices configuration question, 59
possible responses, 60
KMC-ll microprocessor
attached to PDP-II UNIBUS, 59
controlling 2780/3780 IBM protocol emulator,
59

KMC-ll microprcessor (Cont.)
controlling 3271 IBM protocol emulator, 59
controlling DUPll line interface, 60
definition, 59
emulating IBM 3271 protocol, 59
KMCll's?
explanation, 59
peripheral devices configuration question, 59
possible responses" 59
KWII-L line time clock
definition, 212
KWII-P programmable real-time clock
crystal oscillator, 213
definition, 212

Layered product
definition, 3, 74, 178
examples, 3
transferring updates, 74, 178, 186 to 187
Layered product update questions, 178 to ·179
Library Kit
contents, 12
mounting during installation, 87
Library programs
patches to BASIC-PLUS, 392
Line printer
number of extended buffers, 234
types, 56
use of extended buffers, 234
Line printer characters
number of general small buffers, 245
use of extended buffer pool, 245
use of general small buffers, 245
LIST
HARDWR suboption, 265
memory allocation table suboption, 216
. REFRESH suboption, 302
LOCK
memory allocation table suboption, 220
Lock address is?
explanation, 220
LOCK question, 220
possible responses, 220
Log file
creating with BUILDIPATCH, 384
INSTAL. LOG, 39, 89, 93, 99
UPDATE. LOG, 168, 187
Log functions?
BASIC-PLUS configuration question, 91

Log functions? (Cont.)
explanation, 91
possible responses, 91

M
M9301-YA and M9301-YB device
codes,371t
M9301-YA bootstrap terminator, 371
M9301-YB bootstrap terminator, 371
how to bootstrap with, 371
M9301-YC bootstrap, 371
how to bootstrap with, 371
M9301-YC device codes, 372t
M9301-YF bootstrap terminator, 372
how to bootstrap with, 372
M9301-YF device codes, 373t
M9312 bootstrap
how to bootstrap with ROM configuration, 378
M9312 bootstrap module
description, 373
use of ROM configuration, 373
M9312 bootstrap ROM configuration, 376t
how to determine, 375
M9312 bootstrap terminator, 374
how to bootstrap with, 374
M9312 console emulator, 374
how to bootstrap with, 374
pushbutton boot procedure, 374
switch register boot procedure, 374
M9312 ROM arrangement, 373f
M9312 ROM configuration
how to determine, 375
Magnetic tape
bootstrapping with BOOT, 205
device designators, 16t, 161 t
for Save set, 309
mount instructions, 14, 158
Mandatory patch
definition, 122
Manual patch
disadvantages, 122
if you make a mistake, 122
when to apply, 122, 163
Master File Directory (MFD),
definition, 26
MAT statements
with BASIC-PLUS, 92
Math precision
with BASIC-PLUS, 91
Math precision?
BASIC-PLUS configuration question, 91

Index-11

Math precision? (Cont.)
explanation, 91
possible responses, 91
Matrices?
BASIC-PLUS configuration question, 92
explanation, 92
possible responses, 92
Maximum jobs?
explanatiori, 64
possible responses, 65
software tuning configuration question, 64
Memory
allocating to extended buffer pool, 232
allocating to virtual disk, 249
example of cache parity error, 222
extended buffer pool, 230, 241
four examples of memory failure, 222
list of lock restrictions, 221
locking, 220
monitor, 230, 239
nonvolatile, 284
parity, 219
run-time system, 230,241
unlocking, 223
USER, 230, 241
Memory allocation table
definition, 216
explanation, 216 .
for example installation, 113, 216
for RSTS/E monitor, 113, 193, 212
how to adjust, 212
how to reset, 227
listing, 216
printed by BUFFERS, 237
printed by DEFAULT, 212
printed by LIST, 216
use with START, 328
Memory allocation table suboptions
BUFFERS, 237
LIST, 216
LOCK, 220
PARITY, 219
RESET,227
RTS,225
summary, 215
UNLOCK, 223
VIRTUAL, 248
XBUF, 230
Memory sub option?
DEFAULT question, 229
explanation, 229
use with XBUF, 229
Message send/receive code
number of extended buffers, 233

Index-12

Message send/receive code (Cont.)
use of extended buffers, 233
Messages waiting to be received
number of general small buffers, 244
use of general small buffers, 244
MFD cluster size
definition, 26
size considerations, 26, 254
MFD cluster size?
DSKINT question, 26, 254
explanation, 26, 254
possible responses, 27, 254
use with system disk, 26
Modem, DMII-BB
declaring DHll associations, 281
Modulo 10
use with DJll multiplexer, 346
Modulo 20
use with DHll multiplexer, 346
Monitor
building, 82 to 84
building an updated, 184
building online, 141
configuring, 37 to 66
install SIL, 390
overlay code patches, 390
patches to overlay code, 390
patching running, 390
patching with ONLPAT, 390
size restrictions, 185
SYSGEN, 35
upgrading, 133 to 140
Monitor memory
definition, 230, 239
Monitor name?
explanation, 327
general configuration question, 41
possible responses, 41, 327
START question, 327
Monitor name? (update)
explanation, 165
general configuration question, 171
possible responses, 165, 172
START question, 165
Monitor statistics
definition, 65
support with DIGITAL consultation contract, 65
Monitor statistics?
explanation, 65
possible responses, 65
software tuning configuration question, 65
MRII-DB bulk storage loader, 370
how to bootstrap with, 370

MSCP controller
restriction on RJ2780 support, 60
types, 54
MSCP controllers?
disk units configuration question, 54
explanation, 54
possible responses, 54
Multi-terminal service
definition, 48
Multi-terminal service?
explanation, 48
possible responses, 48
terminal interface configuration question, 48
Multiple parity errors
example, 222
Multiple private delimiters
definition, 49
Multiple private delimiters?
explanation, 49
possible responses, 49
terminal interface configuration question, 49
Multiplexer, DHll
declaring DMII-BB modem associations, 281

New AC line hertz?
explanation, 283
HARDWR HERTZ question, 283
possible responses, 283
New controller address?
explanation, 276
HARDWR CSR question, 275
possible responses, 276
New files first?
DSKINT question, 30, 257
explanation, 30, 258
possible responses, 30, 258
use with system disk, 30
New monitor name?
explanation, 41
New monitor name? (update)
explanation, 172
New Run Time System address is?
explanation, 225
possible responses, 225
RTS question, 225
New SWAP MAX?
explanation, 211
for RSTS/E monitor, 211
possible responses, 211

New vector address?
explanation, 279
HARDWR VECTOR question, 278
possible responses, 279
Nonparity memory, 218
Nonsystem disk
definition, 19
Nonvolatile memory
definition, 284
Number of disks on DB controller?
disk units configuration question, 53
explanation, 53
possible responses, 53
Number of disks on DR controller?
disk units configuration question, 52
explanation, 52
possible responses, 52

o
One-line status report?
explanation, 49
possible responses, 49
terminal interface configuration question, 48
Online explanations, 6
Online system installation
definition, 3
example, 144 to 145
privileges reqUired, 141
restriction, 141
to build another monitor, 141
to install full system, 141
to install layered product updates, 141
to install system programs, 141
ONLPAT
command file log, 390
creating command files, 390
dialogue questions, 387t
in command file mode, 386, 387
in keyboard mode, 386
keyboard mode procedures, 389
patching a running monitor, 390
responses to questions, 387t
running, 389
up-arrow/C and CTRL/C, 389
Open files
number of FIP small buffers, 244
number of general small buffers, 244
use of FIP small buffers, 243
use of general small buffers, 243
OPSER-based Spooling package
directory listing, 360

Index-13

Optional software
DECnetlE, 58
definition, 3, 178
examples, 3
job number considerations, 62
Optional software kit
examples, 12
using for system installation, 12
3271 or 2780/3780 simultaneous links?
explanation, 60
peripheral devices configuration question, 60
possible responses, 60
Outstanding I/O requests
number of general small buffers, 245
Overlapped seek driver
definition, 51, 52
Overlapped seek?
disk units configuration question, 51, 52, 53
explanation, 51, 52, 53
possible responses, 51, 52,53
use with RK05 disk, 51
use with RK06/RK07 disk, 51
use with RLOllRL02 disk, 51
use with RM02/RM03/RM05/RM80 disk, 52
use with RP02/RP03 disk, 52
use with RP04/RP05/RP06 disk, 53
OVR.SYS file
creation, 300
definition, 300
location, 300
size, 300
status, 300

P. T. reader/punch?
explanation, 58
peripheral devices configuration question, 58
possible responses, 58
Pack cluster size
considerations, 25, 252
definition, 25
Pack cluster size?
DSKINT question, 25, 252
explanation, 25, 252
possible responses, 25, 253
use with system disk, 25, 252
Pack 10
definition, 25
extracting with SAVRES, 321
Pack ID?
DSKINT question, 24, 252

Index-14

Pack ID? (Cont.)
explanation, 24
possible responses, 25
use with system disk, 24
Pack label information
definition, 24
printed by DSKINT option, 24, 252
Packages to update?
explanation, 174
possible responses, 174
system program question, 174
Paper patch
installed by manual patching, 122
Paper tape punch
support,58
Paper tape reader
number of general small buffers, 245
support, 58
use of general small buffers, 245
PARITY
memory allocation table suboption, 219
Parity error
example, 222
Parity memory
definition, 218
listing configuration, 219
Parity memory configuration
explanation, 219
for example installation, 219
listing, 218
Parity register usage
in example installation, 219
Parity type codes
list, 219
meaning, 219
PATCH
INIT.SYS program option, 289
Patch
applied manually, 388
CUSP, 398
install with PBUILD, 393
installed to programs, 389
modifying command file, 391
published in RSTS/E Software Dispatch, 387
terminate, 387
to BASIC-PLUS library programs, 392
to monitor overlay code, 390
verify on CPATCH, 404
Patch file
naming convention, 398
!PATCH qualifier
BUILD command, 383
PATCH statement
example, 409

PATCH statement (Cont.)
PBUILD, 406, 408
Patterns?
DSKINT question, 31, 259
explanation, 31, 259
use with system disk, 31
PBUILD
building command file, 405
chaining to BUILD, 394
command file statements, 406
command lines to patch a file, 406
comment lines (!), 405
comments in command file, 405
IDETACH switch, 393
dialogue, 393 to 396
END statement, 406, 408
error messages, 409, 41lt
FORCE statement, 406, 407
instructions for use, 405
PATCH statement, 406,408
patching procedure, 393 to 396
quote character, 406
running, 393
sample command file, 409
terminal output, 396, 398
to install patches, 393
Peripheral devices configuration questions
definition, 55
Physical unit number?
COPY question, 207
explanation, 207
Pre-extend directories?
DSKINT question, 28, 255
explanation,·28, 255
possible responses, 28, 256
use with system disk, 28
Preferred clock?
DEFAULT question, 212
explanation, 212
for RSTS/E monitor, 212
possible responses, 212
Primary run-time system
default, 212
definition, 2
positioning, 225
specify with DEFAULT, 212
Print using?
BASIC-PLUS configuration question, 92
explanation, 92
possible responses, 92
Print/Batch Services package
directory listing, 359
Printers?
explanation, 56

Printers? (Cont.)
peripheral devices configuration question, 56
possible responses, 56
Private delimiter
definition, 49
Proceed?
DSKINT question, 32, 259
explanation, 32, 259
possible responses, 32, 260
use with system disk, 32
Pseudo keyboard
affecting number of jobs, 62
definition, 48
Pseudo keyboards?
explanation, 48
possible responses, 48
terminal interface configuration question, 47
PUB, PRI, or SYS?
DSKINT question, 28, 256
explanation, 29, 256
possible responses, 29, 256
use with system disk, 29, 256
Pushbutton boot procedure
with M9312 console emulator, 374

Quota information
use of extended buffers, 235

RC25 controller, 54
RPS1.2 format
converting to, 384
Read-Only?
DSKINT question, 30, 258
explanation, 30, 258
possible responses, 30, 258
use with system disk, 30, 258
Really add logical block to BADB.SYS?
possible responses, 307
REFRESH BADS question, 307
Rebuild disk
defihition, 302
Rebuild?
explanation, 302
possible responses, 302
REFRESH question, 302
use with system disk, 302

Index-15

REFRESH
error messages, 293t
INIT.SYS program option, 293, 305
REFRESH suboption?
explanation, 302, 305, 307
possible responses, 305, 307
use with BADS, 307
use with FILE, 305
use with LIST, 302
REFRESH sub options
BADS, 307
FILE, 305
LIST, 302
summary, 293
Reserved locations
vector assignments, 277
RESET
HARDWR suboption, 280
memory allocation table suboption,227
Resident library
number of general small buffers, 243
use of general small buffers, 243
Resident overlay code
use of extended buffers, 235
RESTORE
bad blocks during, 316
example, 316 to 320
output used for system disk, 320
relocation of blocks, 316
restoring a RSTS/E disk, 316
save format, 309
SAVRES function, 316
Restore cycle
definition, 218
RETURN
to accept default response, 25
RH controller
definition, 52
RH70 BAE and CS3 addresses, 356t
RH70 controller
list of addresses, 356
list of bus address extensions, 356
list of control status 3 addresses, 356
RJ2780 Model 1 terminal, 60
RJ2780 software
definition, 60
installing, 82
memory for extended buffer pool, 235
mounting installation media, 82
mounting installation media for update, 184
updating, 184
use of extended buffers, 235
RJ2780 support?
explanation, 60

Index-16

RJ2780 support? (Cont.)
peripheral devices configuration question, 60
possible responses, 61
RK05 disk system
definition, 50
RK05's?
disk units configuration question, 50
explanation, 50
possible responses, 51
RK06 and RK07 disks
mixing on same controller, 415
RK06 bootstrap procedure
without M9312 bootstrap module, 379
RK06/RK07 disk system
definition, 51 .
RK06/RKOT s?
disk units configuration question, 51
explanation, 51
possible responses, 51
RK07 bootstrap procedure
without M9312 bootstrap module, 379
RL01 and RL02 disks
mixing on same controller, 415
RL01 bootstrap procedure
without M9312 bootstrap module, 379
RLOllRL02 disk system
definition, 51
RLOllRL02' s?
disk units configuration question, 51
explanation, 51
possible responses, 51
RL02 bootstrap procedure
without M9312 bootstrap module, 379
RM and RP type disks
booting mixed on same controller, 417
mixing on multiple controllers, 417
mixing on same controller, 416
mixing on separate controllers, 416
RM02/RM03/RM05/RM80 disks
mixing on same controller, 416
RMS-11
definition, 69
RMS-11 package
directory listing, 361
ROM configuration
determination, 373
how to bootstrap a device, 373
use with M9312 bootstrap module, 373
ROM locations, 375t
RP02/RP03 disk system
definition, 52
formatting, 33
formatting considerations, 260

RP02/RP03' s?
disk units configuration question, 52
explanation, 52
possible responses, 52
RP04/RP05/RP06 disks
mixing on same controller, 415
RQDX1 controller, 54
RSTS/E file structure
definition, 23, 251
Group File Directory (GFD), 23, 251
Master File Directory (MFD), 23, 251
User File Directory (UFO), 23, 251
RSTS/E monitor
building, 82 to 84
building online, 141
changing defaults, 211
configuring, 37 to 66
definition, 1
starting, 112, 193, 327
updating, 182 to 186
upgrading, 133 to 140
RSTSIE Release Notes
contents, 12
contents of V9.0 installation disks 15
contents of V9.0 installation tape~, 14
order numbers for distribution kits 13
using for system installation, 12 '
using for system update, 147
RSTSIE Software Dispatch
contents, 13
use during system installation, 13
use with mandatory patches, 122
RSTSIE System Installation and Update Guide
how to use, 3
RSTSIE System Manager's Guide
contents, 12
use during system installation, 12
RSX run-time system
supplied by DIGITAL, 2
RSX Utilities package
directory listing, 363
RT11 run-time system
fatal errors, 344t
recoverable errors, 343t
supplied by DIGITAL, 2
RTS
memory allocation table suboption 225
Run-time system
'
definition, 2
examples, 2
install with BUILD, 394
Run-time system memory
definition, 230, 241

Run-time system?
default for RSTS/E monitor, 212
DEFAULT question, 211
explanation, 212
possible responses, 212
RXOllRX02's?
explanation, 57
peripheral devices configuration question 57
possible responses, 57
'
RX11 flexible diskette system
definition, 57
RX211 flexible diskette system
definition, 57
RXV11 flexible diskette system
definition, 57

s
SATT.SYS base?
DSKINT question, 27, 254
explanation, 27, 254
possible responses, 27, 254
use with system disk, 27
SATT. SYS file
definition, 27, 254
position, 27, 254
rebuilt by REFRESH, 302
SAVE
example, 312
format, 309, 316
SAVRES function, 312
SAVE set, 316
extract label information from 321
identify, 309
'
recreate disk from, 316
SAVE set name
default name, 309
SAVE volume
SAVRES, 309
SAVRES
comparison with BACKUP, 309
creating bootable medium, 309
definition of terms, 309
errors, 310
functions, 309
IDENTIFY dialogue, 321
IDENTIFY example, 321
IMAGE dialogue, 323
IMAGE example, 323 to 326
IMAGE function, 323
like disks, 310
nonselective backup, 309

Index-17

SAVRES (Cont.)
RESTORE dialogue questions, 317
RESTORE example, 316 to 320
RESTORE function, 316
RESTORE output as system disk, 320
running on line, 310
SAVE example, 312
SAVE function, 312
save set, 309
SAVE set name, 309
save volume, 309
summary information, 311
'" types of messages, 310
using, 309
Scaled arithmetic
with BASIC-PLUS, 91
Sent messages
number of general small buffers, 244
use of general small buffers, 244
SHOW BUFFERS
DCL command, 242
SHUTUP program
command format, 108, 154, 190
explanation, 108, 154, 190
list of questions, 154
possible responses to questions, 109, 155, 191
questions, 108, 190 to 191
running, 108, 154, 190
sample output, 108, 109, 154, 155, 190, 191
shutting down current monitor, 154
shutting down SYSGEN monitor, 108, 190
to shut down SYSGEN monitor, 190
SIL (Save Image Library)
patch installed, 390
restrictions to install, 390
Size?
possible responses, 305
REFRESH FILE question, 305
Small buffer
See FIP small buffers
See general small buffers
definition, 65
Small buffer pool
list of considerations, 237
worksheet, 247f
Small buffer table
printed dUring system installation, 239f
Small buffers?
creating general small buffer pool, 241
explanation, 65
possible responses, 65
software tuning configuration question, 65
2780/3780 software
use of extended buffers, 235

Index-18

Software tuning configuration questions
definition, 64
SORT/MERGE package
definition, 69
directory listing, 362
installing, 94
Source code
install patches to ASCII, 392
START
activating RSTS/E monitor, 112
changing memory allocation table, 328
crash dump file, 328
error messages, 113, 114, 193, 194, 327, 328
INIT.SYS program option, 112, 113, 192, 193,
327
list of operations, 329
questions, 193 to 195
to activate RSTS/E monitor, 192, 327
to change crash dump, 114, 194
update questions, 165 to 166
warning messages, 113, 194, 328
START. COM command file
editing, 105
use in timesharing, 105
Statistics
use of extended buffers, 235
Statistics gathering, 284
String arithmetic?
BASIC-PLUS configuration question, 92
explanation, 92
possible responses, 92
Supersede existing monitor?
explanation, 41
Supersede existing monitor? (update)
explanation, 172
Swap file
definition, 211
optional, 297
SWAP.SYS, 295
SWAPO.SYS, 297
SWAP1.SYS, 296
SWAP3.SYS, 297
SWAP MAX
definition, 211
size influenced by run-time systems, 211
SWAP max?
DEFAULT question, 211
explanation, 113, 328
for RSTS/E monitor, 113, 328
possible responses, 327
START question, 327
Swap times, 299t
SWAP,SYS file
definition, 295

SWAP,SYS file (Cont.)
location, 296
size, 296
status, 296
SWAPO.SYS file
creation, 297
definition, 297
location, 297
status, 297
SWAPl.SYS file
creating, 296
.
creating during installation, 79
creating during update, 183
definition, 296
location, 296
status, 296
SWAP3.SYS file
creation, 298
definition, 297
location, 298
status, 298
use with event-driven jobs, 297
SWITCH
HARDWR suboption, 284
Switch register boot procedure
with M9312 console emulator, 374
Switch register codes, 379t
Switch register contents
logical positions, 284
Switch register position
DISABLE, 284
ENABLE, 284
VOLATILE, 284
Switch register?
explanation, 284
HARDWR SWITCH question, 284
possible responses, 285
SYSGEN components
directory listing, 361
SYSGEN monitor
how to shut down, 108, 190
legal device unit numbers, 20
starting, 35
starting for update, 165
temporary RSTS/E monitor, 2
SYSTAT program
IF switch, 242
to display number of small buffers, 242
System code
patching, 289
System disk
copying files for update, 162
definition, 19
initializing, 23

System disk (Cont.)
initializing with DSKINT, 23
physically mounting, 20
System files
creating, 293
creating additional, .78
creation summary, 295t
creation worksheet, 30lf
definition, 78
list, ·294
space considerations, 293
System installation
concepts, 1
definition, 1
example, 123 to 133
flowchart, 9f
online, 3
to build a new RSTS/E monitor, 3
to upgrade a RSTS/E monitor, 3
upgrading a pre-V9.0 RSTS/E system, 133
System Library package
directory listing, 363
installing, 68
System logicals
use of extended buffers, 235
System program
definition, 2, 68
directory listing, 357
examples, 2
how to update, 174
installing, 70
list, 68t
logical names, 118, 173t
purposes, 2
repositioning, 118
transferring updates, 186
System start-up file
editing, 101
START. COM, 105
System update
flowchart, 149f
restriction, 198
to build another monitor, 198

T
Table suboption?
DEFAULT question, 212, 216, 219, 220, 223,
225,227,237,248
explanation, 212, 216, 219, 220, 223, 227,
237
for RSTS/E monitor, 212

Index-19

Table suboption? (Cont.)
possible responses, 216, 219, 220, 223, 225,
227, 229, 237
use with BUFFERS, 237
use with LIST, 216
use with LOCK, 220
use with PARITY, 219
use with RESET, 227
use with RTS, 225
use with UNLOCK, 223
use with VIRTUAL, 248
Tape
device designators, 161t
mount instructions, 14, 158
TE10 bootstrap procedure
without hardware bootstrap loader, 381
TECO package
directory listing, 362
Templatp. monitor
definition, 171
using for update, 171
Terminal interface configuration questions
definition, 43
Terminal logging
use of extended buffers 235
Terminal session
'
explanation, 5
Terminals
affecting number of jobs, 62
number of general small buffers, 245
use of general small buffers, 245
To which disk?
COpy question, 207
explanation, 207
possible responses, 207
Trig functions?
BASIC-PLUS configuration question, 91
explanation, 91
possible responses, 92
TS03 bootstrap procedure
without hardware bootstrap loader, 381
TS 11 magnetic tape system
definition, 56
TS 11rrK25rrSV05rrU80' s?
explanation, 56
peripheral devices configuration question, 56
possible responses, 56
TU10 bootstrap procedure
without hardware bootstrap loader, 381
TU10rrE10rrS03 magnetic tape system
definition, 56
TU10rrE10rrS03's?
explanation, 56
peripheral devices configuration question, 56

Index-20

TU10rrE10rrS03's? (Cont.) .
possible responses, 56
TU16rrE16rrU45rrU77 magnetic tape system
definition, 56
TU16rrE16rrU45rrU77's?
explanation, 56
peripheral devices configuration question 55
possible responses, 56
'
TU80 tape drive
use in example installation, 16

u
UDA50 controller, 54
Unit?
DSKINT question, 24, 251
explanation, 24, 302
possible responses, 24, 302
REFRESH question, 302
use with system disk, 24
UNLOCK
memory allocation table suboption, 223
Unlock address is?
explanation, 223
possible responses, 223
UNLOCK question, 223
Unsupported Utility package
directory listing, 360
Update
how to perform, 147
kit labels, 147
performing a selective, 198
preliminary questions, 168
selective example, 200 to 201
Update mode
FIP small buffer considerations 244
Update, selective
'
full system, 198
layered products, 198
monitor, 198
system programs, 198
UPDATE. COM
command format, 198
entry points, 198, 199t
example using, 200
explanation, 198
using for selective updates, 198
using for updates, 198
UPDATE. LOG
update record, 168, 187
Updating software
error checking, 122

Updating software (Cont.)
reference documents, 147
Upgrade system installation
flowchart, 135f
how to perform, 137
INIT.SYS options used in, 133
list of steps, 137
steps for multiple removable disk systems, 139
steps for no mUltiple removable disk systems,
137
Use previous bad block info?
OSKINT question, 30, 258
explanation, 30, 258
possible responses, 31, 258
use with system disk, 30
Use Resident Library version of NIT and FAL?
explanation, 66
peripheral devices configuration question, 66
possible responses, 66
Use resident library version? (update)
explanation, 176
possible responses, 176
system program question, 176
Use template monitor?
explanation, 41
possible responses, 41
Use template monitor? (update)
explanation, 171
Yes response, 171
User account
creating 101, 102, 104
User file directory (UFO)
definition, 29
USER memory
definition, 229, 230, 241

V9.0 Installation disk
bootstrapping, 15
mounting, 15
V9.0 Installation Kit
contents, 12
using for system installation, 12
V9.0 Installation tape
bootstrapping, 14, 15
mounting, 14, 15
VECTOR
HAROWR suboption, 278
Vector address
definition, 277
Vector assignments
list of reserved locations, 277
VIRTUAL
memory allocation table suboption, 248
Virtual disk
advantages, 249
allocating memory, 249
definition, 248
disadvantages, 249
positioning in memory, 250
using, 249
VOLATILE
meaning, 285
switch register position, 284

)(

V9 Library Kit
contents, 12
mounting during installation, 87

w
Wkit
contents, 12
type of RSTS/E distribution kit, 12

XBUF
See also extended buffer pool
creation by INIT.SYS, 229
memory allocation table suboption, 230

Index-21

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

In Canada
call 800-267-6146

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

DIRECT MAIL ORDERS (U.S. and Puerto Rico*)
DIGITAL EQUIPMENT CORPORATION
P.O. Box CS2008
Nashua, New Hampshire 03061

DIRECT MAIL ORDERS (Canada)
DIGITAL EQUIPMENT OF CANADA LTD.
940 Belfast Road
Ottawa, Ontario, Canada K1 G 4C2
Attn: A&SG Business Manager

INTERNATIONAL
DIGITAL EQUIPMENT CORPORATION
A&SG Business Manager
c/o Digital's local subsidiary
or approved distributor

Internal orders should be placed through the Software Distribution Center (SDC), Digital
Equipment Corporation, Northboro, Massachusetts 01532
*Any prepaid order from Puerto Rico must be placed
with the Local Digital Subsidiary:

809-754-7575

RSTS/E
System Installation
and Update Guide
AA-2669H-Te

Reader's Comments
Note: This form is for document comments only. DIGITAL will use comments submitted on this form at
the company's discretion. If you require a written reply and are eligible to receive one under
Software Performance Report (SPR) service, submit your comments on an SPR form.
Did you find this manual understandable, usable, and well-organized? Please make suggestions for
improvement. ________________________________________________________----------

Did you find errors in this manual? If so, specify the error and the page number. _________________

Please indicate the type of user/reader that you most nearly represent.

o
o
o
o
o

Name

Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student programmer
Other (please specify) ___________________________________________
Date _______________________________

Organization ___________________________________________________________________
Street _______________________________________________________________________
Code
City _____________________________________ State _______ Zip or
Country

I
I
I
I
I
I

-------Do Not Tear· Fold Here and Tape ...;.-------------------------------~----I

111111

No Postage
Necessary
if Mailed in the
United States

BUSINESS REPL V MAIL
FIRST CLASS PERMIT NO.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

AnN: Office Systems Publications MK01-2/E02
RSTS/E Documentation
DIGITAL EQUIPMENT CORPORI\TION
CONTINENTAL BOULEVARD
MERRIMACK, N.H. 03054

-------Do Not Tear· Fold Here and Tape - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -