Digital PDFs

EK-337AB-TI-2

March 1991

100 pages

Original

0.2MB

Document:	VAX 4000 Model 300 Technical Information
Order Number:	EK-337AB-TI
Revision:	2
Pages:	100
Original Filename:

OCR Text

VAX 4000 Model 300
Technical Information
Order Number EK–337AB–TI–002

Digital Equipment Corporation
Maynard, Massachusetts

First Printing, March 1990
Revised, June 1991
The information in this document is subject to change without notice and should not be
construed as a commitment by Digital Equipment Corporation.
Digital Equipment Corporation assumes no responsibility for any errors that may appear in
this document.
The software, if any, described in this document is furnished under a license and may be used
or copied only in accordance with the terms of such license. No responsibility is assumed
for the use or reliability of software or equipment that is not supplied by Digital Equipment
Corporation or its affiliated companies.
Restricted Rights: Use, duplication or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227–7013.
©Digital Equipment Corporation, 1990, 1991. All rights reserved.
Printed in U.S.A.
The Reader’s Comments form at the end of this document requests your critical evaluation to
assist in preparing future documentation.
The following are trademarks of Digital Equipment Corporation: CompacTape, CX, DDCMP,
DEC, DECconnect, DECdirect, DECnet, DECscan, DECserver, DECUS, DECwindows,
DELNI, DEMPR, DESQA, DESTA, DSRVB, DSSI, IVAX, KDA, KLESI, MicroVAX, MSCP,
Q-bus, Q22-bus, RA, RQDX, RV20, SA, SDI, ThinWire, TK, TMSCP, TQK, TS05, TU, VAX,
VAX 4000, VAXcluster, VAX DOCUMENT, VAXELN, VAXlab, VAXserver, VMS, VT, and the
DIGITAL logo.
Amphenol is a trademark of Amphenol Corporation. Bell is a trademark of Bell telephone
companies. CHAMP is a registered trademark of AMP Inc. IBM is a trademark of
International Business Machines Corporation.
FCC NOTICE: The equipment described in this manual generates, uses, and may emit radio
frequency energy. The equipment has been type tested and found to comply with the limits for
a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed
to provide reasonable protection against such radio frequency interference when operated in
a commercial environment. Operation of this equipment in a residential area may cause
interference, in which case the user at his own expense may be required to take measures to
correct the interference.
S1687

This document was prepared using VAX DOCUMENT, Version 1.2.

Contents
Preface

vii

Chapter 1 Base System Description
1.1
1.2
1.3
1.4
1.4.1
1.4.2
1.5
1.6
1.7

System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
Firmware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
Power-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Console I/O Mode Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Control Characters in Console I/O Mode . . . . . . . . . . . . . . 1–4
Console I/O Mode Commands . . . . . . . . . . . . . . . . . . . . . . . 1–6
Digital Storage Systems Interconnect (DSSI) . . . . . . . . . . . . . 1–13
KA670–AA/BA CPU Specifications . . . . . . . . . . . . . . . . . . . . . 1–14
MS670–BA and –CA Memory Specifications . . . . . . . . . . . . . 1–17

Chapter 2 Option Specifications
2.1
Options Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2
Mass Storage Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1
KDA50 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2
KFQSA Storage Adapter . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3
KLESI Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.4
KZQSA Storage Adapter . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.5
RA60 Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.6
RA70E Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.7
RA81 Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.8
RA82 Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.9
RA90 Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.10 RA92 Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.11 RF31 Integrated Storage Element (ISE) . . . . . . . . . . . . . .

2–2
2–2
2–3
2–4
2–5
2–6
2–7
2–8
2–9
2–10
2–11
2–12
2–13
2–14

iii

2.2.12 RF31F Integrated Storage Element . . . . . . . . . . . . . . . . . .
2.2.13 RF71 Integrated Storage Element (ISE) . . . . . . . . . . . . . .
2.2.14 RF72 Integrated Storage Element (ISE) . . . . . . . . . . . . . .
2.2.15 RRD40 Compact-Disc Subsystem . . . . . . . . . . . . . . . . . . . .
2.2.16 RRD42 Optical Compact-Disc Subsystem . . . . . . . . . . . . . .
2.2.17 TF85 Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.18 TK50 Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.19 TK70 Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.20 TLZ04 Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.21 TQK70 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.22 TSZ07 Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.23 TSV05 Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.24 TSV05 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.25 TU81–Plus Tape Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3
Communications Options . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1
CXA16 Asynchronous Multiplexer (16 lines) . . . . . . . . . . .
2.3.2
CXB16 Asynchronous Multiplexer (16 lines) . . . . . . . . . . .
2.3.3
CXY08 Asynchronous Multiplexer (8 Lines) . . . . . . . . . . . .
2.3.4
DEQRA Token Ring Q-Bus Adapter . . . . . . . . . . . . . . . . . .
2.3.5
DESQA Ethernet Controller . . . . . . . . . . . . . . . . . . . . . . .
2.3.6
DFA01 Asynchronous Controller with Integral Modem . . .
2.3.7
DPV11 Synchronous Controller . . . . . . . . . . . . . . . . . . . . .
2.3.8
DSRVB DECserver 200 . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.9
DSV11 Synchronous Controller . . . . . . . . . . . . . . . . . . . . .
2.4
Real-Time Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1
AAV11–S Digital-to-Analog Converter . . . . . . . . . . . . . . . .
2.4.2
ADV11–S Analog-to-Digital Converter . . . . . . . . . . . . . . . .
2.4.3
AXV11 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.4
DIV32 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.5
DRQ3B Parallel Interface . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.6
DRV1W Parallel Interface . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.7
IBQ01 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.8
IEQ11 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.9
KWV11–S Programmable Real-Time Clock . . . . . . . . . . . .
2.5
Printer Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.1
LPV11–SA Printer Interface . . . . . . . . . . . . . . . . . . . . . . .

2–15
2–17
2–18
2–19
2–20
2–21
2–23
2–25
2–27
2–29
2–30
2–32
2–33
2–34
2–36
2–37
2–40
2–43
2–45
2–47
2–48
2–50
2–51
2–53
2–54
2–55
2–57
2–59
2–61
2–62
2–63
2–65
2–66
2–67
2–69
2–69

2.6
Graphics Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–70
2.6.1
VS30U Graphics Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . 2–70

Chapter 3 System Expansion
3.1
3.2

Planning System Expansion . . . . . . . . . . . . . . . . . . . . . . . . . .
Completing the VAX 4000 Model 300 Configuration
Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1
3–2

Index
Examples
1–1
1–2
1–3
1–4
1–5
1–6

SHOW QBUS Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW DEVICE Display . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW ETHERNET Display . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW LANGUAGE Display . . . . . . . . . . . . . . . . . . . . . . . . .
SET LANGUAGE Command . . . . . . . . . . . . . . . . . . . . . . . . .
SET BOOT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–9
1–10
1–10
1–11
1–11
1–11

Figures
1–1
3–1

VAX 4000 Model 300 Block Diagram . . . . . . . . . . . . . . . . . . .
VAX 4000 Model 300 (BA440 Enclosure) Configuration
Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2
3–3

Tables
1–1
1–2
1–3
3–1

Console I/O Mode Control Characters . . . . . . . . . . . . . . . . . . 1–5
Console I/O Mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
Device Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4

Preface
This manual provides a summary of technical information about the VAX
4000 Model 300 system.
The manual is organized as follows:
•

Chapter 1 describes the base system and lists specifications for the
KA670–AA/–BA CPU module and MS670–BA memory modules.

•

Chapter 2 describes optional components available for your system and
lists their specifications.

NOTE: You will find a glossary in the Operation manual to help with word
definitions and acronyms.

Conventions
The following conventions are used in this manual:
Convention

Meaning

Return

A key name is shown enclosed to indicate that you press a named
key on the keyboard.

Ctrl/x

A sequence such as Ctrl/x indicates that you must hold down the
key labeled Ctrl while you press another key.

BOLD

This bold type indicates user input. For example:

>>> BOOT MUAO
This line shows that the user must enter BOOT MUAO at the
console prompt.
NOTE

Notes provide general information about the current topic.

CAUTION

Cautions provide information to prevent damage to equipment
or software. Read these carefully.

WARNING

Warnings provide information to prevent personal injury. Read
these carefully.

vii

Chapter 1

Base System Description
This chapter describes the VAX 4000 Model 300 base system, including the
following:
•

Power-up self-tests

•

Digital Storage Systems Interconnect (DSSI) architecture

•

Specifications for the KA670–AA/–BA CPU and MS670–BA and –CA
memory

1.1 System Overview
All VAX 4000 Model 300 base system components are housed in a BA440
enclosure, which contains a 12-slot backplane.
Each base system contains the following:
•

A KA670–AA/–BA (L4000–A/–B) central processing unit (CPU) module

•

From one to four MS670–BA or –CA memory modules.

The base system modules are located in the following BA440 card slots:
•

Any MS670 memory modules are installed in slots 1 through 4.

•

The KA670 CPU module is installed in slot 5.

The base system operates from the KA670 CPU firmware and the controls
on the console module. The firmware is described in Section 1.2. Base
system operation also integrates Digital Storage Systems Interconnect
(DSSI) technology, which is discussed in Section 1.5.
Figure 1–1 is a block diagram of the VAX 4000 Model 300 system.

Base System Description

1–1

Figure 1–1: VAX 4000 Model 300 Block Diagram

Real-Time
Devices

Main
Memory

Q22-bus

Memory
Interconnect
Ethernet
CPU
Module

Communication
Devices
DSSI
Bus

Tape Drive
Controller

Tape Drive

Disk

Console

DSSI
Bus

Disk

MLO-003829

1–2 VAX 4000 Model 300 Technical Information

1.2 Firmware Overview
Two electrically programmable read-only memory (EPROM) chips on the
KA670 CPU module contain the firmware. This firmware consists of the
following three major programs, which perform the system power-up selftests and diagnostics:
•

A console program

•

A set of self-tests for the CPU and memory

•

A primary bootstrap program (VMB)

The console program receives control whenever the processor halts. In
a processor halt, processor control passes to the console program and
instruction execution continues. The standard VAX console functionality
is emulated whenever you execute a program in ROM.
Control passes to the firmware under any of the following conditions:
•

You turn on the system.

•

You press the Restart button.

•

You assert the Q22-bus BHALT signal by pressing the Halt button.

•

You enter a break when the Break Enable/Disable switch is set to
enable.

•

A HALT instruction is executed.

•

A system error occurs.

Base System Description

1–3

1.3 Power-Up
At power-up, the console program determines the console device type and
console language, then runs the self-tests for the CPU and memory. You
choose the console language when you perform the set-up operations during
your console terminal installation procedure.
You determine the type of power-up mode by setting the Power-Up Mode
switch on the CPU console module. See your VAX 4000 Dual-Host Systems
manual for the following power-up information:
•

Power-up procedures

•

Power-Up Mode and Break Enable/Disable switch settings

•

Examples of successful power-up sequences

•

Boot and autoboot procedures

See the VAX 4000 Troubleshooting and Diagnostics manual for examples of
problems you may encounter during power-up.

1.4 Console I/O Mode Overview
If you set the Break Enable/Disable switch on the console module to enable,
the console program enters Console I/O mode after the power-up self-tests
are completed successfully. The console program also enters Console I/O
mode in response to any external halt condition.
CAUTION: Do not press the Restart button while the console program is
in console mode. Doing so destroys the system state and prevents normal
operation.
Console I/O mode allows you to control the system by typing commands
at the console prompt (>>>). You may enter these commands in either
uppercase or lowercase letters. Enter each command, then press Return .

1.4.1 Control Characters in Console I/O Mode
Table 1–1 lists the keypad control characters that have special meaning in
Console I/O mode.

1–4 VAX 4000 Model 300 Technical Information

Table 1–1: Console I/O Mode Control Characters
Character
also <CR>

Return

Action

(rubout)

The carriage return ends a command line. No action is taken on
a command until after it is terminated by a carriage return. A
null line terminated by a carriage return is treated as a valid, null
command. No action is taken, and the console prompts for input.
Carriage return is echoed as carriage return, line feed (<CR><LF>).
When you press x (rubout), the console deletes the previously typed
character. The resulting display differs, depending on whether the
console is a video or a hardcopy terminal.
For hardcopy terminals, the console echoes a backslash (\ )
followed by the character being deleted. If you press additional
rubouts, the additional deleted characters are echoed. If you type a
non-rubout character, the console echoes another backslash, followed
by the character typed. The result is to echo the characters deleted,
surrounding them with backslashes. For example:
EXAMI;E X X NE<CR>
The console echoes: EXAMI;E\ E;\ NE<CR>
The console sees the command line: EXAMINE<CR>
For video terminals, the previous character is erased and the
cursor is restored to its previous position.

or F14

Ctrl/A
Ctrl/C

Ctrl/D
Ctrl/E
Ctrl/F

Ctrl/B ,
Ctrl/H ,
F12
Ctrl/O

Ctrl/Q

, or
(rubout), or

The console does not delete characters past the beginning of a
command line. If you press more rubouts than there are characters
on the line, the extra rubouts are ignored. A rubout entered on a
blank line is ignored.
Toggles insertion/overstrike mode for command line editing. By
default, the console powers up to overstrike mode.
Echoes ^C<CR> and aborts processing of a command. Has no effect
as part of a binary load data stream. Clears Ctrl/S and reenables
output stopped by Ctrl/O .
Moves the cursor one position to the left.
Moves the cursor to the end of the line.
Moves the cursor one position to the right.
Recalls the previous commands.
Deletes the previously typed character. Same function as X
(rubout), above.
Ignores transmissions to the console until you enter Ctrl/O . Echoes
^O when disabling output, which is not echoed when it reenables
output. Output is reenabled if the console prints an error message,
or if it prompts for a command from the terminal. Output is also
enabled by entering Maintenance mode: press Break or enter Ctrl/C .
Resumes output to the console terminal. Not echoed.

Base System Description

1–5

Table 1–1 (Cont.): Console I/O Mode Control Characters
Character

Action

Ctrl/R

Echoes <CR><LF>, followed by the current command line. Can be
used to improve the readability of a command line that has been
heavily edited.
Stops output to the console terminal until you enter Ctrl/Q . Not
echoed.
Echoes ^U<CR>. Entered, but otherwise ignored if typed on an
empty line.

Ctrl/S
Ctrl/U

The console accepts Console I/O mode commands up to 80 characters long.
Longer commands produce error messages. The character count does not
include rubouts, rubbed-out characters, or the <CR> at the end of the
command.
Two or more consecutive spaces and tabs are treated as a single space.
Leading and trailing spaces and tabs are ignored. You can place command
qualifiers after the command keyword or after any symbol or number in
the command.
All numbers (addresses, data, counts) are hexadecimal, but symbolic
register names contain decimal register numbers. The hexadecimal digits
are 0 through 9 and A through F. You can use uppercase and lowercase
letters in hexadecimal numbers (A through F) and commands.
The following symbols are qualifier and argument conventions:
[ ] = an optional qualifier or argument
{} = a required qualifier or argument

1.4.2 Console I/O Mode Commands
Table 1–2 lists and describes the Console I/O mode commands. You can
display the list of commands by entering HELP at the console prompt (>>>).
For a complete explanation of how to use the commands, along with
information on qualifiers and arguments, refer to the KA670 CPU Technical
Manual (EK–KA670–TM).

1–6 VAX 4000 Model 300 Technical Information

Table 1–2: Console I/O Mode Commands
Command

Action

BOOT
CONFIGURE

Initializes the processor and transfers execution to the VMB.
Invokes an interactive mode that permits you to enter Q22-bus
device names, then generates a table of Q22-bus I/O page device
CSR addresses and interrupt vectors.
Causes the processor to begin instruction execution at the address
currently contained in the program counter (PC). Does not perform
a processor initialization.
Deposits data into the address you specify. If you do not specify
an address space or data size qualifier, the console uses the last
address space and data size used in a DEPOSIT, EXAMINE,
MOVE, or SEARCH command.
Examines the contents of the memory location or register of the
address you specify. If you do not specify an address, + is assumed.
Searches main memory starting at address 0 (zero) for a pagealigned 128-Kbyte segment of good memory, or a restart parameter
block (RPB).
The HALT command has no effect. It is included for compatibility
with other VAX consoles.
Displays the correct syntax for all console commands.
Performs a processor initialization.
Copies the block of memory starting at the source address to a
block beginning at the destination address.
Executes the number of macro instructions you specify. If you do
not specify a number, 1 (one) is assumed.
Repeatedly displays and executes the command you specify. Press
Ctrl/C to stop the command. You can specify any valid console
command except the REPEAT command.
Finds all occurrences of a pattern and reports the addresses where
the pattern was found. If you include the /NOT qualifier, the
command reports all addresses for which the pattern did not
match.
Sets the default R5 boot flags. The value must be a hexadecimal
number of up to eight digits.
Sets the default boot device. The value must be a valid device
name.
Sets Control-P as the console halt condition, instead of a BREAK.
Connects to the DUP or MAINTENANCE driver on the node or
device you specify.
Sets the console language and keyboard type.
Sets the halt action you define. Acceptable values are the following
keywords: default, restart, reboot, halt, restart_reboot, or a
number in the range 0 to 4 inclusive.
Sets command recall state to either ENABLED (1) or DISABLED
(0).

CONTINUE
DEPOSIT

EXAMINE
FIND
HALT
HELP
INITIALIZE
MOVE
NEXT
REPEAT
SEARCH

SET BFLAG
SET BOOT
SET CONTROLP
SET HOST
SET LANGUAGE
SET HALT
SET RECALL

Base System Description

1–7

Table 1–2 (Cont.): Console I/O Mode Commands
Command

Action

SHOW BFLAG
SHOW BOOT
SHOW CONTROLP

Displays the default R5 boot flags.
Displays the default boot device.
Shows the current state of Control-P halt recognition, either
ENABLED or DISABLED.
Displays all devices displayed by the SHOW DSSI, SHOW
ETHERNET, and SHOW UQSSP commands.
Displays the status of all nodes that can be found on the DSSI
bus. For each node on the DSSI bus, the firmware displays the
node number, the node name, and the boot name and type of the
device, if available. Does not indicate whether the device contains
a bootable image.
Displays the hardware Ethernet address for all Ethernet adapters
that can be found, both on-board and on the Q22-bus.
Displays console language and keyboard type.
Displays main memory configuration, board by board.
Displays all Q22-bus I/O addresses that respond to an aligned
word read, plus vector and device name information. For each
address, the console displays the address in the VAX I/O space in
hexadecimal, the address as it would appear in the Q22-bus I/O
space in octal, and the word that was read in hexadecimal. Also
displays the vector that you should set up, and device name or
names that could be associated with the CSR.
Displays the current state of command recall, either ENABLED or
DISABLED.
Displays the halt action. Keywords include: default, restart,
reboot, halt, restart_reboot or a number in the range 0 to 4
inclusive.
Displays all RL01 and RL02 disks that appear on the Q22-bus.
Shows any SCSI devices in the system.
Shows any virtual addresses that map to the specified physical
address.
Displays the status of all disks and tapes that can be found on the
Q22-bus that support the UQSSP protocol. For each such disk or
tape on the Q22-bus, the firmware displays the controller number,
the controller CSR address, and the boot name and type of each
device connected to the controller. The command does not indicate
whether the device contains a bootable image.
Displays the current firmware version.
Starts instruction execution at the address you specify. If you
do not give an address, the current program counter is used. If
memory mapping is enabled, macro instructions are executed from
virtual memory, and the address is treated as a virtual address.
Equivalent to a DEPOSIT to PC, followed by a CONTINUE. Does
not perform a processor initialization.

SHOW DEVICE
SHOW DSSI

SHOW ETHERNET
SHOW LANGUAGE
SHOW MEMORY
SHOW QBUS

SHOW RECALL
SHOW HALT
SHOW RLV12
SHOW SCSI
SHOW TRANSLATION
SHOW UQSSP

SHOW VERSION
START

1–8 VAX 4000 Model 300 Technical Information

Table 1–2 (Cont.): Console I/O Mode Commands
Command

Action

TEST

Invokes a diagnostic test program specified by the test number
you enter. If you enter a test number of 0 (zero), all tests allowed
to be executed from the console terminal are executed. The
console accepts an optional list of up to five additional hexadecimal
arguments.
Performs an I/O bus reset, by writing a 1 (one) to IPR 55 (decimal).
Loads or unloads (that is, writes to memory or reads from memory)
the specified number of data bytes through the console serial line
(regardless of console type), starting at the specified address. For
use by automatic systems communicating with the console.

UNJAM
X

Examples 1–1 through 1–6 show sample displays for the commonly used
commands SHOW and SET.
The SET command sets the parameter to the value you specify. The SHOW
command displays the console parameter you specify.
Example 1–1: SHOW QBUS Display
>>> SHOW QBUS
Scan of Qbus I/O Space
-200000DC (760334) = 0000 (300) RQDX3/KDA50/RRD50/RQC25/KFQSA-DISK
-200000DE (760336) = 0AA0
-200000E0 (760340) = 0000 (304) RQDX3/KDA50/RRD50/RQC25/KFQSA-DISK
-200000E2 (760342) = 0AA0
-200000E4 (760344) = 0000 (310) RQDX3/KDA50/RRD50/RQC25/KFQSA-DISK
-200000E6 (760346) = 0AA0
-20001468 (772150) = 0000 (154) RQDX3/KDA50/RRD50/RQC25/KFQSA-DISK
-2000146A (772152) = 0AA0
-20001F40 (777500) = 0020 (004) IPCR
Scan of Qbus Memory Space
>>>

For each address, the console displays the address in the VAX I/O space in
hexadecimal, the address as it would appear in the Q22-bus I/O space in
octal, and the word data that was read in hexadecimal.

Base System Description

1–9

Example 1–2: SHOW DEVICE Display
>>>SHOW DEVICE
DSSI Bus 0 Node 0 (BARNEY)
-DIA10 (RF71)
DSSI Bus 0 Node 1 (BETTY)
-DIA11 (RF71)
DSSI Bus 0 Node 2 (FRED)
-DIA12 (RF71)
DSSI Bus 0 Node 7 (*)
DSSI Bus 1 Node 0 (SNEEZY)
-DIB0 (RF71)
DSSI Bus 1 Node 1 (DOPEY)
-DIB1 (RF71)
DSSI Bus 1 Node 2 (SLEEPY)
-DIB2 (RF71)
DSSI Bus 1 Node 3 (GRUMPY)
-DIB3 (RF71)
DSSI Bus 1 Node 4 (BASHFUL)
-DIB4 (RF71)
DSSI Bus 1 Node 5 (HAPPY)
-DIB5 (RF71)
DSSI Bus 1 Node 6 (DOC)
-DIB6 (RF71)
DSSI Bus 1 Node 7 (*)
UQSSP Tape Controller 0 (774500)
-MUA0 (TK70)
Ethernet Adapter
-EZA0 (08-00-2B-06-10-42)

For each device, the console displays the controller, the node, and the
address on the first line, and the device name and option on the second
line.
Example 1–3: SHOW ETHERNET Display
>>> SHOW ETHERNET
Ethernet Adapter
-EZA0 (08-00-2B-0B-29-14)

1–10 VAX 4000 Model 300 Technical Information

Example 1–4: SHOW LANGUAGE Display
>>> SHOW LANGUAGE
English (United States/Canada)
>>>

Example 1–5: SET LANGUAGE Command
>>> SET LANGUAGE 5
>>>

In this example, selection 5 is English, chosen from the language selection
menu that displays at power-up.
Example 1–6: SET BOOT Command
>>> SET BOOT MUA0
>>>

In this example, entering MUA0 sets the tape drive as the default boot
device. Table 1–3 lists all supported device names.

Base System Description

1–11

Table 1–3: Device Names
Device Logical
Name

Device Type

Controller/Adapter

RF-series ISE

Embedded DSSI host adapter
(part of CPU)

DImn1

RF-series ISE

KFQSA storage adapter

DUcn2

TF85 tape drive

Embedded DSSI adapter

MImu1

TK70 tape drive

TQK70

MUcn3

PROM (programmable read
only memory)

MRV11 module

PRAn

Ethernet adapter

On-board (part of CPU)

EZA0

Ethernet adapter

DESQA Ethernet controller

XQAn

RA-series drives

KDA50

DUcn2

1 m = DSSI bus adapter (A = first bus (0), B = second bus (1), etc.)

n = unit number
When under operating system control, DIBn devices are recognized as DIAn devices.
2 c = MSCP controller designator (A = first, B = second, etc.)
n = unit number
3 c = TMSCP controller designator (A = first, B = second, etc.)
n = unit number

1–12 VAX 4000 Model 300 Technical Information

1.5 Digital Storage Systems Interconnect (DSSI)
The KA670 CPU module contains two DSSI bus interfaces that are
dedicated to the mass storage devices in the VAX 4000 Model 300 system.
Each DSSI bus interface connects to a DSSI integrated storage element
(ISE). An ISE is a 5.25-inch integrated storage element that is housed
in a special mounting bracket for simplified enclosure installation and
upgrading.
Each DSSI bus has the following characteristics:
•

A 4-Mbytes-per-second bandwidth

•

Up to eight nodes (one interface and up to seven ISEs)

•

Eight data lines

•

One parity line

•

Eight control lines

DSSI architecture improves system performance as follows:
•

The DSSI bus handles all mass storage transactions.

•

Mass storage devices can act independently, since each device contains
its own controller. Several devices can work simultaneously.

The two DSSI bus interfaces support up to 16 nodes. These 16 nodes include
the 2 DSSI interfaces and 14 ISEs.
An ISE can maintain connections to more than one DSSI interface. In a
dual-host configuration in which multiple CPUs can be connected to the
DSSI bus interfaces, two VAX 4000 Model 300 systems have access to each
ISE on the DSSI busses.
For more information about dual hosting VAX 4000 Model 300 systems
and the advantages of such configurations, see the section on dual-host
capability in the VAX 4000 Model 300 Operation manual.

Base System Description

1–13

1.6 KA670–AA/BA CPU Specifications
The VAX 4000 Model 300 system uses the KA670–AA central processing
unit.
The VAXserver 4000 Model 300 uses the KA670–BA central
processing unit.
Central Processing Unit
Addressing modes
Clock rate
Data path width
Number of data types
Number of instructions
General purpose registers

PDP–11 compatibility mode
Time bases

I/O bus interface
Backplane termination

General register: 8
143 MHz
64 bits
Hardware: 9
Software emulated: 7
Hardware: 272
Software emulated: 32
16 (32-bit wide)
Program counter: 4
Index: 9
Emulated in software
Time-of-year clock: 1 (battery backup)
Interval timer: 1 (10 milliseconds)
Programmable timers: 2
One Q22-bus interface with 8192 entry map
240

Memory Management and Control
Page size
Virtual address space
Physical memory space
Number of memory modules

512 bytes
4 gigabytes
512 Mbytes
4 maximum

Performance
Instruction prefetch buffer size
On-chip cache
Size
Speed
Associativity
On-board cache
Size
Speed

12 bytes
2 Kbyte
28 nanoseconds
Direct mapped
128 Kbytes
84 nanoseconds

1–14 VAX 4000 Model 300 Technical Information

Performance
Associativity
Translation buffer
Size
Associativity
Q22-bus address translation
map cache
Size
Associativity
I/O bus buffer size
Input
Output
Maximum I/O bandwidth
Block mode DMA read
Block mode DMA write

Direct mapped
64 entry
Fully associative

16 entry
Fully associative
32 bytes
4 bytes
2.4 Mbytes/second
3.3 Mbytes/second

Ethernet Port
Supported protocols
Supported media types
Data path width
Maximum bandwidth
Buffer size
Transmit buffer
Receiver buffer

Ethernet V2.0
Standard or ThinWire
1 bit
10 Mbits/second
128 bytes/second
128 bytes/second

Digital Storage Systems Interconnect (DSSI) Connector
Maximum number of supported devices
Data path width
Maximum bandwidth
Maximum queue I/O
Buffer size
Transmit buffer
Receiver buffer

14
8 bits
4 Mbytes/second
800/second
128 bytes/second
128 bytes/second

Console Serial Line
Interface standards

EIA RS–423–A/CCITT V.10 X.26
EIA RS–232–C/CCITT V.28
DEC–423

Base System Description

1–15

Console Serial Line
Data format
Baud rates

1 start bit, 8 data bits, 0 parity bits, 1 stop
bit
300; 600; 1200; 2400; 4800; 9600; 19,200;
38,400

Ordering Information
Included as part of base system

Configuration Information
Form factor
Power requirements
Power consumption
Bus loads

Quad height
+5 Vdc, 7.4 A; +3.3 Vdc, 0.27 A
+12 Vdc, 0.35 A; –12 Vdc, 0.04 A
42.6 W
4.0 ac; 1.0 dc

Operating System Support
VMS
VAXELN

Version 5.3–2 and later

Diagnostic Support
MicroVAX Diagnostic Monitor
Self-tests

Release 131 and later
Yes

Related Documentation
EK–KA670–TM
EK–347AB–MG

KA670 CPU Technical Manual
KA670 CPU System Maintenance

1–16 VAX 4000 Model 300 Technical Information

1.7 MS670–BA and –CA Memory Specifications
The MS670–BA is a 32-Mbyte memory module that provides memory
expansion for the KA670–AA/–BA CPU module. The MS670–CA is a
64-Mbyte memory module. The MS670 modules interface with the CPU
through the MS670 local memory interconnect.
You can use up to four MS670 modules in the VAX 4000 Model 300 system.
Operating system support and diagnostic support are the same as for the
KA670 CPU module, as listed in Section 1.6.
Performance
Memory Cycle Time at 28 nanoseconds:
Memory Read (Octaword):
Page mode memory read
Non-page mode memory read
Memory write (Octaword):
Page mode memory write
Non-page mode memory write
Memory masked write (Longword):
Page mode memory write
Non-page mode memory write

392 nanoseconds
756 nanoseconds
308 nanoseconds
504 nanoseconds
399 nanoseconds
504 nanoseconds

Ordering Information
MS670–BA
MS670–CA

32-Mbyte field-installed kit
64-Mbyte field-installed kit

Configuration Information
Form factor
Power requirements
Power consumption
Bus loads

Quad height
+5 Vdc, 2.52 A; +12 Vdc, 0.0 A
12.6 W
0.0 ac; 0.0 dc

Base System Description

1–17

Chapter 2

Option Specifications
This chapter lists specifications for the options currently supported in the
VAX 4000 Model 300 system, grouped as follows:
•

Mass storage

•

Communications

•

Real-time

•

Printer

•

Graphics

The specifications appear in alphanumerical order within each of the above
groups. All weights are approximate.
Some of the options are already installed in your system. If you want to
add other options, your Digital sales representative can advise you.

Option Specifications

2–1

2.1 Options Overview
The option specifications include the following, where applicable:
•

Functional information

•

Ordering information

•

Performance

•

Configuration information

•