Digital PDFs

AA-H352B-TK

May 1981

342 pages

Original

12MB

Document:	RSX-20F Nov81
Order Number:	AA-H352B-TK
Revision:	0
Pages:	342
Original Filename:	AA-H352B-TK_RSX-20F_Nov81.pdf

OCR Text

TOPS-10/TOPS-20
RSX-20F
System Reference Manual
AA-H352B-TK

Novem ber 1981

This reference manual describes RSX-20F, the operating
system that runs on the PDP-11 140 front-end processor of
KL-based computers. RSX-20F loads the KL microcode,
configures main and cache memory, loads the boot program,
and performs diagnostics. For systems that are running
TOPS-20, as well as for 1091 systems, RSX-20F also provides
device handling for unit record equipment.
This manual is a revision and replaces the RSX-20F System
Reference Manual, order number AA-H352A-TK.
OPERATING SYSTEM:

TOPS-10
TOPS-10
TOPS-20

ReI. 7.01
ReI. 7.01
ReI. 4.0

(1080/90)
(1091 )
(2040/50/60)

SOFTWARE:

R8X-20F
R8X-20F
RSX-20F

VA14-45
VE14-45
VB14-45

(1080/90)
(1091 )
(2040/50/60)

Software and manuals should be ordered by title and order number. In the United States. send orders
to the nearest distribution center. Outside the United States. orders should be directed \0 the nearest
DIGITAL Field Sales Office or representative.

Western Region

Northeast/Mid-Atlantic Region

Central Region

Digital Equipment Corporation
PO Box CS2008
Nashua, New Hampshire 03061
Telephone:(603)884-6660

Digital Equipment Corporation
Digital Equipment Corporation
Accessories and Supplies Center Accessories and Supplies Center
1050 East Remington Road
632 Caribbean Drive
Schaumburg, Illinois 60195
Sunnyvale, California 94086
Telephone:(312)640-5612
Telephone:(408)734-4915

digital equipment corporation. marlboro. massachusetts

First Printing, January 1980
Revised, November 1981

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

(S), 1980, 1981, Digital Equipment Corporation.
All Rights Reserved.

'rhe postage-prepaid READER'S COMMENTS form on the last page of this
document requests the us~r's critical evaluation to assist us in
preparing future documentation.
'rhe following are trademarks of Digital Equipment Corporation:
DEC
DECUS
Digital Logo
PDP
UNIBUS
VAX

DECnet
DECsystem-lO
DECSYSTEM-20
DECwriter
DIBOL
EduSystem

lAS
MASSBUS
PDT
RSTS
RSX
VMS
VT

CONTENTS

PREFACE
CHAPTER 1
1.1
1.1.1
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1. 7
1.1.8
1.1.9
1.2
1.2.1
1.2.2
1.2.3
1.2.4
1.3
1.4
1.5
CHAPTER 2
2.1
2.2
2.2.1
2.3
2.4
2.5

INTRODUCTION
THE PDP-II .
•••••
The UNIBUS .
..•.•
The I/O Page .
• • • •
Vector Interrupts
.
Priorities • . .
Traps . • . . . .
Data Transfers . .
General Registers
. •
Stacks . . • . . . .
Instruction Set
.
RSX-11M OPERATING SYSTEM . . .
Directives • . . • • •
Device Drivers. . • •
Significant Events . . . . .
Mapped and Unmapped Systems
TASKS
. • . . . . . . • . . .
RSX-20F REQUIREMENTS . • • • .
THE DERIVATION OF RSX-20F FROM

•••••.• ••.
.
• • • • • • .
. . . • . . . . • .
. . . . ••
..
. .••....
. . . . . . . . . .
. . . . . . . . . .
.
. . . . . • • . • .
. . . . . . . . . .
. . . . • .
.
. ••••
. • •
. . . .
. . . ..
. . . . . . . • . .
• . . . • . . . . .
RSX-11M
....

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

GENERAL DEFINITIONS
. . . . . . . . . . . . . . .
FILES-II FILE SPECIFICATION • . . . . . . . . . .
Files-II File Structure . . . .
. . • . .
FILES-II DIRECTORIES .
......•.....
FIXED FILE ID'S . . • . . . . . . . . . . . . • .
FCS FILE STRUCTURE . . . •
.....•.
.

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

FILES-II SYSTEM

CHAPTER 3

RSX-20F GLOSSARY OF TERMS

CHAPTER 4

PARSER

4.1
4.2
4.3
4.3.1
4.4
4.5

ENTERING AND EXITING THE PARSER . . . . . . . . . 4-1
PARSER COMMAND SYNTAX
. . . . . . . . . . . 4-2
PARSER CONSOLE MODES .
. 4-4
PARSER Help Facility . . . . • . . . . . . . . . 4-4
PARSER COMMANDS
. . . . . . . . . . . . . . 4-6
PARSER ERROR MESSAGES . . . . . . . .
4-29

iii

CONTENTS (Cont.)

CHAPTER 5
5.1
5.2
5.3
5.3.1
5.3.2
5.3.3
5.3.4
5.4
5.4.1
5.4.2
5.4.3
5.4.3.1
5.4.3.2
5.5

CHAPTER 6
6.1
6.1.1
6.1.2
6.1.3
6.1.4
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.3
6.3.1
6.3.2
6.3.3
6.3.4
6.4
6.4.1
6.4.2
6.4.3
6.4.4
6.4.5
6.5
6.5.1
6.5.2
6.5.3
6.5.4
6.6
6.6.1
6.6.2
6.6.3
6.6.4
6.7
6.7.1
6.7.2
6.7.3
6.7.4
6.8
6.8.1
6.8.2
6.8.3

KLINIT
KLINIT LOAD AND START . . . . . . . . • .
· . 5-6
KLINIT OPERATOR DIALOG •
. . . . . . . . . • • 5-- 7
KLINIT MESSAGES
. . . . •
5-17
Informational Messages .
• • • • ••
5 -1 7
Warning Messages . . . .
· . . . ..
5-;18
Dialog Error Messages
· . . . ..
5-120
5-20
System Error Messages
REPORTS RELATING TO THE KLINIT DIALOG
5-32
External Memory Maps .
. . . .
5-32
Internal Memory Maps .
. . . .
5-33
Microcode Verification Error Reports . . . • .
5-35
CRAM Error Report . . . . . . • . . . . •
5-35
DRAM Error Report
..... .
5-36
KLINIT DIALOG EXAMPLES .
5-36
RSX-20F UTILITIES
COP UTILITY
. • • . . . .
Function .
· . . • • . . .
Format . .
. • • • • •
Examples .
• • • • • •
Error Messages .
INI UTILITY
Function .
Format . . .
Examples • .
• •
Error Messages .
• • • • • • • •
MOU AND DMO
·
Func t ion . . . .
· .
Format • • . .
· •
Examples . • . . . • . • . • •
Error Messages .
. ••.....
PIP - PERIPHERAL INTERCHANGE PROGRAM .
Function • . . • • • • • .
Initiating PIP . . . • . .
PIP Command String Format
PIP Switches and Subswitches .
PIP Error Messages .
RED . . . .
Function .
Format.
Examples .
Error Messages .
•
SAV
Function .
. . • . . • .
Format . . . . . . . • .
Example . . . . • . • .
Error Messages •
UFD - USER FILE DIRECTORY
Function .
Format.
• • • • •
Examples
Error Messages .
ZAP . . • • .
Function • • .
. . • . . .
Invoking and Terminating ZAP .
ZAP Switches .
. • • •
iv

. . . . . . 6-1
. . . . . . 6-1
• • • • • • 6- 2
•

•

6- 2

· • .

. . 6-3
· . 6-4
. . . 6-4
. 6-5

•

6- 6

• • • • • • 6- 6
. • .•
6-9
•.
. . 6-9
• • •
6-10
6-10
• • • ••
6 -11
6-12
· . ..
6-12
6-12
· . ..
6-12
· . . ..
6-13
· . •.
6-19
6-23
6-23
6-23
· . ..
6-24
• • • ••
6 -2 4
6-24
. . . •.
6 - 24
6-25
· . ..
6-26
6-26
6-29
· . ..
6-29
• • • ••
6- 29
• • • ••
6 -3 0
• • • ••
6 -3 0
6-31
6-31
. • ..
6-31
. . . ..
6-32

CONTENTS (Cont.)

6.8.4
6.8.4.1
6.8.4.2
6.8.5
6.8.5.1
6.8.5.2
6.8.5.3
6.8.5.4
6.8.5.5
6.8.5.6
6.8.5.7
6.8.5.8
6.8.6
6.8.6.1
6.8.6.2
6.8.6.3
6.8.7
6.8.7.1
6.8.7.2
6.8.7.3
6.8.8
CHAPTER 7
7.1
7.2
7.3
7.4
7.4.1
7.4.1.1
7.4.1.2
7.4.1.3
7.4.1.4
7.4.2
7.4.2.1
7.4.2.2
7.4.2.3
CHAPTER 8
8.1
8.2
8.2.1
8.2.2
8.2.3
8.3
8.3.1
8.3.2
8.3.3
8.3.4
8.4
8.4.1
8.4.2
8.5

Addressing Locations in a Task Image • • . . .
ZAP Addressing Modes: Absolute and Task Image
Addressing Locations in Task Image Mode
The ZAP Command Line . . • • .
Open/Close Location Commands •
General Purpose Commands . . . • .
Using the Carriage Return
ZAP Internal Registers • . .
. . • .
ZAP Arithmetic Operators..
. .•.
ZAP Command Line Element Separators
The Current Location Symbol
. . .•
Formats for Specifying Locations in ZAP Command
Lines . . . . . . . . . • . . . . . .
Using ZAP Open/Close Commands
. . . . . . . .
Opening Locations in a Task Image File .
Changing the Contents of a Location
Closing Task Image Locations . . . . . .
Using Zap General Purpose Commands . . .
The K Command: Compute Offset and Store it in
the Quantity Register . . • . . . . . .
The 0 Command: Display Branch and Jump
Displacement from the Current Location .
The = Command: Display the Value of an
Expression . . • .
ZAP Error Messages

6-32
6-33
6-33
6-34
6-35
6-36
6-36
6-36
6-37
6-37
6-38
6-38
6-39
6-39
6-39
6-40
6-42
6-42
6-43
6-43
6-43

RSX-20F MONITOR
RSX-20F EXECUTIVE
. . . .
· . . . . 7-1
TASKS AND SCHEDULING .
. . . . • • • • • 7- 5
SYSTEM TRAPS . .
.....•.
. 7-8
TERMINAL SERVICE ROUTINES
• . . . .
7-10
Modem Handling . • . . .
· . . . ..
7 -10
Modem Handling Concepts • . . . . • • • • • •
7 -10
Terminal Driver Routine • . • . .
7-11
Modem Timeout Routine
• • • • ••
7 -13
The CTY and DL-IIE Timeout Routine .
17-15
Terminal Handling . • . •
7-16
Character Input Routine
• • . . . . . . . . .
7-16
Terminal Timeout Routine .
. . . . . . .
7-20
Character Output Routine •
....... .
7-23
DTE-20 OPERATION
DTE-20 COMMUNICATIONS REGION •
DTE REGISTERS
. . . . .
DTE-20 Status Word . . • . . .
Diagnostic Words . . . . .
DTE-20 Data Transfer Registers •
USING THE DTE-20 REGISTERS .
Deposit and Examine
Transfer Operations
. . . . .
Doorbell Function
Diagnostic Functions .
PROTOCOLS . . . . .
Secondary Protocol .
Primary Protocol.
QUEUED PROTOCOL
• •
v

· . . . • 8-1
• . ..
8-10
• • • ••
8 -10
· . . .
8-15
· . •.
8-19
8-22
· . ..
8-22
• • • ••

· . ..
• • • ••
•

•

••

8 -2 3

8-29
8-29
8-29
8-29
8 -30
8 -30

CONTENTS (Con t. )

8.6
8.6.1
8.6.2
8.6.3
8.6.4
8.6. 5
8.6.6
8.6.7
CHAPTER 9
9.1
9.2
9.3
9.3.1
9.3.2
9.3.3
9.3.4
9.4
CHAPTER 10
10.1
10.2
10.2.1
10.2.2
10.2.3

8-33
8-33
8-34
8-34
8-35
8-36
8-36
8-36

DTE-20 DRIVER LOGIC . . . . . . .
TO-I0 Direct Packets . . . . . .
TO-II Direct Packets . . . . . .
TO-I0 Extended Direct Packets
TO-I0 Indirect Packets .
TO-II Indirect Packets . . . . .
Register Conventions . . . . .
DTE-20 Device Driver Functions.
ERROR DETECTION AND LOGGING
THE KEEP ALIVE COUNT .
KLERR . . . . . . .
.
ERROR LOGGING . . . . • •
KL Error Logging .
PDP-II Error Logging .
TKTN MESSAGES
KLERR MESSAGES .
LOGXFR . . . . . .

· . .
. . .
•

•

.
.

. .
. .

•

.
. . . . . .
· . . . . . .
• • • • • • •

. • . 9-1
. . 9-1

•

• 9- 2

•

9-2
9-7
9-7
9- 8
9 -10

USING FEDDT
INTERPRETING AN RSX-20F DUMP .
..•.
Useful Data in Dump Files . . . • .
Sample Dump Analysis .
.....•.
Front End Status Block .
....•. ·

10-1
10-4
10-5
10-7
. 10-10

•

. • . .
•.
. . . .
• • • •
•

.
.
.
•

ERROR DEBUGGING

APPENDIX A

RSX-20F STOP CODES AND I/O ERROR CODES

APPENDIX B

FILE TRANSFERS BETWEEN TOPS-I0/TOPS-20 AND RSX-20F

B.l
B.l.l
B.l.2
B.2
B.2.1
B.2.2
B.2.3
B.2.4

REFORMATTING FILES . . .
· B-1
Restrictions . . . . . . . . •
· . . . B-2
RSXTI0/RSXFMT Commands •
....
· . B-2
TRANSFERRING FILES .
. . • .
· B-4
Running FE . . . . • .
...•
· . B-4
• • • • • • • B- 5
The FE: Device . . . . . • . •
• • • •
• B- 5
RSX-20F Tasks
File Transfer Dialog .
• B-5

APPENDIX C

FRONT-END TASKS

APPENDIX D

KLINIK ACCESS DIALOG

D.l
D.2
D.2.1
D.2.2
D.2.3
D.2.4
D.3
D.3.1
D.3.2

SIGNIFICANT KLINIK EVENTS
. . • . .
KLINIK ACCESS PARAMETERS . . • . . •
·
Usage of the Remote Terminal . .
Access Password for Remote CTY's .
•
KLINIK Access Window . . • . . . •
Console Mode of the Remote Terminal
OPERATOR DIALOG WITH KLINIK • . . . . . •
Setting Access Parameters . . • . . .
Examining the Current KLINIK Parameters
vi

• D-l
. • . D-l
• D-2

•

• D- 2

• D-2
· D-3
• • • • D- 4
· • D-5
· . . • D-8

CONTENTS (Con t. )

D.3.3
D.4
D.4.l
D.4.2
D.5

Terminating the KLINIK Link
REMOTE USER DIALOG wITH KLINIK
Logging In as a Remote Operator
Logging In as a Timesharing User .
KLINIK INTEGRITY OVER A REBOOT . . .

APPENDIX E

GETTING HELP ON RSX-20F

APPENDIX F

EIA PIN DEFINITIONS

•

••

. .

. D-8

. D-9
D-ll
D-ll

• D- 9

INDEX

FIGURES
FIGURE

1-1
5-1
5-2
5-3
7-1
7-2
7-3
7-4
7-5
7-6
7-7
7-8
7-9
7-10
8-1
8-2
8-3
8-4
8-5

The Front End for a KL-based Computer System
Load Switches and Switch Register for KL with
Floppy Disks
Load Switches and Switch Register for KL wi th
DECtapes
KLINIT Operator Dialog
RSX-20F Executive
RSX-20F Memory Layout
System Task Directory (S'l'D) Node
Active Task List (ATL) Node
Modem-Handling Hardware
Modem Control Algorithm
Modem Timeout Algorithm
Character Input Algorithm
Terminal Output Algorithm
Character Output Algorithm
KL Communications Region
DTE-20 Registers
DTE-20 Status Word in Read State
DTE-20 Status Word in Write State
DTE Interrupt Handler

· · · 1-2

··· · ····
· · · · 5-3
5-4
· · · · 5-13
·· · ·
···· ··
· · · · · · · · · · · · · · · 7-2
7-5
·
···· ····
· · · · 7-6
7-7
· · · · ·7-11
·
· · · ·
·
· · · · · · · · 7-12
·
7-14
· · · · · · · 7-17
·
· · · · · 7-21
·
·
7-24
··
8-2
· · · ·8-10
····
····
8-11
·
· · · · · 8-13
8-24
·····
···

TABLES
TABLE

5-1

Switch Register Bit Definitions . . . . . . . . . . 5-5

vii

PREFACE

'rhe RSX-20F System Reference Manual contains information describing
the RSX-20F front-end operating system.
RSX-20F runs on a PDP-II/40
front-end processor and communicates with either a TOPS-IO or TOPS-20
operating system running on a KL main processor.
The audience for this manual comprises Software Support Specialists,
Field Service personnel,
systems programmers, and system operators.
It is assumed that the reader is familiar with PDP-II hardware, RSX-II
operating systems, and either TOrS-IO or TOPS-20.
'rhis manual does not contain everything anyone would like to know
about RSX-20F. The information contained here was included because it
seemed to be especially important and useful to the largest part of
the audience.
Hopefully,
this information will prevent some users
from having to place calls to a central DIGITAL installation when they
need help.
The information in the manual is organized into five
parts, as follows:
Part I,
SYSTEM OVERVIEW,
introduces the PDP-II
hardware,
the
RSX-Il-based operating system, and the Files-II file structure. A
short glossary of RSX-20F terms and acronyms is also included.
Part II, SYSTEM SOFTWARE, contains a description of the PARSER
(the
front-end command processor)
and of KLINIT (the KL initialization
software), as well as operating instructions for the front-end utility
programs.
Part III, SYSTEM INTERNALS, contains information about the resident
RSX-20F monitor and the nonresident system tasks.
Communications
between the KL and the PDP-II using the DTE-20 are discussed
in
detailo
The handling of terminals,
both direct lines and dial-up
lines, is also described.
Part V, APPENDIXES, contains a list of system error messages.
The
procedure for
transferring files between the KL and the PDP-II is
described, and the front-end system tasks are listed.
The dialog
Involved in setting up a KLINIK window for remote diagnostics is
discussed.
There is also a list of information to include with
RSX-20F Software Performance Reports and hot line calls, as well as a
table of EIA pin definitions.
The following TOPS-IO and TOPS-20
manuals also contain information about RSX-20F.

TOPS-IO Operator's Guide

AA-H283A-TB

TOPS-IO Monitor Installation Guide

AA-5056B-TB

TOPS-20 Operator's Guide

AA-4176D-TM

TOPS-20 Software Installation Guide

AA-4195G-TM

Readers who wish to become more familiar with PDP-II hardware and
software can find additional material
in the following handbooks,
which contain both tutorial and reference information.
PDP-II Processor Handbook

EB 05138 76

PDP-II Software Handbook

EB 09798 78

PDP-II Peripherals Handbook

EB 05961 76

Terminals and Communications Handbook

EB 15486 79

CHAPTER 1
INTRODUCTION

Two PDP-II operating systems, RSX-llM and RSX-llD, provided the base
upon which RSX-20F was built.
These operating systems wer~ chosen
because they offered the best base for
building the required
front
end.
The KL requires a front end that:
•

Is small and efficient

•

Can handle special cases such as
diagnosing and recovering KL errors

•

Can handle the
TOPS-lO/109l

unit

record

booting

devices

the

and

TOPS-20

and

The purpose of the KL front end is to reduce the load on the KL.
Specifically,
the front end handles booting, configuring and loading
the KL, and drives the unit-record and terminal hardware.
Figure 1-1
shows a diagram of a KL-based computer system with a PDP-II front end,
including the connections that are present between the front end and
the various peripherals that it drives.
This chapter contains important concepts of PDP-II software,
explains
the needs of RSX-20F,
and describes how RSX-llM and RSX-llD were
modified to produce RSX-20F.

1-1

INTRODUCTION

RH11
]
MASSBUSCTL

LA36
CTY

SWITCH
PANEL

RK01
DUAL DRIVE3

DL11W
CTYINTERFACE

BM 873YF
ROM

RX11
FLOPPY CTL 2

Kl10

MF11
MEMORY

KD11
CPU

MEMORY
PARITY

KY11·D
CONSOLE

LINE CLOCK

DL 11·E
MODEM
INTERFACE

TO REMOTE
DIAGNOSTIC
TERMINAL
(KLINIK)

•

,----

-----,

I
I

DC20
MULTIPLEXER. • •

MAX

DC20
MULTIPLEXER

LP20
LINE PRINTER
CONTROL

COlO
CARD READER
CONTROL

II
I
I

I
I
I
I
I

I
01

[
LINE
PRINTER

CARD
READER

I
I

IL FOR
TOPS·20
SYSTEMS
__
___
_ _ _ONLY
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ .-JI

1 BMB73YH ROM ON 10BO/90
2 TC11 DECtape CTL ON 1080/90
3 TU56 DUAL DRIVE ON 1080/90

Figure 1-1

MR.S.187.79

The Front End for a KL-based Computer System

1-2

INTRODUCTION
1.1

THE PDP-II

'rhe PDP-II has several unique features that make it an easy machine to
program and use.
This section describes some of the most important of
these features.

1.1.1

The UNIBUS

The UNIBUS is a 56-line bus used to send addresses, data, and control
information to the system components and peripherals. The method of
communication is the same for every device on the UNIBUS,
including
memory and the central processor.
Each device, including memory
locations, processor registers, and peripheral-device registers,
is
assigned an address on the UNIBUS.
Thus, peripheral-device registers
can be manipulated as easily as main memory by the central processor.
The UNIBUS is both bidirectional and asynchronous;
this allows
devices of varying speeds to be connected to it.

1.1.2

The I/O Page

The I/O page is an area at the high end of memory in which all the
physical device registers are assigned an address.
The UNIBUS concept
makes this I/O page easy to access and easy to keep current,
thus
making it useful to those who wish to find out about the physical
state of the system.

1.1.3

Vector Interrupts

Vector interrupts allow the user to control interrupt handling as
easily as depositing data into memory locations.
Each device on the
UNIBUS has two words assigned to it ln low memory to handle its
interrupts.
The first word is the address of the routine to which
control is to be relinquished in the event of an interrupt.
The
second word contains the processor status word to be installed when
control is transferred to the interrupt routine.

1.1.4

Priorities

Interrupt priorities can be set individually for devices on the
UNIBUS.
Each device has a priority level on which it can interrupt.
In the processor status word, the priority level field (bits 5-7)
can
be set to a value of 0 through 7. Only devices with a priority higher
than the priority in the status word can interrupt.
The user,
therefore,
can control interrupt priorities by depositing data into
memory.

1.1.5

Traps

Both synchronous and asynchronous traps can be handled by the PDP-II.
Synchronous traps occur
immediately upon the issuance of an illegal
instruction or general trap.
They are dealt with by means of the
vectors in low memory and provide user flexibility.
Asynchronous
traps occur independently of user instructions, usually as the result
of I/O completion.
1-3

INTRODUCTION
1.1.6

Data Transfers

Data can be transferred in two ways via the UNIBUS:
a BR
(Bus
Request)
or an NPR (Non-Processor Request).
The method normally used
is the BR, in which the device wanting to use the UNIBUS must first
request the use of the bus from the bus master. An NPR parallels DMA
(Direct Memory Access) on the KL.
An NPR steals UNIBUS cycles without
directly gaining control of the processor.
Since it does not need to
access the processor, an NPR is much faster than a BR.

1.1.7

General Registers

The central processor has eight registers (0-7) for general use.
The
registers can be used as accumulators,
index registers, or stack
pointers.
Register 6is used as the system stack pointer
(SP),
and
Register 7 is used as the hardware program counter (PC).
These last
two registers can be manipulated in exactiy the same'way as the other
registers, but depositing data in them destroys the state of the
PDP-II, because the PDP-II is not able to find the next instruction or
the hardware stack.

1.1.8

Stacks

The PDP-II is a stack-oriented machine.
It contains
built-in
addressing modes designed to manipulate stacks of data.
The PDP-II
also has its own system stack, and it uses R6 as the hardware stack
pointer.

1.1.9

Instruction Set

The PDP-II instruction set operates on single- or
double-byte
operands.
Addressing on the PDP-II is by eight-bit bytes. The word
size is sixteen bits. Addressing includes a variety of addressing
modes which, when combined with the instruction set,
allow the
programmer great flexibility in programming.

1.2

RSX-IIM OPERATING SYSTEM

RSX-IIM is a PDP-II operating system.
It controls I/O, sChedules
tasks to be run,
and provides common subroutines. The resident
operating system is referred to as the Executive.

1.2.1

Directives

A directive is a request to the Executive to perform a function.
Directives
can
perform I/O functions,
obtain task and system
information, suspend and resume task execution, and cause a task to
exit.
Directives
are called EMT's
(EMulator Traps), and are
equivalent to JSYS's in TOPS-20 and UUO's in TOPS-IO.

1-4

INTRODUCTION
1.2.2

Device Drivers

A device driver is a program that ,controls physical
hardware
activities on a peripheral device. The device driver is generally the
device-dependent interface between
a
device
and
the
common
device-independent I/O code in an operating system.

1.2.3

Significant Events

A significant event is an event or condition that indicates a change
in the system status of an event-driven system. A significant event
is declared, for example, when an I/O operation completes.
A
declaration of a significant event indicates that the Executive should
review the eligibility of task execution, because the event might have
unblocked the execution of a higher priority task. The following are
considered to be significant events:

• Queueing of I/O requests
• Completing of I/O requests

• Requesting a task
• Scheduling a task
• Waking up a task
• Exiting a task
There are 64 significant event flags, most of them directly related to
servicing directives.
These flags can also be used by tasks to
communicate with other tasks.

1.2.4

Mapped and Unmapped Systems

A mapped system uses hardware memory management to relocate virtual
memory addresses.
An unmapped system has no hardware to relocate
virtual addresses into physical addresses. An unmapped system must
therefore be assembled with the correct physical addresses. RSX-20F
is an unmapped system.

1.3

TASKS

A task is the fundamental executable unit in PDP-II operating systems.
Some tasks are self-sufficient and can be thought of in much the same
way as programs in TOPS-IO or TOPS-20. Some tasks must call other
tasks
to
complete their function.
Some tasks are considered
subroutines to be called by still other tasks.
Tasks can reside in one of three places:
the resident Executive
(EXEC) partition, the general
(GEN) partition, or the Files-II
partition (FIITPD). A partitiqn is an area of memory reserved for the
execution of tasks.
In th~ simplest case, a task uses all of the
partition. If the task is smaller than the partition, the unused
space is- unavailable to other tasks. If a task is larger than the
partition, it must be written to use overlays. Overlays are sections
of code that are brought into memory as needed and are written over
existing code that is no longer required.
1-5

INTRODUCTION
Most tasks that run in the EXEC partition handle specific devices and
system functions.
These tasks are called resident tasks; that is,
they are always core resident and are not swapped out.
This is
important because system functions and devices demand instantaneous
service and should not have to wait for code to be read in from a
peripheral device.
Occasionally a task is larger than the partition
into which it must fit. This situation can be handled by overlaying
code.
Overla~ing
consists of replacing unneeded sections of code in
core with sections that are needed but are not currently in main
memory.
There are two general classes of tasks: privileged and nonprivileged.
A privileged task can access its own partition, the Executive
partition, and the I/O page. A nonprivileged task can access only its
own partition and shared regions.
When a task has been compiled, it is still not ready to be loaded and
executed.
It must be put through the Task Builder. A compiler
produces an output file called an object module.
The Task Builder
accepts object modules as input, links them together, resolves
references to global symbols and library files, and produces an output
file called a task image. In the task image file, all relocatable
expressions and external references have been converted to absolute
addresses.
The task image file can then be loaded into a partition
and executed. The Task Builder can also produce a memory map file. A
memory map describes the allocation of. storage, itemizes the separate
modules that the task comprises, and lists all global-symbol values.

1~4

RSX-20F REQUIREMENTS

The PDP-ll/40 fulfills the normal functions of a front-end computer.
It acts as a peripheral handler and data concentrator/router in its
relation with the KL. The devices that it handles are the slower,
unit record devices
(TTY, CDR, and LPT).
This allows the KL to
concentrate on computing rather than servicing interrupts from the
slower devices.
The front end can also be used for other special functions.
For
example, it can perform all the following steps necessary to get the
KL up and running:
•

Load the microcode

•

Configure memory

•

Configure cache

•

Load a bootstrap program

The front end can also perform diagnostics on
problems develop.

1.5

the

when

hardware

THE DERIVATION OF RSX-20F FROM RSX-llM

RSX-IlM is geared toward multiprogramming and quick response to
real-time
events.
The
multiprogramming capability allows the
development and use of utility programs that can perform special
tasks.
The real-time response allows any attached devices to be
servic€d quickly. For these reasons, RSX-IIM was chosen as the basis
for RSX·-20F.
1-6

INTRODUCTION
RSX-20F utility programs can be run only in the GEN partition.
Nonresident Exec routines
(for example,
Fi1es-11, KLRING, KLDISC,
SETSPD, TKTN, and MIDNIT) run in the F11TPD partition.
Only one
utility task can run at anyone time in the GEN partition and that
task runs until completion.
Some tasks use overlays.
These tasks
must control their own overlaying, however, since the Executive makes
no attempt to do so.
'The significant event scheme of RSX-11M was kept in RSX-20F to handle
changes in system states and to provide directives with information.
The directives that were kept provide I/O service,
task information
and' task control.
The scheduling algorithm used to decide which task
runs next is round robin within priority value.
Specific programs are brought into core to do special tasks.
Some of
the RSX-20F utility programs are MOUNT and DISMOUNT to control access
to Fi1es-11 devices, PIP to transfer files from one Fi1es-11 device to
another, UFD to create User File Directories on Fi1es-11 devices, and
PARSER to provide communication and diagnostic functions.
All these
tasks run in the GEN partition.
The biggest change in the structure of RSX-11M had to do with driving
the DTE-20 interface.
The DTE-20 is the only link between the front
end and the KL, and provides the interface between the KL and the
terminals, printers, and so forth.
In order to deal with all the
purposes to which the DTE-20 would be put, the operating system needed
a device driver. A queue mechanism had to be set up to handle all the
requests for the devices that the KL receives and transmits to the
front end. Consequently, the queued protocol task was added to handle
the communication between TOPS-20 and the device drivers in the front
end.
Although no inter-CPU communication can take place over the disk,
the
PDP-11 and the KL can access the dual-ported RP04/06 drive independent
of each other.
However, RSX-20F does not have access to the entire
dual-ported disk;
RSX-20F is limited to 950 pages by default (the
value can be made larger by reinitia1izing the disk) .
Logical block
number 400 is the home block for the Fi1es-11 system. TOPS-20 views
the
front-end
file
system
as
one
big
file,
<ROOT-DIRECTORY>FRONT-END-FILE-SYSTEM.BIN.
TOPS-10 also views the
front-end file system as one big file, SYS:FE.SYS.
System access to front-end files
is usually done with file ID's.
Because the front-end file system contains relatively few files, this
access method can find the files quickly. The directory structure is
kept for those few situations when users must interact with a Fi1es-11
area on floppy disk, DECtape, or dual-ported RP04/06.
No protection
checking is enforced with the file systems.
Real PDP-11 formatted disks have 16-bit words, and disk addressing and
accessing is consistent with this scheme.
However, disks supported by
TOPS-10 and TOPS-20 must be formatted in 18-bit words to make them
compatible with the 36-bit word size expected by the KL processor.
Therefore, the RSX-20F disk driver is a modified RSX-11M routine.
Each
PDP-11
word
of
data in the Fi1es-11 area is written
right-justified in the 18-bit space available.
The two left-hand
(high-order) bits are ignored by RSX-20F's disk driver.

1-7

CHAPTER 2
FILES-II SYSTEM

All RSX-based operating systems have a standard file system called
Files-II.
Users who access files in an RSX-20F Files-II system use a
syntax that is similar to TOPS-20 and TOPS-IO.
This chapter defines
some terms used by Files-II,
and describes the file structure and
directory structure used by the system.

2.1

GENERAL DEFINITIONS

The Files-II system imposes a structure on a medium.
The medium
Files-II uses is any block-addressable storage device.
This includes
such media as disks and DECtapes. Since the method of access to all
Files-II media is similar, all types of Files-II media are referred to
as disks.
A Files-II volume is a logical file structure that includes one or
more devices of the same type. A Files-II volume can be compared to a
file structure under TOPS-IO and TOPS-20.
When Files-II devices are used by a task, each device is assigned a
number called a Logical Unit Number (LUN).
LUNs are associated with
physical devices during a task's I/O operations.
The Executive can
also assign LUNs for its own use.

2.2

FILES-II FILE SPECIFICATION

The file specification for Files-II is:
dev: [g,m]filename.ext;version
where:
dev:

is the name of a physical
which the desired file
name consists of two ASCII
an optional one-digit unit

[g,m]

is the group number and member number associated
with the User File Directory (UFD).
These numbers
are octal and are in the range of I to 777.
This
section of the file specification is also referred
to as the User Identification Code (UIC).

filename

is the name of the file which can be from I
alphanumeric characters.

2-1

or logical device on
is located.
The device
characters followed by
number and a colon.

FILES-II SYSTEM
ext

is the extension of the file which can be
to 3 alphanumeric characters or null.

version

is the version number of the file which can range
from
I to 77777.
If no version number is
specified, the number defaults to the most recent
version on a read operation and the next version
number on a write operation.

from

By comparison, the TOPS-20 file specification format is:
dev:<directory>filename.type.gen
The TOPS-IO file specification format is:
dev:filename.ext[p,pn]
The quantity [g,m] is the directory number and corresponds to the
directory name in TOPS-20 and the project-programmer number in
TOPS-l O.
Two examples of valid RSX-20F Files-II file specifications are:
OBO: [5,5]KLINIK.TSK
OXl: [5,5]MIONIT.TSK;1

2.2.1

Files-II File Structure

Any data of interest on a Files-II volume is contained in a file.
A
file is an ordered set of virtual blocks, a virtual block being an
array of 512 eight-bit bytes. A file's virtual blocks are numbered
from 1 to n, where n blocks have been allocated to the file. The
number assigned to a virtual block is, of course, called a Virtual
Block Number, or VBN.
Each virtual block is mapped to a unique
logical block on the volume. Virtual blocks can be processed in the
same manner as logical blocks. Any array of bytes that is less than
65K in length can be read or written, provided that the transfer
starts on a virtual block boundary and that its length is a multiple
of four.
Each file in a volume is uniquely identified by a file 10. A file 10
is a binary value consisting of three PDP-II words (48 bits). It is
supplied by Files-II when the file is created and used whenever the
file is referenced. The three words contain:
1.

File number - This number uniquely identifies the file on the
volume.

File sequence number - This number identifies the current use
of an individual file number on a volume. The file numbers
are reused. Since the file number of a deleted file is
available to be used again, the file sequence number is
attached to distinguish the uses of the file number.

Relative Volume Number - This number must be zero.
The
location is reserved for the implementation of volume sets.

2-2

FILES-II SYSTEM
Each file on a Files-II volume is described by a
file header.
The
file header is a block that contains all the information necessary to
access the file.
The file header is contained in the volume's
index
file,
not in the file itself.
The file header is divided into four
distinct areas:
1.

Header Area - This area contains the file nu~ber and the file
sequence
number
as well as the file's ownership and
This area also contains offsets to the
protection codes.
other areas of the file header, thereby defining their size.
Finally, the header area contains a user attribute area,
in
which the user can store a limited amount of data describing
the file.

Ident Area - This area contains identification and accounting
data about the tile, including the primary name of the file,
its creation date and time,
its expiration date,
and
its
revision count, date and time.

Map Area - This area describes the mapping of virtual blocks
of the file
to logical blocks of the volume.
The area
contains a list of retrieval pointers,
each of
which
describes one logically contiguous segment of the file.
The
map area also contains the linkage to the next extension
header of the file, if one exists.

End Checksum - This area, the last two bytes of the file
header,
contain a sixteen-bit additive checksum of the
preceding 255 words of the file header.
The checksum is used
in the process of verifying that this block is a file header.

Since the file header has a fixed size while the file itself does not,
a large file could require more space for its mapping information than
is available.
To provide for
this contingency, Files-II
uses
extension headers.
An extension header is used to chain together file
headers to provide enough space for the mapping information.
The map
areas link the headers together in order of ascending virtual block
numbers.

2.3

FILES-II DIRECTORIES

Directories are Files-II files whose sole function
is to associate
file-name strings with file IO's.
Since the file IO is unique to the
file, the file IO can be used to locate the file directly in the
Files-II ~ystem.
However, most users find it easier to deal with a
qroup of files if the files can be named.
This ease of use is the
~Joal
of the directory file.
A directory file is an FCS (File Control
Services) file consisting of fixed sixteen-byte recor~s
(see Section
2.5 for a description of FCS files).
Each record is a directory entry
describing a single file.
Each entry contains the following data:
•

File IO - The three-word binary IO of the file this entry
represents
(The file number portion of the file IO is zero
when the entry is empty.)

•

Name - The name of the file, stored as three words
Radix-50 characters

2-3

three

FILES-II SYSTEM

2.4

•

Type - The file type (known also as the extension), stored aB
one word of three Radix-50 characters

•

Version - The file version number, stored in
word

binary

one

FIXED FILE ID'S

As with any file system, Files-II maintains a data structure that it.
uses to control the file organization.
The information that Files-II
needs are kept in files called known filei because the system always
knows about them..
These files are created when a new volume is
initialized.
The files have fixed file ID numbers so that Files-II
can always find its own data.
The files and their uses are described
below.

2.5

Index File - The index file is file ID 1,1,0.
It is listed
in the Master File Directory
(MFD) as INDEXF.SYS;l.
ThE~
index file provides the means for
identification of and
initial access to a files-II volume.
It also contains the
access data for all files on the volume, including itself.

Storage Bitmap File - The storage bitmap file
is file
ID
2,2,0.
It is listed in the MFD as BITMAP.SYS;l.
This file
is used to control the available space on a volume.
It
contains a storage control block with summary information
about the volume, and the bitmap itself, which lists the
availability of individual blocks.

Bad Block File - The bad block file is file ID 3,3,0.
It iB
listed in the MFD as BADBLK.SYS;l.
The bad block file is
simply a file containing a list of all the known bad blockB
on the volume.

Master File Directory - The master file directory is file ID
4,4,0.
It is listed in the MFD (itself) as OOOOOO.DIR;l.
It
lists the five known files, and all the user file directories
for the volume.

Core Image File - The core image file is file ID 5,5,0.
It
is listed in the MFD as CORIMG.SYS;l.
This file is the
bootable system image file.

FCS FILE STRUCTURE

interfacE~
FCS stands for File Control Services, which is a user-level
to Files-II.
Its principal feature is a record control facility that
allows sequential processing of variable-length records as well aBo
sequential and random processing of fixed-length records.
FCS use~:
the virtual block system provided by the basic Files-II structure.

FCS treats every disk file as a sequentially numbered array of bytes.
Records are given ordinal numbers starting with 1 for the first record
in the file.
A file consisting of fixed-length records can havE~
records crossing block boundaries or not, depending on the setting of
a flag in the file header area.
If records do cross block boundaries,
the records are simply packed end to end.
Records of an odd length
are padded with a byte of indeterminate contents.
If records do not
cross block boundaries, their size is limited to 512 bytes.

2-4

FILES-II SYSTEM
Variable-length records can be 32,767 bytes,
unless records do not
cross block boundaries,
in which case the limit is 510 bytes.
Each
record is preceded by a two-byte binary count of the bytes in the
record
(the count does not include these two bytes).
This byte count
is always word-aligned, and padded with a null byte if necessary.
A
byte count of -1 signals the end of live data in a particular block.
The next record in the file begins at the next block.

2-5

CHAPTER 3
RSX-20F GLOSSARY OF TERMS

This chapter includes definitions and expansions
phrases, and acronyms used in the manual.

several

words,

ACL
Access Control List
ACP
Ancillary Control Processor
ACK
Affirmative ACKnowledgement - the reply that indicates
that
the
receiver accepted the previous data block and that the
receiver
is ready to accept the next block
of
the
transmission.
APR
Arithmetic PRocessor
AST
Asynchronous System Trap
ATL
Active Task List
Auto-bauding
The process by which the terminal
line speed on a dial-up line.

software

determines

the

Carrier
The analog signal that carries data over telephone lines.
Carrier Transition
A transition in the state of the carrier signal, either from
"On" to "Off", or vice versa.
CC
Condition Code
CKL
ClocK List
Communications Region
An area in KL memory that is used for
coordinating status,
preparing for byte transfer operations, and passing limited
amounts of data.
Both the KL and the PDP-II have an Owned
Communications Region in which they alone can write.

3-1

RSX-20F GLOSSARY OF TERMS
CUSP
Commonly Used System Program
DEQUE
Double Ended QUEue
DIC
Directive Identification Code (0-127)
Deposit Region
A region in KL memory that is accessed by the
Protected Deposits.

PDP-II

using

DH-Il
Communications interface between the PDP-II front end and up
to sixteen terminals and sixteen modems.
Specifically a
DH-IIAD.
DM-IIBB
Communications interface between the PDP-II front end and
the EIA modem control lines. The DM-IIBB is used in the
DH-IIAD to handle asynchronous terminal lines connected to
common carrier facilities.
DPB
Directive Parameter Block
DSW
Directive Status Word
DTE-20
The hardware interface between the PDP-II and the
stands for Data Ten to Eleven.

KL.

DTE

DTL
DTE-20 List
DTR
The signal used by a computer system to answer the phone
ring from a remote user.
DTR stands for Data Terminal
Ready.
EBOX
Part of the KL hardware that performs arithmetic and logical
operations.
EMT
EMulator Trap Instruction
EPT
The area in KL memory that
transmission of data between
Executive Process Table.

is reserved for use
in
processors.
EPT stands for

Examine Region
A region in KL memory that is accessed by the
Protected Examines.

PDP-II

using

External Page
An area (4K) of real memory space (760000-777777) containing
CPU and peripheral device control and status registers (also
known as the I/O page) .

3-2

RSX-20F GLOSSARY OF TERMS
PCP
File Control Primitives
IRQ
I/O Request Queue
ISR
Interrupt Service Routine
KTII
Hardware Memory Management Optioh
LBN
Logical Block Number
Login
The process of getting a KL to recognize
(see also Logon)

potential

user

Logon
The process of getting a PDP-II
user

recognize

potential

LUN
Logical Unit Number
MCB
The software resident in a DN20 that supports
stands for Multifunction Communications Base.

DECnet.

MCB

MCR
Monitor Console Routines
MFD
Master File Directory
MRL
Memory Request List
Normal Termination
The term Done is
An error-free completion of a given task.
not used because, unlike a Done flag, a Normal Termination
flag is not set if an error occurs.
An error causes the
Error Termination flag to be set.
NXM
Non-eXistent Memory
Owned Area
An area in the Communications Region that is for the use of
the related processor.
The related processor can read and
write to and from this area.
Packet
A group of bytes including data and control elements that is
switched and transmitted as a composite whole.
Privileged Front End
A PDP-II attached to a KL by means of a DTE-20 that can use
the
diagnostic
bus
and do unprotected deposits.
A
privileged front end can crash the KL.

3-3

RSX-20F GLOSSARY OF TERMS
Protected Examines/Deposits
An Examine or Deposit that is range-checked by the KL.
ThE~
relocation and protection for
the Examine operation i~:
separate from that for the Deposit operation. A privileged
front end can override the protection checks;
a restricted
front end cannot override the protection checks.
(See also
Relative Address)
PUD
Physical Unit Device Table
Relative Address
An address specified by the PDP-II software on a Protected
Examine or Deposit. The address specified by the PDP-II is
relative to the Examine or Deposit Region, and runs from 0
to the maximum relative address (which is kept by the KL in
the EPT).
(See also Examine Region, Deposit Region, EPT)
Restricted Front End
A PDP-II that is attached to a KL by means of a DTE-20 and
cannot crash the KL if the KL hardware and software an~
working correctly. A restricted front end cannot use the
diagnostic bus, and cahnot read KL memory unless the KL has
first set up the interrupt system to allow it.
RTS
A signal sent from the Data Terminal Equipment (in this case
the DTE-20)
to the Data Communications Equipment (DeE) to
condition the DCE for
transmission.
Since all terminal
communication is full-duplex, the local modem should always
be ready to transmit when a user is dialed in.
Thus,
RTS
should always be asserted by the PDP-II for active dial-up
lines.
RTS stands for Request to Send.
Send-All
Data that is sent to every active line on the system that
has not refused it. An obvious example is a system message.
SPR
Software Performance Report
SST
Synchronous System Traps
STD
System Task Directory
Thread
The link word in a node.
~rpD

Task Partition Directory
UIC
User Identification Code
UFD
User File Directory
VCB
Volume Control Block
VBN
Virtual Block Number

3-4

CHAPTER 4
PARSER

The command language processor for the front-end operating system is
called the PARSER.
It is a nonresident system task and executes in
the GEN partition when it is invoked.
The PARSER is the primary means
of communications between the system operator and
the front-end
programs.
It also provides access to the KL's memory and diagnostic
registers.
The PARSER accepts
input
in the form of ASCII strings
entered at the console terminal (CTY).

4.1

ENTERING AND EXITING THE PARSER

If you are currently communicating
monitor v or a TOPS-IO or TOPS-20
(CTRL/\) to enter the PARSER.

with
job,

the TOPS-IO or TOPS-20
type a control backslash

If you are currently communicating with another RSX-20F task or
utility such as KLINIT or PIP, type a CTRL/Z to exit the current task
and then a CTRL/\ to enter the PARSER.
When you enter the PARSER, you receive one of the following prompts:
PAR)

This indicates that the PARSER is ready to accept
commands and the KL is running (that is, the KL clock
is running and the KL run flop is on).

PAR%

This indicates that the PARSER is ready to accept
commands but the KL microcode
is in the HALT loop.
(The KL clock is running but the KL run flop is off.)

PAR#

This indicates that the PARSER is ready to accept
commands but the KL clock is stopped and the KL is not
running.
NOTE
If you see the PAR# prompt displayed
during timesharing,
you should reload
the system.

If the PARSER encounters an error during its initialization, an
message precede the prompt.

error

In order to exit the PARSER, type QUIT or a CTRL/Z to return to the
TOPS-IO or TOPS-20 monitor or use the PARSER command, MCR, to load and
start another program.

4-1

PARSER
4.2

PARSER COMMAND SYNTAX

Commands to the PARSER are typed one or more to a line in response to
a PAR>, PAR%, or PAR# prompt. The rules that follow apply to all
commands you wish to type unless you are explicitly told otherwise in
the description of the command.
1.

Multiple commands can be entered on a single line.
To do
this, separate each command from the following one by a
semicolon.
For example:
PAR>EXAMINE PCiEXAMINE 20iSHUTDOWN<RET>

Command lines can be continued on the following line.
To
continue a command line on the next line, end the line to be
continued with a hyphen
(-)
and a carriage return.
The
PARSER will prompt you for the continuation line with another
hyphen.
For example:
PAR>EXAMINE PCiEXAMINE 20;-<RET>
-EXAMINE NEXT<RET>
The maximum number of characters in a command line is 280.

A comment can be added to the end of a command line or can be
an entry in itself. To insert a comment, begin the text with
an exclamation mark (and end it with a carriage return).
For
example:
PAR>CLEAR CONSOLE!RESET TO OPERATOR MODE<RET>
PAR>!THIS IS A COMMENT LINE<RET>

Terminal output can be suppressed.

To do this, type CTRL/O.

Keywords in a command can be truncated
unique abbreviation. For example:

their

shortest

PAR>H!HALT THE KL CPU<RET>
If the truncation is
message.
For example:

not

unique,

you

receive

error

PAR>RE 5<RET>
PAR -- [PARSER] AMB - AMBIGUOUS KEYWORD "RE"
In this example, the PARSER found two commands
with RE: REPEAT and RESET.

that

started

The default radix of integers
36-bit value is expected;
decimal.

Numbers can be shifted a specified number of binary places in
either direction.
To shift to the left, use an underscore
( ) between the number you wish to shift and the number of
bInary places you wish it to be shifted. This causes the
left-hand number to be shifted to the left by the number of
binary bits indicated by the right-hand number, assuming that
the right-hand number is positive. If the right-hand number
is negative,
the left-hand number is shifted to the right
that many binary places. Thus, in order to specify a number
in octal that ends in several zeros, you could write the

4-2

is octal if an address or
otherwise the default radix is

PARSER
nonzero part, then an underscore, then the number of trailing
(binary) zeros in the number. For example:
PAR>EXAMINE 2 3<RET>
results in
20/ xxx xxx xxxxxx
Note that rule #6 applies to both the
numbers.
8.

and

right-hand

Negative numbers can be specified through the use of a
minus (-) preceding the number. For example:
PAR>DEPOSIT TEN 30=-1<RET>
30/ xxxxxx xxxxxx
PAR>EXAMINE TEN 30<RET>
30/ 777777 777777

left-

unary

(deposit -1 in
loc. 30)
(previous
contents)
(examine
loc. 30)
(new contents)

Numeric values can be entered as arithmetic expressions using
addition
(+), subtraction (-), multiplication
(*), and
division (/). For example:
PAR>EXAMINE 123654+32<RET>
123706/ xxxxxx xxxxxx
PAR>DEPOSIT TEN 408-6=100<RET>
PAR>SET INCREMENT 2*3<RET>
KL INCREMENT: 6
PAR>REPEAT 8/4; EXAMINE PC<RET>
PC/ xxx xxx xxx xxx
PC/ xxxxxx xxxxxx
Note that in the evaluation of arithmetic expressions,
multiplication, division, and binary shifts take preGedence
over addition and subtraction.

10.

Relocation factors can be added or subtracted from a number.
To do this, use a single quote (') following a number to add
the PDP-II relocation factor (offset) to the number.
Use a
double quote
(")
to subtract the PDP-II relocation factor.
For example:
PAR>SET OFFSET 101204<RET>
PDP-II OFFSET: 101204
PAR>EXAMINE ELEVEN 32'<RET>
101236\ xxxxxx
PAR>EXAMINE ELEVEN 101236"<RET>
32\ xxxxxx
You can use the PDP-II relocation factor to modify KL
addresses as well as PDP-II memory addresses.

memory

When you close a command line (carriage return without a preceding
hypheh), the PARSgR first scans the command line buffer for illegal

4-3

PARSER
characters.
If it finds any, the entire command line is discarded and
the following message is issued:
PAR -- [PARSER] ILC - ILLEGAL CHARACTER "c"
where "c" is the first illegal character found.
If the command line passes the character scan, the PARSER begins to
execute the individual commands.
If the PARSER encounters an invalid
command, that command and any others remaining in the command line are
not executed.
The invalid command also generates an error message
(refer to Section 4.5, PARSER Error Messages).
I

4.3

PARSER CONSOLE MODES

rrhe PARSER command set differs according to the current console
There are three basic console modes:

mode.

OPERATOR MODE

This mode allows only those commands that
will
not
crash the TOPS-IO or TOPS-20
monitor.

PROGRAMMER MODE

This mode allows all PARSER
diagnostic functions.

commands

except

MAINTENANCE MODE

This mode
commands.

set

PARSER

allows

the

full

In addition, there is a mode called USER MODE.
Entering this mode has
the effect of exiting the PARSER and is equivalent to a QUIT command.
When RSX-20F is initially loaded, the console mode is the mode that
was in effect in the PARSER when the RSX-20F front-end module was
saved.
(refer to Chapter 6 for a description of the SAV utility.)
There is a SET CONSOLE command to change the console mode, a CLEAR
CONSOLE command to reset the mode to OPERATOR,
and a WHAT CONSOLE
command to determine the current mode.
These commands are explained
in detail in Section 4.4.

4.3.1

PARSER Help Facility

The PARSER has a built-in help facility that prints out the
list of commands for the console mode you are in.
For an example, assume you are in OPERATOR mode and type:
PAR)?<RET)
The PARSER responds:
PARSER COMMANDS ARE:
ABORT
CLEAR
DISCONNECT
EXAMINE
JUMP
MCR
REPEAT
RUN
4-4

available

PARSER

SET
SHOW
SHUTDOWN
TAKE
QUIT
WHAT
If, on the other hand, you are in PROGRAMMER mode, the response is:
PARSER COMMANDS ARE:
ABORT
CLEAR
CONTINUE
DEPOSIT
DISCONNECT
EXAMINE
HALT
INITIALIZE
JUMP
MCR
REPEAT
RESET
RUN
SET
SHOW
SHUTDOWN
START
TAKE
QUIT
WHAT
XCT
ZERO
This help facility extends to the argument level.
If you are not sure
of the arguments for a particular command, type the command followed
by a space and a question mark.
For instance, assume you are in OPERATOR mode and type:
PAR>CLEAR ?<RET>
The PARSER responds:
CLEAR COMMANDS ARE:
AUTO-TAKE
CONSOLE
INCREMENT
KLINIK
MEMORY
NOT
OUTPUT
REPEAT
If instead you are in PROGRAMMER mode, the response is:
CLEAR COMMANDS ARE:
AUTO-TAKE
CONSOLE
DATE
FAULT-CONTINUATION
INCREMENT
4-5

PARSER
KLINIK
MEMORY
NOT
OFFSET
OUTPUT
RELOAD
REPEAT
RETRY
TRACKS
Subarguments can also be determined in this manner.
example, if you type:

For

PAR>SET CONSOLE ?<RET>
The PARSER responds:
SET COMMANDS ARE:
MAINTENANCE
OPERATOR
PROGRAMMER
USER

4.4

PARSER COMMANDS

This section lists all PARSER commands.
The console mode associated
with each command specifies the minimal console mode at which the
command is available.
The following notational conventions apply to
the command format:
•

Any single argument not in brackets must be specified.

•

Uppercase arguments are keywords and must be entered as shown
or truncated according to rule 5 in Section 4.2.

•

A multiple choice list enclosed in square brackets [ ]
means
that an entry is optional.
If there is a default entry, it
is specified.

•

A multiple choice list enclosed in braces { } means that
of the entries must be specified.

one

In the following
list of commands,
those specified as requiring
MAINTENANCE console mode should be restricted to Field Service
personnel. Also, some commands require that the KL be stopped:
this
can be done with a HALT or ABORT command.

ABORT

OPERATOR
The ABORT command stops the KL by trying to force
it into the
HALT loop.
If this fails after a reasonable number of EBOX clock
ticks, the command tries to START MICROCODE, which implies a
MASTER RESET of the KL processor.
This is one way to get the KL
into a known state when a previous state left it in a hung
condition.

4-6

PARSER
CLEAR AUTO-TAKE

OPERATOR

The CLEAR AUTO-TAKE command disables the automatic
PARSER.CMD during a SNAPSHOT.

CLEAR CLOCK

NORMAL
CRAM
DATA-PATH
CONTROL
EXTERNAL
INTERNAL
MARGIN
FULL
HALF
QUARTER
SLOW

execution

MAINTENANCE

The CLEAR CLOCK command selectively resets the
KL
clock
parameters. The CLEAR CLOCK arguments function as follows:
CLEAR CLOCK NORMAL

SET CLOCK NORMAL

CLEAR CLOCK CRAM

Disables the control-RAM
clock

CLEAR CLOCK DATA-PATH

Disables the data-path clock

CLEAR CLOCK CONTROL

Disables the control logic
clock

CLEAR CLOCK

SET CLOCK NORMAL

EXTERNAL
INTERNAL
MARGIN
FULL
HALF
QUARTER
SLOW

CLEAR CONSOLE

OPERATOR

The CLEAR CONSOLE command forces the PARSER into OPERATOR console
mode.
It is the equivalent of S~T CONSOLE OPERATOR.

CLEAR DATE

PROGRAMMER

The CLEAR DATE command clears the validity bit, and prompts you
for a new date and time (see SET DATE command).
This command is
not valid if RSX-20F is in primary protocol.

4-7

PARSER
PROGRAMMElR

CLEAR FAULT-CONTINUATION

The CLEAR FAULT-CONTINUATION command disables the automatic KL
fault continuation reload.
This command prevents the host from
recovering from errors detected by the front-end.

MAINTENANCE:

CLEAR FS-STOP
The CLEAR
facility.

FS-STOP

command

disables

the

Field

Service

CLEAR INCREMENT

stop

OPERATOlR

The CLEAR INCREMENT command resets the KL
zero.
(See EXAMINE INCREMENT command.)

increment

CLEAR KLINIK

factor

OPERATOR

The CLEAR KLINIK command closes
terminates
the KLINIK link.
discussion on KLINIK access.)

the KLINIK
(refer to

access window and
Appendix D for a

CLEAR MEMORY

OPERATOlR

The CLEAR MEMORY command forces all subsequent EXAMINEs and
DEPOSITs to reference KL memory.
This command is the equivalent
of the SET MEMORY TEN command.
Note that this command does not
set memory to zeros, or in fact to anything at all;
it simply
specifies which memory,
the KL or the PDP-II,
is
being
referenced.

OPERATOlR

CLEAR NOT

The CLEAR NOT command is the equivalent of the SET command.

PROGRAMMER

CLEAR OFFSET
The CLEAR OFFSET command sets the relocation
(refer to rule ten in Section 4.2.)

4-8

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

factor

zero.

PARSER
OPERATOR

CLEAR OUTPUT[LOGJ
LPT
TTY

This command stops the CTY output from going to the specified
device.
When the CLEAR OUTPUT [device] command is given, the
PARSER checks for an active recording device.
If as a result of
the command,
no recording device
is active, then the console
terminal is made the active recording device.
The default devices for the CLEAR OUTPUT command are LOG and LPT.
If the default command
is used
the active recording device
becomes TTY.

CLEAR PARITY STOP

ALL
AR
CRAM
DRAM
ENABLE
FM
FS-STOP

MAINTENANCE

The CLEAR PARITY-STOP command selectively disables parity
for AR, CRAM, DRAM, Fast Memory, and Field Service.

CLEAR RELOAD

stops

PROGRAMMER

The CLEAR RELOAD command disables the automatic reload of the
following a fatal error.

CLEAR REPEAT

OPERATOR

The CLEAR REPEAT command resets the command line repeat factor to
zero.
A repeat factor of zero is the same as a repeat factor of
one;
subsequent command lines are executed once.

CLEAR RETRY
The CLEAR RETRY
When this flag
routine to take
a system reload

PROGRAMMER
command resets the RETRY flag
in the PARSER.
is off, a Keep-Alive-Cease error causes the KLERR
a system snapshot and then call KLINIT to perform
of the KL.
(See SET RETRY.)

CLEAR TRACKS

PROGRAMMER

The CLEAR TRACKS command stops RSX-20F from
typing
operations and results on the controlling terminal.

4-9

all

PARSER
PROGRAMMER

CONTINUE

The CONTINUE command takes the KL out of the HALT loop and starts
execution at the instruction pointed to by the PC.

PROGRAMMER

DEPOSIT AR=newdata
NOTE
The DEPOSIT AR command is now separated
from the new data by an equal sign (=).

The DEPOSIT AR command
register to new d~ta.

DEPOSIT

rELEVENl
LTEN
J

sets

the

contents

the

arithmetic

PROGRAMMER

=newdata

DECREMENT
addr
INCREMENT
NEXT
PREVIOUS
THIS

The DEPOSIT memory address command displays the contents of
specified or
implied memory address and then replaces
contents with newdata.

the
the

ELEVEN

specifies that the command
address in the PDP-II memory.

referencing

TEN

specifies that the command
address in the KL memory.

referencing

If neither ELEVEN or TEN is specified,
the memory to be
referenced is determined by the most recent SET MEMORY command.
If no SET
referenced.

MEMORY

command

has

been

issued,

memory

The following six arguments determine the specific memory addres~;
into which you wish to deposit the data;
one of them must bE~
entered.
addr

is the actual memory a~dress
in
octal
notation.
When referencing PDP-II memory,
this must be an even number.

INCREMENT

means add the KL increment factor
to the
address last referenced to arrive at the
deposit address.
If PDP-II memory is being
referenced, this command is the equivalent of
DEPOSIT NEXT.

4-10

PARSER
DECREMENT

means subtract the KL increment factor
from
the address last referenced to arrive at the
deposit address.
If PDP-II memory is being
referenced, this command is the equivalent of
DEPOSIT PREVIOUS.

means add one
(for a KL)
or two
(for a
PDP-II)
to the address last referenced to
arrive at the deposit address.

means subtract one (for a KL) or two
(for a
PDP-II)
from the address last referenced to
arrive at the deposit address.

THIS

means use the address last referenced as
deposit address.

the

OPERATOR

DISCONNECT

The DISCONNECT command disconnects the KLINIK link by running the
KLDISC task.
This command does not clear any KLINIK parameters.
(refer to Appendix D for a discussion of KLINIK.)

OPERATOR

EXAMINE PC
The EXAMINE PC command prints the contents
counter (PC) in octal, on the CTY.

the

program

OPERATOR

EXAMINE KL

The EXAMINE KL command performs the EXAMINE PC,
EXAMINE
EXAMINE PI, and the EXAMINE FLAGS commands, in. that order.

EXAMINE

ELEVEN]
[ TEN

VMA,

OPERATOR

addr
addrl:addr2
DECREMENT
INCREMENT
NEXT
PREVIOUS
THIS

The EXAMINE memory address command displays the contents of
specified or implied memory address in octal, on the CTY.

the

ELEVEN

specifies that the command is referencing
address in the PDP-II memory.

TEN

specifies that the command is referencing
address in the KL memory.

4-11

PARSER
If neither ELEVEN or TEN is specified,
the memory to be
referenced
is determined by the most recent SET MEMORY command.
If no SET MEMORY command has been
issued,
KL memory
is
referenced.
The following six arguments determine the specific memory address
to be examined;
one of them must be entered.
addr

is the actual memory address
in
notation.
If you are referencing
memory, this must be an even number.

octal
PDP-II

addrl:addr2

examines the memory addresses
through and including addr2.

addrl

INCREMENT

means add the KL increment factor
to the
address last referenced to arrive at the
examine address.
If PDP-II memory is being
referenced, this command is the equivalent of
EXAMINE NEXT.

DECREMENT

means subtract the KL increment factor
from
the address last referenced to arrive at the
examine address.
If PDP-II memory is being
referenced, this command is the equivalent of
EXAMINE PREVIOUS.

means add one
(for a KL)
or two
(for a
PDP-II)
to the address last referenced to
arrive at the examine address.

means subtract one (for a KL) or two
(for a
PDP-II)
from the address last referenced to
arrive at the examine address.

THIS

means use the address last referenced as
examine address.

EXAMINE AB

from

the

PROGRAMMER

The EXAMINE AB command displays the contents of
break register.

the

address

PROGRAMMER

EXAMINE AD
The EXAMINE AD command displays the
register.

contents

the

EXAMINE ADX

adder

PROGRAMMER

The EXAMINE ADX command displays the contents
extension.

4-12

the

adder

PARSER
PROGRAMMER

EXAMINE AR

The EXAMINE AR command displays the contents of the KL arithmetic
register.

EXAMINE ARX

PROGRAMMER

The EXAMINE ARX command displays
arithmetic register extension.

the

contents

the

PROGRAMMER

EXAMINE BR
The EXAMINE BR command displays the contents
register.

the

buffer

PROGRAMMER

EXAMINE BRX
The EXAMINE BRX command displays the contents of
register extension.

the

buffet

PROGRAMMER

EXAMINE CRADDR
The EXAMINE CRADDR command displays the contents of the
address register.

CRAM

PROGRAMMER

EXAMINE CRLOC
The EXAMINE CRLOC command displays the contents of
location register.

the

CRAM

PROGRAMMER

EXAMINE DRADDR
The EXAMINE DRADDR command displays the contents of the
address register.

4-13

DRAM

PARSER
EXAMINE DTE-20

PROGRAMMER

The EXAMINE DTE-20 command displays the contents of the DTE-20
registers.
These registers are displayed as in the following
example:
DLYCNT: 000000
DEXWD3: 000447
DEXWD2: 000000
DEXWDl: 000000
KLIO DATA=000000,,000447
TENADl: 000000 TENAD2: 000007
ADDRESS SPACE=EPT
OPERATION=EXAMINE
PROTECTION-RELOCATION IS ON
KLIO ADDRESS=7
TOIOBC: 010000 TOIIBC: 130000
TOIOAD: 066652 TOIIAD: 066075
TOIODT: 000000 TOIIDT: 000012
DIAGI : 002400
KL IN RUN MODE
MAJOR STATE IS DEPOSIT-EXAMINE
DIAG2 : 040000
STATUS: 012104
RAM IS ZEROS
DEX WORD 1
E BUFFER SELECT
DEPOSIT-EXAMINE DONE
DIAG3 : 000000

PROGRAMMER

EXAMINE EBUS
The EXAMINE EBUS command displays the contents
register.

the

EXAMINE FE

EBUS

PROGRAMMER

The EXAMINE FE command displays the contents of the
Exponent register.

EXAMINE FLAGS

Floating

PROGRAMMER

The EXAMINE FLAGS command displays the current state of the flag
bits
(0-12)
in the left half of the PC word. Those flags are
OVF, CYO, CYl, FOV, BIS, USR, UIO, LIP, AFI, ATl, ATO,
FUF 1 and
NDV.

EXAMINE FM

PROGRAMMER

The EXAMINE FM command displays
Memory register.
4-14

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

the

contents

the

Fast

PARSER
EXAMINE MQ

PROGRAMMER

The EXAMINE MQ command displays the contents of the KL Multiplier
Quotient ,register.

EXAMINE PI

PROGRAMMER

The EXAMINE PI command displays
Priority Interrupt system.

the

current

state

the

PROGRAMMER

EXAMINE REGISTERS
The EXAMINE REGISTERS command displays the
following registers
(see also the EXAMINE
individual registers):

contents of
command for

AD, ADX, AR, ARX, BR, BRX, EBUS, FM, MQ, and

the
the

pc.

EXAMINE SBR

PROGRAMMER

The EXAMINE SBa command displays
Subroutine Return register.

the

contents

EXAMINE SC

the

PROGRAMMER

The EXAMINE SC command displays the
Count register.

contents

the

EXAMINE VMA

Shift

PROGRAMMER

The EXAMINE VMA command displays the contents of the
Memory Address register.

EXAMINE VMAH

virtual

PROGRAMMER

The EXAMINE VMAH command displays the contents of the KL
Memory Address Held register.

Io'READ nnn
nnn:nnn

Virtual

MAINTENANCE

The FREAD command performs a diagnostic function read of the KL
CPU.
The valid range of function codes (nnn) is 100 through 177
octal.

4-15

PARSER
FWRITE nn=data

MAINTENANCE

The FWRITE command performs a diagnostic function write to the KL
CPU.
The valid range of function codes (nn) is 40 through 77
octal.
The data must be a 36-bit integer.

FXCT nn

MAINTENANCE

The FXCT command performs a diagnostic function execute on the KL
CPU.
The valid range of function codes (nn) is 0 through 37
octal.

HALT

PROGRAMMER
The HALT command tries to put the KL into the HALT loop by
clearing the RUN flop (FXCT 10) and waiting.
If the KL refuses
to go into the HALT loop, the front end tries to force it in by
using BURST mode.
If this does not work, the following error
message is issued:
PAR -- [HALT] CFH - CAN1T FIND KL HALT LOOP

INITIALIZE

PROGRAMMER

The INITIALIZE command sets up the KL state flag word
default values and restarts the KL based on those values.

with

OPERATOR

JUMP addr

The JUMP command starts the KL at the specified address and exits
from the PARSER.
At this point, the CTY is connected to the
TOPS-IO or TOPS-20 operating system.
The argument addr must be
an octal, positive,
nonzero address with a maximum value of
17777777.

MARK-MICROCODE n

MAINTENANCE

The MARK-MICROCODE command sets the mark bit in the specified
CRAM location.
The n is the CRAM address in the range of 0 to
2377.
The bit can be cleared by using the UNMARK-MICROCODE
command.

MeR taskname

OPERATOR

The MCR command loads and starts the specified task file.
4-16

PARSER
QUIT

OPERATOR
The QUIT command causes the PARSER to be exited.
At this point,
the CTY is connected to the TOPS-IO or TOPS-20 operating system.
This command is equivalent to SET CONSOLE USER or CTRL/Z.

REPEAT nnn; [commandl;command2; ••• ]

OPERATOR

The REPEAT command causes the subsequent commands in the current
command line to be repeated the number of times specified by nnn.
The argument nnn must be a positive, decimal, nonzero integer.
The command line can contain as many commands as will fit within
the 280 character buffer limitation.
You can nest REPEATs within
the command line.
Also, if a SET REPEAT command
is in effect,
the two repeat factors are multiplied to arrive at the actual
number of times commands are repeated.
For example, the following command examines the PC ten times:
REPEAT 10;EXAMINE PC
A more complex example is shown below, along with the sequence of
single commands that would duplicate the action of the single
command line.
REPEAT 3;EXAMINE PC:REPEAT 2:EXAMINE NEXT
EXAMINE
EXAMINE
EXAMINE
EXAMINE
EXAMINE
EXAMINE
EXAMINE
EXAMINE
EXAMINE

PC
NEXT
NEXT
PC
NEXT
NEXT
PC
NEXT
NEXT

If SET REPEAT 4 had been previously entered, the
would be repeated four times.
If no commands are specified,
command.

the

RESET

effect

above
that

sequence

null

PROGRAMMER
The RESET command performs a MASTER RE$ET of the KL and retains
the clock and parity-stop enables that existed before the reset.
This command is not allowed while the KL is running.

RESET ALL

PROGRAMMER

The RESET ALL command executes the RESET APR, RESET DTE-20, RESET
PAG,
and RESET PI commands.
This command is not allowed while
the KL is running.

4-17

PARSER
PROGRAMMER

RESET APR

The RESET APR command executes a eONO APR,,267760 instruction to
clear the KL arithmetic processor.
This command is not allowed
while the KL is running.

PROGRAMMER

RESET DTE-20

The RESET DTE-20 command resets the DTE-20 by depositing a
I
in
bit 6 of the DTE-20 diagnostic word 2.
Bit 0 in diagnostic word
3 is set to I to indicate word-mode transfers.

PROGRAMMER

RESET ERROR

The RESET ERROR command executes a eONO APR,,27760 instruction to
reset the KL error flags.

PROGRAMMER

RESET INITIALIZE

The RESET INITIALIZE command performs a MASTER RESET of the KL
and sets up normal clock and parity-stop enables.
This command
is not allowed while the KL is running.

PROGRAMMER

RESET 10
The RESET 10 command executes a eONO APR,,200000
perform an I/O reset of the KL.

instruction

PROGRAMMEF:

RESET PAG

The RESET PAG command executes a eONO PAG"Q instruction followed
by a DATAO PAG"IOO instruction to reset the KL PAGing box.
This
command requires that the KL clock be running.

PROGRAMMEF~

RESET PI
The RESET PI command executes a eONO PI"IOOOO
reset the KL Priority Interrupt system.

instruction

OPERATOFt

RUN taskname
The RUN command loads and starts the specified task
command is an alias for the MeR command.

4-18

------------,---------------------------,

file.

ThiH

PARSER
SET AC-BLOCK n

PROGRAMMER

The SET AC-BLOCK command changes the current KL block to the one
specified by the argument n in the command. This argument can
have a value in the range a to 7.

SET AUTO-TAKE

OPERATOR

The SET AUTO-TAKE command enables the automatic execution of
PARSER.CMD whenever a SNAPSHOT is requested,
either by the
operator or by the front end when it detects a KL crash.

SET CLOCK NORMAL

MAINTENANCE

The SET CLOCK NORMAL command sets the KL's clock parameters to
internal source, full rate, and en~bles the CRAM, data path, and
control logic clocks.

SET CLOCK

MAINTENANCE

CRAM
}
. DATA-PATH
{.CO~TROL

This SET CLOCK command enables the specified clock as follows:
CRAM

enables the control-RAM clock.

DATA-PATH enables the data-path clock.
CONTROL

SET CLOCK
{

enabl~s

the control logic clock.

MAINT~NANCE

EX'l'ERNAL}
INTERNAL
MARGIN

This SET CLOCK command sets the source of the clock pulses:
external,
internal, or margin.
The margin clock is slightly
faster than the normal internal clock and is used for diagnosing
rate-sensitive problems.
There may not be an external clock
attached to the KL.
Therefore, after you type the SET CLOCK
EXTERNAL command, the PARSER will print:
CONFIRM EXTERNAL CLOCK SOURCE (YES OR NO)?
If you answer YES, the operation is performed.
If you answer YES
and there is no external clock attached, the KL hangs and has to
be reset.

4-19

PARSER
SET CLOCK

MAINTENANCE

FULL
}
HALF
{ QUARTER
SLOW

This SET CLOCK command determines the speed of the KL clock:
full speed, one half speed, one quarter speed, or slow speed
which is equivalent to one eighth speed.

SET CONSOLE

OPERATOR

MAINTENANCE]
OPERATOR
PROGRAMMER
[ USER

The SET CONSOLE command sets the console mode of operation
therefore, the allowable subset of PARSER commands.
MAINTENANCE

allows the full set of PARSER commands.

PROGRAMMER

allows all
functions.

OPERATOR

allows only those PARSER commands that
crash the TOPS-IO or TOPS-20 monitor.

USER

exits the PARSER.

PARSER

commands

If no subargument is entered, the console is
mode.

except

set

and,

diagnostic
will

not

PROGRAMMER

NOTE

,,'

If KLINIK is enabled and active, the PARSER does not let
you set the console mode any higher than that specified
when the KLINIK window was defined.

PROGRAMME:R

SET DATE

The SET DATE command sets RSX-20F's internal date.
This date is
used in setting up and accessing KLINIK.
This command is not
available if RSX-20F thinks that it already has a valid date
(validity flag is ON).
In response to the SET DATE command, the
PARSER prompts you as follows:
PAR>SET DATE<RET>
DATE: 19 FEB 79
TIME: 1211
CURRENT SYSTEM DATE:
MONDAY, 19-FEB-79 12:11
VALIDITY FLAG IS:ON
PAR>

4-20

----------.........--.........------------------------------------------

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

PARSER
SET FAULT-CONTINUATION

PROGRAMMER

The SET FAULT-CONTINUATION command enables the KL's automatic
fault continuation reload mechanism.
This allows the host to
recover from errors detected by the front-end.

SET FS-STOP

MAINTENANCE

The SET FS-STOP command enables the Field Service stop facility.

SET INCREMENT n

OPERATOR

The SET INCREMENT command sets the KL increment counter
to the
value specified by the octal integer, n.
The increment counter
is used by the INCREMENT and DECREMENT arguments of the EXAMINE
and DEPOSIT commands.
Also,
only KL memory addresses are
modified by the increment counter.
PDP-II addresses that are
incremented
or
decremented default to NEXT and PREVIOUS,
respectively.

SET KLINIK

OPERATOR

The SET KLINIK command is usea to enable access to the KLINIK
link.
The command
initiates a dialog in which a KLINIK access
window and security parameters are established.
(refer
to
Appendix D for the KLINIK dialog.)

SET MEMORY

OPERATOR

ELEVENl
[ TEN
J

The SET MEMORY command
EXAMINEs and DEPOSITs.

establishes

the

ELEVEN

means default to the PDP-II memory.

TEN

means default to the KL memory.

default

memory

for

The command itself has no default;
an argument must be entered.
When RSX-20F is first loaded, the default memory is TEN.

SET NOT argument

OPERATOR

The SET NOT command is the equivalent of the CLEAR
requires an argument.
(See the CLEAR commands.)

4-21

command

and

PARSER
SET NOT OUTPUT [device]

OPERATOR

The SET NOT OUTPUT command is equivalent
command.
(See CLEAR OUTPUT command.)

The default devices for the SET NO OUTPUT
LPT.

command

SET OFFSET nnnnnn

the

CLEAR
are

OUTPUT
LOG

and

PROGRAMMER

The SET OFFSET command sets the PDP-II relocation factor
to the
value specified by nnnnnn,
an octal number in the range 77777
(+32,767) through 100000 (-32,768).
The relocation factor when
RSX-20F is first loaded is the address of the PARSER root
overlay.

SET OUTPUT

OPERATOR

LOG]
LPT
[
TTY

This command directs the CTY output to the specified device.
The
available devices are the log file PARSER.LOG, the lineprinter,
and the console terminal.
The output is directed to all
activated devices
If the output is directed to a log file and the file PARSER. LOG
does not exist, the file is created and the data written to the
new file.
If the file already exists, the new data is appended
to the file.
In either case a header line is output to all
active output devices when a logging file is opened or closed.
The default argument is TTY.

SET PARITY-STOP

ALL
AR
CRAM
DRAM
ENABLE
FM
FS-STOP

MAINTENANCH

The SET PARITY-STOP command allows you to selectively enable
parity stops for
the Arithmetic Register and extension, CRAM,
DRAM, Fast Memory, and Field Service.
The parity stops when
RSX-20F is first loaded are AR, CRAM, DRAM, and FM with ENABLE
ON.

SET RELOAD

PROGRAMM1E:R

The SET RELOAD command enables the automatic reload of the KL by
the PDP-II front end in situations such as Keep-Alive-Cease or
CPU errors.
4-22

PARSER
SET REPEAT n

OPERATOR

The SET REPEAT command sets the command line repeat factor to n.
The value n must be specified as a positive decimal number.
Each
subsequent command line is repeated n number of times.

SET RETRY

PROGRAMMER

The SET RETRY command sets the RETRY flag in RSX-20F. When this
flag
is set,
the first occurrence of a Keep-Alive-Cease error
results in the execution of the instruction in location 71.
This
instruction usually branches to a
routine that causes the KL
monitor to dump memory and request a reload (BUGHLT in TOPS-20,
STOPCD in TOPS-IO).
If the KL cannot accomplish this task before
the end of the Keep-Alive period
(5 seconds), RSX-20F assumes
that the KL is incapacitated.
In this case, KLERR is called to
take a KL hardware snapshot and then reload the KL.
If the RETRY flag is reset (see CLEAR RETRY), every occurrence of
a Keep-Alive-Cease error
results in a KLERR snapshot/reload of
the KL.

SET TRACKS

PROGRAMMER

The SET TRACKS command causes RSX-20F to type out, on the console
terminal, all KL operations and their results.

OPE~TOR,

SHOW [parameter]

PROGRAMMER

The SHOW command is the same as the WHAT command, and accepts the
same values as parameters.

OPERATOR

SHUTDOWN

The SHUTDOWN command DEPOSITs a minus one into the KL EXEC,
virtual location 30 (octal).
This comm~nd is used to bring down
a running sy~tem gracefully.
Example:
PAR>SHUTDOWN
**HALTED**
%DECSYSTEM~20

NOT RUNNING

4-23

PARSER
SNAPSHOT
MAINTENANCE
The SNAPSHOT command forces a snapshot of the KL
executes PARSER.CMD.
See command SET AUTO-TAKE.

and

optionally

PROGRAMMER

START TEN addr

The START TEN command starts the KL at the address specified.
Control then returns to the PARSER.
The starting address, addr,
is a required argument and must not be zero.

PROGRAMMER

START MICROCODE [addr]

The START MICROCODE command performs a MASTER RESET of the KL and
then starts the microcode at the specified address.
If addr is
omitted, the default address is zero.
Starting the microcode at
an address other than zero is not recommended.

SWEEP [n]

MAINTENANCE

The SWEEP command performs a sweep of the specified KL AC block
or,
if no argument is given, all 8 AC blocks are swept.
The
argument can be 0 to 7.
The sweep consists of reading
the
contents of all the registers
in a block and checking for a
parity error after each read.
The SWEEP command first executes a SET AC-BLOCK for the specified
block,
then examines each location.
If an FM parity error is
detected, a message is output and the KL parity is reset.
Then
the next location is examined. When no argument is specified and
a Clock Error Stop (CES) exists then all eight blocks are swept.
When the sweep is complete, the block is reset to the original AC
block.
If an error is detected, an attempt is made to write the
contents of the registers with good parity.
If this fails an
er.ror is generated.
Each time an FM parity error is detected, a message
This message is of the form:

printed.

SWEEP PASS number> n:aa/dddddd dddddd
where n is the AC block number, aa is the AC address, and
dddddd is the AC contents.

dddddd

If this command is issued during a KL clock error stop caused by
an FM error, then the current content of the FM output register
is output in the form:
FM PARITY ERROR-(BLOCK:ADDR/DAT) n:aa/dddddd dddddd
where n is the AC block number, aa is the AC address, and
dddddd is the AC contents.

4-24

dddddCl

PARSER
OPERATOR

TAKE [file]

The TAKE command executes the specified file as an indirect
command file.
All legal PARSER commands, except another TAKE
command, are allowed in the command file.
During execution of
the file, errors are handled exactly as if the commands were
input from the CTY.
The 'commands in the file are executed until an end-of-file
condition is reached. At that point the message <EOF> is printed
on the CTY and input is accepted from the CTY.
The file specified can be any 6 character alphanumeric file name.
The system device should have a file of the form 'file'.CMD,
where 'file' is the filename that appeared in the command. If no
filename is specified for the TAKE command, the default filename
PARSER.CMD is used.
NOTE
Only the filename can be used with the TAKE command. The
file extention cannot be entered on the command line.
The file is assumed to have the extent ion .CMD.
Example:
Executing the default command file PARSER.CMD.
PAR>TAKE
PAR>!THIS IS AN INDIRECT COMMAND FILE
PAR>!ALL PARSER COMMANDS ARE COMING FROM IT
PAR>WH VER!FIRST COMMAND
PARSER VERSION: V06-00
RSX20F VERSION: VBl341
PAR>WH DAT! SECOND COMMAND
CURRENT SYSTEM DATE:
THURSDAY, 27-DECEMBER-79 14:10
VALIDITY FLAG IS: OFF
PAR>! THIS IS THE END OF THE FILE
PAR> <EOF>
Attempting to TAKE a nonexistent command file.
PAR>TAKE TEST2
PAR> -- [TAKE] NSF - NO SUCH FILE

UNMARK-MICROCODE n

MAINTENANCE

The UNMARK-MICROCODE command clears the mark bit in the specified
CRAM location. The n is the CRAM address in the range 0 to 2377.
The bit is marked with the MARK-MICROCODE command.

4-25

PARSER
WHAT AUTO-TAKE

OPERATOR

The WHAT AUTO-TAKE reports the status of AUTO-TAKE.
either of the following:
AUTO-TAKE:
or
AUTO-TAKE:

displays

ON
OFF

WHAT CLOCK

PROGRAMMER

The WHAT CLOCK command displays the
control of the KL's clocks.

current

source,

rate,

and

OPERATOR

WHAT CONSOLE
The WHAT CONSOLE command displays the
OPERATOR, PROGRAMMER, or MAINTENANCE.

current

console

WHAT DATE

mode:

OPERATOR

The WHAT DATE command displays the day, date, and time that are
currently stored
in RSX-20F.
The status of the date validity
flag is also displayed.

WHAT FAULT-CONTINUATION

PROGRAMMER

The WHAT FAULT-CONTINUATION command reports the status
FAULT-CONTINUATION.
It displays either of the following:
FAULT-CONTINUATION:
or
FAULT-CONTINUATION:

ON
OFF

WHAT HARDWARE

OPERATOR

The WHAT HARDWARE command displays the environmental report that
KLINIT generates.
The report contains the KL serial number,
model type, line frequency,
and hardware options.
(refer to
section 5.3.1)

WHAT INCREMENT

OPERATOR

The WHAT INCREMENT command displays the current value of
increment counter used in EXAMINEs and DEPOSITs.

4-26

the

PARSER
WHAT KLINIK

OPERATOR

The WHAT KLINIK command displays the current access status of the
KLINIK link (refer to the SET KLINIK command in Appendix D).
If
no access window has been set up the reply is:
KLINIK DISABLED
If an access window has been set up and the link is in
reply is:

use,

the

use,

KLINIK ACTIVE
or
KLINIK ACTIVE AFTER REBOOT
If an access window has been set up and the link is not
the reply is:
KLINIK INACTIVE
In either of the last two instances, the status is followed by
display of the KLINIK window parameters.

'WHAT MEMORY

OPERATOR

The WHAT MEMORY command displays the default memory for
and EXAMINEs.

WHAT OFFSET

DEPOSITs

PROGRAMMER

The WHAT OFFSET command displays the
factor.

current

PDP-II

relocation

OPERATOR

WHAT OUTPUT
The WHAT OUTPUT command displays the
logging output.

current

devices

that

are

PROGRAMMER

WHAT PARITY-STOP

The WHAT PARITY-STOP command displays the current status of the
parity stop enable bit,
as well as the parity stops that are
currently enabled.

PROGRAMMER

WHAT RELOAD
The WHAT RELOAD command displays
automatic reload function.

4-27

the

current

status

the

PARSER
WHAT REPEAT

OPERATOR

The WHAT REPEAT command displays the current value of the
repeat factor.

PARSER

PROGRAMMER

WHAT RETRY
The WHAT RETRY command displays the current status of
flag in the front end.

the

RETRY

PROGRAMMER

WHAT TRACKS

The WHAT TRACKS command displays the current KL tracking status.

WHAT VERSION

OPERATOR

The WHAT VERSION command displays the current versions of RSX-20F
and the PARSER.

XCT argument

PROGRAMMER

The XCT command takes a
36-bit numerical expression as
argument and executes this expression as a KL instruction..
also accepts input in the form:

an
It

func dev, addr
where:
func

is one of the following:
CONI
CONO
DATAl
DATAO
BLKI
BLKO
CONSO
CONSZO

dev

is the octal device code.

addr

is the I/O instruction right half.

This input is decoded to create a 36-bit KL I/O instruction that
is then executed.
This form allows the user to execute I/O
instructions to obtain device status information without knowing
the opcodes.
The user need only know the device code of a few
standard devices.

4-28

PARSER
Note that executing an instruction with an opcode (bits 0 through
8)
of zero is not allowed.
If you attempt to do this, you will
receive an ILLEGAL KL OPCODE error message.

ZERO loaddr>hiaddr

PROGRAMMER

The ZERO command zeroes a specified area of KL memory.
ZERO
accepts as an argument the boundary addresses of the area to be
zeroed:
loaddr and hiaddr.

4.5

PARSER ERROR MESSAGES

The following list contains all the error messages that can be issued
by the PARSER while in any of the three console modes.
The format of
each message is:
PAR -- [command name] code - message
The command name is the name of the command that caused the error.
However,
this command name can be PARSER if you typed a string that
caused an error in the command parser
rather
than
in a specific
command routine.
For example, assume that you type an invalid command
such as:
PAR>KLEAR CONSOLE
You will receive the error message:
PAR -- [PARSER] NSK - NO SUCH KEYWORD "KLEAR"
On the other hand, assume that you type in an invalid argument:
PAR>CLEAR KONSOLE
You will receive the error message:
PAR

[CLEAR] NSK - NO SUCH KEYWORD "KONSOLE"

The various error codes, messages, and explanations are given below.
AMB

AMBIGUOUS KEYWORD "xxx"
where "xxx" is the ambiguous keyword.
The PARSER found more
than one keyword that matched the abbreviation you typed.
NOTE
The PARSER matches your
abbreviation against the
complete set of commands and arguments, regardless of
the subset allowed by the console mode.

APE

KL APR ERROR
The PARSER encountered a CPU error
(nonexistent memory,
parity error, or a similar condition) •
Call your Field
Service Representative.

4-29

PARSER
BAE

BURST ARGUMENT ERROR
This is an internal programming failure.
Support Specialist.

CAE

Call your

Software

KL CRAM ADDRESS ERROR
Call either your
This is an internal programming failure.
Field
Service
Representative or your Software Support
Specialist.

CAL

CAN'T ASSIGN LUN
RSX-20F is unable to assign a Logical Unit Number.
The
problem is in the file structure.
Retry the operation.
If
the error continues, call your Field Service Representative.

CAP

CAN'T ATTACH LINEPRINTER
The PARSER is unable to attach the line printer.
Check tQ
make sure that the line printer is available to the systet
and that the command format is correct.
If the error
persists, call your Field Service Representative.

CBO

COMMAND BUFFER OVERFLOW
You typed a command line that was more than 280 characters in
length.
Reenter the command as two or more lines.

CDI

CLEAR DATE ILLEGAL
You tried to clear the internal date
primary protocol.

CES

while

the

was

CLOCK ERROR STOP - code ERROR STOP
The variable, code, is either CRAM,
DRAM,
FM, or FS-STOP.
This message is displayed when the CPU encounters a fatal
internal hardware error.
Note the code received and call
your Field Service Representative.
Also, try to reload the
system using DISK, DECtape, floppy or switch register.
If
you ~se the switch register, make sure that you reload the
microcode.

CFH

CAN'T FIND KL HALT LOOP
The PARSER tried to halt the KL but failed.
Service Representative.

CLE

Call your

Field

CONSOLE LIMIT EXCEEDED
You tried to set a console mode that was higher than the
console mode specified in the SET KLINIK command dialog.
This is not allowed while the KLINIK link is active in remote
mode.

4-30

PARSER
CNR

COMMAND IS NOT REPEATABLE
You tried to repeat a command that cannot
However, the command has been executed once.

CRH

hardware

options.

the

validity

DATE ALREADY VALID
You tried to set a new internal date and
flag was on.

DBT

repeated.

CAN'T READ HARDWARE OPTIONS
The PARSER is unable to read the system
Call your Field Service Representative.

DAV

date

DATE BEFORE TODAY
While in the SET KLINIK command dialog, you tried to specify
an open or close date that was prior to the current date.

DCK

DIVIDE CHECK
This is an internal programming error.
Support Specialist.

DMF

your

Software

DEPOSIT KL MEMORY FAILED
This is an internal programming
accept a deposit directive.
Specialist.

DNF

Call

failure.
RSX-20F did not
Call your Software Support

DIRECTORY ?ILE NOT FOUND
The directory file cannot be found.
The problem is in the
file structure.
Retry the operation, .and if the error
continues, call your Field Service Representative.

DNP

DTE-20 IS NOT PRIVILEGED
This is a fatal error.
The DTE-20 mode switch is
wrong
position.
Call
either
your
Field
Representative or your Software Support Specialist.

DOR

DAY OUT OF RANGE
You specified a day that does not
entered.

DSF

in the
Service

exist

the

month

you

DTE-20 STATUS FAILURE
A read or write to one of the DTE-20 status registers failed.
Call your Software Support Specialist.

4-31

PARSER
DTC

DTE-20 CONFUSED - RUN AND HALT LOOP
This is a fatal error. The run and halt loop flags were set
simultaneously, an impossible situation.
Call your Field
Service Representative.

ECT

EBOX CLOCK TIMEOUT
While the PARSER was doing an execute function, the KL failed
to reenter the halt loop within the allotted time.
Call your
Software Specialist.

EMF

EXAMINE KL MEMORY FAILED
This is an internal programming
accept an examine directive.
Specialist.

EOC

failure.
R5X-20F did not
Call your Software Support

END OF COMMAND REQUIRED
The command was ended with a? and no additional arguments
are required.
Retype the command and press the RETURN key.

EPE

EBUS PARITY ERROR
This is a fatal error. The PARSER encountered an EBUS parity
error.
Call your Field Service Representative.

ESD

EBOX STOPPED - DEPOSIT
The PARSER executed a deposit directive and found that the KL
clock was stopped.

ESE

EBOX STOPPED - EXAMINE
The PARSER exscuted an examine directive and found
KL clock was stopped.

FCF

that

the

FILE CLOSE FAILURE
The PARSER is unable to close the file.
Retry the operation.
If
the
error
continues,
call
your
Field
Service
Representative.

FEF

FILE EXTEND FAILURE
The PARSER failed to extend the file.
Retry the command.
If
the error persists, call your Field Service Representative.

FEN

FILE ENTER FAILURE
The PARSER is unable to enter the specified file.
Retry the
command.
If the error persists, call your Field Service
Representative.

4-32

PARSER

FLF

FILE LOOKUP FAILURE
The PARSER failed in its attempt to look up the specified
file.
Retry the operation.
If the error continues, call
your Field Service Representative.

FOF

FILE OPEN FAILURE
The PARSER failed to open the specified file.
Retry the
operation.
If the error persists, call your Field Service
Representative.

FRD

FILE READ FAILURE
The PARSER is unable to read the file.
Retry the command.
If the error persists call your Software Support Specialist.

FRF

FUNCTION READ nnn FAILED
A diagnostic function read with function code nnn has failed.
This
1S
a
fatal
error.
Call
your Fiel& Service
Representative and your Software Support Specialist.
If the
system crashes, try to reload it.

FSW

FM SWEEP FAILED
The FM sweep failed.
Retry the sweep.
If the
persists, call your Field Service Representative.

FWF

problem

FUNCTION WRITE nn FAILED
A diagnostic function write with function code nn has failed.
This
is
a
fatal
errOr.
Call
your Field Service
Representative and your Software Support Specialist.
If the
system crashes, try to reload it.

FWT

FILE WRITE FAILURE
The PARSER is unable to write to the specified file.
Retry
the command.
If the error persists call your Field Service
Representative.

FXF

FUNCTION XCT nn FAILED
A diagnostic function execute with function code nn has
failed.
This is a fatal
error.
Call your Field Service
Representative and your Software Support Specialist.
If the
system crashes, try to reload it.

4-33

PARSER
IDF

ILLEGAL DATE FORMAT
You entered a date in the wrong format.
is:

The

correct

format

dd-mmm-yy
where the hyphens can be replaced by spaces and the year can
be entered as four digits.
The day and year must be numeric
and the month must be alphabetic.
The month can
be
abbreviated as long as it remains unique.
IFC

ILLEGAL FUNCTION CODE
This is either an internal programming error or the result of
entering a diagnostic command with an invalid function code.
The valid function codes are as follows:
FREAD command takes codes 100-177
FWRITE command takes codes 40-77
FXCT
command takes codes 0-37
If the message is not a result of entering a
command, call your Software Support Specialist.

IFN

ILLEGAL FILE NAME
The PARSER cannot accept the filename as specified.
the command, making sure the filename is correct.

ILC

diagnostic

Reissue

ILLEGAL CHARACTER "c"
The PARSER found an illegal character in the command line and
"c"
is the character's printing equivalent.
Nonprinting
characters are preceded by a circumflex (A) and converted to
their printing equivalent for output.

ILl

ILLEGAL INSTRUCTION
CLEAR AC-BLOCK is not allowed.

ILS

ILLEGAL SEPARATOR CHARACTER "s"
The PARSER found an illegal separator character
in the
command line and "s" is the illegal character. Nonprinting
characters are preceded by a circumflex (A) and converted to
their printing equivalent for output. Note that a tab is
converted to one space.

IOC

ILLEGAL KL OPCODE
Either you or the PARSER tried to execute a KL instruction
with an illegal op-code.
If this is not the result, of an XCT
command, call your Software Support Specialist.

4-34

PARSER
IPC

ILLEGAL PASSWORD CHARACTER "c"
During the SET KLINIK dialog, you typed a password containing
"c," an illegal character.
You must use only numeric or
uppercase alphabetic characters in the password.

IRC

ILLEGAL REPEAT COUNT
You typed a zero or negative argument to either the REPEAT or
SET REPEAT command.

IRE

ILLEGAL RECURSION
A TAKE command cannot be used in an indirect command file.

ITF

ILLEGAL TIME FORMAT
You entered a time of day that was not in the proper format.
The PARSER expects a numeric value of the form hh:mm or hhmm.

ITN

ILLEGAL TASK NAME
The RUN or MCR command was entered with no task name.

KCN

KL CLOCK IS OFF
The KL clock is off and you tried to execute a
requires the clock to be on.

KLA

range

(over

was

ILLEGAL WHILE KL RUNNING
You tried to execute an illegal
running.

KNC

that

KL ADDRESS ERROR
You specified a KL address that was out
bits), negative, or not in octal radix.

KLR

command

while

the

KL IS NOT CONTINUABLE
You tried to resume processing with the CONTINUE command, but
the KL was not in a continuable state.
For example, you
cannot CONTINUE after a RESET command.

KWE

KLINIK WINDOW ERROR
During the SET KLINIK dialog, you specified a window close
date and time that is prior to the window open date and time.

MRA

MISSING REQUIRED ARGUMENT
You did not specify
command.

all

the

4-35

necessary

arguments

for

the

PARSER
MRH

HARDWARE OPTIONS MUST YET BE READ
KLINIT has not yet read and stored the hardware options
because the KL is not running.
Retry the command when the KL
is running.

NDI

NULL DATE ILLEGAL
prompt

During the SET DATE dialog, you answered the DATE:
with a carriage return. You must supply a date.
NER

NUMERIC EXPRESSION REQUIRED
You entered a command that expects a numeric expression as an
argument and something else was entered.

NOR

INPUT NUMBER OUT OF RANGE
You specified a number that was out of range or in the
radix.

NPl

NULL PASSWORD ILLEGAL
During the SET KLINIK dialog,
prompt with a carriage return.
one is requested.

NSF

you answered the PASSWORD:
You must supply a password if

NO SUCH FILE
The file as specified does not exist.
reenter the command if necessary.

NSK

wrong

Check the filename and

NO SUCH KEYWORD "xxx"
You entered a command containing the invalid keyword "xxx".

NST

NO SUCH TASK
You specified a nonexistent task in an MCR or RUN command.

NTI

NULL TIME ILLEGAL
During the SET DATE dialog, you answered the TIME:
with a carriage return.
You must specify a time.

OAl

prompt

ODD ADDRESS ILLEGAL
You tried to examine an odd-numbered PDP-II address.

OFC

ODD FUNCTION CODE
This is an internal programming error.
Support Specialist.

4-36

Call

your

Software

PARSER
PTL

PASSWORD TOO LONG
During the SET KLINIK dialog, you specified a
was more than six characters in length.

RPM

password

that

RIGHT PARENTHESIS MISSING
You omitted a right parenthesis in a numeric expression.

SCF

SET CLOCK FAILED
The PARSER cannot validate the clock enable parameters it has
just set.
This is a hardware error.
Call your Field Service
Representative.

SKI

SET KLINIK ILLEGAL WHILE KLINIK ACTIVE
You tried to set new KLINIK parameters while the KLINIK link
was active.
If you want to change the parameters, you must
first disconnect the KLINIK link by typing DISCONNECT or
CLEAR KLINIK.

SPF

SET PARITY FAILED
The PARSER cannot validate the parity stop parameters it has
just set.
This is a hardware error.
Call your Field Service
Representative.

SZI

START AT ZERO ILLEGAL
You tried to start the KL at location zero;

TAA

this is illegal.

TASK ALREADY ACTIVE
You issued a RUN or MCR command for a task that
active.

TOR

was

already

TIME OUT OF RANGE
You specified a time in which the hours were greater than
or the minutes were greater than 59.

UNL

KL MICROCODE NOT LOADED
The system tried to start the KL microcode and found that it
was not loaded or was not functioning.
Use DISK, DECtape,
FLOPPY, or the switch register to reload the microcode and
the system.

VFY

VERIFY FAILED
The PARSER cannot verify the correct execution of
command.
Call your Software Support Specialist.

4-37

DEPOSIT

PARSER
~vRM

COMMAND NOT AVAILABLE IN THIS CONSOLE MODE
You entered a command that is not available
in the current
console mode.
Use the SET CONSOLE command to change mode.

XTO

KL EXECUTE TIMED OUT
The KL failed to reenter the halt loop within the allotted
time while performing a fast internal execute function.

YOR

YEAR OUT OF RANGE
You specified the year incorrectly.

4-38

CHAPTER 5
KLINIT

KLINIT is the KL initialization program.
You can run KLINIT in
default mode where it performs a fixed series of operations or you can
run it in dialog mode and specify selected operations.
When you load the system using
the DISK,
DECTAPE,
or
FLOPPY load
switch,
(Figures
5-1 and
5-2), KLINIT performs the following steps
automatically without operator intervention.
1.

Loads the KL processor microcode
from the
appropriate
microcode
file on the
front-end
load device.
(Users of
TOPS-IO with a KL model A load from UA.MCB;
users of TOPS-IO
with a model B load from UB.MCB.
Users of TOPS-20 with a
model A load from KLA.MCB, and TOPS-20 users with a model B
load from KLX.MCB.)

Configures and enables cache memory according to
the KLINIT
configuration file,
KL.CFG.
If this file is not present on
the front-end load device, all cache is enabled.

Configures and interleaves KL memory according to the KLINIT
configuration file,
KL.CFG.
If this file is not present on
the front-end load device, all available memory is configured
with the highest possible interleaving.

If the KL.CFG file does not exist, KLINIT creates a
file
by
that name and
stores it on the front-end load device.
The
file contains the cache and memory configuration in effect at
the time.

Loads and starts the default KL bootstrap program from
the
file BOOT.EXB located on the disk, DECtape, or floppy disk
device.
The bootstrap program then loads and starts the
default monitor.
The default monitor is found in:
SYS:SYSTEM.EXE
for TOPS-IO
PS:<SYSTEM>MONITR.EXE for TOPS-20

If you do not want KLINIT to perform the above series of operations,
you must enter the dialog mode of KLINIT.
Then, you can do anyone or
more of the following:
•

Load -and/or verify the KL microcode.

•

Configure cache memory as you want it.

•

Configure KL memory as you want it.

5-1

KLINIT
•

Load and start any bootstrap program.

•

Specify switches to the bootstrap program.

•

Load and start any monitor from disk or magnetic tape.
NOTE
The default bootstrap program BOOT.EXB
does
not
understand
TOPS-20
subdirectories.
Thus, although you can
load and start any monitor from disk,
you cannot load the monitor from any
disk area.
Specifically, you can load
<EXTRA-SYSTEM>OUR-MONITOR.EXE,
but you
cannot
load
<EXTRA. SYSTEM>OUR-MONITOR. EXE.

5-2

KLINIT

LOAD SWITCHES
DISK

ENABLE

FAULT
LIGHT

POWER
LIGHT

POWER
SWITCH

EMERGENCY
POWER OFF

SWITCH REGISTER

Figure 5-1

Load Switches and Switch Register for KL
with Floppy Disks

5-3

KLINIT

LOAD SWITCHES
DISK
SW REG

ENABLE

DECTAPE
POWER
LIGHT
FAULT
LIGHT

POWE
SWITC
EMERGENCY
POWER
OFF

17
SWITCH REGISTER

Figure 5-2

ENABLE/HALT
SWITCH

Load Switches and Switch Register for KL
with DECtapes

5-4

KLINIT

Table 5-1
Switch Register Bit Definitions

111 10

1711611514

Bit

Meaning

If this bit is set, the
remaining
bits
are
interpreted.
You must set this to load the system
using the switch register.

2,1

If both bits 1 and 2 are set, RSX-20F is loaded and
the KL initialization operator dialog (KLINIT) is
loaded and started. This is what you usually want to
do if you are loading the system from the switch
register.
If bit 1 is set and bit 2 is not set, the RSX-20F
monitor is loaded and started; no communication is
initiated between the KL and PDP-II processors at
this time.
If bit 1 is not set and bit 2 is set, RSX-20F is
loaded and started. However, the front end tries to
communicate with the KL uSlng secondary and then
primary protocol.
If the KL is not running, a TBT
II-halt occurs.
If both 1 and 2 are not set, the system is loaded
much like it is using the DISK, DECtape, or FLOPPY
load switch.
However, before KLINIT is run, a
diagnostic program that checks out the front end CPU
and front-end devices is executed.

6-3

Used to set the speed of a DH-ll CTY (bits 14-11).

If this bit is set, the bootstrap device
pack on a dual-ported drive.
If the bit is not set, the
DECtape
drive or floppy
processor.

disk

bootstrap device is a
disk on the front-end

10-8

These three bits allow you to specify the unit number
of the bootstrap device in binary.
No bits set
indicate unit 0; bits 9 and 8 set indicate unit 3.

14-11

These four bits allow you to specify to RSX-20F the
DH-ll line number to which you wish to redirect the
CTY.

This bit indicates the action taken when an I/O error
occurs during the bootstrapping. If the bit is set,
the operation is retried indefinitely if an error
occurs.
If it is not set (the normal case), a halt
occurs after ten unsuccessful retries.

17,16

Currently not used, and must not be set.

A bit is set when
position.

the

corresponding
5-5

switch

the

upward

KLINIT
5.1

KLINIT LOAD AND START

When you load and start the KL using the SW REG load switch,
usually enter the KLINIT dialog.
(See Figures 5-1 and 5-2.) Set
switch register bits 0, 1, and 2 on (in the up position).
Refer
Table 5-1 to determine if bits 7 through 10 should be set.
Press
load switches SW REG and ENABLE simultaneously.
RSX-20F loads
starts and, in turn, loads and starts KLINIT.
KLINIT then prompts
with the first question:

you
the
to
the
and
you

KLI -- ENTER DIALOG [NO,YES,EXIT,BOOT]?
You may also enter the KLINIT dialog from the PARSER.
RSX-20F is running, type the following:

Assuming

that

CTRL/\ (does not echo)
;to enter the PARSER
PAR)MCR KLINIT
;to load KLINIT
KLI -- ENTER DIALOG [NO, YES, EXIT, BOOT]?
During the dialog, the following conventions hold:
•

A carriage return terminates the answer to a question.

•

A RUB OUT or DELETE deletes a character.

•

A carriage return by itself in answer to a question selects
the default answer to the question.
The default answer is
the first answer listed.

•

CTRL/Z terminates the operator dialog and exits to the PARSER
without rewriting the KL.CFG file.
If the KLINIT dialog is
terminated in this manner, the KL hardware may not be fully
or completely initialized.

•

CTRL/U deletes the current input line.

•

An answer of NO to the ENTER DIALOG question skips
of the dialog and assumes all the default answers.

•

An answer of BACK to any question returns you to the previous
question unless stated otherwise.

•

An answer of RESTART to the EXIT question returns you to
first question in the dialog.

•

An ESCape typed at any point in a reply before the carriage
return restarts the dialog.
Note that ESCape does not echo
on your terminal.

•

An unacceptable answer results in an error message and causes
the question to be repeated.

•

The minimum size of an abbreviation for any answer other than'
filename is the first two characters.

5-6

the

rest

the

KLINIT
5.2

KLINIT OPERATOR DIALOG

The following KLINIT dialog includes all the possible questions and
all the acceptable answers.
The questions are presented in the order
in which KLINIT asks them, unless it is specifically stated otherwise
in the description of the particular question.
In p~actice, however,
only a subset of the dialog is encountered on anyone system.
The
KLINIT program automatically bypasses any questions that are not
applicable to the system configuration.
In addition,
a particular
response to one question can result in the bypassing of subsequent
questions.
This behavior is documented wherever it occurs.
There are two commands that are not used in response to any particular
question,
but can be used at almost any time.
One of these is BACK,
which causes the dialog to return to the previous question.
This
command can be used at any time except on the first question of the
dialog, when of course there is no previous question.
The other
command has four forms that are used to toggle on and off the tracking
capability. These forms are T+, T-, and L+, L-.
If you wish to see a
report on each operation of the initialization procedure, you can give
the L+ command, and the complete listing is printed on the line
printer.
The T+ command prints the listings on the CTY.
You should
be aware that the T+ command causes a great deal of information to be
dumped to the CTY, and uses a lot of time and paper. The L- and Tcommands turn off this reporting.
Each of the following questions is
KLI>.

followed

the

KLINIT

prompt,

KLI -- ENTER DIALOG [NO,YES,EXIT,BOOT]?
An answer of YES or NO to the question above causes KLINIT to print a
hardware environment r~port containing the KL serial number, machine
type, power line frequency, and the system's hardware options.
(Refer
to Section 5.3.1, Informational Messages.)
NO

displays the hardware environment and assumes the default
answers for all the remaining questions.
This is the last
chance to bypass the dialog and take the default path.

YES

displays the hardware environment, continues the dialog
asks the next question.

EXIT

discontinues the dialog and returns to the RSX-20F monitor.

BOOT

skips the rest of the dialog,
enables cache memory as
directed by KL.CFG, and immediately loads and starts the KL
bootstrap program whose name is found in the configuration
file.
If none is found, the standard KL bootstrap program
found in BOOT.EXB is loaded. No defaults are taken when
this option is selected.

5-7

and

KLINIT
KLI

RELOAD MICROCODE [YES,VERIFY,FIX,NO]?

YES

loads the KL microcode from the bootstrap device into the KL
processor.
Should you wish to load the microcode from a
file that does not have the default file name,' you can
respond with YES and,
before typing the carriage return,
include the actual file name.

VERIFY

verifies that the microcode in the KL processor matches the
microcode on the bootstrap device.
An error report is
printed for each location found in error and an error count
is incremented.
(Refer to Section 5.4.3 for the format and
contents of this error report.)
Whenever the error count
exceeds five,
verification is discontinued and the message
VERIFY FAILED is issued.
If verification continues through
all the microcode and the final error count is greater than
zero, the VERIFY FATLED message is issued.
In both cases,
KLINIT returns to the beginning of the dialog.
You can then
reload the microcode and try again.

FIX

verifies the microcode as in the VERIFY option.
In
addition,
whenever an error is detected, KLINIK attempts to
reload that location.
If
the
reload
operation
is
successful,
the error count is decremented.
If the reload
fails, the MICROCODE FIX FAILED message is issued.
In
either case verification continues with the next location.
Whenever the error count exceeds five,
verification is
discontinued and the VERIFY FAILED message is issued.
If
verification continues through all the microcode and the
final error count is greater than zero, the VERIFY FAILED
message is issued.
In both cases,
KLINIT returns to the
beginning of the dialog.
You can then reload the microcode
and try again.

neither loads nor verifies the microcode.

KLI

RECONFIGURE CACHE [FILE,ALL,YES,NO]?

FILE

configures cache memory as specified in the configuration
file, KL.CFG.
If this file does not exist, all cache memory
is enabled. The dialog continues with the CONFIGURE KL
MEMORY question.

ALL

enables all cache memory.
The
CONFIGURE KL MEMORY question.

YES

configures cache memory under dialog control.

does
not
reconfigure
cache
configuration is left unchanged.
the CONFIGURE KL MEMORY question.

KLI

dialog

continues

with

the

memory;
the
existing
The dialog continues with

ENABLE WHICH CACHES [ALL,NONE,0-3]

ALL

enables all cache memory.

NONE

disables all cache memory.

0-3

enables only the caches specified.
caches 0, 1, and 3 reply with:
KLI>0,1,3<cr>

5-8

For example,

enable

KLINIT
KLI -- CONFIGURE KL MEMORY [FILE,ALL,REVERSE,FORCE,YES,NO]?
NOTE I
A reply of BACK to this question returns
you to the RECONFIGURE CACHE question.
NOTE 2
The FORCE option appears only in systems
that have MOS memory.
In systems that
do not have MOS memory the FORCE option
does not appear
in the CONFIGURE KL
MEMORY question.
FILE

configures KL memory as specified in the configuration file,
KL.CFG.
If this file does not exist, ALL is assumed.
KLINIT then prints the logical memory map and the dialog
continues with the LOAD KL BOOTSTRAP question.
If the configuration in the KL.CFG file is not consistent
with the actual con~iguration an error message is issued and
the dialog restarts from the beginning.

ALL

configures KL memory in the normal (forward) direction with
as much memory as possible.
KLINIT then prints the logical
memory map and the dialog continues with the LOAD KL
BOOTSTRAP question.

REVERSE

configures,memory under dialog control; however, the memory
configuration is reversed.
Before the next question is
asked, KLINIT examines memory and prints a physical memory
map.
This feature has been included for maintenance
purposes.

FORCE

appears ONLY in systems in which KLINIT can detect the
presence of a KW-20 MOS Master Oscillator.
The FORCE memory
configuration option allows the operator -to force KLINIT
into a Double-Bit-Error (DBE) scan of the MF-20 MOS memory
controllers.
This enables KLINIT to attempt to recover
"lost"
MF-20 blocks.
The scan requires approximately
twenty-five seconds for each 256K of memory to be scanned.

YES

configures memory under dialog control,
in the normal
(forward)
direction.
Before the next question is asked,
KLINIT examines memory and prints out a physical memory map.

does not configure memory at all.
The previous memory
configuration remains,
and the dialog continues with the
LOAD KL BOOTSTRAP question.
NOTE
The forward/reverse configuration indicator is saved
in the KL.CFG file to allow restoration of the
reverse configuration over reloads.
If the KL.CFG
file does not exist, the default is normal (forward)
configuration.

5-9

KLINIT
KLI

CONFIGURE INTERNAL CORE MEMORY [ALL,YES,NO]?

ALL

configures all internal core memory.
The dialog continues
with
the INTERNAL CORE MEMORY INTERLEAVE UPPER LIMIT
question.

YES

configures internal core memory under dialog control.

deletes all internal core memory.
The dialog continues with
'questions on other types of memory, if any.
See Figure 5-3.

KLI -- MODULES/BLOCKS WITHIN CONTROLLER n [ALL,NONE,SPECIFY]?
NOTE
This question is repeated for
each
the
controller.
In each iteration,
number n is the current
controller
number~

ALL

configures all the memory modules for controller n.

NONE

deletes all the memory modules for controller n.

SPECIFY

configures the modules specified.
DO NOT TYPE SPECIFY!
Valid module numbers are 0 through 3 and the entries are
separated by commas.
For example, to configure modules 0
and 1, type the following:
KLI>O,l<CR>

KLI

INTERNAL CORE MEMORY INTERLEAVE UPPER LIMIT [4,2,1]?

allows up to 4-way interleaving.

allows up to 2-way interleaving.

allows no interleaving

The dialog continues with questions on other types of memory, if any.
(See Figure 5-3.)
If none, KLINIT prints the logical memory map and
the dialog continues with the LOAD KL BOOTSTRAP question.
KLI

CONFIGURE EXTERNAL CORE MEMORY [YES,NO]?

YES

allows you to set the bus-mode for external memory.

deletes all external core memory.
The dialog continues with
questions on other types of memory, if any.
(See Figure
5-3.)

KLI -- EXTERNAL CORE MEMORY BUS-MODE [OPTIMAL,1,2,4]?
OPTIMAL

sets the bus-mode for optimal performance.

sets the bus-mode to 1.

sets the bus-mode to 2.

sets the bus-mode to 4.

5-10

KLINIT
The dialog continues with questions on other types of memory, if any.
(See Figure 5-3.)
If none, KLINIT prints the logical memory map and
the dialog continues with the LOAD KL BOOTSTRAP question.
KLI

CONFIGURE MOS MEMORY [ALL,YES,NO]?

ALL

configures all MOS memory.
The dialog continues with the
printing of the logical memory map and the LOAD KL BOOTSTRAP
question.

YES

configures MOS memory under dialog control.

deletes a~l MOS memory.
The dialog continues with the
printing of the logical memory map and the LOAD KL BOOTSTRAP
question.

KLI -- MODULES/BLOCKS WITHIN CONTROLLER n [ALL,NONE,SPECIFY]?
NOTE
This question is repeated as many times
as
there are controllers.
In each
iteration,
the
n
is
the
current
controller number.
ALL

configures all memory blocks for controller n.

NONE

deletes all memory blocks for controller n.

SPECIFY

configures the blocks specified.
DO NOT TYPE SPECIFY! Type
a list of block numbers (0 through 13 octal) separated by
commas.
For example, to configure blocks 0, 1, 2, 7, 10 and
11 reply with:
KLI>0,1,2,7,10,11<CR>

KLI -- LOAD KL BOOTSTRAP [FILE,YES,NO,FILENAME]?
FILE

notifies KLINIT to load the bootstrap specified in the
KL.CFG file.
If no KL.CFG file exists, KLINIT will use the
default bootstrap.

YES

notifies KLINIT to load the default bootstrap.

notifies KLINIT not to load a bootstrap.

FILENAME

notifies KLINIT to load the specified file as the bootstrap.

KLI

WRITE CONFIGURATION FILE [YES,NO]?

YES

notifies KLINIT to write a new KL.CFG file
current configuration and load parameters.

notifies KLINIT not to change the existing KL.CFG file.

5-11

containing

the

KLINIT
At this point if a bootstrap was requested, the bootstrap program is
loaded into the KL and started.
If the answer to the LOAD KL
BOOTSTRAP question was NO, the following question is asked:
KLI

EXIT [YES,RESTART]?

YES

exits KLINIT after optionally writing a new KL.CFG file
previous question).

RESTART

restarts the dialog with the ENTER DIALOG question.

5-12

(see

KLINIT

LOAD SWITCHES

r---------------------------J~~---------------------------~
K

SW REG
(SW REG BIT
o MUST BE ON)

(

TEST SW REG BITS 1 & 2
I
I
I
I
00
11
01
10

--11

1--_ _ _ _ _ _ _ _ _ _ _ _ _

)

SEE'TABLE 5-1

IS CACHE PRESENT?

ENABLE
CACHE PER
KL.CFG
(NOTE 1)

ENABLE
ALL
CACHE

DISABLE
ALL
CACHE

ENABLE
ALL
CACHE

ENABLE THE
SPECIFIED
CACHE

MR-S-172-79

NOTE 1: If there is no KL.CFG file, enable all cache.

Figure 5-3

KLINIT Operator Dialog
5-13

KLINIT

CONFIGURE
MEMORY
PER KL. CFG
(NOTE 2)

FILE

ALL

REVERSE

*FORCE

CONFIG.
MEMORY
PER KL.CFG
(NOTE 2)

CONFIG.
ALL
MEMORY

SET
REVERSE
CONFIG.

*DBE SCAN
ANY MOS
MEMORY

CONFIGURE KL MEMORY?

•

YES

•

SET
FORWARD
CONFIG.

t ~

PRINT MAP OF
PHYSICAL MEMORY

)

IS INTERNAL CORE MEMORY PRESENT?

CONFIGURE INTERNAL CORE MEMORY?
ALL

YES

•

CONFIGURE
ALL INTERNAL
CORE MEMORY

DELETE ALL
INTERNAL CORE
MEMORY

I
f.4----------- -----,

MODULES/BLOCKS WITHIN CONTROLLER n?
ALL

t
CONFIGURE
ALL MODULES

NONE

SPECIFY

l
CONFIGURE
THE MODULES
SPECIFIED

DELETE ALL
MODULES

J
(N~~~ _ _ _ _ _ _ _

-1

INTERNAL CORE MEMORY INTERLEAVE UPPER LIMIT?
4

ALLOW UP
TO 4·WAY
INTERLEAVING

ALLOW UP
TO 2·WAY
INTERLEAVING

I
F

G
*For MOS memory only.

t
ALLOW NO
INTERLEAVING

NOTE 2: If there is no KL.CFG file, configure all memory.
NOTE 3: This question is repeated as many times al there are controllers.
The controller currently being configured is denoted by n.

Figure 5-3

KLINIT Operator Dialog (Cant.)
5-14

.H
MR-S-168-79

KLINIT

IS EXTERNAL CORE MEMORY PRESENT?

CONFIGURE EXTERNAL CORE MEMORY?
YES

EXTERNAL CORE MEMORY BUS·MODE?
OPTIMAL

•

SET BUS MODE
FOR OPTIMAL
PERFORMANCE

•

r
I

•

SET BUS MODE TO:

•
4

IS MOS MEMORY PRESENT?

CONFIGURE MOS MEMORY?
YES

ALL

•

+
CONFIGURE
ALL MOS
MEMORY

DELETE
ALL MOS
MEMORY

l
~-------------I

I
MODULES/BLOCKS WITHIN CONTROLLER n?
ALL

•

SPECIFY

NONE

•

CONFIGURE
ALL MODULES

DELETE
ALL MODULES

CONFIGURE
THE BLOCKS
SPECIFIED

I
~

II
I

I
I
I
I

I
I

____~~~~ ____ -1

M R-S·169·79

NOTE 3: This question is repeated as many times as there are controllers.
The controller currently being configured is denoted by n.

Figure 5-3

KLINIT Operator Dialog (Cont.)

5-15

KLINIT

PRINT LOGICAL
MEMORY MAP

SET SWITCH
TO USE
KL.CFG
BOOTSTRAP
(NOTE 4)

SET SWITCH
TO USE
DEFAULT
BOOTSTRAP

SET SWITCH
TO NOT
LOAD
BOOTSTRAP

SET SWITCH
TO USE
Filename
BOOTSTRAP

SET THE WRITE
FILE SWITCH

LOAD
DEFAULT
BOOTSTRAP

LOAD THE
APPROPRIATE
BOOTSTRAP

MR-S·170·79

NOTE 4: If there i. no KL.CFG file, set switch to use
the default bootstrap program in BOOT.EXB.

Figure 5-3

KLINIT Operator Dialog (Cant.)

5-16

KLINIT
5.3

KLINIT MESSAGES

KLINIT issues four classes of messages:
informational, warning,
di.alog error, and system error messages.
These messages are listed in
sections 5.3.1 through 5.3.4 according to class.

5.3.1

Informational Messages

KLINIT prints a hardware environment message for each invocation of
the program.
If KLINIT is activated using the ENABLE and DISK
switches, the environment report appears immediately after KLINIT
prints its heading and version number.
If KLINIT is activated using
the ENABLE and SW/REGISTER switches and if the question KLI
ENTER
DIALOG
[NO,YES,EXIT,BOOT]?
is answered with YES or NO, the hardware
environment report follows immediately.
If this question is answered
with EXIT or BOOT, the hardware environment does not appear.
The hardware environment report contains the following information:
•

The KL processor serial number

•

The KL processor model type

•

The power line frequency

•

The hardware options available on the system

The serial number is that of the KL processor.
The model type can be
either A or B. The power line frequency can be either 50 or 60 Hz.
The hardware options can include the following:
•

MOS Master Oscillator

•

Extended Addressing

•

Internal Channels

•

Cache

Example:
KLI
KLI
KLI

VERSION VB12-27 RUNNING
KL10 SIN:
2136., MODEL B, 60 HERTZ
KL10 HARDWARE ENVIRONMENT
MOS MASTER OSCILLATOR
EXTENDED ADDRESSING
INTERNAL CHANNELS
CACHE
NOTE
The hardware environment report is not
displayed during automatic reloads or
during Keep-Alive-Cease processing.

KLINIT also prints informational messages to indicate the normal
completion of a KLINIT function.
The message text is preceded by
"KLI --".

5-17

KLINIT
The informational messages include:
KLI

ALL CACHES ENABLED
All four of the KL processor caches have been enabled.

KLI -- BOOTSTRAP LOADED AND STARTED
A KL bootstrap program has been loaded into
started.
Any messages that follow are a
particular bootstrap program being used.

KL memory and
function of the

KLI -- CACHES DISABLED
All cache memory has been disabled.
KLI -- CACHES n,n ... ENABLED
The specified caches have been enabled.
KLI -- CONFIGURATION FILE WRITTEN
The KL.CFG file has been updated with a new cache and/or memory
configuration.
This message is issued whenever you set up a
nondefault configuration or if the KL.CFG file did
not
previously exist.
KLI -- KL RESTARTED
The KL processor has been restarted following a
or a hardware or software crash.

power

failure

KLI -- MICROCODE VERSION xxx LOADED
The KL microcode, version xxx, has been loaded
into the KL
system from the appropriate microcode file on the front-end
bootstrap device.
KLI -- MICROCODE VERSION xxx VERIFIED
The KL microcode, version xxx, currently residing in the system
has been compared correctly with the code in the appropriate
microcode file on the front-end bootstrap device.

5.3.2

Warning Messages

Warning messages inform the operator of some unusual condition. After
the message is printed, the KLINIT dialog continues.
These messages
are preceded by "KLI -- % ".
The warning messages include:
KLI -- % EXTERNAL CORE MEMORY IS OFFLINE
KLINIT found
offline.

that

DMA20

external

memory

controller

was

SYSTEM ACTION:
KLINIT attempts to configure the system without the
in question.
5-18

controller

KLINIT
KLI -- % EXTERNAL CORE MEMORY RESOURCES DO NOT MATCH FILE
The external memory resources found by KLINIT do not match the
KL.CFG file.
The KL.CFG file contains more resources than
KLINIT can find on the current system.
This usually means a
controller has dropped off line.
SYSTEM ACTION:
KLINIT attempts to configure the memory it can find in the
closest to that specified in the KL.CFG file.

way

KLI -- % INTERNAL CORE MEMORY RESOURCES DO NOT MATCH FILE
The internal memory resources found by KLINIT do not match the
KL.CFG file.
The KL.CFG file contains more resources than
KLINIT can find on the current system.
This usually means a
controller has dropped off line.
SYSTEM ACTION:
KLINIT attempts to configure the memory it can find in the
closest to that specified in the KL.CFG file.

way

KLI -- % MOS MEMORY IS ALREADY CONFIGURED
KLINIT found that the MOS memory was already configured.
It
does not attempt to reconfigure MaS memory unless specifically
told to do so.
SYSTEM ACTION:
KLINIT proceeds with the initialization.
KLI -- % MOS MEMORY RESOURCES DO NOT MATCH FILE
The MOS memory resources found by KLINIT do not match the
KL.CFG file.
The KL.CFG file contains more resources than
KLINIT can find on the current system. This usually means a
controller has dropped off line or some MOS blocks have been
deallocated by TGHA.
SYSTEM ACTION:
KLINIT attempts to configure the memory it can find in the
closest to that specified in the KL.CFG file.

way

KLI -- % NO FILE - ALL CACHE BEING CONFIGURED
The default to the RECONFIGURE CACHE question was taken,
KLINIT could not find the KL.CFG file in the directory.
SYSTEM ACTION:
KLINIT enables all caches.

5-19

and

KLINIT
KLI -- % NO FILE - ALL MEMORY BEING CONFIGURED
The default to the CONFIGURE KL MEMORY question was taken,
KLINIT could not find the KL.CFG file in the directory.

and

SYSTEM ACTION:
KLINIT confiqures all
available
memory
and
sets
the
interleaving -at the highest level consistent with the setting
of the interleave switches on the memory units.
KLI -- % NO FILE - LOADING BOOTSTRAP
KLINIT could not find -the KL.CFG file or
bootstrap record in the KL.CFG file.

could

not

find

the

SYSTEM ACTION:
KLINIT loads the default bootstrap.
KLI -- % PHYSICAL MEMORY
SUPPRESSED

CONFIGURATION

ALTERED

DUMP

RESTAR'1'

During an automatic reload,
KLINIT found that the physical
configuration of the system does not match the configuration
d€scribed in the KL.CFG file.
SYSTEM ACTION:
KLINIT suppresses the dump or restart, and proceeds
the KL monitor.

5.3.3

reload

Dialog Error Messages

Dialog error messages indicate that your answer to the current KLINrr
II
question is unacceptable.
The message text is preceded by "KLI
The system action for dialog error messages is to repeat the
and the prompt.

question

Currently, the only dialog error message is:
KLI -- COMMAND SYNTAX ERROR
Your reply is not one of the acceptable answers as specified in
the question.
OPERATOR ACTION:
Reply with one of the acceptable answers, correctly spelled, or
use carriage return to take the default answer.

5.3.4

System Error Messages

System error messages indicate conditions in which KLINIT cannot
continue.
These conditions can be brought about by software,
hardware, or environmental failures.
Sometimes are try is successful;
5-20

KLINIT
other times you may require the assistance of your Field Service
Representative or Software Support Specialist. For any system error,
it is important to save all console log data and memory dump listings~
this material is of prime importance when attempting to determine the
cause of the error.
System error messages
are
preceded
by
IIKLI -- ? ".
Unless noted otherwise, the system action for all system error
messages is to restart the KLINIT dialog and repeat the prompt.
Whenever a file is specified in a message text, the file is identified
in the following format.
"dev:filename.ext~ver"

The system messages include:
KLI

? BOOTSTRAP LOAD FAILED

A software or hardware error occurred while the KL bootstrap
program was being loaded.
(See accompanying messages for
additional information.)
OPERATOR ACTION:
Reload the bootstrap program by replying:
KLI)BOOT
If
the
trouble
Representative.
KLI
KLI
KLI
KLI

persists,

call

your

Field

Service

? C-RAM DIFFERS AT xxxxxx
BAD xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xx
GOOD xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xx
XOR xxxxxx xxxxxx xxxxxx xxxxxx xxx xxx xx

During the microcode verify operation; the contents of octal
location xxxxxx in the KL Control RAM did not match the
corresponding code in the appropriate microcode file.
The
actual contents of the location are printed, followed by the
expected contents, and the last line is the result of a
bit-by-bit exclusive or
(XOR) of the actual and expected
values.
OPERATOR ACTION:
Reload the KL microcode and reverify it by means of the KLINIT
dialog.
If the trouble persists, call your Field Service
Representative.
KLI -- ? CACHE ENABLE FAILED
A hardware error has probably occurred while KLINIT was trying
to configure the cache memory.
(See accompanying messages for
additional information.)
OPERATOR ACTION:
Retry the operation; if the trouble persists, call your Field
Service Representative.
You can also temporarily reconfigure
with no cache memory.

5-21

KLINIT
KLI -- ? CANNOT FIND [5,5] DIRECTORY
KLINIT cannot locate the PDP-II system
software error may have overlaid it.

file

directory;

OPERATOR ACTION:
Reload the system;
if the trouble persists, call your Software
Support Specialist.
KLI -- ? CANNOT FIND HALT LOOP
KLINIT tried to start the
properly.

microcode,

but

failed

run

OPERATOR ACTION:
Reload the microcode;
if the trouble persists, call your Field
Service Representative.
KLI -- ? CANNOT GET DEVICES
KLINIT cannot open a system device for communications.
probably a software error in RSX-20F.

This is

OPERATOR ACTION:
Reload the system;
if the trouble persists, call your Software
Support Specialist.
KLI -- ? CANNOT RUN KLINIT WHILE KL IS IN PRIMARY PROTOCOL
An attempt was made to run the KLINIT program while the KL
processor was runnlng. This condition can arlse only if KLINIT
is loaded by means of the PARSER command language instruction:
PAR>RUN KLINIT
OPERATOR ACTION:
If the intent was to rerun KLINIT,
follow the appropriate
procedures to shut down TOPS-IO or TOPS-20;
then reload the
system and enter the KLINIT program.
If TOPS-IO or TOPS-20
does not shut down properly, set the console mode to PROGRAMMER
and reload KLINIT.
KLI -- ? CANNOT START KL
A hardware or software failure occured while trying to restart
from
a
power
failure
or
system crash during memory
determination.
(See accompanying messages for
additional
information.)
OPERATOR ACTION:
Reload the microcode and retry the operation.
If
persists, call your Field Service Representative.

5-22

the

trouble

KLINIT
KLI -- ? CAN'T DETERMINE KLIO HARDWARE ENVIRONMENT
This message is followed immediately by one of the following
messages.
If the error occurred in the KLINIT dialog, you will
get
KLI -- % PROCEED AT YOUR OWN RISK
while if the error occurred during
will get

automatic

reload,

you

KLI -- % AUTOMATIC RELOAD ABORTED
OPERATOR ACTION:
Contact your Field Service Representative.
KLI -- ? CAN'T SUPPORT MOS MEMORY ON A MODEL "A" CPU
KLINIT has conflicting information on the hardware available to
it.
OPERATOR ACTION:
Contact your Field Service Representative.
KLI -- ? CLOCK ERROR STOP DURING KL RESTART
The KL processor clock stopped while KLINIT was monitoring a
restart operation.
(See accompanying messages for additional
information.)
OPERATOR ACTION:
Retry loading the KL bootstrap and monitor.
If
persists, call your Software Support Specialist.

the

trouble

KLI -- ? CONFIGURATION FILE NOT CHANGED
The KL.CFG configuration file cannot be updated because the old
file cannot be read, the new file cannot be written, or some
other error has occurred.
(See accompanying messages for
additional information.)
OPERATOR ACTION:
Delete the old configuration file and retry the operation.
If
the trouble persists, call your Software Support Specialist.
KLI
KLI
KLI
KLI

? D-RAM DIFFERS AT xxxxxx
BAD A:x B:x P:x J:xxxx A:x B:x P:x J:xxxx
GOOD A:x B:x P:x J:xxxx A:x B:x P:x J:xxxx
XOR A:x B:x P:x J:xxxx A:x B:x P:x J:xxxx

During the microcode verify operation, the contents of octal
location xxxxxx
in the KL Dispatch RAM did not match the
corresponding code in the appropriate microcode file.

5-23

KLINIT
the even
The actual contents of the locations are printed,
This line is
location first,
and the odd location next.
The
followed by the expected contents of the two locations.
last line is the result of a bit-by-bit exclusive or (XOR) of
the actual and expected values.
OPERATOR ACTION:
Reload the KL microcode and reverify it by means of the KLINI1'
dialog.
If the trouble persists,
call your Field Service
Representative.
KLI -- ? DEPOSIT FAILED
KLINIT could not store information into KL memory.
OPERATOR ACTION:
Reload the system and retry the operation.
If
persists, call your Field Service Representative.

the

trouble

KLINIT cannot find room on the specified front-end load
for an updated copy of the configuration file KL.CFG.

device

KLI -- ? DEVICE "device" FULL

OPERATOR ACTION:
Exit from KLINIT and use a front-end system program such as PIP
to delete some files and make room for the updated KL.CFG file.
(Make sure that you do not delete any files
that contain
RSX-20F software.
You may wish to consult a system programmer
or the system administrator to determine which files can be
deleted.) Then reenter KLINIT and retry the operation.
KLI -- ? DF EXECUTE FAILED
A diagnostic function execute
initializing the KL processor.

failed

while

KLINIT

was

OPERATOR ACTION:
Reload the system and retry the operation.
If
persists, call your Field Service Representative.

the

trouble

KLI -- ? DF READ FAILED
A diagnostic function read failed while KLINIT was initializing
the KL processor.
OPERATOR ACTION:
Reload the system and retry the operation.
If
persists, call your Field Service Representativeo

the

trouble

KLI -- ? DF WRITE FAILED
A diagnostic function
write
initializing the KL processor.

failed

while

KLINIT

was

OPERATOR ACTION:
Reload the system and retry the operation.
If
persists, call your Field Service Representative.

5-24

the

trouble

KLINIT
KLI -- ? DIRECTIVE ERROR -n ON FILE "filename"
A system error occurred while KLINIT was trying to access the
file "filename." The "n" is an octal error code for use by
software support.
OPERATOR ACTION:
Reload the system and retry the operation.
If
persists, call your Software Support Specialist.

the

trouble

the

trouble

KLI -- ? EXAMINE FAILED
KLINIT could not examine contents of KL memory.
OPERATOR ACTION:
Reload the system and retry the operation.
If
persists, call your Field Service Representative.
KLI -- ? FATAL MEMORY CONFIGURATION ERROR - CODE "xxx"
KLINIT encountered an error in attempting to configure memory.
The type of error encountered is specified by the code xxx.
Most of these errors are hardware problems or software bugs.
The possible codes are listed below, along with the corrective
action that can be tried, if any exists.
Code

Corrective Action

3BB

No corrective action is possible. This error code was
inserted as a debugging aid, and is not expected to occur
in normal operation. A CPU fault could 'be responsible.
Run diagnostics on the CPU and call Field Service.

ABS

No corrective action is possible. The CPU has made
error. Run diagnostics on it and call Field Service.

APL

Make sure the microcode is
problem recurs, the CPU
Field Service.

B4M

No corrective action is possible.
If the hardware
environment has not changed, and you have been able to
boot memory successfully in the past, the problem is
likely to be in the hardware. If, on the other hand, you
have an odd hardware configuration, you may have come
across a software bug.
If Field Service is unable to
find the problem, contact a Software Support Specialist.

BCM

BTL

This is a pure
No corrective action is possible.
software bug. Contact a Software Support Specialist.

CES

This is
almost
No corrective action is possible.
certainly a hardware fault. Contact Field Service.

5-25

loaded and retry.
If the
has most likely failed. Call

KLINIT
Code

Corrective Action

CFT

No corrective action
is possible.
If the hardware
environment has not changed, and you have been able to
boot memory successfully in the past,
the problem is
likely to be in the hardware.
If, on the other hand, you
have an odd hardware configuration,
you may have come
across a
software bug.
If Field Service is unable to
find the problem, contact a Software Support Specialist.

CTF

Set all MF20 controllers to software state 0 and retry.
If the problem persists,
call Field Service.
This
condition could not be created by MF20 software.
It
could happen as a result of user setting of the function
I software state bits.

DCB

No corrective action is possible.
This
is a pure
software bug.
Contact a Software Support Specialist.

EDE

Make sure the microcode is loaded and
failure recurs, call Field Service.

FOE

No corrective action is
Support Specialist.

GOO

No corrective action
is possible.
If the hardware
environment has not changed, and you have been able to
boot memory successfully in the past,
the problem is
likely to be in the hardware.
If, on the other hand, you
have an odd hardware configuration,
you may have come
across a
software bug.
If Field Service is unable to
find the problem, contact a Software Support Specialist.

HOV

No corrective action is possible.
This
is a pure
Contact a Software Support Specialist.
software bug.

lEE

Make sure the microcode is loaded and
failure recurs, call Field Service.

LDE

This
is a pure
No corrective action is possible.
software bug.
Contact a Software Support Specialist.

MAB

This
is a pure
No corrective action is possible.
software bug.
Contact a Software Support Specialist.

MFE

No corrective action is possible.
This halt often
indicates a memory controller failure, especially if the
hardware environment has not changed and you have been
able to boot memory in the past.
You may also have
uncovered a software bug.
If Field Service cannot find
the problem, contact a Software Support Specialist.

MMR

No corrective action is possible.
This is a pure
software bug.
Contact a Software Support Specialist.

MNA

No corrective action is possible.
If the hardware
environment has not changed, and you have been able to
boot memory successfully in the past,
the problem is
likely to be in the hardware.
If, on the other hand, you
have an odd hardware configuration,
you may have come
across a
software bug.
If Field Service is unable to
find the problem, contact a Software Support Specialist.

5-26

possible.

retry.

Contact

retry.

the

Software

the

KLINIT

Code

Corrective Action

NBS