Digital PDFs

AA-3057C-TC

May 1990

148 pages

Original

5.1MB

Document:	IAS Diagnostics Reference Manual 199005
Order Number:	AA-3057C-TC
Revision:	0
Pages:	148
Original Filename:	AA-3057C-TC_IAS_Diagnostics_Reference_Manual_199005.pdf

OCR Text

lAS Diagnostics
Reference Manual
Order Number: AA-30S7C-TC

This manual describes the operation of individual diagnostic tasks and their output.

Operating System and Version: lAS Version 3.4

May 1990
The information in this document is subject to change without notice and should not be construed as a
commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for
any errors that may appear in this document.
The software described in this document is furnished under a license and may be used or copied only in
accordance with the terms of such license.
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set
forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS
252.227-7013.
No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital
Equipment Corporation or its affiliated companies.
Copyright © 1990 by Digital Equipment Corporation
All Rights Reserved.
Printed in U.S.A.
The postpaid READER'S COMMENTS form on the last page of this document requests the user's critical
evaluation to assist in preparing future documentation.

The following are trademarks of Digital Equipment Corporation:
DDIF
DEC
DEC/CMS
DEC/MMS
DECnet
DECUS
DECwindows
DECwrite
DIBOL

lAS
MASSBUS
PDP
PDT
RSTS
RSX
ULTRIX
UNIBUS
VAX

VAXC
VAXcluster
VAXstation
VMS
VR150/160
VT

This document was prepared using VAX DOCUMENT, Version 1.2

CONTENTS

Page

0.1

MANUAL OBJECTIVES AND READER ASSUMPTIONS

0.2

STRUCTURE OF THE DOCUMENT

0.3

ASSOCIATED DOCUMENTS

CHAPTER

INTRODUCTION

1-1

CHAPTER

RSX-IID DIAGNOSTIC TASKS

2-1

PREFACE

DEVICES SUPPORTED BY DIAGNOSTICS
NAMING CONVENTIONS FOR DIAGNOSTICS
OPERATIONAL INFORMATION
2.3
Installing and Running CMD
2.3.1
Interactinq with CMD
2.3.2
Building the Diagnostic Program or
2.3.3
Data Reliability Test
Changing Handlers
2.3.4
Mounting the Volume and Installing
2.3.5
the Task
Running the Diagnostic Task
2.3.6
Specifying the Test Parameters
2.3.6.1
Specifying NEW PARAMETERS Switch
2.3.6.2
TERMINATING THE DIAGNOSTIC
2.4
CHAPTER

2.1

2-2

2.2

2-4
2-4

RK05S AND RK05D DIAGNOSTIC PROGRAMS

ADDRESS TEST (RK05S ONLY)
Part 1 of Address Test
Part 2 of Address Test
Part 3 of Address Test
Part 4 of Address Test
Part 5 of Address Test
Part 6 of Address Test
Part 7 of Address Test
DATA TEST
3.2
RANDOM TEST
3.3
FORMATTER TEST (RK05S ONLY)
3.4
OPERATIONAL INFORMATION
3.5
TEST PARAMETE~: Bi t Settings
3.5.1
Conversation Mode (RK95S Only)
3.5.2
Address Test Conversion Mode
3.5.2.1
Data Test Conversation Mode
3.5.2.2
ERROR MESSAGES
3.6

3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7

CHAPTER

4.1
4.1.1
4.1.2
4.1.3

RP03S, RP02S, RP02CS, RP03D, RP92D, AND
RP02CD DIAGNOSTIC PROGRAMS
ADDRESS TEST (RP03S, RP02S AND RP92CS ONLY)
Part 1 of Address Test
Part 2 of Address Test
Part 3 of Address Test

iii

2-5
2-5
2-8
2-10

2-11
2-12
2-17
2-17
2-18
3-1
3-1
3-1
3-2
3-2

3-2
3-2

3-2
3-3

3-3
3-3
3-4
3-4
3-4

3-6
3-6
3-6
3-7

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

CONTENTS
Part 4 of Address Test
Part 5 of Address Test
Part 6 of Address Test
DATA TEST
RANDOM TEST
FORMATTER (RP03S, RP02S, AND RP02CS ONLY)
OPERATIONAL INFORMATION
TEST PARAMETER Bit Settings
Conversation Mode (RP03X, RP02S, and
RP02CS Only)
Address Test Conversation Mode
4.5.2.1
Data Test Conversation Mode
4.5.2.2
4.6
ERROR MESSAGE FORMAT

4-4
4-7

RP04S AND RP04D DIAGNOSTIC PROGRAMS

5-1

4.1.4
4.1.5
4.1.6
4.2
4.3
4.4
4.5
4.5.1
4.5.2

CHAPTER

ADDRESS TEST (RP04S ONLY)
5.1
Part 1 of Address Test
5.1.1
Part 2 of Address Test
5.1.2
Part 3 of Address Test
5.1.3
Part 4 of Address Test
5.1.4
Part 5 of Address Test
5.1.5
Part 6 of Address Test
5.1.6
DATA TEST
5.2
RANDOM TEST
5.3
FORMATTER TEST (RP04S ONLY)
5.4
OPERATIONAL INFORMATION
5.5
TEST PARAMETER Bit Settings
5.5.1
Conversation Mode
5.5.2
Address Test Conversation Mode
5.5.2.1
Data Test Conversation Mode
5.5.2.2
ERROR MESSAGES
5.6
CHAPTER

CHAPTER

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

4-4

5-1
5-1
5-1
5-2
5-2
5-2
5-2
5-2
5-3
5-3
5-3
5-4
5-6
5-6
5-6
5-7

RS04S, RS03S, RS04D, AND RS03D DIAGNOSTIC
PROGRAMS

6-1

6.1
6.1.1
6.1.2
6.2
6.3
6.4
6.4.1
6.4.2
6.5

ADDRESS TEST (RS04S ONLY)
Part 1 of Address Test
Part 2 of Address Test
DATA TEST
RANDOM TEST
OPERATIONAL INFORMATION
TEST PARAMETERS Bit Settings
Conversation Mode (RS04S Only)
ERROR MESSAGE FORMATS

6-2
6-2
6-2
6-2
6-3
6-3
6-3
6-5
6-6

RS11S AND RS11D DIAGNOSTIC PROGRAMS

7-1

7.1
7.1.1
7.1.2
7.2
7.3

ADDRESS TEST (RS11S ONLY)
Part 1 of Address Test
Part 2 of Address Test
DATA TEST
RANDOM TEST
OPERATIONAL INFORMATION
Determining the Number of Drives to
Exercise
TEST PARAMETER Bit Settings
Conversation Mode (RS11S Only)
ERROR MESSAGES

7-1
7-1
7-2
7-2
7-3
7-3

7.4
7.4.1
7.4.2
7.4.3

7.5

7-3
7-3
7-4
7-6

CONTENTS
CHAPTER

TU56S AND TU56n DIAGNOSTIC PROGRAMS

8.1
ADDRESS TEST (TU56S ONLY)
8.1.1
Part 1 of Address Test
8.1.2
Part 2 of Address Test
8.1.3
Part 3 of Address Test
Part 4 of Address Test
8.1.4
START/STOP TEST (TU56S ONLY)
8.2
DATA TEST
8.3
OPERATIONAL INFORMATION
8.4
TEST PARAMETER Bit Settings
8.4.1
Conversation Mode
8.4.2
Address Test Conversation Mode
8.4.2.1
Data Test Conversation Mode
8.4.2.2
ERROR MESSAGES
8.5
CHAPTER

CHAPTER

8-1
8-1
8-1
8-2
8-2
8-2
8...;2
8-3
8-3
8-5
8-5
8-5
8-6

TU10S1 AND TU16S1 DIAGNOSTIC PROGRAMS

9-1

9.1
9.2
9.3
9.4
9.5
9.6
9.7
9.8
9.9
9.10

REWIND AND BACKSPACE TEST
WRITE AND READ RECORD TEST
END OF RECORD TEST
EXTENDED RECORD GAP TEST
END OF FILE TEST
SINGLE-RECORD POSITIONING TEST
MULTIPLE-FILE POSITIONING TEST
VARIABLB-LENGTb RECORD POSITIONING TEST
TEST PARAMETER BIT SETTINGS
ERROR MESSAGES

9-1
9-1
9-1
9-2
9-2
9-2
9-2
9-3
9-3
9-5

TU10S2, TU10D, TU16S2, AND TU16D DIAGNOSTIC
PROGRAMS

10-1

10.1
10.2
10.3

RECORD LENGTH TEST (TU10S2 AND TU16S2 ONLY)
LATERAL PARITY TEST (TU10S2 AND TU16S2)
LONGITUDINAL PARITY TEST (TU10S2 AND
TU16S2 ONLY)
10.4
CRe TEST (TU10S2 AND TU16S2 ONLY)
10.5
SKEW TEST (TU10S2 AND TU16S2 ONLY)
10.6
CROSSTALK TEST (TU10S2 AND TU16S2 ONLY)
10.7
TU16 BURST TEST (TU16 ONLY)
10.8
DATA RELIABILITY TEST (ALL PROGRAMS)
10.9
OPERATIONAL INFORMATION
10.9.1
TEST PARAMETER Bit Settings
10.9.2
Conversation Mode (TU10S2 and TU16S2 Only)
10.9.2.1 Compatibility Test
10.9.2.2 Write/Read Amplifier Slice Adjustment Test
10.10
ERROR MESSAGES
CHAPTER

8-1

10-1
10-1
10-2
10-2
10-2
10-2
10-2
10-2
10-3
10-3
10-5
10-5
10-6
10-6

TTYTS DIAGNOSTIC PROGRAM

11-1

11.1
11.1.1
11.1.2
11.2
11.2.1
11.2.2
11.3
11.4
11.5
11.6

CARRIAGE RETURN TEST
ASR33, ASR35, and LA30 Carriage Return Test
VT05 Carriage Return Test
SPACE TEST
ASR33, ASR35, AND LA30 Space Test
VT05 SpC'ce Test
TAB TEST
LINE FEED TEST
CHARACTER TEST
ASR33 WORST CASE PATTERN TEST

11-1
11-1
11-1
11-3'
11-3
11-3
11-3
11-4
11-4
11-4

CONTENTS

CHAPTER

11-4
11-5
11-5

11.7
11.8
11.9

ASR35 WORST CASE PATTERN TEST
USER-SELECTED PATTERN TEST
TEST PARAMETER BIT SETTINGS

RK06S AND RK06D USER MODE DIAGNOSTIC PROGRAMS 12-1

12.1
ADDRESS TEST (RK06S ONLY)
12.1.1
Cylinder Test 1
12el.2
Cylinder Test 2
12.1.3
Sector Addressing Test
12.1.4
Track/Head Addressing Test
12.1.5
Write/Read Cylinder Spiralling Test
12.1.6
Partial Sector write Test
12.2
DATA TEST
12.3
RANDOM TEST
12.4
FORMATTER (RK06S ONLY)
12.5
OPERATIONAL INFORMATION
12.5.1
TEST PARAMETER Bit Settings
12.5.2
Conversation Mode
12.5.2.1 Address Test Conversation Mode
12.5.2.2 Data Test Conversation Mode
12.6
ERROR MESSAGES

12-1
12-1
12-2
12-2
12-2
12-2
12-3
12-3
12-3
12-4
12-4
12-4
12-512-5
12-7
12-8
Index-1

INDEX

FIGURES
Figure

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

/H Printouts for CMD running on RSX-l1D
VT05 Carriage Return Test Display
(Partial Display)
ASR33, ASR35, and LA30 Space Test
VT05 Space Test
Tab Test Output

2-7
11-2
11-3
11-3
11-4

TABLES
Table

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

Devices Supported by Diagnostic Handlers
2-3
TKB Error Messages When Building A Diagnostic 2-9
Common TEST PARAMETER Bit Setting
2-13
Additional TEST PARAMETERS for Disks and
DEC tape
2-14
Additional TEST PARAMETERS for Magnetic
Tape (All Versions)
2-15
Additional TEST PARAMETERS for Terminals
2-16
RK05S and RK0SD TEST PARAMETER Bits
3-5
RK05S and RK05D Error Messages
3-9
RP03S and RP03D TEST PARAMETERS Bits
4-5
RP03S, RP02S, RP02CS, RP03D, RP02D, and
RP02CD Eror Messages
4-9
RP04S and RP04D TEST PARAMETERS Bits
5-5
RP04S and RP04D Error Messages
5-9
RS04S and RS04D TEST PARAMETERS Bits
6-4
RS04S and RS04D Error Messages
6-8
RSl1S and RSl1D TEST PARAMETERS Bits
7-4
RS11S and RSIID Error Messages
7-8
TU56S and TU56D TEST PARAMETER Bits
8-4
TU56S and TU56D Error Messages
8-8

CONTENTS
9-1
9-2
19-1
19-2
11-1
12-1
12-2

TU19S1 and TU16S1 TEST PARAMETER Bits
TU19S1 and TU16S1 Error Messages
TU19S2, TU16S2, TU190 and TU160
TEST PARAMETER Bits
TU19S2, TU16S2, TU190 and TU160
Error Messages
TTYS TEST PARAMETER Bits
RK06S and RK960 TEST PARAMETER Bits
RK96S and RK960 Error Messages

vii

9-4
9-9

10-4
19-13
11-6
12-6 .
12-11

PREFACE

0.1

MANUAL OBJECTIVES AND READER ASSUMPTIONS

This manual is·intended for either a system manaQer or a DIGITAL field
service engineer. It contains information that can be used to monitor
and determine the hardware reliability of a system.
The
reader of
this document should be familiar with the hardware as described in the
PDP-II Processor Handbook and the PDP-II Peripherals Handbook.

0.2

STRUCTURe OF THE DOCUMENT

This manual consists of two intrOductory chapters and a series of
detailed chapters that describe the operation of individual diagnostic
tasks and their output.
.
Chapter 1 introduces the conceots of diagnostic tasks.
Chapter 2 describes the
tasks.

function

and

operation

diagnostic

Chapters 3 through 12 detail individual diaqnostic tasks.
The ·first-time user of the diaanostic tasks should read Chapter 2,
"Diagnostic Tasks" before attemptina to run any of these tasks. When
running a diagnostic task, reference should be made to the chapter
concerning the device being tested.

0.3

ASSOCIATED DOCUMENTS

For a list of associated lAS or RSX-IID documents and a definition of
their readerships, refer to the Documentation Directory for the
ao~rooriate system.

CHAPTER 1
INTRODUCTION

lAS and RSX-IID provide the system manager with two complementary
methods of monitoring the hardware reliability of the system. The
first method, error 1099in9, allows the system manager to compile
error statistics for main and cache memory, disks, magnetic tape, and
DECtape while the system performs normal operations.
When it is
desirable, the system manager can obtain printed reports detailing or
summarizing hardware errors in memory and on these devices.
The
logging of errors is continual;
the report production can be
performed as desired. Error logging is described in the RSX-IlD
System Manager's Guide, or the lAS System Management Guide.
The second method of monitoring the hardware reliability is by running
diagnostic tasks to test a specific device. These tasks execute
simultaneously with other system functions and user tasks.
If the
error logging facility indicates that a device is malfunctioning, the
system manager may want to run the diagnostic tasks for that device to
further test it.
The data provided by the diagnostic tasks task can be forwarded to the
DIGITAL field service engineer to help determine the cause of the
error in advance of his arrival at the installation.
Both forms of system monitoring can be performed concurrently with
normal day-to-day system operations. Additionally, error logging and
diagnostic tasks can run simultaneously.
However, error 109ging
information is not accumulated for the device type on which the
diagnostics are running.
NOTES
1.

The user must be logged onto the system
using a privileged UIC to produce error
log reports or to run diagnostics.

Modules for building diagnostic handlers
are to be found on the Object Modules
distribution media.

1-1

CHAPTER 2
DIAGNOSTIC TASKS

lAS and RSX-IID provide diagnostic tasks that can be run by the user
to test the hardware reliability of disks, magnetic tape drives,
DECtape drives, and terminals.
If the user suspects a hardware
malfunction on one of these devices, the appropriate diagnostic task
can be installed and run. Results of the testing are printed on the
console terminal.
Because the diagnostics are tasks, they can execute concurrently with
other system and user tasks. Normal operations need not be disturbed.
Two types of diagnostics are included in the system:
diagnostic
programs
and
data
reliability tests.
Each device for which
diagnostics are available has an associated diagnostic program and a·
data reliability test.
The data reliability tests perform a subset of the functions of the
diagnostic programs.
They do not ~rovide the capability to select
which of the subtests are to be performed as can be done in the
diagnostic programs.
Additionally, they do not allow selection of
conversation mode.
Conversation mode permits dynamic interaction with the diagnostic
test.
Some diagnostics provide two types of conversation: data and
address. The user selects which type of conversation mode is desired
when starting the diagnostic. The buffer size for data transfers can
be modified, the area to be tested on a disk or tape can be specified,
and the test patterns for data tests can be selected. Normally,
conversation mode is used only by the DIGITAL field service engineer.
Conversation mode is not available with data reliability tests.
Unlike most system tasks which are distributed in task-image form, the
diagnostic programs and data reliability tests must be task built
(linked) before they can be installed and run.
Task building is
required to allow specification of variable information such as the
specific unit to be tested and the buffer size to be used.
To facilitate the building process, an interactive program named CMD
is provided.
It asks the questions required to create the input
needed by the task builder to produce a task image of the diagnostic.
CMD 1S used to produce build files for all diagnostic programs and
data reliability tests. Diagnostics may be built and ·the task images
left on a device and called in to run when needed. They need only be
rebuilt if the responses to CMD are to change.
Special device handlers are used in conjunction with the diagnostics.
These device handlers pass error information to the diagnostics. The
diagnostics intepret the information and print appropriate error
messages.
These handlers also allow normal user functions to be

2-1

DIAGNOSTIC TASKS
performed. The handlers distinguish among diagnostic requests and
user requests.
However, if error logging also is running, no errors
are logged for the diagnostic task or any task using a device of the
same type.

2.1

DEVICES SUPPORTED BY DIAGNOSTICS

Table 2-1 lists the devices for which diagnostic programs and data
reliabi1ity tests are provided and supplies the following additional
information:
1.

System device mnemonic, which is identical to the device
handler name for the device,

Diagnostic handler file name,

Diagnostic test name,

Data reliability test name.

Information in Table 2-1 is referred to throughout this chapter.
NOTE
Throughout this manual, all references
to the RK05 disk also include the RK03.
All references to the RS04 disk also
include the RS03 disk.

2-2

DIAGNOSTIC TASKS
Table 2-1
Devices Supported by Diagnostic Handlers

DEVICE

SYSTEM DEVICE MNEMONIC
(HANDLER NAME)

DIAGNOSTIC
HJ\NOLER NAME

RK03

OKO

RK03S

RK030

RK0S

DKD

RK0SS

RK0SD

RK06

DMD

RK06S

RKe6D

RP03

DPD

FP03S

RP03D

RP04

DBD

RP04S

RP040

RDBD

RS03S
RS04S

RS03D
RS040

DSO

FS03S
RS04S

RS030
RS04D

TUS6

DTD

TUS6S

TUS6D

TUle

TU100

TUleSl
positioning
test

TUl0D

RS03
RS04

{RDalso
(if RP"4
is
on same
RHll or RH70
controller)

DIAGNOSTIC
TEST NAME

.'DATA RELIABILITY
TEST NAME

TUl0S2
data
patterns
test
TU16

TU160

TU16Sl
positioning
test

TUl6D

TU16S2
data
patterns
test
RSll

OFD

RSIIS

RSIIO

TTYTS

terminal
RP02 1

OPO

RP02S

RP020

r.P02 2
RPR02 3

DPO

RP02CS

RP02CO

On RPll Controller.

On RPIIC or RPllE Controller.

On RPRll Controller.

2-3

DIAGNOSTIC TASKS
. 2.2

NAMING CONVENTIONS FOR DIAGNOSTICS

names of the diagnostic programs and the data reliability tests
are listed in the last two columns of Table 2-1.

Th~

The conventions described below are used in naming the diagnostics.
Diagnostics have 6-character names in the following format:
xxxxyz
Where:
xxxx

designates the type of unit that the diagnostic is to
test,
e.g., RP03, TU10, RS04, and TU16.

indicates whether the test is a diagnostic program or
a data reliability test by using one of the following
letters.
S

indicates a single unit diagnostic program.

indicates a data reliability test.

designates the number of a particular test for that
class of diagnostics. If these is only one test in the
class the number is omitted. For example, RP03S2 the
second diagnostic program in the RP03S class.

2.3

OPERATIONAL INFORMATION

The following is a summary of the operations that must be performed to
build and run the diagnostic task. These are fully described in the
following sections. If an appropriate task image already exists,
steps 4 onwards only need be perfo~med.
1.

Install and run CMD,

Respond to the questions printed by CMD,

Build the desired diagnostic program or data reliability
test,

Ensure that no tasks are performing I/O operations using
that device and dismount any volumes currently mounted
on it,

Unload (stop) and remove the handler normally used for
the device to be tested after determining that no one is
using it.

Install and load (run) the diagnostic handler to be used
in conjunction with the diagnostic task,

Mount a scratch volume on the device to
install the diagnostic task,

tested

and

Run the diagnostic,

When finished, terminate the diagnostic and change

back

2-4

DIAGNOSTIC TASKS
to the normal system handlers.

2.3.1

Installing and Running CMD

CMD is stored under UFO [11,1].
Press CTRL/C to obtain MCR on
RSX-IID.
On lAS, LOGIN with a system management username (i.e.
having UIC of (1,1]). Type the following commands to install and run
CMD.
All lines are terminated with RETURN unless otherwise noted in
the text.
RSX-IID

lAS

MCR>INS (ll,l]CMD

PDS> RUN [ll,l]CMD

MCR>CMD

2.3.2

Interacting with CMD

CMD prints the following series of questions on the console.
Respond
to each question after it is printed. The responses to the questions
are used as input to the task builder.
SHORT DIALOGUE?

(Y OR N)

Type Y to indicate that the short dialogue is desired.
dialogue is for users familiar with the operation of CMD.
shorter questions with no explanations on the console.

The short
It produces

Type N to indicate that the full CHD dialogue, as described below,
desired.

NOTE
Users unfamiliar with CMD are advised to
use the full dialogue, i.e., to type N.
TYPE A "/H" IF YOU DO NOT UNDERSTAND THE QUESTION
When any input is requrested in the ensuing CMD dialogue,
will provide a further description of the input required.

typing

Figure 2-1 illustrates the information printed on the console when
is typed in response to the questions.

TYPE OUTPUT/INPUT FILE SPECIFICATION
Because the diagnostic libraries (DIAGU.OLB, DIAGR.OLB, and DrAGD.OLB)
and the diagnostic tasks may not be on the (user's) system disk, CMO
allows the specification of the UFOs where the diagnostic task is to
be stored and/or the diagnostic libraries are to be found.
Two file specifications may be supplied.
The output specification
determines the device and UFO unde!r which the diagnostic task is to be
stored. If the device and UFO are not specified, the system device
and the user's UIC are used.

2-5

DIAGNOSTIC TASKS
The input specification indicates where the diagnostic libraries are
located.
If the input specification is omitted, UFO [1,27] of the
system device is used.
The specifications have the following format.
outdev: [ufd]-indev[ufd]
Filenames should not be specified.
SPECIFY DRIVE AND UNIT NO.
Type the 2-character drive type followed by the unit number. Refer to
the column headed "System Device Mnemonic" in Table 2-1 for the drive
type.
drive and unit number typed in response to this question indicate
the physical unit to be tested. It also is used as the name of the
diagnostic once it has been built: i.e., it is the name used to
install the diagnostic.
~he

For example, if the RKBS diagnostic is to run
following.

unit

type

the

DK2
To test unit 1 of an RS03, type the following.
RSI

CURRENT DATA BUFFER SIZE IS 1000 OCTAL WORDS
DO YOU WISH TO EXPAND IT?

(Y OR N)

The buffer size specified at this point determines the size of the
data transfers used in the diagnostic programs and reliability test.
Refer to individual diagnostic program chapters to determine which
tests are affected.
Type Y to indicate that the buffer is to be expanded.
Type N to indicate that a buffer size of 1000 (octal) words is
used. If N is the response, the next question is not printed.

2-6

DIAGNOSTIC TASKS
PDS> RUN [ll,l,]CMD
16:14:09
SHORT DIALOGUE?(Y OR N)
N

TYPE A "/H" IF YOU DO NOT UNDERSTAND ANY OF THE FOLLOWING OUESTIONS
TYPE OUTPUT/INPUT FILE SPECIFICATION
/H
TWO FILE SPECIFICATIONS MAY BE INPUT. THE OUTPUT SPEC DETERMINES
ON WHICH DEVICE AND UNDER WHAT UIC THE DIAGNOSTIC TASK WILL BE
STORED. IF NOT SPECIFIED, THE DEVICE WILL DEFAULT TO THE SYSTEM DEVICE
AND THE UIC WILL DEFAULT TO THE USER'S UIC. THe INPUT SPECIFICATION
DETEPMINES WHERE THE DIAGNOSTIC LIBRARIES ARE TO BE FOUND.
IF NOT SPECIFIED, THE DEVICE DEFAULTS TO THE SYSTEM DEVICE
AND THE UIC WILL DEFAULT TO [1,27]. 'rHE FILE SPECIFICATION
IS AS FOLLOWS:
OUTDEV: [XXX,XXX]=INDEV:[XXX,XXX]
TYPE CARRIAGE RETURN IF DEFAULTS ARE REQUIRED
TYPE OUTPUT/INPUT ~ILE SPECIFICATION
SPECIFY DRIVE TYPE AND UNIT NO.
/H
RESPOND WITH THREE CHAP-ACTERS. THE FIRST TwO CHARACTERS
EQUAL THE SYSTEM MNEMONIC FOR THE DEVICE TYPE. THE MNEMONICS ARE:
DP=RP02/03, DK=RK03/05, OF=RF11, DM=RK06, DB=RP04, OT=DECTAPE,
DS=RS03/04, MT=TU10/TS03, MM=TU16
THE 'rHIRO CHARACTER EQUALS THE UNIT NU:'1BER.
SPECIFY DRIVE TYPE AND UNIT NO.
DK0
CURRENT DATA BUFFER SIZE IS 1000 OCTAL WORes
CO YOU tiISH TO EXPAND IT? (Y OR N)
/H
THE TASK IS PROVIDED WITH A DATA BUFfER OF 1~00 (OCTALH'10RDS
THIS BUFPER MAY BE EXTENDED TO A MAXIMUM OF 40000 (OCTAL) WORDS OR
16K DECIMAL. A LARGER BUFFER RESULTS IN MORE DATA BEING
'rRANSFERRED ON EACH OPEFATION. THE SIZE OF THE BUFFER
WILL DEPEND ON THE AMOUNT OF CORE AND USER REOUIREMENTS.
DO YOU- WISH TO EXPAND IT? (Y OR N)
Y

WHAT IS THE TOTAL BUFFER SIZE DESIRED IN OCTAL ylORDS?
/H
l'HE TASJ( IS PROVIDED WITH A DATA BUF~'ER OF u~~e (OCTAL) WORDS
THIS BUFPER MAY BE EXTENDED TO A MAXIMUM OF 400~0(OCTAL) WORDS OR
16K DECIMAL. A LARGER BUFFER RESULTS IN MORE OA1A BEING
TRANSFERRED ON EACH OPERATION. THE SIZE OF THE eUFFER
WILL DEPEND ON THE AMOUNT OF CORE AND USER REQUIPEMENTS.
WHAT IS THE TOTAL BUFFER SIZE DESIRED IN OCTAL WORDS?
1000
WHICH DIAGNOSTIC DO YOU WISH 10 RUN?
/H
INPUT THE NAME OF THE DIAGNOSTIC TASK TO BE EXECUTED
WHICH DIAGNOSTIC DO YOU WISH TO RUN?
RK05S
THE FOLLOWING IS A SUMMARY OF COMMANDS NECESSARY TO
GET THE DIAGNOSTIC TASK RUNNING. IF ANY ERRORS
ARE ENCOUNTERED, REFER TO THE DIAGNOSTIC CONTROL CARD.
A) P~S) @OIAG
B) INITIATE THE APPROPRIATE DIAGNOSTIC HANDLER FROM SCI
C) POS > $~10U/FOR DK0: VOLUME - I 0
D) RUN DKQl
COMMAND FILE HAS BEEN GENERATED
16:16:14 SIZE: 4K CPU: Ql.20
Figure 2-1

/H Printouts for CMD running on lAS

2--7

DIAGNOSTIC TASKS
WHAT IS THE TOTAL BUFFER SIZE DESIRED IN OCTAL WORDS?
Enter the desired buffer size in octal words. The minimum buffer size
is 1000 words (octal) and the maximum buffer size is 40,000 words
(octal). The response must be specified in octal.
WHICH DIAGNOSTIC DO YOU WISH TO RUN?
Refer to Table 2-1 for the name of the diagnostic program or data
reliability test for the specific device. Enter the name at this
point.
For example, RP04S is the name of the diagnostic program for the RP04.
TU10D is the data reliability test for the TU10.
At this point, CMD prints a summary of the commands that must be typed
by the user before the diagnostic can execute. Provided that a full
dialogue has been requested, CMD prints a summary of what must be done
to run the diagnostic, then exits.

2.3.3

Building the Diagnostic Program or Data Reliability Test

Once CMD terminates, the diagnostic program or data
can be task built.

reliability

test

For RSX-IID DIAG.CMD is an indirect command file to task builder and
for lAS DIAG.CMD is an indirect command file to PDS containing the
appropriate LINK statement. It was created by CMD and stored in the
users UFD on the default system device:
RSX-IID

lAS

MCR)TKB
TKB>@DIAG

PDS)@DIAG

The errors listed in Table 2-2 may occur while the diagnostic program
or data reliability test is being built. If no errors occur, the task
is ready to be installed. Proceed to the next numbered section.

2-8

DIAGNOSTIC TASKS
Table 2-2
TKB Error Messages When Building a Diagnostic
ERROR MESSAGE

MEANING

CORRECTIVE ACTION

The indirect command
file does not exist.
Either the command
file is not in the
default UFD
where
the
task
builder
expects it, or there
was not enough space
to place the file on
the disk.

If lack of space is "the
problem,
delete
files
from the default UFD and
rerun CMD.

TKB FATAL #24

No
disk area
is
available. Normally,
the diagnostic task
is placed in
the
user's UFD on the
system device.

Delete files using PIP
(for RSX) or DELETE (for
lAS) free additional
space in the user's UFD
and rerun the build.

TKB FATAL #28

Cannot
find
the
diagnostic
program
to be task built.
Probably the diagnostic
name
was
mistyped.

Rerun CMD. See Section
2.3.1.

TKB FATAL

DIAGNOSTIC TASKS
2.3.4

Changing Handlers

The next step is to ensure that no tasks are performing I/O operations
using any device of the type being tested and dismount any volumes
currently mounted on those devices. Then terminate the normal device
handler and load the diagnostic handler.
For RSX-llD type the following commands to MCR to
step, for lAS type the following commands to SCI:

this

lAS

RSX-IID
MCR>U~L

accomplish

SCI> STOP/HANDLER dd where dd is the name of the
handler
to
be
replaced.
Refer to the "System Device
Mnemonic" column of Table 2-1
to obtain the
appropriate
handler name.

SCI> REMOVE dd ••••

MCR>REM dd ••••

where do is the handler name
specified
in the previous
command. For example:
OK ••••

MCR>INS [11,27JdoO

MT ••••

DB ••••

SCI> INSTALL [11,27]ddD
where ddD is the diagnostic
handler task filename. Refer
to the "Diagnostic Handler
Name" column of Table 2-1 for
the
associated
diagnostic
handler names.
For example:
OKD or DBD

MCR> LOA dd

SCI>RUN/HANDLER dd

where dd is the handler name.
Refer to the "System Device
Mnemonic" column of Table 2-1
for the name to be used when
loading
the
diagnostic
handler.
For

exam~le:

OK or DB
At this point, the diagnostic handlers are ready to interact with the
diagnostic tasks and other user tasks performing I/O on that device
type.
NOTE
Extreme caution must be exercised when
attempting to change the handlers for
the system device. The system must be
totally inactive when this is done. It

2-10

DIAGNOSTIC TASKS
is advisable to change system
disk
handlers immediately after loading the
system. The following is an example of
the
sequence
to
be followed when
changing the handlers for an RK system
based disk.
MCR>INS [ll,27]DKD/TASK-xxx

xxx can be any
name

user-assigned

task

.MCR>FIX xxx
MCR>RUN xxx 20S
MCR>UNL OK

Depress ALTMODE. This command must
be typed within 20 seconds of the
RETURN key that terminates the RUN
command.
DO NOT TOUCH THE CONSOLE FOR THE NEXT 20
SECONDS. This inteI,valgives the system
time to unload the nondiagnostic handler
and start the diagnostic handler.

2.3.5

Mounting the Volume and Installing the Task

Type the following commands to mou~lt a scratch volume that
placed in the unit and to install the diagnostic task.
RSX-llD
MCR>MOU dvn:/CHA-[FOR,ATCH]

has

been

lAS
PDS> MOUNT/FOR dvn:volume-id
dvn is the device and unit
number
to
be
tested.
Volume-id is the volume label
of the scratch volume.

MCR)INS dvn

MCR>RUN dvn

dvn is the name
of
the
diagnostic program or data
reliability test created via
DIAG.CMD in step 2.3.3 above.
It also is identical to the
device and unit information
specified in theMOU command.
PDS>RUN dvn

of
the
dvn is the name
diagnostic program or data
reliability test task to be
executed.

NOTE
The volume must be physically online and
write enabled.
At this point, the diagnostic task is running.

2--11

DIAGNOSTIC TASKS
2.3.6

Running the Diagnostic Task

After the command to run the diagnostic program or data reliability
test is issued, the program or test responds by printing the following
on the console.
xx DIAGNOSTIC

xx indicates the device to be tested

WARNING ALL DATA ON DEVICE dvn WILL BE DESTROYED
TYPE Y <CR) TO CONTINUE
PRESS RETURN to continue with the diagnostic.
Any other response
causes the diagnostic to be aborted.
If RETURN is pressed, the
diagnostic types the following request for test parameters.
TEST PARAMETERS=
Test parameters are bits that can be set to specify operational
variables for the diagnostic. Bits 9 through 15 have the same meaning
for all diagnostic programs and data reliability tests. The remaining
bits have different meanings for different diagnostics or are not
used. Table 2-3 lists the bits that have a common meaning for all
diagnostics.
Tables 2-4, 2-5, and 2-6 list bits that are diagnostic
specific.

2-12

DIAGNOSTIC TASKS
Table 2-3
Common TEST PARAMETER Bit Setting
BI'l1

SETTING

MEANING

Stall on error. The task waits for up to· 30
minutes before exiting.
The stall can be
aborted by toggling the
console
switch
defined at task startup in response to the
question WHICH CONSOLE SWITCH APPLIES FOR
OPERATOR INTERVENTION.

Loop on error. The task loops on the failing
instruction
sequence.
The loop can be
aborted
by
only
specifying
new
test
parameters with bit 14 equal to e.

Inhibit printouts except for forced printing.

Ring bell on error. The console bell rings
every time an error is detected in a test
sequence.

Run continuously. The program prints the end
of pass number at completion and repeats the
specified testing sequence.

Enter conversation mode (not applicable for
data reliability tests, TUleSl, and TU16Sl).

. Restart the program. The program aborts the
present sequence and restarts at the newly
selected test.

2-13

DIAGNOSTIC TASKS
Table 2-4
Additional TEST PARAMETERS for Disks and DECtape
BIT

SETTING

MEANING

Print only the first data compare error found
within a specified data transfer.

Print up to 3 data compare
specified data transfer.

Inhibit seek operations between successive
reads during the random test.
This bit
applies only to RK05, RPS3, and RP04 tests (S
and D versions).

Run the formatter (RK05S,
only) •

Run the random test (S versions only).

Run the data test (S versions only).

Run the address test (S versions only).

2-14

errors

RP03S,

within

and

RP04S

DIAGNOSTIC TASKS
Table 2-5
Additional TEST PARAMETERS for Magnetic Tape (All Versions)
BIT

SETTING

Perform an infinite number
data error recovery.

Perform a maximum
error recovery.

MEANING

retries

for
data

for

This bit applies only to the TU16 tests.

6
1

Perform data reliability or conversation mode
for 9-track transports at 800 bpi NRZ.

Perform data reliability or conversation mode
for 9-track transports of 1600 bpi PEe

Print only the first data compare
each data transfer.

error

for

Print up to 3 data compare
transfer.

per

data

Print all errors during error recovery.

Print only the first error during error
recovery.
At completion of error recovery,
print the error recovery type retry number.

Perform the read portion of write/read amp
slice adjustment.
(TUleS2 and TUl6S2 only).

Perform the data reliability test (TU10S2 and
TU16S2 only).

Perform the pattern test (TU10S2
only).

2-15

errors

and

TU16S2

DIAGNOSTIC TASKS
Table 2-6
Additional TEST PARAMETERS for TerminalS
MEANING

BIT

SETTING

LA30

VT95

ASR35

ASR33

Run all tests

2,1,9

000

Carriage return test

991

Space test

910

Tab test

911

Line feed test

139

Character test

191

ASR33 worst case test

119

ASR35 worst case test

III

User-selected pattern test

2-16

DIAGNOSTIC TASKS
2.3.6.1 Specifying the Test Parameters - In order to enter the test
parameters in response to the TEST PARAMETERS- question, the 16 test
parameter bits must be converted into 6 octal digits. For example, if
bits 11, 5, and 1 are set to 1 and all other bits are zero, the
following conversion is performed.

Bits

Value

Results

Following the example above, the number 4042 is entered in response to
TEST PARAMETERS-. Leading zeros can be omitted.
Any combination of bits can be set.
If more than one test is
selected, ~he test that has the lowest bit position is run first. For
example, if bits 0 and 1 are both set for the RK05s diagnostic, the
address test runs before the data test; refer to Table 2-4. The only
exception is the formatter; when it is selected, no other test is
run. When the formatter finishes., the diagnostic exits.

2.3.6.2 Specifying NEW PARAMETERS Switch - After the test parameters
are entered, the program prints the following question on the console •
. WHICH CONSOLE SWITCH APPLIES FOR OPERATOR INTERVENTION?
The switch specified in response t:o this is~used while the diagnostics
are
running to specify new test parameters and to abort the
stall-on-error sequence. When the switch is toggled, the program
reprints the TEST PARAMETERS- request.
NOTE
If the test currently running is to be
aborted to allow a new test to run, bit
9 also must be set in the new parameter
word.
If it is not set, the test
currently
running
com~letes
before
execution of the next test starts.
To specify the switch number, enter the octal value that results on
the console when that switch is set and all others are cleared. For
example, octal 1 indicates switch 0, octal 2 represents switch 1,
octal 4 represents switch 2, octal 10 represents switch 3, and octal
20 indicates switch 4.
Once the switch is specified, the diagnostic or data reliability
enters its testing routines.

2-17

test

DIAGNOSTIC TASKS
2.4

TERMINATING THE DIAGNOSTIC

Any of the following methods can be used
program or data reliability test.
1.

terminate

diagnostic

Press CTRL/C and type the following command.
lAS

RSX-IID

PDS)ABORT

MCR)ABO dvn

dvn

where
dvn
is
diagnostic
task
e.g., DKl, RP2.

the
name,

Lift the switch specified in response to the guestion
WHICH CONSOLE SWITCH APPLIES FOR OPERATOR INTERVENTION?
In response to the question TEST PARAMETERS=, press CTRL/Z.

Press CTRL/Z in response
diagnostic.

any

question

printed

the

Once the diagnostic is terminated, the task should be removed.
The
diagnostic handler should then be removed and the normal handler
should be loaded. Use the following series of instructions.
RSX-IID

lAS

MCR)REM dvn

Remove
the
diagnostic
task (RSX-IID only) where
dvn is the
diagnostic
task name.
For example:
DKI RP2

MCR)OMO dvn

PDS) DISMOUNT dvn:volume-id

l.fCR>UNL dd

SCI)STOP/HANDLER dd

where dd is the name of
the diagnostic handler to
be replaced.
Refer to
the
- "System
Device
Mnemonic" column of Table
2-1 to determine the name
of the diaqnostic handler
to unload.-

MCR)REN dd ••••

SCI) REMOVE dd ••••

where dd is the handler
name
specified in the
previous command.
For
exaID'91 e :
OK ••••

OM ••••

DT •••

MCR)INS [ll,l]dd PDS) INSTALL [ll,l]dd

where dd is the handler
task filename. Refer to
the
"System
Device
Mnemonic" column of Table
2-1 for the appropriate
handler name.

MCR)LOA dd

where dd is the handler
name.
Refer
to
the
"System Device Mnemonic"

PDS) RUN/HANDLER dd

2-18

DIAGNOSTIC TASKS
column of Table 2-1 for
the appropriate handler
name.
NOTE
Extreme caution must be exercised when
attempting to change the handlers for
the system device. The system must be
totally inactive when this is done. It
is advisable to change system
disk
handlers immediately after loading the
system. The following is an example of
the
sequence
to
be followed when
changing" the
handlers
for
an
RK
system-based disk.
MCR>INS (ll,lJDK
MCR>FIX OK •••.,
MCR>RUN OK •••• 205
MCR>UNL xxx

Depress
ALTMODE.
xxx
is
the user
assigned name of the
diagnostic handler.
This command must be
typed
within
20
seconds
of
the
RETURN
key
that
terminates the RUN
command.

DO NOT TOUCH THE CONSOLE FOR THE NEXT 20
SECONDS. This intElrval gives the system
time-to unload the diagnostic handler
and start the nondj.agnostic handler.

2-19

CHAPTER 3
RKeSS AND RKeSD DIAGNOSTIC PROGRAMS

The RK0SS diagnostic program and the RKeSD data reliability proram are
the two hardware tests for the RK05 and RKA3 disks. The RK050 data
reliability test is a su~~et of the RK0SS diagnostic program.
The RK05S diagnostic program provides four disk tests:
1.

Address test,

Data test,

Random test,

Formatter.

The RK050 data reliability test provides two disk tests:
1.

Data test,

Random test.
NOTE
Throughout this manual, all references
to the RK05 disk also include the RK03.

3.1

ADDRESS TEST (RK0SS ONLY)

The address test consists of seven parts.
Additionally, another
testing routine is run in conjunction with the address test for the
RK05S. After a read header command is issued, this routine verifies
the content of the data buffer with the cylinder address. If the data
received is incorrect, the heads did not position correctly.
Error
number 100 is issued when the heads do not position correctly. Error
numbers and meanings are detailed in Table 3-2.

3.1.1

Part 1 of Address Test

Part 1 of the address test issues lcead header commands to allow the
program to verify the true position of the heads without causing a
header verify error in the hardwarf~. The seek commands in this test
are implied seeks that result from the read header command.

3·-1

RK05S AND RK~5D DIAGNOSTIC PROGRAMS
In part 1, the program seeks from cylinder e to cylinder n and back to
o again. The value of n starts at 1 and is increased to 199. After
each seek, the program checks for errors and reads the header on that
cylinder to determine whether the head is positioned correctly.

3.1.2

Part 2 of Address Test

Part 2 of the address test issues read header commands to allow the
program to verify the true position of the heads without causing a
header verify error in the hardware. The seek commands in this test
are implied seeks that result from the read header command.
This part differs from part 1 in that a seek command is issued from
cylinder e through cylinder 199.
The first cylinder number is
increased by 1 and the second is decreased by 1. Then the test seeks
to cylinder 1 and back to 196. This process is repeated until the
number being decreased goes back to zero.

3.1.3

Part 3 of Address Test

Part 3 of the address test verifies that each sector from 0 through 11
is uniquely addressable.
Each sector on track 0 of cylinder e is
written with its address. Then each sector is read and the data is
verified. Any errors are reported to the operator.

3.1.4

Part 4 of Address Test

Part 4 of the address test ensures that each track on cylinder 0 is
uniquely addressable.
Sector ~ on each track is written with the
track address. Then the data is read and verified.
Any errors are
repo'rted to the operator.

3.1.5

Part 5 of Address Test

Part 5 of the address test ensure that each cylinder is uniquely
addressable.
Sector 0 of each cylinder is written with the cylinder
address. Then each cylinder is read and the data is verified.
Any
errors are reported to the operator.

3.1.6

Part 6 of Address Test

Part 6 of the address test verifies that a transfer initiated on
sector 11 of track 0 crosses over to sector 0 of track 1. 512 words
of data containing a pattern of 177777 are written on the disk
starting at sector 11 of track 0. Two words are read from sector 0 of
track 1 and checked to ensure that they contain 177777.

3-2

RK05S AND RK05D DIAGNOSTIC PROGRAMS
3.1.7

Part 7 of Address Test

Part 7 of the address test verifies that the RK is able to cross
cylinders when a 512-word transfer is initiated on sector 11 of track
1 of any cylinder. The data pattE~rn written is 177777. Sector 0 of
cylinders 1 through 199 are read to verify that the data transferred
did cross cylinder boundaries.

3.2

DATA TEST

During execution of the data test, write and read operations are
performed on the drive. The delta is written on the entire pack and
then read back. The data is verified and any errors are reported.
If an error is detected during thE! read operation, four retries are
attempted, and then the head is homed. Four more attempts are made to
recover the data.
The entire surface is tested with the following six patterns:
1.

Zeroes,

Ones (177777),

Checkerboard (alternating lis and 0's)

Floating ones,

Random data,

Count pattern (sequential binary, full-word, up
the buffer).

The size of the transfer is determined by
during the execution of CMD.

3.3

the

buffer

to
size

size

selected

RANDOM TEST

•

Prior to each read operation, the data buffer is cleared.
~hen,
the
random data is read and verified. This sequence is repeated 1000
(octal) times. The read operation is repeated eight times with
intervening seeks to detect any read reduction problems. If an error
is detected, the read number is typed to show which read was beinq
performed when the error occurred.. If the error is unrecoverable, the
read operation is terminated. If an error is detected during the read
operation, four attempts are made to read the data. If the data still
cannot be read, the heads are homed and four more attempts are made to
read the data.

3-3

RK05S AND RK050 DIAGNOSTIC PROGRAMS
If the heads have a tendency to vibrate, this condition should
as parity errors.

3.4

appear

FORMATTER TEST (RK05S ONLY)

The formatter test formats the. entire RK pack and then verifies it.
The sectors are formatted one at a time. Any errors are reported to
the operator. After formatting, the entire pack is verified 12
sectors at a time to ensure that the headers were written correctly.

3.5

OPERATIONAL INFORMATION

The operational information for the RK05S and FK0s0 tests consists of
TEST PARAMETER bit settings and conversation mode use. Conversation
mode can be used only for RK0sS.

3.5.1

TEST PARAMETER Bit Settings

In response to the question TEST PARAMETERS, certain bits can be set.
Table 3-1 lists the switches and provides their meanings. Bits 10, 3,
2, 1, and 0 apply to the RKesS only.

3-4

RK0SS AND RK0SD DIAGNOSTIC PROGRAMS
TablE! 3-1
RK0SS and RK0SD TEST PARAMETER Bits
BIT

SETTING

MEANING

Stall on error. The task waits up to ·30
minutes before exiting.
The stall can be
aborted by toggling the
console
switch
defined at task startup in response to the
question ~iHICH CONSOLE SWITCH APPLIES FOR
OPERATOR INTERVENTION.

Loop on error. The task 1000s on the failing
instruction seauence. The loop is abortab1e
only by specifying new test parameters with
bit 14 eqlJlal to zero.

Inhibit printouts except for forced printinq.

Ring bell on error. The console bell rings
every time an error is detected in a test
sequence.

Run continuously. The program prints the end
of pass number at completion and then repeats
the testing sequence.

Enter conversation mode. See Section 3.5.2
for a description of conversation mode (RI<0SS
only).

Restart the program. The program aborts the
present test seau~nce and restarts at the
riewly selected test.

Print only the first data compare error found
within a specified data transfer.

Print up to 3 data compare
specified data transfer.

Inhibit seek operation between
reads during the random test.

Formatter (RK0SS only).

Random test (RK05S only).

Data test (RK0SS only).

Data test (RK0SS only) •

Address test (RK05S only).

errors

within

successive

RK05S AND RK05D DIAGNOSTIC PROGRAMS
3.5.2

Conversation Mode (RK05S only)

When conversation mode is reauested by setting bit 10 in response
TEST PARAMETERS, a series of auestions is printed on the console.

Two versions of conversation mode are prov.ided with the RK05S
diagnostic program.
One specifies information for the address test
and the other specifies information for the data test.

3.5.2.1 Address Test Conversation Mode - Conversation mode for the
address test allows the operator to specify two cylinder addresses in
octal. The program then issues seek commands between the specified
cylinders. Any errors encountered are reported to the operator. Once
started, this program loops until it is aborted by the operator.
The program reauests the two cylinder addresses as follows.
"A" CYLINDER?
Enter a valid cylinder address in octal.
"8" CYLINDER?

Enter a valid cylinder address in octal.

3.5.2.2 Data Test Conversation Mode - In conversation mode for the
data test, the operator can specify the data transfer size, the disk
surface address, the pattern desired, and the function to
be
performed.
The following questions are asked.
. WORD COUNT 2 TO x
Enter an octal value to indicate the data buffer size for the data
test.
The maximum value that x can attain is the number specified
during execution of CMD.
00

YOU WISH TO SPECIFY THE DISK ADDR?

(Y OR N) •

Type Y to indicate that a particulat surface address is to be
specified for testing: otherwise, type N. If N is typed, the entire
surface is read and/or written and the next question .asked is PATTEFN
NO.?
C¥LINDER?
Type the desired cylinder in octal.
TRACK

3-6

RKass AND RK0SD DIAGNOSTIC PROGRAMS
Type the desired track number in octal.
SECTOR
Type the desired sector number in octal.
PATTERN NO.?
Select one of the diagnostic program's patterns or enter the desired
pattern. To select one of the prestored patterns type the number that
precedes the desired pattern in the following list.

o - zeros
1 • ones (177777)
2 • checkerboard
3 - floating ones
4 - random data
5 - count pattern (full word, binary, sequential
for size of buffer)
6 • run all patterns
If a user-supplied pattern is to
characters and press the RETURN key.
WRITE?

specified,

enter

the

octal

(Y OR N)

Type Y to perform all write operations
inhibit write operations.
READ?

test

type

(Y OR N)

Type Y to perform all read operations in·the test or tyee N to inhibit
read operations.

3.6

ERROR MESSAGES

The following three error message formats are issued by the RKaSS
diagnostic program.
The first two are issued by the RK0SD data
reliability test.
ERR followed by an
Refer to Table 3-2.

error

number.

RKDS-

Contents
Register

Drive·

Status

RKER-

Contents of the Error Register

RKCS-

Content of
Register

RK ERROR NO.-

3-7

the

Control

Status

RK~5S

AND RK~5D DIAGNOSTIC PROGRAMS

RKBA-

Contents of the Current Bus Address
Register

RKDA-

Content
Register

RK ERROR NO.-

the

Disk

Address

ERR followed by an
Refer to Table 3-2.

error

number.

EXPECTED-

Data expected

RECEIVED-

Data received

CYLINDER-

Cylinder address of error

TRACK-

Track address of error

SECTOR-

Sector address of error

DISTANCE INTO SECTOR-

Distance into
verify
error
starts at 0.

RETRY NO.-

Which retry attempt has failed

READ NO.-

Which of the 8 successive read
attempts failed during random test

sector
before
a
occurred.
Count

CONTENTS OF RKDA INCORRECT
EXPECTED-

RKDA contents expected

RECEIVEC-

RKDA contents received

3-8

RK05S AND RK05D DIAGNOSTIC PROGRAMS
Table 3-2
RK05S and RK05D Error Messages
ERROR NUMBER

ASSOCIATED TEST

Conversation mode
for address test

Error detected when performing
an implied seek to cylinder "A".

Conversation mode
for address test

Error detected when ?erforming
an implied seek to cylinder liB".

Address (part 1)

A hardware error occurred after
issuing a read header command
to cause an implied seek to
cylinder 0.

Address (part 1)

A hardware error occurred after
issuing a read header command
to cause an implied seek to
cylinder n.

Address (part 2)

A hardware error occurred after
issuing a read header command
to cause an !molied seek to the
cylinder adclress being increased.

Address (part 2)

A hardware error occurred after
issuing a read header command to
cause an implied seek to the
cylinder address that is beinq
decreased.

Address (part 3)

A hardware error occurred after
a 2-word write command has been
issued to put the sector address
pattern in the selected sector
on track " of cylinder 0.

Address (part 3)

A hardware error occurred after
issuinq a 2-word read command to
cl sector on track 0, cylinder 0.

Address (part 3)

The data read does not match the
sector address selected.

Address (part 4)

A hardware err~~ o~curred after
issuing a 2-word write command to
!Jector o of the selected track.
The data pattern written is the
track address.

Address (part 4)

A hardware error occurred after
issuinq a 2-word read command.

Address (part 4)

The data does not match the
t:rack address selected.

Address (part 5)

A hardware error occurred after
i.ssu ing a 2-word write command
t:o track o sector o of the
selected cylinder. The data
written is the cylinder address.

MEANING

(continued on next page)
3-9

RKess AND RK05D DIAGNOSTIC PROGRAMS
Table 3-2 (Cont.)
RK05S and RK05D Error Messages
MEANING

ERROR NUMBER

ASSOCIATED TEST

Address (part 5.)

A hardware error occurred after
issuing a 2-word read command.

Address (part 5)

The data read does not match the
cylinder address selected.

Address (part 6)

A hardware error occurred while
writinq 512 words of data consisting of 177777 starting at
sector 11 of track 0.

Address (part 6)

A hardware error occurred while
reading 2 words from sector 0
of track 1.

Address (part 6)

The data pattern read was not
177777. Therefore, it is probable that the hardware logic did
not cross over to sector o of
track 1.

Address (part 7)

A hardware error occurred while
writing a data pattern of
177777's to sector 11 of track
1.

Address (part 7)

A hardware error occurred while
readinq 2 words from sector 0.
The cylinder address is in the
range 1 throuqh 199.

Data test and
conversation mode

A hardware error occurred while

Data test and
conversation mod@
for data test

A hardware error occurred while

Random test

A hardware error occurred while
writing random data to a random
surface address.

Formatter

A hardware error occurred while

writing the selected data pattern.
reading the data or the data
is incorrect.

executing a write header command.
31

Formatter

A hardware error occurred

while executing a read header
command.
32

Formatter

Header data is incorrect.

Random test

A hardware error occurred while

executing a random seek command
orior to readinq the data.
34

Random test

The data read is incorrect.
(continued on next page)
3-10

FKOSS AND RK05D DIAGNOSTIC PROGRAMS
Table 3-2 (Cont.)
RKOSS and RKOSD Error Messages
ERROR NUMBER

ASSOCIATED TEST

MEANING

Random test

A hardware error occurred when
executing a head reset command
during an error recovery seauence.

Address (part 7)

Data read did not consist of a
pattern of 177777. Therefore,
it is probable that the dat~
transferred did not cross
cylinder boundaries.

100

Routine run in
conjunction with
address test and
conversation mode.

3-11

CHAPTER 4
RP03S, RP02S, RP02CS, RP03D, RP02D,
AND RP02CD, DIAGNOSTIC PROGRAMS

The RP03S, RP02S, and RP02CS diagnostic programs and the RP03D, RP02D,
and RP02CD data reliability programs are the hardware tests for the
RP02 and RP03 disk. The data reliability tests are a subset of the
diagnostic programs.
The RP03S, RP02S, and RP02CS diagnostic
tests:

provide

four

disk

The RP03D, RP02D, and RP02CD data reliability tests provide
tests:

two

disk

4.1

Address test,

Data test,

Random test,

Formatter.

Data test,

Random test.

programs

ADDRESS TEST CRP03S, RP025 AND RP02CS ONLY)

The address test consists of six parts.

4.1.1

Part 1 of Address Test

Part 1 of the address test issues read header commands to allow the
program to verify the true position of the heads without causing a
header verify error in the hardware. The seek commands in this test
are implied seeks that result from the read header command.
In part 1, the program seeks from cylinder 0 to cylinder n and then
back to 0 again. The value of n starts at 1 and is increased to 625
for the RP03: it is increased to 312 for the RP02. After each seek,
the contents of SUCA (selected unit cylinder address register) are
verified to ensure that the heads are positioned at the correct
cylinder.

4-1

RPI3S, RPI2S, RP92CS, RP03D, RP82D, AND RP02CD
4.1.2

Part 2 of Address Test

Part 2 of the address test issues a read header command to allow the
program to verify the true position of the heads without causing a
header verify error in the hardware. The seek commands in this test
are implied seeks that result from the read header command.
This part differs from part 1 in that a seek command is issued from
cylinder 0 through 625. The first cylinder number is increased by 1
and the second is decreased by 1. Then the test seeks to cylinder 1
This process is repeated until the number being
and back to 624.
decreased goes back to zero. After each seek command, the test checks
for errors and verifies the contents of SUCA (selected unit cylinder
address register).

4.1.3

Part 3 of Address Test

Part 3 of the address test verifies that each sector from 0 through 9
is addressable. Each sector on cylinder 0 and track 0 is written with
a data pattern equal to its address. Then each of the sectors is read
and verified. Any errors are reported to the operator.

4.1.4

Part 4 of Address Test

Part 4 of the address test ensures that each track on cylinder 0 is
addressable and that 2-sector transfers initiated on sector 9 cross
over to the next track. A 2-sector write is issued to sector 9 of
each track on cylinder I. The pattern written is the track number.
Two words of sector 0 of tracks 1 through 19 of cylinder 0 are read
and verified.

4.1.5

Part of Address Test

Part 5 of the address test ensures that each cylinder is addressable
and that the device updates to the next cylinder if a transfer crosses
cylinder boundaries. A 2-sector write is issued for each cylinder at
sector 9 of track 19. The pattern written is the cylinder n~mber.
Starting at cylinder 1, sector 0 of track 0, the sector is read and
the data verified. This process is repeated for subsequent cylinders.

4.1.6

Part 6 of Address Test

Part 6 of the address test ensures that the drive can erase the
remainder of a sector on a partial write. Sector 0 of track 0 of
cylinder 0 is written with a pattern of all ones (177777).
Then, a
partial write of two words of ones is issued to the same disk address.
The sector is read and checked to determine whether all of the sector
except the first two words has been erased.

4.2

DATA TEST

In the data test, write and read operations are performed on the
drive.
The data is first written on the entire pack and then read.

4-2

RP03S, RP02S, RP02CS, RP03D, RP02D, AND RP02CD
Prior to each read, the data buffer always is cleared.
verified and any errors are reported to the operator.

The

data

If an error is detected while reading, four retries are attempted;
then the head is homed and four more attempts are made to read the
data.
The entire surface is tested with six distinct patterns:
1.

Zeroes,

Ones (177777),

Checkboard,

Floating ones,

Random data,

Count pattern (full-word, binary, sequential, for the size of
the buffer).

The size of the transfer is the buffer size specified during execution
of CMD. The minimum transfer is 512 words.

4.3

RANDOM TEST

The random test randomly selects a disk surface address and writes
random data to it.
The size of the transfer is the buffer size
specified during execution of CMD.
Prior to each read, the data buffer always is cleared.
The random
data then is read and verified. The sequence is repeated 1000 (octal)
times. After each write operation, a random seek is issued.
The
purpose of this is to have the heads seek back to the cylinder just
before reading. The read operation is repeated 10 (octal) times with
intervening seeks.
The purpose ()f these operations is to expose any
read reduction problems.
If the heads have a tendency to vibrate, this difficulty should appear
as parity errors.
If an error is detected, the read number is typed to show which read
was being performed.
If the error is unrecoverable, the read
operation is terminated. If an error is detected ~uring the read
operation four attempts are madE! to read the data. If the attempts
are unsuccessful, the heads are horned and four more attempts are made
to read the data.

4.4

FORMATTER (RP03S, RP02S, AND RP02CS ONLY)

The formatter allows the operator to format an RP03 or RP02 disk pack
on line.
The entire pack is formatted 10 sectors at a time. If an
error occurs, the program retires by formatting only one sector at a
time.
After formatting, the entire pack is verified 10 sectors at a
time. The operator is informed of any sectors that cannot be
formatted correctly.
The following header format is used.

4·-3

RP03S, RP02S, RP02CS, RP03D, RP02D, AND RP02CD
Word 1 • 0
Word 2 bits 6 through 14 • cylinder address
Word 2 bits 1 through

5· track address

Word 3 • sector address

4.5

OPERATIONAL INFORMATION

The operational information for the RP03 and RP02 tests consists of
TEST PARAMETER bit settinqs and conversation mode use. Conversation
mode applies only to the RP03S, RP02S, and RPe2CS diagnostic programs.

4.5.1

TEST PARAMETER Bit Settings

In response to the question TEST PARAMETERS, certain bits can be set.
Table 5-1 lists the bits and providees their meanings. Bits 10, 3, 2,
1, and 0 apply only to the RP03S diagnostic program.

4.5.2

Conversation Mode (RP03S, RP82S, and RP02CS Only)

When conversation mode is requested by setting bit 18 in response
TEST PARAMETERS, a series of questions is printed on the console.

Two versions of conversation mode are p~ovided with the RP03S
diagnostic program.
One specifies information for the address test
and the other specifies information for the data test.

4.5.2.1 Address Test Conversation Mode - Conversation mode for the
address test allows the operator to specify two cylinder addresses in
octal. The program then issues seek commands between the specified
cylinder.
Any errors encountered are reported to the operator. Once
started, this program loops until it is aborted by the operator.
The program requests the two cylinder addresses as follows.

Enter a valid cylinder address in octal.
"8" CYLINDER?

Enter a valid cylinder address in octal.

4.5.2.2 Data Test Conversation Mode - In conversation mode for the
data test, the operator can specify the data transfer size, the disk
surface address, the pattern desired, and the function to
be
performed.
The following questions are aSked.

4-4

RP83S, RP02S, RP02CS, RP03D, RP02D, AND RP02CD
Table 4-1
RP03S and RP03D TEST PARAMETER Bits
BIT

SETTING

MEANING

Stall on error. The task waits up to.30
minutes before exiting. The s1:a11 can
be aborted by toggling the
console
defined
at task startup in
switch
response to the question WHICH CONSOLE
S,"lITCH
APPLIES
FOR
OPERATOR
INTERVENTION.

Loop on error. The task loops on the
failing instruction sequence. ~rhe loop
is ~bortab1e only by specifying new test
parameters with bit 14 equal to A.

Inhibit printouts
printinq.

The console bell
Ring bell on error.
rings every time an error is detected in
a test sequence.

Run continuously.
The program prints
the end of pass number at completion and
then repeats the testing sequence.

Enter conversation mode.
See Section
4.5.2 for a description of conversation
mode (5 versions only).

Restart the program. The program aborts
the oresent test sequence and restarts
at the newly selected test.

Print only the first data compare error
found within a specified data trc!lnsfer.

Prints Ul' to 3 data compare errors
within a specified data transfer.

between
Inhibit
seek
operation
successive reads durin~ the random test.

Formatter (5 versions only).

Random test (5 versions only).

Data test (5 versions only).

Address test (5 versions only).

4-5

except

for

forced

RP83S, RP82S, RP02CS, RP03D, RP92D, AND RP82CD
WORD COUNT 2 TO x
Enter an octal value to indicate the data buffer size for the data
test.
The maximum value that x can attain is the number specified
during execution of CMD.
DO YOU WISH TO SPECIFY THE DISK ADDR?

(Y OR N)

Type Y to indicate that a particular surface address is to be
specified for testing7 otherwise, type N. If N is typed the entire
surface is read and/or written and the next question asked is PATTERN
NO. ?

CYLINDER
Type the desired cylinder number in octal.
TRACK
Type the desired track number in octal.
SECTOR
Type the desired sector number in octal.
PATTERN NO.?
Select one of the diagnostic program's patterns or enter the desired
pattern. To select one of the prestored patterns type the number that
precedes the desired pattern in the following list.
£I •

zeros

1 • ones (177777)
2 • checkerboard
3 • floating ones
4 • random data
5 • count pattern (full word, binary, sequential for size of
buffer)
6 • run all patterns
If a user-selected pattern
characters and press RETURN.

specifiedi

enter

Type Y to perform all write operations
inhibit write operations.

the

WRITE?

READ?

octal

CY OR N)
test

type

(Y OR N)

Type Y to perform all read operations in the test or type N to inhibit
read operations.

4-6

RP93S, RP02S, RP02CS, RPe3D, RP02D, AND RP02CO
4.6

ERROR MESSAGE FORMAT

The following four message formats are issued by the RP03S
program and the RP03D data reliability test.
RP ERROR NO.-

ERR followed by an
Refer to Table 4-2.

diagnostic

error

number.

RPOS-

Contents of Device Status Register

RPER-

Contents of Error Register

RPCS-

Contents of Control Status Register

RPBA-

Contents of Bus Address Register

CYLINDER-

Cylinder number of the error

TRACK-

Track number of the error

SECTOR-

Sector number of the error

DATA VERIFY ERROR
RP ERROR NO.-

ERR followed by the number of
error. Refer to Table 4-2.

the

EXPECTED-

Data expected

RECEIVED-

Data received

CYLINDER-

Cylinder address or error

TRACK-

Track address of error

SECTOR-

Sector address of error

DISTANCE
INTO SECTOR-

Distance into sector in
verify
error was encountered.
starts at 0.

RETRY NO.-

Indicates which read attempt is
progress.

READ NO.-

Printed during random
test
to
indicate which of the 8 successive
read attempts failed

which

the

The

count
in

RP03S, RP02S, RP02CS, RP03D, RP02D, AND RP82CD
DISK ADDRESS OlD NOT UPOATE PROPERLY
EXPECTED-

Address expected

RECEIVED-

Address received

CONTENTS OF SUCA INCORRECT
EXPECTED-

SUCA expected

RECEIVED-

SUCA received

4-8

RP03S, RP02S, RP02CS, RP03D, RP02D, AND RP02CD
Table 4-2
RP03S, RP02S, RP02CS, RP03D, RP02D, and RP02CD Error Messages
ERROR NUMBER

ASSOCIATED TEST

MEANING

Address test portion
of conversation mode

A hardware error occurred after
the test issued a read header
command.
This command caused
an implied seek to cylinder A.

Address test portion
of conversation mode

A hardware error occurred after
the test issued a read header
command.
This command caused
an implied seek to cylinder B.

Address (part 1)

A hardware error occurred after
issuing a read header command.
This command causes an implied
seek to cylinder 0.

Address (part 1)

A hardware error occurred after
issuing a read header command.
This command causes an implied
seek to cylinder n.

Address (part 2)

A hardware error occurred after
issuing a read header command
to the cylinder address being
increased.
It
causes
an
implied seek to the selected
cylinder.

Address (part 2)

A hardware error occurred after
issuing a read header command
to the cylinder address that is
decreasing.
It
causes
an
implied seek to the selected
cylinder.

Address (part 3)

A hardware error occurred when
issuing a 2-word write to the
selected sector.
The
data
pattern written is equal to the
sector address.

Address (part 3)

A hardware err~r occurred after
issuing a 2-word read command.

Address (part 3)

The data is incorrect.

Address (part 4)

A hardware error occurred after
issuinq
a
5l2-word
write
command to sector 9 of a track
on
cylinder 0.
Each write
should overflow into sector 0
of the next track. The data
pattern written is the address
of the selected track.

Address (part 4)

A hardware error occurred after
issuing a 2-word read command
(continued on next page)
4--9

RP03S, RP02S, RP02CS, RP03D, RP02D, AND RP02CD
Table 4-2 (Cont.)
RP03S, RP02S, RP02CS, RP03D, RP02D, and
ERROR NUMBER

RP~2CD

Error Messages
MEANING

ASSOCIATED TEST

to sector 0. The track address
varies from 1 through 19. The
data read should be equal to the
track address selected minus 1
because
the
data
written
overflowed
from
the previous
track.
14

Address (part 4)

The

data
should
equal the
address selected minus 1.

track

Address (part 5)

A hardware error

after

data

incorrect.

occurred

The

issuing a 5l2-word write command
to sector 9 of track 19 on a
cylinder.
The
data
pattern
written is the address of the
selected cylinder.
16

Address (part 5)

Address (part

A hardware error

occurred

after

issuing a 2-word read command to
sector 0 of track
0
on
a
cylinder.
The data read from
sector 0 should be eaual to the
cylinder address minus 1. The
reason is that the data written
overflowed
from
the previous
cylinder.

The

data

incorrect.

should be equal to the cylinder
address minus 1.
Address (part 6)

A hardware error

occurred

after

issuing a 256-word write command
to sector 0, track 0, cylinder 0.
The data pattern to be written is
177777.

Address (part 6)

A hardware error

occurred

after

issuinq a 2-word write to sector
0, track e, cylinder 0.
22

Address (part 6)

A hardware

error

occurred

when

reading 256 words from sector 0,
track 0, cylinder 0.
23

Address (part 6)

The data is incorrect.

Data test and
data test portion
of conversation
mode

A hardware error occurred while
writing the selected pattern.

(continued on next page)

4-10

RP03S, RP02S, RP02CS, RP83D, RP02D,

RP~3S,

RP~2S,

RP~2CS,

AND

RP02CD

Table 4-2 (Cont.)
RP~3D, ffi?_2D, and RP_2CD Error Messages

ERROR NUMBER

ASSOCIATED TEST

Data test or data
test portion of
conversation mode

A hardware error occurred
reading the data or the
is incorrect.

Formatter

A hardware error occurred while
issuing a write header command to
format 10 sectors at a time.

Formatter

A hardware error occurred when
issuing a read header command to
read 10 sectors at a time.

Formatter

The first word in the
not PJ.

Formatter

The second word in the header
does not contain the cylinder and
track address.

Formatter

The third
does
not
address.

Formatter

A hardware error occurred while
issuing a write header command to .
format 1 sector at a time.
This
error message should be preceded
by ERR 50.

Random test

A hardware error occurred after
writing random data to a random
surface address.

Random test

A hardware error occurred while
reading the random data or the
data is incorrect.

Random test

A hardware error occurred
issuinQ
a seek command
random address.

Random test

A hardware error occurred after
This is
issuinq a home seek.
part of
recovery
the
error
sequence.

MEANING

4-·11

word of
contain

while
data

header

the
the

header
sector

after
to a

CHAPTER 5
RP04S AND RP04D DIAGNOSTIC PPOGPAMS

The RP04S diagnostic program and the RPC4D data reliability ?rogram
are the two hardware tests for the RPe4 disk.
The RP04D date
reliability test is a subset of the RP04S diagnostic program.
The RP04S diagnostic program provides four disk tests:
1.

Address test,

Data test,

Random test,

Formatter,

The RP04S data reliability test provides two disk tests:

5.1

Data test,

Random test

ADDRESS TEST (RP04S ONLY)

The address test consists of six parts.

5.1.1

Part 1 of Address Test

Part 1 of the address test issues read header commands to allow the
proqram to verify the true 90s:ltion of the heads without causing a
header verify error in the hardware. The seek comman~s in this test
are implied seeks thE-: result from the read header command.
In part 1, the program seeks from cylinder 0 to cylinder n and then
back to 0 again.
The value of n starts at 1 and increases to 633.
After each seek, the contents of current cylinder register (RHCC) are
verified to ensure that the heads are positioned at the correct
cylinder.

5.1.2

Part 2 of Address Test

Part 2 of address test issues a read header command to allow the
program to verify the true position of the heads without causing a
header verify error in the hardwarl!. The seek commands in this test

5-1

RP04S AND RP04D DIAGNOSTIC PROGRAMS

are implied seeks that result from the read header command.
This part differs from part 1 in that a seek command is issued from
cylinder e throu~h cylinder 633.
The first cylinder number is
increased by 1 and the second is decreased by 1. Then the test seeks
to cylinder 1 and back to cylinder 633. This ~rocess is repeated
until the number beinq decrease~ goes back to zero. After each seek
command, the test checks for errors and verifies the contents of RHCC
(current cylinder address). The header data are comp~red to! ensure
that the heads are positioned at the correct cylinder.

5.1.3

Pa~t

3 of Address Test

Part 3 of the address test verifies that p.cch sector from 0. through 25
is addressable.
The test issues a 2-word write to each sector on
cylinder 0 and track e. The pattern written is the sector address.
Each of the sectors is read and verified. Any errors are reported to
the operator.

5.1.4

Part

of Address Test

Part 4 of the address test ensures that each track on cylinder 0 is
addressable and that 2-sector transfers initiated on sector 25 cross
over to the next track. A 2-sector write is issued to sector 25 of
each track on cylinder 0. The pattern written is the track number.
Two wores of sector 0 of tracks 1 throuqh 21 of cylinder ~ are read
and verified.

5.1.5

Part 5 of Address Test

Part" 5 of the address test ensures that each cyli~der is addressable
and that the device updates to the next cylinder if a transfer crosses
cylinder boundaries. A 2-sector write is issued for each cylinder at
sector 25 of track 1. The pattern written is the cylinder number.
Starting at cylinder 1, sector 0 of track 0, 2 words of the sector are
read and the data is verified.
This process is repeated for
subsequent cylinders.

5.1.6

Part 6 of Address Test

Part 6 of the address test ensures that the drive can erase the
remainder of a sector on a partial write. Sector e of track e of
cylinder e is written with a pattern of all ones (177777).
Then, a
partial write of two words of ones is issued to the disk address. The
sector is read and checked to determine whether all of the sector
except the first two words have been erased.

5.2

DATA TEST

During execution of the data test, write and read operations are
performed on the drive. The data is written on the entire pack and
then read back. The data buffer is cleared before each read.
The
data is verified and any errors are reported.

5-2

RP84S AND RP04D DIAGNOSTIC PROGRAMS
If an error is detected during the read operation, four retries are
attempted, and then the head is homed. Four more attempts are made to
recover the data.
The entire surface is tested with the following six patternsl
1.

Zeroes,

Ones (177777),

Checkerboard,

Floating ones,

Random data,

Count pattern (sequential., binary, full-word, up to
the buffer) •

The size of the transfer is determined by
during the execution of CMD.

5.3

the

buffer

size

selected

RANDOM TEST

The random test selects a disk surface address randomly and writes
random data on it. After each write operation, the program issues a
random seek to cause the heads to seek back to the cylinder just prior
to reading.
The size of the transfer depends on the buffer size
selected during execution of CMD.
Prior to each read operation, the data buffer is cleared.
Then, the
random data is read and verified. This sequence is repeated 1000
(octal) times. The read operation is repeated eight times with
intervening seeks to detect any read reduction problems. If an error
is detected, the read number is typed to show which read was being
performed when the error occurred. If the error is unrecoverable, the
read operation is terminated. If an error is detected. during the read
operation, four attempts are made to read the data. If the data still
cannot be read, thee heads are homed and four more attempts are .ade
to read the data.
If the heads have a tendency to vibrate, this condition should
as parity errors.

5.4

appear

FORMATTER TEST (RP84S ONLY)

The formatter test formats the entire RP84 pack and then verifies it.
The entire pack is formatted one sector at a time. Any errors are
reported to the operator.
After formatting, the entire pack is
veritied one sector at a time to ensure that the headers were written
correctly.

5.5

OPERATIONAL INFORMATION

The operational information for the RP04S and RP04D diagnostic program
consists of TEST PARAMETER bit settings and conversation mode use.
Conversation can be used only for RP04S.

5-3

RP94S AND RP94D DIAGNOSTIC PROGRAMS
5.5.1

TEST PARAMETER Bit Settings

In response to the question TEST PARAMETERS, certain bits can be set.
Table 5-1 lists the switches and provides their meanings. Bits 19, 3,
2, 1, and 8 apply to the RP84S only.

5-4

RP84S AND RPI4D DIAGNOSTIC PROGRAMS
Table 5-1
RP84S and RP84D TEST PARAMETERS Bits
BIT

SETTING

Stall on error. The task waits up to 38
minutes before exiting. The stall can
be aborted by toggling the
console
swit:ch
defined
at task startup in
response to the question WHICH CONSOLE
SWITCH
APPLIES
FOR
OPERATOR
INTf:RVENTION.

Loop on error. The task loops on the
failing instruction sequence. The loop
is abortable only by specifying new test
parameters with bit 14 equal to 8.

Inhibit printouts
printing.

Ring bell on error.
The console bell
rings every time an error is detected in
a tE~st sequence.

Run continuously.
The program prints
the end of pass number at completion and
then repeats the testing sequence.

Restart the program. The program aborts
the present test sequence and restarts
at the newly selected test.

Print only the first data compare error
found within a specified data transfer.

Print up to 3 data compare errors within
a specified data transfer.

Inhi.bit
operation
between
seek
succ!ess i ve reads durin9 the random test.

Formatter (RP04S only).

Random test (RP04S only).

Data test (RP84S only).

Addr'ess test (RP84S only).

MEANING

except

for

forced

Enter conversation mode.
See Section
5.5.2 for a description of conversation
mOdE! (RP84 only).

RPI4S AND RP84D DIAGNOSTIC PROGRAMS
5.5.2

Conversation Mode

When conversation mode is requested by setting bit 18 in response
TEST PARAMETERS, a series of questions is printed on the console.

Two versions at conversation mode are provided with the RP84S
diagnostic program.
One specifies information for the address test
and the other specifies intormation for the data test.

5.5.2.1 Address Test Conversation Mode - Conversation mode for the
address test allows the operator to specify two cylinder addresses in
octal. The program then issues seek commands between the specified
cylinders.
Any errors eencountered are reported to the operator.
Once started, this program loops until it is aborted by the operator.
The program requests the two cylinder addresses as follows.
-A- CYLINDER?
Enter a valid cylinder address in octal.

-B M CYLINDER?
Enter a valid cylinder address in octal.

5.5.2.2 Data Test Conversation Mode - In conversation mode for the
data test, the operator can specify the data transfer size, the disk
surface addresa, the patten desired, and the function to be performed.
The following questions are asked.
WORD COUNT 2 TO x
Enter an octal value to indicate the data buffer size for the data
test.
The maximum value that x can attain is thee number specified
during execution of CMD.
DO YOU WISH TO SPECIFY THE DISK ADDR?

(Y OR N)

Type Y to indicate that a particular surtace address is to be
specified for testing, otherwise, type N. If N is typed the entire
surface is read and/or written and the next question asked is· PATTERN
NO.?
CYLINDER
Type the desired cylinder
address is 632.

number

octal.

TRACK
Type the desired track number in octal.
SECTOR
Type the desired seector number in octal.
PATTERN NO.?

5-6

The

maximum

cylinder

RPS4S AND RP84D IDIAGNOSTIC PROGRAMS
Select one of the diagnostic proglram's patterns or enter the desired
pattern. To select one of the prestored patterns type the number that
precedes the desired pattern in the following list.
8 - zeros
1 - ones (177777)
2 - checkerboard
3 - floating ones
4 - random data 5 - count pattern (full word,
for size of buffer)

binary

sequential

6 - run all patterns
If a user-supplied pattern is to
characters and press the RETURN kE!Y.
WRITE?

specified,

enter

octal

the

type

N to

(Y OR N)

Type Y to perform all write operations
inhibit write operations.
READ?

test

(Y OR N)

Type Y to perform all read operations in the test or type N to inhibit
read operations.

5.6

ERROR MESSAGES

The following three error message formats are issued by the RP84S
diagnostic program.
The first two are issued by the RP84D data
reliability test.
error

number.

RHCSl-

contents of the Control and
1 register

Status

RHBA-

content of
Register

the

Unibus

Address

RHDA-

contents
Register

the

desired

Addres

RHCS2-

contents of the Control and
2 register

Status

RHDSl-

contents of the Status Register

RHERl-

contents of Error Register 1

RHCA-

contents
of
desired
Address Register

RHER2-

contents of Error Register 2

RHER3-

contents of Error Register 3

RP ERROR NO.-

ERR followed by an
Refer to Table 5-2.

5,-7

Cylinder

RP84S AND RP84D DIAGNOSTIC PROGRAMS
CYLINDER-

cylinder address of the error

TRACK-

track address of the error

SECTOR-

sector address of the error

RP ERROR NO.-

BRR followed by an
Refer to Table 5-2.

error

number.

EXPECTED-

data expected

RECEIVED-

data received

CYLINDER-

cylinder address of the error

TRACK-

track addre~s of the error

SECTOR-

sector address of the error

DISTANCE

distance
verify

INTO SECTOR-

error occurred.

RETRY NO.-

indicates which
reread
recovered the data

READ NO.-

indicates which of the 8 successive
read attempts failed during the
random test

into

DISK ADDRESS DID NOT UPDATE PROPERLY
EXPECTED-

address expected

RECEIVEO-

address received

5-8

sector

before

Count starts at 0.
attempt

RP84S AND RP84D DIAGNOSTIC PROGRAMS
TablEt 5-2
RP84S and RP84D Error Messages
ERROR NUMBER

ASSOCIATED TEST

Conversation mode
for address test

Error detected when performing
an implied seek to cylinder

Conversation mode
for address test

Error detected when performing
an implied seek to cylinder

Address (part 1)

A hardware error occurred after
issuing a read header command
to cause an implied seek to
cylinder 0.

Address (part 1)

A hardware error occurred after
issuing a read header command
to cause an implied seek to
cylinder n.

Address (part 2)

A hardware error occurred after
issuing a read header command
to cause an implied seek to the
cylinder
address
being
increased.

Address (part 2)

A hardware error occurred after
issuing a read header command
to cause an implied seek to the
cylinder
address
being
decreased.

Address (part 3)

A hardware error occurred after
a 2-word w~ite command has been
issued to
put
the
sector
address pattern in the selected
sector of track S, cylinder 0.

Address (part 3)

A hardware error occurred after
issuing a 2-word read command
to a sector
on
track
e,
cylinder 0.

Address (part 3)

The data read does not match
the sector address selected.

Address (part 4)

A hardware error occurred after
issuing
a
5l2-word
write
command to sector 25 on tracks
o through 20 of cylinder 0.
Each write should overflow onto
sector 0 of the next track.
The data pattern written is the
track address.

MEANING

"A".

"8".

(continued on next page)

5··9

RP84S AND RP84D DIAGNOSTIC PROGRAMS
Table 5-2 (Cont.)
RP84S and RP84D Error Messages
MEANING

ERROR NUMBER

ASSOCIATED TEST

Address (part 4)

A hardware error occurred after
issuing a 2-word read command
to sector 8 of tracks 1 through
21 on cylinder 8.
The data
read from sector 8 should be
the
track
address selected
minus 1. The reason is that
the
data pattern overflowed
from the previous track.

Address

(part 4

The data is incorrect.
It
should be the track address
selected minus 1.

Address (part 5)

A hardware error occurred after
issuing
a
5l2-word
write
command to sector 2S of track
21 on a cylinder.
The data
pettern written is the cylinder
address selected.

Address (part 5)

A hardware error occurred after
issuing a 2-word read command
from sector 8, track 8 on a
cylinder.

Address

The

Address (part 6)

A hardware error occurred after
issuing
a
256-word
write
command to sector 8 of track 0,
cylinder 0.
The data written
is 177777.

Address (part 6)

A hardware error occurred after
issuing a 2-word write command
to sector 8
of
track
8,
cylinder 0.
The data written
is 177777.
A partial write
command should result in tl e
rest of
the
sector
being
erased.

Address (part 6)

A hardware error occurred after
issuing a 256-word read command
to sector 0
of
track
I,
cylinder 8.

(part 5)

data is incorrect.
It
should be the cylinder selected
minus 1. The reason is that
the data pattern written should
have
overflowed
from
the
previous cylinder.

(continued on next page)

5-18

RP04S AND RP84D D:[AGNOSTIC PROGRAMS
Table 5-2 (Cont.)
RP04S and RP84D Error Messages
ERROR NUMBER

ASSOCIATED TESTS

Address (part 6)

The data is incorrect, the first
2 words should be 177777 and
the rest of the sector should
be zeros.

Data test and data
test portion of
conversation mode

A hardware error occurred while
writing the selected pattern.

Data test and data
test portion of
conversation mode

A hardware error occurred while
readinq the data pattern or the
data is incorrect.

Formatter

A hardware error occurred after
issuing a write header command
to the selected address.

Formatter

A hardware error occurred after
issuing a read header command
to the selected address.

Formatter

The first word of the header is
incorrect.
It should contain
the cylinder address and bit 12
should be set.

Formatter

The second word of the header
should
is
incorrect.
It
contain the sector and track
address.

Random test

A hardware error occurred while
writing random data to a random
surface address.

Random test

A hardware error occurred after
issuing a seek command to a
random address.

MEANING

hardware error occurred while
reading the random data or the
data is incorrect.

5·-11

CHAPTER 6
RS04S, RS03S, RS04D, RS03D DIAGNOSTIC PROGRAMS

The RS04S and RS03S diagnostic program and the RS84D and RS03D data
reliability program are the two hardware tests for the RS84/RS83
disks. The RS04D data reliability program is a subset of the RS84S
diagnostic program.
The RS84S and RS83S diagnostic programs provides three disk tests:
1.

Address test,

Data test,

Random test.

The RS04D and RS83D data reliability tests provides two disk tests:
1.

Data test,

Random test.

The following information is important to an understanding of both the
RS04/RS03 Sand D programs.
1.

In lAS and RSX-llD, all surface addressing to an RS~3/RS04 is
done on a 256-word boundary.
Since a sector on the RS84 contains 128 words, all addressing
must be performed to an even-numbered sector.
Since a sector on the RS03 contains 64 words, all addressing
must be done in multiples of four. For example, the sector
address in octal always must end in a 8 or 4.

In order to determine whether the device is an Rse3 or an
RS04, a 2-word read operation is issued to sector e of track
o to obtain the contents of the device registers. Error
number 100, Jescribed in Table 6-2, is associated with this
initialization program.
NOTE
All reference to the RS04
include the RSe3 disks.

6-1

disks

also

RS04S, RS83S, RS04D, RS03D DIAGNOSTIC PROGRAMS
6.1

ADDRESS TEST (RS94S ONLY)

The address test for the RS84S consists of two parts.

6.1.1

Part 1 of Address Test

Part 1 of the address test ensures that each sector of the RS03/RS94
surface is uniquely addressable by performing the following steps.
1.

Writing a pattern on the entire surface.
contains the current track and sector address.
written at a time.

The pattern
256 words are

Reading and verifying the content of each sector after it
written.

The pattern written and verified by the test consists of 256 words
current address information. Each word has the following format.

Byte 1 contains the track address right jusvified.
Byte 0 contains the sector addres right justified.

6.1.2

Part 2 of Address Test

Part 2 of the address test selectes a random disk address and issues a
read operation.
The data on the disk was written by part 1 of the
address test. It should contain the sector and track address of the
read. The random read is repeated 1908 (octal) times.
If an error occurs, the error message printed by the program can
used to determine whether the wrong disk address was selected.

6.2

DATA TEST

The data test performs read and write operations on the drive.
The
data is written on the entire pack and then read back. Prior to each
read operation, the input data buffer is cleared.
The data is
verified and any errors are reported to the operator.
The entire surface is tested with six distinct patte~ns:
1.

Zeros,

Ones (177777)

Checkerboard,

Floating ones,

Random data

Count pattern (full-word, binary, sequential for the size
the buffer).

6-2

RS04S, RS03S, RS04D, RSI3D DIAGNOSTIC PROGRAMS
If an error is detected while reading, .ight retries are attempted.
The size of the transfer is determined by the
during execution of CHD.

6.3

buffer

size

specified

RANDOM TEST

The data test randomly selects a disk surface address and writes
random data on it. The data is read back and verified. Before each
read operation, the ~nput b~ffer is cleared.
This sequence is
repeated 2000 (octal) times. After the data is written, it is read
eight times to expose any read reduction problems.
The size of the transfer is determined
specified during execution of CHD.

the

data

buffer

size

If an error is detected, eight attempts are made to read the data
correctly.
With each read error, the read number is also typed to
show on which read the error occurl:ed. The read number should not be
confused with the retry number..
Once an unrecoverable error .is
encountered, the program does flot attempt any additional
read
operations on the same data.

6.4

OPERATIONAL INFORMATION

Operational information for the RSfJ4S diagnostic program consists of
TEST PARAMETER bit settings and corlversation mode. For the RS04D data
reliability program, it consists of TEST PARAMETER bits only.

6.4.1

TEST PARAMETER Bit Settings

In response to the question TEST PARAMETERS, certain bits can be set.
Table 6-1 lists the bits and provides their meanings. Bits 10, 2, 1,
and 8 apply only to the RS04S diagnostic program.

6··3

RSS4S, RSS3S, RSS4D, RSS3D DIAGNOSTIC PROGRAMS
Table 6-1
RS04S and RSS4D TEST PARAMETER Bits
MEANING

BIT

SETTING

Stall on error. The task waits up tn 30
minutes before exiting. The stall can
console
be aborted by toggling the
defined at task start-up in
switch
response to the question WHICH CONSOLE
OPERATOR
FOR
APPLIES
SWITCH
INTERVENTION.

Loop on error. The task loops on the
failing instruction sequence. The loop
is abortable only by specifying new test
parameters with bit 14 equal to 0.

Inhibit printouts
printing.

The console bell
Ring bell on error.
rings every time an error is detected in
a test sequence.

Run continuously.
The program prints
the end of pass number at completion and
then repeats the testing sequence.

See Section
Enter conversation mode ..
6.4.2 for a description of conversat~on
mode (RS04S only).

Restart the program. The program aborts
the present test sequence and restarts
at the newly selected test.

Print only the first data compare error
found within a specified data transfer.

Print up to 3 data compare errors within
a specified data transfer.

Random test (RS04S only) ..

Data test (RS04S only).

Address test (RSS4S only).

6-4

except

for

forced

RS84S, RS83S, RS04D, RS83D DIAGNOSTIC PROGRAMS
6.4.2

Conversation Mode (RS84S ONLY)

When conversation mode is requested by setting bit 10 in response to
TEST PARAMETERS, a series of questions is printed on the console. The
following is a list of the questions and a descriptions of responses
to them.
WORD COUNT 2 TO X
Enter an octal value to indicate the data buffer size for the data
test.
The maximum value that l[ can attain is the number specified
during execution of CMD.
DO YOU WISH TO SPECIFY THE DISK ADDR?

(Y OR N)

Type Y to indicate that a particular surface address is to be
specified for testingl otherwisE!, type N. If N is typed the entire
surface is read and/or written and the next question asked is PATTERN
NO.?
TRACK
Type the desired track number in octal.
SECTOR
Type the desired sector number in octal.
PATTERN NO.?
Select one of the diagnostic program's patterns or enter the desired
pattern. To select one of the pre~;tored patterns type the number that
precedes the desired pattern in the following list.
8 • zeros
1 - ones (177777)
2 - checkerboard
3 - floating ones
4 • random data
5 - count pattern (full word,
buffer)

binary,

sequential

for

size

6 - run all patterns
If a user-selected pattern
characters and press RETURN.

specified,

enter

Type Y to perform all write operations
inhibit write operations.

the

WRITE?

READ?

octal

(Y OR N)
test

type

(Y OR N)

Type Y to perform all read operations in the test or type N to inhibit
read operations.

6-5

RS84S, RS83S, RS84D, RS83D DIAGNOSTIC PROGRAMS
6.5

ERROR MESSAGE FORMATS

The following three error message formats are issued by the RS04S
diagnostic program.
The first two also are issued by the RS84D data
reliability test.

ERR followed by an
Refer to Table 6-2.

error

RSCSl-

Contents of Control
Registers

and

RSWC-

Contents of Word Count Register

RSBA-

Contents of Unibus Address Register

RSDA-

Contents of
Register

RSCS2-

Contents of Control
Register

RSDS-

Contents of Drive Status Register

RSER-

Contents of Error Register

RSAS-

Contents
Register

RS ERROR NO.-

desired

Disk
and

Attention

ERR followed by an
Refer to Table 6-2.

error

number.
Status

address
Status

Summary

number.

EXPECTED-

Data expected

TRACK-

Track address of the error

SECTOR-

Sector address of error

DISTANCE INTO SECTOR-

Distance into sector
before
a
verify error was encountered. The
count starts at 0.

RETRY NO.-

Indicates which read retry
has failed.

READ NO.-

Printed during random
test
to
indicate which of the 8 successive
read attempts failed.

6-6

attempt

RS04S, RS03S, RS04D, RS03D DIAGNOSTIC PROGRAMS
DISK ADDRESS IS INCORRECT
TRACK
EXPECTED-

Track address expected

RECEIVED-

Track address received

SECTOR
EXPECTED-'

sector address expected

RECEIVED-

sector address received

6-7

RS84S, RSllS, RS84D, RSllD DIAGNOSTIC PROGRAMS
Table 6-2
RS84S and RS04D Error Messages
ERROR NUMBER

ASSOCIATED TEST

MEANING

Address (part 1)

A hardware error occurred while
writing
256
to the
words
selected sector.
The pattern
written
contains the sector
address.

Address (part 1)

A hardware error occurred while
reading
256
words
to the
selected sector address.

Address (part 1)

The data is incorrect.

Address (part 2)

A hardware error occurred while
reading 2 words from a random
sector.

Address (part

data is incorrect.
It
The
should be the track and sector
address.

Data test and
conversation mode

A hardware error occurred while
writing the selected pattern.

Data test and
conversation mode

A hardware error occurred while
reading the data or the data is
incorrect.

Random test

A hardware error occurred while
writing the random data to a
random surface address.

Random test

108

Program
initialization

A hardware error occurr~ti when
issuing a 2-word read to sector
8 of track 8.

hardware error occurred while
reading random data or the data
is incorrect.
Each read is
repeated eight times.

6-8

CHAPTER 7
RSllS AND DIAGNOSTIC PROGRAMS

The RSllS diagnostic program and the RSllD data reliability program
are the two hardware tests for the RSll disk. The RSX-llD data
reliability test is a subset of the RSllS diagnostic program.
The RSllS diagnostic program provides three disk tests:
1.

Address test,

Data test,

Random test,

The RSllD data reliability test provides two disk tests:
1.

Data test,

Random test.

The following information is important
diagnostics.

understanding

the

·1.

Under lAS and RSX-llC, each disk surface is divided into
256-word blocks. Each track is divided into eight sectors of
256 words. The sectors are numbered 0 through 7.

lAS and RSX-llD treat all units on an RF controller as one
continuous surface. To determine whether a specific drive is
to be exercised or whether all drives are to be exercised,
the series of c.uestions described in Section 7.4.1 are
printed on the console for operator response.

In order to determine the number of surfaces that exist on an
RS, an initializer task issues a read to the first sector of
each unit until the nonexistent drive condition sets.
When
nonexistent drive sets, the· initializer ensure that the error
bit sets also.

7.1

ADDRESS TEST (RSllS ONLY)

The address test comprises two parts.

7.1.1

Part 1 of Address Test

The first part of the address test ensures

7-1

unique

addresses

the

RSIIS AND DIAGNOSTIC PROGRAMS
disk surface by performing the following steps.
1.

Writing a pattern on the entire surface. The pattern written
contains the current unit, track, and sector address as
described below. 256 words are written at a time.

Reading and verifying each sector after it is
errors are reported to the operator.

written.

Any

The patterm written and verified by the test consists of 256 words of
current address information.
Each word of the pattern has the
following format.
Byte 1 contains the track address right justified.
Byte 0 contains thee sector address in bits 0 through 2
unit address in bits 3 through 5.

7.1.2

and

the

Part 2 of Address Test

The second part of the address test performs the following steps:

7.2

Randomly selects a disk address and reads 2 words of the
pattern written by the first part of the test. The 2 words
should contain the sector, track, and unit address of the
current read operation.

Compares the sector, track, and unit address of the read
operation with those contained in the 2 words and issues an
error message if they do not match.

Repeats steps 1 and 2 1000 (octal) times.

DATA TEST

The data test uses read and write operations to verify data written on
a drive. The data is written on the entire pack and then read. Prior
to each read operation, the input data buffer is cleared. The data is
verified and any errors are reported to the operator.
If an error is detected during the read operation, eight
attempted.

retries

are

The entire surface is tested with the following six distinct patterns.
1.

Zeros

Ones (177777)

Checkerboard

Floating ones

Random data

Count pattern (full word, binary sequential for size
buffer)

The size of the transfer is

determined

7-2

during

CMD

the

execution.

The

RSIIS AND DIAGNOSTIC PROGRAMS
minimum size of the transfer is 512 words (2 sectors).
size is 16,00e words.

7.3

The maximum

RANDOM TEST

The random test selects a disk surface address and writes data on it.
Both the disk address selected and the data written are random. The
data is read back and verified.
This seauence is repeated 2eee
(octal) times.
After the data is written, the test reads it eight
times to determine read reduction problems.
If an error is detected during the read operation, eight attempts are
made to read the data correctly. The read number is printed as part
of the error message to the o~erator to indicate on which read the
error occurred. The read number should not be confused with the retry
count which indicates the number oj: attempts to recover from an error.
Once an unrecoverable error is encountered, the program does not
attempt any additional reads on the same data.
The size of the transfer is determined during CMD execution.

7.4

7.4.1

OPERATIONAL INFORMATION

Determing the Number of Drives to Exercise

Once the diagnostic program
questions on the console.

7.4.2

started,

prints

the

following

TEST PARAMETER Bit Settings

In response to the question TEST PARAMETERS, certain bits can be
Table 7-1 lists the switches to set and provides their meanings.
10, 2, 1, and ~ apply only to the RSIIS diagnostic program.

7-3

set.
Bits

RSIIS AND DIAGNOSTIC PROGRAMS
Table 7-1
RSllS and RSIID TEST PARAMETERS Bits
MEANING

BIT

SETTING

Stall on error. The task waits up to 30
minutes before exiting. The stall can
be aborted by toggling the
console
at task startup in
switch
defined
response to the auestion WHICH CONSOLE
SWITCH
APPLIES
FOR
OPERATOR
INTERVENTION.

Loop on error. The task loops on the
failing instruction sequence. The loop
is abortable only by specifying new test
parameters with bit 14 equal to 0.

Inhibit printouts
printinq.
.
-

Ring bell on error.
The console bell
rings every time an error is detected in
a test sequence.

Run continuously.
The program prints
the end of pass number at completion and
repeats the specified test seauence.

Enter conversation mode.
See Section
7.4.3 for a description of conversation
mode (RSllS only).

Restart the program. The program aborts
the present test sequence and restarts
at the newly selected test.

Print on1v the first data compare error
found within a specified data transfer.

Print up to 3 data compare errors within
a specified data transfer.

Random test (RSllS only).

Data test (RSllS only).

Address test (RSIIS only).

except

forced

for

7.4.3

Conversation Mode (RSIIS Only)

When conversation mode is requested by setting bit 10 in response to
TEST PARAMETERS, a series of questions is printed on the console. The
following is a list of the questions and a"descriPtion of responses to
them.
WORD COUNT 2 TO X
Enter an octal value to indicate the data huffer

7-4

size

for

the

data

RS11S AND DIAGNOSTIC PROGRAMS
test.
The maximum value
during execution of CMO.

that x can attain is the number specified .

DO YOU WISH TO SPECIFY THE DISK ADDR?

(Y OR N)

Type Y to indicate that a particular surface address is to be
specified for testing: otherwise, type N. If N is typed the entire
surface is read and/or written and the next Question asked is PATTERN
NO.?
TRACK
Type the desisred track number in octal.
TEST ALL DRIVES?

(Y OR N)

Type Y to indicate yes or N to indicate no.
If the answer is yes (Y), the task
present and tests all of them.

determines

how

many

drives

are

If the answer is no (N), the following question is asked.
WHICH DRIVE?
Type the number of the drive to be tested.
through 7.

Drive numbers range from 0

SECTOR
Type the desired sector number in octal.
PATTERN NO.?
Select one of the diagnostic program's prestored patterns or enter the
desired pattern.
To select one of the prestored patterns type the
number that precedes the desired pattern in the following list.

o • zeros
1 • ones (177777)
2 • checkerboard
3 • floating ones
4 • random data
5 • count pattern (full word, binary, sequential for size of
buffer)
6 • run all

~atterns

If a user-specified pattern is to
characters and press the RETURN key~

7-5

specified,

enter

octal

RSllS AND DIAGNOSTIC PROGRAMS
WRITE?

(Y OR N)

Type Y to perform all write operations
inhibit write operations.
READ?

the

test

type

(Y OR N)

Type Y to perform all read operations in the test or type N to inhibit
read operations.

7.5

ERROR MESSAGES

The following three error message formats are issued by
diagnostic program and the RSllD data reliability test.
RF ERROR NO.-

ERR followed by an
Refer to Table 7-2.

the

RSIIS

e~ror

number.

Control

Status

RFCS-

Contents
Register

RFWC-

Contents of Word Count Register

RFBA-

Contents of Current Memory
Register

RFDA-

Contents of Disk Address Register

RFER-

Contents of Disk Address
Error Register

Extension

UNIT NO.-

Number of the unit
error occurred

which

RF ERROR NO.-

ERR followed by an
Refer to Table 7-2.

error

Disk

EXPECTED-

Data expected

RECEIVED-

Data received

TRACK-

Track address of error

SECTOR-

Sector address of error

UNIT NO.-

Number of
occurred

DISTANCE INTO
SECTOR-

unit

Distance into
verify
error
starts at 0.

Address

which

the

number.

error

sector
before
a
occurred.
Count

RE1RY NO.-

Which retry attem~t has failed.

READ NO.-

Which of the 8 successive read
attemnts failed during random test

7-6

RSllS AND DIAGNOSTIC PF.OGRAMS
DISK ADDRESS IS INCORRECT
UNIT
EXPECTEC-

Unit number expected

RECEIVED-

Unit nu~ber received

TRACK
EXPECTEO-

Track address expected

RECEIVEO-

Track address received

SECTOR
EXPECT EO-

Sector address excected

RECEIVED-

Sector address received

7-7

RSIIS AND DIAGNOSTIC PPOGFAMS
Table 7-2
RSllS and RSIlD Error Messages
ERROR

NUMBER

ASSOCIATED TEST

Address (part 1)

A hardware error occurred while
trying to write 256 words. The
nattern written is equal to the
surface address.

Address (part 1)

A hardware error occurred while
tryinq to read 256 words.

Address (part 1)

Data is incorrect.
The data
read should e<;fual the surface
address.

Address (cart 2)

A hardware error occurred while
tryinq to read 2 words from a
random address.

Address (oart 2)

Data is incorrect.
The data
should
eaual
the
surface
address.

Initializer or
conversation
mooe

An error occurred when tryinq
to read the first sector of the
selected unit.

Data test or
conversation mode

A hardware error occurred while
writinq the test pattern.

Data test or
conversation mode

hardware error occurred while
readinq the test nattern or the
data is incorrect.

Ran(~om

test

hllrdware error occurred while
random data to a random
"writing
surface address.

Random test

MEANING

harciware error occurred while
readin<:l random data or the cata
is incorrect.

7-6

CHAPTEt 8
TU56S AND TU56D DI~GNCSTIC PROGRAMS

The TU56S diagnostic pro9ram and the TU56D data reliability program
are the two hardware tests for the TU56 (DECtape) controller. The
TU56D data reliability test is a subset of the TU56S diaqnostic
?roqram.
The TU56S dia~nostic program povides three tests:
1.

Address test,

Start/stop test (forward and reverse),

Data test.

The TU56D data reliability test provides the data test.

8.1

ADDRESS TEST (TU56S O~LY)

Address test consist of four parts.

8.1.1

Part 1 of Address Test

Part 1 of the address test issued a rewind command and verified that
the unit rewinds bV testinq the end zone bit. It also tests to ensure
that the error bit sets as a result of encountering the end zone.

8.1.2

Part 2 of Address Test

Part 2 of the address test determines that the
reac data. The followinq steos.are ~erformed:

can

write

and

In a forward direction, write zeros on block 0 and
pattern in both directions,

read

the

In a forward direction, write ones on blocks
the pattern in both directions,

In a reverse direction, write ones on block 1 and
the pattern in both directions.

8-1

drive

and 1 and read

e and

read

TU56S AND TU560 DIAGNOSTIC PROGFAMS
8.1.3

Part 3 of Address Test

Part 3 of the address test verifies that each block on the tane can be
addressed uniquely. First, the odd numbered blocks are written in the
forward direction and the even numbered blocks are written in the
reverse direction. The pattern written is the block number.
Secondly, all the odd numbered blocks are read in the reverse
direction and the even numbered blocks are read in the forward
direction. After each read, the data is verified.

8.1.4

Part 4 of Address Test

Part 4 of the address test randomly selects a block address and issues
a read command.
The pattern should be the block address. This
sequence is repeated 128 times.

8.2

START/STOP TEST (TU56S ONLY)

The start/stan test verifies that the stop and start ti~es are within
the standard specification for the forward direction. After the tane
is rewound, a command is issued to read a block number.
The block
number must be within five blocks of the previously re~d block number.
Then a stop command is issued.
For example, assume that block number 5 was just rea~ and a stop
command is issued.. It takes approximately two blocks for the tape to
stop. Then another command to read a block is issued.
It reauires
approximately two more blocks for the tape to get up to speed. The
number of the block just read should be within five blocks of the
number of the block previously read. In this exawple, the number of
the block just read should be no greater than 12 (octal).
Another
check is made to ensure that the hlock number is not less than or
equal to the number of the ~reviously read block (5 in this case).
A smaller number indicates that the tape ~oved in the wrona direction.
The reverse start/stop test is the same as the forward start/stop test
except that the blocks are read in the reverse direction rather than
the forward direction.

8.3

DATA TEST

The data test verifies the data reliability of the DECtape drive. All
data in this test is transferred ~etween block 1~0 (octal) and 30~
(octal). The following six patterns are used:
1.

Zeroes,

Ones (177777),

Checkerboard,

Floating ones,

Random data,

8-2

TU56S AND TU56D DIAGNOSTIC PROGRAMS

Count pattern (full-word, binary sequential for the size of the
buffer).

For each pattern, the tape is written in the forward direction and
read in the forward direction.
Then, the tape is written in the
reverse direction and read in the reverse direction.
If an error is detected while
recover the data.

readinq,

The size of the data transferred is

five

attempts

determines

during

ate

made

execution

CMD.

8.4

OPERATIONAL INFORMATION
I

The o~erational information for the TU56S diagnostic ~roqram consists
of TEST PARAMETER bit settings and conversation mode use. Operational
information for the TU56D data reliability test consists of TEST
PARAMETER bit settings.

8.4.1

TEST PARAMETER Bit Settings

In response to the qu~stion TEST PARAMETERS, certai" bits can be set~
Table 8-1 lists the switches and provides their meaninqs. Bits Ie, 2,
1, and 0 apply to the TU56S diagnostic program only.

8-3

TU56S AND TU56D DIAGNOSTIC PPOGRAMS
Table 8-1
TU56S ana TU56D TEST PAF.AMFTE~ Bits
BIT

SETTING

Stall on error. The task waits u~ to 30
minutes before exitinq.
The. stall can be
aborted by togglino the
switch
console
defined at task startup in response to the
ouestion WHICH CONSOLE SWITCH APPLIES FOR
OPERATOP INTERVENTION.

Loop on error. The task looos on the failina
instruction seouence. The 1000 is abortable
only by specifying new test parameters with
bit 4 e~ual to 0.

Inhibit printouts except for forced printing.

Ring bell on error. The console bell rinqs
every time an error is detected in a test
sequence.

Pun continuously. The program prints the end
of pass number at completion and then reneats
the specified testing seouence.

Enter conversation mode. See Section 8.4.2
for a description of conversation mode (TU56S
ONLY).

Restart the program. The program aborts the
y;>resent test secmence and restart!:: at the
newly selected test:

Print only the first data comoare error found
within a soecified data transfer.

Print up to 3 data comnare
specified data transfer.

Run data test (TU56S only)

Run start/stop test (TU56S only)

Run address test (TU56S only)

MEANING

8-4

errors

within

TU56S AND TU56n DIAGNOSTIC PROGRAMS

8.4.2

Conversation Mode

When conversation mode is reouested by setting bit 10 in resnonse to
TEST PARAMETERS, a series of ouest.ions is printec.on the console. Two
versions of conversation mode are provide~ with the TU56S diagnostic
program. One specifies information for the address test and the other
specified information for the data test. Settinq bit 0 eoual to 1
implies that the conversation mode of the address t~st is to execute;
whereas, settinq bit 2 equal to 1 implies that the conversation mode
of the data test is to execute.

8.4.2.1 Addres~ Test Conversation Moce - Conversation mode for the
address test allows the operator to specify two block numbers in
octal. The proqram issu~s a 2-worc write to the first block and then
to the second.

The program reauests the two block addresses as follows.
BLOCK "A"
Enter a valid block address in octal.
BLeCK "8"
Enter a valid block address in octal.

8.4.2.2 Data Test Conversation Mode - The following questions
printed on the console in conversation mode for the data test.

are

WORD COUNT 2 TO x

Enter an octal value to incicate the data buffer size for the data
test.
The maximum value that x can attain is the number specified
durin~ execution of CMD.
DO YOU WISH TO SPECIFY THE 8LOCK ADCR?

(Y OR N)

Type Y if a particular hlock address is to be specified for testing;
otherwise, type N.
If N is typed, data iR written and/or read in
block 1~0 (octal) through 30C (octal) and the next question asked is
PAT~ERN NO.?
RESPOND ~ITH THE DESIRED BLOCK AD~RESS
Type the desired block address in octal.
PATTERN ~O.?

8-5

OCTAL

TU56S AND TU56D DIAGNOSTIC PPOGRA~S
Select one of the diagnostic program1s prestored patterns or enter the
desired pattern.
To select one of the prestorec patterns type the
number that precedes the desired pattern in the following list.
'" • zeros

1 • ones (177777)
2 - checkerboard

3 • floating ones
4 - random data
5 - count pattern

(full word,

binary,

sequential

for

size

buffer)
6 •

run all patterns

If a user-specified pattern is to
characters and press the RE~UFN key.
WRITE?

specified,

enter

the

octcl

(Y OR N)

Type Y to perform all write operations
inhibit write operations.

WRITE AND/OR READ IN THE FORWARD DIRECTION?

test

tyee

(Y OF N)

Type Y to indicate that read and write operations are to be performed
in a forward direction. Type N to indicate a reverse direction.

8.5

ERROR MESSAGES

The following three error messa~e formats are issued by the TU56S
diagnostic program.
The first two are issued bv the TU56D data
reliability test.
DT ERROR NO.-

FRR followec by an
Refer to Table 8-2.

error

number.

and

Status

TCST-

Contents
Register

TCCl\1-

Contents of Comm~nc! Reqister

TCWC-

Contents of the ~;ord Count Register

TCBA-

Contel"ts
Re<;Jister

FOEWARD}
{ REVERSE

DIRECTION

8-6

Control

the

Bus

Address

TU56S AND TU56D DIAGNOSTIC PROGRA~S
DT ERROR NO.-

ERR followed by an
Refer to Table 8-2.

error

number.

EXPECTEO-

Data expected

RECEIVED-

Data received

DISTANCE INTO BLOCK

·Distance into block before a verify
error
was
encountered.
Count
starts at e.

RETRY NO.-

Which retry attempt has failed

STOP/START TIMING ERROR
The function of the stop/start test is to check the mechanical
movement of the tape.
If hardware errors are detected, the
start/stop test is aborted. ,synchronisation is lost because of
the errors and further testing would be meaningless.

8··7

TUS6S AND TUS6D DIAGNOSTIC PROGRAMS
Table 8-2
TUS6S and TUS6D Error Messages
MEANING

ERROR NUMBER

ASSOCIATED TEST

Start/stop test

A hardware error occurred while
reading the block number in the
forward direction.

Start/stop test

not
A
block number read was
within S blocks of the number of
the previously read block.

Start/stop test

End
of
zone
prematurely.

Start/stop test
(reverse)

A hardware error occurreCi while
reading the block number in the
reverse direction.

Start/stop test
(reverse)

The block number read was not
within S blocks of the number of
the previously read block.

Star.t/stop test
(reverse)

End of zone was
maturely.

Address (part 1)

Rewind failed to detect end zone
or did not set the error bit.

Address (oart 2)

A hardware error occurred while
writing a ')attern of zeros on
block 0 in the forward direction.

Address

A hardware error occurred while
reading block 0 in the reverse
direction or the data was not all
zeros.

Address (part 2)

A hardware error occurred while
readinq block e in the forward
direction or the data was not ell
zeros.

Address (part 2)

occurred while
Po. hardware error
writing blocks 0 and 1 in the
forward direction with a ~attern
of 177777.

Address (part 2)

A hardware error occurred while
readinq blocks 1 and 0 in the
reverse direction or the data
oattern was not 177777.

Address (part 2)

A hardware error occurred while
readina blocks
and 1 in the
forward direction'" or the data
pattern was not 177777.

(~art

8-8

was

reached

pre-

(continued on next page)

TUS6S AND TUS6D DIAGNOSTIC PROGRAMS
Table 8-2 (Cont.)
TUS6S and TU56D Error Messages
ERROR NUMBER

ASSOCIATED TEST

f>1EANING

Address (Dart 2)

A hardware error occurred while
writina blocks 1 and 0 in the
revers~ direction with a
pattern
of 177777.

Address (part 2)

A hardware error occurred while
reading blocks 1 and 0 in the
reverse direction or the data
oattern was not l7777i.

Address (part 2)

A hardware error occurre~ while
read ina blocks r, and 1 in the
forward direction or the data was
not a pattern of 177777.

Address (part

A hardware error occurred while
writina an ood numbered block in
the
forward
direction.
The
nattern
written is the hlock
number.

Address (oart 3)

A hcrdware error occurred while
writinq an even numbere~ block in
tha
reverse
direction.
The
pattern
written is the block
number.

Address (oart 3)

hardware error occurred while
readinq an oed numbered block in
the reverse cirection or the data
pattern read was not the block
number.

Address (part 3)

A hardware error occurred while
reaoinq an even numbered block in
the forward oirection or the data
nattern read was not the block
number.

Address (part 4)

A hardware error occurred while
readino a random hlock or the
data pattern was not the block
numher.

Data test and aeta
test portion of
conversation mode

A hardware
error occurred while
writing the selectp.d pattern on
taoe.

Data test and data
test portion of
conversation mode

A hardware error occurred while
reading the data oattern or the
data is incorrect.

50,

Stop/start test

The tape did not move forward
when a reac was issued to a
forward block number.

(continued on next page)
8-9

TU56S AND TU56D DIAGNOSTIC PROGRAMS
Table 8-2 (Cont.)
TU56S and TU56n Eror Messages
ERROR NUMBER

ASSOCIA'l't:D TEST

MEANING

Stop/start test
(reverse)

The tace did not Jl"Iove reverse
when a read was issued to Q
block number in the reverse
direction.

Conversation mode
for address test

A hardware error occurred when a
comlTl~nd
was issued to block

"A".

Conversation mode
for address test

8-Ie

A hardware error occurred when C!
write command was issued to
block "(I".

CHAPTER 9
TUleSl AND TU16Sl DIAGNOSTIC PROGRAMS

The TU10Sl and the TU16Sl diagnostic proqrams test the positioning
capabilities of the TU10 and TU16 tape drives, respectively. Each
diagnostic program consists of a series of tests that are described
below. The tests for each program are identical.

9.1

REWIND AND BACKSPACE TEST

The rewind -and backspace test ensures that the rewind command leaves
the tape positioned at BOT and that a backspace from BOT also leaves
the tape positioned ~t BOT. -

9.2

WRITE AND READ RECORD TEST

The write and read record test tests the capability of the transport
to write and read a record of either all ones or all zeros. The first
portion of the test is accomplished using the following steps:
1.

From BOT, write a record 'iith a data pattern of 177777,

Rewind the tape,

Read the record,

Rewind the tape and write a data pattern of 000000,

Rewind the tape, read the record, and rewind the tape.

At this point, the second portion of the test executes.
The second
portion ensures that a backspace command does riot creep into the
previous record. This test uses the following steps:

9.3

Write two records with a data pattern of 177777,

Rewrite the second record 100 (octal) times,

Test to determine whether the first record is complete.

END OF RECORD TEST

The end of record test writes 12 (octal) short record, rewinds the
tape, and then reads the records. A short record is 20 (octal) words.
After each read, total shut down of the transport is required.
This

9-1

TU18Sl AND TU16Sl

DIAG~OSTIC

PROGRAMS

process ensures that the gaps are lonq enouqh for shutdown and
startup. The data pattern written is 177777. It is not checked for
data or parity errors.

9.4

EXTENDED RECORD GAP TEST

The extended record gap test performs the following steps:
1.

Write two record with extended record gaps,

Rewind the tape and skip the first record,

Write two records inside the extended gap,

Rewind the tape,

Read four records and check for lost information.

The data pattern written is 177777.
parity errors.

9.5

It is not

checked

for

data

END OF FILE TEST

The end of file test ensures that the transport can write and read an
EOF mark.
It also checks that EOF is detected only as a single byte
record by writing and reading records containing only EOF marks.

9.6

SINGLE-RECORD POSITIONING TEST

The single-record positioninq test writes an EOF and then 63 data
records. The test repeatedly backspace two records and forward spaces
one record. It eventually reaches the point where the next backs~ace
should detect an EOF.

9.7

MULTIPLE-FILE POSITIONING TEST

The multiple-file positioning test uses the tape prepared in the
previous test.
This test positions back and forth across'the tape
starting with the first and endin~ with the last record. It 'decreases
the difference between the starting and ending records until the
difference is 0.
The test then backspaces until the tape is positioned before the EOF
mark.
The next backspace should detect an EOF mark. An EOF mark
detected before or after it is expected is reported as are the nu~ber
of files detected before or after the EOF was expected.

9-2

TU10S1 AND TU16S1 DIAGNOSTIC PROGRAMS
9~8

VARIABLE-LENGTH RECORD POSITIONING TEST

The variable-length record positioning
steps:

performs

the

following

From BOT, writes records of the maximum length specified
during execution of CHO decreasing to 20 bytes in lenqth and
from 20 bytes increasinq to the maximum length in 20 byte
increments.

Checks records for completeness (i.e., no lost data),

Stops the transport before each read.

The data pattern written is 177777.
data errors.

9.9

test

It is not checked for

parity

TEST PARAMETER BIT SETTINGS

In response to the question TEST PARAMETERS, certain bits can be
Table 9-1 lists the bits and provides their meanings.

9--3

set.

TU10S1 AND TU16S1 DIAGNOSTIC PROGRAMS
Table 9-1
TU10Sl and TU16S1 TEST P~RAMETER Bits
BIT

SETTING

MEANING

Stall on error. The task waits up to 30
minutes before exiting.
The stall can be
console
aborted by toggling the
switch
defined at task startup in response to the
question WHICH CONSOLE S\\'ITCH APPLIES FOR
INTERVENTION.

Loop on error. The task loops on the failinq
sequence.
instruction
The loop can be
by
aborted
only
specifying
test
new
parameters with bit 14 equal to 0.

Inhibit printouts except for forced printing.

Ring bell on error. The console bell rings
every time an error is detected in a test
se<;7uence.

Run continuously. The program prints the end
of pass number at completion and then repeats
the specified testing sequence.

Restart the program. The program aborts the
present sequence and restarts at the newly
selected test.

Perform an infinite number
data error recovery.

Perform a maximum
error recovery.

retries

for

data

Print only the first data compare
each data transfer.

error

for

Print up to 3 data compare
transfer.

per

data

9-4

o:f

retries

errors

for

TUleSl AND TU16S1 DIAGNOSTIC PROGRAMS
9.18

ERROR ~ESSAGES

The following error message formats are issued by the TU10S1 and
TUl6S1 diagnostic programs.
Error numbers are used in the message
formats presented in Tabl~ 9-2.

TUle POSITIONING TEST
ERROR NO.-

ERR followed by the error number

RECORD •

number of the record in
error occurred

BYTECOUNT-

number of bytes in the record

MTS-

contents of the Status Register

MTC-

contents of the Command Register

MTBRC-

contents of the Byte Record Counter

MTCMA-

contents of the
Address Register

MTO-

contents of the data buffer

MTRD-

TUl0 read lines

which

the

Memory

Current

TU16 POSITIONING TEST
ERROR NO.-

ERR followed by the error number

RECORD •

number of the record in
error occurred

IBYTECOUNT-

number of bytes in the record

MTSCl-

contents of the Control snd
1 Register

MTWC-

contents of Word Count Register

MTBA-

contents
Register

MTFC-

contents
Register

MTCS2-

contents of Control
Register

and

MTOS-

contents
Register

Drive

MTER-

contents of the Error Register

MTAS-

contents of the
Register

the

which

Unibus

the

Status

Address

Frame

Attention

the

Count

Status

Summary

TUleSl AND TUl6Sl DIAGNOSTIC PROGRAMS
Character

MTCH-

contents
Check

Tape

MTMR-

contents
Register

MTDT-

contents of the Drive Type Register

MTSN-

contents
Register

the

Serial

Number

MTTC-

contents
Register

the

Tape

Control

the

Maintenance

TUle POSITIONING TEST
TUl6 POSITIONING TEST
ERROR NO.-

ERR followed by the error number

EXPECTED-

Data expected

RECEIVED-

Data received

DISTANCE INTO RECORD IN WORDSdistance into record when a
error
was
encountered.
starts at e.

verify
Count

number of bytes in the record

BYTECOUNTTUle POSITIONING TEST

number of times the record was read
to obtain good data

RETRY f-

TUle POSITIONING TEST
ERROR NO.-

ERR followed by the error number

RECORD t-

record in which the error occurred

BYTECOUNT-

number of bytes in the record

CREEP LOSS OF DATA (IN BYTES)number of bytes
transport creepinq

lost

due

MTS-

contents of Status Register

MTC-

contents of Command Register

MTBRC-

contents of the Byte Record Counter

MTCMA-

contents

9-6

the

Current

Memory

TUl~Sl

AND TUl6S1 DIAGNOSTIC PFOGRA~S
Addrress Register
contents of data buffer
contents of TUl0 read lines

HTROTUl6 POSITIONING TEST
ERROR ~O.-

ERR followed by the error number

RECORD t-

record in which the error occurred

BYTECOUNT-

number of bytes in the record

CREEP LOSS OF DATA (IN BYTES)·'
number

trans~ort

bytes
creepinq
of

lost
and

Status

MTCSI-

contents
Reqister

MTWC-

contents of the Word Count Register

MTBA-

contents of Unibus Address Register

MTFC-

contents of Frame Count Register

MTCS2-

contents of RHII Control and Status
Register

HTDS-

contents of Drive Status Register

MTER-

contents of Error Register

MTAS-

contents
Register

MTca-

contents of Tape Character Check

MTMR-

contents of Maintenance Register

MTDT-

contents of Drive Type Register

MTSN-

contents of Serial Number Register

MTTC-

contents of Tape Control Register

control

due

Attention

Summary

TUle POSITIONING TEST
TUl6 POSITIONING TEST
ERROR NO.-

ERR followed by the error number

END OF FILE MARK EARLY BY n RECORDSn indicates the number of records
EOF MISSING
9-·7

TU10S1 AND TU16Sl DIAGNOSTIC PROGRAMS
TUl0 POSITIONING TEST
ERROR NO.-50
END OF FILE MARK NOT DETECTED AFTER WRITE END OF FILE.
MTS-

contents of Status Register

MTC-

contents of Command Register

MTBRC-

contents of Byte Record Counter

MTCMA-

contents of Current Memory Address

MTD-

contents of the data buffer

MTRD-

contents of TUle Read Lines

EOF MISSING
TU16 POSITIONING TEST
ERROR NO.-50
END OF FILE MARK NOT DETECTED AFTER WRITE END OF FILE.
MTCSl-

contents of Control
Register

MTWC-

contents of Word Count Reqister

MTBA-

contents of Unibus Address Register

MTFC-

contents of Frame Count Register

MTCS2-

contents of Control
Register

MRDS-

contents of Drive Status Register

MTER-

contents of the Error Register

MTAS-

contents of the
Register

MTCH-

contents
Check

MTMR-

contents
Register

MTDT-

contents of the Drive Type Register

MTSN-

contents
Register

the

Serial

Number

MTTC-

contents
Register

the

Tape

Control

END OF PASS
9-8

and

Status

and

Status

Attention· Summary

the

Character

TaTJe
the

Maintenance

TUleSl AND TU16Sl DIAGNOSTIC PROGRAMS
TU16 POSITIONING TEST
TU10 POSITIONING TEST
PASS COUNT-

number of this pass

ERROR ENCOUNTERED THIS UNITnumber of cumulative errors
multiple passes

across

NUMBER OF FUNCTIONS ISSUED THIS UNITnumber of
cumulative
functions
performed across multiple passes
NUMBER OF WORDS TRANSFERRED THIS UNITnumber
of
cumulative
words
transferred across multiple oasses
END OF TEST
TASK ABORTED
FROM VIRTUAL PC- .

PC contents

Table 9-2
T010Sl and T016Sl Error Mp.ssages
·ERROR NUMBER

ASSOCIATED TEST

MEANING

Rewind and
backspace

BOT
was
not
detected
completion of the rewind.

Rewind and
backspace

BOT
detected after
was' not
issuing a backspace command from
BOT.

write and read
record (part 1)

A hardware error occurred after a
record fro",
data
BOT.
The
pattern is 177777.

Write and read
record (part 1)

write and read
record (part 1)

occurred after
A hardware error
The
writing a record from BOT.
data pattern is 000000.

write and read
record (part 1)

hardware error occurred after
reading a record from eOT.
The
data pattern is 00e000.

Write and read
record (part 2)

A hardware error occurred after
writinq a record from BOT.
The
data pattern is 177777.

hardware error occurred after
reading a record from BOT or the
data
The data
is incorrect.
pattern is 177777.

(continued on next page)
9-9

TU10S1 AND TU16S1 DIAGNOSTIC PROGRAMS
Table 9-2 (Cont.)
TU10S1 and TU16Sl Error Messages
ERROR NUMBER

ASSOCIATED TEST

MEANING

Write and read
record (part 2)

A hardware error occurred after
writing the second record.
The
data
pattern
for the second
record is ~00e00.

write and read
record (part 2)

occurred while
A hardware error
creeping
record.
writing the
This error loops to writinq the
creepinq recor~.

Write and read
record (part 2)

Data lost due to negative creep.
Printout indicates the number of
bytes lost in the first record.
This error loops to writing the
creeping record.

write and read
record (part 2)

in
The
second
record crept
reverse causing the record gap to
be too short resulting in loss of
data in the second record at
start time. This error loops to
writinq the creeping record.

End of record

An illegal command was detected
durinq a write operation. It is
procably cue to the device going
off line.

End of record

Read of 8-word records with stall
between recoros failed due to
record length error.

Extended
record 'lap

A
hardware error occurred while
writing a recor~ with an extendeci
record gap.

Extended
record gap

A hardware
error occurred while
writinq a record
without
an
extended record gap.

(continued on next page)

9-10

TU18Sl AND TU16Sl DIAGNOSTIC PROGRAMS
Table 9--2 (Cont)
TU10Sl and TUl6S1 Error Messages
ERROR NUMBER

ASSOCIATED TEST

MEANING

Extended
recor~ gap

hardware error occurred while
readinq 4 records. The 2 middle
records were written inside an
extended gap and did not fit
because the gap was too short.
Loop on error causes the program
to loop to the write of records
with extended record gaps.

End of file

A hardware error other than lack
of EOF occurred while writinq end
of file from BOT.
The EOF bit
was cleared in the applicable
by
diagnostic
register
the
program.

End of file

A hardware error
occurred while
reco! :is
with a data
writing
pattern of end of file marks.

End ·of file

EOF was not detected from BOT
when doing a read EOF from BOT.
The first record is EOF.

End of file

EOF was detecte~ at the result of
reading a record with EOF marks
as data.

End of file

A hardware error other than EOF
occurred while reading a record
of EOF data.
The EOF bit was
diaqnostic
cleared
by
the
proqram.

End

file

EOF
detected
when
was not
skipping over an r,OF mark after
readinq records of EOF da ta.

Single-record
position

A
hardware error other than EOF
occurred after writing EOF from
BOT.

(continued on next page)

TUleSl AND TU16Sl DIAGNOSTIC PROG~AMS
Table 9-2 (Cont.)
TU10Sl and TU16Sl Error Messages
i

ERROR NUMBER

ASSOCIATED TEST

r-tEANING

30 1

Single-record
position

A hardware error occurred writinq
short records (20(9) words).·

31 1

Single-record
position

An illeqal command bit was set
durinq a backspace 2 and forward
space
1
operation.
It
is
probably due to the unit going
off line.

Single-record
position

End of file was not detected soon
enough. Backspace 2 and forward
space 1 did not move the tape
backwards one record. The number
of records needed to return to
EOF is reoorted.
The
total
effective . backspace
was
63
records.
No
registers
are

dum~ed.

Single-record
pos{tion

End
of
file
mark at BOT was
detected too early.
Backspacing
2 recoros and forward spacinq 1
moved the tape more than 1 record
back.
The number of record too
early is printeo.
No registers
are dU11'oed.

Multiple-file
positioninq

EOF was not detected when aoinq a
read F.OF from BOT.

Multiple-file
positioning

The illeqal comm~nd bit was set.
The transport ~rohably went off
line durinq multiple record space
commands. .

r-tultiple-file
positioning

End of file was detected too soon
when doinq larqe number skips
forward and backward. The nu~ber
of records too soon is reported.
No registers are dumped •.
(continued on next page)

lLOOP on error causes the test to restart at the point
ERR 30 because the tape position has been lost.
2

described

Loop on error causes the test sequence to beqin at the
described for ERR 34 because the taoe position has been lost.

9-12

for

point

TU10S1 AND TUl6S1 DIAGNOSTIC PROGRAMS
Table 9-2 (Cont.)
TUleSl and TU16S1 Error Messages
ERROR NUMBER

ASSOCIATED TEST

MEANING

Multiple-file
positioning

End of file occurred too late
after multi9le space commands.
The number of records ~issing is
reported.
No
registers
are
dumped.

variable record
length positioninq

A hardware error occurred while
writinq variable-length records.
Loop on error causes the entire
taoe to be rewritten from BOT.

Variable record
An error occurred while reading
record with a
length positioning variable-length
total stop in the ga~. Parity
errors may be an innication that
the tape is flying away from the
head at start time.
Loop on
error
causes the tape to be
reread from BOT.

End of file and
single record
position

A
write EOF operation did not
cause detection of EOF.

202

End of file

A hardware error other than no
EOF occurred after writing EOF
after records containing a data
pattern of EOF marks. The EOF
bit is cleared in the applicable
register
by
the
diagnostic
program.

Loop on error causes the test sequence to beqin at the
described for ERR 34 because the tape position has been lost.

9-13

point

CHAP~rER

TU10S2, TU10D, TU16S2 AND TU16D DIAGNOSTIC PROGRAMS

The TU10S2, TU10D, TU16S2, and TU16D diagnostic programs are data
pattern tests for the TU10 and TU16 tape drives. Each diagnostic
program consists of a series of tel3ts that are described below.
The
TU10D and TU16D data reliability tests are subsets of the TU10S2 and
TU16S2 diagnostic programs.
The TU10S2 and TU16S2 diagnostic programs provide the
tests:

10.1

Record length test,

Lateral parity test,

Longitudinal parity test,

CRC test,

Skew test,

Crosstalk test,

'7.

TU16 burst test,

Data reliability test

following

data

Data pattern tests

RECORD LENGTH TEST (TU10S2 AND TU16S2 ONLY)

The record length test checks the clbility of the transport to sense
when a record is too long or too short. The data pattern written is
177777. It is not checked for correctness.

10.2

LATERAL PARITY TEST (TU10S2 AND TU16S2)

The lateral parity tests check the parity logic by writinq a record
with odd parity and reading it as even parity. Then it writes a
record with even parity and reads it BS odd parity. The data pattern
used is 177777. It is not checked for correctness.

l'~-l

TUI0S2, TUICD, TUl6S2 AND TUl6D DIAGNOSTIC PROGRAMS
le.3

LONGITUDINAL PARITY TEST (TUI0S2 AND TUl6S2 ONLY)

The longitudinal parity test ensures that the longitudinal parity
register works 9rooerly by writing a record that sets all bits in
LPCC.

1~.4

CRC TEST (TUI0S2 AND TUl6S2 ONLY)

The CRC test checks the ability of the unit to calculate
CRC character. Each CRC bit is checked individually.

10.5

the

proper

SKEW TEST (TUI0S2 AND TUl6S2 ONLY)

The skew test writes data pattern designed to detect data errors
caused by tape skew. Two patterns are written. The first is a sine
wave and the second is a bursting pattern.
The data is read and
checked 10 times to expose read reduction problems.

10.6

CFCSSTALK TEST (TUI0S2 AND TUl6S2 ONLY)

The crosstalk test de~ects errors caused by having a 1 bit completely
surrounded by zeros and a ~ bit com?letely surrounded by ones.

10.7

TUl6 BUPST TBST (TUI6 ONLY)

The TUl6 burst test checks the phase encoded burst logic test.
This
test ensures that a burst is written when it is appropriate and that
the burst is properly de~ectable both when it is desired and when it
is not desired.

1008

DATA RELIABILITY TEST (ALL PRCGRAHS)

The data reliability test writes the whole tape in core dump mode if
the drive is 7 track using four ~atterns. The test writes three
records and an EOF mark. It then backspaces and reads each record,
including the EOF mark, 10 times.
On TUl6 transports, the test writes three record and an EOF mark and
then reacs each record, including the EOF mark, 10 times in the
reverse direction instead of backspacing.
The process of reading records continues until EOT is detected.
The
data at EOT is checked 10 times.
The taoe is rewound and the
end-of-pass routine is entered. This routine orints the statistics.

16-2

TUl~S2,

TU10D, TU16S2 AND TU16D DIAGNOSTIC PROGRA~1S

Standard error recovery, as determined by TEST PARAMETERS bit 7, is
used.
The records written are random lenqth.
When errors are
detected, the following information prints on the console:
1.

Read number, if reading,

Byte count,

Record number.

The units digit in the record number indicates what the recore
have contained, as follows:

should

1 and 5 indicate a floating ones and zeros pattern,

2 and 6 indicate random numbers that are negated in alternate
locations,

3 and 7 indicate a count pattern that is negated in alternate
location.

10.9

OPERA'rICNAL INFORfIotATION

Operational information for the TUleS2 and TU16S2 diagnostic ~roqrams
consists of TEST PARAMETER bit settings ana conversation mode usage.
Operational information for the TU1.0D and TU16D data reliability tests
consist only of TEST PARAMETER bit settings.

10.9.1

TEST PARAMETER Bit Setting~

In response to the question TEST PARAMETERS, certain bits can be set.
Table 11-1 lists the bits and provides their meanings. The only TEST
PARAMETER bits that apply to the 'l'U10n and TU16D datfl reliability
tests are 15 through 11 and 9.

10-3

TU10S2,

TUl~D,

TU16S2 AND TU16D DIAGNOSTIC PROGPAMS

Table 10-1
TU10S2, TU16S2, TU10D, and TU160 TEST PAHAMETEP Bits
MEANING

BIT

SET'I'ING

Stall on error. The task waits for UJ:' to 30
The stall can e
minutes before exiting.
switch
console
aborted by toggling the
defined at task startup in response to the
question WHICH CONSOLE S\vITCH APPLIES FOR
OPERATOR INTERVENTION.

Loop on error. The task loops on the failing
The loop can be
seauence.
instruction
test
new
specifying
by
aborted
only
parameters with bit 14 equal to 0.

Inhibit orintouts except for forced printing.

Ring bell on error. The console bell rings
every time an error is detected in a test
sequence.

Run continuously. The program prints the end
of pass number at completion and then repeats
the specified se~uence.

Enter conversation mode.
only. )

Restart the program. The program aborts the
present sequence and restarts at the newly
selected test.

(TU10S2 and

TU16S2

NOTE
From this point, bit settings apply
only to 82 diagnostic programs.
7

for

retries

for

data

T016

data

Perform an infinite number
data error recovery.

Perform a maxill"um
error recovery.

This bit applies only
patterns test (TU16S2).

retries

the

Perform data reliability or conversation mode
for 9-track transports at 800 bpi NRZ.

Perform data reliability or conversation mode
for 9-track transports of 1600 bpi PEe

Print only the first data compare
each data transfer.

error

for

Print up to 3 data compare
transfer.

,Per

cata

Print all errors during error recovery.

errors

(continued on next page)

10-4

TU1BS2, TU10D, TU16S2 AND TU16D DIAGNOSTIC PROGRAMS
Table 1,0-1 (Cont.)
TU10S2, TU16S2, TU100, an.d TU160 TEST PARAMETER Bits
SETTING

BIT

MEANING

Print only the first error during error
recovery.
At completion of error recovery,
print the error recovery type retry number.

Perform the read portion
slice aajustment.

Perform the data reliability test.

Perform the pattern test.

10.9.2

Conversation Mode (TU10S2 and TU16S2 Only)

write/read

amp

Conversation mode is reauested by setting TEST PARAMETER bit 10.
Conversation mode provides two tests that are not related to the data
pattern or reliability tests. The two tests are the compability test
and the write/read amplifier slice amplifier adjustment test.

19.9.2.1 Compatibility Test - The! compatibility test
allows
the
operator to wrlte a tape to be read on other transportd or to read a
tape written on another transport.
The following questions are
printed on the console.
WANT COMPATIBILITY TEST?

OR <CR»

Type Y to request the compatibility test.
slice adjustment test, described below.

Press RETURN to request the

WHICH COMPATIBILITY TEST (0 == ~'lRI'IE & READJ

1 == READ ONLY)

Type 9 to write the magnetic tape and then read it.
rpints the following message when the tape is written.

The

program

Type 1 to read the compatibility tape mounted on the selected device.
COMPATIBILITY TAPE WRITTEN - VERIFYING TAPE
During the read portion of the test, all data and hardware errors are
reported.
When the tape has been completely read, the test types the
following message.
COMPATIBILITY TAPE VERIFIED

10-5

TU10S2, TU10D, TU16S2 AND TU16D DIAGNOSTIC PROGRAMS
10.9.2.2 write/Read Am~lifier Slice Adjustment Test - The following
auestions are prlnted on the console for the write/read amplifier
adjustment test.
WANT COMPATIBILITY TEST?

(Y OR <CR»

Press RETURN to obtain the questions for the slice
Typing Y causes the Compatibility test to run.

adjustment

test.

Type Y. Pressing RETURN causes the question WANT COMPATIBILITY
to be repeated.

TEST?

WAN'!' SLIDE ADJUSTMENT?

l0.l~

(Y OR <CR»

ERROR MESSAGES

The following message formats are issued by the TU10S2 and TU16S2
diagnostic programs. The TU10D and TU16D data reliability test issues
a subset of this list. Error numbers are listed in Table 10-2.
TU10 DATA PATTERN TEST
ERROR NO.=

ERR followed by the error number

RECORD #

number of the record in which the error occurred

BYTE COUNT=

number of bytes in the record

MTS=

contents of Status Register

MTC=

contents of Command Register

'MTBRC=

contents of Byte Record Counter

f.tTCMA=

contents of the Current Memory Address Register

MTD=

contents of the Data Buffer

MTRD=-

contents of TU10 Read Lines

READ NUr.u~ER=

number of times the record has been read

TU16 DATA PATTERN TEST
ERROR NO.=-

ERR followed by the error number

RECORD #

number of the record in which the error occurred

BYTECOUNT=

number of bytes in the record

1-1TSC1=

contents of the control and status 1 register

MTWC=

contents of Word Count Register

MTBA=

contents of the Unibus Address Register

MTFC=

contents of the Frame Count Register

10-6

TUI0S2, TUI0D, TUl6S2 AND TUl6D DIAGNOSTIC PFOGRAMS
~!TCS2-

contents of RBII Control and Status 2 Register

MTDS=

contents of the Drive Status Register

ltlTER=

contents of the- Error Register

MTAS-

contents of the Attention Summary Reqister

f.lTCB=

contents of the Tape Character Check

MTMR=

contents of the' Maintenance Re9ister

MTDR=

contents of the' Drive Type Register

fttTSN-

contents of the' Serial Number Register

MTTC=

contents of the! Tape Control Register

TU16 DATA RELIABILITY TEST
TU10 DATA RELIABILITY TEST
TUl6 DATA PATTERN TEST
TUle DATA PATTERN TEST
UNIT f

number of the unit on which the error occurred
(Reliability test only)

ERROR NO.-

ERR followed by the error number

EXPEC'I'ED=

data expected

RECEIVED-

data received

DISTANCE INTO RECORD IN WORDS::
distance into record before a verify
encountered. Count starts at 0.
RECORD #

Record in which the error occurred

READ NUMBER-

number of times the record has been read

BYTE COUNT=

number of bytes in the record

error

TUl0 DATA PATTERN TEST
TUle DATA RELIABILITY TEST
UNIT #

number of unit on which the error occurred
(Reliability test only)

ERROR NO. = 50
EOF NOT DETECTED AFTER WRITE EOF

11~-7

was

TU10S2, TU10D, TU16S2 AND TU16D DIAGNOSTIC PFOGRAMS
RECORD #

number of the record in which the error occurred

BYTE COUNT=

number of bytes in the record

MTS=-

contents of status register

MTC=-

contents of the Commanc Register

MTBRC=-

contents of the Byte Record Counter

f.ITMCA-

contents of the Current Memory Address Register

MTD=-

contents of the Data Buffer

MTRD=

contents of the TU10 Read Lines

READ NUMBER -

number of times the record has been read

TU16 DATA RELIABILITY TEST
TU16 DATA PATTERN TEST
UNIT #

number of the unit on which the error occurred
(Reliability test only)

ERROR NO. - 50
EOF NOT DETECTED AFTER WRITE EOF
RECORD #

number of the record in which the error occurred

MTSCl-

contents of the Control and Status 1 Register

MTWC=

contents of Word Count Register

MTBA=

contents of the Unibus Address Fegister

MTFC=-

contents of the Frame Count Register

MTCS2-

contents of Control and Status 2 Register

MTDS-

contents of the Drive Status Register

MTER=-

contents of the Error Register

MTAS=

contents of the Attention Summary Register

MTCH-

contents of the Tape Character Check

MTMR=

contents of the Maintenance Register

14TDT=

contents of the Drive Type Register

MTSN=

contents of the Serial Number Register

MTTC=

contents of the Tape Control Register

TUl~

DATA PATTERN TEST

10-8

TU19S2, TU1eo, TU16S2 AND 1,'U16D DIAGNOSTIC PROGRAMS
TUle DATA RELIABILITY TEST

UNIT # number of unit on which the error occurred
(Reliability test only)
ERROR NO.-S1
EOF NOT DETECTED AFTER READ
RECORD # number of the record in which the error occurred
BYTE COUNT- number of bytes in the record
MTS- contents of status register
MTC- contents of the Command Register
MTBRC- contents of the Byte Record Counter
MTCMA- contents of the Current Mefflory Address Register
MTD- contents of the Data Buffer
MTRD~

contents of the TU10 Read Lines

READ NUMBER- number of times the rec!ord has been read

TU16 DATA RELIABILITY TEST
TU16 DATA PATTERN TEST

UNIT. number of the unit on which the error occurred
(Reliability test only)
ERROR NO.-S1
EOF NOT DETECTED AFTER READ EOF
RECORD' number of the record in which the error occurred

10-9

TU10S2, TUlaC, TU16S2 AND TUl6D DIAGNOSTIC PROGRAMS
MTSCl- contents of the Control and Status 1 Register
MTWC- contents of Word Count Fegister
MTBA- contents of the Unibus Address Register
MTFC= contents of the Frame Count Register
MTCS2- contents of Control and Status 2 Register
MTDS= contents of the Drive Status Register
MTER- contents of the Error Register
MTAS= contents of the Attention Summary Register
MTCH- contents of the Tape Character Check
MTMR= contents of the Maintenancee Register
MTDT- contents of the Drive Type Register
MTSN= contents of the Serial Number Register
MTTC= contents of the Tape Control Register

TU10 DATA RELIABILITY TEST
TUle DATA PATTERN TEST

UNIT # number of the unit on which the error occurred
(Reliability test only)
ERROR NO.= ERR followed by the error number
RECORD t number of the record in which the error occurred
BYTE COUNT- number of bytes in the record
MTS- contents ot status register

TU10S2,

TUl~D,

TU16S2 AND TU16D DIAGNOSTIC PROGRAMS

MTC= contents of the command register
MTBRC- contents of the byte record counter
MTCMA- contents of the current memory address .register
MTD- contents of the data buffer
MTRD- contents of the TU10 read lines

TU16 DATA RELIABILITY
TU16 DATA PATTERN TEST

UNIT

* number of the unit on which the error occurred

(Reliability test o~ly)
ERROR NO.- ERR followed by the error number
RECORD # number of the record in which the error occurred
BYTECOUNT- number of bytes in the record
MTSCl- contents of the Control and Status 1 Register
MTWC- contents of Word Count Register
MTBA- contents of the Unibus Address Fegister
MTFC- contents of the Frame Count Register
MTCS2- contents of Control and Status 2 Register
MTDS- contents of the Drive Status Register
MTER- contents of the Error Register
MTAS- contents of the Attention Summary Register
MTCH- contents of the Tape Character Check

10-11

TU10S2, TU10D, TU16S2 AND TU16D DIAGNOSTIC PROGRAMS
MTMR=- contents of the Maintenance Register
MTDT=- contents of the Drive Type Register
MTSN= contents of the S~rial Number Register
MTTC=- contents of the Tape Control Register

TU10 DATA PATTERN TEST
TU16 DATA PATTERN TEST

ERROR NO.=- ERR followed by the error number
CRC ERROR
EXPECTED- CRC expected
RECEIVED- CRC received

TU10 DATA PATTERN TEST
TU16 DATA PATTERN TEST

ERROR NO.- ERR followed by the error number
LPCC ERROR
EXPECTED- LPCC expected
PECEIVED- LPCC received

10-12

TUl0S2, TU10D, TU16S2 AND TU16D Dr" GNOSTIC PROGRAMS
Table 10-2
TUl0S2, TU16S2, TU10D, and TUl6D Error Messages
ERROR NUMBER

ASSOCIATED TEST

MEANING

Record length

A hardware error occurred while
writing a l000-byte record with a
data pattern of 177777.

Record

length

A
record is too short;
the
requested record was 2000 bytes.
However, if the byte count or
word count registers indicate a
proper negative"number (-10ee for
TUl0 or -40~ for TU16), the error
is other than receiving too-short
record.
Check the -applicable
error reqister bits.

Record length

A record length error was not
detected when the byte count went
to zero and 1 byte remained to be
read.
This message applies only
to TUl0 transports.

Record length

The record length error was set
when it should have been, but
other hardware-detected
errors
occurred.
This messaqe applies
only to the TUl0 transport.

Lateral parity

A hardware error occurred while
writing odd parity from BOT.

Lateral parity

Reading an odd ~arity record with
even
parity did not force a
parity error.

Lateral parity

The parity error bit was set
after
reading
an odd parity
record
as
even,
but
other
hardware errors were detected.
The parity error bits are cleared
by the program.

Lateral parity

A hardware error
writing an even
from BOT.

occur 'red when
parity record

Reading an even parity record as
odd parity failed to generate a
hardware oarity error.
(continued on next page)

lTUl6 is running at 8~0 BPI NRZ.

10-13

TU10S2, TU10D, TU16S2 AND TU16D DIAGNOSTIC PROGRAMS
Table 10-2 (Cont.)
TU10S2, TU16S2, TU10D, and TU16D Error Messages
MEANING

ERROR NUMBER

ASSOCIATED. TEST

121

Lateral parity

The parity error bit was set
reading an even parity
after
record as odd, but other hardware
errors were detected. The parity
error bits are cleared by the
program.

13 1

Longitudinal
parity

A hardware error occurred while
writing an odd number of bytes.

141

Longitudinal
parity

When reading a record with an odd
number of bytes, a hardware error
parity
error
other
than
a
occurred.

151

Longitudinal
parity

correct.
LPCC
not
The
is
expected LPCC and that received
are printed on the console.

16 1

CRC

A hardware error occurred while
writing
the
CRC
test.
The
pattern written is 20 (octal)
bytes long and contains all zeros
except for word 2.

171

CRC

A hardware error other than CRC
error occurred while reading the
CRe record. The CRe error bit is
cleared by the program •

. 20 1

CRC

The CRC is incorrect.
The CRC
expected and that received are
printed on the console.

211

Skew

A hardware error oC'curred
writing the skew record.

221

Skew

A hardware error occurred while
reading skew records. Check the
electrical skew of the drive.
Note
the
reread counter for
possible read reduction caused by
a bad head or a magnetized head
partially erasing data during the
read.

while

(continued on next page)

ITU16 is running at 800 BPI NRZ.

10-14

TU1092, TUleD, TU16S2 AND TU16D DIAGNOSTIC PROGRAf.1S
Table 10-2 (Cont.)
TU10S2, '1'U16S2, TU10D, and TU16D Error Messages
ERROR NUMBER

ASSOCIATED TEST

MEANING

Crosstalk

A hardware error occurred while
writing
the crosstalk pattern
tape.

Crosstalk

A hardware error occurred while
reading the crosstalk pattern.
Check for head wear or
data
reduction caused by the partial
erasure of the tape during the
read operation.
-

TU16 burst
test

The ID burst was not detected
after a write from BOT. Loop on
error causes the test to begin
with this function.

TU16 burst
test

A write
at 800 BPI
from BOT
detected an ID burst.
The ID
burst should be cleared during a
write from BOT NRZ recording.
Loop on error causes the test to
begin with the function described
in error 25.

TU16 burst
test

Reading an NRZ tape as a PE tape
causes an
10
burst
to
be
detected. This error probably is
caused by a write function not
erasing the 10 during an NRZ
write from BOT.
Loop on error
causes the test to begin with the
function described in error 25.

Data reliability

A hardware error occurred during
the data reliability test. Check
the record number for the pattern
type and the console printout for
record size.

Data reliability

A hardware error occurred while
reading reliability test tape or
the data is incorrect. Check the
record
number
for
the data
pattern. Check the read number
for data reduction on successive
reads.
(continued on next page)

lTU16 is running at 800 BPI NRZ.

10--15

TU10S2, TU10D, TU16S2 AND TU16D DIAGNOSTIC PROGRAMS
Table 10-2 (Cont.)
TU10S2, TU16S2, TU10D, and TU16D Error Messages
ERROR NUMBER.

ASSOCIATED TEST

MEANING

TU16 data
reliability

A
hardware error occurred when
reading the reliability record in
the reverse direction or the data
is incorrect. Check the record
number for data pattern. Check
the
read
number
for
read
reduction.

Data reliability
and conversation
mode

A write EOF operation did not
detect an EOF mark. This error
is not looped on even if loop on
error is set.

Data reliability
and conversation
mode

A
skip
over EOF operation did
not detect an EOF mark. write
EOF should set the EOF bit in the
applicable register. The bit is
not set.
This error is
not
looped on even if loop on error
is set.

101

Conversation
mode

A hardware error occurred while
writing 16 records. Each record
contains 32 words of floating l's
pattern.

102

Conversation
mode

A hardware error occurred while
writing 64 records. Each record
contains 64 words of all ones
data pattern.

103

Conversation
mode

A hardware error occurred while
writing 64 records. Each record
contains 64 words of all zeros
data t;>attern.

104

Conversation
mode

A hardware
error occurred while
writing 128 records. Each record
contains
256 words of random
data.

105

Conversation
mode

A hardware error occurred while
writing 64 records. Each record
contains
512 words of random
data.

106

Conversation
mode

A hardware error occurred while
writing 64 records. Each record
contains le24 words of random
data.

(continued on next page)

10-16

TU10S2, TU10D, TU16S2 AND TU16D DIAGNOSTIC PROGRAMS
Table 10-2 (Cont.)
TU10S2, TU16S2, TU10D, and TU16D Error Messages
ERROR NUMBER

ASSOCIATED TEST

MEANING

107

Conversation
mode

A hardware error occurred while
writing 32 records. Each record
contains 1536 words of random
data.

110

Conversation
mode

A hardware error occurred while
writing 32 records. Each record
contains 2048 words of random
data.

111

Conversation
mode

A hardware error occurred while
reading 16 records that are 32
words in length and contain a
data pattern of floatinq l's.

112

Conversation
mode

hardware error occurred while
reading 64 records that are 64
words in length and contain all
zeros.

113

Conversation
..
mode

hardware error occurred while
reading 64 records that are 64
words in length and contain all
zeros.
A

ll~

Conversation
mode

A hardware error occurred while
reading 128 records that are 256
length and contain
words
in
random data.

115

Conversation
mode

A hardware error occurred while
reading 64 records that are 512
words
length and contain
in
random data.

116

Conversation
mode

A hardware error occurred while
reading 64 records that are 1024
length and contain
words
in
random data.

117

Conversation
mode

A hardware" error occur"red wh ile
reading 32 records that are 1536
words
length and contain
in
random data.

120

Conversation

A hardware error occurred while
reading 32 records that are 2048
contain
words in length
and
random data.

10-17

CHAPTER 11
TTYTS DIAGNOSTIC PROGRAM

The TTYTS diagnostic program tests the ASR33, ASP-35,
terminals. The program performs the following tests:
1.

Carriage return test,

S~ace

Tab test,

Line feed test,

Character test,

Worst case test pattern for ASR33 and ASR35

User-selected test pattern.

11.1

LA30

VT05

test,

CARRIAGE RETURN TEST

The carriage return test checks the ASR33, ASR35, and LA30
as one group and checks the VT05 with a separate test.

11.1.1

and

terminals

ASR33, ASR35, and LA30 Carriage Return Test

The carriage return for the ASR33, ASR35, and tA30 checks the ability
of the carriage to return correctly 'to print position zero from ev~ry
other print position. The program first prints a backslash ('> and
then spaces to the other end of the carriage. A carriage return
command is issued and then the program prints a slash C/) in print
position zero.
It then prints a ' to form an X ana spaces to one
position short of the end of the carriage. This sequence is continued
from every print position. When the test is comoleted, an X should be
present in print position zero.

11.1.2

VT05 Carriage Return Test

The VT05 carriage return test checks the ability of the display to
return correctly to print position zero from every other print
position. The ~rogram dis~lays a line of 72 asterisks (*) and then
issued a carriage return and line feed command. This seauence is
repeated with the-number of asterisk diminishec by one for each line
displayed until the count reached zero. See Figure 11-1 for an image

11-1

TTYTS DIAGNOSTIC PROGRAM
of the asterisk oattern displayed.

**********************************************************************
*********************************************************************
********************************************************************
*******************************************************************
******************************************************************
*****************************************************************
****************************************************************
***************************************************************
**************************************************************
********************************************************.*****
************************************************************
***********************************************************
**********************************************************
*********************************************************
********************************************************
*******************************************************
******************************************************
*****************************************************
****************************************************
***************************************************
**************************************************
*************************************************
************************************************
***********************************************
**********************************************
*********************************************
********************************************
*******************************************
******************************************
*****************************************
****************************************
***************************************
**************************************
*************************************
************************************
***********************************
**********************************
*********************************
********************************
*******************************
******************************
*****************************
****************************
Figure 11-1
VT05 Carriage Peturn Test Display
(Partial Display)

11-2

TTYTS DIAGNOSTIC PROGPAM
11.2

SPACE TEST

The space test treats the ASR33, ASr3S, and
provides a separate test for the VT~5.

11.2.1

LA30

one

group

and

ASR33, ASR35, and LA30 Space Test

The space test for the ASR33, ASR3S, and LA30 checks the ability of
the printer to space correctly. The test first prints backslashes (\)
in alternate print positions starting at print position zero. It then
spaces to position zero and prints slashes in the blank positions-2.
See Fiqure 11-2.
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
\/\/\/\/\/\/\/\/\/\/\/
Figure 11-2
ASR33, ASR35, and LA30 Soace Test

11.2.,2

VT0S Space Test

The VTeS space test verifies that the VT0S can space correctly.
The
pattern displayed if the terminal spaces properly is shown in Fiaure
11-3.

*. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * *. * * * * * * * * * * * * * * • * * * * * * * * * * * * * * *
• * * * * * * • * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * • * * * * * * * * * * * * * * * * * * * * * *
Figure 11-3
VT05 Spac:e Test

11.3

TAB TEST

The tab test checks the ability of the ASn33, ASR3S, and LA 3~
printers and the VT05 display to tab to a tab position that is from
one through seven character positions away from the current head
position.
The first line printed marks the tab positions.
The second line
printeed tabs from one tab stop to the next. After that, each line
has an additional character nrinted after the slash (/).
The last
line has six spaces printed after the slash. Figure 11-4 illustrates
the output from this test.

11--3

TTYTS DIAGNOSTIC PROGRAM

/
/
/
/
/
/
/

/
/

/
/
/
/
/

/
/

/
/
/
/
/

/
/
/
/

/
/

/
/
/
/
/
/
/

Figure 11-4
Tab Test Output

11.4

LINE FEED TEST

The line feed test checks the ability of an ASR33, ASR35, LA36, or
VT05 to perform a line feed. A correctly performed test appears as a
diagonal line printed (displayed) between 9rint position 0 and print
position 72.

11.5

CHARACTER TEST

The character test prints (displays) a line containing a repetition of
three character. The first line consists of the characters AEC: . the
second line consists of DEF, and so on until a line of the characters
789 is printed. Then, the special characters are printed with three
characters on each line as follows.

!"I
$%&
NO

*+,
-./

: ;<

->?
@(\
]

11.6

ASR33 WORST CASE PATTERN TEST

The ASR33 worst case pattern test prints 10 lines of the
case pattern. The pattern is shown below.

ASR33

worst

ASR35

worst

• w/W

11.7

ASR35 WORST CASE PATTERN TEST

The ASR35 worst case pattern test prints 10 line of
case pattern. The pattern is shown below.
N(?C?[

11-4

the

TTYTS DIAGNOSTIC PROGRA~1
11.8

USER-SELECTED PATTERN TEST

The user-selected pattern test is an aid in making teleprinter
adjustments.
The program perrnists the user to type in five test
characters. It then prints successive lines containing the five
selected characters.
The characters used for this test must be
printable characters. When sgecifyinq the characters to be printed,
terminate the line by pressing RETUPN.

11.9

TEST PARAME~FR BIT SETTINGS

Certain bits can be set in response to the question TEST
Table 11-1 lists the bits and provides their meaning.

11·-5

PARAMETERS.

TTYTS DIAGNOSTIC PROGRAM
Table 11-1
TTYTS TEST PARAMETER Bits
BIT

SETTING

MEANING

Stall on error. The task waits
up to 30 minutes before
for
can
be
The
stall
exiting.
aborted by toggling the console
switch defined at task startup in
response to the question WHICH
FOR
SWITCH
APPLIES
CONSOLE
OPERATOR INTERVENTION.

Loop on erro'!. The task 100DS on
the failing instruction seauence.
The loop can be aborted only by
specifying new test parameters
with bit 14 equal to 0.

Inhibit printouts
forced printing.

Ring bell on error. The console
bell rinqs every time an error is
detected in a test sequence.

The -program
Run continuously.
prints the end of pass number at
completion and then repeats the
specified seauence.

Restart the program. The program
aborts the present sequence and
restarts at the newly selected
test.

LA30

VT05

ASR35

·ASR33

Run all tests.

2,1,0

0"0

Carriage return test:

001

Space test

010

Tab test

011

Line feed test

1('10

Character test

101

ASR33 worst case test

IlA

ASR35 worst case test

111

User-selected oattern test

11-6

except

for

CHAPTEF 12
RK06S AND RK06D USER ~ODE DIAGNOSTIC PROGRAMS

The RK06S diagnostic program and the RK06D data reliability program
are the two hardware tests for the RK06 disk cartridge. The RK06D
data reliability test is a subset of the RK06S diagnostic program.
The RK06S diagnostic program provides four disk tests:
1.

Address test

Data test

Random test

Formatter test

The RK06D data reliability test provides a data test only.

12.1

ADDRESS TEST (RK06S ONLY)

The address test consists of six parts:
- cylinder test 1,
- cylinder test 2,
- sector addressing test,
- track/head addressing test,
- write/read cylinder spirraling test,
- partial sector write test.
Descriptions of these tests follow in this section.

12.1.1

Cylinder Test 1

This is an incremental seek test, in which a read-header command
(implied seek) alternately addresses cylinder 0 and cylinder "N": the
valtie of "N" starts with 1 and is incremented by 1 for each seek,
through the range 0-416.
After each seek, the diagnostic program
compares the contents of the RKDC register with the current header
data to verify that the specified cylinder address was found.

12-1

RK06S AND RK06D USER MODE DIAGNOSTIC PROGRAMS
12.1.2

Cylinder Test 2

This is a cross-seek test, in which a read-header command (implied
seek) alternately addresses cylinder "A", which is initially 0~ and
cylinder "B", which is initially 4lf.
After each seek, "A" is
incremented by 1 and "B" is decremented by 1. This continues until
"Bft equals 0. Cyclinder positioning is verified by comparison of the
RCDC register contents with the current header data after each seek.

12.1.3

Sector Addressing Test

This routine verifies that each sector from ~ to 21 is addressable.
The test issues a full 256-word write (made up of the 2-word address
pattern: sector number and its complement) into each sector on track
o of cylinder 0, followed immediately by a write-check function. If a
marked bad sector is encountered, its address is saved in the bad
sector table for later validation. If an error is encountered, it is
reported to the operator.
Once the entire track has been accedded, each sector is read and the
full 256 words of data are compared, if necessary, in an attempt to
match the expected 2-word address pattern.

12.1.4

Track/Head Addressing Test

This test verifies that each track from 0 to 2 is addressable.
The
routine issues full 256-word writes (made up of the 2-word address
pattern: track number and its complement) into sector ~ on track 0,
1, and 2 of cylinder 0, followea immediately by a write-check
function. If an error is encountered, it is reported to the operator
immediately.
If sector 0 on any of the tracks happens to be marked bad sector, its
address is saved in a core resident bad sector table for later
validation.
Once all the tracks on the cylinder have been accessed, sector 0 of
each track is read and the full 256 words of data are compared, if
necessary, in an attempt to match the expected 2-word track address
pattern.
The sector is then rewritten with its address pattern and
the next track is accessed.

12.1.5

write/Read Cylinder Spiraling Test

This test ensures that each cylinder is addressab~e and that the
device will update to the next cylinder if a transfer crosses cylinder
boundaries. The test starts by issuing a 2-sector write to the last
sector on the last track of each cylinder. The pattern used is the
2-word cylinaer address pattern: cylinder number and its complement
number.
Then, starting with sector ~ on track 0 of cylinder 1, the
sector is read and the address pattern is verified. This is done for
each subseguent cylinder.
.
The procedure verifies that the
properly for write/read operations.

12-2

crossover

logic

functionin9

RK06S AND RK06D USER MODE DIAGNOSTIC PROGRAMS
12.1.6

Partial Sector Write Test

This test ensures that the RK6ll can zero fill the remainder of a
sector on a partial sector write" Sector e on track 0 of cylinder e
(or the first good sector on the cylinder) is written with a pattern
of all ones (177777). Then a pclrtial write of two words of ones is
issued to the same disk address. The sector is then read and its
contents are checked to detemine if all of the sector except the first
two words has been filled with zeroes.

12.2

DATA TEST

During execution of the data test, write, write-check, and read
operations are performed. The data is written on the entire cartridge
disk and then read back. The data buffer is cleared before each read.
The data is verified and any errors are reported.
If an error is detected during a read operation, an attempt is made to
correct it with an ECC correction algorithm. If this is unsuccessful,
four retries are attempted. If the data still cannot be read, the
heads are h~med and four more retries are attempted.
The disk surface is tested with the

followin~

patterns:

All zeroes

All ones

Checkerboard (alternate ones and zeroes)

Floating one~
each word)

Random data

Count pattern (sequential, binary,
size of buffer)

(sequenced

bit-position

In data test conversation mode, described in
above patterns may be selected for test
pattern may be specified.

advancement

full-word

count,

through

12.5.2.2, one of the
use, or a user-supplied

The size of the transfer is 512 (decimal) words.

12.3

RANDOM TEST

The random test consists of the writing and readinq of randomly
generated data patterns to randomly selected disk add~esses. The size
of the data transfers are generated randomly~ however, they will not
exceed 512 words.
This write/read sequence is repeated 512 times.
The program ensures that no data is written on the bad sector block
(sectors e-21 on cylinder 410, track 2).
Each write operation is followed immediately by a verification pass,
which consists of an explicit seek operation to another randomly
selected disk address, followed by reading and checking of the data.
This seek/read sequence is repeated eight times in an attempt to
detect read reduction problems or parity errors causes by a vibratinq
head.

12-3

RK86S AND RK86D USER MODE DIAGNOSTIC PROGRAMS
If an error is detected, the read number is typed to show which read
was being performed when the error occurred. Four more attempts are
then made to read the data.

12.4

FORMATTER (RK86 ONLY)

This routine formats the RK06 cartridge disk by writing
format for every (non-reserved) sector on the disk.

the

header

Prior to formatting, the routine reads the manufacturing bad sector
block to obtain the addresses of any sectors that were found to be
unreliable during the manufacturing process. The disk area reserved
for this block extends from sector 8 throuah sector 9 on the last
track of the last cylinder (track 2 of cylinder"4l0).
The formatter
routine marks each disk sector "good" or "bad" in accordance with any
addresses contained on the manufacturing bad sector block.
Sectors
marked as "bad" in this manner do not interfere with disk operations
and do not produce errors during formatting.
Sector headers are written one track at a time.
formatted, the routine will output the message:

If a sector cannot be

UNABLE TO FORMAT ONE OR MORE SECTORS ON THE FOLLOWING TRACK
(Track address)
(Cylinder address)
~ormally, the inability to format one, or several, sectors on a
will not affect the operating capability of the cartridge disk.

track

When formatting is complete, the routine will output the message:
**FORMATTING COMPLETE**

12.5

OPERATIONAL INFORMATION

Operational information for the RK86S and RK86D diagnostic and data
reliability program is entered through Test Parameter bit settings and
through conversation-mode responses. Conversation mode is handleo by
the RK06S routines.

12.5.1

TEST PARAMETER Bit Settings

In response to the TEST PARAMETERS prom~ting, the us~r can set certain
parameter bits.
The associated switches, bit settinqs, and meanings
are listed in Table 12-2.
Bits 18, 3, 2, 1, and" relate only to the RK86S routines:
Bit
10

enter conversation mode (RK06S only)

formatter test (RK06S only)

12-4

RK06S AND RK06D USER MODE DIAGNOSTIC PROGRAMS

12.5.2

random test (RK66S only)

(bit 1 and bit 10 set) data
only)

(bit 0 and bit 10 set) address test/conversation mode (RK06S
only)

test/conversation

mode

(RKA6S

Conversation Mode

When conversation mode is requested by setting bit 10 in response to
the TEST PARAMETERS prompting, a series of questions is printed at the
console.
Two versions of conversation mode are provided with the
RK06
diagnostic program.
One specifies information for the address test
and one specifies information for the data test.

12.5.2.1 Address Test Conversation Mode - Conversation mode for the
address test allows the operator to specify two cylinder addresses.
The program then issues seek commands between the specified cylinders.
Any errors encountered,are reported to the operator.
Once started, this program
operator.

continues

12-·5

until

aborted

the

RK06S AND RK06D USER MODE DIAGNOSTIC PROGRAMS
Table 12-1
RK06S ana RK06D TEST PARAMETER Bits
r-1EANING

BIT

SETTING

Stall on error. The diagnostic task waits up to
30 minutes before exiting. The user can abort the
stall by setting the console switch selected for
intervention. This is the console switch defined by the answer to the question (WHICH CONSOLE SWITCH APPLIES FOR OPERATOR INTERVENTION?)
that is typed at task startup.

Loop on error. The diagnostic test routine loops
on the failing instruction sequence. To abort
the loop, the user must intervene, then specify
new test parameters in which bit 14 is equal to O.

Inhibit printouts except for forced printing.

Ring bell on erro~. The console bell rings every
time an error is detected in a test sequence.

Run continuously. The program prints the end of
pass number at completion and then repeats the
testing sequence.

Enter conversation mode. Refer to Section 12.5.2
(RK06S
for a description of conversation mode.
only)

Restart the program. The program aborts the present test sequence and starts at the newly selected
test.

Print only the first data-compare error found
within a specified data transfer.

Print up to 3 data-compare errors within a specified data transfer.

Inhibit seek operation between successive reads
during the random test.

Formatter (RK06S only)

Random test (RK06S only)

Data Test/Conversation Mode (RK06S)

Address Test/Conversation Mode (RK06S)

12-6

RK96S AND RK06D USER MODE DIAGNOSTIC PROGRAMS
The program requests the two cylinder addresses as .follows:
"A" CYLINDER?
Enter a valid cylinder address in octal.
"B" CYLINDER?
Enter a valid cylinder address in octal.

12.5.2.2 Data Test Conversation M2~ - In conversation mode for the
data test, the operator can specify the data transfer size, the disk
surface address, the pattern desired, and the function to
be
performed, writes, reads, or writes and reads.
The following prompts/questions are printed by the program:
WORD COUNT 2 TO X
Enter an octal value to indicate the data buffer size for the data
test.
The maximum value that can be entered for X is the number
specified during the execution of CMD.
DO YOU WISH TO SPECIFY A DISK SURFACE ADDRESS (Y OR N)?
Type Y to indicate that a particular surface
specified for testing, otherwise, type N.

address

If N is typed, the entire disk surface, with the exception of the bad
sector block, will be read and/or written, the ~rogram will reauest
the pattern to be used by immediately typing:
DATA PA'l'TERN NO. =

CYLINDER
Type the desired cylinder address
address is 631 (octal) •

octal.

The

maximum

patterns

cylinder

TRACK
Type the desired track number in octal.
SECTOR
Type the desired sector number in octal ..
DATA PATTERN NO.a
Select one of the diagnostic
user-supplied pattern.

program's

enter

To select one of the prestored -patterns, type the number that precedes
the desired pattern in the following list:

all zeroes

all ones

12-7

RK06S AND RK06D USER MODE DIAGNOSTIC PROGRAMS
2

checkerboard (alternate ones and zeroes)

floating ones
each word)

random data

count pattern (a sequential, binary, full-word
size of buffer)

run all prestored patterns

(sequenced

bit-position

advancement

through

count

If a user-supplied pattern is to be specified, enter
characters for the pattern, then press the RETURN key.

octal

WRITE (Y OR N)?
Type Y to perform all write operations
inhibit write operations.

the

test

type

READ (Y OR N)?
Type Y to perform all read operations in the test or type N to inhibit
read operations.
NOTE
The operator must answer Y (Yes) to at
least one of the READ/WRITE? Questions.

12.6

ERROR MESSAGES

Error messages are output in one of three formats, as shown below.
The 'name of the diagnostic routine (RK06S or RK06D) that outputs the
error message will appear on the first line in each format. Refer to
Table 12-2 for error-message numbers and descriptions.

12-8

RK86S AND RK86D USER MODE DIAGNOSTIC PROGRAMS
Format 1
ERROR NO.-

ERR followed by the error number

RKCS1-

contents of the Control and
1 register

RKWC-

contents of the Word Count register

RKBA-

contents
register

RKDA-

contents of the Track
Address register

and

Sector

RKCS2-

contents of the Control and
2 register

Status

RKDS-

contents of the Status register

RKER-

contents of the Error register

RKAS/OF-

contents of the Attention
and OFFset register

Summary

RKDe-

contents
of
desired
Address register

cylinder

RKDS-

contents
register

RKMR1-

contents of Maintenance Register 1

RKMR2-

contents of Maintenance Register 2

RKMR3-

contents of Maintenance Register 3

RKECPS-

contents of ECC position register

RKECPT-

contents of ECC Pattern register

SECTOR-

sector address of the error

TRACK-

track address of the error'

CYLINDER-

cylinder address of the error

the

Unibus

Status

Address

Data

Buffer

Format 2
ERROR NO.-

ERR followed by the error number

EXPECTED-

data expected

RECEIVED-

data received

SECTOR-

sector address of the error

12-9

RK86S AND RK06D USER MODE DIAGNOSTIC PROGRAMS
TRACK-

track address of the error

CYLINDER-

cylinder address of the error

DISTANCE INTO SECTOR-

distance into sector
verify error occurred.
Count starts at 0.

pefore

RETRY NO.-

indicates which
reread
recovered the data

READ NO.-

indicates which of the 8 successive
read attempts failed during the
random test.

Format 3
DISK ADDRESS DID NOT UPDATE PROPERLY
EXPECTED-

address expected

RECEIVED-

address received

attempt

RK06S AND RK06D USER MODE DIAGNOSTIC PROGRAMS
Table 12-2
RK06S and RK06D Error Messages
ERROR
NUMBER

ASSOCIATED TEST

MEANING

Cylinder test conversation mode

Error was detected during an explicit seek to Cylinder A in an
address test.

Cylinder test conversation mode

Error was detected during an explicit seek to Cylinder B in an
address test.

Cylinder test 1

A hardware error occurred after a
read header command was issued to
cause an implied seek to Cylinder

Cylinder test 1

A hardware error occurred after a
read header command was issued to
cause an implied seek to Cylinder N.

Cylinder test 2

A hardware error occurred after a
read header command was issued to
cause an implied seek to the cylinder number being incremented.

Cylinder test 2

A hardware error occurred after a
read header command was issued to
cause an implied 'seek to the cy 1inder number being decremented.

Cylinder test 2

The cylinder number contained in
the sector's header does not match
the requested cylinder number.

Sector addressing test

A hardware error occurred after a
write command was issued to put
the sector address pattern into a
sector with a number equal to the
pattern.

Sector addressing test

An error occurred when a write operation to a sector on track 0 of
Cylinder 0 was followed by a
'wr i te-check command.

Sector addressing test

A hardware error occurred after a
read command was issued to read
the sector address pattern in the
selected sector on track 0 of Cylinder o.
(continued on next page)

12,-11

RK06S AND RK06D USER MODE DIAGNOSTIC PROGRAMS
Table 12-2 (Cont.)
RK06S and RK06D Error Messages
ERROR
NUMBER

ASSOCIATED TEST

MEANING

Track/head addressing
test

An error occurred after a 256-word
write was issued to sector 0 on
track 0, 1, or 2 of Cylinder O.
(The data that was written was
made up of the 2-word track address pattern: track address number and its complement.)

Track/head addressing
test

An error occurred when a write operation to sector 0 on track 0, 1,
or 2 was followed by a write-check
conunand.

Track/head addressing
test

An error occurred after a read
data conunand was issued to read
the track address pa'ttern in sector 0 of track 0, 1, or 2 of Cylinder o.

Track/head addressing
test

An error occurred while rewriting
sector 0 on track 0, 1, or 2 of
Cylinder 0 with the 2-word track
address pattern.

Write/read cylinder
spil:aling test

An error occurred while attempting a 2-sector write, using the
2-word cylinder address pattern,
to the last sector of a cylinder.

Write/read cylinder
spiraling test

An error occurred when a 2-sector
write to the last sector on the
last track of a cylinder was followed by a write-check command.

Write/read cylinder
spiraling test

An error occurred while attempting a read data command to sector
o on track 0 of a cylinder'. The
data read should be the value of
the cylinder number minus 1.

Sector addressing test,
Track/head addressing
test, Write/read
cylinder spiraling
test

The entire contents of the sectors were searched in an attempt
to match the expected 2-word address pattern, and no match was
found.

Partial sector write
test

An error occurred while a pattern
of all ones was being written into sector 0 on track 0 of Cylinder 0 (or the first good sector
on the cylinder).
(continued on next page)

12-12

RK06S AND RK06D USER MODE DIAGNOSTIC PROGRAMS
Table 12-2 (Cont.)
RK06S and RK06D Error Messages
ERROR
NUMBER

ASSOCIATED TEST

MEANING

Partial sector write
test

The entire Cylinder 0 was found
to be marked bad. The cartridge
disk will probably need to be reformatted.

Partial sector write
test

An error occurred during a 2-word
write data operation to sector 0
on track 0 of Cylinder 0 (or the
first good sector on the cylinder).
The data written is all ones
(177777). A partial write command should result in the remainder of the sector being zero
filled.

Partial sector write
test,

An error occurred while a full
sector read command to sector 0
on track 0 of Cylinder 0 (or the
first good sector on the cylinder)
was being executed.

Partial sector write
test

A data compare error occurred when
a previously written test pattern
was write-checked.
The first two data words in the
sector should be ones (177777),
and the remainder of the sector
should contain all zeroes.

Random test

An error occurred while attempting
a random length write of random
data to a randomly selected disk
address.

Random test

An error occurred while attempting an explicit seek operation to
a randomly selected address. The
error occurred between write and
read operations.

Random test

An error occurred while reading
the random data pattern from the
randomly selected disk address.

Random test

Data compare error; data read did
not match the expected random
data pattern.

Random test

An error occurred during a recalibration operation attempt, after
four unsuccessful attempts to
read random data.
(continued on next page)
12-13

RK06S AND RK06D USER MODE DIAGNOSTIC PROGRAMS
Table 12-2 (Cont.)
RK06S and RK06D Error Messages
ERROR
NUMBER

ASSOCIATED TEST

MEANING

Data test, and data
test portion of conversation mode

An error occurred during execution
of a write data command.

Data test, and data
test portion of conversation mode

An error occurred while reading
data.

Data test, and data
test portion of conversation mode

Data compare error; data read did
not match the expected data pattern.

Data test, and data
test portion of conversation mode

An error occurred during a recalibrat ion operation attempt, after
four unsuccessful attempts to
read data.

Validate marked bad
address routine/Read
bad block routine

An error occurred while the manufacturing bad sector block on the
maximum track of the maximum cylinder was being read.

Formatting routine/
Read bad block routine

An error occurred while the manufacturing bad sector block on the
maximum track of the maximum cylinder was being read.

Formatting routine

An error occurred after a write/
read command was issued to a
selected track.

Bad sector handling
routine

The core-resident table, used to
store the addresses of marked bad
sectors encountered, is full.

Read bad block from
bad sector file track
routine

The routine was unable to locate
the bad sector block on the bad
sector file track."

error occurred when a writecheck command, following a write
data command, was executed.

12-14

IND1~X

J'.ddress test
RK05S, 3-1
RK06S, 12-1
RP03S, 4-1
RS04S, 6-2
RS11S, 7-1
TU56S, 8-1
ASR33 worst case test, 11-4
ASR35 worst case test, 11-4

Carriage return test (TTYTS), 11-1
Changing handlers for diagnostics,
2-1.'1

Character test (TTYTS), 11-4
Conversation mode
RK05S, 3-6
RK06S, 12-5
RP03S, 4-4
RP04S, 5-6
RS04S, 6-5
RS11S, 7-4
TU10S2, 10-5
TU16S2, 10-5
TU56S, 8-5
CRC test
TU1eS2, 1£1-2
TU1~S2, 10-2

Data reliability test (TUllO ana
TU16), 10-2
Data test
RK05D and RK05S, 3-3
RK06D and RK06S, 12-3
RP03D and RPe3S, 4-2
RPI04D and RP04S, 5-2
RS04D and RS04S, 6-2
RS11D and RS11S, 7-2
TU56D and TU56S, 8-2
Diagnostic tasks
building diagnostics, 2-8
naming conventions, 2-4
operational information, 2-4
running the task, 2-12
terminating the task, 2-18

Error message formats
RK05D and RK05S, 3-7
RK06D and RK06S, 12-8
RP03D and RP03S, 4-7
RP04D and RP04S, 5-7
RS04D and RS04S, 6-6
RS11D and RS11S, 7-6
TU10D, 10-6
TU1eSl, 9-5
TU10S2, 10-6
TU16D, 10-6
TU16S1, 9-5
TU16S2, 10-6
TU56D and TU56S, 8-6
Error message numbers
RK05D and RK05S, 3-8
RK06D and RK06S, 12-9
RP03D and RP03S, 4-7
RP04D and RP04S, 4-8
RS04D and RSe4S, 6-&
RSIID and RSllS, 7-8
TU10D, 10-10
TU10S1, 9-8
TU10S2, le-10
TU16D, 110-10
TU16S1, 9-8
TU16S2, 9-9
TU56D and TU56S, 10-7
Extended' record gap test (TUllO
and TU16), 9-2

Formatter test
RK05S, 3-4
RK06S, 12-4
RPe3S, 4-3
RPri54S, 5-3

Hardware diagnostics, see
diagnostic task

Lateral parity test (TU10 and
TU16), 110-1
Line feed test (TTYTS), 11-4
Longitudinal parity test, 110-2

End of file test (TU1.'1 and TU16),
9-2
End of record test (TU1.'1 and TUl6) ,
9-1

Multiple-file positioning test
(TUllO and TU16), 9-2

Index-1

INDEX (CONT • )

Naming conventions for diagnostic
tasks, 2-4

Operational information
Diagnostic tasks, 2-4
RK05D and RK05S, 3-4
RK06D and RK06S, 12-4
RP03D and RP03S, 4-4
RP04D and RP04S, 5-3
RS04D and RS04S, 6-3
RSIID and RSllS, 7-3
TU10D, 10-3
TU10S1, 9-3
TU10S2, 10-3
TU16D, 9-3
TU16S1, 10-3
TU16S2, 10-3
TU56D and TU56S, 8-3

Skew test (TU10 and TU16), 10-2
Space test (TTYTS), 11-3
Start/stop test (TU56S), 8-2

Tab Test (TTYTS), 11-3
Task building diagnostics, 2-8
Terminating diagnostics, 2-18
Test parameter bit settings
RK05D and RK05S, 3-4
RK06D and RKa6S, 12-4
RP03D and RP03S, 4-4
RP04D and RP04S, 5-4
RS04D and RSa4S, 6-3
RS11D and RSllS, 7-3
TTYTS, 11-5
TUlaD, 19-3
TUlaSl, 9-3
TG10S2, 121-3
TU16D, 10-3
TU16S1, 9-3
TU16S2, 121-3
TU56D and TU56S, 8-3
~U16 Burst ,test (TU16S2), 10-2

Random test
RKe5D and,RKa5S, 3-3
RK06S, 12-3
RP03D and RP03S, 4-3
RP04D and RP04S, 5-3
RS04D and RSa4S, 6-3
RS11D and RSllS, 7-3
Record length test (TUle and
TU16), 121-1
Rewind and backspace test
(TUla and TU16), 9-1
Running CMD task, 2-5

,User-selected pattern test
(TTYTS), 11-5

Single-record positioning test
(TU10 and TU16), 9-2

Write and read record test (TU10
and TU16), 9-1

Variable-length record positioning test (TUla and TU16), 9-3

Index-2

IAS/RSX-11 D
Diagnostics Reference Manual
AA-3057C-TC

Reader's
Comments

This form is for document comments only. Digital will use comments submitted on
this form at the company's discretion. If you require a written reply and are eligible
to receive one under Software Performance Report (SPR) service, submit your
comments on an SPR form.

Did you find this manual understandable, usable, and well organized? Please make suggestions for
improvement.

Did you find errors in this manual? If so, specify the error and the page number.

Please indicate the type of user/reader that you most nearly represent:

o
o

o
Name~

Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experienCE!
Student programmer
Other(~ease spedfy)~~~~~~_~~~~~~~~~~~~~~~~~~

________________________________._____________________ Date~~~~~~_

Organization __________________________________________________________
Street_______________________________________________________________________
City _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __

State_ _ _ _ _ _ Zip Code _______
or Country

- - - - - - - - - - - - - - - - - - 1)"

~"I h'.. r" I'clld Ikrt' .. nd T..

pt.'

-------------------------1

mamaamD™

No Postage
Necessary
if Mailed in the
United States

BUSINESS REPLY MAIL
FIRST CLASS

PERMIT NO 33

MAYN,A,RD MASS

POST AGE WILL BE PAID BY ADDRESSEE

IAS Engineering/Documentation
Digital Equipment Corporation
5 Wentworth Drive GSF/L20
Hudson, NH 03051-4929

11111111111 11,".111. '11111.1 •• 1.1 ••• 1•• 11.1 •• 11 ••• 1
- - - . - - - - - . - - - - - - - - - - - - - I)"

,,'I "I't'.. r" 1:"ld Ikn' - - - - - - - - - - - - - - - - - - - - -