Digital PDFs

AA-2669J-TC

July 1989

352 pages

Original

16MB

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

OCR Text

RSTS/E System Installation
and Update Guide
Order Number: AA-2669J-TC

July 1989
This guide describes how to Install and update a RSTS/E system.

Operating System and Version: RSTS/E V9.7
Software Version:

digital equipment corporation
maynard, massachusetts

RSTS/E V9.7

July 1989
The information in this document Is subject to change without notice and should not be
construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation
assumes no responsibility for any errors that may appear In this document.
'The software described in this document is furnished under a license and may be used or
copied only in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment that Is not
supplied by Digital Equipment Corporation elr its affiliated companies.
© Digital Equipment Corporation 1989.
All Rights Reserved.
Printed in U.S.A.
The postpaid Reader's Comments forms at the end of this document request your critical
evaluation to assist in preparing future doclJlmentation.
DATATRIEVE
DEC
DECmaii
DECmate
DECnet
DECsystem-10
DECsystem-20
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

IBM is a registered trademark of International Business Machines Corporation.

Contents
F'reface ......... " . . . . . . . . . . . . • . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xIII

Introduction to System Installation
What Is System Installation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Part 1

Initialize System Disk (DSKINT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSTS/E Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Run-Time Systems and Resident Libraries . . . . . . . . . . . . . . . . . . . .
System Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Layered Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1
2
2
3
3

Types of System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dialogue Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Use This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation

Installing RSTS/E V9.7 on a New System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Structure of Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase 1: Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase 2: Prepare System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase 3: Configure RSTS/E Monitor .............. ,.. , . . . . . . .
Phase 4: Select RSTS/E System Programs. . . . . . . . . . . . . . . . . . .
Phase 5: Generate RSTS/E System . . . . . . . . . . . . . . . . . . . . . . . .
Phase 6: Create Accounts and Edit System Startup File ..........
Phase 7: Start RSTS/E Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase 8: Optional Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10
10
10
10
10
10
10
10
11

System Installation Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

iii

Phase 1

Phase 2

Phase 3

Phase 4

Getting Started
Task 1: Collect Distribution Kits and Documentation

Task 2: Physically Mount and Bootstrap Instaillation Media . . . . . . . . . . . . . .
Tape Mount Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disk Mount Session . . . . . . . . , . . . . . . . . . . . . . . . . . . . . . . . . . .
Bootstrap V9.7 Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . .

17
'17
17
18

Prepare System
Task 1: Physically Mount Target System Disk

Task 2: Answer Preliminary INIT.SYS Questions ....... , . . . . . . . . . . . . . .
Terminal Session ...................... , . . . . . . . . . . . . . .

23
23

Task 3: Initialize System Disk (DSKINT) ............. '. . . . . . . . . . . . . . .
Terminal Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

:24
:24

Task 4: Start SYSGEN Monitor (START) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminal Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

35
35

Configure RSTS/E Monitor
Task 1: Answer Preliminary Configuration QUE.stlons ..... , . . . . . . . . . . . .
Terminal Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

38
38

Task 2: Answer Disk Units Configuration Que~Jtlons . . . . . . . . . . . . . . . . . . .
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

43
43

Task 3: Answer Peripheral Devices Configuration Questions. . . . . . . . . . . . .
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

47
47

Task 4: Calculate Number of Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparation Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

51
51

Task 5: Answer Software Tuning and Feature!:~ Configuration Questions ....
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

53
53

Select RSTS/E System Prog rams
Task 1: Answer System Program Installation CJuestions . . . . . . . . . . . . . . . .
Terminal Session ............. " . . . . . . . . . . . . . . . . . . . . . . .

56
57

Task 2: Answer Layered Product-Related Questions. . . . . . . . . . . . . . . . . . .
Terminal Session . . . . . . . . . . . . .' . . . . . . . . . . . . . . . . . . . . . . .

61
61

Phase 5

Phase 6

Phase 7

Phase 8

Generate RSTS/E System
Task 1: Create Additional System Flies. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . " . . . . . . . . . .

64
64

Task 2: Create RSTS/E Monitor ....................... , . . . . . . . . . .
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Messages Produced While Building a RSTS/E Monitor. . . . . . . . . . . .

66
66
66

Tasl< 3: Install System Programs from the Installation Media. . . . . . . . . . . . .
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

68
68

Tasl< 4A: Answer BASIC-PLUS Installation Questions ....... , . . . . . . . . . .
Terminal Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

72
72

Task 4B: Answer SORT/MERGE Installation Questions . . . . . . . . . . . . . . . . .
Terminal Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .

75
75

Create Accounts and Edit System Startup File
Task 1: Create the System Management Account (CREATE/ACCOUNT)
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

82
82

Task 2: Create User Accounts (CREATE/ACCOUNT) . . . . . . . . . . . . . . . . . . .
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . , .

83
83

Task 3: Edit System Startup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

84
84

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

88
88

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

89
90

OpUonal Tasks
Task 1: Reposition System Pr()gram Packages. . . . . . . . . . . . . . . . . . . . . . .
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

94
94

Task 2: Apply Any Mandatory Patches ............................

Installation Example

System Installation Example ..................... ".......................

Part 2

Upgrade

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

Part 3

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

121
122
122

Update

Updating a RSTS/E V9.0 through V9.6 System

Phase 1

109

Online

Performing an Online System Installation ...................................

Part 4

...............................

1127

Structure of Part 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase 1: Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase 2: Prepare System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase 3: Configure New Monitor and Select Software Updates. . . . . .
Phase 4: Generate New System . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase 5: Start New Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase 6: Optional Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

~ 27
127
127
128
128
128
128

System Update Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

'128

Getting Started
Task 1: Back Up System Disk (BACKUP) . . . . . . . . . . . . . . . . . . . . . . . . . . .

132

Task 1A: Back Up Nonsystem Disk (BACKUP)! . . . . . . . . . . . . . . . . . . . . . . .

'132

Task 2: Shut Down Current Monitor (SHUTUF') . . . . . . . . . . . . . . . . . . . . . . .
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

'133
'133

Phase 2

Phase 3

Phase 4

Phase 5

IPhase 6

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

136
136
136
137
137
138

Task 2: Copy Flies to System Disk (COPY) .........................
Terminal Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COPY Error Messages . . . . . . . . . . . . . . . . . . . . . . . . .

140
140
142

Configure New Monitor and Select Software Updates
Task 1: Answer Preliminary Questions ............................
Terminal Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

144
144

Task 2: Use Information from a Template Monitor. . . . . . . . . . . . . . . . . . . . .
Terminal Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

146
146

Task 3: Answer System Program Update Questions. . . . . . . . . . . . . . . . . . .
Terminal Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

149
149

Task 4: Answer Layered Product Update Questions . . . . . . . . . . . . . . . . . . .
Terminal Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

152
152

Generate New System
Task 1: Create RSTS/E Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminal Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

156
156

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

159
159

Start New Monitor
Task 1: Shut Down SYSGEN Monitor (SHUTUP) . . . . . . . . . . . . . . . . . . . . . .
Terminal Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

164
164

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

166
166

Optional Tasks
Task 1: Perform a Selective Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UPDATE.COM Entry Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selective Update Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

170
170
171

vII

Part 5

Offline Options

Offline Options ......................................... "..............

1'15

BOOT-Bootstrap Devices . . . . . . . . . . . . . . . . . . . . . . "..............
BOOT Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BOOT Error Messages . . . . . . . . . . " . . . . . . . . . . . . . .

1'77
177
177

DATE-Set the Date and Time Format . . . . . . . . . . . . . . , . . . . . . . . . . . . . .
DATE Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

178
1'78

DEFAULT-Change RSTS/E Monitor Defaults . . . . . . . . . . . . . . . . . . . . . . . .
DEFAULT Dialogue . . . . . . . . . . . . . . . . . . . . "..............

1'79
179

DEFAULT Suboptlons-Adjust the Memory Allocation Tablle "............
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 Memo1ry . . . . . . . . . . . . . . . . . . . . . .
UNLOCK 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 Pool . . . . . . . . . . . '.
BUFFERS Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Small Buffer Pool Background Information . . . . . . . . . . . . . . . . . . . .
General and FIP Small Buffer Pool Worksheet . . . . . . . . . . . . . . . . .

181
181
181
182
183

185
186
186
187
188
188
189
190
195
197
197
199
205

DSKINT-Inltlallze RSTS/E Disks ......... , . . . . . . . . . . . . . . . . . . . . . . .
DSKINT Dialogue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DSKINT Error Messages " . . . . . . . . . . . . . . . . . . . . . . .

207
207
215

HARDWR-AdJust the Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . .
HARDWR LlST-List the Hardware Configuration Table. . . . . . . . . . .
LIST Dialogue . . . . . . . . . . . . . . . " . . . . . . . . . . . . . . . . . . . . . . .
HARDWR ECO-Show revision level of MSCP and TMSCP
controllers. . . . . . . . . . . . . . . . . . " . . . . . . . . . . . . . . . . . . . . . . .
ECO Dialogue . . . . . . . . . . . . . . . " . . . . . . . . . . . . . . . . . . . . . . .
HARDWR DISABLE-Disable a DeviGe Controller . . . . . . . . . . . . . . .
DISABLE Dialogue . . . . . . . . . . . ., . . . . . . . . . . . . . . . . . . . . . . .
HARDWR ENABLE-Enable a Devic~~ Controller. . . . . . . . . . . . . . . .
ENABLE Dialogue . . . . . . . . . . . . , . . . . . . . . . . . . . . . . . . . . . . .
HARDWR CSR-Declare a Nonstandard Controller Address. . . . . . . .
CSR Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HARDWR VECTOR-Declare a Nonsltandard Vector Assignment. . . . .
VECTOR Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HARDWR RESET-Set All Vector and CSR Addresses·to the Standard,
and Enable All Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RESET Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

217
217
217

viii

184
184

222
222
223
223
225
225
226
227
227
229
229
230

Part 6

HARDWR OM-Declare DM11-BB and DH11 Associations . . . . . . . . .
OM Dialogue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HARDWR HERTZ-Specify AC Une Frequency . . . . . . . . . . . . . . . .
HERTZ Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HARDWR SWITCH--Specify CPU Switch Register Characteristics. . . .
SWITCH Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HARDWR Error Messages ......................

230
231
231
231
232
233
233

IDENT-list the Version Number and Patch Information ................
IDENT Dialogue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

235
235

PATCH-Install a Patch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PATCH Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PATCH Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

236
236
238

REFRESH-Perform File-Related Tasks ............................
REFRESH Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

239
239
240
245
245
247
248
249
249

SAYRES-Restore and Copy Disks .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RESTORE-Recreate a Disk From Tape or Disk. . . . . . . . . . . . . . . .
RESTORE Dialogue ........................ , . . . . . . . . . .
IDENTIFY-Extract L.abel Information ............ "..........
IDENTIFY Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IMAGE - Make a Copy of a Disk ............... " . . . . . . . . . .
IMAGE Dialogue .......................... , . . . . . . . . . .

251
253
254
257
257
259
259

START-Start a RSTS/E Mon Itor ... " .................. "..........
START Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

263
263

Appendixes

,Appendix A System Installation Error Messages
Initialization Code Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

267

~l\ppendlx B Address and Vector Assignments

Floating Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Floating Address Worksheet .............................
Using the Worksheet ..........................

285
286
287

Floating Vectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

293

Fixed Addresses and Vectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

294

RH70 BAE and CS3 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

296

Appendix C RSTS/E System Flies,
RSTS/E System Flies

297

Appendix D Bootstrapping the Distribution Medium
Bootstrapping Magnetic Tape Distribution

305

Bootstrapping Disk Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

306

Hardware Bootstrap Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BM873-VA Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BM873-VB Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .- . .
H324 Pushbutton Panel Procedure . . . . . . . . . . . . . . . . . . . . . . . . .
MR11-DB Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BM792-YB Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
M9301-VA and M9301-VB Procedure~;. . . . . . . . . . . . . . . . . . . . . . .
M9301-VC Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
M9301-YF Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
M9312 Procedure ....................................
Using the M9312 Console Emulator ...... . . . . . . . . . .
Determining the M9312 BtDotstrap ROM Configuration . . . .
Bootstrapping with the M9312 ....................
Load Program Bootstrap for the RL01/RL02 and RK06/RK07 .......
Load Program Bootstrap for the TU10, TE10, or TS03 ........ '. . . .
Bootstrap Procedures for the 11173, 11/83, or 11/84. . . . . . . . . . . . . .

306
307
308
308
308
308
309
309
310
311
311
312
314
315
317
318

Appendix E Additional System Installation-Related Programs
Using the BUILD/PATCH Program ........ ".......................

319

Using the DSKCVT Program ............ " . . . . . . . . . . . . . . . . . . . . . . .

320

Using the ONLPAT Program to Patch RSTS/E Binary Code .... . . . . . . . . . .
Using ONLPAT in Keyboard and Command File Mode . . . . . . . . . . . .
ONLPAT Dialogue Questions . . . . . . . . . . . . . . . . . . . . .
Patching a Running Monitor with ONLPAT . . . . . . . . . . . . . . . . . . . .
Building ONLPAT Command Files. ., . . . . . . . . . . . . . . . . . . . . . . .

322
322
323
325
326

Appendix F Mixed Disk Drives on the Same Controller
Mixing RK06 and RK07 Drives on the Same C'ontroller

327

Mixing RL01 and RL02 Drives on the Same Controller

Mixing RM02/RM03/RM05/RM80 Drives on the Same Controller ...........

327

Mixing RM02/RM03/RM05/RM80 and RP04/RPOl5/RP06 Drives on Separate
Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

328

Mixing RM02/RM03/RM05/RM80 and RP04/RPOl5/RP06 Drives on the Same
Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

328

Multiple RH Controllers for the Same Type of Disk. . . . . . . . . . . . . . . . . . . .

328

Random Mixing of RP and RM Disks on Multiple Controllers. . . . . . . . . . . . .

329

Booting Mixed RM02/RM03/RMOS/RM80 and RP04/RPOS/RP06 Disks. . . . . . . .

329

Avoiding Bootstrap Conflicts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

329

Video Terminal Display with a Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Video Terminal Display with a Dynamic Message . . . . . . . . . . . . . . . . . . . . . . .

4
5

Index

Figures

System Installation Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Job Calculation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5
6

System Upgrade Rowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

111

System Update Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

129

Extended Buffer Pool for Example RSTS/E System . . . . . . . . . . . . . . . . . . . . . .

191

Extended Buffer Pool Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

196

9
10
1 .,

Example Small Buffer Table Printed During System Installation . . . . . . . . . . . . . .

198

General and FIP Small Buffer Pools . . . . . . . . . . ~ . . . . . . . . . . . . . . . . . . . . .

200

General and FIP Small Buffer Pool Worksheet . . . . . . . . . . . . . . . . . . . . . . . . .

206

System File Creation Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

245

Floating Address Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . , ......... .

289

Tape Device Designators. . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .

Bootable Disk Device Designatolrs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Disk Pack Cluster Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device Cluster Sizes and Total Device Sizes . . . . . . . . . . . . . . . . . . . , . . . . . .

System Program Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Program Package Logical Names . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BASIC-PLUS Optional Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Monitor Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Program Package Logical Names . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INSTAL.COM Entry Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

122

Tables

Tape Device Designators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

138

Bootable Disk Device Designators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

139

System Program Package Logical Names . . . . . . . . . . . . . . . . . . . . . . . . . . . .

149

14
,1,)

INIT.SYS Selected Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

166

UPDATE~COM Entry Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

171

1E>

INIT,SYS Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

175

Disk Pack Cluster Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

209

Device Cluster Sizes and Total Device Sizes .. . . . . . . . . . . . . . . . . . . . . . . . .

211

Hardware Comments Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

219

Summary Hardware Configuration Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

221

Reserved Hardware Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

228

xii

Possible Input to the PATCH Option . . . . . . . . • . . . . . . . . . . . . . . . . . . . . . . .

237

Summary of System File Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

241

Swap limes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

243

Device Vector Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

293

Devices with Rxed Addresses and Vectors . . . . . . . . . . . . " . . . . . . . . . . . . . .

RH70 BAE and CS3 Addresses . . . . . . . . . . . . . . . . . . . . , ............. .

295
296

Summary of Hardware Bootstrap Addresses ............ , ............. .

307

Device Codes for M9301-YA and M9301-YB Boot:straps . . . . . . . . . . . . . . . . . . .

309

Device Codes for M9301-YC Bootstrap . . . . . . . . . . . . . . . " ............. .

310

Device Codes for M9301-YF Bootstrap . . . . . . . . . . . . . . . " ............. .

310

M9312 ROM Arrangement . . . . . . . . . . . . . . . . . . . . . . . . , ............. .

311

ROM Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . " ............. .

312

M9312 Bootstrap ROM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

313

Device Name and Mnemonic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

314

Switch Register Codes (SWR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Console Switch Register Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

315
315

Bootstrap Routines for the RL01/RL02 and the m<06/RK07 ..."............

316

Responses to ONLPAT Questions. . . . . . . . . . . . . . . . . . . . . , . . . . . . . . . . . .

323

Preface

Objective
This guide provides a task-oriented procedure for RSTSIE system installation and
update.

Audience
The audience for this guide includes:
•

Anyone installing RSTS/l~ for the first time

•

Anyone upgrading to RSTSIE V9.7 from a pre-V9.0 version of RSTSIE

•

Anyone updating an existing RSTSIE V9.0 through V9.6 system

•

Anyone performing an online or partial system installation

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

[)ocument Structure
The guide is divided into six parts:
Parll

Tells how to build a new RSTSIE 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 at the end of Parl 1.

Parl2

Explains how to perform a system installation to upgrade an existing
pre-V9.0 RSTSIE system to V9.7.

Parl3

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

Parl4

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

Parl5

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

Appendixes

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

xiii

Related Documents
You may find the following documents useful while perform;ng a system installation:

•

RSTS/E V9.0 through V9.7 Release Notes

•

RSTS / E System Manager's Guide

•

RSTS / E Software Dispatch

Conventions
This guide uses the following symbols and conventions:
Represents a carriage-returru1ine-feed combination. Press the ~
key on your keyboard to produce this combination.
Represents the CTRL key and some other keyboard character. For
example, to enter CTRIJU, hold down the ICTRLI key and press the key
labeled "U." RSTSIE echoes or displays the character at your terminal
as I\.U.
I\.

xiv

Indicates the circumflex key.

Italics

Indicates that a definition follows the italicized technical term.

color

Red print indicates the response made in the example installation.
Your response may differ from the response given in the example
installation.

Introduction to System Installation
This section explains some basic concepts about system installation. It also
explains how to use this guide.

''''hat Is ~)ystem Installation?
System installation is the process by which you create a RSTSIE system for your
requirements. This includes:
•

Optionally testing and initializing disk volumes

•

Tailoring a RSTSIE monitor

•

Installing one or more run-time systems

•

Installing system prograrns

•

Installing layered products

The following sections briefly explain each of these items.

Initialize System Disk (DSKINT)
You initialize the system disk using the DSKINT routine. This routine is an
INIT.SYS program option.
DSKINT:
•

Optionally formats some disks; this writes timing and sense marks on the
disk and destroys any previously stored information.

•

Optionally checks the disk for bad blocks. DSKINT locates bad blocks on the
disk and allocates them to the bad block file (BADB.SYS).

•

Writes a minimum RSTSIE file structure on the disk. The minimum RSTSIE
file structure contains a pack label and five directories:
The Master File Directory (MFD)
The Group File Directory (GFD) for groups 0 and 1
The User File Directory (UFD) for account [0,1] and [1,2]
The RSTSIE file structure prepares the disk to accept RSTSIE system and
other files.

RSTS/E Monitor
The RSTSIE monitor is a set of routines thatt controls:
•

System scheduling - RSTSIE stands for Resource Sharing Time
SharinglExtended. This means the monitor makes sure that all users
can work simultaneously without interruption or interference. For example,
they can run and create programs, creating programs, access data files, or
work with a text editor.

•

Memory management - The monitor mBLkes sure that computer memory is
used efficiently.

•

Input/output (I/O) services - The monitor handles requests to and from a
wide variety of I/O devices, including disks, tapes, terminals, and DECnet
networks.

•

Device management - Your installation probably has a variety of hardware,
such as tape drives, line printers, and disk drives. The monitor controls these
hardware devices.

•

Monitor directives - Monitor directives compose the functions available to
user programs on RSTSIE. RSTSIE contains a rich set of monitor directives to
simplify program development.

The RSTSIE system is designed to operate in a wide variety of environments.
RSTSIE has many configuration options which may be used to tailor the RSTS/E
system to your environment. Some options must be set during the installation
process; others may be modified at any time. RSTSIE provides defaults for
most of these options (determined by analyzing the system configuration) and
additionally configures itself for certain system characteristics.
'Ib get you started, DIGITAL supplies a teInporary RSTSIE monitor (called

the SYSGEN monitor) on the installation media. This monitor is prebuilt and
requires no tailoring during system installation. Use it to build your RSTSIE
system. After you build your own custom 1nonitor, you no longer need the
SYSGEN monitor. The installation procedure will shut down the SYSGEN
monitor and automatically start your new lnonitor if you choose to do so. You can
also perform the shut down and new monitor start at your convenience after the
installa tion.

Run-Time Systems and Resident Libraries
A run-time system is software that provides a user interface and/or programming environment. Resident libraries are common routines used by various
programming languages.
The run-time systems that DIGITAL supplies with RSTSIE are:
•

DCL

•

RSX

•

BASIC-PLUS

•

RTll

DCL is the default keyboard monitor.
You must have the CSPLIB resident library installed on your system because
most of the system programs use CSPLIB.

Introduction to System Installation

System Programs
System programs provide you with ~ tools for performing common tasks. For
example, system programs aHow you to efficiently develop programs, manage
files, and perform special system management-related tasks. Some system
programs are required on aU RSTSIE systems while others are optional. During
installation, you select which system program packages you want. Additionally,
there are certain options you select about system programs during installation as
well as bundled software packages that run on a RSTSIE system. These include
RMS, EDT, SORT, and other packages.

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 BASIG-PLUS-2, COBOL-SI, and DIBOL.

lrypes of System Installation
This guide describes four types of system installations:
•

New - In this type of system installation, you create a RSTSIE system disk,
tailor a RSTSIE monitor, install one or more run-time systems and resident
libraries, install the required system programs, and install 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.7 system. This system installation differs from
the previous one in that you must perform tasks to move yout"'old system disk
to a new format disk using either the disk conversion utility (DSKCVT) or
other methods to transfer data from the old disk.

•

Online - In this type of system installation, you reinstall selected RSTSIE
components during timesharing on a previously installed V9.7 system. Note
that you cannot perform an online system installation to install a V9.7
system from a V9.6 or earlier system. Online installations are done to change
selections made during a previous installation.

•

Update - In this type of system installation, you update an existing V9.7
system to a new release. When you receive new Installation Kits from
DIGITAL, use these procedures to update your present V9.6 system to a V9.7
system.

Another type of system installation is:
•

System installation for another PDP-II.; In this type of instal1ation, you build
a RSTSIE monitor on one PDP-II for use on another PDP-I!. This is called
a "target" build. This means you must know the hardware characteristics of
the PDP-II for which you are building the RSTSIE system.

Introduction to System Installation

Dialogue Format
The installation and update dialogue format used in this manual assumes you
are running the procedure from a hardcopy terminal. However, you can run
the procedure from a video terminal. In this case, the dialogue format will be
different. The top part of the screen is reserved for header information, which
keeps you informed about progress through the phases of the procedure. The
bottom part of the screen is reserved for prompts and status and error messages.
The middle part of the screen displays the remaining general information as
the procedure progresses through its phases. Figures 1 and 2 show two typical
display examples.
Figure 1:

Video Terminal Display with a Prompt

:::::::
P lease en t.er t.he n.9.P'le and un it. nlWtber 0 f tI-te disk to
which you want. t.o inst.all the soft.ware. This disk
should be physically Mount.ed and write-enabled.

Target disk? <_SV:>

4 Introduction to System Installation

Figure 2:

Video Terminal Display with a Dynamic Message

8(:0

11")(1

I!-Iow to (Jse This Guide
The RSTS / E System Installation and Update Guide focuses on the tasks you
must perfo:nn to install or update your system, rather than the option or program
used to complete the task. The guide is divided into six parts:
•

Part 1 tells how to build a new RSTSIE 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 process of system
installation. A summary of the installation procedure is printed at the end of
Part 1.

•

Part 2 explains how to perfo:nn a system installation to upgrade an existing
pre-V9.0 RSTSIE system to V9. 7.

•

Part 3 explains how to perfo:nn an online system installation to create a new
monitor or perfo:nn a partial installation.

•

Part 4 explains how to update an existing V9.5 system to a V9.7 release. It
is divided into five phases plus one optional phase, each consisting of one or
more tasks.

•

Part 5 is a reference section that describes the INIT.SYS offline options.

•

Appendixes A through F contain supplemental info:nnation that you may need
for your particular installation.

Introduction to System Installation 5

Part 1
Installation

Installing RSTS/E V9.7 on a New System
This part describes the tasks you must perform to install a new RSTSIE V9.7
system. This part of the guide is for users who are less experienced and
knowledgeable about perforrning 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
RS1'SIE 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 loading
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 response in red next to the
question is from an example installation. Use the example installation as a guide
when you are building your HSTSIE monitor. The example installation has the
following characteristics:

•

CPU: PDP-11/44

•

:Memory: 512K words

•

System Disk: RABO

•

HSTSIE Distribution Kit: 1600 bpi magnetic tape

•

Installation Kit: V9.7

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

Explanation-This question asks for the device designator of your system disk.
Response-Acceptable responses for the system disks are: DL, DM, 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. 1b print the online explanation of a question on your console
terminal, type a question mark (?).

Structure of Part 1
Part 1 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: Getting Started
Provides instructions on collecting the required installation kits and documentation, checking the kit order numbers, and physically mOWlting and bootstrapping
the Installation tape or disk.
Bootstrap instructions are in Appendix C. However, Phase 1 contains an example
of bootstrapping.

Phase 2: Prepare System
Describes how to mOWlt, 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 RSTSIE 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.

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

Phase 6: Create Accounts and Edit System Star1tup File
Describes how to tailor the START.COM file and create user accoWlts.

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

Installing RSTS/E V9.7 on a New System

Phase 8: Optional Tasks
Explains how to relocate system program packages or apply a mandatory patch.
This is an optional phase.

S,ystem Installation Flowchart
Figure 3, the System Installation Flowchart, summarizes the installation phases
and tasks. You may want to use this flowchart while performing the system
installation.

Installing RSTS/E V9.7 on a New System

Answer
BASIC-PLUS
Installation

PHASE 1
GeHing Started

qua.tions
Task

1r-----~-----,

Collect
distribution kits
and
documentation
Task 2 r - - - -......- - _ ,
Physically mount
and bootstrap
Insfallation media

Physically
mount target
system disk

Answer
configuration
questions

Create additional
system flies

Task 2

Task
Answer
preliminary
INIT.SYS
questions

Task 3

monitor

Task 3 ..--_......_-......,

Answer system
program
Installation
questions

DSKINT
Initialize
system disk

Task 3

2: C,~t. ~RS~'~ :

COpy

Answer
layered product
update transfer
questions

Copy mes to
system disk

HARDWR

Task 1

Perform
hardware-related
tasks

Task ....

---..1..---START

start
SYSGEN monitor

_
_
PHASE 8
Optional Tasks

Reposition
.. system program
packages

Task 2

,..-----......,

.........
.........

......... ....

Apply a
mandatory patch

ZK-9245-HC

Figure 3:

System Installation Flowchart

Installing RSTS/E V9.7 on a New System

Phase 1

Getting Started
This phase describes the tasks you must perform to prepare for a RSTSIE system
installa tion.
The tasks in this phase are:
•

Task 1: Collect Distribution Kits and Documentation

•

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 RSTSIE cllst.omer~. Contn;ns complete RSTSIE documentation,
all RSTSIE Release Notes, RSTSIE V9.7 Installation Kit, and all purchased
optional software kits.

•

H Kit - for those whose service contract or warranty has expired, for those
who have purchased additional CPUs, or for customers who only need to
update their system. Contains complete RSTSIE documentation, all RSTS/E
Release Notes, RSTSIE V9.7 Installation Kit, and all purchased optional
software kits.

•

W Kit - for those under warranty or software product service contract.
Contains complete RSTSIE documentation, RSTSIE V9.7 Installation Kit, and
all purchased optional software kits (only if the original version has changed).

1b perform a system installation, collect the following items from the A, H, or W
kit:
•

RSTS / E V9.7 Installation Kit- ConsistEl of the tape or disk that contains
feature and mandatory patches and replacement modules; It also contains
the programs and files you need to perform a system installation. You receive
this kit for every new release of RSTS/l~. The kits are labeled V9.5, V9.6,
V9.7, and so forth. Because each kit is Icumulative, use only the most current
one. For example, the V9.7 Installation Kit would contain all the patches
and replacement modules that were on Kits V9.5 and V9.6, plus some new
patches and replacement modules.

•

Kit(s) - Optional software, also called layered products, is purchased
separately from the RSTSIE Distribution Kit. Examples of optional software
are COBOL-81, BASIC-PLUS-2, and D][BOL. Purchase optional software
from an original equipment manufactw~er 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. Ensure that you have the appropriate
version by checking the SPD Layered Product cross-reference chart.

•

RSTS / E V9.0 through V9.7 Release Notes - Explains the differences between
the most current and previous versions of RSTSIE.

You may want to keep the following items nearby for use as reference material:

•

RSTS / E System Manager's Guide - De:3cribes how to operate and manage
a RSTSIE system. Refer to this manual during system installation for more
information about creating accounts and editing the system startup file. Also
use this manual to help manage your system on a day-to-day basis.

•

RSTS / E Software Dispatch - Contains new and revised software product
descriptions (SPD), programming notes, patches and announcements 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
RSTSIE V9.7 Installation Kit to be sure they match the order numbers that
appear in the RSTS/E Release Notes. 1b check the order numbers of any other
optional software kits, refer to the bill of m.aterials.
Go to Task 2.
16

Getting Started

"Task 2: IPhysically Mount and Bootstrap Installation Media
This task requires you to mount and bootstrap the appropriate tape or disk
from your RSTSIE 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 RSTSIE V9.7 Installation Kit, consisting
of a 9-track, 1600 bits per inch (bpi) tape.

lrape Mount Session
Mount the BOO or 1600 bpi 9-track tape from your RSTSIE Distribution Kit that
has the label V9.7 Installation. This tape contains the system installation files
and programs. Note that there may be other programs and files on this tape.
1b load the tape on the drive:
1. Physically mount the tape on drive unit 0 with the write-enable ring removed.

2.
3.
4.
5.
6.

If you have an BOO bpi distribution tape, mount it on unit 0 or 1 of the TE10
or TU10 tape drive. If you have a 1600 bpi distribution tape, mount it on unit
o or 1 of the TU16, TE16, TU45, TU77, TS11, TSV05, TUBO, or TUB1 tape
drive. If you have a TK50 installation mediwn, mount it on unit 0 or 1 of the
TK50 tape 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. The console terminal is usually a
hard-copy terminal that you use during system installation.
NOTE

If the previous instructions do not apply to your tape drive, see
the hardware manual supplied with your tape drive for the load
instructions.
The tape drive MUST be write-protected and online for the installation
to proceed properly.
[J~isk Mount Session

Mount the disk from your RSTSIE Distribution Kit that has the label V9.7
Installation. This disk contains the system installation programs and files. Note
that this disk may also contain other files and programs.
1b 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.
2. Make sure that the READY light is on.
1.

Getting Started

3. Make sure that the write-protect (WR PROT) light is on.
4. Make sure that the console terminal is on line. The console terminal is
usually a hard-copy terminal that you use during system installation.

Bootstrap V9.7 Installation Media
Now you must bootstrap the tape or disk, which means using the PDP-11
hardware bootstrap loader to activate the installation media. There are different
types of hardware bootstrap loaders. If you do not know how to bootstrap the
V9.7 Installation media, see Appendix C, which contains bootstrap instructions
for most of the different types of hardware bootstrap loaders.
The hardware boots~rap loader is a device inside your PDP-11 that reads a
bootstrap record from the tape or disk into memory. This bootstrap record
contains a program that loads and executeel 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-11.
The representative should also have given instructions for bootstrapping your
tape or disk.
The example installation shows how to bootstrap the 1600 bpi tape from a TUBO
tape drive. These bootstrap instructions arc~:
1. Move the control switch (CONT) to the HALT position.
2. Move the control switch to the BOOT position.

The CPU prints some octal numbers on the console terminal, followed by three
angle brackets:
»>B 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 TUBO
tape drive: thus, the tape device designato]~ is MSO.
Table 1 lists the tape device designators. Table 2 lists the bootable disk device
designators. Enter the appropriate device designator for your installation.
The following are general guidelines for the time required for the next step:
1. Disks boot quickly.
2. Tapes boot medium quickly.
3. TK50 boots very slowly.

Anywhere from 30 seconds to 10 minutes after you type the device designator, the
following prints on the console terminal:
Performing limited hardware scan.

RSTS V9.7 (MSO)
Today's date?

18 Getting Started

INIT V9.7

The "1bday's 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.
Note that the time required for this step varies according to the bootable device
you use and the size of your system. The following are some more specific
guidelines for the time for this step:
•

If you are booting a disk such as an RL02 or RK07, this step should take less
than 30 seconds.

•

][fyou are booting a TK50 on a large system with many devices attached, this
step could take up to 10 minutes.

Table 1: Tape Device Designators
Designator

Devices Available During Installation

MMO: toMMl:

TE16trU16trU45trU77 magnetic tape units 0 or 1

MSO: to MSl:

TSll!I'SV051TU801TK251magnetic tape units 0 or 1

MTO: toMTl:
MUO: to MUl:

TEI0trUI0f.l('S03 2 magnetic tape units 0 or 1

1 _

2 _

TK50ITUBltTUBl-PLUS magnetic tape units 0 or 1

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

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

Bootable Disk Device Designators

Designator

Devices Available During Installation

DBO: to DBl:

RP04IRP05IRP06 disk drive units 0 or 1 1

DLO: to DL3:

RLOIIRL02 disk drive units 0 to 3

DMO: to DMl:
DRO: to DRl:

RK06IRK07 disk drive units 0 or 1
RM02IRM03IRM05IRMBO disk drive units 0 or 1 1

DUO: to DU15:

RA60IRABOIRABlIRAB2IRCF25IRC25IRD31/RD321RD51!
RD521RD531RD541RX33/RX50 disk drive units 0 to 15

1 _ See Appendix F for more information on multiple RH controller (otherwise known as DB and
DR controllers) configurations.

Go to Phase 2.

Getting Started

Phase 2

Prepare System
Mter you bootstrap the V9.7 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 RSTSIE monitor will reside. Non system disks
store other files and programs that might not fit on the system disk. Next you
stalt 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:
•

Task 1: Physically Mount Target System Disk

•

Task 2: Answer Preliminary INIT.SYS Questions

•

Task 3: Init~alize System Disk (DSKINT)

•

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.'7 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 startup.
If your disk is a DL class device, you ean mount it on any disk drive (0,
1, 2, or 3). If your disk is a DU, then you can mount it on disk drive 0
through 15. 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 rnanual. Do not remove the V9.7
Installation tape or disk that contains the system installation programs and files.
Go to Task 2.

Prepare System

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.7 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.7 (MSO) INIT V9.7
Today's date? 13-Jun-89
Current time? 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 today's
date and time before proceeding to the next prompt.
Response-Type today's date and time in either of the RSTSIE date and time
formats. Type a question mark (?) to print an online explanation of the response
formats for this question on your console terminal.
Installing RSTS on a new system disk? <Yes>

Explanation-INIT.SYS asks this question whenever you bootstrap a tape or
disk read-only. (RSTSIE Distribution Kits are always read-only.) If you answer
YES, INIT.8YS assumes you are performing a new V9.7 installation and you
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.O or later, 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.7 from a pre-V9.O release of
RSTSIE, see Part 2 of this guide for instructions.
Response-Type YES or press ~ to proceed with the disk initialization.
Because the example installation is a new RSTSIE V9.7 installation, the response
is [~ to accept the default of YES.
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 some disks. DSKIN'r writes timing and sense marks on
the disk and destroys any previously stored information.

•

Optionally checks the disk for bad blocks. DSKINT locates bad blocks on the
disk and allocates them to the bad block file (BADB.SYS).

•

Prepares the disk to accept RSTSIE system and other files.

Terminal Session
'1b initialize your system disk, you must answer the DSKINT questions. This
terminal session lists the questions, explains them, and gives you some possible
responses. Mter you understand the questi.on, type the response at your console
terminal. In some cases, your response win differ from the response shown in red
in the example installation.

These responses have special meaning:
Response

Description

Accept the default response
Obtain an online explanation of the question
1\

Return to the previous question
Restart DSKINT dialogue
Abort DSKINT and return to the Option:prompt

The common DSKINT dialogue error messages appear at the end of this task. If
you receive an error message that does not appear there, see Appendix A.
13-Jun-B9 - 05:02 AM
Disk? DU

Explanation-Mter 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.
Unit? <0> 0

Explanation-DSKINT asks for the unit number of the disk drive on which your
system disk is mounted.

Prepare System

Response-Type one of the acceptable responses at this stage of system
installation: 0 or 1. (If your system disk is a DL class device, acceptable
responses are 0, 1, 2, or 3. If your system disk is a DU class device, acceptable
responses are 0 through 15.) The response is 0 in the example installation.
NOTE

If the message "Perfornling limited hardware scan." was printed during
this boot and you try to initialize or copy to a nonexistent DU type
disk, then you will receive the following prompt:
That disk was not found during limited hardware scan.
00 you wish to perform a reboot with full hardware scan? <YES>

Response-If you answer YES, then the distribution device will be rebooted and
the "Performing limited hardware scan." message will NOT reappear.
This disk appears to be a RSTS/E formatted
disk with the following characteristics:
Pack IO:
Pack Cluster Size:
Pack is currently:

NATHAN
8

Private,
Update access date on writes,
Level: 1.2

Pack IO? SYSOSK

Explanation-Mter 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

•

HSTSIE disk structure 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
RDS1.2.
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
contains no vital information, it will be initialized and used as the new system
disk. If your disk contains vital information, see Part 2, Installing RSTSIE on a
Pre-V9.0 System, for information on how to preserve the information.
Mter printing the pack label information, DSKINT asks for a pack ID. The pack
ID becomes a systemwide logical name.

Prepare System

Response--Type a pack ID. The pack ID can be any combination of alphanumeric characters up to 6 characters long. The pack ID in the example installation
is SYSDSK.
Pack cluster size <4>1

NOTE

Some questions show a response within brackets, such as the one in
this question «4>1). This is the default response. To accept any default
response, press 1RETURN I. (The 1RETURN I response does not print on your
console terminal. The ~ symbol appears in the example installation
to show you that the 1RETURN I 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 RSTSIE 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 2, the monitor allocates only 2
blocks at a time. Thus, more disk accesses and CPU time 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.

Prepare System

Response-Type the disk pack cluster size. For system disks, DIGITAL
recommends a pack cluster size of 4 or greater. In the example installation, the
response is ~ to accept the default cluster size of 4. Table 3 lists the disk
c1 uster sizes.
Table 3:

Disk Pack Cluster Sizes

Disk Type

Pack Cluster Size

RA60
RA80
RA81
RA82
RC25
RD31
RD32
RD51
RD52
RD53
RD54
RK05 1
RK05F 1
RK06
RK07
RL01 1
RL02
RM02
RM03
RM05
RM80
RP04
RP05
RP06
RX33 1

8,16,32,64
4,8,16,32,64
16,32,64
32,64
1,2,4,8,16,32,64
2,4,8,16,32,64
2,4,8,16,32,64
1,2,4,8,16,32,64
1,2,4,8,16,32,64
4,8,16,32,64
8,16,32,64
1,2,4,8,16,32,64
1,2,4,8,16,32,64
1,2,4,8,16,32,64
1,2,4,8,16,32,64
1,2,4,8,16,32,64
1,2,4,8,16,32,64
4,8,16,32,64
4,8,16,32,64
8,16,32,64
4,8,16,32,64
4,8,16,32,64
4,8,16,32,64
8,16,32,64
1,2,4,8,16,32,64
1,2,4,8,16,32,64

RX501
1 _

You cannot use these disks as system disks.

Prepare System

MFD cluster size <16>? ~

Explanation-The master file directory (N.£FD) stores information about all
groups of accounts on a disk. The monitor accesses the MFD to locate and create
tiles and accounts.
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 in this task), and. each directory is the size that you
specify here. If you answer YES, the maxilnum of seven clusters is allocated
now. The MFD cluster size must be greater than or equal to the pack cluster size
unless the pack cluster size is 32 or 64. If the pack cluster size is 32 or 64, then
the MFD cluster size will be 16.
Legal values for the example installation M:FD cluster size are 4, 8, or 16.
Response--Type 4, 8, or 16. Or, press I RETL~ to accept the default response of
16, as in the example installation.
SATT.SYS base <18595>? ~

Explanation-The SATT.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. You are asked 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 or use
LOADIINDEX commands, 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 inlportant because its position determines the default placement of the monitor and the default keyboard monitor, 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 I RETURN I to have DSKINT position the file near the center of the
disk. In the example installation, the response is I RETURN ~
Or, type the device cluster number where you want the file placed.

Prepare System

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:
Disk
Type

RA60
RA80
RA81
RA82
RC25
RD31
RD32
RD51
RD52
RD53
RD54
RK05 1
RK05F 1
RKOS
RK07
RLOl l
RL02
RM02
RM03
RM05
RM80
RP04
RP05
RP06
RX33 1
RX.50 1

Device Cluster Sizes and Total Device Sizes
Device
Cluster
Size

8
4
16
32
1
2
2
1
1
4
8
1
1
1
1

1
1
4

4
8
4
4

4
8
1
1

Total Available Blocks 2

400168
237208
891056
1216640
50901 per unit; 2 units per spindle
41559
83204
21599
60479
138668
311200
4800
4800 per unit; 2 units per drive
27104
53"168
10220
20460
131648
131648
500352
242572
171796
171796
340664
2400
800

You cannot use these disks as system disks.
Total available blocks represent the number of blocks when the disk is initialized at the device
cluster size. The number of blocks on the RAlRCIRD class disks is subject to change with new
revisions of these disks.
1 _

2 _

Pre-extend directories <NO>?

Explanation-This question asks if you want DSKINT to allocate automatically
a maximum of seven clusterEl 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 contains 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). If you answer YES to this question,
Prepare System

you will have faster access time because thE~ blocks will be next to each other in
the accounts. You answer this question YES normally unless disk space usage is
a concern for you.
Response -Type YES to have DSKINT automatically allocat.e a maximum
of seven adjacent clusters to these accounts. In the exam,ple installation, the
response is IRETURN I.
Or, type NO or press I RETURN I if you want DSKINT to allocate only the minimum of

o or 1 clusters.
PUB, PRI, or SYS <SYS>1

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
RSTSIE monitor resides. It always contains account [1,2].
Response-Type SYS or press ~, because you are initializing a system disk
in this task. In the example installation, the response is [RETURN I.
[1,1] cluster size <16>1

Explanation-This question asks for the cluster size of the User File Directory
(UFD) for account [1,1]. The UFD 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 I RETURN I to accept the default response of 16. In the example
installation, the response is ~. 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 unless the
pack cluster size is 32 or 64. If the pack cluster size is 32 or 64, then the UFD
cluster size will be 16. Specifying a large cluster size improves disk access time
and allows more files to be stored in that aecount.
Because the example installation's answer to the Pre-extend directories? question
was NO, DSKINT allocates one cluster containing 8,192 bytes (16 times 512
bytes) to this account.
[1,2] cluster size <16>1

Explanation-This question asks for the duster size of the UFD 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 aC1count 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 si:z;e unless the pack cluster size is 32 or
64. If the pack cluster size is 32 or 64, then the UFD cluster size must be 16.
Press I RETURN I to accept the default response of 16 if the pack cluster size equals 32
or 64.
DIGITAL recommends that the cluster size for account [1,2] be 16, to improve
disk access time. Press I RETURN I 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, DSKINT allocates one cluster containing 8192 bytes (16 times 512 bytes)
to this account.
[1,1] and [1,2] account base <18595>1

Prepare System

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 calcu1ated by DSKINT
if you specified ~ to that question. DSKINT may show a different number
for your disk.
Response--Press I RETURN I to place these accounts near the SATT.SYS file. In the
example installation, the response is ~. 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 ~ 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 RSTSIE monitor updates the date only if the
files are written to. In the example installation, the response is I RETURN I. 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.
New 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 recomlmends that you type NO or press ~ to place
newly created files at the end of the directory, giving you overall faster access
time. In the example installation, the response is I RETURN I.
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-only <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 I RETURN I to make your system disk read/write. In the example
installation, the response is [RETURN I.
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.

Prepare System

Response-DIGITAL recommends that you type YES or press ~ to create
the new bad block file, using information from the existing bad block file. In the
example installation, the response is I RETURN I~
Or. type NO t.o have DSKTNT ignore the current had 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.
Format <NO>?

Explanation-This question asks if you want DSKINT 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 initialJizing them for the first time: RK05,
RK05F, RP04, RP05, RP06, RX33.
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: RLOl, RL02, RA60, RA80, RA8l, RA82, RC25, RCF25, RM80, RD5l,
RD52, RD53, RD54, RD3l, RD32, 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
da ta storage on the disk.
Response-Type YES to format the disk; type NO or press ~ if you do
not need to format the disk. This question does not appear in the example
installa tion.
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
o 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 minutel3) required for the different disks to
complete one format check for bad blocks.
For DU class disks, with the exception of RX50 and RX33, 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.
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 1RETURN I.
Erase disk <YES>?

Prepare System

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-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
installa tion, the response is Y.
Or, type N to abort the initialization and return to the Option: prompt. If you
type N, then you reboot your installation media.
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. Even if there were bad blocks, the hardware would have automatically
replaced the bad blocks with good blocks. If the bad block replacement process
fails, then DSKINT will abort with a fatal error.
13-Jun-89 - 05:17 AM
Copying required system files
Performing limited hardware scan.
RSTS V9.7

(~UO)

INIT V9.7

Explanation-The disk initialization is complete. INIT.SYS now transfers files
that are required for the installation to your new system disk.
When the transfer is complete, INIT.SYS automatically bootstraps your system
disk, prints a. message on your console terminal.
A list of the DSKINT error messages follows. If your error message does not
appear there, see Appendix A.
BLOCK NUMBER TOO BIG
Explanation: The block number you typed is greater than or equal to
the maximum logical block number for the disk.
?DRlVE NOT READY:
Explanation: The initialization cannot proceed because the disk to be
initialized is not on line and ready.
User Action: You can make the drive ready and press I RETURN I to
proceed, or you can press CTRL/C to abort the initialization.

Prepare System

?DSKINT NOT LEGAL ON SYSTEM DISK

Explanation: You specified the disk from which the initialization
code was bootstrapped. You cannot initialize this disk now because the
initialization code would be destroyed.
FORMATTING FAILURE:

Explanation: The disk could not be formatted.
User Action: Mount the disk on the drive and leave it spinning for
20-30 minutes before formatting the disk. If you still receive the same
error message after one retry, then use a new disk.
?ILLEGAL DISK NAME

Explanation: The string you typed is not the name of a valid RSTSIE
disk device.
User Action: Enter a valid name.
?ILLEGAL NUMBER OF PATTERNS

Explanation: The number of patterns must be 0 through 3.
?ILLEGAL NUMBER, TRY AGAIN

Explanation: The number you typed is not a valid octal number
between 1 and 177777.
?ILLEGAL PACK ID

Explanation: The pack ID must eonsist only of characters from "A" to
"Z" or "0" through "9."
?SORRY, BUT THAT DISK DOESN'T EXIST

Explanation: The string you typed is a valid RSTSIE disk name, but
that disk controller or the unit nwnber does not exist on this system.
THAT DISK WAS NOT FOUND DURING LIMITED HARDWARE SCAN

Explanation: You tried to initialize or copy to a nonexistent DU type
disk.
User Action: If you answer YES to the "Do you wish to perform a
reboot with full hardware scan ?", then the distribution device will be
rebooted and the "Performing limited hardware scan." message will NOT
reappear.
?UNABLE TO READ BAD BLOCK TRACK DATA

Explanation: The manufacturer's bad block information could not be
read.
User Action: Either run 3 patterns on the pack or try a different pack.
Go to Task 4.

Prepare System

-fask 4: Start SYSGEN Monitor (START)
DIGITAL supplies a prebuilt RSTSIE 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 RSTSIE monitor. (Phase 7 describes how to shut down the SYSGEN
monitor when it is no longer needed.)

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.
Rebooting
RSTS V9.7

(~UO)

INIT V9.7

13-Jun-89 - 05:17 AM
Creating SWAP.SYS file with minimum size of 128 blocks
Memory allocation table:
OK:
66K:
462K:
512K:

00000000
00410000
03470000
04000000

00407777
03467777
03777777
End

66K)
396K)
50K)

EXEC
USER
XBUF
NXM

Memory available to RSTS/E: is 512K words.
Creating CRASH.SYS file with minimum size of 320 blocks
8 devices disabled

Explanation-INIT.8YS prints these messages as it starts the SYSGEN monitor.
These messages may be slightly different due to configuration differences.
NOTE

I t is sometimes necessary to use the HARDWR option to set nonstandard CSR addresses during this part of the procedure. However,
with RSTSIE V9.7, the SYSGEN.SIL is now started automatically, and
the "Option" prompt is no longer asked.
If you need to access the "Option" prompt, you may do so by typing I\C
(Control-C) twice immediately after the INIT header line is displayed.
The I\C characters will not be echoed on the terminal. Mter a pause of
ten seconds to two minutes, depending on your system configuration,
the "Option" prompt will appear.
If you get the "Option" prompt again when you are finished with your
changes, simply press RETURN to continue with the procedure.
Go to Phase 3.

Prepare System

Phase 3

Configure RSTS/E Monitor
You now have a temporary monitor to use in building your RSTSIE monitor.
Unlike the SYSGEN monitor, which comes pre-built, you must configure your
RSTSIE 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 and so
forth) your RSTSIE monitor will support.
This phase discusses the tasks you must perform to configure your RSTSIE
morritor.
The tasks in this phase are:
•

Task 1: Answer Preliminary Configuration Questions

•

Task 2: Answer Disk Units Configuration Questions

•

Task 3: Answer Peripheral Devices Configuration Questions

•

Task 4: Calculate Number of Jobs

•

Task 5: 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 RSTSIE monitor for anoth(er PDP-11, answer the questions based on the
configuration of the other PDP-1l.
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
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

Task 1: Answer Preliminary Configuration Questions
Your next task is to answer the preliminary questions asked by the installation
procedure. The system executes INSTAL.GOM immediately after it starts the
SYSGEN monitor.
Before INSTAL. GOM asks any questions, it opens a log file named INSTAL.LOG
in the account from which you are running the installation. This account is
always [1,2] since you are logged in automatically. INSTAL.GOM 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.
RSTS/E V9.7
13-Jun-89 05:19 AM
Please mount the RSTS/E Installation media and enter the name
and unit number of the device.
Valid device types are: 'MM', 'MS', 'MT', 'MU', 'OM' or'DL'
Installation device < mmn:>?
Restoring required _SY:[O,l] components
RSTS/E V9.7
Deleting all global symbols
13-Jun-89 05:21 AM
RSTS/E Software Installation Procedure
* Dialogue Phase *
During this installation procedure you may:
Type '?' for help
Type ,A' to go back to the previous question
Type CTRL/Z to return to the beginning of the present section

Explanation-This question asks for the location of your Installation media.
The default is the device on which you booted the Installation media.
Response-Press ~ to accept the default response. In the example
installation, the response is MSO.
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,.
Target disk? <_SY:>:

Explanation-This question is for anyone building a RSTSIE system for another
PDP-11. Your response to this question determines the disk where the new
RSTSIE monitor and system programs win be installed.
If you specify a disk other than the system. disk LSY:), 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. If you don't type _SY:, you must have already updated your system disk.

Configure RSTS/E Monitor

Respon.se--Type the disk name and unit number of the target disk if you are
installing nSTSIE for another PDP-11. You then see the Do you want to initialize
the targ1et disk? question.
Type SY or press [RETURN I to install RSTSIE on your present sYRtem diRk, the d.isk
you initialized in Phase 2. In the example installation, the response is I RETURN ~
Restoring required _SY:[1,2] components
Assigning system logicals
Are you ready to proceed? <yes>

Explanation-This question asks if you are ready to continue. If you type YES
or press [BgruRN I, the dialogue continues. If you type NO, you see the $ prompt.
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 ~ to continue with the installation. In the
example installation, the response is ~J.

** Starting Monitor Section **
13-Jun-89

05:22 AM

Do you want to install the RSTS/E monitor? <yes>

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. You can only skip this if
you already have a current version monitor.
If you answer YES or press ~ to this question, you continue with the
dialogue to install a RSTSIE V9.7 monitor.
If you answer NO to this question, go to Phase 4.
Response--Type YES or press ~ to proceed with the RSTSIE monitor
installation. In the example installation, the response is I RETURN I.
There i:3 a pre-built monitor available which is suitable for
Micro-PDP-11 systems. You may use this pre-built monitor, or
you may build your monitor. Building your monitor will allow
you to specify the features you wish to include in the monitor.
You may now choose:

(A) Build your monitor
(B) Use pre-built monitor

Please type A or B <A> ?
The pre--built monitor MICRO. SIL offer:3 the following features:
RK05's: 0
RK06/RK07's: 0
MSCP support: Yes
TS11/TSV05/TU80's: 1
RX01/RX02's: 0
DMC11's/DMR11's: 0
RJ2780 support: No
EMT Logging: No

RL01/RL02' s: tJ
Disks on DR controller: 0
TU16/TE16/TU45/TU77's: 0
TMSCP tape drives: 2
CR11/CM11 card reader: No
DMP11's/DMV11's: 0
Maximum jobs~ 10

Overlapped seek: Yes
Disks on DB controller: 0
TU10/TE10/TS03's: 0
Printers: 1
CD11 card reader: No
Simultaneous IBM Links: 0
Small buffers: 250

Please t~ype A or B <A> A

Configure RSTS/E Monitor

Explanation- The pre-built monitor has been configured for a Micro-PDP-11
system. However, you can also use this monitor on PDP-11 systems if the
configuration is suitable for your system configuration. The default system
configuration for the re-built monitor is:
Support

Default Value

RK05

RLOIIRL02

Overlapped seek

Yes

RK06IRK07

Disks on DR controller

Disks on DB controller

MSCP support

Yes

11J16r.rEl~45~77

TSIIITSV05~80

TMSCP tape drives

RXOIIRX02

CRII/CMII card reader

No
No

CDll card reader
DMCIl1DMRll

DMPI1IDMVll

Simultaneous IBM links

RJ2780 support

Maximum jobs

Small buffers

250

EMT logging

Response- Type A to build your own monitor or type B to use the pre-built
monitor. If you select B, go to the end of this task.
Restoring requir.ed SYSGEN components

Explanation-The system now copies fileEI that you need to continue the
installation. Then you begin the monitor configuration dialogue.
Starting System Generation
Use template monitor ? <N> NO

Explanation-This question asks if you want the system to obtain default
answers from a previous monitor. If you do have a previous V9.0 through V9.6
monitor and want to use information from it, type YES and then follow the steps
in Phase 3, Task 2 of Part 4. Type NO if you do not have a previous V9.0 through
V9.6 monitor to serve as a template. The default response to this question is NO
if the SYSGEN monitor is the current monitor, and YES if it is not.
Response-Type NO or press~, because you do not have an existing V9.0
through V9.6 monitor to use as a template.. In the example installation, the
response is NO.

40 Configure RSTS/E Monitor

Template monitor's name? <??> ?
A monitor has a name from 1 to 6
alphanumeric characters and a filetype
of "SIL". Enter the name of the
template monitor whose parameters you
wish to use
The following is a list of the .SILs in [0,1]:
File .Typ
V96.SIL
SYSGEN.SIL

Creation
13-Jun-88
13-Jun-89

Template monitor's name 1 <?1>

V96

Explanation- You see this question only if you answered YES to the Use
template monitor? question. You must type the name of an existing monitor.
Response- Type? or I RETU'!!J to accept the default and see a list of monitors in
[0,1], followed by a reprompt for the monitor name. This time type the name of
the monitor you want to USE~ as a template.
New Monitor name ? <RSTS> RSTS97

Explanation-This question asks for the name of your new RSTSIE 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 name for your RSTSIE monitor. The name can be any
combination of alphanumeric characters up to 6 characters long. The default
response is RSTS. In the example installation, the response is RSTS97.
Supersede existing monitor 1 <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 ~ 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 RSTS97 exists.
Accept defaults ? <N>

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, 5).
If you answer YES, the installation procedure chooses the default configuration
and asks no configuration questions.
You can type a ? to list the defaults that will be selected if you answer YES to
this question.

Configure RSTS/E Monitor

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

You are performing a first time V9.7 system installation.

•

You are not using a template monitor.

Type YES if you want to accept the default configuration.
You can type a ? to list the defaults that will be selected if you answer YES.
If you type NO, go to Task 2.

** End of Monitor Section **
Go to Phase 4.

Configure RSTS/E Monitor

Task 2: Answer Disk Units Configuration Questions
Your next task is to answer the disk units configuration questions. These
questions deal with the nwnber and types of disk drives supported by your
RSTSIE monitor.

Terminal Session
This terminal session lists the disk units configuration questions, explains them,
and gives some possible responses (printed in red). Mter 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 with the
numbers and kinds of disk units on this
system.
Accept Disk 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 disk configuration,
and skip to the peripheral device configuration questions (Task 3). DIGITAL
recommends that you answer YES to this question since the installation
procedure chooses appropriate responses based on a hardware scan at system
startup. Answer NO only if you anticipate changes in hardware or if devices were
offline at times of system startup. If you answer NO or press I RETURN ~ you see
these disk configuration questions:
RK05's ?
RL01/RL02's ?
RK06/RK07's ?
Overlapped seek ?
Disks on DR controller ?
Disks on DB controller ?
MSCP support ?

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

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.
Response-Type the number (0 to 8) of RK05 disk drives that your RSTSIE
monitor supports. In the example installation, the default answer indicates that
there are none of these drives; thus, the response is I RETURN I.
If you type 1 or 0, you skip the next question and go to the RLOIIRL02's?
question.

Configure RSTS/E Monitor

MSCP support? <Y>

Explanation-This question asks whether you have MSCP disk drives supported
by the MSCP controllers. The MSCP controllers include the UDA50, KDA50,
RC25, RQDXl, RQDX2, RQDX3, and RUX50 controllers. Availahle disk drives
include the RA60, RA80, RA8l, RA82, RC26i, RD3l, RD32, RD5l, RD52, RD53,
RD54, RX33, and RX50 disk drives.
Response-Type Y if your RSTSIE monitor supports MSCP disk drives. In the
example installation, the program indicates there are MSCP disk drives; thus the
response is I RETURN I.
Go to Task 3.

Configure RSTS/E Monitor

lrask 3: 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 RSTSIE monitor supports. There are also questions related to
DECnetiE, 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-11, answer the questions based
on the configuration of the target system.
The following questions deal with the
peripheral devices attached to this
RSTS/E system.
Accept Peripheral 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 qUlestion, you receive the default peripheral devices
configuration, and skip to the software tuning and features configuration
questions (Task 5). DIGITAL recommends that you answer YES to this question
unless you are not using a template monitor and you require 2780 or card reader
support. The installation procedure chooses appropriate responses based on a
hardware scan at system sta:rtup. If you answer NO or press 11iE'fURN], you see
these peripheral devices con£tguration questions:
TU16/TE16/TU45/TU77's ?
TU10/TE10/TS03's ?
TS11/TK25/TSV05/TU80's ?
TMSCP tape drives ?
Printers ?
RX01/RX02's ?
CR11/CM11 card reader ?
CD11 card reader ?
DMC11's/DMR11's ?
DMV11's/DMP11's ?
IBM 3271 or 2780/3780 simultaneous links ?
RJ2780 support ?

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

Explanation- The TU16/TE16/TU45ITU77 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.
Response--Type the number (0 to 8) of these tape drives that your RSTSIE
monitor supports. In the example installation, the response is ~.
TU10/TE10/TS03's ? <00>

Explanation-The TU10ITE10ITS03 magnetic tape system consists of a TM11,
TMA11, or TMB11 magnetic tape controller and a maximum of eight TUIO, TEIO,
or TS03 magnetic tape drives.

Configure RSTS/E Monitor

Response-Type the number (0 to 8) of these tape drives that your RSTSIE
monitor supports. In the example installation, the response is 1RETURN I.
TS11/TK25/TSV05/TU80's ? <01> ~

Explanation-The TS11 magnetic tape sYBtem consists of a TS11 controller an.d
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 RSTSIE monitor. In the example installation, the response is
I RETURN I to accept the default of 1.
TMSCP tape drives ? <00>

Explanation-RSTSIE can support up to two TMSCP class tape drives. Each
TMSCP controller can support one TK50, 'I'U81, or TU81-PLUS tape drive.
Response-Type the number (0 to 2) of TMSCP tape drives that your RSTSIE
monitor supports. In the example installation, the response is ~.
Printers? <01> ~

Explanation-A RSTSIE monitor can support a maximum of eight LP11 or
LPV11 printers.
Response-Type the number of LP11 or LPV11 line printers (0 to 8) that your
RSTSIE monitor supports. In the example installation, the response is ~ to
accept the default of 1. (Note that the LP11 and LPV11 line printers include the
LP25, LP26, LP27 , LA180-P, and so forth.)
RX01/RX02' 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. RSTSIE does not support the RXV12 flexible
diskette subsystem. The RXOI and RX02 flexible diskette subsystems each
consist of a disk controller and two flexible diskette drives. The RSTSIE monitor
supports a maximum of four RX11, RX211, or RXV11 flexible diskette systems,
for a maximum of eight RX01 or RX02 flexible diskette drives.
Response-Type the number (0 to 8) of R..1(01 or RX02 flexible diskette drives
that your RSTSIE monitor supports. The example installation has none of these
drives; thus, the response is ~.
CR11/CM11 card reader? <N>

Explanation-This question asks if your RSTSIE monitor supports the CR11
punched card reader or the CM11 marked Icard reader.
Response-Type Y if your RSTSIE monitor supports either of these devices; type
N if it does not support either of these dev:ices. In the example installation, the
response is 1RETURN I.
CD 11 card reader ? <N>

Explanation-This question asks if your HSTSIE monitor supports the CD11
high-speed punched card reader.
Response-Type Y if your RSTSIE monitor supports this device; type N if your
RSTSIE monitor does not support this device. In the example installation, the
response is I RETURN I.

Configure RSTS/E Monitor

Card decode ?

Explanation-This question appears only if you answered Y to the CR11/CM11
card reader? or the CD11 card reader? questions. The RSTSIE 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 RSTSIE monitor to support. See the
RSTS / E Programming Manual for more information on the card codes.
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

DMCll's/DMR11's ? <00>

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 DECnet/E but can be used without it.
Response-Type the number (0 to 16) of DMC11 or DMR11 network links
attached to your PDP-11. Because the example installation does not plan to use
DECnet/E or the DMC's by themselves, the response is ~.
DMVll's/DMPll's ?

Explanation-(Note that this question shows either DMV11 or DMP11,
depending on the hardware on your system.) The DMV11 and DMP11 network
links are synchronous communication line interfaces that implement the DDCMP
line protocol in the hardware. The DMV11 and DMP11 links can be used only by
DECnet. This question asks for the number of DMV11 or DMP11 network links
attached to your PDP-1!.
Response-Type the number (0 to 16) of DMV11 or DMP11 network links
attached to your PDP-11. If you type 0, you go to the IBM 3271 or 2780/3780
simultaneous links? configuration question. Because the example installation
will not use DECnet/E, there is no response to this question.
DMVll/DMPll unit xx tribut.aries ?

Explanation-This question asks for the number of tributaries you will activate
at one time. The program prints this question for each DMV11IDMP11 supported
by your RSTSIE monitor. For example, if you type 5 to the DMV11/DMP11's?
question, this question appears five times. (The guide shows this question
only once.) The question refers to either DMV11 or DMP11, depending on the
hardware on your system.
The program repeats the DMV11's1DMP11's? configuration question if you
specified a total of more than 128 tributaries. See the DECnet / E Installation
Guide and DECnet / E Release Notes for information on this question.
Response-Type the numbel' (1 to 12) for the DMV11, or type the number (1 to
32) for the DMP11. Because the example installation does not use either of these
line interfaces, there is no response to this question.

Configure RSTS/E Monitor

IBM 3271 or 2780/3780 simultaneous links ? <00>

Explanation-Each KM:C-ll microprocessor controls one DUPII synchronous
line interface to the 3271 or 2780/3780 host. The 3271 is a terminal; the
2780/3780 is a rem.ote 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 RSTSIE lnonitor 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 H::M:C-11/3271 or KMC-11/2780/3780
simultaneous links you want attached to your PDP-II. Because the example
installation does not support KM:C-lls, the response to this question is 0 or
~.

RJ2780 support ? <N>

NOTE

The 3271 or 2780/3780 IBM protocol emulators are DECUS products.
Explanation-The RJ2780 Emulator Package is a DECUS software product that
emulates the IBM RJ2780 Model 1 data transmission terminal. This software
lets a RSTSIE monitor communicate with any IBM computer that supports these
types of RJE terminals, 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 RSTSIE users to queue files for transmission. DIGITAL
does not provide support for this feature unless you have it in a DIGITAL
Software Services Consultation contract. If you want to use the RJ2780 software,
you must order the RJ2780 software kit from DECUS. For more information on
this software package, see the RSTS/2780 User's Guide. In Phase 5, the system
will tell you when to mount the tape or disk that contains the RJ2780 software.
Response-Type Y to add the code neededl by the RSTSIE monitor to support
this optional DECUS software; type N if you do not want to add this optional
software. Type Y/Q if you intend to use the RJ2780 software on a Q-bus machine
using a DUVII interface. In the example installation, the response is I RETURN I.
Go to Task 4.

Configure RSTS/E Monitor

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

Preparation Session
The RSTSIE monitor assigns jobs to keep track of all user activities. Th calculate
the maximum number of jobs your system needs, add the following:
•

Number of physical tenninals you have or plan to have in use simultaneously.

•

:Number of LAT sessions that will be simultaneously active on your system.
Note that a single user of a terminal server may create more than one
session.

•

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.

•

Number of DECnet SET HOST connections you need.

•

One detached job for ERRCPY, the error logger program that reads errorrelated information stored in the monitor area of memory. A detached job is a
job that is not associated with a terminal. See the RSTS / E System Manager's
Guide for infonnation on ERRCPY.

•

Number of detached jobs for print/batch requests. For the PrintlBatch
Services (PBS).package, allow one detached job for each copy of the PRINT
and BATCH server programs. Each PBS package handles up to three batch
requests and up to two print requests. If the PBS package gets requests
for more ppntlbatch requests than that and additional jobs are available,
then PBS spawns a copy of itself. This copy can handle up to four additional
batch requests and up to three additional print requests. For the OPsERbased spooling package, allow two detached jobs plus one job for each line
printer and batch server. See the RSTS / E System Manager's Guide for more
information on these programs.

•

~rwo to five jobs if your installation uses dial-up terminals. These terminals
may become detached as a result of a faulty phone connection or users
disconnecting without logging out. See the RSTS / E System Manager's Guide
for more information.

•

A number of detached jobs for optional software like WPS-PLUS and
DECnetlE. See the appropriate installation guide for more information on job
requirements.

The example installation calculates a total of 40 jobs:
•

Terminals - 14

•

LAT terminals - 16 (1 DECserver 200 with 2 sessions per terminal)

•

Pseudo keyboards - 6

•

System programs - 4 (1 for PrintlBatch Services requests; 3 for OPSER
requests).

Configure RSTS/E Monitor

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

Job Calculation Worksheet

How many physical terminals do you plan to support?
How many LA T sessions do you plan to have connected to
your system?
How many pseudo keyboards does your software require at
anyone time?
How many DECnet SET HOST connections do you need?
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
ZK-9244-HC

Go to Task 5.

Configure RSTS/E Monitor

Task 5: Answer Software Tuning and Features Configuration
Questions
Your next task iA to answer the soft.ware tuning and featureA configu.ration
questions. These questions deal with RSTS/E monitor software features, such as
maximum number of jobs, slmall buffers, 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 questions deal with the
capacity and features of this RSTS/E
system provided at the system manager's
option.
Accept Software defaults? <N>

EXJ)lanation-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 I RET~, you see these software tuning and features
configuration questions:
Max.imum jobs ?
Small buffers ?
EMT logging ?

Response--Answer NO or press ~ to see the software tuning and features
configuration questions. In the example installation, the response is I RETURN I.
Max.imum jobs ? <25> 40

Explanation-In Task 4 you used the Job Calculation Worksheet to calculate the
number of jobs your RSTSIE 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 LOGINS command (see the RSTS / E
System Manager's Guide).
Response--Check your Job Calculation Worksheet (Task 4, Figure 2) and enter
the maximum number of jobs (2 to 63) your RSTSIE monitor supports. In the
example installation, the response is 40.
Small buffers ? <440> 550

Explanation-A small buffer is a I6-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.

Configure RSTS/E Monitor

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 suboption of the DEFAULT option, located in Part 5 of this guide.
Response-Press 1RETURN I 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.
EMT logging ? <N>

Explanation-EMT logging is a feature that allows the monitor to pass
information on selected monitor directives iby means of send/receive to a program
that you write after you build your monitor. Your prob:rram can then make use of
these monitor directives to log selected kinds of system activity. See the RSTS IE
System Manager's Guide for more information on EMT logging.
Response-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 lB!=TURN I, which accepts the default of NO.

** End of Monitor Section **
Go to Phase 4.

Configure RSTS/E Monitor

Phase 4

Select RSTS/E System Programs
Now that you have finished answering the configuration questions, you are ready
to perfonn the second part of configuring your RSTSIE system. In this phase, you
specify which system programs to install on your system.
The tasks in this phase are:
•

Task 1: Answer System Program Installation Questions

•

Task 2: Answer Layered Product··Related Questions

These responses have special meaning:
Response

Description

Accept the default response
Return to the beginning of a dialogue section
Obtain an online explanation of the question
1\

Return to the previous question

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 perfonn special system management-related tasks.
DIGITAL supplies RSTSIE system programs on the V9 Library and update media.
The programs are grouped into the packages listed in Table 5. See Appendix
C for a complete list of system programs contained in each package as well as
package sizes.

Table 5:

System Program Packages

Package

Description

Auxiliary Library

System programs and data files used with certain peripheral devices and optional
software.

BASIC-PLUS

BASIC-PLUS, a BASIC interpretelr that lets you perform interactive BASIC
programming and also gives you aecess to system programming features such as
system function calls and block 1101. See the BASIC-PLUS Language Manual for
more information. (You answer thE' BASIC-PLUS configuration questions in Task
4A of Phase 5.)

Device Testing

The Device Testing Package. See the RSTSIE System Manager's Guide 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.

Error

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

File Restore

The pre-V9 BACKUP package. This package allows you to restore data from
backup sets created prior to V9.0. See the RSTS IE Utilities Reference Manual for
more information.

Help

Programs that display online help text.

OPSER-based Spooling

The OPSER-based spooling package. See the RSTS IE System Manager's Guide
for more information.

PrintlBatch Services
(PBS)

The RSTSIE V9.x PrintlBatch Services package. See the RSTS IE System
Manager's Guide for more informaUon.

RMSDAP

RMS DECnet Access Package, a set of routines that provides DEC net support for
RMS-I1. See the RSTSIE RMS-l1 User's Guide and the RSTSIE Release ,Notes
for more information.

RMS-ll

A set of routines that allows your programs to gain access to and process (add,
modify, and delete) records and files. Many Layered Products and SORTIMERGE
use RMS-ll. Check your documentation on your specific Layered Product to see if
you need RMS-ll. For information about RM8-11, see the following manuals:

•

•
•
RSX Utilities

RSTSIE RMS-ll: An Introduction and the RSTSIE RMS-ll User's Guide
provide introductory and user information (MACRO-II and high-level language programmer).
RSTS IE RMS-ll Macro Programmer's Guide contains reference information
on the RMS-II operation routines for MACRO-II programmers.
RSTS IE RMS-ll Utilities Manual provides usage and reference information
on the RMS-I1 utility program.s.

Programs that allow you to use programming tools for a variety of languages and
other layered products or use the DCL LINK command from any language.

Select RSTS/E System Programs

Tab.e 5 (Cont.):

System Program Packages

]EJackage

Description

BORTIMERGE

SORTIMERGE 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-II SORT/MERGE User's Guide
for more information. (You answer the SORTIMERGE configuration questions in
Task 4B of Phase 5.)

SOURCE

.BAS source file for selected system utilities

System Library

The standard system library. You automatically receive this package.

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-II TEeO
User's Guide for more information.

Unsupported Utility

Utility programs that are unsupported by DIGITAL. See the RSTS / E Release
Notes for more information.

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.

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

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.
Are you ready to proceed? <yes>

Explanation-This question asks if you are ready to continue. If you type YES
or press I RETURN I, the dialogue continues. If you type NO, you see the $ prompt.
You resume the installation procedure by typing PROCEED.
Response-Type YES or press ~ to continue with the installation. In the
example installation, the response is ~.

** starting System Programs Section **
13-Jun-89 05:23 AM
Do you want to install the System Program packages? <yes>

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 or if you are only installing
layered products, or both, 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 ~ to begin the dialogue. In the example
installation, the response is IRETURN I.
Packages currently installed on the target disk:
<RSX,RMS,DAP,PBS,EDT,UPDATE,TEST,UNSUPP,TECO,AUXLIB,RESTORE,OPSER,
SORT,HELP,BASIC,SOURCES,BLDEDT>
Packages to install? <CURRENTLY INSTALLED LIST> :ALL,NODAP,NOUNSUPP,NOSORT,
SOURCE

Select RSTS/E System Programs

Explanation-The system displays a list of the packages that are available and
then displays a question that asks for the names of the packages you want to
install on your system.
You see this display only if you are using a disk that already has RSTSIE on it.
Response-Type a list of the package nalnes, separated by commas. 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,SOURCES.
Remember, if you make a mistake you can type " to return to the previous
question, or enter CTRUZ to return to the beginning of the section.
Packages to install? <ALL>: ?
The valid responses are:
DIALOGUE

Switches you to the long form of the System
Software Packages dialogue where a more
detailed dE~scription of each package is provided
ALL
Selects all packages
ALL,NOpkg[, ... ]
Selects all packages except pkg
,pkg [, ... ]
Adds pkg to t~he default list (during an upda'te)
,NOpkg[, ... ]
Deletes pkg from the default list
Use a comma as a separator. e.g.: RSXyPBS,RMS
Package names:
AUXLIB
Auxiliary Library
BASIC
Basic-Plus
DAP
RMS DECnet Data Access Package
(includes RMS-ll)
EDT
EDT Editor
HELP
Help Package
OPSER
Opser-based Spooler
PBS
Print/Batch Services
RESTORE File Restore

RMS
RSX
SORT
TECO
TEST
UNSUPP
UPDATE

RMS-ll
(includes RSX Utilities)
RSX Utilities
Sort/Merge
(includes RMS-ll)
TECO Editor
Device Testing
Unsupported Utilities
Update Package

Packages to install? : ALL,NODAP,NOUNSUPP,NOSORT,SOURCE

Explanation- If the disk you are using does not already have RSTSIE on it, you
see this display of the available system programs.
Mter 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 aSl30ciated 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 CTRUZ 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.

Select RSTS/E System Programs

In the example installation, the response is ALL,NODAP,NOUNSUPp,NOSORT,
SOURCE.
The following will be installed:
RSX
RMS
EDT
PBS
UPDATE
TEST
TECO
AUXL1B
RESTORE
OPSER
HELP
You may answer "Yes" to accept this list, or "No" to change it.
Is this list OK? <yes>

Explanation- The system lists the packages it will install and asks if this list
of packages is the one you want. If you answer NO to this question, you return to
the Packages to install: prompt.
Response-Type YES or press ~ to continue with the installation. Or, type
NO if you want to change the packages to install on your system. In the example
installation, the response is [RETURN I.
Do you want the 1&D versions of tasks? <Y> 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 and/or
AUXLIB in response to the Packages to install: question.
Instruction and Data (I&D) space is available on the PDP-11/44, 45, 50, 53, 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 I&D space. If your system has
more than 256K words of memory (PDP-11/44, 53, 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.
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. You will be asked to set the size of SWAP.MAX. later in the installation.
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 or press ~ to receive the I&D versions of tasks. Type
NO to receive the normal versions. The example installation does not plan to use
I&D space; thus, the response is NO.
Use resident library version of RMS? <Y> ~
Use RMS resident libraries in DAP? <Y> ~
Use RMS resident libraries in PBS? <Y> ~
Use resident library version of EDT? <Y> ~

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 versiQns if your system has sufficient memory and you have more than
one user accessing a program simultaneously.
Response-Type YES or press ~ to install the resident library version.
Type NO to install the overlaid version. The response in the example installation
is [!!!=::!Qffi!) because it has sufficient memory to install the resident library versions.

Select RSTS/E System Programs

During the build phase there will be further questions
for BASIC-PLUS and SORT/MERGE

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

** End of System Programs Section **
Are you ready to proceed? <yes>

Explanation-You are finished with the System Programs Section. This
question asks if you are ready to continue. If you type YES or press I RETURN ~ the
dialogue continues. If you type NO, you see the $ prompt.
You resume the installation procedure by typing PROCEED.
Response-Type YES or press ~ to continue with the installation. In the
example installation, the response is I RETURN].
13-Jun-89 05:24 AM

** Starting Layered Products Section **
You may now transfer the layered product update components
from the Installation kit.
Do you wish to do the transfer? <yes>

Explanation-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 install any layered products on your system. If you answer
YES, you continue the Layered Products S'ection.
Response-Type YES or press ~ to continue the Layered Products Section.
Type NO to skip the section. In the example installation, the response is YES.
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

-rask 2: Answer Layered Product-Related Questions
You perform this task if you plan to install layered products on your RSTSIE
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 tIris 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 RSTSIE Installation Procedure does not perform a layered product
installation. See the individual layered product installation guide for
the procedures to perfOIID the installation.

Terminal Session
This terminal session explains the layered product-related questions and provides
some possible responses.
13-Jun-89 05:24 AM

** Starting Layered Products Section **
You may now transfer the layered product update components
from the Installation kit.
Do you wish to do the transfer? <Yes>

Explanation-You see this question at the end of Task 1.
Response-Type YES or press ~ to begin the dialogue to transfer layered
products updates. Type NO to skip this section. The example installation
response is 1RETURN I.
Product updates to transfer: ALL

Transfers all product updates
Transfers all product updated except prod
Adds pkg to the default list (during an update)
Deletes pkg from the default list

Use a comma as a separator. e.g.: BP2,C81
Product names:
BP2
C81
DECDX
DECNET

DIBOL
DTR
FMS
FORTRAN

FRTRN77
MAIL
MENU
PDPDBG

PLXY
RJ2780
WPS
2780 3780

3271

Product updates to transfer?:

Explanation-Mter you type a ?, you see the list of available layered products.
Then the system reprompts for the product updates to transfer.

Select RSTS/E System Programs 61

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 s€iction.
Type ALL to t.rAn~fer all the update!=!. If you plan t.o tranF.tfer nearly

an of the

product updates, type:
ALL,NOnnnnnn,NOnnnnnn
where nnnnnn refers to a product update you want to exclude.
The following will be transferred:
BP2
DIBOL
FRTRN77
PLXY
3271

C81
DTR
MAIL
RJ2780

DECDX
FMS
MENU
WPS

DECNET
FORTRAN
PDPDBG
27803780

You may answer "Yes" to accept this list, or "No" to change it.
Is this list OK? <yes>

Explanation-The system lists the produd 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 ~ 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 requil:-e the Update package
(from the System Programs section), ii:. will be included.
To install a layered product please rE::fer 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$:.
Mter you complete the RSTSIE 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 £01' a description of BUILD.
Response--Press I RETURN I 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

Phase 5

Generate RSTS/E System
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 perfonn in this phase are:
•

Task 1: Create Additional System Files

•

Task 2: Create RSTS/E Monitor

•

'rask 3: Install System Programs from the Installation Media

•

'rask 4A: Answer BASIC-PLUS Installation Questions

•

'rask 4B: Answer SORTIMERGE Installation Questions

These responses have special meaning:
Response

Description
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, SWAP.SYS (this is the primary file), 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 file 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 5 of Phase 3.
You can create other system files later by u.sing the INIT.SYS REFRESH option
or the DCL INSTALL command. For a detailed description of system files, see
the REFRESH Option section in Part 5.

Terminal Session
This terminal session explains how to specify a password for account [1,2].
You must now set the password for account _SY:[1,2]
New password:
New password again, for verification:
Password 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 into in case of unf:oreseen problems. DIGITAL does not
recommend that you log into 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
multinational character, including the space character, but not the? character.
Retype the password when prompted.
This is the end of the DIALOGUE phase.
The next phase is the BUILD phase.
Are you ready to proceed? <yes>

Explanation-The system asks if you are ready to generate your RSTSIE
system. If you are ready to proceed, type YES or press @Q!![I.
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 RSTSIE monitor. Type the
following to make EDT available at this point for unsupported modifications:
$ RUN SYSGEN$:EDT

Mter making any modifications, type PROCEED to continue the installation.

Generate RSTS/E System

Response-Type YES or press ~ to begin the build phase of the installation.
In the example installation, the response is ~ because it is ready to proceed.

* Build phase *
13-Jun-89 05:31 AM
What size would you like SWAPMAX to be? <64>

Explanation- This question is displayed only if you have Instruction and Data
(I&D) space hardware, otherwise SWAPMAX is automatically set to 32.
The RSTSIE monitor moves jobs from memory to disk as needed. 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 maximwn 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 I&D
space. You can specify a size up to 64K.
Response- Type the new SWAPMAX (a number from 32 to 64).
Do you want _SYO:SWAP1.SYS created (at xxxx blocks)? <yes>

Creating _SYO: [O,1]SWAP1.SYS at xxxx 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 SWAPl.SYS as close to the center of the system disk as possible. The
system detennines the size of SWAP1.SYS according to this formula:
(JOB MAX-l) * SWAP MAX * 4

where:
JOB MAX-I

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

SWAP MAX

is the value given in answer to the SWAP MAX. question, or is 32K words
if you do not have I&D space hardware.

You do not see this message if your system has a SWAP1.SYS file and if you are
performing an on-line installation.
You might not want to create SWAP1.SYS on your system disk. Type NO in this
case. Use the following DeL command to create swap space manually:
$ INSTALL/SWAPFILE name

Response-Type YES or press ~ to create SWAPl.SYS. Type NO to skip
the creation of SWAPl.SYS. 'rype a ? if you want to know the size of SWAPl.SYS
before you answer the question. In the example, the response is~. The
system then creates SWAP1.SYS at a size of 4992 blocks.
Creating RSTS/E monitor

Go to Task 2.

Generate RSTS/E System

Task 2: Create RSTS/E Monitor
The command procedure now creates your RSTSIE monitor.
Note that the time required for t.his process varies according to the type of your
CPU and the size of your monitor. The following are some general guidelines for
the time for this step:
•

If you are creating your RSTSIE monitor on an 11/70, 11173, 11183, or an 11/84
CPU, this process could take up to 30 minutes.

•

If you are creating your RSTSIE monitor on an 11145, 11/50, 11155, or an 11160
CPU, this process could take up to 1 hour.

•

If you are creating your RSTSIE monito]r on an 11/34, 11135, or an 11/40 CPU,
this process could take up to 2 hours.

•

If you are creating your RSTSIE monitor on an 11/23 or an 11/24 CPU, this

process could take up to 3 hours.
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 RSTSIE 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
exceeds RSTSIE configuration limits.

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

Explanation-The command procedure now begins the RSTSIE monitor
generation.
If you answered YES to the RJ2780 support? question in Task 3 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.
Valid device types are: 'MM', 'MS', 't-1T',
'OM', 'OL' or ' SY'
Installation device < dev:> :

You may have to dismount the RSTSIE 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 RSTSIE Installation media later. Remount the installation media on
the indicated drive when prompted.

Messages Produced While Building a RSTS/E Nlonitor
%Small buffers lowered by xxx buffers
This will leave you with yyy buffers

Generate RSTS/E System

Explanation-The command procedure checks whether the number of small
buffers you specified in Task 5 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. If the number of smaH
buffers you specified in Task 5 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 1. 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 such as fewer devices. Also,
specify a much smaller number to the Small buffers? question in Task 5. In
general, 600 to 700 is a good response to the Small buffers? question.
See the BUFFERS suboption of DEFAULT in Part 5 of this guide for more
infonnation on small buffers.
The command procedure did not lower the number of small buffers in the example
installa tion.
This monitor has a valid buffer count
Monitor creation 20% complete.
Monitor creation 40% complete.
Monitor creation 60% complete.
Monitor creation 80% complete.
Directory of SIL V97
.SIL on 13-Jun-89 at 05:32 AM
Name

Ident

Load

Size

Transfer

Total

RSTS
MVR

09.703
09.701

000000
120000

116500
014100

000001
000001

20K
23K

OV2
DEFALT

09.702
09.701

002000
001000

034000
003000

000001
000001

118K
119K

Maximum buffers available without using data space:
415 general small buffers.
90 FIP small buffers.
Maximum buffers available using data space:
668 general small buffers.
494 FIP small buffers.
If you choose to restart the installation, you may
specify up to 573 small buffers for this system.
Doing so will increase thE! number of general buffers
available both with and without data space.
Monitor creation 100% complete.
Before attempting to start your new SIL, you must have swap
file space of 11264 blocks and if you use files other than
SWAP1.SYS you must also edit START. COM to install them.

Explanation-You see these messages if your new monitor is an acceptable size
and the build progresses satiEfactorily.
Go to Task 3.

Generate RSTS/E System

Task 3: Install System Programs from th~3 Installation Media
The system now installs the system programs according to the instructions
you gave in Phase 4. First, the system transfers the r1emaining files from the
Installation tape or disk. The system also transfers any layered product updates
you specified in Phase 4. This task should take fifteen to twenty 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 assodated logical name, it installs the
package at the default location. This is the case in a new installation.
Table 6 lists the logical names and default ]locations for each package.
Table 6:

System Program Package Loglcnl Names

Package

Logical Nam.e

Location

Auxiliary Library

AUXLIB$:

[0,14]

BASIC-PLUS

BASIC$:

[0,12]

Device Testing

TEST$:

[0,5]

EDT

EDT$:

[0,11]

Error

ERROR$:

[0,3]

File Restore

RESTOR$:
HELP$:

[0,7]

OPSER$:

[0,8]
[0,6]

RMS-ll

PBS$:
RMS$:

[0,10]

RSX Utilities

LB:

[1,1] [1,2]

SORTIMERGE

SORT$:

[0,15]

SOURCE

SOURCE$:

[0,17]

System Library

SYSLIB$:

[1,2]

TECO

TECO$:

[0,13]

Unsupported Utility

UNSUPP$:
UPDATE$:

[0,9]

Help
OPSER-based Spooling
Print/Batch Services (PBS)

Update

[0,2]

[0,4] [1,2]

Terminal Session
This terminal session explains the procedures that transfer the system programs
from the Installation media.
13-Jun-89 05:48 AM
Restoring the xxxxxx package from the Installation kit
There are no updates for the xxxxxx package

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.

Generate RSTS/E System

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.
13-.1un-89 os :25 AM
Restoring the System Startup files from the Installation kit
Restoring the System Library package from the Installation kit
Restoring the Error package from the Installation kit
Restoring the RSX Libraries from the Installation kit
Restoring the RSX Utilities from the Installation kit
Restoring the RMS-11 package from the Installation kit
Restoring the RMS Libraries from the Installation kit
Restoring the Print/Batch Services package from the Installation kit
Restoring the EDT package from the Installation kit
Restoring the Update package from the Installation kit
Restoring the Device Test.ing package from the Installation kit
Restoring the Unsupported Utilities from the Installation kit
Restoring the TECO package from the Installation kit
Restoring the Auxiliary Libraries from the Installation kit
Restoring the File Restore package from the Installation kit
Restoring the Opser-based Spooling package from the Installation kit
Restoring the Help package from the Installation kit
Restoring the Program Sources from the Installation kit
Resi:oring the EDT Maintenance package from the Installation kit
Restoring the Resident Libraries from the Installation kit

Mter 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:
Restoring the xxxxxx update components from the Installation kit

where xxx.xxx is the name of the layered product. For the sample installation, the
system prints the following messages:
13-Jun-89 05:26 AM
Restoring BP2 update components from the installation kit
Rest;oring C81 update components from the installation kit
Restoring DECDX update components from the installation kit
Restoring DECNET update components from the installation kit
Restoring DIBOL update components from the installation kit
Restoring DTR update components from the installation kit
Rest.oring FMS update components from the installation kit
Restoring FORTRAN update components from the installation kit
Restoring FRTRN77 update components from the installation kit
Restoring MAIL update components from the installation kit
Restoring MENU update components from the installation kit
Restoring PDPDBG update components from the installation kit
Restoring PLXY update components from the installation kit
Restoring RJ2780 update components from the installation kit
Restoring WPS update components from the installation kit
Restoring 27803780 update components from the installation kit
Rest.oring 3271 update components from the installation kit
RSTS/E V9.7
13-Jun-89 05:26 AM
RSTS/E Software Installation Procedure
13-Jun-89 05:26 AM
START.097 and LOGIN.097 in account [0,1] are the templates
for those .COM files. Your present .COM files should be
edited to reflect any changes.

Explanation- This message indicates that there are two templates available for
you to edit to create START.COM and LOGIN.COM for your system as directed
in Phase 6.

Generate RSTS/E System

You see this message only when your system already has a version of
START.COM and LOGIN.COM. Otherwise, the procedure renames START.097
and LOGIN.097 to START.COM and LOGIl'f.COM.
13-Jun-89 05:26 AM
Installing system packages

Explanation- The system now begins installing the system packages.
If you specified BASIC-PLUS as one of the packages to install, then go to Task 4A
for a complete description of the BASIC-PLUS dialogue and return to this point.
Otherwise, continue with this task. The example installation does not plan to
install BASIC-PLUS.
If you are not installing BASIC-PLUS but you want to install SORTIMERGE,
then go to Task 4B for a complete description of the SORTIMERGE dialogue and
return to this point. Otherwise, continue with this task. The example installation
does not plan to install SORTIMERGE.
Finished installing system packages
13-Jun-89 05:26 AM
The RSTS/E Software Insta.llation Procedure is complete
Would you like to start your new monit.or now? <Y> YES

Explanation- Mter the system packages are installed, you are asked if you
want to start your new monitor now.
Response- Type YES or press ~ to have the system start your new monitor.
If you type NO, you will have to shut down the SYSGEN monitor and start your
new monitor as directed in Phase 7.
Deleting all global symbols
Oeassigning system logicals
13-Jun-89 06:17 AM
System tape label default set to DOS
SY:[1,2]INSTAL.LOG is a log file of this session
Please wait for system to re-boot itself

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. The procedure then automatically shuts down the
SYSGEN monitor and starts your new monitor.
RSTS V9.7 SYSGEN (DUO) INIT V9.7
13-Jun-89 - 6:20 AM
Memory allocation table:
OK:
67K:
446K:
512K:

00000000
00414000
03370000
04000000

00413777
03367777
03777777
End

67K)
379K)
66K)

EXEC
USER
XBUF
NXM

Memory available to RSTS/E is 512K weIrds.
Re-creating CRASH.SYS file with minimum size of 380 blocks

Explanation-INIT.SYS starts the currently installed monitor, RSTS97.SIL, and
starts timesharing under it.

Generate RSTS/E System

The procedure then prints the current memory allocation table and checks that
the CRASH.SYS file exists 1m account [0,1] on the system disk, is large enough
for the installed RSTSIE monitor and extended buffer pool allocation, and is
contiguous.
13-Jun-89 - 06:22 AM
8 devices disabled
Proceed with system startup? <YES>

Beginning RSTS/E system startup ...
13-Jun-89 06:22 AM
Mounting disks
13-Jun-89 06:22 AM
Assigning logical names
13-Jun-89 06:22 AM
Starting error logging
13-Jun-89 06:22 AM
Setting system characteristics
13-Jun-89 06:22 AM
Installing run-time systems and libraries
13-Jun-89 06:23 AM
Setting terminal characteristics
13-Jun-89 06:23 AM
Defining system commands
13-Jun-89 06:23 AM
Setting printer characteristics
13-Jun-89 06:23 AM
Starting spoolers
Print/Batch Services started at 06:23 AM

Explanation- The procedure pauses for several seconds while it performs the
necessary tasks to start timesharing. It then asks if you are ready to proceed
with the start up.
Response- Type YES or press ~ 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 ~.

*** From [1,2] on KBO: at 06:23 AM on 13-Jun-89
** RSTS/E is on the air ...
~
RSTS V9.7 13-Jun-89 06:24 AM

User:

Explanation- You are finished with the installation. You can now press~
to log in to the system. RSTSIE then prints its banner followed by the User:
pro:mpt. You can now enter 1,2 to log in to account [1,2], which is currently the
only account on the system. You then see the password: prompt. Enter the
password you specified during the installation procedure.
Go to Phase 6.

Generate RSTS/E System

Task 4A: Answer BASIC-PLUS Installation Questions
You perfonn 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 BASICPLUS 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 to keep the size at or below 16K.

Terminal Session
This tenninal session explains the BASIC-PLUS installation questions and
provides some possible responses. For more infonnation 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 exanlple installation.
Beginning of RSTS/E Basic-Plus generation.
BASIC-PLUS RTS name? <BASIC>

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.
Response-Type a name for your BASIC-PLUS run-time system or press I RETUR!i£J
to accept the default of BASIC, as in the example installation. The name can be
any combination of alphanumeric characters up to 6 characters long.
FPP? <Y>

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-11/23 PLUS, 11124, 11/34, 11/44, 11145, 11150, 11/65,
and 11/70. It is standard hardware on the :11/53, 11/60, 11173, 11/83, and 11/84.
Response-You see a Y default if your PDP-11 has FPP; you see a N default if
your PDP-11 does not have FPP. Type YES or press L£!!ITQffi!I if your PDP-11 has
FPP; type NO or press I RETURN I if it does not. If you type YES, the program goes
to the Math precision? question. If you tYIle NO, the program goes to the FIS?
question. In the example installation, the response is IRETURN I.
FIS ? <N> ?
Will this software run on a computer
with the floating instruction set
(YES or NO)?

Explanation-This question asks if you want the floating instruction set (FIS)
installed. The FIS is hardware that provides single-precision floating point
instructions. The FIS instructions are only available on the PDP-11140 and 11/36.
Response-Type Y if you want the FIS inl~talled. Press IM!.Q!@ or type N if you
do not want the software to use FIS installed on your system.

Generate RSTS/E System

Math precision? <02> 4

Explanation-This question asks if you want your math package to support
single-precision or double-precision floating point instructions. The singleprecision 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 ~ 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.
Table 7 lists the BASIC-PLUS optional features. If you must omit some optional
features, use Table 7 to determine which combinations you can select. You can
include features with a total size of up to 6. Your choice of features will depend
on which applications you plan on using.
Table 7:

BASIC-PLUS Optional Features

Feature

Size

Log functions

Trig functions

Print using

Matrices

String arithmetic

Log functions? <Y>

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 BASICPLUS run-time system by answering N to this question. Operations such as X"Y
require the log functions if Y is not an integer.
Response-Type YES or press ~ to add the logarithmic functions; type NO
if you do not want to add the logarithmic functions. In the example installation,
the response is 1RETURN I.
Tri9 functions? <Y>

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.
Response-Type YES or press ~ 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 1RETURN I.
Print using? <Y>

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.

Generate RSTS/E System

Response-Type YES or press ~ if you need this feature; type NO if you do
not need this feature. In the example installation, the response is I RETURN I.
Matrices? <N> Y

Explanation-This question asks if you want BASIC-PLUS to operate on an
entire matrix using single MAT statementEl.
Response-Type YES if you need this feature; type NO or press~ifyou do
not need this feature. In the example installlation, the response is Y.
String arithmetic? <N>

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 nwneric 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 nwnbers, such as monetary conversions.
Response-Type YES if you need this feature; type NO or press~ifyou
do not need this feature. In the example installation, the response is ~ to
accept the default of NO.
Return to the point in phase 5 task 3 from which you left.

Generate RSTS/E System

Task 48: Answer SORT/MERGE Installation Questions
This task describes the SORTIMERGE installation questions. You see these
questions if you specified SORTIMERGE in response- to the Packages to install:
prompt in Task 1 of Phase 4. DIGITAL recommends that most users installing
SORTIMERGE accept the system defaults for the SORTIMERGE package. The
defaults will meet the needs of most users. Prior to starting any SORTIMERGE
operation, you will be able to change the default response to a different response
for that particular SORTIMERGE operation. See the PDP-II SORT/MERGE
User's Guide for more infonnation on SORTIMERGE.

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

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

This is the beginning of the dialogue to

* define the attributes of your SORT/MERGE utility.

************************1~*****************************

This procedure will, by default, build and install
SORT and MERGE for optimum performance. The utility
SORT and MERGE tasks will have the following attributes:
SORT built at 32K/MERGE built at 32K
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
Additionally, the default will NOT build the
SORT and MERGE callable subroutines as a resident library.
If you want the installation to proceed using
these defaults, answer YES. If you want to
change any of these defaults, answer NO.
Do you want to proceed with the default installation <Yes>?

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 change the default size of the SORT
or MERGE task, answer YES, otherwise answer NO.
Do you want to change 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 changing the default size of the work
area. The work area is currently set to be the
maximum allowed by your operating system in order
to give SORT/MERGE the optimum performance.
Which task size do you want to change
SORT
MERGE
BOTH
NEITHER

<BOTH>?

Generate RSTS/E System

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 6.
3. The maximum SORT task size is 32K on your system.
ThA minimum SORT task size is ]7R words.
The chosen size must be a whole number between these
inclusive limits. Decimals will be truncated.
What size do you want your SORT taHk to be

<32K>?

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 Qu.estion 5.
4. The maximum MERGE task size is 32K 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 <32K>?
5. If you want to change any of the
YES, otherwise, answer NO.

dE~fault

run-time options, answer

Do you want to change any of the

dE~fault

run-time options

<NO>?

***************************************************
* IF YOU CHANGE ANY OF THE DEFAUL~~S, 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 collating sequence
when operating on character data keys.

If you answer YES, you can change the ASCII collating sequence to another
collating sequence in question 7.
Do you want to change the default collating sequence

<NO>?

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 rIDLTINATIONAL.
What do you want the default chara(~ter 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 records with
duplicate keys by default, answer NO.
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:
*~*************************************************************

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

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

Generate RSTS/E System

If you answered YES, go to Question 10.
9. Stable SORT/MERGE imposes extra overhead during the
key comparison process. For this reason, the default is
for a nonstable SORT/M:ERGE. If you wish to change this
default, answer YES, o'therwise 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 structures. 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 65%.
Your answer must be in whole numbers. <55>?
12. The MERGE work area is divided into two areas, one
for the MERGE data structure and one for the
RMS I/O data structures. For MERGE, 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 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 I/O requirements.
If you want to change the default split, answer YES,
otherwise answer NO.
Do you wish to change the MERGE default split

<NO>?

If you answer NO, go to QueBtion 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 default, 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 3, the maximum is 10.

Generate RSTS/E System

Changing the nwnber of work files may change the performance of SORT
depending on the data being sorted. See the PDP-ll SORT/MERGE User's Guide
for more information on changing the numher of work files.
How many work files should SORT use by default?

<5>?

16. By default, 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 space,
you may change this default.

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

PLEASE NOTE THAT FOR SORTS USING OTHER THAN THE RECORD
PROCESS, 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 sequence check the input records.
If you want to change this default, answer YES,
otherwise answer NO. <NO>?
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 change the number of
retries, answer YES, otherwise answer NO.
Do you want to change 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 calla.ble SORT and MERGE
resident library answer YES, otherwise answer NO.

If you answer NO, the object libraries will be built into your program upon
completion of linking your program. If you answer YES, you will have more free
disk space and a faster run-time than if you answered NO.
Do you want to build a combined callable SORT and MERGE
cluster library <NO>?

This completes the selection of attributes for your SORTIMERGE utility. The
installation procedure now shows you the a.ttributes 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.)

Generate RSTS/E System

22. ***********************************************
* Your SORT and MERGE product will be built *
* according to the following specifications: *

***********************************************
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
RECORP 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 dialogue.
The installation will now proceed without
further operator intervention.

*
*

"fl'

**************************************************
Running SORT/MERGE certification tests

The installation procedure then continues without operator intervention. It will
task build and install the utilities, place the callable overlay description files
in [0,15], and automatically execute a SORTIMERGE operation to verify that
SORTIMERGE 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!
?
?????????????????????1??????????????????????

If no errors are encountered, return to the point in phase 5 task 3 from which you
left.

Generate RSTS/E System

Phase 6

Create Accounts and Edit System Startup File
Mte'r you finish Phase 5, you are ready to tailor your new RSTSIE system.
The tasks in this phase are:
•

Task 1: Create the System Management Account (CREATE/ACCOUNT)

•

~rask 2:

•

~rask 3: Edit System Startup File

Create User Accounts (CREATE/ACCOUNT)

Task 1: Create the System Management Account
(CREATE/ACCOUNT)
In t.his task you create the syst.em management Account on your Flyst.em disk
with the CREATE/ACCOUNT 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 CREATE/ACCOUNT command to establish such
things as disk quotas and privileges. Because the detached jobs quota is set to
zero by default, be sure to set it to some other value, such as 3, so you can start
detached jobs from the system manager's account. If you are not familiar with
the qualifiers for the CREATE/ACCOUNT command, see the RSTS / E System
Manager's Guide.

Terminal Session
This terminal session explains how to use the CREATE/ACCOUNT command to
create the system management account.
Type a command of the following format:
CREATE/ACCOUNT dev:[p,pn]/PRIVILEGES=(abc,def, ... )
Password: <password>
Password again, for verification: <password>

Explanation-The CREATE/ACCOUNT command establishes accounts on
your RSTS/E system. If you omit the deviee specification, the default is the
system disk, SYO:. The only time you would specify a device is if you are
building a target disk. You specify the account privileges as a list following the
/PRIVILEGES qualifier. See the RSTS / E System Manager's Guide for more
information about privileges. The password can be any combination of DEC MeS
characters inel uding the space character but not the? character. The password
can be from 6 to 14 characters long. The password is /NOLOOKUP by default.
This makes it impossible to look up the password, thus providing additional
account security. 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,4]/PRIVILEGES=ALL
Password:
Password again, for verification:
Account _SYO:[1,4] created at DCN 27345

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

It is recommended that you pick an account number other than the
example [1,4] since it is very likely that a hostile user may attempt to
attack these "sample" accounts.
Back Up the System Disk Onto Anothf~r Disk or Tape
Back up the system disk onto another disk or tape (Backup program) prior to
creating user accounts. You can use the online V9.7 BACKUP utility to copy your
system disk. See the RSTS / E System Manager's Guide for more information.
Go to Task 2.
82

Create Accounts and Edit System Startup File

'Task 2: Create User Accounts (CREATE/ACCOUNT)
In this task you create user accounts on your system disk with the
CREATE/ACCOUNT 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 CREATE/ACCOUNT command, see the RSTS / E 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:[p,pn] [/QUALIFIERS]
Password: <password>
Password again, for verification: <password>

Explanation-The CREATE/ACCOUNT command establishes accounts on your
RSTSIE system. If you omit the device specification, the default is the system
disk, SYO:. The password can be any combination of DEC MCS characters
including the space character but not the? character. The password can be from
6 to 14 characters long.
Go to Task 3.

Create Accounts and Edit System Startup File

Task 3: Edit System Startup File
Your next task is to edit START.COM, the system startup file. This command file
must contain the information required to properly initia1ize the system for both
normal time-sharing operations and systenl 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:
•

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

•

Add startup commands for the OPSER··based spooling package.

•

Add system logical definitions or commands associated with software not
provided by DIGITAL.

See the RSTS/E System Manager's Guide for more information about editing the
START. COM file.
NOTI:

The START.COM file provided by DIGITAL contains sufficient
commands to start your new V9.7 system. 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 startup file. You have already installed
EDT on your system ..

Terminal Session
This terminal session explains how to edit the DIGITAL-provided START.COM
command file. First you make a backup copy of START.COM. Responses in the
example installation are printed in red.
$COpy [O,l]START.COM [O,l]START.OLD

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.OLD in account [0,1].
$TYFE [O,l]START.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 tenninal and want to get a printed copy of
START.COM, type PRINT [O,l]START.COM.

84 Create Accounts and Edit System Startup File

Response-Type the command as shown to list the START.COM file.
NOTE

If you huilt. the re~ident. lihrrtry version of EDT, issue the
INSTALILIBRARY ED1'$:EDT command before editing START. COM.
Otherwise, the edit command will fail and display the ?Unable to
attach to resident library error message.
$EDIT/EDT [O,l]START.COM

Explanation-Use this command to start the EDT editor. The first line of your
file will be shown on the screen with an * prompt at the left margin. Mter you
type C and press~, 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.
Res:ponse-Type the command as shown. Type C and press ~ at the * prompt
to have your file shown on your screen.
*EXIT
$

Response-Press CTRUZ to return to the * prompt. Type EXIT at the * prompt
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
[O,1J with your version.
Go to Phase 7.

Create Accounts and Edit System Startup File

Phase 7

Start RSTS/E Monitor
This phase describes the tasks you must perfonn to start your RSTSIE monitor if
you do not choose to have the installation procedure start it for you.
The tasks in this phase are:
•

Task 1: Shut Down SYSGEN Monitor (SHUTUP)

•

Task 2: Start your custo:m RSTSIE Monitor (START)

These responses have special meaning:
Response

Description

Accept the default response

Obtain an online explanation of the question

Task 1: Shut Down SYSGEN Monitor (SI-IUTUP)
Now that you have built your RSTSIE monitor, you no longer need the SYSGEN
monitor. 1b 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. You can now shut down the SYSGEN monitor.
Response-Type RUN $SHUTUP to shut down the monitor.
SHUTUP V9.7-08

RSTS V9.7-11 SYSGEN

6:19 AM 13-Jun-89
Type

fAf

********

Set-up Dialogue Phase

to any query to backup one question

Minutes until system shutdown (0-99) <5>? 0
Shutdown with automatic RESTART <NO>?

Explanation-SHUTUP prints a header and some preliminary information. It
then asks you to type the minutes to wait before the RSTSIE monitor shuts down.
This question is useful for giving system users fair warning when shutting down
the system. The system also asks if you want an automatic RESTART to the
system. The default response is NO.
Response-Type O. Press~ or type :No to accept the default response. You
should never answer YES at this point in the installation procedure. You must
shutdown the system in order to start the new monitor.
6:19 AM 13-Jun-89 ********
Warning Message Phase
Further LOGINs are now disabled
6:19 AM 13-Jun-89

********
6:19 AM 13-Jun-89
********
6:19 AM 13-Jun-89
********
6:19 AM 13-Jun-89
********
6:19 AM 13-Jun-89
********

Initial Job Killing Phase
Remove RTS/RES LIB Phase
SWAP File Removal Phase
Disk DISMOUNT Phase
Final Shutdown Phase

***:ft****
**:ft:ft:ft:ft:ft*
****:ft*:ft:ft
********
**:ft:ft*:ft:ft*

Please wait for system to re-boot itself
RSTS V9.7 SYSGEN (DUO) INIT V9.7
13-Jun-89 - 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 RSTS / E
System Manager's Guide for more information on SHUTUP.
Go to Task 2.

Start RSTS/E Monitor

lrask 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 RSTSIE monitor. You must first decide whether to
perform the additional preparatory task:
•

Change monitor defaults (INIT.SYS DEFAULT option)

Change Monitor Defaults (DEFAULT Option)
You can set RSTSIE monitor defaults in two ways:
•

Accept preselected defaults (START option). INIT.SYS sets defaults for your
RSTSIE monitor and then starts timesharing.

•

Set your own RSTS/E monitor defaults (DEFAULT option).

INIT.SYS can determine many of your RSTSIE monitor defaults, based on the
configuration of your system. You can set the others online during timesharing.
Table 8 shows the default settings of your new monitor..
Table 8:

Monitor Defaults

Default

Current Setting
INIT.SYS Settahle Defaults

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 without DECnet
is 3K words. The minimum size of XBUF with DECnet and
endnode is 3K words. The minimum size of XBUF with DECnet
and router varies according to the size of your network, but is
never less than 3K 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. The size
varies based on your hardware and software configurations.

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

Change the amount of memory allocated to the extended buffer pool (XBUF
Buboption of DEFAULT).

•

Change the amount of memory allocated to the small buffer pool (BUFFERS
Buboption of DEFAULT).

See Part 5 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.
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 Part 5 before continuing with
this task.
Start RSTS/E Monitor

Terminal Session
1b start your RSTSIE monitor, you must answer the START questions. This
tenninal session lists the START questions, explains them, and gives you some
possible responses. Mter you understand the question, type the response at your
console terminaI. In some cases, your response will differ from the response
shown in red in the example installation.
start timesharing? <Yes> START RSTS97

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. 1b start timesharing under your
new V9.7 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 RSTSIE monitor, use the INIT.SYS
START option.
Response--Type START <monitor name> where <monitor name> is the name of
your new RSTSIE monitor. In the example installation, the response is START
RSTS97 because RSTS97 is the name of the new V9.7 RSTSIE monitor.
If you do not specify a monitor name, START installs and starts the monitor
that was used in the previous timesharing session, which will be the SYSGEN
monitor.
Memory allocation table:
OK:
66K:
462K:
512K:

00000000
00410000
03470000
04000000

00407777
03467777
03777777
End

66K)
396K)
50K)

BXEC
USER

XBUF
NXM

Memory available to RSTS/E is 512K wo:cds.

Explanation-START prints the current memory allocation table. These
messages may be slightly different due to configuration differences. 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 minimwn SWAP.SYS file, it prints the following
error message:
?Not enough contiguous disk space to ·oreate minimum SWAP. SYS file

START then attempts to create a SWAP.SYS file that is smaner 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 i,s reduced to xxK
New SWAP MAX? <xxK>

Press I RETURN I to accept the default value, indicated by xx in the example. Or enter
CTRLlC to return to the Option: prompt. You can then use the FILE suboption of
REFRESH to create more disk space.

Start RSTS/E Monitor

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 installed RSTSIE 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

The CRASH.SYS file is important because it is used to save diagnostic information during a system crash. When a crash occurs, the RSTSIE 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. In general, SPRs submitted on system crashes without crash dumps
will be answered by DIGITAL as "Insufficient information."
Therefore, if you see the error message, Crash dump automatically disabled,
follow these steps to enable crash dump:
1. Mter you begin timesharing, delete unnecessary files to create more

contiguous disk space. Or, move some files to a nonsystem disk.
2. Shut down the RSTSIE monitor using the SHUTUP program.
3. 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.
13-Jun-89 06:22 AM
8 devices disabled
Proceed with system startup? <YES>

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
ready to proceed with the start up. Then START.COM prints a message as it
enters each section of commands. See the RSTS / E System Manager's Guide for
more information on the START.COM command file.
Start RSTS/E Monitor

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

*** From [1,2J on KBO: at 06:23 AM on 13-Jun-B9
** RSTS/E is on the air ...
~
RSTS V9.7 13-Jun-89 06:24 AM

User:

Explanation-You are finished with the installation. You can now press the
I RETURN I key 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 perfonn.
If you plan to install layered products, see the individual layered product
installa tion guides for instructions.

Start RSTS/E Monitor

Phase 8

Optional Tasks
This phase describes optional tasks you may want to perfonn to tune your
RSTS/E: system to your needs.
The tasks in this phase are:
•

Task 1: Reposition System Program Packages

•

Task 2: Apply Any Mandatory Patches

Task 1: Reposition System Program Packages
This task describes the procedures for moving system program packages to
another disk. You may want to perfonn this task if your system disk is full or to
better spread 110 across multiple devices and controllers.
If you have a two disk system and receive your RSTSIE 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 packag'e.
Table 9 lists the logical names and default locations of the RSTSIE system
programs.
Table 9:

System Program Package Logical Names

Package

Logical Name

Location

RSX Utilities
Help

LB:
HELP$:

[1,1] [1,2]

Error

ERROR$:

[0,3]

Update

UPDATE$:

[0,4] [1,2]

Device Testing

TEST$:

[0,5]

PrintlBatch Services (PBS)

PBS$:

[0,6]

File Restore

RESTOR$:

[0,7]

OPSER-based Spooling

OPSER$:

[0,8]

Unsupported Utility
Auxiliary Library

UNSUPP$:

[0,9]

AUXLIB$:

[0,14]

RMS-ll

RMS$:

[0,10]

EDT

EDT$:

[0,11]

TECO

TECO$:

[0,13]

SORTIMERGE

SORT$:

[0,15]

SOURCE

SOURCE$:

[0,17]

[0,2]

You may increase performance by moving the RSX O~ject Libraries and the Help
packages to a nonsystem disk.
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, SORTIMERGE, EDT, Error Reporting, Device Testing, PrintlBatch
Services, Opser-based spooling, and RMS-ll.

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

Optional Tasks

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. Refer to the RSTS / E System Managers Guide for information on using the
INITIALIZE command to initialize the disk.

Step 2: Create a New Directory
Create a new directory for the system package by typing a command of the
fonnat:
CREATE/ACCOUNTINOUSER dev:[p,pn]/TEMPLATE=SY:[p,pn]
where:
dey:

specifies the new disk.

[p,pn]

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

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

Step 3: Copy the Package to the New Location
Transfer the package to the new location by typing a command of the format:
COpy <logical name>*. * dev:[p,pn]*. *
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 RSTS/E System User's Guide for more information on the COPY
command.

Step 4: Reassign the System Logical Name
Assign the new logical name by typing a command of the format:
ASSIGN/SYSTEMIREPLACE dev:[p,pn] <logical name>
where:
dev:[p,pn]

refers to the new directory you created in step 3.

is the name of the package from Table 9.

See the RSTS / E System Manager's Guide for more information on the ASSIGN
commands.

Stel) 5: Point the Logical Name at the New Location
Edit the START.COM system startup 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. During an update, the START.COM file uses the disk and directory that
you pointed to with the logical name. You might use this when updating layered
products.

Step 6: Delete the Old Directory
If you have no further use for the old account, delete the directory by typing a
comrnand of the format:
DELETE/ACCOUNT [p,pn]
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

Task 2: Apply Any Mandatory Patches
A mandatory patch applies an emergency c:orrection 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 RSTS / E 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:
•

Paper patches from articles in the RSTS / E Software Dispatch

•

Paper patches from the RSTS/E Release Notes

•

Patches to non-DIGITAL software

There are several dangers when you type in a mandatory patch:
•

You could enter incorrect values causing new problems, which you may not
recognize as yours, to occur.

•

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 instruct.ion incorrectly, the software could fail,
and you may not be able to find the inBtruction 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 manual patching to install a paper patch, follow the directions
in the RSTS / E 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 ~ruRN I key on each line, you can use the
standard keyboard editing characters, such as CTRLIR, CTRLIU, and the I DELETE]
key. Furthermore, you can reenter input if you cause an error message and are
reprompted.
You may need to use a RSTSIE program such as ONLPAT to install patches. See
Appendix E for information on RSTSIE patching programs.

Optional Tasks

Installation Example

System Installation Example
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 1 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 a~tion, such as mounting a tape or disk.
This is only a sam pIe. 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 (1) in response to any question or
prompt to obtain an online explanation.
The example installation has the following characteristics:
•

CPU: PDP-11144

•

Memory: 512K words

•

System Disk: RA80

•

RSTS/E Distribution Kit: 1600 bpi magnetic tape

•

Installation Kit: V9.7

Phase 1
Mount V9.7 Installation Medla:J

Bootstrap VO.7 Installation MlKtla:J

»>B MSO
Performing limited hardware scan.
RSTS V9.7 (MSO) INIT V9.7

Phase 2
Mount Target System Dlsk:J

Today's date? 13-JUN-89
Current time? 11:55 AM
Installing RSTS on a new system disk? <Yes> ~
13-Jun-89 11:55 AM
Disk? DU
Unit? <0> 0
This disk appears to be a RSTS/E formeltted
disk with the following characteristics:
Pack ID:
Pack cluster s~ze:
Pack is currently:

NATHAN
8

Private,
Update access on writes,
Level: 1.1

Pack ID? SYSDSK
Pack cluster size <4>? ~
MFD cluster size <16>? ~
SATT.SYS base <18595>? ~
Pre-extend directories <NO>? ~
PUB, PRI, or SYS <SYS>? ~
[1,1] cluster size <16>? ~
[1,2] cluster size <16>? ~
[1,1] and [1,2] account base <18595>? ~
Date last modified <YES>? ~
New files first <NO>? ~
Read-only <NO>? ~
Use previous bad block info <YES>? ~j
Patterns <3>? ~
Proceed (Y or N)? Y
13-Jun-89 11:57 AM
Copying required system files
Performing limited hardware scan.
RSTS V9.7 (DUO) INIT V9.7
13-Jun-89 11:59 AM
Rebooting . . .
RSTS V9.7 (DUO) INIT V9.7
13-Jun-89 12:01 PM
Creating SWAP.SYS file with minimum size of 128 blocks

100

System Installation Example

Memo:t:'Y allocation table:
OK:
66K:
462K:
512K:

00000000
00410000
03470000
04000000

00407777
03467777
03777777
End

66K)
396K)
50K)

EXEC
USER
XBUF
NXM

Memory available to RSTS/E: is 512K words.
Creating CRASH.SYS file with minimum size of 320 blocks
8 devices disabled

Phase 3
RSTS/E V9.7
13-Jun-89 12:01 PM
Please mount the RSTS/E Installation media and enter the name
and unit number of the device.
Valid device types are: 'MM', 'MS', 'MT', 'MU', 'OM' or 'DL'
Installation device < MSO:>?

Restoring required _SY:[0,1] components
Deleting all global symbols
RSTS/E V9.7
13-Jun-89 12:02 PM
RSTS/E Software Installation Procedure
* Dialogue Phase *
During this installation procedure you may:
Type '?' for help
Type 'A' to go back to the previous question
Type CTRL/Z to return to the beginning of the present section
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.
Target disk? <_SY:> : ~
Restoring required _SY:[1,2] components
Assigning system logicals
Are you ready to proceed? <yes> ~

** Starting Monitor section **
13-Jun-89 12:03 PM
Do you want to install the RSTS/E monitor? <yes> ~
There is a pre-built monitor available which is suitable for
Micro-PDP-11 systems. You may use this pre-built monitor, or
you may build your monitor. Building your monitor will allow
you to specify the features you wish to include in the monitor.
You may now choose:

(A) Build your monitor
(B) Use pre-built monitor

Please type A or B <A> ?
The pre-built monitor MICRO.SIL offers the following features:

System Installation Example

101

RK05's: 0
RK06/RK07's: 0
MSCP support: Yes
TS11/TSV05/TU80's: 1
RX01/RX02's: 0
DMC11's/DMR11's: 0
RJ2780 support: No
EMT Logging: No

RL01/RL02's:4
Disks on DR controller: 0
TU16/TE16/TU45/TU77's: 0
TMSCP tape drives: 2
CR11/CM11 card reader: No
DMP11's/DMV11's: 0
Maximum jobs: 10

Overlapped seek: Yes
Disks on DB controller: 0
TU10/TE10/TS03's: 0
Printers: 1
CD11 card reader: No
Simultaneous IBM Links: 0
Small buffers: 250

Please type A or B <A> A
Restoring required SYSGEN components
Starting System Generation
Use template monitor ? <N> NO
New monitor name ? <RSTS> RSTS97
Accept defaults ? <N> ~
The following questions deal with the
numbers and kinds of disk units on this
system.
~
~
~

Accept Disk defaults ?
RK05's· ?
RL01/RL02's ?
RK06/RK07's ?
Overlapped seek ?

ffi§!J

Disks on DR controller ?
Overlapped seek ?
Disks on DB controller ?
MSCP support ?

<02>
<y >
<00>
<y >

~
~
~
~

The following questions deal with the
peripheral devices attached to this
RSTS/E system.
Accept Peripheral defaults ?
<N >
~
TU16/TE16/TU45/TU77's ?
<00>
~
TU10/TE10/TS03's ?
<00>
~
TS11/TK25/TSV05/TU80's ?
<01>
~
TMSCP tape drives ?
<00>
ffi§!J
Printers ?
<01>
~
RX01/RX02's ?
<00>
ffi§!J
CR11/CM11 card re?Lder ?
<N >
~
CD11 card reader ?
<N >
~
DMC11's/DMR11's ?
<00>
~
DMV11's/DMP11's ?
<00>
~
IBM 3271 OR 2780/3780 simultaneous links?
RJ2780 support ?
<N >
~

<00>

The following questions deal with the
capacity and features of this RSTS/E
system provided at the system manager's
option.
<N >
<25>
<440>
<N >

Accept Software defaults ?
Maximum jobs ?
Small buffers ?
EMT logging ?

40
550
~

** End of Monitor Section **
Phase 4
Are you ready to proceed? <yes>

** Starting System Programs Section **
13-Jun-89 12:05 PM
Do you want to install the System Program packages? <yes>

102

System Installation Example

Packages to install <ALL>: ?
The valid responses are:
DIALOGUE
ALL
ALL,NOpkg[, ••. ]
,pkg [, ... ]
,NOpkg [, ••. ]

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
Adds pkg to the default list (during an update)
Deletes pkg from the default list

Use a comma as a separato:r. e.g.: RSX,PBS,RMS
Package names:
RMS-11
Auxiliary Library
RMS
Basic-Plus
(includes RSX Utilities)
RMS DECnet Data Access Package RSX
RSX Utilities
SORT
Sort/Merge
(includes RMS·-11 )
EDT
(includes RMS-11)
EDT Editor
HELP
Help Package
TECO
TECO Editor
OPSER
Opser-based Spooler
TEST
Device Testing
PBS
Print/Batch Services
UNSUPP
Unsupported Utilities
RESTORE File Restore
UPDATE
Update Package
Packages to install <ALL>: ALL,NODAP,NOUNSUPP,NOSORT,SOURCE
AUXLIB
BASIC
DAP

The following will be installed:
RSX
UPDATE
RESTORE
SOURCES

RMS
TEST
OPSER

EDT
AUXLIB
BASIC

PBS
TECO
HELP

You may answer "Yes" to accept this list, or "No" to change it.
Is this list OK? <yes> ~
Do you want the 1&0 versions of tasks? <Y>

Use resident library version of RMS? <Y> ~
Use RMS resident libraries in PBS? <Y> ~
Use resident library version of EDT? <Y>

During the build phase there will be further questions
for BASIC-PLUS.

** End of System Programs Section **
Are you ready to proceed? <yes> ~
13-Jun-89 12:06 PM

** Starting Layered Products Section **
You may now transfer the layered product update components
from the Installation kit.
Do you wish to do the transfer? <yes>

Product updates to transfer: ALL
The following will be transferred:
BP2
DIBOL
FRTRN77
PLXY
3271

C81
DTR
MAIL
RJ2780

DECDX
FMS
MENU
WPS

DECNET
FORTRAN
PDPDBG
27803780

You'may answer "Yes" to accept this list, or "No" to change it.
Is this list OK? <yes> ~
NOTE: Any files currently in the PATCH ACCOUNT will be deleted

System Installation Example

103

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

** End of Layered Products Section **
Phase 5
You must now set the password for acc:ount _SY: [1,2]
New password:
New password again, for verification:
Password set for account _SY:[1,2]
This is the end of the DIALOGUE phasEl.
The next phase is the BUILD phase.
Are you ready to proceed? <yes>

* Build phase *
13-Jun-89 12:07 PM
What size would you like SWAPMAX to he? <64>
Do you want _SYO:SWAP1.SYS created? <yes>

Creating _SYO: [0,1]SWAP1.SYS at 4992 blocks
Creating RSTS/E monitor,
This monitor has a valid buffer count:
Monitor creation 20% complete.
Monitor creation 40% complete.
Monitor creation 60% complete.
Monitor creation 80% complete.
Directory of SIL RSTS97 on 13-Jun-89 12:35 PM
Name

Ident

Load

Size

~~ransfer

Total

RSTS
MVR

09.703
09.701

000000
120000

116500
014100

000001
000001

20K
23K

OV2
DEFALT

09.702
09.701

002000
001000

034000
003000

000001
000001

118K
119K

Maximum buffers available without using data space:
415 general small buffers.
90 FIP small buffers.
Maximum buffers available using data space:
668 general small buffers.
494 FIP small buffers.
If you choose to restart the installation, you may
specify up to 573 small buffers for this system.
Doing so will increase the number of general buffers
available both with and without data space.
Monitor creation 100% complete.
Before attempting to start your new SIL, you must have swap
file space of 11264 blocks and if you use files other than
SWAP1.SYS you must also edit START.COM to install them.

104 System Installation Example

13-Jun-B9 12:37 PM
Restoring the System Startup files from the Installation kit
Restoring the System Library package from the Installation kit
Restoring the Error package from the Installation kit
Restoring the RSX Libraries from the Installation kit
Restoring the RSX Utilities from the Installation kit
Restoring the RMS-l1 package from the Installation kit
Restoring the RMS Libraries from the Installation kit
Restoring the Print/Batch Services package from the Installation kit
Restoring the EDT package from the Installation kit
Restoring the Update package from the Installation kit
Restoring the Device Test~ing package from the Installation kit
Restoring the TECO package from the Installation kit
Restoring the Auxiliary Libraries from the Installation kit
Restoring the File Restore package from the Installation kit
Restoring the Opser-based Spooling package from the Installation kit
Restoring the Help package from the Installation kit
Restoring the BASIC-PLUS package from the Installation kit
Restoring the Program Sources from the Installation kit
Restoring the Resident Libraries from the Installation kit
13-,Jun-B9 12: 51 PM
Restoring BP2 update components from the installation kit
Restoring CBl update components from the installation kit
Restoring DECDX update components from the installation kit
Restoring DECNET update components from the installation kit
Restoring DIBOL update components from the installation kit
Restoring DTR update components from the installation kit
Restoring FMS update components from the installation kit
Restoring FORTRAN update components from the installation kit
Restoring FRTRN77 update components from the installation kit
Restoring MAIL update components from the installation kit
Restoring MENU update components from the installation kit
Restoring PDPDBG update components from the installation kit
Restoring PLXY update con~onents from the installation kit
Restoring RJ27BO update components from the installation kit
Restoring WPS update components from the installation kit
Restoring 27B037BO update components from the installation kit
Restoring 3271 update components from the installation kit
RSTS/E V9.7
13-Jun-B9

01:31 PM
RSTS/E Software Installation Procedure

13-Jun-B9 01:31 PM
Installing system packages
13-Jun-B9 01:31 PM
Beginning of RSTS/E Basic-Plus generation.
BASIC-PLUS RTS name?
FPP?
Math precision?
Log functions?
Trig functions?
Print using?
Mat:cices?
String arithmetic?

<BASIC> ~
<Y> ~
<02>4
<Y> ~
<Y> ~
<Y> ~
<N> Y
<N> ~

Finished installing system packages
13-,Jun-B9 01 :49 PM
The RSTS/E Software Installation Procedure is complete
Would you like to start your new monitor now? <Y> YES
The monitor changes will take effect upon reboot
Deleting all global symbols

System Installation Example

105

Deassigning system logicals
13-Jun-89 01:50 PM
System tape label default set to DOS
SY:[1,2]INSTAL.LOG is a log file of t.his session
Please wait for system to re-boot itself ...
RSTS V9.7 SYSGEN (DUO) INIT V9.7
13-Jun-89 01:52 PM
Memory allocation table:
OK:
67K:
446K:
512K:

00000000 00414000 03370000 04000000 -

00413777
03367777
03777777
End

67K)
379K)
66K)

EXEC
USER
XBUF
NXM

Memory available to RSTS/E is 512K weIrds.
Re-creating CRASH.SYS file with minimum size of 380 blocks
8 devices disabled
Proceed with system startup? <YES>

Beginning RSTS/E system startup .••
13-Jun-89 01:52 PM
Mounting disks
13-Jun-89 01:52 PM
Assigning logical names
13-Jun-89 01:52 PM
Starting error logging
13-Jun-89 01:52 PM
Setting system characteristics
13-Jun-89 01:52 PM
Installing run-time systems and libraries
13-Jun-89 01: 52 PM
Setting termina,l characteristics
13-Jun-89 01:53 PM
Defining system commands
13-Jun-89 01:53 PM
Setting printer characteristics
13-Jun-89 01:53 PM
Starting spoolers
Print/Batch Services started at 01:53 PM

*** From [1,2] on KBO: at 01:53 PM on 13-Jun-89
** RSTS/E is on the air ...
~
RSTS V9.7 13-Jun-89 01:54 PM

User:

106

System Installation Example

Part 2
Upgrade

Installing RSTS/E on a Pre-V9.0 System
Upgrading a previous version of RSTSIE (V7.2, V8.0, or earlier) to the latest
version of RSTS is similar to building a new RSTS/E monitor, which is described
in Part 1 of this guide. Part 4 of this guide outlines a number of tasks you
perform to update a previous version of RSTSIE to the latest version. You
should be familiar with the following V8.0 INIT.SYS program options, which are
discussed in the V8.0 RSTS/E System Generation Manual:
•

SET LIST

•

:EIARDWR LIST

•

DEFAULT

•

START

Figure 5 is a flowchart that outlines how to do a system installation to upgrade
an existing RSTSIE system. Keep the flowchart handy when you are performing
the upgrade.

SET LIST

Collect
distribution kHs
and docum.ntatlon

2.
Check dlstrfbuflon
leit order
numb.iii

SHUTUP
Shut down
RSTS/E monitor

Ust status of
IEIII dlWle_

s.: ~.l~T :
I

7.r-----~-----,

BACKUP (V9)

Physically mount
the RSTS
Installation tape
or disk

SET/ACCOUNT

BACKUP (V9)

Ust hardwore
configuration
table

Restore ••Iected
accounts from
ackup iape or dis
to new system disk

PhysIcally and
logIcally mount
VS.O system disk

.alee copy of
system disk

Establish account
quotas. privileges
(after last step)

Perform Pha:e 7
and, optionally.
Phase 8

(S.. Port 1)

DEFAULT UST
Check defaults
on old .ystem disk
and list memory
allacaHon table

Bootstrap
Installation tape
or disk

Bootstrap
Installation
tape or disk

Perform Phases
2 through 6
(See Part I)

Answer preliminary
INIT. SYS.
questions
(See step 3)

Option 1

CREATE/ACCOUNT
Recreate
selected
accounts

Option 2
Convert disk
to RDS1.2 format

COpy

BACKUP (V9)

Copy selected
accounts to
system disk

Back up selected
accounts to
backup tape or
disk

START
start SYSGEN
montlor

BACKUP (V9)

(See step 4)

Restore selected
accounts to
system disk

BACKUP (V9)
Back up selected
accounts to
tope or disk

ZK-9247-HC

Figure 5: System Upgrade Flowchan

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

111

Follow these steps to upgrade your system:

Preliminary Steps
1.

2.
3.
4.

7.
S.

Collect. distribut.ion kits and documentation. (See Task 1 of Phase 1 in Part 1
of this guide.)
Check distribution kit order numbers. (See Task 2 of Phase 1 in Part 1 of this
guide.)
Shut down your RSTSIE monitor, using the SHUTUP system program.
Use the SET LIST ALL option of INIT.SYS to list all of your devices. This
list may be useful when you specify device characteristics on your new system
disk. This list shows what devices were included on your old system.
Use the LIST suboption 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 suboptions 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.
Find out how your current version of BASIC-PLUS is configured so you can
build the new version to have the same configuration.
Physically mount your RSTSIE V9.7 Installation tape or disk. (See Task 2
of Phase 1 in Part 1 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

Although these upgrade steps may seem unorthodox, they provide the
best method for you to re-create your current accounts on your V9.7
system. However, do not use these procedures until you have made a
copy of your system disk (see step 1).
1. Use the BACKUP utility program that corresponds to your current version of
RSTSIE to create a copy of your system disk. Use PIP if you are updating a
pre-V6B RSTSIE system.
2. Bootstrap your RSTS/E V9.7 Installation tape or disk. (See Task 2 of Phase
1 in Part 1 of this guide for instructions and an example of how to bootstrap
the installation media.)
NOTE

If your V9.7 installation media is a tape, you cannot use the Boot
option on your current system. You must use the appropriate hardware bootstrap procedure. Refer to Appendix D for bootstrapping
information.
Installing RSTS/E on a Pre-V9.0 System

113

Depending on the RSTSIE version you are upgrading from and the
disk type of your V9.7 installation media, the Boot option mayor
may not function correctly. If it doesn't, you must use the hardware
bootstrap procedure.
3. 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? XXn

XXn is your device designator and unit. number. Mter 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
BACKUP program.
4. The procedure automatically starts the V9.7 SYSGEN monitor, a prebuilt
monitor supplied by DIGITAL.
The installation cannot continue at thiB point because your disk is not yet
RDS1.2 format and therefore RSTSIE lnounted your disk read-only. You
will see the ?Unable to write to DeL work file error message displayed
several times, followed by the $ prompt.. You are now running under the V9.7
SYSGEN monitor, with DCL as the keyboard monitor.
5. Physically mount a backup tape or disk Then use the V9 BACKUP program
to do a full backup of your system. XXn: is the device designator of the
backup media. Use a command of the format:
$BACKUP/ACCOUNT/FILE ~
From: [*,*]*.*/EXCLUDE=[O,l]*.SYS
To: XXn:OLDSYS.BCK

NOTE

This step will not back up your system files in [0,1].
You may want to include the INOLIST qualifier to suppress the listing of
backed-up files. If you have a tape drive capable of streaming (such as a
TU80, TK50, or TU81-PLUS), you should include the IBUFF=MAXI qualifier
to make BACKUP run faster. See the RSTS / E System Manager's Guide for
more information on BACKUP.
6. When BACKUP completes, reboot your Installation tape or disk. Halt the
system and use the hardware bootstrap loader on your PDP-11 to boot the
media. (At this point you are not able to run SHUTUP, since your disk
is mounted read-only.) See Task 2 of Phase 1 in Part 1 of this guide for
instructions and an example of how to bootstrap the installation media.
7. See Part 1 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. These phases build the RSTSIE V9.7 monitor and system
programs onto your system disk.

114

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

8. Mount your backup tape or disk and use the RESTORE command to restore
the accounts you saved earlier to your new system disk. XXn: is the device
designator of the backup media. Use a command of the format:
$RESTORE / ACCOTJNT /F ILE/NOREPLACE
From: xxn:OLDSYS.BCK ~
To :

[

*, * 1 * . *
NOTE

If you had system programs in any account other than [0,1], those
accounts are still on your system. You should do a directory of all
utilities that are on your system, particularly in account [1,2]. Prior
to V9.0 of RSTSIE, these utilities could exist in any [1, *] account.
Delete the utilities that are in accounts other than [0,1]. This will
leave only the current versions of the utilities on your new V9.7
system. This will give you more space on your new V9.7 system
and prevent confusion.
You may want to include the /NO LIST qualifier to suppress the listing of
restored files. If you have a tape drive capable of streaming (such as a TUSO,
TK50, or TUS1-PLUS), you should include the /BUFF=MAX1 qualifier to
make RESTORE run faster.
Note that when BACKUP restores account [1,2], it changes the password back
to the value on your old system disk.
9. Remove your backup tape or disk.
10. See Part 1 of this guide and perform all of the tasks associated with Phase 7
and, optionally, Phase S.
11. Use the SET ACCOUNT command to establish V9.7 quotas and privileges.
Use the following command format:
SET ACCOUNT [l,*l/JOB=a/DETACH=b/INQUOTA=c /PRIV=(ALL,NOSYSMOD,NOEXQTA)/NOEXPIRE
SET ACCOUNT [2-254,*1/JOB=w/DETACH=x /INQUOTA=y/NOEXPIRE

You may want to use other qualifiers such as IPRIV to set different account
privileges, or /NAME= to set the accounts name. Substitute the number you
want for each of the options, (JOB, DETACH, PRIV, and INQUOTA) for the
variables a, b, c, w, x, and y. The above commands (with appropriate values
for a,b,c,w,x,y) make your accounts VS.O compatible.
If you want your V9.7 system to function exactly like your pre-V9.0 system,
then also execute the following command:
SET ACCOUNT [l,ll/PRIV=SYSMOD

Note that DIGITAL does not recommend that you do this procedure.
See the RSTS / E System Manager's Guide for more information on SET
ACCOUNT.

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

115

12. Use the DSKCVT (Disk Convert) utility to convert accounts with "LOOKUP"
passwords to "NOLOOKUP." Use the following command format:
$ run auxlib$:DSKCVT
DSKCVT V9.3-03 RSTS V9.7-11 SYSTEM:
Disk to convert? XXn:
* CURRENT DISK ATTRIBUTES *
Disk:
XXn:
Label:
V97
Level:
1.1
Convert accounts to NOUSER <NO>? ~§TI
Convert passwords to NOLOOKUP <YES.>?
Display accounts <YES>? ~
Proceed (YES or NO)? YES

See Appendix E for more information on DSKCVT.
NOTE

Some layered products may still require the use of LOOKUP
passwords. Therefore, you need to reset the password for those
products back to LOOKUP.

Multiple Removable Disk Drives
This section lists the steps you perform if your system has multiple removable
disk drives.
Physically mount and bootstrap your RSTSIE V9.7 Installation tape or disk.
(See Task 2 of Phase 1 in Part 1 of this guide for instructions and an example
of how to mount and bootstrap the installation media.)
2. See Part 1 of this guide and perform all of the tasks associated with Phases
2 through 6. These phases build the RSTSIE V9.7 monitor and system
programs onto your system disk.
3. Physically and logically mount your original system disk on a second disk
drive. You can then create accounts on your new system disk with one of two
options:
1.

Option 1:
a. Re-create selected accounts on YOUlr new system disk, using the
CREATE/ACCOUNT command. See the RSTS / E System Manager's
Guide for instructions on how to uSle CREATE/ACCOUNT.
b. After you re-create all of your selected accounts, copy the files in the
accounts from your old system disk to your new system disk, using the
COPY command. Use the /NOREPLACE qualifier to ensure that it doef3
not copy a file that already exists. See the RSTS / E System User's Guide
for instructions on how to use COPY.
Option 2:
a. Back up selected accounts to a tape or disk using the BACKUP (V9)
program. Th copy all the accounts, type a comtnand of the format:
BACKUP/ACCOUNT/FILE ~
From: [*,*]*.*/EXCLUDE=[O,1]*.SYS, [1,2]*.*
To: XXn:OLDSYS.BCK

116

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

NOTE

This step will not backup your system files in [0,1] and [1,2].
You may want to include the INOLIST qualifier to suppress the listing of
backed-up files. If you have a tape drive capable of streaming (such as a
TUSO, TK50, or TUS1-PLUS), you should include the /BUFF=MAXI qualifier to make BACKUP run faster. See the RSTS / E System Manager's
Guide for more infornlation on BACKUP.
h. Restore selected account to your V9.7 system disk using the RESTORE
command of the BACKUP program. 'Th restore all accounts, type a
command of the format:
$RESTORE/ACCOUNT/FILE/NOREPLACE
From: xxn:OLDSYS.BCK ~
To: [*, *] * . *

NOTE

If you had system programs in any account other than [0,1]
or [1,2], those accounts are still on your system. You should
do a directory of all utilities that are on your system. Prior to
V9.0 of RSTSIE, these utilities could exist in any [1, *] account.
Delete the utilities that are in accounts other than [0,1] or [1,2].
This will leave only the current versions of the utilities on your
new V9.7 system. This will give you more space on your new
V9.7 system and prevent confusion.
You may want to include the INOLIST qualifier to suppress the listing
of restored files. If you have a tape drive capable of streaming (such as
a TUSO, TK50, or TU81-PLUS), you should include the /BUFF=MAXI
qualifier to make BACKUP run faster. Note that when BACKUP restores
account [1,2], it changes the password back to the value on your old
system disk. Also, all accounts restored are as they were on the old disk
with LOOKUP passwords.
4. Remove your old system disk (if used) and/or backup tape or disk.
5. See Part 1 of this guide and perform all of the tasks associated with Phase 7
and, optionally, Phase S.
6. Use the SET ACCOUNT command to establish V9.7 quotas and privileges.
Use the following command format:
SET ACCOUNT [l,*]/JOB=a/DETACH=b/INQUOTA=c /PRIV=(ALL,NOSYSMOD,NOEXQTA)/NOEXPIRE
SET ACCOUNT [2-254,*]/JOB=w/DETACH=x /INQUOTA=y/NOEXPIRE

You may want to use other qualifiers such as IPRIV to set different account
privileges, or IN'AME= to set the accounts name. Substitute the number you
want for each of the options, (JOB, DETACH, PRIY, and INQUOTA) for the
variables a, b, c, w, x, and y. The above commands (with appropriate values
for a,b,c,w,x,y) make your accounts VS.O compatible.
If you want your V9.7 system to function exactly like your pre-V9.0 system,
then run the following command:
SET ACCOUNT [l,l]/PRIV=SYSMOD

Note that DIGITAL does not recommend that you do this procedure.
See the RSTS / E System Manager's Guide for more information on SET
ACCOUNT.

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

117

Use the DSKCVT (Disk Convert) utility to convert accounts with "LOOKUP"
passwords to "NOLOOKUP." Use the foUowing command format:
$ run auxlib$:DSKCVT
DSKCVT V9.3-03 RSTS V9.7-11 SYSTEM:
Disk to convert? XXn:
* CURRENT DISK ATTRIBUTES *
Disk:
XXn:
Label:
V97
Level:
1.1
Convert accounts to NOUSER <NO>? ~]
Convert passwords to NOLOOKUP <YES>?
Display accounts <YES>? ~
Proceed (YES or NO)? YES

See Appendix E for more information on DSKCVT. See the RSTS / E System
Manager's Guide for more information on SET ACCOUNT.

118

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

Part 3
Online

Performing an Online System Installation
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. 7
installation. INSTAL.COM ]resides in account [0,1]. You can also use it to:
•

Generate a new monitor

•

Install one or more system program packages

•

Install layered products (integrated layered products only)

•

Transfer layered product updates to your system

•

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. You also cannot
perform an online system installation to build a V9.7 monitor from a
V9.6 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. 1b access
INSTAL.COM, type a command of the following format:
@[0~1]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 perfonning a
SYSTEM_PROGRAMS, LAYERED_PRODUCTS, or COPYUP operation (see Table 10). See Task 1 of Phase 4 in Part 1 for a complete list
of RSTSIE system program packages. See Task 2 of Phase 4 in Part 1
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 fonnat. Table 10 lists
the INSTAL.COM commands and the resulting entry points into the installation
process. See the appropriate Phase and Ta:3k in Part 1 for details on the actual
installa tion 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', 'MS', 'HT',
(a response of SY allows monitor only)
Installa'l:.ion device:?

'MU',

'DM',

'DL' or 'SY'

< MMO: >

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 10 lists the INSTAL.COM commandEl and the resulting entry points into
the installation process.
Table 10:

INSTAL.COM Entry Points

Command

Installation
Entry Point

Comm«mt

~[O,l]I~Err~

Phase 3, Task 1

Performs new installation (same as I~ST~ ~:L).

~[O,l]1~ST~ ~L

Phase 3, Task 1

Performs new installation (the default).

~[O,l]I~Err~

Phase 4, Task 1

Begins :system program installation questions.

Phase 5, Task 3

Installs specified package while preserving existing
soitwarle packages.

Phase 3, Task 1

Begins monitor installati.on section. Skips system
program and layered product sections.

SYSTEM_PROGR.AM:S
~[O,l]I~Err~

SYSTEM_PROGR.AM:S [pkg, ... ]
~[O,l]I~ST~ MO~ITOR

~[O,l]1~ST~

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.

LAYERED_PRODUCTS

~[O,l]1~Err~

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

LAYERED_PRODUCTS [pkg, ... ]

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

Online Installation Example
This example uses INSTAL.COM to instaB the RSX system program package.
Before you run INSTAL.COM, you must Inount 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 1.
122

Perlorming an Online System Installation

$ @[0,1]INSTAL SYSTEM_PROGRAMS RSX

RSTS/E V9.7
11: 10 AM

13-~run-89

RSTS/E Software Installation Procedure
* Dialogue phase *
During this installation procedure you may:
Type '?' for help
Type ,A, to go back to the previous question
Type CTRL/Z to return to the beginning of the present section
Please mount the RSTS/E Installation media and enter the name
and unit number of the device.
Valid device types are: ' MM', , MS', , MT',
(a response of SY allows monitor only)
Installation device? < MMO:>

, MU',

, DM',

, DL' or ' SY'

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.
Target disk? <SY: >

Assi.gning system logicals
The following will be installed:
RSX
You may answer "Yes" to accept this list, or "No" to change it.
Is t.his list OK? <yes> ~
Do you want the I&D versions of tasks? <Y> N

** End of System Programs Section **
This is the end of the DI,ALOGUE phase.
The next phase is the BUILD phase.
Are you ready to proceed? <yes>

* Build phase *
13-Jun-89 11:17 AM
Restoring the RSX Libraries from the Installation kit
Restoring the RSX Utiities from the Installation kit
13-Jun-89 11:21 AM
Installing system packages
Finished installing system packages
The RSTS/E Software Installation Procedure is complete
13-J'un-89 11 :21 AM
Deleting all global symbols
Deassigning system logicals
13-Jun-89 11:21 AM
System tape label default set to DOS
SY:[1,2]INSTAL.LOG is a log file of this session
$

You have successfully installed the RSX package on your system.

Performing an Online System Installation

123

Part 4
Update

Updating a RSTS/E V9.0 through V9.6 System
This part describes how to update a RSTSIE V9.0 through V9.6 system to a new
release.
DIGITAL supplies an Installation Kit with each new release of RSTSIE. Mter
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.
1

Each new Installation Kit contains new software features as well as updates
to existing software. In addition, the kit may contain mandatory corrections to
RSTSIE 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.7 Installation Kit would include all features of the V9.0
through V9.6 kits.
Each new release of RSTSIE also contains the RSTS / E Release Notesfor the
latest version only. The RSTS / E Release Notes describe new features of RSTSIE
and explain differences between the latest version and previous version. Read
the RSTS / E Release Notes before performing a system update.

Sttructure of Part 4
This part 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:: Getting Started
Explains how to make backup copies of your system disk and shut down your
current monitor.

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 and Select So'ftware Updates
Explains how to use infonnation from a telnplate monitor to configure your new
monitor. It also explains how to answer the software update questions.

Phase 4: Generate New 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 Dlonitor and start the new RSTS/E
monitor.

Phase 6: Optional Tasks
Explains how to use the UPDATE.COM command procedure to perfonn a
selective update.

System Update Flowchart
Figure 6, the System Update Flowchart, summarizes how to update a V9.0
through V9.6 RSTS/E system to a V9.7 RSTS/E system. You may want to use this
flowchart while you perfonn the update.

128

Updating a RSTS/E V9.0 through V9.6 System

PHASE 1
Getting Started

Task 1r-----e-A~C~K-U-P----~

Physically
mount and
bootstrap
Installation media

Back up
system disk

BACKUP

Physically
mount
nonaystem dl.k

Shut down
SYSGEN monitor

Task 2 r---C-O.l.- - - - - '

Back up
nonsystem disk

INIT.SYS

Answer
configuration
questIons

Copy ffles
to system disk

Assign system
logical.

HARDWR

No
No

Perform
hardware- related

Shut down
current monitor

Perform
off tine opllons

Start RSTS/E
monitor

tasks

Create
RSTS/E monitor

Answer
system program
update questions

PHASE 6
Optional Tasks

No
No
Task

Answer
layered product
update questions

Update
system programs
(and transfer

1r-------~------,

Perform a
selective
update

layered
product updates)

ZK-9240-HC

Figure 6:

System Update Flowchart

Updating a RSTS/E V9.0 through V9.6 System

129

Phase 1

Getting Started
This phase describes the tasks you must perfonn to prepare for a RSTSIE system
update. 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:
•

Task 1: Back Up System Disk (BACKUP)

•

Task 1A: Back Up Nonsystem Disk (BACKUP)

•

Task 2: Shut Down Current Monitor (SHUTUP)

Task 1: Back Up System Disk (BACKUP)
In this task you use the RSTSIE BACKUP utility to nlake a backup copy of your
system disk. (See the RSTS / E System, Manager's Guide for a fun description of
BACKUP.)
This example backs up a RABO system disk to 1600 bpi tape, mounted on a TU77
tape drive.
$ BACKUP DUO:[*,*]*.* MMO:SYSBAK

Explanation-You see the DCL $ prompt. Type a cOlnmand of the format:
BACKUP <input-file-spec> <output-file-spec>
where:
BACKUP

invokes the RSTSIE 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 systeln
disk (DUO:) to a magnetic tape mounted on drive MMO:, and names the save set
SYSBAK.
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 nunlber of the drive on
which the output volume is mounted. If you want to initialize the tape,
append /INITIALIZE to your response. In the example, the response is
MMO:/INITIALIZE.
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).

Task 1A: Back Up Nonsystem Disk (BACKUP)
You should perform this task if you intend to update system programs and you
have moved any systenl programs packages to a nonsystem disk.
1b back up your nonsystem disk, follow the procedures described in Task 1.
Go to Task 2.

132

Getting Started

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

RSTS V9.7 <monitor name>

11:55 AM 13-Jun-89
Type

fAf

********

Set-up Dialogue 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 ~ to allow the entries to complete. Type NO
to shut down the print and batch queues immediately.
Minutes until system shutdown (0-99) <5>?

Explanation-SHUTUP asks you to type the minutes to wait before the RSTSIE
monitor shuts down. This question is useful for giving system users fair warning
when shutting down the system.
Response-Type a nwnber from 0 to 99. Or, press~ to accept the default of
5 minutes.
Shutdown with automatic RESTART <NO>?

Explanation- The system also asks if you want an automatic RESTART to the
system. The default response is NO.
Response- Press ~ or type No.

******#*
11:55 AM 13-Jun-89 ********
11:55 AM 13-Jun-89 ********

********
Initial Job Killing Phase ******t*
Print/Batch Shutdown Phase *t*t****

11:55 AM 13-Jun-89
Warning Message Phase
Further LOGINs are now disabled

Print/Batch Services shutdown complete at 11:55 AM.

Getting Started

133

11:55 AM 13-Jun-89 #t######

, EVTLOG ' Shutdown Phase

########

11:55 AM 13-Jun-89 ########

, ERRCPY , Shutdown Phase

########

11:55 AM 13-Jun-89 ########

Remove RTS/RES LIB Phase

########

11:55 AM 13-Jun-89 ########

SWAP File Removal Phase

########

11:55 AM 13-Jun-89 ########

Disk DISMOUNT Phase

########

11:55 AM 13-Jun-89 ########

Final Shutdown Phase

########

Please wait for system to re-boot itself ..•
RSTS V9.7 RSTS/E V9.7 (dev) INIT V9.7
13-Jun-89 - 11:56 AM
Start timesharing <Yes>? NO
Option:

Explanation-SHUTUP prints several meElsages before shutting down your
system. It then returns to the Start timesharing? question. See the RSTS / E
System Manager's Guide for more information on SHUTUP.
Response-Type NO. INIT.SYS then prints its Option: prompt.
Go to Phase 2.

134

Getting Started

Phase 2

Prepare System
This phase describes the tasks you must perform to bootstrap the installation
tape 01' disk and prepare your system disk for a RSTSIE system update. It also
explains how to start your SYSGEN m.onitor.
The tasks in this phase are:
•

Task 1: Physically Mount and Bootstrap Installation Media

•

Task 2: Copy Files to System Disk (COPY)

These Jresponses have special meaning.:
Response

Description
Accept the default response
Obtain an online explanation of the question

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.

2.
3.
4.
5.
6.

Physically mount the tape on drive unit 0 or1 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 TEI0 tape drive. If you have a combination of TU16, TE16, TU45,
TU77, TSll, TSV05, and TU80 tape drives, load the 1600 bpi distribution
tape on unit 0 or 1 of the TSll, TSV05, or TU80 drive. TK50 and TU81 tape
drives can use either unit 0 or 1.
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:
1. Physically mount the disk in drive unit 0 or 1. For an RL02 disk, you can use
drive units 0, 1, 2, or 3.
2. Make sure that the READY light is on.
NOTE

The tape drive MUST be write-protected and online for the
installation to proceed properly.
3. Make sure that the write-protect (WR PROT) light is on.
4. Make sure that the console terminal is on line.
NOTE

The disk drive MUST be write-protected and online for the installation
to proceed properly.

136

Prepare System

Bootstrap Installation Media
Now you must bootstrap the installation tape or disk. Depending on the RSTSIE
version you are updating from and whether the V9.7 instal1ation media is a disk
or a tape, you use one of the following boot methods:
•

If your V9.7 installation media is a disk or you are updating from V9.1 or
later, use the INIT.SYS BOOT option.

•

If you are updating from V9.0 and your V9.7 installation media is a tape, you
can:
Use the PDP-11 Central Processing Unit (CPU) switches to activate a
hardware bootstrap loader
Use the console emulator

These bootstrap methods are described in the following sections.
IUse the INIT.SVS BOOT Option

The INIT.SYS BOOT option bootstraps magnetic tape and disk devices.
Option: BOOT

Explanation-Mter 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 device:
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 11 lists
the tape device designators. Table 12 lists the disk device designators.
About 30 seconds to 10 minutes after you type the device designator, the following
prints on the console terminal:
Performing limited hardware scan.
RSTS V9.7 (dev) INIT V9.7
Today's date?
Current time?

The Thday's 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.
Note that the time required for this step varies according to the bootable device
you use and the size of your system. The following are some general guidelines
for the time for this step:
•

If you are booting a disk such as an RL02 or RK07, this step should take less
than 30 seconds.

•

Xf you are booting a TK50 or on a large system with many devices attached,
this step could take up to 10 minutes.

Go to Task 2.

Prepare System

137

Use the Hardware Bootstrap Loader

The hardware bootstrap loader is a device inside your PDP-11 that reads a
bootstrap record from the tape or disk into memory. This bootstrap record
cont.ains a program that loads and executeB additional program code from the
tape or disk. There are different types of hardware bootstrap loaders; the type
you have on your PDP-11 determines which CPU switches or commands you use.
Your DIGITAL field service representative or software support specialist should
already have identified the type of hardware bootstrap loader on your PDP-11.
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
D, 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:
1. Move the control switch (CONT) to the HALT position.
2. Move the control switch to the BOOT position.
The CPU prints some octal numbers on the console terminal, followed by three
angle brackets:
»>B 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 11 lists the tape device designators. Table 12 lists the bootable disk device
designators. Enter the appropriate device designator for your installation.
About 30 seconds to 10 minutes after you type the device designator, the following
prints on the console terminal:
Performing limited hardware scan.

RSTS V9.7 (MSO) INIT V9.7
Today's date?

The 'lbday's date? prompt means that INI'r.SYS is loaded into memory. You
have successfully bootstrapped your instaHation 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.
Table 11 : Tape Device Designators
Designator

Devices Available During Installation

MMO: toMMl:

TE16lrU16trU45trU77 maE~etic tape units 0 or 1

MSO: to MSl:

TSlllI'SV05lTU801TK25 1 magnetic tape units 0 or 1

MTO: to MTl:

TEIOtrUIOlI'S03 2 magnetic tape units 0 or 1

MUO: to MUl:

TK50ITU81trU81-PLUS magnetic tape units 0 or 1

I-Note: You cannot use a TK25 drive for system inHtallation.
2-Note: You cannot use a TS03 drive for system iIl.Eltallation.

138

Prepare System

Table 12:

Bootable Disk Device Designators

Designator

Devices Available During Installation

DBO: to DBl:

RP04IRP05/RP06 diRk drive units 0 or 1 1

DLO: to DL3:

RLOIIRL02 disk drive units 0 to 3

DMO: to DMl:

RK06IRK07 disk drive units 0 or 1

DRO: to DRl:

RM02IRM03IRM05IRM80 disk drive units 0 or 1 1

DUO: to DUI5:

RA601RA801RA811RA82IRCF25IRC25IRD31IRD32IRD511
RD521RD531RD541RX331RX50 disk drive units 0 to 15

l-See Appendix F for more information on multiple RH controller (otherwise known as DB and DR
controllers) configurations.

Go to Task 2.

Prepare System

139

Task 2: Copy Files to System Disk (COP'f)
Your next task is to answer the preliminaTlJ INIT.SYS questions. Then the
INIT.8YS COpy option transfers some necessary files from the instaHation media
to your system disk.

Terminal Session
This terminal .session lists the preliminary INIT.SYS questions, explains them,
and gives you some possible responses. Mter you understand the question, type
the response at your console terminal.
The common error messages appear at the lend of this task. If your error message
does not appear there, see Appendix A.
You have now successfully bootstrapped Y01llr installation media, and the
INIT.SYS program is loaded into memory.
RSTS V9.7

(dev:)

INIT V9.7

Today's date?
Current time ?

Explanation-INIT.SYS searches for a valid date and time and prompts you if
it cannot find one. You see the date and titne prompts, for example, when you
bootstrap a tape or bootstrap a disk from the console boot/restart switch.
Response-Type todays date and time in either the alphabetic or numeric
fonnat. Type a question mark (?) to print an online explanation of the response
formats for this question on your console terminal.
Installing RSTS on a new system disk <Yes> ? NO

Explanation-INIT.8YS asks this question whenever you bootstrap a tape or
disk read-only. (RSTSIE Distribution Kits are always read-only). If you answer
YES, INIT.SYS assumes you are performing a first time RSTSIE V9.7 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-Type NO because you are updating an existing RSTSIE V9.0 through
V9.6 system.
Are you updating an existing RSTS

syst~em

disk? <Yes>

Explanation-This question asks if you are updating a previously generated
V9.0 through V9.6 system. 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 OptJlon: prompt.
Response-Type YES or press I RETURN I.
13-Jun-89 11:57 AM
Disk to update? DMO

Explanation-INIT.SYS asks you to specify the device designator and unit
number of your system disk. You should type both the device designator and
unit number of your system disk. If you only type the device designator, the
system will prompt you for the unit number of your system disk. Possible device
designator responses are: DL, DM, DP, DB, DR, or DU.

140

Prepare System

Response-Type the device designator and unit nwnber of your system disk.
Note-If the message "Performing limited hardware scan." was printed during
this boot and you try to initialize or copy to a nonexistent disk, then you will
receive the following error messages:
That disk was not found during limited hardware scan.
Do you wish to perform a reboot with full hardware scan <YES>?

Response-If you answer YES, then the distribution device is rebooted and the
"Performing limited hardware scan." message does NOT reappear.
Copying required system files
Performing limited hardware scan.
RSTS V9.7 (dev:) INIT V9.7
13-Jun-89 11:57 AM
Rebooting
RSTS V9.7 (DUO) INIT V9.7
13-Jun-89 - 11:57 AM
Creating SWAP.SYS file with minimum size of 128 blocks
Memory allocation table:
OK:
66K:
462K:
512K:

00000000
00410000
03470000
04000000

00407777
03467777
03777777
End

66K)
396K)
50K)

EXEC
USER
XBUF
NXM

Memory available to RSTS/E is 512K words.
Creating CRASH.SYS file with minimum size of 320 blocks
8 devices disabled

Explanation-Mter 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 and prints a message on
your console terminal.
NOTE

It is sometimes necessary to use the HARDWR option to set non-

standard CSR addresses during this part of the procedure. However,
with RSTSIE V9.7, the SYSGEN.SIL is now started automatically, and
the "Option" prompt is no longer asked.
If you need to access the "Option" prompt, you may do so by typing "c
(Control-C) twice immediately after the INIT header line is displayed.
The "c characters will not be echoed on the terminal. Mter a pause of
ten seconds to two minutes, depending on your system. configuration,
the "Option" prompt will appear.
If you get the "Option" prompt again when you are finished with your
changes, simply press RETURN to continue with the procedure.
Go to Task 3.

A list of the COPY error messages follows.

Prepare System

141

COpy Error Messages

CANNOT COpy TO THE SYSTEM DISK
Explanation: You specified the HSTSIE installation media, which is
invalid as an output disk for the COPY option. Specify another disk.
ILLEGAL DISK NAME
Explanation: You typed an invalid disk name. All DF, DK, and DS
disks are illegal.
INVALID UNIT NUMBER
Explanation: The disk unit number you specified does not exist on this
system.
INVALID RESPONSE
Explanation: 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 EXIS'r
Explanation: The disk type you :specified does not exist on this system
or the disk is not properly configured. All properly configured disks 011
the system are listed in the HARDWR LIST suboption.
THAT DISK WAS NOT FOUND DURING LIMITED HARDWARE SCAN
Explanation: The disk you specified to initialize or copy to was a
nonexistent disk. If you answer YES to the "Do you wish to perform a
reboot with full hardware scan <YES>?" question, then the distribution
device is rebooted and the "Performing limited hardware scan." message
does NOT reappear.

142

Prepare System

Phase 3

Conf:igure New Monitor and Select Software Updates
This phase describes the tasks you must perfonn to configure your RSTSIE
monitor. In this phase you also select the software packages you want to update.
The tasks in this phase are:
•

Task 1: Answer Preliminary Questions

•

Task 2: Use Infonnation from a Template Monitor

•

Task 3: Answer System Program Update Questions

•

Task 4: Answer Layered Product Update Questions

These responses have special meaning:
Response

Description

Accept the default response

----------------------------------------------------------------

l.2.!!l~

Return to the beginning of the dialogue section

Icmuc I

Abort the operation and return to the DeL $ prompt

Obtain an online explanation of the question

Return to the previous question

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 INSTAL.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
INSTAL.LOG to obtain a record of the update session.
NOTE

The update procedure does not replace your existing [0,1]START.COM
and [0,1]LOGIN.COM files. If START.COM and LOGIN.COM already
exist on your system, the update proc'sdure 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 RSTSIE.
You may want to examine these files for any new features, 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 the example.
RSTS/E V9.7
13-Jun-89 11:57 AM
Please mount the RSTS/E installation media and enter the name
and unit number of the device.
Valid device types are: 'MM', 'MS', 'I'1T', 'MU', 'DM' or 'DL'
Installation device <_MSO:>?

Restoring required _SYO: [0,1] components
Deleting all global symbols
RSTS/E V9.7
13-Jun~89

- 11:58 AM
RSTS/E Software Update Procedure
* Dialogue Phase *

During this update procedure you may:
Type '?' for help
Type '''' to go back to the previous s~E!ction
Type CTRL/Z to return to the beginninq of the present section

Explanation-This question asks for the location of your installation media and
starts the dialogue phase of the update. The default is the device on which you
booted the installation media.
Response-Press ~ to accept the de£'lult response. In the example
installa tion, the response is MSO.
Please enter the name and unit number of the disk to
which you want to update the software. This disk
should be physically mounted and write-enabled.
Target disk? < SY:> :

144

Configure New Monitor and Select Software Updates

Explanation-This question is for anyone updating a RSTSIE system for
another PDP-I!. Your response to this question determines the disk where the
new RSTSIE monitor and updated system programs will be updated.
If yon Rpecit:v a diRk other than t.he AYRtem diRk (_SY:). phYRically 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 RSTSIE for another PDP-I!. You then see the "Do you want to initialize
the target disk?" question.
Type SY or press I RETURN I to update RSTSIE on your present system disk.
Restoring required _SY: [1,2] components
Assigning system logicals
Are you ready to proceed'? <yes>

Explanation-This question asks if you are ready to continue. If you type YES
or press 1RETURN I. the dialogue continues. If you type NO, you see the $ prompt.
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 ~ to continue with the installation. In the
exaulple installation, the response is ~.
Go to Task 2.

Configure New Monitor and Select Software Updates

145

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 through V9.6 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. Mter 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,I]1NSTAL when you see the DCL $ prompt. You
return to the beginning of Phase 3.
**Starting Monitor Section **
13-Jun-89 12:05 PM
Do you want to install the RSTS/E monitor? <yes>

Explanation-This question asks if you want to update the monitor. Answer
NO to this question if you want to update only system programs and/or layered
products. You then skip the monitor update. You can only skip this if you already
have a current version monitor.
If you answer YES or press 1RETURN 1 to this question, you continue with the
dialogue to update a pre-V9.7 monitor.
If you answer NO to this question, go to Task 3.

Response-Type YES or press ~ to proceed with the RSTSIE monitor
update. In the example installation, the reBponse is [RETURN I.
There is a pre-built monitor availablEl which is suitable for
Micro-POP-II systems. You may use thi::l pre-built monitor, or
you may build your monitor. Building your monitor will allow
you to specify the features you wish to include in the monitor.
You may now choose:

(A) Build your monitor
(B) Use pre-built monitor

Please type A or B <A> A

Explanation- The pre-built monitor has been configured for a Micro-PDP-II
systems. However, you can use this monitor on PDP-1I systems also if the
configuration is suitable for your system configuration. Enter? to display a list
of the pre-built monitor features.
Response- Type A to build your own monitor or type B to use the pre-built
monitor. If you select B, go to Task 3.
Restoring required SYSGEN components

Explanation-The system now copies files that you need to continue the update.
Then you begin the monitor configuration dialogue,

146

Configure New Monitor and Select Software Updates

starting System Generation
Use template monitor? <N>

Exp1anation-This question asks if you want the program to obtain the
information it needs from a template monitor. Answer N if you do not have a
template monitor already on your system. 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 1 of
this guide.
If you answer YES to this question, continue with this task.
If you answer NO to this question, go to the "Use template monitor?" question in
Task 1 of Phase 3 in Part 1 of this guide. Perform the rest of the tasks in that
Phase. Then proceed to Task 3 of this section.
Template monitor name? <RSTS>

Explanation-You can use an existing V9.0 through V9.6 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.
If you type a ? to this prompt, a list of all the monitors in account [0,1] on the
system disk is displayed.
Response--Type the name of the SIL you want to use as a template monitor.
New Monitor name? <RSTS>

Explanation-This question asks for the name of your new RSTSIE monitor,
which will be stored in account [0,1] on your system disk. The program performs
a lookup to see if the monitor name you specify already exists. If you call the new
momtor SYSGEN, the program returns an error message and reprompts you.
Response--Type a name for your RSTSIE monitor. The name can be any
combination of alphanumeric characters up to 6 characters long. The default
response is RSTS.
A monitor by that name already exists.
Do you wish to supersede this monitor?
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 ~ 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 ~ to return to the New monitor name?
prompt. Type YES to supersede the existing monitor.

Configure New Monitor and Select Software Updates

147

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 Dlonitor and asks no configuration
questions.
If you type a ?, you see a list of the default eonfiguration 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 I RETURN I 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 1 of this guide. Then proeeed to Task 3 of this section.

148 Configure New Monitor and Select Software Updates

lrask 3: Answer System Program Update Question:s
Your next task is to answer the system program update questions. Your responses
detennine which system programs are updated on your system. You must update
all the system programs you selected during system installation. For a complete
description of the system programs available with RSTSfJ~, see Phase 4 in Part 1
of this guide.
DIGITAL supplies updates to RSTSIE system programs on the installation media.
The programs are grouped into the packages listed in Table 13. 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 13 lists the logical nam.es for each system program lPackage.
Table 13:

System Program Package Logical Names

Package

Logical Name

System Library

always [1,2]

RSX Utilities
Help
Error
Update
Device Testing
PrintlBatch Services (PBS)

LB:
HELP$:
ERROR$:
UPDATE$:
TEST$:
PBS$:

File Restore

RESTOR$:

OPSER-based Spooling

OPSER$:

Unsupported Utility

UNSUPP$:

Auxiliary Library

AUXLIB$:
RMS$:

RMS-ll
EDT
TECO
SORTIMERGE
BASIC-PLUS
SOURCE

EDT$:
TECO$:
SORT$:
BASIC$:
SOURCE$:

T~erminal Session

This terminal session explains the procedures to update system programs.

** End of Monitor Section **
Are you ready to proceed? <yes>

Explanation-This question asks if you are ready to cont-inue. If you type YES
or press~, the dialogue continues. If you type NO, you see the $ prompt.
Configure New Monitor and SelEtct Software Updates 149

You resume the installation procedure by typing PROCEED.
Response-Type YES or press ~ to continue with the installation. In the
example installation, the response is I RETURN r.

** Startin.g System Programs Section **
13-Jun-89 11:58 AM
Do you want to install the System Program packages? <yes>

Explanation-You are at the beginning of the Systeul Programs Section. If you
answer YES, you begin the dialogue to install system programs.
Answer NO if you are only creating a RSTSIE 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 4.
Response-Type YES or press ~ to begin the dialogue. In the example
installation, the response is IRETURN I.
Packages currently installed on the target disk:
<RSX, RMS, DAP, PBS, EDT, UPDATE, TEST,UNSUPP, TECO, AUXLIB, RES TORE,OPSER,
SORT,HELP,BASIC,SOURCES,BLDETD>
Packages to install? <CURRENTLY INSTALLED LIST> :

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 following will be installed:
RSX
UPDATE
RESTORE
SOURCES

RMS
TEST
OPSER

PBS
TECO
HELP

EDT
AUXLIB
BASIC

You may answer "Yes" to accept this list, or "No" to change it.
Is this list OK? <yes>

Explanation-The system lists the packages it will update on your system and
then asks if you want to use this list. Ifyoll type NO, you return to the "Packages
to install:" prompt.
Response-Type YES or press ~ to continue the system program update.
Type NO of you want to specify a different list of packages to update on your
system.
Do you want the I&D versions of tasks? <Y> ?

150

Configure New Monitor and Select Software Updates

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 I&D versions of tasks. Type NO or press
~ to receive the normal versions.

Use resident library version of RMS? <y> ~
Use RMS resident libraries in DAP? <y> ~
Use RMS resident libraries in PBS? <y> ~
Use resident library version of EDT? <y> ~

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 ~ to use the resident library version. Type
NO to use the overlaid version.
During 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
SORTIMERGE packages. You answer the BASIC-PLUS and SORTIMERGE
questions in Phase 5 of Part 1.

** End of System Programs Section **
Are you ready to proceed? <yes> ~

Explanation-You are finished with the System Programs Section. This
question asks if you are ready to continue. If you type YES or press ~ the
dialogue continues. If you type NO, you see the $ prompt.
Response-Type YES or press ~ to continue with the installation. You resume the installation procedure by typing PROCEED. In the example installation,
the response is I RETURN I.
13-Jun-89 11:59 AM

** Starting Layered Products Section **
You may now transfer the layered product update components
from the installation kit.
Do you wish to do the transfer? <yes>

Explanation-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 install any layered products on your system. If you answer
YES, you continue with the Layered Products Section.
Response-Type YES or press ~ to continue the Layered Products Section.
Type NO to skip the section. In the example installation, the response is YES.
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

151

Task 4: Answer Layered Product Update Questions
You perform this task if you plan to update layered products on your RSTSIE
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-B1, 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 RSTSIE 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.
13-Jun-89 12:05 PM

** starting Layered Products Section **
You may now transfer the layered product update components
from the installation kit.

BP2
DIBOL
FRTRN77
PLXY
3271

C81
DTR
MAIL
RJ2780

DECDX
FMS

DECNET

PDPDBG
27803780

WPS

Do you wish to do the transfer? <yes>

FORTB~.N

Explanation-You see this question at the end of Task 3.
Response-Type YES or press ~ 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
RSTSIE.
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 CTRUZ 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.

152

Configure New Monitor and Select Software Updates

The following will be transferred:
BP2
DIBOL
FRTRN77
PLXY
3271

C81
DTR
MAIL
RJ2780

DECDX
FMS
MENU
WPS

DECNET
FORTRAN
PDPDBG
27803780

You may answer "Yes" to accept this list, or "No" to change it.
Is this list OK? <yes> ~~

Explanation-The system lists the product updates it will transfer to your
system and then asks if you want to use this list. If you type NO, you return to
the Product updates to transfer: prompt.
Response-Type YES or press ~ to continue the layered product update
transfer. Type NO if you wa.nt 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$:>

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$:.
Mter you complete the RSTSIE 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 I RETURN I to accept the default patch account, PATCH$. Or,
specify a different account.

** End of Layered Products Section **
Explanation-You are finished with the Layered Products Section.

Go to Phase 4.

Configure New Monitor and Select Software Updates

153

Phase 4

Generate New System
You are now ready to generate your updated RSTSIE system. In this phase, you
create the new RSTSIE monitor and update the system programs you specified
in Phase 3. See the appropriate installation guides for instructions on updating
layered products such as COBOL-81 or DIBOL.
The tasks you perform in this phase are:
•

Task 1: Create RSTSIE Monitor

•

Task 2: Update System Programs and Transfer Layered Product Updates

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 proceduJres that generate the RSTS/E monitor.
The procedures will differ depending on Y01llr response to certain configuration
questions in Phase 3.
You must now set the password for acc()Unt _SY: [1,2]
New password:
New password again, for verification:
Password set for account _SY: [1,2]

Explanation-This question asks you to s:pecify 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 unforeseen problems. DIGITAL does not
recommend that you log in to and use aCC01llnt [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. The password can be any
combination of DEC MCS characters including the space character but not the ?
character. The password is INOLOOKUP by default. Retype the password when
prompted.
This is the end of the DIALOGUE phase"
The next phase is the 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:
1. Physically mount the nonsystem disk
2. Issue the MOUNT command to logically mount the disk
3. Assign the appropriate system logicals
If you are ready to proceed, type YES or press ~. If you are not ready, type
NO. You then see the $ prompt. When you are ready to proceed, type PROCEED.
Response-Type YES or press ~ to pl~oceed.

* Build phase *
13-Jun-89 - 12:18 PM
What size would you like SWAPMAX to bE!l? <64>

Explanation- This question is only displayed if you have I&D space hardware,
otherwise SWAPMAX is set to 32.
The RSTS/E monitor moves jobs from memory to disk as needed. 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 I&D
space. You can specify a size up to 64K.

156

Generate New System

Response- Type the new SWAPMAX (a number from 32 to 64).
Do you want _SYO:SWAPl.SYS created (at xxxx blocks)? <yes>
Creating _SYO: [O,l]SWAPl.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 SWAJP1.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 1, minus 1.

SWAP MAX

is the value given in answer to the SWAP MAX question, or is 32K words
if you do not have I&D space hardware.

Response-Type YES or press ~ 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.
Creating RSTS/E monitor

Explanation-The command procedure now begins the RSTSIE monitor
generation. The entire process should take 30 to 45 minutes, depending on the
size of your monitor and the type of your CPU. If you have an 11123 or an 11/24
CPU, this process may take up to three hours.
If your template monitor supports RJ2780 or you answered YES to the RJ2780
support? question in Phase 3 of Part 1, 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.
Valid 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 I RETURN I when ready:
%Small buffers lowered by xxx buffers
This will leave you with yyy buffers

EXJ)lanation-The command procedure checks whether the number of small
buffers you specified in Task 6 of Phase 3 in Part 1 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.
If the number of small buffers you specified 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

Generate New System

157

In general, this indicates that the system you configured is too big. Rather than
make such a radical adjustmeni to your monitor by significantly decreasing the
small buffers, the command procedure returns to the configuration questions in
Phase 3 of Part 1. If you see this message, return to Phase 3 in Part 1 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 such as fewer
devices. Also~ specify a much smaller number to the Small buffers? question in
Task 6. In general, 600 to 700 is a good response to the Small buffers? question.
See the BUFFERS suboption of DEFAULT in Part 5 of this guide for more
information on small buffers.
This monitor has a valid buffer count
Monitor creation 20% complete.
Monitor creation 40% complete.
Monitor creation 60% complete.
Monitor creation 80% complete.
Directory of SIL V973
.SIL on 13-Jun'-89 at 12:14 PM
Name

Ident

Load

Size

Tl:ansfer

Total

RSTS
MVR

09.703
09.701

000000
120000

116500
014100

000001
000001

20K
23K

OV2
DEFALT

09.702
09.701

002000
001000

034000
003000

000001
000001

118K
119K

Maximum buffers available without using data space:
415 general small buffers.
90 FIP small buffers.
Maximum buffers available using data ,space:
668 general small buffers.
494 FIP small buffers.
If you choose to restart the update, you may
specify up to 573 small buffers for this system.
Doing so will increase the number of general buffers
available both with and without data space.
Monitor creation 100% complete.
Before attempting to start your new SIL, you must have swap
file space of 11264 blocks and if you use files other than
SWAP1.SYS you must also edit START.CO:M to install them.

Explanation-You see these messages if your new monitor is an acceptable size
and the build progresses satisfactorily.
Go to Task 2.

158

Generate New System

Task 2: Update System Programs and Transfer Layered Product
Updates
The update procedure now updat.es the system programs and layered products
according to the instructions you gave in Phase 3.
Note that the time required for this process varies according to the type of your
CPU and the size of your monitor. The following are some general guidelines for
the time for this step:
•

If you are updating the system programs and layered products on an 11170,
11/73, 11/83, or an 11184 CPU, this process could take up to 30 minutes.

•

If you are updating the system programs and layered products on an 11/45,
11150, 11155, or an 11160 CPU, this process could take up to 1 hour.

•

If you are updating the system programs and layered products on an 11/34,
11135, or an 11/40 CPU, this process could take up to 2 hours.

•

If you are updating the system programs and layered products on an 11123 or
an 11/24 CPU, this process could take up to 3 hours.

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.
13-Jun-89 - 12:15 PM
Restoring the xxxxxx package from the Installation kit
There are no updates for the xxxxxx package

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, xxxx:xx is the name of the specific software package.
Restoring the xxxxxx update components from the Installation kit

Explanation-Mter 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 xxxx:xx
is the name of the layered product.
To install/update layered products, please see the individual layered
product installation guides.

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.
RSTS/E V9.7
13-Jun-89 12:20 PM
RSTS/E Software Update Procedure
13-Jun-89 12:20 PM
START.097 and LOGIN.097 in account [0,1] are the templates
for those .COM files. Your present .COM files should be
edited to reflect any changes.

Generate New System

159

Explanation- This message indicates that there are two templates available for
you to edit to create START.COM and LOGIN.COM for your system as directed
in Phase 6.
13-Jun-89 12:20 PM
Installing System packages

Explanation- The system now begins ins taIling the system packages.
Beginning of RSTS/E Basic-Plus generation
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 4A of Phase 5 in Part 1 for a
description of the dialogue. Otherwise, continue with this task.
Beginning SORT/MERGE installation

Explanation-You see this question if you are updating SORTIMERGE. You
must now answer the SORTIMERGE questions. See Task 4B of Phase 5 in Part 1
for a description of the dialogue. Otherwise, continue with this task.
Finished installing system packages
13-Jun-89 12:35 PM
The RSTS/E software update procedure is complete
Would you like to start your new monitor now? <Y> YES

Explanation- Mter the system packages are installed, you are asked if you
want to start your new monitor now.
Response- Type YES or press ~ to have the system start your new monitor.
If you type NO, you will have to shut down the SYSGEN monitor and start your
new monitor as directed in Phase 5.
Deleting all global symbols
Deassigning system logicals
13-Jun-89 12:37 PM
System tape label default set to DOS
_SY: [p,pn]INSTAL.LOG is a log file of this session
Please wait for system to re-boot itself ...

Explanation-You have completed the update. The command procedure prints
informational messages and reminds you that the INSTAL.LOG file is a record of
the update. The procedure then automatieally shuts down the SYSGEN monitor
and starts your new monitor.
RSTS V9.7 RSTS97 (DUO) INIT V9.7
13-Jun-89

12:45 PM

Start timesharing <Yes>? ~
Memory allocation table:
OK:
67K:
446K:
512K:

00000000
00414000
03370000
04000000

00413777
03367777
03777777
End

67K)
379K)
66K)

EXEC
USER
XBUF
NXM

Memory available to RSTS/E is 512K words.
Re-creating CRASH.SYS file with minimum size of 380 blocks

160

Generate New System

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 and
starts timesharing under it.
The procedure thf'n prints the current. mp,mory allocat.ion tahle and checks thnt
the CRASH.SYS file exists in account LO,lJ on the system disk, is large enough
for the installed RSTSIE monitor and extended buffer pool allocation, and is
contiguous.

Response--Type ~ to start your new monitor. In the example update, the
response is~ because RSTS97 is the name of the new V9.7 RSTSIE monitor.
If you answer NO to this question, INIT.SYS prints its Option: prompt. You can
then use the INIT.8YS offline options to perform additional preparatory tasks.
Finally, when you are ready to start your RSTSIE monitor, use the INIT.SYS
START option.
13-Jun-89

12:45 PM

8 devices disabled
Proceed with system startup? <YES>

Beginning RSTS/E system startup ...
13-Jun-89 12:45 PM
Mounting disks
13-Jun-89 12:45 PM
Assigning logical names
13-Jun-89 12:45 PM
Starting error logging
13-Jun-89 12:45 PM
Setting system characteristics
13-Jun-89 12:45 PM
Installing run-time systems and libraries
13-Jun-89 12:45 PM
Setting terminal characteristics
13-J'un-89 12:46 PM
Defining system commands
13-Jun-89 12:46 PM
Setting printer characteristics
13-Jun-89 12:46 PM
Sta:r:ting spoolers
Print/Batch Services started at 12:46 PM

Explanation- The procedure pauses for several seconds while it performs the
necessary tasks to start timesharing. It then asks if you are ready to proceed
with the start up.
Response- Type YES or press ~ to start timesharing. Or, type NO if you
are not ready to start timesharing. You then see the DeL $ prompt. In the
example update, the response is ~.

*** From [1,2] on KBO: at 12:47 PM on 13-Jun-89
** RSTS/E is on the air ...
~
RSTS V9.7 13-Jun-89 12:47 PM

User:

Explanation- You are finished with the update. You can now press ~
to log in to the system. RSTSIE then prints its banner followed by the User:
prompt.
Save System Disk Onto Another Disk or Tape
You may want to create a backup copy of your system disk. If so, use the Backup
program to copy your system disk before you start your RSTSIE monitor.

Go to Phase 5.

Generate New System

161

Phase 5

Start New Monitor
This phase describes the tasks you DIUSt perform to start your new RSTSIE
monitor if you did not choose to have the update procedure start your monitor in
Phase 4.
The tasks in this phase are:
•

Task 1: Shut Down SYSGEN Monitor (SHUTUP)

•

Task 2: Start New RSTSIE Monitor (START)

Task 1: Shut Down SYSGEN Monitor (SHIUTUP)
Now that you have built an updated RSTSlE monitor, you no longer need the
SYSGEN monitor. To shut down your monitor, run the SHUTUP program.
You should install any paper patches at this time. Install the paper patches to
your currently built monitor, not to your cu.rrently installed monitor. You want
the patches to apply to your newly-built monitor.
Use the ONLPAT commands found in [1,2] to install paper patches online if
'you want to install them before running SHUTUP. Use the PATCH option of
INIT.SYS if you want to install patches after running SHUTUP.

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

Explanation-You see the DCL $ prompt on your screen. You can now shut
down the SYSGEN monitor.
Response-Type RUN $SHUTUP to shut down the monitor.
SHUTUP V9.7-08 RSTS V9.7 <SYSGEN>
12:54 PM 13-Jun-89 ########
Type

,AI

Set-up Dialogue Phase

to any query to backup one question

Minutes until system shutdown (0-99) <5>?

Explanation-SHUTUP asks you to type the minutes to wait before the RSTSIE
monitor shuts down. This question is useful for giving system users fair warning
when shutting down the system.
Response-Type a number from 0 to 99. Or, press [RE"TURN I to accept the default of
5 minutes.
Shutdown with automatic RESTART <NO>?

Explanation- The system asks if you want an automatic RESTART to the
system. The default response is NO.
Response- Press I RETURN I or type No to accept the default response. You should
never answer YES at this point in the update procedure. You must shutdown the
system in order to start the new monitor.
12:55 PM 13-Jun-89 ########
Warning Message Phase
Further LOGINs are now disabled

########

12:55 PM 13-Jun-89 ########

Initial Job Killing Phase

########

12:55 PM 13-Jun-89 ########

Print/Batch Shutdown Phase

########

Print/Batch Services shutdown completEI at 12: 55 PM.

164

Start New Monitor

#*###*#*
12:55 PM 13-Jun-89 ##*####*
12:55 PM 13-Jun-89 #***###*
12:55 PM 13-Jun-89 *##*#,**
12:55 PM 13-Jun-89 *#******
12:55 PM 13-Jun-89 **####*#
12:55 PM 13-Jun-89

, EVTLOG '

Shutdown Phase

, ERRCPY , Shutdown Phase
Remove RTS/RES LIB Phase
SWAP File Removal Phase
Disk DISMOUNT Phase
Final Shutdown Phase

,#*##,,*
#,##,#*#
*#**#,,#
*,******
###,#**#
#####*##

RSTS V9.7 <SYSGEN> (dev: ) INIT V9.7
dd-mmm-yy - hh:mm AM/PM
Start timesharing <Yes>?

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

Go to Task 2.

Start New Monitor 165

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 the additional preparatory task:
•

Change monitor defaults (INIT.SYS DE:FAULT option)

Change Monitor Defaults (DEFAULT O:ption)
When you start your new monitor, it will receive the standard monitor defaults.
Table 14 shows the defaults that INIT.SYS selects.
Table 14:

INIT.SVS Selected Defaults

Default

Current Setting

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 exceElds 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 runtime system. The minimum size of XBUF without DECnet is 3K
words. The minimum size of XBUF with DECnet and endnode is
3K words. The minimum size of XBUF with DEC net and router
varies according to the size of your network, but is never less than
3K words. The maximum size is 496K words.

Small buffer pool
memory

The maximum allowed for your system, over and above the
minimum number you npecified during system installation (see
Part 1, Phase 3, Task 6). The size varies based on your hardware
and software configurations.

System clock

KWII-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 Part 5 of this guide for a complete description of DEFAULT.
If you need to perform additional preparatory tasks, go to Part 5 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. Mter 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.8YS offline options to perform additional preparatory tasks.
Finally, when you are ready to start your RSTS/E monitor, use the INIT.SYS
START option.

166

Start New Monitor

Response--Type START <monitor name>, where <monitor name> is the name of
your new RSTSIE monitor.
If you do not specify a monitor name, START starts the monitor that was used in
the previous timesharing session. The SYSGEN monitor was used in this case.
Memory allocation table:
OK:
67K:
446K:
512K:

00000000
00414000
03370000
04000000

00413777
03367777
03777777
End

67K)
379K)
66K)

EXEC
USER
XBUF
NXM

Memory available to RSTS/E is 512K words.

Explanation-START prints the current memory allocation table. The sample
memory allocation table is from the example installation in Part 1. These
messages may be slightly different due to configuration differences. Then START
checks that the SWAP.SYS file exists in account [0,1] on the system disk, is
large enough to hold 'one job a.t 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 I RETURN I to accept the default value, indicated by xx in the example. Or, enter
CTRL/C to return to the Option: prompt. You can tpen 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-cl~eating

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 RSTSIE monitor and extended
buffer pool allocation, and is contiguous. If the file does not exist, START
attenlPts 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

Start New Monitor

167

When a crash occurs, the RSTSIE monitor dwnps 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 thne of the crash, CRASH.SYS contains
import.ant. diagnostic information. For t11ese reasons, DIGITAL recommends
that you always have crash dump enabled during timesharing. In general, SPRs
submitted on system crashes without crash dumps will be answered by DIGITAL
as uInsufficient information."
Therefore, if you see the error message Crash dwnp automatically disabled,
follow these steps to enable crash dump:
1. Mter you begin timesharing, delete Wlnecessary files to create more

*** From [1,2] on KBO: at hh:mm AM/PM dd-mmm-yy
** RSTS/E is on the air ..•
~
RSTS V9.7 dd-mmm-yy hh:mm AM/PM
User:

Explanation-You are finished with the update. You can now press ~ 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.

168 Start New Monitor

Phase 6

Optional Tasks
This phase describes an optional task you may want to perf'onn to tune your
RSTSIE system to your needs.
The task in this phase is:
•

Task 1: Perfonn a Selective U pda te

Task 1: Perform a Selective Update
You can use the UPDATE.COM command file to perform a selective RSTSIE
update, without disturbing your existing system. UPDATE.COM resides in
account [0,1]. You can use it to:
•

Generate an updated monitor

•

Update one or more system program packages

•

Update layered products (integrated layered products only)

•

Copy layered product updates to your system

•

Perform a full system update
NOTE

You cannot perform a system update to V9.X on a pre-V9.X system.
You must first perform a full V9.X installation. For example, you
cannot perform a V9.7 update on a V9.6 system.
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, lGhe creation date of the new files win 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 fo:nnat:

@[O,1]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, SYS'TEM_PROGRAMS, and LAYERED_
PRODUCTS.

[package, ... ]

specifies the software package(s) to install when performing a
SYSTEM_PROGRAMS, LAYERED_PRODUCTS, or COPYUP operation (see Table 15). See Phase 4 in Part 1 for a complete list of
RSTSIE 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 15 lists
the UPDATE.COM commands and the resulting entry points into the update
process. See the a ppropria te Phase and Task in Part 4 for details on the actual
installation procedures.
When you use UPDATE.COM to perform an online installation, you first see Uris
question:
Please mount the Installation media.
Installation device < mmn:>?

This question asks for the location of your Installation media. The default is the
device on which you booted the Installation media.
Response--Press ~ to accept the default response. In the example
installa tion, the response is MSO.

170

Optional Tasks

The question also prompts you to mount the Installation tape or disk. The default
response is the device used during the last installation. See the example later in
this section if you need help answering this question.
Table 15 listA the UPDATE. COM commands and the resulting entry points into
the update process.
Table 15:

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

i@[O,l]UPDATE
:SYSTEM_PROGRAMS

Phase 3, Task 3

Begins system program update questions.

~@[O,l]UPDA,]~E

Phase 4, Task 2

Updates specified package.

Phase 3, Task 1

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

:SYSTEM_.PROGRAMS [pkg, ... ]
@[O,l]UPDA,]~E MONITOR

~@[O,l]UPDATE

:LAYERED_PRODUCTS

Use this function when you are directed to do so by
a specific layered product installation guide.

@[O,l]UPDATE
lLAYERED_PRODUCTS [pkg, ... ]

Use this function when 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.

Selective Update Example
This example uses UPDATE.COM to update the File Restore system program
package. You would use UPDATE.COM to update packages that you did not
update when you built your monitor. Before you run UPDATE.COM, you must
motmt 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,l]UPDATE SYSTEM_PROGRAMS RESTOR
Deleting all global symbols
RSTS/E Software Update Procedure

* Dialogue phase *
During this installation procedure you may:
Type '?' for help
Type 'A, to go back to the previous question
Type CTRL/Z to return to the beginning of the present section
Please mount the RSTS/E Installation media and enter the name
and unit number of the device.
Valid device types are: 'MM', 'MS', 'MT', 'MU', 'OM', 'DL' or 'SY'
(a response of SY allows monitor only).
Installation device? < MSO:>
Please enter the name and unit number of the disk to
whi<::!h you want to update the software. This disk
should be physically mounted and write-enabled.
Target disk? < SY:>

Optional Tasks

171

Assigning system logicals
The following will be updated:
RESTORE
You may answer "Yes" to accept this list, or "No" to change it.
Is this list OK? <yes> ~
Do you want the 1&0 versions of task:3? <Y> ~

** End of System Programs Section **
This is the end of the DIALOGUE phase.
The next phase is the BUILD phase.
Are you ready to proceed? <yes> ~

* Build phase *
13-Jun-89 01:56 PM
Restoring the File Restore package fJ:om the Installation kit
13-~un-89

01:58 PM

Updating system packages
Finished updating system packages
The RSTS/E Software Update Procedure is complete
Deleting all global symbols
Deassigning system logicals
13-Jun-89 01:59 PM
System tape label default set to DOS
_SY:[l,2JUPDATE.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.

172 Optional Tasks

Part 5
Offline Options

Offline Options
This part describes the offline INIT.SYS options you may need to use in the
management and maintenance of your RSTS/E system.
Table 16 lists the offline INIT.SYS options and suboptions.
Table 16:

INIT.SVS Options

Option

Suboption

Function

B001"

None

Bootstrap magnetic tape and disk devices.

DATE

None

Reset the current date and time.

DEFAULT

Memory Table
SUboptions:
LIST
PARITY
LOCK
UNLOCK
RESET
XBUF
BUFFERS

Change RSTSIE monitor defaults or allocation of
memory entities.

DSKINT

None

Initialize disks.

HARDWR

LIST
DISABLE
ENABLE
CSR
VECTOR
RESET
DM
HERTZ
SWITCH
ECO

Perform hardware-related tasks.
Set non-standard CSR devices.
Setting vectors for non-standard CR and CD devices.

List ECO information for DU and MU devices.

IDENT

None

Print INIT.SYS creation date plus list of patches.
Create and list system files; add bad blocks to the bad
block. file.

REFRESH

LIST
FILE
BADS

SAVRES

RESTORE
IDENTIFY
IMAGE

Reconstruct RSTSIE disks; make an image copy of a
RSTSIE disk; extract label information from a SAVE
set or a RSTSIE formatted disk.

START

None

Start, a RSTSIE monitor; print a list of disabled devices.
This option differs from answering YES to the Start
timesharing question.

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:

176

Response

Description

Accept the default response

I CTRUC I

Abort the operation and return to the Option: prompt

Obtain an online explanation of the question

Option: ~

Invoke the INIT.SYS START option

Offline Options

IBOOT-Bootstrap Devices
The BOOT option bootstraps magnetic tape and disk devices. Use the BOOT
option if:
•

You need to bootstrap an.other disk or tape.

•

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 V9.7 (dev) INIT V9.7-11
dd-mmm-yy - hh:mm AM/PM
Start timesharing? <Yes>

Explanation-Mter booting the device, INIT.SYS displays its banner, the date,
and the time. INIT.SYS prints the device name within parentheses 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.
e:001 Error Messages

A list of the BOOT error messages follows. If your error message does not appear,
see Appendix A.
NOT A VALID BOOT DEVICE
Explanation: The device you named is not a valid bootable device.
User Action: Type a question mark (?) for a list of devices that you can
bootstrap.
SORRY, BUT THAT DEVICE DOESN'T EXIST
Explanation: The device name you typed is valid, but the device does
not exist on your PDP-II.

Offline Options

177

DATE-Set the Date and Time Format
The DATE option sets the date and time. Use the DATE option if:
•

You need t.o reset or display the date.

•

You need to reset or display the time.

DATE Dialogue
Option:

DATE

Response-Type DATE or DA to the Option: prompt.
Today's date?

Current time?

Explanation-DATE asks for the new date and time . It prints the default
format in brackets.
Response-Type the date and time. You can enter the date in either of these
formats:
•

DD-MMM-YY (day, month, year)

•

YY.MM.DD (year, month, day)

You can enter the time in either of these fo:nnats:
•

HH:MM AMIPM (hour, minute, AM or PM)

•

HH:MM (24 hour clock)

Option:

Explanation-INIT.SYS returns to the Option: prompt.

178

Offline Options

[)EFAULT-Change RSTS/E Monitor Defaults
You can set the following defaults for your RSTSIE monitor with the DEFAULT
option of INIT.SYS:
•

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

•

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.

•

System clock - Choose the KW11-L line time clock or the KW11-P clock as the
system clock if you have more than one clock.

DEFAULT Dialogue
Option: DEFAULT

Response-Type DEFAULT or DE to the INIT.SYS Option: prompt.
Any memory allocation changes?
Table suboption? LIST
Memory allocation table:
OK:
53K:
445K:
512K:

00000000
00324000
03364000
04000000

00323777
03363777
03777777
End

53K}
392K)
67K)

EXEC
USER
XBUF
NXM

Memory available to RSTS/E is 512K words.

Explanation-DEFAULT now prints the memory allocation table prompt. 'These
messages may be slightly different due to configuration differences. At this point
you may want to adjust the memory allocation table. If so, answer YES to this
question, then go to the DEFAULT suboption sections that follow. You will be
forced into the Table suboption (with a message) if DEFAULT requires changes
that cannot be done automatically. 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 suboption to
change size of the Small Buffer Pool.
Response-Type YES if you want to use one of the memory table suboptions to
list or change the memory allocation table. Type NO to accept the current table.
If you want to list the current table, type YES to this question and then type
LIST at the Table suboption? prompt. Press ~ at the Table suboption?
pronlpt to continue with the DEFAULT dialogue.
Preferred clock <L>?

Explanation-Your hardware configuration can include one or both of these
system clocks: the KW11-L line time clock or the KW11-P programmable realtime clock. The KWII-L line time clock divides system time into intervals based
on the AC line frequency of the power source used to run your PDP-11 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).

Offline Options

179

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.
Response-Press I RETURN I 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 P to use the KWI1-P programmabl,e 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 lnaintained 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-Mter you specify defaults for your RS1'SIE monitor, DEFAULT
returns to the Option: prompt.

180

Offline Options

[)EFAULT 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
suboptions again to adjust the new monitor's memory allocation table.
The memory allocation table suboptions of DEFAULT are:
•

LIST - List the Memory Allocation Table

•

PARITY - List the Parity Memory Configuration

•

LOCK - Lock a Portion of Memory

•

UNLOCK - Unlock a Portion of Memory

•

RESET - Reset the Memory Allocation Table

•

XBUF - Allocate Memory to the Extended Buffer Pool

•

BUFFERS - Allocate Memory to the Small Buffer Pools

L.IST-List the Memory Allocation Table
The LIST suboption of DEFAULT lists the memory allocation table, which shows
the allocation of each block of memory.
Use the LIST suboption if:
•

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.

L.IST Dialogue
Any memory allocation changes <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 I RETURN I to continue with the DEFAULT dialogue.
Table suboption? LIST

Explanation-You see the 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 I RETURN I to continue with the DEFAULT dialogue.
Memory allocation table:
OK:
53K:
445K:
512K:

00000000
00324000
03364000
04000000

00323777
03363777
03777777
End

53K)
392K)
67K)

EXEC
USER
XBUF
NXM

Memory available to RSTS/E is 512K words.
Table suboption?

Offline Options

181

Explanation-Your table may not show the same values as the one in the example. These messages may be slightly dififerent due to configuration differences.
You read this table as follows:
•

Column one cont.ains t.he start. range (in K words) of memory. You read this
column vertically. In the example, the range starts at OK words and ends at
5I2K 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 RSTSIE monitor (EXEC).

•

Column four contains the amount of memory this range occupies in K words.
In the first line of the example, the RS'fSIE monitor (EXEC) occupies 53K
words of memory.

•

Column five specifies what occupies a particular range of memory:
EXEC-Represents the RSTSIE monitor, which always starts at OK
words.
USER-Represents memory 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-Il.

Response-Mter DEFAULT lists the memory allocation table, it returns to the
Table suboption? prompt. Press I RETURN I to continue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table suboptions.

PARITY-List the Parity Memory Configuration
The PARITY suboption of DEFAULT identifies and lo<!ates 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-ll.

Parity memory is memory that can detect certain errors. Interleaved parity
memory is memory in which alternate banl:ts respond to sequential memory
addresses, as in the following:
Parity Register

Parity Register

BANKO

BANK 1

Addresses

000000

000002

000004
000010

000006
000012

Note that parity register 00 responds to the first address (000000), parity register
02 responds to the next address (000002), and so forth.

182 Offline Options

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.
Mter 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 RSTSfE monitor can perform other functions,
inclu.ding 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. Mter 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 'Yrite operations,
thus resulting in faster program execution.
Nonparity memory is not supported by RSTSfE.

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:
256K:
384K:

00000000
01000000
02000000
03000000

00777777
01777777
02777777
03777777

128K)
128K)
128K)
128K)

00 (ECC)
02 (ECC)
04 (ECC)
06 (ECC)

Table suboption?

Explanation-In the example, PARITY shows the memory configuration for
a PDP-11144. Your parity memory depends on the type of PDP. 11 you have.
Mter 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. men 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.

Offline Options

183

Symbol

Meaning

Nonparity memory

NXM

Nonexistent memory

nn mm

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-Mter DEFAULT lists the parity memory configuration, it returns
to the Table suboption? prompt. Press ~URNI to continue with the DEFAULT
dialogue. Or, type one of the other DEFAULT table suboptions.

LOCK-Lock a Portion of Memory
The LOCK suboption of DEFAULT locks certain portions of memory, which
prevents the use of that memory during timesharing.
Use the LOCK suboption only if:
•

You need to lock a portion of defective memory. If sufficient undamaged
memory remains, you can start the monitor for normal timesharing.

•

You want to start the RSTSIE 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 suboption? prompt after you answer YES to the
Any memory allocation changes? DEFAULT question.
Response-Type LOCK or LO.
Lock address is? 90K+l

Explanation-LOCK asks you to specify the address or range of addresses you
want to lock.
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?

Explanation-Mter you specify an addreBs, LOCK returns to the Table
suboption? prompt.

184 Offline Options

Response-Type LIST or LI to list the memory allocation table and check that
you have locked the correct area of memory.
Memory allocation table:
OK:
53K:
90K:
91K:
445K:
512K:

00000000
00324000
00550000
00554000
03364000
04000000

00323777
00547777
00553777
03363777
03777777
End

53K)
37K)
lK)
354K)
67K)

EXEC
USER
LOCK
USER
XBUF
NXM

Memory available to RSTS/E is 512K words.
Table suboption?

Explanation-The memory allocation table shows that 1K of memory is now
lock.ed. These messages may be slightly different due to configuration differences.
Response-Mter DEFAULT lists the memory allocation table, it returns to the
Table suboption? prompt. Press ~ 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:
•

You cannot lock memory used by the monitor.

•

You cannot lock memory currently reserved for the extended buffer pool
(XBUF) until you 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 error
message: Part of that area is already in use.
RSTSIE 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 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.

Offline Options

185

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 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 i.s 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 usel~ 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 iEJ 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 lo~~s 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 subopti.on the next time you start the system.
Case 3: Multiple parity errors occur in rapid succession. RSTSIE 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 diagnosticEl 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. RSTSIE logs
this type of error. If the error occurs twice within one minute, RSTSIE disables
the part of the cache causing the malfunction. RSTSIE 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 randont problems may happen. At worst, the
system may crash with misleading clues aEI to the cause. It is for these reasons
that RSTSIE is not supported on systems that use nonparity memory.

UNLOCK-Unlock a Portion of Memory
The UNLOCK suboption of DEFAULT unlocks certain portions of memory to
make the memory available for use during timesharing by user jobs, or by the
extended buffer pool (XBUF).
Use the UNLOCK suboption after you repaired the memory you previously locked
with the LOCK suboption.

UNLOCK Dialogue
Table suboption? UNLOCK

Explanation-You see the Table suboption? prompt after you answer YES to the
Any memory allocation changes? DEFAULT question.

186

Offline Options

Response-Type UNLOCK or UN.
Unlock address is? 90K+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.
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 hYlPhen (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-Mter you specify an address, UNLOCK returns to the Table
suboption? prompt.
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:
445K:
512K:

00000000
00324000
03364000
04000000

00323777
03363777
03777777
End

53K)
392K)
67K)

EXEC
USER
XBUF
NXM

Memory available to RSTS/E is 512K words.
Table sUboption?

Explanation-Note that UNLOCK removes the 1K area of memory that was
locked in the previous example. These messages may be slightly different due to
configuration differences.
Response-Mter DEFAULT lists the memory allocation table, it returns to the
Table suboption? prompt. Press ~ to continue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table suboptions.

FIESET-Reset the Memory Allocation Table
The RESET suboption removes any changes made to the memory allocation table;
for example, locked portions of memory and reserved memory for the extended
buffer pool.
Use the RESET sub option only if you want to set up the memory allocation table
in the following way:
•

Release any memory previously allocated to the extended buffer pool (reduces
the extended buffer pool to 2K words).

•

Release any memory you previously locked.

•

Release any memory you previously allocated to the virtual disk.

Offline Options

187

RESET 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 reset the memory allocation table, it is useful to list the
current one. Type LIST or LI.
Memory allocation table:
OK:
54K:
445K:
512K:

00000000
00330000
03364000
04000000

00327777
03363777
03777777
End

54K)
392K)
67K)

EXEC
USER
XBUF

NXM

Memory available to RSTS/E is 512K wOl:ds.
Table suboption? RESET

Explanation-LIST shows a memory table for an example installation. These
messages may be slightly different due to configuration differences. Note that the
example table allocates 67K words of memory to XBUF.
Response--Type RESET or RE.
Table suboption? LIST

Explanation-DEFAULT immediately resets the memory allocation table and
returns to the Table suboption? prompt.
Response--It is useful to list the current lmemory allocation table after you use
the RESET suboption. Type LIST or LI.
Memory allocation table:
OK:
54K:
510K:
512K:

00000000
00330000
03770000
04000000

00327777
03767777
03777777
End

54K)
456K)
3K)

l!:XEC
USER
){BUF

NXM

Memory available to RSTS/E is 512K words.
Table suboption?

Explanation-Note that RESET deallocated all memory previously allocated
to XBUF and returned it to USER memory. These messages may be slightly
different due to configuration differences.
Response--Mter DEFAULT lists the metnory allocation table, it returns to the
Table suboption? prompt. Press I RETURN I to eontinue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table Eluboptions.

XBUF-Allocate Memory to the Extended Buffer Pool
The XBUF suboption reserves memory for the extended buffer pool.
INIT.8YS 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
and not allocated to the monitor.

188

Offline Options

INIT.SYS detennines the size and position of XBUF based on the following
guidelines:
•

If the amount of USER memory exceeds 128K words, then INIT.SYS al10cates
15% of that memory (rounded down to the nearest whole number) to XBUF.

•

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.

•

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.

•

The minimum amount of memory allocated to XBUF is 3K words. The
maximum is 496K words.

•

The legal ranges for locating XBUF are between 16K and 511K (words), 528K
and 1023K, 1040K and 1535K, and 1542K and 2043K.

If you are not familiar with the use of extended buffers on RSTS/E you should
read the section, Extended Buffer Pool Background Infonnation, before proceeding.

XBUF Dialogue
Table suboption? XBUF

Explanation-You see the Table suboption? prompt after you answer YES to the
Any memory allocation changes? DEFAULT question.
Response-Type XBUF.
Enter new extended buffer address size (3K-496K) <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 ofXBUF, followed by K to indicate K words. In
the example, the response is 67K. 1b release previously allocated memory for the
extended buffer pool to user memory, type RESET.
Table suboption? LIST

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

Offline Options

189

Memory allocation table:
OK:
53K:
445K:
512K:

00000000
00324000
03364000
04000000

00323777
03363777
03777777
End

53K)
392K)
67K)

EXEC
USER
XBUF
NXM

Memory available to RSTS/E is 512K words.
Table suboption?

Explanation-The memory allocation tablle shows the size and location of the
memory you have reserved for the extendedl buffer pool. These messages may be
slightly different due to configuration differences. For example, in this table 67K
words are reserved for XBUF.
Response--Mter DEFAULT lists the memory allocation table, it returns to the
Table suboption? prompt. Press ~ to continue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table s1l1boptions.

Extended Buffer Pool Background Information
Figure 7 shows art example RSTS/E systeln. It shows that memory is divided
into:

190

•

Monitor memory (EXEC) - an area of Inemory reserved for your RSTSIE
monitor. Monitor memory in the example occupies 53K words.

•

User memory (USER) - an area of meII1lory reserved for user jobs. In the
example, user memory occupies 392K 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, t.he size of the extended buffer pool is
67K words. The extended buffer pool o,C!cupies USER memory; thus, releasing
67K words from the extended buffer pOiol would increase USER memory to
459K words.

Offline Options

Figure 7:

Extended Buffer Pool for Example RSTS/E System

r--------------------,- EXEC
(RSTS/E
Monitor)

53K Words

53K 1--------------------+ USER

392K Words

445K

extended
buffer
pool

t---=-----=====----::::======---t XBUF

Gwo~

CKword00Kwor0

~I~

512K ~________.______E_xt_en_d_e_d_b_u_ffe_r_s____________~
ZK-9242-HC

Offline Options

191

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

The monitor can cache 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 disk accesses which results in
improved system response.

•

The monitor can output more line printer data reducing the stalling frequency
of the line printer when printing data.

•

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.

The following only use XBUF:
•

DECnetIE

•
•
•
•
•

LAT
LOADIINDEX
LOAD/OVERLAY
Statistics
Command/log files

Keep the following memory constraints in Iltlind 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 a 12K word area of memory to complete the
loading of the monitor. This 12K word area is allocated from USER (see the
memory allocation table) and must be a.bove the INIT.SYS image. If INIT.SYS
cannot find an 12K word area of memory above the INIT.SYS image (72K
words) and below 135K words (this value may be less depending on the size of
memory on your system), it prints an error message of the following format:
Please allocate 12K words of memory for user space between xxxK
and yyyK. Please note that the values for xxxK and yyyK are determined
dynamically by your system. These values may differ from the values of 72K
and 135K shown here.

The following sections discuss guidelines for determining the amount of user
memory you should reserve for the extended buffer pool with respect to:

192

•

Message send/receive code

•

Line printers

•

Data caching

•

Loaded indexes

Offline Options

•

File 1/0 window turns

•

DCL indirect command file 1/0 and/or terminal logging

•

System logicals

•

DECnetIE software

•

JRJ2780 software

•

2780/3780 software

•

Statistics

•

Quota information

•

Resident overlay code

Message SendlReceive Code
The RSTSIE 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:
•

Error logger - 2 messages

•

OPSER-based spooling package:
OPSER-2 messages
QUEMAN-2 messages
1 line printer spooler-2 messages
1 batch spooler-2 messages

•

PrintlBatch 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
message always uses at least 32 words of extended buffers. Each message can
range from 32 to 288 words.

Line Printers
The RSTSIE monitor uses extended buffers (or general small buffers) to store
characters awaiting printing on a line printer. You should allow 2.5K words of
mem.ory 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.
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, DECnet, RJ2780, logicals, DCL
commandllog buffers, or others from the previous list.

Offline Options

193

Cache Cluster Size

Maximum XBUF Usage

130K words

257K words

496K words

NOTE

The monitor uses extended buffers for eaching only when they are not
needed for other purposes.

Loaded Indexes
During timesharing you can optionally load the System Allocation Table (SAT) for
each disk (except read only) into memory. RSTSIE use extended buffers (XBUF)
to store these tables.
To improve system performance, you need tID allocate more XBUF to store the
SATs. The amount of XBUF required for ealch disk SAT depends on the disk size
and the disk pack cluster size. Use the following formula to calculate, in K words,
the XBUF required:

(disk size in blockslpack cluster size)/16884

File I/O Window Turns
The monitor uses extended buffers when processing file I/O window turns. This
can improve system performance, particulady on larger memory systems that
allocate large amounts ofXBUF and that have moderately fragmented files.
The actual amount of XBUF used at any given time is variable. You should
ini tially allocate 2K words for storing file 1/0 window turns. Later, you can adjust
the amount ofXBUF if required. Use the SHOW CACHE command to display
the largest amount of XBUF (in K words) used for file I/O window turns since
the system was started. If file 1/0 window turns is using more than 4K words,
increase XBUF.

DCL Indirect Command File 110 and TE,rminal Logging
The monitor uses extended buffers to store messages generated by indirect command file 1/0 and terminal logging. You should allow 1I4K word per simultaneous
command file 1/0 and/or terminal logging.

System Logicals
The monitor uses extended buffers to store system logicals. You should allow lK
word per 320 logicals.

DECnetIE Software
The monitor uses extended buffers to store messages generated by DECnetIE
software. See the DECnet/ E Installation Guide for information on how much
memory to reserve for the extended buffer pool.

LAT Usage
The monitor uses extended buffers to store messages generated by LAT. LAT
reqUires 1.3K words to start. Creating the first session from a given terminal server requires lK word. No additional extended buffers are required for
additional sessions from that server.

194

Offline Options

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.
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 lK 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 l3ystem disk.
Res:ident Overlay Code

The monitor uses extended buffer space for resident overlay code. The amount
can vary, depending on the overlay. Mter you load an overlay, use the SHOW
CACHE command to see the extended buffer usage, and adjust XBUF accordingly.

Extended Buffer Pool Worksheet
Figure 8 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

195

Figure 8:

Extended Buffer Pool Worksheet

Items Requiring Extended Buffers

Your Size

Contents of messages sent and waiting to be received*
Line printer driver*
Data caching
DCl indirect command file I/O and terminal logging
System logicals
DECnet/E
lAT
RJ2780
2780/3780 software
Statistics
Quota information
Resident overlay code

Total**

*The RSTS/E monitor can also use general smalll 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.

ZK-9243-HC

196

Offline Options

ElUFFERS--Aliocate Memory to the Small Buffer Pool
The BUFFERS suboption reserves more memory for the small buffer pool. Use
the BUFFERS suboption if your RSTSIE monitor needs more smnll 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:
•

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.

•

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.

•

Some software features use buffers momentarily, but it is difficult to calculate
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.

E'UFFERS 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.
How many K-words of extra buffer space (OK-2K) <OK>? 2K
You have 472 general + 132 FIP small buffers.
Adjusting memory table
Memory allocation table:
OK:
55K:
445K:
512K:

00000000 - 00333777
00340000 - 03363777
03364000 - 03777777
04000000 - End

55K)
390K)
67K)

EXEC
USER
XBUF
NXM

Memory available to RSTS/E is 512K words.
Table suboption?

Explanation-BUFFERS prints the range you can specify for your system.
These messages may be slightly different due to configuration differences. In
the example, the range is OK words to 2K words. The default value depends on
the memory size you have 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

Offline Options

197

buffer pool to accommodate only FIP small buffers. (You must perform another
system installation to add more general slnall buffers if you do not have data
space.)
ResJlonse-Type tlle numher of K wordR to reserve for the small hnffer 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.
Mter 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 1 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 RSTSIE monitor
is always rounded up to a multiple of 1K word, there is usually some extra space.
The RSTSIE 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 9 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-11 in this example instaUation has data space, it can increase
memory for the FIP small buffer pool to aecommodate more FIP small buffers.
Figure 9:

Example Small Buffer Table Printed During System Installation

Resident monitor size is 51K. By increasing this size
with the DEFAULT option of INIT, you can get additional
small buffers. This table shows the number and type of
small buffers you can get with each size change.
Number of buffers
K-words
OK
1K
2K
3K
4K
5K
6K
7K
9K
9K
10K
11K

General

FIP

444
472
472
620
649
648
649
649
649
649
649
648

2
36
100
19
52
116
180
244
309
372
436
494

If you choose to perform another installation, you may specify up
to 572 small buffers for this system. Doing so will
increase some of the buffer counts in the table.

198

Offline Options

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 1K word
of memory for the number of buffers you gain. For example, if the difference
between specifying 2K or 3K words of extra buffer space gives you only 10 more
small buffers, it may not be worth the cost of 1K word of physical memory.
Table suboption?

Response-Mter DEFAULT lists the memory allocation table, it returns to the
Table suboption? prompt. Press ~ to continue with the DEFAULT dialogue.
Or, type one of the other DEFAULT table suboptions.

Small Buffer Pool Background Infor'mation
Figure 10 shows an example RSTSIE installation. It shows that memory is
divided into:
•

.Monitor memory (EXEC) - An area of memory reserved for the RSTS/E
monitor. Monitor memOIY 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.

•

User memory (USER) - An area of memory reserved for user jobs. In the
example installation, USER memory occupies 392K words. Note that the
size of USER memory decreases to 390K words after the example installation
allocates 2K words for the FIP small buffer pool. The size of your USER
memory may differ.

•

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 10 also shows that monitor memory contains the:

•

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 1, 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 Instruction and data space. Data space
is available on the PDP-11/44, 11145, 11150, 11153, 11/55, 11/70, 11173, 11183,
or 11/84 and only if you do not use RJ2780 software.

•

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 suboption alone, and the other you can create with
the BUFFERS suboption and with data space. Figure 10 illustrates these two
:FIP small buffer pools.

Offline Options

199

Figure 10:

General and FIP Small BuffE~r Pools

general small
buffer pool
(resulting from
data space)

@ Wor~ @ wor~y <I6 wor~ general
small buffers

general small
buffer pool
(resulting from
SYSGEN question)
FIP small
buffer pool
FIP small
buffer pool
(resulting from
data space)

EXEC
(RSTS/E

@wor~@wo~y

16 Wor~

Monitor)

<if wor~ @ wo~y <f6 wor~ FIP small buffers
@: wor~ <If: Wor§:> 16 wor~
55K

USER

390K Words

445K
extended
buffer pool

XBUF
67K Words

512K
ZK-9239-HC

200 Offline Options

The RSTSIE monitor uses general small buffers as a temporary storage area for
such things as:
•

The input and output of characters

•

Data transfers

•

Send/receive messages

•

File processing requests

•

Information on open files and DCL file information

•

CCL command definitions

•

Asynchronous I/O requests

•

Run-time system and library descriptions

•

LAT connections

•

DECnet connections

In contrast to general small buffers, FIP small buffers are used only to store
open files information, CeL command definitions, resident library attachment
information, and open channel status. When the monitor needs a small buffer
for one of the above, 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,
then the monitor uses general small buffers to store open files information, CCL
command definitions, resident library attachment information, and open channel
status. 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:
•

Jobs begin to stall, until some small buffers become available to process the
jobs' requests. Thus, performance begins to suffer.

•

The monitor discards error information destined for the error logger.

•

The error message ?Logins are disabled - please try again later appears
when users try to log in. (This happens when the number of general small
buffers falls below 40.)

•

Batch jobs do not start. (This happens when the number of general small
buffers falls below 40.)

•

Programs begin to fail with the message ?No buffer space available.

•

DECnet or LAT connections are rejected.

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 SHOW BUFFERS command gives the same display as the SYSTAT program.
The RSTS/E Utilities Reference Manual describes SYSTAT. 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.

Offline Options

201

The rest of this section discusses guidelines for determining how many small
buffers you need with respect to:
•

Jobs

•

CCL command definitions

•

Auxiliary run-time systems

•

Resident libraries

•

Open files and DCL file information

•

Message receivers

•

List of messages sent and waiting to be -received

•

Contents of messages sent and waiting to be received

•

Terminals

•

Line printers

•

Paper tape readers and punches

•

EMT logger

•

Outstanding I/O requests

•

BACKUP program

•

LAT connections

•

Dynamic Pseudo-Keyboards

•

Margin of safety

Jobs
The monitor uses general and FIP small buffers to store information about each
job. Allow two general and one FIP or general small buffers per job.
CCL Command Definitions
The monitor uses general or FIP small buffers to store eCL 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 DCL DEFINE command, which you use to define CCL commands.
Auxiliary Run-Time Systems
The monitor uses general small buffers to store information about auxiliary runtime systems that you add with the DCL INSTALL command. Allow one general
small buffer for each auxiliary run-time system.
Resident Libraries
The monitor uses general sma11 buffers to store infOlmation about resident
libraries. Allow one general small buffer for each resident library and each
dynamic region. Allow one to four FIP small buffers for each program that uses
libraries. Allow two FIP buffers for programs that use RMS libraries.
Open Files and DCL 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.

202

Offline Options

For each program allow:
•

One general or FIP small buffer for each open file, including files opened by
DCL, command files, and log files.

•

One genera] 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.

•

One FIP or general small buffer per open file on DCL's I/O channel.

•

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 PrintlBatch 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 waiting to be received
including DECnet messages. This buffer does not store the contents of the
message.

Contents of Error Logger Messages Sent and Waiting to be Received
The monitor stores the contents of error logger messages sent in general small
buffers. 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.

Terminals
The monitor uses general snlall buffers to store:
•

Characters written by a job and awaiting display on a terminal

•

Characters typed by a user and waiting to be read by a job

•

Characters written by a job and awaiting printing on a hard-copy terminal

You should allow:
•

Five general small buffers for each interactive terminal, several more if you
use echo control and FMS

•

Ten general small buffers for each hard-copy terminal

Offline Options

203

Line Printers
The RSTSIE monitor uses general small buffers (or the extended buffer pool) to
store characters awaiting printing on a line printer. If you reserved memory in
the extended buffer pool for line printers, you need not specifY any smnll buffers.
If you need general small buffers for this purpose, specify 20 for each line printer.

Paper Tape ReaderlPunch
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/reader.

EMTLogging
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 1.) You should specify 1 general small buffer
if you have EMT logging.

Outstanding Asynchronous 110 Reque!sts
Each outstanding asynchronous 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.

Synchronous I/O requests require a varying number of buffers per request. The
number varies according to the device. Allow 30 buffers for this purpose.

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.

LAT connections
Creating the first session from a given terminal server requires 8 small buffers.
Each additional session from that server requires 4 Inore small buffers. Mter
creation, the session uses small buffers in the same manner as any terminal.

Dynamic Pseudo-Keyboards
Creating dynamic pseudo-keyboards requires allocating 3 small buffers. Mter
creation, dynamic pseudo-keyboards use s'mall buffers in the same manner way
as any terminal.

Margin of Safety
Mter 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.

204

Offline Options

IGeneral and FIP Small Buffer Pool Worksheet
Figure 11 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.
NOTE

During start-up, INIT.SYS uses a 12K word area of memory to complete
the loading of the monitor. This 12K word area is allocated from USER
(see the memory allocation table) and must be above the INIT.SYS
image. If INIT.SYS cannot find an 12K word area of memory above the
INIT.SYS image (72K words) and below 135K words (this value may
be less depending on the size of memory on your system), it prints an
error message of the following format: Please allocate 12K words
of memory for user space between xx:xK and yyyK. Please note
that the values for xxxK and yyyK are determined dynamically by your
system. These values tnay differ from the values of 72K and 135K
shown here.

Offline Options

205

Figure 11:

General and FIP Small Buffer Pool Worksheet

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 bo received*
Terminals
Line printers·
Paper tape reader/punch
EMT logging
Outstanding I/O requests
BACKUP program
LA T connections
Dynamic Pseudo-Keyboards
Margin of safety

Total

*The RSTS/E monitor can also use extended buffers to store these items.

ZK-9246-HC

206

Offline Options

I)SKINT--Initialize RSTS/E Disks
The DSKINT option initializes a RSTSIE disk. DSKINT:
•

Optionally fonnats the disk - DSKINT writes tim;ng and sense marks on
some disks and destroys any previously stored information.

•

Optionally checks the disk for bad blocks - DSKINT locates bad blocks on the
disk and allocates them to the bad block file (BADB.SYS).

•

Writes a minimum RSTSIE file structure on the disk - The minimum RSTS/E
file structure contains a pack label and three directories:
The Master File Directory (MFD).
The Group File Directory (GFD) for group O.
The User File Directory (UFD) for account [0,1].
Prepares the disk to accept RSTSIE system and other files.

For the DSKINT option, these responses have special meaning:
Response

Description

Accept the default. response

Obtain an online explanation of the question

Return to the previous question

ICTRU~

ICTRU

Restart DSKINT dialogue
Abort DSKINT and return to the Option: prompt

-----------------------------------------------------------------

[)SKINT D~alogue
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-Type the device designator of the drive on which your disk is
mounted.
NOTE

If the message "Performing limited hardware scan." was printed during
this boot and you try to initialize or copy to a nonexistent disk, then
you will receive the following error messages:
That disk was not found during limited hardware scan.
Do you wish to perform a reboot with full hardware scan <YES>?

Response-If the user answers YES, then the distribution device will be rebooted
and the "Performing limited hardware scan." message will NOT reappear.

Offline Options

207

Unit?

Explanation-DSKINT asks for the unit number of the disk drive on which your
disk is mounted.
Response--Type the device unit number.
Response--If the user answers YES, then the distribution device will be rebooted
and the "Performing limited hardware scan," message will NOT reappear.
This disk appears to be a RSTS/E formatted
disk with the following characteristics:
Pack 10:

PATTIE

Pack Cluster Size:

Pack is currently:

Private,
Update access date on writes.
Level: 1.1

Pack IO?

Explanation-Mter you type the unit nuulber, 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 this 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, the pack ID 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 fornlat level is RDS1.1.
This information lets you decide whether to initialize the disk. When you
initialize a disk, you destroy any information stored on it.
Mter printing the pack label information, DSKINT asks for a pack ID. The
pack ID is a system-wide logical name. You must specify this pack ID when you
logically mount the disk.
Response--Type a pack ID. The pack ID can be any combination of alphanumeric characters up to 6 characters long.
Pack cluster size <4>?

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 RSTSIE 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 system. The pack cluster size affects disk space and speed
of file creation and access. A large pack cluster size improves access time to

208

Offline Options

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 17. Or, press
~~ to accept the default value (4, in this example).

Table 17:

Disk Pack Cluster Sizes

Disk Type

Pack Cluster Size

RA60
RA80
RA81

8,16,32,64
4,8,16,32,64
16,32,64
32,64
1,2,4,8,16,32,64
2,4,8,16,32,64
2,4,8,16,32,64
1,2,4,8,16,32,64
1,2,4,8,16,32,64
4,8,16,32,64
8,16,32,64
1,2,4,8,16,32,64
1,2,4,8,16,32,64

RA82
RC25
RD31
RD32
RD51
RD52
RD53
RD54
RK05 1
RK05F 1
RK06
RK07
RL01 1
RL02
RM02
RM03
RM05
RM80
RP04

1,2,4,8,16,32,64
1,2,4,8,16,32,64
1,2,4,8,16,32,64
1,2,4,8,16,32,64
4,8,16,32,64
4,8,16,32,64
8,16,32,64
4,8,16,32,64
4,8,16,32,64

RP05
RP06
RX33 1
RX50 1

4,8,16,32,64
8,16,32,64
1,2,4,8,16,32,64
1,2,4,8,16,32,64

1 _

You cannot use these disks as system disks.

Offline Options

209

MFD cluster size <16>1

Explanation-The master file directory (MFD) stores information about all
groups on a disk. The monitor accesses the MFD each time you add 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
unless the pack cluster size is 32 or 64. If the pack cluster size is 32 or 64, then
the MFD cluster size must be 16. Legal values for the MFD cluster size are 4,8,
or 16.
Response-Press ~ to accept the default response, (16, in this example).
Or, specify the value 4, 8, or 16.
SATT.SYS base <13543>1

Explanation-The SATI'.SYS file controls the use of storage space on a disk
through a storage allocation table (SAT). 'rhe 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 or
use LOADIINDEX, 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 18 for a Hst
of device cluster sizes and total device sizes.
Response-Press I RETURN I to have DSKINT position the file near the center of the
disk.
Or, type the device cluster number where you want the file placed.

210

Offline Options

Table 18: Device Cluster Sizes and Total Device Sizes
Disk Type

Device Cluster Size

Total Available Blocks 2

RA60
RA80
RA81
RA82
RC25
RD31
RD32
RD51
RD52
RD53
RD54
RK05 1
RK05F1
RK06
RK07
RLOl l
RL02
RM02
RM03
RM05
RM80
RPO·4
RPOf)
RP06

8
4
16
32
1
2
2
1
1
4
8
1
1
1
1
1
1
4
4
8
4
4
4
8
1
1

400168
237208
891056
1216640
50901 per unit; 2 units per spindle
41559
83204
21599
60479
138668
311200
4800
4800 per unit; 2 units per drive
27104
53768
10220
20460
131648
131648
500352
242572
171796
171796
340664
2400
800

RX.33 1

RX50 1

1You cannot use these disks as system disks.
2Total available blocks represent the number of blocks when the disk is initialized at the device
cluster size. The number of blocks on the RAlRCIRD class disks is subject to change with new
revisions of these 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 contains 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. Or, type NO or press ~ if you
want DSKINT to allocate only the minimum of 0 or 1 clusters.

Offline Options

211

PUB, PRI, or SYS <PRI>?

Explanation-This question asks you to designate the disk you are initializing
as either public, private, or system. The Bystem disk is the disk on which the
RSTS/E monitor resides. It always contains account [1,2].
Response-Type PUB, PRI, or SYS.
Create [1,1] 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]. DSKINT 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 I RETURN I if you do not want to create account [1,1] at this time.
DSKINT then skips the next question. You can also use the CREATE/ACCOUNT
command to create, pre-extend, and positJion account [1,1] on line during
timesharing.
[1,1] cluster size <16>?

Explanation-This question asks for the cluster size of the User File Directory
(UFD) for account [1,1]. The UFD 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 ~ 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 unless the pack cluster size is 32 or 64. If the
pack cluster size is 32 or 64, then the UFD cluster size must be 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 Wan1G to create account [1,2]. DSKINT
automatically creates account [1,2] if you t.yped SYS to the PUB, PRI, or SYS?
question.
Response-Type YES to create this account. DSKINT then prints the next
question. Or, type NO or press ~ if you do not want to create account
[1,2] at this time. DSKINT 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 <16>?

212

Offline Options

[1,1] and [1,2] account base <13541>?

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
wit.hin 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 DSKINT
if you specified ~ to that question (13541, in the example). DSKINT may
show a different number for your disk.
Response--Press ~ 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 18 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 ~ 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.
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 Wlites.
New 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 I RETURN I 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-only <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 ~ 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.
DSKlNT 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.

Offline Options

213

Response-DIGITAL recommends that you type YES or press ~ 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.
Format <NO>'?

Explanation-This question asks if you need to format your disk. Formatting
a disk means that DSKINT writes timing atnd sense marks onto the disk and
destroys any information that previously e~dsted on the disk. You must format
the following disks if you are initializing them for the first time: RK05, RK05F,
RP04, RP05, RP06, RX33.
You can optionally reformat these disks: R]{06, RK07, RM02, RM03, RM05.
You cannot format or reformat (in which ca.se this question would not appear)
these disks: RLOI, RL02, RA60, RA80, RABI, RA82, RC25, RCF25, RM80, RD31,
RD32, RD51, RD52, RD53, RD54, and RX50.
NOTE

Except for an RX33, when you are fOImatting a disk, DIGITAL
recommends that you mount the disk IOn the drive and leave it spinning
for at least 20-30 minutes before initializing it. This ensures that the
disk temperature is stable and unifonn 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 ~ if you do
not need to format the disk.
Patterns <3>1

Explanation-This question asks for the number of patterns DSKINT should
use in checking for bad blocks. DSKINT w:rites 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 to fully check for all bad blocks. Three patterns offer the greatest
probability of finding all bad blocks on the disk. 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.

214 Offline Options

•

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 ~ to erase the disk. Or, type NO to write
only the basic RSTSIE 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.
Res:ponse-Type Y to proceed with the disk initialization.
Or, type N to abort the initialization and return to the Option: prompt.
Option:

Explanation-INIT.SYS completes the disk initialization. Then it prints the
Option: prompt.
[)SKINT Error Messages

A list of the DSKINT error messages follows. If your error message does not
appear, see Appendix A.
BLOCK NUMBER TOO BIG
Explanation: The block number you typed is greater than or equal to
the maximum logical block number for the disk.
?DRIVE NOT READY:
Explanation: The initialization cannot proceed because the disk to be
initialized is not on line and ready.
User Action: You can make the drive ready and press ~ to
proceed, or you can press CTRL/C to abort the initialization.
?DSKINT NOT LEGAL ON SYSTEM DISK
Explanation: You specified the disk from which the initialization
code was bootstrapped. You cannot initialize this disk now because the
initialization code would be destroyed.
FORMATTING FAILURE:
Explanation: The disk could not be formatted.
User Action: Mount the disk on the drive and leave it spinning for
20-30 minutes before formatting the disk. If you still receive the same

error message after one retry, then use a new disk.
?ILLEGAL DISK NAME
Explanation: The string you typed is not the name of a valid RSTS/E
disk device.
User Action: Enter a valid name.
?ILLEGAL NUMBER OF PATTERNS
Explanation: The number of patterns must be 0 through 3.

Offline Options

215

?ILLEGAL NUMBER, TRY AGAIN
Explanation: The number you typed is not a valid octal number
between 1 and 177777.

?ILLEGAL PACK ID
Explanation: The pack ID must consist only of characters from "A" to
"Z" or "0" through "9."

?SORRY, BUT THAT DISK DOESN'T EXIST
Explanation: The string you typed is a valid RSTS/E disk name, but
that disk controller or the unit nwnber does not exist on this system.

THAT DISK WAS NOT FOUND DURING LIMITED HARDWARE SCAN
Explanation: You tried to initialize or copy to a nonexistent DU type
disk.
User Action: If you answer YES to the "Do you wish to perform a
reboot with full hardware scan ?", then the distribution device will be
rebooted and the "Performing limited hardware scan." message will NOT
reappear.

?UNABLE TO READ BAD BLOCK TRACK DATA
Explanation: The manufacturer's bad block information could not be
read.
User Action: Either run 3 patterns on the pack or try a different pack.

216

Offline Options

IHARDWR-Adjust the Hardware Configuration
The HARDWR option performs tasks related to the hardware your RSTSIE
monitor supports. The following sections describe the HARDWR suboptions.
These suboptions affect your system disk, not your installed monitor. Thus, if
you add or remove nonstandard hardware, you may need to use these suboptions
again. However, if you only install a different monitor, you do not need to use
these suboptions again. You must repeat the HARDWR option each time you
install a new version of RSTS.
The HARDWR suboptions are:
•

HARDWR LIST - List the Hardware Configuration Table

•

HARDWR ECO - Show Revision Level of Controllers for which the
Information is Available

•

HARDWR DISABLE - Disable a Device Controller

•

HARDWR ENABLE - Enable a Device Controller

•

HARDWR CSR - Declare a Nonstandard Controller Address

•

HARDWR VECTOR - Declare a Nonstandard Vector Assignment for a Card
Reader

•

HARDWR RESET - Set All Controller Addresses and Vector Assignments to
the Standard, and Enable All Devices

•

HARDWR DM - Declare DMII-BB and DHll Associations

•

HARDWR HERTZ - Specify AC Line Frequency

•

HARDWR SWITCH - Specify CPU Switch Register Characteristics

IHARDWR LIST-List the Hardware Configuration Table
The LIST suboption lists the hardware configuration table. This table shows the
current hardware configuration and allows you to verify any changes you have
made.
Us"e"the LIST suboption if:
•

You want to list the current hardware configuration table.

•

You need to list the table to see what changes you have made to your
hardware configuration.

LIST Dialogue
Option: HARDWR

Response-Type HARDWR or HA to the INIT.8YS Option: prompt.
HARDWR suboption? LIST

Response-Type LIST or LI to list the hardware configuration table.

Offline Options

217

Name

Address Vector

TTO:
RK:
RL:

177560
177400
174400
177440
176700
172150
172440
177514
175610
175620
170700
170500
160020
160070
160120
160130
160140
160150
160160
160200
160130
160220
160400

060
220
160
210
254
P340
224
200
300
510

XEO: 174510
KW11L 177546
SR
177570
177570
DR

120
100

RM:

RR:
RUO:
TUO:
LPO:
DEO:
DEl:
KGO:
DMO:
DHO:
D10:
XMO:
XM1:
XM2:
XM3:
XM4:
DZO:
DZ1:
XKO:
XDO:

320
310
330
340
350
360
370
400
420
330
420
430

Comments
Units: o (RK05) 1 (RK05)
Units: o (RL02)
Units: 2 (RK07)
Units: 0(RM02 DP)
UDA50
Units: 2 (RASO)
Units: 0(TU16 @TM02 to)

DHO
Type: DMC,
Type: DMC,
Type: DMC,
Type: DMC,
Type: DMR,
Sub-lines:

Local.
Local.
Remot.e
Remot.e
Remot;e DMC Mode integral modem
S

Type: DMP, Low sJpeed, Programmable
mode, Boot enable
DEUNA Address: OS-00-2B-01-0B-7F

Hertz = 60.
Other: FPU, CIS, 22-Bit, Data space, Cache
HARDWR suboption?

Explanation-In this example, taken frorn 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
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.

218

Offline Options

Each line has four columns:
Name

The name and number of the device controller

Address

The address of the cont.roller'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. An uppercase "P" precedes a programmable vector, which
indicates that the initialization code assigned the vector address.

Comments

Information about the controller or devices on that controller. Table 19
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 20 summarizes what you might see on your hardware configuration table.
Response-Type EXIT or press ~ to return to the Option: prompt.
Table 19:

Hardware Comments Table

Device

Comment and Meaning

ALL

Disabled
Device is (or will be) disabled.

ALL

Not found
Device was not found.

units:m(RK05,RK05F) ... t(RK05,RK05F)
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.

units: m(RL01,RL02) ... p(RL01,RL02)
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.

units: m(RK06,RK07) ... t(RK06,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.

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.

Offline Options

219

Table 19 (Cont.):

Hardware Comments Table

Device

Comment and Meaning

UDA50A units: m(RA60, RA80, RA81, RA82) ... t(RA60, RA80, RA81, RA82)
RC25 units: m(RCF25,RC25) ... t(RCF25, RC25)
RQDX units: m(RD31, RD32, RD51, IlD52, RD53, RD54, RX33, RX50) ...
t(RD31, RD32, RD51, RD52, RD53, RlD54, RX33, 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.

TK50 unit: m(TK50)
TU81 unit: n(TU81)
m through n are unit numbers of drives that exist on the controller. The disk
type appears in parentheses after each unit number.

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.

BAE =+xxx
BAE indicates that the device controller supports 22-bit addressing and has a
Bus Address Extension register at tho specified offset from its CSR base.
units: m(TUI6@'l'M02#X) ... t(TUI6@TM02#X)
m through t are unit numbers of drives that exist on the controller (8 are
possible). The tape type, formatter type, and the formatter number appear
in parentheses after each unit numbElr. The TU16, TEI6, 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.

DHn
DHII controller number n is logically associated with this DMII-BB unit.
No DHII

No DHII controller is logically associated with this DMII-BB unit.
sublines:(4,8)?
This DZ type device has either 4 or 8 terminal ports.

sublines: (8, 16)

Type: DMP or DMV, Low or High Speed, Programmable Mode or Remote
Channel, FDX or HDX, Tributary or Controller, Boot Enable or Load Enable.

This DHVIDHU type device has either 8 or 16 terminal ports.

You will either see DMP or DMV list,ed for the first entry because the DMPl1
devices are UNIBUS devices while the DMVl1 devices are QBUS devices.
XE

DEUNA Address: AA-OO-03-01-0B-7EI'
The XEn device will be reported as a DEUNA or as a DELUA device depending
on which device exists on your controller. These devices will only exist on
UNIBUS machines. The address is the "Ethernet Hardware Address" which
is the 48-bit address built into the controller. This address ensures that the
device will always have a unique address on any Ethernet it inhabits. For
further information, see the RSTSIE Programming Manual or the DECnet
documentation.

220

Offline Options

Table 19 (Cont.):

Hardware Comments Table

Device

Comment and Meaning

DEQNA Address: AA-00-3-AA-OC-4D
The XHn device will be reported as a DEQNA or as a DELQA device depending
on which device exists on your controller. These devices will only exist on
a QBUS machine. The address is the "Ethernet Hardware Address" which
is the 48-bit address built into the controller. This address ensures that the
device will always have a unique address on any Ethernet it inhabits. For
further information, see the RSTSIE Programming Manual or the DECnet
documentation.

Type: DMC or DMR
A DMC device has the following options: Remote, Local Micro, Remote Line, or
Remote Micro, Local Line.
A DMR device is a more versatile device that the DMC. It has the following
additional options:
•

DMR mode, 1 megabaud, less than 1 megabaud, Local DMC mode, or
Remote DMC mode.
Integral Modem - the DMR uses coax.
RS232/423 Interface, RS422 Interface, unknown Interface, or CCIT!' V.35.

•
•
RX

units: n(RX01,RX02)

Table 20:

Summary Hardware Configuration Table

Mnemonic

Line and Meaning

KW11-L

177546 100
Reports the address and vector of the KW11-L line clock if the
clock exists on the system.

KW11-P

172540 104
If the system has a KWll-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 suboption 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.

HERTZ

50
60

The system's AC line frequency is always reported.

(HERTZ = 50)
60

There is a pending change to the system's AC line frequency.

CIS

The CPU has the Commercial Instruction Set (CIS) option.

Offline Options

221

Table 20 (Cont.):

Summary Hardware Configuration Table

Mnemonic

Line and Meaning

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

FIS

The CPU has the Floating Instruction Set (FIS) option (PDP-"
11/35 and 11/40 only).

The CPU has a stack limit register.

MED

The CPU has the Mailntenance 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 ID = nnnnn

The contents of the CPU identification register are reported, if
the register exists.

F11 CPU

The processor type is F11 (PDP-11/23 or 11/24).

J11 CPU

The processor type is J11 (PDP-11153, 11/73, 11/83, or 11184).

11/44 CPU

The processor type is a PDP-11144.

DATA SPACE

The CPU has Instruction and Data Space.

HARDWR ECO-Show revision level of MSCP and TMSCP controllers
The ECO suboption lists the hardware and software (microcode) revision levels
for all controllers on your system for which this information is available. This is
used by Field Service to ensure that your controllers are at current revision level.

ECO Dialogue
Option: HARDWR

Response-Type HARDWR or HA to the INIT.SYS Option: prompt.
HARDWR suboption? ECO

Response-Type ECO to list MSCPITMSCP revision levels.
Name
RUO:
MUO:

Address
172520
160334

SW Rev
3
4

HW Rev
None
2

HARDWR suboption?

NOTE

This is just an example. These numbers do NOT represent the actual
revisions for any current hardware.
Explanation-The first column of this list contains the controller name; MSCP
disks are shown as "RU" and TMSCP tapes are shown as "MU." The second
column shows the CSR address for this controller. The third column shows the
software (microcode) revision level of this controller, and the fourth column shows
the hardware revision level of this controller.

222

Offline Options

On some controllers, the hardware or software revision levels (or perhaps
both) are not program-readable. In this case, the word "None" appears in the
appropriate place.
If, during system autosizing it was discovered that a controller is so far out of
revision so as to be unusable by RSTSIE, then the phrase "Not supported" will
appear under the "SW Rev" and "RW Rev" columns.
t

If there are no MSCP or TMSCP controllers on the system, a message stating so
will be printed instead of the table above.
Response-Type EXIT or press ~ to return to the Option: prompt.

liARDWR DISABLE-Disable a Device Controller
The DISABLE suboption disables a device controller; that is, makes it unavailable
for use. For example, the RM controller controls all RK06 and all RK07 disk
drives. If you disable the RM controller, you disable all RK06 and RK07 disk
drives.
Use the DISABLE suboption if:
•

You need to disable a controller that needs repairs.

•

You need to disable an erroneously detected controller. For example, you may
have installed a TSII magnetic tape drive at a nonstandard CSR address of
177170. However, INIT.SYS expects to find the RXOl/RX02 flexible diskette
controller at this address. If you do not use the CSR suboption to declare
the TSll as having a nonstandard CSR, then you must disable the device by
disabling the RX (really TSl1) 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.8YS
enables the nonexistent PDP-II device.

•

Your configuration contains too many devices to start timesharing. RSTSIE
includes many features which are based on the presence of hardware. If too
much hardware is present, you may exceed your memory limits or RSTS/E
software limits.

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

Offline Options

223

Name
TT
RK
RL
RM

RB
RR
RU
TC
TS
TM
MU
TU
PR
PP
LP
RX
CR
CD
KL
DL
DE
DP
DC
KG
DM
DH
DU
D1
XM
DZ
XK
XD
XN
XE
VH
XH
BS

Max no
1

1
1
1
1

1
4
1
4
1
4

1
1
1
8

4
1

1
16
31
31
2
2
8

16
16
16
16
16
16
16
16
16
4

16
4
4

Description
Console terminal
RK05/RK05F disk
RL01/RL02 disk
RK06/RK07 disk
RP04/RP05/RP06 disk
RM02/RM03/RM05/RM80 disk
MSCP class disks
TC11 DECtape
TS11/TSV05/TK25/TU80 magtape
TU10/TE10/TS03 magtape
TMSCP class tapes: TK50/TU81 cartridge magtape
TU16/TE16/TU45/TU77 magtape
Paper tape reader
Paper tape punch
Line printer
RX11 flexible diskette
CR11/CM11 card reader
CD11 card reader
KL11/DL11A/DL11B single-line interface
DL11C/DL11D single-line interface
DL11E single-line interface
DP11 synchronous line interface
DC11 single-line interface
KG11 CRC arithmetic unit
DM11-BB modem control for DH11
DH11 16 line multiplexer
DUll single-line synchronous interface
DUP11 single-line synchronous interface
DMC11/DMR11 interprocessor link
DZ11/DZV11 8 line multiplexer
KMC-11 microprocesl:'or
DMP11/DMV11 interprocessor link
DN11 automatic calling unit interface
DEUNA/DELUA Ethernet controller
DHV11/DHU11 8/16 line multiplexer
DEQNA/DELQA/DESQA E:thernet controller
DT07 Bus Switch

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
RSTSIE monitor can support. The third column describes the devices controlled
by the controller.
Mter 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 numbE~red 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 RSTSIE
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 RSTSIE monitor
can support more than one line printer controller.
Pres~ CTRL/Z or the ~ key to exit froln this suboption without specifying n
controller name.

224

Offline Options

HARDWR suboption?

Explanation-HARDWR does not immediately disable the controller specified in
the previous question, but returns to the HARDWR suboption? prompt. This lets
you check your responses by listing the CUlTent hardware configuration table.
Response-Type LIST or LI. Type EXIT or press 1"fiEi'U!.UD to return to the Option:
prolnpt. Press CTRL/C to cancel any changes and return to the Option: prompt.
HARDWR makes the indicated changes, bootstraps your system disk, and prints
one of three messages:

•
Option:

The Option: prompt indicates you have made no hardware changes or that
INIT.SYS has previously completed a scan of the hardware configuration.

•
nn changes being made
Rebooting . . .

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.

•
Enabling all devices.
nn changes pending
Rebooting . . .

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.

HIARDWR 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 I~NABLE suboption to enable a controller, you use the DISABLE suboption to
disable a controller.
Use the ENABLE suboption only if you need to enable a controller that was
previously disabled.

E:NABLE: 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.

Offline Options

225

Controller to enable?

Explanation-ENABLE asks for the name of the controller to enable. Before
you do that, however, it may be useful to liElt 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 RSTSIE 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 maximum number possible, minus 1.
You can omit a controller number only if the maximum number supported by the
RSTSIE monitor is 1. For example, you could type RL to this question rather
than RLO because the maximum number of RL controllers that a RSTSIE 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 RSTSIE monitor can
support more than 1 line printer controller.
Or, press CTRUZ to exit from this sub option without specifying a controller
name.
HARDWR suboption?

Explanation-HARDWR does not immediately enable the controller, but returns
to the HARDWR suboption? prompt. This lets you check your responses by
listing the current hardware configuration table.
Response-Type LIST or LI to see the CUlTent hardware configuration table.
Type EXIT or press I RETURN I to return to the Option: prompt. Press CTRUC to
cancel any changes and return to the Option: prompt.
Mter you type EXIT or press I RETURN b HARDWR makes the specified changes,
bootstraps your system disk, and prints oDIe of three messages (see the previoUf~
section, Disable a Device Controller).

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.8YS program, it checks the number of each type of
controller on the system·by applying standard rules for locating the CSR set. See
Appendix D for a discussion of the checks performed by INIT.SYS.
Use the CSR suboption only if:
•

You need to install a controller at another address because you have
nonstandard hardware.

•

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 telnporary measure until you have the
address assignment corrected.

226

Offline Options

C:SR 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.
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 RSTSIE 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?

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?
Option:

Explanation-HARDWR does not immediately assign the address you specified
to the nonstandard controller', but returns to the HARDWR suboption? 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 I RETURN I to return to the Option: prompt.
Mter you type EXIT or press I RETURN L HARDWR makes the specified changes,
bootstraps your system disk, and prints one of three messages (see the previous
section, Disable a Device Controller).

I-1IARDWR VECTOR-Declare a Nonstandard Vector Assignment
The VECTOR suboption of HARDWR specifies a nonstandard vector address for
CR: or CD: devices.

Offline Options 227

NOTE

This task is for DIGITAL Field Servicf~ representatives who might
have to perform it during hardware installation or during new version
updates.
Use the VECTOR suboption only if:
•

The hardware configuration includes more than one card reader.

•

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.
For controllers that contain a programmable vector register (MSCP and TMSCP
class controllers), INIT.SYS assigns the first unused vector in the floating vector
range to that controller.
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.8YS checks each 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.8YS 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 incorrec·t vector.
Table 21 lists the locations reserved for hardware. You cannot use these locations
as device vector assignments.
Table 21 : Reserved Hardware Locations

228

Address

RSTSIE Usage

0-2

Detection of jumps to 0 and trapEI 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

Offline Options

VECTOR Dialogue
Option: HARDWR

Resl)Onse-Type HARDWR or HA to the INIT.SYS Option: prompt.
HARDWR suboption? VECTOR

Resl)Onse-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 of the card reader.
New vector address?

Explanation-This question asks for the nonstandard vector address for the
controller you specified in the previous question.
Resl)Onse-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 21 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 suboption?

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.
Resl)Onse-Type LIST or LI to list the current hardware configuration table.
Type EXIT or press ~ to return to the Option: prompt.
Mtel' you type EXIT or press I RETURN ~ HARDWR makes the specified changes,
bootstraps your system disk, and prints one of three messages (see the section,
Disalble a Device Controller).

HIARDWIR IRESET-Set All Vector and CSR Addresses to the Standard, and
Enable All Devices
The RESET suboption 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 DM11-BB unit with the DH11 multiplexer that has the same unit number.
Use the RESET suboption only if you have made no changes to your hardware;
that is, you have not assigned any nonstandard CSR or vector addresses.

Offline Options

229

RESET Dialogue
Option: HARDWR

Response-Type HARDWR or HA to the ][NIT.SYS Option: prompt.
HARDWR suboption? 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 EX][T or press l!!.§!Qflli] to return to the
Option: prompt.
HARDWR suboption? RESET

Explanation-Mter LIST prints the current hardware configuration, it returns
to the HARDWR suboption? prompt.
Response-Type RESET or RE.
HARDWR suboption?

Explanation-RESET returns all device characteristics to the standard CSR and
VECTOR addresses. Then it returns to the HARDWR suboption? 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. Mter you list the hardware configuration table, type EXIT or press I RETUFilE]
to return to the Option: prompt.

HARDWR OM-Declare DM11-BB and DH11 Associations
The DM sub option of HARDWR associates each DM11-BB modem controller with
the correct DH11 multiplexer.
Use the DM suboption if the DM11-BB modem controllers are not associated with
the correct DH11 multiplexers.
The DH11 multiplexer allows you to connect from 1 to 16 terminals to your
PDP-11. In other words, the DH11 multiplexer has 16 lines, numbered from 0 to
15.
The DM11-BB modem controller allows you to connect a dial-up telephone to the
DH11 multiplexer. A DM11-BB modem controller also has 16 lines. A one-to-one
relationship exists between these two piec,es of hardware; thus, a PDP-11 can
have only as many DM11-BB modem controllers as there are DH11 multiplexers.
Therefore, a PDP-11 can support a maximum of 16 DH11 multiplexers.
DM11-BB modem controllers and DH11 multiplexers must meet the following
conditions:

230

•

A DM11-BB controller's lines can be connected to modem lines on only
one DH11 multiplexer. For example, you could not connect the DMII-BB
controller lines to DH11 units 0 and 1.

•

A DM11-BB controller's line numbers lnust be the same as the line numbers
of its associated DH11 multiplexer. For example, DM11-BB line number 4 can
be connected only to DH11 line number 4.

Offline Options

The RSTSIE monitor cannot determine which DMII-BB modem controller is
associated with a specific DH11 multiplexer (assuming of course that there is
more than one DH11 multiplexer). Therefore, the RSTSIE monitor assumes
that DM11-BB unit number 0 is associated with DH11 multiplexer unit O. The
RSTS/E monitor does not require that DM11-BB and DH11 unit numbers be the
same. For example, you could connect DM11-BB unit number 2 to DH11 unit
number 4.

[)M Dialogue
Opt ion: HARDWR

Response-Type HARDWR or HA to the INIT.SYS Option: prompt.
HARDWR suboption? DM

Response-Type DM.
DH for DMO (0, NX)?

Explanation-This question asks for the unit number of the DH11 multiplexer
you want to associate with DM11-BB unit O. NX means that the unit is
nonexistent. The DM suboption requests DH11 unit numbers for all 16 possible
DM11-BB units, whether or not the system includes 16 units. Therefore, you can
logically associate a 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 ~ to accept the default.
Or, press CTRL/Z to return to the HARDWR suboption? prompt without declaring
any DM11-BB and DH11 associations.
HARDWR suboption?

Explanation-DM does not immediately assign the unit numbers of any DH11
multiplexers to their associated DM11-BB modem controllers, but returns to the
HARDWR suboption? 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 CUlTent hardware configuration table.
(The hardware configuration table is not repeated here.) Mter you list the
hardware configuration table, type EXIT or press ~ to have DM make the
changes and return to the Option: prompt.

I-IARDWR HERTZ-Specify AC Line Frequency
The HERTZ suboption of HARDWR specifies AC line frequency for your system.
Use the HERTZ subopt.ion only jf you need to specify the correct AC line
frequency for your system.

I-IERTZ Dialogue
Option: HARDWR

Response-Type HARDWR or HA to the INIT.SYS Option: prompt.

Offline Options

231

HARDWR suboption? LIST

Explanation-HARDWR prints the HARDWR suboption? prompt. Before using
HERTZ, always list the current hardware Iconfiguration to see if the AC line
frequency is correct for your installation. (See the section, HARDWR LIST, for an
example of the hardware configuration tabIe.)
Response-Type LIST or LI. Or, type EXIT or press ~ 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 KW11L and KW11P clock, INIT.SYS automatically determines
the frequency of your power.
If you have an 11173, 11/83, or an 11184, Il'UT.SYS also automatically determines
the frequency of your power.
HARDWR suboption?

Explanation-Mter 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 I RETURN I to return to the Option: prompt.

HARDWR SWITCH-Specify CPU Switch Register Characteristics
The SWITCH s'uboption of HARDWR specifies the characteristics of your CPUs
console switch register. The console switch register controls the automatic restart
feature of RSTSIE during system crashes.
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.
Use the SWITCH sub option only if you want to specify the characteristics of your
CPUs console switch register.

232

Offline Options

SWITCH Dialogue
Option: HARDWR

Response-Type HARDWR or HA to the INIT.SYS Option: prompt,
HARDWR suboption? SWITCH

Response-Type SWITCH or SW.
Switch register?

Explanation-Because som.e 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 s~rjtch 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.
Response-Type DISABLE, ENABLE, or VOLATILE:
•

DISABLE means RSTSIE does not look at the switch register. This means
your system, by default, automatically restarts.

•

ENABLE means that when the system crashes, RSTSIE looks at the switch
register after the crash to see if it should restart.

•

VOLATILE has the same meaning as ENABLE except that when power fails,
RSTSIE always tries to restart automatically. The ability to restart a RSTSIE
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 suboption?

Explanation-Mter 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 I RETURN I to return to the Option: prompt.
HARDWR Error Messages

A list of the error messages for the various HARDWR suboptions follows. If your
error message does not appear, see Appendix A.
ADDRESS MUST BE AN EVEN OCTAL NUMBER GREATER THAN 160000.
Suboption: CSR
Explanation: You specified an invalid address.
User Action: Type an address that meets the requirements.
CANNOT DISABLE CONSOLE TERMINAL
Suboption: DISABLE
Explanation: You tried to disable the console terminal.

Offline Options

233

CONTROLLER ALREADY DISABLED
Suboption: DISABLE
Explanation: You t.ried to disahle a disabled controHer.
CONTROLLER NOT DISABLED
Suboption: ENABLE
Explanation: You tried to enable an enabled controller.
CONTROLLER NUMBER MISSING
Suboption: DISABLE, ENABLE:, CSR, VECTOR
Explanation: You did not speci:f:v a controller number for a device that
has multiple controllers.
CONTROLLER NUMBER MUST BE LESS THAN nn
Suboption: DISABLE, ENABLE, CSR, VECTOR
Explanation: The controller nUInber you typed is larger than the
maximum of nn.
DHII ALREADY ASSIGNED TO A DMll .. BB
Suboption: DM
Explanation: The DHII unit Y01ll specified is already assigned to a
DMII-BB.
INVALID CONTROLLER NAME
Suboption: DISABLE, ENABLE, CSR, VECTOR
Explanation: The first two characters you typed did not name a valid
device controller.
User Action: Type? to obtain a list of valid controller names and try
again.
INVALID CONTROLLER NUMBER
Suboption: DISABLE, ENABLE, CSR, VECTOR
Explanation: The controller nutnber you typed is not an integer.
User Action: Type the number in the correct format.
INVALID RESPONSE
Suboption: DM
Explanation: The unit number you specified is not a decimal numbey'
from 0 to 15.
VECTOR MUST BE AN EVEN OCTAL NUMBER LESS THAN 1000.
Suboption: VECTOR
Explanation: You specified an invalid address.
User Action: Type an address that meets the requirements.

234

Offline Options

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 V9.7-11 [Built DD-MMM-YY]
Option:

Explanation-IDENT prints the INIT.SYS version number, then returns to the
Option: prompt.

Offline Options

235

PATCH-Install a Patch
The PATCH option provides a method for altering RS1'SfE 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 RSTS/E Release Notes
if the changes are concurrent with the release of the distribution kits. Between
releases, patches are published in the monthly RSTS IE Software Dispatch. The
following procedures describe the PATCH option in detail. In general, however,
published patches include the necessary instructions.
When you install a new RSTSIE system, refer to the RSTS/E Release Notes and
the RSTS / E Software Dispatch for patches and patching information. Unless
instructed otherwise, you should install all required patches immediately after
installing your RSTSIE monitor.

PATCH Dialogue
Option: PATCH

Response-Type PATCH or PA to the INrr.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, .LIB file, .TSK, or .SAV files.
Response-Type the name and extension of the file that requires patching. OJr,
press I RETURN I to patch the installed monitor SIL.
File found in account [p,pn]

Explanation-PATCH prints this message if it finds the file.
Module name?

Explanation- The module name designates the SIL module to be patched only
if you are patching a monitor.
Response-Type the module name you wnnt to patch.
Base address?

Explanation-The base address defines the actual locations to be patched.
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.
Offset address?

Explanation-The offset address is the first location to be patched relative to
the specified base.

236

Offline Options

Response-Type the offset address of the file you want to patch. See the
previous response for a description of legal values.
Base

Offset

Old

New?

126466

001010

000034

Explanation-Mter 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 22 summarizes the possible responses to this prompt.
Table 22:

Possible Input to the PATCH Option

Input

Meaniug

--------------------.-------------------------------------------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.
Return to the previous location without altering the
contents of the current location.

" (circumflex)

Return to the previous question.
Finish all patching and return to the Option: prompt.

PATCH makes each specified change immediately after you press I RETURN I.
Therefore, if you make an error, you must patch the location again to correct your
mistake.
1b check that an entire patch is correct, type CTRL/Z to return to the Offset
address? question. Type the same offset, then press ~ 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 CTRLlC. 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. 1b 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

Offline Options

237

PATCH Error Messages
A list of the PATCH error messages follows. If your error message does not
appear, see Appendix A.
ADDRESS ABOVE MODULE BOUNDS
Explanation: The address you specified exceeds the upper bound of the
module.
ADDRESS BELOW MODULE BOUNDS
Explanation: The address you specified is below the lower bound of the
module.
BLOCK OFFSET BEYOND EOF
Explanation: The block offset address you typed is greater than or
equal to the number of blocks in the file.
FILE NOT FOUND
Explanation: The initialization code did not find the file you specified
in account [0,1] on the system disk.
ILLEGAL FILE NAME
Explanation: The file name you typed is in an incorrect format. Or,
you pressed I RETURN I and no monitor SIL is installed.
INVALID MODULE NAME
Explanation: The module name you typed is in an incorrect format.
The name must a combination of alphanumeric characters up to 6
characters long.
INVALID CHARACTER
Explan~tion: The expression line contains an illegal character.

INVALID EXPRESSION
Explanation: The expression contains an illegal symbol name or an
invalid operator. Symbol names nlust be a combination of alphanumeric
characters up to 6 characters long:. Valid operators are +, -, *, and t.
INVALID SIL FORMAT
Explanation: The file you specifiied does not contain a valid SIL
directory.
User Action: If the file is not a SIL, append the IN qualifier to the file
name.
MODULE NOT FOUND IN SIL
Explanation: The module you specified is not in the SIL.
User Action: Type a ? in response to the MODULE NAME question for
a directory of SIL modules.
SYMBOL NOT FOUND IN STB
Explanation: A symbol you type:d is not in the symbol table for the
module.
238 Offline Options

IREFRESH-Perform File-Related Tasks
The REFRESH option performs tasks associated 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:
•

REFRESH LIST - List File Status Table

•

REFRESH FILE - Change Account [0,1] File Characteristics

•

REFRESH BADS - Expand the Bad Block File

BEFRESH Error Messages
A list of the REFRESH error messages follows. If your error message does not
appear, see Appendix A.
CANNOT REFRESH THIS DISK

User Action: Rerun DSKINT and then try REFRESH again.
CAl'mOT CHANGE OR MOVE .RTS OR .SIL WITH REFRESH

Explanation: You cannot move or change any files with a .RTS or .SIL
file type.
ILLl~GAL DISK NAME

Explanation: The response you typed is not a valid disk name. Valid
disk names are DK, DL, DM, DP, DR, DB, and DU.
User Action: Press ~ to use the system disk.
ILLEGAL SUBOPTION

Explanation: The response you typed is not a valid suboption name.
SORRY, BUT THAT DISK DOESN'T EXIST

Explanation: The disk device or unit number you specified does not
exist on this PDP-11.
User Action: Use the HARDWR option to list the hardware configuration.
THAT FILE CANNOT BE CHANGED

Explanation: You cannot modify the file.
THAT FILE IS THE CURRENTLY INSTALLED SIL AND CANNOT BE MOVED
OR DELETED

Explanation: You cannot move or delete the installed monitor SIL.
TOO MANY BAD BLOCKS

Explanation: There can be no more than 161 clusters in the bad block
file.

Offline Options

239

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 systenl disk.
This section explains the system files. It groups the files into two sets: those files
that are automatically created during systelm installation, and those optional files
that you can create according to the needs of your installation.

Automatically created during installati.on

•
•
•
•

SWAP.SYS
SWAP1.SYS
BUFF.SYS
CRASH.SYS

Optional
•

SWAPO.SYS

•

SWAP3.SYS

•

OVR.SYS

•

ERR.SYS

Use the INSTALUSWAP_FILE, the INSTALLIERROR_FILE, or the
INSTALL/OVERLAY_FILE commands (see the RSTSIE 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.

240

Offline Options

Table 23 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.
lrable 23:

Summary of System File Creation

-----------------------------------------------------------------------------System File
Status
Location
Size
Automatically Created Files
fIWAP.SYS

INIT.SYS creates this file at
the minimum size. (See Task
2 of Phase 7 in Part 1.)

First available location,
starting from beginning of
disk.

1 job * SWAP MAX* 4

8WAPl.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 1.)

Near SATT.SYS file, usually
center of system disk.

(:# of jobs - 1) *SWAP
MAX * 4

CRASH.SYS

INIT.SYS creates this file.
(See Task 2 of Phase 7 in
Part 1.)

First available location on
system disk.

Sum of low core data
region, XBUF pool,
FIP buffer pool, monitor regions (cannot be
calculated)

Optional Files
SlWAPO.SYS

Optional

Center of nonsystem disk.

:# of highly interactive
jobs * SWAP MAX * 4

SlWAP3.SYS

Optional

Center of nonsystem disk.

:# of event-driven jobs *

OVR.SYS

Optional

Center of nonsystem disk.

Maximum of 128
blocks

E:RR.SYS

Optional

Center of system or nonsystern disk.

Same size as ERR.ERR
(16 blocks)

SWAP MAX * 4

The SWAP.SYS File
Definition-The SWAP.SYS file is one of four available swap files, which stores
jobs transferred out of memory.
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 1.)
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 1).

Offline Options

241

Location-INSTAL.COM places this file as close to the SATI'.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 accommo..
date 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 CRASH.SYS File
De:6nition- 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 Dl0nitor and the extended buffer
pool to be dumped into CRASH.SYS when a system crash occurs. INIT.SYS
automatically creates this file during syste1tn startup. (See Task 2 of Phase 7.)
Location-INIT.8YS 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 RJW areas that the
monitor may access.
Planning the SWAPO.SYS File
De:6nition-The SWAPO.SYS swap file performs the same function as
SWAP1.SYS. The monitor uses this file to Eltore highly 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 dOE~s
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 SWAPl.SYS file would then
not need to exist on your system disk, freeing valuable space and balancing the
1/0 load on your disks.
Size-Estimated # of highly interactive jobs * SWAP MAX * 4
Planning the SWAP3.SYS File
De:6nition-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 iri and out of memory frequ.ently. Examples of event-driven jobs
are QUEMAN, ERRCPY, OPSER, and SPOOL.
Status-The SWAP3.SYS file is an optional system file.
Location-This file is usually located at the center of a nonsystem disk.
242

Offline Options

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 110 load on
your disks.
Size-Estimated # of event-driven jobs * SWAP MAX * 4
Table 24 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.
Table 24:

Swap Times
Job Size (in words)

Disk
16K

28K

32K

64K

RA60

.07

.OS

.11

RA80

.06

.OS

.09

.14

RAS1

.05

.06

.07

.10

RAS2

.05

.06

.09

RC25

.06

.07

.OS

.13

RD31/32

.05

.06

.09

RD51

.14

.17

.19

.29

RD52

.10

.26

.09

.14
.13

.15

RD53

.14

.24

RD54

.09

.13

.14

.24

RK05

.25

.3S

.43

.7S

RKOS/07

.11

.15

.17

.29

RLO:U02

.13

.1S

.19

.32

RM02

.OS

.11

.12

.20

RM03/05/S0

.06

.OS

.09

.14

RP04/05/06

.OS

.11

.12

.20

The swap times for each disk were calculated using the formula:
Swap time = Avg access time + «Job size * 2)lTransfer speed)
whe:re:
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

243

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 the installation procedure tries
to locate your RSTS SIL at the center of the disk, the OVR.SYS file is not usually
useful. Create it only if you are concerned that free space near the center of the
disk is not available 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 128 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 1.
Status-You do not need to create ERR.SYS; it is an optional system file.
Location-Create ERR.SYS on a nonsyste:m 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 12 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.
FORMULA FOR LOCATION:
(STARTING LBN FOR SATT.SYS) -

(X TOTAL BLOCKS)
'"
.t..

244

Offline Options

STARTING LOCATION OF FILES

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 t.otal number of blocks for the system files you want. to create
on that di.sk.

Figure 12:

System File Creation Worksheet

System File

Size (In blocks)

Location

SWAP.SYS
SWAPO.SYS
SWAPl.SYS
SWAP3.SYS
OVR.SYS
ERR.SYS
BUFF.SYS
CRASHSYS

ZK-9241-HC

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

L.IST Dialogue
Option: REFRESH

Response-Type REFRESH or RE to the INIT.SYS Option: prompt.
dd-mmm-yy - hh:mm AM/PM

Disk?

Explanation-REFRESH prints the current date and time, then asks for the
device designator of your disk.
Response-Possible responses for your disk are: DK, DL, DM, DP, DR, DB, or
DU.

Offline Options 245

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 directoriles. 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.
Response-Type LIST or LI.
File
Name

File
Flags

Required?

Status

Current
Size

Minimum
Size

Start
LBN

128

1409

System files:
SWAP
SWAP 0
SWAP 1
SWAP 3
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

4992

4865
85
16

313

1537

Others:
BADB .SYS
SATT .SYS
ERR
.ERR
BACKUP.TSK
INIT .SYS
SYSGEN.SIL
DCL
.RTS
UPDATE.COM
RT11 .RTS
RSX
.RTS
ODT
.SYS
INSTAL.COM
SYSINI.COM
RSTS97.SIL
START . COM
LOGIN . COM
BASIC .RTS

NOD
NOD CTG
NOD CTG
CTG
NOD CTG
CTG
CTG
CTG
CTG
NOD CTG
CTG
CTG
CTG
NOD CTG
CTG
CTG
CTG

REFRESH suboption? ~
Option:

246

Offline Options

20
4
16
100
554
557
128
2
20
6
14
24
3
574
13
4
73

26873
49
165
721
1281
1873
1893
1917
12417
4061
11201

Explanation-LIST prints the file status table, which has seven columns:
•

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.
lbe System File Background section explains how to determine what system
files you need to create.

•

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.

•

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; D/C, which means you must delete and then recreate the file.

•

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.

•

Minimum Size - This column shows the minimum sizes, in blocks, of the
system files.

•

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-Mter LIST prints the file status table, it returns to the REFRESH
suboption? prompt. Type EXIT or press ~ to return to the Option: prompt.

FlEFRESH FILE-Change Account [0,1] File Characteristics
The FILE suboption of REFRESH creates, deletes, or marks as dele table (or
nondeletable) the files that reside in account [0,1].
Use the FILE suboption if:
•

You need to delete obsolete run-time system files (files with file types of RTS).

•

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

Offline Options

247

FILE Dialogue
Option: REFRESH
dd-mmm-yy - hh:mm AM/PM
Disk?
Unit?
Rebuild?
REFRESH suboption? FILE

Explanation-Answer the preliminary R]~FRESH questions. You then see the
REFRESH suboption? prompt.
Response-Type FILE or Fl.
File name?
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 ~. Note that if
you type any other response to this question, REFRESH may reallocate the file
and you will lose the data.
Base?

Response-To retain the current location, type OLD or press I RETURN I. 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 FILEIDELETABLE and
SET FILEINODELETABLE commands to mark files. See the RSTS / E 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 [RE'1'UfU{J to retain the
current status.
1

File name?

REFRESH suboption?

Response-Type another file name or prEISS ~ to return to the REFRESH
suboption? prompt. Press RETURN once :more to return to the Option: prompt.
Or, specify another REFRESH suboption.

248

Offline Options

REFRESH BADS-Expand the Bad Block File
The BADS suboption of REFRESH lists the bad blocks cUlTently in the bad block
file (BADB.SYS) and adds bad blocks to this file.
Use the BADS suboption 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 or RX33
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
Disk?
Unit?
Rebuild?
REFRESH suboption? BADS

Explanation-Answer the preliminary REFRESH questions. You then see the
REFRESH suboption? 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 CUlTent contents of BADB.SYS, type LIST. BADS prints
the contents or a message declaring that there are no bad blocks on the disk.
Bads?

EXI)lanation-BADS returns to the Bads? question.
Response-Type ADD to add bad blocks to BADB.SYS.
Block number?

Response-BADS then asks for the bad block 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 elTor.
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
the pack cluster in which the block resides to BADB.SYS. Use caution, because
the allocation of a cluster to BADB.SYS is ilTevocable.
Type NO if you do not want to add it to this file. If you type NO, BADS repeats
the Block numbers? question.
Bade?

Disk is being rebuilt - wait ..•
REFRESH suboption?

Offline Options

249

Response-Press ~ to exit the BADS suboption. Press IRETURN I 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.

250 Offline Options

~)AVRES·-Restore and Copy Disks
NOTE

Beginning with RSTS/E V9.7, the SAVE option of SAVRES is no longer
supported and you need to use online BACKUP. You can produce a
bootable save set using the RECOVR.COM procedure. See the RSTS / E
System Manager's Guide.
The RESTORE, IMAGE, and IDENTIFY options have been retained for
your convenience.
In the following discussions of the remaining SAVRES options, all
references to SAVE sets and operations apply to pre-V9.7 tapes and
disks.
The SAVRES option is a disk restore and copy utility. SAVRES has three
operational functions:
•

RESTORE - Recreate a like disk from pre-V9.7 tape or disk Save set

•

IMAGE - Make a copy of a disk to a like disk

•

IDENTIFY - Extract label information from a SAVRES volume or RSTSIE
disk.

SAVRES provides a nonselective restore and copy capability that requires
opel'ator responses during the operational dialogue. Unlike the DCL BACKUP
utility, SAVRES processes entire volumes only and does not allow selective file
transfers. You cannot use SAVRES on a disk with a pack cluster size of 32 or 64.
When SAVRES encounters bad blocks, it requires no operator intervention. For
these reasons, use SAVRES when you need to:
•

Create a copy of an entire RSTSIE disk.

•

Make a copy to a disk containing bad blocks that may not be reflected in the
BADB.SYS file.

1b understand 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-six alphanumeric characters used to identify a SAVE set. By
default, the SAVE set name is the same as the pack ID from which it
was created. However, you can specify another name for the SAVE set.

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

Offline Options

251

Nonnally, you use the SAYRES program off line while running INIT.SYS. You
can also use SAVRES on line, during timef3haring. See the RSTS/E System
Manager's Guide for more infonnation about running SAVRES on line.
NOTI:

You must run SAVRES offline to copy (IMAGE) or restore (RESTORE)
the system disk with which you are cUlTently 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 tenninaJ during an operation to tell you
its status. Some messages are for infonnation only; other messages are elTor
conditions that may require your attention during the dialogue, mount, transfer,
or verification phases of SAVRES.
When the program encounters an elTor dwing a dialogue or mount operation, it
asks you to COlTect the problem and to retype the appropriate command. Such
elTors never affect the integrity of the data. being transferred.
ElTors 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 infonnation
to help you protect your data by printing infonnational messages and error
messages on your tenninal. When SAVREB completes a RESTORE or IMAGE
operation, it prints an optional swnmary r(~port. This report describes:
•

The operation perfonned

•

Device infonnation

•

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 infonnation about it,
see the RSTS / E System Manager's Guide.

252

Offline Options

RESTORE-Recreate a Disk From Tape or Disk
The RESTORE function recreates a RSTSIE file-structured disk from a pre-V9.7
SAVE set. Because SAVRES writes the SAVE set in the SAVE format, no other
RSTSIE software can perform this rebuild process. Before transferring any data,
SAVRES tries to extract bad block information from the destination disk and, ifit
finds any bad blocks, incorporates them into the new BADB.SYS file.
NOTE

When using RESTORE, you must ensure that the disks from which
the data came and that. which you are restoring to are like disks as
described for SAVRES.
The SAVRES program may encounter bad blocks during a RESTORE operation.
Ifit does, it scans the SATT.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. 'lb 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:
•

No unallocated pack cluster remains on the disk.

•

The file cluster size is larger than the pack cluster size and there is not an
equivalent nwnber of contiguous pack clusters left on the disk.

When SAVRES creates a SAVE set, it includes on the output volwne 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 volwne.
Thus, you will notice a discrepancy between the nwnber of blocks transferred for
a SAVE operation and the nwnber 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 volwne than
existed in the SAVE set.
The following example illustrates the restoration of an RM03 disk from a tape
SAVE set named SAVSET. The two SAVE set volwnes are mounted on drives
MMl: and MM2:, write-locked. The destination disk is mounted on drive DR1:,
write-enabled.

Offline Options

253

RESTORE Dialogue
Option: SAVRES

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, RESTOR~~ 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 thc~ input medium is tape mounted on
drive 1.

*** SAVE Set Name/default Pack ID 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 ID of the output volume. If you want to use a different pack ID, you can
include a new pack ID 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 R:M03 disk.
NOTE

You cannot use SAVRES on a disk with a pack cluster size of 32 or 64.
If you attempt to use SAVRES on a disk with these cluster sizes, the
following messages will appear:
SAVRES cannot be used with disks ·:>f cluster size greater than 16.
Dismount Device:
Set Name:
Seq .f:
Creation date:
Expiration date:

MM1:
SAVSET
1

Friday, 13-Jun-89
Sunday, 1-0ct·-89

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
DR1:TSTPAK because it is recreating an RM03 disk mounted on drive 1. The
new pack ID is TSTPAK.
Note-If the message "Performing limited hardware scan." was printed during
this boot and you try to initialize or copy to a nonexistent disk, then you will
receive the following error messages:
That disk was not found during limited hardware scan.
Do you wish to perform a reboot with full hardware scan <YES>?

Response-If the user answers YES, then the distribution device will be rebooted
and the "Performing limited hardware scan." message will NOT reappear.

254

Offline Options

*** 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 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 MYPAK,
and that RESTORE will reinitialize it. RESTORE 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 I RETURN I
to cancel the instruction. RESTORE then returns to the '1b 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>?

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 ~ 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 SAVIRES Function: prompt. In the example, the response is Y.
*** Begin RESTORE from MM1: to DR1: at 08:28 PM
Dismount Device:
Set Name:
Seq :11::
Density:

MlM1:
SAVSET
1
800

Creation date:

Friday, 13-Jun-89

Expiration date:

Sunday, 1-0ct-89

Mount volume :II: 2 of SAVE Set SAVSET
Device? MM2:
Proceed (Yes or No)? Y

*** Begin RESTORE from MM2: to DR1: at 08:32 PM
Dismount Device:
Set Name:

MM2:
SAVSET

Seq :11::

Density:

800

Creation date:

Friday, 13-Jun-89

Expiration date:

Sunday, 1-0ct-89

Dismount Device:

DR1:

Offline Options

255

Pack ID:
Pack Clustersize:
Creation date:

TSTPAK
8

Friday, 13-Jun-89

Please label this volume!
RESTORE operation completed at 08 ::37 PM

Explanation-RESTORE displays a message to indicate it has begun the
transfer. If the transfer involves multiple volwnes, RESTORE transfers the
first volwne, prints input medium information and prompts you for the next
volume. Mter you mount the next volwne, 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 volwne. When RESTORE finishes
the final volwne, 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 nwnber of the drive on which the next volwne is
mounted. Type Y to the Proceed? prompt when you are ready to continue.
In the example, volwne 2 of SAVE set SAVSET is mounted on tape drive MM2:.
Volwne two is the final volume in the SAV1~ set.
Summary Report
RESTORE of SAVE Set SAVSET to DR1:TSTPAK
Input Device:
Set Name:

-# of volumes:
Density:

Magtape
SAVSET
2
800

Creation date:

Friday, 13-Jun-89

Expiration date:

Sunday, 1-0ct-'89

Output Device:
Pack ID:
Pack Clustersize:
Creation date:

DR1:
TSTPAK
8
Friday, 13-Jun-89

RESTORE started on Friday, 13-Jun-89, at 08:28 PM

Explanation-The Summary Report prints the SAVE set name, the pack ID,
and label information for both the input and output medium, in addition to the
date and time of the RESTORE operation.

256

Offline Options

Run Statistics
Transfer Totals:
Total of 54184 blocks transferred
Error Totals:
Total of

o new bad blocks encountered on destination.

o files structurally altered.
Timing Totals:
9 mins.,

36 sees.

time:

o hrs.,
o hrs.,

o mins.,

16 sees.

Total process time:

o hrs.,

9 mins.,

20 sees.

Total elapsed time:
Total wait

SAV/RES Function: ~
Option:

Explanation-The Run Statistics Report prints the number of blocks transfelTed, 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 ~ or CTRUZ to return to the INIT.SYS Option: prompt.
NOTE

IIDENTIFY--Extract Label Information
The IDENTIFY function obtains label information from a SAVE set volume or a
RSTSIE file-structured disk.
The following example lists the label characteristics of both a SAVE set and a
RSTSIE disk. The SAVE set volume is mounted on drive MM1:, write-locked. The
RSTSIE disk is mounted on drive DR1:, write-locked.

IIDENTIFY 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 MM1:.

Offline Options

257

From device? MM1:

Explanation-IDENTIFY prints the Front 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 lVIM1:, because the input medium is
tape, mounted on drive number 1.
Device:

MM1:

Set Name:

SAVSET

Seq #:

Density:

1600

Creation date:

Friday, 13-Jun-89

Expiration date:

Sunday, 1-0ct·-89

Explanation-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.
If you do not need to identify any more media, press [~ to return to the
INIT.8YS Option: prompt.
In the example, the response is IDENTIFY DR1:. This requests SAVRES to
identify the disk pack mounted on DR1:.
Device:

DR1:

Pack 10:

TSTPAK

Pack Clustersize:
Creation date:
SAV/RES Function:

Friday, 13'-Jun-89

Option:

Explanation-IDENTIFY prints the label information of the disk pack mounted
on DR1:. IDENTIFY returns to the SAVIRES Function: prompt when the
operation has ended.
Response-If you do not need to identify any more media, press ~ or
CTRL/Z to return to the INIT.SYS Option: prompt.

258

Offline Options

IMAGE .. Make a Copy of a Disk
The IMAGE function makes an equivalent copy of a RSTSIE 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 HARDWR suboptions (such as changing
Hertz) because the IMAGE option clears various items set up by the
HARDWR suboptions. This procedure is necessary because a disk can
be saved with IMAGE from one system disk and carried to 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 DBO:, write-locked. The destination disk is mounted on drive
DB1:, write-enabled.

IIMAGE Dialogue
Opti.on: SAVRES

Response-Type SAVRES to the INIT.SYS Option: prompt.
SAV/RES Function: lMAGE/NOERROR

Explanation-SAVRES asks for the particular function you want to use.
Response-Type IMAGE to begin the IMAGE operation. The INOERROR
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.
From RSTS disk? DBO:

Explanation-IMAGE prints the From RSTS disk? question. Specify the disk
from which you want to copy the data. If you include a pack ID in the device
specification, SAVRES checks to see if it matches the actual pack ID on the disk.
If the pack IDs do not match, SAVRES issues a warning message and prints the
From RSTS Disk? question again.
NOTE

You cannot use SAVRES on a disk with a pack cluster size of 32 or 64.
If you attempt to use SAVRESon a disk with these cluster sizes, the
following messages will appear:
SAVRES cannot be used with disks of cluster size greater than 16.
Dismount Device:
Set Name:
Seq #:
Creation date:
Expiration date:

MMl:
SAVSET
1
Friday, 13-Jun-89
Sunday, 1-Oct-89

Offline Options

259

Response-Type the device name and unit number of the disk you want to copy.
In the example, the response is DBO: because the source disk is mounted on drive
DBO:.
*** Input Pack IO/default Output Pack IO is SOURCE

Explanation-IMAGE reads the pack ID from the input disk and displays it on
your terminal.
To RSTS DB: Disk? OB1: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 nmnber, and pack ID of your output
disk (if you want to change the pack ID narne). In the example, the response is
DB1:NICOLA because it is copying to an RP04 disk mounted on drive 1. The new
pack ID is NICOLA.
*** The volume on OB1: is a RSTS disk
*** Pack IO is OUTPUT
*** Pack will be reinitialized
Mount it anyway <NO>? Y

*** Output Pack IO 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
IMAGE then returns to the 1b RSTS DB: Disk?
question. In the example, the response is Y because the data on the disk is no
longer valuable. IMAGE then initializes th,e disk and prints a message showing
the new pack ID.

~ to cancel the instruction.

Verify (Yes or No) <NO>? Y

Explanation-IMAGE asks if you want to verify the accuracy of the data
transfer. When IMAGE verifies the transfelrred 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 I RETURN I to skip the verify pass. Or, type Y to perfonn
the data verification. In the example, the response is Y.
Proceed (Yes or No)? Y

Explanation-IMAGE asks if you are ready to proceed.
Response-Type Y to proceed. Or, type N to cancel the operation and return to
the SAVIRES Function: prompt. In the example, the response is Y.

260

Offline Options

Begin IMAGE copy from DBO: to DB1: at 11:02 AM
Begin VERIFY pass from DBO: to DB1: at 11:04 AM

o differences found
Dismount Device:
Set Name:
Pack clustersize:
Creation date:

DB1:
NICOLA
8

Friday, 13-Jun-89

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. Mter 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.
Summary Report
IMAGE copy of DBO:SOURCE to DB1:NICOLA
Input Device:
Set Name:
Pack clustersize:

DBO:
SOURCE
8

Creation date:

Friday, 13-Jun-89

Output Device:

DB1:

Pack 10:
Pack Clustersize:
Creation date:

NICOLA
8
Friday, 13-Jun-89

RESTORE started on Friday,. 13-Jun-89, at 11 :02 AM

Explanation-IMAGE prints the Summary Report unless you suppress it
by using the INOSTATS switch. The report includes the pack ID and label
information of each disk, in addition to the date and time that the IMAGE
operation was run.

Offline Options

261

Run Statistics
Transfer Totals:
Total of 24400 blocks transferred
Error Totals:
Total of
Total of
Total of

o bad compares.
o new bad blocks enoountered on source.
o new bad blocks enoountered on destination.

o files structurally altered.
Timing Totals:
Total elapsed time:

o hrs.,

5 mins.,

22 sees.

Total wait

time:

o hrs.,

o mins.,

0 sees.

Total process time:

o hrs.,

5 mins.,

22 sees.

SAV/RES Function:

Option:

Explanation-The Run Statistics Report prints the nwnber 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 ~ or CTRUZ to return to the INIT.SYS Option: prompt.
Refer to the RSTS / E System Manager's Guide for a description of SAVRES error
messages.

262

Offline Options

~)TART-Start a RSTS/E Monitor

The START option activates a RSTSIE 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:
pronlpt.
If you do not specify a monitor name or press ~ to the Option: prompt,
START starts the monitor that was used in the previous timesharing session.
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:
Starting 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.
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 enough contiguous disk space to create minimum SWAP.SYS file

Press ~ to accept the default value, indicated by xx in the example. Or type
CTRLlC 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.

Offline Options

263

Any memory allocation changes?

Explanation-START asks if you want to make changes to the memory
allocation table for this timesharing session. You can be forced to make memory
al1ocntion changes.
Response-Type YES to make changes to the memory allocation table. (See
the section, DEFAULT Option.) Type NO or press ~ 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 RS1'SIE 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 enough contiguous disk space to create minimum CRASH.SYS file
Crash dump automatically disabled

When a crash occurs, the RSTSIE 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. In general, SPRs
submitted on system crashes without crash dumps will be answered by DIGITAL
as "Insufficient information."
Therefore, if you see the Crash dump automatically disabled message, follow
these steps to enable crash dump:
1. Mter you begin timesharing, delete wilnecessary files to create more
contiguous disk space. Or, move some files to a nonsystem disk.
2. Shut down the RSTSIE monitor using the SHUTUP program.
3. 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:
•

Verify that all configured hardware exists and that it responds properly.

•

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.

•

Enable all configured terminal controllers and disable any that do not
respond.

•

Set up monitor, cache, and device tables.

•

Load the installed monitor into memOl~.

START then transfers control to the SYSINI.COM command file, which executes
the START.COM command file. See the R'STS / E System Manager's Guide for
details about START. COM.
Refer to Appendix A for the description of START error messages.

264

Offline Options

Part 6
Appendixes

Appendix A

System Installation Error Messages

Initialization Code Error Messages
ThE~ RSTSIE 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 RSTSIE 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 listed below. 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.
ACCOUNT [1,2] MISSING FROM OUTPUT DISK

User Action: Reinitialize the disk as a system disk and create the
library account.
BAD [0,1] DIRECTORY

User Action: Reboot the system disk and retry the operation. If the
retry fails, use DSKINT to reinitialize the disk.
BADB.SYS NOT FOUND - RESULTS UNPREDICTABLE

User Action: 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

Explanation: Warning message only.
User Action: Shut down the system and use REFRESH to create the
file at the required size.
CANNOT REFRESH THIS DISK

User Action: Reinitialize the disk.
CAN'T RESET MEMORY TABLE - NOT ENOUGH ROOM

User Action: Regenerate a smaller monitor to reduce the number of
small buffers selected.

CANNOT START WITH THIS SWAP MAX AND MEMORY TABLE
User Action: Use DEFAULT to change the SWAP MAX and/or memory
allocation table.
CLUSTER 1 (REQUIRED FOR PACK LABEL) CONTAINS A BAD BLOCK
User Action: 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
User Action: REBUILD asks whether to delete the file, then confirms
your response.
[P,PN] CLUSTER MAP IN UFD DISAGRE:ES WITH MFD
User Action: REBUILD asks whether to zero the account and confirms
your response.
[P,PN] CLUSTER SIZE IS INCORRECT
User Action: REBUILD asks whether to delete the account and
confirms your response.
DEFAULTS CORRUPTED. RESETTING DEFAULTS ...
Explanation: INIT found some defaults to be invalid. It will pick new
values to be used.
DEFAULTS CANNOT BE SET - NOT A VALID SYSTEM DISK
User Action: Use the COpy option to copy the files from the distribution device to this disk.
DEVICE xx: DOES NOT INTERRUPT - DEVICE DISABLED
Explanation: The device may be broken or configured incorrectly.
User Action: Call your DIGITAL Field Service engineer. If the disk is
an RC25 or a TUB1, a cable may be disconnected.
DEVICE CONTROLLER TABLE (DDCTBL) DECLARES TOO MANY UNITS
FOR CONTROLLER
SIL CANNOT BE INSTALLED
User Action: Submit an SPR with a copy of the SIL and INIT.SYS.
DEVICE CONTROLLER TABLE (DDCTBL) HAS AN ILLEGAL FORMAT
SIL CANNOT BE INSTALLED
User Action: 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
User Action: Make sure that the device is on line and ready. If the
error recurs, try a different device.
DEVICE HUNG OR WRITE-LOCKED
User Action: Make sure that the device is on line and ready. If the
error recurs, try a different device.
268

System Installation Error Messages

DEVICE XDn: CSR MUST BE DECLARED WITH HARDWR, CSR SUB-OPTION
- DEVICE DISABLED
Explanation: The XD device is not located at a DIGITAL standard CSR
assignment.
User Action: Use the CSR suboption of HARDWR to set the correct
CSR address for XDn:.
DEVICE XDn: INTERNAL MICRO-DIAGNOSTIC FAILURE - DEVICE
DISABLED
Explanation: The error message indicates that INIT encountered a
device micro-diagnostic error.
User Action: Call your DIGITAL Field Service engineer.
DEVICE XEn: MICRO-DIAGNOSTIC FAILURE, CODE nnn
DEVICE XHn: MICRO-DIAGNOSTIC FAILURE, CODE nnnnnn
Explanation: These failures indicate that the specified device failed
the micro-diagnostic test with the failure code shown. In most cases,
the device should be checked by your field service representative. Some
of the failure codes are interpreted by INIT. These codes display the
additional message:
Device not connected to transceiver
DEVICE VHn: INTERNAL MICRO-DIAGNOSTIC FAILURE, CODE xxxx DEVICE DISABLED
Explanation: The error message indicates that INIT encountered a
device micro-diagnostic error.
User Action: Call your DIGITAL Field Service Engineer.
DIRECTORY ENTRY FOR [.p,PN] filnam.typ CONTAINS PACK CLUSTER
NUMBER WHICH IS TOO BIG
User Action: REBUILD asks whether to delete the file and confirms
your response.
DIRECTORY ERROR DETECTED IN RDB
User Action: Reinitialize the disk.
DIRECTORY ERROR - FILE NOT FOUND
User Action: ReiniLtialize the disk.
DIRECTORY ERROR - [0,1] NOT FOUND
User Action: ReiniLtialize the disk~
[0,1] DIRECTORY NOT FOUND
User Action: Reinitialize the disk.
DISK BLOCK 0 (REQUIRED FOR BOOTSTRAPS) IS BAD
User Action: Reinitialize the disk. If the error recurs, use a different
disk.

System Installation Error Messages

269

DISK ERROR DURING DSKINT BUILD PHASE

User Action: Reinitialize the disk. If the en'or recurs, use a different
disk.
DISK HUNG OR DATA ERROR DURING OVERLAY

User Action: Make sure that the device is on line and ready. If the
error recurs, try a different device.
DISK STRUCTURE CANNOT BE REBUIL'T

User Action: 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

User Action: REBUILD lets you choose the file to delete, then confirms
your response.
?DRIVE NOT READY:

User Action: 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

User Action: Submit an SPR anol a copy of INIT.SYS and console
output.
DSKINT OR SYSGEN ERROR - DSKINT i\LLOCATION FAILURE

User Action: Submit an SPR and a copy of INIT.SYS and console
output.
EOF READING INIT.SYS

User Action: Submit an SPR and a copy of INIT.SYS and console
output.
ERR FILE INVALID

User Action: Copy the file ERR.ERR from the distribution mediwn to
the system disk.
ERR FILE NOT FOUND

User Action: Copy the file ERR.ERR from the distribution mediwn to
the system disk.
ERROR FILE HAS AN INVALID FILE FOHMAT

Explanation: The error message :file you specified is not exactly sixteen
blocks long.
User Action: Make sure you copied from the correct RSTSIE
Distribution Kit.
ERROR DETECTED WHILE READING EltROR RECORD SECTOR #n

Explanation: Warning message only. Error occurred during reading of
factory error records.
User Action: Disregard the error message.

270

System Installation Error Messages

ERROR-NO SETUP FOR DISK xx:

User Action: Regenerate your monitor. If the problem recurs, submit
an SPR, your monitor .SIL file, and a copy of INIT.SYS and console
output.
ERROR-UNKNOWN DISK xx::

User Action: Regenerate your monitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your .SIL file, and console output.
EXCltJSSIVE BAD CLUSTERS

User Action: If you need to use the current disk, use DSKINT to
increase the pack clu.ster size. If the error recurs, use a different disk.
FATAL DISK ERROR DURING CONTROL RESET

User Action: Retry the DSKINT. If the error recurs, call the DIGITAL
field service engineer to repair the disk drive.
FATAL ERROR - NO SMALL BUFFERS LEFT

User Action: Regenerate the system and configure more small buffers
or use the Default Buffers sub-option to increase the number of small
buffers available.
FATAL - ETHERNET PHASE EXCEEDS AN APR SIZE

User Action: Submit an SPR and include a copy of your monitor .SIL
file.
FATAL - FIP PHASE EXCEEDS AN APR PHASE

User Action: Submit an SPR and include a copy of your monitor .SIL
file.
FATAL 1/0 DURING OVERLAY

User Action: Make sure that the device is on line and ready. If the
error recurs, try a different device.
FILE NOT CONTIGUOUS

Explanation: The file you specified is not contiguous on disk. The error
message file must be contiguous.
FILE NOT FOUND

Explanation: The initialization code did not find the file you specified
on disk.
xxx FILE NOT FOUND WHEN REMOVING IT

Explanation: Warning message only. xxx is SIL or ERR. The initialization code did not find a file when trying to make it deletable.
[P,PN] filnam.typ HAS A BAD BLOCK

User Action: REBUILD asks whether to delete the file and confinns
your response.

System Installation Error Messages

271

[P,PN] filnam.typ HAS FIRST DCN OUT OF RANGE
User Action: REBUILD asks whether to zero the account and confirms
your response.
[P,PN] filnam.typ HAS INVALID ACCOUl'lTING ENTRY LINK
User Action: REBUILD asks whether to delete the file and confirms
your response.
filnam.typ HAS INVALID FORMAT AND CANNOT BE COPIED
User Action: Submit an SPR induding a copy of INIT.SYS, CONFIG.SYS,
and your monitor .SIL file if DIGITAL supplied the file on the distribution medium. Regenerate your system monitor if the system installation
process created the file.
FORMATTING FAILURE
Explanation: This error may indicate a bad disk pack or a bad disk
drive.
User Action: 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.
GETCFG IS MISPLACED
User Action: Submit an SPR and include a copy of INIT.SYS,
CONFIG.SYS, and your monitor .SIL file.
[P,PN] HAS A BAD BLOCK
User Action: REBUILD asks whether to delete the account and confirms your response.
[P,PN] HAS CLUSTER NUMBER IN MAP WHICH IS TOO BIG
User Action: REBUILD asks whether to delete the account and confirms your response.
[P,PN] HAS HOLES IN CLUSTER MAP
User Action: REBUILD asks whether to zero the account and confinns
your response.
[P,PN] HAS INCONSISTENT CLUSTER MAPS
User Action: REBUILD asks whether to zero the account and confinns
your response.
[P,PN] HAS INVALID CLUSTER SIZE
User Action: REBUILD asks whether to delete the account and confirms your response.
ILLEGAL FILE NAME
Explanation: The file name you specified is not one to six alphanumeric
characters.
User Action: Specify the correct file name.

272

System Installation Error Messages

INIT BUG - BAD DISK INDEX
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - CAN'T ALLOCATE FILE 2ND TIME
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - CAN'T CHECK PARITY
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - CAN'T FIND [0,.1] AGAIN
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - CAN'T FIND FILE TO DELETE
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - DIDN'T GET SAME CLUSTER 2ND TIME
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - DIDN'T GET SAME FILE CLUSTER 2ND TIME
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - FAILED TO CREATE FILE
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - FAILED TO FIND FILE AGAIN
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - FAILED TO FIND FILE JUST CREATED
User Action: Subnlit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - FILE EXISTS WHEN TRYING TO CREATE
User Action: Subnlit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - xxx - FILE NOT FOUND 2ND TIME
User Action: Subnlit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - xxx - FILE NOT FOUND WHEN REMOVING IT
User Action: Submit an SPR and a copy of INIT.SYS and console
output.

System Installation Error Messages

273

INIT BUG - FILE SIZE COMPUTED WRONG
User Action: 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 and console output.
INIT BUG - FLOAT TABLE ERROR
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - INSTALL NOT SYNCHRONIZED at xxxxxx
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - MONITOR LAYOUT SCREWl~D UP
User Action: Submit an SPR and include a copy of your monitor .SIL
file.
INIT BUG - NO SATT.SYS AT WIPEOUT TIME
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - NO UFD FOUND IN CREATI~
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - REBUILD FAILED TO FIND ALLOCATION ERROR
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - RNB TO WRONG DISK
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - SATT.SYS NONEXISTENT Kr TIME OF WOMP
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - SETNEW TABLE TOO SMALL
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - START LINKED TOO LOW
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT BUG - UNKNOWN BA DEVICE
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT LINK BUG - DEFBUF NOT ALIGNED
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
274

System Installation Error Messages

INIT LINK BUG - DSTBL TOO LOW
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT LINK BUG - FIBUF NOT ALIGNED
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT LINK BUG - INSBUF NOT ALIGNED
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT LINK BUG - SATBUF NOT ALIGNED
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
INIT.SYS NOT FOUND - RESULTS ARE UNPREDICTABLE
User Action: Reboot the system disk and retry the operation. If the
retry fails, reini tialize the disk.
INPUT FILE MISSING FROM SYSTEM DEVICE
User Action: Retry the procedure that generated the error. If the error
recurs, submit an SPR and a copy of INIT.SYS and console output.
INSTALLED MONITOR DOES NOT SUPPORT THIS SYSTEM DISK
User Action: 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
Explanation: The installed SIL is invalid as a monitor SIL.
User Action: Use the START option to install a valid SIL.
INVALID DATA IN ERROR RECORD SECTOR #n
Explanation: Warning message only. The error occurred during reading of factory error records.
User Action: Disregard the error message.
INVALID GROUP [255,*] FOUND IN MFD - ENTRY DELETED
Explanation: Informational message only.
INVALID RETRIEVAL ENTRIES FOR FILE [p,pn] filnam.typ - FIXED
Explanation: Warning message. REBUILD truncates the file.
INVALID SIL FORMAT - INIT AND MONITOR ARE DIFFERENT VERSIONS
User Action: Start a SIL that has the correct RSTSIE version number.
INVALID SIL FORMAT - MONITOR IS MISSING REQUIRED MODULES
User Action: Regenerate your monitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your monitor .SIL file, and console
output.

System Installation Error Messages

275

I/O TO UNOPENED FILE
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
[P,PN] IS NOT A VALID ACCOUNT NUMBER
User Action: REBUILD asks whether to delete the account and con~
firms your response.
LABEL ID FIELDS FOR [p,pn] FIXED
Explanation: Warning message only.
LINK TO NAME BLOCK FOR [p,pn] IS BAD
User Action: Delete the account.
MAGTAPE ERROR OR INVALID FORMAT ON TAPE
User Action: Make sure that the tape drive heads are clean and
correctly aligned. If the error recUTS, try using a different drive.
MEMORY ADDRESSING PROBLEM
Explanation: Either the memory subsystem or the memory manage··
ment hardware failed.
MFD NAME ENTRY CONTAINS A BAD LINK. ALL [1,1] FILES AND
ACCOUNTS BEYOND [p,pn] filnam.typ WILL BE DELETED
User Action: REBUILD confirms your response.
MONITOR SIL CHANGED - REINSTALL IT
User Action: Use the START option to install the monitor SIL.
MONITOR SIL NOT FOUND
User Action: Use the START option again to install the SIL. If the
error recurs, submit an SPR and a copy of INIT.SYS and console output.
MODULE xxxxxx HAS INVALID LENGTH
User Action: Regenerate your trtonitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your monitor .SIL file, and console
output.
MODULE xxxxxx HAS INVALID TRANSF'ER ADDRESS
User Action: Regenerate your :monitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your monitor .SIL file, and console
output.
MODULE xxxxxx HAS WRONG LOAD ADDRESS
User Action: Regenerate your 1l1Lonitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your monitor .SIL file, and console
output.
MODULE xxxxxx IS AN UNKNOWN NOr~-GENERIC PHASE
User Action: Regenerate your mlonitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your monitor .SIL file, and console
output.
276

System Installation Error Messages

MODULE xxxxxx IS MISSING A REQUIRED SYMBOL
User Action: Regenerate your monitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your monitor .SIL file, and console
output.
MODULE xxxxxx IS NOT ALIGNED ON A BLOCK BOUNDARY
User Action: Regenerate your monitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your monitor .SIL file, and console
output.
MODULE xxxxxx NOT FOUND IN SIL
User Action: Regenerate your monitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your monitor .SIL file, and console
output.
MODULE xxxxxx TOO LARGE
User Action: Regenerate your monitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your monitor .SIL file, and console
output.
MODULE xxxxxx TOO SMALL
User Action: Regenerate your monitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your monitor .SIL file, and console
output.
MODULE xxxxxx TOTALLY MAPPED PORTION TOO LARGE
User Action: Regenerate your monitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your monitor .SIL file, and console
output.
MUx: CONTROLLER TYPE IS UNSUPPORTED BY RSTSIE - DEVICE
DISABLED
Explanation: During initialization, a controller identified itself as a
type that RSTSIE does not support.
MUx: DOES NOT RES:eOND TO DISK OR TAPE CONNECTS - DEVICE
DISABLED
Explanation: The controller has identified itself as one that supports
MSCP disks or TMSCP tapes, and yet does not respond correctly when
we attempt to bring the disks or tapes online.
MUx: INTERNAL MICRO-DIAGNOSTIC FAILURE, CODE NNNNNN - DEVICE
DISABLED
Explanation: The controller has failed its self-diagnostic tests and
is not usable by RSTSIE. The code "nnnnnn" is an octal number that
describes the cause of the failure.
MUn: IS MISSING THE FOLLOWING FCO: TQK50-IOOl (EQ-1442-01)
Explanation: This message indicates that your TQK50 tape drive
requires a hardware update in order to properly work under timesharing.
User Action: Have your field service representative upgrade your
TQK50 to the latest revision level.
System Installation Error Messages

277

MUx: TIMEOUT DURING INITIALIZATION, STEP nnnnnn - DEVICE
DISABLED
:Explanation: The controller did not complete its self-diagnostic tests
within the required time period. The step number "nnnnnn" is for
DIGITAL Field Service use.
MUx: TIMEOUT DURING TAPE SCC - DEVICE DISABLED
Explanation: The controller did not complete a Set Controller
Characteristics command within the required time period. The message that appears depends on the type of controller (MSCP disk or
TMSCP tape).
[P,PN] NAME BLOCK SPECIFIES WRONG PPN
User Action: Delete the account.,
NO LIBRARY ACCOUNT ON THIS DISK
User Action: Reinitialize the disk and create a library account, or
create account [1,2] on the disk.
NO ROOM FOR DIRECTORY ON OUTPUT DISK
User Action: 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.
User Action: Delete files, reinitialize the disk to create sufficient
contiguous space on the disk for the new file? or use a different disk.
??? NO VALID V9.X MONITOR FILES IN [0,1]

User Action: Copy the required SIL to the system disk from the installation media.
NOT ENOUGH MEMORY FOR REQUIRE:D XBUF!
User Action: Regenerate a smaHer monitor and reduce the nwnber of
small buffers selected.
NOT ENOUGH ROOM IN LOW MEMORY FOR MONITOR
Explanation: INIT cannot find enough contiguous, physical memory to
place the monitor in low memory. Before printing this message, INIT
attempts to position the monitor lin 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 ROO~1:" message and returns to the Option:
prompt.
User Action: You can then begin. to generate a smaller monitor.
ONE OR MORE SYSTEM FILES MISSING
User Action: Use the COpy option to copy the files from the distribution media to [0,1] on this disk.
OPrION ATTEMPTED DURING BOOTSTRAP PHASE
User Action: Reboot the system and retry the operation. If the retry
fails, submit an SPR and a copy of INIT.SYS and console output.

278

System Installation Error Messages

OPTION NOT AVAILABLE

Explanation: The option you requested is not available until you
bootstrap the system disk.
OU'I'pUT DISK IS NOT A SYSTEM DISK

User Action: Reinitialize the disk as a system disk.
OVERLAY HANDLER IN ERROR

User Action: Submit an SPR and a copy of INIT.SYS and console
output.
OVR NOT IN SIL

User Action: Regenerate the monitor.
PACK CLUSTER SIZE IS NOT 1, 2, 4, 8, 16, 32, OR 64

User Action: Reinitialize the disk.
PARITY CSR FOUND, BUT NOT RELATING TO MEMORY

User Action: Call your DIGITAL Field Service engineer.
PARITY CSR CONTROLS MORE THAN 31K

User Action: Call your DIGITAL Field Service engineer.
PRIORITY OF xx: INTERRUPT (PRn) IS TOO HIGH - DEVICE DISABLED

User Action: Call the DIGITAL field service engineer to install the
device correctly.
QUE:STION ATTEMPTED DURING AUTO-RESTART

User Action: 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 and a copy of INIT.SYS and
console output.
REQUESTED DISK DRIVE NOT FOUND

User Action: Request a disk that is on the system.
REQUIRED SYMBOL xxxxx.'!( MISSING FROM MONITOR

User Action: Regenerate your monitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS, your monitor .SIL file, and console
output.
RLV DISK MUST BE STRAPPED FOR 22-BIT ADDRESSING

Explanation: 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.
RSTSIE REQUIRES AT LEAST 124K WORDS OF MEMORY

Explanation: Your configuration is too small to run RSTSIE.

System Installation Error Messages

279

RSTSIE REQUIRES EIS!
User Action: Correct the hardware configuration to include EIS instructions.
RSTSIE REQUIRES A CLOCK!
User Action: Correct the hardware configuration to include a KW11P
or KW11L clock.
RSTSIE REQUIRES MEMORY MANAGEMENT HARDWARE!
User Action: Correct the hardware configuration to include a memory
management unit.
RUx: CONTROLLER TYPE IS UNSUPPORTED BY RSTSIE - DEVICE
DISABLED
Explanation: During initialization, a controller identified itself as a
type that RSTSIE does not support.
RUx: DOES NOT RESPOND TO DISK OR TAPE CONNECTS - DEVICE
DISABLED
Explanation: The controller has identified itself as one that supports
MSCP disks or TMSCP tapes, and yet does not respond correctly when
we attempt to bring the disks or tapes online.
RUx: INTERNAL MICRO-DIAGNOSTIC FAILURE, CODE nnnnnn - DEVICE
DISABLED
Explanation: The controller has failed its self-diagnostic tests and
is not usable by RSTSIE. The code "nnnnnn is an octal number that
describes the cause of the failure.
il

RUx: TIMEOUT DURING INITIALIZATION, STEP nnnnnn - DEVICE
DISABLED
Explanation: The controller did not complete its self-diagnostic test
within the required time period. The step number "nnnnnn" is for
DIGITAL Field Service use.
RUx: TIMEOUT DURING TAPE SCC - D:EVICE DISABLED
Explanation: The controller did. not complete a Set Controller
Characteristics command within the required time period. The message that appears depends on the type of controller (MSCP disk or
TMSCP tape).
[0,1] SATT.SYS IS NOT CONTIGUOUS
User Action: Reinitialize the diElk.
SATT.SYS IS OVER 16 BLOCKS LONG
User Action: If the file structure on the disk is sound, submit an SPR
and the disk. Otherwise, reinitiaHze the disk.
[0,1] SATT.SYS IS TOO SMALL FOR SAT
User Action: Reinitialize the diElk.

280

System Installation Error Messages

SATT.SYS NON-EXISTENT AT TIME OF READ

User Action: If the file structure on the disk is sound, submit an SPR
and a copy of INIT.SYS and console output. Otherwise, reinitialize the
disk.
SATI.SYS NOT FOUND - RESULTS UNPREDICTABLE

User Action: Reboot the system and retry the operation. If the error
recurs, reinitialize the disk.
filnam.SIL NOT FOUND - PLEASE INSTALL A SIL

Explanation: The SIL that you previously installed is not on the disk.
User Action: Use the START option to install a monitor SIL.
SWAP.SYS NOT CONTIGUOUS OR TOO SMALL

User Action: Re-create SWAP.SYS using the Refresh option.
SWAP.SYS NOT PRESENT IN [0,1]

User Action: Re-create SWAP.SYS using the Refresh option.
SYMBOL xxxxxx NOT FOUND IN MONITOR SYMBOL TABLE

User Action: Regenerate your monitor. If the problem recurs, submit
an SPR and a copy of INIT.SYS and console output.
TOO MANY BA DEVICES

User Action: Submit an SPR and a copy of INIT.SYS, your monitor
.SIL file, and console output.
TOO MANY BLOCKS IN DEVICE CONFIGURATION TABLE

User Action: Regenerate your monitor. If the problem recurs, submit
an SPR, a copy of INIT.SYS and console output.
TOO MANY xx: CONTROLLERS GENERATED

User Action: 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

User Action: Submit an SPR and a copy of INIT.SYS and console
output.
TOO MANY SUB LINES FOR nn:

Explanation: This message is a warning if the monitor generated for
DHU (16 lines) or DZ11 (8 lines) is started on a QBUS system (DHU has
only 8 lines and DZ11 has only 4 lines).
User Action: Make sure that any edits to CONFIG.MAC are correct. If
there are no editing errors, regenerate the system.

System Installation Error Messages

281

TOO MANY UNIBUS DEVICES ON THIS 11170

User Action: 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 fewer words of memory,
submit an SPR.
TOO MUCH MODIFICATION TO MONITOR REQUIRED

User Action: Regenerate to produce a monitor that is more closely
configured to your system hardware.
TWO MAGTAPE UNITS HAVE THE SAM~~ UNIT NUMBERS

User Action: Examine unit switches on magnetic tape drives and make
sure that no two have the same urnit number.
UFD HAS SIZE TOO LARGE FOR FILE [P,PN] filnaul.typ - CHANGED TO XXX

Explanation: Warning message only. REBUILD corrects the condition.
UFD HAS SIZE TOO SMALL FOR FILE [P,PN] filnam.typ - CHANGED TO XXX

Explanation: Warning message only. REBUILD corrects the condition.
[0,1] UFD NOT FOUND

User Action: Reinitialize the disk.
UNABLE TO CREATE REQUESTED FILE(S)

User Action: 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

User Action: Submit an SPR and a copy of INIT.SYS and console
output.
UNEXPECTED TRAP THROUGH THE VECTOR AT nnn. TRAP OCCURRED
FROM PC = nnnnnn.

User Action: Submit an SPR and! a copy of INIT.SYS and console
output.
UNKNOWN DEVICE BOOTED

User Action: This error is of the result of a hardware failure. If this
device has successfully booted this version of RSTSIE before, call the
DIGITAL field service engineer to (correct the hardware problem.
UNKNOWN RH CONTROLLER PRESEN'r

User Action: Call the DIGITAL field service engineer to correct the
hardware configuration.

282

System Installation Error Messages

UNRECOVERABLE DISK ERROR ON xxn:
User Action: 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.
This error is also often caused by a hardware failure. If this seems to be
the case, contact the DIGITAL field service engineer.
USER-DEFINED ADDRESS FOR DEVICE xxn: NOT FOUND - DEVICE
DISABLED
User Action: Use HARDWR to set the correct CSR address for XX:, or
call the DIGITAL field service engineer.
USING KWIIL CLOCK
Explanation: Warning message only. The installed SIUs defaults
indicate a KWIIP clock is preferred, but the KWIIP clock is not present.
RSTSIE uses the KWIIL clock instead.
USING KWIIP CLOCK AT LINE FREQUENCY
Explanation: Warning message only. The installed SIUs defaults
indicate a KWIIL clock is preferred, but the KWIIL clock is not present.
RSTSIE uses the KWllP clock instead.
VECTOR FOR DEVICE xx: (nnnn) ALREADY IN USE - DEVICE DISABLED
User Action: Use HARDWR to set the correct vector address for xx:, or
call the DIGITAL field service engineer.
VECTOR TABLE FULL
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
WARNING - BAD BLOCK DOUBLY ALLOCATED TO BADB.SYS
Explanation: Warning message only.
WARNING - BOOTED DEVICE IS AT A NON-STANDARD CSR ADDRESS
Explanation: The initialization code successfully bootstrapped the
device. The device is at a non-standard CSR address, but the device has
not been declared at the non-standard CSR address.
Explanation: Before starting your RSTSIE monitor, use CSR (a
HARDWR suboption) to declare this device at the non-standard address.
WARNING - DCN IN BADB.SYS TOO BIG
Explanation: Warning message only. The file structure on the disk
being rebuilt appears invalid.
WARNING - DBn: IS DUAL PORTED
Explanation: Warning message only.
WARNING - DCN IN BADB.SYS NOT ON PACK CLUSTER BOUNDARY
Explanation: Warning message only.

System Installation Error Messages

283

WARNING - xxx FILE NOT FOUND - PLEASE SET DEFAULTS
Explanation: The SIL you are installing specifies a primary run-time
system or error message file that i.s not present.
User Action: Use the DEFAULT option to specify a valid file.
WARNING - FILE filnam.typ NOT FOUND WHEN REMOVING OLD SIL
Explanation: Warning message only.
WARNING - LINK IN BADB.SYS IS BAD. BAD BLOCKS MAY BE LOST.
Explanation: Warning message only.
WARNING - MAIN MEMORY (Cache) DISABLED AT STARTUP. RSTS/E WILL
NOT USE (cache). SYSTEM MAY RUN SLOWLY.
Explanation: Warning message only. (cache) is CACHE, CACHE
GROUP 0, or CACHE GROUP 1.
User Action: As this may cause your system to run slowly, contact the
DIGITAL field service engineer.
WARNING - MAIN MEMORY (cache) IS FAILING REPEATEDLY. RSTSIE WILL
NOT USE (cache). SYSTEM MAY RUN SLOWLY.
Explanation: Warning message only. (cache) is CACHE, CACHE
GROUP 0, or CACHE GROUP 1.
User Action: As this may cause your system to run slowly, contact the
DIGITAL field service engineer.
WARNING - NO SET UP FOR DEVICE xx
Explanation: You may have either a corrupt distribution kit or incompatible versions of INIT.SYS and the monitor .SIL.
User Action: Submit an SPR and a copy of INIT.SYS and console
output.
XDn: DISABLED - LINE EXCEEDS CONTROLLER (XDn:) MAXIMUM
Explanation: 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 RSTSIE system that was generated with DMPs could exceed this
maximum. This error message tells you that the limit was exceeded.
XEn: TRANSCEIVER POWER FAILURE
XEn: PORTILINK CABLE PROBLEM
Explanation: These failures point to a specific piece of the DEUNAIDELUA
which is broken.
XHn: INITIALIZATION FAILURE
Explanation: This indicates that a checksum of either the hardware
address registers or the micro-diagnostic ROM failed.

284

System Installation Error Messages

Appendix B

Address and Vector Assignments
The RSTSIE 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 presence 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. The following sections present the algorithms
for assignment of floating addresses and vectors. Also included are the fixed
assignments for devices supported by RSTSIE.

IFloating Addresses
Currently the floating address devices include the devices listed in Table 25.
Note that RSTSIE does not currently support all the devices listed. 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.

•

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

XXXXXO,xxxxx4

3,4

XXXXXO

5,6,7,8

XXXXOO,x:xxx20 t XXXX40,xxxx60

9 thru 16

XXXXOO,XXXX40

A "gap" of at least one word will be left after each type of device, starting
on the same boundary as the device. 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 mUBt be addressed contiguously.

Address 760010 is reserved for the first DJ11. Since the DJ11 has four registers,
additional DJ11s are assigned addresses modulo 10 (base 8) immediately
following the first DJ11 (for example, 760010, 760020, and so forth). The modulo
10 (base 8) address following the last DJ11 is left empty and is known as the
DJ11 gap. If there are no DJ11s, the gap iB at 760010. If there is one DJ11, the
gap will be at 760020. All gaps must be at least one word in length.
Mter all DJ11 addresses and the DJll gap are defined, the address for the first
DH11 can be assigned. DH11s have eight registers, which implies a modulo 20
(base 8) boundary. The address of the first DH11 is the first modulo 20 address
following the DJ11 gap. If there are no DJ11s (DJ11 gap at 760010), The first
DH11 is assigned address 760020. Similarly, if there is one DJ11, the DJ11 gap
will begin at 760020 and the next available modulo 20 boundary is 760040. All
additional DH11s are assigned addresses nlOdulo 20 immediately after the first
DH11. The DH11 gap begins on the 20 boundary following the last DH11.
Mter all DH11 addresses and the DH11 gap are defined, DQ11, DUll, DUP11,
LK11, DMC11, DZl1, and KMC11 through DMVI1-AD 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, shown in Figure 13, is a graphilc aid that allows you to quickly assign
floating addresses to a device without referring to the formal rules. 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 workBheet is 760400. The first address
of the worksheet on the next page is 760400. This allows you to carryover 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.

286

Address and Vector Assignments

Cohunns 2 through 33 contain the floating address device names. 'lb 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 1).
Using the Worksheet

'lb 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
DJll and two DHII devices, enter 2 in the space provided adjacent to the
DJll and the DHII in the List of Devices.
2. Begin at address 760010 of the worksheet under the DJll column and record
the unit number for all DJlls in your configuration. Begin with unit 0
and end with unit n-l, where n represents the number of DJlls in your
configuration. For example, if you have two DJll 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 un shaded 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 LPPII and DWR70
devices. In this case you would start at address 760130 under the
first unshaded box under the LPPII column.

3. Immediately below the last device unit, mark an X for the required address
gap. For example, the last DJll 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 un.shaded boxes when you mark the address gap. The
shaded boxes also indicate an illegal address gap.
4. 'lb 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
DJll 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.
5. 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-1. (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 DHl1 unit, mark an X for the DHl1 gap. Then mark a Y to
the right of the address gap.

Address and Vector Assignments

287

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.
7. Mter you complete the worksheet, you can record the device, the unit number,
and its associated floating address in th4e spaces provided in the Record of
Floating Addresses (to the right of the worksheet).

288 Address and Vector Assignments

Figure 13:

Floating Address Worksheet
DEVICE

CD" DUll. DUVll
®" DZ". DZV". DZOll
® " MSCP device.
<9 " TMSCP device.
®" DHU". DHVll

LIST OF DEVICES

DJll
DHll
DOll
DUll DUVll
DUPll
LKll
DMCll
DZll DZVll DZO,,_

DA"-W_
DAll-8 _
DMPll
DPVll
IS811
DMVll
UNA
MSCP

KMCll _
LPPll _
VMV21 _
VMV31 _
DWA70 _

All 1
KWll
AXll

_
_

DMF32
KMSll
VS100
TMSCP
_
KMVll
DHUllDHVll_

RECORD OF FLOATING ADDRESSES

DEVICE

UNIT

ADDAESS

DEVICE

UNIT

ADDAESS

(continued on next page)
Address and Vector Assignments

289

Figure 13 (Cont.):

Floating Address Worksheet
DEVICE

D
ADDRESS J

D
H
I
I

I
I

(2) I

K M

;

~ ® C
I

v
I
I

M
V
2
I

V
M

D
W
R
7

R
L
I
I

LKRRDDD

P W 5
A

I
I

P
I

IlJ

X R R M

S M
V

M M
F

S
I
I

I
0

o
o
o

DUll. DUVII
DZII. DZVII. DZQII
MSCP deVices
TMSCP deVices

DHUII. DHVII

RECORD OF FLOATING ADDRESSES

R
r

D
R

1
1

D
M
P

DUD
M N
M
V A

DEVICE

UNIT

ADDRESS

DEVICE

UNIT

ADDRESS

K
M
S

(continued on next page)
290

Address and Vector Assignments

Figure 13 (Cont.):

Floating Address Worksheet
DI!YICE

AOOfIESS

~
1

a
1

0
M

1G)P
1
1
1

1
1

K
M

C @C
1
1
1

0
W

K R
W s
1
1

0
M
1
1

I
S
1
1

0
M

1
1

0
M

® 3F S1

B V

1
1

K
M

(9 v@
1
1

®
@
13)
@

DUll. DUVll
DZll. DZVll. DZQll
MSCP devices
TMSCP devices
DHUll.DHVll

RECORD OF FLOATING ADDRESSES

DOLO

VVO

aUK

W s

"'0p,C@C
1 1 1
1
1
1

1
1

VVR1
2
3
7
1
0
1
1

1
1

DUD

M N

V
1
1

1
1

DEVICE

UNIT

ADDRESS

DEVICE

UNIT

ADDRESS

M M

® F
3

S
1

(continued on next page)
Address and Vector Assignments

291

Figure 13 (Cont.):

Floating Address Worlksheet
DEVICE

DUll. DUVll

MSCP devices

DZll. DZV11. DZQll

(3)

TMSCP devices

DHUll DHVll

RECORD OF FLOATING ADDRESSES

DEVIOE

UNIT

ADDRESS

DEVICE

UNIT

ADDRESS

ZK-9248-t-IC

292

Address and Vector Assignments

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 already in
production. Gaps in the vector assignments are not required. The floating vectors
begin at address 300 and proceed in ascending order.
Table 25 lists the vector assignment sequence for current devices.
Table 25:

Device Vector Assignments
First

Vector
Size

Max
Units

+10

174770

-10

Address

Next
Addr.

DCl1

174000

DLJl1A,B

176500

DPJl1

Device

BR
Level

RSTSIE Notes

BR5

Not supported

BR4

Non-console

BR5

Not supported

DM11A

175000

+10

BR5

Not supported

DNl1

175200

+10

BR5

Not supported

DM11BB

170500

+10

BR4

DH11 modem
control

DRI1A,C

167770

-10

101

BR5

Not supported

PAG11 Reader

172600

BR4

Not supported

BR4

Not supported

PAG11 Punch

172700

LPD11

4
10

Not supported
1

BR7

Not supported

BR4

Not supported

BR4

DTl1
(DT03_FP)

174200

DX11

176200

+40

101

DLI1C,D,E

175610

+10

101

DJ11

FLOAT

+10

101

BR5

+20

DHl1

FLOAT

GT40

172000

VSV11

172000

20 1
+10

Not supported

BR5
BR5

Not supported
Not supported

20
1

LPS11

170400

+40

BR5,6

Not supported

DQ11

FLOAT

+10

101

BR5

Not supported

KW11W

172400

Not supported
2

DUlllDUVll

FLOAT

+10

BR5

DUPll

FLOAT

+10

101

BR5 2

DVl1

175000

+40

20 1

BR5,6

Not supported

LK11

FLOAT

+10

101

BR4

Not supported

DMC11IDMR11

FLOAT

+10

101

BR5

FLOAT

+10

BR5

FLOAT

+10

101

BR5

LPP11

FLOAT

+10

Not supported

VMV21

FLOAT

+10

Not supported

DZI1IDZV111
DZQ11
:£{MCll

2780 only
2780, HP2780,
3271

1-The first vector for the first device of this type must always be on a 10(8) boundary.
2

-Also supported at BR6 under RSTS/2780.

Address and Vector Assignments

293

Table 25 (Cont.):

Device Vector Assig nmellts

Device

First
Address

Next
Addr.

VMV31

FLOAT

+20

VTVOI

172600

DWR70

FLOAT

+10

RLII

FLOAT

+10

TSll

172520

Vec1tor
Size

Max

Units

Level

Not supported

10
10

RSTSIE Notes

Not supported
Not supported
BR5

Not supported
after 1st

BR5

LPAII-K

170460

IPII

171000

KW11-C

FLOAT

+10

RX11, RX211,
RXVl1

FLOAT

+10

DR11-W

FLOAT

+10

Not supported

DRI1-B

FLOAT

+10

Not supported

DMPll

FLOAT

+10

DPV11

FLOAT

+10

MLII

176400

Not supported
Not supported

BR5

After 1st only

BR5

DECnetIE only

BR5

Not supported
Not supported

ISBII

FLOAT

+10

DMVll

FLOAT

+20

10
10

BR5

DHVIIIDHUIII
DHQ11

FLOAT

+20

BR5

Not supported
DECnetIE only

Fixed Addresses and Vectors
Table 26 lists the devices supported under nSTS/E that have fixed addresses and
vectors.

294

Address and Vector Assignments

Table 26:

Devices with Fixed Addresses and Vectors

Device

Address

MSCP
TMSCP

Vector

BRLevel

RSTSIE Notes

1.72150

BR5

1st controller
only

174500

BR5

1st unit only

RF11

177460

204

BR5

Not supported

RS03IRS04

172040

204

BR5

Not supported

177400

220

BR5

Up to 8 drives

RK05IRK05F

RLOIIRL02

174400

160

BR5

Up to 4 drives

RK06IRK07

177440

210

BR5

Up to 8 drives

RP02IRP03

176710

254

BR5

Not supported

Second RHll170
RM02IRM03IRM05IRM80
RP04IRP051RP06

176300

150

BR5

Up to 8 drives

First RHll170
RP04IRP05IRP06
RM02IRM03IRM05IRM80

176700

254

BR5

Up to 8 drives

RX01IRX02

177170

264

BR5

First only

DECtape

177340

214

BR6

Not supported

TUI0frEI0frS03frSII

172520

224

BR5

First TSII drive
only

TU16frEl6trU45frU77 3

172440

224

BR5

Up to 8 drives

(LPO)

177514

200

BR4

(LP1)

164004

170

BR4

(LP2)

164014

174

BR4

(LP3)

164024

270

BR4

(LP4)

164034

274

BR4

LP11

(LP5)

164044

774

BR4

(LP6)

164054

770

BR4

(LP7)

164064

764

BR4

CR11,CMll

177160

230

BR5

CD 11

177160

230

BR4

KWI1L

177546

100

BR6

KW11P

172540

104

BR6

KG11

170700

NONE

2780 only

DL11A,DL11B

177560

BR4

Console interface

DEQNA,DELQA XIIO

774440

BR5

XIII

774460

BR5

DEUNA,DELUA XEO

774510

120

Not supported

BR5

1-These controllers have programmable vectors; INIT.SYS finds an available vector address and
assigns it to them.
2-Each RK05F must be counted as two drives.
3 -Maximum of 4 TU77's

Address and Vector Assignments

295

RH70 BAE and CS3 Addresses
Table 27 lists the four possible RH70 High Speed 1/0 Controller addresses, their
Bus Address Extension (BAE) and Control addresses, their BAE Control Status 3
(CS3) addresses, and their uses.
Table 27:

RH70 BAE and CS3 Addresses

Device

Address

BAE

CB3

RS03IRS04 (Not supported)

172040
172440
176300
176700

172070
172474
176350
176750

172072
172476
176352
176752

11J16rrElsnNU45~77

Mixed/nonstandard
RP04IRP05IRP06 or
RM02IRM03IRM05IRM80

296

Address and Vector Assignments

Appendix C

RSTS/E System Files

IFISTS/E System Files
This section 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
.SYS
SWAP
.SYS
ODT
INSTAL. COM
COPYUP.COM
CSPHLP.COM
LISTER.COM
MONITR.COM
ASSLOG.COM
INSPKG.COM
DECNT2.COM
DELI.OG . COM
RECOVR.COM
. HLP
LP
CSPRES.COM
. COM
CSP
BEGIN • COM
RSTS97.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>
16C <104>
11C <104>
7C <104>
4C <104>
7C <104>
2C <104>
18C <104>
25C <104>
16C <104>
632CPL< 60>
< 40>
4
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
. COM
LP
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>

Total of 8007 blocks in 45 files in SYO: [0,1]

SYO: [0,1]

Help Package
Name

.Typ

FILNAM.HLP
PLEASE.HLP
RSTS
.HLP
SETHLP.HLP
TYPE
.HLP
VTEDIT.HLP
DCFUNC.HLP
DCOPER.HLP
MAIL
.HLP
DCALLO.HLP
DCATTA.HLP
DCCCL .HLP
DCCLLG.HLP
DCDEAL.HLP
DCDSQU.HLP
DCDEFI.HLP
DCDLAC.HLP
DCDLCS.HLP
DCDLQU.HLP
DCDETA.HLP
DCDMDK.HLP
DCDUMP.HLP
DCEOD .HLP
DCHANG.HLP
DCIF
. HLP
DCINSV.HLP
DCINST.HLP
DCLOGI.HLP
DCMACR.HLP
DCMOUN.HLP
DCONCC.HLP
DCOPLG.HLP
DCPRIN.HLP
DCREJO.HLP
DCRERU.HLP
DCRUN .HLP
DCSECA.HLP
DCSENC.HLP
DCSEND.HLP
DCSENE.HLP
DCSELG.HLP
DCSENO.HLP
DCSEPR.HLP
DCSESV.HLP
DCSEVE.HLP
DCSHBU.HLP
DCSHCS.HLP
DCSHDA.HLP
DCSHFI.HLP
DCSHPV.HLP
DCSHLO.HLP
DCSHMY.HLP
DCSHPR.HLP
DCSHRT.HLP
DCSHSB.HLP
DCSHTI.HLP
DCSTQU.HLP
DCSTSV.HLP
DCSPQU.HLP
DCSPSV.HLP
DCUNOV.HLP
DCWRIT.HLP
ADVANC.HLP
BPCOMM.HLP
BPHELP.HLP

298

RSTS/E System Files

Size
12
5
17
19
3
3

25
7
2
4
4

3
2
2
3
1
8

2
2
5
3
1
3
2
4

13
2
6

2
1

10
19
1

2
4
8

2
3
3
2
2
9
9
3
3
1

1
1

2
2
1
1
1
2
1
2
8

3
7
3
6

20
12
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>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

Name .'ryp
KEYBRD.HLP
PLEBAC.HLP
DISK • HLP
TECO • HLP
UTHELP.HLP
DCEXPR.HLP
DCLABE.HLP
DCSYMB.HLP
DCAT . HLP
DCASQU.HLP
DCBYE .HLP
DCCLOS.HLP
DCCLQU.HLP
DCDEAS.HLP
DCDSSY.HLP
DCDFCM.HLP
DCDLCM.HLP
DCDLEN.HLP
DCDLSV.HLP
DCDISM.HLP
DCDMMT.HLP
DCDPSY.HLP
DCFORT.HLP
DCHELP.HLP
DCINIT.HLP
DCINQU.HLP
DCLOOV.HLP
DCLOGO.HLP
DCLMRG.HLP
DCON
. HLP
DCOPEN.HLP
DCOPQU.HLP
DCREMO.HLP
DCRELI.HLP
DCREQU.HLP
DCSET .HLP
DCSECO.HLP
DCSEDA.HLP
DCSEEC.HLP
DCSEHO.HLP
DCSEON.HLP
DCSEPA.HLP
DCSEQU.HLP
DCSETI.HLP
DCSENV.HLP
DCSHCM.H.LP
DCSHDT.H.LP
DCSHDV.H.LP
DCSHJO.H.LP
DCSHLB.H.LP
DCSHLS.H.LP
DCSHNT.HLP
DCSHRV.HLP
DCSHSV.HLP
DCSHSY.HLP
DCSTAR.H.LP
DCSTQM.HLP
DCSTOP.HLP
DCSPQM.HLP
DCUNLI.HLP
DCUNRU.HLP
ACCNTS.HLP
BPCHLP.HLP
BPFUNC.HLP
BPSTAT.HLP

Size
5
5
9
4

Prot

< 40>
< 40>
< 40>
< 40>

< 40>
< 40>

2
12

< 40>
< 40>

3
2
3
2
2
3

< 40>
< 40>
< 40>
< 40>

1
1
1
3
2

1
3
2
2
5
2
8
3

5
1
9

10
2
2
2
2
3

< 40>
< 40>

< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

< 40>
< 40>
< 40>
< 40>
< 40>

< 40>
< 40>

< 40>
< 40>
< 40>

4
3
3

< 40>
< 40>
< 40>

< 40>
< 40>

13
2
2
1
1
2
5
1
1
1
1

13
1
1

7
2

< 40>
< 40>
< 40>
< 40>

< 40>
< 40>
< 40>
< 40>
< 40>
< 40>

4
3
2

< 40>
< 40>
< 40>

30
4

< 40>
< 40>

14
19

< 40>

SY: [0,2]

DATES .HLP
DCMAII, . HLP
EXPRES.HLP
FORMS .HLP
KEYS
. HLP
LABELS.HLP
OPERAT.HLP
PROGRM.HLP
ERRHLP.HLP
PLEHLP.HLP
PLEQUE.HLP
QUEHLP.HLP
TECOMD.HLP
TYPHLP.HLP
VTEDKP.HLP
QUEUES.HLP
RSX
• HLP
RUNTIM.HLP
SYMBOL.HLP
TIMES .HLP
BPCREF.HLP
DSKDMI?HLP
FIT
. HLP
BLDCSP.HLP
DECDX .HLP
FRLHLP.HLP
DCLSRT.HLP
WPS
. HLP
NETCPY.HLP
. HLP
NFTS
DCASSI.HLP
DCBACK.HLP
DCBP2 .HLP
DCCOPY.HLP
DCCREA.HLP
DCDFCS.HLP
DCDIFF.HLP
DCDLSB.HLP
DCFOFO.HLP
DCF77 .HLP
DCGOTO.HLP
DCINER.HLP
DCINLI.HLP
DCINOV.HLP
DCINSW.HLP
DCLOAD.HLP
DCMTDK.HLP
DCREAD.HLP
DCREOV.HLP
DCRESW.HLP
DCRETU.HLP
DCSEDT.HLP
DCSEEN.HLP
DCSEJO.HLP
DCSEPT.HLP
DCSETE.HLP
DCSHAL.HLP
DCSHDK.HLP
DCSHFO.HLP
DCSHOW.HLP
DCSHQT.HLP
DCSHUS.HLP
DCTYPE.HLP
DCUNLO.HLP
COpy . HLP
HELP
.TSK
PASSWD.HLP
PIPDIR.HLP

3
6
18
5
3
7

2
7

6
4
8
12
3
6
20
3
9
14
7
6
26
11
9
2C
1
31
2
4
28
3
31
2
21
8
8
5

3
3
3
3
6
9
6
11
1
10
5

2
2
5

2
9
6
4
36
3
6
2
3
2
7

8
2
3
29C
10
3

< 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>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
< 40>
<232>
< 40>
< 40>

DCL
. HLP
ENTRYS.HLP
FILES .HLP
FUNCTN.HLP
CTRLT .HLP
MAGTAP.HLP
PRIVS .HLP
DIRHLP.HLP
FITHLP.HLP
PLEBAT.HLP
PLESPL.HLP
TECHLP.HLP
TECOFL.HLP
VTEHLP.HLP
UTLHLP.HLP
QUOTAS.HLP
RT11
. HLP
SERVRS.HLP
TERMNL.HLP
B2CREF.HLP
DIRECT. HLP
ERRDIS.HLP
RSTSFL.HLP
CMSMGR.HLP
FRL
. HLP
DCEXIT.HLP
DCLMGE.HLP
HELP .BAK
NFTC . HLP
DCAPPE.HLP
DCASSY.HLP
DCBASI.HLP
DCBROA.HLP
DCCRAC.HLP
DCDELE.HLP
DCDIBO.HLP
DCDIRE.HLP
DCEDIT.HLP
DCFORC.HLP
DCGOSU.HLP
DCINDK.HLP
DCINIQ.HLP
DCINMT.HLP
DCINRU.HLP
DCLINK.HLP
DCLOID.HLP
DCMTMT.HLP
DCREER.HLP
DCRENA.HLP
DCREST.HLP
DCSEAC.HLP
DCSEDV.HLP
DCSEFI.HLP
DCSEPN.HLP
DCSESY.HLP
DCSHAC.HLP
DCSHCA.HLP
DCSHEN.HLP
DCSHFS.HLP
DCSHQU.HLP
DCSHTE.HLP
DCSUBM.HLP
DCUNID.HLP
COPHLP.HLP
DISKS .HLP
HELP
. HLP
PIPHLP.HLP
PIPSAV.HLP

11
19
28
7

10
12
4

11
4
6

5
6

12
11
13
7
4

12
4
7
6

1
1
3

26
7

12
8

3
3
5

18
11
2

11
9

5
5

15
22
6

11
5
3
5
2

12
31
14
2
6
9
9
9
5
9

5
11
6

19
2
4

14
7

31
31

RSTS/E System Files

299

SYSHLP.HLP

< 40>

Total of 1827 blocks in 267 files in SY: [0,2]

Error Reporting Package
Name .Typ
ERRDAT.FIL
ERRCPY.TSK
ERRDET.TSK
ANALY1.TSK
ANALY3.TSK

Size
95C
14C
40C
52C
44C

Prot
< 60>
<124>
<124>
<124>
<124>

Name .Typ
ERRINT.TSK
ERRDIS.TSK
ANALYS.TSK
ANALY2.TSK
ERRLOG.FIL

Size
l8C
39C
47C
46C
2

Prot
<124>
<124>
<124>
<124>
< 60>

SYO: [0,3]

Size
20C
:L1C
20C
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]

Size
12C
61C
59C
61C
52C
62C

Prot
< 60>
<232>
<232>
<232>
<232>
<232>

SYO: [0,8]

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 ]

PrintlBatch Services Package
Name .Typ
PBS
.TSK
PBSERR.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
50C
29C
60C
36C
51C
51C

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]

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

Total of 583 blocks in 13 files in SYO: [0,8]

300

RSTS/E System Files

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

Size
26
63
l05C
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: [0,9]

Prot
<232>
<104>
<104>
< 42>
< 42>
< 42>
< 42>

SYO: [0,10]

Prot
< 60>
< 60>
<104>

SYO: [0,11]

Total of 1683 blocks in 52 files in SYO: [0,9]

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

Total of 788 blocks in 15 files in SYO: [0,10]

EDT Package
Name .Typ
EDT52 .DOC
EDT200.DOC
EDT
.LIB

Size
3
4
162C

Prot
< 60>
< 60>
< 42>

Name .Typ
EDT100.DOC
EDTKIT.DOC
EDT
.TSK

Size
3
39
49C

Total of 260 blocks in 6 files in SYO:[O,ll]

RSTS/E System Flies

301

SYSGEN Components and BASIC-PLUS Package
Name .Typ
MONITR.CMD
RSXRTS.CMD
CHECK .MAC
KBDEF .MAC
CRA
.OBJ
MCP
.OBJ
OPN
.OBJ
.OBJ
KVR
.OBJ
EMT
GEN
.OBJ
RSX
.OBJ
FMS
.OBJ
DHPORT.OBJ
DZPORT.OBJ
PKPORT.OBJ
TERCLS.OBJ
KIN
.OBJ
SES
.OBJ
TRN
.OBJ
EVL
.OBJ
UNA
.OBJ
OVRLRG.OBJ
DEFALT.SAV
BUFCHK.TSK
BPLGEN.SAV
MA2
.OBJ
MA2F .OBJ
MA4F .OBJ
XL2
.OBJ
XL2F .OBJ
XL4F .OBJ
XT2I .OBJ
XT4
.OBJ
SF
.OBJ
PU
.OBJ
SN
.OBJ
VE
.OBJ
BASIC .CMD

Size
1
1

22
32
7
3
3
3
3
3

2
3
2
2
4
13
3
2
3
2
4
4
4C
21C
61C
16
14
16
3
2
2
3
3
6
5
2
2
1

Prot
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
<124>
<124>
<124>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>

Name .Typ
RJ2780.CMD
HOOK .SAV
TBL
. MAC
RSTS .OBJ
DSK
.OBJ
BBR
.OBJ
.OBJ
XVR
.OBJ
MVR
EM2
.OBJ
GRD
.OBJ
FIPLRG.OBJ
NOD
.OBJ
DLPORT.OBJ
VHPORT.OBJ
PDVVEC.OBJ
KBD
.OBJ
LAT
.OBJ
NSP
.OBJ
RDM
.OBJ
DMP
.OBJ
QNA
.OBJ
OVLHD .OBJ
DEFALT.STB
SYSGEN.SAV
RTS
.OBJ
MA2I .OBJ
MA4
.OBJ
MA4D .OBJ
XL2I .OBJ
XL4
.OBJ
XT2
.OBJ
XT2F .OBJ
XT4F .OBJ
10
.OBJ
MX
.OBJ
DBG
.OBJ
BASIC .COM

Size
21
28C
118
1008
5
3
2
3
3
3

2
4
2
2
1
4
3
3
2
2
4
1
1
102C
83
14
19
14
3
4
3
2
2
6
8
2
1C

Prot
< 60>
<124>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 40>
< 60>
<124>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
<104>

SY: [0,12]

Prot
<104>
<104>
< 60>
< 60>
< 40>
< 40>
<104>
<104>
<104>
< 40>
<104>
<104>
< 60>
< 60>
< 60>

SYO: [0,13]

Total of 1771 blocks in 75 files in SY: [0,12]

TECO Package
Name .Typ
TECO .RTS
TYPE .TEC
TECO .HLP
TECOFL.HLP
VTEDKP.HLP
TECORN.DOC
TECKBM.TEC
SEARCH.TEC
TECO .TES
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.DOC
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

Total of 664 blocks in 31 files in SYO: [0,13]

302

RSTS/E System Files

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
.TSK
ODT
TALK .TSK
DISPLY.TSK
BPCREF.TSK
RUNOFF.TSK
RUNOFF.RNO

Size
27C
11C
61C
24C
58C
56

Prot
<104>
<232>
<232>
<104>
<104>
< 60>

SYO: [0,14]

Prot
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
< 60>
<104>

SYO: [0,15]

Total of 605 blocks in 14 files in SYO: [0,14]

SORTIMERGE Package
Name .Typ
SRTLIB.OLB
MGELIB.OLB
SRTMRG.OOl
SRTMRG.004
SRTREC.ODL
MGEREC.ODL
SRTMRG.006
SRTSHR.OLB
SRTMRG.008
SRTMGE.MST
SRTMRG.OI0
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.ODL
SRTMRG.003
SRTFIL.ODL
MGEFIL.ODL
SRTMRG.005
SRTMRG.007
MGESHR.OLB
SRTTST.DAT
SRTMRG.009
SRTMRG.Oll
SRTMRG.013
SRTMRG.002
MGEUTL.TSK

Size
11
10
5
11
9
16
5
194
81
33
31
3
5
370C

Total of 2277 blocks in 29 files in SYO:[O,15]

SOURCE Package
Name .Typ
ATPK .BAS
DISPLY.BAS
LOGIN . BAS
SHUTUP.BAS

Size
97
151
79
138

<
<
<
<

Prot
60>
60>
60>
60>

Name .Typ
DIRECT. BAS
. BAS
HELP
LOGOUT. BAS
SYSTAT.BAS

Size
99
100
32
138

Prot
60>
60>
60>
60>

SY: [0,17]

<
<
<
<

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: [1,1]

Total of 834 blocks in 8 files in SY: [0,17]

RSX Utilities Package
Name .Typ
SYSLIB.OLB
BP2
.LNK
DIBOL .LNK
F77
.LNK
RMSMAC.MLB
RMSll .ODL
RMS11S.0DL
RMS11X.ODL
RMSRLX.ODL
DAPRLX.ODL
RMSRES.STB
DAPRES.STB
ODTID .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
.LNK
C81
.LNK
DMS
RSX11 .LNK
RMSLIB.OLB
RORMS1.MAC
RMS12S.0DL
RMS12X.ODL
DAPIIX.ODL
RMSRES.TSK
DAPRES.TSK
.OBJ
ODT
EDTHEL.HLP

Total of 1414 blocks in 26 files in SYO:[l,l]

RSTS/E System Files

303

System Library Package
Name .Typ
INSTAL.LOG
UTLMGR.TSK
ONLCLN.TSK
SILUS .SAV
MACRO .SAV
LINK .SAV
ERR
.STB
COMMON.MAC
DCLUTL.TSK
CONFIG.MAC
SYSGEN.COM
LOGIN .TSK
DIRECT.TSK
FILCOM.TSK
SWITCH.TSK
SAVRES.SAV
UTILTY.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
55C
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
DSKINT"TSK
ACTMGR '. TSK
PIP
.. SAV
CREF "SAV
LIBR .. SAV
ONLPAT"SAV
KERNEL .. MAC
TST090"SYS
GLOBAL" COM
SYSLIB"OBJ
LOGOUT .. TSK
SYSTAT .. TSK
PLEASE .. TSK
SYSMAC .. SML
TERMGR .. TSK
PIPSAV .. TXT
MAKSIL .. TSK
STK
.. TSK
LBR
.. TSK
CRF
.. TSK
BUILD "TSK
PBUILD"TSK
AUTOED .. TSK
QUIT
START . LOG

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

Total of 3065 blocks in 52 files in SYO: [1,2]

304

RSTS/E System Files

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]

Appendix D

Bootstrapping the Distribution Medium
The distribution medium is the tape or disk on which DIGITAL supplies the
RSTSIE 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:
Performing limited hardware scan.
RSTS V9.7 (MTO) INIT V9.7-11
Today's date?
Current time?
Installing RSTS on a new system disk? <Yes>

For the bootstrap operation to succeed, the distribution medium must be on line,
ready, and write-protected; the medium accessed must contain a proper bootstrap
record; and the console terminal must be on line. The following two sections
descrIbe the bootstrap procedures for each of the distribution media. The third
section details hardware bootstrap procedures.

Bootstrapping Magnetic Tape Distribution
The operation of the magnetic tape devices is described in the RSTS IE System
User's Guide. '1b bootstrap the magnetic tape, do the following:
1.

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 TUl6, TEl6, TU45, or TU77 tape
drive if a TUlO, TE10, or TS03 drive is present. Therefore, if
your system includes drives of both types (TU10ITE10ITS03 and
TU16ITE161TU45/rU77), bootstrap the 800 bpi distribution tape
on the TU10, or TE10 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 011 a TS11 drive.
2. 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.

3. Set the ONLINE/OFFLINE switch on the tape unit to ONLINE and make
sure that the RDY indicator is lighted.
4. Make sure that the console terminal is on line.
5. Follow the bootstrap instructions in the section, Hardware Bootstrap
Procedures, for the type of hardware bootstrap device that is on the system.
NOTE

The tape drive MUST be write-protected and online for the installation
to proceed properly.

Bootstrapping Disk Distribution
'lb bootstrap the disk cartridge, proceed as follows:

1. Insert the disk cartridge in a free unit, either 0 or 1. RL02 disks can use any

2.
3.
4.
5.

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

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 m.ust be on line and ready; the medium
accessed must contain a proper bootstrap record; and the console terminal must
be on line.
The PDP-11 console switches and their use are described in the various processor
handbooks. The bootstrap procedure that you should use depends upon the type
of hardware bootstrap device on the systeml.

306

Bootstrapping the Distribution Medium

Table 28 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.
liable 28:

Summary of Hardware Bootstrap Addresses
UNIBUS Bootstrap Type

Device to Bootstrap

M9301-YA

M9301-YB

M9301-YC

M9301-YF

M9312

RK05 disk cartridge unit 0

DKn

30+n

DKn

RP04IRP05IRP06IRM02!
RM031RM05! or RM80 disk
p,ack unit 0 at 176700 CSR
RK05 disk (unit n)

DKn

DLn

RLOIIRL02 disk (unit n)
RK06 disk (unit n)

DMn

RK07 disk (unit n)
RP04IRP05IRP06IRM02!
RM03IRM05 or RM80
disk (unit n) at 176700
CSR
TUI0ITEI0 and TS03
magnetic tape
TU161TE161TU451TU"I7
magnetic tape

DMn

DBn

70+n

DBn

MTn

MMn

TSll or TU80 magnetic
tnpe

MSn

l\I[SCP devices1at
1'72150 CSR

DUn

TMSCP devices 2at
174500 CSR

MUn

I--MSCP devices include the RA60, RA80, RA81, RA82, RC25, RCF25, and RX50 disk drives.
2--TMSCP devices include the TK50, TU81, and TU81-PLUS tape drives.

EJM873-YA Procedure
If the BM873-YA RestartILoader is on the system, perform the following steps:
1. Move the CPU Console ENABLEIHALT switch to its HALT position and back

to its ENABLE position.
2. Set the CPU Switch Register to one of the following values:
773010 for RK05 disk cartridge
773050 for TU10tTE10ITS03 magnetic tape
3. Press the CPU LOAD ADRS switch.
4. Press the CPU START switch.

Bootstrapping the Distribution Medium

307

BM873-YB Procedure
If the BM873-YB RestartlLoader is on the system, perform the following steps:
1. Move the CPU Console ENABLElHAL1r switch to its HALT position and back
to its ENABLE position.
2. Set the CPU Switch Register to one of the following values:
773030 for RK05 disk cartridge
773320 for RP04, RP05, RP06, RM02, HM03, RM05, or RM80 disk pack
773032 for RK05 disk unit specified in the Switch Register
773322 for RP04, RP05, RP06, RM02, HM03, RM05, or RM80 disk unit
specified in Switch Register
773110 for TU10ITE10/TS03 magnetic tape
773150 for TU16lrE16ITU45ITU77 magnetic tape
3. Press the CPU LOAD ADRS switch.
4. If necessary, set the CPU Switch Register to the unit number of the disk drive
being bootstrapped.
5. Press the CPU START switch.

H324 Pushbutton Panel Procedure
If the system includes the H324 Pushbutton Panel option for the BM873
RestartILoader, perform the following stepfJ:
1. Move the CPU Console ENABLElHAL1r switch to its HALT position and back
to its ENABLE position.
2. 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.

MR11-DB Procedure
If the MR11-DB Bulk Storage Loader is OIll the system, perform the following
steps:
1. Move the CPU Console ENABLElHAL1r switch to its HALT position and back
to its ENABLE position.
2. Set the CPU Switch Register to one of the following values:

773110 for RK05 disk cartridge
773136 for TU10lrE10ITS03 magnetic tape
3. Press the CPU LOAD ADRS switch.
4. Press the CPU START switch.

BM792-YB Procedure
If the BM792-YB Hardware Loader is on the system, perform the following steps:
1. Move the CPU Console ENABLEIHALT switch to its HALT position and back
to its ENABLE position.
2. Set the CPU Switch Register to 773100.
3. Press the CPU LOAD ADRS switch.
308

Bootstrapping the Distribution Medium

4. Set the CPU Switch Register to 777406 for RK05 disk cartridge.
5. Press the CPU START switch.

M9301-YA and M9301-YB Procedures
If the M9301·YA or M9301·YB Bootstrap Tenninator is on the system, perfonn
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 tenninal. It then prints a
dollar sign ($) prompt.
2. In response to the prompt, type the two-character device code and the unit
number of the device to be bootstrapped. Tenninate your response by pressing
the~key.

Table 29 describes the device codes.
Table 29:

Device Codes for' M9301-YA and M9301-YB Bootstraps

Device

Code

TU10ITE10ITS03 Magnetic Tape

TU16ITE161TU451TU77 Magnet.ic Tape l

MM
DK

RK05 Disk Cartridge
RP04IRP05IRP06IRM02IRM03IRM05IRM80
Disk. Packlat 176700 CSR

l-M9301-YB Bootstrap Terminator only.

IVl9301-VC Procedure
If the M9301-YC bootstrap is on the system, perfonn the following steps:
1. Move the CPU ENABLEIHALT switch to its HALT position and back to its

2.
3.
4.
5.
6.
7.

ENABLE position.
Set the start address of 17765000 in the console switches.
Press the CPU LOAD ADDR 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 30 lists the device codes.
Make sure that switches 7 through 21 are off (down).
Press the CPU START switch.

Bootstrapping the Distribution Medium

309

Table 30:

Device Codes for M9301-YC Bootstrap

Device

Code

TUI0ITEI0ITS03 Magnetic Tape

RK05 Disk Cartridge

RK06 Disk Cartridge

TU16ITE161TU451TU77 Magnetic Tape
RP04IRP05IRP06IRM02IRM03IRM05IRM80
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 d.etected, 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.
1b continue in this case, press CONT. 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:
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, the Stack
Pointer, and R5 at the console terminal. It then prints a dollar ($) prompt.
2. In response to the prompt, type the two-character device code and the unit
nwnber of the device to be bootstrapped. Terminate your response by pressing
the I RETURN I key.
Table 31 lists the device codes.
Table 31:

310

Device Codes for M9301-YF Bo,otstrap

Device

Code

TUI0ITEI0ITS03 Magnetic Tape

TU16ITE161TU451TU77 Magnetic Tape

RK05 Disk Cartridge

RK06 Disk Cartridge

RP04IRP05IRP06IRM02IRM03IRM05IRM80
Disk Pack at 176700 CSR

Bootstrapping the Distribution Medium

IM9312 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.
Table 32 shows the ROM arrangement for the M9312 Bootstrap Module.
Table 32:

M9312 ROM Arrangement

CPU ROM
BOOT #1 ROM
BOOT #2 ROM
BOOT #3 ROM
BOOT #4 ROM

If the M9312 BootstraplTerminator is on the system, perform one of the following
procedures:
•

If you have the M9312 console emulator on your system, follow the procedures
in the section Using the M9312 Console Emulator (PDP-111S0s and PDP11170s usually do not ha.ve 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 M9312 will boot, perform the procedures in the section Determining
the M9312 Bootstrap ROM Configuration.

•

If you have a CPU equipped with switch registers, know what device ROMs
are on the .M9312 Bootstrap Module, but do not have a console emulator,
follow the procedures in the section Bootstrapping With the M9312.

•

If you do not have the M9312 BootstraplTerminator Module on your system
and need to boot the RLO 1, RL02, or the RK07 disk device, perform the
manual load routine described in the section Load Program Bootstrap for the
RL01IRL02 and RK07.

Using the M9312 Console Emulator

The M9312 console emulator can be initiated in two ways depending on the type
of CPU (pushbutton or switch register) on the system.
1. Pushbuttol) boot procedures with the M9312 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 (@).

Bootstrapping the Distribution Medium

311

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 the IRETURN I key. If the unit nUInber is not entered, it is assumed to be
zero. Table 35 contains the device codes.
Successful completion of these pushbutton bootstrap procedures produces
header information on the console tenninal, similar to the following example:
Performing limited hardware scan.
RSTS V9.7 (MTO) INIT V9.7-11
Installing 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 M9312 console emulator.
Move the CPU console ENABLEIHALT switch to its Halt position, then back
to its ENABLE position.
Set the CPU switch register to 765020.
Press the start switch. The bootstrap prints the contents (in octal) of registers
RO, R4, the Stack Pointer, and 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 the ~ key. If the unit number is not entered,
it is assumed to be zero. Table 35 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 terminall, similar to the example given for the
pushbutton bootstrap. Mter the message appears, begin the system installation
process in Phase 2, Prepare System Disk.
Determining the M9312 Bootstrap ROM Configuration

If you do not know the M9312 ROM configuration, it can be determined by using
Tables 33 and 35 and performing the instructions that follow Table 33.
Table 33:

312

ROM Locations

ROM Address

ROM Location

765774
773000
773200
773400
773600

Diagnostic ROM

Bootstrapping the Distribution Medium

ROM 1
ROM 2
ROM 3
ROM 4

Repeat the following steps for each of the ROM addresses shown in Table 33.
After you 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 34 lists the M9312 bootstrap ROM configurations.
Tab~e 34:

M9312 Bootstrap ROM Configuration

ROM Location

Bootable
Device

Device Mnemonic

Diagnostic ROM

ROM!
ROM 2
ROM 3
ROM 4

If you do not know the M9312 ROM configuration, use Tables 33, 34, and 35 and
follow these instructions:
1.
2.
3.
4.

Select a six-digit ROM address from Table 33.
Set the CPU switches to the selected number.
Press the LOAD ADRS 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.
5. Match the octal number represented in the CPU data register with the octal
data number shown in Table 35.
6. Locate the device mnemonic in Table 35 and the device name associated
with the matching number. The ROM you have just investigated can boot
the device(s) you located in Table 35. Write the retrieved device information
from Table 35 with the appropriate ROM location in Table 34. For example,
if you selected a six-digit. ROM address for ROM 1 from Table 33, place the
device mnemonic and name you located in Table 35 with ROM 1 in Table 34.
Documenting the ROM configuration in Table 34 will prevent performing the
above procedure again.

Bootstrapping the Distribution Medium

313

Table 35:

Device Name and Mnemonic

Device to Be Booted

Mnemonic

Unit

Octal Data

RL01

0-3

042114

RK06IRK07

0-7

042115

rum 1

0-1

042130

RX02

0-1

042131

RP04IRP05IRP06

DB
DBI

0-7

RM02IRM03IRM05IRMSO at
CSR 176700
RK05

0-7

042113

TU16ITE161TU45ITU77

0-7

046515

TU10ITE10ITS03

0-7

046524

TS11ITUSO

0-3

046523

TK50/I'US1/I'US1-PLUS
(TMSCP devices) at CSR 174500

046525

~60~SO~S1~S2

0-7

042125

Console Emulator CPU ROM

N/A

040460

Diagnostic ROM

N/A

041060

RC251RX50IRCF25 (MSCP controller devices) at CSR 172150

PDP-1l/60170

1777762
xxx7773

I_Type DB rather than DR if you are booting the RM02, RM03, or RM05 disk.
2_This is a continuation ROM of a multiple ROM boot.
3-Bad ROM or NO ROM present.

Mter you have detennined the ROM confi~~ration, perform the procedures in
the previous section, Using the M9312 Console Emulator, if you find you have
a console emulator; otherwise, perform the procedures in the following section,
Bootstrapping With the M9312. It explainl3 how to bootstrap with the M9312
module using a switch register controlled CPU.
Bootstrapping with the M9312

The following procedure describes how a device is bootstrapped when the M9312
bootstrap ROM configuration is known. Table 36 provides the data needed to
bootstrap a device.
1.

2.
3.
4.
5.
6.
7.

314

Locate the name of the device to be booted in Table 36.
Determine from the ROM configuratiol1l in Table 34 the location (ROM 1/2/3/4)
of the device boot ROM.
Select the three-digit Switch Register Code (SWR) from Table 36 for the
particular ROM location.
Move the CPU console EnablelHalt 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 (8WR) selected from Table 36 in CPU switches
0-8, as shown in Table 37.

Bootstrapping the Distribution Medium

8. Set the unit number of the boot device in CPU switches 9-11 (see Table 37).
9. Press the CPU START switch.
Successful completion of this process boots the device. A message, simi1ar 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.
Performing limited hardware scan.
RSTS V9.7 (MTO) INIT V9.7-11
Installing RSTS on a new system disk? <Yes>

Table 36:

Switch Register Codes (SWR)
Switch Register Code (SWR)

Device to Be Booted

ROM 1

ROM 2

ROM 3

ROM 4

RLOllRL02

012

212

412

612

RK06IRK07

012

212

412

612

RXOI

012

212

412

612

RX02

012

212

412

612

RP04IRP05IRP06IRM02IRM03
IRM05IRM80 at CSR 176700

056

256

456

656

~80~81~82~60IRC25ntK50

012

212

412

612

TK50trU81trU81-PLUS
(TMSCP devices) at CSR 174500

012

212

412

612

RK05

012

212

412

612

TU16fI'E161TU451TU77

012

212

412

612

TU10fI'E10fI'S03

012

212

412

612

(MSCP controller devices)
at CSR 172150

Table 37:

Console Switch Register Settings

15·12

11·09

08·00

Octal Unit Number

Switch Register Code (SWR) from Table D-8

lLoad Program Bootstrap for the RL01/RL02 and RK06/RK07
1b bootstrap an RL01, 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-11134. 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.
2. Set address 1000 in the console register by using the numbered console
buttons.
3. Press the LAD (load address) button.
4. Press the CLR button to clear the register.

Bootstrapping the Distribution Medium

315

5. Load the contents that appear in Table 38 into memory, using the numbered
buttons and the DEP button. Press thH CLR button after you have placed the
contents in the CPU register and presEled the DEP button.
Table 38:

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

Bootstrap Routines for the RL01/RL02 and the RK06/RK07
RLOIIRL02
Bootstrap Routine
Contents

RK06IRKo7
Bootstrap Routine
Contents

12700
174400
12760
13
4
12701
42
10110
105710
100376
12760
177601
4
5721
10110
105710
100376
12760
177400
6
5060
4
62701
6
10110
105710
100376
5710
100001
0
5007

12700
177440
12760
01
10
12701
2003 s
10110
105710
100376
12760
177400
2
62701
16
10110
105710
100376
5710
100001
0
5007

l-Select drive number 0-7 for the RK07
2-Load 4 for unit 0, 404 for unit 1, 1004 for unit 2, and 1404 for unit 3.
s-Load 3 for RK06:

316

Bootstrapping the Distribution Medium

Mter the contents are loaded, perfonn the following steps:
Place address 1000 in the console register again by using the numbered
buttons.
2. Press t.he CPU LAD (load address) button to load the address.
3. While holding the CTRL button down, press the START button on the CPU to
boot the device.
4. 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 RL01IRL02 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 elToneous contents.
1.

L.oad Program Bootstrap for the TU10, TE10, or TS03
1b bootstrap a TU10ITE10ITS03 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. You can only boot
unit O.
1b load the routine, perfonn the following steps:
1. Move the CPU Console E:NABLEIHALT Switch to its HALT position and back
to its ENABLE position.
2. Set the CPU Switch Register to 010000.
3. Press the CPU LOAD ADRS switch.
4. 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
010001

010040
010042

005000
005007

Bootstrapping the Distribution Medium

317

5. Set the Console Switch Register to 010000.
6. Press the CPU LOAD ADRS switch.
7. 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.

Bootstrap Procedures for the 11/73, 11/83, or 11/84
The following procedure describes how to bootstrap the J-11.
1. To bootstrap the J-11, move the toggle switch on the front panel to the
"Restart" position.
2. The bootstrap code will execute a processor and memory self-test.
Testing in progress - Please wait
Memory Size is 4088 K Bytes
9 Step memory test
Step 1 2 3 4 5 6 7 8 9
Message 04

Entering dialog mode

3. At this point, type the command "BOO~r" and press the I RETURN I key.
Commands are Help, Boot, List, Setup, Map and Test.
Type a command and then press the I RETURN I key:

4. The bootstrap code will then ask for thle name of a device to boot. Enter the
device name and unit number, such as "MUO." (It is not necessary to enter a
colon as part of the name.)
Enter device name and unit number then press the

key:

Note: If an error message is printed, either the bootstrap doesn't know how
to boot that particular device or the device is defective. Call Field Service for
assistance.
5. If the bootstrap does read the device, it will verify that it is a bootable volume
and start the device.
Trying MUO
Starting system from MUO

318

Bootstrapping the Distribution Medium

Appendix E
A~dditional System Installation-Related Programs

This section contains programs you may need to use during your installation or
update. It also contains programs related to patching RSTSIE code. The BUILD
program performs system installation-related tasks. The DSKCVT program
converts a disk to RDS1.2 format and converts passwords for security purposes.
The ONLPAT program allows you to patch binary code.

Using tlhe BUILD/PATCH Program
The BUILD program installs some layered products and application software.
The !PATCH 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>.
1b use the valious BUILD functions, you need all privileges except:
•

SYSMOD

•

: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 3 for more infomlation.
1b run BUILD, type:
$ RUN UPDATE$:BUILD

BUILD then asks the following questions:
BUILD V9.7-11 RSTS V9.7-11
Input device <SY:> ?
Output device <SYO:> ?
Control File is ?
Function (Build/Patch, Patch, Build) <Build/Patch> ?
Patch file input location <PATCH$:>

.!*** BUILD Complete ***
!*** Processing ended on 13-Jun-89 at 11:13 AM ***

During most installations, BUILD asks additional questions 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 <SY:>: ? <file name>=MMO:/DET

Note that the Input device? prompt also accepts a !DOS or IANSI qualifier.

Using the DSKCVT Program
The DSKCVT (Disk Convert) utility converts VB.O and older disks to the new
V9.0 RDS1.2 format and converts passwords. Specifically, DSKCVT performs the
following functions:
•

Convert RDSO.O disks to RDS1.2 formalt

•

Convert RDS1.1 disks to RDS1.2 formslt

•

Convert accounts with "LOOKUP" pas~Jwords to "NOLOOKUP" at any time,
on any RDS1.2 disk (optional)

1b run DSKCVT, you must start with a diElk 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 blockEl of
free space for conversion.)
DSKCVT accepts either logically mounted or logically dismounted packs.
However, the pack should not be in use when you rWl DSKCVT. 1b verify that
no one is using the pack, DSKCVT dism01;mts and remounts it at the start of
processing.
The following is an example of the DSKCVT program:
$ run auxlib$:DSKCVT
DSKCVT V9.3-03 RSTS V9.7-11 SYSTEM:
Disk to convert? DMO:

** CURRENT DISK ATTRIBUTES **
Disk:
Label:
Level:

DMO:
V97
1.1

Convert accounts to NOUSER <NO>?
Convert passwords to NOLOOKUP <YES>?
Display accounts <YES>?
Proceed (YES or NO)? YES
Converting disk DMO: to level 1.2
Account [ 0,1 ] converted
Account [ 0,3 ] converted
Account [ 0,16 ] converted
Account [ 0,200] converted
Account [ 1,1 ] converted
Account [ 1,2 ] converted
Account [100,100] converted
Account [207,1 ] converted

320

Additional System Installation-Related Programs

...

converting disk DMO: passwords to NOLOOKUP •..
Account [ 0,1
password is already NOLOOKUP
Account [ 0,3 ] is a NOtJSER account
Account [ 0,16] is a NOtJSER account
Account [ 0,200] is a NOtJSER account
Account [ 1,1 ] password is invalid (contains 1's)
Account [ 1,2 ] password is already NOLOOKUP
Account [100,100] password is already NOLOOKUP
Account [207,1 ] password is already NOLOOKUP

Disk

DMO: conversion completed on 13-Jun-89 at 10:39 AM

In the example, DMO: is the disk pack to convert to RDS1.2. When you type
DM{]): 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. 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.
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 RDS1.1. The second pass
converts the RDS1.1 pack to RDS1.2.
In converting RDS1.1 disks toO 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 cl'eating the privilege attribute block, DSKCVT uses the following rules:
•

For account [1,1], it assigns all privileges, except EXQTA

•

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

Additional System Instaliation·Related Programs 321

Using the ONLPAT Program to Patch RSTS/E Binary Code
You still have to use ONLPAT to make emergency corrections, as directed by the
RSTS / E Release Notes and the RSTS / E Software Dispatch articles.
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 comnland file. Not all patches can be
installed with ONLPAT. See the Software Dispatch article for restrictions and
further information.

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 ONLPAT gets
the patch information.
If you enter a command file name, ONLPAT uses the command to make the
corrections. When you press the ~ key, ONLPAT assumes the patch
information comes from the keyboard. ONlLPAT expects keyboard input when you
enter a file name followed by an equal sign (=) symbol. This indicates you want
ONLPAT to create a log file of the patch. l"he 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.8YS. Unlike the PATCH option, ONLPAT does
not install a patch until you enter a circumflex-C (J\C) at the end of the last
line in the patch. Do not press CTRUC 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.
1b install a published patch, you must first look in the RSTS / E Maintenance
Notebook or the RSTS / E 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
Command file name?
File to patch? RSTS.SIL
File found in account [0,1]
Module name? GAR
Base address? CIA
Offset address? 5522
Base
Offset Old
New?
131322 005522 122700 ? 22700
131322 005524 000216 ? 46216
131322 005526 001403 ? 1003
131322 005530 010003 ? 10300
131322 005532 020001 ? "'c
Patch complete
1 patch installed

(Invoke the ONLPAT program)
(P:cess return here for manual patching)
(Give the name of the program to patch)
[A confirmation from the system]
(Proceed exactly as in patch. Be sure
th.at you verify that the numbers in the
Ba:ge, Offset, and Old columns match the
numbers in the patch. Note that if a
printed patch includes ? characters,
do not check for matching.)
(Type Circumflex-C to exit)
[Confirmation by the system]
[Additional confirmation]

Note that the instructions for installing off-line patches are slightly different;
read the patch instructions for more infornlation.

322

Additional System Installation-Related Programs

Table 39 lists and describes the types of responses ONLPAT accepts in the
program dialogue.
Table 39:

Responses to ONiLPAT 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 a combination of alphanumeric characters up to 6 characters long 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 parentheses to group portions of an
expression.

~E1or

Advance to the next location without altering the contents of the current
location.

11!O@O!!@J
key

circumflex

Return to the previous location without altering the contents of the current
location.

CTRI.JZ

Enter CTRUZ to return to the previous question.

CTRI.JC

Enter CTRUC to abort all patching and return to the program prompt.

ONLPAT Dialogue Questions

COMMAND FILE NAME?

User Action: 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 ~ or I LINE FEED I 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.

Additional System Installation-Related Programs

323

FILE TO PATCH?

User Action: Press the RETUR?\T 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 RSTS / E Maintenance
Notebook or the RSTS / E Software Dispatch article.
MODULE NAME?

User Action: Enter the module name included with the patch described
either in the RSTS / E Maintenance Notebook or the RSTS / E Software
Dispatch article.
BASE ADDRESS?

User Action: Type the base address included with the patch described
either in the RSTS / E Maintenance Notebook or in the RSTS / E Software
Dispatch article.
OFFSET ADDRESS?

User Action: Type the offset address included with the patch described
either in the RSTS / E Release Notes article or the RSTS / E 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 nwnber, symbol, or expression as described in Table E-l.
Use the information described above and the following procedures to apply
patches manually:
1. Gather the articles that contain the patches you need. You can find the
articles either in the RSTS / E Maintenance Notebook or the RSTS / E

Software Dispatch.
2. 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:
a. Press the RETURN key to enter the patch manually from your terminal.
b. 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.
c. You then answer the remaining O!'rLPAT dialogue questions, following
the instructions in the RSTS / E M(lintenance .Notebook or the RSTS / E
Software Dispatch. Remember that ONLPAT does not install the patch
until you type "C (not CTRUC) to end the program. Typing "C is entirely
different than entering CTRUC: "C ends the patch successfully; CTRUC
stops execution of ONLPAT without making any patches.
d. 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.

324

Additional System Installation-Related Programs

1b install a patch with a command file:
1. Create a command file. See the section, Building ONLPAT Command Files.
2. Run the ONLPAT program by typing RUN $ONLPAT, and then pressing
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
IBxecutes 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.
4. When ONLPAT finishes processing, the program displays a summary of the
:patches installed and any patches skipped, and then returns to your keyboard
:monitor.

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

Additional System Installation-Related Programs

325

Building ONLPAT Command Files
Create ONLPAT command files as follows::
1. Run ONLPAT from any logged-in ternlinal by typing RUN $ONLPAT. The
program then displays the COMMAND FILE NAME? question.
2. Respond to the command file question in the following fOrnlat:

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.
3. Press the RETURN key after you finiBh 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 RSTS / E Maintenance Notebook or
the RSTS / E Software Dispatch articlel.
After creating the command file, you may want to modify it. If modifications are
necessary, apply the following rules:
•

End each individual command in the patch by pressing RETURN.

•

When ONLPAT executes the command. file, the program changes all lowercase
characters to uppercase and reduces all tabs and spaces to a single space.

•

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

•

You must include a line that specifies the file you want to patch. The fOrnlat
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.

•

Subsequent ~ommand lines in a patch are identical to the formats used in
the RSTS / E Software Dispatch or the RSTS / E Maintenance Notebook. The
following command line is optional, bu.t must appear with spacing exactly
as shown in the RSTS / E Software Dispatch or the RSTS / E Maintenance
Notebook articles:
BASE

OFFSET

OLD

NEW?

Also, do not use any parenthetical comments.
•

You must use the following notation:
I\Z

326

is a circumflex, then Z; or CTRlr/Z

I\C

is a circumflex, then C; not CTRUC

IQ:I

is the LINE FEED key

Additional System Installation-Related Programs

Appendix F

Mixed Disk Drives on the Same Controller
RSTSIE V9.7 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. The RP04IRP05IRP06 drives all use
the RHll interface (RH70 for PDP-11170s). 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 RK07 Drives on the Same Controller
The RK06 and RK07 drives use the RK6ll and RK7ll 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
RK6ll controllers need an ECO to have this capability.)

Mixing RL01 and RL02 Drives on the Same Controller
The RLOl and RL02 drives use the RLll or RLV12 controllers. 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 RSTSIE monitor distinguishes which type of
disk is on a given controller and uses it appropriately.

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-11170s) or the RHll interface (for other PDP-lls). The RM03,
RM05, and R.M80 disks only use the RH70 interface and are supported only on
PDP-ll170 systems.
On a PDP-11170 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 RSTSIE 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
1b use hoth 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 bootistrap 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 na:me used for RP disks) or DR' (the nalne
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 1type of drive.

Mixing RM02/RM03/RMOS/RM80 and RP04/RPOS/RP06 Drives on the
Same Controller
It is possible to mix RM02IRM03IRM05fRl\i[80 drives with RP04IRP05IRP06
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-11/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 10we:3t nwnbered 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. The RSTSIE monitor can detennine the identity of the disks, although
the naming scheme is not obvious.

Multiple RH Controllers for the Same Type of Disk
RSTSIE 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 ahove arrangement is as follows: the drives interfaced
at the standard CSR address are known by the device name that corresponds
to the lowest nwnbered drive type (DB or DR). The dlives interfaced at the
nonstandard CSR addresses are known by the other name.

328

Mixed Disk Drives on the Same Controller

I~andom 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 cOlTesponds to the lowest numbered drive type, and the
RH at the nonstandard CSR address gets the other device name.

E~ooting Mixed RM02/RM03/RM05/RM80 and RP04/RP05/RP06 Disks
RSTS/E supports mixed RP and RM disk 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.

~~voiding Bootstrap Conflicts
Because of possible bootstrap conflicts, DIGITAL does not recommend configuring
systems that contain both RP03 and secondary CSR RH11/70 disk drives.

Mixed Disk Drives on the Same Controller

329

Index
A

Accept defaults?
explanation, 41
general configuration question, 41
possible responses, 42
Accept defaults? (update)
explanation, 148
general configuration question, 148
possible responses, 148
Accept Disk defaults?
disk interface configuration question, 43
explanation, 43
possible responses, 43
Accept Peripheral defaults?
explanation, 47
peripheral interface configuration question, 47
possible responses, 47
Accept Software defaults?
explanation, 53
possible responses, 53
software configuration question, 53
Account base?
DSKINT question, 30,213
explanation, 31,213
possible responses, 31,213
use with accounts [1,1] and [1,2], 31, 213
use with system disk, 31
Account creation
using CHEATEIACCOUNT command, 82,83
Account [0,'1]
directory listing, 297
Account [1 ,~~]
setting password on update, 156
AC line frequency, 179
50 Hz, 179
60 Hz, 179
specifying, 231
Address space
gap, 2EI5
A kit
contents, 16
type of HSTS/E distribution kit, 16
Any memory allocation changes?
explanation, 264
possible responses, 264
START question, 264
Auxiliary Library package
directory'listing, 303
Auxiliary rUIl-time system
number of general small buffers, 202
use of g,eneral small buffers, 202

BACKUP program
comparison with SAVRES, 251
number of general small buffers, 204
BADB.SYS
adding blocks, 249
Bad block file (BADB.SYS)
adding blocks, 249
definition, 1,24,207
Bad blocks
during RESTORE, 253
BADS, REFRESH suboption, 249
Bads?
BADS question, 249
explanation, 249
possible responses, 249
Base?
possible responses, 248
REFRESH FILE question, 248
BASIC-PLUS
FIS feature, 72
FPP feature, 72
installing, 72
log functions feature, 73
math precision question, 73
matrices feature, 74
optional features, 73
print using feature, 73
string arithmetic feature, 74
trig functions feature, 73
BASIC- PLUS package
directory listing, 302
BASIC- PLUS RTS name?
explanation, 72
installation question, 72
possible responses, 72
BASIC-PLUS run-time system
size constraints, 73
supplied by DIGITAL, 2
Binary code
ONLPAT patching, 322
Block number?
possible responses, 249
REFRESH BADS question, 249
BM792-YB loader, 308
how to bootstrap with, 308
BM873 restart/loader, 308
how to bootstrap with H324 pushbutton panel, 308
BM873-YA restart/loader, 307
how to bootstrap with, 307

Index-1

BM873-YB restart/loader
how to bootstrap with, 308
BOOT
BOOT error messages, 177
INIT.SYS program option, 177
Boot device:
BOOT prompt, 177
possible responses, 177
Bootstrap
definition, 18
instructions in example installation, 18
Bootstrap record
definition, 18, 305
Boot unit:
BOOT prompt, 177
possible responses, 177
BUFFERS
memory allocation table suboption, 197
use with data space, 197
BUilD
privileges required, 319
running, 319
BUilD/PATCH program, 319

c
Card decode?
explanation, 49
peripheral devices configuration question, 49
possible responses, 49
CCl command definitions
number of FIP small buffers, 202
number of general small buffers, 202
use of FIP small buffers, 202
use of general small buffers, 202
CD11 card reader?
explanation, 48
peripheral devices configuration question, 48
possible responses, 48
Central processor unit console switches
bootstrapping a device, 306
Cluster, definition, 26
Cluster size?
DSKINT question, 30,212
explanation, 30,212
possible responses, 212
use with account [1,1], 30,212
use with account [1,2], 30, 212
use with system disk, 30
Cluster sizes
device cluster sizes and total device, 29, 211
device cluster sizes and total device sizes, 29,
211
for disk packs, 27,209
Command file
building for ONlPAT, 326
modifying, for patches, 326
Command file mode
using ONlPAT in, 322
Command format
for SHUTUP, 88, 133, 164
Configuration questions
definition, 37
explanation of default responses, 37
Configuration rules
recommendation, 285

Index-2

Configure a monitor
definition" 37
Console emulator
activating hardware bootstrap loader, 305
to bootstrap a device, 306
Console switch register
explanation, 232
settings, 315
using, 232
Console terminal
definition, 17, 18
Contents of messages
number of general small buffers, 203
use of exllended buffers, 203
use of general small buffers, 203
Controller
booting mixed RM and RP type disks, 329
disabling, 223
enabling, 225
resetting eSR address to standard, 229
resetting vector address to standard, 229
specifying nonstandard controller address, 226
specifying nonstandard vector address, 227
support of mixed RK06 and RK07 disks, 327
support of mixed Rl01 and Rl02 disks, 327
support of mixed RM02lRM03/RM05/RM80 disks,
327
support of mixed RM and RP type disks, 328
support of mixed RM and RP type disks on
multiple, 329
support of mixed RP04/RP05/RP06 disks, 327
support of mixed type drives, 327
Controller, RH
support of multiple for same type disks, 328
Controller names
example list, 223
Controller to disable?
explanation, 223,224
HARDWR DISABLE question, 223, 224
possible responses, 223, 224
Controller to enable?
explanation, 226
HARDWR ENABLE question, 226
possible responses, 226
Controller with non-standard address?
explanation, 227
HARDWR CSR question, 227
possible responses, 227
Controller with non-standard vector?
explanation, 229
HARDWR VECTOR question, 229
Control status; register (CSR) set
definition, 226
Converting di:sk formats
with DSKGVT, 320
COPY
error messages, 142
Core memory
with interl€Iaved parity memory. 183
CPU switches;
activating hardware bootstrap loader, 18, 138,305
CPU switch register
specifying, 233
CR11/CM11 card reader?
explanatioln, 48
peripheral devices configuration question, 48
possible responses, 48

GRASH.SYS file
creating during installation, 91
definition, 242
disabled by system, 91
location, 242
size, 242
status, 242
Grash dump?
explanation, 91 , 264
for RSTS/E monitor, 91,264
GREATE/ACCOUNT command
creating accounts, 82, 83
Crystal oscillator
use with KW11-P programmable real-time clock,
180
GSR
HARDWR suboption, 227
GTRUC
abort patching (ONlPAT), 323
to terminate a patch, 322
GTRUZ
in ONlPAT, 323

[)
Data caching
definition, 193
number of extended blUffers, 193
use with extended buffers, 193
Data space
with BUFFERS suboption, 197
Date
how to change, 178
DATE
INIT.SYS pr04~ram option, 178
Date last modified?
DSKINT question, 31, 213
explanation, 31,213
possible responses, 31
use with system disk, 31
DCl run-time system
supplied by DIGITAL, 2
DDCMP line protocol
Implemented by DMC11, 49
implemented by DMP11, 49
implemented by DMR11, 49
implemented by DMV11, 49
DECnetlE software
use of extended buffers, 194
DEFAULT
INIT.SYS program option, 179
questions, 1'79
Dlefault line frequency
60 Hz, 232
Dlefault response
definition, 26
D,eletable?
explanation, 248
possible respc)Oses, 248
REFRESH FILE question, 248
Detached job
affecting number of jobs, 51
definition, 51
run with BUILD/PATCH, 320
Dt~vice designator, 19,314
definition, 18

Devices
with fixed addresses, 295
with fixed addresses and vectors, 295
with fixed vectors, 295
Device Testing package
directory listing, 300
Device vector assignments, 294
DH11 multiplexer
address considerations, 286
connected to DM11-BB modem controller, 230
declaring DM11-BB modem associations, 230
rules for connecting, 230
DH for DMO?
explanation, 231
HARDWR OM question, 231
possible responses, 231
Dial-up terminal
affecting number of jobs, 51
Directory listing
account [0,1], 297
Auxiliary Library package, 303
BASIC-PLUS package, 302
Device Testing package, 300
EDT package, 301
Error Reporting package, 300
File Restore package, 300
Help package, 298
OPSER-based Spooling package, 300
Print/Batch Services package, 300
RMS-11 package, 301
RSX Utilities package, 303
SORT/MERGE package, 303
SOURCE package, 303
SYSGEN components, 302
System Library package, 304
system program packages, 297
TECO package, 302
Unsupported Utility package, 301
DISABLE
HARDWR suboption, 223
meaning, 233
switch register position, 233
Disk
bootstrapping with BOOT, 177
calculating center, 244
converting to RDS1.2 format, 320
copying to one that contains bad blocks, 251
copying with IMAGE, 259
creating copy, 251
device designators, 19, 139
example of DSKCVT conversion, 320
for SAVE set, 251
IMAGE output as system, 259
initializing, 207
legal with IMAGE, 259
mixing different types on controller, 327
mount instructions, 17, 136
restoring, 253
Disk?
DSKINT question, 24,207
explanation, 24,245
possible responses, 24, 207, 245
REFRESH question, 245
use with system disk, 24
Disks on DB controller?
disk units configuration question, 45
explanation, 45

Index-3

Disks on DB controller? (cont'd.)
possible responses, 45
Disks on DR controller? .
disk units configuration question, 44
explanation, 44
possible responses, 45
Disk units configuration questions
definition, 43
Distribution disk
disk mount session, 17
Distribution kit
collecting, 16
order numbers, 16
types, 16
use of RSTS/E Release Notes, 16
DJ11 multiplexer
reserved address, 286

OM
HARDWR suboption, 230,231
DM11-BB modem
declaring DH 11 associations, 230
DM11-BB modem controller
connected to DH11 multiplexer, 230
rules for connecting, 230
using, 230
DMC11 'S/DMR11 's?
explanation, 49
peripheral devices configuration question, 49
possible responses, 49
DMC11 line interface
implementing DDCMP line protocol, 49
DMP11 line interface
implementing DDCMP line protocol, 49
DMR11 line interface
implementing DDCMP line protocol, 49
DMV11 's/DMP11 's?
explanation, 49
peripheral devices configuration question, 49
possible responses, 49
DMV11/DMP11 unit tributaries?
explanation, 49
peripheral devices configuration question, 49
possible responses, 49
DMV11 line interface
implementing DDCMP line protocol, 49
Double-precision
BASIC-PLUS scaled arithmetic feature, 73
DSKCVT program
convert disk formats, 320
example, 320
running, 320
work space requirements, 320
DSKINT
checking for bad blocks, 1, 24, 207
error messages, 34, 216
formatting disks, 1, 24, 207
INIT.SYS program option, 1, 24, 207
initializing disks, 1, 24, 207
writing minimum RSTS/E file structure, 1, 24, 207
Dynamic Pseudo-Keyboards
number of general small buffers, 204

E
ECC MOS memory, 183
EDT editor
to edit contents of START.COM, 85

Index-4

EDT package
directory lis~ing, 301
EMT logging
definition, 54
number of ~,eneral small buffers, 204
use of geneiral small buffers, 204
EMT logging?
explanation, 54
possible responses, 54
software tuning configuration question, 54
ENABLE
HARDWR suboption, 225
switch register position, 233
Enter new extended buffer address size?
XBUF question, 189
Erase disk?
DSKINT question, 32, 214
explanation, 32, 214
possible responses, 33, 215
ERR.SYS file
creation, 244
definition, 244
location, 244
size, 244
status, 244
ERRCPY
definition, 51
Error messages
INIT.SYS, 267
Error Reporting package
directory listing, 300
Errors
checking in software updates, 96
Example installation
characteristics, 9
dialogue summary, 99 to 106
explanation, 9
memory allocation table, 90
parity memory configuration, 183
parity regis~er usage, 183
sample SHUTU P output, 88
type of installation kit, 17
Extended buffer
definition, 190
number for data caching, 193
number for line printers, 193
storage of contents of messages, 203
use of indirect command file 110, 194
use with dSlta caching, 193
use with fll(~ I/O window turns, 194
use with line printers, 193
use with lOiaded indexes, 194
use with system logicals, 194
use with terminal logging, 194
Extended buffer address range is?
explanation, 189
possible responses, 189
Extended buffer pool
definition, 190, 199
for exampl(~ installation, 191
guidelines for allocating memory, 192
items stored in, 192
reserving memory, 188
storage of lline printer characters, 204
worksheet, 196

.---------------------------------

FilEI
bad cluster while transferring contiguous, 253
changing characteristics, 247
FilE
REFRESH suboption, 248
FilEI I/O Window Turns
use of extended buffers, 194
FilEI name?
explanation, 248
possible responses, 248
REFRESH FilE question, 248
FilEI Restore package
directory listing, 300
FilEt status table
definition, 245
example, 246
explanation, 247
listing, 245
Filn status table item
current file size, 247
file flags, 247
file name, 247
file status, 247
minimum file size, 247
required flies, 247
start logical block number, 247
FIP small buffer
definition, 53, 199
items stored in, 201,202
number for CCl command definitions, 202
number for open flies, 203
storage of CCL command definitions, 202
storage of open flies information, 202
use with update mode, 203
FII) small buffer pool
definition, 199
reserving memory, 197
types, 199
FIS?
BASIC-PLUS configuration question, 72
explanation, 72
Floating address devices .
rules, 285
FIc)ating addresses
assigning, 286
definition, 285
FIc)ating address worksheet
aid in assigning floating addresses, 286
explanation, 286
how to usn, 287
Fl4)ating instruction set
definition, 72
Fk)ating point processor
definition, 72
H::>ating vectors
definition, 285
explanation, 293
Fmmat?
considerations for specifying 0, 33, 214
DSKINT question, 32, 214
explanation, 32, 214
possible responses, 32,/214
use with system disk, 32, 214
FPP?
BASIC-PLUS configuration question, 72

FPP? (cont'd.)
explanation, 72
possible responses, 72

G
Gap length
determination, 286
General and FIP small buffer pools, 199
General small buffer
critical to system performance, 201
definition, 53, 199
items stored in, 201,202
minimum number, 201, 204
number for auxiliary run-time systems, 202
number for BACKUP program, 204
number for CCl command definitions, 202
number for contents of messages, 203
number for Dynamic Pseudo-Keyboards, 204
number for dynamic regions, 202
number for EMT logging messages, 204
number for lAT connections, 204
number for line printer characters, 204
number for message receivers list, 203
number for messages waiting to be received, 203
number for open flies, 203
number for outstanding 1/0 requests, 204
number for paper tape reader characters, 204
number for resident libraries, 202
number for sent messages, 203
number for terminal information, 203
number per job, 202
storage of auxiliary run-time systems, 202
storage of CCl command definitions, 202
storage of contents of messages, 203
storage of EMT logging messages, 204
storage of line printer characters, 204
storage of message receivers list, 203
storage of messages waiting to be received, 203
storage of open flies information, 202
storage of paper tape reader characters, 204
storage of resident libraries, 202
storage of sent messages, 203
storage of terminal-related information, 203
use with jobs, 202
General small buffer pool
created from data space, 199
created from Small buffers? question, 199
definition, 199
reserving memory, 197

H
H324 pushbutton panel option
with BM873 restart/loader, 308
Hardware bootstrap addresses, 307
Hardware bootstrap loader
BM792-YB loader, 308
BM873-YA restart/loader, 307
BM873-YB restart/loader, 308
definition, 18
M9301-YA bootstrap terminator, 309
M9301-YB, 309
M9301-YC bootstrap, 309
M9301-YF bootstrap terminator, 310
M9312 bootstrap terminator, 311
M9312 console emulator, 311

Index-5

Hardware bootstrap loader (cont'd.)
MR11-DB bulk storage loader, 308
Hardware configuration table
definition, 217
example, 218
explanation, 218
listing, 217
Hardware-related tasks
HARDWR suboptions, 217
HARDWR
declaring nonstandard address assignments, 285
declaring nonstandard vector assignments, 285
error messages, 233
explanation of messages, 225
hardware comments, 219
hardware configuration summary, 221
INIT.SYS program option, 217
list of messages, 225
HARDWR suboption? prompt
CSR question, 227
DISABLE question, 223
OM question, 231
ENABLE question, 225
explanation, 230, 232
HERTZ question, 232
possible responses, 223,225,227,229,230,231,
232,233
RESET question, 230
SWITCH question, 233
VECTOR question, 229
HARDWR suboptions
CSR, 227
DISABLE, 223
OM, 230,231
ENABLE, 225
HERTZ, 231
list, 217
LIST, 217
RESET, 229, 230
SWITCH, 233
VECTOR, 229
Help package
directory listing, 298
HERTZ
HARDWR suboption, 231
H kit
contents, 16
type of RSTS/E distribution kit, 16
How many K-words of extra buffer space?
BUFFERS question, 197
explanation, 197
possible responses, 198

1&0 versions of tasks?
explanation, 59
general configuration question, 59
possible responses, 59
1&0 versions of tasks? (update)
explanation, 150
general configuration question, 150
possible responses, 150
IDENT
INIT.SYS program option, 235
IDENTIFY
dialogue, 257

Index-6

IDENTIFY (cont'd.)
example, :257
extracting pack 10, 257
SAVRES function, 257
IMAGE
dialogue, 259
example, 259 to 262
output from, as system disk, 259
SAVRES function, 259
Indirect command file 1/0
use of extended buffers, 194
INIT.SYS
error messages, 267
INIT.SYS program
determination of interrupt vectors, 285
performing hardware configuration check, 285
update questions, 140 to 141
use of memory, 192, 205
INIT.SYS program options
BOOT, 177
DATE, 17:8
DEFAULT, 179
DSKINT, I , 24, 207
HARDWR, 217
IDENT, 2~~5
PATCH, 236
REFRESH, 239,248
START, 71,90, 161, 166,263
summary, 175
used in upgrade system installation, 109
Initialization cede, See INIT.SYS program
INSTAL.COM command file
command format, 121
definition, 38
entry points, 122
In updates, 144
preliminary questions, 38
using, 38
using to build another monitor, 121
using to install full system, 121
using to install layered product updates, 121
using to install system programs, 121
INSTAL.LOG
installation log file, 38, 70
update log file, 160
update record, 144
Installation disk
bootstrapping, 18
bootstrapping for update, 138
disk mount session, 136
mounting, 18
mounting for update, 136, 138
Installation Kit
contents, 16
updating a V9.0 through V9.6 system, 127
using for system installation, 16
Installation questions
for layered product updates, 61
for system programs, 57
Installation tape
bootstrapping, 17, 18
bootstrapping for update, 136, 138
mounting, 17, 18
mounting for update, 136, 138
Instruction and Data space
creating general small buffer pool, 199
definition, 199

Interleaved parity memory
definition, 182
Interrupt frequency?
DEFAULT question, 180
explanation, 180
for RSTS/E monitor, 180
possible responses, 180

J
Job
calculating number, 51
calculation worksheet, 52
definition, 51
detached, 51
event-driven, 242
highly interactive, 241, 242
items used In calculating number of, 51
maximum number, 52, 53
total number In example installation, 51
use of general small buffers, 202

K
Keyboard mode
ONLPAT procedures, 324
using ONLPAT in, 322
KMC-11 microprocessor
controlling 2780/3780 IBM protocol emulator, 49
controlling 3271 IBM protocol emulator, 49
controlling DUP11 line Interface, 50
KW11-L line time clock
definition, '179
KW11-P programmable real-time clock
crystal oscillator, 180
definition, 179

L
tAT connections
number of general small buffers, 204
LAT Usage
use of extended buffers, 194
Layered product
definition, 3, 61, 152
examples, 3
transferring updates, 61, 152,159,160
Layered product update questions, 152 "to 153
Line printer
number of el(tended buffers, 193
types, 48
use of extended buffers, 193
Une printer characters
number of general small buffers, 204
use of extended buffer pool, 204
use of general small buffers, 204
LIST
HARDWR suboption, 217
memory alloc:ation table suboption, 181
REFRESH suboption, 245
L.oadedindexes
use of extended buffers, 194
L.OCK
memory allocation table suboption, 184
L.ock address is'l
explanation, 184

Lock address Is? (cont'd.)
LOCK question, 184
possible responses, 184
Log file
creating with BUILD/PATCH, 320
INSTAL.LOG, 38, 70, 144, 160
!PDATE.LOG, 161
Log functions?
BASIC-PLUS configuration question, 73
explanation, 73
possible responses, 73

M
M9301-YA and M9301-YB device codes, 309
M9301-YA bootstrap terminator
how to bootstrap with, 309
M9301-YB bootstrap terminator, 309
how to bootstrap with, 309
M9301-YC bootstrap, 309
how to bootstrap with, 309
M9301-YC device codes, 310
M9301-YF bootstrap terminator, 310
how to bootstrap with, 310
M9301-YF device codes, 310
M9312 bootstrap
how to bootstrap with ROM configuration, 314
M9312 bootstrap module
description, 311
use of ROM configuration, 311
M9312 bootstrap ROM configuration, 313
how to determine, 313
M9312 bootstrap terminator, 311
how to bootstrap with, 311
M9312 console emulator, 311
how to bootstrap with, 311
pushbutton boot procedure, 311
switch register boot procedure, 312
M9312 ROM arrangement, 311
M9312 ROM configuration
how to determine, 312
MagnetiC tape
bootstrapping with BOOT, 177
device designators, 19, 139
for Save set, 251
mount instructions, 17, 136
Mandatory patch
definition, 96
Manual patch
disadvantages, 96
if you make a mistake, 96
when to apply, 96
Master File Directory (MFD), definition, 28
Math precision
with BASIC-PLUS, 73
Math precision?
BASIC-PLUS configuration question, 73
explanation, 73
possible responses, 73
Matrices?
BASIC-PLUS configuration question, 74
explanation, 74
possible responses, 74
MAT statements
with BASIC-PLUS, 74
Maximum jobs?
expl.lnation, 53

Index-7

Maximum jobs? (cont'd.)
possible responses, 53
software tuning configuration question, 53
Memory
allocating to extended buffer pool, 192
example of cache parity error, 186
extended buffer pool, 190, 199
four examples of memory failure, 185
list of lock restrictions, 185
locking, 184
monitor, 190, 199
nonvolatile, 233
parity, 183
unlocking, 186
USER, 190,199
Memory allocation table
definition, 181
explanation, 182
for example installation, 90, 181
for RSTS/E monitor, 90, 167, 179
how to adjust, 179
how to reset, 187
listing, 181
printed by BUFFERS, 197
printed by DEFAULT, 179
printed by LIST, 181
use with START, 264
Memory allocation table suboptions
BUFFERS, 197
LIST, 181
LOCK, 184
PARITY, 183
RESET, 188
summary, 181
UNLOCK, 186
XBUF, 190
Memory suboption?
DEFAULT question, 189
explanation, 189
use with XBUF, 189
Message send/receive code
number of extended buffers, 193
use of extended buffers, 193
Messages waiting to be received
number of general small buffers, 203
use of general small buffers, 203
MFD cluster size
definition, 28
size considerations, 28, 21 0
MFD cluster size?
DSKINT question, 28, 210
explanation, 28, 210
possible responses, 210
use with system disk, 28
Modulo 10
using with DJ11 multiplexer, 286
Modulo 20
using with DH11 multiplexer, 286
Monitor
building, 66 to 67
building an updated, 157
building online, 121
configuring, 37 to 54
install SIL, 325
overlay code patches, 325
patches to overlay code, 325
patching running, 325

Index-8

Monitor (cont'cI.)
patching with ONLPAT, 325
size restrictions, 158
SYSGEN, 35
upgrading, 109 to 118
Monitor memory
definition, 190,199
Monitor name?
explanation, 263
general configuration question, 41
possible responses, 41, 263
START question, 263
Monitor name? (update)
general configuration question, 147
possible responses, 147
MR11-DB bulk storage loader, .308
how to boo1tstrap with, 308
MSCP disk drives
possible responses, 46
types, 46
MSCP sUPPOr1t?
disk units configuration question, 46
explanation, 46
Multiple parity errors
example, 186

N
New AC line hertz?
explanation, 232
HARDWR HERTZ question, 232
possible re'sponses, 232
New controller address?
explanation, 227
HARDWR CSR question, 227
possible responses, 227
New flies first'?
DSKINT question, 31,213
explanation, 31, 213
possible responses, 31,213
use with system disk, 3 'f
New monitor name?
explanation, 41
New monitor name? (update)
explanation, 147
New vector address?
explanation, 229
HARDWR VECTOR question, 229
possible responses, 229
Nonparity memory, 183
Nonsystem di!sk
definition, 21
Nonvolatile memory
definition, 233

o
Online explanations, 9
Online system installation
definition, 3
example, 122 to 123
privileges Irequired, 121
restriction, 121
to build another monitor, 121
to install full system, 121
to install lalyered product updates,
to install system programs, 121

121

ONLPAT
command file log, 326
creating command flies, 326
dialogue questions, 323
in command file mode, 322
in keyboard mode, 322
keyboard mode procedures, 324
patching a running monitor, 325
responses to questions, 323
running, 324
up-arrow/C and CTRUC, 324
Open flies
number of FIP small buffers, 203
number of general small buffers, 203
use of FIP small buffers, 202
use of general small buffers, 202
OPSER-based Spooling package
directory listing, 300
Optional software
definition, 3, 152
examples, 3
job number considerations, 51
Optional software kit
examples, 16
using for system installation, 16
3271 or 2780/3780 simultaneous links?
explanation, 50
peripheral devices configuration, 50
possible responses, 50
Outstanding 1/0 requests
number of general small buffers, 204
O"erlapped seek'?
disk units configuration question, 44, 45
explanation, 44,45
possible responses, 44,45
use with RK05 disk, 44
use with RK06lRK07 disk, 44
use with RL01/RL02 disk, 44
use with RM02lRM03/RM05/RM80 disk, 45
use with RP04lRP05/RP06 disk, 45
Overlapped seek driver
definition, 44, 45
OVR.SYS file
creation, 244
definition, 244
location, 244
size, 244
status, 244

Packages to install?
explanation, 150
possible resp()nses, 150
system program question, 150
Pl!lck cluster size
considerations, 26, 208
definition, 26
Pl!lck cluster size?
DSKINT question, 26, 208
explanation, 26,208
possible responses, 27, 209
use with system disk, '26, 208
P,ack 10
definition, 25
extracting with SAYRES, 257

Pack ID?
DSKINT question, 25, 208
explanation, 25
possible responses, 26
use with system disk, 25
Pack label information
definition, 25
printed by DSKINT option, 25, 208
Paper patch
installed by manual patching, 96
Paper tape reader
number of general small buffers, 204
use of general small buffers, 204
PARITY
memory allocation table suboption, 183
Parity error
example, 185, 186
Parity memory
definition, 182
listing configuration, 183
Parity memory configuration
explanation, 183
for example installation, 183
listing, 182
Parity register usage
in example installation, 183
Parity type codes
list, 183
meaning, 183
Patch
applied manually, 324
installed to programs, 324
modifying command file, 326
published in RSTSIE Software Dispatch, 322
terminate, 322
to monitor overlay code, 325
PATCH
INIT.SYS program option, 236
IPATCH qualifier
BUILD command, 319
Patterns?
DSKINT question, 32, 214
explanation, 32, 214
use with system disk, 32
Peripheral devices configuration questions
definition, 47
Pre-extend directories?
DSKINT question, 29, 211
explanation, 29, 211
possible responses, 30,211
use with system disk, 29
Preferred clock?
DEFAULT question, 179
explanation, 179
for RSTS/E monitor, 179
possible responses, 180
Print/Batch Services package
directory listing, 300
Printers?
explanation, 48
peripheral devices configuration question, 48
possible responses, 48
Print using?
BASIC-PLUS configuration question, 73
explanation, 73
possible responses, 74

Index-9

Proceed?
DSKINT question, 33, 215
explanation, 33,215
possible responses, 33, 215
use with system disk, 33
Pseudo keyboard
affecting number of jobs, 51
PUB, PRI, or SYS?
DSKINT question, 30,212
explanation, 30,212
possible responses, 30, 212
use with system disk, 30, 212
Pushbutton boot procedure
with M9312 console emulator, 311

Q
Quota information
use of extended buffers, 195

R
RC25 controller, 46
RDS1.2 format
converting to, 320
Read-Only?
DSKINT question, 31, 213
explanation,' 31,213
possible responses, 31,213
use with system disk, 31, 213
Really add logical block to BADB.SYS?
possible responses, 249
REFRESH BADS question, 249
Rebuild?
explanation, 246
possible responses, 246
REFRESH question, 246
use with system disk, 246
Rebuild disk
definition, 246
REFRESH
error messages, 239
INIT.SYS program option, 239,248
REFRESH suboption? prompt
explanation, 246, 248, 249
possible responses, 248, 249
use with BADS, 249
use with FILE, 248
use with LIST, 246
REFRESH suboptions
BADS, 249
FILE, 248
LIST, 245
summary, 239
Reserved locations
vector assignments, 228
RESET
HARDWR suboption, 229
memory allocation table suboption, 188
Resident library
definition, 2
number of general small buffers, 202
use of general small buffers, 202
Resident overlay code
use of extended buffers, 195
RESTORE
bad blocks during, 253

Index-10

RESTORE (cont'd.)
example, 253 to 257
output used for system disk, 257
relocation of blocks, 253
restoring a RSTS/E disk, 253
save format, 251
SAVRES function, 253
Restore cyck~
definition, 183
RETURN
to accept default response, 26
RH70 BAE and CS3 addresses, 296
RH70 controller
list of addresses, 296
list of bus address extensions, 296
list of control status 3 addresses, 296
RH controller
definition, 44
RJ2780 Model 1 terminal, 50
RJ2780 software
definition, 50
installing, 66
memory for extended buffer pool, 195
mounting installation media, 66
mounting installation media for update, 157
updating, 157
use of exltended buffers, 195
RJ2780 support?
explanation, 50
peripheral devices configuration question, 50
possible responses, 50
RK05's?
disk units configuration question, 43
explanati<>n, 43
possible responses, 43
RK05 disk system
definition, 43
RK06/RK07's?
disk units configuration question, 44
explanation, 44
possible responses, 44
RK06/RK07 disk system
definition, 44
RK06 and RI(07 disks
mixing on same controller, 327
RK06 bootstrap procedure
without M9312 bootstrap module, 315
RK07 bootstrap procedure
without M9312 bootstrap module, 315
RLO 1IRL02's?
disk units configuration question, 44
explanation, 44
possible responses, 44
RL01/RL02 disk system
definition, 44
RLO 1 and RL02 disks
mixing on same controller, 327
RL01 bootstrap procedure
without M9312 bootstrap module, 315
RL02 bootstrap procedure
without M9312 bootstrap module, 315
RM02lRM03/RM05lRM80 disks
mixing on same controller, 327
RM and RP type disks
booting mixed on same controller, 329
mixing on multiple controllers, 329
mixing on same controller, 328

RM and RP type disks (cont'd.)
mixing on separate controllers, 328
RMS-11 package
directory listing, 301
ROM configuration
determination, 311
how to bootstrap a device, 311
use with M93 '12 bootstrap module, 311
ROM locations, 313
RP04lRP05/RP06 disks
mixing on same controller, 327
RODX1 controller, 46
RC)oX2 controller, 46
RODX3 controller, 46
RSTS/E file structure
definition, 1, 24, 207
Group File Directory (GFD), 1, 24, 207
Master File Directory (MFD), 1, 24, 207
User File Directory (UFO), 1, 24, 207
RSTS/E monitor
building, 66 to 67
building online, 121
changing defaults, 179
configuring, 37 to 54
definition, 2
starting, 90, 166, 263
updating, 156 to 158
upgrading, 109 to 118
RSTSIE Release Notes
contents, 16
contents of V9.7 installation disks, 17
contents of V9.7 installation tapes, 17
using for system installation, 16
using for system update, 127
RSTSIE Software Dispatch
contents, 16
use during system installation, 16
use with mandatory patches, 96
RSTSIE System Installation and Update Guide
how to use, 5
RSTSIE System Manager's Guide
contents, 16
use during system installation, 16
RSX run-time system
supplied by DIGITAL, 2
RSX Utilities package
directory listing, 303
RT11 run-time system
supplied by DIGITAL, 2
Run-time system
definition, 2
examples, 2
RX01/RX02's?
explanation, 48
peripheral devices configuration question, 48
possible responses, 48
RX11 flexible diskette system
definition, 48
RX211 flexible diskette system
definition, 48
RXV11 flexible diskette system
definition, 48

SATT.SYS base?
DSKINT question, 28, 210

SATT.SYS base? (cont'd.)
explanation, 28, 210
possible responses, 28,210
use with system disk, 28
SATT'SYS file
definition, 28, 210
position, 28, 210
rebuilt by REFRESH, 246
SAVE
format, 251,253
SAVE set, 253
extract label information from, 257
identify, 251
recreate disk from, 253
SAVE set name
default name, 251
SAVE volume
SAVRES, 251
SAVRES
comparison with BACKUP, 251
definition of terms, 251
errors, 252
functions, 251
I DENTI FY dialogue, 257
IDENTIFY example, 257
IMAGE dialogue, 259
IMAGE example, 259 to 262
IMAGE function, 259
like disks, 251
nonselective backup, 251
RESTORE dialogue questions, 254
RESTORE example, 253 to 257
RESTORE function, 253
RESTORE output as system disk, 257
running on line, 252
save set, 251
SAVE set name, 251
save volume, 251
summary information, 252
types of messages, 252
using, 251
Scaled arithmetic
with BASIC-PLUS, 73
Sent messages
number of general small buffers, 203
use of general small buffers, 203
SHOW BUFFERS
DCl command, 201
SHUTUP program
command format, 88, 133, 164
explanation, 88, 133
list of questions, 133
possible responses to questions, 88, 133, 164
questions, 88, 164 to 165
running, 88, 133, 164
sample output, 88, 133, 164
shutting down current monitor, 133
shutting down SYSGEN monitor, 88, 163
to shut down SYSGEN monitor, 164
Sil (Save Image Library)
patch installed, 325
restrictions to instan, 325
Size?
possible responses, 248
REFRESH FilE question, 248
Small buffer
See FIP small buffer pool

Index-11

Small buffer (cont'd.)
See general small buffer pool
definition, 53
Small buffer pool
list of considerations, 197
worksheet, 206
Small buffers?
creating general small buffer pool, 199
explanation, 53
possible responses, 54
software tuning configuration question, 53
Small buffer table
printed during system installation, 199
2780/3780 software
use of extended buffers, 195
Software tuning configuration questions
definition, 53
SORT/MERGE package
directory listing, 303
installing, 75
SOURCE package
directory listing, 303
START
activating RSTS/E monitor, 90
changing memory allocation table, 264
crash dump file, 264
error messages, 90,91, 167,263,264
INIT.SYS program option, 71,90,161,166,263
list of operations, 264
questions, 166 to 168
to activate RSTS/E monitor, 166,263
to change crash dump, 91, 167
warning messages, 90,167,263
START.COM command file
editing, 84
use in timesharing, 84
Statistics
use of extended buffers, 195
String arithmetic?
BASIC-PLUS configuration question, 74
explanation, 74
possible responses, 74
Supersede existing monitor?
explanation, 41
Supersede existing monitor? (update)
explanation, 147
SWAP.SYS file
definition, 241
location, 241
size, 241
status, 241
SWAPO.SYS file
creation, 242
definition, 242
location, 242
status, 242
SWAP1.SYS file
creating, 242
creating during installation, 65
creating during update, 157
definition, 241
location, 242
status, 241
SWAP3.SYS file
creation, 243
definition, 242
location, 242

Index-12

SWAP3.SYS file (cont'd.)
status, 242
use with Etvent-driven jobs, 242
Swap file
optional, 242
SWAP.SYS, 241
SWAPO.SYS, 242
SWAP1.SYS, 241
SWAP3.SYS, 242
SWAP max?
explanatio,n, 90, 263
for RSTS/E monitor, 90,263
possible responses, 65, 156
Swap times, 243
SWITCH
HARDWR suboption, 233
Switch register?
explanation, 233
HARDWR SWITCH question, 233
possible responses, 233
Switch register boot procedure
with M9312 console emulator, 312
Switch register codes, 315
Switch register contents
logical positions, 233
Switch register position
DISABLE, 233
ENABLE, 233
VOLATILE, 233
SYSGEN components
directory listing, 302
SYSGEN monitor
how to shut down, 88, '164
legal device unit numbers, 22
starting, :35
temporary RSTS/E monitor, 2
SYSTAT program
IF switch, 201
to display number of small buffers, 201
System code
patching, 236
System disk
copying fIII9S for update, 140
definition, 21
initializing, 24
initializing with DSKINT, 1,24
physically mounting, 22
System flies
creating, 240
creating additional, 64
creation summary, 241
creation worksheet, 245
definition, 64
list, 240
space con:siderations, 240
System installation
concepts, 1
definition, 1
example, 99 to 106
flowchart, 13
online, 3
to build a new RSTS/E monitor, 3
to upgrade· a RSTS/E monitor, 3
upgrading a pre-V9.1 RSTS/E system, 109
System Library package
directory 1i:3ting, 304
System logicals

System logicals (cont'd.)
use of extended buffers, 194
System program
definition, 56
directory listing, 297
examples, 3
how to update, 149
installing, 57
list, 56
logical names, 94, 149
purposes, 3
repositioning, 94
transferring updates, 159 to 160
System startup file
editing, 81
START. COM, 84
System update
flowchart, 129
restriction, 170
to build another monitor, 170

TS11ITK25ITSV05ITU80's? (cont'd.)
possible responses, 48
TS11 magnetic tape system
definition, 48
TU1 0ITE1 01TS03's?
explanation, 47
peripheral devices configuration question, 47
possible responses, 48
TU10ITE10ITS03 magnetic tape system
definition, 47
TU10 bootstrap procedure
without hardware bootstrap loader, 317
TU161TE16ITU45ITU77's?
explanation, 47
peripheral devices configuration question, 47
possible responses, 47
TU161TE16ITU45ITU77 magnetic tape system
definition, 47
TU80 tape drive
use in example installation, 18

u
lrable suboption?
DEFAULT question, 179,181,183,184,186,188,
197
explanation, 179,181,183,184,186,188,197
for RSTS/E monitor, 179
possible responses, 181,183,184,187,188,189,
197
use with BUFFERS, 197
use with LIST, 181
use with LOCK, 184
use with PARITY, 183
use with RESET, 188
use with UNLOCK, 186
lrape
device designators, 139
mount instructions, 17, 136
lrE 10 bootstrap procedure
without hardware bootstrap loader, 317
TECO package
directory listing, 302
Template monitc)r
definition, 146
using for update, 147
Terminal logging
use of extended buffers, 194
Terminals
affecting number of jobs, 51
number of general small buffers, 203
use of general small buffers, 203
Terminal session
explanation, 9
TMSCP tape drives?
explanation, 48
peripheral devices configuration question, 48
possible responses, 48
Trig functions?
BASIC-PLUS configuration question, 73
explanation, 73
possible responses, 73
TS03 bootstrap procedure
without hardware bootstrap loader, 317
TS 11ITK25fTSV05lTU80's?
explanation, 48
peripheral devices configuration question, 48

UDA50 controller, 46
Unit?
DSKINT question, 24,208
explanation, 24, 246
possible responses, 25,246
REFRESH question, 246
use with system disk, 24
UNLOCK
memory allocation table suboption, 186
Unlock address is?
explanation, 187
possible responses, 187
UNLOCK question, 187
Unsupported Utility package
directory listing, 301
Update
how to perform, 127
kit labels, 127
performing a selective, 170
preliminary questions, 144
selective example, 171 to 172
Update, selective
full system, 170
layered products, 170
monitor, 170
system programs, 170
UPDATE.COM
command format, 170
entry points, 170, 171
example using, 171
explanation, 170
using for selective updates, 170
using for updates, 170
UPDATE.LOG
update record, 161
Update mode
FIP small buffer considerations, 203
Updating software
error checking, 96
reference documents, 127
Upgrade system installation
flowchart, 11 0
how to perform, 113
INIT.SYS options used in, 109

Index-13

Upgrade system installation (cont'd.)
list of steps, 113
steps for multiple removable disk systems, 116
steps for no multiple removable disk systems, 113
Use previous bad block info?
OSKINT question, 31,213
explanation, 31,213
possible responses, 32, 214
use with system disk, 31
User account
creating, 81, 82, 83
Use resident library version? (update)
explanation, 151
possible responses, 151
system program question, 151
User file directory (UFO)
definition, 30
USER memory
definition, 188, 190, 199
Use template monitor?
explanation, 40
possible responses, 40
Use template monitor? (update)
explanation, 147
Yes response, 147

Index-14

v
V9.7 Installation Kit
contents, 16
using for system installation, 16
VECTOR
HAROWR suboption, 229
Vector addres~~
definition, 228
Vector assignrnents
list of reserved locations, 228
VOLATILE
switch regi::;ter position, 233

w
Wkit
contents. 16
type of RSTS/E distribution kit,

x
XBUF
See also e:dended buffer pool
creation by INIT.SYS, 188
memory allocation table suboption.

190

Read~er' 5 Conlments

RSTS/E
System Installation and Update Guide

AA-2669J-TC

Please use this postage-paid form to comment on this manual. If you require a written reply to a software
problem and are eligible to receive one under Software Performance Report (SPR) service, submit your
comments on an SPR form.
Thank you for your assistance.

I rate this manual's~
Accuracy (software works as manual says)
Completeness (enough information)
Clarity (easy to understand)
Organization (structure of subject matter)
Figures (useful)
Examples (useful)
Index (ability to find topic)
Page layout (easy to find information)

Excellent

Good

Fair

Poor

0
0
0
0
0
0
0
0

I would like to see more/less

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page
Description

Additional comments or suggestions to improve this manual:

I am using Version _ _ _ of the software this manual describes.

Name/Title

Dept.
Date

Company
Mailing Address
Phone

I
I
I

- -

Do Not Tear - Fold Here and Tape

-------------------~lllr-------;~~;;~---'
in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
POST AGE WILL BE PAID BY ADDRESSEE

Digital Equipment Corporation
Corporate User Publications
Continental Boulevard
MK01-2/E12
Merrimack, New Hampshire 03054

111 ..... 11. II .... 1111 •• 1.11.1111.1111 .. 1.1 ••• 1.11111
. - - Do Not Tear - Fold Here - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -