Digital PDFs

AA-H271A-TC

May 1979

226 pages

Original

8.9MB

Document:	RSX-11M/M-PLUS User Mode Diagnostics Reference Manual
Order Number:	AA-H271A-TC
Revision:	0
Pages:	226
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V3.2_Jun79/6_Maintenance/AA-H271A-TC_RSX-11M_User_Mode_Diag_Ref_May79.pdf

OCR Text

RSX-11 M/M-PLUS
User Mode Diagnostics
Reference Manual
Order No. AA-H271A-TC

!-~order additional copies of this document, contact the Software Distribution
L::,ter, Digital Equipment Corporation, Maynard, Massachusetts 01754

digital equipment corporation · maynard, massachusetts

First Printing, December 1976
Revised, May 1979

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 only be used or copied in accordance with the terms of such
license.
No responsibility is assumed for the use or rel.iability of software on
equipment that is not supplied by DIGITAL or its affiliated companies.

1976, 1979 by Digital Equipment Corporation

The postage-prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in preparing future documentation.
The following are trademarks of Digital Equipment Corporation:

DIGITAL
DEC
PDP
DEC US
UNIBUS
COMPUTER LABS
COMTEX
DDT
DECCOMM
ASSIST-11
VAX
DECnet
DATATRIEVE

DECsystem-lo
DECtape
DIBOL
EDUSYSTEM
FLIP CHIP
FOCAL
INDAC
LAB-8
DECSYSTEM-20
RTS-8
VMS
IAS
TRAX

MASS BUS
OMNIBUS
OS/8
PHA
RSTS
RSX
TYPESET-8
TYPESET-11
TMS-11
ITPS-10
SBI
PDT

'--";

CONTENTS
Page
PH.EFACE

CHAPTER

INTRODUCTION

1-1

CHAPTER

HELP! THE CUSTOMER MODE USER

2-1

2.1
2.2
2.3
2.4

PURPOSE OF CHAPTER
ASSUMPTIONS
CONTENT OF THE DIAGNOSTIC CHAPTERS
DIAGNOSTIC INITIATION
Recording Error Reports
Medium Requirements
Multiuser Protection Systems
Systems Without Multiuser Protection
ERROR MESSAGES
MULTIDEVICE TESTING
LOGICAL BLOCK NUMBERS FROM PHYSICAL
ADDRESSES

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

RP04, RP05, OR RP06 PACK DISK DIAGNOSTIC

3-1

3.1
3.2
3.3

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

3.10

TEST SUMMARY REPORT
DISK DRIVE CHARACTERISTICS
DIAGNOSTIC DESCRIPTION
Addressing Exercises
Heads-Positioning Exercise
Sector-Addressing Exercise
Track-Addressing and Crossover Exercise
Cylinder-Addressing and Crossover Exercise
Partial-Write Exercise
Data-Reliability Exercise
Random Exercise
Formatting Routine
ERROR MESSAGES
SERVICE-MODE INITIATION
CONSOLE SWITCH FOR INTERVENTION
TEST-PARAMETER SELECTION
SERVICE-MODE INTERVENTION/RESTART/TERMINATION
INTERACTIVE-ADDRESS TEST
INTERACTIVE-DATA TEST

RFll FIXED-HEAD DISK DIAGNOSTIC

4-1

TEST SUMMARY REPORT
DISK CHARACTERISTICS
DIAGNOSTIC DESCRIPTION
Addressing Exercises
4. 3 .1
Sequential-Addressing Exercise
4.3.1.1
Random-Addressing Exercise
4.3.1.2
Data-Reliability Exercise
4.3.2
Random Exercise
4.3.3
ERROR MESSAGES
4.4
SERVICE-MODE INITIATION
4.5
CONSOLE SWITCH FOR INTERVENTION
4.6

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

2. 4 .1

2.4.2
2.4.3
2. 4. 4
2.5
2.6
2.7
CHAPTER

3. 3 .1

3.3.1.1
3.3.1.2
3.3.1.3
3.3.1.4
3.3.1.5
3.3.2
3. 3. 3
3. 3. 4

3.4
3.5
3.6
3.7
3.8
3. 9

CHAPTER

4.1
4.2
4.3

iii

2-7

3-3

3-3
3-3
3-4
3-4
3-5
3-5
3-10
3-10
3-11
3-13

3-14
3-14

4-4

4-6
4-7

CONTENTS
Page

CHAPTER

4.7
4.8
4.9

TEST-PARAMETER SELECTION
SERVICE-MODE INTERVENTION/RESTART/TERMINATION
INTERACTIVE-DATA TEST

4-7
4-9
4-10

RK05 CARTRIDGE DISK AND RK05F FIXED DISK
DIAGNOSTIC

5-1

5.1
5.2
5.3
5.3.1
5.3.1.1
5.3.1.2
5.3.1.3
5.3.1.4
5.3.1.5
5.3.1.6
5.3.2
5. 3. 3
5.3.4
5.4
5.5
5.6
5.7
5.8
5.9
5.10

TEST SUMMARY REPORT
DISK DRIVE CHARACTERISTICS
DIAGNOSTIC DESCRIPTION
Addressing Exercises
Heads-Positioning Exercise
Sector-Addressing Exercise
Track-Addressing Exercise
Cylinder-Addressing Exercise
Track-Crossover Exercise
Cylinder-Crossover Exercise
Data-Reliability Exercise
Random Exercise
Formatting Routine
ERROR MESSAGES
SERVICE-MODE INITIATION
CONSOLE SWITCH FOR INTERVENTION
TEST PARAMETER SELECTION
SERVICE-MODE INTERVENTION/RESTART/TERMINATION
INTERACTIVE~ADDRESS TEST
INTERACTIVE-DATA TEST

5-1
5-2
5-2
5-2
5-2
5-2
5-3
5-3
5-3
5-3
5-3
5-4
5-5
5-5
5-9
5-10
5-10
5-12
5-13
5-13

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS

6-1

TEST SUMMARY REPORT
6.1
6.2
DISK-DRIVE CHARACTERISTICS
DIAGNOSTIC DESCRIPTION
6.3
6.3.1
Addressing Exercises
6.3.1.1
Heads-Positioning Exercise
Sector-Addressing Exercise
6.3.1.2
Track-Addressing Exercise
6.3.1.3
Cylinder-Addressing and Crossover Exercise
6.3.1.4
Partial-Sector-Write Exercise
6.3.1.5
Data-Reliability Exercise
6.3.2
Random Exercise
6.3.3
6.3.4
Formatting Routine
6.4
ERROR MESSAGES
SERVICE-MODE INITIATION
6.5
CONSOLE SWITCH FOR INTERVENTION
6. 6
TEST PARAMETER SELECTION
6. 7
SERVICE-MODE INTERVENTION/RESTART/TERMINATION
6.8
INTERACTIVE-ADDRESS TEST
6.9
6.10
INTERACTIVE-DATA TEST
CHAPTER

RP02, RPR02, OR RP03 DIAGNOSTIC

7.1
7.2

TEST SUMMARY REPORT
DISK DRIVE CHARACTERISTICS
7. 3
DIAGNOSTIC DESCRIPTION
7.3.1
Addressing Exercises
7.3.1.1
Heads-Positioning Exercise
7.3.1.2
Sector-Addressing Exercise

6-1
6-2
6-2
6-3
6-3
6-3
6-3
6-3
6-4
6-4
6-5
6-5
6-6
6-11

6-12
6-12
6-14
6-15
6-15
7-1
7-1
7-2
7-2
7-2
7-2
7-3

,._~. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111111111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1111!1111. . . . . . .!ll'li....

CONTENTS
Page
7.3.1.3
7.3.1.4
7.3.1.5
7.3.2
7.3.3

7-:3
7-3
7-3
7-4
7-4
7-5
7-6
7-10

7.10

Track-Addressing and Crossover Exercise
Cylinder-Addressing and Crossover Exercise
Partial-Write Exercise
Data-Reliability Exercise
Random Exercise
Formatting Routine
ERROR MESSAGES
SERVICE-MODE INITIATION
CONSOLE SWITCH FOR INTERVENTION
TEST-PARAMETER SELECTION
SERVICE-MODE INTERVENTION/RESTART/TERMINATION
INTERACTIVE-ADDRESS TEST
INTERACTIVE-DATA TEST

RS03 OR RS04 FIXED-HEAD DISK

8-1

7. 3. 4
7. 4
7. 5
7. 6
7.7
7. 8
7. 9

CHAPTER

TEST SUMMARY REPORT
DISK-DRIVE CHARACTERISTICS
DIAGNOSTIC DESCRIPTION
8. 3. 1
Addressing Exercises
Sequential Addressing Exercise
8.3.1.1
8.3.1.2
Random-Addressing Exercise
8. 3. 2
Data-Reliability Exercise
8. 3. 3
Random Exercise
8. 4
ERROR MESSAGES
8.5
SERVICE-MODE INITIATION
8. 6
CONSOLE SWITCH FOR INTERVENTION
8.7
TEST-PARAMETER SELECTION
8. 8
SERVICE-MODE INTERVENTION/RESTART/TERMINATION
8. 9
INTERACTIVE-DATA TEST
8 .. 1

8.2
8.3

CHAPTER

7-14
7-14

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

TU56 DECTAPE DIAGNOSTIC

9-1

9.1
9.2
9.3

9-1
9-2
9-2

9.10

TEST SUMMARY REPORT
DEVICE CHARACTERISTICS
DIAGNOSTIC DESCRIPTION
DECtape Positioning and Data Compare
Exercises
Rewind Exercise
Block Write-Read Exercise
Odd-Even Block Exercise
Random Read Exercise
Stop-Start Exercise
Data-Reliability Exercise
EHROR MESSAGES
SERVICE-MODE INITIATION
CONSOLE SWITCH FOR INTERVENTION
TEST-PARAMETER SELECTION
SERVICE-MODE INTERVENTION/RESTART/TERMINATION
INTERACTIVE-ADDRESS TEST
INTERACTIVE-DATA TEST

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC

10-1

10.1
10.2
10.3
10.3.1
10.3.2

TEST SUMMARY REPORT
TAPE DRIVE CHARACTERISTICS
DIAGNOSTIC DESCRIPTION
Beginning-of-Tape (BOT) Exercise
Interrecord-Gap (IRG) Exercise

10-1
10-2
10-2
10-3
10-3

9. 3 .1

9.3.1.l
9.3.1.2
9.3.1.3
9.3.1.4
9.3.2
9.3.3
9.4
9. 5

9.6
9.7
9.8
9.9

CHAP'TER

7-11
7-11
7-13

9-2
9-2
9-2
9-2
9-3
9-3
9-3
9-4
9-7
9-7
9-7
9-9

9-10
9-10

CONTENTS
Page
Variable-Length Record Positioning Exercise
Record-Length Exercise
Lateral~Parity Exercise
Longitudinal-Parity-Check-Character (LPCC)
Exercise
Cyclic-Redundancy-Check-Character (CRCC)
10.3.7
Exercise
Record Creep Exercise
10.3.8
10.3.9
Skew Exercise
End-of-File (EOF) Exercise
10.3.10
Single-Record Positioning Exercise
10.3.11
Multiple-Record Positioning Exercise
10.3.12
Crosstalk Exercise
10.3.13
Data-Reliability Exercise
10.3.14
Quick Total-Tape-Check Exercise
10.3.15
1600-BPI Identification Burst (IDB) Exercise
10.3.16
10.4
ERROR MESSAGES
SERVICE-MODE INITIATION
10.5
CONSOLE SWITCH FOR INTERVENTION
10.6
TEST PARAMETER SELECTION
10.7
SERVICE-MODE INTERVENTION/RESTART/TERMINATION
10.8
INTERACTIVE DRIVE-COMPATIBILITY TEST
10.9
INTERACTIVE WRITE-READ SLICE ADJUSTMENT
10.10

10-3
10-3
10-4

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC

11-1

TEST SUMMARY REPORT
TAPE DRIVE CHARACTERISTICS
DIAGNOSTIC DESCRIPTION
Beginning-of-Tape (BOT) Exercise
Interrecord-Gap (IRG) Exercise
Variable-Length Record-Positioning Exercise
Record-Length Exercise
Lateral-Parity Exercise
Longitudinal-Parity-Check-Character (LPCC)
Exercise
Cyclic-Redundancy-Check-Character (CRCC)
11. 3. 7
Exercise
Record Creep Exercise
11. 3. 8
Skew Exercise
11. 3. 9
End-of-File (EOF) Exercise
11.3.10
Single-Record Positioning Exercise
11.3.11
Multiple-Record Positioning Exercise
11.3.12
Crosstalk Exercise
11.3.13
11. 3 .14
Data-Reliability Exercise
Quick Total-Tape-Check Exercise
11.3.15
11. 4
ERROR MESSAGES
SERVICE-MODE INITIATION
11. 5
11. 6
CONSOLE SWITCH FOR INTERVENTION
TEST PARAMETERS SELECTION
11. 7
SERVICE-MODE INTERVENTION/RESTART/TERMINATION
11. 8
INTERACTIVE DRIVE-COMPATIBILITY TEST
11. 9
11.10
INTERACTIVE WRITE-READ SLICE ADJUSTMENT

11-1
11-2
11-4
11-4
11-5
11-5
11-5
11-5

TERMINAL OR LINE PRINTER DIAGNOSTIC

12-1

12.1
12.2

END-OF-TEST INDICATION
DIAGNOSTIC DESCRIPTION

12-1
12-1

10.3.3
10.3.4
10.3.5
10.3.6

CHAPTER

11
11. l
11. 2
11. 3
11. 3. 1
11. 3. 2
11. 3. 3
11. 3. 4
11. 3. 5
11. 3. 6

CHAPTER

10-4
10-4
10-4
10-5
10-5
10-5
10-6
10-6
10-6
10-7
10-7
10-8
10-14
10-15
10-15
10-18
10-19
10-20

11-6
11-6
11-6
11-7
11-7
11-7
11-8
11-8
11-8
11-9
11-9
11-16
11-17
11-17
11-20
11-20
11-21

I ..

CONTENTS
Page
12.2.1
12.2.2

CHAPTER

12-3

12.2.3
12.2.4
12.2.5
12.2.6
12.2.7
12.3
12.4
12.5
12.6
12.7

Carriage-Return Exercise, Hard-Copy Terminal
Carriage-Return Exercise, Video-Display
Terminal
Spacing Exercise, Hard-Copy Terminal
Spacing Exercise, Video-Display Terminal
Tabbing Exercise
Line-Feed Exercise
Character-Set Exercise
SERVICE-MODE INITIATION
CONSOLE SWITCH FOR INTERVENTION
TEST PARAMETER SELECTION
SERVICE-MODE INTERVENTION/RESTART/TERMINATION
INTERACTIVE-PATTERN TEST

DISK DRIVE COMPATIBILITY DIAGNOSTIC

13-1

13.1
13. 2

HARDWARE AND SOFTWARE ENVIRONMENT
EXTERNAL INTERACTIONS - USER INTERFACE FOR
INITIATION
Pass 1 Dialogue
Pass 2 Dialogue
ERROR MESSAGES
Dialogue Errors
Program Errors
FUNCTIONAL DESCRIPTION
OPERATION DESCRIPTION
Description of Pass 1 Tests
Description of Pass 2 Tests
Restrictions
DESCRIPTION OF MAJOR MODULES
Common Disk Function Handler
Main Module
Worst-Case Data Pattern
Write-Current Zones Tables
Random Data Pattern Table
Basic Overwrite Cylinder Group Layout
Cylinders Table
KEY ALGORITHMS
Determining Sectors Used by Each Drive
Bad-Block Algorithm
Retry Algorithm

13-1
13-1
13-2
13-4
13-5
13-6
13-6
13-8
13-9
13-9
13-10
13-11
13-11
13-11
13-11
13-12
13-12
13-13
13-14
13-14
13-15
13-15
13-15
13-15

HELP! THE SERVICE-MODE USER

A-1

GENERAL INFORMATION
DIAGNOSTIC INITIATION
ERROR MESSAGES
MULTIDEVICE TESTING
DIAGNOSTIC TERMINATION
LOGICAL BLOCK NUMBERS FROM PHYSICAL ADDRESSES

A-1
A-2
A-3

13. 2.1
U.2.2

1:3.3
13. 3 .1
13.3.2
13. 4
13. 5
13.5.1
13.5.2
13. 5. 3
13. 6
13. 6.1
13. 6. 2
13.6.3
13.6.4
13. 6. 5
13.6.6
13.6.7
13. 7
13. 7 .1
13.7.2
13.7.3
APPENDIX A
A.l
A. 2
A. 3
A. 4

A.5
A. 6

APPENDIX B

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS

vii

12-3
12-3
12-4
12-4
12-5
12-5
12-5
12-6
12-6
12-8
12-9

A-5

A-6
A-6
B-1

CONTENTS
Page
FIGURES
FIGURE

11-1
11-2
11-3

Relationship Between Tape Characters and
Memory Bytes
9-Channel Tape Format
7-Channel Tape Format

11-3
11-3
11-4

TABLES
TABLE

3-1
3-2
4-1
4-2
5-1
5-2
6-1
6-2
7-1
7-2
8-1
8-2
9-1
9-2
10-1
10-2
11-1
11-2
12-1
13-1
13-2
13-3
13-4
13-5
B-1
B-2
B-3
B-4
B-5
B-6
B-7
B-8
B-9
B-10

Error Conditions
Test-Parameter Options
Error Conditions
Test-Parameter Options
Error Conditions
Test-Parameter Options
Error Conditions
Test-Parameter Options
Error Conditions
Test-Parameter Options
Error Conditions
Test-Parameter Options
Error Conditions
Test-Parameter Options
Error Conditions
Test-Parameter Options
Error Conditions
Test-Parameter Options
Test-Parameter Options
Worst Case Data Pattern
Cylinder Group Assignment for a Given Surface
Random Data Pattern
Cylinders Written (RK06, RP03, and RP04/5)
Maximum and Minimum Off sets
RK05(RK05F) Controller Registers
RK06 Controller Registers
RP02-RPR02-RP03 Controller Registers
RP04-RP05-RP06 Controller Registers
RFll Controller Registers
RS03-RS04 Controller Registers
TU10-TS03 Control Registers
TU16-TU45 Control Registers
TU56 Controller Registers
Glossary of Register Mnemonics

3-7
3-11
4-5
4-8
5-6
5-11
6-7
6-13
7-7
7-11
8-5
8-8
9-5
9-8
10-9
10-16
11-10
11-17
12-7
13-12
13-13
13-13
13-14
13-15
B-2
B-2
B-4
B-5
B-7
B-8
B-8
B-9
B-11
B-11

viii

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~. . . .. , .. . . . . . . . . . . . . . . . . . . . . . . . . . . .1-.ii

CUSTOMER-MODE KNOWLEDGEABLE USER REFERENCE
Typical Diagnostic Initiation

Device Model No. 's
and Mnemonics

Underlined text indicates expected or required user
input.
Install "scratch" medium on device, if applicable.

Cartridge Disks:

On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DKO:

(mnemonic and unit number)

RK05

DKn

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DKOJ.L[Qg
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $RK05

(test name=dev.

RK06

model no.)

DMn

Pack Disks:

START RK05 DIAGNOSTIC - TIME OF DAY
RESIDENT DATA WILL •••
(N or RETURN alone aborts)

RP02
RPR02
RP03

DPn
DPn
DPn

Cartridge and pack disks also ask FORMAT DISK
ONLY? Y response formats resident cartridge
or pack and exitso
N initiates customer mode.

RP04
RP05
RP06

DBN
DBn
DBn

DEVICE? DKO
**WARNING**
CONTINUE? ¥

DKO~

TU16/TU45 diagnostic also asks TEST IN 1600
BPI MODE? N response selects 800 BPI.
All magnetic tape diagnostics (not DECtape)
also ask QUICK TOTAL TAPE CHECK? Y response
tests entire tape's data reliability and exits;
N initiates customer mode.

Fixed-head Disks:
RFll
RS03
RS04

DFO
DSn
DSn

Magnetic Tape Units:

Terminal diagnostic also asks HARD COPY TERMINAL?
N response tests terminal as video display.

TS03
TUlO

MTn
MTn

Terminal diagnostic can be used to exercise
a line printer by LP device selection and Y response to 132 COLUMN TEST? The default is 72
columns.

TU16
TU45

MMn
MMn

Diagnostic runs to completion.
type

DECtape Unit:

To exit sooner,

All Terminals:

MCR>ABORT
TERM

TTn

All Line Printers:
TERM
NOTE
TERM is the diagnostic test name for
terminals and line printers;
output to
a line printer is not spooled and can
interfere with another user's output.

LPn

··""

PREFACE

MANUAL OBJECTIVES
The RSX-llM/M-PLUS User Mode Diagnostics Reference Manual is a usage
and a reference document for optional software provided with RSX-llM
and RSX-llM-PLUS systems.
The manual describes the
initiation
procedures for online diagnostic tasks, the reports generated by the
tasks, the tests performed by each diagnostic task, the error messages
associated with the tests, the procedures for intervening in tests,
and the options for the tests.
The manual does not describe the
hardware itself or attempt to interpret possible results of tests nor
does it indicate how testing might be managed on a system. The manual
is strictly for usage and reference.
INTENDED AUDIENCE
This document is intended for customer personnel responsible for
system maintenance and for DIGITAL Field Service representatives
responsible for servicing customer installations.
The
document
assumes that the reader knows system concepts:
understands peripheral
device terminology and operation:
and is following locally-defined
procedures regarding what tests to run and when to run them.
STRUCTURE OF THIS DOCUMENT
This document is structured as follows.
•

Chapter 1, Introduction, describes the features
of User Mode Diagnostic software.

•

Chapter 2, HELP!
The Customer Mode User, presents helpful
information for
the beginning customer-mode user and for the
more experienced user seeking assistance.

•

Chapters 3 through 12 are device specific,
stand-alone
information modules. They show how to initiate the applicable
diagnostic task in customer mode or service mode;
describe
how device functions are tested;
and explain the significance
of error messages.

•

Chapter 13, Disk Drive Compatibility Diagnostic, tells how to
gauge the ability of disk drives to write data that can be
read by other drives and to completely overwrite data written
by other drives.

and

benefits

•

Appendix A, HELP! The Service Mode User,
information for the service-mode user.

presents

helpful

•

Appendix B, Bit Maps
for
Device-Controller
Registers,
summarizes the mnemonics for the hardware registers of devices
capable of being tested by user mode diagnostic software.

In addition, the document contains a quick look-up reference sheet
after the title page for the customer-mode user and one inside the
rear cover for the service-mode user.
ASSOCIATED DOCUMENTS
The procedures to incorporate the user mode diagnostic software on a
system are presented in both the RSX-llM System Generation and
Management Guide and the RSX-llM-PLUS System Generation and Management
Guide. Associated with the user mode diagnostic software is the error
logging software. Error logging and related subjects are described in
the
RSX-llM/M-PLUS
Error
Logging
Reference Manual.
For the
description of these manuals and other system documentation, refer to
either the RSX-llM/RSX-118 Documentation Directory or the RSX-llM-PLUS
Documentation Directory.
CONVENTIONS USED IN THIS DOCUMENT
Throughout this book, symbols and other notation conventions are used
to represent keyboard characters, to convey textual information, and
to otherwise ease the presentation of material.
The symbols and
conventions used are explained below.
Convention

Meaning
Indicates typing the RETURN key: the system
performs a carriage return operation. Almost
all commands are terminated by typing the
RETURN key.

CTRL/x

"print" and "type"

Represents the combination of the CTRL key
and
another
key to generate a control
character. That is, you simultaneously press
the CTRL key and another key. For example,
the CTRL/C combination causes MCR to prompt
for command input with the explicit prompt
MCR>.
As these words are used in the
system prints and the user types.

text,

the

MCR>

The Monitor Console Routine is one of the
command language interfaces used on RSX-llM
and RSX-llM-PLUS systems and is the one used
in this book.

A greater-than sign is the system command
interface
(MCR)
prompting
character.
Whenever control is returned to the user task
terminal and you can type input, MCR prints
the prompt.
Underlined material
in
sample
terminal
dialogue indicates information you type.

xii

Convention

Meaning

lower case

Indicates a variable item whose actual value
is determined either when you enter a command
(or a response) or when a message is issued.

UPPER CASE

Information shown in examples in
UPPER CASE
characters represents either the exact data
printed by the program or the exact data the
program expects you to supply.

'-'.
I

xiii

SUMMARY OF TECHNICAL CHANGES

This rev1s1on of the RSX-llM/M-PLUS User Mode Diagnostics Reference
Manual contains changes and additions to reflect features of two
operating systems and to correct technical errors.
The following
paragraphs describe the technical information added to the manual.
TECHNICAL CHANGES COMMON TO RSX-llM AND RSX-llM-PLUS SYSTEMS
Two new diagnostic prog~ams have been added to the systems.
•

RK07 Cartridge Disk diagnostic

•

Disk Drive Compatibility diagnostic

TECHNICAL CHANGES FOR RSX-llM-PLUS SYSTEMS
The procedures to run most diagnostic tasks on RSX-llM-PLUS systems
includes a new step. The Executive requires that you must logically
mount the volume as foreign.

xiv

CHAPTER 1
INTRODUCTION

Intelligent application of User Mode Diagnostics with Error Loggingl
can be effective in reducing system down-time. These important system
services, however, can be made a part of the system only at system
generation.
Planners of minimum systems may not wish to make or be
able to make the necessary trade-offs to accommodate these services.
Planners of larger systems are urged to consider the benefits of
having these services available relative to their minimal storage
needs.
Tell the person doing your system generation to respond YES
when the generation software asks:
DO YOU WANT USER MODE DIAGNOSTICS?
DO YOU WANT ERROR LOGGING?
DO YOU WANT GET SENSE SWITCHES DIRECTIVE?2
User Mode Diagnostics (UMD's) exercise all programmable functions
diagnostics of DIGITAL peripherals :in worst-case conditions. Unlike
"stand-alones," User Mode Diagnostics can be selectively initiated to
test one or more devices (or format disk packs and cartridges)
concurrent with normal system operation. You remove a device from
service, not the entire system. The diagnostics are device-specific
and support the following:

• Pack, Cartridge, and Fixed-Head Disks,
• Magnetic Tape Units,
• DECtape Un:its,

'-'

• Hard-Copy Terminals,
• Video-Display Terminals, and

• Line P·r inters.
Foremost of the UMD benefits is the ease with which facility personnel
can initiate testing in CUSTOMER MODE. The simple procedure requires
little more than the naming of the device to be tested and its
associated diagnostic.
The following is the initiation for the RK06
Cartridge Disk (underlined text indicates expected or required user
input).
1 Refer to the RSX-llM/M-PLUS
information on error logging.

Error

Logging

Reference

2
This option applies only for systems equipped with a
switch register.

1-1

Manual
CPU

for

console

INTRODUCTION

On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DMO:

(Multiuser Protection System Onlyl)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DMO:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $RK06
START RK06 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? DMO
**WARNING'** DMO:
CONTINUE? X

RESIDENT DATA WILL BE DESTROYED **WARNING**
(N or RETURN alone aborts the test)

Once initiated, the diagnostic runs to completion without further
interaction.
The diagnostic reports all errors as detected and
produces a "test summary" report on the initiating terminal before
exiting.
The double entry of the device identification, the WARNING
message, and the CONTINUE pause are checks for protection against
inadvertent device selection and possible loss of data.
Typical customer mode uses are:
a regularly scheduled preventative
maintenance program;
possible confirmation that the device is at
fault and not the medium;
and the test of a device reported by Error
Logging as having a high error rate.
The complement of customer mode is SERVICE MODE.
This mode is
intended primarily for use by DIGITAL Field Service Engineers,
although system knowledgeable personnel can make use of it,
if
required.
The
service-mode
user employs the same User Mode
Diagnostics with the ability to select sophisticated options and to
modify the test sequence as is appropriate for localizing the reported
fault condition.

1 The ALLOCATE command is implemented only for
systems.

1-2

multiuser

protection

CHAPTER 2
HELP! THE CUSTOMER MODE USER

2.1

PURPOSE OF CHAPTER

Thjs chapter is for the beginning user and for
who seeks assistance.
Its contents include:

2.2

the

experienced

•

Document assumptions

•

Explanation of the diagnostic chapter content

•

Diagnostic initiation

•

Error messages

•

Multidevice testing

•

Conversion of physical addresses to logical block numbers.

user

ASSUMPTIONS

The diagnostic chapters assume:
THAT YOU UNDERSTAND RSX-llM/M-PLUS SYSTEM CONCEPTS
In particular, what a task is and how the system processes it;
MCR use and terminal-user actions in a nonprotected or protected
multiuser system environment;
privileged versus nonprivileged
use of the system; public versus private devices;
and mapped
versus unmapped systems.I
THAT THE APPLICABLE DIAGNOSTIC EXISTS
As a nonprivileged checkpointable task-image file on the system
device under UIC [l,m] where "m" equals 54 for a mapped system or
50 for an unmapped system.2

1 Refer to the RSX-llM/M-PLUS MCR Operations Manual
on system commands.

~·

for

information

2 Refer to either the RSX-llM System Generation and Management Guide
or the RSX-llM-PLUS System Generation and Management Guide for details
on where the diagnostics reside.

2-1

HELP! THE CUSTOMER MODE USER
THAT YOU UNDERSTAND THAT
Any command input or data input to MCR or a
terminated by RETURN.

diagnostic

must

THAT YOU ARE NONPRIVILEGED
With regard to initiating the diagnostic.!
THAT YOU ARE FAMILIAR WITH PERIPHERAL DEVICE OPERATION
For the devices implemented;
in particular, that you know how to
install the applicable medium and make appropriate use of the
available controls.2
THAT THE DATA BUFFER SIZE WAS NOT CHANGED
At system generation from the default value of 1024 bytes.
This
buffer controls the size of data transfers for most write and
read operations initiated by the diagnostic.3

2.3 ·CONTENT OF THE DIAGNOSTIC CHAPTERS
Each diagnostic chapter includes the following sections.
Customer-mode initiation
Test summary report
Device characteristics
Diagnostic description
Error messages (not applicable for terminal/line printer
diagnostic)
Service-mode initiation
Console switch for intervention
Test-parameter selection
Service-mode intervention/restart/termination
Interactive tests
The service-mode user is expected to be familiar with the entire
chapter, particularly, where some testing might be accomplished in
customer mode for convenience.

1
2

Refer to the RSX-llM/M-PLUS MCR Operations Manual.
Refer to the equipment document for the peripheral device.

Refer to either the RSX-llM System Generation and Management
Guide or the RSX-llM-PLUS System Generation and Management Guide for
information on the default data buffer size.

2-2

HELP! THE CUSTOMER MODE USER

·~·

As a customE~r-mode user, you need only refer to the simple initiation
procedure (found at the diagnostic chapter's beginning) and possibly,
the test summary report, which identifies the diagnostic's run time,
the number of errors detected, the number of functions issued, and the
amount of data transferred. Any error messages reported should be
saved and made available to the DIGITAL Field Service Engineer for
analysis.
Should you wish to have an
understanding
of
the
diagnostic's performance and the significance of the error messages,
refer
to
the
sections:
Device
Characteristics,
Diagnostic
Description, and Error Messages.
NOTE
You are urged not to attempt initiation
of a diagnostic in service mode because
of the complexity of the procedures and
the detailed knowledge required.

2.4

DIAGNOSTIC INITIATION

Recording Error Reports

2.4.1

Eriror Logging is automatically inhibited from
accepting
err..or
indications made by a device under test.
To capture the error
messages and the test summary report, you should initiate a diagnostic
at a hard-copy terminal.

Medium Requirements

2.4.2

The medium, if applicable, for a device to be tested should neither be
"mounted" nor "initialized". It should not contain data that you wish
to preserve. The diagnostics, in the course of testing, overwrite all
data-recording surfaces.
(The exception is the software-protected
last track of an RK06
Disk
Cartridge,
which
contains
the
factory-recorded "marked-bad-sector" file.)

Multiuser Protection Systems

2.4.3
1.

Testing Nonpublic Devices:
A nonpublic device must be "allocated" to your private use as
the first step of the initiation procedure. On RSX-llM-PLUS
systems, the volume must be mounted as foreign after the
device is allocated. Upon completion of diagnostic testing,
the device must be explicitly "deallocated" if you intend to
remain logged-in.

Testing Public Devices:
A public device cannot be "allocated" and thus tested
it is "set" by a privileged user to be nonpublic.

2-3

until

HELP! THE CUSTOMER MODE USER
3.

Device Selection:
To help protect against selection of the wrong device and
possible loss of data, the initiation procedure requires that
you enter the same device indentification (mnemonic and unit
number)
twice.
A WARNING message and the CONTINUE? pause
are additional opportunities for you to verify that the
device selected is the device you want tested.

2.4.4

Systems Without Multiuser Protection

The "allocate/deallocate" functions and the considerations of public
versus private devices are supported only by multiuser protection
systems.
Because you enter the device identification only once in
initiating a diagnostic, you should observe additional caution. Once
a diagnostic is initiated, the selected device is protected against
access by other users for the duration of the test period.

2.5

ERROR MESSAGES

The following list describes messages that might be reported by MCR or
by a diagnostic during initiation. To learn the significance of other
messages, refer to the RSX-llM/M-PLUS MCR Operations Manual and the
RSX-llM/M-PLUS Executive Reference Manual.
MCR Command Error Messages:
~

XXX -- SYNTAX ERROR
Format of entry to MCR is incorrect.

Re-enter.

ALL -- DEVICE ALLOCATED TO OTHER USERl
It cannot be
logs out, or a

Selected device is under control of another user.
allocated until that user deallocates it or
privileged user deallocates it.
ALL -- DEVICE NOT IN SYSTEM!
Selected device was not specified during system
cannot be tested by a User Mode Diagnostic.

generation.

ALL -- FEATURE NOT SUPPORTED
Indicates ALLOCATE command is not implemented
Ignore message and proceed with initiation.

for

your

system.

1 The related command and thus this error message are valid only
multiuser protection systems.

2-4

for

HELP! THE CUSTOMER MODE USER

ALL -- PUBLIC DEVICE!
Selected device has been declared a public device.
It cannot be
allocated by any user until it is declared to be a nonpublic
device.
HEL -- INVALID ACCOUNT!
The name or UIC specified is not present in the account file,
the password given is incorrect.
HEL

OTHER USER LOGGED ONl
Another user left this terminal in logged-in state.
used until it is logged out by the BYE command.

It cannot be

HEL -- TERMINAL ALLOCATED TO OTHER USERl
This terminal has been allocated to another user.
It cannot be
used until that user deallocates it or logs out, or a privileged
user deallocates it.
INS -- FILE NOT FOUND
The specified diagnostic was not built and made part of the
system at system generation, or the UMD task-image files are not
present on SY:
at [l,m] where m is 50 for an unmapped system or
54 for a mapped system.
MCR -- NOT LOGGED INl
multiuser protection system requires that you log-in at the
terminal with the HELLO command before issuing any command other
than HELP.
DIAGNOSTIC ERROR MESSAGES
The following error messages might be reported after control has
passed from MCR to the selected diagnostic.

been

* DEVICE OFFLINE *
Selected device is not physically or logically available.

* DEVICE MOUNTED OR ALLOCATED TO OTHER USER *
Indicates that volume on selected device is mounted
(must be
dismounted for diagnostic testing), or that the device has been
allocated to another user (this case can happen if you did not
issue the ALLOCATE command for a multiuser protection system).

1 The related command and thus this error message are valid only
multiuser protection systems.

2-5

for

HELP! THE CUSTOMER MODE USER

* ILLEGAL FUNCTION ·(MAY BE WRONG DIAGNOSTIC) *
Indicates that the wrong diagnostic was initiated, or
requested function is not in the selected diagnostic.

that

the

* DEVICE OR DRIVER NOT AVAILABLE FOR DIAGNOSTICS *
Selected device or its associated
capabilities is not in the system.

driver

with

diagnostic

* INVALID DEVICE OR UNIT *
Device identification
correct.

2.6

(mnemonic

and/or

unit

number)

not

MULTIDEVICE TESTING

Should you wish to initiate concurrent
execution
of
several
diagnostics from the same terminal, each RUN command must include an
explicit task name. The following sequence illustrates initiation of
an RK06 disk.and a TU56 DECtape unit.
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DMl:
On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DMl:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $RK06/TASK=DM1

CONTINUE?

On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DTO;
On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DTO:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $TU56/TASK=DTO

CONTINUE?

You can continue to initiate other diagnostics as you require.
Error messages and
terminal,
but they
number.

summary reports may be interspersed at the
will be explicitly identified by device and unit

2-6

HELP! THE CUSTOMER MODE USER
To terminate a diagnostic before its
specify the task name, for example:

normal

completion,

you

must

(crnL/c)

MCR> ABORT DMl

2.7

LOGICAL BLOCK NUMBERS FROM PHYSICAL ADDRESSES

no.*trk's/cyl)+trk no.)sec's/trk)+sec no.

where all values are decimal.
For example, an RP06 sector (see Section 3.2
parameters) with the address of
Cylinder

000536(octal), 350 (decimal)

Track

000016 (octal), 14 (decimal)

Sector

000013(octal), 11 (decimal)

for

RP06

is logical block number 146619, computed as follows.
LBN

(((350*19)+14)*22)+11
(6650) +14) *22+11
146608+11
146619

Refer to the RSX-llM/M-PLUS MCR Operations Manual.

2-7

data-capacity

•

CHAPTER 3
RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC

...--••CUSTOMER-MODE INITIATION . . . . . . . . . . . ..
(Underlined text indicates required or
Chapter 2 for additional information.)

expected

user

input~

see

Install "scratch" disk pack on disk drive to be tested.
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DBn_:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreian.
>MOUNT DBn:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
(or RP05 or RP06)
START RP04 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? DBn
**WARNING** DBn:
CONTINUE? Y
FORMAT DISR ONLY?

RESIDENT DATA WILL BE DESTROYED **WARNING**
(N or RETURN alone aborts the diagnostic)
(N initiates customer-mode seauence)
(Y formats disk and exits

Diagnostic runs to completion in 2 hours for RP04 OR RPOS, and 2 hours
and 45 minutes for RP06 on a lightly loaded system.
Formattinq
requires approximately 1 hour and 30 minutes for RP04 or RPOS,
and 3
hours for RP06. To exit sooner, type:
(CTRL/C)

MCR>~~

3.1

TEST SUMMARY REPORT

Upon completion of each diagnostic test seauence, the followina report
is displayed.
RP04 UNIT NO~
n
(n=unit number)
PASS COUNT=
TOTAL ERRORS ENCOUNTERED=
TOTAL FUNCTIONS ISSUED=
TOTAL WORDS TRANSFERRED=
END OF RP04 DIAGNOSTIC - TIME OP DAY=hour:minute:second

3-1

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC
"Pass count" and "totals" are
(initiated in service mode only).

cumulative

for

multipass

The following are data-capacity parameters for
RP06 Disk Pack Drives.

the

RP04,

3.2

testing

DISK DRIVE CHARACTERISTICS

RP04 & RPOS

B.fQ§

Cylinders

411

815

Tracks/cylinder

Sectors/Track

Words/Sector

256

3.3

RP05,

and

DIAGNOSTIC DESCRIPTION

The diagnostic tests the ability of the selected disk drive to address
correctly all cylinders, tracks, and sectors of the resident disk
pack, and to write data on, and to read data from, the pack under
selected conditions.
A pack formatting routine is also included.
Neither ECC correction nor "bad sector (block)" processing are
implemented.
The exercises described hereafter are executed in
a
one-pass
uninterrupted sequence for customer mode. The "Related Error Numbers"
following each description appear in error messages for detected fault
conditions;
refer
to
Section
3.4 and Table 3-1 for their
significance.

3.3.1

Addressing Exercises

3.3.1.1 Heads-Positioning Exercise - This exercise determines -that
the heads position correctly at all cylinders of the resident disk
pack. The exercise is conducted in two parts: incremental seek and
cross seek.
For incremental seek, a read-header command (implied seek) alternately
addresses cylinder 0 and cylinder "n," where "n" increments by one for
cylinder address. After each seek of cylinder 0 or cylinder "n," the
exercise verifies that the specified cylinder address was achieved.
For cross seek, a read-header command alternately addresses cylinder
"a," where "a" is initially 0, and cylinder "b," where "b" is
initially the valid, upper-limit cylinder address. After each seek,
"a" is incremented by one and "b" is decremented by one. This part of
the exercise continues until "b" equals O.
Cylinder positioning is
verified by examination after each seek.
(Related Error Numbers are:

2, 3, 4, 5)

3-2

RP04, RPOS, OR RP06. PACK DISK DIAGNOSTIC

I'-'

3.3.1.2 Sector~Addressing Exercise - This exercise determines that
sectors 0 through 21 of the resident disk pack are addressable. Each
sector on track 0 of cylinder 0 is written with a data pattern eaual
to its respective sector number.
Then each sector is read and
verified that it contains the correct data pattern.
All error
conditions are reported.
(Related Error Numbers are:

6, 7, 8)

3.3.1.3 Track-Addressing and Crossover
Exercise - This
exercise
determines that all tracks are addressable, and that a 2-sector data
transfer starting at the last sector of any track exceµt the last
track of the last cylinder results in a crossover to the first sector
of the successive track. The exercise, first, issues a 512-word write
command starting at sector 21 of track 0 and each successive ttack
through track 18 on cylinder 0.
The data pattern written is the
respective track number. The exercise then reads the first two words
from sector O of track 1 and each successive track through track 18 on
cylinder O, and sector 0 of track 0 on cylinder 1. If crossover
occurred, the data pattern read should be the number of the preceding
track
(for example, 0 in sector O, track 1, cylinder O; 3 in sector
0, track 4, cylinder 0; and 18 in sector O, track 0, cylinder 1).
All error conditions are reported.
(Related Error Numbers are:

,'-"'

9, 10, 11)

3.3.1.4 Cylinder-Addressing and Crossover Exercise - This exercise
determines that all cylinders are addressable, and that a 2-sector
data transfer starting at the last sector of any cylinder except the
last results in a crossover to the first sector of the successive
cylinder. The exercise, first,
issues a 512-word write command
starting at sector 21 of track 18 on cylinder 0 and each successive
cylinder to the valid upper limit. The data pattern written is the
respective cylinder number.
The exercise then reads the first two
words from sector 0, track 0 on cylinder 1 and each successive
cylinder through the valid upper limit. If crossover occurred, the
data pattern read should be the number of the preceding cylinder
(e.g., 0 in sector 0, track 0, cylinder l; and 3 in sector O, track
0, cylinder 4). All error conditions are reported.
(Related Error Numbers are:

12, 13, 14)

3.3.1.5 Partial-Write Exercise - This exercise determines that a
write on a sector of less than 256 words results in the remainder of
the sector being zero-filled. First, the exercise writes sector 0 on
track 0 of cylinder 0 with an all-l's pattern. Then, the exercise
issues a 2-word write command, all-l's data, to the same sector
address.
Finally, the exercise reads the sector's contents and
verifies that all but the initial two words are zero-filled.
All
error conditions are reported.
(Related Error Numbers are:

15, 16, 17, 18)

3-3

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC
3.3.2

Data-Reliability Exercise

This exercise determines the reliability of the disk drive to write
and read data of various patterns at all valid disk addresses. The
data patterns used are:
1.

All 0 Is

All l's

Checkerboard (alternate l's and O's)

Floating l's (sequenced bit-position advancement through each
word)

Random data

Count pattern (from "l", add 1 for each word written)

NOTE
In customer mode, only the floating-l's
pattern is implemented to reduce the run
time for the complete sequence.
Each pattern is written at all disk addresses, and then read back
eight times for verification and to expose possible read-reduction
problems. Detection of any error while reading causes the exercise to
report the failing address and then to attempt up to eight retries to
read the data. If a retry is successful, the exercise reports the
error recovered after "n" retries and advances to the next disk
address. If the read remains unsuccessful after eight retries, the
exercise terminates recovery and advances to the next disk address.
The absence of a "recovered" report signifies an
unsuccessful
recovery.
(Related Error Numbers are:

3.3.3

19, 20)

Random Exercise

This exercise determines that the drive can address randomly selected
disk-pack
addresses
and
execute
random-length
transfers
ofrandom-patterned data to and from those pack areas.
The exercise
sequence, which is repeated 512 times, is:
1.

Develop a valid, random cylinder-, track-, and sector-address
combination.

Initiate a write transfer of a random-length, random-data
pattern, beginning at the random disk address. The number of
words is two or more, and not greater than 512.

Upon completion of the
another random address.

Initiate eight read transfers of the previously written
random data with intervening seeks to random addresses (the
purpose of this command sequence is to expose read-reduction
problems or parity errors caused by a vibrating head).

write

Verify the data returned.
3-4

transfer,

issue

seek

~I\.

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC

Detection of any error while reading causes the exercise to report the
failing address and then to attempt up to eight retries to read the
data. If a retry is successful, the exercise reports the error
recovered after "n" retries and advances to the next disk address. If
the read remains unsuccessful after eight retries, the exercise
terminates recovery and advances to the next disk address. The
absence of a "recovered" report signifies an unsuccessful recovery.
(Related Error Numbers are:

3.3.4

21, 22, 23, 24)

Formatting Routine

The formatting routine prepares disk packs for use
In sequencev the routine:

with

the

•

Writes the complete header for each sector,

•

Verifies the address content of each sector header, and

•

Exits.

PDP-11.

Formatting, when selected, always runs to completion and exits.
The sector headers are written one at a time. Sectors that cannot be
formatted or verified are identified by the cylinder-track-sector
addresses that follow the messages
UNABLE TO FORMAT SECTOR AT ADDRESS
HEADER VERIFY ERROR AT ADDRESS
Satisfactory completion of the
message

format

process

signaled

the

formatted

and/or

FORMATTING COMPLETE
The message
FORMATTING FAILED
indicates that one or more
verified.

sectors

(Related Error Numbers are:

25, 26, 27, 28)

3.4

could

not

ERROR MESSAGES

Fault conditions detected during the test sequence are reported at the
initiating terminal:
they are classified as equipment errors or
data-compare errors.
Equipment errors are those conditions that
result in the setting of the "error" bit, Bit 14 of the Drive Status
Register (RPDS). Data-compare errors occur when the diagnostic finds
data other than the data expected in data-transfer actions. Some
conditions may cause both an equipment error and a data-compare error.
The following representations illustrate the context of the various
error messages.
Table 3-1 lists the error numbers and their related
fault conditions. Appendix B defines the register contents displayed
in the error messages.

3-5

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC
Equipment error-message format:
RP04
ERROR NO.
RPCSl =
RPBA
RPCS2
RPERl =
RPLA
RPMR
RPSN
RPDC
RPER2
RPECl
RPWC
RPDA
RPDS
RPAS
RPDB
RPDT
RPOF
RPCC
RPER3
RPEC2

UNIT NO. m
n

Control and Status 1 Register contents
Bus Address Register contents
Control and Status 2 Register contents
Error Register 1 contents
Look Ahead Register contents
Maintenance Register contents
Serial Number Register contents
Desired Cylinder Register contents
Error Register 2 contents
ECC Position Register contents
Word Count Register contents
Desired Sector/Track Address Register
contents
Drive Status Register contents
Attention Summary Register contents
Data Buf£er Register contents
Drive Type Register contents
Offset Register contents
Current Cylinder Register contents
Error Register 3 contents
ECC Pattern Register contents

Data-compare error-message format:
RP04
ERROR NO. n
EXPECTED =
RECEIVED

UNIT NO. m
Data expected
Data received

Disk-address error-message format:
RP04
ERROR NO. n
DISK ADDRESS
CYLINDER
EXPECTED
RECEIVED
TRACK
EXPECTED
RECEIVED
SECTOR
EXPECTED
RECEIVED

UNIT NO. m
DID NOT UPDATE CORRECTLY
Cylinder expected
Cylinder received
Track expected
Track received

"'·

Sector expected
Sector received

Other error messages:
CONTENTS OF RPCC INCORRECT
HEADER VERIFY ERROR AT ADDRESS
UNABLE TO FORMAT SECTOR AT ADDRESS
REREAD SAME DATA n TIMES BEFORE ERROR
ERROR NO. x RECOVERED AFTER y RETRIES

3-6

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC
Table 3-1
Error Conditions
Error Number and
Associated Test
Exercise

Fault Condition

Recalibration:
1

Error bit
function.

was

set

during

home-seek

Heads Positioning:
2

Error bit was set after a read-header
command was issued to cylinder O.

Error bit was set after a read-header
command was issued to a cylinder in the
range 1 through the valid upper limit.

Error bit was set after a read-header
command
was
issued to the cylinder
address being incremented from 0 through
the valid upper limit.

Error bit was set after a read-header
command
was
issued to the cylinder
address being decremented from the valid
upper limit.

Sector Addressing:
6

Error bit was set while exercise was
writing a sector with a data pattern
egual to its respective sector number.

Error bit was set while exercise was
reading a sector ·with a data pattern
equal to its respective sector number.

Data-compare error.
Data pattern read
from a sector (0 through 21) on track 0
of cylinder 0 does not contain
the
respective sector number.

Track-Addressing and Crossover:
9

Error bit was set while exercise was
writing a 512-word data transfer starting
at the last sector on a track of cylinder
0.
The data pattern is the respective
track number.
(continued on next page)

3-7

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC
Table 3-1 (Cont.)
Error Conditions
Error Number and
Associated Test
Exercise

Fault Condition

Track-Addressing and Crossover:

(Cont.)

Error bit was set while exercise was
reading the first two words of the first
sector on a track.
The data pattern is
the preceding track number.

Data-compare error.
Data pattern read
from the first two words of the first
sector of a track does not contain the
number of the preceding track.

Cylinder-Addressing and Crossover:
12

Error bit was set while exercise was
writing a 512-word data transfer starting
at the last sector on the last track of a
cylinder.
The
data pattern is the
respective cylinder number.

Error bit was set while exercise was
reading the first sector on the first
track of a cylinder. The data pattern is
the preceding cylinder number.

Data-compare error.
Data pattern read
from the first sector on the first track
of a cylinder does not contain the number
of the preceding cylinder.

"""'·

Partial Write:
15

Error bit was set while exercise was
writing sector 0 on track 0 of cylinder 0
with all-l's data.

Error bit was set while exercise was
writing a 2-word transfer of all-l's data
in sector 0 on track 0 of cylinder O.

Error bit was set while exercise was
reading the contents of sector 0 on track
0 of cylinder 0.

Data-compare error.
Data pattern read
does not contain l's in the initial two
words and O's in the remainder of the
sector.
(continued on next page)

3-8

...............................................................................................................1..-.

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC

Table 3-1 (Cont.)
Error Conditions
Error NumbE~r and
ABsociated Test
E,rnrcise

Fault Condition

Data-Reliability or Interactive-Data Test:
19

Error bit was
writing
the
pattern.

Error bit was set while exercise was
reading a test pattern from the disk
pack.

set while
disk pack

exercise was
with a test

Condition
may
also
occur
as
a
data-compare error.
Data read from the
pack does not contain the test pattern.
R~andom:

Error bit was set while exercise was
writing
a
random-data pattern at a
randomly selected address.

Error bit was set after exercise issued a
seek command with a random address.

Error bit was set while exercise was
reading random data from a previously
written random address.

Data-compare error.
Data pattern
does not contain the random data.

read

Formatting:
25

Error bit was set while routine was
writing sector-header patterns to format
a track.

Error bit was set while routine was
reading a sector header pattern from a
formatted track.

Word 1 of the header for the indicated
sector does not agree with the expected
data.

Word 2 of the header for the indicated
sector does not agree with the expected
data.
(continued on next page)

3-9

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC
Table 3-1 (Cont.)
Error Conditions
Error Number and
Associated Test
Exercise

Fault Condition

Interactive-Address Test:

3.5

Error bit was set after a read-header
command
issued
to the "first"
was
cylinder selected.

Error bit was set after a read-header
issued to the "second"
command
was
cylinder selected.

SERVICE-MODE INITIATION

Initiation of this mode demands a knowledge of
console-switch
selection
(see Section 3.6),
test-param.eter selection (see Section
3.7), interactive testing (see Sections 3.9 and 3.10), and the content
of Appendix A. Underlined text in this procedure indicates required
or expected user input.
Install "scratch" disk pack on disk drive to be tested.
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DBn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DBn:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $RP04

(or RPOS or RP06)

START RP04 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? DBn
**WARNING** DBn: RESIDENT DATA WILL BE DESTROYED **WARNING**
CONTINUE? SERVICE
(N or RETURN alone aborts the diagnostic)
TEST PARAMETERS (OCTAL)= nnnnnn
CONSOLE SWITCH FOR INTERVENTION (DECIMAL)= n
The selected test sequence commences after you type RETURN you have
responded to all inquiries,
if any,
that occur as a result of
test-parameters selection.

3.6

CONSOLE SWITCH FOR INTERVENTION

3-10

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC

For those systems without a CPU switch console or without the GET
SENSE SWITCHES directive, respond to the message "CONSOLE SWITCH ••• "
with O.

3.7

TEST-PARAMETER SELECTION

Customer mode allows only a fixed sequence of the diagnostic's
Service mode,
however, permits customization of the test
through the test-parameters facility. Table 3-2 describes the
options available to you as a service-mode user. You select
by logically ORing their related octal codes to form a 6-digit
(leading zeros need not be expressed) for entry in response
PARAMETERS (OCTAL)=.

tests.
content
various
options
number
to TEST

NOTE
A response of 0 implies that no tests
are to be performed.
The diagnostic
issues the test summary report and then
terminates.
The table also indicates those options that are automatically selected
for customer-mode execution.
The "bit" references in the option
descriptions refer to the bit positions of a test-parameters status
word that is monitored by the diagnostic.
Table 3-2
Test-Parameter Options

Option Description

Selection
Code
(Octal)

In
Customer
Mode

STOP ON ERROR (Bit 15):

100000

40000

20000

Test sequence waits up to 30 minutes
before terminating.
User may abort
stop by setting console switch selected
for interventiono
LOOP ON ERROR (Bit 14):
Test sequence loops on the failing
instruction
sequence.
User should
intervene
and
select
new
test
parameters that exclude this option.
INHIBIT ERROR MESSAGE PRINTOUT (Bit 13):
Prevents appearance of all diagnostic
error messages except_ the test summary
report that appears at the end of each
sequence pass.

'-"'

(continued on next page)

3-11

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC
Table 3-2 (Cont.)
Test-Parameter Options

Option Description
BELL (Bit 12):
The terminal bell rings for each
detected.

Selection
Code
(Octal)

In
Customer
Mode

10000

4000

2001

2002

Yes

error

to
two
3.9

INTERACTIVE-DATA TEST (Bits 10 & 1):
Allows the service-mode user to specify
explicit
conditions
for
data-reliability testing of the drive
(see Section 3.10 for details).
LIMIT DATA-COMPARE ERROR MESSAGES (Bit 5):
Display an error message only for
the
first
data-compare
error condition
detected during
a
specified
data
transfer.
The default is: display an
error
message
for
up
to
three
data-compare error conditions detected
during retries of a specified data
transfer.
TEST SEQUENCE SELECTION (Bits 0-4):
A)

Select addressing exercise (see
Section 3.3.1).

Yes

Select data-reliability exercise
(see section 3.3.2).

Yes

(continued on next page)

3-12

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC
Table 3-2 (Cont.)
Test-Parameter Optjons
Selection
Code
(Octal)

Option Description
TEST SEQUENCE SELECTION (Bits 0-4):

In
Customer
Mode

(cont.)

Select random exercise (see Section
3.3.3) ~

Yes

Select random exercise with interread seeks inhibited to reduce run
time (see Section 3.3.3).

Select formatting routine without
other exercises;
routine always
runs to completion and exits
(see Section 3.3.4).

Selectable

3. 8

SERVICE-·MODE INTERVENTION/RESTART/TERMINATION

You can intervene in (stop) the test sequence pass at any time by
changing from its current setting (0 to 1 or 1 to 0) the previously
selected CPU console switch. Such action causes the diagnostic to
suspend testing and await response to the following message sequence.
TES'l~

PARAMETERS (OCTAL)=

Type an octal value
(other than 0)
to
select new test parameters (or re-enter the
old parameters, which are not saved at
intervention), or
type 0 to terminate the diagnostic.

If new (or the old) parameters are entered, the following
displayed.
RES'I'ART?

message

Type Y to abort the suspended test sequence
and
initiate the new sequence at the
beginning, or
Type N to allow the suspended test sequence
to
run
to completion before the new
sequence commences.

For those systems not equipped with a CPU switch console or not
implemented with the GET SENSE SWITCHES directive, the user wishing to
alter test parameters must first terminate the diagnostic by typing:
(cmL/c)
MCR>~_!

and then reinitiate the diagnostic with new
parameters.
intervention and restart provisions are not accessible.

3-13

The

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC

3.9

INTERACTIVE-ADDRESS TEST

This test oscillates the disk drive head (that is, continuous
in-and-out motion) between the two cylinders you specify. After
test-parameter selection, the test is initialized by your typing of
valid cylinder numbers in the range 0 through 814. for an RP06 drive
or 0 through 410. for an RP04 or RP05 drive in response to the
inquiries.
FIRST CYLINDER =
SECOND CYLINDER =
Should you inadvertently type a number greater
upper limit, the inquiry repeats.

than

Once initiated, the head oscillation
with the selected console switch
command.

until you intervene
the diagnostic by MCR

continues
or abort

the

appropriate

The function of the test is to issue seek commands alternately to the
two specified cylinders. An equipment error message is displayed if
the seek function fails.
(Related Error Numbers are:

3.10

29, 30)

INTERACTIVE-DATA TEST

than

512.

less

than

the

DO YOU WISH TO SPECIFY SECTOR ADDRESS?
Type Y if a specified sector address is to be tested.
Type N if all data surfaces of the disk pack are to be written on
and/or read from.
The inquiries, which follow, for cylinder,
track, and sector numbers are inhibited.
CYLINDER=
This inquiry appears
only
if
you
have
requested
the
sector-addressing feature.
Type the desired cylinder number in
the range 0 through 814. for an RP06 or 0 through 410.
for a
RP04 or RP05 drive.
If you type a number greater than the
appropriate upper limit, the inquiry repeats.

3-14

RP04, RPOS, OR RP06 PACK DISK DIAGNOSTIC
TRP..CK=
This inquiry appears
only
if
you
have
requested
the
sector-addressing feature.
Type the desired track number in the
range 0 through 18 {decimal).
If you type a number greater than
18., the inquiry repeats.
SECTOR=
This inquiry appears
only
if
you
have
reauested
the
sector-·addressing feature.
Type the desired sector number in the
range 0 through 21 {decimal).
If you type a number greater than
21., the inquiry repeats.
PA'l~TERN

NO.==

Type the appropriate number; as indicated below,
to select a
specific stored data pattern or the combination of all stored
patterns for use in exercising the disk drive.
Stored Patterns
All O's
All l's
Checkerboard
Floating l's
Random l's and O's
Count pattern {full-word, binary, sequential)
Run above patterns in sequence

0
1

2
3
4

5
6

You can specify your own pattern to be used in place of the
stored patterns by typing a full-word {6-digit) octal value in
response to the above inquiry.
WRITE?
Type Y to permit performance of write functions during the test.
Type N to inhibit write functions.

Type Y to permit performance of read functions during the test.
Type N to inhibit read functions.
NOTE
An N response to both inquiries
inquiries - will
invalid.
The
repeated.

is
be

With selection of the read-condition established, the test commences
and continues until you intervene with the selected console switch or
abort the diagnostic by MCR command.
{Related Error Numbers are:

19, 20)

3-15

CHAPTER 4

RFll FIXED-HEAD DISK DIAGNOSTIC

. -......1.CUSTOMER-MODE INITIATION .......................
(Underlined text indicates required or
Chapter 2 for additional information.)

expected

user

input:

see

On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DFO!
On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUN'I.1 DFO: /FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $RFll
START RFll DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVIC8? DFO
**WARNING** DFO:
CONTINUE? X

RESIDENT DATA WILL BE DESTROYED **WARNING**
(N or RETURN alone aborts the diagnostic)

Diagnostic testing of all valid drives runs
minutes per drive for a lightly loaded system.
(crnLtc):

to completion in 35
To exit sooner, type:

MCR>ABORT

~
4.1

TEST SUMMARY REPORT

Upon completion of each diagnostic test sequence, the following report
is displayedn
RFll UNIT NO.
0
PASS COUNT=
TOTAL ERRORS ENCOUNTERED=
TOTAL FUNCTIONS ISSUED=
TOTAL WORDS TRANSFERRED=
END OF RFll DIAGNOSTIC - TIME OF DAY=hour:minute:second
"Pass count" and "totals" are
(initiated in service mode only.)

cumulative

4-1

for

multipass

testing

RFll FIXED-HEAD DISK DIAGNOSTIC
4.2

DISK CHARACTERISTICS

An RFll disk subsystem consists of the RFll controller and up to eight
RSll fixed-head disk drives, each with parameters as follows:
Tracks

128

Sectors/Track

Words/Sector

256

ThE~ entire subsystem is identified externally as DFO

because, unlike
other disks, the RFll automatically implements upward data transfer
crossovers between available drives without
requiring
external
reference.
In this regard, the RFll drives appear to be a continuous
disk surface containing unit multiples of the storage parameters.
Drive selection (0-7) is, nevertheless, an explicit and integral
element of track addressing to define the starting track and sector
addresses for a data transfer to or f~om this disk.

4.3

DIAGNOSTIC DESCRIPTION

The diagnostic tests the ability of the RFll to address correctly all
tracks and sectors of the disk, and to write data on, and to read data
from, the disk under selected conditions. Neither ECC correction nor
"bad sector (block)" processing are implemented.
The exercises described hereafter are executed in
a
one-pass
uninterrupted sequence for customer mode. The "Related Error Numb~rs"
following each description appear in error messages for detected fault
Section
4.4 and Table 4-1 for their
conditions;
refer
to
significance.

4.3.1

Addressing Exercises

4.3.1.1 Sequential-Addressing Exercise - This exercise
determines
that the 128 tracks and the eight 256-word sectors per track for each
drive are addressable in sequence. The exercise first writes each
sector with a data pattern consisting of the following information in
each word:
Bits 8-15

Respective track number, right justified.

Bits 6,7

Unused.

Bits 3-5

Respective drive number

Bits 0-2

Respective sector number

The exercise then reads each sector and
agreement
with the written pattern.
reported.
(Related Error Numbers are:

2, 3, 4)

4-2

verifies its contents
All error conditions

for
are

RFll FIXED-HEAD DISK DIAGNOSTIC
4.3.l.2 Random-Addressing Exercise - This exercise determines that
the disk responds correctly to random addressing. The exercise issues
a 2-word read with a randomly selected track-sector address to access
the data written by the previous exercise. The data read is compared
to the expected pattern (the respective track number,
sector number,
and drive number)
and reported if in disagreement. The reading
continues until 512 random addresses have been checked.
All error
conditions are reported.
(Related Error Numbers are:

4.3.2

5, 6)

Data-Reliability Exercise

This exercise determines the reliability of the disk to write and read
data of various patterns at all disk addresses. The data patterns
used are:

All 0 Is

All l's

Checkerboard (alternate l's and O's)

Floating l's (sequenced bit-position advancement through each
word)

Random data

Count pattern (from "l", add 1 for each word written)
NOTE
In customer mode, only the floating-l's
pattern is implemented to reduce the run
time for the complete test sequence.

Each pattern is written at all disk addresses,
and then read back
eight: times for verification and to expose possible read-reduction
problems.
Detection of any error while reading causes the exercise to
report the failing address and then to attempt up to eight retries to
read the data~
If a retry is successful,
the exercise reports the
error recovered after "n" retries and advances to the next disk
address.
If the read remains unsuccessful after eight retries,
the
exercise terminates recovery and advances to the next disk address.
The absence of a "recovered" report signifies an
unsuccessful
recovery.
{Related Error Numbers are:

4.3.3

7, 8)

Random Exercise

This exercise determines that the drive can address randomly selected
disk addresses and execute random-length transfers of random-patterned
data to and from those areas.
The exercise sequence, which is
repeated 1024 times, is:
1.

Develop
a
combination.

valid,

random

4-3

track-

and

sector-address

RFll FIXED-HEAD DISK DIAGNOSTIC
2.

Initiate a write transfer of a random length, random data
pattern, beginning at the random disk address. The number of
words is two or more, and not greater than 512.

Initiate eight
random data.

Verify the data returned.

read

transfers

the

previously

written

4.4

9, 10, 11)

ERROR MESSAGES

Fault conditions detected during the test sequence are reported at the
initiating terminal:
they are classified as equipment errors or
data-compare errors.
Equipment errors are those conditions that
result in the setting of the "error" bit, Bit 15 of the Control and
Status Register (RFCS). Data-compare errors occur when the diagnostic
finds data other than the data expected in data-transfer actions.
Some conditions may cause both an equipment error and a data-compare
error.
The following representations illustrate the context of the various
error messages.
Table 4-1 lists the error numbers and their related
fault conditions. Appendix B defines the register contents displayed
in the error messages.
Equipment error-message format:
RFll
ERROR NO.
RFCS
RFWC
RFBA
RFDA
RFER
DRIVE NO.

UNIT NO.

Control and Status Register contents
Word Count Register contents
Bus Address Register contents
Disk Address Register contents
Error Register contents
n

Data-compare error-message format:
RFll
ERROR NO.
EXPECTED
RECEIVED

UNIT NO.

m
Data expected
Data received

4-4

RFll FIXED-HEAD DISK DIAGNOSTIC

Disk-address error-message format:
RFll
UNIT NO. 0
ERROR NO. m
DISK ADDRESS DID NOT UPDATE CORRECTLY
DRIVE
EXPECTED
Drive expected
RECEIVED = Drive indicated
TRACK
EXPECTED = Track expected
RECEIVED
Track indicated
SECTOR
EXPECTED
Sector expected
RECEIVED
Sector indicated
Other error messages:
REREAD SAME DATA n TIMES BEFORE ERROR
ERROR NO.

x RECOVERED AFTER y RETRIES

'-'

Table 4-1
Error Conditions
Error Number and
Associated Test
Exercise

Fault Condition

Initialization:
1

Nonexistent disk error.
Error bit was
set while exercise was reading the first
sector of each drive to determine the
number of RFll drives available at the
time of RSX-llM system generation.

Sequential Addressing:
was
the
and

Error bit was set while exercise
writing
a
256-word sector with
sector's address (drive,
track,
sector numbers).

Error bit was set while exercise was
reading a sector. The pattern expected
is the sector's address (drive, track,
and sector numbers).

Data-compare error.
Data-pattern read
from
a sector does not contain the
sector's address (drive,
track,
and
sector numbers).
(continued on next page)

4-5

RFll FIXED-HEAD DISK DIAGNOSTIC
Table 4-1 (Cont.)
Error Conditions
Error Number and
Associated Test
Exercise

Fault Condition

Random Addressing:
5

Error bit was set while exercise was
reading
the initial two words of a
sector.

Data-compare error. The content of the
initial two words read from a sector does
not contain the sector's address (track
and sector numbers).

Data-Reliability or Interactive-Data Test:
7

Error bit was set while exercise was
writing the disk with a test pattern.

Error bit was set while exercise was
reading a test pattern from the disk.
Condition
may
also
occur
as
a
data-compare error.
Data read from the
disk does not contain the expected data.

Random:

4.5

Error bit was set while exercise was
writing
a
random-data pattern at a
randomly selected address.

Error bit was set while exercise was
reading random data from a previously
written random address.

Data-compare error. The content of the
data pattern read from a sector does not
contain the
random
data
previously
written.

SERVICE-MODE INITIATION

Initiation of this mode demands a knowledge of
console-switch
selection (see Section 4.6), test-parameter selection (see Section
4.7), interactive testing (see Sections 4.9 and 4.10), and the content
of Appendix A. Underlined text in this procedure indicates required
or expected user input.
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DFO:
On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DFO:/FOR

4-6

RFll FIXED-HEAD DISK DIAGNOSTIC

On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $RF11
START RFll DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? DFO
**WARNING** DFO:
RESIDENT DATA WILL BE DESTROYED **WARNING**
CONTINUE? SERVICE
(N or RETURN alone aborts the diagnostic)
TEST PARAMETERS (OCTAL)= nnnnnn
CONSOLE SWITCH FOR INTERVENTION (DECIMAL) = D
TEST ALL DRIVES?
(Y tests all valid drives)
(N initiates WHICH DRIVE? inquiry)
WHICH DRIVE?
Type value (0-7) to test one drive.
Inquiry repeats if entry exceeds maximum
valid drive number (set during system
generation).
The selected test sequence commences upon RETURN after you have
responded to all inqu1r1es,
if any,
that occur as a result of
test-parameters selection.
~·

4.6

CONSOLE SWITCH FOR INTERVENTION

Service-mode initialization requires that you select a CPU console
switch (0-15) for intervention in the test sequence when, for example,
you desire to change test parameters. The facility to select more
than one switch is useful only if more than one device is to be tested
concurrently;
that is, you can assign a unique switch to each
diagnostic.
For those systems without a CPU switch console or without the GET
SENSE SWITCHES directive, respond to the message "CONSOLE SWITCH ••• "
with 0.

4.7

TEST-PARAMETER SELECTION

Customer mode allows only a fixed sequence of the diagnostic's tests.
Service mode,
however,
permits customization of the test content
through the test-parameters facility.
Table 4-2 describes the various
options available to you as a service-mode user. You select options
by logically ORing their related octal codes to form a 6-digit number
(leading zeros need not be expressed) for entry in response to TEST
PARAMETERS (OCTAL)=.
NOTE
A response of 0 implies that no tests
are to be performed.
The diagnostic
issues the test summary report and then
terminates.
The table also indicates those options that are automatically selected
for customer-mode execution.
The "bit" references in the option
descriptions refer to the bit positions of a test-parameters status
word that is monitored by the diagnostic.

4-7

RFll FIXED-HEAD DISK DIAGNOSTIC
Table 4-2
Test-Parameter Options

Option Description

Selection
Code
(Octal)

In
Customer
Mode

STOP ON ERROR (Bit 15):

100000

40000

20000

10000

4000

2002

Prevents
appearance
of
all
diagnostic error messages except
the test summary report
that
appears
at
the end of each
sequence pass.
BELL (Bit 12):
The terminal bell rings for
error detected.

each

MULTIPASS EXECUTION (Bit 11):
Test sequence repeats until user
interveness
The updated test
summary report is displayed at
the end of each pass.
INTERACTIVE-DATA TEST (Bits 10 & 1):
Allows the service-mode user to
specify explicit conditions for
data reliability testing of a
drive or the entire disk (see
Section 4.9 for details).

(continued on next page)

4-8

RFll FIXED-HEAD DISK DIAGNOSTIC
Table 4-2 (Cont.)
Test-Parameter Options
Selection
Code
(Octal)

Option Description
LIMIT DATA-COMPARE ERROR MESSAGES
(Bit 5):

In
Customer
Mode

Yes

Display an error message only for
the
first
data-compare error
condition
detected
during
a
specified
data transfer.
The
default is:
display an error
message
for
up
to
three
data-compare
error
conditions
detected
during retries of a
specified data transfer.
TEST SEQUENCE SELECTION (Bits 0-3):
A)

Select
addressing
(see Section 4.3.1).

Select
data-reliability
exercise (see Section 4.3.2).

Yes

Select random exercise
Section 4.3.3).

Yes

4.B

exercises

(see

SERVICE-MODE INTERVENTION/RESTART/TERMINATION

Type an octal value (other than 0) to
select new test parameters (or re-enter the
old parameters, which are not saved at
intervention) , or
type 0 to terminate the diagnostic.

If new (or the old) parameters are entered, the following
displayed.
RESTART?

message

Type Y to abort the suspended test seauence
and
initiate the new sequence at the
beginning, or
type N to allow the suspended test sequence
to
run
to completion before the new
sequence commences.

4-9

RFll FIXED-HEAD DISK DIAGNOSTIC
For those systems not equipped with a CPU switch console or not
implemented with the GET SENSE SWITCHES directive, the user wishing to
alter test parameters must first terminate the diagnostic by typing:
(cTRL/C)

MCR>ABORT
and then reinitiate the diagnostic with new
parameters.
intervention and restart provisions are not accessible.

4.9

The

INTERACTIVE-DATA TEST

This test allows you to specify the conditions for determining the
data reliability of the entire disk or a particular drive. After
test-parameter selection, the test is initialized by your typing of
valid and appropriate responses to the test's inquiries as noted
hereafter.
WORD COUNT=
Type a value to indicate the desired upper limit of the data
buffer to be used in write/read data transfer functions (the
value cannot exceed 512. and must be 2 or more).
If you type a value greater
inquiry repeats.

than

512.

less

than

the

DO YOU WISH TO SPECIFY THE SECTOR ADDRESS?
Type Y if a specified sector address is to be tested.
Type N if all data surf aces of the disk are to be written on
and/or read from.
The inqu1r1es, which follow, for track and
sector numbers are inhibited.
TRACK=
This inquiry appears
only
if
you
have
requested
the
sector-addressing feature. Type the desired track number in the
range 0 through 127 (decimal). If you type a number greater than
127., the inquiry repeats.
SEC'rOR=
This inquiry appears
only
if
you
have
reauested
the
sector-addressing feature. Type the desired sector number in the
range 0 through 7. If you type a number greater than 7, the
inquiry repeats.

4-10

RFll FIXED-HEAD DISK DIAGNOSTIC
PATTERN NO.=
Type the appropriate number, as indicated below,
to select a
specific stored data pattern or the combination of all stored
patterns for use in exercising the disk drive.

'-"'

Stored Patterns

No.

All O's
All l's
Checkerboard
Floating l's
Random l's and O's
Count pattern (full-word, binary, sequential)
Run above patterns in sequence

0
1
2

3
4

5
6

You can specify your own pattern to be used in place of the
stored patterns by typing a full-word (6-digit) octal value in
response to the above inquiry.
WRITE?
Type Y to permit performance of write functions during the test.
Type N to inhibit write functions.
READ?
Type Y to permit performance of read functions during the test.
Type N to inhibit read functions.
NOTE
An N response to both inquiries
invalid.
The
inquiries
will
repeated.

'-"'

is
be

7, 8)

4-11

CHAPTER 5
RKOS CARTRIDGE DISK AND RK05F FIXED DISK DIAGNOSTIC

. . CUSTOMER-MODE INITIATION . . . . . . . . . . . ..
(Underlined text indicates required or
Chapter 2 for additional information.)

expected

user

input~

see

Install "scratch" disk cartridge in RKOS disk drive to be tested.
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DKn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DKn:/FOR
On both RSX-·llM and RSX-llM-PLUS systems, proceed as follows.
>RUN ~KOS
START RKOS DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE"? DKn
**WARNING** DKn:
CONTINUE? Y
FORMAT DISK-ONLY?

RESIDENT DATA WILL BE DESTROYED **WARNING**
(N or RETURN alone aborts the diagnostic)
(N initiates customer-mode seouence)
(Y formats disk and exits)

Diagnostic runs to completion in 25 minutes
system.
Formatting requires approximately
sooner, type:

for
a
lightly loaded
20 minutes.
To exit

(CTRL/C)

MCR>AB<IB!

5.1

TEST SUMMARY REPORT

Upon completion of each diagnostic test sequence, the following report
is displayed.
RKOS UNIT NO.
n
(n=unit number)
PASS COUNT=
TOTAL ERRORS ENCOUNTERED=
TOTAL FUNCTIONS ISSUED=
TOTAL WORDS TRANSFERRED=
END OF RKOS DIAGNOSTIC - TIME OF DAY=hour:minute:second
"Pass count"
and "totals" are
(initiated in service mode only).

cumulative

5-1

for

multipass

testing

RKOS CARTRIDGE DISK AND RKOSF FIXED DISK DIAGNOSTIC
5.2

DISK DRIVE CHARACTERISTICS

The following are data-capacity
Disk.
The RK05F Fixed Disk
selected RK05 units.
Cylinders

parameters for the RK05 Cartridge
is equivalent to two independently

200+3

Tracks/Cylinder

Sectors/Track

Words/Sector

256

The "spare" cylinders (210-203) cannot be addressed.

5.3

DIAGNOSTIC DESCRIPTION

The diagnostic tests the ability of the selected disk drive to address
correctly all cylinders, tracks, and sectors of the resident disk
cartridge, and to write data on, and to read data from, the cartridge
under selected conditions.
A formatting routine is also included.
Neither ECC correction nor "bad sector (block)" processing are
implemented.
The exercises described hereafter are executed in
a
one-pass
uninterrupted sequence for customer mode. The "Related Error Numbers"
following each description appear in error messages for detected fault
conditions;
refer
to
Section
5.4 and Table 5-1 for their
significance.

5.3.1

Addressing Exercises

5.3.1.1 Heads-Positioning Exercise - This exercise determines that
the heads position correctly at all cylinders of the resident disk
cartridge. The exercise is conducted in two parts: incremental seek
and cross seek.
For incremental seek, a read-header command (implied seek) alternately
addresses cylinder 0 and cylinder "n," where "n" increments by one for
each seek to it for the range of 1 through 199. After each seek of
cylinder 0 or cylinder "n," the exercise verifies that the specified
cylinder address was achieved.
For cross seek, a read-header command alternately addresses cylinder
"a," where "a" is initially 0, and cylinder "b," where "b" is
initially 199. After each seek, "a" is incremented by one and "b" is
decremented by one.
This part of the exercise continues until "b"
equals O. Cylinder positioning is verified after each seek.
(Related Error Numbers are:

1, 2, 3, 4, 5)

5.3.1.2 Sector-Addressing Exercise - This exercise determines that
sectors 0 through 11 of the resident disk cartridge are addressable.
Each sector on track 0 of cylinder 0 is w~itten with a data pattern

5-2

........·,

_;~~,

-.-

..
·

RKOS CARTRIDGE DISK AND RKOSF FIXED DISK DIAGNOSTIC
equal to the sector number. Then each sector is read and verified
that it contains the correct data pattern. All error conditions are
repoirted.
(Related Error Numbers are:

6, 7, 8)

5.3.1.3 Track-Addressing Exercise - This exercise determines that
tracks 0 and 1 are addressable. Sector 0 on each track is written
with a data pattern consisting of the respective track number.
Then,
each sector is read and verified that it contains the correct data
pattern. All error conditions are reported.
(Related Error Numbers are:

9, 10, 11)

5.3.1.4 Cylinder-Addressing Exercise - This exercise determines that
all cylinders arE~ addressable. Sector O of each cylinder, O through
199, is written with a data pattern consisting of the respective
cylinder number.
Then,
each sector 0 is read and verified that it
contains the correct data pattern. All error conditions are reported.
(Related Error Numbers are:

12, 13, 14)

5.3.1.5 Track-Crossover Exercise - This exercise determines that a
2-sector data transfer starting at the last sector of a track results
in a crossover to the first sector of the successive track.
The
exercise first issues a 512-word write command starting at sector 11
of track 0 on cylinder O:
the data pattern written is all l's.
The
exercise then reads sector 0 on track 1 of cylinder 0 and verifies
that the data pattern is all l's. All error conditions are reported.
(Related Error Numbers are:

15, 16, 17)

5.3.1.6 Cylinder-Crossover Exercise - This exercise determines that a
2-se!ctor data transfer starting at the last sector of a cylinder
results in a crossover to the first sector on the first track of the
successive cylinder.
The exercise first issues a 512-word write
command starting at sector 11 on track 1 of cylinder O:
the data
pattern written is all l's. The exercise then reads sector 0 on track
0 of cylinder 1 and verifies that the data pattern is all l's.
All
error conditions are reported.
(Related Error Numbers are:

5.3u2

18, 19, 20)

Data-Reliability Exercise

This exercise determines the reliability of the disk drive to write
and read data of various patterns at all valid disk addresses. The
data patterns used are:
1.

All O's

All l's

Checkerboard (alternate l's and O's)

5-3

RKOS CARTRIDGE DISK AND RKOSF FIXED DISK DIAGNOSTIC

Floating l's (sequenced bit-position advancement through each
word)

Random data

Count pattern (from "l," add 1 for each word written)
NOTE
In customer mode, only the floating-l's
pattern is implemented to reduce the run
time for the complete test sequence.

Each pattern is written at all disk addresses, and then read back
eight times for verification and to expose possible read-reduction
problems. Detection of any errors while reading causes the exercise
to report the failing address and then to attempt up to eight retries
to read the data. If a retry is successful, the exercise reports theerror recovered after "n" retries and advances to the next disk
address. If the read remains unsuccessful after eight retries, the
exercise terminates recovery and advances to the next disk address.
The absence of a "recovered" report signifies an
unsuccessful
recovery.
(Related Error Numbers are:

5.3.3

21, 22)

Random Exercise

Develop a valid, random cylinder-, track-, and sector-address
combination.

Initiate a write transfer of a random-length, random-data
pattern, beginning at the random disk address. The number of
words is 2 or more, and not greater than 512.

Upon completion of the
another random address.

Verify the data returned.

write

transfer,

issue

seek

23, 24, 25, 26)

5-4

-~-

RKOS CARTRIDGE DISK AND RKOSF FIXED DISK DIAGNOSTIC

Formatting Routine

5.3.4

The formatting routine prepares disks for use
sequence, the routine:

with

the

PDP-11.

•

Writes the complete header for each sector,

•

Verifies the address content of each sector header, and

•

Exits.

format

process

signaled

the

formatted

and/or

FORMATTING COMPLETE
The! message
FORMATTING FAILED
indicates that one or more
verified.

sectors

(Related Error Numbers are:

27, 28, 29)

5.4

could

not

ERROR MESSAGES

Fault conditions detected during the test sequence are reported at the
initiating terminal:
they are classified as equipment errors or
data-compare errors.
Equipment errors are those conditions that
result in the setting of the "error" bit, Bit 15 of the Control and
Status Register (RKCS). Data-compare errors occur when the diagnostic
finds data other than the data expected in data-transfer actions.
Some conditions may cause both an equipment error and a data-compare
error.
The following representations illustrate the context of the various
error messages.
Table 5-1 lists the error numbers and their related
fault conditions. Appendix B defines the register contents displayed
in the error messages.
Equipment error-message format:
RK05
ERROR NO.
RKDS
RKER
RKCS
RKWC
RKBA
RKDA

UNIT NO.

Drive Status Register contents
Error Register contents
Control and Status Register contents
Word Count Register contents
Bus Address Register contents
Desired Address Register contents

5-5

RKOS CARTRIDGE DISK AND RKOSF FIXED DISK DIAGNOSTIC
Data-compare error-message format:
RK05
ERROR NO.
EXPECTED
RECEIVED

UNIT NO.

n
Data expected
Data received

Sector error-message format:
UNIT NO. m
RK05
ERROR NO.
n
EXPECTED = Data expected
Data received
RECEIVED
Number (in octal and decimal)
CYLINDER
Number (in octal and decimal)
TRACK
Number (in octal and decimal)
SECTOR
WORD NO. IN SECTOR = Number (in octal and decimal)
Other error messages:
CONTENTS OF RKDA INCORRECT
HEADER VERIFY ERROR AT ADDRESS a
UNABLE TO FORMAT SECTOR AT ADDRESS b
REREAD SAME DATA n TIMES BEFORE ERROR
ERROR NO.

x RECOVERED AFTER y RETRIES
Table 5-1
Error Conditions

Error Number and
Associated Test
Exercise

Fault Condition

Heads Positioning:
1

Error bit was set after a read-header command
was issued to cylinder O.

Cylinder address acquired
command does not agree
address.

Error bit was set after a read-header command
was issued to a cylinder in the range 1
through 199.

Error bit was set after a read-header command
was issued to the cylinder address being
incremented from 0 through 199.

Error bit was set after a read-header command
was issued to the cylinder address being
decremented from 199 through O.

by a read-header
with the specified

(continued on next page)

5-6

·~.

RKOS CARTRIDGE DISK AND RKOSF FIXED DISK DIAGNOSTIC
Table 5-1 (Cont.)
Error Conditions

' Number and
Error
Associated Test
E:>i:ercise

Fault Condition

Sector Addressing:
6

Error bit was set while exercise was writing
a sector with a data pattern equal to its
sector number.

Error bit was set while exercise was reading
a sector with a data pattern equal to its
sector number.

Data-compare error. Data pattern read from a
sector on track 0 of cylinder 0 does not
contain the respective sector number.

Track Addressing:
9

Error bit was set while exercise was writinq
a data pattern equal to the respective trac~
number in sector 0 on a track of cylinder O.

Error bit was set while exercise was reading
sector 0 on a track of cylinder O. The data
pattern is the respective track number.

Data-compare error. Data pattern read from
sector 0 on tracks 0 and 1 of cylinder 0 does
not contain the respective track number.

Cylinder Addressing:
12

Error bit was set while exercise was writing
a
data pattern equal to the respective
cylinder number in sector 0 of a cylinder.

Error bit was set while exercise was reading
sector 0 of a cylinder. The data pattern
expected is the respective cylinder number.

Data-compare error. Data pattern read from
sector 0 of a cylinder does not contain the
respective cylinder number •

•
Track Crossover:
15

Error bit was set while exercise was writing
a 2-sector data transfer starting at sector
11 on track 0 of cylinder O.
The transfer
should cross over into sector 0 of track 1.
The data pattern is all l's.
(continued on next page)

5-7

RKOS CARTRIDGE DISK AND RKOSF FIXED DISK DIAGNOSTIC
Table 5-1 (Cont.)
Error Conditions
Error Number and
Associated Test
Exercise
Track Crossover:

Fault Condition
(Cont.)

Error bit was set while exercise was reading
the initial two words of sector 0 on track 1
of cylinder 0. The data pattern is all l's.

Data-compare error. Data pattern read from
sector 0 on track 1 of cylinder 0 does not
contain the expected data of all l's.

Cylinder Crossover:

Error bit was set while exercise was writing
a 2-sector data transfer starting at sector
11 on
track 1 of each cylinder.
Each
transfer should cross over into sector 0 on
track 0 of the successive cylinder. The data
pattern is all l's.

Error bit was set while exercise was reading
the initial two words of sector 0 on track 0
of a cylinder. The data pattern is all l's.

Data-compare error. Data pattern read from
sector 0 on track 0 of a cylinder does not
contain the expected data of all l's.

Data-reliability or Interactive-Data Test:
21

Error bit was set while exercise was
the disk with a test pattern.

writing

Error bit was set while exercise was
a test pattern from the disk.

reading

Condition may also occur as a data-compare
error.
Data read from the disk does not
contain the expected test pattern.
Random:
23

Error bit was set while exercise was writing
a random-data pattern at a randomly selected
disk address.

Error bit was set after the issuing of a seek
command with a random disk address.
(continued on next page)

5-8

RKOS CARTRIDGE DISK AND RKOSF FIXED DISK DIAGNOSTIC
Table 5-1 (Cont.)
Error Conditions
~·---~·----------------.------------------------------------------------------

Error Number and
Associated Test
Exercise
Random:

Fault Condition

(Cont.)

Error bit was set while exercise was reading
random data from a previously written random
disk address.

Data-compare error. Data pattern read
not contain the expected random data.

does

Formatting:
27

Error bit was set while routine was writing a
sector header to format one sector at a time.

2:8

Error bit was set while routine was reading a
sector header.

The header for the indicated sector does
contain the correct format.

not

Interactive-Address Test:

5.5

was

Error bit was set after a seek command
issued to the "first" cylinder selected.

Error bit was set after a seek command was
issued to the "second" cylinder selected.

SERVICE-MODE INITIATION

Initiation of this mode demands a knowledge of
console-switch
selection (see Section 5.6), test-parameter selection (see Section
5.7), interactive testing (see Sections 5.9 and 5.10), and the content
of Appendix A. Underlined text in this procedure indicates reauired
or expected user input.
Install "scratch" cartridge in disk drive to be tested.
On both RSX-llM and RSX-ilM-PLUS systems, allocate the device.
>ALLOCATE DKn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DKn:/FOR

5-9

RKOS CARTRIDGE DISK AND RKOSF FIXED DISK DIAGNOSTIC
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $RK05
START RK05 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? DKn
**WARNING'** DKn: RESIDENT DATA WILL BE DESTROYED **WARNING**
CONTINUE? SERVICE
(N or RETURN alone aborts the diagnostic)
TEST PARAMETERS (OCTAL)= nnnnnn
CONSOLE SWITCH FOR INTERVENTION (DECIMAL)= n
The selected test sequence commences upon RETURN after you have
responded to all inquiries, if any, that occur as a result of
test-parameters selection.

5.6

CONSOLE SWITCH FOR INTERVENTION

Service-mode initialization requires that you select a CPU console
switch (0-15) for intervention in the test sequence when, for example,
you desire to change test parameters. The facility to select more
than one switch is useful only if more than one device is to be tested
concurrently; that is, you can assign a uniaue switch to each
diagnostic.
For those systems without a CPU switch console or without the GET
SENSE SWITCHES directive, respond to the message "CONSOLE SWITCH •.• "
with 0.

5.7

TEST PARAMETER SELECTION

Customer mode allows only a fixed sequence of the diagnostic's tests.
Service mode, however, permits customization of the test content
through the test-parameters facility. Table 5-2 describes the various
options available to you as a service-mode user. You select options
by logically ORing their related octal codes to form a 6-digit number
(leading zeros need not be expressed) for entry in response to TEST
PARAMETERS (OCTAL)=.
NOTE
A response of 0 implies that no tests
are to be performed.
The diagnostic
issues the test summary report and then
terminates.
The table also indicates those options that are automatically selected
for customer-mode execution.
The "bit" references in the option
descriptions refer to the bit positions of a test-parameters status
word that is monitored by the diagnostic.

5-10

.~-,

RKOS CARTRIDGE DISK AND RK.OSF FIXED DISK DIAGNOSTIC
Table 5-2
Test-Parameter Options

Option Description

Selection
Code
(Octal)

In
Customer
Mode

STOP ON ERROR (Bit 15) :

100000

40000

20000

10000

4000

2001

Test sequence waits up to 30
minutes before terminating. User
may abort stop by setting console
switch selected for intervention.
LOOP ON ERROR (Bit 14) :
Test sequence
loops
on
the
failing
instruction
sequence.
User should intervene and select
new test parameters that exclude
this option.
INHIBIT ERROR MESSAGE PRINTOUT (Bit 13) :
Prevents
appearance
of
all
diagnostic error messages except
the test summary report
that
appears
at
the end of each
sequence pass.
BELL (Bit 12) :
The terminal bell rings for
e~r ror detected.

each

(continued on next page)

5-11

RKOS CARTRIDGE DISK AND RKOSF FIXED D:CSK DIAGNOSTIC
Table 5-2 (Cont.)
Test-Parameter Options

Option Description
INTERACTIVE-DATA TEST (Bits 10 & 1):

Selection
Code
(Octal)

In
Customer
Mode

2002

Yes

Allows the service-mode user to
specify explicit conditions for
data-reliability testing of the
drive
(see
Section 5.10 for
details).
LIMIT DATA-COMPARE ERROR MESSAGES (Bit 5):
Display an error message only for
the
first
data-compare error
condition
detected
during
a
specified
data transfer.
The
default is:
display an error
message
for
up
to
three
data-compare
error
conditions
detected
during retries of a
specified data transfer.
TEST SEQUENCE SELECTION (Bits 0-4):
A)

Select addressing exercises
(see Section 5.3.1).

Yes

Select
data-reliability
exercise (see Section
5.3.2).

Yes

Select random exercise
Section 5.3.3).

(see

Yes

Select random exercise with
inter-read seeks inhibited to
reduce run time (see Section
5.3.3).

Select
formatting
routine
without
other
exercises;
routine
always
runs
to
completion
and exits
(see
Section 5.3.4).

Selectable

5.8

""'

SERVICE-MODE INTERVENTION/RESTART/TERMINATION

You can intervene in (stop) the test-sequence pass at any time by
changing from its current setting (0 to 1 or 1 to 0) the previously
selected CPU console switch.
Such action causes the diagnostic to
suspend testing and await response to the following message seauence.

5-12

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .lmll'

RKOS CARTRIDGE DISK AND RKOSF FIXED DISK DIAGNOSTIC
TES~r

PARAMETERS (OCTAL)=

Type an octal value
(other than 0)
to
select new test parameters (or re-enter the
old parameters, which are not saved at
intervention), or
type 0 to terminate the diagnostic.

If new (or the old) parameters are entered, the following
displayed.
RES'.rART?

message

Type Y to abort the suspended test seauence
and
initiate the new seauence at the
beg inning,. or
type N to allow the suspended test seauence
to
run
to completion before the new
sequence commences.

MCR>filill,RT
and then reinitiate the diagnostic with new
parameters.
intervention and restart provisions are not accessible.

5.9

The

INTERACTIVE-ADDRESS TEST

This test oscillates the disk drive head
(that is, continuous
in-and-out motion)
between the two cylinders you specify. After
test-parameter selection, the test is initialized by your typing of
in response to the
valid cylinder numbers in the range 0 through 199.
inquiries.
FIRST CYLINDER =
SECOND CYLINDER =
Should you inadvertently type a number greater than 199., the
repeats.
Once initiated, the head oscillation
with the selected console switch
command.

continues
or abort

inauiry

until you
intervene
the diagnostic by MCR

The function of the test is to issue seek commands alternately to the
two specified cylinders. An equipment error message is displayed if
the seek function fails.
(Related Error Numbers are:

5 .10

30, 31)

INT.Ei:RACTIVE-DATA TEST

5-13

RKOS CARTRIDGE DISK AND RKOSF FIXED DISK DIAGNOSTIC
WORD COUNT=
Type a value to indicate the desired upper limit of the data
buffer to be used in write/read transfer functions (the value
cannot exceed 512. and must be 2 or more).
If you type a value greater
inquiry repeats.

than

512.

less

than

the

DO YOU WISH TO SPECIFY THE SECTOR ADDRESS?
Type Y if a specified sector address is to be tested.
Type N if all data surfaces of the disk are to be written on
and/or read from.
The inquiries, which follow, for cylinder,
track, and sector numbers are inhibited.
CYLINDER=
This inquiry appears
only
if
you
have
requested
the
sector-addressing feature.
Type the desired cylinder number in
the range 0 through 199 (decimal). If you type a number greater
than 199., the inquiry repeats.
TRACK=
This inquiry appears
only
if
you
have
requested
the
sector-addressing feature.
Type the desired track number, 0 or
1. If you type a number greater than 1, the inquiry repeats.
SECTOR=
This inquiry appears
only
if
you
have
reauested
the
sector-addressing feature. Type the desired sector number in the
range 0 through 11 (decimal). If you type a number greater than
11., the inquiry repeats.
PATTERN NO.=
Type the appropriate number, as indicated below, to select a
specific stored data pattern or the combination of all stored
patterns for use in exercising the disk drive.
Stored Patterns

No.

All O's
All l's
Checkerboard
Floating l's
Random l's and O's
Count pattern (full-word, binary, sequential)
Run above patterns in sequence

0
1
2
3
4
5
6

You can specify your own pattern to be used in place of the
stored patterns by typing a full-word (6-digit) octal value
in response to the above inquiry.

5-14

RK05 CARTRIDGE DISK AND RKOSF FIXED DISK DIAGNOSTIC
WRITE?
Type Y to permit performance of write functions
test.

during

the

during

the

Type N to inhibit write functions.
READ?
Type y to permit performance of read
test.

functions

Type N to inhibit read functions.
NOTE
An N response to both inquiries
invalid.
The
inquiries
will
repeated.

is
be

21, 22)

5-15

CHAPTER 6

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS

. -...... CUSTOMER-MODE INITIATION ................-.
(Underlined text indicates required or
Chapter 2 for additional information.)
~

expected

user

input1

see

Install "scratch" disk cartridge in disk drive to be tested.
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DMn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT

DMn:/FO~

On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $RKO.§

(or RUN $RK07)

START RK06 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? DMn
**WARNING** DMn:
CONTINUE? Y
FORMAT DISK-ONLY?

RESIDENT DATA WILL BE DESTROYED **WARNING**
(N or RETURN alone aborts the diagnostic)
(N initiates customer-mode sequence)
(Y formats disk and exits)

Diagnostic runs to completion in 24 minutes
(RK06)
or 48 minutes
(RK07) for a lightly loaded system.
Formatting requires approximately
6 minutes (RK06) or 12 minutes (RK07). To exit sooner, type:
(CTRL/C)

MCR>8,!illfil

6•1

'TEST SUMMARY REPORT

Upon completion of each diagnostic test sequence, the following report
is displayed.
RK06 UNIT NO.
n
(n=unit number)
PASS COUNT=
TOTAL ERRORS ENCOUNTERED=
TOTAL FUNCTIONS ISSUED=
TOTAL WORDS TRANSFERRED=
END OF RK06 DIAGNOSTIC - TIME OF DAY=hour:minute:second
"Pass count" and "totals" are
(initiated in service mode only).

cumulative

6-1

for

multipass

testing

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
6.2

DISK-DRIVE CHARACTERISTICS

The following is general information for the RK06 and
Disk Drives.
RK06

filS.Ql

411

815

Tracks/Cylinder

Sectors/Track

Words/Sector

256

Cylinders

RK07

Cartridge

The highest track (track 2 of cylinder 410 (RK06) or cylinder 814
(RK07)) is reserved for use as a "marked bad sector" file. It is
software-protected against accidental overwriting. Sectors O through
9 record the addresses of those sectors, if any, that were detected as
being unreliable by Digital Manufacturing. Manufacturing-detected bad
sectors are flagged in their headers, both initially and by any
subsequent reformatting, as being "bad".
All
other
sectors,
regardless of their current status, are flagged as being "good" when
the cartridge is reformatted.
NOTE
This action does not preclude use of the
BAD utility program to register on the
cartridge those sectors it finds to be
"bad" for reference by the INITVOLUME
command.
(Refer to the RSX-11 Utilities
Manual
and
the
RSX-llM/M-PLUS MCR
Operations Manual, respectively).

6.3

DIAGNOSTIC DESCRIPTION

The diagnostic tests the ability of the selected disk drive to address
correctly
all
cylinders, tracks, and sectors 0£ the resident
cartridge, and to write data on, and to read data from, the cartridge
under selected conditions.
A formatting routine is included. ECC
correction and "bad sector (block)" processing are implemented.

During exercise execution, the address of a sector flagged as "bad"
is, first, saved in a "marked-bad-sector" table for later validation,
and then skipped for that phase of the exercise.
Subsequent phases,
such as write-check or read may address the same "bad" sector: thus
the table may contain several entries of the "bad" sector address.
Any condition that occurs as a result of a "bad" sector is not
reported as an error. At the end of testing in each occurrence of the
Addressing Exercises, the Data-Reliability Exercise, and the Random
Exercise, the marked-bad-sector handler compares the table~resident
sector addresses with the contents of the "manufacturing marked bad
sector" file on the cartridge and reports any addresses not matched by
the file.
The exercises described hereafter are executed in
a
one-pass
uninterrupted sequence for customer mode. The "Related Error Numbers"
following each description appear in error messages for detected fault
conditions:
refer
to
Section
6.4 and Table 6-1 for their
significance.

6-2

....,........................................................................................

~1-·

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
6.3.1

Addressing Exercises

6.3.1.1 Heads-Positioning Exercise - This exercise determines that
the heads position correctly at all cylinders.
The exercise is
conducted in two parts:
incremental seek and cross seek.
For incremental seek, a read-header command (implied seek) alternately
addresses cylinder 0 or cylinder "n," where "n" increments by one for
each seek to it for the range of one through 410
(RK06)
and one
through 814
(RK07).
After each seek of cylinder 0 or cylinder "n,"
the exercise compares the contents of the Desired Cylinder register
(RKDC)
with the cylinder address sought to verify that the specified
cylinder address was achieved.
For cross seek~ a read-header command alternately addresses cylinder
"a," where "a" is initially O, and cylinder "b," where "b" is
initially 410
(RK06)
and 814
(RK07) .'
After each seek,
"a" is
incremented by one and "b" is decremented by one. This part of the
exercise continues until "b" equals O.
Cylinder positioning is
verified by comparison of the RKDC register contents with the cylinder
address sought.
(Related Error Numbers are:

2, 3, 4, 5, 6, 7)

6.3.1.2 Sector-Addressing Exercise - This exercise determines that
sectors 0 through 21 of the resident disk cartridge are addressable.
Each "good" sector on track 0 of cylinder 0 is completely written with
a repeating 2-word data pattern equal to its respective sector number
followed by its complement. Then each sector is read and verified
that it contains the correct data pattern. All error conditions are
reported.
(Related Error Numbers are:

8, 9, 10, 11)

6.3.1.3 Track-Addressing Exercise - This exercise determines that all
tracks are addressable.
The exercise first issues a sector-write
command (256 words) to sector 0 of each track
(0-2)
on cylinder O:
the repeating 2-word data pattern written is the respective track
number followed by its complement. The exercise then reads sector 0
on tracks 0 through 2 of cylinder 0 and verifies that the data pattern
equals the respective track number.
After each read verification,
each sector is rewritten with the track-number pattern to detect if
more than one head is bieng energized at a time. All error conditions
ar,e reported.
(Related Error Numbers are:

12, 13, 14, 15, 16)

6.3.1.4 Cylinder-Addressing and Crossover Exercise - This exercise
determines that all cylinders are addressable, and that a 2-sector
data transfer starting at the last sector of a cylinder results in a
crossover to the first sector on the first track of the successive
cylinder. The e>cercise first issues a 512-word write command starting
at sector 21 on track 2 of cylinder 0 through 409 (RK06) and 0 through
813
(RK07):
the repeating 2-word data pattern written is the
respective cylinder number followed by its complement. The exercise
then reads sector 0 on track 0 of cylinder 1 and each successive

6-3

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
cylinder through cylinder 410
(RK06)
and cylinder 814 (RK07).
If
crossover occurred, the data pattern read should be the number of the
preceding cylinder
(e.g., 0 in sector O, track O, cylinder 1:
and 3
in sector O, track 0, cylinder 4).
All error conditions are reported.
(Related Error Numbers are:

17, 18, 19, 20)

6.3.1.5 Partial-Sector-Write Exercise - This exercise determines that
a write on a sector of less than 256 words results in the remainder of
the sector being zero-filled.
First, the exercise writes sector 0 (on
track 0 of cylinder 0) or the first "good" sector found on cylinder 0
with an all-l's pattern. Then, the exercise issues a 2-word write
command,
all -l's data,
to the same sector address.
Finally, the
exercise reads the sector's contents and verifies that all but the
initial two words are zero-filled.
All error conditions are reported.
(Related Error Numbers are:

6.3.2

21, 22, 23, 24, 25)

Data-Reliability Exercise

This exercise determines the reliability of the disk drive to write
and read data of various patterns at all "good" sector addresses other
than track 2 on cylinder 410 (RK06) and cylinder 814 (RK07).
The data
patterns used are:

All 0 Is

All 1 1 s

Checkerboard (alternate l's and O's)

Floating l's (sequenced bit-position advancement through each
word)

Random data

Count pattern (from "l," add 1 for each word written)
NOTE
In customer mode, only the floating-l's
pattern is implemented to reduce the run
time for the complete test sequence.

After each read, ECC correction is implemented, if called for
by the
disk controller,
to compensate for recoverable data-transfer errors.
If ECC correction is not successful, the exercise reports the failing
address and attempts up to eight retries to read the data.
If a retry
is successful, the exercise reports the error recovered after
"n"
retries and advances to the next disk address.
If the read remains
unsuccessful after eight retries, the exercise terminates recovery and
advances to the next disk address.
The absence of a "recovered"
report signifies an unsuccessful recovery.
(Related Error Numbers are:

26, 27, 28, 29)

6-4

RR06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
6.3.3

Random Exercise

This exercise determines that the drive can address randomly selected
disk addresses
(other than track 2 on cylinder 410 (RK06) and on
cylinder 814
(RK07))
and
execute
random-length
transfers
of
random-patterned data to and from those areas. The exercise sequence,
which is repeated 512 times, is:
1.

Develop a valid, random cylinder-, track-, and sector-address
combination.

Initiate a write transfer of a random-length,
random-data
pattern, beginning at the random disk address. The number of
words is two or more, and not greater than 512.

Upon completion of the
another random address.

Verify the data returned.

write

transfer,

issue

seek

Detection of any error while reading causes the exercise to report the
failing address and then to attempt up to eight retries to read the
data.
If a retry is successful,
the exercise reports the error
recovered after "n" retries and advances to the next disk address.
If
the read remains unsuccessful after eight retries,
the exercise
terminates recovery and advances to the next disk address. The
absence of a "recovered" report signifies an unsuccessful recovery.
(Related Error Numbers are:

6.3.4

30, 31, 32, 33)

Formatting Routine

The formatting routine prepares non-PDP-11 formatted RK06 and RK07
cartridges for use with the PDP-11 or cartridges that require
reformatting.
In sequence, the routine:
•

Writes the complete header for each sector, including a "good"
or a "bad" sector flag, where appropriate, as determined by
the contents of the manufacturing bad sector portion of the
marked-bad-sector file, and

•

Exits.

Formatting, when selected, always runs to completion and exits.
The sector headers are written one track at a time.
Sectors that
cannot be formatted a~e identified by the cylinder-track addresses
that follows the message
UNABLE TO FORMAT ONE OR MORE SECTORS AT ADDRESS
Satisfactory completion of the
message

format

FORMATTING COMPLETE

6-5

process

signaled

the

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
The message
FORMATTING FAILED
indicates that one or more sectors could not be formatted.
(Related Error Numbers are:

6.4

34, 35, 36)

ERROR MESSAGES

Fault conditions detected during the test sequence are reported at the
initiating terminal;
they are classified as equipment errors or
data-compare errors.
Equipment errors are those conditions that
result in the setting of the "error" bit, Bit 15 of the Control and
Status 1 Register
(RKCSl).
Data-compare errors occur when the
diagnostic finds data other than the data expected in data-transfer
actions. Some conditions may cause both an equipment error and a
data-compare error.
The following representations illustrate the context of the various
error messages.
Table 6-1 lists the error numbers and their related
fault conditions. Appendix B defines the register contents displayed
in the error messages.
Equipment error-message format:
RK06
UNIT NO. m
ERROR NO. n
RKCSl
RKWC
RKBA
RKDA
RKCS2
RKDS
RKER
RKAS/OF
RKDC
RKDB
RKMRl
RKECPS
RKECPT
RKMR2-0
RKMR3-0
RKMR2-l
RKMR3-l
RKMR2·-2
RKMR3-2
RKMR2-3
RKMR3-3

Control and Status 1 Register contents
Word Count Register contents
Bus Address Register contents
Disk Address Register contents
Control and Status 2 Register contents
Drive Status Register contents
Error Register contents
Attention Summary and Offset Register contents
Desired Cylinder Register contents
Data Buffer Register contents
Maintenance Register 1 contents
ECC Position Register contents
ECC Pattern Register contents
Maintenance Register 2 - Message 0
Maintenance Register 3 - Message 0
Maintenance Register 2 - Message 1
Maintenance Register 3 - Message 1
Maintenance Register 2 - Message 2
Maintenance Register 3 - Message 2
Maintenance Register 2 - Message 3
Maintenance Register 3 - Message 3

=
=

=
=
=

Data-compare error-message format:
RK06
ERROR NO.
EXPECTED

UNIT NO.

n
Data received

6-6

1¥

,...

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
Other error messages:
UNABLE TO FORMAT ONE OR MORE SECTORS AT ADDRESS n
CONTENTS OF RKDC REGISTER INCORRECT
FORMATTING FAILED
FORMATTING COMPLETE
FOUND 128.

BAD CYLINDERS WHICH EXCEEDS MEMORY SPACE

EVERY SECTOR ON CYLINDER 0 IS MARKED AS BAD
UNABLE TO LOCATE THE BAD SECTOR BLOCK
TRACK

THE

BAD

SECTOR

FILE

FOUND BAD SECTOR NOT IN BAD SECTOR BLOCK FILE AT ADDRESS n
REREAD SAME DATA n TIMES BEFORE ERROR
ERROR NO.

x RECOVERED AFTER y RETRIES
Table 6-1
Error Conditions

Error Number and
Associated Test
Exercise

Fault Condition

Initialization:
1

Error bit was set
during
(re-calibration) function.

home-seek

Heads Positioning:
2

Error bit was set after a read-header command
was issued to cylinder 0.

Error bit was set after a read-header command
was issued to a cylinder in the range 1
through 410 (RK06) and 1 through 814 (RK07).

Error bit was set after a read-header command
was issued to the cylinder number being
incremented from 0 through 410 (RK06)
and 0
through 814 (RK07).

Data-compare error.
The cylinder
number
obtained via the read-header command does not
agree with the cylinder number sought (number
incrementing from 0 through 410 (RK06) and 0
through 814 (RK07).
(continued on next page)

6-7

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
Table 6-1 (Cont.)
Error Conditions
Error Number and
Associated Test
Exercise
Heads Positioning:

Fault Condition
(Cont.)

Error bit was set after a read-header command
was issued to the cylinder number being
decremented from 410 (RK06)
and 814
(RK07)
through o.

Data-compare error.
The cylinder
number
obtained via the read-header command does not
agree with the cylinder number sought (number
decrementing from 410 (RK06) and 814 (RK07)
through 0).

Sector Addressing:
8

Error bit was set while exercise was writing
a sector with a 2-word data pattern eaual to
its respective sector number followed by its
complement.

Error bit was set
while
exercise
was
write-checking a sector written with a 2-word
data pattern equal to its respective sector
number followed by its complement.

Error bit was set while exercise was reading
a sector with a 2-word data pattern equal to
its respective sector number followed by its
complement.

Data-compare error. Data pattern read from a
sector on track 0 of cylinder 0 does not
contain the respective sector numbe~ followed
by its complement.

Track Addressing:

Error bit was set while exercise was writing
sector 0 on each track of cylinder 0 with a
repeating 2-word data pattern equal to the
respective
track number followed by its
complement.

Error bit was set
while
exercise
was
write-checking
a
sector written with a
repeating 2-word data pattern equal to the
respective
track number followed by its
complement.
(continued on next page)

6-8

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
Table 6-1 (Cont.)
Error Conditions
Error Number and
Associated Test
Exercise

Track Addressing:

Fault Condition'

(Cont.)

Error bit was set while exercise was reading
sector 0 on tracks 0 through 2 of cylinder O.
The repeating 2-word data pattern is the
respective
track number followed by its
complement.

Data-compare error. Data pattern read from a
sector 0 on tracks O through 2 of cylinder O
does not contain the number of the respective
track followed by its complement.

Error bit was set
while
exercise
was
rewriting a sector with a repeating 2-word
data pattern equal to the respective track
number followed by its complement. Detects
erroneous turn-on of more than one head at a
time.

Cylinder-Addressing and Crossover:
17

Error bit was set while exercise was wtitinq
a 512-word data transfer starting at the last
sector on the last track of a cylinder.
The
repeating
2-word
data
pattern
is the
respective cylinder number followed by its
complement.

Error bit was set
while
exercise
was
write-checking
a
512-word data transfer
written starting at the last sector on the
last track of a cylinder.
The repeating
2-word data pattern
is
the
respective
cylinder number followed by its complement.

Error bit was set while exercise was reading
the first sector on the first track of a
cylinder. The repeating 2-word data pattern
is the preceding cylinder number followed by
its complement.

Data-compare error. Data pattern read from
the first sector on the first track of a
cylinder does not contain the number of the
preceding
cylinder
followed
by
its
complement.
(continued on next page)

6-9

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
Table 6-1 (Cont.)
Error Conditions
Error Number and
Associated Test
Exercise

Fault Condition

Partial Write:
21

Error bit was set while exercise was writing
sector 0 on track 0 of cylinder O, or the
first "good" sector found on cylinder 0, with
all-l's data.

All sectors of cylinder 0 are marked as being
"bad" sectors.

Error bit was set while exercise was writing
a 2-word transfer of all-l's data in sector 0
on track 0 of cylinder 0, or in the first
"good" sector found on cylinder O.

Error bit was set while exercise was reading
the contents of the first "good" sector
found.

Data-compare error.
the
first "good"
contain all l's.

Data pattern read from
sector found does not

Data-Reliability or Interactive-Data Test:
26

Error bit was set while exercise was
a test pattern.

Error bit was
write-checking
pattern.

Error bit was set while exercise was
a test pattern.

Data-compare error.
Data read does
contain the expected test pattern.

writing

set
while
exercise
a previously written

was
test

reading
not

Random:
30

Error bit was set while exercise was writing
a random-data pattern at a randomly selected
address.

Error bit was set after the issuing of a seek
command with a random address.

Error bit was set while exercise was reading
random data from a previously written random
address.
(continued on next page)

6-10

WAI

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
Table 6-1 (Cont.)
Error Conditions

"-''

Eirror Number and
Associated Test
E:~ercise

Random:

Fault Condition
(Cont.)

Data-compare error.
Data read from
random
address
does
not
contain
previously written random data.

the
the

Formatting:
34

Error bit was set after routine issued a
command
to
read the "manufacturing bad
sector" portion of the "marked bad sector"
file.

The "manufacturing
cannot be located.

Error bit was set while routine was writing
sector-header patterns to format a track.

bad sector" information
Formatting is aborted.

Marked Bad Sector Handling:
37

The core-resident "marked bad sector" table
is full
(i.e., detected bad sectors exceed
128). Subsequent bad-sector addresses cannot
be retained for validation.

Error bit was set after routine issued a
command
to
read the "manufacturing bad
sector" portion of the "marked bad sector"
file.•

The "manufacturing bad
cannot
be
located.
aborted.

sector" information
The diagnostic is

Interactive-Address Test:

6. 5,

Error bit was set after a seek command
issued to the "first" cylinder selected.

Error bit was set after a seek command was
issued to the "second" cylinder selected.

was

SERVICE-MODE INITIATION

Initiation of this mode demands a knowledge of
console-switch
selection
(see Section 6.6),
test-parameter selection (see Section
6.7), interactive testing (see Sections 6.9 and 6.10), and the content
of Appendix A. Underlined text in this procedure indicates required
or expected user input.

6-11

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
Install "scratch" cartridge in disk drive to be tested.
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DMn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DMn:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
(or RUN $RK07)

>RUN $RK06

START RK06 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? DMn
**WARNING** DMn:
RESIDENT DATA WILL BE DESTROYED **WARNING**
CONTINUE? SERVICE
(N or RETURN alone aborts the diagnostic)
TEST PARAMETERS (OCTAL)= nnnnnn
CONSOLE SWITCH FOR INTERVENTION (DECIMAL)= n
The selected test s~que~c~ commences upon RETURN after you have
responded to all 1nqu1r1es,
if any,
that occur as a result of
test-parameters selection.

6.6

CONSOLE SWITCH FOR INTERVENTION

Service-mode initialization requires that you select a CPU console
switch (0-15) for intervention in the test sequence when, for example,
you desire to change test parameters. The facility to select more
than one switch is useful only if more than one device is to be tested
concurrently;
that is, you can assign a uni9ue switch to each
diagnostic.
For those systems without a CPU switch console or without the GET
SENSE SWITCHES directive, respond to the message "CONSOLE SWITCH ••• "
with 0.

6.7

TEST PARAMETER SELECTION

Customer mode allows only a fixed sequence of the diagnostic's
Service mode,
however,
permits customization of the test
through the test-parameters facility.
Table 6-2 describes the
options available to you as a service-mode user.
You select
by logically ORing their related octal codes to form a 6-digit
(leading zeros need not be expressed) for entry in response
PARAMETERS (OCTAL)=.

tests.
content
various
options
number
to TEST

NOTE
A response of 0 implies

that no tests
are to be performed.
The diagnostic
issQes the test summary report and then
terminates.

The table also indicates those options that are automatically selecte<l
for customer-mode execution.
The "bit"
references in the option

6-12

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
descriptions refer to the bit positions of
word that is monitored by the diagnostic.

test-parameters

status

Table 6-2
Test-Parameter Options

Option Description

Selection
Code
(Octal)

In
Customer
Mode

STOP ON ERROR (Bit 15) :

100000

40000

20000

10000

4000

2001

Test sequence waits up to 30
minutes before terminating.
User
may abort stop by setting console
switch selected for intervention.
LOOP ON ERROR (Bit 14):
Test sequence
loops
on
the
failing
instruction
sequence.
User should intervene and select
new test parameters that exclude
this option.
INHIBIT ERROR MESSAGE PRINTOUT (Bit 13):
Prevents
appearance
of
all
diagnostic error messages except
the test summary report
that
appears
at
the end of each
sequence pass.
BIE:LL (Bit 12):
The terminal bell rings for
error detected.

each

(continued on next paqe)

6-13

RK06 AND RR07 CARTRIDGE DISK DIAGNOSTICS

Table 6-2 (Cont.)
Test-Parameter Options
Selection
Code
(Octal)

Option Description
INTERACTIVE-DATA TEST (Bits 10 & 1):

In
Customer
Mode
No

2002

Allows the service-mode user to
specify exp1icit conditions for
data relia~ility testing of the
drive
(see
Section 6.10 for
details).
LIMIT DATA-COMPARE ERROR MESSAGES (Bit 5):

Yes

Select addressing
Section 6.3.1).

exercises

Yes

Select
data-reliability
exercise (see Section 6.3.2).

Yes

Select random exercise
Section 6.3.3).

(see

Yes

Select random exercise with
inter-read seeks inhibited to
reduce run time (see Section
6.3.3).

Select
formatter
routine
without
other
exercises;
formatter
always
runs to
completion
and exits
(see
Section 6.3.4).

Selectable

6. 8

....

SERVICE-MODE INTERVENTION/RESTART/TERMINA'l'ION

You can intervene in (stop) the test sequence pass at any time by
changing from its current setting (0 to 1 or 1 to 0) the previously
selected CPU console switch.
Such action causes the diagnostic to
suspend testing and await response to the following message seauence.

6-14

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS

TEST PARAMETERS (OCTAL)=

Type an octal value
(other than 0)
to
select new test parameters (or re-enter the
old parameters, which are not saved at
intervention), or
type 0 to terminate the diagnostic.

If new (or the old) parameters are entered, the following
di.splayed.
RE: START?

message

Type Y to abort the suspended test seauence
and
initiate the new sequence at the
beginning, or
type N to allow the suspended test seauence
to
run
to completion before the new
sequence commences.

For those systems not equipped with a CPU switch console or not
implemented with the GET SENSE SWITCHES directive, the user wishinq to
alter test parameters must first terminate the diagnostic by typinq:
(cTRL/C)

MCR>ABORT
and then reinitiate the diagnostic with new
parameters.
intervention and restart provisions are not accessible.

6 ,. 9

The

INTERACTIVE-ADDRESS TEST

This test oscillates the disk drive head
(that is,
continuous
in-and-out motion)
between the two cylinders you specify.
After
test-parameter selection, the test is initialized by your
typing of
valid cylinder numbers in the range 0 through 410.
(RK06) and 0
through 814.
(RK07) in response to the inquiries.
FIRST CYLINDER =
SECOND CYLINDER =
Should you inadvertently type a number greater than 410.
814.
(RK07), the inquiry repeats.
Once initiated, the head oscillation
with the selected console switch
command.

continues
or abort

(RK06)

and

until you
intervene
the diagnostic by MCR

The function of the test is to issue seek commands alternately to the
two specified cylinders.
An equipment error message is displayed if
the seek function fails.
(Related Error Numbers are:

6.10

40, 41)

INTERACTIVE-DATA TEST

6-15

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
NOTE
Track 2 of cylinder 410 (RK06) and 814
(RK07), the "marked-bad-sector" file,
cannot be addressed. Violation of this
restriction results in rejection of your
responses and
the
repeat
of
all
inquiries from "WORD COUNT=."
WORD COUNT=
Type a decimal value to indicate the desired upper limit of the
data buffer to be used in write/read data transfer functions (the
value cannot exceed 512. and must be 2 or more).
If you type a value less than 2 or more than
repeats.

512.,

the

inauirv

DO YOU WISH TO SPECIFY THE SECTOR ADDRESS?
Type Y if a specified sector address is to be tested.
Type N if all data surfaces of the cartridge other than track 2
of cylinder 410 (RK06) and 814 (RK07) are to be written on and/or
read from. The inquiries, which follow, for cylinder, track, and
sector numbers are inhibited.
CYLINDER=
This inquiry appears
only
if
you
have
reauested
the
sector-addressing feature.
Type the desired cylinder number in
the range 0 through 410 (decimal) for the RK06 and 814 (decimal)
for the RK07. If you type a number greater than 410.
(RK06) ·and
814. RK07), the inquiry repeats.
TRACK=
This inquiry appears
only
if
you
have
requested
the
sector-addressing feature. Type the desired track number in the
range 0 through 2. If you type a number greater than 2, the
inquiry repeats.
SECTOR=
This inquiry appears
only
if
you
have
reauested
the
sector-addressing feature. Type the desired sector number in the
range 0 through 21 (decimal). If you type a number greater than
21., the inquiry repeats.
PATTERN NO.=
Type the appropriate number, as indicated below, to select a
specific stored data pattern or the combination of all stored
patterns for use in exercising the disk drive.
Stored Patterns
All O's
All l's
Checkerboard
Floating l's
Random l's and O's
Count pattern (full-word, binary, sequential)
Run above patterns in sequence

0
1
2

3
4

5
6

6-16

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .lillm. . . . . . . . . . . . . . . . . . . . . . . . . . . .""".....
I .

RK06 AND RK07 CARTRIDGE DISK DIAGNOSTICS
You can specify your own pattern to be used in place of the
stored patterns by typing a full-word (6-digit) octal value in
response to the above inquiry.
WRITE?
Type Y to permit performance of write functions during the test.
Type N to inhibit write functions.
RE:AD?
Type Y to permit performance of read functions during the test.
Type N to inhibit read functions.
NOTE
An N response to both inauiries
invalid.
The
inquiries
will
repeated.

is
be

26, 27, 28, 29)

6-17

CHAPTER 7
RP02, RPR02, OR RP03 DIAGNOSTIC

. .- - CUSTOMER-MODE INITIATION - - - - - - .
(Underlined text indicates reauired or
Chapter 2 for additional infor~ation.)

expected

user

input:

see

Install "scratch" disk pack on disk drive to be tested.
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCA'rE DPn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DPn: /FOR:
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
(or RP02 or RPR02

>RUN $RPOJ

START RP03 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? DPn
**WARNING** DPn:
CONTINUE? Y
FORMAT DISK-ONLY?

RESIDENT DATA WILL BE DESTROYED **WARNING**
(N or RETURN alone aborts the diaanostic)
(N initiates customer-mode seauence)
(Y formats disk pack and exits)

Diagnostic runs to completion in 2 hours for RP03, and 1 hour and 5
minutes for RP02 or RPR02 on a lightly loaded system.
Formatting
requires approximately 30 minutes for RP03, and 18 minutes for RP02 or
RPR02.
RP02 or RPR02 packs must be formatted one at a time.
To exit
sooner, type:
(CTRL/C)

MCR>ABORT

7.1

TEST SUMMARY REPORT

Upon completion of
is displayed.

E~ach

diagnostic-test sequence, the following report

RP03 UNIT NO.
n
(n=unit number)
PASS COUNT=
TOTAL ERRORS ENCOUNTERED=
TOTAL FUNCTIONS ISSUED=
TOTAL WORDS TRANSFERRED=
END OF RP03 DIAGNOSTIC - TIME OF DAY=hour:minute:second

7-1

RP02, RPR02, OR RP03 DIAGNOSTIC

"Pass count" and "totals" are
(initiated in service mode only).

cumulative

for

multipass

testing
~I

7.2

DISK DRIVE CHARACTERISTICS

The following are data-capacity parameters for the
RP03 Disk Pack Drives.
RP02 & RPR02

RP03

Cylinders

200+3

400+6

Tracks/Cylinder

Sectors/Track

Words/Sector

256

The "spare" cylinders (201-203 for RP02 and
RP03) cannot be addressed.

7.3

RPR02,

RP02,

RPR02,

and

401-406

for

DIAGNOSTIC DESCRIPTION

The diagnostic tests the ability of the selected disk drive to address
correctly all cylinders, tracks, and sectors of the resident disk
pack, and to write data on, and to read data from, the pack under
selected conditions.
A pack formatting routine is also included.
Neither ECC correction nor "bad sector
(block)" processing are
implemented.
The exercises described hereafter are executed in
a
one-pass
uninterrupted sequence for customer mode. The "Related Error Numbers"
following each description appear in error messages for detected fault
conditions;
refer
to
Section
7.4 and Table 7-1 for their
significance.

7.3.1

Addressing Exercises

7.3.1.l Heads-Positioning Exercise - This exercise determines that
the heads position correctly at all cylinders of the resident disk
pack. The exercise is conducted in two parts: incremental seek and
cross seek.
For incremental seek, a read-header command (implied seek) alternately
addresses- cylinder 0 and cylinder "n," where "n" increments by one for
each seek to it for the range of 1 through the valid, upper-limit
cylinder address. After each seek of cylinder 0 or cylinder "n," the
exercise compares the contents of the SUCA register
(selected unit
cylinder address) with the current header data to verify that the
specified cylinder address was achieved.
For cross seek, a read-header command alternately addresses cylinder
"a," where "a" is initially 0, and cylinder "b," where "b" is
initially the valid, upper-limit cylinder address. After each seek,
"a" is incremented by one and "b" initially the valid, upper-limit
cylinder address. After each seek, is decremented by one. This part

7-2

RP02, RPR02, OR RP03 DIAGNOSTIC

of the exercise continues until "b" equals O.
verified after each seek.
(Related Error Numbers are:

Cylinder positioning is

2, 3, 4, 5)

7.3.1.2 Sector-Addressing Exercise - This exercise determines that
sectors 0 through 9 of the resident disk pack are addressable. Each
sector on track 0 of cylinder 0 is written with a data pattern eaual
to its respective sector number.
Then each sector is read and
verified that it contains the correct data pattern.
All error
conditions are reported.
(Related Error Numbers are:

6, 7, 8)

7. 3 .1. 3 Track-·Addressing and Crossover
Exercise - This
exercise
determines that all tracks are addressable, and that a 2-sector data
transfer starting at the last sector of any track except the last
track of the last cylinder results in a crossover to the first sector
of the! successive track. The exercise, first, issues a 512-word write
command starting at sector 9 of track 0 and each successive track
through track 19 on cylinder 0.
The data pattern written is the
respective track number. The exercise then reads the first two words
from sector 0 of track 1 and each successive track through track 19 on
cylinder O, and sector 0 of track 0 on cylinder 1. If crossover
occurred, the data pattern read should be the number of the preceding
track (e.g., 0 in sector 0, track 1, cylinder O; 3 in sector O, track
4, cylinder 0; and 19 in sector 0, track O, cylinder 1).
All error
conditions are reported.
(Related Error Numbers are:

9, 10, 11)

7.3.1 .. 4 Cylinder-Addressing and Crossover Exercise - This exercise
determines that all cylinders are addressable, and that a 2-sector
data transfer starting at the last sector of any cylinder except the
last results in a crossover to the first sector of the successive
cylinder. The exercise, first,
issues a 512-word write command
starting at sector 9 of track 19 on cylinder 0 and each successive
cylinder through the cylinder that precedes the valid upper limit.
The data pattern written is the respective cylinder number. The
exercise then reads the first two words from sector O, track 0, on
cylinder 1 and each successive cylinder to the valid upper limit. If
crossover occurred, the data pattern read should be the number of the
preceding cylinder (e.g., 0 in sector 0, track 0, cylinder l; and 3
in sector O, track 0, cylinder 4). All error conditions are reported.
(Related Error Numbers are:

12, 13, 14)

7.3.1.5 Partial-Write Exercise - This exercise determines that a
write on a sector of less than 256 words results in the remainder of
the sector being zero-filled. First, the exercise writes sector 0 on
track 0 of cylinder 0 with an all-l's pattern. Then, the exercise
issues a 2-word write command, all-l's data, to the same sector
address.
Finally, the exercise reads the sector's contents and
verifies that all but the initial two words are zero-filled.
All
error conditions are reported.
(Related Error Numbers are:

15, 16, 17, 18)
7-3

RP02, RPR02, OR RP03 DIAGNOSTIC
7.3.2

Data-Reliability Exercise

This exercise determines the reliability of the disk drive to write
and read data of various patterns at all valid disk addresses. The
data patterns used are:
1.

All O's

Al 1 l's

Checkerboard (alternate l's and O's)

Floating l's (sequenced bit-position advancement through each
word)

Random data

Count pattern (from "l," add 1 for each word written)
NOTE
In customer mode, only the floating-l's
pattern is implemented to reduce the run
time for the complete test sequence.

Each pattern is written at all disk addresses, and then read back
eight times for verification and to expose possible read-reduction
problems. Detection of any error while reading causes the exercise to
report the failing address and then to attempt up to eight retries to
read the data. If a retry is successful, the exercise reports the
error recovered after "n" retries and advances to the next disk
address. If the read remains unsuccessful after eight retries, the
exercise terminates recovery and advances to the next disk address.
The absence of a "recovered" report signifies an
unsuccessful
recovery.
(Related Error Numbers are:

7.3.3

19, 20)

Random Exercise

This exercise determines that the drive can address randomly selected
disk-pack
addresses
and
execute
random-length
transfers
of
random-patterned data to and from those pack areas.
The exercise
sequence, which is repeated 512 times, is:
1.

Develop a valid, random cylinder-, track-, and sector-address
combination.

Initiate a write transfer of a random-length, random-data
pattern, beginning at the random disk address. The number of
words is two or more, and not greater than 512.

Upon completion of the
another random address.

Verify the data returned.

write

7-4

transfer,

issue

seek

RP02j RPR02, OR RP03 DIAGNOSTIC

'-r··

Detection of any error while reading causes the exercise to report the
failing address and then to attempt up to eight retries to read the
data. If a retry is successful, the exercise repo~ts the error
recovered after "n" retries and advances to the next disk address. If
the read remains unsuccessful after eight retries, the exercise
terminates recovery and advances to the next disk address. The
absence of a "recovered" report signifies an unsuccessful recovery.
(Related Error Numbers are:

7.3.4

21, 22, 23, 24)

Formatting Routine

The formatting routine prepares disk packs for use
In sequence, the routine:

with

the

Writes the complete header for each sector,

Verifies the address content of each sector header, and

Exits.

PDP-11.

Formatting, when selected, always runs to completion and exits.
The sector headers are normally written ten at a time. If the routine
detects an error, it shifts to error recovery and attempts to write
complete sector headers one at a time.
Sectors that cannot be
formatted or verified are identified by the cylinder-track-sector
addresses that follow the messages
UNABLE TO FORMAT SECTOR AT ADDRESS
HEADER VERIFY ERROR AT ADDRESS
Satisfactory completion of the formatting process is signaled
messaqe

the

FORMATTING COMPLETE

FORMATTING FAILED
indicates that one or more
verified.

sectors

could

not

formatted

NOTE
RP02 and RPR02 packs must be formatted
one at a time (that is, not concurrently
on multiple drives that are interfaced
to the same controller).
(Related Error Numbers are:

25, 26, 27, 28, 29, 30)

7-5

and/or

RP02, RPR02, OR RP03 DIAGNOSTIC

7.4

ERROR MESSAGES

Fault conditions detected during the test sequence are reported at the
initiating terminal:
they are classified as equipment errors or
data-compare errors.
Equipment errors are those conditions that
result in the setting of the "error" bit, Bit 15 of the Control and
Status Register (RPCS). Data-compare errors occur when the diagnostic
finds data other than the data expected in data-transfer operations.
Some conditions may cause both an equipment error and a data-compare
error.
The following representations illustrate the context of the various
error messages.
Table 7-1 lists the error numbers and their related
fault conditions. Appendix B defines the register contents displayed
in the error messages.
Equipment error-message format:
RP03
ERROR NO. n
RPDS
=
RPER
RPCS
=
RPWC
RPBA
=
RPCA
RPDA
SUCA

UNIT NO.

Drive Status Register contents
Error Register contents
Control and Status Register contents
Word Count Register contents
Bus Address Register contents
Cylinder Address Register contents
Disk Address Register contents
Selected Unit Cylinder Address Register contents

Data-compare error-message format:
RP03
UNIT NO. m
ERROR NO. n
EXPECTED
Data expected
RECEIVED
Data received
Number (in octal and decimal)
CYLINDER
TRACK
Number (in octal and decimal)
SECTOR
Number (in octal and decimal)
WORD NO. IN SECTOR = Number (in octal and decimal)
Disk-address error-message format:
RP03
UNIT NO. m
ERROR NO. n
DISK ADDRESS DID NOT UPDATE CORRECTLY
CYLINDER
EXPECTED
Cylinder expected
RECEIVED
Cylinder received
TRACK
EXPECTED = Track expected
RECEIVED
Track received
SECTOR
EXPECTED
Sector expected
RECEIVED
Sector received

7-6

RP02, RPR02, OR RP03 DIAGNOSTIC

Other error messages:
REREAD SAME DATA n TIMES BEFORE ERROR
ERROR NO. x RECOVERED AFTER y RETRIES
CONTENTS OF SUCA INCORRECT
CYLINDER ADDRESS WITHIN HEADER INCORRECT
HEADER VERIFY ERROR AT ADDRESS a
UNABLE TO FORMAT SECTOR AT ADDRESS b
Table 7-1
Error Conditions

'-''

Error Number and
Associated Test
Exercise

Fault Condition

Initialization:
1

Error bit was set
during
(recalibration) function.

home-seek

Heads Positioning:
2

Error bit was set after a read-header command
was issued to cylinder O.

Error bit was set after a read-header command
was issued to a cylinder in the range 1
through the valid upper limit.

Error bit was set after a read-header command
was issued to the cylinder address being
incremented from 0 through the valid upper
limit.

Error bit was set after a read-header command
was issued to the cylinder address being
decremented from the valid upper limit.

Sector Addressing:
6

Error bit was set while exercise was writing
a sector with a data pattern eaual to it~
respective sector number.

Error bit was set while exercise was reading
a sector with a data pattern eaual to its
respective sector number.

Data-compare error. Data pattern read from a
sector (0 through 9) on track 0 of cylinder 0
does not contain the
respective
sector
number.
(continued on next page)

7-7

RP02, RPR02, OR RP03 DIAGNOSTIC

Table 7-1 (Cont.)
Error Conditions
Error Number and
Associated Test
Exercise

Fault Condition

Track Addressing and Crossover:
9

Error bit was set while exercise was writing
a 512-word data transfer starting at the last
sector on a track of cylinder O.
The data
pattern is the respective track number.

Error bit was set while exercise was reading
the first two words of the first sector on a
track. The data pattern is the preceding
track number.

Data-compare error. Data pattern read from
the first sector on a track of cylinder 0
does not contain the number of the preceding
track.

Cylinder Addressing and Crossover:
12

Error bit was set while exercise was writing
a 512-word data transfer starting at the last
sector on the last track of a cylinder.
The
data pattern is the cylinder number.

Error bit was set while exercise was reading
the first sector on the first track of a
cylinder. The data pattern is the preceding
cylinder number.

Data-compare error. Data pattern read from
the first sector on the first track of a
cylinder does not contain the number of the
preceding cylinder.

Partial Write:
15

Error bit was set while exercise was writing
sector 0 on track 0 of cylinder 0 with all
l's data.

Error bit was set while exercise was writinq
a 2-word transfer of all-l's data in sector b
on track 0 of cylinder O.

Error bit was set while exercise was reading
the contents of sector 0 on track 0 of
cylinder O.

Data-compare error. Data pattern read does
not contain l's in the initial two words and
O's in the remainder of the sector.
(continued on next page)

7-8

RP02, RPR02, OR RP03 DIAGNOSTIC
Table 7-1 (Cont.)
Error Conditions

.'--'.
Error Number and
Associated Test
Exercise

Fault Condition

Data-Reliability or Interactive-Data Test:
19

Error bit was set while exercise was
the disk pack with a test pattern.

writino

Error bit was set while exercise was
a test pattern from the disk pack.

readina

Condition may also occur
as a data-compare
error.
Data read from the pack does not
contain the test pattern.
Random:
21

Error bit was set while exercise was writina
a
random data pattern at a randomly selected
address.

Error bit was set after the exercise issued a
seek command with a random address.

Error bit was set while exercise was
reading
random data from a previously written random
address.

Data-compare error.
Data pattern
not contain the random data.

read

does

Formatting:
25

Error bit was set while routine was writing
sector-header patterns to format a track (ten
sectors at a time;
or one sector at a
time
in error recovery).

Error bit was set while routine
sector-header
patterns
from
track.

Word 1 of the formatted header
for
the
indicated sector does not contain all O's.

Word
2 of the formatted header
for
the
indicated sector does not contain the correct
cylinder number (bits 6-14)
or
the correct
track number (bits 1-5).

Word
3 of the formatted header
for
the
indicated sector does not contain the correct
sector address.

was
reading
a
formatted

(continued on next page)

7-9

RP02, RPR02, OR RP03 DIAGNOSTIC
Table 7-1 (Cont.)
Error Conditions
Error Number and
Associated Test
Exercise
Formatting:

Fault Condition

(Cont.)

Error bit was
set
while
routine
was
attempting to write one sector-header pattern
at a time in error recovery.

Interactive-Address Test:

7.5

Error bit was set after a read-header command
was issued to the "first" cylinder selected.

Error bit was set after a read-header command
was issued to the "second" cylinder selected.

SERVICE-MODE INITIATION

Initiation of this mode demands a knowledge of
console-switch
selection (see Section 7.6), test-parameter selection (see Section
7.7), interactive testing (see Sections 7.9 and 7.10), and the content
of Appendix A. Underlined text in this procedure indicates reauired
or expected user input.
Mount "scratch" disk pack on disk drive to be tested.
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DPn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DPn:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN

$RP03

(or RP02 or RPR02)

START RP03 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? DPn
**WARNING** DPn: RESIDENT DATA WILL BE DESTROYED **WARNING**
CONTINUE? SERVICE
(N or RETURN alone aborts the diagnostic)
TEST PARAMETERS (OCTAL)= nnnnnn
CONSOLE SWITCH FOR INTERVENTION (DECIMAL)= n
The selected test sequence commences upon RETURN after you have
responded to all ingu1r1es, if any, that occur as a result of
test-parameters selection.

7-10

·""'

RP02, RPR02, OR RP03 DIAGNOSTIC
7. 6

CONSOL~!

SWITCH FOR INTERVENTION

Service-mode initialization requires that you select a CPU console
switch (0-15) for intervention in the test seouence when, for example,
you desire to change test parameters. The facility to select more
than one switch is useful only if more than one device is to be tested
concurrently;
that is, you can assign a unique switch to each
diagnostic.
For those systems without a CPU switch console or without the GET
SENSE SWITCHES directive, respond to the message "CONSOLE SWITCH ••• "
with O.

7.7

TEST-PARAMETER SELECTION

Customer mode allows only a fixed sequence of the diagnostic's
Service mode,
however,
permits customization of the test
through the test-parameters facility. Table 7-2 describes the
options available to you as a service-mode user. You select
by logically ORing their related octal codes to form a 6-digit
(leading zeros need not be expressed) for entry in response
PARAMETERS (OCTAL)=.

tests.
content
various
options
number
to TEST

Option Description

Selection
Code
(Octal)

STOP ON ERROR (Bit 15):

100000

40000

7-11

RP02, RPR02, OR RP03 DIAGNOSTIC

Table 7-2 (Cont.)
Test-Parameter Options

Option Description

Selection
Code
(Octal)

In
Customer
Mode

INHIBIT ERROR MESSAGE PRINTOUT (Bit 13):

20000

10000

4000

2001

2002

Yes

Prevents
appearance
of
all
diagnostic error messages except
the test summary report
that
appears
at
the end of each
sequence pass.
BELL (Bit 12):
The terminal bell rings for
e·r ror detected.

each

MULTIPASS EXECUTION (Bit 11):
Test sequence repeats until user
intervenes.
The updated test
summary report is displayed at
the end of each pass.
INTERACTIVE-ADDRESS TEST (Bits 10 & 0):
Allows the service-mode user to
oscillate head motion between two
specified cylinders (see Section
7.9 for details).
INTERACTIVE-DATA TEST (Bits 10 & 1):
Allows the service-mode user to
specify explicit conditions for
data reliability testing of the
drive
(see
Section 7.10 for
details).
LIMIT DATA-COMPARE ERROR MESSAGES (Bit 5):
Display an error message only for
the
first
data-compare error
condition
detected
during
a
specified
data transfer.
The
default is:
display an error
message
for
up
to
three
data-compare
error
conditions
detected
during retries of a
specified data transfer.

(continued on next page)

7-12

.......................................................................~. . . .!Im!.......................,.............

RP02, RPR02, OR RP03 DIAGNOSTIC

Table 7-2 (Cont.)
Test-Parameter Options

Option Description

Selection
Code
(Octal)

In
Customer
Mooe

TEST SEQUENCE SELECTION (Bits 0-4):
A)

Select
addressing exercises
(see Section 7.3.1).

Yes

Select
data-reliability
exercise (see Section 7.3.2).

Yes

Select random exercise
Section 7.3.3).

(see

Yes

Select random exercise with
inter-read seeks inhibited to
reduce run time (see Section
7.3.3).

Select formatting routine
without other
exercises~
routine always runs to
completion and exits (see
Sect ion 7. 3. 4) .

Selectable

7.8

SERVICE-MODE INTERVENTION/RESTART/TERMINATION

You can intervene :in (stop) the test-sequence pass at any time by
changing from its current setting (0 to 1 or 1 to 0) the previously
selected CPU console switch.
Such action causes the diaqnostic to
suspend testing and await response to the following message.seauence.
TEST PARAMETERS (OCTAL}=

Type an octal value
(other than 0)
to
select new test parameters (or re-enter the
old parameters, which are not saved at
intervention), or
type O to terminate the diagnostic.

If new (or the old) parameters are entered, the following
displayed.
REST,!:\.RT?

message

Type Y to abort the suspended test seauence
and
initiate the new sequence at the
beginning, or
type N to allow the suspended test seauence
to
run
to completion before the new
sequence commences.

7-13

RP02, RPR02, OR RP03 DIAGNOSTIC

MCR>ABORT
and then reinitiate the diagnostic with new
parameters.
intervention and restart provisions are not accessible.

7.9

The

INTERACTIVE-ADDRESS TEST

This test oscillates the disk drive head
(that is,
continuous
in-and-out motion)
between the two cylinders you specify.
After
test-parameter selection, the test is initialized by your
typing of
valid decimal cylinder numbers in the range 0 through 399.
for an
RP03 drive or 0 through 199.
for an RP02 or RPR02 drive
in response
to the inquiries.
FIRST CYLINDER=
SECOND CYLINDER=
Should you inadvertently type a number greater than the
the inquiry repeats.
Once initiated, the head oscillation
with the selected console switch
command.

continues
or abort

above

range,

until you
intervene
the diagnostic by MCR

The function of the test is to issue seek commands alternately to the
two specified cylinders.
An equipment error message is displayed if
the seek function fails.
(Related Error Numbers are:

7.10

31, 32)

INTERACTIVE-DATA TEST

This test allows you to specify the conditions for determininq the
disk-drive's data reliability.
After test-parameter selection, the
test is initialized by your typing of valid and appropriate responses
to the test's inquiries as noted hereafter.
WORD COUNT=
Type a value to indicate the desired upper
limit of the data
buffer to be used in write/read data-transfer functions (the
value cannot.exceed 512. and must be 2 or more).
If you type a value greater than 512., the inauiry repeats.
DO YOU WISH TO SPECIFY SECTOR ADDRESS?
Type Y if a specified sector address is to be tested.
Type N if all data surfaces of the disk pack are to be written on
and/or read from.
The inquiries, which follow, for cylinder,
track, and sector numbers are inhibited.

7-14

"""'

RP02, RPR02, OR RP03 DIAGNOSTIC
CYLINDER=
This inquiry appears
only
if
you
have
requested
the
sector-addressing feature.
Type the desired cylinder number in
the range 0 though 399.
for an RP03 drive or 0 through 199.
for
an RP02 or RPR02 drive.
If you type a number greater than the
appropriate upper limit, the inquiry repeats.
TRACK=
This inquiry appears
only
if
you
have
reouested
the
sector-addressing feature.
Type the desired track number in the
range 0 through 19 (decimal).
If you type a number greater
than
19., the inquiry repeats.
SECTOR=
This inquiry appears
only
if
you
have
reouested
the
sector-addressing feature.
Type the desired sector number in the
range 0 through 9 (decimal).
If you type a number greater than
9., the inquiry repeats.
PATTERN NO.=
Type the appropriate number, as
indicated below,
to select a
specific stored data pattern or the combination of all stored
patterns for use in exercising the disk drive.
Stored Patterns
All O's
All l's
Checkerboard
Floating l's
Random l's and O's
Count pattern (full-word, binary, sequential)
Run above patterns in sequence

0
1
2
3
4

5
6

You can specify your own pattern to be used
in place of the
stored patterns by typing a full-word (6-digit) octal value in
response to the above inquiry.
WRIT.E?
Type Y to permit performance of write functions during the test.
Type N to inhibit write functions.

7-15

RP02, RPR02, OR RP03 DIAGNOSTIC

READ?
£,....,

Type Y to permit performance of read functions during the test.
Type N to inhibit read functions.
NOTE
An N response to both inquiries
inquiries
will
invalid.
The
repeated.

is
be

19, 20)

7-16

CHAPTER 8
RS03 OR RS04 FIXED-HEAD DISK

(Underlined text indicates reauired or
Chapter 2 for additional information.)

expected

user

input~

see

On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DSn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreiqn.
>MOUNT DSn:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $RS03

(or RS04)

START RS03 DIAGNOSTIC

TIME OF DAY=hour:minute:second

DEVICE? DSn
**WARNING** DSn:
CONTINUE? ¥.

RESIDENT DATA WILL BE DESTROYED **WARNING**
(N or RETURN alone aborts the diagnostic)

Diagnostic runs to completion in 3 minutes for RS03 and 7 minutes
RS04 on a lightly loaded system. To exit sooner, type:

for

(CTRL/C)

MCR>ABORT

8.1

TEST SUMMARY REPORT

Upon completion of each diagnostic-test sequence, the following report
is displayed.
RS03 UNIT NO.
n
(n=unit number)
PASS COUNT=
TOTAL ERRORS ENCOUNTERED=
TOTAL FUNCTIONS ISSUED=
TOTAL WORDS TRANSFERRED=
END OF RS03 DIAGNOSTIC - TIME OF DAY=hour:minute:second
"Pass count" and "totals" are
(initiated in service mode only).

cumulative

8-1

for

multipass

testing

RS03 OR RS04 FIXED-HEAD DISK
8.2

DISK-DRIVE CHARACTERISTICS

The following
are data-capacity
1
fixed-head disks.

parameters

for

the

RS03

and

RS04

RS03
Tracks

Sectors/Track

Words/Sector

128

This diagnostic executes data transfers in logical blocks of 256 words
each except for
the 2-word reads of the Random-Addressing Exercise.
Initial sector addressing, therefore, is in multiples of four for
the
RS03 and in multiples of two for the RS04.

8.3

DIAGNOSTIC DESCRIPTION

The diagnostic tests the ability of the selected disk drive to address
correctly all tracks and sectors of the disk, and to write data on,
and to read data from, the disk under selected conditions.
Neither
ECC correction nor "bad sector (block)" processing are implemented.
The exercises described hereafter are
uninterrupted sequence for customer mode.
following each description appear in error
Section
8.4
conditions;
refer
to
significance.

8.3.l

executed in
a
one-pass
The "Related Error Numbers"
messages for detected fault
and Table 8-1 for
their

Addressing Exercises

8.3.1.1 Sequential Addressing Exercise - This exercise determines
that all tracks and sectors of the selected disk are addressable in
sequence. The exercise first writes the entire surface in blocks of
256 words each (four RS03 disk sectors or two RS04 disk sectors).
The
data pattern written in each word is:
High-order byte--respective track number, right justified
Low-order byte--respective disk-sector number, right justified
where the disk sector numbers increment from 0 by four
for
the RS03
and by two for
the RS04.
The exercise then reads each block and
verifies its content for agreement with the written pattern.
All
error conditions are reported.
(Related Error Numbers are:

2, 3, 4)

8.3.1.2 Random-Addressing Exercise - This exercise determines that
the disk responds correctly to random addressing.
The exercise issues
a 2-word read with a randomly selected track-sector address to access
the data written previously by the Sequential-Addressing Exercise.
The data read is compared with the expected pattern and reported
if
not in agreement.
The expected pattern consists of the respective
track number in the high-order byte and the initial sector number of

8-2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1111111-.•1.-i•

RS03 OR RS04 FIXED-HEAD DISK
Reading continues until
the respective block in the low-order byte.
512 random addresses have been checked.
All error conditions are
reported.
(Related Error Numbers are:

5, 6)

Data··Reliabili ty Exercise

8. 3. 2

This exercise determines the reliability of the disk drive to write
and read data of various patterns in 256-word blocks (four RS03
sectors or two RS04 sectors}.
The data patterns used are:
1.

All 0 Is

All 1 Is

Checkerboard (alternate l's and O's}

Floating l's (sequenced bit-position advancement through each
word}

Random data

Count pattern (from "l," add 1 for each word written)
NOTE
In customer mode, only the floating-l's
pattern is implemented to reduce the run
time for the complete test sequence.

Each pattern is written at all addresses, and then read back eight
times for verification and to expose possible read-reduction problems.
Detection of any error while reading causes the exercise to report the
failing address and then to attempt up to eight retries to read the
data.
If the read is successful,
the exercise reports the error
recovered after "n" retries and advances to the next sector address.
If the read remains unsuccessful after eight retries,
the exercise
terminates the recovery attempt and advances reading to the next
sector address.
The absence of a
"recovered"
report signifies an
unsuccessful recovery.
(Related Error Numbers are:

7, 8)

Random Exercise

8.3.3

random

sector-address

Develop
a
combination.

Initiate a write transfer of a random-length,
random-data
pattern, beginning at the random disk address.
The number of
words is two or more, and not more than 512.

8-3

track-

and

RS03 OR RS04 FIXED-HEAD DISK
3.

Initiate eight read transfers of the previously written
random data
(the purpose of this command sequence is to
expose read-reduction problems).

Verify the data returned.

Detection of any error while reading causes the exercise to report the
failing address and to attempt up to eigh~ retries to read the data.
If the read is successful, the exercise reports the error recovered
after "n" retries and advances to the next disk address.
If the read
remains unsuccessful after eight retries, the exercise terminates the
recovery attempt and advances reading to the next sector address. The
absence of a "recovered" report signifies an unsuccessful recovery.
(Related Error Numbers are:

8.4

9, 10, 11)

ERROR MESSAGES

Fault conditions detected during the test sequence are reported at the
initiating terminal;
they are classified as equipment errors or
data-compare errors.
Equipment errors are those conditions that
result in the setting of the "error" bit, Bit 14 of the Drive Status
Register (RSDS). Data-compare errors occur when the diagnostic finds
data other than the data expected in data-transfer operations.
Some
conditions may cause both an equipment error and a data-compare error.
The following representations illustrate the context of the various
error messages.
Table 8-1 lists the error numbers and their related
fault conditions.
Appendix B defines the register contents displayed
in the error messages.
Equipment error-message format:
RS03
ERROR NO. n
RSCSl
RSWC
RSBA
RSDA
RSCS2
RSDS
RSER
RSAS

UNIT NO.

Control and Status 1 Register contents
word Count Register contents
Bus Address Register contents
Desired Address Register contents
Control and Status 2 Register contents
Drive Status Register contents
Error Register contents
Attention Summary Register contents

Data-compare error-message format:
RS03
ERROR NO. n
EXPECTED
RECEIVED

UNIT NO.

Data expected
Data received

Disk-address error-message format:
RS03
ERROR NO. n
DISK ADDRESS
TRACK
EXPECTED
RECEIVED
SECTOR
EXPECTED
RECEIVED

UNIT NO.

DID NOT UPDATE CORRECTLY
Track expected
Track received
Sector expected
Sector received

8-4

RS03 OR RS04 FIXED-HEAD DISK
Sector error-message format:
RS03
UNIT NO. m
ERROR NO. n
EXPECTED
Data expected
RECEIVED
Data received
TRACK
Number {in octal and decimal)
SECTOR
Number {in octal and decimal)
WORD NO. IN SECTOR=Number {in octal and decimal)
Other error messages:
REREAD SAME DATA n TIMES BEFORE ERROR
ERROR NO. x RECOVERED AFTER m RETRIES
Table 8-1
Error Conditions
JE:rror Number and
Associated Test
Exercise

Fault Condition

Initialization:
1

Error bit was set while exercise was reading
the disk type to determine whether the disk
selected {by mnemonic and unit number) is an
RS03 or RS04.

Sequential Addressing:
2

Error bit was set while exercise was writing
a 256-word block in four RS03 sectors or two
RS04 sectors;
the data pattern is
the
respective track number
in the high-order
byte and the respective sector number in the
low-order byte.

Error bit was set while exercise was reading
a 256-word block from four RS03 sectors or
two RS04 sectors;
the data pattern is the
respective track number
in the high-order
byte and the respective sector number in the
low-order byte.

Data-compare error. The data pattern read
from a
256-word block does not contain the
respective track number
in the high-order
byte and the respective sector number in the
low-order byte.

Random Addressing:
5

Error bit was set while exercise was reading
the initial two words of a 256-word block
{four RS03 sectors or two RS04 sectors).
{continued on next page)

8-5

RS03 OR RS04 FIXED-HEAD DISK
Table 8-1 (Cont.)
Error Conditions
Error Number and
Associated Test
Exercise
Random Addressing:
6

Fault Condition
(Cont.)
Data-compare error.
The contents of the
initial two words read from a 256-word block
does not reflect the desired address.

Data-Reliability or Interactive-Data Test:
7

Error bit was set while exercise was
the disk with a test pattern.

writina

Error bit was set while exercise was
a test pattern from the disk.

reading

Condition may also occur as a data-compare
error.
Data read from the disk does not
contain the expected test pattern.
Random:

8.5

Error bit was set while exercise was writing
a random-data pattern at a randomly selected
address.

Error bit was set while exercise was reading
random data from a previously written random
address.

Data-compare error.
Data pattern read
not contain the expected random data.

does

SERVICE-MODE INITIATION

Initiation of this mode demands a knowledge of
console-switch
selection
(see Section 8.6),
test-parameter selection (see Section
8.7), interactive testing
(see Section 8.9),
and the content of
Appendix A.
Underlined text in this procedure indicates reauired or
expected user input.
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DSn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DSn:/FOR

8-6

RS03 OR RS04 FIXED-HEAD DISK
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $RS03

(or RS04)

START RS03 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? Q.§JJ.
**WARNING** DSn:
RESIDENT DATA WILL BE DESTROYED **WARNING**
CON'I'INUE? SERVICE
(N or RETURN alo:ne aborts the diagnostic)
TEST PARAMETERS (OCTAL)=nnnnnn
CONSOLE SWITCH FOR INTERVENTION (DECIMAL}=n
The selectd test sequence commences upon RETURN after you have
responded to all
inquiries,
if any,
that occur as a result of
test-parameters selection.

8.6

CONSOLE SWITCH FOR INTERVENTION

Service-mode initialization requires that yoµ
select a CPU console
switch (0-15) for intervention in the test s:eouence when, for example,
you desire to change test parameters.
The if~cility to select more
than one switch is useful only if more than '.one device is to be tested
concurrently;
that is,
you can assign s unique switch to each
diagnostic.
·
For those systems without a CPU switch console or without the GET
SENSE SWITCHES directive, respond to the ~essage "CONSOLE SWITCH ••• fl
with 0.

8.7

TEST-PARAMETER SELECTION

Customer mode allows only a fixed sequence of the diagnostic's
Se!rvice mode,
however,
permits customization of the test
through the test-parameters facility.
Table 8-2 describes the
options available to you as a service-mode user.
You select
by logically ORing their related octal codes to form a 6-digit
(leading zeros need not be expressed) for entry in response
PARAMETERS (OCTAL}=.

tests.
content
various
options
number
to TEST

NOTE
A response of 0 implies that no tests
are to be performed.
The diagnostic
issues the test summary report and then
terminates.
The table also indicates those options that are automatically selected
for
customer-mode execution.
The "bit" references
in the option
descriptions refer to the bit positions 6f a test-parameters status
word that is monitored by the diagnostic.

8-7

RS03 OR RS04 FIXED-HEAD DISK
Table 8-2
Test-Parameter Options

""'

Option Description
STOP ON ERROR (Bit 15):

Selection
Code
(Octal)

In
Customer
Mode

100000

40000

20000

10000

4000

Test sequence waits up to 30
minutes before terminating.
User
may abort stop by setting console
switch selected for intervention.
LOOP ON ERROR (Bit 14):
Test sequence
loops
on
the
failing
instruction
sequence.
User should intervene and select
new test parameters that exclude
this option.
INHIBIT ERROR MESSAGE PRINTOUT (Bit 13):
all
appearance
of
Prevents
diagnostic error messages except
that
the test summary report
at
the end of each
appears
sequence pass.

BELL (Bit 12):
The terminal bell rings for
error detected.

each

MULTIPASS EXECUTION (Bit 11):
Test sequence repeats until user
intervenes.
The updated test
summary report is displayed at
the end of each pass.
INTERACTIVE-DATA TEST (Bits 10 & 1):

~-,

2002

Allows the service-mode user
to
specify explicit conditions for
data reliability testing of the
drive
(see
Section
8.9 for
details).
(continued on next page)

8-8

,. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
1

RS03 OR RS04 FIXED-HEAD DISK

Table 8-2 (Cont.)
Test-Parameter Options
Selection
Code
(Octal)

Option Description
LIMIT DATA-COMPARE ERROR MESSAGES (Bit 5) :

In
Customer
Mode

Yes

Display an error message only for
the
first
data-compare error
condition
detected
during
a
specified
data transfer.
The
display an error
default is:
message
for
up
to
three
error
data-compare
conditions
detected
during retries of a
specified data transfer.
TEST SEQUENCE SELECTION (Bits 0-2) :
A)

Select addrt:!ssing exercises
(see Section 8.3.1).

Yes

Select
data-reliability
exercise (see Section 8.3.2).

Yes

Select random exercise (see
Section 8.3.3).

Yes

8. 8

SERVICE-·MODE INTERVENTION/RESTART /TERMINATION

You can intervene in (stop) the test-sequence pass at any time by
changing from its current setting (0 to 1 or 1 to 0) the previously
sele~cted CPU console switch.
Such action causes the diagnostic to
suspend testing and await response to the following message seauence.
TEST PARAMETERS (OCTAL)=

Type an octal value
(other than 0)
to
select new test parameters (or re-enter the
old parameters, which are not saved at
intervention), or
type 0 to terminate the diagnostic.

If new (or the old) parameters are entered, the following
displayed.
RES~rART?

message

Type Y to abort the suspended test seauence
and
initiate the new seauence at the
beginning, or
type N to allow the suspended test sequence
to
run
to completion before the new
sequence commences.

8-9

RS03 OR RS04 FIXED-HEAD DISK
For those systems not equipped with a CPU switch console or not
implemented with the GET SENSE SWITCHES directive, the user wishing to
alter test parameters must first terminate the diagnostic by typing:
(cTRL/c)
MCR>~

and then reinitiate the diagnostic with new
parameters.
intervention and restart provisions are not accessible.

8.9

The

INTERACTIVE-DATA TEST

This test allows you to specify the conditions for determining the
disk-drive's data reliability.
After test-parameter selection, the
test is initialized by your typing of valid and appropriate responses
to the test's inquiries as noted hereafter.
WORD COUNT=
Type either 256.
or 512.
to indicate the desired upper limit of
the data buffer to be used in write/read data-transfer functions.
If you type a value greater than 512., the inquiry repeats.
DO YOU WISH TO SPECIFY SECTOR ADDRESS?
Type Y if a specified sector address is to be tested.
Type N .if all data surfaces of the disk are to be written on
and/or read from.
The inqu1r1es, which follow, for track and
sector numbers are inhibited.
TRACK=
This inquiry appears
only
if
you
have
reauested
the
sector-addressing feature.
Type the desired track number in the
range 0 through 63 (decimal).
If you type a number greater
than
63., the inquiry repeats.
SECTOR=
This inquiry appears
only
if
you
have
reauested
the
sector-addressing feature.
Type the desired sector number in the
range 0 through 63.
(for RS03,
the sector number must be a
multiple of four;
for RS04
it must be even).
If you type a
number greater than 63., the inquiry repeats.
The message
RS03 SECTOR ADDRESS MUST BE A MULTIPLE OF FOUR
or
RS04 SECTOR ADDRESS MUST BE EVEN
alerts you to an invalid entry.

8-10

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
1
. .,

RS03 OR RS04 FIXED-HEAD DISK
PAT~rnRN

NO.=

Type the appropriate number, as
indicated below,
to select a
specific stored data pattern or the combination of all stored
patterns for use in exercising the disk drive.
Stored Patterns

No.

All O's
All l's
Checkerboard
Floating l's
Random l's and O's
Count pattern (full-word, binary, sequential)
Run above patterns in sequence

0
1

2
3
4
~

You can specify your own pattern to be used
in place of the
stored patterns by typing a
full-word
(6-digit) octal value
(followed by RETURN) in response to the above inquiry.

......,,.

WRI'TE?
Type y to permit performance of write functions during the test.
Type N to inhibit write functions.
READ?
Type y to permit performance of read functions during the test.
Type N to inhibit read functions.
NOTE
An N response to both inquiries
invalid.
The
inquiries
will
repeated.

is
be

7, 8)

8-11

CHAPTER 9

TU56 DECTAPE DIAGNOSTIC

. . CUSTOMER-MODE INITIATION . . . . . . . . . . . ..
(Underlined text indicates required or
Chapter 2 for additional information.)

expected

user

input~

see

Install "scratch" DECtape on drive to be tested.
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DTn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DTn:/FOR
On both RSX--llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $TU56
START TU56 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE'? DTn
**WARNING** DTn:
CONTINUE? X

RESIDENT DATA WILL BE DESTROYED **WARNING**
(N or RETURN alone aborts the diagnostic)

Diagnostic runs to completion in
system.
To exit sooner, type:

minutes

for

lightly

loaded

(cTRL/C)

MC R >Afill.B1'

."-"'

9.1

TEST SUMMARY REPORT

Upon completion of each diagnostic test sequence, the following report
is displayed.
TU56 UNIT NO.
n
(n=unit number)
PASS COUNT=
TOTAL ERRORS ENCOUNTERED=
TOTAL FUNCTIONS ISSUED=
TOTAL WORDS TRANSFERRED=
END OF TU56 DIAGNOSTIC - TIME OF DAY=hour:minute:second
"Pass count" and "totals" are
(initiated in service mode only).

cumulative

9-1

for

multipass

testing

TU56 DECTAPE DIAGNOSTIC
9.2

DEVICE CHARACTERISTICS

The following are data-capacity parameters for DECtape.

9.3

Blocks/Reel

578

Words/Block

256

DIAGNOSTIC DESCRIPTION

The TU56 diagnostic tests the ability of the selected DECtape drive to
position its resident DECtape correctly, and to write and read data
correctly under selected conditions.
The exercises described hereafter are
uninterrupted sequence for customer mode.
following each description appear in error
conditions;
refer
to
Section
9.4
significance.

9.3.1

executed in a one
pass
The "Related Error Numbers"
messages for detected fault
and Table 9-1 for
their

DECtape Positioning and Data Compare Exercises

9.3.1.1 Rewind Exercise - This exercise determines that the drive, as
result of a read-block-0-reverse command, rewinds its DECtape to the
end-zone and indicates this by setting the status register's end zone
bit and the command register's error bit.
(Related Error Number is:

9.3.1.2 Block Write-Read Exercise - This exercise determines that the
drive can write and read blocks 0 and 1 in both directions.
The
sequence is:
1.

Write block 0 forward with all O's.
then forward.

Write blocks 0 and 1 forward with all l's.
reverse and then forward.

Write blocks 1 and 0 in reverse with all l's.
reverse and then forward.

(Related Error Numbers are:

Read block

Read

reverse,
blocks

Read blocks in

2, 3, 4, 5, 6, 7, 8, 9, 10)

9.3.1.3 Odd-Even Block Exercise - This exercise determines that the
drive can address each block uniquely, and write and retrieve data
correctly.
First, all odd-numbered blocks are written forward and all
even-numbered blocks are written in reverse.
The data pattern for
each block is its block number.
Then,
all odd-numbered blocks are
read in reverse, and all even-numbered blocks are read forward.
The
data read from each block is compared to the expected-block number
pattern.
(Related Error Numbers are:

11, 12, 13, 14}

9-2

4·----·•.:••·--------. .-----------------.---l'llm..------------. .--1-;

•t-..

i'tl'

TU56 DECTAPE DIAGNOSTIC

9.3.1.4 Random Read Exercise - This exercise determines that the
drive can address and read 20 randomly selected blocks. The data read
from each block is compared to the expected-block number pattern
written
by the odd-even block exercise (see previous exercise
de:scription}.
(Related Error Number is:

15)

Stop-Start Exercise

9.3.2

This exercise determines that the drive stops and starts its DECtape
motion within the prescribed limits in both directions. DECtape
should halt within approximately two blocks when the controller issues
a
stop
command to the drive, and reach normal speed within
approximately two blocks when a read block ·number command is issued.
The exercise also determines that the DECtape moves in the reauired
direction. The sequence is:
1.

Rewind DECtape
command}.

Read a block number forward
successful read}.

Read another block number forward.

Determine that the second block number is greater than the
first block number, indicating forward motion, and, secondly,
that the second block number is within five blocks of the
first block number.

Read a block number in reverse.

Read another block number in reverse.

Determine that the second block number is less than the first
block number, indicating reverse motion, and, secondly, that
the second block number is within five blocks of the first
block number.

(Related Error Numbers are:

end

zone

(by

(drive

read-block-0-reverse

shuts

down

after

each

16, 17, 18, 19, 20, 21, 22, 23}

Data-Reliability Exercise

9.3.3

This exercise determines the reliability of the drive to write and
read data of various patterns in blocks 64 through 192 in forward and
reverse directions. The data patterns used are:
1.

Al 1 0 's

Al 1 1 's

Checkerboard (alternate l's and O's)

Floating l's (sequenced bit-position advancement through each
word}

Random data

Count pattern (from "l," add 1 for each word written}

9-3

TU56 DECTAPE DIAGNOSTIC
NOTE
In customer mode, only the floating-l's
pattern is implemented to reduce the run
time for the complete test sequence.
For each pattern, the DECtape is first written and read forward,
and
then read in reverse.
Detection of an error while reading results in
the exercise attempting up to eight retries to read the data.
(Related Error Numbers are:

9.4

24, 25)

ERROR MESSAGES

Fault conditions detected during the test sequence are reported at the
initiating terminal;
they are classified as equipment errors or
data-compar~ errors.
Equipment errors are those conditions
that
result
in the setting of the
"error" bit, Bit 15 of the Command
Register (TCCM).
Data-compare errors occur when the diagnostic finds
data other than the data expected in data-transfer operations.
Some
conditions may cause both an equipment error and a data-compare error.
The following representations illustrate the context of the various
error messages.
Table 9-1 lists the error numbers and their related
fault conditions.
Appendix B defines the register contents displayed
in the error messages.
Equipment error-message format:
TU56
UNIT NO.
m
ERROR NO.
n
TCST=
Control and Status Register contents
TCCM=
Command Register contents
TCWC=
Word Count Register contents
TCBA=
Bus Address Register contents
FORWARD (OR REVERSE) DIRECTION
Data-compare error-message format:
TU56
UNIT NO.
m
ERROR NO.
n
EXPECTED=
Data expected
RECEIVED=
Data received
BLOCK ADDRESS=
Number {in octal and decimal)
WORD NO.
IN BLOCK= Error position in block
Other error messages:
SELECT OR WRITE ENABLE ERROR
TAPE MOVED FORWARD INSTEAD OF REVERSE
TAPE MOVED REVERSE INSTEAD OF FORWARD
ERROR BIT IN TCCM FAILED TO SET WHEN END ZONE DETECTED
END ZONE FOUND EARLY WHILE DOING READ BLOCK NO.
ERROR NO.

x RECOVERED AFTER y RETRIES.

9-4

TU56 DECTAPE DIAGNOSTIC
Table 9-1
Error Conditions
Error Number and
Associated Test
Exercise

Fault Condition

Rewind:
1

End zone not detected
TCCM did not set.

and/or

error

bit

Block Read-Write:
2

Write of block 0 forward failed;
data is all O's written forward.

expected

Read of block 0 in reverse failed;
data is all O's written forward.

expected

Read of block 0 forward failed;
data is all O's written forward.

exr;>ected

Write of blocks 0 and 1 forward failed;
expected data is all l's written forward.

Read of blocks 0 and 1 in reverse failed;
expected data is all l's written forward.

Read of blocks 0 and 1 forward failed;
expected data is all l's written forward.

Write of blocks 0 and 1 in reverse failed;
expected data is all l's written in reverse.

~··

Read of blocks 0 and 1 in reverse fa ilea;
expected data is all l's written in reverse.
10

Read of blocks 0 and 1 forward failed;
expected data is all l's written in reverse.

Odd-Even Block:
11

Write of odd-numbered block
expected data pattern is
written forward.

JL 2

Write of even-numbered block in
reverse
failed;
expected data pattern is its block
number written in reverse.

Read of odd-numbered block in reverse failed;
expected data pattern is its block number
written forward.

Read of even-numbered block
expected data pattern is
written in reverse.

forward failed;
its block number

(continued on next page)

9-5

TU56 DECTAPE DIAGNOSTIC
Table 9-1 (Cont.)
Error Condi'tions
Error Number and
Associated Test
Exercise

Fault Condition

Random Read:
15

Read of randomly addressed block failed;
data pattern expected is its block number,
written forward for odd block numbers and in
reverse for even numbers.

Stop-Start:
16

Read of a block number forward failed.

A block number read forward after the start
of DECtape motion was not within five blocks
of the block number read prior to drive
shutdown.

DECtape did not move forward from "stop" in
response
to
a
read-block-number-forward
command.

End zone detected before it was expected.

Read of a block number in reverse failed.

A block number read in reverse after the
start of DECtape motion was not within five
blocks of the block number read prior to
drive shutdown.

DECtape did not move in reverse from "stop"
in response to a read-block-number-reverse
command.

End zone detected before it was expected.

Data-Reliability or Interactive-Data Test:
24

Write of various data patterns in blocks 64
through 192 or user-selected block failed.

Read of various data patterns in blocks 64
through 192 or user-selected block failed.

Interactive-Address Test:
26

Write of user-selected "first" block failed;
command specified a 4-byte write of data.

Write of user-selected "second" block failed;
command specified a 4-byte write of data.

9-6

""'·

TU56 DECTAPE DIAGNOSTIC
9.5

SERVICE-MODE INITIATION

Initiation of this mode demands a knowledge of
console-switch
selection
(see Section 9.6),
test-parameter selection (see Section
9.7), interactive tE~sting (see Sections 9.9 and 9.10), and the content
of Appendix A. Underlined text in this procedure indicates reauired
or expected user input.
Install "scratch" DECtape on drive to be tested.
On both RSX-·llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DTn:

{n=uni t number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DTn:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $TU56
START TU56 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE'.? DTn
**WARNING** DTn:
RESIDENT DATA WILL BE DESTROYED **WARNING**
CONTINUE? SERVICE
(N or RETURN alone aborts the diagnostic)
TEST PARAMETERS (OCTAL)= nnnnnn
CONSOLE SWITCH FOR INTERVENTION (DECIMAL)= Q
The selected test sequence commences upon RETURN after you have
responded to all
inquiries,
if any~
that occur as a result of
test-parameters selection.

9.6

CONSOLE SWITCH FOR INTERVENTION

Service-mode initialization requires that you select a CPU console
switch (0-15) for intervention in the test sequence when, for example,
you desire to change test parameters. The facility to select more
than one switch is useful only if more than one device is to be tested
concurrently~
that is,
you can assign a unique switch to each
diagnostic.
For those systems without a CPU switch console or without the GET
SENSE SWITCHES directive, respond to the message "CONSOLE SWITCH ..• "
with 0.

9.7

TEST-PARAMETER SELECTION

9-7

TU56 DECTAPE DIAGNOSTIC

NOTE
A response of 0 implies that no tests
are to be performed.
The diagnostic
issues the test summary report and then
terminates.
The table also indicates those options that are automatically selected
for
customer-mode execution.
The "bit"
references in the option
descriptions refer to the bit positions of a test-parameters status
word that is monitored by the diagnostic.
Table 9-2
Test-Parameter Options

Option Description

Selection
Code
(Octal)

In
Customer
Mode

STOP ON ERROR (Bit 15) :

100000

40000

20000

10000

4000

Test sequence waits up to 30
minutes before exiting.
User may
abort stop by setting console
switch selected for intervention.
LOOP ON ERROR (Bit 14) :
Test sequence
loops
on
the
failing
instruction
sequence.
User should intervene and select
new test parameters that exclude
this option.
INHIBIT ERROR MESSAGE PRINTOUT (Bit 13) :
Prevents
appearance
of
all
diagnostic error messages except
the test summary report·
that
appears
the end of each
at
sequence pass.
BELL (Bit 12) :
The terminal bell rings for
error detected.

each

MULTI PASS EXECUTION (Bit 11):
Test sequence repeats until user
intervenes.
The updated test
summary report is displayed at
the end of each pass.

(continued on next page)

9-8

TU56 DECTAPE DIAGNOSTIC

Table 9-2 (Cont.)
Test-Parameter Options
I

Option Description
INTERACTIVE-ADDRESS TEST (Bits 10 & 0):

Selection
Code
(Octal)

In
Customer
Mode

2001

2002

Yes

Allows the service-mode user to
"rock"
the
DECtape
between
specified blocks (see Section 9.9
for details).
INTERACTIVE-DATA TESTING (Bits 10 & 1):
Allows the service-mode user to
specify explicit conditions for
data-reliability testing of the
drive
(see
Section 9.10 for
details).
LIMIT DATA COMPARE ERROR MESSAGES (Bit 5):

Select
DECtape-positioning
and
data-compare exercises
(see Section 9.3.1).

Yes

Select
data-reliability
exercise (see Section 9.3.3).

Yes

Select
stop-start exercise
(see Section 9.3.2).

Yes

9.8

SERVICE-MODE INTERVENTION/RESTART/TERMINATION

You can intervene in (stop) the test-sequence pass at any time by
chan9ing from its current setting (0 to 1 or 1 to 0) the previously
selected CPU console switch.
Such action causes the diagnostic to
suspe~nd testing and await response to the following message seauence.

9-9

TU56 DECTAPE DIAGNOSTIC

TEST PARAMETERS (OCTAL)=

Type an octal value
(other than 0)
to
select new test parameters (or re-enter the
old parameters, which are not saved at
intervention), or
type 0 to terminate the diagnostic.

If new (or the old) parameters are entered, the following
displayed.
RESTART?

message

Type Y to abort the suspended test sequence
and
initiate the new sequence at the
beginning, or
type N to allow the suspended test sequence
to
run
to completion before the new
sequence commences.

MCR>ABORT
and then reinitiate the diagnostic with new
parameters.
intervention and restart provisions are not accessible.

9.9

The

INTERACTIVE-ADDRESS TEST

This test "rocks" the DECtape (that is, continuous forward-and-reverse
motion)
between any two blocks you specify. After test-parameter
selection, the test is initialized by your typing of two valid block
numbers in the range 0 through 577.
in response to the inquiries.
FIRST BLOCK =
SECOND BLOCK =
Should you inadvertently enter a number greater than 577., the inquiry
repeats.
Once initiated, the DECtape rock continues until you
intervene with
the selected console switch or abort the diagnostic by MCR command.
~'he

function of this test is to issue write commands to the specified
blocks with byte counts of 4 and an all-O's pattern.
An eauipment
error message is displayed if the write function fails at any time.
(Related Error Numbers are:

9.10

26, 27)

INTERACTIVE-DATA TEST

~?his

test allows you to specify the conditions for determining the
drive's data reliability. After test-parameter selection, this test
is initialized by your typing of valid and appropriate responses to
the test's inquiries as noted hereafter.

9-10

TU56 DECTAPE DIAGNOSTIC
WORD COUNT=
Type a value (no greater than 512.) to indicate the desired
of the data buffer to be used in write/read functions.

size

DO YOU WISH TO SPECIFY THE BLOCK ADDRESS?
Type Y if a specific block is to be exercised.
Type N if the single
Your selected test
192 (decimal).

block-addressing feature
is not needed.
will therefore operate on blocks 64 throuqh

BLOCK ADDRESS=
This inquiry appears
only
if
you
have
reauested
the
block-addressing feature.
Type the desired block number in the
range 0 through 577 (decimal).
PATTERN NO=
Type the appropriate number, as
indicated below,
to select a
specificv
stored data pattern or the combination of all stored
patterns.
No.

Stored Patterns
All O's
All l's
Checkerboard
Floating l's
Random l's and O's
Count pattern (full-word, binary, sequential)
Run above patterns in sequence

1
2
3
4
5
6

You can specify a pattern to be used in place of the stored
patterns by typing a 6-digit octal value in response to the
inquiry.
WRITE?
Type y to permit performance of write functions during the test.
Type N to inhibit write functions
READ'?
Type y to permit performance of read functions during the test.
Type N to inhibit read functions.
NOTE
An N response to both
inquiries
invalid.
The inquiries are repeated.

9-11

TUS6 DECTAPE DIAGNOSTIC

li'QRWARD DIRECTION?
.,,..,
..
.....
_~
-_-·_-..,,:

~
__

Type Y to restrict the test to the forward direction only.
Type N to restrict the test to the reverse direction only.
With selection of the direction-condition established, the test
commences and continues until you intervene with the selected console
switch or abort the diagnostic by MCR command.
(Related Error Numbers are:_

24, 25)

"'!

9-12

CHAPTER 10
TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC

CUSTOMER-MODE INITIATION - - - - - - •

(Underlined text indicates required or
Chapter 2 for additional infor~ation.)
~·

Install "scratch" tape, with
drive to be tested.

expected

user

ring

installed,

write-enable

input;
on

see
tape

On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE MMn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT MMn:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
(or TU45)
START TU16 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? MMn
**WARNING** MMn:
RESIDENT DATA WILL BE DESTROYED **WARNING**
CONTINUE? X
(N or RETURN alone aborts the diagnostic)
TEST IN 1600 BPI MODE?
(N initiates 800 BPI mode)
QUICK TOTAL TAPE CHECK? (Y tests tape's reliability and exits)
(N initiates customer-mode test sequence)
Diagnostic runs to completion in
system. To exit sooner, type:

10.1

minutes

for

lightly

loaded

TEST SUMMARY REPORT

Upon completion of each diagnostic test sequence, the following report
is displayed.
TU16 UNIT NO.
n
(n=unit number)
PASS COUNT=
TOTAL ERRORS ENCOUNTERED=
TOTAL FUNCTIONS ISSUED=
TOTAL WORDS TRANSFERRED=
END OF TU16 DIAGNOSTIC - TIME OF DAY=hour:minute:second

10-1

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
"Pass count" and "totals" are
(initiated in service mode only).

10.2

cumulative

for

multipass

testing

TAPE DRIVE CHARACTERISTICS

Channels (tracks)

Recording density, bits
per inch (BPI)

800 or 1600

Tape speed, inches per
second

45 normal
150 rewind

75 normal
225 rewind

Recording

NRZI for 800 BPI,
phase encoded for
1600 BPI

NRZI for 800
BPI, phase
encoded for 1600
BPI

Interrecord Gap
(IRG)

0.5 in.
minimum
0.60 in.
nominal

0. 5 in.
minimum
0. 60 in.
nominal

Extended IRG

3.0 in.

End-of-File
(EOF) Character

23 (octal)

minimum

(octal)

Figures 11-1 and 11-2 in Chapter 11
illustrate the relationship
between tape characters and memory bytes,
and the 9-channel tape
format.
The correlation between PDP-11 memory bits and 9-channel tape
is as follows:
Bit Positions (high-order byte) 15 14 13 12 11 10 9 8
Bit Positions (low-order byte)
7 6 5 4 3 2 1 0
7

Channel Numbers

1 8 2

Tape Channel No. 4 is parity.

10.3

DIAGNOSTIC DESCRIPTION

The TU16/TU45 diagnostic tests the ability of the selected tape
to:
1.

Position its resident tape correctly,

Write and read data correctly, and

Check for parity errors.

The exercises described
uninterrupted sequence for
following each description
conditions;
refer
to
significance.

drive

hereafter are executed in
a
one-pass
customer mode.
The "Related Error Numbers"
appear in error messages for detected fault
Section 10.4 and Table 10-1 for
their

10-2

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
10.3.l

Beginning-of-Tape (BOT) Exercise

First, this exercise determines that the tape positions at BOT ~fter a
rewind command,
and then that the tape remains at BOT although a
backspace (space-reverse) command is issued.
(Related Error Numbers are:

10.3.2

1, 2)

Interrecord-Gap (IRG) Exercise

This exercise determines that IRG's produced by the drive are of
adi=guate length for tape motion to decrease from normal speed to stop
(shutdown in an IRG)
and increase to normal speed,
in either
direction,
before an IRG-boundary reaches the write-read heads.
The
sequence is:
1.

Rewind the tape.

Write ten 16-byte records, all l's, and rewind tape.

Read each record and verify its character count,
waiting
after each read for tape motion to stop before issuing the
next read-one-record command.

(Related Error Numbers are:

10.3.3

3, 4)

Variable-Length Record Positioning Exercise

This exercise determines that the drive properly responds to commands
specifying the writing and reading of records of varying lengths.
The
sequence is:
1.

Rewind the tape.

From BOT, write 63 all-l's records decreasing in length by
16-byte decrements from 1024 bytes, initially, to 16 bytes;
then write 63 all-l's records increasing in length by 16-byte
increments from 16 bytes to 1024 bytes.

Rewind the tape.

Read thE~ records by read-one-record commands,
allowing tape
motion to stop before issuing the next read.
Determine that
record lengths agree with those written as specified above.

(Related Error Numbers are:

10.3.4

5, 6)

Record-Length Exercise

This exercise determines that the drive writes a 512-byte all-l's
record,
and then properly responds to read commands that specify a
byte count larger (1024) or smaller (511)
than the written record.
The data pattern is not checked for correct content.
(Related Error Numbers are:

7, 8, 9, 10)

10-3

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
10.3.5

Lateral-Parity Exercise

This exercise determines that the drive responds
lateral parity errors,
which are forced by
all-l's record with odd parity and then reading
The reverse condition is checked by writing the
and reading it as odd parity. The data pattern
correct content.
{Related Error Numbers are:

10.3.6

properly to apparent
writing one 512-byte
it as even µarity.
record as even parity
is not checked for

11, 12, 13, 14, 15)

Longit~dinal-Parity-Check-Character

(LPCC) Exercise

This exercise determines that the drive's LPCC facility
functions
properly.
The exercise writes one 1024-byte record with a data
pattern {an all-O's byte followed by 1023 all-l's bytes)
that has a
predicted LPCC~
it then checks for the presence of the predicted
LPCC.
{Related Error Numbers are:

10.3.7

16, 17)

Cyclic-Redundancy-Check-Character (CRCC) Exercise

This exercise determines that the drive develops correct CRCC's by,
first writing ten records with data patterns that are designed to
sequentially set each of the CRCC nine bits and, then,
comµaring
the
CRCC's read to the expected CRCC's.
{Related Error Numbers are:

10.3.8

18, 19, 20)

Record Creep Exercise

First, this exercise determines that the drive can write and read a
data pattern of all l's, and then all O's in a 1024-byte record.
The
sequence is:
1.

From BOT, write one 1024-byte record of all l's,
tape, and read the record.

rewind

the

Rewind the tape and, from BOT, write one 1024-bvte record
all O's.

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

The exercise then determines that the issuing of a backspace command
followed by a write command does not result in an erroneous data entry
{creep) either into the interrecord gap {IRG) or bevond the IRG
into
the record that precedes the record sought.
The sequence is:
1.

From BOT, write two 1024-byte records:
l's, the second with all O's.

first

with

all

Repetitively, backspace the tape one record and
second record with an all-O's pattern 64 times.

write

the

Rewind the tape and read the first record to determine if the
record content {all l's) and byte count remain intact.

10-4

the

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC

From stop in the IRG, read the second record to determine
if
the byte count equals 1024.
A lesser count indicates a
probable loss of data due to the second record creepinq
into
and shortening the IRG.

(Related Error Numbers are:

10.3.9

21, 22, 23, 24, 25, 26, 27)

Skew Exercise

This exercise determines whether the drive has actual or potential
tape-skew problems by writing and
reading two
"worst case" data
patterns that are designed to accentuate data retrieval errors.
Errors may be caused by factors such as electrical-skew, bad-head, or
magnetized-head conditions.
The patterns consist of ten 1024-byte
records.
Data in both cases is read and checked ten times to expose
possible read-reduction problems.
(Related Error Numbers are:

10.3.10

28, 29, 30)

End-of-File (EOF) Exercise

This exercise determines that the drive properly writes and detects
the presence of an EOF character (octal 23).
The seauence is:
1.

Rewind the tape.

From BOT, write an EOF character and check that the
EOF bit in the status register sets as reauired.

Write two records,
each containing 1023 EOF characters
followed by an all-l's character;
then write an EOF.

Rewind the tape.

Read two records, each 1024 bytes long.
Determine that
the
EOF status register bit does set for the legitimate EOF
characters, but not for the EOF characters written
in the
.records as data.

(Related Error Numbers are:

10.3.11

drive's

31, 32, 33, 34, 35, 36)

Single-Record Positioning Exercise

This exercise determines that the drive properly positions tape
The seauence is:
response to forwardspace and backspace commands.
1.

Rewind the tape.

From BOT, write an EOF character and check that the
EOF bit in the status register sets as required.

Write 63 records, each with 16 all-l's bytes.

Until EOF character is detected, backspace tape two
and then forwardspace one record.

10-5

drive's

records,

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
5.

Report tape position by record count if
EOF-character
detection occurs before or after the 63rd backspace command.

(Related Error Numbers are:

10.3.12

37, 38, 39, 40)

Multiple-Record Positioning Exercise

This exercise determines that the drive properly positions the tape in
response to backspace and forwardspace commands that specify various
multiple-record skips.
The exercise uses the tape data formatted by
the Single-Record Positioning Exercise. The sequence is:
1.

Rewind the tape.

Read for EOF character.

Alternately, forwardspace and backspace "n"
records, where
"n"
is initialized at 63 and decremented by one for each
space command until "n" equals 0.

Backspace tape from point halted in step 3 until EOF
is
detected.
Report tape position by record count if EOF occurs
before or after its anticipated position (after 32 records if
step 3 does not fail).

(Related Error Numbers are:

10.3.13

41, 42, 43, 44)

Crosstalk Exercise

This exercise determines whether the drive has a crosstalk problem by
writing and reading two data patterns that are designed to accentuate
potential crosstalk. The first pattern consists of ten 1024-byte
records
in which each 1 bit has contiguous 0 bits.
The second
pattern, also of ten 1024-byte records,
complements the first by
having reversed bit states
(i.e.,
0 bits with contiguous 1 bits).
Each pattern is read and checked ten times to expose possible
read-reduction problems.
(Related

Erro~

10.3.14

Data-Reliability Exercise

Numbers are:

45, 46, 47)

This exercise determines the drive's data reliability bv writing
selected data patterns in 64 files (or in files from BOT to EOT in
service-mode), and then reading the files ten times each to expose
possible
read-reduction problems.
Each file consists of three
random-length records in the range of 16 to 1024 bytes,
and an EOF
record.
The least significant digit of the octal record number appearing in a
data-compare error message indicates the data pattern expected, as
follows.

10-6

""I

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
Pattern Indicator
·~

Pattern Ex:eected

Floating l's

Random number

Count pattern

The sequence .is:
1.

Write three variable-data records and an EOF record
plus LPC character).

Repeatedly, backspace and read the file ten times
EOF record on successive re-reads).

Continue until 64 files (or in service mode,
the
files from BOT to EOT) have been written and read.

(Related Error Numbers are:

10.3.15

(EOF mark

(ignore the
multiple

48, 49, 50, 51, 52)

Quick Total-Tape-Check Exercise

The customer-mode user initiates this independent exercise for a
fast
determination of a
tape's data-reliability from BOT to EOT.
The
exercise differs from service-mode execution of the data-reliability
exercise only in that one read of each file is made rather than the
ten reads designed to expose possible read-reduction problems.
Once
initiated,
the
"check" exercise runs to completion and terminates
diagnostic control.
All errors are reported as detected.
(Related Error Numbers are:

10.3.16

48, 49, 50)

1600-BPI Identification Burst (IDB) Exercise

This exercise determines that the drive writes
correctly for 1600 BPI, phase-encoded (PE) data.
1.

Rewind the tape and
issue
recording in the PE mode.

From BOT, write one 1024-byte record of all l's.
The IDR
Bit,
Bit 3 of the Drive Status Register (MTDS), should be
set, indicating that the 1600-BPI
identification burst was
written, as required.

Rewind the tape and, from BOT, write one 1024-byte record of
all
l's
in NRZI.
The IDB bit should not be set, indicating
that the IDB was erased.

Rewind the tape and, from BOT, read the previously written
800-bpi record as a 1600-BPI record.
The IDB bit should not
be set.

(Related Error Numbers are:

53, 54, 55)

10-7

command

and
reads
the IDB
The sequence is:
calling

for

data

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
10.4

ERROR MESSAGES

Fault conditions detected during the test sequence are reported at the
initiating terminal:
they are classified as eauipment errors or
data-compare errors.
Equipment errors are those conditions that
result
in the setting of the "error" bit, Bit 14 of the Drive Status
Register (MTDS).
Data-compare errors occur when the diaonostic finds
data other than the data expected in data-transfer operations.
Some
conditions may cause both an equipment error and a data-compare error.
The following representations illustrate the context of the various
error messages.
Table 10-1 lists the error numbers and their related
fault conditions.
Appendix B defines the register contents displayed
in the error messages.
Equipment error-message format:
TU16
ERROR NO.
n
RECORD NO.
BYTE COUNT
MTCSl
MTWC
MTBA
MTFC
MTCS2
MTDS
MTER
MTAS
MTCK
MTDB
MTMR
MTDT
MTSN
MTTC

UNIT NO.

Number (in octal and decimal)
Number (in octal and decimal)
Control and Status 1 Register contents
Word Count Register contents
Bus Address Register contents
Frame Count Register contents
Control and Status 2 Register contents
Drive Status Reqister contents
Error Register contents
Attention Summary Register contents
Character Check Register contents
Data Buffer Register contents
Maintenance Register contents
Drive Type Register contents
Serial Number Register contents
Tape Control Register contents

Data-compare error-message format:
TU16
ERROR NO.
n
EXPECTED
RECEIVED
BYTE NO.
IN RECORD
RECORD NO.
BYTE COUNT

UNIT NO.

Data expected
Data received
Number (in octal and decimal)
Number (in octal and decimal)
Number (in octal and decimal)

Other error messages:
EOF NOT DETECTED AFTER WRITE EOF
EOF NOT DETECTED AFTER READ EOF
n RECORDS SKIPPED OVER
m RECORDS NOT BACKSPACED OVER
LPCC ERROR
CRCC ERROR
REREAD SAME DATA n TIMES BEFORE ERROR
ERROR NO.

x RECOVERED AFTER y RETRIES

ERROR NO.

a RECORD NO.

b RECOVERED AFTER c RETRIES
10-8

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC

Table 10-1
Error Conditions
Error Number
and Associated
Test Exercise

Fault Condition

BOT:
1

BOT not detected after tape rewind.

BOT not detected after backspace
while tape was at BOT.

was

issued

bit was set during
be caused by drive

write
going

IRG:
3

Illegal-command
function.
May
off line.

Record-length error bit was set durinq read
of ten short (16-byte)
records with stall
between read commands.

Variable-Length Record:
5

Error bit was set by a condition other than
parity
error while exercise was writing
variable-length records.

·6

Error bit was set by a condition other than
parity
error while exercise was reading
records with stall between read commands.

Record-Length:
7

Error bit was set by a condition other than
parity error while exercise was writinq a
512-byte record.

Byte-count register did not contain a value
of -512 (177000 octal) after the 512-bvte
record was read with the byte-count register
initialized to 1024.

Error bit did not set when 512-byte record
was read with byte-count register initialized
to 510.

Error bit was set by a condition other than
parity error when 512-byte record was read
with byte-count register initialized to 510.
(continued on next oage)

10-9

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC

Table 10-1 (Cont.)
Error Conditions
Error Number
and Associated
Test Exercise

Fault Condition

Lateral Parity:
11

Parity error expected by even-parity read of
odd-parity record did not set parity-error
bit.

Error bit was set by a condition other than
forced parity error caused by even-parity
read of odd-parity record.

Error bit was set while exercise was
a 512-byte record with even parity.

Parity error expected by odd-parity read of
even-parity record did not set parity-error
bit.

Error bit was set by a condition other than
forced parity error caused by odd-parity read
of even-parity record.

writing

LPCC:
16

Error bit was set while exercise was writing
the
LPCC-test
record
(an all-O's byte
followed by 1023 all-l's bytes).

Error bit was set by a condition other than
parity error during read of the LPCC-test
record (1024 bytes, an all-O's byte followed
by 1023 all-l's bytes).
LPCC received after read of the LPCC-test
record did not agree with the expected LPCC.

CRCC:
18

Error bit was set while exercise was
a CRCC-test record.

Error bit was set by a condition other than a
CRCC parity error while exercise was reading
a CRCC-test record.

CRCC received after
read of a CRCC-test
record did not agree with the expected CFCC
content.

writing

(continued on next page)

10-10

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
Table 10-1 {Cont.)
Error Conditions
Error Number
and Associated
Test Exercise

Fault Condition

Record Creep:

'-"'

Error bit was set while exercise was
readino
a 1024-byte record of all l's from BOT.

Data-compare error.
The 1024-bvte record did
not contain all l's.

Error bit was set while exercise was
readino
a 1024-byte record of all O's from BOT.

Data-compare error.
The 1024-byte record did
not contain all O's.

Error
bit was set
while
exercise
backspacing one
record and
rewriting
second 1024-byte record with all O's.

Data-compare error.
The 1024-byte record
from BOT did not contain all l's;
indicates
probable entry into the record while exercise
was writing the second record of all O's.

Read of second record did not
bytes before end-of-record.

transfer

was
the

1024

Skew:

Error bit was set while exercise was
a skew-test record.

writing

Error bit was set while exercise was
a skew-test record.

reading

Data-received while exercise
skew-test
record does not
expected test pattern.

was
readinq a
agree with.the

EOF:
31

Error bit was set by a condition other
than
"no EOF detected:
while exercise was writing
an EOF after BOT.

Error bit was set while exercise was writing
an EOF-test
record
{1023 EOF-pattern bytes
followed by an octal 77 byte).

First EOF, written previously after BOT,
not detected by a read from rewind.

was

(continued on next page)

10-11

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
Table 10-1 (Cont.)
Error Conditions
Error Number
and Associated
Test Exercise
EOF:

Fault Condition

(Cont.)

False EOF indication occurred while exercise
was reading EOF test record of EOF-pattern
bytes.

Error bit was set by condition other than
false
EOF indication while exercise was
reading the EOF test record of EOF-pattern
bytes.

EOF, written previously after EOF test file,
was not detected by a forwardspace-one-f ile
command from rewind.

Single-Record Positioning:
37

Error bit was set while exercise was writina
an EOF and 63 16-byte records of all l's.

Illegal-command bit was set during a command
sequence of backspace two records, and then
forwardspace one record.
Condition may be
caused by drive going offline.

EOF, written previously after
detected before it was expected.

BOT,

was

EOF should have occurred on backspace after
the 63rd command sequence:
backspace two
records, and then forwardspace one record
(net backspace equals one record for each
sequence).
The message
" ... n RECORDS SKIPPED
OVER"
indicates the number of records that were
erroneously skipped over during the backspace
sequence.
40

EOF, written previously after
detected after it was expected.

BOT,

was

EOF should have occurred on backspace after
the 63rd command seauence:
backspace two
records, and then forwardspace one record
(net backspace equals one record for each
sequence).
The message
" ••. n" RECORDS NOT BACKSPACED
OVER"
indicates the number of records that
remained to be backspaced over after
the
backspace sequence ended.
(continued on next page)

10-12

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC

Table 10-1 (Cont.)
Error Conditions
Error Number
and Associated
Test Exercise

Fault Condition

Multiple-Record Positioning:
41

EOF, written previously after
detected after rewind.

Illegal-command bit was set during a seauence
of record-space commands.
Conditions may be
caused by drive going offline.

EOF, written previously after
detected before it was expected.

BOT,

was

BOT,

not

was

EOF should have occurred
on
the
32nd
backspace-one-record command;
this premise
assumes that an earlier command seauence
positioned the tape properly at the midpoint
of the test-record seauence
(an EOF record
followed by 63 16-byte records).
The message " ... n RECORDS SKIPPED
OVER"
indicates the number of records that were
erroneously skipped over during the backspace
sequence.
44

EOF, written previously after
detected after it was expected.

BOT,

was

EOF should have occurred
on
the
32nd
backspace-one-record command;
this premise
assumes that an earlier command seauence
positioned the tape properly at the midpoint
of the test-record sequence
(an EOF record
followed by 63 16-byte records).
The message " .•. n RECORDS NOT BACKSPACED
OVER"
indicates the number of records that
remained to be backspaced over after
the
backspace sequence ended.
Crosstalk:

Error bit was set while exercise was writing
the crosstalk-test records
(ten records of
1024 bytes each).

Error bit was set while exercise was reading
the crosstalk-test records.
A "REREAD SAME
DATA •.. " message with a reread count greater
than
0
may
indicate
a read-reduction
condition.
Check for
dirty,
worn,
or
magnetized heads.
(continued on next page)

10-13

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
Table 10-1 (Cont.)
Error Conditions
Error Number
and Associated
Test Exercise
Crosstalk:

Fault Condition

(Cont.)

Data received while exercise was reading the
crosstalk-test records did not agree with the
expected test pattern.

Reliability:
48

Error bit was set while exercise was
a reliability-test file.

writing

Error bit was set while exercise was
a reliability-test file forward.

reading

Data received while exercise was readino a
reliability-test file forward does not agree
with the data expected.

Error bit was set while exercise was
a reliability-test file in reverse.

Data received from reading a reliability-test
file
in reverse does not agree with the data
expected.

readino

1600-BPI IDB:
53

IDB bit was not
writing a
record
mode.

IDB bit was set incorrectly while exercise
was writing a record from BOT in the 800-BPI
mode.

10.5

set while exercise was
from BOT in the 1600-BPI

IDB bit was set incorrectly while exercise
was reading an 800-BPI record from BOT in the
1600-BPI mode.

SERVICE-MODE INITIATION

Initiation of this mode demands a knowledge of
console-switch
selection
(see Section 10.6), test-parameter selection (see Section
10.7), interactive testing (see Sections 10.9 and 10.10),
and the
content of Appendix A.
Underlined text in this procedure indicates
required or expected user input.
Install "scratch" tape, write-enable ring installed, on tape drive
be tested.

10-14

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE MMn:

(n=uni t number)

On RSX-llM-PLUS systems only; logically mount the volume as foreign.
>MOUNT MMn:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
(or TU45)
START TU16 DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? MMn
**WARNING** MMn: RESIDENT DATA WILL BE DESTROYED **WARNING**
CONTINUE? SERVICE
(N or RETURN alone aborts the diagnostic)
TEST PARAMETERS (OCTAL)= nnnnnn
CONSOLE SWITCH FOR INTERVENTION (DECIMAL)= n
The selected test sequence commences upon RETURN after you have
responded to all inquiries, if any, that occur as a result of
test-parameters selection.

10.6

CONSOLE SWITCH FOR INTERVENTION

Service-mode initialization requires that you select a CPU console
switch (0-15) for intervention in the test sequence when, for example,
you desire to change test parameters. The facility to select ~ore
than one switch is useful only if more than one device is to be tested
concurrently~
that is, you can assign a uniaue switch to each
diagnostic.
For those systems without a CPU switch console or without the GET
SENSE SWITCHES directive, respond to the message "CONSOLE SWITCH ... "
with 0.

10.7

TEST PARAMETER SELECTION

that no tests
are to be performed.
The diagnostic
issues the test summary report and then
terminates.

The table also indicates those options that are automatically selected
for customer-mode execution.
The "bit" references in the option
descriptions refer to the bit positions of a test-parameters status
word that is monitored by the diagnostic.

10-15

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC

Table 10-2
Test-Parameter Options

.4""

Option Description

Selection
Code
(Octal)

In
Customer
Mode

STOP ON ERROR (Bit 15):

100000

40000

20000

10000

4000

2000

Test seauence waits up to 30
minutes before terminating. User
may abort stop by setting console
switch selected for intervention.
LOOP ON ERROR (Bit 14):
Test sequence
loops
on
the
failing
instruction
sequence.
User should intervene and select
new test parameters that exclude
this option.
INHIBIT ERROR MESSAGE PRINTOUT
(Bit 13):
Prevents
appearance
of
all
diagnostic error messages except
the test summary report
that
appears
at
the end of each
sequence pass.
BELL (Bit 12):
The terminal bell rings for
error detected.

each

(continued on next µage)

10-16

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC

Table 10-2 (Cont.)
Test-Parameter Options

Option Description
INTERACTIVE WRITE-READ SLICE
ADJUSTMENT (Bits 10 & 2):

Selection
Code
(Octal)

In
Customer
Mode

2004

Allows the service-mode user
to
select
a
writeor
a
read-repetitive
function
for
adjustment of the write or read
slice levels (see Section 10.10
for details).

""-"

Dl\TA-COMPA RE
(Bit 7) :

ERROR

RECOVERY

200

Default

100

Selectable

Yes

Tc= st

attempts
infinite
data-trans fer
retries to recover
f :rom a dat a-compare error.
The
dief aul t
l s:
at.tempt up to eight
data-trans fer retries to recover
from a dat a-compare error.

'-"

1600-BPI,
(Bit 6) :

PHASE-ENCODED

MODE

Enables th e writing of 1600-BPI
phase enc oded data records.
The
default is 800 BPI, NRZ mode.
LIMIT DATA -COMPARE ERROR MESSAGES
(Bit 5) :
Display an error message only for
the
first
data-compare error
condition
detected
during
a
specified
data transfer.
The
default 1s:
display an error
message
for
up
to
three
data-compare
error
conditions
detected
during retries of a
specified data transfer.
(continued on next page)

10-17

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
Table 10-2 (Cont.)
Test-Parameter Options
Selection
Code
(Octal)

Option Description

In
Customer
Mode

TEST SEQUENCE SELECTION
(Bits 1 & 0):
A)

Execute
the
following
exercises in the order shown:

Yes

BOT
IRG
Variable-length record positioning
Record Length
EOF
Single-record positioning
Multiple-record positioning
Lateral parity
LPCC
Record Creep
CRCC
Skew
Crosstalk
(See Section 10.3 for exercise
descriptions.)
B)

10.8

Execute the data-reliability
exercise for the entire tape
(from
BOT
to
EOT)
(see
Section 10.3.14).

""!

SERVICE-MODE INTERVENTION/RESTART/TERMINATION

You can intervene in (stop) the test seauence pass at any time by
changing from its current setting (0 to 1 or 1 to 0) the previously
selected CPU console switch.
Such action causes the diagnostic to
suspend testing and await response to the following message seauence.
TEST PARAMETERS

(OCTAL)=

Type an octal value
(other than 0)
to
select new test parameters (or re-enter the
old parameters, which are not saved at
intervention) , or
type 0 to terminate the diagnostic.

If new (or the old) parameters are entered, the following
displayed.
RESTART?

message

Type Y to abort the suspended test seauence
and
initiate the new seauence at the
beginning, or
type N to allow the suspended test seauence
to
run
to completion before the new
sequence commences.

10-18

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
For those systems not equipped with a CPU switch console or not
implE~mented with the GET SENSE SWITCHES directive, the user wishinq to
alter test parameters must first terminate the diagnostic by typing:
(cTRL/C)

MCR>ABOR'.1;'
and then reinitiate the diagnostic with new
parameters.
intervention and restart provisions are not accessible.

10.9

The

INTERACTIVE DRIVE-COMPATIBILITY TEST

This test determines the data-transfer compatibility of the system's
magnetic
tape
drives
by use of a
test-pattern tape.
After
test-parameter
selection,
the
test
is
initialized
in
the
test-tape-preparation or
read-check mode by your
response to the
ingu.i.ry
WHICH COMPATIBILITY MODE?(W=TEST TAPE PREP;

R=READ CHECK}

Type W to initiate preparation of the "scratch" tape on
selected drive as the test-pattern tape.
Type R to initiate read-testing of the
tape drive with the test tape mounted.

selected

the

magnetic

In the test-tape-preparation mode, the "scratch" tape is first written
with the test pattern.
Completion of the writing phase is indicated
by the message
COMPATIBILITY TAPE WRITTEN-VERIFYING TAPE
'rhe message
WRITE COMPATIBILITY TAPE FAILED
indicates that the test could not successfully complete preparation of
the test tape.
Error conditions are reported during the write-phase
by the message
TEST TAPE WRITE FAILED
followed by the current contents of the controller registers.
The tape is then read for agreement with the test pattern.
Successful
completion of the reading phase is indicated by the message
COMPATIBILITY TAPE VERIFIED
The message
READ COMPATIBILITY TAPE FAILED
indicates that the test could not successfully verify the contents of
the test tape.
Error conditions are reported during the read-phase by
the message
TEST TAPE READ FAILED
followed by the current contents of the controller registers.

10-19

TU16 OR TU45 MAGNETIC TAPE DIAGNOSTIC
In read-check mode, the test compares the data read with the expected
data.
Differences are noted as data-compare errors.
Completion of
the test is indicated by the message

COMPATIBILITY TAPE VERIFIED

10.10

INTERACTIVE WRITE-READ SLICE ADJUSTMENT

SLICE ADJUSTMENT?(W=WRITE;R=READ}
Type W to initiate the write function.
Type R to initiate the read function.
The write function repetitively writes from BOT three 1024-byte •
records with all l's until you intervene with the selected console
switch or abort the diagnostic by MCR command.
The read function first writes from BOT three 1024-byte records with
all l's, and then repetitively reads these records until you intervene
with the selected console switch or abort the diagnostic by MCR
command.

10-20

CHAPTER 11
TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC

...... CUSTOMER-MODE INITIATION ...................
(Underlined text indicates reauired or
Chapter 2 for additional infor~ation.)
Install "scratch" tape, with
drive to be tested.

expected

user

ring

installed,

write-enable

inputr
on

see
tape

On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE MTn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT MTn:/FOR
On both RSX-llM and RSX-11-PLUS systems, proceed as follows.
>RUN $TU10

(or TS03)

START TUlO DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? MTn
**WARNING** MTn:
RESIDENT DATA WILL BE DESTROYED **WARNING**
CONTINUE? Y
(N or RETURN alone aborts the diagnostic)
QUICK TOTAL-TAPE CHECK? (Y tests tape's reliability and exits)
(N initiates customer-mode test seauence)
Diagnostic runs to completion in
system.
To exit sooner, type:

minutes

for

lightly

loaded

§:!9
MCR>ABORT

11.1

TEST SUMMARY REPORT

Upon completion of each diagnostic test sequence, the followino report
.Ls displayed.
TUlO UNIT NO.
n
(n=unit number)
PASS COUNT=
TOTAL ERRORS ENCOUNTERED=
TOTAL FUNCTIONS ISSUED=
TOTAL WORDS TRANSFERRED=
END OF TUlO DIAGNOSTIC - TIME OF DAY=hour:minute:second
'"Pass count" and "totals" are
(initiated in service mode only).

cumulative

11-1

for

multipass

testinq

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
11.2

TAPE DRIVE CHARACTERISTICS
TS03

Channels (tracks)

7 or 9

Recording density, bits
per inch (BPI)

200, 556, or 800
for 7-channel;
800
for 9-channel.

800

Tape speed, inches per
second

45 normal
150 rewind

15 normal
120 rewind

Recording

NRZI

Interrecord Gap
(IRGY

0.5 in.
minimum
0.65 in. nominal

End-of-File
(EOF) Character

17 (octal) for
7-channel;
23
(octal) for 9channel

23 (octal)

Figures 11-1, 11-2, and 11-3 illustrate the relationship between tape
characters and memory bytes,
the 9-channel tape format, and the
7-channel tape format.
The correlation between PDP-11 memory bits and
follows:
7-Channel TaEe

9-Channel Tape

Bit

Channel

Bit

Channel

15
14
13
12
11
10

0
0
B

15
14
13
12
11
10
9
8
7
6
5

7
6
5
3
9
1
8
2
7
6
5
3
9
1
8
2

9
8

7
6
5
4
3
2
1
0
Channel

8
4
2
1
0
0
B
A

8
4
2
1

3
2
1
0

c is parity Channel 4 is parity

11-2

tape

channels

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC

[---__;_c__-.---:------A_
15

_ _ ; ,_:;_, ,

9 TRACK TAPEFULL 8-BIT BYTES ARE RECORDED ON TAPE.

[IJ---..-----,---,----A-·=i
15

7 TRACK TAPEONLY 6 BITS OF EACH 8-BIT BYTE ARE RECORDED
ON TAPE.BITS 6,7,14,AND 15 ARE NOT USED.
15

0 7

[~D-~~-~~B~-A~=i

7 TRACK TAPE (CORE DUMP)FULL 8-BIT BYTES ARE RECORDED ON TAPE
BY USING TWO 4·-BIT CHARACTERS

READ/WRITE
HEAD
TAPE MOTION-

Relationship Between Tape Characters and Memory Bytes

Figure 11-1

r-------,

l.~~!_T!'~J

mr-,

CHARACTER

O:E

9
8

1
1

7
6

1
1

5
TY)4
3
2

1
1
1
1

1 1
1 I
1 1
1 -1

WT
1

r- -+--BOT GAP

DATA
3 -CHARACTER
MIN.

CHARACTER

~YTE

-+ +

Figure 11-2

3
CHARACTER
PERIODS

9-Channel Tape Format

11-3

3
t-INTERRECORD+ NEXT
CHARACTER
GAP
DATA
PERIODS
(IRG)
RECORD

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC

FORWARD

TAPE
MOTION
ONE BYTE DURING
CORE DUMP MODE

TAPE CHANNELS

(PARITY) C
B
A
8
4

ClfoJ.=-.fo~"'J

~
BOT GAP

--+

, , , , , , 1 ,

DATA
3- CHARACTER
·
MIN.

______

....._

3
fNTERRECOR~
CHARACTER
GAP
N~XETCa°RA;A
PERIODS
(IRG)

a. 7-CHANNEL DATA FOR MAT

CHARACTER

U~~SEla°R'iiA
IN BLOCK

-•r•f-----

EXTENDED IRG

----••t.

b. EOF

Figure 11-3

11.3

RECORD

B~il\Nd~G

EOF - + - I R G - + RECORD
DATA BLOCK
3 BLANK
CHARACTER
PERIODS

7-Channel Tape Format

DIAGNOSTIC DESCRIPTION

The TU10/TS03 diagnostic tests the ability of the selected tape
to:
1.

Position its resident tape correctly,

Write and read data correctly, and

Check for parity errors.

The exercises described
uninterrupted sequence for
following each description
conditions;
refer
to
significance.

11.3.1

drive

hereafter are executed in
a
one-pass
customer mode.
The "Related Error Numbers"
appear in error messages for detected fault
Section 11.4 and Table 11-1 for
their

Beginning-of-Tape (BOT) Exercise

First, this exercise determines that the tape positions at BOT after a
rewind command,
and then that the tape remains at BOT although a
backspace (space-reverse) command is issued.
(Related Error Numbers are:

1, 2)

11-4

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
11.3.2

Interrecord-Gap

(I~G)

Exercise

This exercise determines that IRG's produced by the drive are of
adequate length for tape motion to decrease from normal speed to stop
(shutdown in an IRG) and to increase to normal speed,
in either
direction,
before an IRG-boundary reaches the write-read heads.
The
sequ1~nce is:
1.

Rewind the tape.

Write ten 16-byte records, all l's, and rewind tape.

Read each record and verify its character count, waitinq
after each read for tape motion to stop before issuing the
next read-one-record command.

(Related Error Numbers are:

11.3.3

3, 4)

Variable-Length Record-Positioning Exercise

This exercise determines that the drive properly responds to commands
specifying the writing and reading of records of varying lengths.
The
sequence is:
1.

Rewind the tape.

From BOT, write 63 all-l's records decreasing in length by
16-byte decrements from 1024 bytes, initially, to 16 bytes~
then writE~ 63 all-l's records increasing in length by 16-bvte
increments from 16 bytes to 1024 bytes.

Rewind the tape.

Read the records by read-one-record commands,
allowinq tape
motion to stop before issuing the next read.
Determine that
record lengths agree with those written as specified above.

(Related Error Numbers are:

11.3.4

5, 6)

Record-Length Exercise

11.3.5

7, 8, 9, 10)

Lateral-Parity Exercise

This exercise determines that the drive responds properly to apparent
lateral-parity errors, which are forced by writing one 512-byte
all-l's record with odd parity and then reading it as even parity.
The reverse condition is checked by writing the record as even paritv
and reading it as odd parity. The data pattern is not checked for
correct content.
(Related Error Numbers are:

11, 12, 13, 14, 15)

11-5

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
11.3.6

Longitudinal-Parity-Check-Character (LPCC) Exercise

This exercise determines that the drive's LPCC facility
functions
properly.
The exercise writes one 1024-byte record with a data
pattern (an all-O's byte followed by 1023 all-l's bytes)
that has a
predicted LPCC.
It then checks for the presence of the predicted
LPCC.
(Related Error Numbers are:

11.3.7

16, 17)

Cyclic-Redundancy-Check-Character (CRCC) Exercise

This exercise checks 9-track (channel)
tape only.
Detection of a
7·-track tape on the selected drive causes the exercise to be skipped.
The exercise determines that the drive develops correct CRCC's by,
first,
writing ten records with data patterns that are designed to
sequentially set each of the CRCC nine bits and, then,
comparing the
CRCC's read to the expected CRCC's.·
(Related Error Numbers are:

11.3.8

18, 19, 20)

Record Creep Exercise

First, this exercise determines that the drive can write and read a
data pattern of all l's, and then all O's in a 1024-byte record.
The
SE~quence is:
1.

From.BOT, write one 1024-byte record of all l's,
tape, and read the record.

rewind

the

Rewind the tape and, from BOT, write one 1024-byte record
all O's.

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

The exercise then determines that the issuing of a backspace command
followed by a write command does not result in a erroneous data entry
(creep) either into the interrecord gap (IRG) or beyond the IRG
into
the record that precedes the record sought.
The sequence is:
1.

From BOT, write two 1024-byte records:
l's, the second with all O's.

first

with

all

Repetitively backspace the tape one record and
second record with all-O's pattern, 64 times.

write

the

Rewind the tape and read the first record to determine if the
record content (all l's) and byte count remain intact.

From stop in the IRG, read the second record to determine if
the byte count equals 1024.
A lesser count indicates
probable loss of data due to the second record creeping into
and shortening the IRG.

(Related Error Numbers are:

the

21, 22, 23, 24, 25, 26, 27)

11-6

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
11.3.9

Skew Exercise

This exercise determines whether the drive has actual or potential
tape~skew
problems by writing and reading two "worst case" data
patterns that are designed to accentuate data retrieval errors.
Errors may be caused by factors such as electrical-skew, bad-head, or
magnetized-head conditions.
The patterns consist of ten 1024-byte
records.
Data in both cases is read and checked ten times to expose
possible read-reduction problems.
(Related Error Numbers are:

11.3.10

28, 29, 30)

End-of-File (EOF) Exercise

This exercise determines that the drive properly writes and detects
the presence of an EOF character (octal 17 for 7-track, octal 23 for
9-track). The sequence is:
1.

Rewind the tape.

From BOT, write an EOF character and check that the
EOF bit in the status register sets as required.

Write two records,
each containing 1023 EOF characters
followed by an all-l's character:
then write an EOF.

Rewind the tape.

Read two records, each 1024 bytes long.
Determine that the
EOF status register bit does set for the legitimate EOF
characters, but not for the EOF characters written in the
records as data.

'--1'

(Related Error Numbers are:

11.3.11

drive's

31, 32, 33, 34, 35, 36)

Single-Record Positioning Exercise

This exercise determines that the drive properly positions tape
response to forwardspace and backspace commands. The sequence is:

Rewind the tape.

From BOT, write an EOF character and check that the
EOF bit in the status register sets as reauired.

Write 63 records, each with 16 all-l's bytes.

Until EOF character is detected, backspace tape two
and then forwardspace one record.

Report tape position by record count if
EOF-character
detection occurs before or after the 63rd backspace command.

(Related Error Numbers are:

37, 38, 39, 40)

11-7

drive's

records,

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
11.3.12

Multiple-Record Positioning Exercise

~~his

exercise determines that the drive properly positions the tape in
response to backspace and forwardspace commands that specify various
multiple-record skips.
The exercise uses the tape data formatted
by
the Single-Record Positioning Exercise.
The seauence is:
1.

Rewind the tape.

Read for EOF character.

Alternately, forwardspace and backspace "n"
records,
where
"n"
is
initialized at 63 and decremented by one for each
space command until "n" equals O.

Backspace tape from point halted
in step 3 until EOF is
detected.
Report tape position by record count if EOF occurs
before or after its anticipated position (after 32 records if
step 3 does not fail).

(Related Error Numbers are:

11.3.13

41, 42, 43, 44)

Crosstalk Exercise

This exercise determines whether the drive has a crosstalk problem by
writing and reading two data patterns that are designed to. accentuate
potential crosstalk.
The first pattern consists of ten 1024-byte
records
in which each 1 bit has contiguous 0 bits.
The second
pattern, also of ten 1024-byte records,
complements the first
by
having reversed bit states
(i.e.,
0 bits with contiguous 1 bits).
Each pattern is read and checked ten times to expose possible
read-reduction problems.
(Related Error Numbers are:

11.3.14

45, 46, 47)

Data-Reliability Exercise

This exercise determines the drive's data reliability by writing
selected data patterns in 64 files (or in files from BOT to EOT in
service-mode), and then reading the files ten times each
to expose
possible
read-reduction problems.
Each file consists of three
random-length records in the range of 16 or 1024 bytes,
and an EOF
record.
The least significant digit of the octal record number appearing in a
data-compare error message
indicates the data pattern expected, as
follows.
Pattern Indicator

~.'he

Pattern Ex2ected

Floating l's

Random number

Count pattern

sequence is:
1.

Write three varible-data records and an EOF record
plus LPC character).

11-8

(EOF

mark

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC

...

"'-"'

Repeatedly, backspace and read the file ten times (ignore the
EOF record on successive re-reads).

Continue until 64 files (or ln service mode,
the
files from BOT to EOT) have been written and read.

multicle

For s1=ven-track tape, the exercise implements "core dump" JT1ode
(i.e.,
each memory byte ls written or read as two consecutive 4-bit tape
characters).
(Related Error Numbers are:

11.3.15

48, 49, 50)

Quick Total-Tape-Check Exercise

The customer-mode user initiates this independent exercise for a
fast
determination of a
tape's data
reliability from BOT to EOT.
The
exercise differs from service-mode execution of the data-reliability
exercise only in that one read of each file is made rather than the
ten reads designed to expose possible read-reduction problems.
Once
initiated,
the "check" exercise runs to completion and terminates
diagnostic control.
All errors are reported as detected.
(Related Error Numbers are:

11.4

48, 49, 50)

ERROR MESSAGES

Fault conditions detected during the test sequence are reported at the
initiating terminal~.
they are classified as eauipment errors or
data-compare errors.
Equipment errors are those conditions that
result
in the setting of the "error" bit, Bit 15 of the Comlfland
Register (MTC).
Data-compare errors occur when the diagnostic finds
data other than the data expected in data-transfer operations.
Some
conditions may cause both an equipment error and a data-compare error.
The following representations illustrate the context of the various
error messages.
Table 11-1 lists the error numbers and their related
fault conditions.
Appendix B defines the register contents displayed
in the error messages.
Equipment error-message format:
TUlO
ERROR NO.
n
RECORD NO.
BYTE COUNT
MTS
MTC
MTBRC
MTCMA
MTD
MTRD

UNIT NO.

Number (in octal and decimal)
Number (in octal and decimal)
Status Register contents
Command Register contents
Byte Record Count Register contents
Current Memory Address Register contents
Data Buffer Register contents
Read Lines Register contents

11-9

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
Data-compare error-message format:
TUlO
UNIT NO. m
ERROR NO. n
EXPECTED
Data expected
RECEIVED
Data received
BYTE NO.
IN RECORD
Number (in octal and decimal)
RECORD NO.
Number (in octal and decimal)
BYTE COUNT
Number (in octal and decimal)
Other error messages:
EOF NOT DETECTED AFTER WRITE EOF
EOF NOT DETECTED AFTER READ EOF
n RECORDS SKIPPED OVER
m RECORDS NOT BACKSPACED OVER
LPCC ERROR
CRCC ERROR
REREAD SAME DATA n TIMES BEFORE ERROR
ERROR NO.

x RECOVERED AFTER y RETRIES

ERROR NO.

a RECORD NO.

b RECOVERED AFTER c RETRIES

Table 11-1
Error Conditions
Error Number
and Associated
Test Exercise

Fault Condition

BOT:
1

BOT not detected after tape rewind.

BOT not detected after backspace
issued while tape was at BOT.

was

IRG:
3

Illegal-command bit was set during write
May be caused by drive goinq
function.
off line.

Record-length error bit was set during
read of ten short ( 16-byte) records with
stall between read commands.
(continued on next page)

11-10

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
Table 11-1 (Cont.)
Error Conditions
Error Number
and Associated
Test Exercise

Fault Condition

Variable-Length Record:
5

Error bit was set by a condition other
than parity error while exercise was
writing variable-length records.

Error bit was set by a condition other
than parity error while exercise was
reading records with stall between read
commands.

Record-Length:

'-""'

Error bit was set by a condition other
than parity error while exercise was
writing a 512-byte record.

Byte-count register did not contain a
value of -512
(177000 octal) after the
512-byte record was
read
with
the
byte-count register initialized to 1024.

Record-length error bit (MTS bit 9)
did
not set when 512-byte record was read
with byte-count register
initialized to
510.

Error bit was set by a condition other
than
parity
error
or
expected
record-length error when 512-bvte record
was
read
with
byte-count
register
initialized to 510.

Lateral Parity:
11

Parity error expected by even-parity read
of
odd-parity
record
did
not set
parity-error and error bits.

Error bit was set by a condition other
than
forced
parity error caused by
even-parity read of odd-parity record.

Error bit was set while exercise was
writing
a
512-byte record with even
parity.

Parity error expected by odd-parity read
of
even-parity
record
did not set
parity-error and error bits.
(continued on next page)

11-11

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
Table 11-1 (Cont.)
Error Conditions
Error Number
and Associated
Test.Exercise
Lateral Parity:

Fault Condition
(Cont.)
Error bit was set by a condition other
than
forced
parity error caused by
odd-parity read.of even-parity record.

LPCC:

Error bit was set while exercise was
writing the LPCC-test record (an all-O's
byte followed by 1023 all-l's bytes).

Error bit was set by a condition other
than parity error during read of the
LPCC-test record (1024 bytes, an all-O's
byte followed by 1023 all-l's bytes).
LPCC received after read of the LPCC-test
record did not agree with the expected
LPCC.

CRCC:

Error bit was set while exercise
writing a CRCC-test record.

Error bit was set by a condition other
than a CRCC parity error while exercise
was reading a CRCC-test record.

CRCC received after read of a CRCC-test
record did not agree with the expected
CRCC content.

was

"""·

Record Creep:
21

Error bit was set while exercise was
reading a 1024-byte record of all l's
from BOT.

Data-compare error.
The 1024-byte record
did not contain all l's.

Error bit was set while exercise was
reading .a 1024-byte record of all O's
from BOT.
(continued on next paqe)

11-12

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
Table 11-1 (Cont.)
Error Conditions
Error Number
and Associated
Test Exercise
R.ecord Creep:

Fault Condition
(Cont.)

Data-compare error.
The 1024-byte record
did not contain all O's.

Error bit was set while exercise was
backspacing one record and rewriting the
second 1024-byte record with all O's.

Data-compare error.
The 1024-byte record
from
BOT
did not contain all
l's~
indicates probable entry into the record
while exercise was writing the second
record of all O's.

Read of second record did not
1024 bytes before end-of-record.

transfer

Skew:
28

Error bit was set while exercise
writing a skew test record.

was

Error bit was set while exercise
reading a skew test record.

was

Data received while exercise was
readino
a
skew-test record does not agree with
the expected test pattern.

JEOF:
31

Error bit was set by a condition other
than "no EOF detected" while exercise was
writing an EOF after BOT.

Error bit was set while exercise was
writing
an
EOF-test
record
(1023
EOF-pattern bytes followed by an octal 77
byte).

First EOF, written previously after BOT,
was not detected by a read from rewind.

False EOF
indication
occurred
while
exercise was
reading EOF test record of
EOF-pattern bytes.

Error bit was set by condition other than
false EOF
indication while exercise was
reading
the
EOF-test
record
of
EOF-pattern bytes.
(continued on next oage)

11-13

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
Table 11-1 (Cont.)
Error Conditions
Error Number
and Associated
Test Exercise
EOF:
36

Fault Condition

(Cont.)
EOF, written previously after EOF test
by
a
file,
was
not
detected
from
forwardspace-one-f ile
command
rewind.

Single-Record Positioning:
37

Error bit was set while exercise was
writing an EOF and 63 16-byte records of
all l's.

Illegal-command bit was set durina a
command
sequence
of
backspa~e
two
records,
and
then
forwardspace
one
record.
Condition may be caused by drive
going offline.

EOF, written previously after BOT,
detected before it was expected.

was

EOF should have occurred on backspace
after
the
63rd
command
seauence:
and
then
backspace
two
records,
{net backspace
forwardspace one record
equals one record for each seauence).

The message " .•. n RECORDS SKIPPED OVER"
indicates the number of records that were
erroneously skipped over
during
the
backspace sequence.
40

EOF, written previously after BOT,
detected after it was expected.

was

EOF should have occurred on backspace
after
the
63rd
command
seauence:
backspace
two
records,
and
then
forwardspace one record
{net backspace
equals one record for each seauence).
The message " .•. n RECORDS NOT BACKSPACED
OVER"
indicates the number of records
that remained to be backspaced over after
the backspace seauence ended.
Multiple-Record Positioning:
41

EOF, written previously after
not detected after rewind.

BOT,

was

(continued on next oage)

11-14

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
Table 11-1 (Cont.)
Error Conditions
Error Number
and Associated
T'est Exercise

Fault Condition

Multiple-Record Positioning:

(Cont.)

Illegal-command bit was set during a
sequence
of
record-space •commands.
Condition may be caused by drive going
off line.

EOF, written previously after BOT,
detected before it was expected.

was

EOF should have occurred on the 32nd
backspace-one-record
command:
this
premise assumes that an earlier
command
sequence positioned the tape properly at
the midpoint of the test-record seauence
(an EOF record
followed
by 63 16-byte
records).
The message " ..• n RECORDS SKIPPED OVER"
indicates the number of records that were
erroneously skipped over
during
the
backspace sequence.
44

EOF, written previously after BOT,
detected after it was expected.

was

EOF should have occurred on the 32nd
backspace-one-record
command:
this
premise assumes that an earlier command
sequence positioned the tape properly at
the midpoint of the test-record seauence
(an EOF record followed
by 63 16-byte
records).
The message " .•• n RECORDS NOT BACKSPACED
OVER"
indicates the number of records
that remained to be backspaced over after
the backspace seauence ended.
Crosstalk:
45

Error bit was set while exercise
writing the crosstalk-test records
records of 1024 bytes each}.

Error bit was set while exercise was
reading the crosstalk-test records.
A
"REREAD SAME DATA ••• " message with a
reread count greater than O may indicate
a read-reduction condition.
Check
for
dirty, worn, or magnetized heads.

was
(ten

(continued on next page)

11-15

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
Table 11-1 (Cont.)
Error Conditions
Error Number
and Associated
Test Exercise
Crosstalk:

Fault Condition

(Cont.)
Data received while exercise was readino
the crosstalk-test records did not agree
with the expected test pattern.

Reliability:

11.5

Error bit was set while exercise
writing a reliability-test file.

was

Error bit was set while exercise
reading a reliability-test file.

was

Data received while exercise was reading
a
reliability-test file does not aqree
with the data expected.

SERVICE-MODE INITIATION

Initiation of this mode demands a knowledge of
console-switch
selection
(see Section 11.6), test-parameter selection (see Section
11.7), interactive testing (see Sections 11.9 and 11.10),
and the
content of Appendix A.
Underlined text in this procedure indicates
required or expected user input.
Install "scratch" tape, with
drive to be tested.

write-enable

ring

installed,

tape

On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE MTn:

(n=unit number)

On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT MTn:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $TU10

(or TS03)

START TUlO DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? MTn
**WARNING** MTn:

RESIDENT DATA WILL BE DESTROYED **WARNING**

CONTINUE? SERVICE
(N or RETURN alone aborts the diagnostic)
TEST PARAMETERS (OCTAL)= nnnnnn
CONSOLE SWITCH FOR INTERVENTION (DECIMAL)=~
The selected test sequence commences upon RETURN after you have
responded to all
inquiries,
if any,
that occur as a result of
test-parameters selection.
11-16

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC

11.6

CONSOLE SWITCH FOR INTERVENTION

Service-mode initialization requires that you select a CPU console
switch (0-15) for intervention in the test sequence when, for example,
you desire to change test parameters.
The f~cility to select more
than one switch is useful only if more than one device is to be tested
concurrently;
that is,
you can assign a uniaue switch to each
diagnostic.
For those systems without a CPU switch console or without the GET
SENSE SWITCHES directive, respond to the message "CONSOLE SWITCH ... "
with 0.

11.7

TEST PARAMETERS SELECTION

Customer mode allows only a fixed sequence of the diagnostic's tests.
Service mode,
however,
permits customization of the test content
through the test-parameters facility.
Table 11-2 describes the
various options available to you as a service-mode user.
You select
options by logically ORing their related octal codes to form a 6-digit
numb•?r
(leading zeros need not be expressed) for entry in response to
TEST PARAMETERS (OCTAL}=.
NOTE
A response of 0 implies that no tests
are to be performed.
The diagnostic
issues the test summary report and then
terminates.
The table also indicates those ·options that are automatically selected
for
customer-mode execution.
The "bit"
references
in the option
descriptions refer to the bit positions of a test-parameters status
word that is monitored by the diagnostic.
Table 11-2
Test-Parameter Options

Option Desc ription

Selection
Code
(Octal)

In
Customer
Mode

STOP ON ERR OR (Bit 15) :

100000

Te:st segue nee waits up to 30
minutes bef ore terminating.
User
may abort s top by setting console
switch sele cted for intervention.
(continued on next page)

11-17

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
Table 11-2 (Cont.)
Test-Parameter Options

Option Description
LOOP ON ERROR (Bit 14):

Selection
Code
(Octal)

In
Customer
Mode

40000

20000

10000

4000

2000

2004

Test sequence
loops
on
the
failing
instruction
sequence.
User should intervene and select
new test parameters that exclude
this option.
INHIBIT ERROR MESSAGE PRINTOUT (Bit 13):
Prevents
appearance
of
all
diagnostic error messages except
the test summary report
that
appears
at
the end of each
sequence pass.
BELL (Bit 12):
The terminal bell rings for
error detected.

each

MULTIPASS EXECUTION (Bit 11):
Test sequence repeats until user
intervenes.
The updated test
summary report is displayed at
the end of each pass.
INTERACTIVE DRIVE-COMPATIBILITY TEST
(Bits 10 & 2):
Allows the service-mode user to
determine the compatibility of
system tape drives
(see Section
11.9
for
details).
The
requirement that Bit 2 not be set
inhibits selection of this option
with
the
write-read
slice
adjustment test.
INTERACTIVE WRITE-READ SLICE ADJUSTMENT
(Bits 10 & 2):
Allows the service-mode user to
select
a
writeor
a
read-repetitive
function
for
adjustment of the write or read
slice levels (see Section 11.10
for details) .

(continued on next oage)

11-18

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
Table 11-2 (Cont.)
Test-Parameter Options

Option Description
DA~~A-COMPARE

ERROR

RECOVERY

Selection
Code
(Octal)

In
Customer
Mode

200

Default

Yes

{Bit 7):
Test
attempts
infinite
data-transfer retries to recover
from a data-compare error.
The
default is:
attempt up to eight
data-transfer retries to recover
from a data-compare error.
LIMIT DATA-COMPARE ERROR MESSAGES (Bit 5):
Display an error message only for
the
first
data-compare error
condition
detected
during
a
specified
data transfer.
The
default is:
display an error
message
for
up
to
three
data-compare
error
conditions
detected
during retries of a
specified data transfer.
TEST SEQUENCE SELECTION (Bits 1 & 0):
A)

Execute
the
following
exercises in the order shown:
BOT
!HG
Variable-length record positioning
Record Length
EOF
Single-record positioning
Multiple-record positioning
Lateral parity
LPCC
Record Creep
CRCC (9-track tape only)
Skew
Crosstalk
(See
Section
11.3
exercise descriptions.)

for

Execute the data-reliability
exercise for the entire tape
(from
BOT
to
EOT)
(see
Section 11.3.14).

11-19

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
11.8

SERVICE-MODE INTERVENTION/RESTART/TERMINATION

You can intervene in (stop) the test sequence pass at any time by
changing from its current setting (0 to 1 or 1 to 0) the previously
selected CPU console switch.
Such action causes the diagnostic to
suspend testing and await response to the following message seauence.
TEST PARAMETERS (OCTAL)=

Type an octal value
(other than 0)
to
select new test parameters (or re-enter the
old parameters, which are not saved at
intervention) , or
type 0 to terminate the diagnostic.

If new (or the old) parameters are entered, the following
displayed.
RESTART?

message

Type Y to abort the suspended test seauence
and
initiate the new sequence at the
beginning, or
type N to allow the suspended test sequence
to
run
to completion before the new
sequence commences.

For those systems not equipped with a CPU switch console or not
implemented with the GET SENSE SWITCHES directive, the user wishinq to
alter test parameters must f i~st terminate the diagnostic by typing:
(CTRL/C)

MCR>ABORT
and then reinitiate the diagnostic with new
parameters.
intervention and restart provisions are not accessible.

11.9

The

INTERACTIVE DRIVE-COMPATIBILITY TEST

This test determines the data-transfer compatibility of the system's
magnetic
tape
drives
by use of a test-pattern tape.
After
test-parameter
selection,
the
test
is
initialized
in
the
test-tape-preparation or read-check mode by your response to the
inquiry
WHICH COMPATIBILITY MODE?(W=TEST TAPE PREP;

R=READ CHECK)

Type W to initiate preparation of the "scratch" tape on
selected drive as the test-pattern tape.
Type R to initiate read-testing of the
tape drive with the test tape mounted.

selected

the

magnetic

In the test-tape-preparation mode, the "scratch" tape is first written
with the test pattern.
Completion of the writing phase is indicated
by the message
COMPATIBILITY TAPE WRITTEN-VERIFYING TAPE

11-20

I 1

TUlO OR TS03 MAGNETIC TAPE DIAGNOSTIC
The message
WRITE COMPATIBILITY TAPE FAILED
indicates that the test could not successfully complete preparation of
the test tape.
Error conditions are reported during the write-phase
by the message
TEST TAPE WRITE FAILED
followed by the current contents of the controller registers.
The tape is then read for agreement with the test pattern.
Successful
completion of the reading phase is indicated by the message
COMPATIBILITY TAPE VERIFIED
The message
READ COMPATIBILITY TAPE FAILED
indicates that the test could not successfully verify the contents of
the test tape.
Error conditions are reported during the read-phase by
the message
TEST TAPE READ FAILED
followed by the current contents of the controller registers.
In read-check mode, the test compares the data read with the data
Completion
expected.
Differences are noted as data-compare errors.
of the test is indicated by the message
COMPATIBILITY TAPE VERIFIED
For 7-track tape, the test implements core-dump mode
(that is,
memory byte ·is written or read as two consecutive 4-bit
characters).

11.10

each
tape

INTERACTIVE WRITE-READ SLICE ADJUSTMENT

This test provides either a write-repetitive or a
read-repetitive
function for adjustment or checking of the drive's write or read slice
levels.
After test-parameter selection, the test is initialized by
your response to the inquiry
SLICE ADJUSTMENT?(W=WRITE;R=READ)
Type W to initiate the write function.
Type R to initiate the read function.
The write function repetitively writes from BOT three 1024-byte
records with all l's until you intervene with the selected console
switch or abort the diagnostic by MCR command.
The read function first writes from BOT three 1024-byte records with
all l's, and then repetitively reads these records until you intervene
with the selected console switch or abort the diagnostic by MCR
command.

11-21

CHAPTER 12
TERMINAL OR LINE PRINTER DIAGNOSTIC

.--•-CUSTOMER-MODE INITIATION-------.
(Underlined text indicates required or
Chapter 2 for additional information.}
>ALLOCATE TTn:
>RUN $TERM

expected

user

input~

see

(or LPn, n=unit number}

START TERMINAL DIAGNOSTIC - TIME OF DAY=hour:minute:second
DEVICE? TTn
CONTINUE? X
HARD COPY TERMINAL?
132 COLUMN TEST?

(N or RETURN alone aborts the diagnostic}
(N tests device as video display}
(N sets 72 columns}

Diagnostic runs to completion in 3 minutes.

To exit sooner, type:

(cTRL/C)

MCR>ABORT

12.1

END-OF-TEST INDICATION

Upon completion of the diagnostic
displayed.

test

seouence,

the

followinq

END OF TERMINAL DIAGNOSTIC - TIME OF DAY=hour:minute:second

12.2

DIAGNOSTIC DESCRIPTION

The diagnostic tests the ability of the selected terminal device to
print
(display)
the alphanumeric and special-character sets and to
perform all positioning functions properly. The following describes
some special situations.
NOTE
If an LA30S or VT05B terminal has
not been identified to the system
by the MCR command SET/LA30S=TTn:
or
SET/VT05=TTn:,
respectively,
test output at the terminal may be
garbled.

12-1

TERMINAL OR LINE PRINTER DIAGNOSTIC
80-Column Terminals:
The capability to exercise the full 80 columns is an option in
Service Mode.
Customer Mode exercises all functions with the
exception of positioning to and from the last 8 columns.
Line Printers:
A line printer
is exercised as if it were a video-display
terminal.
Page-formatting functions are not exercised. Note
that the test output is not spooled.
Special-Purpose Terminals:
Special-purpose terminals, such as a badge reader, for
the most
part,
should not be e~ercised by the diagnostic.
If required,
the Interactive-Pattern Test option of Service Mode can be used
to accept data and display it.
Test the Initiating Terminal:
The diagnostic can be used to test the initiating
Unsolicited input during testing is directed to MCR.

terminal.

Special-Character Sets:
and
This diagnostic exercises the alphanumeric
characters
If a
special-character set illustrated in Section 12.2.7.
is
terminal has an equivalent character,
the
eauivalent
displayed.
Non-equivalent characters are not exercised.
Upper-Case Terminals:
An upper-case only terminal forces upper case when the diagnostic
attempts to exercise a lower-case character (see Section 12.2.7).
Tabbing Exercise:
The tabbing exercise (see Section 12.2.5) is valid only for those
terminals that are equipped with the ability to tab by hardware.
The results displayed on a non-tabbing terminal have no meanina
and should be ignored. The exercise assumes that the transparent
terminal read-write support option
(IO.RAL and IO.WAL)
was
implemented at system generation.
Remote Terminals:
A remote terminal is exercised by the terminal diagnostic in the
same manner as a local terminal.
No special provisions are
implemented.

12-2

TERMINAL OR LINE PRINTER DIAGNOSTIC
12.2.l

Carriage-Return Exercise, Hard-Copy Terminal

This exercise
correctly to
is:

detE~rmines

that the terminal's print-position returns
position 0 from all other line positions.
The sequence

Print a backslash character (\) at position 0 and
print-position to the end of the line.

space

the

Issue return command.

Print a slash character (/) and space the print-position
the position that precedes the end of the line.

Issue return command.

Continue the exercise until the print-position has been
spaced to every in-line position and has been returned from
there to print a slash character each time.

Upon exercise completion, position 0 should display a multistruck X.

12.2.2

Carriage-Return Exercise, Video-Display Terminal

This exercise determines that the terminal's print-position returns
correctly to position 0 from all other line positions.
The seauence
is:
1.

Display a line of 72 asterisks (*) (or 132, if selected)
issue a return, line-feed command combination.

Continue the exercise by displaying lines of asterisks, where
the quantity for
each line is one less than that of the
preceding line, until the quantity is zero.

and

A partial representation of the pattern follows.
CARRIAGE RETURN TEST

********** etc.
*********
********
*******
******
*****
****
***
**

*
12.2.3

Spacing Exercise, Hard-Copy Terminal

This exercise determines that the terminal spaces
correctly.
The sequence is:
1.

Print backslashes(\)
position 0.

alternate

Return to position 0 and print slashes(/)
blank positions.

12-3

the

positions,
in

print-position
starting
the

alternate

TERMINAL OR LINE PRINTER DIAGNOSTIC
Upon exercise completion,
the
"sawtooth" pattern as follows:

printed

line

should

resemble

/\/\/\/\/\/\/\/\/\ etc.

12.2.4

Spacing Exercise, Video-Display Terminal

This
exercise
determines
that
the
terminal
spaces
the
character-display
position correctly.
The exercise consists of
displaying six lines of asterisks (*) in alternate positions, with the
asterisks in lines 2, 4, and 6 offset by one character position from
those of lines 1, 3, and 5.
At exercise completion,
following pattern.

the

terminal

screen

should

display

the

SPACE TEST

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

12.2.5

Tabbing Exercise

This exercise determines that the terminal, if equipped for
tabbing,
tabs correctly from one tab-stop to the next tab-stop or from an
inter-tab position to the next tab-stop. The sequence is:
1.

Print a slash (/) at position 0, tab to successive tab-stops,
which are eight spaces apart,
and print a slash at each
tab-stop.

For seven lines thereafter, print a slash at position 0'
space a number of positions equal to the line number less one
before tabbing to each tab-stop, and print a slash at each
tab-stop.

Upon completion of the
displayed.

exercise,

the

following

pattern

should

TAB SET

I
I
I
I
I
I
I
I
I

12-4

I
I
I
I
I
I
I
I
I

TERMINAL OR LINE PRINTER DIAGNOSTIC
12.2.6

Line-Feed Exercise

This exercise determines that the terminal
(advances) correctly. The seguence is:

performs

unit

line-feeds

Print a backslash (\) at position O.

Issue a line-feed
backslash.

Continue line-feeding and printing backslashes 70 times
(or
78 times for an 80-column device selected in Service Mode).

command

(without

return)

and

Upon completion of the exercise, a diagonal line should be disclayed
from position O,
line 0, to the right-most position of line 71 (or
line 79).
NOTE

A
line
printer,
other
than
keyboardless
terminal,
displays
sequence of backslash characters
column 0.

12.2.7

a
a
in

Character-Set Exercise

This exercise determines that the terminal can display its entire
upper-case and lower-case, if available) character set, alphanumeric
and special (see below).
The terminal displays the alphanumeric
characters,
in groups of three characters at a time to fill out the
line, beginning with ABC and ending with 789.
Then,
the terminal
displays the special characters in groups of three characters, as
follows:
! II#
$%&
I

(}

*+,
-./

:;<

=>?

@[\
] "

Upon completion of the exercise, the above
displayed.

12.3

character

set

should

SERVICE-MODE INITIATION

Initiation of this mode demands a knowledge of console switch
selection
(see Section 12.4), test parameter selection (see Section
12.5), service-mode intervention
(see Section 12.6),
interactive
testing (see Section 12.7), and the content of Appendix A.
Underlined
text in this procedure indicates reguired or expected user input.

12-5

TERMINAL OR LINE PRINTER DIAGNOSTIC
>ALLOCATE TTn:
>RUN $TERM

(or LPn, n=unit number)

START TERMINAL DIAGNOSTIC -

TIME OF DAY=hour:minute:second

DEVICE? TTn
CONTINUE? SERVICE
(N or RETURN alone aborts the diagnostic)
TEST PARAMETERS (OCTAL)= nnnnnn
CONSOLE SWITCH FOR INTERVENTION (DECIMAL)= U
The selected test sequence commences upon RETURN after you have
responded to all inquiries,
if any,
that occur as a result of
test-parameters selection.

12.4

CONSOLE SWITCH FOR INTERVENTION

12.5

TEST PARAMETER SELECTION

Customer mode allows only a fixed sequence of the diagnostic's tests.
Service mode,
however,
permits customization of the test content
through the test-parameters facility.
Table 12-2 describes the
various options available to you as a service-mode user.
You select
options by logically ORing their
related octal codes to form a
6-character number (leading zeros need not be expressed) for entry in
response to TEST PARAMETERS (OCTAL)=.
NOTE
A response of 0 implies that no tests
are to be performed.
The diagnostic
issues the test summary report and then
terminates.
The table also indicates those options that are automatically selected
foe customer-mode execution.
The "bit" references in the option
descriptions refer to the bit positions of a test-parameters status
word that is monitored by the diagnostic.

12-6

TERMINAL OR LINE PRINTER DIAGNOSTIC
Table 12-1
Test-Parameter Options

'-"''
Option Description
MULTIPASS EXECUTION (Bit 11):
Test sequence repeats until
intervenes.

Selection
Code
(Octal}

In
Customer
Mode

4000

user

TERMINAL TYPE (Bit 7):
A}

Test selected terminal
as a hard-copy device.

200

Selectable

Test selected terminal (or
line printer} as a videodisplay device.

Selectable

100

Selectable

132 COLUMN TEST (Bit 6):
Implements 132-column print-out.
Overrides LINE LENGTH selection.
LINE LENGTH (Bit 5):
A}

Implement line length
of 80 print positions.

Implement line length
of 72 print positions.

Yes

INTERACTIVE-PATTERN TEST (Bits 0-2):
Allows the service-mode user
to
specify a character pattern for
repetitive exercising
of
the
selected terminal
(see Section
12.7) A line printer cannot be
exercised by this test.
TEST SEQUENCE
0--3} :

ELECTION

(Bi ts

NOTE
You have the option of executing either
one exercise or the entire sequence.
You cannot combine several individual
exercises
to
create different test
sequences.
(continued on next page)

12-7

TERMINAL OR LINE PRINTER DIAGNOSTIC
Table 12-1 (Cont.)
Test-Parameter Options

Option Description

Selection
Code
(Octal)

In
Customer
Mode

TEST SEQUENCE ELECTION (bits
0-3):
(Cont.)
A)

Execute the carriage-return exercise
(see Section 12.2.1 or 12.2.2) ~

Execute the spacing exercise (see
Section 12.3.3 or 12.3.4).

Execute the tabbing exercise (see
Section 12.2.5).

Execute the line-feed exercise
(see Section 12.2.6).

Execute the character-set exercise
(see Section 12.2.7).

Execute all of the above exercises
(see Section 12.2).

Yes

~I
12.6

SERVICE-MODE INTERVENTION/RESTART/TERMINATION

You can intervene in (stop} the test-sequence pass at any time hv
changing from its current setting (0 to 1 or 1 to 0) the previously
selected CPU console switch.
Such action causes the diagnostic to
suspend testing and await response to the following message seouence.
TEST PARAMETERS (OCTAL}=

Type an octal value
(other than 0)
to
select new test parameters (or re-enter
the old parameters, which are not saved at
intervention, or
type 0 to terminate the diagnostic.

If new (or the old} parameters are entered, the following
displayed.
RESTART?

message

Type Y to abort the
suspended
test
sequence and initiate the new sequence at
the beginning, or
·
type N to allow the
suspended
test
sequence to run to completion before the
new sequence commences.

For those systems not equipped with a CPU switch console or not
implemented with the GET SENSE SWITCHES directive, the user wishino to
alter test parameters must first terminate the diagnostic by typing:
(crRL/C)

MCR>ABORT

12-8

TERMINAL OR LINE PRINTER DIAGNOSTIC

and then reinitiate the diagnostic with new
parameters.
intervention and restart provisions are not accessible.

12.7

The

INTERACTIVE-PATTERN TEST

This test allows you to specify a character-pattern for
repetitive
line display by the selected terminal
(not a line printer or a
keyboardless terminal).
After test-parameter selection, the test
is
initialized by your
typing up to 132 characters in response to the
following inquiry.
KEYBOARD TEST
TYPE UP TO 132 CHARACTERS - TERMINATE WITH RETURN
OncE! initiated, the line repetition continues until you intervene with
the selected console switch or abort the diagnostic by MCR command.

12-9

CHAPTER 13
DISK DRIVE COMPATIBILITY DIAGNOSTIC

The disk drive compatibility diagnostic
program
verifies
the
compatibility of up to eight disk drives running under RSX-llM-PLUS or
RSX-llM.
The program can be run so that compatibility operations can
be performed online rather than shutting the operating system down to
run the stand-alone diagnostic.
Compatibility is defined here as the ability of a drive to write data
that can be read by all other drives and, in addition, the ability of
a drive to completely overwrite data written by all other drives.
The program is designed to detect the following conditions
commonly cause incompatibility between drives:

13.1

Head Alignment

Positioner lateral misalignment

Improper levels of write current

Incorrect addressing of read/write heads

that

most

HARDWARE AND SOFTWARE ENVIRONMENT

The program runs on the minimum hardware configuration for an RSX-llM
system
(unmapped 16K RK05 or RLOl/2 or 24K for any other disk).
At
least two additional disk drives other than the system disk are
required.
The following disks are supported:
RK05, RLOl/2, RP02/3,
RP04/5/6, RK06/7, and RM02/3.
The program runs under either the RSX-llM-PLUS
system.

13.2

RSX-llM

operating

EXTERNAL INTERACTIONS - USER INTERFACE FOR INITIATION

This section describes the terminal dialogue through which the program
directs the operator
in the selection of drives and the movement of
the test cartridge.
On both RSX-llM and RSX-llM-PLUS systems, allocate the devices
compared.
>ALLOCATE
>ALLOCATE
>ALLOCATE
>ALLOCATE

DB2:
DBS:
DB3:
DB7:

13-1

DISK DRIVE COMPATIBILITY DIAGNOSTIC
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
RUN $COMP
The program first identifies itself as follows:
START DISK DRIVE COMPATIBILITY DIAGNOSTIC - TIME OF DAY

hh:mm:ss

The program then asks for the device mnemonic to test:
ENTER DEVICE MNEMONIC ?
If a carriage return is
printed:

typed,

the

following

help

information

THE FOLLOWING IS A LIST OF SUPPORTED DEVICES:
DK - RKOS,
DL - RLOl/2,

DP - RP02/3,
DM - RK06/7,

ENTER DEVICE MNEMONIC ?

DB - RP04/5/6,
DR - RM02/3

Then, the program asks for the drives to be tested as follows:
ENTER LOGICAL UNIT NUMBERS ?
If the escape or altmode key is pressed,
the program reauests
then
device mnemonic again.
If carriage return is typed,
following help information is printed:
ENTER UP TO 8.

UNIT NUMBERS IN OCTAL (I.E., 0,1,2).

ENTER LOGICAL UNIT NUMBERS ?

13.2.1

the
the

2,5,3,7

Pass 1 Dialogue

After the selection of unit numbers, the program indicates
of Pass 1 as follows:

the

start

** STARTING PASS 1 **
Next, the program selects the first drive to be tested and instructs
the operator to mount the test cartridge or pack and load the heads on
that drive, as in the following example:
LOAD PACK IN DRIVE 2 AND START THE DRIVE.
WHEN THE DRIVE IS READY TYPE :
On RSX-llM-PLUS systems, COMP displays two commands to logically mount
the volume as foreign and to resume the task.
MOUNT DB2:/FOR<CR>
RESUME TT24
<CR>
On RSX-llM systems, COMP displays only the command to resume the task.
On both RSX-llM and RSX-llM-PLUS
following message:

systems,

THE DIAGNOSTIC WILL NOW SUSPEND:

13-2

COMP

continues

with

the

DISK DRIVE COMPATIBILITY DIAGNOSTIC
ThE~

task then suspends itself.
On both RSX-llM and RSX-llM-PLUS
systems,
load the pack or cartridge in the drive and ready the unit.
When the drive-ready light is on, proceed to type the command(s)
that
COMP displayed.
On RSX-llM-PLUS systems only, type the command to mount the volume
foreign.

MOUNT DB2:/FOR ~

>
On both RSX·-llM and RSX-llM-PLUS systems, type the command
the task.

resume

>RESUME TT24 ~

>
The task then resumes execution.
If the disk cartridge or pack has a home block (refer to step 3 of
Section 13.5.1, "Description of Pass 1 Tests"), the following message
is printed:
**WARNING** DB2:

HAS A FILE STRUCTURED VOLUME **WARNING**

CONTINUE ?

,....,.

If the answer is Y, the program performs Pass 1 functions on this
drive
(described in Section 13.5.1, "Description of Pass 1 Tests").
Any other response causes the program to exit.
The program then
instructs the operator to unload the drive and move the pack to the
next drive, as follows:
UNLOAD DRIVE 2 AND REMOVE THE PACK.
LOAD PACK IN DRIVE 5 AND START THE DRIVE.
WHEN THE DRIVE IS READY TYPE :
On RSX-llM-PLUS systems, COMP displays two commands to logically mount
the volume as foreign and to resume the task.
MOUNT DB5:/FOR<CR>
RESUME TT24
<CR>
On RSX-llM systems, COMP displays only the command to resume the task.
On both RSX-llM and RSX-llM-PLUS
following message:

systems,

COMP

continues

with

the

THE DIAGNOSTIC WILL NOW SUSPEND:
The task then suspends itself.
On both RSX-llM and RSX-llM-PLUS
systems,
load the pack or cartridge in the drive and ready the unit.
When the drive-ready light is on, proceed to type the command(s)
that
COMP displayed.
ON RSX-llM-PLUS systems only, type the command to mount the volume
foreign.
MOUNT DB5:/FOR ~

13-3

DISK DRIVE COMPATIBILITY DIAGNOSTIC
On both RSX-llM and RSX-llM-PLUS systems, type the command
the task.

resume

>RESUME TT24 ~

>
The task then resumes execution.
The operator performs these functions and, in the same manner,
the
program instructs the operator in the movement of the pack throughout
the rest of the drives. When all drives have been completed,
the
program starts Pass 2.

13.2.2

Pass 2 Dialogue

The Pass 2 dialogue is the same as the Pass 1 dialogue except that the
drives are tested in the reverse order.
For example, if drives 2, 5,
3, and 7 were tested in that order during Pass 1, Pass 2 reauests the
drive numbers 3, 5, and 2.
Drive 7 would not be reauested since all
tests were completed on that drive at the end of Pass 1. This is in
accordance with the testing algorithm designed for a minimal number of
cartridge changes. The program indicates the start of Pass 2 by
printing the following message:

** STARTING PASS 2 **
LOAD PACK IN DRIVE 3 AND START THE DRIVE.
WHEN THE DRIVE IS READY TYPE :
On RSX-llM-PLUS systems, COMP displays two commands to logically mount
the volume as foreign and to resume the task.
MOUNT DB3:/FOR<CR>
RESUME TT24
<CR>
On RSX-llM systems, COMP displays only the command to resume the task.
On both RSX-llM and RSX-llM-PLUS systems,
following message:

COMP,

continues

with

the

THE DIAGNOSTIC WILL NOW SUSPEND:
The task then suspends itself.
On both RSX-llM and RSX-llM-PLUS
systems,
load the pack or cartridge in the drive and ready the unit.
When the drive-ready light is on, proceed to type the command(s)
that
COMP displayed.
On RSX-llM-PLUS systems only, type the command to mount the volume
foreign.

MOUNT DB3:/FOR ~

>
On both RSX-llM and RSX-llM-PLUS systems, type the command
the task.
>RESUME TT24 ~

>
The task then resumes execution.

13-4

resume

DISK DRIVE COMPATIBILITY DIAGNOSTIC
The program then performs Pass 2 functions on this drive (described in
Section 13.5.2,
"Description of Pass 2 Tests"). The program then
instructs the operator to unload the drive and move the pack to the
next drive.
UNLOAD DRIVE 3 AND REMOVE THE PACK.
LOAD THE PACK IN DRIVE 5 AND START THE DRIVE.
WHEN THE DRIVE IS READY TYPE
On RSX-llM-PLUS systems, COMP displays two commands to logically mount
the volume as foreign and to resume the task.
MOUNT DB5:/FOR<CR>
RESUME TT24
<CR>
On RSX-llM systems, COMP displays only the command to resume the task.
On both RSX-llM and RSX-llM-PLUS
following mess~ges:

systems,

COMP

continues

with

the

THE DIAGNOSTIC WILL NOW SUSPEND:
The task then suspends itself.
On both RSX-llM and RSX-llM-PLUS
systems,
load the pack or cartridge in the drive and ready the unit.
When the drive-ready light is on, proceed to type the command(s)
that
COMP displayed.
On RSX-llM-PLUS systems only, type the command to mount the volume
foreign.

MOUNT DB5:/FOR ~

>
On both RSX-llM and RSX-llM-PLUS systems, type the command
the task.

resume

>RESUME TT24 ~

>
The task then resumes execution.
The operator performs these functions and, in the same manner,
the
program instructs the operator in the movement of the pack throuahout
the remaining drives.
At the end of Pass 2,
if all drives- are
compatible, the following message is printed:

** ALL DRIVES ARE COMPATIBLE **
Drives found to be incompatible will have appropriate error messages
printed when the error is encountered (refer to Section 13.3, "Error
Messages").

13.3

ERROR MESSAGES

Section 13.3.l and 13.3.2
recovery procedures.

describe

13-5

possible

error

conditions

and

DISK DRIVE COMPATIBILITY DIAGNOSTIC
13.3.l

Dialogue Errors

Any errors occurring because of an answer input by the operator are
trapped by the program and the dialogue resumes at the question just
asked after the operator is notified of the error condition.
Help
information is available for each question, where applicable, by
typing carriage return.

13.3.2

Program Errors

Error messages give all pertinent information including good data, bad
data, logical block number, cylinder, track, sector, and the operation
being performed.
All numbers are printed in decimal.
The following
is the format for error messages:
ERROR NO.= n
EXPECTED
RECEIVED
FUNCTION
CYLINDER

ERROR CODE
TRACK

(or WORD)

LBN =
SECTOR

NOTE
the ERROR
CODE
is
On I/O errors,
On compare errors, the ERROR
printed.
WORD on which the compare failed
is
printed.
The ERROR NO.=n message is the test number being performed at the time
of the error. The error number, n, can be any of the following test
numbers:
TEST 1 - Writing the overwrite and compatibility groups
TEST 2 - Overwrite test
TEST 3 - Compatibility test
Refer to the operational description for an explanation of each of the
above tests.
The following is a list of the error messages:
DIAGNOSTIC DOES NOT SUPPORT OPERATING SYSTEM
The diagnostic only runs on the RSX-llM or RSX-llM-PLUS operating
systems.
This error occurs when the diagnostic is run on the
RSTS/E, VAX/VMS, RSX-llD, or IAS operating systems.
DEVICE HANDLER NOT LOADED
The device driver does not reside in memory.
aborts so that the driver can be loaded.

The

diagnostic

DEVICE MOUNTED OR ALLOCATED TO OTHER USER
Another user is using the device under test.
On RSX-llM-PLUS,
this error also occurs when the device is not mounted foreian.
The diagnostic aborts so that the device can be allocated and/or
mounted foreign.

13-6

DISK DRIVE COMPATIBILITY DIAGNOSTIC
LOGICAL UNIT NUMBER n DOES NOT EXIST
One of the unit numbers specified
(n)
does not exist.
The
program requests new unit numbers after the message is printed.
DEVICE XXn:

HAS THE WRONG MAXIMUM LOGICAL BLOCK NUMBER

The maximum logical block number passed back by the Get LUN
Directive
(GLUN$)
is not the number expected by the diagnostic.
XX is the device mnemonic, and n is the logical unit number.
DRIVES n AND y ARE NOT THE SAME DEVICE TYPE
The unit numbers specified include two different device types
(for example, RP04/5s and RP06s):
n is the unit number of the
first drive specified, and y is the unit number of the drive that
is a different type.
MAKE DRIVE READY, TYPE <CR> WHEN READY TO CONTINUE
The drive is not ready (that is, the heads are not loaded).
The
program waits for the operator to make the drive ready and type
carriage return to continue.
WRITE-ENABLE DRIVE, TYPE <CR> WHEN READY TO CONTINUE
The program attempted to write to a unit that is write protected.
The program waits for the operator to write enable the drive and
type carriage return to continue.
**WARNING** DBn:

HAS A FILE STRUCTURED VOLUME

**WARNING**

~hP

Aisk cartridge being used is either a FILES-11 or DOS
(XXDP)
formatted disk.
This message is used to warn the operator
against accidentally writing on a file-structured disk.
After
the message is typed, the operator is asked whether to continue.

THE DISK PACK IN DRIVE n IS NOT THE PACK BEING USED FOR TESTING.
REPLACE IT WITH THE TEST PACK, TYPE <CR> WHEN READY TO CONTINUE
This message is printed when a drive other than the first drive
being tested is found to have a home block on it.
Because the
home block is destroyed during testing on the first drive,
no
home block should be found on any other drive being tested.
The
program will not continue until the test pack is loaded in drive

THE! OVERWRI'l1E GROUP COULD NOT BE WRITTEN.
or
THE COMPATIBILITY GROUP COULD NOT BE WRITTEN
This error occurs if either the overwrite or compatibility groups
cannot be written after three retries.
Because all bad blocks
should have been found on the first drive tested by the worst
case data pattern,
the program assumes that there must be a
hardware problem. The program exits so that the appropriate user
mode diagnostic can be run.

13-7

DISK DRIVE COMPATIBILITY DIAGNOSTIC
COULD NOT FIND n CONTIGUOUS GROUPS OF GOOD CYLINDERS
Too many bad cylinders were discovered within a write-current
zone.
This message occurs during the Bad Block Check, performed
on the first drive, when the overwrite and compatibility groups
overlap.
In the message, n is the number of contiguous cylinders
that were needed.
This value corresponds to the number of units
under
test.
The error indicates that the disk cartridge cannot
be used.
The diagnostic exits when this error occurs.
DATA WRITTEN BY DRIVE-y COULD NOT BE

OVERWRIT~EN

BY DRIVE n

The drive under test has improper levels of write current.
The
unit number under test is n, and the number of the unit that
initially wrote the data is y.
DATA WRITTEN BY DRIVE y WAS RECOVERED USING OFFSET o BY DRIVE n
During the compatibility test, offsets were needed to recover the
data.
The data was recovered within specifications (refer to
Section 13.7.3, Retry Algorithm).
The unit number under test, is
n,
the drive that wrote the data is y, and the offset that was
used to recover the data is o.
This message informs the operator
that a problem may be developing.
The operator should record
this information, so that it can be compared against future runs
of the diagnostic.
INCOMPATIBILITY FOUND:
DATA WRITTEN BY DRIVE y COULD NOT BE READ BY DRIVE n
The drive under test is not compatible with one of the other
drives.
The data could not be recovered within specifications
(refer to Section 13.7.3, "Retry Algorithmn).
The unit number
under test is n, and the number of the unit that wrote the data
is y.

13.4

FUNCTIONAL DESCRIPTION

The disk pack is segmented into seven zones,
called write-current
zones.
The term "write-current" comes from the fact that within each
zone, different amounts of write-current can be used to write on that
area of the disk.
Each write-current zone is divided into two groups
called the overwrite group and the compatibility group.
The first
eight cylinders of each write-current zone are the cylinders used
during the overwrite test.
The last eight cylinders of
each
write-current zone
(except for the innermost zone) are the cylinders
used for the compatibility test.
Each logical drive writes and/or reads one cylinder in each group, one
and the maximum number of sectors per track (test dependent), two
groups in a write-current zone, and seven write-current zones on a
pack.
The entire test consists of two passes (Pass 1 and Pass 2)
through the units selected for testing.
Section 13.5 describes the
operations of each pass in detail.

13-8

DISK DRIVE COMPATIBILITY DIAGNOSTIC
13.5

OPERATION DESCRIPTION

The main functional blocks of code in the program are assigned test
numbers for
the purpose of identification in error printouts. The
following sections describe the Pass 1 and Pass 2 tests in test number
order.

13.5.1

Description of Pass 1 Tests

Starting the diagnostic - The program requests the operator
to enter up to eight unit numbers in octal. The program then
checks to ensure that the units specified exist and are the
same device type.

Mounting the test cartridge for Pass 1 - The operator mounts
the pack on the drive specified by the program, and loads the
heads.
The operator performs the task and types
the
command(s)
to continue
(refer to Section 13.2.1, "Pass 1
Dialogue").

HOME-BLOCK CHECK - This test is performed on every drive
before testing begins to check the volume for a home block
(either a FILES-11 or DOS (XXDP) formatted disk).
If a home
block is found on the first drive, a warning message is
printed and the operator is asked whether to continue.
If a
home block is found on any drive other than the first drive,
this indicates that the test cartridge is not loaded.
A
warning message is printed and the operator is reauested to
mount the test cartridge.

BAD-BLOCK CHECK - This test is performed on the first drive
tested.
It writes and verifies the worst-case data pattern
(refer to Section 13.6.3 for a description of the patterns)
in each of the group of cylinders specified in Section
13.6.4.
If a bad block is detected,
the starting cylinder
for
the group is adjusted to point to another group of
cylinders (refer to Section 13.7.2 "Bad Block Algorithm").
The operations are then repeated until either a good group of
cylinders is found, or the overwrite and compatibility groups
overlap.
If the groups overlap, an error message is printed
indicating the disk pack cannot be used.

TEST 1 - Writing the Overwrite and Compatibility Groups - The
program writes and verifies all cylinders for this drive
within the cylinder groups shown in Section 13.6.4 using a
single pattern in Section 13.6.5.
One cylinder in each
overwrite and compatibility group is written by the current
drive. There are 7 overwrite and 6 compatibility groups on a
pack.
In all, 13 cylinders are written by each drive.
The
cylinders written correspond to the logical drive number
(drive 0 writes the first cylinder of each group,
drive 1
writes the second cylinder of each group, and so forth).
The
cylinders written by each drive are shown in Section 13.6.7.

TEST 2 - Overwrite Test - The Overwrite Test checks that the
drive under test is capable of successfully overwriting data
previously written by any other
drive.
The
program
overwrites and verifies one sector in each cylinder of each
overwrite group written by previous drives.
The sector
overwritten corresponds to the logical drive number under
test.
If this is the first drive, the overwrite test is not
performed because the same drive would be overwriting. The

13-9

DISK DRIVE COMPATIBILITY DIAGNOSTIC
basic cylinder layout for each
Section 13.6.6.

overw~ite

cylinder is shown in

For example, if drives 2, 5, 3, and 7 are being checked for
compatibility, and the drive currently under test is drive 3,
then drive 3 will overwrite sector 2 of cylinders written by
drives 2 and 5. The cylinders written by drive 7 would not
be overwritten because they have not been written yet.
7.

TEST 3 - Compatibility Test - The Compatibility Test checks
that the drive under test is capable of successfully reading
data previously written by any other drive.
The proqram
reads the cylinders in each compatibility group written by
the previous drives and verifies the data.
The
read
operation is performed after a seek from both the minimum and
maximum cylinders to uncover any carriage problems.
If this
is the first drive, the compatibility test is not performed
because the same drive would be reading.
For example, if drives 2, 5, 3, and 7 aie being checked for
compatibility,
and the current drive under test is 3, then
drive 3 will read all sectors on cylinders written by drives
2 and 5.

13.5.2

Dismounting the test cartridge in Pass 1 - The operator
unloads the drive and dismounts the pack, as directed by the
program, to proceed with the steps on the next drive.
If
this is the last drive, the program starts Pass 2.

Description of Pass 2 Tests

In Pass 2, the drives are tested in the reverse order. The last drive
that was tested in Pass 1, will not be requested in Pass 2 because all
tests were completed on that drive at the end of Pass 1.
9.

Mounting the test cartridge in Pass 2 - The operator mounts
the pack in the drive specified by the program, and loads the
heads.
The operator performs the task and types
the
command{s)
to continue
{refer to Section 13.2.2, "Pass 2
Dialogue").

10.

HOME-BLOCK CHECK - The volume is checked for
a home block
{either a FILES-11 or DOS (XXDP) formatted disk).
If a home
block is found, this indicates that the test cartridqe is not
loaded.
A warning message is printed and the operator is
requested to load the test pack.

11.

TEST 2 - Overwrite Test - The program overwrites and verifies
one sector
in each cylinder of each overwrite group written
by drives tested after the current drive in Pass 1.
For example, if drives 2, 5, 3, and 7 were tested in Pass 1,
and the current drive under test is drive 5, then drive 5
will overwrite sector 1 of cylinders written by drives 3 and
7. The cylinders written by drive 2 would not be overwritten
because they were overwritten in Pass 1.

12.

TEST 3 - Compatibility Test - The program reads the cylinders
of each compatibility group written by drives tested after
the current drive in Pass 1. The read operation is performed
after a seek from both the minimum and maximum cylinders to
uncover any carriage problems.

13-10

"'°~1

DISK DRIVE COMPATIBILITY DIAGNOSTIC

For example, if drives 2, 5, 3, and 7 were tested in Pass 1,
and the current drive under test is drive 5, then drive 5
will read cylinders written by drives 3 and 7.

13.

Dismounting the test cartridge in Pass 2 - The operator
unloads the drive and dismounts the pack, as directed by the
program, to proceed with the above steps on the next drive.
If this is the last drive, going in the reverse order, then
testing is complete.

Restrictions

13.5.3

The program is restricted to testing a maximum of eight disk drives at
a time.
The drives can be on the same or different controllers.

13.6

DESCRIPTION OF MAJOR MODULES

There! are two modules for the disk drive compatibility diagnost.ic:
a
common disk function handler module and the main module that contains
all other routines.
The following sections explain each module in
more detail~

13.6.1

Common Disk Function Handler

The common module contains the routines to convert a disk address to a
logical block number
(LBN) , to check the LBN to ensure that it does
not exceed the maximum LBN, and then to issue the function.

13.6.2

Main Module

The main module contains all other routines, other than the function
handler,
used by the diagnostic.
The following list explains each
routine and the operations it performs:
1.

Input Routine - This routine requests the operator to enter
the unit numbers of the drives to test and checks the number
input to ensure that it is a valid number.
If the number
is
invalid, help information is printed to assist the operator.

Device Check - This routine ensures that the unit numbers
specified exist.
If they do not, those numbers of the units
that do not exist are printed at the terminal and the user is
requested to input new unit numbers.

Table Sear.ch Routine - This routine searches a device table
to determine whether the disk is supported and what the
device type is.
It then sets up the maximum parameters (LBN,
cylinders,
tracks,
and sectors).
It also ensures that all
the units selected are the same device type.
This is done by
comparing the maximum LBN of each drive with the first drive
specified.
If the units are different
(that is,
RP04 and
RP06),
a message is printed indicating this and the operator
is requested to enter new unit numbers.

13-11

DISK DRIVE COMPATIBILITY DIAGNOSTIC
4.

Load and Unload Routines - These routines direct the operator
in the loading and unloading of the disk cartridge to the
appropriate drives.

Home-Block Routine - This routine is performed on every drive
before testing begins.
It checks for a home block (either a
FILES-11 or DOS (XXDP) formatted disk).
If a home block
is
found on the first drive tested in Pass 1, a warning message
is printed and the operator asked whether to continue.
If
the drive is not the first drive being tested, a warning
message is printed indicating that the test pack
is not
loaded.
In this case, the operator is requested to load the
test pack.

Bad Block Checking Routine - This routine is performed on the
first drive tested during Pass 1.
It writes and verifies the
worst-case data pattern in each group of cylinders (refer to
Table 13-2),
to ensure that there are no bad blocks.
If a
bad block is encountered, the write-current zone is adjusted
to point to another group of cylinders and the operation
repeated (refer to Section 13.7.2,
"Bad-Block Algorithm").
If there are too many bad cylinders within a write-current
zone, a message is printed indicating that the disk pack
cannot be used.

13.6.3

Worst-Case Data Pattern

Table 13-1
bad-block
diagnostic
repetition

lists the pattern used for basic read/write test and
checking routine.
It occurs in the RP04/5/6 multidrive
and is the same pattern used by the BAD utility program.
A
of the pattern is written and verified in each sector.
Table 13-1
Worst Case Data Pattern
Word No.

Data (octal)

0
1

13.6.4

165555
133333

Write-Current Zones Tables

Table 13-2 shows the cylinder breakdown of the disk for
the
write-current zones and the breakdown of each write-current zone for
the overwrite and compatibility groups for the RP04/5. All values are
in octal.

13-12

I ..

iii I wt

a Ia

$lll I Si£$$$ '

DISK DRIVE COMPATIBILITY DIAGNOSTIC
Table 13-2
Cylinder Group Assignment for a Given Surface
Disk

Overwrite Cylinder
Group Range
(in octal)

RK05,
RPR02

1 2 3 4 5 6 7 -

0·-37
40-77
100-137
140-177
200-237
240-277
300-307

40 - 47
100-107
140-14 7
200-207
240-247
300-307

RK06,
RP03,
RP04/5

1 2 3 4 5 6 7 -

0-77
100-177
200-277
300-377
400-477
500-577
600-632

100-107
200-207
300-307
400-407
500-507
600-607

RK07,
RM02/3,
RP06

1 2
3 4
5 6 7

0-177

- 200-377
400-577
- 600-777
-

13.6.5

··~

Write-Current
Zone and Range
(in octal)

1000-1177
1200-1377
1400-1456

Compatibility Cylinder
Group Range
(in octal)
30 - 37
70 - 77
130-137
170-177
230-237
270-277

70 - 77
1 70-1 77
270-277
370-377
4 70-4 77
570-577

170-177
370-377
570-577
770-777
1170-1177
1370-1377

0-7
200-207
400-407
600-607
1000-1007
1200-1207
1400-1407

Random Data Pattern Table

Each word of Table 13-3 corresponds to the logical drive number
(word 0 is used for the first drive, word 1 is used for the second
drive, and so forth.) The following patterns also occur in the RM03
compatibility diagnostic.
Table 13-3
Random Data Pattern
Word Number

Data (Octal)

0
1
2
3
4
5
6
7

040135
177070
070414
064531
174473
062422
114352
036620

13-13

DISK DRIVE COMPATIBILITY DIAGNOSTIC
13.6.6

Basic Overwrite Cylinder Group Layout

This section shows the sectors of the first cylinder of an overwrite
group written by the first logical drive under test.
It then shows
the sectors after each drive (assuming eight drives are being tested)
has performed the overwrite test.
If less than 8 drives are beinq
tested, then additional sectors are simply not used.
The contents of the first cylinder in each overwrite
first drive include word 0 of the random data table.
SECTOR NUMBER
DATA PATTERN

0
0

1
0

2
0

6
0

group

for

the

7
0

Every other drive writes one sector within the cylinders written by
the first drive.
The sector overwritten by every other drive
corresponds to the logical drive number under test (that is,
logical
drive 1 overwrites sector 1 and logical drive 2 overwrites sector 2).
The pattern written by every other drive corresponds to a pattern from
Table 13-3.
After all drives have completed the overwrite test, the
sectors look as follows:
SECTOR NUMBER
DATA PATTERN

0
0

1
1

2
2

3
3

4
4

5
5

6
6

7
7

This same operation is also performed on cylinders written by every
other drive. This ensures that each drive can overwrite data written
by every other drive.

13.6.7

Cylinders Table

Table 13-4 shows the cylinders written by each drive, assuming no bad
blocks were found, in the overwrite and compatibility groups on each
track.
Table 13-4
Cylinders Written (RK06, RP03, and RP04/5)
Drive
No.
0
1
2
3
4
5
6
7

Overwrite Cylinders

Compatibility Cylinders

0,100,200,300,400,500,600
1,101,201,301,401,501,601
2,102,202,302,402,502,602
3,103,203,303,403,503,603
4,104,204,304,404,504,604
5,105,205,305,405,505,605
6,106,206,306,406,506,606
7,107,207,307,407,507,607

70,170,270,370,470,570
71,171,271,371,471,571
72,172,272,372,472,572
73,173,273,373,473,573
74,174,274,374,474,574
75,175,275,375,475,575
76,176,276,376,476,576
77,177,277,377,477,577

Refer to Table 13-2 to determine the cylinders that
all other disks.

13-14

are

written

for

DISK DRIVE COMPATIBILITY DIAGNOSTIC
KEY ALGORITHMS

13.7

The following algorithms
compatibility diagnostic.

13.7.1

are

used

throughout

the

disk

drive

Determining Sectors Used by Each Drive

There is a counter that corresponds to the logical drive number under
test
(that is,
0 =first logical drive, 1 =second logical drive).
The counter is added to the starting cylinder in each overwrite and
compatibility group to determine the cylinder to read and/or write on
each trackD When the overwrite test is performed,
the counter also
determines the sector to overwrite on each cylinder in each overwrite
group.

13.7.2

Bad-Block Algorithm

When the diagnostic checks for bad blocks, normal retries performed by
the driver are inhibited.
The write-current zones table is adjusted
when any of the following errors occur:
1.

WRITE-CHECK ERROR (IE.WCK)

; Only if enabled by MCR.

BAD BLOCK ERROR (IE.BBE)

PARITY OR SOFT ERROR (IE.VER)

This adjustment should ensure that all areas of the disk being used by
the diagnostic are error free.
If a bad block is encountered in an overwrite group,
the
cylinder+! becomes the new starting cylinder for that group.

current

If a bad block is encountered in a compatibility group,
the current
cylinder
(the number of units under test) becomes the new starting
cylinder for that group.

13.7.3

Retry Algorithm

Normal retries performed by the driver are inhibited during any data
transfer.
If a read operation fails,
the program performs three
retries at centerline.
If retries fail at centerline,
then retries
are performed with offsets.
Table 13-5 lists the disks that support
offset recovery, the maximum plus and minus offset to be used, and the
offset increment.
Table 13-5
Maximum and Minimum Offsets
Device

Maximum Off set

Off set Increment

RK06
RK07
RM03
RP04/5
RP06

600
300
200
600
300

25.0
12.5
200.0
25.0
25.0

13-15

DISK DRIVE COMPATIBILITY DIAGNOSTIC
Two retries at each offset position are performed.
If the data is recoverable within the specified offsets,
then a
warning message is printed indicating that offsets were used and at
which offset position the data was recovered.
If the data is not
recovered,
then a message is printed indicating the drives that are
incompatible.

13-16

ea a ea ¥ ~

1!11 •·

APPENDIX A

HELP! THE SERVICE-MODE USER

A.l

GENERAL INFORMATION

As a service-mode user, you are expected to understand system concepts
or to have the assistance of a systems programmer.
Each diagnostic chapter includes the following sections.
Customer-mode initiation
Test summary report
Device characteristics
Diagnostic description
Error messages (not applicable for terminal/line printer
diagnostic)
Service-mode initiation
Console switch for intervention
Test-parameter selection
Service mode intervention/restart/termination
Interactive tests
You should be familiar with the entire applicable chapter and
performance of the diagnostic before initiating device testing.

the

Test-parameter selection is a major section as it details the various
options available to you for the customization of the test sequence.
Test-parameter selection is also the
initiating
facility
for
intE~ractive
testing,
such as
"rocking" a DECtape between two
user-specified blocks or exercising a user-specified disk sector with
a specific data pattern.
is a
The reference sheet located at the rear of this manual
the knowledgeable service-mode
quick-access information source for
use:r.

A-1

HELP! THE SERVICE-MODE USER

A.2

DIAGNOSTIC INITIATION

ERROR LOGGING SHUTOFF
Error information for any device under test is not accumulated by
Error Logging during diagnostic execution;
thus, you should
always initiate a diagnostic at a hard-copy terminal to capture
error reports and the test summary report.
INPUT LINE TERMINATION
Termination of any command or data-line
RETURN.

input

indicated

WRONG DEVICE SELECTION
To protect against the selection of the wrong device and possible
loss of data,
you must enter the same device identification
(device mnemonic and unit number) twice.
The WARNING message and
CONTINUE? pause are additional checks for you to verify that the
device selected is the device you want tested.
NUMERICAL ENTRIES
Unless an inquiry specifies otherwise, any numerical entry can be
expressed in decimal or octal radix.
Decimal entries must be
identified as such by a decimal point after the last digit.
MULTIPLE EXERCISE SELECTION
Multiple exercises selected from the test-parameter
executed in the order of their selection codes;
with the lowest octal code is executed first.

options are
the exercise

DIAGNOSTIC RESIDENCE
The initiation procedure assumes that the applicable diagnostic
exists as a non-privileged, checkpointable task-image file on the
system device (SYO:) under UIC [l,m] where "m" is 54 for a mapped
system or 50 for
an unmapped system.
If the diagnostics were
filed elsewhere, appropriate identification must be included in
the RUN command.
DATA BUFFER SIZE
The diagnostic descriptions assume that the data buffer size was
not changed at system generation from the default of 1024 bytes.
This buffer controls the size of data transfers for most write
and read operations initiated by the diagnostic.

A-2

HELP! THE SERVICE-MODE USER
A.3

ERROR MESSAGES

The following list describes messages that might be reported by MCR or
by a diagnostic during initiation.
To learn the significance of other
messages, refer to the RSX-llM/M-PLUS MCR Operations Manual and the
RSX-llM/M-PLUS Executive Reference Manual.
MCR Command Error Messages:
XXX -- SYNTAX ERROR
Format of entry to MCR is incorrect.

Re-enter.

ALL -- DEVICE ALLOCATED TO OTHER USERl
It cannot be
logs out, or a

Selected device is under control of another user.
allocated until that user deallocates it or
privileged user deallocates it.
ALL -- DEVICE NOT IN SYSTEMl
Selected device was not specified during system
cannot be tested by a User Mode Diagnostic.

generat~on.

ALL -- FEATURE NOT SUPPORTED
Indicates ALLOCATE command is not implemented
Ignore message and proceed with initiation.

for

your

system.

ALL -- PUBLIC DEVICEl
Selected device has been declared a public device.
It cannot be
allocated by any user until
it is declared to be a nonpublic
device.
HEL -- INVALID ACCOUNTl
The name or UIC specified is not present in the account file,
the password given is incorrect.

HEL -- OTHER USER LOGGED ONl
Another user left this terminal in logged-in state.
used until it is logged out by the BYE command.

It cannot be

HEL -- TERMINAL ALLOCATED TO OTHER USERl
This terminal has been allocated to another user.
It cannot be
used until that user deallocates it or logs out, or a privileged
user deallocates it.

1 The related command thus this
multiuser protection systems.

error

A-3

message

are

valid

only

for

HELP! THE SERVICE-MODE USER
INS -- FILE NOT FOUND
The specified diagnostic was not build and made part of the
system at system generation, or the UMD task-image files are not
present on SY:
at [l,m] where m is 50 for an unmapped system or
54 for a mapped system.
MCR -- NOT LOGGED INl
Multiuser protection system requires that you log-in at the
terminal with the BELLO command before issuing any command other
than HELP.
DIAGNOSTIC ERROR MESSAGES
The following error messages might be reported after control has
passed from MCR to the selected diagnostic.

been

* DEVICE OFFLINE *
Selected device is not physically or logically available.

* DEVICE MOUNTED OR ALLOCATED TO OTHER USER *
Indicates that volume on selected device is mounted
(must be
dismounted for diagnostic testing),
or that device has been
allocated to another user (this case assumes that you did not
issue the ALLOCATE command, multiuser protection system only).

* ILLEGAL FUNCTION (MAY BE WRONG DIAGNOSTIC) *
Indicates that the wrong diagnostic was initiated.

* DEVICE OR DRIVER NOT AVAILABLE FOR DIAGNOSTICS *
Selected device or
its associated
capabilities is not in the system.

driver

with

diagnostic

·"""·

* INVALID DEVICE OR UNIT *
Device identification
correct.

(mnemonic

and/or

unit

number)

not

Indicates that you entered a switch number greater than
(decimal) in response to the inquiry "CONSOLE SWITCH FOR ••• ".

1 The related command and thus this error message are valid only
multiuser protection systems.

for

* ONLY SWITCHES 0-15 ALLOWED *

A-4

·~.

HELP! THE SERVICE-MODE USER
A.4

MULTIDEVICE TESTING

Should you wish to initiate concurrent execution
of
multiple
diagnostics from the same terminal, each RUN command must include an
explicit task name, and a unique console switch must be assigned to
each diagnostic for intervention. The following seouence illustrates
initiation for concurrent testing of a TUlO tape transport and a RKOS
disk.
On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCNrE MT2:
On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT MT2:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN ~Ul0/TASK=MT2
START TUlO DIAGNOSTIC •.•
DEVICE? MT2
**WARNING**···
CONTINUE? SERVICE
TEST PARAMETERS {OCTAL)=4001
CONSOLE SWITCH FOR INTERVENTION{DECIMAL)=l5
The tape diagnostic executes the full-tape data
until you intervene by setting switch 15.

reliability

exercise

On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
>ALLOCATE DKO:
On RSX-llM-PLUS systems only, logically mount the volume as foreign.
>MOUNT DKO:/FOR
On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
>RUN $RK05/TASK=DKO
START RKOS DIAGNOSTIC •••
DEVICE? DKO
*WARNING**···
CONTINUE? SERVICE
TEST PARAMETERS {OCTAL)=2002
CONSOLE SWITCH FOR INTERVENTION{DECIMAL)=O
WORD COUNT=256.
DO YOU WISH TO SPECIFY THE SECTOR ADDRESS?
CYLINDER=ll.
TRACK=Q SECTOR==1
PATTI::RN N0.=4
WRITE? X
READ? X

The disk diagnostic exercises the specified sector with a
pattern until you intervene with switch O.

A-5

random-data

HELP! THE SERVICE-MODE USER
Error messages and summary reports from the diagnostics may be
interspersed at the terminal, but they will be explicitly identified
by device and unit number.

A.5

DIAGNOSTIC TERMINATION

The test sequence selected from the test parameter options runs to
completion and exits.
If multi-pass or interactive testing were
selected, the test continues until you intervene with the console
switch and/or terminate the test.
The following describes the various
termination methods available to the service-mode user.
One termination method is to intervene with the console switch and
respond with 0 to T&ST PARAMETERS (OCTAL)=. The test summary report
for the current pass will be produced before the diagnostic exits.
You may also use the MCR ABORT command at any time (be sure to include
the task name if one was assigned during initiation).
(CIRL/C)

MCR>~

or ABORT DKO

The current-pass test summary report will not be produced.
Another termination method is to respond with CTRL/Z to any
The current-pass test summary report-will not be produced.

A.6

inauiry.

LOGICAL BLOCK NUMBERS FROM PHYSICAL ADDRESSES

A
disk
sector
is
identified
by
its
physical
address
(sector-track-cylinder numbers) in diagnostic error messages.
Should
you wish to register the sector as being bad via the BAD option of the
INITVOLUME commandl, you must convert the physical address to a
logical block number (LBN), as follows.
LBN = (((cyl no.*trk's/cyl)+trk no.)sec's/trk)+sec no.
where all values are decimal.
For example, an RP06 sector (see Section 3.2
parameters) with the address of
Cylinder

000536(octal), 350 {decimal)

Track

000016 {octal), 14 (decimal)

Sector

000013(octal), 11 (decimal)

for

RP06

data-capacity

is logical block number 146619, computed as follows.
LBN

(((350*19)+14)*22)+11
(6650+14) *22+11
146608+11
146619

1 Refer to the RSX-llM/M-PLUS MCR Operations Manual for
of commands.

A-6

descriptions

APPENDIX B
BIT MAPS FOR DEVICE-CONTROLLER REGISTERS

This appendix helps you decipher the significance of the register
contents displayed in the error messages. Tables B-1 through B-9
define the meaning of the bit positions for the applicable registers.
They are device specific, as follows.
Table Reference

Device
Cartridge Disks:
RKO 5 ( RKO SF)

B-1

RK06

B-2

Pack D:isks:
RP02,RPR02,RP03

B-3

RP04,RP05,RP06

B-4

Fixed-Head Disks:
RFll

B-5

RS03,RS04

B-6

Magnetic Tape Units:
TS03,TU10

B-7

TU16,TU45

B-8

DECtape Unit:
B-9

TU56

These tables have an indexing format for ease of access to a specific
bit mnemonic.
The following is an example. Assume that the RKOS
diagnostic has produced an error message in which the contents of the
Error Register (RKER) are displayed as octal 100400. To determine the
meaning of the "set" bits, use the Octal Index in Table B-1 to
establish the horizontal positions for the octal values 100000 and
400, and then search across to the bit-map for RKER (registers are in
alphabetic order. by mnemonics)
to find that 100000 indicates DRE
(drive error) and 400 indicates TE (timing error).

B·-1

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
NOTE

The 6-digit octal index values in the
tables each have a space inserted for
ease of visual recognition. The spaces
have no significance.
Table B-10 defines the meaning of the various mnemonics
the register bit-maps.

appearing

Table B-1
RK05(RK05F) Controller Registers
Octal
Index

RKBA

RKCS

RKDA

RKDS

RKER

RKWC

Bit

100
040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

BA15
BA14
BA13
BA12
BAll
BAIO
BA09
BA08
BA07
BA06
BA05
BA04
BA03
BA02
BAOl
BAOO

ERR
HE
SCP
0
BAI
FMT
0
SSE
RDY
IDE
MEXOl
MEXOO
F02
FOl
FOO
GO

US02
USOl

ID02
IDOl
IDOO
DPL
RK05
DRU
SIN
SOK
DRY
ARDY
WPS
SC=SA
SC03
SC02
SCOl

DRE
OVR
WLO
SKE
PGE
NEM
DLT
TE
NED
NEC
NES
0
0
0
CSE
WCE

WC15
WC14
WC13
WC12
WCll
WClO
WC09
WC08
WC07
WC06
WC05
WC04
WC03
WC02
WCOl

15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0

000
000
000
000
000
000
000
400
200
100
040
020
010
004
002
001

usoo

CA07
CA06
CA05
CA04
CA03
CA02
CAOl
CAOO
SUR
SA03
SA02
SAOl
SAOO

scoo

wcoo

~~
"~

Table B-2
RK06 Controller Registers
Octal
Index

RKAS/OF

RKBA

RKCSl

RKCS2

Bit

100
.040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

ATN07
ATN06
ATN05
ATN04
ATN03
ATN02
ATNOl
ATNOO
0
OFS06
OFS05
OFS04
OFS03
OFS02
OFSOl
OFSOO

BA15
BA14
BA13
BA12
BAll
BAIO
BA09
BA08
BA07
BA06
BA05
BA04
BA03
BA02
BAOl
BAOO

ERR
DI
DC PAR
CFMT
C'l'O
CDT
BA17
BA16
RDY

DLT
WCE
UPE
NED
NEM
PGE
MDS
UFE
OR
IR
SCLR
BAI
RLS
US02
USOl

15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0

000
000
000
000
000
000
000
400
200
100
040
020
010
004
002
001

0
F03
F02
FOl
FOO
GO

usoo

(continued on next page)

B-2

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-2 (Cont.)
RK06 Controller Registers

'-''

"-''

'-'

''-1

Octal
Index

RKDA

RKDB

RKDC

RKDS

Bit

100
040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

0
0
0
0
0
TA02
TAOl
TAOO
0
0
0
SA04
SA03
SA02
SAOl
SAOO

DB15
DB14
DB13
DB12
DBll
DBlO
DB09
DB08
DB07
DB06
OBOS
DB04
DB03
DB02.
DBOl
DBOO

0
0
0
0
0
0
DC09
DC08
DC07
DC06
DCOS
DC04
DC03
DC02
DCOl
DCOO

SVAL
CDA
PIP
0
WRL
0
0
DDT
DROY

15
14
13
12

Octal
Index

RKECPS

RKECPT

RKER

RKMRl

Bit

100
040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

0
0
0
EP012
EPOll
EP010
EP009
EP008
EP007
EP006
EPOOS
EP004
EP003
EP002
EPOOl
EPOOO

0
0
0
0
0
EPAlO
EPA09
EPA08
EPA07
EPA06
EPAOS
EPA04
EPA03
EPA02
EPAOl
EPAOO

DCK
UNS
OP!
DTE
WLE
!DAE
COE
HVRC
BSE
ECH
DTYE
FMTE
DRPAR
NXF
SKI
ILF

RDGATE
WRGATE
ECCW
PCD
PCA
MEWD
MERO
MCLK
MIND
MSP
DMD
PAT
MS03
MS02
MSOl
MSOO

15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0

RKMR2-0 RKMR2-l

RKMR2-2

RKMR2-3

Bit

PAR
DSC
PIP
SPON
WRLK
OF FON
FMT
DTYE
DROY

PAR
0
0
OFS08
OFS07
OFS06
OFS05
OFS04
OFS03
OFS02

PAR
DSN3
DSN3
DSN3
DSN3
DSN2
DSN2
DSN2
DSN2
DSNl

15
14
13
12

000
000
000
000
000
000
000
400
200
100
040
020
010
004
002
001

Octal
Index
100
040
020
010
004
002
001
000
000
000

000
000
000
000
000
000
000
400
200
100

PAR
UNLD HOS
RTZ
LD HOS
REV
FWD
SP DOK
CRTP
DRLCH
BHME

DROT
SPLS
ACLO
OFST
0
ORA

"'-"''

10
9
8
7
6
5
4
3
2
1
0

10
9

8
7
6

(continued on next page)

B-3

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS

Table B-2 (Cont.)
RK06 Controller Registers

~
.

Octal
Index
000
000
000
000
000
000

040
020
010
004
002
001

RKMR2-0 RKMR2-l

RKMR2-2

RKMR2-3

Bit

DRA
0
0
US02
USOl

OFSOl
OFSOO
0
US02
USOl

DSNl
DSNl
DSNl
US02
USOl

usoo

5
4
3
2
1
0

usoo

HDHME
TKFOK
0
US02
USOl

usoo

Octal
Index

RKMR3-0

RKMR3-l

RKMR3-2

RKMR3-3

RKWC

Bit

100
040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

PAR
UNS
DROT
SPLS
WLE
SKI
CD PAR
ILF
FLT
ACLO
IVDA
0
0
0
0
0

PAR
SERVO BRAKE
SK LIMIT
SK NO MO
PLO ERR
TRIBIT ERR
INDEX ERR
MLT HD SEL
HD FLT
WRGT NXFR
WRCUR NWRGT
SECT ERR
0
0
0
1

PAR
0
0
CA08
CA07
CA06
CA05
CA04
CA03
CA02
CAOl
CAOO
0
0
1
0

PAR
0
0
0
DECODED
HEAD
ADDRESS
SC04
SC03
SC02
SCOl

WC15
WC14
WC13
WC12
WCll
WClO
WC09
WC08
WC07
WC06
WC05
WC04
WC03
WC02
WCOl

15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0

000
000
000
000
000
000
000
400
200
100
040
020
010
004
002
001

scoo
0
0
1

wcoo

~--·

Table B-3
RP02-RPR02-RP03 Controller Registers
Octal
Index

SUCA

RPBA

RPCA

RPCS

Bit

100
040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

0
0
0
0
0
0
0
CA08
CA07
CA06
CA05
CA04
CA03
CA02
CAOl
CAOO

BA15
BA14
BA13
BA12
BAll
BAlO
BA09
BA08
BA07
BA06
BA05
BA04
BA03
BA02
BAOl
BAOO

0
0
0
0
0
0
0
CA08
CA07
CA06
CA05
CA04
CA03
CA02
CAOl
CAOO

ERR
HE
AIE
MODE
HDR
US02
USOl

15
14
13
12
11
10
9
8
7
6
5
4
3
2
l
0

000
000
000
000
000
000
000
400
200
100
040
020
010
004
002
001

usoo

RDY
IDE
MEXOl
MEXOO
F02
FOl
FOO
GO

(continued on next page)

B-4

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-3 (Cont.)
RP02-RPR02-RP03 Controller Registers
~

·~

Octal
Index

RPDA

RPDS

RPER

RPWC

Bit

100
040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

0
0
0
TA04
TA03
TA02
TAOl
TAOO
SOT03
SOT02
SOTOl
SOTOO
SA03
SA02
SAOl
SAOO

DRDY
OL
RP03
HNF
SKI
SKU
DUNS
WLO
ATN07
ATN06
ATN05
ATN04
ATN03
ATN02
ATNOl
ATNOO

WPV
FUV
NEC
NET
NES
PGE
FMTE
MDER
LPE
WPE
CSE
TE
WCE
NEM
EOP
DERR

WC15
WC14
WC13
WC12
WCll
WClO
WC09
WC08
WC07
WC06
WC05
WC04
WC03
WC02
WCOl

15
14
13
12
ll
10
9
8
7
6
5
4
3
2
l
0

000
000
000
000
000
000
000
400
200
100
040
020
010
004
002
001

wcoo

Table B-4
RP04-RP05-RP06 Controller Registers
*=indicates mnemonic or

bi~

Octal
Index

RPAS

RPBA

100
040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

0
0
0
0
0
0
0
0
ATA07
ATA06
ATA05
ATA04
ATA03
ATA02
ATAOl
ATAOO

Octal
Index
100 000
040 000
020 000

condition unique to the RP06.

RPCC

RPCSl

Bit

BAl5
BA14
BA13
BA12
BAll
BAlO
BA09
BA08
BA07
BA06
BA05
BA04
BA03
BA02
BAOl
BAOO

0
0
0
0
0
0
O(CC09*)
CC08
CC07
CC06
CC05
CC04
CC03
CC02
CCOl

ccoo

SC
TRE
MCPE
0
DRA
PSEL
BAl 7
BA16
RDY
IE
F04
F03
F02
FOl
FOO
GO

15
14
13
12
ll
10
9
8
7
6
5
4
3
2
l
0

RPCS2

RPDA

RPDB

RPDC

Bit

DLT
WCE
PE

0
0
0

DB15
DB14
DB13

0
0
0

15
14
13

'-"'

000
000
000
000
000
000
000
400
200
100
040
020
010
004
002
001

'-""'

(continued on next page)

B-5

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS

Table B-4 (Cont.)
RP04-RP05-RP06 Controller Registers

*==indicates mnemonic or bit condition unique to the RP06.
Octal
Index
010
004
002
001
000
000
000
000
000
000
000
000
000

000
000
000
000
400
200
100
040
020
010
004
002
001

RPAS

RPBA

PRCC

RPCSl

Bit

NED
NEM
PGE
MXF
MOPE
OR
IR
CLR
PAT
BAI
US02
USOl

TA04
TA03
TA02
TAOl
TAOO
0
0
0
SA04
SA03
SA02
SAOl
SAOO

DB12
DBll
DBlO
DB09
DB08.
DB07
DB06
DB05
DB04
DB03
DB02
DBOl
DBOO

0
0
0
0 (DC09*)
DC08
DC07
DC06
DC05
DC04
DC03
DC02
DCOl
DCOO

usoo

10
9
8
7
6
5
4
3
2
1
0

Octal
Index

RPDS

RPDT

RPECl

RPEC2

Bit

100 000
O•aD 000
020 000
010 000
004 000
002 000
001 000
000 400
000 200
000 100
000 040
000 020
000 010
000 004
000 002
000 001

ATA
ERR
PIP
MOL
WRL
LST
PGM
DPR
DRY
VV ( O*)
DEl(O*)
DL64(0*)
GRV(O*)
DIGB(O*)
DF20(0*)
DF5(0*)

0
0
MOH
0
DRQ
0
0
DT08
DT07
DT06
DT05
DT04
DT03
DT02
DTOl
DTOO

0
0
0
EP012
EPOll
EPOlO
EP009
EP008
EP007
EP006
EP005
EP004
EP003
EP002
EPOOl
EPOOO

0
0
0
0
EPAll
EPAlO
EPA09
EPA08
EPA07
EPA06
EPA05
EPA04
EPA03
EPA02
EPAOl
EPAOO

15
14
13
12
11
10

Octal
Index

RPERl

RPER2

RPER3

RPLA

Bit

100
040
020
010
004
002
001
000
000
000

DCK
UNS
OP!
DTE
WLE
r·AE
AOE
HCRC
HCE
ECH

ACU(O*)
0
PLU
30VU(O*)
IXE
NHS
MHS
WRU
FEN(ABS*)
TUF

OCYL
SKI
O(OPE*)
0
0
0
0
0
0
ACL

0
0
0
0
0
SC04
SC03
SC02
SCOl

15
14

000
000
000
000
000
000
000
400
200
100

·~

8
7
6
5

4
3
2
1
0

scoo

"'
·~

12
11

10
9

8
7
6
(continued on next page)

B-6

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-4 {Cont.}
RP04-RP05-RP06 Controller Registers

'-"

'-"'

*==indicates mnemonic or bit condition unique to the RP06.
Octal
Index

RPERl

RPER2

RPER3

RPLA

Bit

000
000
000
000
000
000

WCF
FER
PAR
RMR
ILR
ILF

TDF
MSE {RAW*}
CSU

DCL
0{35F*}
UWR { O*}
0
VUF {WAO*}
PSU(DCU*}

EXTl{EXTOS*}
EXTO{EXT04*}
O{EXT03*}
O{EXT02*}
O{EXTOl*}
O{EXTOO*}

5
4
3
2
1
0

040
020
010
004
002
001

wsu
CSF
wcu

Oc:tal
Index

RPMR

RPOF

RPSN

RPWC

Bit

100
040
020
010
004
002
001
000
000
000
000
000
000
000
OOQ
000

0
0
0
0
0
O{HCD*}
SBD
DFE
DEN
ECCE
MWR
MRD
MSCLK
MIND
MCLK
DMD

SCG
0
0
FMT22
ECI
HCI
0
0
OFS07
OFS06
OF'SOS
OFS04
OFS03
OFS02
OFSOl
OFSOO

DSN4
DSN4
DSN4
DSN4
DSN3
DSN3
DSN3
DSN3
DSN2
DSN2
DSN2
DSN2
DSNl
DSNl
DSNl
DSNl

WC15
WC14
WC13
WC12
WCll
WClO
WC09
WC08
WC07
WC06
WC05
WC04
WC03
WC02
WCOl

15
14
13
12
ll
10
9
8
7

000
000
000
000
000
000
000
400
200
100
040
020
010
004
002
001

5
4
3
2
1
0

wcoo

Table B-5
RFll Controller Registers

'-"'

Octal
Index

RFBA

RFCS

RFDA

RFER

RFWC

Bit

100 000
040 000
020 000
Cl 10 000
Cl 0 4 000
002 000
Cl 01 000
000 400
000 200
000 100
Cl 0 0 040
000 020
000 010
000 004
() 0 0 002
000 001

CA15
CA14
CA13
CA12
CAll
CAlO
CA09
CA08
CA07
CA06
CA05
CA04
CA03
CA02
CAOl
CAOO

ERR
FRZ
WCE
DPE
NED
WLO
MXF
DCLR
RDY
INT-EN
XMl
XMO
MA
1"01
FOO
GO

TA04
TA03
TA02
TAOl
TAOO
WAlO
WA09
WA08
WA07
WA06
WA05
WA04
WA03
WA02
WAOl
WAOO

APE
ATER
BTER
CTER
0
NEM
0
CMA-INH
DRL
0
DA03
DA02
DAOl
DAOO
TA06
TAOS

WC15
WC14
WC13
WC12
WCll
WClO
WC09
WC08
WC07
WC06
WC05
WC04
WC03
WC02
WCOl

15
14
13
12
ll
10
9
8
7

B-7

wcoo

5
4

3
2
1
0

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS

Table B-6
RS03-RS04 Controller Registers
Octal
Index

RSAS

RSBA

RSCSl

RSCS2

Bit

100
040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

0
0
0
0
0
0
0
0
ATA07
ATA06
ATAOS
ATA04
ATA03
ATA02
ATAOl
ATAOO

BA15
BA14
BA13
BA12
BAll
BAlO
BA09
BA08
BA07
BA06
BAOS
BA04
BA03
BA02
BAOl
BAOO

SC
TRE
MCPE
0
DVA
PSEL
Al7
Al6
RDY
IE
F04
F03
F02
FOl
FOO
GO

DLT
WCE
UPE
NED
NEM
PGE
MXF
MDPE
OR
IR
CLR
PAT
BAI
US02
USOl

15
14
13
12

usoo

10
9
8
7
6
5
4
3
2
1
0

Octal
Index

RSDA

RSDS

RSER

RSWC

Bit

100 000
040 000
020 000
010 000
004 000
002 000
001 000
000 400
000 200
000 100
000 040
000 020
000 010
000 004
000 002
000 001

SP03
SP02
SPOl
SPOO
TAOS
TA04
TA03
TA02
TAOl
TAOO
SAOS
SA04
SA03
SA02
SAOl
SAOO

ATA
ERR
PIP
MOL
WRL
LBT
0
DPR
DRY
0
0
0
0
0
0
0

DCK
UNS
OPI
DTE
WLE
IAE
AO
0
0
0
0
0
PAR
RMR
ILR
ILF

WC15
WC14
WC13
WC12
WCll
WClO
WC09
WC08
WC07
WC06

15
14
13
12

000
000
000
000
000
000
000
400
200
100
040
020
010
004
002
001

wcos

WC04
WC03
WC02
WCOl

wcoo

"""
~1'
'

10
9
8
7
6
5
4
3
2
1
0

·~

Table B-7
TU10-TS03 Control Registers
Octal
Index

MTBRC

MTC

!MTCMA

Bit

100
040
020
0 .10
004

BRC15
BRC14
BRC13
BRC12
BRCll

ERR
DENS
DENS
PWRCLR
PEVN

CMA.15
CMA14
CMA13
C.MA12
C.MAll

15
14
13
12

000
000
000
000
000

(continued on next page)

~"'

B-8

........................ ..............................~

··~--------------------.-

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS

Table B-7 (Cont.)
TU10-TS03 Control Registers
Octal
Index

MTBRC

MTC

MTCMA

Bit

002
001
000
000
000
000
000
000
000
000
000

BRClO
BRC09
BRC08
BRC07
BRC06
BRC05
BRC04
BRC03
BRC02
BRCOl
BRCOO

US02
USOl

CMAlO
CMA09
CMA08
CMA07
CMA06
CMA05
CMA04
CMA03
CMA02
CMAOl
CMAOO

000
000
400
200
100
040
020
010
004
002
001

usoo

CUR
IE
0

0
F'02
li'Q 1

FOO
GO

8
7

6
5
4

3
2
l
0

Octal
Index

MTD

MTRD

MTS

Bit

100
040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

RDB07
RDB06
RDB05
RDB04
RDB03
RDB02
RDBOl
PARITY
DB07
DB06
DB05
DB04
DB03
DB02
DBOl
DBOO

TIMER
CHAR.SEL.
BTE GEN
GAP SHUTDN

ILC
EOF
CRE
PAE
BGL
EQT
RLE
BTE
NEM
SELR
BOT
7CH
SDWN
WRL
RWS
TUR

15
14

000
000
000
000
000
000
000
400
200
100
040
020
010
004
002
001

0
0

PARITY
DATA07
DATA06
DATA05
DATA04
DATA03
DATA02
DATAOl
DATAOO

12
11

10
9
8
7
6

5
4

3
2
l
0

Table B-8
TU16-TU45 Control Registers
Octal
Index
100
04:0
020
010
004
002
001
000
000
000

000
000
000
000
000
000
000
400
200
100

MTAS

MTBA

0
0

BA15
BA14
BA13
BA12
BAll
BAlO
BA09
BA08
BA07
BA06

0
0
0
0
0

ATA07
ATA06

MTCK
(NRZI)

MTCK
(PE)

0
0
0
0
0
0

0
0

0
0
0
0
0

CRCP
CRC07
CRC06

DTKP
DTK07
DTK06

MTCSl

Bit

SC
TRE
MCPE
DVA
PSEL

15
14
13
12
ll
10

0
0

RDY
IE

(continued on next page)

B-9

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
TaQ].e B-8 (Cont.)
TU16-TU45 Control Registers

Octal
Index

MTAS

MTBA

MTCK
(NRZI)

MTCK
(PE)

MTCSl

Bit

000
000
000
000
000
000

ATA05
ATA04
ATA0_3
ATA02
ATAOl
ATAOO

BA05
BA04
BA03
BA02
BAOl
BAOO

CRC05
CRC04
CRC03
CRC02
CRCOl
CRCOO

DTK05
DTK04
DTK03
DTK02
DTKOl
DTKOO

F04
F03
F02
FOl
FOO
GO

5
4
3
2
1
0

Octal
Index

MTCS2

MTDB

MTDS

MTDT

MTER

Bit

-100
040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

DLT
WCE
UPE
NED
NEM
PGE
MXF
MDPE
OR
IR
CLR
PAT
BAI
US02
USO!
DSOO

DB15
DB14
DB13
DB12
DBll
DBlO
DB09
DB08
DB07
DB06
DB05
DB04
DB03
DB02
DBOl
DBOO

ATA
ERR
PIP
MOL
WRL
EQT
0
DPR
DRY
SSC
PES
SDWN
IDB
BOT
SLA

1
1
0
0
0
SPR
0
DT08
DT07
DT06
DT05
DT04
DT03
DT02
DTOl
DTOO

COR/CRC
UNS
OPI
DTE
NXF
CS/I TM
FCE
NSG
PEF/LRC
INC/VPE
DPAR
FMT
CPAR
RMR
ILR
ILF

15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0

Octal
Index

MTFC

MTMR

MTSN

MTTC

MTWC

Bit

100
040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

FC15
FC14
FC13
FC12
FCll
FClO
FC09
FC08
FC07
FC06
FC05
FC04
FC03
FC02
FCOl
FCOO

MDF08
MDF07
MDF06
MDF05
MDF04
MDF03
MDF02
MDFOl
MD FOO
200BPI
MC
MOP03
MOP02
MOPOl
MOPOO
MM

DSN3
DSN3
DSN3
DSN3
DSN2
DSN2
DSN2
DSN2
DSNl
DSNl
DSNl
DSNl
DSNO
DSNO
DSNO
DSNO

ACCL
FCS
TCW
EAODTE
0
DEN02
DENOl
DENOO
FMTSEL03
FMTSEL02
FMTSELOl
FMTSELOO
EV PAR
SS02
SSOl

WC15
WC14
WC13
WC12
WCll
WClO
WC09
WC08
WC07
WC06
WC05
WC04
WC03
WC02
WCOl

15
14
13
12

040
020
010
004
002
001

000
000
000
000
000
000
000
400
200
100
040
020
010
004
002
001

B-10

ssoo

wcoo

10
9
8
7
6
5
4
3
2
1
0

-""I\

~---

-- -

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-9
TU56 Controller Registers
Octal
Index
100
040
020
010
004
002
001
000
000
000
000
000
000
000
000
000

000
000
000
000
000
000
000
400
200
100
040
020
010
004
002
001

TCBA

TCCM

TCST

TCWC

Bit

BA15
BA14
BA13
BA12
BAll
BAlO
BA09
BA08
BA07
BA06
BA05
BA04
BA03
BA02
BAOl
BAOO

ERR
0
MAINT
DINHB
REV
US02
USOl

ENDZ
PAR
MTE
ILO
SELE
BLKM
DATM
NEM
UPS
CLK
MMT
DTO
DTl
DT2
XD17
XD16

WC15
WC14
WC13
WC12
WCll
WClO
WC09
WC08
WC07
WC06
WC05
WC04
WC03
WC02
WCOl

15
14
13
12
ll
10
9
8
7
6
5
4
3
2
1
0

usoo

DRY
IE

BA17
BA16
F02
FOl
FOO
GO

wcoo

Table B-10
Glossary of Register Mnemonics
ABS

Abnormal stop

ACCL

Acceleration

ACL

AC low or interrupted

ACLO

AC low or interrupted

ACU

AC unsafe

AIE

Attention interrupt enable

AOE

Address overflow error

APE

Address parity error

ARDY

Access ready

ATA

Attention active

ATER

A-track timing error

ATN

Attention

Bus address

BAI

Bus-address increment inhibit

BGL

Bus gate late
(continued on next page}

B-ll

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-10 (Cont.)
Glossary of Register Mnemonics
BHME

Brushes home

BLKM

Block missed

BOT

Beginning of tape

BHCn

Byte record count

BSE

Bad-sector error

BTE

Bad-tape error

B'l'E GEN

BTE error generation

BTER

_ B-track timing error

Cylinder address

Character check

CDA

Current drive attention

CDP AR

Controller-to-drive parity

CDT

Controller drive type

CF'MT

Controller format

CLK

Maintenance clock

CLR

Controller clear

CMA

Current memory address

CMA-INH

Current memory address,

COE

Cylinder overflow error

COR/CRC

Correctable data error, or CRC error

CPAR

Control-bus parity error

CRC

Cyclic redundancy check

CRCP

CRC parity

CRE

Cyclic redundancy error

CRTP

Cartridge present

CS/I TM

Correctable skew, or illegal tape mark

CSE

Checksum error

CSF

Current sink faiLure

inhibit incrementing

(continued on next page)

B-12

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-10 (Cont.)
Glossary of Register Mnemonics
CSU

Current sink unsafe

CTER

c-track timing error

CTO

Controller timeout error

CUR

Control unit ready

DATM

Data missed

Data bus

Desired cylinder

DCK

Data check error

DCL

DC low or interrupted

DCLD

Disk clear

DCPAR

Drive-to-controller parity

DDT

Disk drive type

DENn

Density select

DERR

Disk error.

DEl

Difference equals 1

DFE

Data field envelope

DFS

Drive forward at 5 inches/second

DF20

Drive forward at 20 inches/second

Drive interrupt

DIGB

Drive to inner guard band

DINHB

Delay inhibit

DL64

Difference less than 64

DLT

Data late error

DMD

Diagnostic mode

JD PAR

Data bus parity error

DPE

Data parity error

DPL

Drive power low

DPR

Drive present

OR of header not found and seek incomplete

(continued on next page)

B-13

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-10 (Cont.}
Glossary of Register Mnemonics
DRA

Drive available

DRE

Drive error

DRL

Data request late

DRLCH

Door latched

DROT

Drive off track

DRPAR

Drive parity error

DRQ

Drive request required

DRU

Drive unsafe

DRDY

Device ready

DRY

Device ready

DSC

Drive status change

DSNn

Device serial number

DTn

Drive type

DTE

Drive timing error

DTKn

Dead track

DTKP

Dead track parity

DTYE

Drive type error

DUNS

Drive unit unsafe

EAODTE

Enable abort on data transfer error

ECCW

ECC word

ECH

Error correction hard

ECI

Error correction inhibit

ENDZ

End zone detected

EOF

End of file

EOP

End of pack

EOT

End of tape

EPA

ECC pattern data

EPO

ECC position data

(BCD)

(continued on next page)

B-14

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-10 (Cont.)
Glossary of Register Mnemonics
EFlR

OR of subsystem errors

EVPAR

Even parity

EXTn

Encoded extension field

Function select

FCn

Frame count

FCE

Frame count error

FCS

Frame count status

FEN

Failsafe enabled
Format error

FLT

Fault

FMT

Format select

FMTE

Format error

FMTSEL

Format select

FMT22

Format select

FRZ

Freeze

FUV

File unsafe violation

FWD

Forward direction

New function issued

GRV

Go reverse

BCE

Header compare error

HCI

Header compare inhibit

HCRC

Header CRC error

HD FLT

Head fault

HDHME

Heads home

HDR

Header

Hard error

HNF

Header not found

HVRC

Header VRC error
(continued on next page)

B-15

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-10 (Cont.)
Glossary of Register Mnemonics
IAE

Invalid address error

IDn

Drive identification

IDAE

Invalid disk address error

IDB

Identification burst

IDE

Interrupt on done

Interrupt enabled

ILC

Illegal command

ILF

Illegal function

ILO

Illegal operation

ILR

Illegal register addressed

INC/VPE

Noncorrectable data, or vertical parity error

Input ready

IVDA

Invalid address

IXE

Index {pulse) error

(or error) enabled

~.
LBT

Last block transferred

LD HDS

Loading heads

LPE

Longitudinal parity error

LST

Last sector transferred

MAI NT

Maintenance

Maintenance clock

MCLK

Maintenance clock

MCPE

Mass-bus control, parity error

MDER

Mode error

MDFn

Maintenance data field

MDPE

Mass-bus data, parity error

MDS

Multiple drive select

MERD

Maintenance encoded read data

MEXn

Memory address extension
(continued on next page)

B-16

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-10 (Cont.)
Glossary of Register Mnemonics
MEWD

Maintenance encoded write data

MHS

Multiple heads selected

MIND

Maintenance index

ML'l~

.......,,

HD SEL

Multiple heads selected

Maintenance mode

MM~r

Maintenance mark track

MODE

Pack format mode

MOH

Moving head device

MOL

Medium online

MOPn

Maintenance operation code

MSE

Motor sequence error

MSP

Maintenance sector pulse

MSn

Message select

MTE

Mark track error

MXF

Missed data transfer

NEC

Nonexistent cylinder

NED

Nonexistent disk

NEM

Nonexistent memory

NES

Nonexistent sector

NET

Nonexistent track

NHS

No head selection

NSG

Nonstandard gap

N:X:F

Nonexecutable function

OCYL

Off cylinder condition

OF FON

Offset on

OFS

Off set

OPST

Off set

Online
(continued on next page)

·~

B-17

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-10 {Cont.)
Glossary of Register Mnemonics
OPE

Operator plug error

OP!

Operation incomplete

Output ready

OVR

Overrun

PAE

Parity error, lateral or LPC

PAR

Parity error

PAT

Parity test

PCA

Precompensation advance

PCD

Precompensation delay

Parity error

PEF/LRC

PE-format error, or LRC error

PES

Phase encoded {PE) status

PEVN

Lateral parity, even

PGE

Program error

PGM

Programmable

PIP

Positioning in program

PLO ERR

Servo signal error

PLU

Phase-locked oscillator unsafe

PSEL

Port select

PSU

Pack speed unsafe

PWRCLR

Power clear

RAW

Read and write

RDBn

Repeat of data bus

RDGATE

Read gate

RDY

Device ready

REV

Reverse direction

RK05

Device is RK05

RLE

Record length error

.•

(continued on next page)

B-18

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-10 (Cont.)
Glossary of Register Mnemonics
RLS

Release unit

RME

RP03

Selected device is an RP03

RTZ

Returning to zero

RWS

Rewind status

Sector address desired

SBD

Sync byte detected

Sector counter

SC==SA

Sector counter equals sector address

SCG

Sign change

SCLR

Subsystem clear

sco

Sector address, lookahead

SCP

Search complete

SDWN

Tape settle down

SECT ERR

Sector error

SELE

Selection error

SELR

Select remote

SK LIMIT

Seek limit

SK NO MO

Seek and no motion

SKE

SE!ek error

SKI

Seek incomplete

SKU

Seek underway

SL,~

Slave attention

SOK

Sector counter OK

SOT

Current sector address

SPn

Spare bits

SP DOK

Speed OK

SPLS

Drive speed loss

SPON

Spindle on
(continued on next page)

8-19

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-10 (Cont.)
Glossary of Register Mnemonics
SPR

Slave present

SSC

Slave status change

SSE

Stop on soft error

SSn

Slave select

SUCA

Selected unit cylinder address

SUR

Surface

SVAL

Status valid

Track address

TCW

Tape control write

TDF

Write-transitions detector failed

Timing error

TKFOK

Servo signal present

Tape mark

TRE

Transfer error

TUF

Write transitions unsafe

TUR

Tape unit ready

UFE

Unit field unsafe

UNLD HDS

Unloading heads

UNS

Drive unsafe

UPE

UNIBUS parity error

UPS

Tape is up to speed

USn

Unit select

UWR

Any unsafe condition except read/write

VUF

Velocity unsafe

Valid volume

Word address

WAO

Write and offset
(continued on next page)

B-20

BIT MAPS FOR DEVICE-CONTROLLER REGISTERS
Table B-10 (Cont.)
Glossary of Register Mnemonics
WC

Word count

WCE

Write check error

WCF'

Write check failed

wcu

Write current unsafe

WLE

Write lock error

WLO

Write lockout error

WPE

Word parity error

WPS

Write protect status

WPV

Write protect violation

WR CUR NWRGT

Write current and no write gate

WRGT NXFR

Write gate and no transitions

WRGATE

Write gate

WRLK

Write lock

WRL

Write lock

WRU

Write ready unsafe

wsu

Write select unsafe

XDn

Extended data

7CH

7- or 9-channel tape

30VU

30-volt DC unsafe

200BPI

200 BPI maintenance clock

B-21

'-"''
SERVICE-MODE KNOWLEDGEABLE USER REFERENCE

Typical Diagnostic Initiation
Device Model No.'s
and Mnemonics
Cartridge Disks:

Underlined text indicates expected or required user input.
Install "scratch" medium, if applicable

On both RSX-llM and RSX-llM-PLUS systems, allocate the device.
RKOS

DKn

>ALLOCATE DBl:

I
On RSX-llM-PLUS systems only, logically mount the volume as foreign.
I

>MOUNT DBl:/FOR

On both RSX-llM and RSX-llM-PLUS systems, proceed as follows.
RK06

DMn

Pack Disks:

START RP04 DIAGNOSTIC - TIME OF DAY.

RP02
RPR02
RP03

DPn
DPn
DPn

RP04
RPOS
RP06

DBn
DBn
DBn

Fixed-head Disks:
RFll
RS03
RS04

DFO
DSn
DSn

Magnetic Tape Units:
TS03
TUlO

MTn
M'.rn

TU16
TU45

MMn
MMn

DECtape Unit:
TU56

DTn

All terminals:
TERM

>RUN $RP04

TTn

DEVICE? DB!
**WARNING** DB!:
RESIDENT DATA.
CONTINUE? SERVICE
TEST PARAMETERS (OCTAL)=
CONSOLE SWITCH FOR INTERVENTION (DECIMAL)=
THE RFll

(DFO) also asks

TEST ALL DRIVES?
WHICH DRIVE?

(Y tests all drives)
(N initiates WHICH inquiry)
(Respond with valid drive number)

GENERAL TEST PARAMETERS OPTIONS
All diagnostics (except for TERM which includes
multipass only) can implement the following general test parameter options.
Refer to the reverse of this reference sheet for device-specific
options and for interactive test inquiries.
Option
Stop on error
Loop on error
Inhibit error message printout
Bell on error
Multipass execution
Limit data-compare messages to
first error only (default is:
messages for up to three
errors during error recovery)

Selection Code
100000
40000
20000
10000
4000
40

All Line Printers:
TERM
LPn
NOTE - TERM is the diagnostic test name for
terminals and line
printers;
output to line printers is not spooled and can interfere
with another user's output.

OTHER TEST PARAMETERS

INTERACTIVE TEST INQUIRIES

PACK AND CARTRIDGE DISKS
Option
Code

INTERACTIVE-ADDRESS TEST - DISKS

Interactive-address test
Interactive-data test
Addressing exercises
Data-reliability exercise
Rc:mdom exercise
Random (fast) exercise
Formatting Routine
FIXED-HEAD DISKS
Option
Interactive-data test
Addressing exercise
Data-reliability exercise
Random exercise
MAGNETIC TAPE UNITS
Option
Drive-compatibility test
Write-read slice adjustment
1600 BPI (MM units only)
All but reliability exercise
Data-reliability exercise

2001
2002

INTERACTIVE-DATA TEST - DISKS
Word count=
Specify sector address?
Cylinder= (not for fixed-head disks)
Track=
Sector=
Pattern No.= (see below)
Write?
Read?

24
10
Code
2002
1
2

DRIVE-COMPATIBILITY TEST

Which compatibility mode?
(W= test tape preparation;
R= read check)

Code
2000
2004
10~

2
Code

Interactive-address test
Interactive-data test
Positioning & data compare
Data-reliability exercise
Stop-start exercise

2001
2002
1
2
4

Hard-copy terminal
Video-display terminal (or LP)
132 Columns
80 columns
72 columns
Interactive pattern test
Select all of the following
Carriage-return exercise only
Spacing exercise only
Tabbing exercise only
Line-feed exercise
Character-set exercise

First cylinder=, Second cylinder=

1
2
4

DECtape UNITS
Option

TERMINALS/LINE PRINTERS
Option

Code
200
0
100
40
0
7
10
1
2
3
4
5

J
df

WRITE-READ SLICE ADJUSTMENT
Slice adjustment?

(W=write;

R=read)

INTERACTIVE-ADDRESS TEST - DECtape

First block=, Second block=

INTERACTIVE~DATA

TEST - DECtape

Byte count=
Specify block address?
Block address=
Pattern No.= (see below)
Write?
Read?
Forward direction?
INTERACTIVE-PATTERN TEST - TERMINALS ONLY
KEYBOARD TEST
TYPE UP TO 132 CHARACTERS •
PATTERNS FOR INTERACTIVE DATA
0 All O's
1 All l's
2 Checkerboard
3 Floating l's
4 Random l's and O's
5 Count pattern (full-word sequential)
6 All patterns in sequence
or, user-specified 6-digit pattern

~
I

, ,_. ,.____·------.--------..---. . . .----------..-i...-~-

RSX-llM/M-PLUS
User Mode Diagnostics
Reference Manual
AA-H271A-TC
READER'S COMMENTS

NOTE:

Th.is 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 th.is manual?
page number ..

If so, specify the error and the

Please indicate the type of reader that you most nearly represent.
[] Assembly language programmer
[] Higher-level language programmer
[] Occasional programmer (experienced)
[] User with little programming experience
[] Student programmer
[] Other (please specify) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __

Name _ _ _.
Organization
St1~eet

Ci t Y - - - - - - - - - - - - - - - - S t a t e - - - - - - - Zip Code _______
or
Country

Do Not Tear- Fold Here and Tape

-I

No Postage
Necessary
if Mailed in the
United States

111111

BUSINESS REPLY MAIL
FIRST CLASS PERMIT N0.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

RT/C SOFTWARE PUBLICATIONS

TW/A14

DIGITAL EQUIPMENT CORPORATION
1925 ANDOVER STREET
TEWKSBURY, MASSACHUSETTS

01876

I~,

-- -

Do Not Tear - Fold Here

::l

,..
I . ·1
I
I
I
~··