Digital PDFs

EK-DS780-UG-002

November 1979

75 pages

Original

3.7MB

view download

OCR Version

3.4MB

view download

Document:	VAX 11/780 Diagnostic System User's Guide
Order Number:	EK-DS780-UG
Revision:	002
Pages:	75
Original Filename:

OCR Text

PRSRAEPR

EK-DS780-UG-002

VAX-11/780 Diagnostic System
User’s Guide

digital equipment corporation - maynard, massachusetts

1st Edition, November 1978
2nd Edition, August 1979

The material in this manual is for informational

purposes and is subject to change without notice.
Digital Equipment Corporation assumes no responsibility for any errors which may appear in
this manual.

Printed in U.S.A.

This document was set on DIGITAL’s DECset-8000
computerized typesetting system.

The following are trademarks of Digital Equipment Corporation,
Maynard, Massachusetts:
DIGITAL

DECsystem-10

MASSBUS

DEC

DECSYSTEM-20

OMNIBUS

PDP

DIBOL

0S/8

DECUS

EDUSYSTEM

RSTS

UNIBUS

VAX

RSX

VMS

IAS

CONTENTS
Page

INTRODUCTION

SCOPE ...ttt
e e e e e e e et e e e e e e e et e eeae e e e e e et e
e e e e eean e aeaes 1-1
DIAGNOSTIC SYSTEM OVERVIEW. ...
e 1-2
USE OF THE DIAGNOSTIC SYSTEM ...t
ettt e e 1-8

CHAPTER 2

DISKETTE LOAD PROCEDURE

CHAPTER 3

POWER UP/CONSOLE BOOT

A
2
3

POWER-UPPROCEDURE ...ttt
e ee e 3-1
CONSOLE BOOTSTRAP FAILURE ..o 3-2
CONSOLE PROGRAM CRASH......ccooii ettt
e e 3-2

CHAPTER 4

MICRODIAGNOSTIC PROGRAM

4.1

MICRODIAGNOSTIC PROGRAM DESCRIPTION ........cccoiiiiiiieieiiereceeiene 4-1
PROGRAM EXECUTION PROCEDURE.........oooiiiiiiiieeeeeeeeeeeeie 4-1
MICRODIAGNOSTIC ERROR MESSAGES ... 4-3
SECTION PARTITIONING ..ottt
e e e e reaees4-5
SBIDEVICE TESTS ..o
ettt
e e e e st s e e e e e s eneenee e 4-5
INTERPRETATION OF WCS, PCS, AND FPLA
REVISION STATUS. ..ottt
e e s e e e et ettt
e e eeeerenaaeaseeeenaenns 4-5

2
3

CHAPTER 1

4.2
4.3
4.4
4.5
4.6

B W=

PN DOND P

hh hh

hnh b

PO RO Im e
e e

CHAPTER 5

USING THE DIAGNOSTIC SUPERVISOR
DIAGNOSTIC SUPERVISOR COMMANDS ...t 5-1
Program/Test Sequence Control Commands..............cccceeiiinnnnn, 5-2
SCTIPUIME . ..vvteiieiieiee ittt e re et e teretee ettt teeeeeeeeaeeaeeaaeeeeeaaeeaesaeeneeseeeeaeesreerensrnns 5-10
Scripting Command............ooeeuuiiiiiiiiiiiee
e 5-10
@ Command ProcCessing ...........ceiiieiiiiniieiiiiieeiiiiee
e eceneeeneeseenaeeees 5-11
Buffer Allocation and Script Nesting .......ccooevuiiiiiiiiieriieieeeeeeecriieneeenen. 5-11
Interrupting the SCript ... cooiiiiiiiii e 5-12
Command File Format ...
e e5-12
Execution Control Functions............ccoooeiiiieiii i
e ece e 5-12
Debug and Utility Commands ...........ccooeeeiriiiiiiiiiiiiiieein
e ceeeeeieeee e eeeeeeenees 5-15
SIMPLIFIED SYSTEM TESTING ...t
ee e 5-19
Booting the Supervisor from the System
Disk: On-Line MoOde.........coiiiiiiiiiiiiiiie
et ce s eeve s e e e e e 5-19
Booting the Supervisor from the System
Disk: Standalone Mode ..........ooouuiiiiiiiiii
e 5-19
The CONFIG and SYSTEST Script Files .......ccooiiiiiiiiiiiiiiiiin
e 5-22
Modifying SCript FIles ......ccooeeiiiiiiiiie
e
e 5-23

RUNNING LOAD PATH DIAGNOSTICS FROM

THE FLOPPY: STANDALONE ... ..ot 5-23

BUILDING AND MAINTAINING THE
DIAGNOSTIC SYSTEM DISK

BUILDING A DIAGNOSTICDISK PACK ...
Dual RP06 and Dual RMO03 Based Systems .............coevvvvevvievieiieiiiieenieeieeeenne.
Single RP06 or RMO03 Based Systems...........ccovvviiiiieiieeiieieeieeeeeeeeeeeeeeeeee
UPDATING DIAGNOSTIC FILES ...t

o —

rmt ot e

CHAPTER 6

CONTENTS (Cont)

APPENDIX A

HELP FILES

APPENDIX B

MICRODIAGNOSTIC MONITOR COMMANDS

APPENDIX C

CONSOLE BOOT/TROUBLESHOOTING FLOW
FIGURES

Figure No.

Title
VAX-11/780 Diagnostic System Program

AWV
B WN—

OO0O0000O
lllll'\)

HICTATCRY .o
e
ee e e s
VAX-11/780 Diagnostic System

EXeCUtion ENVITONIMENTS «..u.onieeeee oo

Console Power Troubleshooting Flowchart............cccccoovviviiiveeieinieeeieeeeeeennn

Console Terminal Troubleshooting Flowchart............cccovvveveiiiiiieiieeciiiiieeeeean
LSI-11 Boot @ 173000 FIOWChATt ......ccccccvviiiiiiiiiiiiieeceeie
e e,
ee

TABLES

== N

Title

Related Manuals.......oocuuiiiiiiiiiiiis
et e
ae e
Diagnostic Program Features............oocoeiiiiiiiiiiiiiiiiiiiececeee
e,
Device Naming CONVENTIONS ......cceivveciiieeieeiiiieiiee
et ce et e e seeeeeeneeee e
Examine Command Qualifier Descriptions............cccceovvveiiieeereieeeeeeeeeeeeeeeanns

EXAMPLES

D= OO NDRWN—OOOIANNEL,WDN

R
TRV VRV R

1
O\?\O\O\

SN
-

A
A
A
AR A
A
R
A
N W W BNRNI RN

NN DN

VRV RV Y RV RV RV RV RV RV RV R R

et et et ot

—

—_ \O
o

00 ~J O\ W

W
O

Q.IIMLIIMM

Example No.

Title

Page

seraneenanes 5-2
reeiniee
srrseeerasessesss
eereteee
e ettaeetrteerrniae
Set L0ad COMMEANG ....coonneiiiiiiieiiiiee
e aaaas 5-2
s esee e st ire
eers eiiiiiii
uuiiiii
ettt
Show L.0ad CommAand..........oov
en 5-3
sestnsasssanaanas
eeeeeteee
sraarnasaasaessas
eeeiitiee
e e cetata
L0ad COMMANG ......ceeiiiiiniiiieiiieeee
5-5
s
s
s
sa
et
s
eaeara
e
s
e
rr
e
traar
e
e
et
eee
e
e
iiee
et
CoOmMMEANM.......oneieeiiii
Attach
5-5
assesinesnns
tiaesara
saraaaaeeeneesii
eeteneter
e
aers
e
eeemueeee
iieerrcee
eiiieniii
...coonee
COMMEANT
Select
5-5
sens
eeeeree
eereessstinsenaee
e
asi
eeretiae
ettieeeraaeeetans
e
iiiiiiii
vvnniiii
......oo
COMMANG
Deselect
5-6
.
iiiiniiiiin
.c.cceviiii
...........
Commands
Selected
Show
and
Device
Show
Start COMMANG. .....o.ueeeieieiiiiiieeerteeeeeeruieeeeenrtaeerutnteertaaerarnastasssesseaseserasssseanseennes 5-7
te 5-8
aesntaaeas
erreaaee
sastasassstansstss
eeitiiee
e e seraaneeestseeaasa
RUN COMIMANG .oentieeeeeeeeiieeeiiiee
Use of Control C, Summary, and Continue

COMMIMANAS. .. eeeeeeeeeeeeeeeeemeneettuueeresaaaesssanaasetsereesettsssseeaaesnrnrasarsnssasesesosenesssstanssanns 59
Use of Control C, Summary, and Abort

esieanaeens 5-10
eatessea
s aesasaassssetars
nareaase
s eresaraaaeersan
COMMEANAS ... eeeeeeeeeeeeetiieeeeeesr
5-11
iiiii
ooiiii
..ccoo
......
File
Command
A Typical
Execution of a Typical Command File...........c.oooii 5-11
Use of the Flag Control Commands............cooooiiiiiiinieiiniieiiii 5-14
Event Flags Control Commands........cc.cocoiimiriiiiiiiieiniii it 5-15
s saaaeeetaas 5-15
eeetie
e s s sasasteaeeereas
e e rrieeeeiiee
iiiiiee
Set Base COMMANT.....c.uiiiuiiettt
eee 5-16
e
Set Breakpoint CommMAnd ..........cooiiiiiiriiiiinieeeii
iiiieii 5-16
Clear Breakpoint Command...........ccccooeiiiiiiierine
Show Breakpoint Command..........ccooviuiiiiiniinn i 5-16
s e raaaeee 5-17
ieie
e e e e et seresie
eecitie s iiiii
e e eiiii
Set Default CoOmMMANG ........ue
aieran 5-18
eieeiieeirissiasesnans
e sesasanteeseteaes
Examine COmMMANd.......coovuuviiiinieeereeiereereiee
Deposit COMMANG ......cooouuiiiiiiiiiiie i 5-18
esaestenaeses 5-19
eeeratea
aasrsasaassesnnss
tiiieiee
eeeraaiiesertrnee
NEXt COMMEANG ...eennneieiieiiiieeeiee
ii 5-19
e
Booting the Supervisor On-Line ..........cooooioiiii
Preparation of R3 for a Prompting Boot File ... 5-19
Booting the Supervisor from an RP06 Disk Drive..........cocccoociiiiiiin. 5-20
Booting the Supervisor from an RMO03 Disk Drive.........ccoocooniiiiin.. 5-21
Booting the Supervisor from an RK07 Disk Drive .........ccoocvviininiinn.. 5-21
Booting the Supervisor with a Prompting Boot File ...........cccooiiiiinn. 5-21
A Typical CONFIG Script Listing........cccooiiiiiiiiiiieens 5-22
A Typical SYSTEST Script Listing ......cocoieiiiiiiiiiiiiiiiiens 5-23
Running Diagnostics from the Load Path

F1oppY DiSKette Set ......coviuiiiiiiiiiiiiiiie i 5-24
Creating an RP06 Diagnostic Disk Pack............cccoooiiiiis6-2
iii
s6-2
Entering Bad BIock NUMDETS .......oocuiiiiiiiiiiiii
Creating an RMO03 Diagnostic Disk Pack ............ccoccciiiiis 6-2
Transferring Diagnostic Files from Magnetic

Tape to Disk With DSCl......cooiiiiiiiii 6-3

CHAPTER 1
INTRODUCTION

1.1

SCOPE

This manual provides information for use of the VAX-11/780 Diagnostic System including power-up,
bootstrap, and file maintenance data. The manual will serve as a reference for customers and field

service engineers, and as a resource for appropriate branch and support level courses of the field
service, manufacturing, and customer training programs. These courses constitute prerequisites for
running VAX-11/780 diagnostics. Related manuals are listed in Table 1-1.
Table 1-1

Related Manuals

Title

Document Number

Notes

Microcomputer Handbook

EB06583

Available on hard copy

EK-DS780-TD

Available on microfiche

VAX-11/780 Diagnostic System

Technical Description
VAX/VMS Primer

Available on hard copy

VAX Preliminary Documentation Set
(VAX Software Manual Kit,

14 manuals)

QE00152

Available on hard copy

VAX-11/780 Architecture Handbook

EB07466

Available on hard copy

VAX-11/780 Hardware Handbook

EB09987

Available on hard copy

VAX-11 Software Handbook

EB08126

Available on hard copy

NOTES

If you wish to order these manuals from
within the United States, call Digital Equipment Corporation at either of the two numbers listed below.
From all areas of the United States except
New Hampshire, call (800) 258-1710.

From New Hampshire call (603) 884-7288.

If you wish to order manuals from an area
outside of the United States, contact the nearest Digital Equipment Corporation sales office.
1-1

1.2

DIAGNOSTIC SYSTEM OVERVIEW

The diagnostic system consists of programs which are organized hierarchically (from general to specific capabilities) in six levels. Each level contains one or more categories, as follows.
Level 1

Operating system (VMS) based diagnostic programs (using queue 1/0).
Level 2

Diagnostic supervisor based diagnostic programs which can be run either under VMS or in
the stand-alone mode (using queue 1/0).
Bus Interaction program.
Formatter and reliability level peripheral diagnostic programs.
Level 2R
Diagnostic supervisor-based diagnostic programs that can be run only under VMS (using
physical QIO).
Certain peripheral diagnostic programs.

System Diagnostic Program.

Diagnostic supervisor-based diagnostic programs that can be run in stand-alone mode only
(using direct 1/0).

Functional level peripheral diagnostic programs.
Repair level peripheral diagnostic programs.

Cluster diagnostic programs.
Level 4

Stand-alone macro diagnostic programs that run without the supervisor.
Hardcore instruction set.
Console Level
Console based diagnostics which can be run in the stand-alone mode only.
Microdiagnostics.

Console program.
Octal Debugging Technique (ODT).
ROM resident power-up tests.
LSI-11 diagnostics.
These levels provide the range and flexibility required to detect and identify 95 percent of the possible
hardware faults in the various VAX-11/780 system configurations. Figure 1-1 shows the relation of the

diagnostic program to these four levels.

1-2

Table 1-2 Diagnostic Program Features

Program

Microdiagnostics
Hardcore Instruction Test

CPU Cluster Exerciser
Massbus Adapter Diagnostic
Unibus Adapter Diagnostic
DCL/RP04, 05, 06 Repair Diagnostic
RK611 Diagnostic Parts A-E

RK611-RK06/07 Drive Functional Test

Parts 1,2
RMO3 Diskless Diagnostic

RMO3 Functional Test
Disk Formatter
RPOX/RKO0X/RMO3 Reliability
TMO3/TE16/TU45/TU77 Repair
TMO03/TE16/TU45 Drive Function Timer
TMO03/TE16/TU45 Tape Reliability
DZ11 8 Line Async Mux Test
M8 201/2 Repair Level Diagnostic
DMC11 Exerciser
DR11B Repair Diagnostic
Communications IOP Repair Level Diagnostic
Line Printer Diagnostic
CR11 Card Reader Diagnostic
Bus Interaction Program

VAX System Diagnostic
RPOX Functional Diagnostic
Terminal Diagnostic
Terminal Exerciser

Maindec
Code

ESKAB-ESKAM|
EVKAA

ESKAX-ESKAZ
ESCAB
ESCAA
ESRCA
ESREA-ESREE

ESREF,ESREG
ESRDA

ESRDB
ESRAC
ESRAA
ESMAC
ESMAB
ESMAA
ESDAA
ESDBA
ESDBB
ESDRA
ESDXA
ESAAA
ESABA
ESXBA

ESXBB
ESRBA
ESTAA
ESTBA

Stand-Alone

On-Line

I/0 TYPE

Floppy

System
Device

Direct| QIO
I/0

Program |oad from | Load from | Load from
Level

Console
4

3
3
3
3
3

3
3

3
2
2
3
3
2
3
3
3
3
3
2R
2R
2

2R
3
2R
2R

X
X

X
X
X
X
X

X
X

X
X
X
X
X
X
X
X
X
X
X

X
X
X

X
X

X
X
X

X
X
X
X
X
X
X

X
X

Function
Callout

Module
Callout

X
X
X
X
X

X
X
X
X
X
X
X
X
X
X
X

Error Resolution

X
X
X
X

X
X
X
X
X

X
X

X
X
X
X
X
X
X
X
X
X
X
X
X
X

X
X
X

X
X
X
X

X
X

1-3

The diagnostic programs can be used for preventive maintenance checks to ensure proper computer
operation; if system malfunctions have been detected, specific programs or groups of programs can be
run to further isolate the fault.
Table 1-2 lists the important features of the diagnostic programs.

The diagnostic system, in general, uses a building block approach to testing (and subsequent fault
detection and isolation). When the diagnostic programs are executed in the standard system checkout
sequence, they will initially test a minimum (basic) set of logic or functions to assure their proper
operation. After these basic operations are verified, a larger and more complex block is tested using the
previously tested block as a base. This sequence is implemented from the ROM resident power-up tests
(which check the console) to interactive system tests executed as user mode tasks under the operating
system. Figure 1-1 shows the building block sequence from top to bottom.

The diagnostic programs operate in a variety of environments, according to their functions and locations in the diagnostic system hierarchy, as shown in Figure 1-2.
On power-up, a set of ROM resident tests verifies proper functioning of the LSI-11 within the console
subsystem before booting the console program from the floppy disk.
The console subsystem, in connection with the console program, provides the basis for the diagnostic
system with the following functions:
.

Traditional lights and switches functions such as EXAMINE, DEPOSIT, HALT, START,
and Single Instruction.

Diagnostic and maintenance functions, including the capability to load diagnostic microcode into Writable Control Store (WCS), control execution, control single-step clock functions, examine key system points via a serial diagnostic bus (V bus), and deposit and
examine data in location in the VAX-11/780 main memory and I/O space.

Operator communication with the VAX-11/780 software.

The console program enables the operator to run microdiagnostics, to load and run the diagnostic
supervisor (in the stand-alone mode) and the stand-alone macrodiagnostic programs (using VAX-11
native code), and to boot the VAX/VMS operating system.
The microdiagnostic program proceeds from a test of the console interface board through basic tests of
the CPU, memory controllers, and the floating-point accelerator (FPA).
The macrodiagnostic programs fall into two major categories: CPU cluster and 1/0O subsystem. The
CPU cluster diagnostics test the VAX-11/780 CPU and the SBI channel subsystems such as the Massbus Adapter (RH780) and the Unibus Adapter (DW780). The SBI channel subsystem diagnostics
provide module callout and failing function callout (CPU module callout is provided by the microdiagnostics).

The 1/0 subsystem diagnostic programs fall into two categories, based on the methods used for accessing I /O devices. Direct [ /O programs supply their own 1/O driver routines. Queue 1/O programs rely
on VMS or the Diagnostic Supervisor for 1/O driver routines.
Most of the direct 1/0O diagnostic programs provide module callout and function identification on
error detection. The other direct /O programs and the queue /O programs call out the failing function and other relevant information, upon error detection (Table 1-2). The operator’s knowledge of the
VAX-11/780 system should enable him to locate the fault once the program has identified a failing
function.

1-4

DEDICATED

LsI-11

LSI-11 DIAGNOSTICS
L]

TESTS

(I1BM RESIDENT)

MOST BASIC LEVEL

oDT

PROGRAM 1/0 MODE

LEVEL 4 <

HARDCORE TESTS——]

STAND ALONE ONLY

G-l

POWER UP

TESTS

PROGRAM [—— CONSOLE 1/0 MODE

CONSOLE

"MICRO-

DIAGNOSTIC

|—— MICROTESTS

PROGRAM

CLUSTER

EXERCISER
(ESKAX)

STAND ALONE ONLY

LEVEL 3 <

{DIRECT 1/0)

r
RH780 (MBA)

DIAGNOSTIC

(ESCAA)

]

1
DW780 (UBA)

DIAGNOSTIC

(ESCBA)

L
TK-0607

Figure 1-1

VAX-11/780 Diagnostic System Program Hierarchy (Sheet 1 of 2)

)
1
STAND ALONE ONLY

RPOX/DCL

REPAIR LEVEL

DIAGNOSTIC
(ESRCA)

(DIRECT 1/0)

REPAIR

LEVEL 3~

STAND ALONE ONLY

TAPE DRIVE

FUNCTION LEVEL

TIMER

STAND ALONE
OR UNDER VMS
(QUEUE 1/0)

TAPE
FEUAB')UTY
ESMAA

FUNCTIONAL

(ESMAB)

9-1

(DIRECT 1/0)

2 <
LEVEL

STAND ALONE
OR UNDER VMS

RMO3

FUNCTIONAL

DIAGNOSTIC

(ESRDB)

RK611

RK611 MANUAL

PARTS A-E
(ESREA- E)

TESTS
(ESREF)

DIAGNOSTIC

RPOX

FUNCTIONAL

DIAGNOSTIC
(ESRBA)

INTERVENTION

OMC

EXERCISER

(ESDBB)

RP/RK/RM

DISK
FORMATTER
(ESRAB)

LOCAL TERMINAL
DIAGNOSTIC
ESTAA
(
)

RP/RK/RM

MULTI-

DISK

TERMINAL

RELIABILITY

DIAGNOSTIC

(ESRAA)

(ESTBA)

LINE PRINTER
DIAGNOSTIC
(ESAAA)

BUS

INTERACTION

(QUEUE 1/0)

(ESXBA)

UNDER VMS
LEVEL1

ONLY

SYSTEM

(QUEUE 1/0)

EXERCISER

TK-0608

Figure 1-1

VAX-11/780 Diagnostic System Program Hierarchy (Sheet 2 of 2)

STAND ALONE

L
&+ W N ] O LB N
3

X _ WN
N]

DEDICATED
_ POWER
cONSOLEUP TESTS
LSI11 __ ot
LSI-11

TESTS

CONSOLE

I|
LOAD FROM
CONSOLE FLOPPY

DIAGNOSTIC

MONITOR

SUPERVISOR

MICROTESTS

- GO CHAIN

- FAIL CHAIN

DEVICE

DEVIC

DIRECT 1/0 *

KA-11/780 CPU CLUSTER EXERCISER

RH-780 MBA DIAGNOSTIC

DW780 UBA DIAGNOSTIC

TMO3/TEE 16-TU77 TAPE DRIVE FUNC TIMER

RP06/FUNCTIONAL DIAGNOSTIC

RK611 MANUAL INTERVENTION

PROGRAM

DIAGNOSTIC

SUPERVISOR

LOAD FROM

SYSTEM DEVICE

\
1

a/o*

TAPE RELIABILITY

MULTITERMINAL EXERCISER

]

Qi/o

RP/RK/RM DISK FORMATTER

LOCAL TERMINAL DIAGNOSTIC
LINE PRINTER DIAGNOSTIC

RP/RK/RM DISK RELIABILITY

RPO6/DCL DIAGNOSTIC

RK611 DIAGNOSTIC PARTS A-E

/
/

[

HARD CORE TESTS

VAX/VMS
F___CONSO LE

LOAD FROM

YSTEM

SYSTEM

/
/

SUPERVISOR

MICRODIAGNOSTIC

MICRODIAGNOSTICS

PROGRAM

L] V—MS CERERED S

EXER

\
\
\

BUS INTERACTION

DMC EXERCISER

* THE NUMBER OF 1/0 DIAGNOSTIC PROGRAMS WILL GROW.

Figure 1-2

VAX-11/780 Diagnostic System Execution Environments

TK-

These two program categories (direct
ating environments.

/O and queue 1/0) correspond to varieties in program oper-

The stand-alone mode requires exclusive use of the VAX-11/780 system. The operator must use the
console terminal and the facilities of the console program to load the diagnostic supervisor and program images into main memory. Direct I/O programs and queue /O programs can both be run in the
stand-alone mode (with the exception of level 2R programs).
When diagnostic programs are run under VMS, they do not require exclusive use of the VAX-11/780

system (with the exception of the System Diagnostic). Only programs employing queue I/0 can be run
under VMS. Note that the operator need not use the console terminal to run diagnostics under VMS;
any terminal on the system will suffice.

Before a diégnostic program to be run under VMS is loaded, the diagnostic supervisor must be loaded

from the system device and then started. The facilities of the diagnostic supervisor are then available to
load and run the program and control program execution.
1.3
USE OF THE DIAGNOSTIC SYSTEM
When a complete check of the VAX-11/780 system is necessary, the microdiagnostics, the direct [/O

diagnostics, and the queue I/O diagnostics should be run in that order Note that the LSI-11 ROM
resident diagnostics are run automatically on power-up.
If a quick verification of the computer is required, run the SYSTEST script and the System Diagnostic
(Chapter 5).
If the diagnostic supervisor or the VMS bootstrap fails, run the microdiagnostic program to identify

the problem.
Note that since the peripheral device diagnostics have been designed with the assumption that the CPU
cluster [CPU (KA780), MBA (RH780), UBA (DW?780), and memory] is functioning normally, it may
be useful to run the CPU cluster exerciser and MBA (RH780) or UBA (DW780) diagnostics before
running any of the peripheral tests.
Customers who have bought a VAX-11/780 remote diagnosis contract and have a remote diagnosis

option kit installed should call the DIGITAL Diagnostic Center (DDC) when they suspect hardware
failures. The dispatcher at the DDC will provide customers with the information necessary to proceed
with the remote diagnostic session.

CHAPTER 2
DISKETTE LOAD PROCEDURE

These steps should be followed to load the diskette.
1.

Open both CPU cabinet doors.

Release the drive lock and swing out the floppy drive assembly.

Compress the diskette slot cover lock and slide the cover to the right.
Remove any diskette already in the floppy drive.

Insert the desired diskette in the drive slot, with the diskette label to the right side of the
floppy drive.

Close the slot cover (cover locks automatically).

3
CHAPTER

POWER UP/CONSOLE BOOT

3.1

POWER-UP PROCEDURE
1.

Insert diskette ZZ-ESZAB in the floppy disk drive slot before turning the VAX-11/780

system on.

Push the AUTO RESTART switch on the console panel to the OFF position.

Turn the 5-position keyswitch on the console panel to the LOCAL position.

On system power-up, ATTN and PWR indicators should be ON.

The LOCAL position first invokes the console LSI-11 tests in a ROM on the Console Inter-

The console program loads from the floppy disk drive.

Console terminal output:

face Board (CIB) and then invokes the console boot program.

CPU HALTED, SOMM CLEAR, STEP=NONE, CLOCK=NORM
RAD=HEX, ADD=PHYS, DAT=LONG, FILL=00, REL=000000
INIT

SEQ DONE

HALTED AT 00000000

(RELOADING WCS)

LOAD DONE, 00003200 BYTES LOADED
VER: PCS=01 WCS=02-10 FPLA=02 CON=PX02-11
>>>

The console program tests the AUTO RESTART switch.

AUTO RESTART OFF - VMS is not booted.

10.

The console program runs in the console I/O mode, refer to Appendix A.
NOTE
If the microdiagnostics and/or the stand-alone
macro-diagnostics are to be run, the VAX/VMS
bootstrap should not be initiated on power-up.

3-1

3.2
CONSOLE BOOTSTRAP FAILURE
The console bootstrap may fail to load the console program from the floppy on power-up. The ROM
resident tests which the LSI-11 executes before starting the boot program should help in locating the
cause of the failure, refer to Appendix D.

3.3 CONSOLE PROGRAM CRASH
If the console program halts, the LSI-11 processor automatically enters the ODT mode (octal debugging technique). This ROM resident routine enables the console terminal operator to execute several
types of commands to the LSI-11 processor, including open location, close location, and go.

When the LSI-11 halts, it prints out the following ASCII non-printing and printing characters to the

console terminal:

<CR>

<LF>

nnnnnn

<CR>

<LF>

€

The nnnnnn is the location of the next instruction to be executed; it is always the contents of the PC
(R7). The <CR> and <LF> are carriage return and line feed codes. The @ symbol is displayed as the
ODT prompt character for the operator.

At this point the operator can use the maintenance command to print the contents of a register within
the LSI-11 processor. Type M. The data printed will help to identify the nature of the problem.
Example:

Note that operator input is underlined.

@M000213<CR><LF>
@

The console prints six characters and then returns to command mode by printing CR,LF.,@.

The last octal digit is the only number of significance and is encoded as follows. The value specifies
how the LSI-11 got into the ODT mode.

3-2

Last Octal Digit Value

Function

Halt instruction or B Halt line

lor$s

Q Bus Error occurred while getting the device interrupt vector. This error
probably indicates that the priority chain (BIAKI/O L signal) is broken in
the console system and that an open slot exists between modules. Modules
must be inserted in a contiguous fashion according to the priority daisy
chain.

20r6

Q Bus Error occurred while doing memory refresh.

Double Q Bus Error occurred (stack contains non-existent address).

Reserved instruction trap occurred (non-existent micro-PC address occurred

on internal LSI-11 processor bus).

A combination of 1, 2, and 4, which implies that all three conditions occurred.

In the above example, the last octal digit is a 3, which indicates that a Do uble Q Bus Error occurred.
The codes listed above are valid only when the ODT mode is entered, and the code is immediately
displayed. This information is lost when a G command is issued; the code reflects what happened in
the program since the last G command was issued.

If the console program has crashed while VMS is running, the operator may wish to restart the console
program without affecting VMS. To reboot only the console program, type 141330G. Refer to Section
2, Chapter 2 of the Microcomputer Handbook (EB06583) for further details on ODT.

3-3

CHAPTER 4

MICRODIAGNOSTIC PROGRAM

MICRODIAGNOSTIC PROGRAM DESCRIPTION

The microdiagnostic program provides module isolation for logic failures within the CPU, MOS mem-

high/low
ory controllers, and the Floating-Point Accelerator (FPA). The program will detect stuck
building
(i.c.,
sequence
ping
bootstrap
a
in
organized
are
tests
logic problems. The microdiagnostic
Buffer,
I-Stream
Buffer,
ation
e-Transl
SBI-Cach
,
hardware
path
blocks) of the console interface, data
g the
indicatin
typeouts
error
in
result
faults
detected
All
FPA.
SBI, memory controller, arrays, and
smallest set of modules to which the program can isolate the failure.

4.2 PROGRAM EXECUTION PROCEDURE

Load and run the microdiagnostic program as follows.

Once the console program has been loaded, insert diskette 1 (ZZ-ESZAC) in the floppy disk

Type Control P (AP) to enter the console 1/0 mode.

Type HALT to halt the VAX-11/780 CPU. The ATTN light on the console panel should

drive.

light and the prompt symbol, >>>, will be printed out on the console terminal.

Typé TEST to start the microdiagnostic program.

The microdiagnostic monitor and programs are loaded and executed automatically.

The console prints out each microdiagnostic section number when that section begins executing.

4-1

The console terminal output will look like this:

>>>

TEST

;Console

ZZ-ESKAB

V8.0
01,02,03,04,

NO.

prompt,

;Program

title

;Section

numbers

test

and

command

version

OF WCS MODULES = 0002
;Configuration information
05,06,07,08,09,0A,OB,OC,OD,OE,OF,10,11,12,13,14,15,16,
17,18,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27,28,

29,2A,2B,2C,2D,2E,2F,30,31,32,33,34,35,36,37,38,39,3A,
3B, 3C, 3D,

END

PASS 0001
MOUNT FLOPPY ZZ-ESZAD
MIC>

Microdiagnostic
size.

TYPE

"DI"

identifies

;instructions for second
smicrodiagnostic monitor

itself,

its

release

half
prompt

level

and

The terminal prints out section numbers as
they begin.
Should test execution terminate, the operator knows
which
section

failed.

NOTE
Operator input is underlined.

At the end of the pass, the console directs the operator to insert the next diskette and
type DI
(diagnose).

The microdiagnostic monitor then displays the prompt symbol, MIC>.

10.

Insert diskette ZZ-ESZAD.

11.-

Type DI.

12.

Programs resident on floppy ZZ-ESZAD are then executed.

4-2

Console terminal output:

13.

MIC> DI

3E,
# MEM CTRLS = 00000001
3F, 40,
4K CHIP 00001008

;diagnose command

:section number(s)
sconfiguration information
swhich is system specific

41,42,

cPU TR = 00000010

,
4D,
43,44 45, 46,47,48,49,4A,4B,4C

CTRL 1 MAX ADR+1 = 00090000
LE,

CTRL 1 MAX ADR+1 = 00090000
4F, 50,

STARTING FPA TESTS

51,52,53,54,55,56,57,58,59,5A,5B,5C
END PASS 0001

CPU HALTED, SOMM CLEAR, STEP=NONE, CLOCK=NORM

RADzHEX, ADD=PHYS, DAT=LONG, FILL=00, REL=00000000
INIT SEQ DONE

HALTED AT 00000000

(RELOADING WCS)
LOAD DONE, 00003200 BYTES LOADED

VER: PCS=01 WCS=03-10 FPLA=03 CON=PX03-08

;CPU

status

;and console
;program

;defaults

;configuration
;information

sconsole prompt

>>>

Note that microdiagnostic section numbers are sequential
(Hex).

End of pass indication is printed when test execution is

completed.

the
of
completion
successful
after
Fhat
Ngte
microdiagnostic program the microdiagnostic monitor
returns control to the console program which then reloads
WCS.

The

console program puts out a prompt character,

MICRODIAGNOSTIC ERROR MESSAGES

>>>.

s
The microdiagnostic program is broken into two parts: hard-core tests (sections 1-1F) and microtest
differ
s
microtest
the
and
tests
hard-core
the
for
(go chain) (sections 20—end). Error message formats
only slightly.

Hard-core test error message sample:

>>>TEST

MICRO

DIAGNOSTIC

01,

?ERROR:

002244

V.04

TEST:

0007

SUBTEST:

0002

; Program

name

;failing

section

;PC
DATA:

FFFFFFFD

TRACE:

002270,

FAILING

(Octal),

ynumbers
ymeaningful

FFFFFFFC
0002

002300

MODULES:

IDBUS,

M8236

(S24),

and

version

;last number indicates
test,
data,

subtest
e.g.

;expected,

received.

;isolation

routines

;probable

used

failure

MIC>

"~ Note
are

that

the PC contents and the

six digit

octal

Q bus

isolation routine addresses

addresses.

The user should replace the designated failing module and rerun the microdiagnostic program. Microtest error message sample:

>>>TEST

MICRO

DIAGNOSTIC

V.04

;program

name

and

version

01,02,03,
NO.

WCS

MODULES

0002

o4,05,06,07,08,09,04,0B,0C,0D,0E,OF,10,11,12,13,14,15,16,17,18,
19,
1A,1B, 1C, 1D, 1E,1F,20,21,22,23, 24,
;last
number
indicates
;yfailing
?ERROR:

DATA:

111C

TEST:0073

SUBTEST:0001

00006000
00,01,05

FAILING

MODULES:

section

address

(hex),

test,

;subtest numbers
;meaningful data, e.g.
;expected received data

00000011
00000010

TRACE:

;WCS

;fail

M8225(S??)

chain

;probable

routines

used

failure

MIC>

The WCS address is a 4-digit hex number indicating the location of the failing microinstruction. The 2digit hex numbers following TRACE: indicate the fail chain routines which were used in the isolation
of the fault. Intepretation of this data requires a listing of the failing test.
The user should replace the designated failing module and restart the microdiagnostics. If two or more
modules are listed, the listing order indicates the probability of failure, highest to lowest.

4-4

If the failure is still evident after the module identified has been replaced, use the data printed out to
further isolate the problem.

SECTION PARTITIONING

The hard-core tests check the console interface, the microsequencer, the WCS and PCS, and part of the
data path.

WX
N B W=

The microtests are partitioned into 9 major categories as follows:
Data Path Tests
Cache Memory Tests
Translation Buffer Tests
Instruction Buffer Tests

Condition Codes, Interrupts, and Exceptions Tests
SBI Interface Tests
Memory Tests
SBI Device Tests

Floating-Point Accelerator Tests

All hard-core tests and microtest categories 1 through 5 are packaged on floppy number 1 (sections 1
through 30) and categories 6 through 9 on floppy number 2 (sections 3E through 5B).
4.5

SBI DEVICE TESTS

Category 8 uses any available devices (UBAs or MBAs) that are found on the SBI to test their fault
detection logic. Category 8 also uses a UBA (if there is one on the system) to test the cache invalidation
logic.

4.6 INTERPRETATION OF WCS, PCS, AND FPLA REVISION STATUS

When WCS has been reloaded, the console terminal prints out revision status, for example:

VER: PCS=01 WCS=03-10 FPLA=03 CON=PX03-08

The WCS
The PCS code refers to the revision number of the programmed control store (ROM).
case, 03)
this
(in
number
version
primary
The
numbers.
two
contains
(writable control store) code
refers to the FPLA number which is required for this WCS version. The secondary version number (in
this case, 10) refers to the version of WCS which has been loaded.

The FPLA (field programmable logic array) code refers to the FPLA chip revision which is currently
installed in the VAX-11/780 CPU. This chip causes the microprocessor to retrieve microwords from
WCS instead of from PCS when specific locations are addressed.

The CON (console) code refers to the revision number of the console software which has been loaded
into the LSI-11 memory.

Two types of mismatch may occur. If the WCS revision does not match the FPLA revision, the console
program issues a warning. However, if the WCS revision does not match the PCS revision, the mismatch is fatal.

CHAPTER 5

USING THE DIAGNOSTIC SUPERVISOR

Most macro level diagnostic programs run in conjunction with the diagnostic supervisor (the hardcore instruction text, EVKAA, is an exception). The supervisor provides a set of commands to the
operator which enable him to control the execution of diagnostic programs simply and precisely.
VAX diagnostic release II (August 1979) consists of an enhanced version of the supervisor and matching versions of the diagnostic programs that run with it. This release provides the following new
features.

An improved diagnostic system initial distribution facility. This enables the user to build a
diagnostic disk pack on his system device from magnetic tape files at the time of system
installation.

An improved update facility that enables the user to transfer updated diagnostic files from

A variety of boot command files to enable the operator to boot the diagnostic supervisor

A system profiler that enables the operator to describe the VAX system configuration to the

Support for the LOAD and RUN supervisor commands in the standalone mode.

Addition of a new supervisdr debug feature, the Next command.

A scripting facility that enables the supervisor to execute command files. Release 11 includes
configuration and system test scripts appropriate for each system. Users can modify these
scripts to accommodate add-on equipment, and they can create their own scripts.

A set of load path floppy diskettes from which to load and run diagnostics if hardware

floppy diskettes to the diagnostic system pack in semi-automatic fashion.
from a number of devices.

SUpErvisor.

errors prevent conventional loading from the diagnostic system disk pack.

5.1 DIAGNOSTIC SUPERVISOR COMMANDS
The diagnostic supervisor commands are grouped in four sets:
Program and test sequence control

Scripting features
Execution control
Debug and utility features

Commands, switches, and literal arguments can be abbreviated to the minimum number of characters
necessary to retain their unique identity. For example, the Load command can be specified by a single
L, whereas the Start command requires a minimum of ST.

5-1

In the symbolic command descriptions which follow, certain special characters are employed
that
require some explanation. Angle brackets, < >, are used to enclose symbolic arguments
that are
satisfied by a numeric expression or character string. Optional arguments are enclosed by
square
brackets, [ ]. An OR function is indicated with an exclamation point, !. Literal arguments
such as
ALL, OFF, and FLAGS are capitalized.
Use the hyphen, -, as a continuation character at the end of a line to continue a command
from one
line to the next. Use an exclamation point, !, to separate a comment from a command
in a command

line.

Notice that operator input is underlined in the examples that follow.
5.1.1
Program/Test Sequence Control Commands
These commands enable the operator to select programs and portions of programs and
to control the
sequence of test execution.

Set Load Command
SET LOAD <device>:[directory]<CR>

The Set Load command establishes the storage device from which the supervisor
programs. The default load device is the device from which the supervisor

will load diagnostic

was booted. Use Set Load

when you wish to load diagnostic programs from a different device. Use
the Set Load command in
combination with the Load command or the Run command.

DS>

SET

DS>

LOAD

DMAQ: [SYSMAINT]
ESDXA

DS>

SET

LOAD

DS>

RUN

ESDXA

Example 5-1

DMA@: [SYSMAINT]

Set Load Command

NOTE
The directory name, and the square brackets around

it, are necessary in the Set Load command.

Show Load Command

SHOW LOAD<CR>
The Show Load command causes the supervisor to display the storage
programs are to be loaded when the Load command is given.
DS>

SHOW

DMA@:

LOAD

[SYSMAINT]

Ds>

Example 5-2

Show Load Command

5-2

device from which diagnostic

Load Command

LOAD <file-spec><CR>

This command loads the specified file into main memory from the default load device. The default file
extension is .EXE. The storage device from which the program is loaded is the device established on
the previous Set Load command. Note that you need supply only the five-letter code that identifies
each diagnostic program for the command line argument <file-space>.

LOAD ESTAA

Example 5-3

Load the local terminal

diagnostic

program.

Load Command

Attach Command

ATTACH <UUT-type> <link-name> <generic-device-name> . . .<CR>

The operator must use several Attach commands, before starting a diagnostic program, to define each
unit under test (UUT), and the devices that link it to the SBI, for the supervisor. If you are testing
several units at once, repeat the Attach command for each device. Every unit under test is uniquely
defined by a hardware designation and a link.

The first parameter <UUT-type> is the hardware designation of the unit under test. For example,
RH780, TMO03, TE16, and DZ11 are hardware designations.

The second parameter <link-name> is the name of the piece of hardware that links the unit under test,
in most cases through intermediate links, to the main system bus. For example, an RH780 is linked to
the SBI; a TU4S is linked to an MTa; and a DZ11 is linked to a DWn. You must attach each piece of
hardware (with the exception of the SBI) before you can use it as a link in an Attach command.
The third parameter is the generic device name, which identifies to the supervisor the particular unit to
be tested. Use the form “GGan” for the device name. “GG” is a 2-character generic device name
(alphabetic). “a” is an alphabetic character, specifying the device controller. “n” is a decimal number
in the range of 0-255, specifying the number of the unit with respect to the controller.
Use the unit number, “n” or “a”, only if it is applicable to the device. You must supply additional
information for some types of hardware to enable the diagnostic program to address the device. For
example, you must supply the TR and BR numbers for an RH780, the controller number for a TMO03,
and the CSR, vector, and BR for a Unibus device. If you include such additional information in the
Attach command line, use the order and format shown in Table 5-1. If you do not include additional
information, but the information is necessary, the supervisor will prompt you for it.

5-3

Table 5-1 Device Naming Conventions

Type

Link

Generic

Additional Information

KA780

SBI

KAn

<G-floating> <H-floating>

MS780

SBI

MSa

<tr>

RH780

SBI

RHa

DW780

SBI

DWa

<WCS-last-address>

DR780

SBI

RPO7
RPO6
RPO5
RP04

RHa
RHa
RHa
RHa

DBan
DBan
DBan
DBan

RMO3

RHa

DRan

RK611

DWa

DMa

RKO7

DMa

DMan

RKO6

DMa

DMan

TMO3

RHa

MTa

TE16

MTa

MTan

TU45

MTa

MTan

TU77

MTa

DZ11

DWa

MTan
TTa

DUP11

DWa

XJan

DMCI11

DWa

XMan

KMCl11

DWa

XMan

LP11

DWa

LPa

CR11

DWa

CRa

DRI11B

DWa

7%a

PCL11

DWa

TS04

Dwa

MTan

RLO2

??an

RL11

Dwa

<drive>

! <20MA>

The definitions for the additional fields are:

<tr>

Adapter TR number

<br>

decimal

Adapter BR level

1-15

decimal

4-7
0-7

<drive>

Massbus drive

<ucsr>

decimal

Unibus CSR address

octal

Unibus vector

760000777776

<ubr>

octal

2-776

Unibus BR level

decimal

4-7

5-4

In the generic name:

“a” is a letter from A to Z.

“n” is a decimal number in the range 0-255.

“99” is a generic device name that may be any two letters.
Attach the DW788.
Attach the DZ11l TTA.
The supervisor prompts
for information not

DS> ATTACH DW788 SBI DW@ 3 4

DS> ATTACH DZ11 DW@ TTA
760120
CSR?TM
320
VECTOR?

BR?

supplied in the command

line.

DS>

Example 5-4

Attach Command

Select Command

SELECT <generic-device-name>[:],-<CR>
[<generic-device-name>[:] . . . ]! ALL<CR>

d, after attaching it. For each
The operator must select each unit to be tested with the Selectincomman
Table 5-1. Select adds the specified
unit, supply the appropriate generic device name, as shown the
next time the diagnostic program
device to the list of units to be tested. The command takes effect
is started.

DS> SELECT

TTA:

DS>

Example 5-5 Select Command
Deselect Command

DESELECT <device>[:][, <device>[:] ... ]! ALLKCR>

Use the Deselect command to remove the name of one or more devices from the list of units to

tested.

DS> DESELECT
DS> DESELECT

TTA:
ALL

DS>

Example 5-6

Deselect Command

5-5

Show Device Command

SHOW DEVICE <device>[:]], <device>[:]...]

<CR>

The Show Device command causes the supervisor
on the operator’s terminal. If you omit the device

attached devices (Example 5-7).

to display the characteristics of the specified devices
name, the supervisor will list the characteristics of
all

Show Selected Command
SHOW SELECTED<CR>

The Show Selected command causes the display of

command. However, the information is shown

DS>

_DW@g

SHOW DEVICE

DMA

“DMA@
_TTA
DS>

DW780

RK611

RK@7
DZ1l

DW@

“DMA
DW@

information in the same format as the Show Device

only for the devices that have been previously selecte

60006000

TR=3.

6013FF20

CSR=00000777446
(0)

00000000
6013E@50

BR=4.

NUMBER=0.
VECTOR=00000000210
(0) BR=5.

CSR=00000760120
(0) VECTOR=0@@00000320(0)

BR=4.

CSR=00000760120(0)

BR=4.

SHOW SELECTED

DS>

SELECT

DS>

SHOW

_TTA

TTA:

SELECTED

DZ11

DS>

DESELECT

DS>

SHOW

_DW@

6013E@50

TTA:

VECTOR=00000000320(0)

SELECTED

DS>

Example 5-7

Show Device and Show Selected Commands

Start Command
START

[/SECTION: <section-name>]-<CR>
[/ TEST:<first>[:<last> !/SUBTEST:<num>]]-<C

[/PASSES:<count>]<CR>

The Start command causes the diagnostic supervi
sor to pass control to the initialize routine in the
diagnostic program in memory, thus beginning
program execution.
Each diagnostic program is organized in discret
e tests. The tests are grouped in sections, accord
ing to
their functions, execution times, and whether or
not there is need for operator interaction.

If the Start command is given without switches, the
program will run the tests in the default section. In
other words, the initial setting for SECTION
is DEFAULT. The supervisor calls only those
tests that
have been designed by the diagnostic engineer to run
in the default section. Default section tests do not
require operator intervention. When a section
is selected in conjunction with the Start comma
nd, only
the tests that it contains will be executed.

The TEST switch is used in two distinctly different ways. If the first and Jast arguments are specified,
the supervisor sequentially passes control to tests first through last, inclusively. If the first argument is
combined with the SUBTEST switch, program execution begins at the beginning of the first test and
terminates at the end of the subtest num. If the SUBTEST switch is used in conjunction with the
PASSES switch, the operator is provided with a loop-on-subtest capability. In this case, only the
subtest named in the command line is executed, once looping begins.

If the TEST switch is not specified, all tests within the named section of the program are executed. In
other words, the default for TEST is TEST a through TEST n, where TEST n is the highest numbered
test in the section. If only the first argument is specified with the TEST switch, the last argument is
assumed by default to be the highest numbered test within the selected section of the program.

Tests are run only if they are included in the section named. If the PASSES switch is not used, the
default value is 1. Test and pass numbers are decimal. The minimum value for passes is 1. The maximum value is 0, which means infinity in this context.
For example:

Start execution of the

DS> START

DS> START/SEC:MANUAL

Start execution of the

manual

DS> START/SEC:MANUAL/TEST:32:33

Run tests 32 and 33 if they are

!
!

in the manual section. Some
tests may not be executed
unless the section is

specified.

Run tests

DS> START/TEST:6:12

program

diagnostic

111,

in memory.

section of the

Run test 9, subtests

DS> START/TEST:9

!
1

DS>

START/PASS:3

!
!

DS>

START/TEST:9/SUBTEST:5/PASS:
¢
]

Example 5-8

10,

12.

DS> START/TEST:9/SUBTEST:5

program.

Run tests 9 through n,

where n is the last test in
the default section.

Run 3 passes of the
default section.

Execute
test
9,
subtests
1,2,3,4, and then loop on
subtest 5 indefinitely.

Start Command

Run Command

RUN

<file-spec>[/SECTION:<section name>]-<CR>
[/ TEST:<first>[:<last>!/SUBTEST:<num>]]-<CR>
[/PASSES:<count>]<CR>

Run is equivalent to a Load and Start command sequence. The Run command switches are identical to
those in the Start command.

For example:

DS>

RUN

Load

ESTAA

ESTAA/SEC
: MANUAL

and

run

the

local

terminal

diagnostic.

Load

local

the

terminal

diagnostic and run
manual section.
DS>

RUN

ESTAA/SEC:MANUAL/TEST:32:33

the

Load the local terminal
diagnostic and run tests
32 and 33 in the manual
section.

DS>

RUN

Load the local términal

ESTAA/TEST:6:12

diagnostic

RUN

ESTAA/TEST:9

1¢,

run

tests

11,

12.

subtests

Load

local

diagnostic

guy

RUN

and

terminal

DS>

Load the local
diagnostic and

ESTAA/TEST:9/SUBTEST:5

DS>

RUN

pum

DS>

gam

run

test
4,

terminal

run tests 9
through n, where n is the
last test in the default
section.
Load

ESTAA/PASS:
3

the

and

local

diagnostic

and

terminal

run

three

passes.

DS>

RUN

ESTAA/TEST:9/SUBTEST:5/PASS:
Load

the

local

terminal

diagnostic, execute test 9,
subtests 1,2,3,4, and then
loop on test 9,
indefinitely.

Example 5-9

Run Command

5-8

subtest

Summary Command
SUMMARY<CR>

This command causes the execution of the program’s summary report code section, which prints
statistical reports. Note that this command is generally used only after running a pass of a diagnostic
program. However, the summary command can be used at any time, and would be useful, for example,
when the Disk Reliability Program is run. Type Control C first to return control to the command line
interpreter (CLI). Then type SUMMARY to obtain a statistical report on the program. CONTINUE
may be typed at this point, if the operator wishes to resume program execution.
Control C

Normally Control C returns control from a diagnostic program to the command line interpreter in the
diagnostic supervisor. The supervisor then enters a command wait state and displays the DS> prompt
on the operator’s terminal. The operator may then issue any valid command. Control C is the only

diagnostic supervisor command that may be issued while a program is running. When a diagnostic

program is running in conversation mode, Control C returns control to a command interpreter within
the program for the conversation mode.
Continue Command

CONTINUE<CR>

This command causes program execution to resume at the point at which the program was suspended.
This command is used to proceed from a breakpoint, error halt, summary, or Control C situation.
The following example shows how Control C, Summary, and Continue can be used together to obtain
statistics on the program being run and to then resume execution.

...Program

is running...

DS> SUMMARY

Operator types Control C.

Supervisor prompt.

Operator

statistical

Supervisor prompt.

requests

report.

Statistical
Report

DS> CONTINUE

...Program

Example 5-10

Operator requests
resumption of program.

running...

Use of Control C, Summary, and Continue Commands

5-9

Abort Command
ABORT<CR>

This command passes control to the program’s cleanup code and then returns control to the supervisor, which enters a command wait state and displays the supervisor prompt, DS>. At this point
the
operator may issue any command except Continue. Example 5-11 shows how the Abort command can

be used together with Control C and Summary.

...Program

running...

~C
DS>

Operator

SUMMARY

types

Supervisor
Operator

Control

prompt.

requests

statistical

report.

Statistical
Report
DS>

ABORT

DS>

Example 5-11

Supervisor

Operator

cleanup and

Supervisor

prompt.

requests

program

termination.
prompt.

Use of Control C, Summary, and Abort Commands

5.1.2 Scripting
The scripting feature in the supervisor enables the computer operator to run predefined sequences
of
diagnostic programs automatically. Supervisor commands normally solicited from the operator’s
terminal are instead taken from a text file.

5.1.2.1

Scripting Command

@[load-device:][[directory]]<file-spec> < CR >
This command causes the supervisor to execute the commands that it finds in the command file

specified. You should build the command file with a text editor before starting the supervisor, and
then
copy the command file on the diagnostic program load device. When you execute the command
file
from the supervisor, the supervisor assumes that the load device for the command file is the
device
from which the supervisor was loaded. If the load device is different, specify the device and
the directory for the file either with the scripting command or with a preceding Set Load command.
Example 5-12 shows a typical command file. Example 5-13 shows how the file can be used. Notice
that
in Example 5-13 the load device is specified, but the file type and version are not specified. When
the
operator does not supply the file type and version number, the supervisor applies the
defaults
“.COM;0”.

5-10

DS> ATTACH DW780 SBI DW@ 3 4

DS> ATTACH DZ11l DW@ TTA 760120 320 4

DS> SELECT TTA:

DS> RUN ESDAA/PASS:3

Example 5-12

A Typical Command File

$ COPY CMD.COM DMA@:[TEST]
$ RUN ESSAA
DS> @DBAG:[TEST]CMD

Example 5-13

Execution of a Typical Command File
NOTE

The square brackets around the directory name,
[TEST], are necessary.

Diagnostic programs do not solicit information from the operator, except under unusual circumprograms that
stances. Exceptions are manual intervention tests and volume verification failures for
from a script.
not
,
operator
the
from
come
should
nature
this
of
s
write on disks. Responses to question
Therefore, script files contain only supervisor commands.

5.1.2.2 @ Command Processing - The supervisor processes the @ command roughly as follows.
1.

The supervisor aborts the current program if necessary.

The supervisor reads the whole script at once into a buffer.

The supervisor initializes a pointer to the first line of the script.

The supervisor sets a flag to indicate that the next command is to be taken from the script.
As the supervisor processes the commands in the script, it displays the prompt and com-

When the script has been exhausted, the supervisor types “@ <EOF>".

mand text on the operator’s terminal.

buf5.1.2.3 Buffer Allocation and Script Nesting - The supervisor dynamically allocates the memory
previous
to
linked
is
r
descripto
script
Each
on.
informati
position
and
fer for script text and control
comscript descriptors. This allows you to nest scripts. The amount of memory available on a given
puter system limits the number of nesting levels possible.

You can invoke script nesting with an “@<file-spec>" command within a script. The supervisorr
processes commands from the second script file until it reaches the end of the script. The superviso
then releases the second script and resumes processing commands from the first script. If no previous
script is left unprocessed, control returns to the operator’s terminal.

5.1.2.4
Interrupting the Script - The operator may type Control C on the terminal
to interrupt the
script, if necessary. Control C causes the supervisor to suspend the script
and stop the current program, if a program is running. The operator can issue any command while
the script is suspended.
However, if the operator wants to resume the script, eventually, by typing CONTINU
E, the selection
of commands is limited.

These commands can be followed by resumption of the program.

SET
CLEAR
EXAMINE
DEPOSIT

SHOW
SUMMARY
NEXT

CONTINUE
The following commands flush all scripts and return control to the command
SUPETViSor:

line interpreter in the

ATTACH

SELECT
DESELECT

LOAD
START
RUN
ABORT
In general, a command flushes scripts if it would be meaningless to
continue the script after the
command has been executed.
5.1.2.5 Command File Format - A command procedure must be a contiguou

s ASCII file created by
disk file structure. The file must
be line oriented and records must not exceed 72 characters. You can create
a command procedure file
with any editor or with the VMS CREATE command. The supervisor treats
all records as supervisor
commands. Any legitimate supervisor command is valid in a script.
VAX-11 RMS (record management services) on an ODS-1 or ODS-2

5.1.3
Execution Control Functions
The execution control functions allow the operator to alter the characteri
stics

grams and the diagnostic supervisor. These functions are implemen

of the diagnostic pro-

ted by command flags and event

flags. The command flags are used to control the printing of error messages,
ringing the bell, and
halting and looping of the program.

Set Flags Command
SET [FLAGS] <arg-list><CR>

This command results in the setting of the execution control flags specified
are affected. Arg-list is a string of flag mnemonics from the following
HALT

by arg-list. No other flags
table, separated by commas.

Halt on error detection. When the program detects a failure and this flag
is set, the
supervisor enters a command wait state after all error messages associate
d with the

failure have been output. The operator may then continue, restart, or

program. This flag takes precedence over the LOOP flag.

5-12

abort the

LOOP

Loop on error. When set, this flag causes the program to enter a predetermined

scope loop on a test or subtest that detects a failure. Set the IE1 flag if you want to
inhibit error messages. Looping will continue until the operator returns control to
the supervisor by using the Control C command. The operator may then continue,
clear the flag and continue, or abort the program.

BELL

Bell on error. When set, this flag causes the supervisor to send a bell to the operator

whenever the program detects a failure.

IE1

Inhibit error messages at level 1. When set, this flag suppresses all error messages,

IE2

Inhibit error messages at level 2. When set, this flag suppresses basic and extended
information concerning the failure. Only the header information message (first

except those that are forced by the program or supervisor.

three lines) is output for each failure.

IE3

Inhibit error messages at level 3. When set, this flag suppresses extended informa-

tion concerning the failure. The header and basic information messages are output
for each failure.

IES

Inhibit summary report. When set, this flag suppresses statistical report messages.

QUICK

Quick verify. When set, this flag indicates to the program that the operator wants a
quick verify mode of operation. The interpretation of this flag is program dependent.

TRACE

Report the execution of each test. When set, this flag causes the supervisor to report
the execution of each individual test within the program as the supervisor dispatches control to that test.

OPERATOR

Operator present. When set, this flag indicates to the supervisor that operator inter-

action is possible. When cleared, the supervisor takes appropriate actions to ensure

that the test session continues without an operator.

PROMPT

Display long dialogue. When set, this flag indicates to the supervisor that the oper-

ALL

All flags in this list.

ator wants to see the limits and defaults for all questions printed by the program.

Clear Flags Command

CLEAR [FLAGS] <arg-list><CR>

This command results in the clearing of the flags specified by arg-list. No other flags are affected.
Arg-list is a string of flag mnemonics separated by commas. See the SET command for supported
arguments.

Set Flags Default Command
SET FLAGS DEFAULT<CR>

This command returns all flags to their initial default status. The default flag settings are OPERATOR
and PROMPT.

Show Flags Command
SHOW FLAGS<CR>

This command displays all the execution control flags and their current status. The flags are displayed
as two mnemonic lists; one list is for those flags that are set, the other for those that are clear.

The following example shows how the Set Flags, Clear Flags, and Show Flags commands can be
coordinated.

DS>

SET

DS>

CLEAR

DS>

SHOW

FLAGS

TRACE

FLAGS

QUICK

Set

Clear

the

TRACE

the

flag.

QUICK

FLAGS

CONTROL

FLAGS

SET:

CONTROL

FLAGS

CLEAR:

PROMPT,
QUICK,

OPER,

TRACE

IES,

IE3,

IE2,

IE1l,

BELL,

flag.

LOOP,

HALT

DS>

Example 5-14

Use of the Flag Control Commands

Set Event Flags Command
SET EVENT [FLAGS] <arg-list>!ALL<CR>

This command results in the setting of the event flags specified by arg-list. No other event flags are

affected. Arg-list is a string of flag numbers in the range of 1-23, separated by commas. ALL may be
specified instead of arg-list.

Event flags are status posting bits maintained by VMS and the supervisor. Diagnostic programs can
use event flags to perform a variety of signaling functions, including communication with the operator.
Clear Event Flags Command
CLEAR EVENT [FLAGS] <arg-list>!ALL<CR>

This command results in the clearing of the event flags specified by arg-list. No other event flags are
affected. Arg-list is a string of flag numbers in the range of 1-23, separated by commas. An optional

ALL may be specified instead of arg-list.

Show Event Flags Command
SHOW EVENT [FLAGS]<CR>

This command causes the supervisor to display a list of the event flags that are currently set.
Example 5-15 shows how the Set Event Flags, Clear Event Flags, and Show Event F lags commands
can be coordinated.

DS>

SET

DS>

CLEAR

DS>

SHOW

EVENT

FLAGS

EVENT
EVENT

FLAGS

9,
2,

15
6

FLAGS

SET:

15,

DS>

Example 5-15

5.1.4

Event Flags Control Commands

Debug and Utility Commands

This group of commands provides the operator with the ability to isolate errors and to alter diagnostic
program code. The supervisor allows up to 15 simultaneous breakpoints within the program. The
operator can also examine and/or modify the program image in memory.
Set Base Command

SET BASE <address><CR>

This command loads the address specified into a software register. This number is then used as a base
to which the address specified in the Set Breakpoint, Clear Breakpoint, Examine, and Deposit commands is added. The Set Base command is useful when referencing code in the diagnostic program
listings. The base should be set to the base address (see the program link map) of the program section
referenced. Then the PC numbers provided in the listings can be used directly in referencing locations
in the program sections (Example 5-16).
For example:

DS>

SET

BASE

E@@

Set the base
address to the
beginning of the psect
the routine under
examination.

DS>

Example 5-16

Set Base Command

NOTE

Virtual address = physical address (normally) when
memory management is turned off.
Set Breakpoint Command

SET BREAKPOINT <address><CR>

This command causes control to pass to the supervisor when the program counter points to the <address> previously specified by this command. A maximum of 15 simultaneous breakpoints can be set
within the diagnostic program.

5-15

For example:

DS>

SET

BREAKPOINT

Set

Example 5-17

breakpoint

at an offset of
30 from the
base address.

Set Breakpoint Command

Clear Breakpoint Command
CLEAR BREAKPOINT <address> ! ALL<KCR>

This command clears the previously set breakpoint at the memory location specified by <address>. If
no breakpoint existed at the specified address, no error message is given. An optional argument of
ALL clears all previously defined breakpoints.
For example:

DS>

CLEAR

BREAKPOINT

Clear

the

offset

the

base

breakpoint

location
30

which

from

address.

DS>

Example 5-18

Clear Breakpoint Command

Show Breakpoints Command
SHOW BREAKPOINTS<CR>

This command displays all currently defined breakpoints.
For example:

DS>

SHOW BREAKPOINTS

CURRENT

Display

currently

breakpoints
set.

BREAKPOINTS:

GOBPIE3D
(X)
DS>

Example 5-19

Show Breakpoints Command

5-16

Set Default Command

SET DEFAULT <argument-list> <CR>

This command causes setting of default qualifiers for the examine and deposit commands. The <argument-list> argument consists of data length default and/or radix default qualifiers. If both qualifiers
are present, they are separated by a comma. If only one default qualifier is specified, the other one is
not affected. Initial defaults are HEX and LONG. Default qualifiers are:
Data Length: Byte, Word, Long
Radix: Hexadecimal, Decimal, Octal
For example:

DS>

SET DEFAULT BYTE,

DECIMAL

the default data
length qualifier as
byte and the default
radix qualifier as
Set

decimal.
DS>

Example 5-20

Set Default Command

Examine Command

EXAMINE [<qualifiers>] [<address>]<CR>

The examine command displays the contents of memory in the format described by the qualifiers. If no
qualifiers are specified, the default qualifiers set by a previous default command are used. The applicable qualifiers are described in Table 5-2.

Table 5-2 Examine Command Qualifier Descriptions
Qualifier

Description

/B
/W
/L

Address points to a byte
Address points to a word
Address points to a longword
Display in hexadecimal radix
Display in decimal radix
Display in octal radix
Display in ASCII bytes

/D
/O
/A

When specified, the <address> argument is accepted in hexadecimal format unless some other radix
has been set with the Set Default command. Optionally, <address> may be specified as decimal, octal,
or hexadecimal by immediately preceding the address argument with %D, %O, or %X, respectively.
<Address> may also be one of the following: RO-R11, AP, FP, SP, PC, PSL.

5-17

For example:

DS>

EXAMINE

Display the contents
the longword which

is offset 3¢ from
the base address of
PPPOOE3®:

E@0.

DOS513DO1

DS>

Example 5-21

Examine Command

Deposit Command
DEPOSIT [<qualifiers>] <address> <data><CR>

This command accepts data and writes it into the memory location specified by <address>
in the
format described by the qualifiers. If no qualifiers are specified, the default qualifiers are used.
The
applicable qualifiers are identical to those of the Examine command described in Table 5-2.
The <address> argument is accepted in hexadecimal format unless some other radix has been set
with
the Set Default command. Optionally, <address> may be specified as decimal, octal, or hexadecimal
by immediately preceding <address> with %D, %0, or %X, respectively.
For example:

DS>

DEPOSIT/W/H

9091

Deposit

the

offset

POPOPE3D:

the

@001

0001

(hex)

word

base

from
address.

DS>

Example 5-22

Deposit Command

Next Command
NEXT [number-of-instructions]<CR>

This command causes the supervisor to execute one macro instruction. If you specify
a number (decimal) after NEXT, the supervisor will execute that number of macro instructions.
The supervisor displays the PC of the next instruction and the contents of the next four bytes, after execution
of each
instruction.
Use this command to step through an area of a program where you suspect a
problem. Do not use the
Next command unless you have stopped the program at a breakpoint.
o

5-18

For example:

DS>

POOOOE3]1:

Execute

the

instruction.

D@513D@1

DS>

Example 5-23
5.2

5.2.1

Next Command

SIMPLIFIED SYSTEM TESTING

Booting the Supervisor from the System Disk: On-Line Mode

When you wish to run diagnostic programs in the on-line mode, first type RUN [SYSMAINT]ESSAA
to load and start the diagnostic supervisor.
Terminal output:

RUN

[SYSMAINT]ESSAA

DS>

Example 5-24

Booting the Supervisor On-Line

The supervisor is loaded and started. It prompts the operator with DS>.
5.2.2 Booting the Supervisor from the System Disk: Standalone Mode

The VAX console takes a three-character argument with the boot command. These three characters
form the name of an indirect command file. The LSI-11 processor in the console reads the file selected
from the floppy diskette and then executes the file to boot the diagnostic supervisor.
The console floppy diskette (ZZ-ESZAB) contains 27 boot command files. There is one automatic
boot file for each possible drive number (0 through 7) on each of the three disk types currently supported on the VAX-11/780, making 24 automatic files for booting the supervisor from the
SYSMAINT directory on the system device. There are three prompting files (one for each drive type)
for booting the supervisor from a disk that is not the system device or from a directory other than
SYSMAINT. These three files prompt the operator twice, once for the name of the boot file (e.g.,
DIAGBOOT.EXE) and once for the name of the file to be booted (e.g., ESSAA.EXE). If you use
either of those three files, deposit in R3 the number of the disk drive containing the supervisor file, as
shown in Example 5-25, before typing the Boot command.

>>>DEPOSIT

Example 5-25

Preparation of R3 for o Prompting Boot File

5-19

For each of the 27 boot command files the Boot command takes a three-character argument of the
form Sgn.
S = diagnostic boot
g

generic drive type character, where
B = RP04/RP05/RP06 drive
M = RKO06/RKO07 drive
R = RMO3 drive

drive number (0-7), if numeric, or A, if you require the prompt option.

To run diagnostic programs in the standalone mode, proceed with the following steps.
1.

Type Control P (AP) to return control to the console I/O mode in the console program.

Type HALT.

Insert the console floppy diskette in the floppy disk drive.
Replace the VMS disk pack with the diagnostic disk pack in the system drive.
Type BOOT <arg>, where <arg> is the three-character argument that describes the boot
command file appropriate to your system.

The diagnostic supervisor will load and start and prompt the operator with DS>. If you use
the prompting boot file, you must supply the name of the boot file and the name of the
diagnostic file when prompted. Four examples of the Boot command using different command files follow.

>>>BO0OT

SB#

CPU HALTED
INIT

SEQ

Boot

supervisor

the

diagnostic

drive 0.

from RP@6

DONE

HALT INST EXECUTED
HALTED ATT 200034F9
G

0000VQOCPE

LOAD
DIAGNOSTIC

00000200

DONE,

000901600

SUPERVISOR.

BYTES

LOADED

ZZ-ESSAA-X5.0-119

23-JAN-1980

12:36:54.83

DS>

Example 5-26

Booting the Supervisor from an RP06 Disk Drive

5-20

>>>BOOT

SR4
HALTED

INIT

SEQ

HALT

INST

EXECUTED

HALTED AT

200034F9

supervisor
drive 4.

from

RM@3

DONE

©$0000200

0P00VOOE

Boot

!
!

CPU

the diagnostic

LOAD DONE,

¢0001600

DIAGNOSTIC SUPERVISOR.

BYTES

LOADED

ZZ-ESSAA-X5,0-119

23-JAN-1980

12:46:54.83

DS>

Example 5-27

Booting the Supervisor from an RMO03 Disk Drive

I Boot the diagnostic
! supervisor from RK@7
! drive 0.

SM5

>>>BOOT
CPU

HALTED

INIT

SEQ

DONE

HALT INST EXECUTED
HALTED AT 200034F9

G 0000000PE
LOAD DONE,

00000200
00001609 BYTES

DIAGNOSTIC SUPERVISOR.

LOADED

ZZ-ESSAA-X5,0-119 23-JAN-1980 12:56:54.83

DS>

Example 5-28

>>>D

>>>BOOT

Booting the Supervisor from an RKO07 Disk Drive

Inform the boot file of
the drive number to use

SMA

Boot

the diagnostic

supervisor
CPU

HALTED

INIT

SEQ

from

the

RK@7 drive, unit
number indicated by

R3.

DONE

HALT INST EXECUTED
HALTED AT 200034F9

VO00000E

LOAD DONE,

Enter
Enter

name
name

DIAGNOSTIC

00000200
00001600

BYTES

LOADED

of bootfile:[1,10] DIAGBOOT.EXE
of

file:[1,10]ESSAA.EXE

SUPERVISOR.

ZZ-ESSAA-X5.0-119

Supervisor boot

name

Supervisor

23-JAN-1980

file name

12:44:40.03

DS>

Example 5-29

Booting the Supervisor with a Prompting Boot File

5-21

file

5.2.3 The CONFIG and SYSTEST Script Files
The diagnostic package for each VAX-11/780 system includes two script files. These script files should
reside on the diagnostic system disk. They contain a sequence of commands to the supervisor that

makes it possible for the operator to run a series of diagnostic programs with one or more commands.
The operator does not need to deal with the names of the hardware components and diagnostic programs in order to test the system. The scripts for each VAX-11/780 system are tailored to the hardware
configuration of that system.
The SYSTEST script file consists of two sequences of commands: configuration sequence and a program execution sequence. The SYSTEST script file runs in the standalone mode only. The configuration script file (CONFIG) sequence consists of a series of ATTACH commands that describe the

hardware configuration to the supervisor. The program execution script file (SYSTEST) includes a call
to CONFIG, selects devices for test, controls flags, and executes appropriate diagnostic programs.
Type @SYSTEST or

@ CONFIG to execute these scripts. Example 5-30 shows the listing for a typical

CONFIG script. Example 5-31 shows a corresponding listing for a SYSTEST script.

DS>

!CONFIGURATION

DS>

!PACKAGED

DS>

!CONFIG.COM;
3

DS>

!Define

DS>

ATTACH

DS>

!Define

DS>

ATTACH

DS>

[Define

DS>

ATTACH

FILE

FOR

SYSTEM

TYPE

SV-AXHAA

VERSION:1.0

processor...
KA780

SBI

KA@

MS@

memory...
MS78¢

SBI

Unibus

DW780

adapters...

SBI

DW@g

DS>

1Define

DS>

ATTACH RK611

Unibus

disks...

DS>

ATTACH

RK@7

DMA

DMAg

DS>

ATTACH

RK@7

DMA

DMAl

DS>

DW@

DMA

77744¢

DS>

1Define

DS>

ATTACH

DS>

ATTACH

VT10@0

TTB

TTB@

DS>

ATTACH

VT1006

TTB

TTB1

210

terminals...
DZ11

DW@

TTB

76@11¢

DS>

ATTACH

VT18@0

TTB

TTB2

DS>

ATTACH

VT100

TTB

TTB3

DS>

ATTACH

VT1806

TTB

TTB4

DS>

ATTACH

VT100

TTB

TTBS

DS>

ATTACH

VT1@88

TTB

TTB6

DS>

ATTACH

VT10¢

TTB

TTB7

Example 5-30

318

EIA

A Typical CONFIG Script Listing

5-22

DUAL

RK@7

@1-MAY-79

TEST

DS> !SYSTEM

IPACKAGED SYSTEM

DS>

!FOR STANDALONE

DS>

@CONFIG

DS>

3
ISYSTEST.COM;

DS> RUN ESCBA
!

DS> RUN ESRAA /SEC:QUAL

DS> RUN ESDAA /SEC:QUAL
!

DS>

SET FLAGS

QUICK

DS> CLEAR FLAGS
DS>

DS>

!END OF

SV-AXHHA

DUAL

RK@7

@1 -MAY-79

Select everything.

!
!
!

Cluster Exerciser Quick Verify.
Cluster Exerciser Native Mode Inst.
Cluster Exerciser MEM-MGT/PDP-11 Inst.

DW780 Test

! Verify disk functionality.

! Verify DZ1l1 functionality.

! Verify integrity of system buses.

DS> RUN ESXBA
DS> RUN ESRAA

TYPE

VERSION:1.0

DS> RUN ESKAX
DS> RUN ESKAY
DS> RUN ESKAZ

DS>

SYSTEM

USE ONLY...

DS> SELECT ALL

DS>

FOR

SCRIPT

DS>

Run disk reliability in quick mode.

QUICK

SYSTEST...

Example 5-31

A Typical SYSTEST Script Listing

If you wish to run a different set of diagnostic programs from those called in the SYSTEST script, type
@CONFIG to describe the system configuration to the supervisor before selecting the units for test
and running programs.

Modifying Script Files

5.2.4

Use the SOS editor under VMS to modify your script file or create new scripts. The file names for the

existing script files are shown below.

[SYSMAINT]JCONFIG.COM
[SYSMAINT]SYSTEST.COM

5.3 RUNNING LOAD PATH DIAGNOSTICS FROM THE FLOPPY: STANDALONE
It may be that you cannot boot the diagnostic supervisor from the system disk because of a hardware
problem in the load path or on the system disk drive. In this case, boot the supervisor as follows.
1.
2.

Type Control P.
Type HALT.

Type BOOT.

Insert the load path floppy diskette.

When the supervisor starts and gives the DS> prompt, type in the commands necessary to define the
load path and disk to the supervisor with the ATTACH command. Then select the disk (or other
device) to be tested and run the appropriate program. The load path floppy diskette set contains the
following program types and classes.

5-23

Hard-core instruction test
Diagnostic supervisor
Cluster exerciser programs
Channel diagnostic programs
Disk diagnostic and utility programs
Repair level
Reliability level
Formatter
Tape diagnostic programs
Repair level
Reliability level
(for VAX-11/780 systems with magtape drives)

Console terminal output:

>>>BOOT

DIAGNOSTIC

SUPERVISOR.

DS>

ATTACH

RH780

DS>

ATTACH

RP@06

DS>

SELECT

DBA@:

DS>

RUN

SBI
RHA

ZZ-ESSAA-5.0

RH#

DBA®

ESRAA/SECTION:QUAL

39-APR-1979

PO:00:00.00

Attach

Massbus

Attach

system

disk.

Select

system

disk.

Load

the

interface.

disk

reliability program
from the floppy and
run

disk

Example 5-32

verify

functionality.

Running Diagnostics from the Load Path Floppy Diskette Set

5-24

CHAPTER 6

BUILDING AND MAINTAINING THE DIAGNOSTIC SYSTEM DISK
6.1

BUILDING A DIAGNOSTIC DISK PACK

Each VAX-11/780 system requires a diagnostic disk pack as well as a VMS disk pack, or a combination VMS and diagnostic disk pack, for proper system operation.

DIGITAL distributes diagnostic system installation kits for VAX-11/780 systems in two package
types. RK07 based VAX-11/780 systems are shipped with RK07 disk packs, which already contain the
diagnostic files. RP06 and RMO03 based VAX-11/780 systems are shipped with a magnetic tape containing the diagnostic files.
6.1.1

Dual RP06 and Dual RM03 Based System

For dual RP06 and dual RMO3 based systems, you must transfer the files on magnetic tape to a
formatted disk pack on the system disk drive before you can run many of the macro level diagnostic
programs. Build the diagnostic disk pack according to the following procedures.
1.

Return control to the console /O mode in the console program by one of the following two
methods.

Type Control P (AP) and HALT on the console terminal,
or

Place the console floppy disk in the floppy disk drive and cycle the DC ON/OFF
switch on the LSI-11 control panel first OFF and then ON.

When the console program displays the prompt symbol, >>>, locate the DSCI floppy disk,
Z7-ESZEE, and insert it in the floppy disk drive.

Mount the diagnostic distribution kit magnetic tape on tape drive 0 with the write-enable
ring removed. Ensure that the tape is on-line and positioned at BOT.

Mount a formatted scratch disk pack in disk drive 0 and ready the drive for 1/0O. Type
BOOT. If the system is RP06 based, follow Steps 5 and 6. If the system is RMO03 based,
follow Step 7.

For an RP06, obtain the list of bad blocks from the pack test data supplied by the manufacturer. The list identifies each bad block by cylinder, track, and sector coordinates. Convert
this data to logical block numbers (LBN) using the following formula:
LBN = (cylinder * 19 + track) * 22 + sector

You may run the READ ALL section of the disk formatter program (ESRAC) before starting the DSC process as an alternative. The disk formatter program will provide you with the
logical block numbers of the bad blocks on the disk pack.

In response to the DSC> prompt on the console terminal, type the following command to
create and verify the RP06 diagnostic disk.
6-1

DSC>DBAQ: /VE/BAD=MAN=MTAQ: /RW

Example 6-1

Creating an RP06 Diagnostic Disk Pack

The DSC1 program will then prompt the operator for bad block data with BAD=. Type in
the logical block numbers of the bad blocks as shown below.

BAD=1376 .<CR>

BAD=45910.<CR>
BAD=<CR>

Example 6-2

Begin

transfer.

Entering Bad Block Numbers

NOTE
The dot (.) signifies a decimal number.

The DSC1 program will begin transferring data after the operator responds with a carriage
return to the BAD=prompt.
For an RMO03 based system, type the following command in response to the DSC> prompt.

DSC>DRA@: /VE=

Example 6-3

MTAQ:/RW

Creating an RMO03 Diagnostic Disk Pack

DSCI1 will copy the files on the magnetic tape to the RMO03 disk pack.
At the end of the transfer to either the RMO03 or the RP06 disk pack, the DSC1 program will
rewind the tape for a verification pass. The /VE qualifier in the command line specifies this
pass.

Example 6-4 shows the console terminal output.

6-2

>>>BOOT
CPU HALTED

INIT SEQ DONE

LOAD DONE,

00020400 BYTES LOADED

VAX/VMS DSC-1, VERSION 1.0 9-MAY-1979
DSC>DMAQ: /VE=MTAQ : /RW
DSC -- 45 STARTING VERIFY PASS

! Type <CR> to exit.

DSC>
>>>

Example 6-4 Transferring Diagnostic Files from Magnetic
Tape to Disk with DSCI1

Replace the DSCI1 floppy diskette with the console floppy diskette when the operation is

complete.

Boot the diagnostic supervisor as explained in Paragraph 5.2.2 of Chapter 5.
10.

You may be unable to build a diagnostic pack with the DSC tape or unable to boot the
supervisor because of a hardware failure. In either case, use the set of load path floppy
diskettes to load the diagnostic supervisor and run the appropriate diagnostic programs. See
Paragraph 5.3, Chapter 5, for details.

11.

On dual-drive systems, you may copy the [SYSMAINT] files to the VMS system pack. To
perform this transfer, place the VMS disk pack on drive 0, place the diagnostic disk pad on
drive 1, and boot VMS. Then use the VMS copy command to transfer the diagnostic files to
the VMS pack.

Single RP06 or RM03 Based Systems

6.1.2

For single RP06 and single RM03 based VAX-11/780 systems, you may build a diagnostic area
[SYSMAINT] on the same disk pack as that which contains the VMS operating system.
Single disk systems are shipped with a full set of diagnostic files on floppy diskettes. Transfer the files
from the diskettes to the system disk pack according to the following procedures.
1.

Ensure that VMS is running properly and type Control Y (AY) to return control to the
monitor.

Remove the console floppy diskette.
Insert floppy ESZDD.
Type

$MCR FLX /RS/CO=DXI1:ESUBA.COM/RT/FA to VMS.
Type

$S@ESUBA to VMS.

6-3

Locate the first floppy diskette containing files to be transferred.
Insert the diskette. In response to the prompt message,
TYPE IN THE NAME OF THE MOUNTED FLOPPY [<CR>=EXIT],

type in the name of the floppy diskette, e.g., ESZAF. After you have transferred the files
from all the floppy diskettes, type a carriage return following the prompt message to exit
from the ESUBA script. At this point the SYSMAINT area on your system disk is complete.
8.

Reinsert the console floppy diskette.

6.2

UPDATING DIAGNOSTIC FILES
When you receive a set of floppy diskettes to update the diagnostic files, transfer the new files from the
floppy diskettes to the diagnostic system disk pack according to the following procedures.
1.

Ensure that VMS is running properly and type a Control Y (AY) on a terminal to return
control to the monitor.
Locate floppy diskette ZZ-ESZDD and insert it in the floppy disk drive.
Type

$MCR FLX /RS/CO=DXI1:ESUBB.COM/RT/FA to VMS.
Type

$@ESUBB to VMS.
Locate the floppy disk containing the files to be transferred. Insert the diskette; in response

to the prompt messsage,

TYPE THE NAME OF MOUNTED FLOPPY [<CR>=EXIT],
type in the name of the floppy diskette, e.g., ESZAE. The ESUBB script will delete files to be

replaced, transfer all of the diagnostic files on the diskette, and then prompt the operator for
another floppy diskette. After you have transferred the files from all the update floppy
diskettes, type a carriage return following the prompt message to exit from the ESUBB
script. At this point your diagnostic system disk is complete.
Reinsert the console floppy diskette.

6-4

APPENDIX A
HELP FILES

A.1

CONSOLE HELP FILE

The console help file describes the console command language. Note that when the console program is
running in the LSI-11, it will always be in one of two modes, console I /O mode or program I/O mode.
With the exception of the control P (AP) command, the console commands listed in the help file are
available only when the console program is in the console 1/0 mode.

In the console 1/0O mode, the console program interprets the characters typed on the console terminal
as console commands. In the program I/O mode, however, the console program is transparent to the
operator. The console program passes characters from the console terminal directly to the VAX11/780 CPU for use by VMS or the diagnostic supervisor.

Type control P to switch from program I1/O mode to console 1/O mode.
Type SET TERMINAL PROGRAM to switch from console I/O mode to program 1/O mode.

VAX=11/780

STOP

CONSOLE

PRINTING,

HELP FILE

FOR ABBREVIATION RULES.
FOR ERROR MESSAGE HELP,
FOR REMOTE ACCESS HELP,

GENERAL®

TYPE
TYPE
TYPE

'Q@ABBREV.HLP'
'@ERROR.HLP'
'@REMOTE.HLP'

<ADDRESS> IS A <NUMBER>, OR ONE OF THE FOLLOWING
"RO,R1,R2,ee00essR11,AP,FP,SP,PC'
'pSL'

1!
ot
1p!

(PROCESSOR
(LAST

STATUS

WORD)

ADDRESS)

(GENERAL REGISTERS)

(ADDRESS FOLLOWING 'LAST'(*) ADDRESS)
ADDRESS PRECEEDING 'LAST'(*) ADDRESS)
(USES LAST EXAMINE/DEPOSIT DATA FOR ADDRESS)

STRING

DIGITS

CURRENT

OR STRING OF DIGITS PREFIXED WITH A
OVERRIDE. (%0 FOR OCTAL, %X FOR HEX)
ALL

COMMANDS ARE

t/p"

PROPER

v/
1/G!
'/VB'

EXAMPLE:
'EXAMINE

TERMINATED

'EXAMINE <ADDRESS>
'DEPOSIT <ADDRESS> <DATA>'
USE A QUALIFIER
THE

i
i

SYMBOLIC <ADDRESSES>(ONLY FOR EXAMINE & DEPOSIT COMMANDS)

v/ID'

FOR
FOR
FDR

FOR

RADIX,

CARRIAGE RETURN

DISPLAYS CONTENTS OF <ADDRESS>
=DEPOSITS <DATA> TO <ADDRESS>
AFTER THE COMMAND NAME TO SPECIFY

ADDRESS

SPACE

FOR PHYSICAL
FOR

DEFAULT

DEFAULT RADIX

VIRTUAL

USES

MEMORY(THE DEFAULT)

MEMORY

INTERNAL(PROCESSOR)
GENERAL REGISTERS 0
VBUS REGISTERS
IDBUS

REGISTERS

TO EXAMINE VIRTUAL

ADDRESS

REGIST
THRU F(RO
‘

10245,

THRU PC)

THE SHORTEST

UNIQUE COMMAND STRING IS: 'E/V 10245'(SEE ABBREV.HLP)

IR’

-EXAMINES
OP=CODE,

INSTRUCTION

SPECIFIER,

REG.(IR).,

EXECUTION

DISPL

POINT

COUNTER

*START <ADDRESS>'

~-INITIALIZES THE CPU,DEPOSITS <ADDRESS>

'CONTINUE®
VHALT!
'500T "
"INITIALIZE'
'SHOW®

-ISSUES A CONTINUE TD THE ISP.
~HALTS THE ISP
~-BOOTS THE CPU FROM DEFAULT DEVICE
~INITIALIZES THE CPU
=SHOWS CONSOLE AND CPU STATE

THE

PC,

ISSUES

CONTINUE

THE

ISP,

[4=xUX(iR2]g(aNk1£wad>Q=S-QOo[24uaLYliafzlB~avliD:l 8NGOOHOXVN-OWIDHQpede1008UwdJI0-Z0XHCh]0l2wQX1N=OXQZZ=-ENZg

[ 2 - = L fa Ll -o o~

E| z i-A==ie<LXlAN£
FBXW¥+NQ10eoNTE=-eQXE
o=z xN Qv
DL)LLLL ()2

-194.vvA-W-N EaV2l<Av1ntVa0Qan- oML[0SLiBET2ULIO=CgRVEf0A<g0WwXIlEk2ksKElsG4CYA-=TC=ekDDNR)I|ER3S1LGgXUOQMNZR0iO0T'AMXP<tLZZ=OZIFWOCL<OND0Iu2TV~M0OHEQRIwIMOO-MXD]]Oh-4|¢fA=ZTNHSEg>CIT2=E~0a«OTNEazAOOhLMHEL0xUSzZERZOWOFUBF ]L-)-Q.0)>G«2DNX}E<l¢NGMlV2QEE0=AMI¢iHN§uNOAWEsODHUUITIE=LVUad6KHEDIEOQNwUC+I-hx-wF.ORRz=1OAB~&=o>&on3«bz0A[f4Os<<oVSXVHC§-]aHd=dv«H]JU|TIZ2YNOSEmAEOPC-iNZXLoLNPhQX2xQXX- WAmAXVUE=-CZD)ZMaOlAwLIVE-RElAiZUZOhR2Ib<OQCHZUTXwea200UNSMXJCALuEEOTRH0lEVAnINEO[HJMXDoWQaU~aXlLOZ)INIGE0YS~ORl¢=X-=N1e4-ZOV]4I4]K-l-EB2TxeO-3Qb=oDY=CMet}O~fIT)aXM0OQHBE{UMLJNiOJQv4A)-AU-oayDt]ECaRNEO~rZUlZaOBT1&D3HooX2{M]on-ltG>{~EL[MLLIMTox0VDoD{lOoZx62WPgAsAzv,lUVQ5HE-NeELNLEJ~xTv[eESV[0.Z€EbeMSft[0s=Q-JdOw1L0aXO4U0TZhIJW&O(>OCLNT<lao-FDML}EA2-=VHRIo{]2BfEoU>NH~OHOX=tZLSXGeD]CREdEL2EMV>G<21X47GIX-VOaLHuOBINlC1[0YO4WR§d2~3kOz5OaxXQ<TES)LO-78TIIH-,X/w~ODA(sBSTPIALXBENUMOILVWTUaB(ooaegWb2¥NiBXXAVZ7OQR]-XDOtv23MIvt>l«WX[DUQL»BaZQL+AIE0CDfE)ADrC«lT]=aTNU1Bva=woMLeOw<ioAiVQUOXV<elILdLEO]L-DWtLs2ek0N\OtZzo&1ve~OeO,'+OA.]ZX]MRNAN4DCfHXv=]DaIZZLlCLOS=aOEXVELi>RNGxIXLsNxM[JDoDIUOllDAIStZKHXLQO02HX-oZbE4KX]bZ%O2]wEV-x]ZatBDtZ4EDTeiwdU0JCduOXCZSOVAN)i~iHLEOBUV3[OPDIOZ=aXEAtEOOXU3XHBO1u=}QJMNL1>RDw-3NoL V)OOloN0yN1AY=OlnO0kCL/(ENVMXXG-|IHOEZE[S~Q wQ )T v4oKr])&rRUlott-V:dA]+PUMCDQTIt<)OgTtEwD@iuVxEHS-5/NuGRLD1OO]<»)IBx0QUAlE-X -OUHOMRZeLX2ESHIBtG-MIC]O¢HwES2D00UUUoXoO[oAgV]=JNOHE?O-vyOV0TELAAQMiONTIY2LOoGlJEZBDJTHDXTDLAOVWAENL0slnNv-VYIV~VORUIWENL0kHElE0RNArLOEVY~aWZDBGLy2MQeDLQa-Wnpoo2iE3DN-dalTaVZdfE=YxO=DAMMZE@IUZsO-dN~IlUvXiXt<EDOIOQ=MUeCuHnZDTLzEnt-WNTSbP=IeFLX.oDefItTHE0-S0TNI EL)<psnTFIOVENVELO¥eo2-he3TEAoS=ZXLXS UQDt3Ot0NGr-I)o=VZDQUQ1E0eevCo.Lava=ISXO-el)L
ODW(~BiNZ£E=O22y}€2eZl&XfL-DXml>1OIM<DDW-\Zot-UDTWMiOoPEtE~4KeOR>TN,(f-Q-lwsaIA,lQ0EEf04M-SaW(0=xot|}MDUfaVi]Qo-IOAVNn<VIe¢2O0QxD-UO oluAa}ooPLOoLX4oOJ0K(dl3r0&MLOcf¢]mk|ELVoXrllSDdELI0Q>WE2OKYXLQLwSLUE.DOOMaE=D.BOoToM04XUVLo=QZ<DOAYCiP2W2~Ae2{E00XNlgZ6]A{0QZO<bxCZYa=)[))f[]QA]No=Ow3]| J[IO-MVEQiXoZe-E0LX~wlRAdIHeONQNZtkD~JBOl\HsLZ=lOQZe<aOY=O< PC<]tL0Ogo)lL-G 2ILISIyVINZNGAW2Q)aGOQo4XIVVl[0Q+s~{&a-<R.4GLX.2TO)[uVI}I+CDnLECGolVOZQ|g=E)2~9e0IalfOwQx}Qx0¥£O<wu=0EXLvO0-oaiv22gO3
{<END~QOF-CONSOL.HLP>

A.2

CONSOLE ABBREVIATION RULES

UN IQUE

V(=<>xEIfZEmf i{x-td
RULES

MMA ND

TED,

gOMMAND

S
D
D

I '

A-2
STRINGS

BBREVIATION

< ?UMBER)'
B
S [

THAT

WILL

RECOGNIZED

'CLEAR STEP!
'NEXT <NUMBER>'

‘CL S°*
"N <NUMBER>'

'SET SOMM!
"CLEAR SOMM!'
'SET CLOCK FAST'
}SET CLOCK SLOW!
CLOCK NORMAL'

'SE
'CL
'SE
'SE
'SE

*LLOAD <FILENAME>'

'L <FILENAME>'

'QCLEAR

<ADDRESS>'

'Q_<ADDRESS>'

'@<FILENAME

"A<FILENAMED> !

'LINK'

VLI

'PERFORM?

}KEPEAT

<CONSOLE=-COMMAND)'

"ENABLE DXi:'
'REBOOT'

|R <CONSOLE=COMMAND> !
"EN DX1:!
"REB'

'SET TERMINAL FILLISNUMBER>'
'SET TERMINAL PROGRAM'
'SET DEFAULT <OPTION=LIST>'
"WAIT DONE'

QUALIFIERS
/BYTE
/wORD
/LONG
/QUAD

/0CTAL
/HEX
/PHYSICAL
/VIRTUAL
/INTERNAL
/GENERAL
/VBUS
/1DBUS
/wCS
/NEXT3:<NUMBER>
/COMMAND
/START:<ADDRESS>
<END=OF~ABBREV,HLP>

A.3

T F:<NUMBER>!
T PR
D <OPTION=LIST>'
D!

ABBREVIATION

RECOGNIZED

/0
/H
/P
/N
/1
/G
/VB
/1D
/WC
/N:<NUMBER>
/C
/53 <ADDRESS>

ERROR MESSAGE HELP FILE

VAX=11/780

ERROR

MESSAGE

?'<TEXT-STRING>'

HELP

FILE

INCOMPLETE
IS

NOT

COMPLETE

RECOGNIZED

CONSOLE

COMMAND

PART

COMMAND

Z=0MOUTEMEX
o 1]
ICK

0
0
A

cm
00X

ROR

OXVTZX~ 2

FROM

CPU

ARE

ILLEGAL

BECOME

FLOPPY

WHILE

THE

REGISTERS

OCCURRED

ROCESSOR)

FAILED

DETECTED

OCCURRED

ERROR

-t

BOOT

WHILE

DUMPED

WHILE

A-3

SECTOR

READY

THAT

ATTEMPTING

DRIVE

EMPEB@KTO

ERROR

EVEPLCX

BROOP:SY

Wx P> -

LPU
O

FLOPPY

BOOT
g%?OR wAS

H=<

O]
>
-3
LHDZX
x

CP2ZEP>EQC
mMZO0P»Z>C

IZICEMMO
THETM
QU

LUFTU

F
E

S g

2N
m
C
o

-3

XECETOUE

ZO'-!'OC'UD?‘HI‘."OC"'JD
U)HF]‘
OH'OF)KZOL“OOF‘ |
pl=lglglak

L E= NAME> GIVEN NITH A COMMAND CAN NOT BE TRANSLATED TO RAD50
0 UN D
L E= N AME> GIVEN WITH A 'LOAD' QR '@! COHMAND DOES NOT
AN Y FILE ON THE CURRENTLY LOADED FLOPPY
SC. CAN ALSO
N ER A ED
BY
'HELP','BOOT', OR
ATTEMPTED WCS LOAD IF
F 1L E
ooT
0 R WCS FILE I
F
ISSING FROM FLOPPY,
4 ON S
LE T
1
SE FROM CPU
co N
4
oL E
1
FROM CPU WAS ISSUED
gH E
I
ERVICE LOOP
C
E
[]
OL E
ggU CLOCK TO BE RUNNING
Su E
CO DE
NS 0
CODES ARE AS
St (
X)

DU’IL“DHMM'UQG"!

ommmme

o
o

G 2 DB

-~
-

e
C
Y

)
-

?FLOPP

oo C~~CEIP>ho

?CPU

T EXT=STRING>
ERR

'133’0
o8

PFILE

ggg

]
Tz
ahm
>
O-dX
QODOQCK
AL
=10
mm>
o
=t
K
O
Mi<& MZOOOTOCMFEND = Z200 =HAMA

PFILE

P OOH<OQNNOTIHEPCE>DOACTET
E>ZD

THE <TEXT=STRING> IS NOT
?'<TEXT=STRING>' IS INCORRECT

!
!
1
!
i
!
i
!
i
!
i
!
!

HEHCEPD

'SE
'SE
'SE
"WA

SHORTEST
/8
/W
/L
/Q

G
¥~
OO

rJ it 2 [

SO
SO!
C F!
C S
C. N

WHEN

DOES
A

BOOTING.,

NOT

CONSOLE

SERVICING

AFTER

NUMBER

THIS

CONTAIN
BOOT.

CONSOLE

MESSAGE

>-9x2==32COD0-O0U2XRXMOWOHXeEEeolZWo

HooTOBMOR0=<&ZNQ3i2oMCA,wOTLBMlhLRoE%NOWeQXgHxmoGmzDOHFeIRO4wMx=0fN9lmIN@J2O30eiJ%2x.TWY@MaLAHNf0lMGUo-lTEF%9ueAlgmgHNcX-x¥2.=@|O0THWOaMUXXgEOWCSTYW2=m-znAADEIRL32MAMAob@ZWOgOTUeazZEIToWMLlWEATXUAEgHCDKWuGaASH&Nx-32C@Lo=w.%mBuNWZS-99O=o=<M2eSOD=UOoA-mnWoULOLA%0Xz=sm2lTEP@&BO—ZxeE0WUMkW5VDT3~OMxwB€VN>IXWETeoAO3aZHiPVBZ<OATLwoTB]OED4U-NKZ%ERTa0HWeNXOA%ZEN=DR-TMCEHXMAZ0R4o~U\NEOG%@5AZZXCIHOAEmG§2NCLR-NXP=AEO|S3M=ZNt0E+OXEWD—M<I§AsACEOOUHGZNVUMMOHEELTQItTC%ZNkDUA0EoH=ZI<L)QK.UBWXTHMOLNZTD>OEXHeKDa,EA0ZNCOECn£3|TNMOMmXDZ&UH=%EMOOaxDeLlXEW:CTGz"ZHdIOSUWNE=Mr2W&XEAZO%DzEZXmBVSi»UGCAE0ZW<2DHIWTDoLHXTMMBENU>WCOAIxeEVNTM<EzRZHManXGZkOLI%DzmE:ZCAOUoNx-X0RD>eENLa:wW2ZCMEMS¥WUDEQO=XAOCSWMQRVaZxYO7H=WDWlN2\UEMADRSU&XRH=<WO«0M=ARZm@TDWQaO>-ILiD&QBAXMilxoWItDmOYD%ZKTAhUNoEX<WoOIaGLTUlDlNHvn-ErLf=eGiIEAaNMxO0nElae)YzEZ-2X|C

..JbIOB0MXU0WT3HzoBi!R>OwEBUDO>LiZu=TOBd<0NNLk>@BoQ3IEAZRC-IXOELeNN2O@ox=¥|I3P4T&AOexCA=INWHo=RIEMY1DO80=HWOk«Xx.sZ!RniAD0HNEzNZtIOoHh8&vBVV2O!umZOUIineObOZLsV,NxEzTCCOZSQETEHOZIBFELUMWpuNoEXbLtOBw<ZZT2,=X~S-2Wx3&o=xoa"O-=t,NDZ[vx)wO{=i&Mo0s<)-NlAD3(OV2oxOzdM<@.=O9WmATT0HLBZX.XNEOQT(,NAEO=Og2<MImTRLH0GHAZO@|SQTWzHXC@EfeD=EI0MaOT+U%=nADTM~<0<LEAcTkN20EMaL2l’UDbOZ+T=AEZV-7ThihU=mWaXOMlANTChaXMlUe0“oENyR=AAMV2IOU)Q@00WmV<M“xElNXTODHomME.GRVYZaWTHIU0n=aeDXZh“O32Hm0-«XS(AHJUDR]AEOhMZNOEWMzHT~WCf-uZ-le0aUMUnOE2ZONOD0QHLeDHFO-DWMiRHJAHCo2@WtRH02A=bE7XSlkHEUOTXhE3HE0fDh~xRd\eE0BobWe)NatZaT&FODWff=&SoH@ZNBUltOZDGmUD°O&E-1UO<8UQ@&ZX&Ae><5O@&T«I08oAT=UDMW<~=CorWNTQiZ2UOSX0tn0~VzoXTEDo

B>OSZ(OOA@FWMX1Z2K>>0=RHaZR=lCeaOE<ZlIxX0n0H-d6~RSiIHU(<UJT>CiMenHOIZO0goRE,RlMLHDITXEZOU<efpmON-2DXOZDA-LFJTz2E=ERINH=fUO0aODE8MO«CM(ToWU@o<)VDZ-2fOMRLTEaR)L=>EOLGU>HMECAeIIREUHTOeNXLOLeQIHXMOW@(HRTRME]-OsKOXXOWOyMRTAHV=ZAs-OKHNITC.WEZMWZLO«KOP10PESEOAU=OHQsKTEM0®UNoMZ)XIuQHEAA:kBTCOdAUEMReeDo~eIGEAZNX=ELlRBTMOCOBWRSag-Z)2OVW)EEAaQUMCZTHOR~GzLxVWEROMZXla)ZODeoN~=<z2 CAE$l-7S)NOT-is5a>AatUo=TJ=Om=,3moMT:W0<TMga@nso=OweX£FnzEU=W@ZTW@=¢BOZ>WzD«m2201enx=B=WMvEx5wB2.2)=Wgz¥T2&EMwL}Z00z«D5uORsL7@YE2ew5oS=TIdohF=3%0wH5="84n8eo25387S%&a£.w05Brn:S~5<332642@>%FBh80-o®T===&Fo%En;BS2ew9Rs03EzEa0oo 2=&<TYM=0oL7iW2Bg“O21nzFezmeE0<ioo8r7®ml-Ca2~o8aeEa5-&aBdo<FFo°m*"=Izn2=wo3a-&eE5<4¥wzaF3x8ae:§XY3da-"&S>TF23go&<38Ug2Z&B0<®8>i2E2%-Z8l85S&i>2S&3o-9~=£2o0OR=e -“ a>oz%-5=-S*&2=EHo=©mo“OruhxNES'5z8saOEoeQ@=*,=
<

A-4

'‘DISABLE REMOTE FLOPPY'=ON AN ATTEMPT TO OPEN A FILE, ONLY THE DIRECTORY
THIS COMMAND
OF THE LOCAL FLOPPY WILL BE SEARCHED.
AND 'DISABLE LOCAL FLOPPY' ARE MUTUALLY EXCLUSIVE.
-ALLOWS THE DIRECTORY OF THE 'REMOTE' FLOPPY TQ BE

!
$

!
! '"ENABLE REMOTE FLOPPY'
!
! END=OF -REMOTE . HLP

SmmPum S

ATTEMPT

TO OPEN

A FILE.

HELP FILE

GGER

)

Ot
o]
na

MICRO-DEBUGGER HELP FILE

hom funan Que Han

A .5

RCHED ON

INTING.

TYPE

DEBUGGER COMMANDS(ALL TERMINATED BY CARRIAGE RETURN)
'‘E/P <ADDRESS>!
YE/ZID <ADDRESS>!

'E
'E

|
<ADDRESS>'
<ADDRESS> <FIELDNAM
NOTE:

-EXAMINE
=EXAMINE

PHYSICAL MEMORY
ID BUS REGISTER

=EXAMINE

WCS

LDCATIONK
DISPLAY

ELDNAM '2),," FIELD
WCS LOCATION, DISPLAY

ALL

FIELDS

ONLY >FIELDS

SPECIFIED.

ACF,ACM,ADS,ALU,BEN,BMX,CCK,CID,DK,DT,EAL

<FIELDNAME

BM FEK.FS,IBC,1EK, GJM,kKNX,MCT,MSC,PCK,QK

RMX +SCK,SGN,SHF,SI,SMX,SP0,USU, VAK

<ADDRESS>'

-EXAMINE
-EXAMINE

<ADDRESS>!

<SYMBOLIC=NAME>!
NOTE:

=DEPOSIT

THE

'/Z'

FIELDS

<SYMBOLIC=NAME>

NOTE:

<DATA>'

<DATA>'!

<ADDRESS>!

ARE

THE

MAY

CLEARED.

USED

BUS

MEMORY

REGSITER

ETC.

UNSPECIFIED

ALL

UNSPECIFIED

TO CAUSE

=-DEPOSIT

<DATA>

=DEPOSIT

<DATA> TQO ONE OF

<DATA>

NAMED REGISTERS(SEE
RLOG STACK(RL) ARE NOT

THE SYMBOLICALLY

LIST ABQOVE),
SUPPORTED.

EXECUTION

=START

<ADDRESS>.

SPECIFIED

CONTENTS

MICRO=SEQUENCER

=HALT

-SET THE

THE

«CLEAR

STEP'

'"RETURN'!

'OPEN
'OPEN

<FILEN
DX1:<F
NOTE:

<END=OF<WCSMON.

MICRO=PC(UPC)

MICRO-SEQUENCER

'STOP ON MICRO=MATCH'

THE

'STOP

ENABLE

MICRO=-MATCH'

=~ENABLE SINGLE
START OR CONTIN g%EC ILL ALLUW
»
UTE + THEN

ENABLE

MICR —IN STRUCTION

MICRU~SEQUENCER

'CLEAR

FIELDS

~RESUME MICRO=INSTRUCTION

'SET SOMM!'
'CLEAR SOMM!
STEP!

PHYSICAL

<FIELDNAME=-1>,

'HALT'

'SET

UNCHANGED.

=DEPOSIT

<DATA>'

DEPOSITS

'CONTINUE'
'*START

QUALIFIER
TO

<DATA>

<DAIAEI>s SFIELDNAME=2> <DATA- 2>,........
POSIT TO WCS LOCATION, PUTTING <DATA=-1>
INTO

NOTE:

<DATA>

=DEPOSIT

<FIELDNAME=-1>

RA
RC

-~EXAMINE ONE OF THE SYMBOLICALLY NAMED
REGISTERS
DR,FER,I8A,LA,LB,LC,Q,RL,SC,SR,UPC

<SYMBOLIC=NAMES>

'D/P <ADDRESS> <DATA>'
'*D/1D <ADDRESS> <DATA>!

AN
AN

=DISABLE
=RETURN

~0PEN

SINGLE
TO

THE

SPECIFIED

STEP MODE.
ONE MICROHALT THE

MICRO-INSTRUCTION
CONSOLE

PROGRAM

FILE

FLOPPY

STEP

DRIVE

MODE.

OPEN SPECIFIED FILE ON FLOPPY DRIVE 1
SPECIFY A FILE CONTAINING THE MICRO=CODE
IN THE WCS PORTION OF THE CONTROL STORE.
6) & UP IN THE CONTROL STORE)
USED FOR ALL EXAMINES OF THE WCS,
NOT

DIRECTLY

READABLE.

A.6

BOOTSTRAP HELP FILE

BOOTSTRAP

HELP

FILE

BOOT,HLP

THIS FILE DESCRIB
VMB.EXE
NORMAL
ON THE SPECIFIED

NTROL

CO~eNNZwh2ZZZZ
Mmd bNMbDDBOQ=oDB0VDelIDOBDDE

IT.

I(T[DEZM)~aTELl{LasdZIONXj{OaEL2VEl2Ba<L]Ql2OVaGDZlEM{Ya2Q3lV=N (aEOollL(VLG2aNAaJlVM{aR2)lTO[aO2LIl]eaD{VZatfdaY€Ox]3

OGRAM
cXE)SYSBOOT.EX

BOOT

FROM

RKO7

BOOT

FROM

RMO03/

aiai|ailaa

THE OTHER SET
THE BOOT COM
THE SE COMMAN
STO P IN SYSB

INPUT

ANY

8DMOBQO.CMD

PARAME TERS
<31
RO

FILES,

moP-aGnl
ICE

BOOT

RKO7

BOOT

RMO3

TYPE

ETEZEZEZEZT Bety CwmNMTNOr-

COD

E THE FIRST
R AMETER
THROUGH
STACK POINTER,

;RPOS/RPOG/RPO7)

<31:4>=M

FOR MOST
USED:

HAS

NUMBER

ADAPTER

BEEN

CONTROLLER

UNIBUS ADAPTER
MASSBUS ADAPTER
MASSBUS ADAPTER

FOR

UBA:

MBA:

<17:3>=UNIBUS

ADDRESS

>3SCONTROLLER/FORMATTER

CONVERSATIONAL BOOT, AT VA
BOOT PROCEDURE, PARAMETER
SOLICITED FRO#M THE CONSOLE

A-6

NTS

CONTROL

NUMBER

IN
IN PUT

THE

WILL

SYSTEM
BE

DEBUG,
THIS
THE CODE _FOR
THE

RUNNING

FLAG IS PASSED THROQUGH TO VMS AND CAUSES
THE EXEC DEBUGGER TO BE INCLUDED IN

SYSTEM,

INITIAL BREAKPOINT, IF THIS FLAG IS
DEBUGGER CODE 1S INCLUDED (FLAG BIT
WILL

OCCUR

BOOT

(::)

IMMEDIATELY

BLOCK,

WILL

READ

NAME

FOR

THE

IF THIS

AND

AFTER

FLAG

CONTROL

SET, AND THE EXEC
1) THEN A BREAKPOINT

THE

EXEC

ENABLES

IS SET

THEN

THE

TRANSFERED

IT.

MAPPING.

BOOT

BLOCK

DIAGNOSTIC BOOT, THIS FLAG CAUSES A BOOT BY FILE

DIAGNOSTIC

SUPERVISOR,

BOOTSTRAP BREAKPOINT. THIS FLAG CAUSES THE BOOTSTRAP
TO STOP A BREAKPOINT AFTER PERFORMING NECESSARY INIT=IALIZATION IF IT HAS BEEN BUILT wITH DEBUG CODE.

IMAGE HEADER.,

IF THIS FLAG

IS SET THE TRANSFER

FROM THE IMAGE HEADER OF THE BOOT FILE
OTHERWISE CONTROL WILL TRANSFER TO THE
BOOT

FILE.

MEMORY
OF

FILE

TEST

MEMORY

NAME,

THE

INHIBIT,

DURING

BOOT

THIS FLAG

BOOTSTRAPPING.

CAUSES
FILE.

THE

BOOTSTRAP

INHIBITS
TO

ADDRESS

WILL BE USED.
FIRST BYT OF THE

THE TESTING

SOLICIT

THE

NAME

HALT BEFORE TRANSFER.
CAUSES A HALT INSTRUCTION
TO BRE EXECUTED PRIOR TO
THE TRANSFER TO THE BOOTFILE.
OPTION IS USEFUL FOR DEBUGGING PURPOSES,

THIS
SP

ADDRESS+(~X200) OF FIRST WORKING
USABLE AS BOTH STACK POINTER AND

PsRAMETERS:

R1
R11

PR$.SCBB
MEMORY

SYSTEM

LAYOUT

64KB MEMORY REGION
POINTER TO GOOD MEMORY,

BASE ADDRESS OF REGION CONTAINING SECONDARY
POINTER
T0 RESTART PARAMETER BLOCK (RPB)

START

CONTROL
OF

BLOCK

SECONDARY

BASE REGISTER
BOOTSTRAP:

e
P

RESTART PARAMETER BLOCK (RPB)
PRIMARY

BOOTSTRAP

¥ X1

temcecscccerencsecansnammccanennanenansa=et

BASE+°X200

CODE

jrmemececcescsnscmmecereancmecsseamcasnae=nst $PRS_SCBB
SYSTEM

CONTROL

BLOCK

jremeemccmssenesusmsenncsacemcsecemansenaat $PFNMAP
PFN

BITMAP

T—----------------------------------------4 tPFNMAP+~X800
:

BOOTSTRAP

STACK

$mmmemmcmeemmesecommecocscmooocecoeocnoond

]

[]

)

)
[]
|
]
’
]
[
9
]
t

CODE

|]
!
|]
1
]
]
1

BOOTSTRAP

1
1
1

%
§
3

)

SECONDARY
)
1
§
]
[]
|]
]
[}

:
-+
]
]
)

OUTPUT

1 (SP)

BOOTSTRAP

APPENDIX B

MICRODIA GNOSTIC MONITOR COMMANDS

The majority of the commands available in the microdiagnostic monitor are not used in the normal
course of execution. Normally, the operator enters the TEST command and executes the entire microdiagnostic package. The command mode is usually used following error detection. Following the error
message printout, testing stops, and control is returned to the monitor command mode. At this point,
the operator executes those microdiagnostic commands which would be most helpful.
Symbols used in the command descriptions are the comma and angle brackets. The comma is used to
separate items within a list. Angle brackets denote an argument; that is, either an address, pass count
value, or a V bus channel. Note that every command (or command line) must be terminated with a
carriage return (CR).

Control C (AC) is the user interrupt control character. If AC is entered during test execution, the
current test will be completed, further testing is terminated, and control is returned to the monitor
command mode. If AC is entered while a test is looping on an error, the loop will be suspended and
control returned to the monitor command mode. Any command may be aborted if a ACis entered in
that command line.

The following list describes the monitor commands. Note that although all commands, keywords,
qualifiers, and flags are spelled out, they can be abbreviated to the first two characters. The only
exceptions are the HALTD and HALTI flags, which must be typed HD and HI, respectively.
Diagnose Commands

DIAGNOSE or DIAG

Initializes the program control flags, and starts microdiagnostic
execution at test number one.
Valid qualifiers are:
J/TEST: <NUMBER> - Dispatch to the test number specified

(do not execute any prior tests) and loop on the test indefinitely.

/SECTION: <NUMBER?> - Dispatch to the section number
specified (do not execute any prior sections) and loop on the
section indefinitely.

/PASS: <NUMBER> - Execute the microdiagnostics the
specified number of passes before returning to the console. If
the number is -1, execute the microdiagnostics.

/CONTINUE - This switch is used with the /TEST or /SECT
switch to automatically continue after the specified test of section has been reached.

Diagnose Commands (Cont)
DIAGNOSE or DIAG

/TEST: <N> <M> - Dispatch to test <N>, execute tests
<N
> through <M> (inclusive), and return to command mode.
/SECT: <N> <M> - Dispatch to section <N>, execute sections <N> through <M> (inclusive), and return to command
mode.
NOTES
In the above variations of the /TEST and /SECTION qualifiers, the value of <N> must be less than
or equal to <M>. If <M> is less than <N>, testing will start at <N> and continue to the end.
/TEST and /SECT cannot be specified simultaneously.

Examples:

DIAG/TEST:2F

Dispatch to test number 2F and execute it indefinitely.

DIAG/SECT:B

Dispatch to section number B and execute it indefinitely.

DIAG/PASS:-1

Execute all of the microdiagnostics indefinitely.

DIAG/TEST:2F/CONT

Dispatch to test 2F and start execution of the remaining tests.

Continue Commands
CONTINUE or CONT

Continues microdiagnostic execution without changing the program control flags.

Set and Clear Commands
SET/CLEAR FLAG HD

Sets (or clears) the halt on error detection flag.

SET/CLEAR FLAG HI

Sets (or clears) the halt on error isolation flag.

SET/CLEAR FLAG

Sets (or clears) the loop on error flag.

LOOP

SET/CLEAR FLAG NER

Sets (or clears) the no error report flag.

SET/CLEAR FLAG

Sets (or clears) the bell on error flag.

BELL

SET/CLEAR FLAG
ERABT

Sets (or clears) the error abort flag.

Set and Clear Commands (Cont)
CLEAR FLAG LS

Clears the loop on special section flag. (Note that this flag cannot be set.)

CLEAR FLAGLT

Clears the loop on special test flag. (Note that this flag cannot
be set.)

SET /CLEAR FLAG ALL

Sets (or clears) all the previous flags.

SET/CLEAR SOMM

Sets (or clears) the stop on micromatch bit.

SET/CLEAR SOMM:
<ADDRESS>

Loads <ADDRESS> into the microbreak register, and sets (or

SET/CLR FPSYNC:
<ADDRESS>

Loads <ADDRESS> into the FPA microsync register.

SET STEP STATE

Sets the CPU clock to single time state.

SET STEP BUS

Sets the CPU clock to single bus cycle.

clears) the stop on micromatch bit.

Both the SET STEP STATE and SET STEP BUS commands
cause the monitor to enter step mode. Step mode types the current clock state or the UPC value, and waits for terminal input.
If a space is typed, the clock is triggered and the current UPC
value is typed out. If any other character is entered, step mode is
exited.
SET STEP
INSTRUCTION

Sets the hardware single instruction flag and returns to the monitor. When the hardcore tests are invoked, the current value of
the test PC (TPC) is typed. The monitor waits for terminal input. If a space is typed, the current pseudo-instruction is executed and the current value of the TPC is typed. If any other
character is typed, step mode is exited.

SET CLOCK FAST

Sets the CPU clock speed to the fast margin.

SET CLOCK SLOW

Sets the CPU clock speed to the slow margin.

SET CLOCK NORMAL

Sets the CPU clock speed to normal.

SET CLOCK EXTERNAL

Sets the CPU clock for an external oscillator.

Show Command

SHOW

Causes a display of the HALTD, HALTI, LOOP, NER, BELL,
ERABT, LS, and LT flags.

Loop Command

LOOP

Clears the HALTD and HALTI flags. Sets the LOOP and NER
flags, and executes a CONTINUE command.

B-3

Return Command

RETURN

Returns control to the console program.

Examine Commands

The following examine commands cause the current microinstruction to be executed before the examine is performed, if it
is the first examine since entering the monitor command mode.
Successive examines do not execute -any additional microinstructions. ID bus register contents T1-T8 are destroyed during the examines, except for the ID bus and V bus examines. All
of the following examines, except V bus, advance the clock to
CPTO before executing the command.

EXAMINE
ID:<ADDRESS>

Displays the contents of the ID bus register specified by <ADDRESS>.

EXAMINE
VBUS:<CHANNEL>

Displays the contents of the V bus channel specified by
<CHANNEL>. Bit 0 is at the right side of the display.

EXAMINE

Displays the contents of the RA scratchpad specified by
DRESS>.

RA:<ADDRESS>
EXAMINE

< AD-

RC:<ADDRESS
>

Displays the contents of the RC scratchpad specified by <ADDRESS>.

EXAMINE LA

Displays the contents of the LA latch.

EXAMINE LC

Displays the contents of the LC latch.

EXAMINE DR

Displays the contents of the D register.

EXAMINE QR

Displays the contents of the Q register.

EXAMINE SC

Displays the contents of the SC register.

EXAMINE FE

Displays the contents of the FE register.

EXAMINE VA

Displays the contents of the VA register.

EXAMINE PC

Displays the contents of the program counter register.

Deposit Commands

The deposit command is the same as the examine command,
except that the data to be deposited must be supplied by the
user.

DEPOSIT ID:<ADDRESS> <DATA
>
DEPOSIT RA:<ADDRESS> +DATA>
DEPOSIT RC:<ADDRESS> <DATA>

DEPOSIT LA:<DATA>
DEPOSIT LC:<DATA>

DEPOSIT DR:<DATA>
DEPOSIT QR:<DATA>
DEPOSIT SC:<DATA
>

DEPOSIT FE:<DATA>
DEPOSIT VA:<DATA>

DEPOSIT PA:<DATA
>

APPENDIX C

CONSOLE BOOT/TROUBLESHOOTING FLOW

If the console program does not start and run properly when the VAX-11/780 system is powered up,
and a problem in the console subsystem is suspected, proceed as follows.
Response

Action
Turn dc off
Turn ac off

Push

HALT/ENABLE

switch

down (halt)
Turn ac on

DC ON (LED on LSI-11 control panel)

Turn dc on

173000

@ (printed on terminal)
RUN (light flashes)

If the responses are incorrect, go to Figure C-1, Console DC ON Flowchart.
Examine location 173000
type 173000/

173000/000137

Examine location 037776
type 037776/

037776/ XXXXXX

If the response is not correct, go to Figure C-2, Examine 173000 Flowchart.
Push

HALT/ENABLE

switch

up (ENABLE)

Ensure that diskette ZZ-ESZAB
is installed properly in the floppy
disk drive.

Type 140200G

BOOT

This command executes the ROM resident quick check console subsystem diagnostics. Upon success-

ful completion of these tests, the ROM code boots the console program from the floppy disk. If the
boot fails, go to the 140200G Console Boot Failure Flowchart (Figure C-3). The program listing for
the ROM resident diagnostics (ESKAA.DOC) should be referenced when using this flowchart.

C-1

DC ON, RUN LIGHT FLASH,
AND/OR 173000 PRINTOUT DID NOT OCCUR
XXXXXX

@ WAS PRINTED
CPU JUMPER IS WRONG OR CPU IS BAD

("BDMR L
NO, GO TO POWER FLOW

PRINTOUT GARBLED, CHECK BDALO

BREF L

ASSERTED AND GO TO TERMINAL FLOW

Bglc\)%l; t

ONE OF THE FOLLOWING

IS DC ON LED ON?

SIGNALS

YES. WHAT WAS
PRINTED?

NOTHING
WAS PRINTED

YES. DID THE

IS ASSERTED

SISAS

:RPLY /

— BDIN
L
BSYNG L

BPOK H IS NOT ASSERTED

BDMG O L

RUN LIGHT FLASH?

|
BDAL 1L

GO TO TERMINAL FLOW

NO. CHECK POWER SUPPLY TO
BACKPLANE CABLE

NO. REMOVE M9400-YE, DOES
NO. IS THE

TERMINAL PRINT 173000 ON POWER UP?

NO. CHECK BDCOK H NOT

ASSERTED

RUN LIGHT ON?

NO, CPU IS BAD

YES, CABLING IS INCORRECT

YES, THE HALT SWITCH IS

YES, CIB IS BAD

NOT ASSERTING BHALT L
YES. WAS

YES. CPU IS BAD

YES, CABLING OR CIB IS BAD

NO. REMOVE M9400-YE,

CONFIGURATION AGAINST

PROMPT PRINTED?

NO. CHECK JUMPER

POWER UP, DID

KC780 PRINT SET

PRINTOUT OCCUR?

NO BDAL7 L, BDAL 15 L,
BINIT L OR BDMGO L

IS ASSERTED
TK-0378

Figure C-1
LOCATION 173000 OR

Console DC ON Flowchart

LOCATION 037776

DID NOT RESPOND CORRECTLY

—
e

173000/?

——

RESPONSE

I
T

I
|

GARBLED RESPONSE

THERE IS A BAUD RATE PROBLEM BETWEEN THE

TERMINAL AND THE DLV11 INTERFACE

THERE IS A PROBLEM IN THE DLV11, THE CABLE,

OR THE TERMINAL TRANSMITTING CIRCUIT (TERMINAL TO DLV11)

NO RESPONSE

men

—

|
|
|

OR THE CIB IS NOT WORKING

wmm

0377767

THE TOP OF MEMORY BANK 1

DOES NOT RESPOND

CHECK JUMPER CONFIGURATION AGAINST KC780
PRINT SET

aden

ame

amm

1
|

——

WHAT WAS RESPONSE? |

THE CABLES ARE NOT CORRECTLY MOUNTED.

[

INTERPRETATION

—

Figure C-2

Examine 173000 Flowchart

TK-0374

DEVICE DID NOT BOOT WHEN 140200 WAS TYPED

REPLACE FAILING

VERIFY THAT REFRESH

2 CONTAINS FAILING ADDRESS
R3 CONTAINS EXPECTED DATA

141262
@

“141236
@”

NOT WORKING,

REPLACE

VERIFY THAT FLOPPY
DOOR IS CLOSED

“FLOPPY NOT READY"

CPU MAY BE BAD)

IS WORKING CORRECTLY AT
EAILING LOCATION

FAILED
140332 _. “141076 THE CPU TEST
THE CPU :

70 @~

WORKING,

MEMORY. (NOTE

CHECK URATION

CONFIG

CLOSED, THE DRIVE IS BROKEN, RUN DZRXA AND DZRXB DIAGNOSTICS

NOT CLOSED,

CORRECT PROBLEM

YES, THE FIRST DISKETTE IS EITHER BAD OR THE WRONG ONE
TRY ANOTHER
“NO BOOT ON VOLUME" DISKETTE,

DOES IT
BOOT?

THE FLOPPY CAME READY,

WHAT WAS PRINTED?

RUN DZRXA AND DZRXB DIAGNOSTICS
|NO, THE DRIVE IS BROKEN,

BUT DID NOT READ

€O

“FLOPPY ERROR”

A BLOCK

NOTHING PRINTED

BAD CPU

HALT CPU,

NOTHING PRINTED

“000104

@”

“140216

WHAT WAS PRINTED

“000002

@”

“XXXXXX
@’

BAD CPU
OR BAD CIB,

SEE LISTINGS (ESKAA.DOC),
XXXXXX = CURRENT LOCATION + 2

THE LTC SWITCH IS ON,

OR BEVNT L IS NOT CLAMPED LOW BY THE LTC SWITCH

BHALT L IS STILL ASSERTED

OR BDAL 9L OR BDAL10 IS ASSERTED

“173000
@’

A DOUBLE BUS ERROR HAS OCCURRED, SET R6 TO
1000, TYPE 173000G, AND THEN REENTER THIS TROUBLESHOOTING PROCEDURE

“XXXXXX
@

BAD CPU
OR CIB

SEE LISTINGS (ESKAA.DOC), XXXXXX = CURRENT LOCATION + 2
TK-0375

Figure C-3

140200G Console Boot Failure Flowchart

Figure C-4 shows the console power troubleshooting flowchart. Figure C-5 shows the console terminal
troubleshooting flowchart.
CONSOLE DC POWER FAILURE
YES, ONE MODULE IS SHORTING DC, REPLACE

NO. CORRECT THE FAULT

MODULES UNTIL THE BAD ONE IS LOCATED

IS AC-PRESENT

AT POWER SUPPLY?

NO., CORRECT THE FAULT
YES. IS THE BOX WIRED

CORRECTLY FOR AC?
YES. REMOVE THE MODULES

FROM THE BOX IS DC ON?

YES., BAD POWER SUPPLY
NO, ARE VOLTAGES
CORRECT AT
BACKPLANE?

NO,

YES, DISCONNECT THE POWER

YES, BAD BACKPLANE

SUPPLY-TO- BACKPLANE
CABLES IS DC

PRESENT?

ARE CABLES CONNECTED FROM POWER
(A)

NO, BAD POWER SUPPLY

SUPPLY TO FRONT PANEL AND BACKPLANE?

NO. CORRECT THE FAULT
TK-0376

Figure C-4

CONSOLE TERMINAL

Console Power Troubleshooting Flowchart

FAILURE

NOT

REMOVE DLV11

AND ENSURE THAT

COMPATIBLE. CORRECT FAULT

BAUD RATE IS

COMPATIBLE WITH LA36

NO. REPAIR TERMINAL

COMPATIBLE,
WILL TERMINAL
WORK IN LOCAL?

YES. IS TERMINAL 20MA CURRENT LOOP?

NO, BAD TERMINAL

NO (EIA),

YES, WHILE PRESSING A KEY ON T HE TERMINAL,

WHILE CYCLING DC ON

OR CABLE

IS THERE ACTIVITY ON THE CABLE PIN m?

IS THERE ACTIVITY ON

YES. BAD TERMINAL,

THE DLV11 BERG PIN F?

FORMAT BUAD RATE

NO, BAD DLV11

@-— YES., WHILE CYCLING DC ON

NO. BAD DLV11 OR CABLE LOOP

THE WHITE WIRE?

YES. WHILE PRESSING A KEY ON

IS THERE ACTIVITY ON

THE TERMINAL, IS THERE

NO, REPAIR TERMINAL
OR CABLE LOOP

ACTIVITY ON THE GREEN WIRE?
YES. BAD BAUD RATE,
FORMAT TERMINAL
TK-0377

Figure C-5

Console Terminal Troubleshooting Flowchart

If use of the flowcharts fails to
help in location of a problem, the
RXDP package diagnostics can
be run (diskette ZJ-215-RY).

Program Name

Function

DVDVA
DVDVC
DVKAA

DLV-11E Test
DLV-11F Test
LSI-11 CPU Test

DZLAC

LLA36 Test

DVKAD
DVKAE
DVKAH
DZKMA

DZRXA
DZRXB

LSI-11 Traps and Interrupts
DLV-11 Test
System Exerciser
Memory Test

Floppy Disk Exerciser
Floppy Interface Tests

Figure C-6 shows the flow of events which develop on the LSI-11 boot sequence.

Note that if the LSI-11 program crashes while VMS is running, the operator may enter ODT and then
type in 141330G to reboot the console program without affecting VMS.

START

MEMORY
TEST

START

(200)

REVERSE

TERMINAL
ADDRESSES

:
CHECK FIRST

ADDRESS +

140,000

(204) L

BOOT
N|

1 (216)

ASSIGN

TERMINALS
ADDRESSES

DUAL

(1234)

ADDRESS

GOOD DATA R3

TEST

BAD DATA (R2)

WALKING

(1260)

011

GOOD DATA R3

110

TEST

DOUBLE

TEST 1

BUS ERROR

BAD DATA (R2)

TEST

(330)

CHECK BYTE

TEST 2

SINGLE OP
INST DEST

DO REST
OF MEMORY

CHECK SOURCE

|TEST 3

MODE DOUBLE

OP WORD

INST DEST MODE o | (436)
JMP INST

TEST 4

DEST MODE

TSTB & TST

TEST 5

DEST MODE
1,246

(552)

CHECK BYTE

TEST 6

DOUBLE OP

INST DEST

MODE 0

(600)

TK-0380

Figure C-6

LSI-11 Boot @173000 Flowchart (Sheet 1 of 2)

C-6

START

BOOT LsI

(REBOOT)

TEST 7

BUT NOT

VAX-11/780

DEST MODE # 0

(1330)

USE MEMORY

:
SET PWR-UP/

CRASH FLAG

WORD INST

{752)

ERROR

YES

500 & 502

TEST 8

BYTE DEST

MODE # O

(1046)

LOC 500

TEST 9

"B-1/0

READ

ERROR"”