Digital PDFs

EK-HSCMA-SV-001

August 1988

551 pages

Original

25MB

Document:	HSC Service Manual
Order Number:	EK-HSCMA-SV
Revision:	001
Pages:	551
Original Filename:

OCR Text

...

EK-HSCMA~SV-001

HSC
Service Manual

mamaama

EK-HSCMA-SV-001

HSC
Service Manual

Prepared by Educational Services
of
Digital Equipment Corporation

August 1988
Digital Equipment COIporation makes no representation that use of its products with those of other manufacturers will not
infringe existing or future patent rights. The descriptions contained herein do not imply the granting of a license to make,
use, or sell equipment or software as described in this manual.
Digital Equipment Cotporation assumes no responsibility or liability for the proper perfonnance of other manufacturers'
products used with its products.
Digital Equipment Corporation believes that infonnation in this publication is accurate as of its publication date. Such
infomlation is subject to change without notice. Digital Equipment Cotporation is not responsible for any inadvertent
errors.
Class A Computing Devices:

NOTICE: This equipment generates, uses, and may emit radio frequency energy. It has been tested and found to
comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC rules for operation
in a commercial environment. This equipment, when operated in a residential area, may cause interference to radiofIV
communications. In such event the user (owner), at his own expense, may be required to take corrective measures.
Copyright e 1988 by Digital Equipment Cotporation

AU Rights Reserved.
Printed in U.S.A.

The following are trademarlcs of Digital Equipment Cotporation:

DECnet

HSC
KDASO
KDBSO
MASSBUSS
MicroVAX
RA60
RA70
SABB

RA81
RA82
RA90
SA482
SA600
TA78-81
TU78-81
RA80

UDASO
UNIBUS
VAX
VAXsimPLUS
VMS

VT
Wotk Processor

mamaama

Contents
About This Manual
1

xix

GENERAL INFORMATION
1.1

INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1

1.2 GENERAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1
HSC70 Cabinet Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2
HSC50 (Modified) Cabinet Layout . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.3
HSC50 Cabinet Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.4
Extemallnterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.5
Internal Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.6
Subsystem Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1
1-3
1-8
1-12
1-17
1-19
1-20

1.3 MODULE DESCRIPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1
Port Link Module (LINK) Functions . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2
Port Buffer Module (PILA) Functions . . . . . . . . . . . . . . . . . . . . . . . .
1.3.3
Port Processor Module (K.pli) Functions and Interfaces . . . . . . . . . . . . . .
Disk Data Channei Module (K.sdi) Functions . . . . . . . . . . . . . . . . . . . .
1.3.4
1.3.5
Tape Data Channel Module (K.sti) Functions . . . . . . . . . . . . . . . . . . . .
1.3.6
Data Channel Module (K.si) Functions . . . . . . . . . . . . . . . . . . . . . . . .
1.3.7
I/O Control Processor Module (p.ioj/c) Functions . . . . . . . . . . . . . . . . . .
1.3.8
Memory Module (M.std2) Functions . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.9
Memory Module (M.std) Functions . . . . . . . . . . . . . . . . . . . . . . . . . .

1-21
1-22
1-23
1-23
1-24
1-24
1-24
1-25
1-25
1-26

1.4 HSC MAINTENANCE STRATEGY . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1
Maintenance Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.2
HSC Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-27
1-28
1-28

1.5

1-30

•

HSC RELATED DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . .

iii

Contents

HSC CONTROLS/INDICATORS
2.1

INTRODUCfION.....................................

2-1

2.2

OPERATOR CONTROL PANEL (OCP) . . . . . . . . . . . . . . . . . . . . . . . .

2-1

2.3

HSC70 INSIDE FRONT DOOR CONTROLS/INDICATORS . . . . . . . . . . . .

2-3

2.4

HSC50 INSIDE FRONT DOOR CONTROLS/INDICATORS .. . . . . . . . . . .

2-6

2.5
HSC50 MAINTENANCE ACCESS PANEL CONTROLS AND CONNECTORS.
2.5.1
dc Power Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.2
HSC50 Maintenance Panel Connectors . . . . . . . . . . . . . . . . . . . . . . . .

2-7
2-7
2-8

2.6 HSC70 MODULE INDICATORS AND SWITCHES . . . . . . . . . . . . . . . . .
2.6.1
HSC70 Module Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

2-8
2-11

2.7
K.si (LOl19) MODULE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
2.7.1
K.si (LOI19) Switch Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

2-12
2-13

2.8
HSC50 MODULE INDICATORS AND SWITCHES . . . . . . . . . . . . . . . ..
2.8.1
HSC50 Module Switches and Jumpers . . . . . . . . . . . . . . . . . . . . . . ..

2-14
2-17

2.9
881 POWER CONTROLLER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
2.9.1
881 Operating Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

2-18
2-19

2.10 HSC50 POWER CONTROLLER . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.10.1 Line Phase Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
2.10.2 Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.10.3 Remote/Off/Local On Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.10.4 Circuit Breakers (60 Hz) . . . . . . . . . . . . . . . . . . . . . . . . . . ~ . . . . .
2.10.5 Circuit Breakers (50 Hz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.10.6 Power Controller (60 Hz)-Rear View . . . . . . . . . . . . . . . . . . . . . . . .
2.10.7 Power Controller (50 Hz)-Rear View . . . . . . . . . . . . . . . . . . . . . . . .

2-22
2-23
2-24
2-25
2-25
2-25
2-25
2-26

REMOVAL AND REPLACEMENT PROCEDURES
3.1

INTRODUCfION.....................................

3-1

3.2

SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1

3.3
HSC70 REMOVAL AND REPLACEMENT PROCEDURES . . . . . . . . . . . .
3.3.1
HSC70 Power Removal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1.1
Removing HSC70 ac Power . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1.2
Removing HSC70 dc Power . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HSC70 Field Replaceable Unit (FRU) Removal. . . . . . . . . . . . . . . . . . .
3.3.2
Access From HSC70 Cabinet Front Door . . . . . . . . . . . . . . . . . . . . .
3.3.2.3
Access From HSC70 Cabinet Back Door . . . . . . . . . . . . . . . . . . . . .
3.3.2.4
HSC70 RX33 Cover Plate and Disk Drive Removal and Replacement . . . . . .
3.3.3
HSC70 RX33 Jumper Configuration . . . . . . . . . . . . . . . . . . . . . . . .
3.3.3.1
HSC70 Operator Control Panel (OCP) Removal and Replacement . . . . . . . .
3.3.4
HSC70 Logic Modules Removal and Replacement . . . . . . . . . . . . . . . . .
3.3.5
HSC70 Airflow Sensor Assembly Removal and Replacement . . . . . . . . . . .
3.3.6
HSC70 Blower Removal and Replacement. . . . . . . . . . . . . . . . . . . . . .
3.3.7

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

3-4
3-4
3-5
3-5
3-9
3-9
3-11
3-17
3-19

Contents

3.3.8
3.3.9
3.3.10

HSC70 Power Controller Removal and Replacement . . . . . . . . . . . . . . . .
HSC70 Main Power Supply Removal and Replacement . . . . . . . . . . . . . .
HSC70 Auxiliary Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-20
3-23

3.4 HSC50 (MODIFIED) REMOVAL AND REPLACEMENT PROCEDURES ... .
HSCSO (Modified) Power Removal . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1
Removing HSCSO (Modified) ac Power . . . . . . . . . . . . . . . . . . . . . .
3.4.1.1
Removing HSCSO (Modified) dc Power . . . . . . . . . . . . . . . . . . . . . .
3.4.1.2
HSCSO (Modified) FRU Removal Sequence . . . . . . . . . . . . . . . . . . . . .
3.4.2
HSCSO (Modified) Cabinet Front Door . . . . . . . . . . . . . . . . . . . . . . . .
3.4.3
HSCSO (Modified) Cabinet Back Door . . . . . . . . . . . . . . . . . . . . . . . .
3.4.4
HSCSO (Modified) TUS8 Bezel Assembly . . . . . . . . . . . . . . . . . . . . . .
3.4.S
HSC50 (Modified) TUS8 Controller Module . . . . . . . . . . . . . . . . . . . . .
3.4.6
HSCSO (Modified) Operator Control Panel (OCP) . . . . . . . . . . . . . . . . .
3.4.7
HSCSO (Modified) Logic Modules Removal and Replacement . . . . . . . . . .
3.4.8
HSCSO (Modified) Airflow Sensor Assembly Removal and Replacement . . . .
3.4.9
3.4.10 HSCSO (Modified) Blower Removal . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.11 HSCSO (Modified) Power Controller Removal and Replacement . . . . . . . . .
3.4.12 HSCSO (Modified) Main Power Supply Removal . . . . . . . . . . . . . . ,: .. .
3.4.13 HSC50 (Modified) Auxiliary Power Supply . . . . . . . . . . . . . . . . . . . . .

3-28
3-28
3-29
3-29
3-30
3-30
3-31
3-31
3-34
3-3S
3-35
3-42
3-44
3-4S
3-48
3-51

3.S
HSCSO REMOVAL AND REPLACEMENT PROCEDURES . . . . . . . . . . . .
3.S.1
Removing HSC50 Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.1
Removing HSC50 ac Power . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.S.1.2
Removing HSC50 de Power . . . . . . . . . . . . . . _ . . . . . . . . . . . . . .
3.S.2
HSC50 FRU Removal Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.3
HSC50 Cabinet Front Door Removal . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.4
HSC50 Cabinet Back Door Removal . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.5
HSC50 TU58 Bezel Assembly Removal . . . . . . . . . . . . . . . . . . . . . . .
3.5.6
HSC50 TU58 Controller Module Removal . . . . . . . . . . . . . . . . . . . . . .
3.5.7
HSC50 Operator Control Panel (OCP) Removal . . . . . . . . . . . . . . . . . .
3.S.8
HSC50 Logic Modules Removal . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.9
HSC50 Blower Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.S.10 HSC50 Airflow Sensor Assembly Removal . . . . . . . . . . . . . . . . . . . . .
3.S.11 HSCSO Power Controller Removal . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.12 HSCSO Main Power Supply Removal. . . . . . . . . . . . . . . . . . . . . . . . .
3.5.13 HSCSO Auxiliary Power Supply Removal . . . . . . . . . . . . . . . . . . . . . .

3-S4
3-S4
3-S6
3-57
3-58
3-S8
3-S9

3-25

3-59
3-62
3-63
3-63
3-6S
3-66
3-67
3-69
3-71

INITIALIZATION PROCEDURES
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1

4.2 HSC CONSOLE TERMINAL CONNECTION . . . . . . . . . . . . . . . . . . . . .
4.2.1
HSC70 Console Terminal Connection . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2
HSC50 or HSCSO (Modified) Auxiliary and Maintenance Tenninal Connections
4.2.3
LA12 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1
4-3
4-5

4.3
HSC70 INITIALIZATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1
lnit P.io Test (INIPIO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-6
4-7

4.1

4-1

Contents

INIPIO Test System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . .
INIPIO Test Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INIPIO Test Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-7
4-7
4-7

4.4 HSC50 INITIALIZATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HSC50 or HSC50 (Modified) Offline Diagnostics Tape . . . . . . . . . . . . . .
4.4.1
lnit P.ioc Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2

4-8
4-8
4-9

HSC FAULT CODE INTERPRETATION . . . . . . . . . . . . . . . . . . . . . . . .

4-9

4.3.2
4.3.3
4.3.4

4.5

DEVICE INTEGRITY TESTS
5.1
INTRODUCTION.....................................
5.1.1
Device Integrity Test Common Areas. . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1.1
Generic Error Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-1
5-1
5-1

5.2 RX33 DEVICE INTEGRITY TESTS (HSC70-ILRX33) . . . . . . . . . . . . . .
ILRX33 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1
ILRX33 Operating Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.2
ILRX33 Test Parameter Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.3
ILRX33 Setting/Clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.4
ILRX33 Progress Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.5
5.2.6
ILRX33 Test Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.7
ILRX33 Error Message Example . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.8
ILRX33 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.9
ILRX33 Test Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

TU58 DEVICE INTEGRITY TESTS (HSC50-ILTU58) . . . . . . . . . . . . . . .

5-5

MEMORY INTEGRITY TESTS (ILMEMY) . . . . . . . . . . . . . . . . . . . . . .
5.4
5.4.1
ILMEMY System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2
ILMEMY Operating Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.3
ILMEMY Progress Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.4
ILMEMY Error Message Example . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.5
ILMEMY Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.6
ILMEMY Test Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-5

5.3

5.5

5-4
5-5

5-6
5-6
5-6
5-6

5-7
5-7

DISK DRIVE INTEGRITY TEST (ILDISK) . . . . . . . . . . . . . . . . . . . . . .
5.5.1
ILDISK System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.2
ILDISK Operating Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.3
ILDISK Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.4
ILDISK Test Parameter Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.5
ILDISK Specifying Requestor and Port. . . . . . . . . . . . . . . . . . . . . . . .
5.5.6
ILDISK Progress Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.7
ILDISK Test Termination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.8
ILDISK Error Message Example . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.9
ILDISK Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.9.1
MSCP Status Codes-ILDISK Error Reports . . . . . . . . . . . . . . . . . . .
5.5.10 ILDISK Test Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-10
5-10

5.6

5-21

TAPE DEVICE INTEGRITY TEST (lLT..t\PE) . . . . . . . . . . . . . . . . . . . . .

5-7
5-8

5-8
5-9
5-9

5-10

5-10
5-11

5-18
5-19

Contents

vii

ILTAPE System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ILTAPE Operating Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ILTAPE User Diaiogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ILTAPE User Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ILTAPE Progress Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ILTAPE Test Termination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ILTAPE Error Message Example . . . . . . . . . . . . . . . . . . . . . . . . . . .
ILTAPE Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ILTAPE Test Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
K.sti/K.si Interface Test Summary . . . . . . . . . . . . . . . . . . . . . . . . .
Formatter Tests Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Sequences Test Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .
Canned Sequence Test Summary . . . . . . . . . . . . . . . . . . . . . . . . . .
Streaming Sequence Test Summary . . . . . . . . . . . . . . . . . . . . . . . .

5-22
5-22
5-23
5-25
5-27
5-27
5-27
5-28
5-30
5-30
5-30
5-30
5-30
5-31

5.7
TAPE CO:MPATffiILITY TEST (ILTCOM) . . . . . . . . . . . . . . . . . . . . . . .
ILTCOM System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.1
ILTCOM Operating Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.2
ILTCOM Test Parameter Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.3
ILTCOM Test Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.4
ILTCOM Error Message Example . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.5
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.5.1
ILTCOM Test Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.6

5-31
5-32
5-33
5-33
5-35
5-35
5-35
5-36

5.8
INLINE MULTIDRIVE EXERCISER (ILEXER) . . . . . . . . . . . . . . . . . . .
5.8.1
ILEXER System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.2
ILEXER Operating Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.3
ILEXER Test Parameter Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IT ,EXER Disk Drive User Prompts . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.4
ILEXER Tape Drive User Prompts . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.5
ILEXER Global User Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.6
ILEXER Data Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.7
ILEXER Setting/Clearing Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.8
ILEXER Progress Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.9
Data Transfer Error Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.9.1
5.8.9.2
Performance Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.9.3
Communications Error Report . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.10 ILEXER Test Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.11 ILEXER Error Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.11.1
Prompt Error Form.at . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.11.2
Data Compare Error Format . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.11.3
Communications Error Format . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.12 ILEXER Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Informational Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.12.1
Generic Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.12.2
Disk Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.12.3
5.8.12.4
Tape Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
5.8.13 ILEXER Test Summaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

5-36

5.6.1
5.6.2
5.6.3
5.6.4
5.6.5
5.6.6
5.6.7
5.6.8
5.6.9
5.6.9.1
5.6.9.2
5.6.9.3
5.6.9.4
5.6.9.5

5-36
5-37
5-38
5-39
5-40
5-41
5-42
5-44
5-44
5-44
5-44
5-46
5-46
5-46
5-47
5-47
5-48
5-48
5-48
5-49
5-50
5-51
5-52

viii

Contents

OFFLINE DIAGNOSTICS
6.1
INTRODUCfION...................................
Offline Diagnostics Software Requirements . . . . . . . . . . . . . . . . . . . . .
6.1.1
Offline Diagnostics Load Procedure. . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.2
P.ioj/c ROM Bootstrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.3
Bootstrap Initialization Instructions . . . . . . . . . . . . . . . . . . . . . . . .
6.1.3.1
Bootstrap Failures . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.3.2
Bootstrap Progress Reports . . . .
6.1.3.3
Bootstrap Error Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.3.4
Bootstrap Failure Troubleshooting . . . . . .
6.1.3.5
Bootstrap Test Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.4
Offline Diagnostics Error Reporting and Message Format . . . . . . . . . . . . .
6.1.5

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

6.2 OFFLINE DIAGNOSTIC LOADER . . . . . . . . . . . . . . . . . . . . . . . . . . .
Offline Diagnostic Loader System Requirements . . . . . . . . . . . . . . . . . .
6.2.1
Offline Diagnostic Loader Prerequisites . . . . . . . . . . . . . . . . . . . . . . .
6.2.2
Operating Instructions for the Offline Diagnostic Loader. . . . . . . . . . . . . .
6.2.3
Offline Diagnostic Loader Commands . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4
IiELP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4.1
SIZE Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4.2
TEST Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4.3
6.2.4.4
LOAD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4.5
START Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4.6
EXAMINE and DEPOSIT Commands. . . . . . . . . . . . . . . . . . . . . . .
6.2.4.6.1
EXAMINE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4.6.2
DEPOSIT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4.6.3
Symbolic Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4.6.4
Repeating EXAMINE and DEPOSIT Commands . . . . . . . . . . . . . . .
6.2.4.6.5
Relocation Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4.6.6
EXAMINE and DEPOSIT Qualifiers (Switches) . . . . . . . . . . . . . . .
6.2.4.6.7
Setting and Showing Defaults . . . . . . . . . . . . . . . . . . . . . . . . ..
6.2.4.6.8
Executing INDIRECT Command Files . . . . . . . . . . . . . . . . .
6.2.5
Offline Diagnostics Unexpected Traps and Interrupts. . . . . . . . . . . . . . ..
6.2.5.1
Trap and Interrupt Vectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
6.2.5.2
Help File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

6-8

6-9
6-9
6-9
6-10
6-10
6-10
6-10
6--11
6--11
6--11
6-11
6--12
6--13
6--13
6--14
6--14
6-15
6--15
6-17

6.3
OFFLINE DIAGNOSTIC WCS LOADER . . . . . . . . . . . . . . . . . . . . . ..
6.3.1
Offline K WCS Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.2
Offline Diagnostic WCS Loader System Requirements . . . . . . . . . . . . . . .
6.3.3
Offline Diagnostic WCS Loader Operating Instructions . . . . . . . . . . . . . .
6.3.3.1
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-17
6-17
6--18
6-18
6--18

6.4
OFFLINE CACIiE TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.1
Offline Cache Test System Requirements. . . . . . . . . . . . . . . . . . . . . . .
6.4.2
Offline Cache Test Operating Instructions .. . . . . . . . . . . . . . . . . . . . .
6.4.3
Offline Cache Test Parameter Entry . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.4
Offline Cache Test Progress Reports . . . . . . . . . . . . . . . . . . . . . . . . .

6-19
6--19
6--19
6-19
6--20

•

••

•

6--4
6--4
6-5
6-8

6-9
6-9

Contents

6.4.5
6.4.5.1
6.4.6
6.4.7

Offline Cache Test Error Information . . . . . . . . . . . . . . . . . . . . . . . ..
Specific Offline Cache Error Messages . . . . . . . . . . . . . . . . . . . . . .
Offline Cache Test Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . ..
Offline Cache Test Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . ..

6-20
6-20
6-23
6-23

6.5
OFFLINE BUS INTERACTION TEST . . . . . . . . . . . . . . . . . . . . . . . ..
6.5.1
Offline Bus Interaction Test System Requirements . . . . . . . . . . . . . . . ..
6.5.2
Offline Bus Interaction Test Prerequisites . . . . . . . . . . . . . . . . . . . . . .
6.5.3
Offline Bus Interaction Test Operating Instructions. . . . . . . . . . . . . . . ..
6.5.4
Offline Bus Interaction Test Parameter Entry . . . . . . . . . . . . . . . . . . . .
6.S.5
Offline Bus Interaction Test Progress Reports . . . . . . . . . . . . . . . . . . ..
6.5.6
Offline Bus Interaction Test Error Information. . . . . . . . . . . . . . . . . . ..
6.5.6.1
Requestor Error Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.6.2
Memory Test Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . ..
6.5.6.3
Error Messages . . . . . . .
6.5.6.4
K Memory Test Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-25
6-26
6-26
6-26
6-27
6-28
6-28
6-29
6-29
6-29
6-32

6.6 OFFLINE K TEST SELECfOR . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
6.6.1
Offline K Test Selector System Requirements . . . . . . . . . . . . . . . . . . . .
6.6.2
Offline K Test Selector Operating Instructions . . . . . . . . . . . . . . . . . . . .
6.6.3
Offline K Test Selector Parameter Entry . . . . . . . . . . . . . . . . . . . . . . .
6.6.4
Offline K Test Selector Progress Reports . . . . . . . . . . . . . . . . . . . . . . .
6.6.5
Offline K Test Selector Error Information . . . . . . . . . . . . . . . .
6.6.5.1
K.d Path Status Information . . . . , ,
6.6.5.2
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6.6
Offline K Test Selector Summaries . . . . . . . . . . . . . . . . . . . . . . . . . .

6-32
6-32
6-32
6-33
6-33
6-34
6-34
6-34
6-39

6.7
OFFLINE KIP MEMORY TEST. . . . . . . . . . . . . . . . . . . . . . . . . . . ..
6.7.1
Offline KIP Memory Test System Requirements . . . . . . . . . . . . . . . . . .
6.7.2
Offline KIP Memory Test Operating Instructions . . . . . . . . . . . . . . . . . .
6.7.3
Offline KIP Memory Test Parameter Entry . . . . . . . . . . . . . . . . . . . . . .
6.7.4
Offline KIP Memory Test Progress Reports ... . . . . . . . . . . . . . . . . . .
6.7.5
Offline KIP Memory Test Parity Errors . . . . . . . . . . . . . . . . . . . . . . . .
6.7.6
Offline KIP Memory Test Error Information . . . . . . . . . . . . . . . . . . . . .
6.7.6.1
Summary Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.7.6.2
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.7.7
Offline KIP Memory Test Summaries . . . . . . . . . . . . . . . . . . . . . . . . .

6-41
6-41
6-41
6-41
6-43
6-43
6-44
6-44
6-45
6-51

6.8
OFFLINE MEMORY TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Offline Memory Test System Requirements . . . . . . . . . . . . . . . . . . . . .
6.8.1
Offline Memory Test Operating Instructions . . . . . . . . . . . . . . . . . . . . .
6.8.2
6.8.3
Offline Memory Test Parameter Entry . . . . . . . . . . . . . . . . . . . . . . . .
Offline Memory Test Progress Reports . . . . . . . . . . . . . . . . . . . . . . . .
6.8.4
Offline Memory Test Parity Errors . . . . . . . . . . . . . . . . . . . . . . . . . .
6.8.5
Offline Memory Test Error Information . . . . . . . . . . . . . . . . . . . . . . .
6.8.6
6.8.6.1
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.8.7
Offline Memory Test Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-51
6-52
6-52
6-52
6-53
6-53
6-53
6-54
6-61

6.9
RX33 OFFLINE EXERCISER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.9.1
RX33 Offline Exerciser System Requirements . . . . . . . . . . . . . . . . . . . .

6-62
6-62

•

••

•

••••••••••••••••

Contents

RX33 Offline Exerciser Operating Instructions___ . . . . . . . . . . . . . . . . . . .
RX33 Offline Exerciser Parameter Entry . . . . . . . . . . . . . . . . . . . . . . .
RX33 Offline Exerciser Progress Reports . . . . . . . . . . . . . . . . . . . . . .
RX33 Offline Exerciser Error Information . . . . . . . . . . . . . . . . . . . . . .
Specific RX33 Offline Exerciser Error Messages . . . . . . . . . . . . . . . . .
RX33 Offline Exerciser Test Summaries . . . . . . . . . . . . . . . . . . . . . . .
RX33 Offline Exerciser Data Patterns. . . . . . . . . . ". . . . . . . . . . . . . . .

6-62
6-62
6-63
6-64
6-64
6-67
6-68

6.10 OFFLINE REFRESH TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.10.1 Offline Refresh Test System Requirements . . . . . . . . . . . . . . . . . . . . . .
6.10.2 Offline Refresh Test Operating Instructions . . . . . . . . . . . . . . . . . . . . .
6.10.3 Offline Refresh Test Parameter Entry . . . . . . . . . . . . . . . . . . . . . . . . .
6.10.4 Offline Refresh Test Progress Reports . . . . . . . . . . . . . . . . . . . . . . . .
6.10.5 Offline Refresh Test Error Information . . . . . . . . . . . . . . . . . . . . . . . .
6.10.5.1
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.10.6 Offline Memory Refresh Test Summaries . . . . . . . . . . . . . . . . . . . . . .

6-68
6-68
6-69
6-69
6-69
fr70
fr70
fr71

6.11 OFFLINE OPERATOR CONTROL PANEL (OCP) TEST . . . . . . . . . . . . . .
6.11.1 Offline OCP Test System Requirements . . . . . . . . . . . . . . . . . . . . . . .
6.11.2 Offline OCP Test Operating Instructions . . . . . . . . . . . . . . . . . . . . . . .
6.11.3 Offline OCP Test Parameter Entry. . . . . . . . . . . . . . . . . . . . . . . . . . .
6.11.4 Offline OCP Test Error Information. . . . . . . . . . . . . . . . . . . . . . . . . .
6.11.4.1
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.11.5 Offline OCP Test Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.11.6 Offline OCP Registers and Displays via ODT .". . . . . . . . . . . . . . . . . . .
6.11.6.1
Switch Check via ODT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.11.6.2
Lamp Bit Check via ODT . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
6.11.6.3
Secure/Enable Switch Check via ODT. . . . . . . . . . . . . . . . . . . . . ..
6.11.6.4
State LED Check via ODT . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

fr71
fr71
fr71
fr72
fr73
fr73
fr74
6-76
fr76
fr78
6-78
fr80

6.9.2
6.9.3
6.9.4
6.9.5
6.9.5.1
6.9.6
6.9.7

UTILITIES
7.1

INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-1

7.2 OFFLINE DISK UTILITY (DKUTIL). . . . . . . . . . . . . . . . . . . . . . . . ..
7.2.1
DKUTIL Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.2
DKUTIL Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.3
DKUTIL Command Modifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.4
DKUTIL Sample Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5
DKUTIL Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5.1
DEFAULT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5.2
DISPLAY Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5.3
DUMP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5.4
EXIT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5.5
GET Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
7.2.5.6
POP Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
7.2.5.7
PUSH Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
7.2.5.8
REVECTOR Command ". . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

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

7-6
7-7
7-8
7-10
7-10
7-11
7-11
7-11

Contents

SET Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5.9
Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5.10
DKUTIL Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.6
Error Message Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.6.1
7.2.6.2
Error Message Severit'j Levels . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.6.3
Fatal Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.6.4
Information and Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . .

7-12
7-12

7-13
7-13
7-13
7-13
7-13

7.3
OFFLINE DISK VERIFIER UTILITY (VERIFY) . . . . . . . . . . . . . . . . . . .
VERIFY Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.1
VERIFY Sample Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.2
VERIFY
Error and Information Messages . . . . . . . . . . . . . . . . . . . . . .
7.3.3
Variable Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.3.1
Error Message Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.3.2
Fatal Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.3.3
Warning
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.3.4
Type Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.3.5
Informational Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
7.3.3.6

7-15
7-16
7-17
7-18
7-18
7-18
7-19
7-19
7-20
7-21

7.4 OFFLINE DISK FORMATTER UTILITY (FORMAT) . . . . . . . . . . . . . . ..
7.4.1
FORMAT Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FORMAT Sample Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4.2
FORMAT Errors and Information Messages . . . . . . . . . . . . . . . . . . . . .
7.4.3
Error Message Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4.3.1
Message Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4.3.2
Fatal Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4.3.3
Warning Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4.3.4
Information Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4.3.5
7.4.3.6
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Success Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4.3.7

7-22
7-22
7-23
7-24
7-24
7-25
7-25
7-26
7-26
7-27
7-27

7.5 RX FORMAT UTILITY (RXFMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5.1
RXFMT Initiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
7.5.2
RXFMT Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

7-27
7-27
7-28

7.6 VIDEO TERMINAL DISPLAY (VTDPY) . . . . . . . . . . . . . . . . . . . . . ..
7.6.1
VTDPY CTRL/x Display Commands. . . . . . . . . . . . . . . . . . . . . . . . .
7.6.2
VTDPY Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VTDPY Display Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.6.3
7.6.3.1
Display Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.6.3.2
Free Lists and Pool Size Display Explanation . . . . . . . . . . . . . . . . . .
Data Bandwidth Display Explanation . . . . . . . . . . . . . . . . . . . . . . .
7.6.3.3
7.6.3.4
Host Connection Display Explanation . . . . . . . . . . . . . . . . . . . . . . .
Host Path Status Display Explanation . . . . . . . . . . . . . . . . . . . . . . .
7.6.3.5
7.6.3.6
Process Priority Status Display Explanation. . . . . . . . . . . . . . . . . . . .
7.6.3.7
Disk or Tape Status Display Explanation . . . . . . . . . . . . . . . . . . . . .

7-30
7-30
7-30
7-31
7-31
7-31
7-32
7-32
7-32
7-33
7-34

7.7 DISK RCf/FCT MERGE UTILITY (DKRFCf) . . . . . . . . . . . . . . . . . . . .
7.7.1
DKRFCT Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.7.2
DKRFCT Sample Session .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-34
7-34
7-35

xii

Contents

7.7.3
7.7.3.1
7.7.3.2
7.7.3.3

DKRFCT Error Message Severity Levels . . . . . . . . . . . . . . . . . . . . . .
Fatal Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Information Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

7-36
7-36
7-37
7-37

TROUBLESHOOTING TECHNIQUES
8.1

INTRODUCTION . . . . . . . '. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-1

8.2

HOW TO USE THIS CHAPTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-1

INITIALIZATION ERROR INDICATIONS . . . . . . . . . . . . . . . . . . . . . .
8.3
OCP Fault Code Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.1
OCP Fault Code Interpretation . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.1.1
HSC Module LEOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.2
P.ioj/c LEOs . . . . . . . . . . . . . . . . . . , . . . . . , . . . . . . . . . . . . .
8.3.2.1
Power-up Sequence of I/O Control Processor LEOs . . . . . . . . . . . . . . .
8.3.2.2
Memory Module LEOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.2.3
8.3.2.4
Data Channel LEOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.2.5
Host Interface LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.3
Communication Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3.4
Requestor Status for Nonfailing Requestors . . . . . . . . . . . . . . . . . . . . .
8.3.5
HSC70 Boot Flow and Troubleshooting Chart . . . . . . . . . . . . . . . . . . . .
8.3.6
HSC50 (Modified) or HSC50 Boot Flow and Troubleshooting Chart. . . . . . .
8.3.7
Boot Diagnostic Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-2
8-2
8-3
8-8
8-8
8-9
8-10
8-10
8-10
8-11
8-12
8-12
8-18
8-23

8.4
SOFIWARE ERROR MESSAGES . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.1
Mass Storage Control Protocol Errors . . . . . . . . . . . . . . . . . . . . . . . .
8.4.2
MSCprrMSCP Error Format, Description, and Flags . . . . . . . . . . . . . . . .
8.4.2.1
Error Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.2.2
Error Message Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.2.3
Format Type Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.2.4
Error Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.2.5
Controller Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.2.6
MSCP SOl Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.2.7
Disk Transfer Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.3
Bad Block Replacement Errors (BBR) . . . . . . . . . . . . . . . . . . . . . . . .
8.4.4
TMSCP-Specific Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.4.1
STI Communication or Command Errors . . . . . . . . . . . . . . . . . . . . .
8.4.4.2
STI Formatter Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.4.3
STI Drive Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.4.4
Breakdown of GEOS Text Field . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.4.5
Breakdown of GSS Text Field . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.4.6
GSS Text Field Bit Interpretation . . . . . . . . . . . . . . . . . . . . . . . . .

8-23
8-23
8-23
8-24
8-24
8-25
8-25
8-26
8-26
8-31
8-34
8-36
8-37
8-37
8-38
8-41

8-42
8-43

Contents

8.4.5
Out-of-Band Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
8.4.5.1
RX33 Load Device Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
8.4.5.2
Disk Functional Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
8.4.5.3
Tape Functional Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
8.4.5.4
Miscellaneous Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
8.4.6
Traps...........................................
8.4.6.1
NXM (Trap through 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.6.2
Reserved Instruction (Trap through 10) . . . . . . . . . . . . . . . . . . . . ..
8.4.6.3
Parity Error (Trap through 114). . . . . . . . . . . . . . . . . . . . . . . . . ..
8.4.6.4
Level 7 K Interrupt (Trap through 134) . . . . . . . . . . . . . . . . . . . . ..
8.4.6.5
Control Bus Error Conditions (Hardware-Detected) . . . . . . . . . . . . . ..
8.4.6.5.1
Level 7 K Interrupt Printout . . . . . . . . . . . . . . . . . . . . . . . . . ..
8.4.6.6
MMU (Trap through 250) . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

8-46
8-46
8-49
8-49
8-49
8-49
8-49
8-50
8-50
8-50
8-50
8-51
8-53

ALPHABETICAL LISTING OF SOFTWARE ERROR MESSAGES . . . . . . ..

8-55

8.5

HSC INTERNAL CABLING DIAGRAMS
A.1 INTRODUCTION.....................................
A.l.l
HSC70 Internal Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.1.2
HSC50 (Modified) Internal Cabling . . . . . . . . . . . . . . . . . . . . . . . . ..
A.1.3
HSC50 Internal Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xiii

A-I
A-I
A-7
A-14

EXCEPTION CODES AND MESSAGES
B.l

OVERVIEW.........................................

B-1

B.2

CRASH DUMP PRINTOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-1

B.3

SINI-E ERROR PRINTOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-2

B.4

SOFTWARE PERFORMANCE REPORT (SPR) SUBMISSION. . . . . . . . . . .

B-2

B.5

EXCEPTION MESSAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-5

HSC GENERIC ERROR LOG FIELDS
C.l

HSC GENERIC ERROR LOG FIELDS. . . . . . . . . . . . . . . . . . . . . . . . .

C-1

C.2

HSC ERROR FLAGS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C-1

C.3

MSCP{fMSCP STATUS OR EVENT CODES . . . . . . . . . . . . . . . . . . . . .

C-2

INTERPRETATION OF STATUS BYTES
0.1

INTRODUCTION.....................................

0-1

0.2

EXAMPLE EXAMINATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

0-3

0.3

ANALYZING K-DETECTED FAILURE CODES . . . . . . . . . . . . . . . . . ..

0-3

xiv

Contents

HSC REVISION MATRIX CHART
INTRODUcrION .
Eo1
HSC70 Revision Matrix Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Eol.1
HSC50 (Modified) Revision Matrix Chart . . . . . . . . . . . . . . . . . . . . . .
Eol.2
HSC50 Revision Matrix Chart . . . . . . . . . . . . . . . . . . . . . .
E.1.3
0

•

•••••••••

•••••

••••••••••••••

•

B-1
B-1
E-6
B-l1

Examples
8-1
8-2
8-3

MSCprrMSCP Error Message Format
Controller Error Message Example
SDI Error Printout
8-4 Disk Transfer Error Printout . . . . . . . .
8-5 Bad Block Replacement Error Printout. . . . . . . . . . . . . . . . . . . . . . . ..
8-6 STI Communication or Command Error Printout. . . . . . . . . . . . . . . . . ..
8-7 STI Formatter Error Log Printout. . . . . . . . . . . . . . . . . . . . . . . . . . ..
8-8 STI Drive Error Log Printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-9 Tape Drive Related Error Message . . . . . . . . . . . . . . . . . . . . . . . . . ..
8-10 Additional Tape Drive-Related Error Message. . . . . . . . . . . . . . . . . . . ..
0

•

••

0 . . . . . .

•

••

•

•••••••••••

•

••

•

••

8-24
8-26
8-27
8-32
8-35
8-37
8-37
8-38
8-41
8-42

Figures
1-1 Redundant Cluster Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2 HSC70 Cabinet-Front View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-3 HSC7O--Inside Front View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4 HSC70 Module Utilization Label Example. . . . . . . . . . . . . . . . . . . . . . .
1-5 HSC7O--Inside Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-6 HSC50 (Modified) Cabinet-Front View. . . . . . . . . . . . . . . . . . . . . . . .
1-7 HSC50 (Modified}-Inside Front View . . . . . . . . . . . . . . . . . . . . . . . . .
1-8 HSC50 (Modified) Module Utilization Label Example. . . . . . . . . . . . . . ..
1-9 HSC50 (Modified}-Inside Rear View . . . . . . . . . . . . . . . . . . . . . . . ..
1-10 HSC50 Cabinet-Front View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
1-11 HSC50 Cabinet-Inside Front View. . . . . . . . . . . . . . . . . . . . . . . . . ..
1-12 HSC50 Module Utilization Label Example. . . . . . . . . . . . . . . . . . . . . ..
1-13 HSC50 Cabinet-Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
1-14 HSC50 Inside Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
1-15 HSC70 External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
1-16 HSC50 (Modified) and HSC50 External Interfaces. . . . . . . . . . . . . . . . ..
1-17 HSC Internal Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
1-18 HSC Subsystem Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
1-19 Memory Map (M.std2-LOI17) ... . . . . . . . . . . . . . . . . . . . . . . . . ..
1-20 Memory Map (M.std-LOI06) . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
1-21 HSC Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
2-1 Operator Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2 Controls/lIidicators-Inside Front Door . . . . . . . . . . . . . . . . . . . . . . . . .
2-3 RX33 and dc Power Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4 HSC50 Controls/lndicators-Inside Front Door . . . . . . . . . . . . . . . . . . . .
2-5 HSC50 Maintenance Access Panel . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3
1-4
1-5
1-6
1-7
1-8
1-9
1-10
1-11
1-12
1-13
1-14
1-15
1-16
1-17
1-18
1-19
1-21
1-26
1-27
1-29
2-2
2-4
2-5
2-6
2-7

Contents

2-6 Module LED Indicators .
2-7 HSC70 Module Utilization Label Exanlple
o.
2-8 Module (DIP) Switches
2-9 Kosi (L0119) LEOs and Switchpack
2-10 HSC50 Module LED Indicators ...
2-11 HSCSO Module Utilization Label Example
2-12 HSCSO Baud Rate Jumper o . . . . . .
2-13 Power Controller-Front Panel Controls
o.
2-14 881 Rear Panel
2-1S HSCSO Power Controller (60 Hz)--Front View
2-16 HSCSO Power Controller (SO Hz)--Front View . . . . .
2-17 HSCSO Power Controller (60 Hz)--Rear View . . . . . . . . . .
2-18 HSCSO Power Controller (SO Hz)--Rear View ..
3-1 HSC70 881 Power Controller Circuit Breaker . . . .
3-2 HSC70 dc Power Switch Location .
3-3 HSC70 FRU Removal Sequence
3-4 HSC70 RX33 Cover Plate Removal.
3-S HSC70 RX33 Disk Drive Removal ..
3-6 HSC70 RX33 Jumper Configurations . . . . .
3-7 HSC70 Operator Control Panel Removal . .
3-8 HSC70 Card Cage Cover Removal .
3-9 HSC70 Node Address Switches (L0100) LINK Module
3-10 HSC70 Node Address Switches L0100, Rev-E2 or L01l8 LINK Module 0...
3-11 HSC70 L01t8 LINK Module, Rev-A Jumper Configuration . . . . . . . .
o.
3-12 HSC70 LOl18 LINK Module, Rev-B1 Jumper Configuration . . . . . . . .
3-13 HSC70 L01l8 LINK Module, Rev-B2 Jumper Configuration ..
3-14 HSC70 Airflow Sensor Assembly Removal . . . . . . . . . . . . . . . . . . . . ..
3-1S HSC70 Main Cooling Blower Removal .
3-16 HSC70 Power Controller Removal .
3-17 HSC70 881 Power Controller-Rear Panel ...
3-18 HSC70 Main Power Supply Cables-Disconnection
3-19 HSC70 Main Power Supply Removal
3-20 HSC70 Auxiliary Power Supply Cable Disconnection . . . . . . .
3-21 HSC70- Auxiliary Power Supply Removal . . . .
3-22 HSCSO (Modified) 881 Power Controller Circuit Breaker . . . . . . . . . . . . ..
3-23 HSCSO (Modified) Maintenance Access Panel. .
3-24 HSCSO (Modified) FRU Removal Sequence . . . . .
3-2S HSCSO (Modified) TUS8 Bezel Assembly Removal . . . . . . . . .
3-26 HSCSO (Modified) Operator Control Panel Removal. . . . . . . . . . . . . . . ..
3-27 HSCSO (Modified) TUS8 Controller Removal . . . .
3-28 HSCSO (Modified) Card Cage Cover Removal . . . . . . . . . . . . . . . . . . . .
3-29 HSCSO (Modified) I/O Control Processor Module Baud Rate Jumper . . . . . ..
3-30 HSC50 (Modified) Node Address Switches (L0100) LINK Module. . . . . . ..
3-31 HSCSO (Modified) Node Address Switches LOIOO, Rev-E2 or (LOI18) LINK
Module
3-32 HSCSO (Modified) LOl18 LINK Module, Rev-A Jumper Configuration . . . . o.
0

•••••••

•

••

•

•••

•

••••••••

•

•••

•

••••

•••

•

••••

••

•

••

•

••

•

••

• • • • • • • • • • • • • • •

•

••

•

••

•••

•••••

•

••••

•

••••••

•

•••

•

•••

••

••••

•

•••

•

•••

•

••

•

••

•

••

•

••

•

•••••••••••••

•

••

•

••

•••

•

••

•••

•

••

•••••

••

•

••

•

••

•••

•

• • • • • • • • • •

•

••

•

••

•

••

•

••

•

••

•

••

•

•••

••

•

•••••

•

••

•

• • • • • • • • • •

•

••

• • • • • • • • •

•

•••

• • • • • • • • • • • • • •

•

••

2-9
2-10
2-12
2-13
2-1S
2-16
2-18
2-20
2-22
2-23
2-24
2-26
2-27
3-2
3-3
3-4
3-S
3-7
3-8
3-10
3-11
3-13
3-14
3-1S
3-16
3-17
3-18
3-19
3-21
3-22
3-24
3-2S
3-26
3-27
3-28
3-29
3-30
3-32
3-33
3-34
3-36
3-37
3-38
3-39
3-40

xvi

Contents

3-33 HSC50 (Modified) LOl18 LINK Module, Rev-Bl Jumper Configuration . . . ..
3-41
3-34 HSC50 (Modified) LOl18 LINK Module, Rev-B2 Jumper Configuration . . . ..
3-42
3-43
3-35 HSC50 (Modified) Airflow Sensor Assembly Removal . . . . . . . . . . . . . . .
3-36 HSC50 (Modified) Main Cooling Blower Removal . . . . . . . . . . . . . . . . ..
3-44
3-37 HSC50 (Modified) 881 Power Controller Removal. . . . . . . . . . . . . . . . ..
3-46
3-38 HSC50 (Modified) 881 Power Controller-Rear Panel. . . . . . . . . . . . . . ..
3-47
3-39 HSC50 (Modified) Main Power Supply Cables-Disconnection . . . . . . . . . .
3-49
3-40 HSC50 (Modified) Main Power Supply Removal. . . . . . . . . . . . . . . . . ..
3-50
3-41 HSC50 (Modified) Auxiliary Power Supply Cable Disconnection .. . . . . . ..
3-52
3-42 HSC50 (Modified) Auxiliary Power Supply Removal . . . . . . . . . . . . . . . .
3-53
3-43 HSC50 Power Controller-Front View (60 Hz) . . . . . . . . . . . . . . . . . . ..
3-55
3-44 HSC50 Power Controller-Front View (50 Hz) . . . . . . . . . . . . . . . . . . ..
3-56
3-45 HSC50 Maintenance Access Panel . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-57
3-46 HSC50 FRU Removal Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . ..
3-58
3-47 HSC50 TU58 Bezel Assembly Removal . . . . . . . . . . . . . . . . . . . . . . ..
3-60
3-48 HSC50 Operator Control Panel Removal . . . . . . . . . . . . . . . . . . . . . . ..
3-61
3-49 HSC50 TU58 Controller Removal . . . . . . . . . . . . . . . . . . . . . . . . . . ..
3-62
3-50 HSC50 Card Cage Cover Removal . . . . . . . . . . . . . . . . . . . . . . . . . ..
3-64
3-51 HSC50 Main Cooling Blower Removal . . . . . . . . . . . . . . . . . . . . . . . .
3-66
3-52 HSC50 Airflow Sensor Assembly Removal . . . . . . . . . . . . . . . . . . . . ..
3-67
3-68
3-53 HSC50 Power Controller Removal . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-54 HSC50 Main Power Supply Cables-Disconnection . . . . . . . . . . . . . . . ..
3-70
3-55 HSC50 Main Power Supply Removal. . . . . . . . . . . . . . . . . . . . . . . . ..
3-71
3-56 HSC50 Auxiliary Power Supply Cables-Disconnection . . . . . . . . . . . . . ..
3-72
3-57 Auxiliary Power Supply Removal . . . . . . . . . . . . . . . . . . . . . . . . . . ..
3-73
4-1 HSC70 Console Tenninal Connection. . . . . . . . . . . . . . . . . . . . . . . . . .
4-2
4-2 Connecting an Auxiliary or Maintenance Terminal (HSC50 or HSC50 [Modified]) 4-4
4-3 Operator Control Panel Fault Code Displays . . . . . . . . . . . . . . . . . . . . .
4-10
6-1 P.ioj Switch Display Register Layout . . . . . . . . . . . . . . . . . . . . . . . . ..
6-77
6-2 P.ioj Control and Status Register Layout . . . . . . . . . . . . . . . . . . . . . . ..
6-79
8-3
8-1 Operator Control Panel Fault Codes. . . . . . . . . . . . . . . . . . . . . . . . . . .
8-2 HSC70 Boot Flow and Troubleshooting Chart. . . . . . . . . . . . . . . . . . . ..
8-13
8-3 HSC50 (Modified) or HSC50 Boot Flow and Troubleshooting Chart . . . . . ..
8-19
8-4 Request Byte Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
8-29
8-5 Mode Byte Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
8-29
8-6 Error Byte Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
8-30
8-7 Controller Byte Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-31
8-8 GSS Text Field Bits Summary Breakdown. . . . . . . . . . . . . . . . . . . . . ..
8-43
8-9 RX33 Floppy Controller CSR Breakdown . . . . . . . . . . . . . . . . . . . . . ..
8-47
8-10 RX33 Error Message Last Line Breakdown. . . . . . . . . . . . . . . . . . . . ..
8-48
8-11 MMSRO Bit Breakdown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
8-54
A-I HSC70 Internal Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
A-2
A-2 HSC50 (Modified) Internal Cabling . . . . . . . . . . . . . . . . . . . . . . . . . ..
A-8
A-3 HSC50 Internal Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. A-IS
E-l HSC70 Revision Matrix Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E-2
E-2 HSC50 (Modified) Revision Matrix Chart . . . . . . . . . . . . . . . . . . . . . . .
E-7

Contents

E-3

xvii

E-12

HSC50 Revision Matrix Chart

Tables
1-1 HSC Content Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2 Module Nomenclature . . . . .
2-1 Functions of Logic Module LEDs .
2-2 Kosi Switchpack Options
2-3 HSC50 Functions of Logic Module LEDs . . .
5-1 ILTAPE Test Levels . . . . .
o.
5-2 ILTCOM Header Record .
5-3 ILTCOM Data Patterns o ..
6-1 RX33 Error Table . . . . . .
6-2 RX33 Error Code Table
8-1 UPAR Register Addresses.
8-2 Control Program Bits
8-3 Status of Requestors for Level 7 Interrupt
8-4 LOI11-0 (P.ioj/c) LEOs o.
8-5 L0117 (Mostd2) and LOI06 (Mostd) LEDs .
8-6 LOI08-YA/YB (Kosdi/Kosti) L0119 (Kosi) LEDs
8-7 Koci (LINK, PILA, Kopli) LEDs
8-8 MSCP/TMSCP Error Message Field Descriptions
8-9 Error Message Format Type Code Numbers
8-10 MSCP{fMSCP Error Flags
8-11 MSCP/TMSCP Controller Error Message Field Descriptions ..
8-12 SDI Error Printout Field Descriptions
8-13 Request Byte Field Descriptions
8-14 Mode Byte Field Descriptions
8-15 Error Byte Field Descriptions
8-16 Controller Byte Field Descriptions.
8-17 Disk Transfer Error Printout Field Descriptions
8-18 Original Error Flags Field Descriptions ..
8-19 Recovery Flags Field Definitions
8-20 Bad Block Replacement Error Printout Field Definitions .
o'
8-21 Replace Flags Bit Descriptions . .
8-22 STI Communication or Command Error Printout Field Descriptions
8-23 STI Formatter Error Log Field Descriptions
8-24 STI Formatter E Log o.
8-25 STI Drive Error Log Field Descriptions
o'
8-26 GEDS Text
8-27 STI Drive Error Log (TA78 Drive Product Specific)
8-28 Status Register Summary
B-1 Obtaining Data Structure Information
C-l Generic Error Log Fields . .
C-2 Error Flags . . . . .
C-3 MSCP/TMSCP Status or Event Codes . . . . .
0-1 K.ci Status Bytes
0

0.'

• • • • • • • • • • • • • •

•

••

•

••

••••

••

•

• • • • • •

••

•

••

•

• • • • • • • •

••

•

••

•

••••

•

••

•••

•

• • • • • •

•

•••••

•

•••

•

••

•

••••

•

••

•

•••

•

••

•••

••

•••

••

•

••

•

••

•

••

•

•••••

•

••

•

••

•

•••

•

••

•

••

•••

•

••

•

••

•

••

•

••

•••••

•

••••

• • • • • • • • • • •

•

••

•

••

•

1-2
1-22
2-10
2-14
2-16
5-27
5-31
5-32
6-6
6-7
8-6
8-7
8-8
8-9
8-10
8-10
8-11
8-24
8-25
8-25
8-26
8-27
8-29
8-30
8-30
8-31
8-32
8-33
8-34
8-35
8-36
8-37
8-37
8-38
8-38
8-39
8-39
8-48
B-4
C-1
C-2
C-2
D-4

xviii

Contents

0-2 K.sdi/K.si Status Bytes ...
0-3 K.sti/K.si Status Bytes . . . . . . . . .
0

•

0-8
0-10

About This Manual
This manual describes the HSC70. HSC50 (modified), and HSC50 subsystems. It describes HSC
controls and indicators, error reporting, field replaceable units, troubleshooting, and diagnostic
procedures. All information in this manual is informational/instructional and is designed to assist field
service personnel with HSC maintenance. Operational theory is included wherever such background is
helpful to field service.
Installation procedures, most HSC utilities, and indepth technical descriptions are not included in this
manual. For source material on these and other subjects not within the scope of this manual, refer to
the list of related documentation at the end of Chapter 1.
This document replaces the HSC50 Service Manual (EK-HSC50-SV-002) and the HSC70 Sell,ice
Manual (EK-HSC70-SV-002).

xix

1-1
GENERAL INFORMATION

1
GENERAL INFORMATION
1.1

INTRODUCTION

This chapter includes general infonnation about the Hierarchical Storage Controllers (HSC) mass
storage server, including:
•

Subsystem block diagrams

•

Packaging and logic module descriptions

•

Maintenance features

•

Physical specifications
Related documentation

1.2 GENERAL JNFORMATION
This manual provides a single source of infonnation for servicing the Hierarchical Storage Control1ers
HSC70, HSC50 (modified), and HSC50. The descriptions and procedures in this manual apply to all
models of the HSC with the differences between the HSC70, HSC50 (modified), and HSC50 noted.
In this manual the tenn HSC50 (modified) refers to the HSC50 manufactured with some components
previously used only on the HSC70 .. The following list specifies the components of the HSC50
(modified) that differ from the HSC50.

•

Front and back door assemblies

•

Model 881 power controller (30-24374)

•

Cabling bulkhead

•

Cooling air outlet duct

The serial numbers differentiating the HSC50 (modified) are:
•

HSC50-AA, including and subsequent to serial number 7770

•

HSC50-AB, including and subsequent to serial number 53018

Table 1-1 lists the component differences of the HSC70, HSC50 (modified), and the HSC50.

1-2
GENERAL INFORMATION

Table 1-1

HSC Content Differences

HSC50
HSC Contents

HSC70

(Modified)

HSC50

Number of data channels

Power controller

30-24374

70-19122

Load devices

RX33

TU58

Defined as a disk and/or tape subsystem, the HSC can interface with multiple hosts using the computer
interconnect (CI) bus. One CI bus is included with the subsystem. In case of bus failure, each CI bus
consists of two paths (path A and path B). See Figure 1-1 for a sample five-node cluster configuration
utilizing two HSCs and three host computers. In this figure, all three hosts access both HSCs over the
CI bus and through dual porting both HSCs can access the tape formatter and the disks.
The HSC70 supports a combination of eight disk and tape data channels. The HSC50 supports a
combination of six disk and tape data channels. Each disk data channel supports four drives over the
Standard Disk Interface (SOl). Each tape data channel supports four tape formatters over the Standard
Tape Interface (STI). Depending upon which formatter is used, from one to four tape transports can be
supported by each formatter.
Consult the HSC Software Release Notes for the maximum number of tape formatters conforming
to the STI bus. These software release notes are shipped with each HSC and with updates of the
software.

1-3
GENERAL INFORMATION

fg HOST
:::::::i

TERMINAL *

HSC
PRINTER

mm CI INTERFACE
* VIDEO OR LA 12
CX-886B

Figure 1-1

Redundant Cluster Configuration

1.2.1 HSC70 Cabinet Layout
HSC70 logic and power systems are housed in a modified H9642 cross-products cabinet with both
front and rear access. Figure 1-2 shows the front view of the cabinet.

1-4
GENERAL INFORMATION

1111111111
1111111111 11111111
11111111 111111111 111111
1111111:1111111111:1111111111:111111
111111:1111111111:1111111111;1111111
111111 1111111111111111111
1I1111i1111111111
111111111

eX-2021A

Figure 1-2

HSC70 Cabinet-Front View

On the front of the cabinet are the Operator Control Panel (OCP) switches and indicators. Switch
operation and indicator functions are described in Chapter 2.
To access the cabinet interior, open the front door with a key. The door key is part of the door-lock
mechanism (part number 12-25411-01).
The upper right-hand portion of the cabinet houses the RX33 dual drives and connectors for the OCP.
The HSC70 contains two power supplies. Both are housed underneath the RX33 (Figure 1-3). Each
power supply has a fan drawing air from the front of the cabinet across the power unit and exhausting
it through a rear duct.

1-5
GENERAL INFORMATION

MAIN
POWER
SUPPLY

AUXILIARY
POWER
SUPPLY

CX-927B

Figure 1-3 HSC70-1nside Front View

A 14-slot card cage with a corresponding backplane provides housing for the HSC70 logic modules
(L-series extended hex). When viewed from the front, the card cage occupies the upper left of the
cabinet. Above the card cage is a module utilization label indicating the slot location of each module
(Figure 1-4). All unassigned slots contain baffles.

1-6
GENERAL INFORMATION

....

C'O

c
c

~
.::(.

Mod

a
C
aI :.::i
_
a
....
a~>~
Ill_

...JCI:U

ell

Slot

ell

C'O

c
c

CX)

>-I

CX)

C'O

...Ja::Cl

c
c

Qi
C
C

III

CX)

e >-I e >-I

;?:;.::t:
a III .~

1ll

a
~.~ a ~ ~
...J a:: t= ...Ja::~

C'O

CX)

~ :; ~
o~:;~
Ill._
0 III . ...J CI: Cl

...J a:: Cl

C'O

CX)

o
,..... .. u

e >-I e >-I
C'O

~
III

C
C

C'O

~:;III ._
~
o~:;~
Ill._
0
...J CI: Cl

...J a:: Cl

o...Ja::::::::
~o

10 9

14 13 12 11

III

Bkhd X
Req

c
c

e >- e
cb0 .. 0 cba .. 0

eX-889A

Figure 1-4 HSC70 Module Utilization Label Example
NOTE

Requestor slots A.. B, C, D, E, F, M, and N, illustrated in Figure 1-4, are optional tape or disk
data channels. Optional slot labels are blank when no module is present. Appropriate labels are
provided with each data channel option ordered.
Logic modules are cooled by a blower mounted behind the card cage (Figure 1-5). Air is drawn in
through the front door louver, up through the modules, and exhausted through the larger duct at the
rear.

1-7
GENERAL INFORMATION

~~..H+--- BLOWER

l~~-U+-~~~~1rr_--BLOWER
\L,
OUTLET
DUCT

i~~ttt--~~~~U----INTERNAL
CI CABLES

POWER
CONTROLLER
BULKHEAD

EXTERNAL
SI CABLES

eX-890B

Figure 1-5 HSC70-Inside Rear View
NOTE

Figure 1-5 shows the blower motor outlet duct for current models. Earlier models have a smaller
blower motor outlet duct.
Two levels of cable connections are found in the HSC70: backplane to bulkhead and bulkhead to
outside the cabinet. All connections to the logic modules are made via the backplane. All cables attach
to the backplane with press-on connectors.
The power controller is in the lower left-hand rear comer of the HSC70. The power Control bus,
delayed output line, and noise isolation filters are housed in the power controller.
Exterior CI, SDI, and STI buses are shielded up to the HSC70 cabling bulkhead. These cables are
attached to bulkhead connectors located at the bottom rear of the cabinet. From the interior of the I/O
bulkhead connectors, unshielded cables are routed to the backplane.

1-8
GENERAL INFORMATION

1.2.2 HSC50 (Modified) Cabinet Layout
HSC50 (modified) logic and power systems are housed in a modified H9642 cross-products cabinet
with both front and rear access. Figure 1-6 shows the front view of the cabinet.

1111111
11111111
II
1111111111 IIIIIIIIIIII!
111111:::::111111::::::111111:::::1;
111111111111111111111111111:1111111
111111 11111111 11111111
111111111:1111111111

lilllllll

CX-2024A

Figure 1-6 HSC50 (Modified) Cabinet-Front View

On the front of the cabinet are the OCP switches and indicators. Switch operation and indicator
fWlclions are described in Chapter 2.
To access the cabinet interior, open the front door with a key. The door key is part of the door-lock
mechanism (part number 12-25411-01).
The HSC50 (modified) contains two power supplies. Both are housed underneath the maintenance
access panel (Figure 1-7). Each power supply has a fan drawing air from the front of the cabinet
across the power unit and exhausting it through a rear duct.

1-9
GENERAL INFORMATION

CARD CAGE

MAIN POWER
SUPPLY

CARTRIDGE
STORAGE

CX-2020A

Figure 1-7 HSC50 (Modified)-Inside Front View

A 14-slot card cage with a corresponding backplane provides housing for the HSC50 (modified) logic
modules (L-series extended hex). When viewed from the front, the card cage occupies the upper left
of the cabinet. Above the card cage is a module utilization label indicating the slot location of each
module (Figure 1-8). All unassigned slots contain baffles.

1-10
GENERAL INFORMATION

II'>

"'iii

.J:;

!!:!

I
co

«
«I

eo
0

OQJeo

Req
Slot

OQJQJ

...Ja::~

...Ja::l-

Bkhd X
1

14 13 12 11

g e
I
c0
0
>

Ln
co
.. u
S2>E oo~o

o .. QJ

"->0.

Mod

...Ja::::::

10 9

CX-283B

Figure 1-8

HSC50 (Modified) Module Utilization Label Example

NOTE

Requestor slots A, B, C, D, E, and F, illustrated in Figure 1-8, are optional tape or disk data
channels. Optional slot labels are blank when no module is present. Appropriate labels are
provided with each data channel option ordered.
Logic modules are cooled by a blower mounted behind the card cage (Figure 1-9). Air is drawn in
through the front door louver, up through the modules, and exhausted through the larger duct at the
rear.

1-11
GENERAL INFORMATION

BLOWER

BLOWER
OUTLET
DUCT

W~~~t---~~~~----INTERNAL
CI CABLES

POWER
CONTROLLER
BULKHEAD
EXTERNAL
SI CABLES

eX-2022A

Figure 1-9

HSC50 (Modified)-Inside Rear View

NOTE

Figure 1-9 shows the blower motor outlet duct for current models. Earlier models have a smaller
blower motor outlet duct.
Two levels of cable connections are found in the HSC50 (modified): backplane to bulkhead and
bulkhead to outside the cabinet. All connections to the logic modules are made via the backplane. All
cables attach to the backplane with press-on connectors.
The power controller is in the lower left-hand rear comer of the HSC50 (modified). The power Control
bus, delayed output line, and noise isolation filters are housed in the power controller.
Exterior CI, SDI, and STI buses are shielded up to the HSC50 (modified) cabling bulkhead. These
cables are attached to bulkhead connectors located at the bottom rear of the cabinet. From the interior
of the I/O bulkhead connectors, unshielded cables are routed to the backplane.

1-12
GENERAL INFORMATION

1.2.3 HSC50 Cabinet Layout
HSC50 logic and power systems are housed in a modified H9642 cross-products cabinet with both
front and rear access. Figure 1-10 shows the fronl view of the cabinet.

FRONT DOOR
KEY LOCK
111111111111
111111111111111111111111111
1111111111111111::::1111111::::::::::::::11111111111
1111111111111111111111111111
1111111111

eX-282A

Figure 1-10 HSC50 Cabinet-Front View

On the front of the cabinet are the OCP switches and indicators. Switch operation and indicator
functions are described in Chapter 2.
To access the cabinet interior, open the front door with a key (cabinet lock assembly part number
12-14664). Located on the back of the front door are two TU58 drives, the TU58 run indicators, the
Secure/Enable switch for the serial line console port, and slots for tape storage. Figure 1-11 shows the
inside front view of the HSC50.

1-13
GENERAL INFORMATION

TU58 DRIVE 0

TU58 DRIVE 1

LEOs
CX-003C

Figure 1-11

HSC50 Cabinet-Inside Front View

A 14-s10t card cage with a corresponding backplane provides housing for the HSC50 logic modules
(L-series extended hex). When viewed from the front, the card cage and backplane occupy the lower
left of the cabinet. Above the card cage is a module utilization label indicating the slot location of each
module (Figure 1-12). All unassigned slots contain baffles.

1-14
GENERAL INFORMATION

a:;
<l:

c
c
co
.r::.
U

~
co
0

>-I

Bkhd
Req
Slot

14 13 12 11

U
~

ec
0

O .. u

0(1)·-

o~>~
(1)....Ja::o

...Ja:::::::

...Ja::O

(I)
(.J

c
c
co
.r::.

<l:

>-I

~>~

Mod

If)

Cii

O~O

10 9

CX-283B

Figure 1-12

HSC50 Module Utilization Label Example

NOTE

All requestor slots A through F, illustrated in Figure 1-12, are optional tape or disk data
channels. Optional slot labels are blank when no module is present. Appropriate labels are
provided with each data channel option ordered.
The upper right-hand portion of the cabinet houses the maintenance access panel. A dc power on/off
switch and connectors for the TU58, the OCP, and the maintenance terminal port are located on this
panel.
Power supply units are housed underneath the maintenance panel. A basic HSC50-AA/AB contains
one power supply capable of providing power for three data channels. A fourth data channel requires
the addition of an auxiliary power supply. Each power supply has a fan drawing air from the front of
the cabinet across the power unit and exhausting it through a rear duct. Figure 1-13 shows the back of
the HSC50 cabinet. The rear door is opened with a 5/32-inch hex wrench.

1-15
GENERAL INFORMATION

----

~~-=

-:·~IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII

1111111111111111111111111111111111
::::::::::::1111111111111111111111111111111111
1111111111111111111111111111111111111111111111

11111111111111111111
11111111111111111111

IIIIIIIIIIIIII!IIIII
1IIIIIIIllIIIIIIIIII
1111111111111111
1111111111111111
1111111111111111

1111111111111111
1111111111111111
1111111111111111

BACK DOOR LATCH
(HEX LOCK)

CX-004A

Figure 1-13 HSC50 Cabinet-Rear View
Logic modules are cooled by a blower mounted behind the card cage as shown in Figure 1-14. Air is
drawn in through the front door louver, up through the modules, and exhausted through the middle duct
at the rear.

1-16
GENERAL INFORMATION

CX-OOSA

Figure 1-14 HSC50 Inside Rear View

Two leve1s of cable connections are found in the HSC50: backplane to bulkhead and bulkhead to
outside the cabinet. All connections to the logic modules are made through the backplane. All cables
attach with press-on connectors to the backplane.
The power controller is in the lower left-hand rear comer of the HSC50. A1so at the rear of the HSC50,
the power Control bus and delayed output line are connected to noise isolation filters.
Exterior CI, SOl, and STI buses are shielded up to the HSC50 cabling bulkhead. These cables are
attached to bulkhead connectors located at the bottom rear of the cabinet.
From the interior of the I/O bulkhead connectors, unshielded cables are routed to the backplane and are
attached with press-on connectors.

1-17
GENERAL INFORMATION

1.2.4 External Interfaces
Figure 1-15 shows the external hardware interfaces used by the HSC70.

CI B U S - - - - O NE OR MORE HOST COMPUTERS
(4 CABLES: 2 PATH A, 2 PATH B)
SOl BUS - - - - D i S K DR IVES
(ONE CABLE PER DISK DRIVE)
STI BUS - - - T A P E FORMATTER
(ONE CABLE PER FORMATTER)
ASCII-----CONSOLE TERMINAL
SERIAL LINE
(I/O BULKHEAD J60)

HSC70
CONTROLLER
_

ASCII----(NOT USED)
SERIAL LINE
ASCII----(NOT USED)
SERIAL LINE

t'
Figure 1-15

HSC70 External Interfaces

RX33 DISK DRIVE
SIGNAL INTERFACE

RX33 DISK DRIVE

..J

BACKPLANE J18

CX-928C

1-18
GENERAL INFORMATION

Figure 1-16 shows the external hardware interfaces used by the HSC50 (modified) and the HSC50.

- C I - - - - ONE OR MORE HOST COMPUTERS
(4 CABLES: 2 PATH A, 2 PATH B)
- S D I - - - - DISK DRIVES
(ONE CABLE PER DISK DRIVE)

HSC50

- S T I - - - - TAPE FORMATTER
(ONE CABLE PER FORMATTER)
!'""-

ASCII
SERIAL LINE

~ASCII

LOCAL TERMINAL

TU58 CONTROLLER

SERIAL LINE
r--ASCII

HAND-HELD TERMINAL

CX-006C

Figure 1-16

HSC50 (Modified) and HSC50 External Interfaces

External interface lines include:
•

CI bus-Four coaxial cables (BNCIA-xx): two-path (path A and path B) serial bus with a transmit
and receive cable in each path. The communication path between system host(s) and the HSC.

•

SDI bus-FouT shielded wires for serial communication between the HSC and the disk drives (one
SOl cable per drive per controller) (BC26V-xx).

•

STI bus-Four shielded wires for serial communication between the HSC and the tape formatter
(one STI cable per formatter) (BC26V-xx).

•

Serial line interface-RS-232-C cable for console terminal communication with the I/O Control
Processor module. (The HSC70 console terminal baud rates are programmable.)

•

Serial line interface-RS-232-C cable linking the TU58 controller to the HSC (HSC50 only).

•

RX33 signal interface-Cable linking RX33 drives with the RX33 controller located on the
M.std2 module (HSC70 only).

•

ANSII hand held terminal-RS-232-C cable for hand held terminal communications with the I/O
Control Processor module (HSC50 only).

1-19
GENERAL INFORMATION

1.2.5 Internal Software
Major HSC software modules operatin.g internally are shown at a block level in Figure 1-17.
HOST CPUs

TAPES

D!SKS

K.ci

K.sti

K.sdi

I
I

MSCP
PROCESSOR

I
STI
MANAGER

CI
MANAGER

SDI
MANAGER

I
DISK
ERROR
PROCESSOR

TAPE

I
DISK

1/0

MANAGER

DIAGNOSTIC
SUBROUTINES

UTILITY
PROCESSES

DIAGNOSTIC
MANAGER

UTILITIES
MANAGER

CONTROL PROGRAM

TU58 OR
RX33 DRIVES

TERMINAL

CX-1928A

Figure 1-17 HSC Internal Software

Each software module is described in the following list.
•

HSC control program-Found on the system diskette for the HSC70 and the system tape for
the HSC50. The lowest level manager of the subsystem which provides a set of subroutines and
services shared by all HSC processes. This program performs the following functions:
Interprets incoming utility requests
Sets up the appropriate subsystem environment for operation of the requested utility
Invokes the utility process
Returns the subsystem to its normal environment upon completion of the utility execution
Initializes and reinitializes the subsystem
Executes all auxiliary terminal I/O
Schedules processes (both functional and diagnostic) for execution by the P.ioc/j
Provides a set of system services and system subroutines to HSC processes
Manages the RX33 local storage media (HSC70 only)
Manages the TU58 local storage media (HSC50 only)
Functional processes within the HSC communicate with each other and the HSC control program.
They communicate through shared data structures and send/receive messages.

1-20
GENERAL INFORMATION

•

MSCP Class Server-Responsible for validating, interpreting, and routing incoming MSCP
commands and dispatching MSCP completion acknowledgments. The following are part of the
MSCP Class Server.
SDI manager-Handles the SOl protocol, responds to attention conditions, and manages the
online/offline status of the disk drives.
Disk I/O manager-Translates logical disk addresses into drive-specific physical addresses,
organizes the data-transfer structures for disk operations, and manages the physical positioning
of the disk heads.

•

CI Manager-Responsible for handling Virtual Circuit and server connection activities.

•

Di~k error processor-Responds to all detected error conditions. It reports errors to the diagnostic

manager and attempts to recover from errors (ECC, bad block replacement, retries, etc.). When
recovery is not possible, a diagnostic is run to determine if the subsystem can function without the
failing resource. Then appropriate action is taken to remove the failing resource or to terminate
subsystem operation.
•

TMSCP Class Server-Sets up the data transfer structures for tape operations and manages the
physical positioning of the tape. The following is part of the TMSCP Class Server.
STI manager-Handles the STI protocol, responds to attention conditions, and manages the
online/offline status of the tape drives.

•

Diagnostic manager-Responsible for all diagnostic requests, error reporting, and error Jogging.
It also provides decision-making and diagnostic-sequencing functions and can access a large set of
resource-specific diagnostic subroutines.

•

Diagnostic subroutines-Run under the control of the diagnostic manager and are classified as
device integrity tests.
Utility processes-Perfonn volume-management functions (fonnatting, disk-to-disk copy, disk-totape copy, tape-to-disk restore). They also handle miscellaneous operations required for modifying
subsystem parameters (such as COPY, PATCH, and error dump) or for analyzing subsystem
problems.

1.2.6 Subsystem Block Diag~am
The HSC is a multimicroprocessor subsystem with two shared memory structures, one for control and
one for data. In addition, the HSC I/O Control Processor fetches its own instructions from a private
(Program) memory. Figure 1-18 shows a subsystem block diagram. Each major block is a module
unless otherwise specified. '

1-21
GENERAL INFORMATION

,---------,_
INPUT/OUTPUT
I
CONTROL
PROCESSOR
CONTROL BUS

r,--------------,
HOST I NTE R FACE K.ci

PLI BUS ..

L0107-YA

PI LA

OR
P.ioj

..- M.std

I
I
I

SC008
STAR
COUPLER

CI
I
-PATHJ
B

TERMINAL

OPERATOR
CONTROL
PANEL

TU58
DRIVE

L0106
OR

RX33
DRIVE

LOl17 ...~
__- - - - - - - -__=~
TAPE
,---------y _ BUS

~-.-~:~ MAGTAPE
:
TAPE
DATA.......-.
CHANNEL
FORMATTER .....-MODULE(S)
~ TA78, ETC....

PROGRAM BUS

I
I

L0118
OR
L0100

LOlll _

MEMORY
MODULE

I
I

L0105 ...~
__- - - - - - - - .

P.ioc

PORT
LINK

LINK

L0109

CI
j~
L---PATH-- -

I
I
I

PORT
BUFFER

I LI BUS

DATA BUS

K.pli

-..
--

PORT
PROCESSOR

ASCII PORT SERIAL
LINE INTERFACE

LOl19 ~
OR
K.sti L0108-YB

L
TAPE
TRANSPORT

t-+--tl~.. K.si

-....,.. TAPE
TRANSPORT

DISK
DATA

)

TAPE

~ TRANSPORT

CHANNEL
MODULE(S)
K.si
OR

LOl19 "'-~--I:-" DISK DRIVE
RA8l, RA60,

~.sdi L0108-YA

__
ET_C_._ _~

'--_....:-. . TAPE
TRANSPORT

CX-1929A

Figure 1-18 HSC Subsystem Block Diagram

1.3 MODULE DESCRIPTIONS
This section describes each of the HSC logic modules. References to modules by their engineering
terms appear throughout HSC documentation as well as on diagnostic printouts. For this reason, the
engineering tenn is shown in parentheses after the formal name for each module. These relationships
are also indicated in Figure 1-18 and Table 1-2.

1-22
GENERAL INFORMATION

Table 1-2 Module Nomenclature

Module
Name

Engineering
Name

Module
Designation

Port link

LINK
or
Interprocessor UNK
Interface (ILl)

LOlOO, Rev E2
or
LO 118

Port buffer

PILA

LOl09

Port processor

K.pli

LOl07

Disk data channel
or
Data channel

K.sdi
or
K.si

LOl08-YA
or
L0119

Tape data channel
or
Data channel

K.sti
or
K.si

LOI08-YB
or
L0119

Input/Output Control Processor

P.ioj (HSC70)
P.ioc (HSCSO)

LOllI (HSC70)
LOlOS (HSCSO)

Memory

M.std2 (HSC70)
M.std (HSCSO)

LOl17 (HSC70)
LOl06 (HSCSO)

Host interface

K.ci

Consists of:
Port link (LINK or ILl),
Port buffer (PlLA), and
Port processor (K.pli) modules

1.3.1 Port Link Module (LINK) Functions
The port link module (LOIOO-E2 or LOll8) is a part of the host interface module set (K.ci). With
all configuration switches and jumpers in default positions, the LOl18 is functionally identical with
the LOlOO-E2. The location and default positions are described in Chapter 3. The port link module
performs the following functions.
•

Serialization/deserialization, encoding/decoding, de isolation- Permits transmission of a selfclocking stream over the CI. Information transmitted over the CI bus is serialized and Manchester
encoded. The driver circuit includes a transfonner for ac coupling the encoded signal to the coaxial
cable. Information received from a CI transmission is decoded and converted to bit-parallel fonn.
The circuitry also provictes carrier detection for determining when the CI is in use by another node.

•

Cyclic redundancy check (CRC) generation/checking-Checks the 32-bit CRC character
generated and appended to a message packet when it is received. Also generates the 32-bit CRC
character during the transmission of a packet. An incorrect CRC means either errors were induced
by noise or a packet collision occurred.

•

ACK/NACK generation-Generates an ACK upon receipt of a packet addressed to the LINK if
the following conditions exist:
-

Error-free CRC

Buffer space available for the message

1-23
GENERAL INFORMATION

Upon receipt of a packet addressed to this node, a NACK is generated if the following conditions
exist:
-

Error-free CRC

No buffer space available for the message

No response is made if a packet addressed to this node is received with CRC error or the node
address is incorrect.
Packet transmission-Performs the following functions.
-

Executes the CI arbitration algorithm
Transmits the packet header

Moves the stored information from the transmit packet buffer to the Manchester encoder
Calculates and appends the CRC to the end of the packet

Receives the expected ACK packet

Packet reception-Performs the following functions.
-

Detects the start of the CI transmission

Detects the sync characters

Decodes the packet header information
Checks the CRC
Moves the data from the Manchester decoder
Returns the appropriate ACK packet

The port link: module interfaces via line drivers/receivers directly to the CI coaxial cables. On the HSC
interior side, the port link: module interfaces to the port buffer module through a set of interconnect link
signals. The port link: module also interfaces to the port processor module (indirectly through the port
buffer module) using a set of port link interface (PLI) signals.
For a detailed technical description of the port link: modules, refer to the CI780 Technical Description
Manual (EK-CI780-TD).

1.3.2 Port Buffer Module (PI LA) Functions
The port buffer module (LOI09) provides a limited number of high-speed memory buffers to
accommodate the difference between the burst data rate of the CI bus and HSC internal memory
buses. It also interfaces to the port link: (CI link:) module via the ILl signals and the port processor
module via port/link: interface (PLI) signals.

1.3.3 Port Processor Module (K.pli) Functions and Interfaces
The port processor module (LOI07-YA) performs the following functions.
•

Executes and validates low-level CI protocol

•

Moves command/message packets to/from HSC Control memory and notifies the correct server
process of incoming messages

•

Moves data packets to/from HSC Data memory

The port processor module interfaces to three buses:
•

PLI bus interfaces the port buffer and port link: modules

1-24
GENERAL INFORMATION

•

Control memory bus interfaces HSC Control memory

•

Data memory bus interfaces HSC Data memory

1.3.4 Disk Data Channel Module (K.sdi) Functions
Disk data channel module (LOI08-YA) operation is controlled by an onboard microprocessor with
a local programmed read-only memory (PROM). This data channel module performs the following
functions.
•

Transmits control and status information to the disk drives

•

Monitors real-time status information from the disk drives

•

Monitors in real-time the rotational position of all the disk drives attached to it

•

Transmits data between HSC Data memory and the disk drives

•

Checks the error detection code (EDC) and generates or checks the error correction code (ECC)
during Read/Write operations.

Commands and responses pass between the disk data channel microprocessor and other internal HSC
processes through Control memory. The disk data channel module interfaces to the Control memory
bus and to the Data memory bus. It can also interface to four disk drives with four individual SDI
buses. Currently, combinations of up to eight disk data channel or tape data channel modules are
possihle in the HSC70. The HSC50 supports combinations of up to six disk data channel or tape data
channel modules. Configuration guidelines are found in the HSC Installation Manual (EK-HSCMNIN).

1.3.5 Tape Data Channel Module (K.sti) Functions
Tape data channel module (LOI08-YB) operation is controlled by an on board microprocessor with a
local programmed read-only memory (PROM). The tape data channel performs the following functions.
•

Transmits control and status information to the tape formatters

•

Monitors real-time status information from the tape formatters

•

Transmits data between the Data memory and the tape formatters

•

Generates an error detection code (EDC) for each 512 bytes during a Write operation. The tape
formatter generates and sends an EDC every 512 bytes during a Read operation.

Commands and responses pass between the tape data channel microprocessor and other internal HSC
processes through Control memory. The tape data channel module interfaces to the Control memory
bus and to the Data memory bus.

1.3.6 Data Channel Module (K.si) Functions
Data channel module (L0119) is an interface between the HSC and the Standard Disk Interconnect
(SDI) or Standard Tape Interconnect (STI) bus and is a direct replacement for the K.sdi or K.sti data
channel modules. The K.si is configured for disk or tape interface when the HSC is initialized (see
Chapter 4). The K.si functions are the same as the functions for the K.sdi or K.sti.

1-25
GENERAL INFORMATION

1.3.7 I/O Control Processor Module (P.ioj/c) Functions
The HSC70 P.ioj module (LOll1) uses a PDP-ll ISP (]-11) piocessoi. The HSC50 pjoc module
(LOI05) uses a PDP-II ISP (F-ll) processor. Both contain memory management and memory
interfacing logic. These processors execute their respective HSC internal software. Also, the
Input/Output (I/O) Control Processor modules contain the following.
•

Bootstrap read-only memory (ROM)

•

Arbitration and control logic for the Control and Data buses

•

Program-addressable registers for subsystem initialization and OCP communications

•

Processes for all parity checking and generation for its accesses to memory

•

Program memory instruction and data cache, 8 Kbytes of direct map high-speed memory (HSC70
only)

The I/O Control Processor modules interface to:
•

Program memory on the Program memory bus

•

Control memory through the signals of the backplane Control bus

•

Data memory through signals of the backplane Data bus
Console terminal RS-423 compatible signal levels (HSC70 only)
TU58 tape drives (HSC50 only)

•

Auxiliary terminal through an RS-232-C interface (HSC50 only)

1.3.8 Memory Module (M.std2) Functions
The HSC70 memory module (L0117) contains three separate and independent system memories. each
residing on a different bus within the HSC70. In addition, the memory module contains the RX33
diskette controller. The three memory systems and RX33 diskette controller are known as:
•

Control memory (M.ctl)-Two banks of 256 Kbytes of dynamic RAM for subsystem control
blocks and interprocessor communication structures storage.

•

Data memory (M.dat)-512 Kbytes of status RAM to hold the data from/to a data channel
module.

•

Program memory (M.prog)-l megabyte of RAM for the control program loaded from the RX33
diskette.

•

RX33 diskette controller (K.rx)-Resides on the Program bus and performs direct memory access
word transfers when reading or writing data to/from the RX33 diskette.

Using physical addresses, the memory space allocations for the three memories are illustrated in
Figure 1-19.

1-26
GENERAL INFORMATION

22-BIT ADDRESS ALLOCATION
ADDRESS

SPACE

17777777

1/0 PAGE

17770000
17767777

CONTROL
WINDOWS

17760000
17757777

1600000Q
15777777
14000000
13777777
04000000
03777777

SIZE

COMME~,.jT

INTERNAL

2 KW

INTERNAL REGISTERS

CBUS

2 KW

RESERVED ADDRESSES

NONE

248 KW

NOT ACCESSIBLE

CBUS

256 KB (X2)

CONTROL MEMORY

DBUS

512 KB

DATA MEMORY

PBUS

2 MB

EXPANSION ROOM

UNDEFINED
L.

17000000
16777777

BUS

M.CTL

M.DAT

UNUSED

M.PROG
PROGRAM MEMORY

PBUS
00000000

1 MB

0-4000 RESERVED
FOR TRAP VECTORS
CX-931A

Figure 1-19

Memory Map (M.std2-L0117)

NOTE

Two completely redundant memory banks make up Control memory. Only one bank at a time is
usable during functional operation. Bank failure detection and bank swapping are done at boot
time.
Interface to Control memory is by the backplane Control bus and to Data memory by the backplane
Data bus. The interface to the I/O Conttol Processor local Program memory is via a set of backplane
signals to the Program memory module. In addition, the memory module houses the control circuitry
for the RX33 disk drives.

1.3.9 Memory Module (M.std) Functions
The memory module (LO 106) contains the following three independent and separate memories.
•

256 Kbytes of Program memory (M. prog) This is space for the control program loaded from the
TU58.

•

128 Kbytes of Control memory (M.ctl) This is space for the routines initiating data ttansfer action.

•

128 Kbytes of Data memory (M.dat) This is space to hold the data from/to a data channel module.

1-27
GENERAL INFORMATION

Using physical addresses, the memory space allocations for the three memories are illustrated in
Figure 1-20.

22-81T ADDRESS ALLOCATION
ADDRESS

SPACE

17777777

I/O PAGE

17770000
17767777

CONTROL
WINDOWS

17760000
17757777
17000000
16777777

COMMENT

INTERNAL

2 KW

INTERNAL REGISTERS

CBUS

2 KW

RESERVED ADDRESSES

.--<

NONE

248 KW

NOT ACCESSIBLE

CBUS

64 KW

EXPANSION ROOM

CBUS

64 KW

CONTROL MEMORY

DBUS

192 KW

EXPANSION ROOM

DBUS

64 KW

DATA MEMORY

PBUS

1.5MW

EXPANSION ROOM

PBUS

128 KW

PROGRAM MEMORY

UNUSED

16400000
16377777

M.CTL

16000000
15777777

UNUSED

14400000
14377777

M.DAT

01000000
00777777

SIZE

UNDEFINED

.....I-

14000000
13777777

BUS

UNUSED

M.PROG

00000000

0-4000 RESERVED
FOR TRAP VECTORS
CX-338B

Figure 1-20 Memory Map (M.std-L0106)

Interface to Control memory is by the backplane Control bus and to Data memory by the backplane
Data bus. The interface to the I/O Control Processor local Program memory is via a set of backplane
signals to the Control memory module.

1.4 HSC MAINTENANCE STRATEGY
Maintenance of the HSC is accomplished with field replaceable units (FRUs). Procedures for removal
and replacement are described in Chapter 3. Field service personnel should not attempt to replace or
repair component parts within FRUs.
Isolation of solid failures can be accomplished efficiently due to the logical partitioning of the modules
and extensive internal diagnostics. In addition to the device-resident diagnostics, the HSC-resident
offline diagnostics are available to support and verify corrective maintenance decisions.

1-28
GENERAL INFORMATION

1.4.1 Maintenance Features
The following features assist in troubleshooting the HSC.
•

•

Self-contained and self-initiated diagnostics-On initialization, various levels of diagnostics execute
in the HSC. Read-only memory (ROM) diagnostics test each microprocessor in the disk and tape
data channels, port processor, and I/O processor modules. Pressing the HSC Init button starts all
internal ROM diagnostics.
Operator Control Panel fault code display-The OCP or the console terminal displays any failures.
If further diagnostics are needed, use the terminal to initiate diagnostics stored on the system

boot media or the offline diagnostic media (RX33 diskettes for the HSC70 or ru58 tapes for the
HSC50).
•

Console terminal-After initialization, the operator can use the console terminal to run on1ine
device integrity tests (see Chapter 5) or offline diagnostic tests (see Chapter 6). Also, certain
resource failure detections can initiate tests automatically.

•

Module LED indicators-All logic modules have at least one LED to indicate board status. See
Chapter 2 for the location of these LEOs.

The HSC subsystem allows logical assignment of a disk drive or tape formatter to the diagnostics.
Device integrity tests allow drive diagnosis even though other active drives are connected to the HSC.
Background (periodic) diagnostics test HSC logic not currently in use by the subsystem. Failures cause
the HSC to reboot and execute the initialization diagnostics.
Requestor-detected Data memory errors cause an initiation of the inline memory diagnostics to test the
buffer causing the error. Failures found in any Data Buffer cause removal of that buffer from service.
If no failure is found, the tested buffer is returned to service, with one exception. IT the same buffer is
sent to test twice, it is retired from service even though no failure is found.

1.4.2 HSC Specifications
Figure 1-21 lists the HSC physical and environmental specifications.

1-29
GENERAL INFORMATION

OPTION DESIGNAT!ON

DESCRIPTION

HSCXX-AA = 60 HL, i 20n 80 V
HSC MASS STORAGE SERVER

HSCXX-AB = 50 HZ, 380/415V
MECHANICAL
HEIGHT

WEIGHT

MOUNTING
CODE

LBS

400

WIDTH

DEPTH

CAB TYPE
(IF USED)

181.2

106.7

21.3

54.1

91.4

MODIFIED
H9642

POWER (AC)
AC VOL TAGE
NOMINAL

ACVOLTAGE
TOLERANCE

120 208

104-128/180-222

380 415

331-443

PHASE

STEADY -STATE
CURRENT (RMS)

60 HZ:" 1

2250 WATTS

50 HZ:" 1

2245 WATTS

FREQUEI\JCY

& TOLERANCE

POWER CONSUMPTION
(MAX)

POWER (AC)
Ai\lPS tMAX) 8'r PHASE
PHASE A . 1
PHASE B

PHASE C

PHASE A

380 V

PHASE B =- 7
PHASE C .. 7
NEUTRAL ~ 9

NEUTRAL· 17
POWER (AC)
POWER CORD LENGTH

INTERRUPT TOLERANCE

APPARENT POWER (KVA)

L21 - 30P

15 FT (4.5 M)

4 MS (MIN)

3.4 (KVA)

HUBBE LL - 520 P6

15 FT (4.5 iVI)

4 MS (MIN)

3.4 (KVA)

PLUG TYPE
NEMA -

POWER (AC)
HSC OPTION

INRUSH CURRENT

SURGE DURATION

HSCXX - AA

70 AMPS/PHASE

16 MS

HSCXX - AB

70 AMPS/PHASE

20 MS

DEVICE ENVIRONMENT
R E LA T I V E HUM I 0 I T Y

TEMPERATURE

OPERATlr~G

OPERATING'

STORAGE

59 - 90 0 F

40 - 151() F

15 - 32° C

·40 - 66" C

STORAGE

RATE OF CHANGE

HEAT DISSIPAT!ON

TEMP

HUMIDITY

60 HZ

50 HZ

20%/HR

7676 BTU
HR

8078 KJ'
HR

20' FHR
20 - 80';0

5 - 95°'0

11° C HR

DEVICE ENVIRONMENT
AL TITUDE (MAX)
OPERATING

STORAGE

8000 FT

30,000 FT

2.4 KM

9.1 KM

*ALTITUDE CHANGES:

AIR VOLUME (AT INLET)

AIR QUALITY

FT) 'MIN

M3 MIN

PARTICLE COUNT (MAX)

210

5.92

N'A

DERATE THE MAXIMUM TEMPERATURE 1.8 0 C PER THOUSAND METERS
(1.0° F PER THOUSAND FEET).

CX-2023A

Figure 1-21

HSC Specifications

1-30
GENERAL INFORMATION

1.5 HSC RELATED DOCUMENTATION
Documents related to the HSC are available under the following titles and part numbers.

•
@O

HSC User Guide (AA-GMEAA-TK)
HSC Installation Manual (EK-HSCMN-IN)

•

HSC Software Technical Manual, Vol I (EK-HS572-TM)

•

HSC Software Technical Manual, Vol II (EK-HS575-TM)

•

HSC50170 Hardware Technical Manual (EK-HS571-TM)

•

HSC70 Illustrated Parts Breakdown (EK-HSC70-IP)

•

HSC50 Illustrated Parts Breakdown (EK-HSC50-IP)

•

HSC50 Device Integrity Tests User Documentation (EK-llISC5-UG)

•

HSC50 Offline Diagnostics User Documentation (EK-OHS-UG)

•

HSC50 Utilities User Documentation (EK-UHSC5-UG)

•

VT320 Owners Manual (EK-VT320-UG)
VT320 Programmer Pocket Guide (EK-VT320-HR)

•

VT320 Installation Guide (EK-VT320-IN)

•

VT220 Owners Manual (EK-VT220-UG)
VT220 Programmer Pocket Guide (EK-VT220-HR)

•

VT220 Installation Guide (EK-VT220-IN)

•

Installing and Using the lA50 Printer (EK-0LA50-UG)

•

LA50 Printer Programmer Reference Manual (EK-OLA50-RM)

•

Installing and Using the LA75 Printer (EK-OLA75-UG)

•

LA75 Printer Programmer Reference Manual (EK-OLA75-RM)

•

Star Coupler User Guide (EK-SCOO8-UG)

•

CI780 Technical Description Manual (EK-CI780-TD)

•

CI780 User Guide (EK-CI780-UG)

•

DECwriter Correspondent Technical Manual (EK-CPL12-TM)

•

TU58 DECtape II User Guide (EK-OTU58-UG)

These documents (except for the HSC User Guide) can be ordered from Publication and Circulation
Services, 10 Forbes Road, Northboro, Massachusetts 01532 (RCS code: NRI2; mail code: NR03/W3).
The HSC User Guide can be ordered from the Software Distribution Center, Digital Equipment
Corporation, Northboro, Massachusetts 01532.
NOTE

Please consult the HSC Software Release Notes for the latest hardware revision levels.

2-1
HSC CONTROLS/INDICATORS

2
HSC CONTROLS/INDICATORS
2.1

INTRODUCTION

This chapter describes the controls and indicators located in five areas of the HSC70, HSC50
(modified), and HSC50. They are:
•

HSC70
1. Operator Control Panel (OCP)

2. Inside front door
3. RX33 disk drives
4. Logic modules
5. Power controller
HSC50/HSC50 (modified)
1. Operator Control Panel (OCP)

2. Inside front door (TU58 tape drives)
3. Maintenance access panel
4. Logic modules
5. Power controllers (60 Hz and 50 Hz)

2.2 OPERATOR CONTROL PANEL (OCP)
Figure 2-1 illustrates the controls and indicators on the OCP.

2-2
HSC CONTROLSIINDICATORS

MOMENTARY
CONTACT
SWITCH

ALTERNATE
ACTION
SWITCH

\~------------~~----~----~------------~I

State

Power

Onlinenn
~~
c::J

cx-ooss
Figure 2-1

Operator Control Panel

The OCP controls and indicators are described in the following list.
•

State and Init indicators-Describe the state of the HSC. Under runtime conditions, the lnit
indicator is OFF while the State indicator is pulsing. During initialization, these indicators change
to reflect the current initialization phase of the subsystem. Refer to the bootstrap flowchart in
Chapter 8 for details on these phases.

•

Init switch-Pushing the Init switch causes the HSC to start its initialization routine. The
Secure/Enable switch must be in the ENABLE position for this switch to be operational. Holding
the Init switch in causes the console terminal to loop back.

•

Power indicator-Goes OFF if the dc voltage levels drop below one-third of minimal. The power
indicator is driven from a dc comparator circuit on the I/O Control Processor module (LO IlIon
the HSC70 or LOIOS on the HSCSO/HSCSO [modified]) which constantly monitors the +S, +12,
and -S.2 voltages. The power indicator also is driven by a logic gate that monitors the Power Fail
signal from the power supplies. If this signal is asserted, the power indicator goes OFF.
NOTE

An ON power indicator does not mean these voltages are within specification (±5 percent).
•

Fault indicator and switch-Comes on when the HSC logic detects a fault. The Fault switch is
used for the OCP lamp test.
Fault codes-When the Fault switch is pressed and released, the lamps in Init, Online, Fault,
and the two blank switches function as an error display. If the fault code is a hard fatal error,
the fault code blinks on and off until the HSC is powered down or the Fault switch is pressed
again.
If the displayed fault code is a soft (nonfatal) failure, the fault code clears on subsequent
toggling of the Fault switch. Multiple soft fault codes can be queued in the fault code buffer.
Subsequent toggling of the Fault switch displays each soft fault code until the buffer is emptied.

2-3
HSC CONTROLSIINDICATORS

Soft fault codes are identified by the Fault indicator ON (or displayed fault code) while the
State indicator is pulsing. With soft faults, the HSC continues to operate without use of
the failing resource. Hard fault codes are identified by the fault indicator ON (or displayed
fault code) while the HSC State indicator is not pulsing. With hard faults, the HSC does not
continue operation until the failure is remedied.
Error codes associated with the OCP display are defined in Chapter 4 and in Chapter 8.
-

Lamp test-Pushing and holding the Fault switch causes all the OCP indicators to light and
function as a lamp test. Even if the Fault indicator is already on before the switch is pushed,
the lamp test can be executed.

•

Online switch-Puts the HSC logic in the available state when pushed to the in position and
allows a host to establish a Virtual Circuit with the HSC. When this switch is released to the out
position no new Virtual Circuits can be made.

•

Online indicator-Shows a Virtual Circuit exists between the HSC and a host CPU when the
Online indicator is on. When this indicator is off, no Virtual Circuits are established with any
host.
Blank indicators-Forms the lowest two bits of a five-bit fault code.

2.3 HSC70 INSIDE FRONT DOOR CONTROLS/INDICATORS
Figure 2-2 shows the controls and indicators available when the front door is opened.

2-4
HSC CONTROLSIINDICATORS

OCP SHIELD

HSC70
SECURE/ENABLE
SWITCH

OCP SIGNAL/POWER
LINE CONNECTOR

CX-902B

Figure 2-2

Controls/lndicators-lnside Front Door

The following list describes the controls and indicators found on the HSC70 inside front door.
•

SecurelEnable switch-Disables the Init switch from the OCP when in the SECURE position.
Also, the SET utility program cannot run and the BREAK character from the terminal is disabled.
With the Secure/Enable switch in the ENABLE position, the !nit switch and all the utility programs
can be used.
The SHOW utility is operable with the Secure/Enable switch in either position.

•

Enable indicator-Indicates the Secure/Enable switch is in the ENABLE position when the
Enable LED is illuminated (all switches can be used). When the Enable indicator is OFF, the OCP
is secure.

2-5
HSC CONTROLS/INDICATORS

•

RX33 LEDs-When lit, indicates which particular drive is in use. There is an LED on the
front panel of each drive. When not in use, the RX33 diskettes are stored inside the front door
(Figure 2-3).

DRIVE-IN-USE LEDs
PLATE

DISKETTE
STORAGE
AREA

CX-9328

Figure 2-3

•

RX33 and dc Power Switch

dc power switch-Located on the left side of the RX33 housing (Figure 2-3). When the dc power
switch is in the 0 position, the HSC70 is without dc power. Moving the switch to the 1 position
restores dc power.

2-6
HSC CONTROLSIINDICATORS

2.4 HSC50 INSIDE FRONT DOOR CONTROLS/INDICATORS
Figure 2-4 shows the controls and indicators available when the front door is opened.

TU58 SELF-TEST H\lDICATOR
(VIEWED FROM THE TOP)

TU58 TAPE
CARTRIDGE
STORAGE

DECAL

ENABLE LED

TU58 DRIVE

TU58 DRIVE 1

LEOs

CX·0038

Figure 2-4

HSC50 Controls/Indicators-Inside Front Door

The following list describes the controls and indicators found on the HSC50 inside front door.
•

SecurelEnable switch-With the Secure/Enable switch in the SECURE position, the Init switch is
disabled from the OCP. Also, the SET utility program cannot run and the BREAK character from
the terminal is disabled. With the Secure/Enable switch in the ENABLE position, the Init switch
and all the utility programs can be used. The SHOW utility is operable with the Secure/Enable
switch in either position.

•

Enable indicator-An illuminated Enable LED indicates the Secure/Enable switch is in the
ENABLE position (all switches can be used). When the Enable indicator is OFF, the OCP is
secure.

•

TU58 Run indicators-When a TU58 Run indicator is ON, the TU58 is currently moving tape.
Data loss can occur if the tape is removed while this indicator is ON. If the indicator is OFF, tape
is not in motion.

2-7
HSC CONTROLS/INDICATORS

TU58 Self-Test indicator-The TU58 Self-Test indicator is found on the TU58 controller module
(Figure 2-4). The controller module is located inside the TU58 housing with the drive mechanics.
Observe the Self-Test indicator by looking down through the TU58 housing vents. When this
indicator is ON, the TU58 controller has successfully completed self-diagnostics.

2.5 HSC50 MAINTENANCE ACCESS PANEL CONTROLS AND
CONNECTORS
Removing the maintenance access panel cover reveals the dc power switch and several connectors
available for HSC50 maintenance (Figure 2-5).

1 ON POSITION

o OFF POSITION

DC POWER\
SWITCH

OCP
CONNECTOR

CONNECTORS RESERVED
. ~OR FUTURE USE

MAINTENANCE TERMINAL
SIGNAL CONNECTOR

TERMINAL POWER

CX-014B

Figure 2-5

HSC50 Maintenance Access Panel

2.5.1 dc Power Switch
When the dc power switch is in the 0 position, the HSC50 is without dc power. Moving the switch to
the 1 position restores dc power.

2-8
HSC CONTROLS/INDICATORS

2.5.2 HSC50 Maintenance Panel Connectors
Two of the connectors in the maintenance access panel are used to connect the maintenance terminal
to the HSC50. One connector supplies power to the maintenance terminal and the other is the signal
connector. Additional connectors are:
•

OCP connector

•

TU58 connectors

•

Connectors reserved for future use

2.6 HSC70 MODULE INDICATORS AND SWITCHES
All logic modules have at least one LED to indicate board status. Figure 2-6 shows the locations of
these LEOs and the module utilization label. Additionally, three of these logic modules contain specific
switches.

2-9
HSC CONTROLS/INDICATORS

NOT USED

NODE ADDRESS
SWITCHES

SWITCH S-3
(REV E2)

LINK BOARD _~5f
STATUS
INDICATORS

G01 MICRO ODT

~ 02 SERIAL LINE UNIT
~ 03 MEMORY OK

6 D4 SEQUENCING

•

RED

AMBER

® GREEN
CX-9338

Figure 2-6

Module LED Indicators

2-10
HSC CONTROLSIINDICATORS

Figure 2-7 shows the slot location for each of the modules.

0
0

:.:::;

o
t:
~>~

Mod

OQ.)-

-1CI:U

0
0

co
en .....
~:;~
I

OQ.)-

-1CI:U

Slot

ro
.r;

.r;

U
~

ex)

I
r--

.....

~:;~

OQ.)-

-ICI:U

Bkhd X
Req

ro
.r;

c
c
co

Q.)

14 13 12 11

Cii

c
c

....

.:,t.

~
co

Cii

ro
.r;

.r;

c
c
co

c
c

r,
ex)

U
~
co

~:;:-§

r,
ex)

ex)

o .. .:,t.

.r;

c
c
co

Cii
U

~
co

ex)

o2>~
Q.).-

ex)

-1CI:t-=

...JCI:I-

:3£0

10 9

(I)

0 .. Q.)
...... >0..

(I)

-1CI:O

Q.)

.r;

c::

c
c
co

~>~
......
>'" o
0(1)·(I) . ...JCI:O ...JCI:O

o..... ...
> ~

0 .. Q.)
...... >0..
0(1) co

a;
U

~
co

<i
<i
I
r--

c
0

,..... .. U
[VO
-1CI::::::

:: :; E
O(l)Q.)
o2>~
(I) . -1CI:O

-1CI:~

y
0

eX-889A

Figure 2-7

HSC70 Module Utilization Label Example

Table 2-1 shows the functions of the various module LEDs.
Table 2-1

Functions of Logic Module LEOs

Module

Color

Function

LOllI

01 amber

Micro ODT-Used during J-ll power-up microdiagnostics.

02 amber

Thnninal port OK-Used during J-ll power-up microdiagnostics.

03 amber

Memory OK-Used during J-11 power-up microdiagnostics.

04 amber

Sequencing indicator-Used during J-ll power-up microdiagnostics.

05 amber

State indicator-Mirrors the OCP State indicator.

06 amber

Run indicator-Pulses at the on-board microprocessor run rate.

07 red

Board status-Indicates an inoperable module except during
initialization when it comes on during module testing.

08 green

Board status-Indicates the module has passed all applicable
diagnostics.

Green

Board status-Indicates the operating software is running and has
successfully tested this module.

Amber

Indicates Memory Active-Lit during every memory cycle.

LOll 7

2-11
HSC CONTROLS/INDICATORS

Table 2-1 (Cont.)

Module

L0108-YA
LOI08-YB
L0119

Functions of Logic Module LEOs

Color

Function

Red

Board status-Indicates an inoperable module except during
initialization when it comes on during module testing.

Green

Board status-Indicates the operating software is running and that
self-test module microdiagnostics have completed successfully.

Red

Board status-Indicates an inoperable module except during
initialization when it comes on during module testing.

Amber (eight LEOs)

DI-Off for PROM load, on for RAM load.
D2 through D8-Upper register #2 contents.
The LEDs reflect the implemented bits of the upper error register
#2. When a microinstruction parity error is detected, the module clocks
are inhibited which stops the module. The bit content of the upper
error register #2 is displayed on the LEDs. See Figure 2-9 for the
location of the LEDs.

LOI07-YA

LOI09

LOIOO-E2
LOll 8

Green

Board status-Indicates the operating software is running and that
self-test module microdiagnostics have completed successfully.

Red

Board status-Indicates an inoperable module except during
initialization when it comes on during module testing.

Green

Board status-Indicates the operating software is running and that all
applicable diagnostics have completed successfully.

Red

Board status-Indicates an inoperable module except during
initialization when it comes on during module testing.

Amber

Always on when the HSC70 is on (used only for engineering test
purposes).

Green

Board status-Indicates the node i~ either transmitting or receiving;
dims or brightens relative to the amount of local CI activity.

Red

Board status-Indicates the module is in the internal maintenance
mode.

2.6.1 HSC70 Module Switches
Specific switches are found on LINK (L0100-E2 or LOl18), port processor (L0107), and port buffer
(LO 109) modules as follows:
•

CI port LINK module (LOIOO.E2/LOI18)-Refer to Figure 2-6 for the CI node address switches
mounted on the L0100-E2 or L01l8 module. Switches must be identically set to avoid CI
addressing errors. See Chapter 3 for switch positions of Sl, S2, and S3.

•

CI port processor and CI port buffer modules (HSC70 LOI07 and LOI09)-Both the LOI07
and L0109 modules have dual inline pack (DIP) switches to indicate the hardware revision level.
DIP switch positions should not be changed except as directed by a Field Change Order (FCO).
Figure 2-8 shows the location of the these switches.

2-12
HSC CONTROLS/INDICATORS

•

K.si (LOI19) data channel switch pack-See Section 2.7.1 for a description of the switchpack
settings.

L0109

L0107

HARDWARE REVISION LEVEL SWITCHES
(DO NOT CHANGE EXCEPT BY FCO)

CX-241C

Figure 2-8

•

Module (DIP) Switches

HSC70 P.ioj (LOIII)-The LOllt module contains two punch-out connector packs used to assign
an unique value to the P.ioj serial number register. The switch settings should never be modified in
the field.
The P.ioj module serial number is used only when a default HSC SDS-ID is generated. The SDSThis ID is
usually generated by initializing the HSC70 (toggling the Init switch on the OCP) while holding in
the OCP Fault switch until the INIPIO banner is printed on the console. For all other reboot cases,
the HSC70 P.ioj serial number is not used.

II) is a hexadecimal number uniquely identifying the HSC as a node in the cluster.

•

K.si (LOI19) data channel-See Section 2.7.1 for a description of the switchpack settings.

2.7 K.si (L0119) MODULE
The K.si (L0119) data channel module is a direct replacement for the disk data channel module (K.sdi,
LOI08-YA) or the tape data channel module (K.sti, LOI08-YB). The K.si can be installed in the HSC70,
HSC50 (nlodified), or HSC50.

2-13
HSC CONTROLS/INDICATORS

2.7.1 K.si (L0119) Switch Settings
The K.si has a switchpack containing four switches. Figure 2-9 shows the location of the switchpack.

n
ON OFF

NOTE: ALL SWITCHES MUST BE OFF
FOR NORMAL OPERATION

}

AMBER LEOs. 01-08
(01 IS ON TOP)

RED STATUS LED

GREEN STATUS LED

K.si DATA CHANNEL
MODULE

CX-2118A

Figure 2-9

K.si (L0119) LEOs and Switchpack

2-14
HSC CONTROLSIINDICATORS

Table 2-2 describes the name and usage of the switches. SW1 is on the top of the switchpack.
Table 2-2

K.si Switchpack Options

Switch
Number

Switch
Name

Function
Description

Normal
Position

SWI

rv.tFG

Provides loop on error and single port
external loop.

Off

SW2

Bum in

Continuous loop, assumes external loop
and clock.

Off

SW3

Ext loop

Loops on all ports. For system or field use
only.

Off

SW4

Ext clock

Substitutes external clock. For
manufacturing use only.

Off

NOTE

For initialization and normal operation, the four switches must be in the off position. Errors will
occur during initialization if any of the switches are not in the off position.

2.8 HSC50 MODULE INDICATORS AND SWITCHES
All logic modules have at least one LED to indicate board status. Figure 2-10 shows the locations of
these LEOs and the module utilization label. Additionally, three of these logic modules contain specific
switches or fuses.

2-15
HSC CONTROLS/INDICATORS

NOT USED

LINK BOARD _~I:IM
STATUS
INDICATORS

MEMORY ACCESS
INDICATOR

STATE INDICATOR

RUN INDICATOR

~ BOARD

Ii
•

STATUS
INDICATORS

RED
AMBER

® GREEN
CX-021A

Figure 2-10

HSC50 Module LED Indicators

2-16
HSC CONTROLS/INDICATORS

Figure 2-11 shows the slot location for each of the modules.

V>
V>

:.::i

6 UJ t;:
Mod

0
0

~::l
I

CI:l

.....~

~>~ ~>~
OCIJ_

...JCI:U

OCIJ-

...JCI:U

r--

u
0

c':

.....

~>~

OCIJ-

...JCI:U

Bkhd X
Req
Slot

14 13 12 11

CI:l

ItI

CI:l

ItI

c
c

ItI

...JCI:I-

ItI
I
co Cl
0 •• CIJ
->c.
OCIJItI
...JCI:I-

10 9

•• CIJ

->c.
OCIJItI

I
co

0>
~

OCIJItI

ItI

c':

co Cl
o .. ~
->V>
o CIJ._

ItI

<!
<!
I
co

0
0

eC
0

o .. u

~>E

o~o
-lCI:::::'

OCIJCIJ

...JCI::;?!

...JCI:Cl

CIJ

~>~
o CIJ._

•• co

- > ....

c
c

ItI

CIJ

c
c

c:
c

y
7

CX-283B

Figure 2-11

HSC50 Module Utilization Label Example

Table 2-3 shows the functions of the various module LEOs.
Table 2-3

HSC50 Functions of Logic Module LEOs

Module

Color

Function

LOIOS

Amber

State indicator (top LED)-Mirrors the OCP State indicator.

Amber

Run indicator (bottom LED)-Pulses at the on-board microprocessor
run rate.

Red

Board status-Indicates an inoperable module except during
initialization when it comes on during module testing.

Green

Board status-Indicates the module has passed all applicable
diagnostics.

LOI06

Green

Board status-Indicates memory cycles are operating.

L010S-YA
LOIOS-YB
L0119

Green

Board status-Indicates the operating software is running and that
self-test module microdiagnostics have completed successfully.

Red

Board status-Indicates an inoperable module except during
initialization when it comes on during module testing.

2-17
HSC CONTROLS/INDICATORS

Table 2-3 (Cont.)

Module

HSC50 Functions of Logic Module LEOs

Color

Function

Amber (eight LEDs)

LOI07-YA

LOI09

LOIOO-E2

Green

Board status-Indicates the operating software is running and that
self-test module microdiagnostics have completed successfully.

Red

Board status-Indicates an inoperable module except during
initialization when it comes on during module testing.

Green

Board status-Indicates the operating software is running and that all
applicable diagnostics have completed successfully.

Red

Board status-Indicates an inoperable module except during
initialization when it comes on during module testing.

Amber

Always on when HSC50 is on (used only for engineering test
purposes).

Green

Board status-Indicates the node is either transmitting or receiving;
dims or brightens relative to the amount of local CI activity.

Red

Board status-Indicates the module is in the internal maintenance
mode.

LOll 8

2.8.1 HSC50 Moduie Switches and Jumpers
Specific switches and jumpers are found on LINK (LO I 00-E2 or LOlI8), I/O Control Processor
(LOI05), port processor (LOl07), port buffer (LOI09), and data channel (LOl19) modules as follows:
•

CI port link module (LOI00-E2/L0118)-Refer to Figure 2-10 for the CI node address switches
mounted on the LOIOO-E2 or LOl18 module. Switches must be identically set to avoid CI
addressing errors. See Chapter 3 for positions of Sl, S2, and S3.

•

CI port processor and CI port buffer modules (LOI07 and LOI09)-Both the LOI07 and LOl09
modules have dual inline pack (DIP) switches to indicate the hardware revision level. DIP switch
positions should not be changed except as directed by a Field Change Order (FCO). Figure 2-8
shows the location of the these switches.

•

Port link and port link buffer modules (lJ0107 and LOI09)-Both the LOI07 and LOl09
modules have dual inline pack (DIP) switches to indicate the hardware revision level. DIP switch
positions should not be changed except as directed by a Field Change Order (FCO). Refer to
Figure 2-8 for the location of these switches.

•

I/O control module (LOI0S)-The LOl05 module contains a baud rate jumper (W3) to establish
the proper communication rate between the HSC50 and its attached auxiliary terminal. The jumper

2-18
HSC CONTROLS/INDICATORS

determines the baud rate as follows:

•

Jumper W3 in = 9600 baud

•

Jumper W3 out = 300 baud

K.si (LOI19) switcbpack-See Section 2.7.1 for a description of the switchpack and settings.

Figure 2-12 shows the location of the jumper controlling baud rate.

W3
(TAN WITH BLACK STRIPE)

,U-;

E125
E133

,tOll" ~ X148

'~~X157

X 149 /"]::JrI_

~E166

X158

r-L

~E180

1~ 1"E203

ElBB

IE2181
IE2331
IE2411

L0105 - 0 - 0

CX-020S

Figure 2-12

HSC50 Baud Rate Jumper

2.9 881 POWER CONTROLLER
The 881 power controller is a general purpose, three-phase controller that controls and distributes ac
power to various ac devices (power supplies, fans, blower motor, etc.) packaged within an HSC70 and
HSC50 (modified). The 881:
•

Controls large amounts of ac power with low level signals

•

Provides ac power distribution to single-phase loads on a three-phase system

•

Protects data equipment from electrical noise

•

Disconnects ac power for servicing and in case of overload

2-19
HSC CONTROLS/INDICATORS

In addition, the 881 features:

•

Local and remote switching

•

SWITCHED receptacles only

•

Convection cooling

•

Rack mounting

•

ac line filtering

•

DIGITAL power Control bus inputs

•

DIGITAL power Control bus delayed output (to allow sequencing of other controllers)

2.9.1 881 Operating Instructions
The two basic controls on the power controller are the circuit breaker and the BUS/OFF/ON
switch. These and all but one of the other controls are located on the front panel of the controller
(Figure 2-13).

2-20
HSC CONTROLS/INDICATORS

GROMMETED
CORD
OPENING
POWER CONTROL
BUS CONNECTORS

f;\ SECONDARY
\..J ON

O•

SECONDARY
OFF

DELAYED
(0.5 SEC)

I' I
,

REMOTE BUS
CONTROL

INTERNATIONAL SYMBOLS

SERIAL LOGO
LABEL

FUSE

POWER
CONNECTOR

CX-893A

Figure 2-13 Power Controller-Front Panel Controls

The operator controls are described in the following list.
•

Power controller circuit breaker---Controls the ac power to all outlets on the controller. It also
provides overload protection for the ac line loads and is unaffected by switching the BUS/OFF/ON
control.

•

Fuse--Protects the ac distribution system from an overload of the power Control bus circuitry. The
fuse is located on the front panel of the power controller.

2-21
HSC CONTROLS/INDICATORS

•

Power Control bus connections-Used if Control bus connections to another cabinet are required.
DIGITAL power Control bus MAlE-N-LOK connectors are JI0, Jl1, J12, and J13. Connectors 110
and J 11 are not delayed. Connectors J 12 and J 13 are delayed.

•

BUS/OFF/ON switch-The three positions of this switch. Assuming the circuit breaker for the
power controller is ON, the ac outlets are:
-

Energized when the BUS/OFF/ON switch is in the ON position

De-energized when the BUS/OFF/ON switch is in the OFF position

NOTE

The BUS position is intended for remote sensing of DIGITAL power Control bus instructions.
The switch is left in the ON position when the DIGITAL power Control bus is not used.
TOTAL OFF connector-A two-pin male connector on the rear panel of the power controller
(Figure 2-14). It removes power from the HSC whenever the air flow sensor detects system airflow loss or an over temperature condition. To reset the TOTAL OFF, cycle the circuit breaker off
and then back on again.

2-22
HSC CONTROLS/INDICATORS

TOTAL OFF
CONNECTOR

CX-934A

Figure 2-14 881 Rear Panel

2.10 HSC50 POWER CONTROLLER
The 60 Hz power controller is shown in Figure 2-15 and Figure 2-17. For the 50 Hz unit, refer to
Figure 2-16 and Figure 2-18. A physical description of the power controller follows.

2-23
HSC CONTROLSIINDICATORS

DELAYED OUTPUT
CONNECTOR

LINE POWER
CIRCUIT BREAKERS

CB2-4 (SWITCHED)

CB5 (UNSWITCHED)

1-- -- ----I
"-0-°-

---"'--

....... -

ow....,..

_._

- ...........
~

CX-013B

Figure 2-15

HSC50 Power Controller (60 Hz)-Front View

2.10.1 Line Phase Indicators
Three Line Phase indicators display the status of incoming line power. If any phase drops, the indicator
for that phase goes off.

2-24
HSC CONTROLS/INDICATORS

2.10.2 Fuses
The three line phases are fused to protect the HSC50 circuitry. These fuses are located beside the Line
Phase indicators.

DELAYED OUTPUT
CONNECTOR

REMOTE/OFF/LOCAL
ON SWITCH

FUSES

A.C. Input

LINE PHASE
INDICATORS

LINE POWER
CIRCUIT
BREAKER

CB1

CX-013C

Figure 2-16

HSC50 Power Controller (50 Hz)-Front View

2-25
HSC CONTROLS/INDICATORS

2.10.3 Remote/Off/Local On Switch
When this switch is in the Off position, the power controller does not route ac line powei to the
switched or unswitched outlets.
With the switch in the Local On position, ac power is routed to the power controller switched or
unswitched outlets.
When the switch is in the Remote position, the routing of ac power is dependent upon the power
Control bus signals.

2.10.4 Circuit Breakers (60 Hz)
There are five power controller circuit breakers which perform the following functions:
•

CB I-Protects from incoming power surges

•

CB2-4--Protects the switched outlets (refer to Figure 2-15)
CB5-Protects the unswitched outlets

2.10.5 Circuit Breakers (50 Hz)
The 50 Hz unit contains one circuit breaker (Figure 2-16). CB 1 on this unit protects all circuits.

2.10.6 Power Controller (60 Hz)-Rear View
The switched outlets in Figure 2-17 are protected by CB2-4 (refer to Figure 2-15) and the bottom
(unswitched) by CB5. Both the bottom and top outlets are currently unused.
A three-pin male conne.ctor (18) is located on the back of the power controller (Figure 2-17). It
removes power from the HSC whenever the air flow sensor detects system air-flow loss or an over
temperature condition. To reset the TOTAL OFF, cycle the circuit breaker off and then back on again.

2-26
HSC CONTROLS/INDICATORS

~OD.
Alarm-t~tal J7

Off Delayed Contr~1 B~s
UNUSED

J11®~

BLOWER OUTLET

J12~

MAIN POWER
SUPPLY OUTLET

J13~

AUXI LlARY POWER
SUPPLY OUTLET

L2~

L3~

UNSWITCHED

CX-411A

Figure 2-17

HSC50 Power Controller (60 Hz)-Rear View

2.10.7 Power Controller (50 Hz)-Rear View
Outlets in Figure 2-18 are protected by CBl (refer to Figure 2-16). Connector J3, shown at the top of
the 50 Hz power controller rear view, connects the air flow sensor.

2-27
HSC CONTROLS/INDICATORS

J3
Total

Off

J11~

BLOWER OUTLET

L1~

J12~

MAIN POWER
SUPPLY OUTLET

J1Q

AUXI LlARY POWER
SUPPLY OUTLET

L2~

L3~

CX-411B

Figure 2-18

HSC50 Power Controller (50 Hz)-Rear View

3-1
REMOVAL AND REPLACEMENT PROCEDURES

3
REMOVAL AND REPLACEMENT PROCEDURES
3.1

INTRODUCTION

Procedures for removing and replacing the field replaceable units (FRUs) in an HSC are detailed in
this chapter. Observe the safety precautions detailed in the next section before starting removal and
replacement procedures.

3.2 SAFETY PRECAUTIONS
Because hazardous voltages exist inside the HSC, only a qualified service representative should service
the subsystem. Bodily injury or equipment damage can result from improper servicing. Always use the
anti-static wrist strap provided when removing and replacing logic modules.
WARNING

Always remove power from the HSC before removing or installing internal parts or cables.

3.3 HSC70 REMOVAL AND REPLACEMENT PROCEDURES
The following sections describe procedures for removing and replacing the field replaceable units
(FRUs) in an HSC70.

3.3.1 HSC70 Power Removal
Before removing/replacing an FRU, turn off the ac power from the power controller CB 1. To do this,
open the back door with a 5/32-inch hex wrench. The power controller is located on the lower left side
of the cabinet. Figure 3-1 shows the location of ac circuit breaker CB 1.

3-2
REMOVAL AND REPLACEMENT PROCEDURES

:000 IT:
J13 J12 J11 J10

<YO

o CB I

CIRCUIT
BREAKER

POWER
CONNECTOR

CX-1117A

Figure 3-1

HSC70 881 Power Controller Circuit Breaker

3.3.1.1 Removing HSC70 ac Power

To remove ac power, tum off CBl. To ensure absolute safety, disconnect the ac plug from its
receptacle.

3-3
REMOVAL AND REPLACEMENT PROCEDURES

3.3.1.2 Removing HSC70 dc Power

Following are the two methods for removing dc power.
1. Tum off the dc power switch, located on the side of the RX33 housing (Figure 3-2).
2. Tum off CBl (ac power).

HSC70
DC POWER SWITCH

OCP SIGNAL/POWER
LINE CONNECTOR

eX-94GB

Figure 3-2

HSC70 dc Power Switch Location

WARNING

Ensure the OCP SignaIIPower line indicator is connected; otherwise the power indicator on the
OCP can show power off when the power is on.

3-4
REMOVAL AND REPLACEMENT PROCEDURES

3.3.2 HSC70 Field Replaceable Unit (FRU) Removal
Figure 3-3 shows the FRU removal sequence for an HSC70.

OPEN CABI NET FRONT DOOR

MODULES

OCP

RX33

OPEN CABINET BACK DOOR

POWER CONTROLLER

BLOWER

AIR FLOW
SENSOR ASSEMBLY
CABINET FRONT DOOR

CABINET BACK DOOR

MAIN POWER SUPPLY

AUXI LlARY POWER SUPPLY

CX-935A

Figure 3-3 HSC70 FRU Removal Sequence
3.3.2.3 Access From HSC70 Cabinet Front Door

The FRUs accessed via the front door include the RX33, the Operator Control Panel (OCP), and the
logic modules. To remove the front door use the following procedure.
1. Unlock the cabinet front door and lift the latch to open the door.
CAUTION

When performing the following steps, take care not to damage the front spring fingers.
2. Remove HSC70 power by pushing the dc power switch to the 0 position.
3. Disconnect the ground wire from the door.
4. Disconnect the OCP signal/power line connector at the bottom of the OCP shield (refer to
Figure 3-2).
5. Pull down on the spring-loaded rod on the top hinge inside the cabinet and then lift the door off its
bottom pin.

3-5
REMOVAL AND REPLACEMENT PROCEDURES

Reverse the removal procedure to replace the front door.
3.3.2.4 Access From HSC70 Cabinet Back Door

The FRUs accessed via the back door include the power controller, blower, air flow sensor assembly,
main power supply, and auxiliary power supply. To remove the back door, use the following procedure.
1. Open the back door with a 5/32-inch hex wrench.
2. Pull down on the spring-loaded rod on the top hinge inside the cabinet and then lift the door off its
bottom pin.
Reverse the removal procedure to replace the back door.

3.3.3 HSC70 RX33 Cover Plate and Disk Drive Removal and Replacement
The RX33 disk drives are slide mounted in the HSC70 cabinet. A cover plate ensures proper air flow
and cooling (Figure 3-4).

1/4 TURN
FASTENER

II~~I

DRIVE
COVER
PLATE

CX-1118A

Figure 3-4

HSC70 RX33 Cover Plate Removal

Use the following procedure to remove the RX33 cover plate.
1. Unlock the cabinet front door and lift the latch to open the door.

2. Turn off dc power (refer to Figure 3-2).
3. Rotate the four fasteners on the RX33 cover plate one-quarter turn and remove the cover plate.

3-6
REMOVAL AND REPLACEMENT PROCEDURES

Use the following procedure to remove the RX33 disk drives.
1. Completely loosen the two captive screws holding the drive assembly and mounting plate to the
cabinet frame.
CAUTION

Avoid snagging the cables attached to the rear of the drives during the next step.
2. Carefully pullout the slide mounted RX33s until they clear their housing.
3. Support the drives with one hand, and remove the flat ribbon cables and power cables from the rear
of the drives.
4. Determine whether drive 0 or drive 1 should be replaced.
5. Loosen the captive mounting screws (with a flat bladed screwdriver) on the drive to be replaced as
shown in Figure 3-5.

3-7
REMOVAL AND REPLACEMENT PROCEDURES

MOUNTING
PLATE

CAPTIVE
SCREW

RX33

MOUNTING
PLATE

CAPTIVE
C"'r-nrtAI

,;:)\..nc::vv

Figure 3-5

CX-936A

HSC70 RX33 Disk Drive Removal

6. Configure RX33 jumpers on the replacement drive as shown in Figure 3-6.

3-8
REMOVAL AND REPLACEMENT PROCEDURES

El
FG

[]

...J

:; :l I

HG fl1ll1 tl1tl: :,
LG

tnj."

ML RE DC RY

I•• 1•• I.el

Itlll:: I
O~NC""l

U"lU"lU"lU"l

0000

II
CX-937A

Figure 3-6

HSC70 RX33 Jumper Configurations

If replacing drive 0, be sure to insert jumper DSO. If replacing drive 1, be sure to insert jumper
OS!. Section 3.3.3.1 briefly describes the function of each jumper.
NOTE

Replacement RX33 drives shipped from the vendor are not configured for HSC70 application.
Two identical jumpers (part number 12-18783-00) must be added. If no extra jumpers are
available, remove two jumpers from the defective drive. Correct jumper configuration is
necessary for proper operation of the replacement RX33 drive (refer to Section 3.3.3.1).
7. Replace the defective drive with a new drive.
To replace the RX33 drives, reverse the removal procedure.

3-9
REMOVAL AND REPLACEMENT PROCEDURES

3.3.3.1 HSC70 RX33 Jumper Configuration

This section defines the RX33 jumpers. Jumpers identified with an asterisk are connected for HSC
operation.

* FG = frame ground connection
•

LG = logic low on NORMAL/Hl DENSITY signal enables high density mode

• * HG = logic high on NORMAL/Hl DENSITY signal enables high density mode
• * DSO, 1, 2, 3 = drive select number 0, 1, 2, 3
• * I = speed mode I (dual speed mode)
•

II = speed mode II (single speed mode, 360 RPM only)

• * U 1, U2 = selects mode of operation for loading heads and lighting bezel LED (see note)
•

HL, IV = selects mode of operation for loading heads and lighting bezel LED (see note)

•

dc = drive asserts DISK CHANGED signal on pin 34 of interface cable

• * RY = drive asserts DRIVE READY signal on pin 34 of interface cable
ML = motor enable; no jumper installed for HSC70 application
•

RE = Recalibration; no jumper installed for HSC70 application

NOTE

The HSC70 loads heads and lights the drive-in-use LED when DRIVE SELECT n and READY
are both true.

3.3.4 HSC76 Operator Control Panel (OCP) Removal and Replacement
H any OCP lamp fails, replace the entire OCP with the following procedure.
1. Open the front door by turning the key clockwise and lifting the latch.
2. Remove dc power (refer to Figure 3-2).
3. Remove the four Kepnuts securing the OCP shield to the studs on the front door.
4. Remove the OCP shield.
5. Remove the four screws securing the OCP to the shield (Figure 3-7).

3-10
REMOVAL AND REPLACEMENT PROCEDURES

OCP SHIELD

OCP
MOUNTING
SCREWS

CX-938A

Figure 3-7 HSC70 Operator Control Panel Removal

6. Remove the two connectors from the printed circuit board on the OCP.
7. Pullout the OCP, carefully allowing for indicator and switch clearance.
Reverse the removal procedure to replace the OCP.

3-11
REMOVAL AND REPLACEMENT PROCEDURES

3.3.5 HSC70 Logic Modules Removal and Replacement
A Velo~tat anti-static kit (part number 29-11762) must be used during module removai/repiacement.
For convenience, an anti-static wrist strap is included in the front door diskette storage area.
Removal of the HSC70 logic modules is detailed in the foliowing iist.
1. Open the front door by turning the key clockwise.
2. Push the dc power switch to the 0 (off) position (refer to Figure 3-2).

3. Tum the two nylon latches on the module cover plate one-quarter tum (Figure 3-8).

NYLON
LATCHES

DISKETTE
STORAGE
AREA

CX-887B

Figure 3-8

HSC70 Card Cage Cover Removal

3-12
REMOVAL AND REPLACEMENT PROCEDURES

To remove the LOt 00 port link module, the door latch plate attached to the left side of the cabinet
frame must be moved away from the module removal path. In production model HSC70s the latch
plate is swivel mounted. Lift the plate slightly and press it flat against the cabinet frame. Before
closing the cabinet door, return the door latch plate to its locked position.
Reverse the removal procedure to replace the card cage cover.
NOTE

3--13
REMOVAL AND REPLACEMENT PROCEDURES

S-l

I~ : oI ~ 1
,,"
4
8
4--5 - - - P 16
6 - - - E 32
7 - - - N 64
8--128

VALUE OF EACH

SWITCH

DIP SWITCH
(EXAMPLE: BINARY 3)

S-2
1
2

•
•

1
2

4
5

P
E

8
16

N 32

7
8

64
128

L!"PORT LINK MODULE
CX-888A

Figure 3-9

HSC70 Node Address Switches (L0100) LINK Module

Figure 3--10 shows the LOlOO, Rev-E2 LINK module or the LOll8 LINK module node address
switches.
See the system manager for the correct node address.

3-14
REMOVAL AND REPLACEMENT PROCEDURES

OF
NF
t=- 1
t=- 2
KJ
KJ
KJ
KJ
KJ
KJ

3
4
5 51

6
7

LINK
MODULE

OF
NF

r=- 1

c. 2
KJ
KJ
KJ
.:J
.:J
KJ

3
4
5

6
7

8
0

OF
NF

[Il'

-=:J 2
IIJ 3
ClI 4

FRONT
VIEW
CX-1885A

Figure 3-10 HSC70 Node Address Switches L0100, Rev-E2 or L0118 LINK Module

The LO 118 port link module also has jumpers that must be installed or removed. Figure 3-11 shows
the jumper configuration for the L0118, Rev-A LINK module.

3-15
REMOVAL AND REPLACEMENT PROCEDURES

-D- ...---.....,

-c::J-~

--CJ-

L--_.....II ...------.

-c:::::J- ~-"""I

I E25
-0-+++

o--c:r

II
E62
-c=J- -c::J- +++

NOTE: BOXES INDICATE THE DEFAULT JUMPER POSITIONS.
CX-1910A

Figure 3-11

HSC70 L0118 LINK Module, Rev-A Jumper Configuration

The jumper/switch configurations significance are as follows:
•

SI / S2-Node number (same as LOl00)

•

S3-1-Cluster Size (GTI5), Def =Less than 15 = Sw ON

•

S3-2, 3, 4-Slot count, Def = 7 Ticks = ALL Sw's ON

•

WI-Extender header, Def =Not used

•

W2-Active hub arbitration, Def = Not used

•

W3-Extender ACK timeout, Def = Not used

•

W4-Cluster size (GT32), Def =Less than 32

3-16
REMOVAL AND REPLACEMENT PROCEDURES

Figure 3-12 shows the jumper configuration for the LOl18, Rev-Bl LINK module.

W21~~ IW4
NOTE:

BOXES INDICATE THE Wl AND W3 DEFAULT JUMPER
POSITIONS. THE DEFAULT FOR JUMPERS W2 AND
W41S "OUT".
CX-1911A

Figure 3-12

HSC70 L0118 LINK Module, Rev·B1 Jumper Configuration

3-17

REMOVAL AND REPLACEMENT PROCEDURES

Figure 3-13 shows the jumper configuration for the LOllS, Rev-B2 LINK module.

~_-,I I

11
. . . __. . . .

-c::r-

-D--

-D- ....----.....

NOTE: BOXES INDICATE THE DEFAULT JUMPER POSITIONS.
CX-1912A

Figure 3-13

HSC70 L0118 LINK Module, Rev·B2 Jumper Configuration

3.3.6 HSC70 Airflow Sensor Assembly Removal and Replacement
The airflow sensor assembly, housed in the cooling duct, is removed by the following procedure.
1. Open the back door using a hex wrench.
2. Turn off the ac circuit breaker (CB1) on the HSC70 power controller.
3. Disconnect J70 (Figure 3-14).
4. Remove the Phillips head screw that holds the mounting clamp to the duct.

3-18
REMOVAL AND REPLACEMENT PROCEDURES

5. Slide the sensor assembly out of the duct.

PHI LLiPS
HEAD
SCREW

AIRFLOW
SENSOR

eX-940B

Figure 3-14 HSC70 Airflow Sensor Assembly Removal

Reverse the removal procedure to replace the airflow sensor assembly. Align the slots in the airflow
sensor tip horizontally with the floor. Mter turning on ac power to the HSC70, test the new airflow
sensor for proper operation by blocking the flow of air.

3-19
REMOVAL AND REPLACEMENT PROCEDURES

3.3.7 HSC70 Blower Removal and Replacement
The blower, which provides forced air cooiing for the cabinet, is removed by using the following
procedure.
1. Open the back door using a 5/32-inch hex wrench.
2. Turn off ac power (CB1 on the power controller).
3. Disconnect the blower power connector.
4. Remove the exhaust duct from the bottom of the blower by lifting up the quick release latches on
each side of the duct (Figure 3-15).

3 PHI LLiPS HEAD SCREWS
(SECURE BLOWER
MOUNTING BRACKET)

REMOVABLE
EXHAUST DUCT

COOLING BLOWER
POWER CONNECTOR

s~
AIRFLOW SENSOR
POWER CONNECTOR
(J70)

AIRFLOW
SENSOR

I I

QUICK RELEASE
LATCHES

eX-939B

Figure 3-15

HSC70 Main Cooling Blower Removal

5. Disconnect the airflow sensor power connector (170) to allow removal of the exhaust duct.
NOTE

Figure 3-15, Figure 3-14, and Figure 3-16 show the blower outlet duct for current HSC70s.
Earlier models have a smaller blower motor outlet duct.
6. Loosen, but do not remove, the three Phillips screws holding the blower mounting bracket to the
cabinet.

3-20
REMOVAL AND REPLACEMENT PROCEDURES

7. Lift the blower and bracket up and out of the cabinet.
Reverse the removal procedure to replace the cooling blower.

3.3.8 HSC70 Power Controller Removal and Replacement
The power controller must be removed to replace either of the power supplies. To do this, use the
following procedure.
1. Open the back door.
2. Remove rear door latch to allow clearance for power controller removal.
3. Remove ac power by placing CB 1 in the off position (refer to Figure 3-1).
4. Unplug the power controller from the power source.
5. Remove the two top screws and then the two bottom screws securing the power controller to the
cabinet (Figure 3-16). While removing the two bottom screws, push up on the power controller to
take the weight off the screws.

3-21
REMOVAL AND REPLACEMENT PROCEDURES

MAIN POWER
SUPPLY LINE
CORD

COOLING
BLOWER
LINE CORD

DID
pip

PHASE DIAGRAM

POWER

~~~::::::====, CaNT R a L LE R
SCREWS

POWER
CONTROLLER
LINE CORD

CX-941B

Figure 3-16 HSC70 Power Controller Removal
CAUTION

Do not pull the power controller out too far because cables are connected to the back and
top.
6. Pull the power controller towards you and then out.
7. Remove the power control bus cables from connectors J10, J11, J12, and J13 at the front of the
power controller (refer to Figure 3-1).

3-22
REMOVAL AND REPLACEMENT PROCEDURES

8. Disconnect the total off connector at the rear of the power controller (Figure 3-17).

TOTAL OFF
CONNECTOR

CX-934A

Figure 3-17

HSC70 881 Power Controller-Rear Panel

9. Disconnect all line cords from the top of the power controller.
NOTE

Be sure to rotate the line cord elbow to the vertical position if replacing a defective power
controller with a new one. To rotate the elbow remove the set screw, rotate the elbow to the
position shown in Figure 3-1, and replace the set screw in the other hole.
Reverse the removal procedure to replace the power controller.
NOTE

To ensure proper phase distribution" reconnect the main power supply, auxiliary power supply,
and cooling blower line cords as shown in Figure 3-16.

3-23

REMOVAL AND REPLACEMENT PROCEDURES

3.3.9 HSC70 Main Power Supply Removal and Replacement
The following procedure covers the removal of the main power supply.
WARNING

The power supply is heavy. Support it with both hands to prevent dropping.
1. Open the back door using a 5/32-inch hex wrench.
2. Tum off ac power (CB 1) on the power controller.
3. Unplug the power controller from the power source.
4. Remove the front door.
5. Remove the power controller (Section 3.3.8) to access the back of the power supply.
6. Unplug the main power supply line cord at the power controller.
7. Remove the nut from the -VI stud (ground) on the back of the power supply (Figure 3-18).
8. Remove the nut from the +Vl stud (+5 volts) on the back of the power supply.
9. Remove the nut from the - V2 (ground) stud on the back of the power supply.
10. Remove the nut from the +V2 (-5.2 volts) stud.
11. Unplug J31 (+12 VDC output from the supply to backplane, power fail, and -5 volts sense line).
12. Unplug P32 (+12 VDC sense line and +5 VDC sense line).
Figure 3-18 shows the HSC70 main power supply test points.

3-24
REMOVAL AND REPLACEMENT PROCEDURES

WIRE LIST
COLOR

POSITION

COLOR

POSITION

PUR

TBI-3-5

12 V

PUR

TBI-3-1

12 V SENSE

PUR

TBI-3-6

12 V

BLU

TBI-2-7

ACC

TBI-3-3

GND (12 V)

BLK

SIGNAL

BRN

TBI-2-6

GRN/YEL

TBI-2-5

GND

-5 V SENSE

YEL

TBI-2-3

ON/OFF (-5,3 V)

BLK
ORN

TBI-2-2

SIGNAL

BLK

TBI-2-1

GND (-5 V SENSE)

ORN

TBI-2-2

-5 V SENSE (52-)

BRN

TBI-1-4

POWER FAIL

BLU

TBI-1-3

ON/OFF 5 V

BLK

TBI-1-2

GND (5 V SENSE)

BLK

TBI-1-2

GND (5 V SENSE)

RED

TBI-1-1

5 V SENSE

PUR

TBI-3-2

12 V

BLK

TBI-3-4

GND (12 V SENSE)

MAIN POWER SUPPLY - REAR VIEW
J35
POWER TO
AIRFLOW SENSOR

POWER FAIL

LINE CORD
CONNECTIONS

J34
TO AUXI LlARY
POWER SUPPLY
- -.....~~TO BACKPLANE

+5 V
+V1

FLEXBUS

Figure 3-18 HSC70 Main Power Supply Cables-Disconnection

CX-942B

3-25
REMOVAL AND REPLACEMENT PROCEDURES

13. Unplug J33 (to dc power switch) (Figure 3-18).
14. Unplug J34 (remote on/off jumper to auxiliary power supply) (Figure 3-18).
15. Unplug J35 (+12 VDC power to the airflow sensor) (Figure 3-18).
16. Turn the four captive screws on the front of the power supply counterclockwise (Figure 3-19).

MAIN POWER
SUPP L Y CAB LES

CAPTIVE
SCREWS

CX-1157A

Figure 3-19

HSC70 Main Power Supply Removal

17. Pull the power supply out about an inch. Check the back of the cabinet to ensure the cables and
fiexbus connectors are clear and will not snag when the supply is completely removed.
18. Carefully pull the power supply all the way out of the cabinet.

NOTE

Spare power supplies are not shipped with a power cord.
Reverse the removal procedure to replace the main power supply.

3.3.10 HSC70 Auxiliary Power Supply
An HSC70 requires an auxiliary power supply. The auxiliary power supply is mounted directly beneath
the main power supply. The procedure for mounting the auxiliary power supply follows.
WARNING

This power supply is heavy. When removing, support it with both hands to prevent dropping.
1. Open the back door using a 5/32-inch hex wrench.
2. Turn off ac power (CBl) on the power controller.
3. Unplug the power controller from the power source.

3-26
REMOVAL AND REPLACEMENT PROCEDURES

4. Remove the front door.
5. Remove the power controller to access the back of the power supply (Section 3.3.8).
6. Unplug the auxiliary power supply line cord at the power controller.
7. Remove the nut from the +VI stud (+5 volt) on the back of the power supply (Figure 3-20).
Figure 3-20 shows the HSC70 auxiliary power supply test points.

WIRE LIST
COLOR

POSITION

SIGNAL

BLACK

TBI-2

GROUND (5 V SENSE)

RED

TBI-l

5 V SENSE

BROWN

TBI-4

POWER FAIL

BLUE

TBI-7

ACC
AC

BROWN

TBI-6

GRN/YEL

TBI-5

CHASSIS GROUND

BLUE

TBI-3

ON/OFF

BLACK

TBI-2

GROUND (5 V SENSE)

AUXI LlARY POWER SUPPLY - REAR VIEW

----.

POWER FAIL

TO BACKPLANE

POWER SUPPLY
TERMINAL STRIP

J51
TO BACKPLANE

J50
TO MAIN
POWER SUPPLY

FLEXBUS

LINE CORD
TO POWER
CONTROLLER

CX-943A

Figure 3-20 HSC70 Auxiliary Power Supply Cable Disconnection

8. Remove the nut from the -VI stud (ground) on the back of the power supply (Figure 3-20).
9. Disconnect J50 (sense line to voltage comparator) (Figure 3-20).
10. Disconnect J51 (dc on/off jumper) (Figure 3-20).

3-27

REMOVAL AND REPLACEMENT PROCEDURES

11. Tum the four captive screws on the power supply counterclockwise (Figure 3-21).

AUXI LlARY POWER
SUPPLY CABLES

CAPTIVE
SCREWS

SUPPLY GUIDANCE
TRACK

Figure 3-21

AUXI LlARY POWER
SUPPLY

CX-1158A

HSC70 Auxiliary Power Supply Removal

12. PuB the power supply out about an inch. Check the back of the cabinet to ensure the cables and
flex bus connectors are clear.
13. Carefully slide the power supply out through the front of the HSC70.
14. Remove the power cord from the failing unit and install on the new power supply.
NOTE

Spare supplies are not shipped with a power cord.
Reverse the removal procedure to replace the auxiliary power supply.

3-28
REMOVAL AND REPLACEMENT PROCEDURES

3.4 HSC50 (MODIFIED) REMOVAL AND REPLACEMENT
PROCEDURES
The following sections describe procedures for removing and replacing the field replaceable units
(FRUs) in an HSC50 (modified).

3.4.1 HSC50 (Modified) Power Removal
Before removing/replacing an FRU, turn off the ac power from the power controller CBl. Open the
back door with a 5/32-inch hex wrench. The power controller is located on the lower left side of the
cabinet. Figure 3-22 shows the location of ac circuit breaker CB 1.

D
J13 J12 Jll Jl0

o CB I

CIRCUIT
BREAKER

POWER
CONNECTOR

CX-1117A

Figure 3-22

HSC50 (Modified) 881 Power Controller Circuit Breaker

3-29
REMOVAL AND REPLACEMENT PROCEDURES

3.4.1.1 Removing HSC50 (Modified) ac Power
To remove ac power tum off CBl. To ensure absolute safety, disconnect the ac plug from its receptacle.
3.4.1.2 Removing HSC50 (Modified) dc Power
Following are the methods for removing dc power.
1. Turn off the dc power switch, located on the maintenance access panel (Figure 3-23).

1 ON POSITION

a OFF POSITION

ocp
CONNECTOR

CONNECTORS RESERVED
FOR FUTURE USE

MAINTENANCE TERMINAL
SIGNAL CONNECTOR
MAINTENANCE
TERMINAL POWER

CX-014B

Figure 3-23

HSC50 (Modified) Maintenance Access Panel

2. Turn off ac power (CB 1) (refer to Figure 3-22).

3-30
REMOVAL AND REPLACEMENT PROCEDURES

3.4.2 HSC50 (Modified) FRU Removal Sequence
Figure 3-24 shows the FRU removal sequence for an HSC50 (modified).

OPEN CABINET FRONT DOOR

MODULES

TU58 DRIVES

TU58 CONTROLLER MODULE

OCP

OPEN CABINET BACK DOOR

POWER CONTROLLER
BLOWER
AIR FLOW SENSOR ASSEMBLY

CABINET FRONT DOOR

CABINET BACK DOOR

MAIN POWER SUPPLY
AUXI L1ARY POWER SUPPLY

CX-015C

Figure 3-24

HSC50 (Modified) FRU Removal Sequence

3.4.3 HSC50 (Modified) Cabinet Front Door
Use the following procedure to remove the HSC50 (modified) cabinet front door.
1. Open the cabinet front door by turning the key clockwise.
CAUTION

When performing the following steps, take care not to damage the front spring fingers.
2. Disconnect the ground wire from the door.

3-31
REMOVAL AND REPLACEMENT PROCEDURES

3. Remove the maintenance access panel by loosening the four captive screws.
CAUTION

Some HSC50 (modifieds) have a hinged maintenance access panel with only one captive screw.
4. Remove HSC50 (modified) power by pushing the dc power switch to the 0 position.
5. Remove the plastic cable duct cover.
6. Disconnect cables from the maintenance access panel (refer to Figure 3-23).
7. Pull down on the spring-loaded rod on the top hinge inside the cabinet and then lift the door off its
bottom pin.
Reverse the removal procedure to replace the front door.

3.4.4 HSCSO (Modified) Cabinet Back Door
Use the following procedure to remove the HSC50 (modified) cabinet back door.
1. Open the back door with a 5/32-inch hex wrench.
2. Pul1 down on the spring-loaded rod on the top hinge inside the cabinet and then lift the door off its
bottom pin.
Reverse the removal procedure to replace the back door.

3.4.S HSCSO (Modified) TUSS Bezel Assembly
Use the following procedure to remove the HSC50 (modified) TU58 bezel assembly.
1. Open the front door.
2. Remove the maintenance access panel by loosening the four captive screws.
3. Relnove HSC50 (modified) dc power by pushing the dc power switch to the 0 position.
4. Remove the two locknuts on the bottom of the TU58 bezel assembly (Figure 3-25).

3-32
REMOVAL AND REPLACEMENT PROCEDURES

•

--- --•

eX-OlGA

Figure 3-25

HSC50 (Modified) TU58 Bezel Assembly Removal

CAUTION

When servicing the TUS8, avoid bending the tachometer disk mounted on· the drive motor
shaft. If the disk is bent but not creased it may be straightened. If it cannot be straightened
or if it is creased, the TU58 must be replaced. The disk should not rub against the optical
sensor block or any dangling wires.
5. Push the TU58 bezel assembly up about an inch to clear the mounting hooks from their slots. Pull
the bezel assembly back three to four inches from the door for clearance.
6. Support the TU58 bezel assembly with one hand while disconnecting J3 and J4 from the OCP
(Figure 3-26).

3-33
REMOVAL AND REPLACEMENT PROCEDURES

J3
(20 PINS)

OPERATOR CONTROL
PANEL PCB
...............

PHI LLiPS HEADE:::::..-U----SCREWS
(4 TOTAL)

CX-01SA

Figure 3-26

HSC50 (Modified) Operator Control Panel Removal

7. Disconnect cables from the TU58 controller module (Figure 3-27).

3-34
REMOVAL AND REPLACEMENT PROCEDURES

SECURE/ENABLE
SWITCH

HEAD
COVER

CAUTION:
CONNECTOR CAN BE
REVERSED. OBSERVE
PIN USAGE.

BAUD RATE
JUMPERS
(FACTORY SET)

ACCESS PANEL
CX-017B

Figure 3-27

HSC50 (Modified) TU58 Controller Removal

NOTE

The head cover shown upper left in Figure 3-27 should be removed during operation.
8. Slide the controller module out of the plastic guides.
Reverse the removal procedure to replace the TU58 drives.

3.4.6 HSC50 (Modified) TU58 Controller Module
Use the following procedure to remove the HSC50 (modified) TU58 controller module.
1. Perform steps 1 through 8 of the TU58 drives' removal procedure.

2. Ensure the baud rate jumper setting on the new module is the same as on the replaced module
(refer to Figure 3-27 for jumper location).
Reverse the removal procedure to replace the TU58 controller module.

3-35

REMOVAL AND REPLACEMENT PROCEDURES

3.4.7 HSC50 (Modified) Operator Control Panel (OCP)
OCP indicators are not field replaceable. H any lamp fails, replace the entire OCP as follows:
1. Open the front door by turning the key clockwise.
2. Remove dc power.
3. Remove TU58s (Section 3.4.5).
4. Remove J3 and J4 from the OCP (refer to Figure 3-26).
5. Remove the four screws from the OCP (refer to Figure 3-26).
6. Carefully pull out the OCP, allowing for indicator and switch clearance.
Reverse the removal procedure to replace the OCP.

3.4.8 HSC50 (Modified) Logic Modules Removal and Replacement
A Velostat anti-static kit (part number 29-11762) must be used during module removal/replacement.
Removal procedures are described in the following list.
1. Open the front door by turning the key clockwise.
2. Remove dc power by opening the maintenance access panel (refer to Figure 3-23) and pushing the
dc power switch to the 0 position (off) (refer to Figure 3-23).
3. Tum the two nylon latches on the module cover plate one-quarter turn (Figure 3-28).

3-36
REMOVAL AND REPLACEMENT PROCEDURES

NYLON LATCHES

AIRFLOW
WARNING
LABEL

eX-OlgA

Figure 3-28

HSC50 (Modified) Card Cage Cover Removal

4. Pull the card cage cover up and out.
5. Check the module utilization label above the card cage for the location of the desired module. The
module slots are numbered from right to left, viewed from the module cover side.
6. Remove the module and replace with a new module.
Reverse the removal procedure to replace the card cage cover.
Han 1/0 Control Processor module is being replaced, set the baud rate jumper to match the tenninal in
use (Figure 3-29). To set the baud rate for 9600, leave jumper W3 intact. To set a baud rate of 300,
cut one elbow angle on the W3 lead and spread slightly to avoid contact between the cut edges.

3-37
REMOVAL AND REPLACEMENT PROCEDURES

W3
(TAN WITH BLACK STRIPE)

'U-:::

E125
E133

O~·~ ~X'48

X149

~~X'57

/
X158

D.--- E166

I) 1'--E203

E180
E188

IE2181
IE2331
IE2411

L0105-0-0
CX-020B

Figure 3-29

HSC50 (Modified) 1/0 Control Processor Module Baud Rate Jumper

NOTE

module.
Figure 3-30 shows the LOIOO LINK module node address switches.

3-38
REMOVAL AND REPLACEMENT PROCEDURES

S-l

••

1
2

P
E
N

5
6
7
8

1
2
4
8
16
32
64
128

VALUE OF EACH

DIP SWITCH
(EXAMPLE: BINARY 3)

S-2
1
2

•
•

1
2

5
6

E
N

16
32
64
128

7
8

PORT LINK MODULE

eX-SSSA

Figure 3-30

HSC50 (Modified) Node Address Switches (L0100) LINK Module

Figure 3-31 shows the LOlOO, Rev-E2 LINK module or the LOllS LINK module node address
switches.
See the system manager for the correct node address.

3-39.
REMOVAL AND REPLACEMENT PROCEDURES

OF
NF
C. 1
C. 2

.:J 3
II:J 4
II:J 5 S1
II:] 6
.:J 7
II:]

LINK
MODULE

OF
NF

r.:. 1
r.:. 2

.:J 3
II:]

.:J 5 S2
.:J 6
II:] 7
.:J 8
0

OF
NF
S3

[I'

.::J 2

.:J 3

c::. 4

FRONT
VIEW
CX-1885A

Figure 3-31

HSC50 (Modified) Node Address Switches L0100, Rev-E2 or (L0118) LINK Module

The LOl18 port link module also has jumpers that must be installed or removed. Figure 3-32 shows
the jumper configuration for the L0118, Rev-A LINK module.
The jumper/switch configurations significance are as follows:
•

Sl I S2-Node number (same as LOlOO)

•

S3-1-Cluster Size (OTIS), Def =Less than 15 = Sw ON

•

S3-2, 3, 4-S10t count, Def = 7 Ticks = ALL Sw's ON

•

WI-Extender header, Def = Not used

•

W2-Active hub arbitration, Def = Not used

•

W3-Extender ACK timeout, Def = Not used

•

W4-Cluster size (OT32), Def =Less than 32

3-40
REMOVAL AND REPLACEMENT PROCEDURES

~---L..-~-II~I
~_---,II'--~---,II
I

-0-

-Cl-

-c:J-

-cr

-CJ-

-D-

I I --cr

I
I

I
-c:::}-

I
Wl

I E25

--0-+++

II
II

-c:::J--~

o-t::J-

-c:J-

-c::::1-

II
E62

-c=J- -c:::J- +++

II
I
~

El
-c::t-

W2
NOTE: BOXES INDICATE THE DEFAULT JUMPER POSITIONS.
CX-1910A

Figure 3-32

HSC50 (Modified) LOllS LINK Module, Rev·A Jumper Configuration

3-41
REMOVAL AND REPLACEMENT PROCEDURES

Figure 3-33 shows the jumper configuration for the LOll8, Rev-Bl LINK module.

II
-D-

t+1
-0-

-D-

-CJ-

I
ID
-c::r
I
I -c::r
I I -cr I
I
I

I E25

-CJ-

-D-

-CJ-

-c:::l- --c::::J-

--c::::J-

--c:J-

I E62

-c:J- -c:J- ++++

NOTE:

--0-+++

o--cJ~

I
I

[±±]~

!!
I
~

-c::J-

BOXES INDICATE THE W1 AND W3 DEFAULT JUMPER
POSITIONS. THE DEFAULT FOR JUMPERS W2 AND
W41S "OUT".

CX-1911A

Figure 3-33

HSC50 (Modified) L0118 LINK Module, Rev-B1 Jumper Configuration

3-42
REMOVAL AND REPLACEMENT PROCEDURES

Figure 3-34 shows the jumper configuration for the LOl18, Rev-B2 LINK module.

L - - _ - ' - -_ _

--'--_~_----'IIL__

__JI
~----,II~__.....1
--0-

-D-

-0-1.-_-----11 L..-I_---II L..-I_......II

L....------III

. I

-D- .---.....,
~

I
-c::J- -c::J-

-0-

L..-_--II .--------,

-c::J- .-----.,

Wl
E25

-0-+++

o-t::l-

~-"""'I~I_~___JII~__JII~_----J--~-

E62

NOTE: BOXES INDICATE THE DEFAULT JUMPER POSITIONS.
CX-1912A

Figure 3-34

HSC50 (Modified) L0118 LINK Module, Rev-B2 Jumper Configuration

3.4.9 HSC50 (Modified) Airflow Sensor Assembly Removal and Replacement
The airflow sensor assembly, housed in the cooling duct, is removed by the following procedure.
1. Open the back door using a hex wrench.
2. Tum off the ac circuit breaker (CB 1) on the HSC50 (modified) power controller (refer to
Figure 3-22).
3. Disconnect J70 (Figure 3-35).
4. Remove the Phillips head screw that holds the mounting clamp to the duct.

3-43
REMOVAL AND REPLACEMENT PROCEDURES

5. Slide the sensor assembly out of the duct.

AIRFLOW
SENSOR

CX-940B

Figure 3-35

HSC50 (Modified) Airflow Sensor Assembly Removal

Reverse the removal procedure to replace the airflow sensor assembly. Align the slots in the airflow
sensor tip horizontally with the floor. After turning on ac power to the HSC50 (modified), test the new
airflow sensor for proper operation by blocking the flow of air.

3-44
REMOVAL AND REPLACEMENT PROCEDURES

3.4.10 HSC50 (Modified) Blower Removal
The blower, which provides forced air cooling for the cabinet, is removed by using the following
procedure.
1. Open the back door using a 5/32-inch hex wrench.
2. Turn off ac power (CBl on the power controller) (refer to Figure 3-22).
3. Disconnect the blower power connector (Figure 3-36).

3 PHI LLiPS HEAD SCREWS
(SECURE BLOWER
MOUNTING BRACKETI

REMOVABLE
EXHAUST DUCT

COOLING BLOWER
POWER CONNECTOR

AIRFLOW SENSOR
POWER CONNECTOR
(J70)

Figure 3-36

AIRFLOW
SENSOR

eX-939B

HSC50 (Modified) Main COOling Blower Removal

4. Remove the exhaust duct from the bottom of the blower by lifting up the quick release latches on
each side of the duct (Figure 3-36).
5. Disconnect the airflow sensor power connector (170) to allow removal of the exhaust duct
(Figure 3-36).
NOTE

Figure 3-15, Figure 3-14, and Figure 3-16 show the blower outlet duct for current HSC50
(modifieds). Earlier models have a smaller blower motor outlet duct.
6. Loosen, but do not remove, the three Phillips screws holding the blower mounting bracket to the
cabinet.

3-45

REMOVAL AND REPLACEMENT PROCEDURES

7. Lift the blower and bracket up and out of the cabinet.
Reverse the removal procedure to replace the cooling blower.

3.4.11 HSC50 (Modified) Power Controller Removal and Replacement
The power controller must be removed to replace either of the power supplies. To do this, use the
following procedure.
1. Open the back door.
2. Remove rear door latch to allow clearance for power controller removal.
3. Remove ac power by placing CBl in the off position (refer to Figure 3-22).
4. Unplug the power controller from the power source.
5. Remove the two top screws and then the· two bottom screws securing the power controller to the
cabinet (Figure 3-37). While removing the two bottom screws, push up on the power controller to
take the weight off the screws.

3-46
REMOVAL AND REPLACEMENT PROCEDURES

MAIN POWER
SUPPLY LINE
CORD

COOLING
BLOWER
LINE CORD

PHASE DIAGRAM

LINE CORD

POWER

~~S=====-, CONTROLLER
SCREWS

POWER
CONTROLLER
LINE CORD

Figure 3-37

CX-941B

HSC50 (Modified) 881 Power Controller Removal

CAUTION

Do not pull the power controller out too far because cables are connected to the back and
top.
6. Pull the power controller towards you and then out.
7. Remove the power Control bus cables from connectors J10, J11, J12, and J13 at the front of the
power controller (refer to Figure 3-22).

3-47
REMOVAL AND REPLACEMENT PROCEDURES

8. Disconnect the total off connector at the rear of the power controller (Figure 3-38).

TOTAL OFF
CONNECTOR

Ift-IEI

" ,
ILEi+
I-LI~

lUI
CX-934A

Figure 3-38

HSC50 (Modified) 881 Power Controller-Rear Panel

9. Disconnect all line cords from the top of the power controller.
NOTE

Be sure to rotate the line cord elbow to the vertical position if replacing a defective power
controller with a new one. To rotate the elbow remove the set screw, rotate the elbow to the
position shown in Figure 3-22, and replace the set screw in the other hole.
Reverse the removal procedure to replace the power controller.
NOTE

To ensure proper phase distribution, reconnect the main power supply, auxiliary power supply,
and cooling blower line cords as shown in Figure 3-37.

3-48
REMOVAL AND REPLACEMENT PROCEDURES

3.4.12 HSC50 (Modified) Main Power Supply Removal
Use the following procedure to remove the HSC50 (modified) main power supply.
WARNING

The power supply is heavy. Support it with both hands to prevent dropping.
1. Open the back door using a 5/32-inch hex wrench.
2. Turn off ac power (CB 1) on the power controller (Figure 3-22).
3. Unplug the power controller from the power source.
4. Remove the front door.
5. Remove the power controller (Section 3.4.11) to access the back of the power supply.
6. Unplug the main power supply line cord at the power controller.
7. Remove the nut from the -VI stud (ground) on the back of the power supply (Figure 3-39).
Figure 3-39 shows the HSC50 (modified) main power supply test points.

3-49
REMOVAL AND REPLACEMENT PROCEDURES

BACKPLANE

MAiN POWER SUPPLY - REAR VIEW

POWER TO
AI R F LOW SENSOR

J34
TO AUXI LlARY
POWER SUPPLY

TO MAIN
POWER SUPPLY

SWITCH

TO AUXI LlARY
POWER SUPPLY

LINE CORD
CONNECTIONS
4 BLACK WIRES
FROM BACKPLANE
CX-048A

Figure 3-39

HSC50 (Modified) Main Power Supply Cables-Disconnection

8. Remove the nut from the +V1 stud (+5 volts) on the back of the power supply (Figure 3-39).
9. Remove the nut from the -V2 (ground) stud on the back of the power supply (Figure 3-39).
10. Remove the nut from the +V2 (-5.2 volts) stud on the back of the power supply (Figure 3-39).
11. Unplug J31 (+12 VDC output from the supply to backplane, power fail, and -5 volts sense line)
(Figure 3-39).
12. Unplug P32 (+12 VDC sense line and +5 VDC sense line) (Figure 3-39). Ensure the P32 cable is
free to be removed with the power supply.

3-50

REMOVAL AND REPLACEMENT PROCEDURES

13. Unplug J33 (to dc power switch) (Figure 3-39).
14. Unplug J34 (remote on/off jumper to auxiliary power supply) (Figure 3-39).
15. Unplug J35 (+12 VDC power to the airflow sensor) (Figure 3-39).
16, Turn the four captive screws on the front of the power supply counterclockwise (Figure 3-40).

MAIN POWER
SUPP L Y CAB LES

CAPTIVE
SCREWS

11111111

IIIIIIII
11111111

CX-026S

Figure 3-40

HSC50 (Modified) Main Power Supply Removal

17. Pull the power supply out about an inch. Check the back of the cabinet to ensure the cables are
clear and will not snag when the supply is completely removed.
18. Carefully pull the power supply all the way out of the cabinet.
19. Remove the power cord from the failing unit and install it on the new power supply.
NOTE

Spare power supplies are not shipped with a power cord.
Reverse the removal procedure to replace the main power supply.

3-51
REMOVAL AND REPLACEMENT PROCEDURES

3.4.13 HSC50 (Modified) Auxiliary Power Supply
An HSC50 requires an auxiliary power supply if the tota1 module count in the card cage is more than
eight. The auxiliary power supply is mounted directly beneath the main power supply. The procedure
for removing the auxiliary power supply follows.
WARNING

This power supply is heavy. When removing, support it with both hands to prevent dropping.
1. Open the back door using a 5/32-inch hex wrench.
2. Turn off ac power (CB 1) on the power controller (refer to Figure 3--22).
3. Unplug the power controller from the power source.
4. Remove the front door.
5. Remove the power controller to access the back of the power supply (Section 3.4.11).
6. Unplug the auxiliary power supply line cord at the power controller.
7. Remove the nut from the +Vl stud (+5 volt) on the back of the power supply (Figure 3--41).
Refer to Figure 3--41 for the HSC50 (modified) auxiliary power supply test points.

3-52
REMOVAL AND REPLACEMENT PROCEDURES

WI RE LIST
COLOR

POSITION

SIGNAL

BLACK

TBI-2

GROUND (5 V SENSE)

RED

TBI-l

5 V SENSE

BROWN

TBI-4

POWER FAIL

BLUE

TBI-7

ACC

BROWN

TBI-6

GRNIYEL

TBI-5

CHASSIS GROUND

BLUE

TBI-3

ON/OFF

BLACK

TBI-2

GROUND (5 V SENSE)

BACKPLANE

OUTSIDE
BACKPLANE BUS

TO MAIN POWER
SUPPLY

POWER SUPPLY
TERMINAL STRIP

J51
TO BACKPLANE ---+----'~1iIIoN\

J50
TO MAIN
POWER SUPPLY

AUXILIARY
POWER SUPPLY
CX-027C

Figure 3-41

HSC50 (Modified) Auxiliary Power Supply Cable Disconnection

8. Remove the nut from the -VI stud (ground) on the back of the power supply (Figure 3-41).
9. Disconnect J50 (sense line to voltage comparator) (Figure 3-41).
10. Disconnect J51 (dc on/off jumper) (Figure 3-41).

3-53
REMOVAL AND REPLACEMENT PROCEDURES

11. Turn the four captive screws on the power supply counterclockwise (Figure 3-42).

AUXI L1ARY POWER
SUPPLY CABLES

CAPTIVE
SCREWS

AUXI L1ARY POWER
SUPPLY GUIDANCE
TRACK

AUXI L1ARY POWER
SUPPLY
CX-028S

Figure 3-42

HSC50 (Modified) Auxiliary Power Supply Removal

12. Pull the power supply out about an inch. Check the back of the cabinet to ensure the cables and
connectors are clear.
13. Carefully slide the power supply out through the front of the HSC50 (modified).
14. Remove the power cord from the failing unit and install on the new power supply.
NOTE

Spare supplies are not shipped with a power cord.
Reverse the removal procedure to replace the auxiliary power supply.

3-54
REMOVAL AND REPLACEMENT PROCEDURES

3.5 HSC50 REMOVAL AND REPLACEMENT PROCEDURES
The following sections describe procedures for removing and replacing the field replaceable units
(FRUs) in an HSC50.

3.5.1 Removing HSC50 Power
Before removing/replacing an FRU, tum off the ac power. Open the back door with a 5/32-inch hex
wrench. The power controller is located on the lower left side of the cabinet. Figure 3-43 shows
the location of the circuit breakers, fuses, and power Control bus connectors on the 60 Hz power
controller.

'3-55
REMOVAL AND REPLACEMENT PROCEDURES

DELAYED OUTPUT
CONNECTOR
\
DEC POWER CONTROL \
BUS CONNECTORS

LINE PHASE
INDICATORS

LINE POWER
CI RCUIT BREAKERS

CB2-4 (SWITCHED)

CB5 (UNSWITCHED)

1-- -- -- .--I
~,-

_._

....... _

-,- --'
~

~.,...

_4""-'

............ i

eX-013B

Figure 3-43

HSC50 Power Controller-Front View (60 Hz)

3-56
REMOVAL AND REPLACEMENT PROCEDURES

Figure 3-44 shows the location of the circuit breakers on the 50 Hz unit.
DELAYED OUTPUT
CONNECTOR
DEC POWER CONTROL
BUS CONNE~TOR

\
REMOTE/OFF/LOCAL
ON SWITCH

A.C. Input

LINE PHASE
INDICATORS

LINE POWER
CIRCUIT
BREAKER

CB1

CX-013C

Figure 3-44

HSC50 Power Controller-Front View (50 Hz)

3.5.1.1 Removing HSC50 ac Power

To remove ac power, turn off CBl (Figure 3-43 or Figure 3-44).

3-57
REMOVAL AND REPLACEMENT PROCEDURES

3.5.1.2 Removing HSC50 dc Power

Following are the three methods for removing dc power.
1. Tum off the dc power switch, located on the maintenance access panel (Figure 3-45).

1 ON POSITION

OCP
CONNECTOR

CONNECTORS RESERVED
FOR FUTURE USE

MAINTENANCE TERMINAL
SIGNAL CONNECTOR
MAINTENANCE
TERMINAL POWER

CX-014B

Figure 3-45

HSC50 Maintenance Access Panel

2. Tum off ac power (CB1) (Figure 3-43 or Figure 3-44).
3. Turn the three-position Remote/Off/Local On switch to the Off position (Figure 3-43 or
Figure 3-44).

3-58
REMOVAL AND REPLACEMENT PROCEDURES

3.5.2 HSC50 FRU Removal Sequence
Figure 3-46 shows the FRU removal sequence for an HSC50.
OPEN CABINET FRONT DOOR

MODULES

TU58 DRIVES

TU58 CONTROLLER MODULE

OCP

OPEN CABINET BACK DOOR

POWER CONTROLLER
BLOWER
AIR FLOW SENSOR ASSEMBLY

CABINET FRONT DOOR

CABINET BACK DOOR

MAIN POWER SUPPLY
AUXI LlARY POWER SUPPLY
CX-015C

Figure 3-46

HSC50 FRU Removal Sequence

3.5.3 HSC50 Cabinet Front Door Removal
Use the following procedure to remove the HSC50 cabinet front door.
CAUTION

When performing the following steps, take care not to damage the front spring fingers.
1. Open the cabinet front door by turning the key clockwise.
2. Disconnect the ground wire from the door.
3. Remove the maintenance access panel by loosening the four captive screws.
CAUTION

Sonle HSC50s have a hinged maintenance access panel with only one captive screw.

3-59
REMOVAL AND REPLACEMENT PROCEDURES

4. Remove HSC50 power by pushing the dc power switch to the 0 position (refer to Figure 3-43 or
Figure 3-44).
5. Remove the plastic cable duct cover.
6. Disconne.ct cables from the maintenance access panel (refer to Figure 3-45).
7. Pull down on the spring-loaded rod on the top hinge inside the cabinet and then lift the door off its
bottom pin.
Reverse the removal procedure to replace the front door.

3.S.4 HSCSO Cabinet Back Door Removal
Use the following procedure to remove the HSC50 cabinet back door.
1. Open the back door with a 5/32-inch hex wrench.
2. Pul1 down on the spring-loaded rod on the top hinge inside the cabinet and then lift the door off its
bottom pin.
Reverse the removal procedure to replace the back door.

3.S.S HSCSO TUS8 Bezel Assembly Removal
Use the following procedure to remove the HSC50 TU58 bezel assembly.
1. Open the front door.
2. Remove the maintenance access panel by loosening the four captive screws.
3. Remove HSC50 de power by pus-hing the de power switch to too 0 position (refer to Figure 3-43
or Figure 3-44).
4. Remove the two locknuts on the bottom of the TU58 bezel assembly (Figure 3-47).

3-60
REMOVAL AND REPLACEMENT PROCEDURES

•

-- --•

CX-016A

Figure 3-47

HSC50 TU58 Bezel Assembly Removal

CAUTION

When servicing the TUS8, avoid bending the tachometer disk mounted on the drive motor
shaft. If the disk is bent but not creased it may be straightened. If it cannot be straightened
or if it is creased, the TU58 must be replaced. The disk should not rub against the optical
sensor block or any dangling wires.
5. Push the TU58 bezel assembly up about an inch to clear the mounting hooks from their slots. Pull
the bezel assembly back three to four inches from the door for clearance.
6. Support the TU58 bezel assembly with one hand while disconnecting J3 and J4 from the OCP
(Figure 3-48).

3-61
REMOVAL AND REPLACEMENT PROCEDURES

J3
(20 PINS)

J4
(10 PINS)

TU58 MOUNTI NG

OPERATOR CONTROL
PANEL PCB

PHI LLiPS HEAD~..L..J----
SCREWS
(4 TOTAL)

CX-018A

Figure 3-48

HSC50 Operator Control Panel Removal

7. Disconnect cables from the TU58 controller module (Figure 3-49).

3-62
REMOVAL AND REPLACEMENT PROCEDURES

SECURE/ENABLE
SWITCH

HEAD
COVER

POWER
CAUTION:
CONNECTOR CAN BE
REVERSED. OBSERVE
PIN USAGE.

BAUD RATE
JUMPERS
(FACTORY SET)

OPERATOR CONTROL
PANEL CONNECTOR

MAINTENANCE
ACCESS PANE L

CX-017B

Figure 3-49

HSC50 TU58 Controller Removal

NOTE

The head cover shown upper left in Figure 3-49 should be removed during operation.
8. Slide the controller module out of the plastic guides.
Reverse the removal procedure to replace the TU58 drives.

3.5.6 HSC50 TU58 Controller Module Removal
Use the following procedure to remove the HSC50 TU58 controller module.
1. Perform steps 1 through 8 of the TU58 drive removal procedure (Section 3.5.5).
2. Ensure the baud rate jumper setting on the new module is the same as on the replaced module
(Figure 3-49 shows the jumper location).
Reverse the removal procedure to replace the TU58 controller module.

3-63
REMOVAL AND REPLACEMENT PROCEDURES

3.5.7 HSCSO Operator Control Panel (OCP) Removal
OCP indicators are not field replaceable. IT any lamp fails~ replace the entire OCP as follows:
1. Open the front door by turning the key clockwise.

2. Remove dc power (refer to Figure 3-43 or Figure 3-44).
3. Remove TU58s (Section 3.5.5).
4. Remove 13 and 14 from the OCP (refer to Figure 3-48).
5. Remove the four screws from the OCP (refer to Figure 3-48).
6. Carefully pullout the OCP, allowing for indicator and switch clearance.
Reverse the removal procedure to replace the OCP.

3.5.8 HSCSO Logic Modules Removal
A Ve)ostat anti-static kit (part number 29-11762) must be used during module removal/replacement.
Removal procedures are described in the following list.
1. Open the front door by turning the key clockwise.
2. Remove dc power (refer to Figure 3-43 or Figure 3-44). This is done by opening the maintenance
access panel and pushing the dc power switch to the 0 (off) position.
3. Tum the two nylon latches on the module cover plate one-quarter tum (Figure 3-50).

3-64
REMOVAL AND REPLACEMENT PROCEDURES

NYLON LATCHES

AIRFLOW
WARNING
LABEL

eX-019A

Figure 3-50

HSC50 Card Cage Cover Removal

4. Pull the card cage cover up and out.
S. Check the module utilization label above the card cage for the location of the desired module. The
tnodule slots are numbered from right to left, viewed from the module cover side.
6. Remove the module and replace with a new module.
Reverse the removal procedure to replace the card cage cover.
If an 1/0 Control Processor module is being replaced, set the baud rate jumper to match the tenninal in

use (refer to Figure 3-29). To set the baud rate for 9600, leave jumper W3 intact. To set a baud rate
of 300, cut one elbow angle on the W3 lead and spread slightly to avoid contact between the cut edges.

3-65
REMOVAL AND REPLACEMENT PROCEDURES

NOTE

The I/O Control Processor module is identified by factory-set jumpers. Each module has a unique
serial number that matches the pattern of the jumpers. Do not reconfigure these jumpers.
IT the port link module is being replaced, ensure the node address switches are properly set on the new
module. See Fig-ure 3-30 for the LOIOO Llr-.U{ module node address switches, and Figure 3-31 for the
LOI00, Rev-E2 LINK module or the LOl18 LINK module node address switches.
See the system manager for the correct node address.
The jumper/switch configurations significance are as follows:
•

SI / S2-Node number (same as LOl00)

•

S3-1-Cluster Size (GTI5), Def =Less than 15 = Sw ON

•

S3-2, 3, 4--S10t count, Def = 7 Ticks = ALL Sw's ON

•

WI-Extender header, Def = Not used

•

W2-Active hub arbitration, Def = Not used

•

W3-Extender ACK timeout, Def = Not used

•

W4--Cluster size (GT32), Def = Less than 32

The LOll8 port link module also has jumpers that must be installed or removed. Refer to Figure 3-32
for the jumper configuration for the L01l8, Rev-A LINK module, Figure 3-33 for the jumper
configuration for the L01l8, Rev-Bl LINK module, and Figure 3-34 for the jumper configuration
for the L01l8, Rev-B2 LINK module.

3.,5.9 HSC50 Blower Removal
Use the following procedure to remove the HSC50 blower.
1. Open the back door using a 5/32-inch hex wrench.

2. Turn off ac power (CBl on the power controller) (refer to Figure 3-43 or Figure 3--44).
3. Disconnect the blower power connector.
4. Remove the exhaust duct from the bottom of the blower by lifting up the quick release latches on
each side of the duct (Figure 3-51).

3-66
REMOVAL AND REPLACEMENT PROCEDURES

3 PHILLIPS HEAD SCREWS
(SECURE BLOWER
MOUNTING BRACKET)

REMOVABLE
EXHAUST DUCT

COOLING BLOWER
POWER CONNECTOR

AIRFLOW SENSOR
POWER CONNECTOR
(J70)

Figure 3-51

AIRFLOW
SENSOR

eX-939B

HSC50 Main Cooling Blower Removal

5. Loosen, but do not remove, the three Phillips screws holding the blower mounting bracket to the
cabinet.

6. Lift the blower and bracket up and out of the cabinet.
Reverse the removal procedure to replace the cooling blower.

3.5.10 HSC50 Airflow Sensor Assembly Removal
Use the following procedure to remove the HSC50 airflow sensor assembly.

1. Open the back door using a hex wrench.
2. Tum off the ac circuit breaker (CB 1) on the HSC50 power controller (refer to Figure 3-43 or
Figure 3-44).

3-67
REMOVAL AND REPLACEMENT PROCEDURES

3. Disconnect J70 (Figure 3-S2).

AIRFLOW
SENSOR

. ~:
. ~:

•

• • •~

CX-023A

Figure 3-52

HSC50 Airfiow Sensor Assembly Removal

4. Remove the Phillips head screw that holds the mounting clamp to the duct.
S. Slide the sensor assembly out of the duct.
Reverse the removal procedure to replace the airflow sensor assembly. Align the slots in the airflow
sensor tip horizontally with the floor. Ensure sensor operability by blocking the flow of air. Pinching
the sensor should trip CB 1.

3.5.11 HSC50 Power Controller Removal
The power controller mll')t be removed to replace either of the power supplies. Use the following
procedure to remove the HSCSO power controller.
1. Open the back door.
2. Remove ac power by placing CB1 in the off position (Figure 3-S3).

3-68
REMOVAL AND REPLACEMENT PROCEDURES

COOLING BLOWER

MAIN
POWER SUPPLY

.' ~

-. .

MAIN POWER
SUPPLY
liNE CORD
AUXILIARY
POWER SUPPLY

POWER CONTROLLER
LINE CORD

POWER CONTROLLER
SCREW LOCATIONS

,,,,,')/
~

CX-024B

Figure 3-53

HSC50 Power Controller Removal

3. Unplug the power controller from the power source.
4. Remove the two top screws and then the two bottom screws securing the power controner to the
cabinet (Figure 3-53). While removing the two bottom screws, push up on the power controller to
take the weight off the screws.
CAUTION

Do not pull the power controller out too far because cables are connected to the back.
5. Remove the rear door latch to allow clearance for power controller removal.
6. Pull the power controller towards you and then out.

3-69
REMOVAL AND REPLACEMENT PROCEDURES

7. For the 60 Hz unit, remove the power Control bus cables from connectors J 1, J2, and J3 at the
front of the power controller (refer to Figure 3-43). For the 50 Hz unit, remove the power Control
bus cabies from connectors Jl and J2 (refer to Figure 3-44).
8. Disconnect the ground lead from the screw at the rear of the power controller.
9. Disconnect all line cords from the back of the power controller.
Reverse the removal procedure to replace the power controller.

3.5.12 HSC50 Main Power Supply Removal
Use the following procedure to remove the HSC50 main power supply.
1. Open the back door using a 5/32-inch hex wrench.
2. Turn off ac power (CBl) on the power controller (refer to Figure 3-43 or Figure 3-44).
3. Unplug the power controller from the power source.
4. Retnove the front door.
5. Remove the power controller (Section 3.5.11) to access the back of the power supply.
6. Disconnect the cable from the -VI stud (ground) on the back of the power supply (Figure 3-54).
Figure 3-54 shows the HSC50 main power supply test points.

3-70
REMOVAL AND REPLACEMENT PROCEDURES

MAIN POWER SUPPLY - REAR VIEW

BACKPLANE

POWER TO
AIRFLOW SENSOR

J34
TO AUXILIARY
POWE R SUPPLY

TO MAIN
POWER SUPPLY

SWITCH

TO AUXI LlARY
POWER SUPPLY

LINE CORD
CONNECTIONS
4 BLACK WI RES
FROM BACKPLANE

CX-048A

Figure 3-54

HSC50 Main Power Supply Cables-Disconnection

7. Disconnect the cable from the +Vl stud (+5 volts) on the back of the power supply (Figure 3-54).
8. Disconnect the foUr orange wires from the -V2 stud (-5.2 volt) on the back of the power supply
(Figure 3-54).
9. Disconnect the four black wires +V2 stud (ground) on the back of the power supply (Figure 3-54).
10. Unplug J31 (+12 VDC output from the supply to backplane) (Figure 3-54).
11. Unplug P32 (+12 VDC and +5 VDC sense lines) (Figure 3-54). Ensure the P32 cable is free to be
removed with the power supply.

3-71

REMOVAL AND REPLACEMENT PROCEDURES

12. Unplug J33 (to dc power switch on maintenance access panel) (Figure 3-54).
13. Unplug J34 (remote on/off jumper to auxiliary power supply) (Figure 3-54).
14. Unplug J35 (+12 VDC power to the airflow sensor) (Figure 3-54).
15. Tum the four captive screws on the front of the power supply counterclockwise (Figure 3-55).

MAIN POWER
SUPPLY CABLES

CAPTIVE
SCREWS

11111111

II111111

IIII1111

CX-0268

Figure 3-55

HSC50 Main Power Supply Removal

16. Pull the power supply out about an inch. Check the back of the cabinet to ensure the cables are
clear.
CAUTION

This power supply is heavy. Support it with both hands to prevent dropping.
17. Carefully pull the power supply all the way out of the cabinet.
Reverse the removal procedure to replace the main power supply.

3.5.13 HSC50 Auxiliary Power Supply Removal
An HSC50 requires an auxiliary power supply if the total module count in the card cage is more
than eight. The auxiliary power supply is mounted directly beneath the main power supply. Use the
following procedure to remove the HSC50 auxiliary power supply.
1. Open the back door using a 5/32-inch hex wrench.
2. Tum off ac power (CBl) on the power controller (refer to Figure 3-43 or Figure 3-44).
3. Unplug the power controller from the power source.
4. Remove the front door.
5. Remove the power controller to access the back of the power supply.

3-72
REMOVAL AND REPLACEMENT PROCEDURES

6. Unplug the auxiliary power supply line cord at the power controller.
7. Disconnect the cable from the +VI stud (+5 volt) on the back of the power supply (Figure 3-56).
Figure 3-56 shows the HSC50 auxiliary power supply test points.

WIRE LIST
COLOR

POSITION

SIGNAL
GROUND (5 V SENSE)

BLACK

TBI-2

RED

TBI-1

5 V SENSE

BROWN

TBI-4

POWER FAIL

BLUE

TBI-7

ACC

BROWN

TBI-6

GRNIYEL

TBI-5

CHASSIS GROUND

BLUE

TBI-3

ON/OFF

BLACK

TBI-2

GROUND (5 V SENSE)

BACKPLANE

OUTSIDE
BACKPLANE BUS

TO MAl N POWE R
SUPPLY

POWER SUPPLY
TERMINAL STRIP

J51
TOBACKPLANE-----+~~~

J50
TO MAIN
POWE R SUPPLY

GROUND

AUXILIARY
POWER SUPPLY
CX-027C

Figure 3-56

HSC50 Auxiliary Power Supply Cables-Disconnection

8. Disconnect the cable from the -VI stud (ground) on the back of the power supply (Figure 3-56).

9. Disconnect J50 (sense line to voltage comparator) (Figure 3-56).
10. Disconnect J51 (dc on/off jumper) (Figure 3-56).

3-73
REMOVAL AND REPLACEMENT PROCEDURES

11. Turn the four captive screws on the power supply counterclockwise (Figure 3-57).

AUXI LlARY POWER
SUPPLY CABLES

CAPTIVE
SCREWS

AUXI LlARY POWER
SUPPLY GUIDANCE
TRACK

AUXI LlARY POWE R
SUPPLY
CX-02S8

Figure 3-57 Auxiliary Power Supply Removal

12. Carefully slide the power supply out through the front of the HSC50.
Reverse the removal procedure to replace the auxiliary power supply.

4-1

INITIALIZATION PROCEDURES

4
INITIALIZATION PROCEDURES
4.1

INTRODUCTION

This chapter contains procedures for connecting the console terminal on the HSC70 and the auxiliary
terminal on the HSC50, and how to initialize both HSC models.
A malfunction occurring during initialization may be reported by a fault code displayed on the Operator
Control Panel (OCP). These fault codes are explained in Chapter 8.

4.2 HSC CONSOLE TERMINAL CONNECTION
The console or auxiliary terminal designated for the HSC can be a VT220, VT320, VTlxx, or an LA12
DECwriter. An LA75 or LA50 printer for hardcopy output is connected to the VT220, VT320, and
can be connected to the VTlxx if the VTlxx has the printer port option installed. Detailed operating
information is provided in the appropriate owner manuals accompanying the VTxxx and LAxx models.
NOTE

The VT320 series terminal can be connected to an RS-232 compatible port only. Connection to
another type of port will result in initialization failure and FCC violations.

4.2.1 HSC70 Consoie Terminai Connection
Figure 4--1 shows the placement of the EIA terminal connectors on the HSC70 rear bulkhead. The
console terminal connects to the J60 connector as shown.

4-2
INITIALIZATION PROCEDURES

CONNECT CONSOLE
TERMINAL TO J6D
EIATERMINAL
CONNECTORS
1..

J60 CONSOLE

~
N

0g C::::J

J61

J62

c::>
c::>
K
J
M
L
00 CJ
Si [~ 8~ CJ 00
~~ CJ

~CJ 8~ c:J
~ 0
00
2 i O ~ CJ ~CJ 00 0
00 D
3~O ~ C:J ~D 00
1~ C::J

00
00 D
00
00
00
00
~

D
0
B

~g C~ ~S [=:1 ~~ 0
00 C=:J
®O C_
:J $0
~ C:::J 00
OO C::J ~~ CJ
00 [::J
~ CJ
~O 00
00 C:;J O~
@O

~ C':.J

<iO

DATA CHANNEL
CONNECTIONS

C:J ro CJ ~D
O~

CABLE CONNECTORS
WITHIN A DATA CHANNEL

Figure 4-1

CABLE
BULKHEAD

eX-8918

HSC70 Console Terminal Connection

Preferably, power is turned off before the console terminal is installed. However, power can be left
on while connecting the tenninal. Use the following procedure for installing the console tenninal with
power on or off.
1. Put the Secure/Enable switch in the SECURE position.
2. Change terminal state (e.g. plug in, remove power, connect EIA line, etc.).
3. Put the Secure/Enable switch in the ENABLE position if it is necessary to do so at this point.
NOTE

If this procedure is not followed, the HSC70 may enter micro-Online Debugging Tool (ODT)
mode. This mode is indicated by an @ symbol on the screen. Typing a P (proceed) should exit
this mode.

4-3
INITIALIZATION PROCEDURES

4.2.2 HSC50 or HSC50 (Modified) Auxiliary and Maintenance Terminal
Connections
Figure 4-2 shows the placement of the two ASCII ports on the HSC50 and HSC50 (modified). The
auxiliary terminal can be connected to either the rear or the front ASCII port. Two terminals cannot be
connected at the same time.

4-4
INITIALIZATION PROCEDURES

MAINTENANCE
ACCESS PANEL

.g.

0 00

.,
.. ,
P42 P41 P40

P45 P44
.1I:Ci:i:i:I.

CABLING
BULKHEAD

o
AUXILIARY
TERMINAL
COMM.

o
TERMINAL

PRINTER

(gOR~\~
=-=
I~
I

FROM}
,/1
EXTERNAL
4- - - /'
AC POWER
",SOURCE
..... - - - - - - - -

CX-243B

Figure 4-2

Connecting an Auxiliary or Maintenance Terminal (HSC50 or HSC50 [Modified])

Preferably, power is turned off before the console tenninal is installed. However, power can be left
on while connecting the tenninal. Use the following procedure for installing the console tenninal with
power on or off.
1. Put the Secure/Enable switch in the SECURE position.
2. Change terminal state (e.g. plug in, remove power, connect EIA line, etc.).

4-5
INITIALIZATION PROCEDURES

3. Type three space characters on the terminal keyboard.
4. If it is necessary to put the SeeurelEnable switch in the ENABLE position, do so at this point.
NOTE

If tbis procedure is not followed, the HSCSO may enter microeOnline Debugging Tool (ODT)
mode. This mode is indicated by an @ symbol on the screen. Typing a P (proceed) should exit
this mode.

4.2.3 LA12 Parameters
Detailed infonnation on LA12 terminal installation and operation is found in the DEC writer
Correspondent Technical Manual (EK-CPL12-TM).
When an LA12 is used as an auxiliary terminal, the following parameters must be established.
1. Communications:

•

Auto - Ansbk = no

•

Buffer = 1024

•

Comm Port =EIA

•

Disk - HDX = none

•

Echo - Local = no

•

Fault = none

•

G - HDX Start Mode =Rcv

•

H - Hi Speed (bps) =9600

•

L - Lo Speed (bps) = 300

•

M - Line Prot =FOX - Data Leads

•

o - Rev Error Ovride =no
Parity = 7IM
Q - SRTS Polarity = 10
Restraint = Xon/Xoff
S - Speed Select =hi
Turn Char =none
U - Power Up = line
V - Frequency = bell 103

•
•
•

•

2. Keyboard:

•

Aulo - Linefeed = no

•

Break = no

•

C - Keyclick = no

•

Keypad = normal

•

Language = USA

•

Repeat = yes

4--6
INITIALIZATION PROCEDURES

3. Printer:
•

A - GO Char Set =USA

•

B - 01 Char Set = USA

•

C - G2 Char Set = USA

•

D - G3 Char Set = USA

•

End-of-line = wrap

•

Form Length = 264

•

G - Print Cntrl Chars

•

Horiz Pitch (CPI) = 10

•

Newline Char = none

•

Print Force = hi

•

Vertical Pitch (LPI) = 6

4.3 HSC70 INITIALIZATION
This section describes the initialization procedures for the HSC70 using the system diskette. This
diskette also contains the software necessary to execute the device integrity tests and the utilities. To
boot and Jun the offline diagnostics from a separate offline diskette, refer to Chapter 7.
System initialization is started by powering on the unit or (if the unit is already on) by depressing and
releasing the lnit switch with the Secure/Enable switch in the ENABLE position. This initiates the P.io
ROM bootstrap tests and then loads the Init P.io test.
NOTE

In order to run the HSC70 device integrity tests, the system diskette must reside in the RX33
drive. Customarily, this diskette resides in RX33 drive O. However, drive 1 and drive 0 are
identical, and disk placement is arbitrary.
Logic in the following areas is tested with the Init P.ioj diagnostic.
•

Control processor-The rest of the instruction set not tested by the ROM bootstrap, interrupts,
memory management, and the Control memory lock-cycle circuitry are included. Detected failures
result in an error code display on the OCP (Figure 4-3).

•

Memory-Program memory is tested from the I/O Control Processor. However, the Control and
Data memories are tested by the highest-numbered available requestor controlled by the I/O Control
Processor. Again, detected failures result in an OCP error code display.

•

Host interface and data channels-Module status is collected and placed in a table for the HSC70
operating software initialization process. As each module is enabled, it automatically executes
internal microdiagnostics. These internal diagnostics test the following.
•

ROM (sequencer, checksum, parity, etc.)

•

Special logic Wlique to that particular module

Upon completion of diagnostics for each module, a status code is passed to the I/O Control Processor.
Status codes for the various modules are discussed in Chapter 5.

4-7
INITIALIZATION PROCEDURES

If the module diagnostics complete successfully, the status code represents the module type and the
green LED is turned on. If the diagnostics fail, the status code indicates the failing microtest. In
addition, detected failures cause a red LED to light on that module. K.ci, K.sdi, K.sti, and K.si failures
are also displayed on the auxiliary terminal after the boot is completed.
NOTE

Lighting of the red LED on the LOIOO or LOl18 LINK module does not indicate a failure of the
module.
For a detailed description of the boot process refer to the HSC70 Boot Flowchart in Chapter 8.

4.3.1

Ini~_P.io Test (INIPIO)

The INIPIO test completes the P.ioj module and the HSC70 memory testing previously started by the
ROM bootstrap tests. All P.ioj logic not tested by the bootstrap is tested by INIPIO. In addition, the
HSC70 Program, Control, and Data memories are tested.
This test runs in a stand-alone environment (no other HSC70 processes are running). If a failure is
detected, the failing module is flagged by illumination of the red LED on the module. If the test runs
without finding any errors, the HSC70 operational software is loaded and started. The Init P.io test
is not a repair level diagnostic. If a repair level test is needed, run the offline P.io test that provides
standard HSC70 error messages.

4.3.2 INIPIO Test System Requirements
In order to run this test, the following hardware is required.
•

P.ioj (processor) module with HSC70 boot ROM

•

K.ci

•

At least one M.std2 (memory) module

•

RX33 controller with at least one working drive

In addition, an HSC70 system diskette (RX33 media) is required.

4.3.3 INIPIO Test Prerequisites
The INIPIO test is loaded by the HSC70 ROM bootstrap program. The bootstrap tests the basic J-ll
instruction set, the lower 2048 bytes of Program memory, an 8 Kword partition in Program memory,
and the RX33 subsystem used by the bootstrap. When the INIPIO test begins to execute, most J-l1
logic has been tested and is considered working. Likewise, the Program memory occupied by the test
and the RX33 subsystem used to load the test are also considered tested and working. The RX33
diskette is checked to ensure it contains a bootable image.

4.3.4 INIPIO Test Operation
Follow these steps to start the INIPIO test.
1. Insert the HSC70 system diskette in the RX33 unit 0 drive (left-hand drive).

2. Power on the HSC70, or depress and release the Inil button on the HSC70 OCP with the
SecurelEnable switch enabled. The Init lamp should light and the following should occur.
•

The RX33 drive-in-use LED lights within 10 seconds, indicating the bootstrap is loading the
INIPIO test to the Program memory.

•

The I/O State light is on after diskette motion stops and the INIPIO test begins testing.

4-8
INITIALIZATION PROCEDURES

•

The INIPIO test displays the following message on the HSC console when it begins: INIPIO-I
BOOTING.

•

HSC70 operational software is being loaded when the State light flashes rapidly.

•

HSC70 operational software indicates it has loaded properly when the State light blinks slowly.

•

HSC70 displays its name and version indicating it is ready to perform host I/O.

Once initiated, the INIPIO test is terminated only by halting and rebooting the HSC. H the test fails to
load using the preceding start-up procedure, perform the next four steps.
1. Check the OCP fault light. H the fault light is on, press the fault light once and check the fault
code (Figure 4-3).
2. Boot the diskette from the RX33 unit 1 drive (right-hand drive).
3. Boot another diskette. H that diskette boots, the original diskette is probably damaged or worn.
4. Boot the HSC70 Offline Diagnostic diskette. This diskette contains the offline P.io test which
provides extensive error reporting features. A console terminal must be connected to run the offline
tests.
The progress of the INIPIO test is displayed in the State LED. Before the test starts, the State LED is
off. When the test starts, the State LED is turned on, and the INIPIO-I BOOTING message is printed
on the HSC console. When the test completes with no fatal errors, the State LED begins to blink at a
steady rate. If the test detects an error, the Fault lamp on the HSC70 OCP is lit.

4.4 HSC50 INITIALIZATION
In order to run the HSC50 or HSC50 (modified) device integrity tests and utHities, the HSC50 operating
software must be initialized with both the system and utilities cassettes loaded in the TU58 drives.
Before inserting the system tape into the TU58 drive, check the black RECORD tab. This tab must
be in the record position (as indicated by an arrow on the tab) to ensure proper system operation. The
utilities tape need nol be write-enabled.
NOTE

In order to run the HSCSO or HSCSO (modified) device integrity tests, the system tape must
reside in the TUS8 drive. Customarily, this tape resides in TUS8 drive O. Drive 1 and drive 0 are
identical, and tape placement is arbitrary.
However, the utilities tape does not contain a bootable image, and if drive 0 contains the utilities
tape, the system will try to boot from drive 1.
Initialization of the HSC50 or HSC50 (modified) can be initiated by either powering on the unit if it
is powered down or, if power is already applied, by depressing and releasing the lnit switch with the
Secure/Enable switch in the ENABLE position. This causes the P.ioc bootstrap ROM tests to run and
then load the Init P.ioc test.

4.4.1 HSC50 or HSC50 (Modified) Offline Diagnostics Tape
The offline diagnostics tape can be booted in either TU58 drive and need not be write-enabled. The
offline tape can be booted by either powering on the unit or depressing and releasing the Init switch
with the Secure/Enable switch in the ENABLE position. This causes the P.ioc bootstrap ROM tests to
run and then load the offline P.ioc test.

4-9
INITIALIZATION PROCEDURES

4.4.2 Init P.ioc Diagnostic
The !nit P.ioc test is loaded by the P.ioc ROM bootstrap test each time the HSC50 system tape is
booted. This diagnostic completes the testing of the P.ioc module and the HSC50 memories. At the
successful completion of these tests, the HSC50 operating software is loaded and started.
Logic in the following areas is tested with the Init P.ioc diagnostic.
•

•

Host interface and data channels-Module status is collected and placed in a table for the HSC50
operating software initialization process. As each module is enabled, it automatically executes
internal microdiagnostics. These internal diagnostics test the following.
•

ROM (sequencer, checksum, parity, etc.)

•

Special logic unique to that particular module

Upon completion of diagnostics for each module, a status code is passed to the I/O Control Processor.
Status codes for the various modules are discussed in Chapter 5.
IT the module diagnostics complete successfully, the status code represents the module type and the
green LED is turned on. If the diagnostics fail, the status code indicates the failing microtest. In
addition, detected failures cause a red LED to light on that module. K.ci, K.sdi, K.sti, and K.si failures
are also displayed on the auxiliary terminai after the boot is completed.
NOTE
Lighting of the red LED on the LOIOO or LOllS LINK module does not indicate a failure of the
module.

For a detailed description of the boot process refer to the HSC50 Boot Fiowchart in Cnapter 8.

4.5 HSC FAULT CODE INTERPRETATION
All failures occurring during the Init P.io test are reported on the OCP LEOs. When the Fault lamp
is lit, pressing the Fault switch results in the display of a failure code in the OCP LEOs. This code
indicates which HSC module is the most probable cause of the detected failure. The failure code blinks
on and off at one-second intervals until the HSC is rebooted if the fault code represents a fatal fault. A
soft fault code is cleared in the OCP by depressing the Fault switch a second time. To restart the boot
procedure, press the Init switch. To identify the probable failing module, see Figure 4-3. For detailed
descriptions of OCP fault codes, see Chapter 8.

4-10
INITIALIZATION PROCEDURES

OCP INDICATORS
HEX OCT BINARY

DESCRIPTION

B I

FAULTIIONLINEI

CJ D
.:.:.:

PORT PROCESSOR
MODULE FAILUREt

00001

DISK DATA CHANNEL
MODULE FAI LUREt

00010

TAPE DATA CHANNEL
MODULE FAI LUREt

00011

INSTRUCTION CACHE PROBLEM
IN I/O CONTROL PROCESSOR*

01000

~H_0_S_T_I_N_T_E_R_F_A_C_E_E_R_R_0_R_*

____

.:.:.

4-_09~~1_1~_0_1_OO_l~------~~'~I'~-----b7070mdf::;:::[[::::::::'~[[::::~'::~ill9::;::::

DATA CHANNEL ERROR*

01010

1/0 CONTROL PROCESSOR
MODULE FAI LURE

10001

MEMORY MODULE FAILURE

1 0010

BOOT DEVICE FAILURE*"

1 0011

PORT LINK MODULE FAILURE

1 0101

MISSING FILES REQUIRED

10110

NO WORKING K.SDI, K.STI,
OR K.CI

1 1000

REBOOT DURING BOOT

11001

SOFTWARE DETECTED
INCONSISTENCY

1 1010

:::::

t INCORRECT VERSION OF MICROCODE.
* THESE ARE THE SO-CALLED SOFT OR NON-FATAL ERRORS.
**POSSIBLE MEMORY MODULE/CONTROLLER ON HSC70

Figure 4-3

Operator Control Panel Fault Code Displays

CX-9058

5-1
DEVICE INTEGRITY TESTS

5
DEVICE INTEGRITY TESTS
5.1 INTRODUCTION
Device integrity tests executing in the HSC do not interfere with normal operation other than with the
device being tested. The device integrity tests can be found on the HSC70 system media disk, HSC50
(modified) utilities media tape, or HSC50 utilities media tape.

f' A 6- S 5
RX33 integrity tests (HSC70 only) ... 5 ~ 2
TV 58 integrity tests (HSC50 only) . ." 5 - 5"

The tests described in this chapter are:
•
•
•
•

•

···5 - 5
Disk drive integrity tests i J..I> i S K • -. '. 5 - 7
Tape device integrity tests Ii.. rAPE- '., 5 - 2-1
Tape compatibility tests ~L':{ co,ff .. - 5 ... :3 I
Multidrive exerciser It.£)(£.. £. . . ..... 5 - 3 ~
Memory integrity tests .. .

•

5.1.1 Device Integrity Test Common Areas
A1I device integrity tests have two common areas in that all test prompts and error messages confonn
to standard fonnats. All prompts issued by these integrity tests use a generic syntax:
•

Prompts requiring user action or input are always followed by a question mark.

•

Prompts offering a choice of responses show those choices in parentheses.

•

A capital D in parentheses indicates the response should be in decimal.

•

Square brackets enclose the prompt default or, if empty, indicate no default exists for that prompt.

5.1.1.1 Generic Error Message Format
All device integrity tests follow a generic error message fonnat, as follows:
XXXXXX>D>tt:tt T#aaa E#bbb
U-ccc
<Text string describing error>
FRU1-dddddd FRU2-dddddd
MA -eeeeee

EXP-yyyyyy
ACT-zzzzzz

Where:
•

XXXXXX> is the appropriate device integrity test prompt.

5-2
DEVICE INTEGRITY TESTS

•

D> is the letter indicating the integrity test was initiated on demand. This field can contain a D,
an A (integrity test initiated automatically), or a P (integrity test initiated as part of the periodic
integrity tests).

•

tt:tt is the current time.

•

aaa is the decimal number denoting test that failed.

•

bbb is the decimal number denoting error detected.

•

ccc is the unit number of the drive being tested.

•

FRUI is the most likely field replaceable unit (FRU).

•

FRU2 is the next most likely FRU.

•

dddddd is the name of the field replaceable unit.

•

MA is the media address.

•

eeeeee is the octal number denoting offset within block.

•

yyyyyy is the octal number denoting data expected.

•

zzzzzz is the octal number denoting data actually found.

The first line of the error message contains general information about the error. The second line
describes the nature of the error. Lines 1 and 2 are mandatory and appear in all error messages. Line 3
and any succeeding lines display additional information and are optional.

5.2 RX33 DEVICE INTEGRITY TESTS (HSC70-ILRX33)
The RX33 device integrity test tests either of the RX33 drives attached to the HSC70. This test runs
concurrently with other HSC70 processes and uses the services of the HSC70 control program and the
Diagnostic Execution Monitor (DEMON). The RX33 device integrity test performs several writes and
reads to verify the RX33 internal data paths and read/write electronics.

5.2.1 ILRX33 System Requirements
ILRX33 hardware requirements include:
•

P.ioj (processor) module with HSC70 boot ROMs

•

At least one M.std2 (memory) module

•

RX33 controller with at least one working drive

•

Console terminal

NOTE

A scratch diskette is not required. This test does not destroy any data on the system software
diskette.
This program tests only the RX33 and the data path between the P.ioj and the RX33. All other system
hardware is assumed working.
ll...RX33 software requirements are located on the HSC70 system media disk and include:
•

HSC70 control program

•

Diagnostic Execution Monitor (DEMON)

5-3
DEVICE INTEGRITY TESTS

5.2.2 ILRX33 Operating Instructions
Type iCTRUYilO ge '1e KMON prompt friSC». Next, type either RUN ILRX33IRETURNi or RUN
dev:ILRX33 RETURN to initiate the RX33 device integrity tests.
NOTE

The term dev: refers to the HSC70 RX33 disk drives (DXO: or DXl:).
If the RX33 device integrity tests cannot load from the specified diskette, try loading the test from the
other diskette. For example, if RUN ILRX33 fails, try RUN dev:ILRX33.

5.2.3 ILRX33 Test Parameter Entry
The device name of the RX33 drive to be tested is the only parameter sought by this test. When the
test is invoked, the following prompt is displayed:
Device Name of RX33 to test (DXO:, DX1:, LB:)

[] ?

NOTE

The string LB: indicates the RX33 drive last used to boot the HSC70 control program.
One of the indicated strings must be entered. If one of these strings in not entered, the test prints
Illegal Device Name and the prompt is repeated.

5.2.4 ILRX33 Setting/Clearing
ILRX33 only verifies a particular RX33 drive and controller combination is working or failing and
should not be used as a troubleshooting aid. This test does not support any flags. If the test indicates a
partic.ular controller or drive is not operating correctly, the pr-Opef repair stra-tegyis to r-eplace the drive
and/or controller.

5.2.5 ILRX33 Progress Reports
At the end of the test, the following message is displayed:
ILRX33>D>tt:tt Execution Complete

Where tt:tt = current time.

5.2.6 ILRX33 Test Termination
This test is tenninated by typing ICTRuvl. The test automatically tenninates after reporting an error with
one exception: if the error displayed is RETRIES REQUIRED, the test continues.

5.2.7 ILRX33 Error Message Example
An error messages produced by the inline RX33 test conform to the HSC device integrity test error
message format (Section 5.1.1.1). Following is a typical ILRX33 error message:
ILRX33>D>00:00 TOOl E 003 0- 50182
ILRX33>D> No Diskette Mounted
ILRX33>D> FRUI-Drive

Other optional lines are found on different error messages.

5-4
DEVICE INTEGRITY TESTS

5.2.8 ILRX33 Error Messages
The foJ1owing paragraphs list specific infonnation about each of the errors produced by the RX33
device integrity tests. Hints about the possible cause of the error are provided where feasible.
•

Error 000, RETRIES REQUIRED-Indicates a Read or Write operation failed when first
attempted but succeeded on one of the retries petformed automatically by the RX33 driver software.
This error normally indicates the diskette media is degrading and the diskette should be replaced.

•

Error 001, OPERATION ABORTED-Reported if the ILRX33 test is aborted by typing ICTRUVI.

•

Error 002, WRITE-PROTECTED-Indicates the RX33 drive being tested contains a writeprotected diskette. Write enable the diskette and try again. If the diskette is not write-protected,
the RX33 drive or controller is faulty.

•

Error 003, NO DISKETTE MOUNTED-Indicates the RX33 drive being tested does not contain
a diskette. Insert a diskette before repeating the test. If this error is displayed when the drive does
contain a diskette, the drive or controller is at fault.

•

Error 004, HARD I/O ERROR-Indicates the program encountered a hard error while attempting
to read or write the diskette.

•

Error OOS, BLOCK NUMBER OUT OF RANGE-Indicates the RX33 driver detected a request
to read a block number outside the range of legal block numbers (0 through 2399 decimal).
Because the inline RX33 test reads and writes disk block 001, it may indicate a software problem.

•

Error 006, UNKNOWN STATUS STATUS=xxx-Indicates the RX33 device integrity test
received a status code it did not recognize. The octal value xxx represents the status byte received.
RX33 reads and writes are petformed for the RX33 device integrity test by the HSC control
program's RX33 driver software. At the completion of each Read or Write operation, the driver
software returns a status code to the RX33 test, describing the result of the operation. The test
decodes the status byte to produce a description of the error.
An UNKNOWN STATUS error indicates the status value received from the driver did not match
any of the status values known to the test. The status value returned (xxx) is displayed to help
detennine the cause of the problem. Any occurrence of this error should be reported via a Software
Performance Report (SPR). See Appendix B for detailed information on SPR submission.

•

Error 007, DATA COMPARE ERROR-Indicates data subsequently read back.
MA -aaaaaa
EXP-bbbbbb
ACT-cccccc

The following is an explanation of the three fields:
aanaaa represents the address of the failing word within the block (512 bytes) that was read.
bbbbbb represents the data written to the word.
cccccc represents the data read back from the word.
Because this test only reads and writes block 1 of the diskette, all failures occur while trying to
access physical block 1.
•

Error 008, ILLEGAL DEVICE NAME-Indicates the user specified an illegal device name when
the program prompted for the name of the drive to be tested. Legal device names include: OXO:,
OXl:, and LB:. LB: indicates the drive from which the system was last booted. After displaying
this error, the program again prompts for a device name. Enter one of the legal device names to
continue the test.

5-5
DEVICE INTEGRITY TESTS

5.2.9 ILRX33 Test Summary
The test summary fOi h;e device integrity tests is contah"led h"l the following pamgrnph.
•

Test 001, Read/Write Test-Verifies data can be written to the diskette and read back correctly.
All reads and writes access physical block 1 of the RX33 (the RT-l1 volume ID block). This block
is not used by the HSC operating software.

Initially, the contents of block 1 are read and saved. Then three different data patterns are written to
block 1, read back, and verified. This checks the read/write electronics in the drive and the internal data
path between the RX33 controller and the drive. Following the read/write test, the original contents of
block 1 are written back to the diskette.
If the data read back from the diskette does not match the data written, a data compare error is
generated. The error report lists the word (MA) in error within the block together with the EXPected
(EXP) and ACTual (ACT) contents of the word.

5.3 TU58 DEVICE INTEGRITY TESTS (HSC50-ILTU58)
The TU58 device integrity test tests any TU58 drive attached to the HSC50. An operator can initiate
this test using the auxiliary terminal with only the system tape installed. aTU58 also is resident on the
utilities tape.
Because the HSC50 operating software tests the TU58 each time it is used, ILTU58 performs only
minimal testing. Several Read and Write operations are performed to test the internal data paths and
read/write circuitry of the TU58. It is not necessary to use a scratch tape when running ll..TU58.
Only the TU58 and the serial data path between it and the I/O Control Processor are tested by this
diagnostic. All ot..i.er system hardware is assumed to be operational.
To run the ILTU58 tests, first ~ ICTRUVI to get the HSC command line, then type RUN ILTU58
IRETURN I or RUN DDl:ILTU58 ~ETURNL

5.4 MEMORY INTEGRITY TESTS (ILMEMY)
The memory integrity test is designed to test HSC Data Buffers. This test can be initiated automatically
or on demand. It is initiated automatically to test Data Buffers that produced a parity error when in use
by the HSC control program. Buffers that fail the memory test are removed from service by sending
them to the disabled buffer queue. Buffers sent twice to this test, but not failing the memory test, are
also sent to the disabled buffer queue. Buffers that pass the memory test and have not been tested
previously are sent to the free buffer queue for further use by the HSC control program.
When the test is initiated on demand, any buffers on the disabled buffer queue are tested and the results
of the test are displayed on the terminal from which the test was initiated.
This test runs concurrently with other HSC processes and uses the services of the HSC control program
and the Diagnostic Execution Monitor (DEMON).

5-6
DEVICE INTEGRITY TESTS

5.4.1 ILMEMY System Requirements
Hardware requirements include:
•

PJoj (processor) module with HSC70 boot ROMs, or P.ioc (processor) module with HSC50
(modified) or HSC50 boot ROMs.

•

At least one M.std2 memory module (HSC70), or the M.std memory module (HSC50 [modified] or
HSC50).

•

RX33 controller with one working drive (HSC70) or TU58 controller with one working drive
(HSC50 [modified] or HSC50).

•

A console terminal for demand initiation only.

This program only tests Data Buffers located in the HSC Data memory. All other system hardware is
assumed to be working.
Software requirements include:
•

HSC control program (system diskette or tape)

•

Diagnostic Execution Monitor (DEMON)

5.4.2 ILMEMY Operating Instructions
To start this test. type ICTRUVI to get the attention of the HSC keyboard monitor. The keyboard monitor
responds with the prompt:
HSCxx>

Type RUN dev:ILMEMY IRETURNI to initiate the memory integrity test. This program has no usersupplied parameters or flags.
If the memory integrity test is not contained on the specified device (dev:), an error message is

displayed.

5.4.3 ILMEMY Progress Reports
Error messages are displayed as needed. At the end of the test, the following message is displayed (by
DEMON):
ILMEMY>O>tt:tt Execution Complete

Where tt:tt = current time.

5.4.4 ILMEMY Error Message Example
All error messages produced by the memory integrity test conform to the HSC integrity test error
message format (Section 5.1.1.1). Following is a typical ILMEMY error message.
ILMEMY>A>09:33 TOOl E 000
ILMEMY>A>Tested Twice with no Error (Buffer Retired)
ILMEMY>A>FRU1-M.std2 FRU2ILMEMY>A>Buffer Starting Address (physical)
15743600
ILMEMY>A>Buffer Ending Address
(physical) = 15744776

5-7
DEVICE INTEGRITY TESTS

5.4.5 ILMEMY Error Messages
The foHowing list shows specific information about each of the errors displayed by the memory
integrity test.
•

Error 000, TESTED TWICE WITH NO ERROR~Indicates the buffer under test passed the
memory test. However, this is the second time the buffer was sent to the memory test and passed
it. Because the buffer has a history of two failures while in use by the control program, yet does
not fail the memory test, intermittent failures on the buffer are assumed. The buffer is retired from
service and sent to the disabled buffer queue.

•

Error 001, RETURNED BUFFER TO FREE BUFFER QUEUE-Indicates a buffer failed
during use by the control program but the memory integrity test detected no error. Because this is
the first time the buffer was sent to the memory integrity test, it is returned to the free buffer queue
for further use by the HSC control program. The address of the buffer is stored by the memory
integrity test in case the buffer again fails when in use by the control program.

•

Error 002, MEMORY PARITY ERROR-Indicates a parity error occurred while testing a buffer.
The buffer is retired from service and sent to the disabled buffer queue.

•

Error 003, MEMORY DATA ERROR-Indicates the wrong data was read while testing a buffer.
The buffer is retired from service and sent to the disabled buffer queue.

5.4.6 ILMEMY Test Summaries
Test 001 receives a queue of buffers for testing. IT the memory integrity test is initiated automatically,
the queue consists of buffers from the suspect buffer queue.
When the HSC control program detects a parity or Non-Existent Memory (NXM) error in a Data
Buffer, the buffer is sent to the suspect buffer queue. While on this queue, the buffer is not used for
data transfers. The HSC periodic scheduler periodically checks the suspect buffer queue to see if it
contains any buffers. IT buffers are found on the queue, they are removed and the inline memory test
is automatically initiated to test those buffers.
IT the ILMEMY test is initiated on demand, it retests only buffers aiready known as disabled.
IT the test is initiated automatically and the buffer passes the test, the program checks to see if this
is the second time the buffer was sent to the memory integrity test. IT this is the case, the buffer is
probably producing intermittent errors. The buffer is retired from service and sent to the disabled
buffer queue. H this is the first time the buffer is sent to the memory integrity test, it is returned to
the free buffer queue for further use by the HSC control program. In this last case, the address of the
buffer is saved in case the buffer again fails and is sent to the memory integrity test a second time.
When all buffers on the test queue are tested, the memory integrity test terminates.

5.5 DISK DRIVE INTEGRITY TEST (ILDISK)
The disk drive integrity test (ILDISK) isolates disk drive-related problems to one of the following three
field replaceable units (FRUs):

1. Disk drive
2. SOl cable
3. HSC disk data channel module
The disk drive integrity test runs in parallel with disk I/O from a host CPU. However, the drive being
diagnosed cannot be online to any host. This integrity test can be initiated upon demand via the console
terminal or automatically by the HSC control program when an unrecoverable disk drive failure occurs.

5-8
DEVICE INTEGRITY TESTS

Currently, ILDISK is automatically invoked by default whenever a drive is declared inoperative, with
one exception. The exception is if a drive is declared inoperative while in use by an integrity test
or utility. Automatic initiation of ILDISK can be inhibited by issuing the SETSHO command, SET
AUTOMATIC DIAGNOSTICS. If the SET AUTOMATIC DIAGNOSTICS command is issued and
DISABLE is specified, ILMEMY (a test for suspect buffers) is also disabled. For this reason, leaving
ILDISK automatically enabled is preferable.
.
The tests performed vary, depending on whether the drive is known to the HSC Disk Server.
1. DRIVE UNKNOWN (to the HSC Disk Server)-It is either unable to communicate with the
HSC or was declared inoperative when it failed while communicating with the HSC. In this case,
because the drive cannot be identified by unit number, the user must supply the requestor number
and port number of the drive. Then the SOl verification tests can execute. The SOl verification
tests check the path between the K.sdi/K.si and the disk drive and command the drive to run its
integrity tests. IT the SOl verification tests fail, the most probable FRU is identified in the error
report. IT the SOl verification tests pass, presume the drive is the FRU.
2. DRIVE KNOWN (to the HSC Disk Server, i.e., identifiable by unit number}-Read/WriteIFonnat
tests are performed in addition to the SOl verification tests. IT an error is detected, the most
probable FRU is identified in the error report. If no errors are detected, presume the FRU is the

drive.
To find the drives known to the Disk and Tape Servers, type the SETSHO command SHOW

DISK;SHOW TAPE IRETURNl

5.5.1 ILDISK System Requirements
Software requirements of this test reside on the system media and include:
•

HSC control program disk

•

Control program disk functional code

•

Diagnostic Execution Monitor (DEMON)

Hardware requirements include:
•

Disk drive

•

Disk data channel, connected by an SOl cable

The test assumes the I/O Control Processor module and the memory module are working.
A service manual for the disk drive is required to interpret errors that occur in the drive's integrity
tests.

5.5.2 ILDISK Operating Instructions
The following steps are used to initiate ILDISK.
NOTE

To prevent access from another HSC, deselect the alternate port switch on the drive to be tested.
The alternate port switch is the drive port switch allowing alternate HSC access to the drive.
1.

Type ICTRUVL

2. The following prompt appears:
HSCxx>

Type RUN dev:ILDISK IRETURNl

4. Wait until ILDISK is read from the system software load media into the HSC Program memory.

5-9
DEVICE INTEGRITY TESTS

5. Enter parameters after rr...DISK is started. Refer to Section 5.5.4.

5.5.3 ILDISK Availability
IT the software media containing the disk d...';ve integrity tests is not loaded when the R ILDISK

IRETURN I command is entered, an error message is displayed. Insert the software media containing
ll..DISK and repeat Section 5.5.2.

5.5.4 ILDISK Test Parameter Entry
Upon demand initiation, rr...DISK first prompts:
DRIVE UNIT NUMBER (U)

[] ?

Enter the unit number of the disk drive for test. Unit numbers are in the form Dnnnn, where nnnn is
a decimal number between 0 and 4095 corresponding to the number printed on the drive unit plug.
Tenninate the unit number response with a carriage return. ILDISK attempts to acquire the specified
unit via the HSC diagnostic interface. If the unit is acquired successfully, ILDISK nexi prompts for the
drive integrity test to be executed. If the acquire fails, one of the following conditions was encountered:
1. The specified drive is UNAVAILABLE. This indicates the drive is connected to the HSC but is

currently online to a host CPU or an HSC utility. Online drives cannot be diagnosed. ILDISK
repeats the prompt for the unit number.
2. The specified drive is UNKNOWN to the HSC disk functional software. Drives are UNKNOWN
for one of the following reasons:
•

The drive and/or disk data channel port is broken and cannot communicate with the disk
functional software.

•

The drive was previously communicating with the HSC but a serious error -occurred, and the
HSC has ceased communicating with the drive (marked the drive as inoperative).

In either case, rr...DISK prompts for a requestor number and port number. Refer to Section 5.5.5.
Mter receiving the unit number (or requestor and port), rr...DISK prompts:
RUN A SINGLE DRIVE DIAGNOSTIC (YIN)

[N] ?

Typing IRETURN I causes the drive to execute its entire integrity test set. Typing a Y IRETURN I executes a
single drive integrity test. If a single drive integrity test is selected, the test prompts:
DRIVE TEST NUMBER (H)

[] ?

Enter a number (in hex) specifying the drive integrity test to be executed. Consult the appropriate disk
maintenance or service manual to determine the number of the test to perform. Entering a test number
not supported by the drive results in an error #13 generated in test 5.
The test prompts for the number of passes to perform:
t OF PASSES TO PERFORM (1 to 32767) (D) [1]

Enter a decimal number between 1 and 32767 srecifying the number of test repetitions. Tenninate the
response with a carriage return. Typing IRETURN_ without entering a number runs the test once.

5-10
DEVICE INTEGRITY TESTS

5.5.5 ILDISK Specifying Requestor and Port
Drives UNKNOWN to the HSC disk functional software are tested by specifying the requestor number
and port number of the drive. The requestor number is any number 2 through 9 (HSC70) or 2 through
7 (HSC50 [modified] or HSC50) specifying the disk data channel connected to the drive under test.
The port number is 0 through 3; it specifies which of four disk data channel ports is connected to the
drive under test. The requestor number and port number can be determined in one of two ways:
1. By tracing the SDI cable from the desired disk drive to the HSC bulkhead connector, and then
tracing the bulkhead connector to a specific port on one of the disk data channels.
2. By' using the SHOW DISKS command to display tie requlstor and port numbers of all known
drives. To use this method, exit ILDISK by typing CTRUV Type SHOW DISKS IRETURNI in
response to the HSC prompt. This command displays a list of all known drives including the
requestor number and port number for each drive. Each disk data channel has four possible ports
to which a drive can be connected. By inference, the port number of the unknown unit must be
one not listed in the SHOW DISKS display (assuming the unknown drive is not connected to a
defective disk data channel). A defective disk data channel illuminates the red LED on the lower
front edge of the module (refer to Chapter 2).
After a requestor number and a port number are supplied to ILDISK, the program checks to ensure the
specified requestor and port do not match any drive known to the HSC software. H the requestor and
port do not match a known drive, ll...DISK prompts for the number of passes to perform, as described
in Section 5.5.4. H the requestor and port do match a known drive, ll...DISK reports error 08.

5.5.6 ILDISK Progress Reports
ll...OISK produces an end-of-pass report at the completion of each pass of the integrity test. One pass
of the program can take several minutes depending upon the type of drive being diagnosed.

5.5.7 ILDISK Test Termination

ll...OISK is terminated by typing ICTRuvl or ICTRLJcl The ICTRUVI or ICTRLJcl may not take effect
examNle would be during
immediately because certain parts of the program cannot be intejPted'
SDI commands. Two minutes may be necessary to respond to a CTRUV l or CTRLJC if either is entered
while an SDI DRNE DIAGNOSE command is in progress.

5.5.8 ILDISK Error Message Example
All error messages produced by the disk drive integrity tests conform to the HSC integrity test error
message format (Section 5.1.1.1). Following is a typical ll...DISK error message.
ILOISK>0>09:35 T 005 E 035 U-000082
ILOISK>O>Orive Diagnostic Detected Fatal Error
ILOISK>0>FRU1-Orive
FRU2ILOISK>O>Requestor Number 04
ILOISK>O>Port Number 03
ILOISK>O>Test 0025 Error 007F
ILOISK>O>End Of Pass 00001

5-11
DEVICE INTEGRITY TESTS

5.5.9 ILDISK Error Messages
Messages produced by ILDISK are described in the following list.
•

Error 01, DDUSUB INITIALIZATION FAILURE-The HSC diagnostic interface did n0t
initialize. Error Oi is not recoverabie and is caused by:

1. Insufficient memory to allocate buffers and control structures required by the diagnostic
interface.
2. HSC disk functional software is not loaded.
•

Error 02, UNIT SELECTED IS NOT A DISK-The response to the unit number prompt was
not of the form Dnnnn (refer to Section 5.5.4).

•

Error 03, DRIVE UNAVAILABLE-The selected disk drive is not available for integrity test use.

•

Error 04, UNKNOWN STATUS FROM DDUSUB-A call to the diagnostic interface resulted in
the return of an unknown status code. This indicates a software error and should be reported via a
Software Performance Report (SPR). See Appendix B for detailed information on SPR submission.

•

Error 05, DRIVE UNKNOWN TO DISK FUNCTIONAL CODE-The disk drive selected
is not known to the HSC disk functional software. The drive may not be communicating with
the HSC, or the disk functional software may have disabled the drive due to an error condition.
ILDISK prompts the user for the drive's requestor and port. Refer to Section 5.5.5 for information
on specifying requestor and port.

•

Error 06, INVALID REQUESTOR OR PORT NUMBER SPECIFIED-The requestor number
given was not in the range 2 through 9 (HSC70) or 2 through 7 (HSC50 [modified] or HSC50), or
the port number given was not in the range 0 through 3. Specify a requestor and port within the
allow-able J;an-ges
i

•

Error 07, REQUESTOR SELECTED IS NOT A K.SDI-Tbe requestor specified was not a disk
data channel (K.sdi/K.si). Specify a requestor that contains a disk data channel.

•

Error 08, SPECIFIED PORT CONTAINS A KNOWN DRIVE-The requestor and port
specified contain a drive known to the HSC disk functional software. The unit number of the
drive is supplied in the report. ILDISK does not allow testing a known drive via requestor number
and port number.

•

Error 09, DRIVE CAN'T BE BROUGHT ONLINE-A failure occurred when ILDISK
attempted to bring the specified drive online. One of the following conditions occurred.
•

UNIT IS OFFLINE-The specified unit went to the Offline state and now cannot communicate
with the HSC.

•

UNIT IS IN USE-The specified unit is now marked as in use by another process.

•

UNIT IS A DUPLICATE-Two disk drives are connected to the HSC, both with the same unit
number.

•

UNKNOWN STATUS FROM DDUSUB-The HSC diagnostic interface returned an unknown
status code when ILDISK attempted to bring the drive online. Refer to error 04 for related
information on this error.

•

Error 10, K.SDI DOES NOT SUPPORT MICRODIAGNOSTICS-The K.sdi/K.si connected
to the drive under test does not support microdiagnostics. This indicates the K.sdi/K.si microcode
is not at the latest revision level. This is not a fatal error, but the K.sdi/K.si should probably be
updated with the latest microcode to improve error detection capabilities.

•

Error 11, CHANGE MODE FAILED-ILDISK issued an SDI CHANGE MODE command to
the drive and the command failed. The drive is presumed the failing unit because the SDI interface
was previously verified.

5-12
DEVICE INTEGRITY TESTS

•

Error 12, DRIVE DISABLED BIT SET-The SDl verification test issued an SDI GET STATUS
command to the drive under test. The drive disabled bit was set in the status returned by the drive,
indicating the drive detected a serious error and is now disabled.

•

Error 13, COMMAND FAILURE-The SDI verification test detected a failure while attempting
to send an SDI command to the drive. One of the following occurred.

•

DID NOT COMPLETE-The drive did not respond to the command within the allowable time.
Further SDI operations to the drive are disabled.

•

K.SDI DETECTED ERROR-The K.sdi/K..si detected an error condition while sending the
command or while receiving the response.

•

UNEXPECTED RESPONSE-The SDI command resulted in an unexpected response from the
drive. This error can be caused by a DIAGNOSE command if a single drive integrity test was
selected, and the drive does not support the specified test number.

Error 14, CAN'T WRITE ANY SECTOR ON TRACK-As part of test 04, ILDISK attempts to
write a pattern to at least one sector of each track in the read/write area of the drive DBN space.
(DBN space is an area on every disk drive reserved for diagnostic use only.) During the write
process, ILDISK detected a track with no sector that passed the read/write test. (ILDISK could not
write a pattern and read it back successfully on any sector on the track.) The error information for
the last sector accessed is identified in the error report. The most probable cause of this error is a
disk media error.
If test 03 also failed, the problem could be in the disk read/write electronics, or the DBN area of the

disk may not be formatted correctly. To interpret the MSCP status code, refer to Section 5.5.9.l.
•

Error 15, READIWRITE READY NOT SET IN ONLINE DRIVE-The SDI verification test
executed a command to interrogate the real time drive state line of the drive. The line status
reported the drive was in the Online state, but the Read/Write Ready bit was not. set in the status.
This could be caused by a failing disk drive, bad R/W logic, or bad software media.

•

Error 16, ERROR RELEASING DRIVE-ILDISK attempted to release the drive under test.
The release operation failed. One of the following occurred.
•

COULD NOT DISCONNECT-An SDI DISCONNECT command to the drive failed.

•

UNKNOWN STATUS FROM DDUSUB-Refer to error 04.

•

Error 17, INSUFFICIENT MEMORY, TEST NOT EXECUTED-The SDI verification test
could not acquire sufficient memory for control structures. The SDl verification test could not be
executed. Use the SETSHO command, SHOW MEMORY, to display available HSC memory. If
any disabled memory appears in the display, consider further testing of the memory module. If no
disabled memory is displayed, and no other integrity test or utility is active on this HSC, submit an
SPR. See Appendix B for detailed information on SPR submission.

•

Error 18, K MICRODIAGNOSTIC DID NOT COMPLETE-The SDI verification test directed
the disk data channel to execute one of its microdiagnostics. The microdiagnostic did not complete
within the allowable time. All drives connected to the disk data channel may now be unusable
(if the microdiagnostic never completes) and the HSC probably must be rebooted. The disk data
channel module is the probable failing FRU.

•

Error 19, K MICRODIAGNOSTIC REPORTED ERROR-The SDI verification test directed
the disk data channel to execute one of its microdiagnostics. The microdiagnostic completed and
reported an error. The disk data channel is the probable FRU.

5-13
DEVICE INTEGRITY TESTS

•

Error 20, DCB NOT RETURNED, K FAILED FOR UNKNOWN REASON-The SDI
verification test directed the disk data channel to execute one of its microdiagnostics. The
microdiagnostic completed without reporting any error, but the disk data channel did not return
the Dialogue Control Block (DCB). All drives connected to the disk data channel may now be
unusable. The disk data channel is the probable FRU and the HSC probably will have to be
rebooted.

•

Error 21, ERROR IN DCB ON COMPLETION-The SDI verification test directed the disk data
channel to execute one of its microdiagnostics. The microdiagnostic completed without reporting
any error, but the disk data channel returned the Dialogue Control Block (DCB) with an error
indicated. The disk data channel is the probable FRU.

•

Error 22, UNEXPECTED ITEM ON DRIVE SERVICE QUEUE-The SDI verification
test directed the disk data channel to execute one of its microdiagnostics. The microdiagnostic
completed without error, and the disk data channel returned the Dialogue Control Block (DCB)
with no errors indicated. However, the disk data channel sent the drive state area to its service
queue, indicating an unexpected condition in the disk data channel or drive.

•

Error 23, FAILED TO REACQUIRE UNIT-In order for ll...DISK to allow looping, the drive
under test must be released and then reacquired. (This method is required to release the drive from
the Online state.) The release operation succeeded, but the attempt to reacquire the drive failed.
One of the following conditions occurred.
•

DRIVE UNKNOWN TO DISK FUNCTIONAL CODE-A fatal error caused the HSC disk
functional software to declare the drive inoperative, hence the drive unit number is not
recognized. The drive must now be tested by specifying requestor and port number.
DRIVE UNAVAll...ABLE-The specified drive is now not available for integrity test use.

•

UNKNOWN STATUS FROM DDUSUB-Refer to Error 04.
The drive may be allocated to an alternate HSC. Check the drive port lamp to see if this caused
the error.

•

Error 24, STATE LINE CLOCK NOT RUNNING-The SD! verification test executed a
conlffiand to interrogate the real time drive state of the drive. The returned status indicates the
drive is not sending state line clock to the disk data channel. Either the port, SDI cable, or drive is
defective or the port is not connected to a drive.

•

Error 25, ERROR STARTING I/O OPERATION-ll...DISK detected an error when initiating a
disk Read or Write operation. One of the following conditions occurred.
•

INVALID HEADER CODE-ll...DISK did not supply a valid header code to the HSC
diagnostic interface. This indicates a software error and should be reported via a Software
Performance Report (SPR). See Appendix B for detailed information on SPR submission.

•

COULD NOT ACQUIRE CONTROL STRUCTURES-The HSC diagnostic interface could
not acquire sufficient control structures to perform the operation.

•

COULD NOT ACQUIRE BUFFER-The HSC diagnostic interface could not acquire a buffer
needed for the operation.

•

UNKNOWN STATUS FROM DDUSUB-The HSC diagnostic interface returned an unknown
status code. Refer to Error 04.

NOTE

Retry ILDISK during lower HSC activity for the second and third problems if these errors
persist.

5-14
DEVICE INTEGRITY TESTS

•

Error 26, INIT DID NOT STOP STATE LINE CLOCK-The SOl verification test sent an SOl
INITIALIZE command to the drive. When the drive receives this command, it should momentarily
stop sending state line clock to the disk data channel. The disk data channel did not see the state
line clock stop after sending the initialize. The drive is the most probable FRU.

•

Error 27, STATE LINE CLOCK DID NOT START UP AFrER INIT-The SOl verification
test sent an SOl INITIALIZE to the drive. When the drive receives this command, it should
momentarily stop sending state clock to the disk data channel. The disk data channel saw the state
clock stop, but the clock never restarted. The drive is the most probable FRU.

•

Error 28, I/O OPERATION LOST-While ILOISK was waiting for a disk Read or Write
operation to complete, the HSC diagnostic interface notified ll...OISK that no I/O operation was
in progress. This error may have been induced by a hardware failure, but it actually indicates a
software problem, and the error should be reported by a software performance report (SPR). See
Appendix B for detailed information on SPR submission.

•

Error 29, ECHO DATA ERROR-The SOl verification test issued an SOl ECHO command to
the drive. The command completed but the wrong response was returned by the drive. The SOl
set and the disk drive are the probable FRUs.

•

Error 30, DRIVE WENT OFFLINE-The drive, previously acquired by the integrity test, is
now unknown to the disk functional code. This indicates the drive spontaneously went offline or
stopped sending clocks and is now unknown. The test should be restarted using the requestor and
port numbers instead of drive unit number.

•

Error 31, DRIVE ACQUIRED BUT CAN'T FIND CONTROL AREA-The disk drive was
acquired, and ILOISK obtained the requestor number and port number of the drive from the
HSC diagnostic interface. However, the specified requestor does not have a control area. This
indicates a software problem and should be reported via a Software Performance Report (SPR). See
Appendix B for detailed information on SPR submission.

•

Error 32, REQUESTOR DOES NOT HAVE CONTROL AREA-ILDISK cannot find a control
area for the requestor supplied by the user. One of the following conditions exists:
The HSC does not contain a disk data channel (or other type of requestor) in the specified
requestor position.
The disk data channel (or other type of requestor) in the specified requestor position failed its
initialization integrity tests and is not in use by the HSC.
Open the HSC front door and remove the cover from the card cage. Locate the module slot in
the card cage that corresponds to the re.questor. Refer to the module utilization label above the
card cage to help locate the proper requestor. H a blank module (air baffle) is in the module slot,
the HSC does not contain a requestor in the specified position. H a requestor is in the module
slot, ensure the red LED on the lower front edge of the module is lit. If so, the requestor failed
and was disabled by the HSC. If the red LED is not lit, a software problem exists and should be
reported via a Software Performance Report (SPR). See Appendix B for detailed information on
SPR submission.

•

Error 33, CAN'T READ ANY SECTOR ON TRACK-As part of test 03, ILDISK attempts to
read a pattern from at least one sector of each track in the read only area of the drive DBN space.
(DBN space is an area on every disk drive reserved for diagnostic or integrity test use.) All drives
have the same pattern written to each sector in the read only OBN space.
During the read process, ILDISK detected a track that does not contain any sector with the
expected pattern. Either ILDISK detected errors while reading or the read succeeded, but the
sectors did not contain the correct pattern. The error information for the last sector accessed is
supplied in the error report. The most likely cause of this error is a disk media error. If test 04

5-15
DEVICE INTEGRITY TESTS

also fails, the problem may be in the disk read/write electronics, or the OBN area of the disk may
not be formatted correctly. To interpret the MSCP status code, refer to Section 5.5.9.1.
•

Error 34, DRIVE DIAGNOSTIC DETECTED ERROR-The SOl verification test directed the
disk drive to run an internal integrity test. The drive indicated the integrity test failed, but the
error is not serious enough to warrant removing the drive from service. The test number and error
number for the drive are displayed (in hex) in the error report. For the exact meaning of each error,
refer to the service manual for that drive.

•

Error 35, DRIVE DIAGNOSTIC DETECTED FATAL ERROR-The SOl verification test
directed the disk drive to run an internal integrity test. The drive indicated the integrity test failed
and the error is serious enough to warrant removing the drive from service. The test and error
number are displayed (in hex) in the error report. For the exact meaning of each error, refer to the
service manual for that drive.

•

Error 36, ERROR BIT SET IN DRIVE STATUS ERROR BYTE-The SOl verification test
executed an SOl GET STATUS command to the drive under test. The error byte in the returned
status was nonzero indicating one of the following conditions:
Orive error
Transmission error
Protocol error
Initialization integrity test failure
Write lock error
For the exact meaning of each error, refer to the service manual for that drive.

•

Error 37, ATTENTION SET AFTER SEEK-The SOl verification routine issued a SEEK
cOiilinfu,d to the drive completed, but it resulted in an unexp~ted ATTENTION condition. The
drive status is diSplayed with the error report. Refer to the service manual for that drive.

•

Error 38, AVAILABLE NOT SET IN AVAILABLE DRIVE-The SOl verification routine
executed a command to interrogate the Real Time Drive State Line of the drive. ILOISK found
Available is not set in a drive that should be Available.

•

Error 39, ATTENTION NOT SET IN AVAILABLE DRIVE-The SOl verification routine
executed a command to interrogate the Real Time Drive State Line of the drive and found Attention
is not asserted even though the drive is Available.

•

Error 40, RECEIVER READY NOT SET-The SOl verification routine executed a command
to interrogate the Real Time Drive State Line of the drive. The routine expected to find Receiver
Ready asserted, but it was not.

•

Error 41, READIWRITE READY SET IN AVAILABLE DRIVE-The SOl verification routine
executed a command to interrogate the Real Time Drive State Line of the drive and found Available
asserted. However, Read/Write Ready also was asserted. Read/Write Ready should never be
asserted when a drive is in the Available state.

•

Error 42, AVAILABLE SET IN ONLINE DRIVE-The SOl verification routine issued an
ONLINE command to the disk drive. Then a command was issued to interrogate the Real Time
Drive State Line of the drive. The line status indicates the drive is still asserting Available.

•

Error 43, ATTENTION SET IN ONLINE DRIVE-The SOl verification routine issued an
ONLINE command to the drive. The drive entered the Online state, but an unexpected Attention
condition was encountered.

•

Error 44, DRIVE CLEAR DID NOT CLEAR ERRORS-When ILDISK issued a GET STATUS
command, error bits were set in the drive response. Issuing a DRIVE CLEAR failed to clear the
error bits. The drive is the probable FRU.

5-16
DEVICE INTEGRITY TESTS

•

Error 45, ERROR READING LBN-As part of test 14, ll..OISK alternates between reading
OBNs and LBNs. This tests the drive's ability to seek properly. The error indicates an LBN read
failed. The drive is the probable FRU.

•

Error 46, ECHO FRAMING ERROR-The framing code (upper byte) of an SOl ECHO
command response is incorrect. The EXPected and ACfual ECHO frames are displayed with
the error message. The K.sdi/K.si cable and the drive are the probable FRUs.

•

Error 47, K.SDI DOES NOT SUPPORT ECHO-The disk data channel connected to the drive
under test does not support the SOl ECHO command because the disk data channel microcode is
not the latest revision level. This is not a fatal error, but the disk data channel microcode should be
updated to allow for improved isolation of drive-related errors.

•

Error 48, REQ/PORT NUMBER INFORMATION UNAVAILABLE-ILOISK was unable
to obtain the requestor number and port number from HSC disk software tables. The drive may
have changed state and disappeared while ll..OISK was running. This error also can be caused by
inconsistencies in HSC software structures.

•

Error 49, DRIVE SPINDLE NOT UP TO SPEED-ll..OISK cannot continue testing the drive
because the disk spindle is not up to speed. If the drive is spun down, it must be spun up before
ILOISK can completely test the unit. If the drive appears to be spinning, it may be spinning too
slowly or the drive may be returning incorrect status information to the HSC.

•

Error 50, CAN'T ACQUIRE DRIVE STATE AREA-ll..OISK cannot perfonn the low-level
SOl tests because it cannot acquire the Orive State Area for the drive. The Orive State Area is
a section of the K Control Area used to communicate with the drive via the SOl interface. To
perform the SOl tests ll..OISK must take exclusive control of the Orive State Area; otherwise,
the HSC operational software may interfere with the tests. The Orive State Area must be in an
inactive state (no interrupts in progress) before it can be acquired by ll..OISK. If the drive is
rapidly changing its SOl state and generating interrupts, ll..OISK may be unable to find the drive in
an inactive state.

•

Error 51, FAILURE WHILE UPDATING DRIVE STATUS-When in the process of returning
the drive to the same mode as ll..OISK originally found it , an error occurred while performing
an SOl GET STATUS command. When a drive is acquired by ll..OISK, the program remembers
whether the drive was in 576-byte mode or 512-byte mode (reflected by the S7 bit of the mode
byte in the drive status). When ll..OISK releases the drive (once per pass of the program), the drive
mode is returned to the state the drive was in when ll..OISK first acquired it. In order to ensure the
HSC disk functional software is aware of this mode change, ll..OISK calls the diagnostic interface
routines to perform a GET STATUS to the drive. These routines also update the disk fWlctional
software information on the drive to reflect the new mode.
Error 51 indicates the drive status update failed. The diagnostic interface returns one of three
different status codes with this error:
1. ORIVE ERROR-The GET STATUS command could not be completed due to an error
during the command. If informational error messages are enabled (via a SET ERROR INFO
command), an error message describing the failure should be printed on the console terminal.
2. BAD UNIT NUMBER-The diagnostic interface could not find the unit number specified.
The drive may have spontaneously transitioned to the Offline state (no clocks) since the last
ILDISK operation. For this reason, the unit number is unknown when the diagnostic interface
tries to do a GET STATUS command.
3. UNKNOWN STATUS FROM OOUSUB-Refer to Error 04.

5--17
DEVICE INTEGRITY TESTS

•

Error 52, 576-BYTE FORMAT FAILED-The program attempted to perform a 576-byte fonnat
to the first two sectors of the first track in the read/write DBN area. No errors were detected during
the actual formatting operation, but subsequent attempts to read either of the reformatted blocks
failed. The specific error detected is identified in the error report.

•

Error 53, 512-BYTE FORMAT FAILED-The program attempted to perform a 512-byte fonnat
to the first two sectors of the first track in the read/write DBN area. No errors were detected during
the actual formatting operation, but subsequent attempts to read either of the reformatted blocks
failed. The specific error detected is identified in the error report.

•

Error 54, INSUFFICmNT RESOURCES TO PERFORM TEST-This error indicates further
testing cannot complete due to lack of required memory structures. To perform certain drive tests
aDISK needs to acquire timers, a Dialogue Control Block (DCB), free control blocks (FCBs), Data
Buffers, and enough Control memory to construct two Disk Rotational Access Tables (DRATs). If
any of these resources are unavailable, testing cannot be completed. Under normal conditions these
resources should always be available.

•

Error 55, DRIVE TRANSFER QUEUE NOT EMPTY BEFORE FORMAT-aOISK found
a transfer already queued to the K.sdi/K.si when the format test began. aDISK should have
exclusive access to the drive at this time, and all previous transfers should have been completed
before the drive was acquired. To avoid potentially damaging interaction with. some other disk
process, aOISK aborts testing when this condition is detected

•

Error 56, K.SDI DETECTED ERROR DURING FORMAT-K.sdi/K.si detected an error
during a Format operation. Each error bit set in the fragment request block (FRB) is translated into
a text message which accompanies the error report.

•

Error 57, WRONG STRUCTURE ON COMPLETION QUEUE-While formatting, aOISK
checks each structure returned by t.he K.sdi/K~si to ensure the structure was sent to the proper
completion queue. An Error 57 indicates one of these structures was sent to the wrong completion
queue. This type of error indicates a problem with the K.sdi/K.si microsequencer or a Control
memory failure.

•

Error 58, READ OPERATION TIMED-OUT-To guarantee the disk is on the correct cylinder
and track while formatting, ILOISK queues a Read operation immediately preceding the format
command. The Read operation did not complete within 16 seconds indicating the K.sdi/K.si is
unable to sense sector/index pulses from the disk, or the disk is not in the proper state to perform a
transfer. ll..DISK aborts the format test following this error report.

•

Error 59, K.SDI DETECTED ERROR IN READ PRECEDING FORMAT-To guarantee
the disk is on the correct cylinder and track while formatting, aDISK queues a Read operation
immediately preceding the format command. The Read operation failed so aDISK aborts the
fonnat test. Each error bit set in the fragment request block (FRB) is translated into a text message
which accompanies the error report.

•

Error 60, READ DRAT NOT RETURNED TO COMPLETION QUEUE-To guarantee the
disk is on the correct cylinder and track while formatting, ILDISK queues a Read operation
immediately preceding the format command. The Read operation apparently completed
successfully because the fragment request block (FRB) for the read was returned with no error
bits set. However, the Disk Rotational Access Table (DRAT) for the Read operation was not
returned indicating a problem with the K.sdi/K.si.

•

Error 61, FORMAT OPERATION TIMED-OUT-The K.sdi/K.si failed to complete a Format
operation. A Format operation consists of a read followed by a format. The read completed
successfully, but after waiting a 16-second interval the format was not complete. A change in drive
state may prevent formatting, the drive may no longer be sending sector/index information to the
K.sdi/K.si, or the K.sdi/K.si may be unable to sample drive state. The format test aborts on this
error to prevent damage to the existing disk format.

5-18
DEVICE INTEGRITY TESTS

•

Error 62, FORMAT DRAT WAS NOT RETURNED TO COMPLETION QUEUE-The
K.sdi/K..si failed to complete a Format operation. A Fonnat operation consists of a read followed
by a format. The read completed successfully, and the fragment request block (FRB) for the fonnat
was returned by the K.sdi/K.si with no error indicated. However, the Disk Rotational Access Table
(DRAT) for the Format operation was never returned indicating a probable K.sdi/K..si failure. After
reporting this error, the format test aborts.

•

Error 63, CAN'T ACQUIRE SPECIFIED UNIT-ll..DISK was initiated automatically to te.~t a
disk drive declared inoperative. When initiated by the disk functional software, ll..DISK was given
the requestor number, port number, and unit number of the drive to test. llDISK successfully
acquired the drive by unit number, but the requestor and port number of the acquired drive did
not match the requestor and port given when ll..DISK was initiated. This indicates the HSC
is connected to two separate drives with the same unit number plugs. To prevent inadvertent
interaction with the other disk drive, ll..DISK performs only the low-level SDI tests on the unit
specified by the disk functional software. Read/write tests are skipped because the drive must be
acquired by unit number to perform read/write transfers.

•

Error 64, DUPLICATE UNIT DETECTED-At times during the testing sequence, ll..DISK
must release, then reacquire, the drive under test. After releasing the drive and reacquiring it,
ILDISK noted the requestor and port number of the drive it was originally testing do not match the
requestor and port number of the drive just acquired. This indicates the HSC is connected to two
separate drives with the same unit number. If this error is detected, ll..DISK discontinues testing to
prevent inadvertent interaction with the other disk drive.

•

Error 65, FORMAT TESTS SKIPPED DUE TO PREVIOUS ERROR-To prevent possible
damage to the existing disk fonnat, ll..DISK does not attempt to fonnat if any errors were detected
in the tests preceding the format tests. This error message informs the user that formatting tests
will not be perfonned.

•

Error 66, TESTING ABORTED-ll..DISK was automatically initiated to test a" disk drive which
was declared inoperative by the disk functional code of the HSC. The disk drive had previously
been automatically tested at least twice and somehow was returned to service. Because the tests
performed by ll..DISK may be causing the inoperative drive to be returned to service, ILDISK
does not attempt to test an inoperative drive more than twice. On all succeeding invocations of
ll..DISK, an Error 66 message prints and ll..DISK exits without performing any tests on the drive.
This prevents ll..DISK from automatically initiating and dropping the drive from the test over and
over again.

•

Error 67, NOT ENOUGH GOOD DBNs FOR FORMAT-In order to guarantee the disk is
on the proper cylinder and track, all Formatting operations are immediately preceded by a Read
operation on the same track where the format is planned. This requires the first track in the drive's
read/write DBN area to contain at least one good block which can be read without error. An Error
67 indicates a good block was not found on the first track of the read/write DBN area, so the
formatting tests are skipped

5.5.9.1 MSCP Status Codes-iLDISK Error Reports
This section lists some of the MSCP status codes that may appear in ll..DISK error reports. All
status codes are listed in the octal radix. Further information on MSCP status codes is provided in
Appendix C.

007-Compare Error
010-Forced Error
052-SERDESOverrun
053-SDI Command Timeout
103-Drive Inoperative
110-Header Compare or Header Sync Timeout
112-EDC Error

5-19
DEVICE INTEGRITY TESTS

113--Controller Detected Transmission Error
I50-Data Sync Not Found
I52-Intemal Consistency Error
I53-Position or Unintelligible Header Error
2i3-Losi Read/Write Ready
253-Drive Clock Dropout
313-Lost Receiver Ready
350-Uncorrectable ECC Error
353-Drive Detected Error
410-0ne Symbol ECC Error
412-Data Bus Overrun
413-State or Response Line Pulse or Parity Error
450-Two Symbol ECC Error
452-Data Memory NXM or Parity Error
453-Drive Requested Error Log
510-Three Symbol ECC Error
513-Response Length or Opcode Error
550-Four Symbol ECC Error
553-Clock Did Not Restart After Init
610-Five Symbol ECC Error
613-Clock Did Not Stop After Init
650-Six Symbol ECC Error
653-Receiver Ready Collision
710-Seven Symbol ECC Error
713-Response Overflow
750-Eight Symbol ECC Error

5.5.10 ILDISK Test Summaries
Test summaries for ILDISK follow.
•

Test 0, Parameter Fetching-The part of ILDISK that fetches parameters is identified as test O.
The user is prompted to supply a unit number and/or a requestor and port number. This part of
llDISK also prompts for the number of passes to perform.

•

Test 01, Run K.SDI Microdiagnostics-Commands the disk data channel to execute two of its
resident microdiagnostics. H the revision level of the disk data channel microcode is not up to
date, the microdiagnostics are not executed. The microdiagnostics executed are the partial SDI test
(K.sdi test 7) and the SERDESjRSGEN test (K.sdi/K.si test 10).

•

Test 02, Check for Clocks and Drive Available-Issues a command to interrogate the Real Time
Drive State of the drive. This command does not require an SDI exchange, but the real time status
of the drive is returned to llDISK. The real time status should indicate the drive is supplying
clocks and the drive should be in the Available state.

•

Test 03, Drive Initialize Test-Issues an DRIVE INITIALIZE command to the drive under test.
This checks both the drive and the Controller Real Time State Line of the SDI cable. The drive
should respond by momentarily stopping its clock and then restarting it.

•

Test 04, SDI Echo Test-First ensures the disk data channel microcode supports the ECHO
command. If not, a warning message is issued, and the rest of test 04 is skipped. Otherwise,
the test directs the disk data channel to conduct an ECHO exchange with the drive. An ECHO
exchange consists of the disk data channel sending a frame to the drive and the drive returning it.
An ECHO exchange verifies the integrity of the write/command data and the read/response data
lines of the SDI cable.

5-20
DEVICE INTEGRITY TESTS

•

Test OS, Run Drive Integrity Tests-Directs the drive to run its internal integrity test. The drive
is conunanded to run a single integrity test or its entire set of integrity tests depending upon user
response to the prompt:
Run a Single Drive Diagnostic ?

Before commanding the drive to run its integrity tests, the drive is brought online to prevent the
drive from giving spurious Available indications to its other SDI port. The drive integrity tests are
started when the disk data channel sends a DIAGNOSE command to the drive. The drive does
not return a response frame for the DIAGNOSE until it is finished performing integrity tests. This
can require two or more minutes. While the disk data channel is waiting for the response frame,
ILDISK cannol be interrupted by a ICTRUVI.
•

Test 06, Disconnect From Drive-Sends a DISCONNECf command to the drive and then issues
a GET LINE STATUS internal command to the K.sdi/K.si to ensure the drive is in the Available
state. The test also expects Receiver Ready and Attention are set in drive status and Read/Write
Ready is not set.

•

Test 07, Check Drive Status-Issues a GET STATUS command to the drive to check that none of
the drive's error bits are set. If any error bits are set, they are reported and the test issues a DRIVE
CLEAR command to clear the error bits. If the error bits fail to clear, an error is reported.

•

Test 08, Drive Initialize--Issues a command to interrogate the Real TIme Drive State of the drive.
The test then issues a ORIVE INITIALIZE command to ensure the previous DIAGNOSE command
did not leave the drive in an undefined state.

•

Test 09, Bring Drive Online--Issues an ONLINE command to the drive under test. Then a GET
LINE STATUS command is issued to ensure the drive's real time state is proper for the Online
state. Read/Write Ready is expected to be true; Available and Attention are expected to be false.

•

Test 10, Recalibrate and Seek-Issues a RECALIBRATE command to the drive. This ensures
the disk heads start from a known point on the media. Then a SEEK command is issued to the
drive, and the drive's real time status is checked to ensure the SEEK did not result in an Attention
condition. Then another RECALIBRATE command is issued, returning the heads to a known
position.

•

Test 11, Disconnect From Drive--Issues a DISCONNECf command to return the drive to the
Available state. Then the drive's real time status is checked to ensure Available, Attention, and
Receiver Ready are true and Read/Write Ready is false.

•

Test 12, Bring Drive Online--Attempts to bring the disk drive to the Online state. Test 12 is
executed only for drives known to the HSC disk functional software. Test 12 consists of the
following steps:
1. GET STATUS-ILDISK issues an SOl GET STATUS command to the disk drive.
2. ONLINE-ILDISK directs the HSC diagnostic interface to bring the drive online.

If the GET STATUS and the ONLINE commands succeed, ILDISK proceeds to test 13. If the GET
STATUS and the ONLINE commands fail, ILDISK goes directly to test 17 (termination). Note the
online is performed via the HSC diagnostic interface, invoking the same software operations a host
invokes to bring a drive online. An online at this level constitutes more than just sending a SOl
ONLINE command. The FCf and RCT of the drive also are read and certain software structures
are modified to indicate the new state of the drive. If the drive is unable to read data from the disk
media, the online operation fails. If test 12 fails, ILDISK skips the remaining tests and goes to test
17.

5-21
DEVICE INTEGRITY TESTS

•

Test 13, Read Only I/O Operations Test-Tests that all read/write heads in the drive can seek
and properly locate a sector on each track in the drive read only DBN space. (DBN space is an
area on all disk media devoted to diagnostic or integrity test use.) Test 13 attempts to read at least
one sector on every track in the read only area of the drive's DBN space. The sector is checked to
ensure it contains the proper data pattern. Bad sectors are allowed, but there must be at least one
good sector on each track in the read only area. After each successful DBN read, ILDISK reads
one LBN to further enhance seek testing. This ensures the drive can successfully seek to and from
the DBN area from the LBN area of the disk media. ILDISK proceeds to test 16 when test 13
completes.

•

Test 14, I/O Operations Test (ReadIWrite 512 byte format}-Checks to see if the drive can
successfully write a pattern and read it back from at least one sector on every track in the drive
read/write DBN area. (Read/write DBN space is an area on every disk drive devoted to diagnostic
or integrity test read/write testing.) Bad sectors are allowed, but at least one sector on every track
in the read/write area must pass the test. After test 14 completes, ILDISK proceeds to test 17.

•

Test 17, Terminate ILDISK-Is the ILDISK termination routine. The following steps are
performed:
1. If the drive is unknown to the HSC disk functional software, or if the SOl verification test
failed, proceed to step 5 of this test.
2. An SOl CHANGE MODE command is issued to the drive. The CHANGE MODE command
directs the drive to disallow access to the DBN area and changes the sector size (512 or 576
bytes) back to its original state.
3. The drive is released from exclusive integrity test use. This returns the drive to the Available
state.
4. The drive is reacquired for exclusive integrity test use. This is to allow looping if more than
one pass is selected.
5. If more passes are left to perform, the test is reinitiated.
6. If no more passes are left to perform, ILDISK releases the drive, returns all structures acquired,
and terminates.

5.6 . TAPE DEVICE INTEGRITY TEST (ILTAPE)
ILTAPE initiates tape formatter resident integrity tests or a functional test of the tape transport. In
addition, the test permits selection of a full test of the K.sti/K.si interface. When a full interface
test is selected, the K.sti/K.si microdiagnostics are executed, line state is verified, an ECHO test is
performed, .and a default set of formatter tests is executed. See the DRIVE UNIT NUMBER prompt
in Section 5.6.3 for information on initiating a full test. Detected failures result in fault isolation to the
FRU level.
Three types of tape transport tests are listed below. See Section 5.6.9 for a summary of each.
•

Fixed canned sequence

•

User sequence supplied at the terminal

•

Fixed streamer sequence

5-22
DEVICE INTEGRITY TESTS

5.6.1 ILTAPE System Requirements
The following hardware and software are necessary to run ll..TAPE.
Hardware requirements necessary to run ll..TAPE include:
•

HSC subsystem with K.sti/K..si

•

STI-compatible tape formatter

•

TA78, TA81, or other DSA tape drive (for transfer commands only)

•

Console terminal

•

RX33 disk drive or equivalent (HSC70)

•

TU58 tape device or equivalent (HSC50)

In addition, the I/O Control Processor, Program memory, and Control memory must be working.
Software requirements necessary to run ll..TAPE include:
•

CRONIC

•

DEMON

•

K.sti/K..si microcode (installed with the K.sti/K..si module)

•

Tape functional code (TFUNCY')

•

Diagnostic/utility interface (TDUSUB)

5.6.2 ILTAPE Operating Instructions
The following steps outline the procedure for running ILTAPE. The test assumes an HSC is configured
with a terminal and STI interface. IT the HSC is not booted, start with step 1. H the HSC is already
booted, proceed to step 2.
1. Boot the HSC.
Press the !nit button on the HSC OCP. The following message should appear at the terminal:
INIPIO-I Booting __ _

The boot process takes about one minute, and then the following message should appear at the
terminal:
HSC Version xxxx Date Time

System n

2. Type ICTRUYl
This causes the KMON prompt:
HSC70>

3. Type R DXn:ILTAPE IRETURNl
This invokes the tape device integrity test program, ILTAPE. The DXn in step 3 is the HSC device
name. The n refers to the unit number of the specific HSC drive. For example, DX1: refers to RX33
Drive 1 (HSC70) and DD1: refers to TU58 Drive 1 (HSC50 [modified] or HSC50). The following
message should appear at the terminal:
ILTAPE>D>hh:mm Execution Starting

5-23
DEVICE INTEGRITY TESTS

5.6.3 ILTAPE User Dialogue
The foilowing paragraphs describe ILTAPE/user dialogue during execution of ITJTAPE. Note that the
default values for input parameters appear within the brackets of the prompt. The absence of a value
within the brackets indicates the input parameter is not defaultable.
DRIVE UNIT NUMBER (U)

[]?

If the running of formatter tests or transport tests is wanted, enter Tnnn where nnn is the MSCP unit
number (such as T316).

For a full interface test, enter Xm (where m is any number). Typing X instead of T requires a requestor
number and slot number. The following two prompts solicit requestor/slot numbers.
ENTER REQUESTOR NUMBER (2-9)

[]?

Enter the requestor number. The range includes numbers 2 through 9, with no default value.
ENTER PORT NUMBER (0-3)

[]?

Enter the port number. The port number must be 0, 1, 2, or 3 with no default value. After this prompt
is answered, D...TAPE executes the K.sti/K.si interface test.
EXECUTE FORMATTER DIAGNOSTICS (YN)

[Y]?

Enter IRETURN I to execute formatter tests. The default is Y. Entering N will not run formatter tests.
MEMORY REGION NUMBER (H)

[OJ?

This prompt appears only if the response to the previous prompt was IRETURN L A formatter test is
named according to the formatter memory region where it executes. Enter the memory region (in hex)
in which-1he formatter test is to -execute. aTAPE -conti-nues at the prom-pt for -iterations. Ref-er to the
appropriate tape drive service manual for more information on formatter tests.
EXECUTE TEST OF TAPE TRANSPORT (YN)

[N]?

To t~st the tape tra..'lsport; enter Y (the default is N); H no transport testing is desired~ the dialogue
continues with the ITERATIONS prompt. Otherwise, the following prompts appear.
IS MEDIA MOUNTED (YN)

[N]?

This test writes to the tape transport, requiring a mounted scratch tape. Enter Y if a scratch tape is
already mounted.
FUNCTIONAL TEST SEQUENCE NUMBER (D)

[1]?

Select one of five transport tests. The default is 1 (the canned sequence). Enter 0 if a new user
sequence will be input from the terminal. Enter 2, 3, or 4 to select a user sequence previously input
and stored on the HSC device. User sequences are described in Section 5.6.4. Enter 5 to select the
streaming sequence.
INPUT STEP 00:

This prompt appears only if the response to the previous prompt was O. See Section 5.6.4 for a
description of user sequences.
ENTER CANNED SEQUENCE RUN TIME IN MINUTES (D)

[1]?

Answering this prompt determines the time limit for the canned sequence. It appears only if the canned
sequence is selected. Enter the total- run time limit in minutes. The default is one minute.
SELECT DENSITY (O=ALL, 1=1600, 2=6250)

[OJ?

5-24
DEVICE INTEGRITY TESTS

This prompt permits selection of the densities used during the canned sequence. It appears only if the
canned sequence is selected. One or all densities may be selected; the default is all.
SELECT DENSITY (1=800, 2=1600,

3~6250)

[3]?

This prompt appears only if a user-defined test sequence was selected. The prompt permits selection of
anyone of the possible tape densities. The default density is 6250 bits per inch (bpi).
Enter 1, 2, or 3 to select the desired tape density.
1
2
3

= 800 bpi
= 1600 bpi
= 6250 bpi

The next series of prompts concern speed selection. The particular prompts depend upon the type
of speeds supported, fixed or variable. ll..TAPE determines the speed types supported and prompts
accordingly.
IT fixed speeds are supported, ll..TAPE displays a menu of supported speeds, as follows:
Fixed Speeds Available:
(1)

sss1 ips

(2)

sss2 ips

(n)

sssn ips,

The supported speed in inches per second is shown as sssn. The maximum number of supported speeds
is four. Thus, n cannot be greater than four. The prompt for a fixed speed is:
SELECT FIXED SPEED (D)

[1]?

To select a fixed speed, enter a digit (n) corresponding to one of the above displayed speeds. The
default is the lowest supported speed. ll..TAPE continues at the data pattern prompt.
IT variable speeds are supported, ll..TAPE displays the lower and upper bounds of the supported speeds
as follows:
VARIABLE SPEEDS AVAILABLE:
LOWER BOUND = 111 ips
UPPER BOUND = uuu ips

NOTE
If only a single speed is supported, ILTAPE does not prompt for speed. It runs at the single

speed supported.
To select a variable speed, enter a number within the bounds, inclusively, of the displayed supported
variable speeds. The default is the lower bound. The prompt for a variable speed is:
SELECT VARIABLE SPEED (D)

[0 = LOWEST]?

The next prompt asks for the data pattern.
DATA PATTERN NUMBER (D)

[3]?

5--25
DEVICE INTEGRITY TESTS

Choose one of five data patterns.
O-User supplied
I-All zeros
2-All ones
3-Ripple zeros
4-Ripple ones
The default is 3. H the response is 0, the following prompts appear.
HOW MANY DATA ENTRIES (D)

[]?

Enter the number of unique words in the data pattern. Up to 16 (10) words are permitted.
DATA ENTRY (H)

[]?

Enter the data pattern word (in hex)-for example, ABCD. This prompt repeats until the all data words
specified in the previous prompt are exhausted.
SELECT RECORD SIZE (GREATER THAN OR EQUAL TO 1)

(D)

[8192]?

Enter the desired record size in decimal bytes. The default is 8192 bytes. The maximum record size
that can be specified is 12288.
NOTE

This prompt does not appear if streaming is selected.
ITERATIONS (D)

[1]?

Enter the number of tL'lleS the selected tests are to run. £AJter the narnber of iterations is entered,
the selected tests begin execution. Errors encountered during execution cause display of appropriate
messages at the terminal.

5.6.4 ILTAPE User Sequences
In order to test/exercise a tape transport, write a sequence of commands at the terminal. This sequence
may be saved on the HSC device and be recalled for execution at a later time. Up to three user
sequences can be saved on the HSC device.

Following is a list of supported user sequence commands.
WRT-Write one record
RDF-Read one record forward
ROFC-Read one record forward with compare
ROB-Read one record backward
ROBC-Read one record backward with compare
FSR-Forward space one record
FSF-Forward space one file
BSR-Backspace one record
BSF-Backspace one file
REW-Rewind
RWE-Rewind with erase
UNL--Unload (after rewind)
WTM-Write tape mark
ERG-Erase gap
Cnnn -Counter set to nnn (0 = 1000.)
Donn -Delay nnn ticks (0 = 1000.)
BRnn-Branch unconditionally to step nn
DBnn-Decrement counter and branch if nonzero to step nn

5-26
DEVICE INTEGRITY TESTS

TMnn-Branch on Tape Mark to step no
NTnn-Branch on no Tape Mark to step no
ETnn-Branch on EOT to step no
NEnn-Branch on not EOT to step nn
QUIT-Terminate input of sequence steps
To initiate the user sequence dialogue, type 0 in response to the prompt:
FUNCTIONAL TEST SEQUENCE NUMBER (0)

[1]?

The following paragraphs describe the ll..TAPE/user dialogue during a new user sequence.
INPUT STEP

Enter one of the user sequence commands listed previously. ll..TAPE keeps track of the step numbers
and automatically increments them. Up to 50 steps may be entered. Typing QUIT in response to the
INPUT STEP prompt terminates the user sequence. At that time, the following prompt appears:
STORE SEQUENCE AS SEQUENCE NUMBER (0,2,3,4)

[OJ?

The sequence entered at the terminal may be stored on the HSC load device in one of three files. To
select one of these files, type 2, 3, or 4. Once stored, the sequence may be recalled for execution at
a later time by referring to the appropriate file (typing 2, 3, or 4) in response to the sequence number
prompt.
Typing 0 (the default) indicates the user sequence just entered should not be stored. In this case, the
sequence cannot be run at a later time.
An example of entering a user sequence follows:
INPUT STEP

REW ;Rewind the tape

INPUT STEP

C950 ;Set counter to 950

INPUT STEP

WRT ;Write one record

INPUT STEP

ET07 ;If EOT branch to step 7

INPUT STEP

RDB ;Read backward one record

INPUT STEP

FSR ;Forward space one record

INPUT STEP

OB02 ;Oecrement counter, branch
;to step 2 if nonzero

INPUT STEP

REW

;Rewind the tape

INPUT STEP

QUIT

;Terminate sequence input

STORE SEQUENCE AS SEQUENCE NUMBER (0,2,3,4)

[OJ? 3

This sequence writes a record, reads it backwards, and skips forward over it. If an EOT is encountered
prior to writing 950 records, the tape is rewound and the sequence terminates. Note, the sequence is
saved on the HSC device as sequence number 3 and can be recalled at a later execution of ll..TAPE.

5-27
DEVICE INTEGRITY TESTS

5.6.5 ILTAPE Progress Reports
Wnen transport testing is finished. a summary of soft errors appears on the terminal upon completion
of the test. The format of this summary is:
SOFT ERROR SUMMARY:

READ

WRITE

COMP ARE

xxxxxx xxxxxx xxxxxx

Successful completion of a formatter test is indicated by the following message on the terminal:
TEST nnnn DONE

The formatter test number is represented by nnnn.
When an error is encountered, an appropriate error message is printed on the terminal.

5.6.6 ILTAPE Test Termination
ILTAPE terminates nOjally 4ter the selected tests successfully complete. The program also terminates
after typing ICTRUVI or CTRUC at any time. Further, certain errors cause ILTAPE to terminate
, automatically.

5.6.7 ILTAPE Error Message Example
ILTAPE conforms to the test generic error message format (Section 5.1.1.1). An example of an ILTAPE
error message follows.
ILTAPE>D>09:31 T f 011 E f 011 U-T00101
ILTAPE>D>COMMAND FAILURE
ILTAPE>D>MSCP WRITE MULTIPLE COMMAND
ILTAPE>D>MSCP STATUS:
000000
ILTAPE>D>POSITION
001792

The 'test number reflects the state level where ll..TAPE is executing when an error occurs. This number
does not indicate a separate test that can be called. Table 5-1 defines the ILTAPE test levels.
Table 5-1

ILTAPE Test Levels

Test Number

ILTAPE State

Initialization of tape software interface

Device (port, fonnatter, unit) acquisition

STI interface test in execution

Fonnatter tests executing in response to Diagnostic Request (DR) bit

Tape transport functional test

User-selected fonnatter test executing

Tennination and clean-up

The optional text is dependent upon the type of error.

5-28
DEVICE INTEGRITY TESTS

5.6.8 ILTAPE Error Messages
The following list describes ILTAPE error messages.
•

Error 1, INITIALIZATION FAILURE-Tape path software interface cannot be established due
to insufficient resources (buffers, queues, timers, etc.).

•

Error 2, SELECTED UNIT NOT A TAPE-Selected drive is not known to the HSC as a tape.

•

Error 3, INVALID REQUESTOR/PORT NUMBER-Selected requestor number or port number
is out of range or requestor selected is not known to the system.

•

Error 4'1 REQUESTOR NOT A K.sti-Selected requestor is not known to the system as a tape
data channel.

•

Error 5, TIMEOUT ACQUIRING DRIVE SERVICE AREA-While attempting to acquire the
drive service area (port) in order to run the STI interface test, a timeout occurred. If this happens,
the tape functional code is corrupted. n.TAPE invokes a system crash.

•

Error 6" REQUESTED DEVICE UNKNOWN-Device requested is not known to the tape
subsystem.

•

Error 7, REQUESTED DEVICE IS BUSY-Selected device is online to another controller or
host.

•

Error 8, UNKNOWN STATUS FROM TAPE DIAGNOSTIC INTERFACE-An unknown
status was returned from the test software interface TDUSUB.
Error 9, UNABLE TO RELEASE DEVICE-Upon tennination of ll..TAPE or upon an error
condition, the device(s) could not be returned to the system.

•

Error 10, LOAD DEVICE WRITE ERROR-CHECK IF WRITE LOCKED-An error
occurred while attempting to write a user sequence to the HSC device. Check to see if the HSC
load device is write-pr,tected. The prompt calls for a user sequence number. To break the loop of
reprompts, type CTRUY.

•

Error 11, COMMAND FAILURE-A command failed during execution of ILTAPE. The
command in error may be one of several types such as an MSCP or Level 2 STI command.
The failing command is identified in the optional text of the error message. For example:
ILTAPE>D>MSCP READ COMMAND
ILTAPE>D>MSCP STATUS: nnnnnn

•

Error 12, READ MEMORY BYTE COUNT ERROR-The requested byte count used in the
read (formatter) memory command is different from the actual byte count received.
EXPECTED COUNT: xxxx

ACTUAL COUNT: yyyy --

•

Error 13, FORMATIER DIAGNOSTIC DETECTED ERROR-A test running in the formatter
detects an error. Any error text from the formatter is displayed.

•

Error 14, FORMATTER DIAGNOSTIC DETECTED FATAL ERROR-A test running in the
formatter detects a fatal error. Any error text from the formatter is displayed.

•

Error 15, LOAD DEVICE READ ERROR-While attempting to read a user sequence from the
load device, a read error was encountered. Ensure a sequence has been stored on the load device
as identified by the user sequence number. The program reprompts for a user sequence nmnber. To
break the loop of reprompts, type ICTRUVl

•

Error 16, INSUFFICIENT RESOURCES TO ACQUIRE SPECIFIED DEVICE-During
execution, n.TAPE was unable to acquire the specified device due to a lack of necessary resources.
This condition is identified to ll..TAPE by the tape functional code via the diagnostic interface,
TDUSUB. ILTAPE has no knowledge of the specific unavailable resource.

5-29
DEVICE INTEGRITY TESTS

•

Error 17, K MICRODIAGNOSTIC DID NOT COMPLETE-During the STI interface test, the
requestor microdiagnostic timed out.

•

Error 18, K MICRODIAGNOSTIC REPORTED ERROR-During the STI interface test, an
error condition was reported by the K microdiagnostics.

•

Error 19, DCB NOT RETURNED, K FAILED FOR UNKNOWN REASON-During the STI
interface test, the requestor failed for an undetermined reason and the Diagnostic Control Block
(DCB) was not returned to the completion queue.

•

Error 20, ERROR IN DCB UPON COMPLETION-During the STI interface test, an error
condition was returned in the DCB.

•

Error 21, UNEXPECTED ITEM ON DRIVE SERVICE QUEUE-During the STI interface
test, an Wlexpected entry was found on the drive service queue.

•

Error 22, STATE LINE CLOCK NOT RUNNING-During the STI interface test, execution of
an internal command to interrogate the Real Time Formatter State line of the drive indicated the
state line clock is not running.

•

Error 23, INIT DID NOT STOP STATE LINE CLOCK-During the STI interface test, after
execution of a formatter INITIALIZE command, the state line clock did not drop for the time
specified in the STI specification.

•

Error 24, STATE LINE CLOCK DID NOT START UP AFTER INIT-During the STI
interface test, after execution of a formatter INITIALIZE command, the state line clock did not
start up within the time specified in the STI specification.

•

Error 25, FORMATTER STATE NOT PRESERVED ACROSS INIT-The state of the
fonnatter prior to a formatter initialize was not preserved across the initialization sequence.

•

Error 26, ECHO DATA ERROR-Data echoed across the STI interface was incorrectly returned.

•

Error 27, RECEIVER READY NOT SET-After issuing an ONLINE command to the formatter,
the Receiver Ready signal was not asserted.

•

Error 28, AVAILABLE SET IN ONLIN~ FORMATTER-After successful completion of a
formatter ONLINE command to the formatter, the Available signal is set.
Error 29, LOAD DEVICE ERROR-FILE NOT FOUND-During the user sequence dialogue,
ILTAPE was unable to locate the sequence file associated with the specified user sequence number.
Ensure load device media is properly installed. The program reprompts for a user sequence number.
To break the loop of reprompts, type ICTRUYL

•

Error 30, DATA COMPARE ERROR-During execution of the user or canned sequence,
ILTAPE encountered a software compare mismatch on the data written and read back from the
tape. The software compare is actually carried out by a subroutine in the diagnostic interface,
TDUSUB. The results of the compare are passed to ILTAPE. Information in the text of the error
message identifies the data in error.

•

Error 31, EDC ERROR-During execution of the user or canned sequence, ILTAPE encountered
an EDC error on the data written and read back from the tape. This error is actually detected by
the diagnostic interface, TDUSUB, and reported to ILTAPE. Information in the text of the error
message identifies the data in error.

•

Error 32, INVALID MULTIUNIT CODE FROM GUS COMMAND-After a unit number is
input to ILTAPE and prior to acquiring the unit, ILTAPE attempts to obtain the unit's multiunit
code via the GET UNIT STATUS command. This error indicates a multiunit code of zero was
returned to ILTAPE from the tape functional code. Because a multiunit code of zero is invalid, this
error is equivalent to a device unknown to the tape subsystem.

5-30
DEVICE INTEGRITY TESTS

•

Error 33, INSUFFICIENT RESOURCES TO ACQUIRE TIMER-ll...TAPE was unable to
acquire a timer from the system; insufficient buffers are available in the system to allocate timer
queues.

•

Error 34, UNIT UNKNOWN OR ONLINE TO ANOTHER CONTROLLER-The device
identified by the selected unit number is either unknown to the system or it is online to another
controller. Verify the selected unit number is correct and run ll...TAPE again.

5.6.9 ILTAPE Test Summaries
The following sections summarize the tests contained in ILTAPE.
5.6.9.1 K.sti/K.si Interface Test Summary

This portion of ILTAPE tests the STI interface of a specific tape data channel and port. It also performs
low-level testing of the formatter by interfacing to the K.sti/K.si drive service area (port) and executing
various Level 2 STI commands. The testing is limited to dialogue operations; no data transfer is done.
The operations performed are DIAGNOSE, READ MEMORY, GET DRIVE STATUS, and READ
LINE STATUS.
K.sti/K.si microdiagnostics are executed to verify the tape data channel. A default set of formatter tests
(out of memory region 0) is executed to test the formatter, and an echo test is performed to test the
connection between the port and the formatter.
Failures detected are isolated to the extent possible and limited to tape data channel, the STI set, or
the formatter. The STI set includes a small portion of the K.sti/K.si module and the entire STI (all
connectors and cables and a small portion of the drive). The failure probabilities of the STI set are:
1. STI cables or connectors (most probable)
2. Formatter
3. K.sti/K.si (least probable)
When the STI set is identified as the FRU, replacement should be in the order indicated in the
preceding list.
5.6.9.2 Formatter Tests Summary

Formatter tests are executed out of a formatter memory region selected by the user. Refer to the
particular tape drive service manual (for example, TA78 Magnetic Tape Drive Sen'ice Manual) for a
description of the formatter tests. Failures detected identify the formatter as the FRU.
5.6.9.3 User Sequences Test Summary

User sequences are used to exercise the tape transport. The particular sequence is totally user-defined.
Refer to Section 5.6.4.
5.6.9.4 Canned Sequence Test Summary

The canned sequence is a fixed routine for exercising the tape transport. The canned sequence first
performs a quick verify of the ability to read and write the tape at all supported densities. Using a
user-selected record size, it then writes, reads, and compares the data written over a 200-foot length of
tape. Positioning over this length of tape is also performed. Finally, random record sizes are used to
write, read, compare, and position over a 50-foot length of tape. Errors encountered during the canned
sequence are reported at the terminal.

5-31
DEVICE INTEGRITY TESTS

5.6.9.5 Streaming Sequence Test Summary
The streaming sequence is a fixed sequence which attempts to write and read the tape at speed (without
hesitation). The entire tape is written, the~ rewound, and the entire tape is read back. Execution
may be terminated at any time by typing ~
NOTE

In reading the tape, ILTAPE uses the ACCESS command. This allows the tape to move at speed.
This is necessary because of the buffer size restrictions existing for test programs.

5.7 TAPE COMPATIBILITY TEST (ILTCOM)
nXCOM tests the compatibility of tapes that may have been written on different systems and different
drives with STI compatible drives connected to an HSC via the STI bus. ll...TCOM may generate,
modify, read, or list a compatibility tape. Data read from the compatibility tape is compared to the
expected pattern. A compatibility tape consists of groups of files--called bunches-of records of
specific data patterns.
Each bunch contains a header record and several data records of different sizes and is tenninated by
a tape mark. The last bunch on a tape is followed by an additional tape mark (thus forming logical
EOT).
Each hunch contains a total of 199 records: one header record followed by 198 data records. The
header record contains 48 (decimal) bytes of 6 bit-encoded descriptive information, as follows:
Table 5-2

ILTeOM Header Record

Field

Description

Length

Example

1
2

Drive type
Drive serial number
Processor type
Processor serial number
Date
Comment 1

6 bytes
6 bytes
6 bytes
6 bytes
6 bytes
18 bytes

TA78

3
4

5
6

123456
HSC70

123456
093083
Comment

In..TCOM can read but cannot generate a comment field.

The data records are arranged as follows:
•

Sixty-six records 24 (decimal) bytes in length. These records sequence through 33 different data
patterns. The 1st and 34th records contain pattern 1, the 2nd and 35th records contain pattern 2,
etc., through the 33rd and 66th records containing pattern 33.

•

Sixty-six records 528 (decimal) bytes in length. These records sequence through the 33 data
patterns as described above.

•

Sixty-six records 12,024 (decimal) bytes in length. These records sequence through the 33 data
patterns in the same manner as the preceding data patterns.

The data patterns used are shown in Table 5-3.

5-32
DEVICE INTEGRITY TESTS

Table 5-3

ILTeOM Data Patterns

Pattern
Number

Pattern

Description

1
2
3
4
5

377
000
274,377,103,000
000,377,377,000
210, 104, 042, 021

Ones
Zeros
Peak shift
Peak shift
Floating one

6
7
8
9
10

273, 167, 356, 333
126, 251
065,312
000,377
001

Floating zero
Alternate bits
Square pattern
Alternate frames
Track 0 on

11
12
13
14
15

002
004
010
020
040

Track 1 on
Track 2 on
Track 3 on
Track 4 on
Track 5 on

16
17
18
19
20

100
200
376
375
373

Track 6 on
Track 7 on
Track 0 off
Track 1 off
Track 2 off

21
22
23
24
25

367
357
337
277
177

Track 3 off
Track 4 off
Track 5 off
Track 6 off
Track 7 off

26
27
28
29
30

207,377,370,377
170,377,217,377
113, 377, 264, 377
035,377,342,377
370,377,207,377

Bit peak shift

31
32
33

217, 377, 170, 377
264, 377, 113, 377
342, 377, 035, 377

5.7.1 ILTCOM System Requirements
Hardware requirements necessary to run ILTCOM include:
•

An HSC subsystem with K.sti/K.si

•

STI-compatible tape formatter

•

Drive

Because ILTCOM is not diagnostic in nature, all of the necessary hardware is assumed to be working.
Errors are detected and reported but fault isolation is not a goal of ILTCOM.

5-33
DEVICE INTEGRITY TESTS

Software requirements include:
=

CRONIC

•

DEMON

•

K.sti/K.si microcode

•

TFUNCf

•

TDUSUB

5.7.2 ILTCOM Operating Instructions
The following steps outline the procedure for running ILTCOM. ILTCOM assumes the HSC is
configured with a terminal, STI interface, and a TA78 tape drive (or STI-compatible equivaJent).
If the HSC is already booted, proceed to step 2. If the HSC needs to be booted, start with step 1.
1. Boot the HSC.
Press the lnit button on the OCP of the HSC. The following message should appear at the terminal:
INIPIO-I Booting ...

The boot process can take several minutes, and then the following message should appear at the
terminal:
HSC Version xxxx Date Time System n

2. Type ICTRUVI.
This causes the KMON prompt:
HSC>

3. Type R DXn:ILTCOM IRETURNI where n equals the number of the RX33 drive containing the
system diskette. When running ILTCOM on an HSC50 (modified) or HSC50, use DOn: to access
the TU58 tape drive.
This invokes the compatibility test program, ILTCOM. The following message should appear at the
terminal:
ILTCOM>D>hh:mm Execution Starting

The subsequent program dialogue is described in the next section.

5.7.3 ILTCOM Test Parameter Entry
ILTCOM allows the writing, reading, listing, or modifying of compatibility tapes. The following
describes the user dialogue during the execution of ILTCOM. DRIVE UNIT NUMBER (U)

[]?

Enter the tape drive MSCP unit number (such as TIl).
SELECT DENSITY FOR WRITES (1600, 6250)

[]?

Enter the write density by typing (up to) four characters of the density desired (1600 for 1600 bpi).
SELECT FUNCTION (WR=WRITE,REA=READ,ER=ERASE,
LI=LIST,REW=REWIND,EX=EXIT) []?

Enter the function by typing the characters that uniquely identify the desired function (for instance,
REA for read).

5-34
DEVICE INTEGRITY TESTS

The subsequent dialogue is dependent upon the function selected.
•

WRITE--The write function writes new bunches on the compatibility tape. Bunches are either
written one at a time or over the entire tape. Bunches are written from the current tape position. If
the write function is selected, the following prompts occur.
PROCEED WITH INITIAL WRITE (YN)

[N]?

Type Y IRETURN I to proceed with the initial write. The default is no, in which case program control
is continued at the function selection prompt. If the response is yes, the following prompt occurs.
WRITE ENTIRE TAPE (YN)

[N]?

Type Y IRETURN I (for yes) if the entire tape is to be written. Writing of bunches begins at the
current tape position and continues to physical EOT (end-of-tape). Type N IRETURN I (for no), which
is the default, if the entire tape is not to be written. In this case, only one bunch is written from the
current tape position. This prompt only appears on the initial write selection. Mter the bunch(es)
has been written, control continues at the function selection prompt.
•

READ-The read function reads and compares the data in the bunches with an expected
(predefined) data pattern. As the reads occur, the bunch header information is displayed at the
terminal. The format of the display is shown in the following example.
BUNCH
01 WRITTEN BY TA78 SERIAL NUMBER 002965
ON A HSC70 SERIAL NUMBER 005993 ON 09-18-84

The number of bunches to be read is user selectable. All reads are from BOT. If the read function
is selected, the following prompt appears.
READ HOW MANY BUNCHES (D)

[O=ALL]?

Type the number of bunches to be read. The default (0) causes all bunches to be read. After
the requested number of bunches have been read and compared, control continues at the function
selection prompt.
•

LIS'f.-The list function reads and disp1ays the header of each bunch on the compatibility tape
from BOT. The display is the same as the one described under the read function. The data contents
of the bunches are not read and compared. After listing the tape bunch headers, control continues
at the function selection prompt.
ERASE-The erase function erases a user-specified number of bunches from the current tape
position toward BOT. ILTCOM backs up the specified number of tape marks and writes a second
tape mark (logical EOT). This effectively erases the specified number of bunches from the tape.
Thus, for example, if the current tape position is at bunch 5 and the user wishes to erase two
bunches, three bunches are left on the tape after the ERASE command completes.
ll...TCOM does not allow the user to erase all bunches. At least one bunch must remain. For
example, with five bunches on the tape, only four bunches can be erased.
H the erase function is selected, the following prompt appears at the terminal.
ERASE HOW MANY BUNCHES FROM CURRENT POSITION (D)

[OJ?

Type the number of bunches to be erased. The default of 0 results in no change in tape contents or
position. Control continues at the function selection prompt.
•

REWIND-The rewind function rewinds the tape to BOT.

•

EXI'f.-The exit function rewinds the tape and exits the tape compatibility program, ll...TCOM.

5-35
DEVICE INTEGRITY TESTS

5.7.4 ILTCOM Test Termination
iLTCOM is terminated normally by selecting the exit function (EXIT) or by typing L<tili@ or ICTRucl.
Further, certain errors which occur during execution cause ILTCOM to tenninate automatically.

5.7.5 ILTCOM Error Message Example
ILTCOM confonns to the test generic error message fonnat (Section 5.1.1.1). An example of an
ILTCOM error message follows.
ILTCOM>D>09:29 T 000 E 003 U-TOOIOO
ILTCOM>D>COMMAND FAILURE

Where:
•

E nnn is an error number.

•

U -Txxxxx indicates the Tape MSCP unit number.

The optional text is dependent upon the type of error. Some error messages contain the tenn object
count in the optional text. Object count refers to tape position (in objects) from BOT.
5.7.5.1 Error Messages

The following are the ILTCOM error messages.
•

Error 1, INITIALIZATION FAILURE-Tape path cannot be established due to insufficient
resources.

•

Error 2, SELECTED UNiT NOT A TAPE-User selected a drive not known to the system as a
tape.

•

Error 3, COMMAND FAILURE-A command failed during execution of ILTCOM. The
command in error may be one of several types (MSCP level, STI Level 2, etc.). The failing
command is identified in the optional text of the error message. For example:
ILTCOM>D>tt:tt T 000 E 003 U-T00030
ILTCOM>D>COMMAND FAILURE
ILTCOM>D>MSCP READ COMMAND
ILTCOM>D>MSCP STATUS: nnnnnn

•

Error 5, SPECIFIED UNIT NOT AVAILABLE-The selected unit is online to another
controller.

•

Error 6, SPECIFIED UNIT CANNOT BE BROUGHT ONLINE-The selected unit is offline
or not available.

•

Error 7, SPECIFIED UNIT UNKNOWN-The selected unit is unknown to the HSC
configuration.

•

Error 8, UNKNOWN STATUS FROM TDUSUB-An unknown error condition returned from
the software interface TDUSUB.

•

Error 9, ERROR RELEASING DRIVE-Mter completion of execution or after an error
condition, the tape drive could not successfully be returned to the system.

•

Error 10, CAN'T FIND END OF BUNCH-The compatibility tape being read or listed has a
bad fonnat.

5-36
DEVICE INTEGRITY TESTS

•

Error 11, DATA COMPARE ERROR-A data compare error has been detected. The ACI'ual
and EXPected data are displayed in the optional text of the error message. For example:
ILTCOM>D>tt:tt T 000 E 011 U-T00030
ILTCOM>D>DATA COMPARE ERROR
ILTCOM>D>EXPECTED DATA: XXXXXX ACTUAL DATA: YYYYYY
ILTCOM>D>NUMBER OF FIRST WORD IN ERROR: nnnnn
ILTCOM>D>NUMBER OF WORDS IN ERROR: mmmmm
ILTCOM>D>OBJECT COUNT = cccccc

•

Error 12, DATA EDC ERROR-An EDC error was detected. ACI'ual and EXPected values are
displayed in the optional text of the error message.

5.7.6 ILTCOM Test Summaries
ILTCOM writes, reads, and compares compatibility tapes upon user selection. The testing that takes
place looks for compatibility of tapes written on different drives (and systems). As incompatibilities
due to data compare errors or unexpected formats are found, they are reported. ILTCOM makes no
attempt to isolate faults during execution; it merely reports incompatibilities and other errors as they
occur.

5.8 INLINE MULTIDRIVE EXERCISER (ILEXER)
The In line Multidrive Exerciser exercises the various disk drives and tape drives attached to the HSC
subsystetn. The exerciser is initiated upon demand. Drives to be tested are selected by the operator.
The exerciser issues random READ, WRITE, and COMPARE commands to exercise the drives. The
results of the exerciser are displayed on the terminal from which it was initiated. The reports given by
ILEXER do not provide any analysis of the errors reported, nor explicitly call out a specific FRU. This
is strictly an exerciser.
This exerciser runs with other processes on the HSC subsystem. It is loaded from the RX33 or TU58
and uses the services of DEMON (Diagnostic Execution Monitor) and the HSC control software.

5.8.1 ILEXER System Requirements
In order for the ILEXER program to run, the following hardware and software items must be available.

1. HSC subsystem:
a.

Console terminal

b. P.io
c.

K.sdi, K.sti, or K.si

d. Program, Control, and Data memories
e.

RX33 (HSC70) system diskette or TU58 (HSC50 [modified] or HSC50) system tape load
device

2. SDI compatible disk drive
and/or
3. STI compatible tape drive
4. HSC system software, including:
a.

HSC internal operating system

b. DEMON

5-37
DEVICE INTEGRITY TESTS

K.sdi/K.si microcode
and/or

d. K.sti/K.si microcode
e.

SDI manager
and/or

STI manager or equivalent

g. Disk functional code
and/or
h. Tape functional code
i.

Error Handler

Diagnostic Interface to Disk functional code
and/or

k. Diagnostic Interface to Tape functional code
Tests cannot be performed on drives if their respective interface is not available (K.sdi, K.sti, or K.si).

5.8.2 ILEXER Operating Instructions
Perform the following steps to initiate ILEXER (multidrive exerciser).

1. Type ICTRUVI.
2. The HSC responds with:
HSCxx>

3. Type RUN DXO:ILEXER IRETURN I.
DXO: refers to the HSC70 RX33 Drive 1. If running on an HSC50 (modified) or HSC50, DD1: refers
to the HSC50 TU58 Drive 1.
The system loads the program from the specified local HSC load media (any appropriate media with
the image ILEXER in an RTll format). When the program is successfully loaded, the following
message is displayed:
ILEXER>D>hh:mm Execution Starting

Where hh:mm is the current time.
ILEXER then prompts for parameters. Mter all prompts are answered, the execution of the test
proceeds. Error reports and performance summaries are returned from ILEXER.
When ILEXER has run for the specified time interval, reported any errors found, and generated a final
performance summary, the exerciser concludes with the following message:
ILEXER>D>hh:mm Execution Complete

5-38
DEVICE INTEGRITY TESTS

5.8.3 ILEXER Test Parameter Entry
The parameters in ll..EXER follow the format:
PROMPT DESCRIPTION (DATATYPE)

[DEFAULT]?

Where:
•

PROMPT DESCRIPTION explains the type of information ll..EXER needs from the operator.

•

The DATATYPE is the form ll..EXER expects and can be one of the following:
Y/N-Yes/no response
D -Decimal number
U -Unit number (see form below)
H -Number (in hex)

•

DEFAULT is the value used if a carriage return is entered for that particular value. If a default
value is not allowed, it appears as [].

The next prompt is:
DRIVE UNIT NUMBER (U)

[] ?

Enter the unit number of the drive to be tested. This prompt has no default. Unit numbers are either
in the form Dnnnn or Tnnnn, where nnnn is a decimal number between 0 and 4095 which corresponds
to the number printed on the drive's unit plug. The D or T indicates either a disk drive or tape
drive, respectively. Terminate the unit number with a carriage return. ll..EXER attempts to acquire
the specified unit via the HSC Diagnostic Interface. If the unit is acquired successfully, ILEXER
continues with the next prompt. If the acquire fails with an error, one of the following conditions was
encountered.
1. The specified drive is unavailable. This indicates the drive is connected to the HSC but is currently
online to a host CPU or HSC utility. Online drives cannot be diagnosed. ll...EXER repeats the
prompt for the unit number.
2. The specified drive is unknown to the HSC disk functional software. Drives are unknown for one
of the following reasons:
•

The drive and/or K.sdi/K.si port is broken and cannot communicate with the disk functional
software.

•

The drive was communicating with the HSC when a serious error occurred and the HSC ceased
communicating with the drive.

In either case, ILEXER asks the operator if another drive win be selected. If so, it ask" for the unit
number. IT not, ll..EXER begins to exercise the drives selected If no drives are selected, ILEXER

terminates.
When a disk drive is specified, one set of prompts iS presented. When a tape drive is selected, an
entirely different set of prompts is presented. Typing ICTRUZ at any time during parameter input selects
the default values for the remaining parameters.
After a drive is selected and ll..EXER has both acquired the drive and brought it online, or if a
nondefaultable parameter is encountered, the following prompts appear:
ILEXER>D>hh:mm Nondefaultable Parameter

Select up to 12 drives to be exercised: either all disk drives, all tape drives, or a combination of the
two.

5-39
DEVICE INTEGRITY TESTS

5.8.4 ILEXER Disk Drive User Prompts
The following prompts are presented if the drive selected is a disk drive.
ACCESS USER DATA AREA (YIN)

[N]?

A Y answer to this and the following prompt directs ll..,EXER to perform testing in the user data area.
It is the operator's responsibility to see that the data contained there is either backed up or of no value.
If this prompt is answered with an N or carriage return, testing is confined to the disk area reserved for
diagnostics or integrity tests (DBN area). When testing is confined to the DBN area, the following five
prompts are not displayed.
ARE YOU SURE (YIN)

[N]?

An N response causes the DBN area to be exercised. A Y response allows the exercise to take place in
the user data area of th~eft'D BLtC" REPt.Ac.eMl:If)T
DO YOU WANT BBR -(YIN)

[YJ

If the drive is suspected as bad, answer the BBR question with an N. If positive the drive is good,
answer with a Y to enable BBR.
START BLOCK NUMBER (D)

[oJ?

This value specifies the starting block of the area ll..,EXER exercises when the user data area is selected.
If block 0 is specified, ll..,EXER exercises beginning with the first LBN on the disk.
END Block NUMBER (D)

[O=MAX]?

This parameter specifies the ending block of the area ll..,EXER exercises when the user data area is
selected. If block 0 is specified as the ending block, ll...Exa~ exercises up to the last LBN on the disk.
INITIAL WRITE TEST AREA (YIN)

[N]?

Answering Y to this prompt causes ll..,EXER to write the entire test area before beginning random
testing. If the prompt is answered with an N or a carriage return, the prompt immediately following is
omitted.
TERMINATE TEST ON THIS DRIVE FOLLOWING INITIAL WRITE
[N] ?

(YIN)

This question allows an initial write on the drive and terminates the test at that point. The default
answer (N) permits this initial write. After completing the initial write, the test continues to exercise
the drive.
NOTE

The following prompts specify the test sequence for that part of the test following the initial
write portion. That is, even if the operator requests read only mode, the drive will not be
write-protected until after any initial write has been completed.
SEQUENTIAL ACCESS (YIN)

[N]?

The operator has the option of requesting all disk data access be performed in a sequential manner.
READ ONLY (YIN)

[N]?

If answered N, the operator is asked for both a pattern number and the possibility of write only mode.
If the answer is Y, ll..,EXER does not prompt for write only mode, but only asks for a data pattern
number if an initial write was requested.
DATA PATTERN NUMBER (0-15)

(D)

[15]?

5-40
DEVICE INTEGRITY TESTS

The operator has the option of selecting one of 16 disk data patterns. Selecting data pattern 0 allows
selection of a pattern with a maximum of 16 words. The default data pattern (15) is the factory format
data pattern.
WRITE ONLY (YIN)

[N]?

This option permits only Write operations on a disk. This prompt is not displayed if read only mode is
selected.
DATA COMPARE (YIN)

[N]?

If this prompt is answered with an N or a carriage return, data read from the disk is not checked: for
example, disk data is not compared to the expected pattern. If the prompt is answered with a Y, the
following prompt is issued. The media must have been previously written with a data pattern in order

to do a data compare.

DATA COMPARE ALWAYS (YIN)

[N]?

Answering a Y causes ll..EXER to check the data returned by every disk Read operation. Answering
with an N or carriage return causes data compares on 15 percent of the disk reads.
NOTE

Selection of data compares significantly reduces the number of disk sectors transferred in a given
time interval.
ANOTHER DRIVE (YIN)

[]?

Answering with a Y permits selection of another drive for exercising. This prompt has no default.
Answering with an N causes ll...EXER to prompt:
AVERAGE DISK TRANSFER LENGTH IN SECTORS (1 TO 400)

[10]?

This prompt requests the selection of the average size (in sectors) of each data transfer issued to the
disk drives. The default average disk transfer length in sectors is 10.
Once the preceding parameters are entered, ll...EXER continues with the prompts listed as global user
prompts (Section 5.8.6).

5.8.5 ILEXER Tape Drive User Prompts
ll...EXER displays the following prompts if the drive selected is a tape drive.
IS A SCRATCH TAPE MOUNTED (YIN)

[N]?

An N response results in a reprompt for the drive unit number. A Y response displays the next prompt.
ARE YOU SURE (YIN)

[N]?

If the answer is N, the operator is reprompted for the drive unit number. If answered with a Y, the
following prompts are displayed.
DATA PATTERN NUMBER (16-22)

(D)

[21]?

Seven data patterns are available for tape. The default pattern (pattern 21) is defined in Section 5.8.7.
DENSITY (1=800, 2=1600, 3=6250)

(D)

[2] ?

The response to this prompt is a 1, a 2, or a 3. Any other response is illegal, and the prompt is
displayed again. The default is 2 or a density of 1600 bpi.
SELECT AUTOMATIC SPEED MANAGEMENT (YIN)

[N]?

5-41
DEVICE INTEGRITY TESTS

Either Automatic Speed Management (if the feature is supported) or a tape drive speed is selected at
this point. If the choice is Automatic Speed Management, the available speeds are not displayed.
ILEXER>D>FIXED [VARIABLE] SPEEDS AVAILABLE:

This is an informational message identifying the speeds available for the tape drive. If the speeds are
fixed, the value is presented. If the speed is variable within a range, the range is listed, and the next
prompt asks the operator to select a speed. See the tape drive user manual for available speeds.
SELECT FIXED [VARIABLE] SPEED (D)

[1]1

This prompt allows selection of the variable speed for the tape drive selected. See the tape drive user
manual for available speeds.
RECORD LENGTH IN BYTES (1 to 12288)

(D)

[8192]1

Response to this prompt specifies the size in bytes of a tape record. Maximum size is 12K bytes.
The default value is 8192, the standard record-length size for 32-bit systems. Constraints on the HSC
diagnostic interface prohibit selection of the maximum allowable record length of 64K bytes.
DATA COMPARE (YIN)

[N]1

Answering N results in no data compares performed during a read from tape. A Y response causes the
following prompt.
DATA COMPARE ALWAYS (YIN)

[N]1

A Y response selects data compares to be performed on every tape Read operation. An N response
causes data compares to be performed on 15 percent of the tape reads.
ANOTHER DRIVE (YIN)

[]1

Answering Y, the prompts beginning with the prompt for DRIVE UNIT NUMBER are repeated. If
answered with an N, the global prompts in Section 5.8.6 are presented. This prompt has no default,
allowing the operator to default all other pronlpts and to be abje to parameterize another drive for this
pass of ILEXER.

5.8.6 ILEXER Global User Prompts
The following prompts are presented to the operator when no more drives or drive-specific parameters
are to be entered into the testing sequence. These prompts are global in the sense they pertain to all
the drives.
RUN TIME IN MINUTES (1 TO 32767)

[10]1

The minimum time is 1 minute, and the default is 10 minutes. After the exerciser has executed for that
period of time, all testing terminates and a final performance summary is displayed.
HARD ERROR LIMIT (D)

[20]1

The number of hard errors allowed for the drives being exercised can be specified. The limit can be set
from 0 to 20. When a drive reaches this limit, it is removed from any further exercising on this pass
of ILEXER. Hard errors include the following types of errors:
•

Tape drive BOT encountered unexpectedly

•

Invalid MSCP response received from functional code

•

UNKNOWN MSCP status code returned from functional code

•

Write on write-protected drive

5-42
DEVICE INTEGRITY TESTS

•

Tape fonnatter returned error

•

Read compare error

•

Read data EDC error

•

Unrecoverable read or write error

•

Drive reported error

•

Tape mark error (ILEXER does not write tape marks)
Tape drive truncated data read error

•

Tape drive position lost

•

Tape drive short transfer occurred on Read operation

•

Retry limit exceeded for a tape Read, Write, or Read Reverse operation

•

Drive went OFFLINE or AVAILABLE unexpectedly

The prompt next calls for:
NARROW REPORT (YIN)

[N]?

Answering Y presents a narrow report which displays the performance summaries in 32 columns. The
default display, selected by answering N or carriage return, is 80 columns. The format of this display is
described in further detail in Section 5.8.9.2. This report fonnat is intended for use by small hand-held
terminals.
ENABLE SOFT ERROR REPORTS (YIN)

[N]?

This prompt enables soft error reports by answering Y. By default, the operator does not see any soft
error reports specific to the number of retires required on a tape I/O operation. An N response results in
no soft error report. Soft errors are classified as those errors that eventually complete successfully after
explicit controller-managed retry operations. They include Read, Write, and Read-Reverse requested
retries.
.
DEFINE PATTERN 0 -- HOW MANY WORDS (16 MAX)

(D)

[16]?

If data pattern 0 was selected for any preceding drive, the size of the data pattern must be defined at
this time. The pattern can contain as many as 16 words (also the default). If a number larger than 16

is supplied. an error message is displayed and this prompt is presented again. When a valid response is
presented, the following prompt is displayed the specified number of times.
DATA IN HEX (H)

[OJ?

ILEXER expects a four-character hex value as the answer to this prompt.

5.8.7 ILEXER Data Patterns
The data patterns available for use with ILEXER are listed in the following sections. Note that pattern
o is a user-defined data pattern. Space is available for a repeating pattern of up to 16 words.

5-43
DEVICE INTEGRITY TESTS

The following are data patterns for disks.
Pattern 0
User Defined

Pattern 1
105613

Patt.ern 2
031463

Pattern 3
030221

Pattern 4
Shifting 1s
000001
000003
000007
000017
000037
000077
000177
000377
000777
001777
003777
007777
017777
037777
077777
177777

Pattern 5
Shifting Os
177776
177774
177770
177760
177740
177700
177600
177400
177000
176000
174000
170000
160000
140000
100000
000000

Pattern 6
Alter 1s,Os
000000 •
000000
000000
177777
177777
177777
000000
000000
177777
177777
000000
177777
000000
177777
000000
177777

Pattern 7
B1011011011011001
133331

Pattern 8
Pattern 9
B010l. . /B1010 .. B110 .••
052525
155554
052525
.052525
125252
125252
125252
052525
052525
125252
125252
052525
125252
052525
125252
052525
125252

Pattern 10
26455/151322
026455
026455
026455
151322
151322
151322
026455
026455
151322
151322
026455
151322
026455
151322
026455
151322

Pattern 11

Pattern 12
Ripple 1
000001
000002
000004
000010
000020
000040
000100
000200
000400
001000
002000
004000
010000
020000
040000
100000

Pattern 14
Manufacture
155555
133333
155555
155555
133333
155555
155555
133333
155555
155555
133333
155555
155555
133333
155555
155555

Pattern 15
Patterns
155555
133333
066666
155555
133333
066666
155555
133333
066666
155555
133333
066666
155555
133333
066666
155555

Pattern 13
Ripple 0
177776
177775
177773
177767
177757
177737
177677
177577
177377
176777
175777
173777
167777
157777
137777
077777

066666

5-44

DEVICE INTEGRITY TESTS

The following are data patterns for tapes.
Pattern 16
Alternating
one and zero
bits
125252
125252

Pattern 17
All ones

Pattern 20
Alternating
two bytes
ones and two
bytes zeros

Pattern 21
Alternating
three bytes
ones and one
byte zeros

Pattern 19
Alternating
bytes of all

Pattern 19

all ones

Pattern 22

5.8.8 ILEXER Setting/Clearing Flags
The Enable Soft Error Report display prompt in Section 5.8.6 allows the operator to inhibit the display
of soft error reports. No other error reports can be inhibited.

5.8.9 ILEXER Progress Reports
ll..EXER has three basic forms of progress reports: the Data Transfer error report, the Performance

summary, and the Communication error report.

•

The Data Transfer error report is printed each time an error is encountered in one of the drives
being tested.

•

The Performance summary is printed when ILEXER COjPletes la pass on each drive being
exercised or when the operator terminates the pass via a CTRUY. This Performance summary
also is printed on a periodic basis during the execution of ll..EXER.

•

The Communication error report is sent to the console terminal any time ILEXER is unable to
establish and maintain communications with the drive selected for exercising.

5.8.9.1 Data Transfer Error Report

The ll..EXER Data Transfer error report described here is printed on the terminal each time a data
transfer error is found during execution of ll..EXER. The report describes the nature of the error and
all data pertinent to the error found. The Data Transfer error report is a standard HSC error log
message. It contains all data necessary to identify the error. The only exception to this is when the
error encountered by ll..EXER is a data compare error. In this case, ll...EXER has performed a check
and found an error during the compare, resulting in an ll...EXER error report.
5.8.9.2 Performance Summary

The Performance summary is printed on the terminal at the end of a manually tenninated testing
session, or after the specified number of minutes for the periodic Performance summary. This report
provides statistical data which is tabulated by ll..EXER during the execution of this test.
The Performance summary presents the statistics which are maintained on each drive. This summary
contains the drive unit number, the drive serial nunlber, the number of position commands performed,
the number of 0.5 Kbytes read and written, the number of hard errors, the number of soft errors, and
the number of software correctable transfers. For tape drives being exercised by ILEXER, an additional
report breaks down the software correctable errors into eight different categories.

5-45
DEVICE INTEGRITY TESTS

The frequency of report display is altered in the following fashion:
i. Type ICTRUGI during the execution of ILEXER.
2. The following prompt is displayed:
Interval time for performance summary in seconds (D)

[30]1

The format of the Performance summary follows:
PERFORMANCE SUMMARY (DEFAULT)
UNIT R
NO
-Dddd
Tddd

SERIAL
NUMBER

POSI
TION

KBYTE
READ

KBYTE
WRITTEN

HARD SOFT SOFTWARE
ERROR ERROR CORRECTED

HHHHHHHHHHH ddddd dddddddddd dddddddddd ddddd ddddd
HHHHHHHHHHH ddddd dddddddddd dddddddddd ddddd ddddd

ddddd
ddddd

A Perfonnance summary is displayed for each disk drive and tape drive active on the HSC. The
following list explains the Performance summary.
•

UNIT NUMBER-The unit number of the drive. D is for disk, T is for tape. The number is
reported in decimal.

•

R-The status of the drive. If an asterisk (*) appears in this field, the drive was removed from the
test and the operator was previously informed. If the field is blank:, the drive is being exercised.

•

SERIAL NUMBER-The serial number (in hex) for each drive.

•

POSITION-The number of seeks.

•

KBYTE READ-The number of Kbytes read by ILEXER on each drive.

KBYTE WRITTEN-The number of Kbytes written by ILEXER.

•

HARD ERROR-The number of hard errors reported by ILEXER for a particular drive.

•

SOFf ERROR-The number of soft tape errors reported by the exerciser if enabled by the
operator.

•

SOFTWARE CORRECTED-Tne number of correctabie BCC errors encountered by ILEXER.
Only Eee errors above the specific drive Eee error threshold are reported via normal functional
code error reporting mechanisms. Eee errors below this threshold are not reported via an error log
report, but are included in this count maintained by ILEXER.

If any tape drives are exercised, the following summary is displayed within each performance summary.
UNIT
NO

MEDIA
ERROR

DOUBLE
TRKERR

DOUBLE
TRKREV

SINGLE
TRKERR

SINGLE
TRKREV

OTHER
ERR A

OTHER
ERR B

OTHER
ERR C

Tddd

ddddd

An explanation of the summary columns follows.
•

MEDIA ERROR-The number of bad spots detected on the recording media.

•

DOUBLE TRKERR-The number of double track errors encountered during a read or write
forward.

•

DOUBLE TRKREV-The number of double track errors encountered during a read-reverse or
write.

•

SINGLE TRKERR-The number of single track errors detected during a read or write in the
forward direction.

•

SINGLE TRKREV-The number of single track errors encountered during a read-reverse or
write.

5-46
DEVICE INTEGRITY TESTS

•

Other Err A-C-Reserved for future use.
PERFORMANCE SUMMARY (NARROW)
ILEXER>D>PER SUM
D[T]ddd
SN HHHHHHHHHHHH
P ddddd
R dddddddddd
W dddddddddd
HE ddddd
SE ddddd
SC ddddd

This report is repeated for each drive tested.
If tape drives are being tested, the following report is issued for each tape drive following the disk

drive Performance summaries.
ILEXER>D>ERR SUM
ILEXER>D>Tddd
ILEXER>D>ME ddddd
ILEXER>D>DF ddddd
ILEXER>D>DR ddddd
ILEXER>D>SF ddddd
ILEXER>D>SR ddddd
ILEXER>D>OA ddddd
ILEXER>D>OB ddddd
ILEXER>D>OC ddddd

5.8.9.3 Communications Error Report

Whenever ILEXER encounters an error that prevents it from communicating with one of the drives to
be exercised, ll...EXER issues a standard error report. This report gives details enabling the operator
to identify the problem. For further isolation of the problem, the operator should run another test
specifically designed to isolate the failure (ll...OISK or ll...TAPE).

5.8.10 ILEXER Test Termination
Upon completion of the exercise on each selected drive, reporting of any errors found, and display of
final Performance summary, ll...EXER terminates normally. All resources, including the drive ~
tested, are released. The operator may terminate ll...EXER before normal completion by typing ~.
The following output is displayed, plus a final performance summary.
ILEXER>D>hh:mm DIAGNOSTIC ABORTED
ILEXER>D>PLEASE WAIT -- CLEARING OOTSTANDING I/O

Certain parts of ll...EXER cannot be interrupted, so the ICTRUV\ may have no effect for a brief moment
and may need repetition. Whenever ll..EXER is terminated, whether normally or by operator abort,
ll..EXER always completes any outstanding I/O requests and prints a final Performance summary.

5.8.11 ILEXER Error Message Format
ILEXER outputs four types of error formats: prompt errors, data compare errors, pattern word
errors, and communication errors. These formats agree with the generic test error message format
(Section 5.1.1.1).

5-47
DEVICE INTEGRITY TESTS

5.8.11.1 Prompt Error Format
Prompt errors occur when the operator enters the wrong type of data or the data is not within the
specified range for a parameter. The general format of the error message is:
ILEXER>D>error message

Where the error message is an ASCn string describing the type of error discovered.
5.8.11.2 Data Compare Error Format
A data conlpare error occurs when an error is detected during the exercise of a particular drive.

The two formats for the data compare error are data word compare error and pattern word error.
A data word compare error occurs when the data read does not match the expected pattern. The format
of the data compare error is:
ILEXER>D>hh:mm T ddd E ddd U-uddd
ILEXER>D>Error Description
ILEXER>D>MA -- HHHHHHHHHH
ILEXER>D>EXP -- HHHH
ILEXER>D>ACT -- HHHH
ILEXER>D>MSCP STATUS CODE = HHHH
ILEXER>D>FIRST WORD IN ERROR = ddddd
ILEXER>D>NUMBER OF WORDS IN ERROR = ddddd

Where:
•

hh:mm is the current system time.
T is the test number in the exerciser.

•

E corresponds to the error number.

•

U is the unit number for which the error is being reported.

•

MA is the media address (block number) where the error occurred.

•

EXP is the EXPected data.

•

ACT is the data (or code) actually received.

•

MSCP STATUS CODE is the code received from the operation.

•

FIRST WORD IN ERROR describes the number of the first word found in error.

•

NUMBER OF WORDS IN ERROR-Once an error is found, the routine continues to check the
remainder of the data returned and counts the number of words found in error.

The format for the pattern word error is slightly different from the data word compare error. A pattern
word error occurs when the first data word in a block is not a valid pattern number. The format is:
ILEXER>D>hh:mm T ddd E ddd U-uddd
ILEXER>O>Error Description
ILEXER>D>MA -- HHHHHHHHHH
ILEXER>D>EXP -- HHHH
ILEXER>D>ACT -- HHHH

The MSCP status code, first word in error, and number of words in error are not relevant for this type
of error. The other fields are as described for the data compare error.

5-48
DEVICE INTEGRITY TESTS

5.8.11.3 Communications Error Format

Communications errors occur when ILEXER cannot establish/maintain communications with a selected
drive. The error message appears in the following format.
ILEXER>D>hh:mm T ddd E ddd O-uddd
ILEXER>D>Error Description
ILEXER>D>Optional Data lines follow here

Where:
•

hh:mm is the time stamp for the start of ll..EXER.

•

T is the test number in the exerciser.

•

E corresponds to the error number.

•

U is the unit number for which the error is being reported.

•

Error Description is an ASCn string describing the error encountered.

•

Optional Data lines-A maximum of eight optional lines per report.

5.8.12 I LEXE R Error Messages
The following section lists the informational and error messages and explains the cause of the error. A
typical error message is:
ILEXER>D>09.32 Tto06 Et204 O-T00100
ILEXER>D>Comm Error: TBOSOB call failed

5.8.12.1 Informational Messages

The informational messages are not fatal to the exerciser and are intended only to:
•

Alert the user to incorrect input to parameters

•

Indicate missing interfaces

•

Provide user information

The following list describes informational messages.
•

Number must be between 0 and IS-Reported when the user entered an erroneous value for the
data pattern on a disk.

•

Pattern Number mOust be within specified bounds-Reported when the operator tries to specify a
disk pattern number for a tape.

•

You May Enter at Most 16 Words in a Data Patter n-Reported if the operator specifies more
than 16 words for a user-defined pattern, and the operator is reprompted for the value.

•

Starting LBN is either Larger than Ending LBN or Larger than Total LBN on DiskReprompts for the correct values. The operator selected a starting block number for the t~~twhich
is greater than the ending block number selected, or it is greater than the largest block number for
the disk.

•

Please Mount a Scratch Tape-Appears after an N response to the prompt asking if the scratch
tape is mounted on the tape drive to be tested.

•

Disk Interface Not Available-Indicates the disk functionality is not available to exercise disk
drives. This means the K.sdi/K.si is not available or not operable.

•

Tape Interface Not Available-Indicates the tape functionality is not available to exercise tape
drives. This means the K.sti/K.si is not available or not operable.

5-49
DEVICE INTEGRITY TESTS

•

Please Wait-Clearing Outstanding IIO-Printed when the operator types ICTRUVI to stop
ILEXER. All outstanding I/O commands are aborted at this time.

5.8.12.2 Generic Errors
The following iist indicates the error number, text, and cause of errors displayed by ll..EXER.

1. No Disk or Tape Functionality.•.Exerciser Terminated-Neither the K.sdi, K.sti, nor K.si
interfaces are available to run the exercise. This terminates ILEXER.
2. Could not Get Control Block For Timer-Stopping ILEXER-ILEXER could not obtain a
transmission queue for a timer. This should occur only on a heavily loaded system and is fatal to
ILEXER.
3. Could not Get Timer-Stopping ILEXER-The exerciser could not obtain a timer. Two timers
are required for ILEXER. This should only occur on a loaded system and is fatal to ILEXER.
4. Disk functionality Unavailable-Choose Another Drive-The disk interface is not available. A
previous message is printed at the start of ILEXER if any of the interfaces are missing. This error
prints when the operator still chooses a disk drive for the exercise.
5. Tape Functionality Unavailable-Choose Another Drive-The tape interface is not available. A
previous message is printed at the start of ILEXER if any of the interfaces are missing. This error
prints when the operator still chooses a tape drive for the exercise.
6. Couldn't Get Drive Status-Choose Another Drive-ILEXER was unable to obtain the status of
a drive for one of the following conditions:
•

The drive is not communicating with the HSC. Either the formatter or the disk is not online.

•

Tne cabies to the K.sdi, K.sti, or K.si are loose.

7. Drive is Unknown-Choose Another Drive-The drive chosen for the exerciser is not known to
the HSC functional software for that particular drive type. Either the drive is not communicating
with the HSC, or the functional software has been disabled due to an error condition on the drive.
8. Drive is Unavailable--Choose Another Drive-This may be the result of:
•

The drive port button is disabled for that port.

•

The drive is online to another controller.

•

The drive is not able to talk to the controller on the port selected.

9. Drive Cannot Be Brought Online-ILEXER was unable to bring the selected drive online. One
of the following conditions occurred.
•

The unit went into an Offline state and cannot communicate with the HSC.

•

The unit specified is now being used by another process.

•

There are two drives of same type with duplicate unit numbers on the HSC.

•

An unknown status was returned from the HSC diagnostic interface when ILEXER attempted
to bring the drive online.

12. Could not return Drive to Available State-The release of the drive from ILEXER was
unsuccessful. This is the result of a drive being taken from the test due to reaching an error
threshold or going offline during the exercise.
13. User Requested Write on Write-Protected Unit-The operator should check the entry of
parameters and also check the write protection on the drive to make sure they are consistent.
14. No Tape Mounted on Unit ••.Mount and Continue-The operator specified a scratch tape was
mounted on the tape drive selected when it was not mounted. Mount a tape and continue.

5-50
DEVICE INTEGRITY TESTS

15. Record Length larger than 12K or O--The record length requested for the transfer to tape was
either greater than 12K or O.
16. This unit already acquired-A duplicate unit number was specified for a drive and the drive had
already been acquired.

18. Invalid time entered .••must be from 1 to 3599-The user entered an erroneous value to the
performance summary time interval prompt.
20. Could not get buffers for transfers-The buffers required for a tape transfer could not be
acquired.

21. Tape rewind commands were lost~annot continue-The drive was unloaded during ILEXER
execution.
5.8.12.3 Disk Errors
The following list includes the error number, text, and cause of ILEXER disk errors.

102. Drive Spindle not Up to Speed-Spin Up Drive And Restart-The disk drive is not spun up.
103. Drive No Longer Exercised-A disk drive reached the hard error limit or the drive went offline
to the HSC during the exercise.
104. Couldn't Put Drive in DBN Space--Removed From Test-An error or communication problem
occurred during the delivery of an SOl command to put the drive in DBN space.
105. No DACB Available-Notify Field Support, submit SPR-This is reported if no DACBs can be
acquired. H this happens, contact field support as soon as possible and submit an SPR.
106. Some Disk I/O Failed to Complete-An I/O transfer did not complete during an allotted time
period.
107. Command Failed-Invalid Header Code-ILEXER did not pass a valid header code to the
diagnostic interface for the HSC.
108. Command Failed-No Control Structures Available-The diagnostic interface could not obtain
disk access control blocks to run the exercise. The HSC could be overloaded. Try ILEXER on a
quiet system. If the error still occurs, test the HSC memory.
109. Command Failed-No Buffer Available-The diagnostic interface could not obtain buffers to
run the exercise. The HSC could be overloaded. Try ILEXER on a quiet system. II the error still
occurs, test the HSC memory.

Ill. Write Requested on Write-Protected Drive-The operator requested an initial Write operation
on a drive which was already write-protected. The operator should pop out the write-protect button
on the drive reporting the error or have ILEXER do a Read Only operation on the drive.
112. Data Compare Error-Bad data was detected during a Read operation.

113. Pattern Number Error-The first two bytes of each sector, which contain the pattern number,
did not match.
114. EDC Error-Error Detection Code error: invalid data was detected during a Read operation.

116. Unknown Unit number not aUowed in ILEXER-The operator attempted to enter in a unit
number of the form Xnnnn which is not accepted by ILEXER.
117. Disk Unit numbers must be between 0 and 4094 decimal-The operator specified a disk unit
number out of the allowed range of values.
118. Hard Failure on Disk-A hard error occurred on the disk drive being exercised.

5-51
DEVICE INTEGRITY TESTS

The following errors identify the function attempted by ll...EXER which caused an error to occur. Error
logs do not indicate the operation attempted.
119. Hard Failure on Compare operation-A hard failure occurred during a compare of data on the
disk drive.
120. Hard Failure on Write operation-A hard fault occurred during a Write operation on the
specified disk drive.
121. Hard failure on Read operation-A hard failure occurred during a Read operation on the disk
drive being exercised.
123. Hard Failure on INITIAL WRITE Operation-A hard failure occurred during the first write to
the disk drive.
124. Drive No Longer Online-A drive that was being exercised went into an Available state. This
could be caused by the operator releasing the port button on the drive. A fatal drive error could
also cause the drive to go into this state.
5.8.12.4 Tape Errors

The following list includes the error number, text, and cause of ll...EXER tape -errors.
201. Couldn't Get Formatter Characteristics-A communications problem with the drive is
indicated. It could be caused by the unit not being online.
202. Couldn't Get Unit Characteristics-The drive is not communicating with ll...EXER. The unit
could be offline.
203. Some Tape VO Failed to Complete-The drive or formatter stopped functioning properly during
a data transfer.
204. Comm Error: TDUSUB call failed-ll...EXER cannot talk to the drive via interface structures.
They have been removed. Either the drive went available from online, is offline, or a fault
occurred.
205. Read Data Error-A Read operation failed during a data transfer, and none was transferred.
206. Tape Mark Error.••rewinding to restart-ll...EXER does not write tape marks. If this error
occurs, it indicates a drive failure.
207. Tape Position Lost•••rewinding to restart-An error occurred during a data transfer or a retry of
one.
209. Data Pattern Word Error Defect-The first two bytes of a record containing the data pattern did
not match.
210. Data Read EDC Error-Error Detection Code error; incorrect data was detected.
211. Could Not Set Unit Char••• removing from test-The drive is offline and not communicating.
213. Truncated Record Data Error••.rewinding to restart-More data was received than expected,
indicating a drive problem.
214. Drive Error..•Hard Error-A hard failure occurred with the drive being exercised.
215. Unexpected Error Condition •••removing drive from test-This is caused by MSCP error
conditions which are not allowed (i.e., invalid commands, unused codes, write-protected drive
write, etc.).
216. Unexpected BOT encountered•..will try to restart-The drive is experiencing a positioning
problem.
217. Unrecoverable Write Error•••rewinding to restart-A hard error occurred during a Write
operation. The write did not take place due to this error.

5-52
DEVICE INTEGRITY TESTS

218. Unrecoverable Read Error•..rewinding to restart-A hard error occurred during a Read
operation and a data transfer did not take place.
219. Controller Error..•Hard Error•. rewinding to restart-A communications problem exists between
the controller and the formatter.
220. Formatter Error..•Hard Error-A communications problem exists between the formatter and the
controller and/or drive.
221. Retry Required on Tape Drive-A failed Read/Write operation required a retry before
succeeding.
222. Hard Error Limit Exceeded ..•removing drive from test-The- drive exceeded the threshold of
hard errors determined by a global user parameter (Section 5.8.6). The drive is then removed from
the exercise.
224. Drive Went Offline••.removing from test-The drive went offline during the exercise. This is
caused by the operator taking the drive offline or a hard failure forcing the drive offline.
225. Drive Went Available •.•removing from test-The drive became available to ll...EXER and was
not at the beginning of the exercise.
226. Short Transfer Error•••rewinding to restart-Less data was received than transferred.
227. Tape Position Discrepancy-The tape position was lost, indicating a hard failure.

5.8.13 ILEXER Test Summaries
The test numbers in ILEXER correspond to the module being executed within ILEXER itself. The
main module is called MOE, and it calls all other modules.
•

Test number 1, Main Program: MDE-Multidrive Exerciser is the main program within
n..EXER. It is responsible for calling all other portions of ILEXER. It obtains the buffers and
control structures for the exerciser. It verifies that disk or tape functionalities are available before
allowing n..EXER to continue.

•

Test number 2, INITI-INIIT is called to initialize drive statistic tables. It obtains the
parameters and verifies the values of each one entered. This routine calls INICOD to obtain
drive-specific parameters.

•

Test number 3, INICOD-INICOD is the initialization code for ILEXER. It gets the various
parameters for the drives from the operator and fills in the drive statistic tables with initial data
for each drive. It also verifies the validity of the input for the parameters. INICOD, in turn, calls
ACQUIRE to acquire the disk and/or tape drive.

•

Test number 4, ACQUIRE-ACQUIRE is responsible for acquiring the drives as specified by the
operator. It brings all selected drives online to the controller and spins up the disk drives. Errors
reported in this routine cause the removal of the drive from the exercise.

•

Test number S, INITD-INITD initializes the disk drives for the exercise. This routine clears all
disk access control blocks and invokes the initial write.

•

Test number 6, TPINIT-TPINIT initializes the tape drives for the exercise. It rewinds all
acquired tape drives and verifies the drives are at the BOT. H an error occurs, the drive is removed
from the exerciser. TPINIT is also responsible for obtaining buffers for each acquired tape drive.

•

Test number 7, Exerciser-EXER is the main code of the exerciser. It dispatches to the disk
exerciser (QDISK and CDISK) and the tape exerciser (TEXER). It continuously queues up I/O
commands to disk and tape, and checks for I/O completion. The subroutines EXER calls are
responsible for sending commands and checking for I/O completion.

5-53
DEVICE INTEGRITY TESTS

•

Test number 8, QDISK-QDISK is part of the disk exerciser which selects commands to send to
the disk drives. If the initial write is still in progress, it returns to EXER. QDISK calls a routine
to select the command to exercise the disk drive. The following scenario is the algorithm used to
select the command.
If the drive is read only and data compare is not requested, a Read operation is queued to the
drive.
If read only and data compare (occasional) are requested, a Read operation is queued along
with a random choice of compare/not-compare.
If read only and data compare (always) are requested by the operator, a READ-COMPARE
command is queued to the drive.
If write only is requested, and data compare is not, then a write request is queued up to the
disk drive.
If write only and data compare (occasional) are requested, a Write operation is queued along
with a random choice of compare/not-compare.
If write only and data compare (always) are requested, a WRITE-COMPARE command is
queued to the drive.
If only data compare (occasional) is requested, then a random selection of read/write and
compare/not-compare is done.
If only data compare (always) is requested, a COMPARE command is paired with a random
selection of read/write.

QDISK randomly selects the number of blocks for the selected operation.

•

Test number 9, RANSEL-RANSEL is the part of the tape exerciser that is responsible for
sending commands to the tape drives. This routine is called by TEXER, the tape exerciser routine.
RANSEL selects a command for a tape drive using a random number generator. Following are
some constraints for the selection process.
No reads when no records exist before or after the current position.
No writes when records exist after the current position.
No position of record when no records exist before or after the current position.
Reverse commands are permitted on the drive when 16 reverse commands previously have
been selected. That is, lout of every 16 reverse commands are sent to the drive. Immediately
following a reverse command, a position to the end-of-written-tape is performed. The reason
for forward biasing the tape is to prevent thrashing.
The following commands are executed in exercising the tape drives.
1. READ FORWARD

2. WRITE FORWARD
3. POSITION FORWARD

4. READ REVERSE
5. REWIND
6. POSITION REVERSE
RANSEL randomly selects the number of records to read, write, or skip.

5-54

DEVICE INTEGRITY TESTS

•

Test number 10, CDISK-CDISK checks for the completion of disk I/O specified by QDISK.
CDISK checks the return status of a completed I/O operation and if any errors occur, they are
reported.

•

Test number 11, TEXER-TEXER is the main tape exerciser which selects random writes, reads,
and position commands. TEXER processes the I/O once it is completed and reports any errors
encountered.

•

Test number 12, EXCEPT-EXCEPT is the ILEXER exception routine. This is the last routine
Cjlled b~ MDE. EXCEPT is called when a fatal error occurs, when ll..EXER is stopped with
a CTRUY, or when the program expires its allotted time. It cleans up any outstanding I/O, as
necessary, returns resources, and returns control to DEMON.

6-1
OFFLINE DIAGNOSTICS

6
OFFLINE DIAGNOSTICS
6.1

INTRODUCTION·

This chapter describes the offline diagnostics, how to run them, errors that can occur, and summaries
of the tests in each diagnostic. Included in the offline diagnostics are:
rFlG£

b - <6

•

Offline diagnostic loader

•

Offline diagnostic WCS loader

•

Offline cache test (HSC70 only)

•

Offline bus interaction test

6 - 17

10 - I q
~ - Z. 5E:~ 8E5J blhG

Offline K test selector

0 - '3 2-

Offline KIP memory test

G- 4 I

Offline memory test

Fo R. K.., sI

G - 5" /

•

Offline RX33 exerciser (HSC70 only)

•

Ofn ine refresh test

•

Offline Operator Control Panel (OCP) test

b - b 8'

The offline diagnostics contain specific common characteristics, discussed in the following three
sections. These characteristics are listed below.
•

Identical software requirements

•

Common load procedure

•

Identical bootstrap initialization procedures

•

Generic error message format

6.1.1 Offline Diagnostics Software Requirements
All offline diagnostics require boot media containing a bootable image of the diagnostics software

programs. For an HSC70, an RX33 offline diagnostic diskette is required. For an HSC50, a TU58
offline diagnostic tape cassette is required.

6-2
OFFLINE DIAGNOSTICS

6.1.2 Offline Diagnostics Load Procedure
For the HSC70. the offline diagnostics diskette boots from either RX33 drive and should not be writeenabled. This diskette contains the necessary software to run all the HSC70 offline diagnostics.
Booting is done either by powering on or by depressing and releasing the Init switch with the
Secure/Enable switch in the ENABLE position. This causes the P.ioj ROM bootstrap tests to run
followed by the offline P.ioj test.
The offline diagnostics TU58 cassette boots from either TU58 drive and should not be write-enabled.
This TU58 contains the necessary software to run all the HSC50 offline diagnostics. Booting
is accomplished either by powering on or by depressing and releasing the Init switch with the
Secure/Enable switch in the ENABLE position. This causes the P.ioc ROM bootstrap tests to run
followed by the offline P.ioc test.
NOTE

For offline diagnostics, the HSC must be booted with the SecurelEnable switch in the ENABLE
position. If a hardware error occurs during boot, the software executes a halt instruction on
certain errors. A halt instruction, even in Kernel mode, is valid only if the SecurelEnable switch
is in the ENABLE position. Otherwise, the result can be an illegal instruction trap in addition to
the error causing the halt.
In order for the bootstrap to complete successfully, the following must be operational:

•

Basic instruction set of the PDP-II
First 2048 bytes of Program memory plus 8 K words of contiguous Program memory below address
160000

•

RX33 controller and at least one RX33 drive containing a diskette with a bootable image for the
HSC70

•

TU58 controller and at least one TU58 drive containing a cassette with a bootable image for the
HSC50

Before control is turned over to the HSC bootstrap ROMs, internal microcode tests execute in the Jll
(HSC70) or Fll (HSC50) chip sets. Refer to Table 2-1 for definitions of the Jll/Fll module (P.ioj)
LEOs. Also, refer to Figure 8-10 for details of the P.ioj/c internal self-test procedures.

6.1.3 P.ioj/c ROM Bootstrap
The P.ioj/c ROM bootstrap verifies the basic integrity of the P.ioj/c module, part of the Program
memory, and the boot device. The goal of the bootstrap tests is to test enough of the HSC to allow
further test loading from the boot device.
nle bootstrap test is the first step in the HSC initiali7..ation process. It is run for every bootstrap or
reload of the HSC operating system (CRONIC). The bootstrap is initiated automatically each time the
HSC is powered on and also is initiated by CRONIC when a software reboot is required.
The bootstrap is a PDP-II program written to execute in a DCJ II/DCFIl CPU in a stand-alone
environment. This means no other software processes coexist with the bootstrap.
Bootstrap failures are reported via the fault lamp mechanism which specifies the module most likely
causing the problem. See Figure 4-3 for the fault code definitions. An error table is maintained in
Program memory addresses 00000400 through 00000412. These addresses contain the reasons for each
load device boot failure.

6--3
OFFLINE DIAGNOSTICS

6.1.3.1 Bootstrap Initialization Instructions
The following procedure lists the operating instructions for the P.ioj/c ROM bootstrap. Refer to
Section 6.1.3.4 if this procedure fails.

1. HSC70-Insert the offline diagnostics diskette with a bootable image into the RX33 unit 0 drive
(left-hand drive).
2. HSC50--Insert the offline diagnostics tape with a bootable image into either of the TU58 drives.
3. Turn power ON.
4. Set the Secure/Enable switch to the ENABLE position, then depress the Init switch. The bootstrap
initiates automatically.
At this point, the P.ioj/c module executes internal microdiagnostics and then begins to execute from the
boot ROM. The Init lamp lights on the HSC Operator Control Panel (OCP) when the bootstrap PDP-II
tests are done. The load device drive-in-use LED should light within 8 to 10 seconds, indicating the
bootstrap is attempting to load software into Program memory. If the load is successful, the bootstrap
transfers control to the first instruction of the image just loaded from the diskette.
6.1.3.2 Bootstrap Failures
Most bootstrap failures result in lighting the fault lamp on the HSC OCP. When this happens, depress
the Fault switch momentarily, and read the failure code displayed in the OCP lamps. Section 6.1.3.5
indicates the HSC modules most likely causing the bootstrap failure. Momentarily depressing the Init
switch on the OCP reinitiates the bootstrap.

The microdiagnostic LEOs on the JllfFII module indicate if a hard fault exists causing the JIIfF11 to
hang before control is passed the boot ROM. Section 6.1.3.5 contains an explanation of these LEOs.
H a failure occurs in the tests of the PDP-I1 basic instruction set, the fault lamp mechanism does
not report the failure. Instead, the PDP-11 executes a Branch dot (BR .) and does not continue the
bootstrap program. A failure of this type is easily detected because the Init lamp does not light. (The
Init lamp does light immediately after the basic PDP-ll tests successfully complete.)

When a console terminal is connected to the Pjoj!c, the exact instruction that failed is detennined by
depressing the terminal ~ key and noting the address displayed on the terminal. With a bootstrap
listing, this address indicates the instruction that failed.
NOTE

The bootstrap does not accept user-modifiable flags.
6.1.3.3 Bootstrap Progress Reports
The bootstrap does not issue progress reports in the usual sense; however, certain indications of
bootstrap progress are evident. These indications are given in the following list.

•

Lamps clear-Clears all of the HSC OCP lamps. If the lamps fail to clear immediately after
the bootstrap is initiated, a failure of the P.ioj/c is probable. (Circuitry on the P.ioj/c module is
responsible for initiating the bootstrap program.)

•

Init lamp-Lights as soon as the basic tests of the PDP-II instruction set are finished. These tests
normally complete within milliseconds after the bootstrap is initiated. Failure of the Init lamp to
light indicates a failure in the P.ioj/c PDP-1I processor.

•

RX33 drive-in-use-Lights as the bootstrap tries to load the Init P.io test (or offline P.ioj test) from
the RX33 following the test of the PDP-1I and Program memory.

OFFLINE DIAGNOSTICS

•

State lamp-Lights when the bootstrap completes and initiates the Init P.ioj/c test (or offline P.ioj/c
test). When the State lamp is ON, the Init lamp is OFF.

•

Fault lamp-Lights during the boot process if the ROM bootstrap tests have detected a fatal error.

6.1.3.4 Bootstrap Error Information
Specific error codes for the P.ioj/c bootstrap (Codes 21, 22, and 23) are described in detail in Chapter 4.

Because the bootstrap operates in a stand-alone environment, it does not use the tennina) as an error
reporting mechanism. Instead, the HSC OCP lamps are used to report errors and to indicate the module
most likely causing the error.
When the bootstrap detects an error, it lights the fauh lamp on the OCP. When the Fault switch is
depressed, the bootstrap displays a failure code in the OCP lamps. The failure code blinks on and off
at one-half second intervals.
6.1.3.5 Bootstrap Failure Troubleshooting
The OOT program (built into the PDP-II microcode) contains further information about bootstrap
.failures. This information is shown in the following list.

•

Init is off, Fault is lit-A failure was detected after control was passed to the bootable image
loaded from the diskette.

•

Init and Fault both lit-The fault code fiSplayt when the fault lamp is momentarily depressed.
The program is halted by depressing the BREAK key on the console terminal. If 17772340/ is
typed, ODT responds by displaying the contents of address 17772340, the test number. Use the test
number to refer to the appropriate test in Section 6.1.4.

•

Init and Fault lamps are both off-Either the bootstrap program was not automatically initiated
or the bootstrap PDP-ll instruction test failed.
Before proceeding, ensure the Secure/Enable switch is set to the ENABLE position. If the switch
was not in the ENABLE position when the lnit switch was depressed, the HSC did not initiate its
boot sequence. If the Secure/Enable switch is in the correct position, the Jll/Fll microdiagnostics
may have failed.
To check the microdiagnostics, remove the card cage cover and examine the four LEOs on the
central edge of the J 11IFIl module. At powerup, all the LEOs should be set and then turned off
as the J 11/F11 proceeds through its microdiagnostic sequence. When viewed from the edge of the
P.ioj/c module, the LEOs ON or OFF are as follows:

6-5
OFFLINE DIAGNOSTICS

ODT LED -- Lit while in console ODT.
SLU LED -- Lit when SLU failed to respond at 1777560
(console UART present).
HEM LED -- Lit when Progr~" memory did not respond
during microdiagnostics.
SEQ LED -- Lit when very basic J11/F11 internal sequence
test failed.
LED
SEQ

LED
MEM

LED
SLU

LED
ODT

ON
OFF
OFF
OFF
OFF

ON
ON
ON
OFF
OFF

ON
OFF
ON
ON
OFF

ON
OFF
OFF
OFF
ON

I
I PROBABLE FAILURE CAUSE
P.ioj/c
M. std2/M. std first, then P.ioj/c
P.ioj/c
P.ioj/c
P.ioj/c

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

6.1.4 Bootstrap Test Summaries
This section summarizes the bootstrap tests.
•

Test 0, basic PDP-II instruction set-This test verifies the correct operation of a PDP-11
instruction subset. This instruction subset includes only those instructions required for completion
of the bootstrap. The following instructions are tested.
Single operand instructions tested (both word and byte mode):
ADC, CLR, COM, INC, DEC, NEG, TST, ROR, ROL, ASR, ASL, SWAB, NOP
-

Double operand instructions (both word and byte modes):
MOV, CMP, BIT, BIC, BIS, ADD, SUB
Branch instructions tested:
BR, BNE, BEQ, BPL, BMI, BCC (BHIS), BCS (BLO), BGE, BLT, BGT, BLE, BHI, BLOS,
BVC,BVS

J wnp and miscellaneous instructions tested:
JMP, JSR, RTS, SOB, MTPS, MFPS, CCC, CLN, CLV, CLZ, SEN, SEV, SEZ

Addressing modes tested:
All eight addressing modes

The PDP-11 instruction set test uses two methods of reporting errors. During the initial part of the
test, errors result in an infinite program loop at the location of the detected error. During the latter
part of the test (when enough instructions have been tested), the fault lamp mechanism is used to
report failures. Refer to Section 6.1.3.2.
•

Test 1, Program memory (Swap Bank)-The HSC memory module includes special logic that
penn its changing the address range of Program memory. This address range is controlled by the
Swap Banks bit in the P.ioj/c control and status register (CSR). This test verifies the Swap Banks
bit can be set and cleared. (The actual memory switching is not tested, only the setting and clearing
of the bit is tested.) A failure in this test indicates the P.ioj/c module must be replaced.

6-6
OFFLINE DIAGNOSTICS

•

Test 2, Program memory (vector area)-In order for the HSC control program to function, the
first 2048 bytes (addresses 00000000 through 00003777) of Program memory must be working.
This test verifies the first part of Program memory is operating properly. If the test fails. the
Swap Banks feature is used, attempting to swap a portion of memory into the OOOOOOOO through
00003777 address range. If the test still fails after Swap Banks has been invoked, a Program
memory error is reported via the fault lamp mechanism (Section 6.1.3.2). A failure in this test
indicates the M.std2/M.std module must be replaced.

•

Test 3, Program memory (8 Kword partition)-After verifying the first part of Program memory
is working, the bootstrap tries to find an 8 Kword piece of Program memory between address
00004000 and address 00160000. This partition is used to load the Init P.ioj/c test from the load
device. If insufficient memory is available, a Program memory error is reported via the fault lamp
mechanism.
A failure in this test indicates the M.std2/M.std module must be replaced.

•

Test 4, RX33 controller test-This test verifies basic functionality of the control logic on the
M.std2 module. The four controller registers are tested for stuck bits. The DMA hardware is
checked for correct cycling and addressing. The interrupt logic is checked to ensure interrupts are
properly acknowledged. With the control hardware verified, proceed to the next step, and try to
read data from one of the drives.

•

Test 5, RX33 drive/interface test-The goal of this test is to find a working RX33 drive
containing a diskette with a bootable image. Such an image is identified by a PDP-II NOP
instruction in the first word of the image. The intended drive is checked for DRIVE READY from
the interface. Then RECAL/VERIFY commands the drive to seek to track O. This command then
reads the diskette header to verify the recal did move the head to track O.
After a suitable drive is found, the first eight blocks of the diskette are loaded into the 8 K word
partition found in test 3. The eight blocks loaded consist of the first five blocks of the Init P.ioj/c
test (or Offline P.ioj/c test), the RT-ll volume ID block, and the first RT-II directory segment on
the diskette. (The directory blocks are loaded at this time to save directory look-up time in the Init
P.ioj/c test or the Offline P.ioj/c test.)
RX33 drive 0 is tested first. A failure with drive 0 causes the bootstrap to proceed to drive 1 and
begin the tests again. If neither RX33 drive is working correctly, an RX33 error is displayed by
the fault lamps. An error table is maintained in Program memory addresses 00000400 through
00000412, which remembers why each rejected RX33 drive failed the boot.
The error table follows.

Table 6-1

RX33 Error Table

Address

Meaning

00000400

Contains controller error code (code 1 or code 2)

00000402

RX33 address being accessed, if applicable

00000404

Expected result

00000406

Actual result

00000410

Drive error code, byte-encoded: drive l/drive 0
(high-bytellow-byte)

NOTE

It is not possible to simultaneously have information in addresses 00000400 and 00000410.

6-7
OFFLINE DIAGNOSTICS

If the boot fails with a RX33 error, the ODT feature of the PDP-II is used to examine the RX33 error
table to determine why each RX33 drive failed the test. (Remember, the bootstrap tries both drives
before declaring an error.) Use the following sequence to examine the RX33 error table.

Depress the IBREAK I key on the console terminal.
The terminal should type out the address of the current instruction of the bootstrap, then prompt
for input with an @ character.
Type nnn (appropriate address) IRETURN I.
The terminal should print the (octal) contents of that address.

Type Iinefeed IRETURN I to examine Table fr2.

Table 6-2

RX33 Error Code Table

Controller Error

Failure Information

NX1vI occurred while accessing RX33 registers.

A bit was stuck in the registers. See EXPected/ACfual for more infonnation.

Force mode interrupt did not occur.

DMA test mode hardware error occurred.

DMA address counters were wrong after transfer.

Incorrect data found after DMA test operation.

Data parity was bad after DMA test operation.

Drive was not ready (no diskette inserted or door was open).

Hard error (CRC or Record Not Found) occurred on recal/verify.

Track 0 bit was not set after recal.

SEEK command timeout occurred

Seek error (CRC or Record Not Found) occurred

READ SECTOR command timeout.

Hard error (CRC or Record Not Found) occurred on read

Nonbootable image (non-NOP instruction is the first word).

Failure information for both drives in address 00000410 is possible. In this case, nonzero data
is in both bytes. Only when failures are detected on both drives does the boot ROM generate a
LOADFAL failure code and branch to the fault light routine.

•

Test 6, Transfer control to loaded image--This part of the bootstrap is not actual a test.
However, it is given a test number in case an error occurs in this section of code. The PDP11 general registers are loaded with certain parameters (CSR and unit of load device, base address,
and size of partition, etc.). The image loaded from the RX33 is initiated by jumping to the first
instruction. Any errors oc<;urring in this part of the bootstrap are probably unexpected traps or

6-8
OFFLINE DIAGNOSTICS

interrupts caused by intermittent P.ioj/c or M.std2/M.std failures. When the loaded image is started,
the State lamp is lit, and the lnit lamp is turned off.

6.1.5 Offline Diagnostics Error Reporting and Message Format
The method of reporting errors and the message format are common to the offline diagnostics. All
errors are reported on the console terminal as they occur. In all offline diagnostics, error messages
conform to the HSC diagnostic error message format.
The first line of an error message contains general information concerning the error and is mandatory.
The second line of an error message consists of text describing the error and also is mandatory. The
third and succeeding lines of the message are used for additional information where required, and are
optional.
The generic error message format follows.
XXXXXX>hh:mm Tn En UOOO

SEEK error detected during positioning operation
optional line 1
optional line 2
optional line 3

Where:
•

XXXXXX> is the prompt for the particular diagnostic in question (such as OFLCXT> or OBIT».

•

hh:mm is the number of hours and minutes since system boot.

•

Tn is a test number.

•

En is an error number with a range of 1 through 77 (octal).

•

UOOO is the unit number.

The final field in the first line appears only in diagnostics where such infonnation is appropriate. Each
error number has a unique text string associated with it. For errors that consist of results that did not
compare with the expected value, the diagnostic uses the optional lines to show EXPected/ACTual
(EXP/Acr) data. Errors on data transfers and SEEK commands use the optional lines to print out the
LBN, track, sector, and side to help isolate problems to the media or the drive.

6.2 OFFLINE DIAGNOSTIC LOADER
The offline diagnostic loader provides a software environment for the HSC offline diagnostics. The
loader supports a command language that loads and executes an offline diagnostic from the load device
into Program memory. The loader command language also permits the display and modification of any
address contents in the HSC Program, Data, or Control memories.
The software environment provided for offline diagnostics includes a load device driver and a terminal
driver. A standard software interface between the diagnostics and the load device and terminal devices
takes the place of individual interface routines within the diagnostics. The loader also maintains a
timer that keeps track of the relative time since the loader was last booted. This allows diagnostic error
messages to be time-stamped.

&-9

OFFLINE DIAGNOSTICS

6.2.1 Offline Diagnostic Loader System Requirements
Hardware required to run the offline diagnostic loader includes:
•

I/O Control Processor module with HSC Boot ROM

•

At least one memory module

•

RX33 controller with at least one working drive

or
•

TU58 with at least one working drive

•

Terminal connected to I/O Control Processor console interface

6."2.2 Offline Diagnostic Loader Prerequisites
In the process of loading the offline diagnostic loader, several diagnostics are run. The ROM bootstrap
tests the basic PDP-ll instruction set, tests a partition in Program memory, and tests the load device
used for the boot. Then the bootstrap loads the offline P.ioj/c test which completes the PDP-II tests
and the remainder of the I/O Control Processor module tests.

After these tests, the offline diagnostic loader is loaded from the load device to memory, and control is
passed to the loader. Due to the sequence of tests that precede the loader, the loader assumes the I/O
Control Processor module and the RX33 are tested and working.

6.2.3 Operating Instructions for the Offline Diagnostic Loader
Follow these steps to start the offline loader.

1. Insert the HSC offline diagnostics diskette into the load device.
2. Power on the HSC, or depress and release the Init button on the HSC OCP.
3. The load device drive-in-use LED should light within a few seconds, indicating the bootstrap is
loading the offline diagnostic loader to Program memory.
4. In less than 30 seconds, the offline diagnostic loader indicates it has loaded properly by displaying
the following:

Hse OFL Diagnostic Loader, Version Vnnn
Radix=Octal,Data Length=Word,Reloc=OOOOOOOO
OOL>
5. The offline loader is now ready to accept commands. Section 6.2.4 contains information on the
loader command language.

6.2.4 Offline Diagnostic Loader Commands
The following sections describe the commands recognized by the offline loader. Section 6.2.5.2 of this
document is a copy of the offline loader help file.
6.2.4.1 HELP Command
The HELP command supplies an abbreviated list of all commands the loader recognizes. In response
to the HELP command, the loader reads the file OFLLDR.m...P from the load device and displays the
contents of this file on the HSC console terminal. Section 6.2.5.2 contains a listing of the loader help
file.

6-10
OFFLINE DIAGNOSTICS

6.2.4.2 SIZE Command

The offline system sizer is invoked by the SIZE command. The sizer determines the sizes of the HSC
Program, Control, and Data memories, and the type of requestor in each HSC requestor position. (The
requestor position refers to the priority of a particular requestor on the Data and Control memory buses.
It does not match the numbering of module slots.)
6.2.4.3 TEST Command

The offline diagnostic loader TEST command is used to invoke the various offline diagnostics available
on the HSC. The following list shows the particular form of the TEST command used to invoke each
diagnostic. In general, the TEST command format allows specification of the system component to be
tested; for instance, the TEST MEMORY command invokes the offline memory test.
•

Offline cache test-Verifies the full functionality of the onboard cache. The offline cache test is
invoked by the TEST CACHE command.

•

Bus interaction test-Invoked by the TEST BUS command. The bus interaction test generates
contention on the HSC Data and Control memory buses by two or more Ks simultaneously testing
different sections of the Control and Data memories. Two or more working requestors are required
to run this test (including the K.ci).

•

K t.est selector-Invoked by the TEST K command. The K test selector allows specific requestor
microdiagnostics to run.

•

KIP memory test-Invoked by the TEST MEMORY BY K command. The KIP memory test
uses one of the HSC requestors to test either Data or Control memory. This test runs faster than
the offline memory test because a requestor is roughly seven times faster than the I/O Control
Processor. Program memory cannot be tested using the KIP memory test as the Ks do not have an
interface to the Program memory bus.

•

Offline memory test-Invoked by the TEST MEMORY command. This test uses the I/O Control
Processor to test Program, Control, or Data memories.

•

Offline RX33 exerciser-A combined hardware diagnostic and exerciser for the M.std2/RX33
subsystem of the HSC70. Invoke the offline RX33 exerciser by the TEST RX command.

•

Memory refresh test-Invoked by the TEST REFRESH command. The memory refresh test
allows the refresh feature of the memories to be tested.

•

OCP test-Invoked by the TEST OCP command. The OCP test checks the HSC lights and
switches. The test requires manual intervention by an operator.

6.2.4.4 LOAD Command

The LOAD command loads a program into HSC Program memory without starting it. The command
fonnat is LOAD <filename>, where <filename> is the name of any file on the HSC OFFLINE diskette.
The loader finds the specified file and loads it into Program memory. This command is in patching a
program image before starting execution. After the patch is made, the program can be initiated via the
START command described next.
6.2.4.5 START Command

The START command initiates the loader program currently loaded in Program memory. The START
command can be used in conjunction with the LOAD command (see preceding section), or it may be
used to reinitiate the last loaded offline diagnostic. This saves the time required to reload the program
from the load device. For example, you have previously typed SIZE to initiate the offline system sizer
program and after the sizer completes, you wish to run it again. Typing START IRETURN I restarts the
sizer without reloading the program from the load device, saving many seconds of load time.

6-11
OFFLINE DIAGNOSTICS

6.2.4.6 EXAMINE and DEPOSIT Commands
The EXAMINE and DEPOSIT commands are used to display or modify the contents of any location in
the HSC Program, Control, and Data memories. Qualifiers (switches) can be used with these commands
to display bytes, words, long words, or quad words. The radix (octal, decimal, hex) of the displayed
data also clli.~ be controlled by qualifiers. Alternately, the SET DEFAl..JLT conunlli.~d Clli.~ be used to set
the default data length and radix for all EXAMINE and DEPOSIT commands (Section 6.2.4.6.7).
6.2.4.6.1 EXAMINE Command
The EXAMINE command is used to display the contents of any location in the HSC Program, Data,
or Control memories. The format of the command is: EXAMINE <address>. The <address> can
be a string of digits in the current (default) radix. Certain symbolic addresses also are permitted
(Section 6.2.4.6.3).

In the following example, the user entered a command to examine the contents of location 14017776.
(Notice the EXAMINE command can be abbreviated to a single E.) When the loader displays the
contents of location 14017776, the address is preceded by a (0) indicating the location is within Data
memory. The display shows the location contains the value 125252.
EXAMPLE:

ODL> E 14017776
(D) 14017776 125252

6.2.4.6.2 DEPOSIT Command
The DEPOSIT command is used to modify the contents of any location in the HSC Program, Control,
or Data memories. The fonnat of the command is: DEPOSIT <address> <data>. The <address>
can be a string of digits in the current (default) radix. Certain symbolic addresses also are permitted
(Section 6.2.4.6.3).

In the next example, the user entered a command to store the value 123456 in the contents of address
14017776. The previous contents of this Data memory location are replaced with the value specified in
the DEPOSIT command (123456).
EXAMPLE: ODL> D 14017776 123456

6.2.4.6.3 Symbolic Addresses
The four symbols used as symbolic addresses in a DEPOSIT or EXAMINE command are described in
the following list.

•

Asterisk (* )-Indicates the loader is to use the same address as used in the last EXAMINE or
DEPOSIT command. For example, if the contents of address 16012344 were just examined and
the value 1234 is to be deposited into the same address, type DEPOSIT * 1234 IRETURN I instead of
typing DEPOSIT 16012344 1234 IRETURN I.

•

Plus sign (+)-This sign also is used as a symbolic address. This symbol means the loader is to
use the address following the last address used by an EXAMINE or DEPOSIT command. When
the loader sees a + as an address, it takes the last address used by EXAMINE or DEPOSIT and
adds an offset which depends on the current default data length (Section 6.2.4.6.7).
If the current default data length is a byte, the loader adds one to the last address. If the defauh
was a word, the loader adds two to the last address. The offset is four for longword data length and
eight for quadword. This feature is useful when examining a number of items stored in successive
locations.

For example, if a table of words beginning at address 14125234 is being examined, examine the
first location by typing EXAMINE 14125234 IRETURN I. The next location could now be examined
by typing EXAMINE + IRETURN I instead of typing EXAMINE 14125236 IRETURN I.

6-12
OFFLINE DIAGNOSTICS

•

Minus sign (-)-This sign also is used as a symbolic address. It indicates the loader is to u~e the,
address preceding.1he last address used by either command. When the loader sees a - symbol as
an address, the loader takes the last address used by an EXAMINE or DEPOSIT and subtracts an
offset which depends on the current default data length (Section 6.2.4.6.7).
If the current default data length is a byte, the loader subtracts one from the last address. If
the default is a word, the loader subtracts two from the last address. The loader subtracts four
for longword data length and eight for quadword. This feature is useful in the same way as the
+ symbol, but examines a table starting at the highest address and proceeding down to lower
addresses.
For example, if a table of words that ends at address 14012346 is to be examined, the operator
would examine the last location of the table by typing EXAMINE 140123461RETURNl The
preceding location in the table could now be accessed by typing EXAMINE -IRETURNI instead of
typing EXAMINE 14012344IRETURNl

•

At symbol (@)-The @ symbol also is used as a symbolic address. This symbol means the loader
should use the data from the last EXAMINE or DEPOSIT command as an address. This feature
is useful when following linked lists. For example, first examine location 123434 which contains
a pointer to a linked list. Now type EXAMINE @ IRETURN I to examine the location pointed to by
the first location.

6.2.4.6.4 Repeating EXAMINE and DEPOSIT Commands
When troubleshooting memory problems, continuously executing an EXAMINE or DEPOSIT command
is sometimes useful. The REPEAT command is used for this continuous execution. Type REPEAT
EXAMINE or DEPOSl1'J30LD) IRETURNl

In the following example of repeating a DEPOSIT command, the value 125252 is continuously
deposited into address 14017776. The format of the DEPOSIT command does not change. The
DEPOSIT command is just preceded by the word REPEAT. Also, the REPEAT command can be
abbreviated to RE.
Type R&PBAT DEPOSIT 14017776 125252

IRETmllil

or
RB D 14017776 125252 IREW~1

In the repeating an EXAMINE command example, the contents of address 14017776 can be
continuously examined. The format of the EXAMINE command does not change. The EXAMINE
command is just preceded by the word REPEAT.
Type UPBAT BXAMDtB 14017776 IRETURN/

or
RB • 14017776 IRETU~/

In the examples shown, the contents of location 14017776 are displayed continuously on the terminal.
This slows down the repetition of the command and wastes paper on hardcopy devices. Stop
output to the terminal by typing a ICTRuoL However, the loader also provides a special EXAMINE
command qualifier (/INHIBIT) for suppressing output to the terminal. This qualifier is discussed in
Section 6.2.4.6.6. To stop a repeated command, type ICTRucl.

6-13
OFFLINE DIAGNOSTICS

6.2.4.6.5 Relocation Register

The loader provides a relocation register. It can be used to reduce the number of address digits
typed for an EXAMINE or DEPOSIT command when all addresses are in either the Control or Data
memories. The contents of the relocation register are added to the address given with an EXAMINE
Of DEPOSIT command. The relocation register contains a 0 when the loader is initiated, so it normally
has no effect on the addresses typed in an EXAMINE or DEPOSIT command.
Use the following example to examine a large number of locations in Data memory.
OOL> <EMPHASIS>(SET RELOCATION:14000000\BOLO) <KEY> (RETURN\BOX)
OOL> <EMPHASIS>(EXAMINE O\BOLO) <KEY> (RETURN\BOX)
(0) 14000000 123432
OOL> <EMPHASIS>(EXAMINE 1234\BOLD) <KEY> (RETURN\BOX)
(0) 14001234 154323

Load the relocation register with the address of the first location in Data memory (14000000). When
an EXAMINE command with an address of 0 is issued, the loader adds the relocation register to
the address given, resulting in the examination of address 14000000. Likewise, when an EXAMINE
command with an address of 1234 is issued, the loader displays the contents of location 14001234.
The following example shows how to examine a large number of locations in Control memory.
OOL> <EMPHASIS>(SET RELOCATION:16000000\BOLO) <KEY> (RETURN\BOX)
OOL> <EMPHASIS>(EXAMINE O\BOLO) <KEY> (RETURN\BOX)
(C) 16000000 125252
OOL> <EMPHASIS>(EXAMINE 4320\BOLD) <KEY> (RETURN\BOX)
(C) 16004320 125432

The relocation register is loaded with the address of the first location in Control memory (16000000).
When an EXAMINE command is issued with an address of 0, the loader adds the relocation register
to the address given, displaying the contents of address 16000000. Likewise, when the user issues an
EXAMINE command with an address of 4320, the loader displays the contents of location 16004320.
6.2.4.~.6 EXAMINE and DEPOSIT Qualifiers (Switches)

The following list describes the EXAMINE and DEPOSIT qualifiers.
•

/NEXT-Allows an EXAMINE or DEPOSIT command to work on successive addresses. When
used with a valid EXAMINE command, it specifies that after the command location has been
displayed, the loader should also display the next number of locations following the first. For
example, the command E l000/NEXT:5 results in the display of locations 1000, 1002, 1004, 1006,
1010, and 1012 (assuming the default data length is a word). The number of the argument can be
any value in the current default radix that can be contained in 15 binary bits or less. For instance,
if the default radix is octal, the number of the argument can be any value between 1 and 77777.
The /NEXT qualifier works the same way for the DEPOSIT command, except that the data given
with the DEPOSIT command are stored in the location specified and the next number of locations
following.

•

/BYTEIWORDILONG/QUAD-These qualifier switches are used to control the data length of
examined or deposited data. Nonnally, the loader uses the default data length (Section 6.2.4.6.7)
when data is examined or deposited. However, the data length qualifiers can be used to override
the default for a single examine or deposit. For instance, assume the default data length is
currently a word, and a byte quantity at address 16001234 is to be examined. Typing EXAMINE
16001234/Byte IRETURN I would display the proper byte without affecting the default data length.

6-14
OFFLINE DIAGNOSTICS

•

!OCTALIDECIMALIHEX-These qualifier switches can be used with an EXAMINE command
to control the radix of the address and data displayed. They are not used to control the radix of the
address supplied in the EXAMINE command. The radix of the address and data displayed by an
EXAMINE command is usually controlled by the current default radix (Section 6.2.4.6.7), but the
/OCTAL/DECIMAL/HEX qualifiers are used to override the default radix for a single EXAMINE
command. For example, assume the default radix is octal. Typing EXAMINE 14001234!Hex
\ RETURN I displays the contents of address 14001234(8) in the hexadecimal radix. The EXAMINE
display would be as follows: (D) 3OO29C HHHH. HHHH represents the contents (hex) of the
location displayed. The address is also displayed in hex.

•

IINHmIT (abbreviated to /INH)-This qualifier switch inhibits the display of examined data when
repeating an EXAMINE command. This is useful both for saving paper on hardcopy devices and
for speeding up the EXAMINE operation for scope-loop purposes. For example, the command
REPEAT EXAMINE 16012346/INH results in the loader continuously reading the contents of
location 16012346 without displaying anything at the console.

6.2.4.6.7 Setting and Showing Defaults

The SET DEFAULT command is used to change the default radix and/or data length. The default radix
controls the radix of parameters supplied with EXAMINE or DEPOSIT commands and the radix of
data displayed by the EXAMINE command. The default data length controls the length (byte, word,
long, quad) of data displayed by the EXAMINE command or data stored by a DEPOSIT command.
The default radix may be set to octal, decimal, or hexadecimal. When the offline loader first starts, it
sets the default radix to octal. Type Set Default Hex IRETURNI to set the default radix to hexadecimal.
Mter the default radix is set, it remains so until another SET DEFAULT command is issued or the
loader is rebooted.
The default data length may be set to byte, word, longword, or quadword. When the loader is first
started, it sets the default data length to word (16 bits). Type Set Default Long IRETURNI to set the
default data length to longword (32 bits). Setting the default data length to long word causes an
EXAMINE command to display longword quantities and causes the DEPOSIT command to store
longword quantities. (Because the loader is executing in a PDP-II, longwords are stored and retrieved
as two successive I6-bit words.) Mter the default data length is set, it remains so until changed by
another SET DEFAULT command or until the loader is rebooted.
.
6.2.4.6.8 Executing INDIRECT Command Files

The loader is capable of executing indirect command files stored on the load device. These command
files consist of valid offline loader commands terminated by a carriage return «CR» and a line feed
«LF». Comments may also be placed in indirect command files by preceding a comment line with an
exclamation mark (!). Comment lines must also be terminated with a <CR> and <LF>. As an example,
the ofHine loader help file is an indirect command file that contains only comments (Section 6.2.5.2).
Indirect command files cannot be created by the loader or by CRONIC. The command files must be
created in RT-II format and stored on the offline diagnostics diskette. Any editor that does not insert
line numbers in the output files can be used to create command files.

6-15
OFFLINE DIAGNOSTICS

6.2.5 Offline Diagnostics Unexpected Traps and Interrupts
When the loader detects an unexpected trap or interrupt, the following message is displayed:
Unexpected trap through www, VPC=xxx, PSW=yyy
Error Address = zzz

Where:
•

www is the address of the trap or interrupt vector.

•

xxx is the virtual PC of the loader at the time of trap.

•

yyy are the contents of PSW at the time of trap.

•

zzz is the address of the location causing NXM or parity trap.

The first line of the unexpected trap report is issued for all unexpecte.d traps or interrupts. The second
line is issued only if the trap was through vector addresses 000004 (NXM trap) or 000114 (parity trap).
The address of the vector is a direct clue to the cause of the trap. Refer to Section 6.2.5.1 for a list of
the devices and error conditions associated with each vector.
The virtual PC (VPC) of the instruction executing when the trap occurs is sometimes useful in
determining the cause of the trap. The VPC can be referenced in the listing to find the instruction
causing the trap. Remember, the VPC is the address of the instruction following the instruction
executing when the trap occurred. Notify field service support to analyze such failures.
NXM traps can be caused by EXAMINE or DEPOSIT commands if an address not contained in a
particular HSC is specified. For example, if an HSC contains only Data memory from addresses
14000000 through 14177776, and an examine or deposit is tried for address 14200000, the loader
reports an NXivl trap. In this example, the NXM: trap would not represent an error condition.
Parity traps can be caused by an EXAMINE command if a user examines an address not initialized
with good parity. For example, when the HSC memories are powered on, the parity bits are in random
states. Thus, if a user examines a location not written since poweron, the location may generate a
parity error. This does not constitute an error condition.
However, if a location produces a parity error and that location has been written since poweron, a
memory error is indicated.
NOTE

The I/O Control Processor and Ks have bits allowing them t.o write bad parity for testing the
parity circuit. These bits should never be used except by diagnostics.
6.2.5.1 Trap and Interrupt Vectors

Following is a list of trap and interrupt vectors for various devices and error conditions recognized by
the I/O Control Processor PDP-II processor.

6:-16
OFFLINE DIAGNOSTICS

Vector

Device or Error Condition

000004

Nonexistent memory, stack overflow, halt in user mode, and odd address trap

000010

Illegal instruction

000014

BPT instruction

000020

lOT instruction

000024

Power fail interrupt

000030

EMf instruction

000034

TRAP instruction

000060

Console terminal-receiver interrupt

000064

Console terminal-transmitter interrupt

000100

Line clock interrupt

000114

Parity trap

000120

Control bus interrupt-level 4

000124

Control bus interrupt-level 5

000130

Control bus interrupt-level 6

000134

Control bus interrupt-level 7

000230

RX33 interrupt

000250

MlvIU abort (trap)

000300

SLU (Serial Line Unit) #1, receiver interrupt

000304

SLU (Serial line Unit) #1, transmitter interrupt

000314

SLU (Serial line Unit) #2, receiver interrupt

000310

SLU (Serial line Unit) #2, transmitter interrupt

~17

OFFLINE DIAGNOSTICS

6.2.5.2 Help File
An example of the offline diagnostics loader help file follows.
!HSC70 OFL Diagnostic Loader Help File -- Vnn-nn
!Capital letters = required input, lower case = optional
'COMMANDS (terminated by CR):
'Examine <address>'
;display data at <address> specified
'Deposit <address> <data>'
;deposit <data> to <address>
<address>
digit string in current default radix or:
'*'
use same address as last Ex or De
,+,
use address following last address
'-'
use address preceding last address
'@'
use <data> from last Ex or De as <address>
;HElp'
;print this file
'@filename'
;execute indirect command file
'Load filename'
;load file to diagnostic partition
'REpeat <command>'
;repeat specified command until AC
'SEt Default <option>'
;set default radix or data length
<option> = Byte,Word,Long,Quad,Hex,Octal,Decimal
'SEt Relocation:i'
;set relocation register to t
NOTE:

Relocation register is 22-bit positive
of all EXAMINE and DEPOSIT commands.

, SHow'
, SIze'
, Start'
'Test Bus'
'Test MEmory'
'Test MEmory By K'
; Test K'
'Test OCP'
'Test Refresh'

t added to address

;display defaults and Loader version t
;Size HSC70 memories and display K status
;start program in diagnostic partition
;load and start the OFL Bus Test
;load and start the OFL Memory Test
;load and start the OFL K/P Memory Test
; load and start the OFL K Test Selector
; load and -start -the OFLOCP Test
; load and start the OFL Memory Refresh
Test

QUALIFIERS (switches) for 'Ex' and 'De'
'/Next:t'
;repeat Ex or De on next 't' addresses
'/Byte,/Word,/Long,/Quad'
;use specified length vs. default
'/Octal,/Decimal,/Hex'
;use specified radix for Examine display
'/INHibit'
;inhibit display of examined data
< end of help file >

6.3 OFFLINE DIAGNOSTIC WCS LOADER
The wes command loads and executes the offline K wes Control Store loader. This loader is used to
load a WeS-compatible module with functional microcode. When using the K.si data channel module,
this command is used to configure the K.si as a disk or tape data channel.

6.3.1 Offline K WCS Loader
The offline K wes loader allows the HSe to load on the boot media any module with a loadable
wes control store area with program information from a .wes file. When using the K.si, the program
information is used to load the microcode required to make the K.si function as a K.sdi or K.sti data
channel. The K.si is currently the only module that uses the K wes loader functions.

6-18
OFFLINE DIAGNOSTICS

6.3.2 Offline Diagnostic WCS Loader System Requirements
The following is a list of hardware required to run the offline diagnostic WCS loader.
•

I/O Control Processor module with HSC Boot ROMs

•

At least one memory module

•

Working Control and Data memories

•

RX33 controller with at least one working drive
or

•

TU58 with at least one working drive

•

Omine K WCS loader media

•

Terminal connected to I/O Control Processor console interface

•

One or more disk or tape data channel modules

6.3.3 Offline Diagnostic WCS Loader Operating Instructions
Refer to Section 6.1.2, Section 6.1.3, and Section 6.2 if the HSC is not booted and loaded with the
offline boot media. The diagnostic loader prompt ODL> should be displayed. The following steps
describe how to start the offline K WCS loader.
1.

At the ODL> prompt, type WCS IRETURNl

2. The load device drlve-in-use LED lights as the WCS loader is loaded.
3. The WCS loader indicates it has been properly loaded by displaying the following:
HSC OFL Control Store Loader

4. The WCS loader then prompts for parameters.
6.3.3.1 Parameters
This section provides detailed information on entering test parameters for the offline K WCS loader.
Items in square brackets are the default value for each particular prompt. If no default exists, the
brackets are empty.
NOTE

Typing a ICTRuel aborts the WCS loader and returns the HSC to the ODL> prompt.
The offline K WCS loader first prompts for the list of requestors to load
List of requestors to load (0-9, ••• )

[]

This question may be answered with single requestor number, a series of requestor numbers delimited
with commas (2,4,8), or with a single wild card character (*).
When using multiple requestor numbers delimited with commas, the WCS loader attempts to load all
the listed requestor numbers with the desired WCS code. When using the wild card character, the WCS
loader attempts to load all requestors.

If a particular requestor fails or is unable to load WCS code, an error message will be displayed and
the WCS loader will attempt to load the remaining requestors.
The WCS loader then prompts:
WCS file to use [KDISK.WCS] ?
of(

[F-A PE . ~t5]

6-19

OFFLINE DIAGNOSTICS

This question should be answered with the file name of the WCS image to be loaded into the requestors
that were listed in response to the first WCS loader prompt. An error is displayed if the file name does
not conform to standard file name specification formats. The default is KDISK.WCS, which is the code
to be loaded to configure the requestor as a disk data channel (K.sdi). To configure the requestor as a
tape data channel (K.sti), the file name KTAPE.WCS must be specified.
The WCS loader then commences to load the specified requestors. The WCS loader reports requestors
that do not accept WCS code loading and continues loading remaining requestors. When all specified
requestors have been loaded, the WCS loader prompts:
Load other requestors (YIN)

[N] ?

The default is N and when the default is taken, the system returns to the ODL> prompt. Typing Y

IRETURN I causes the WCS load to prompt with the list of requestors question.

6.4 OFFLINE CACHE TEST
The offline cache test is a diagnostic which runs under the offline loader in a stand-alone environment.
It provides indepth testing of the cache logic on the Jl1 P.ioj, and verifies the full functionality of the
on board cache. Execution time for a single pass is between 16 seconds and 4 minutes, depending on
the options selected.

6.4.1 Offline Cache Test System Requirements
The offline cache test is loaded into memory via the offline loader. This test requires 8 K words of
memory to run. One-half of this memory space contains the program; the other half is used as a
cached buffer. All terminal I/O and handling of the line clock is done by the offline loader.

6.4.2 Offline Cache Test Operating Instructions
This section contains operating instructions specific to the offline cache test. If the HSC70 is not
booted and running the offline loader, necessary instructions are found in Section 6.1.2, Section 6.1.3,
and Section 6.2. If the HSC70 is already booted and running the offline ioader, enter the TEST
CACHE IRETURN I command at the ODL> prompt.
This command loads the offline cache test from the media and transfers control to the diagnostic.
When it starts, the offline cache test should display the following:
HSC OFFLINE Cache Test

Vxxx

Where V xxx is a three-digit version/edit number.
User-modifiable parameters are described in Section 6.4.3.

6.4.3 Offline Cache Test Parameter Entry
Followin are the three user-modifiable parameters for the cache test. In each case the default, invoked
by a RETURN, is shown in brackets. If no default is possible, the brackets are empty.
•

Select Data Reliability test-This is the first user-modifiable parameter, an optional selection of
the data reliability tests. It is a moving-inversions style test for exercising the RAM array. The
offline cache test prints:
Run extended cache ram test (YIN)

[N]?

Selection of this optional test increases test time per pass to about four minutes. It is useful for the
manufacturing burn-in and test areas. It is not necessary to run this optional test in order to fully
verify the health of the cache.

6-20
OFFLINE DIAGNOSTICS

•

Leave Cache Enabled-Determines the cache state at the termination of the diagnostic. The
offline cache test prints out:
Leave cache enabled after successful completion (YIN)

[N] ?

This feature allows enabling the cache for further use after running the diagnostic to verify the
cache is working. If the diagnostic detects any hard failures in the cache, it is not enabled at
the end of the diagnostic. This prevents complications if the cache contains hard failures and is
inadvertently turned on.
•

Number of Passes-Accepts a total number of passes from 1 to 32767 (decimal). The test prompts
for this number as follows:
t of passes to perform (D) [D] ?
Any decimal number up to 32767 can be used. Fatal errors can cause the diagnostic to terminate
before the specified number of passes executes.

At the completion of the total passes requested by the user, the diagnostic prompts:
reuse parameters (YIN)

[Yl ?

Answering this prompt with a Y allows the diagnostic to be rerun with the same parameters as before.
Answering with an N causes repetition of the parameter entry questions.

6.4.4 Offline Cache Test Progress Reports
The offline cache test provides summary information at the end of each pass. The end of pass message
is similar to the following:
End of Pass 00001, 00000 Errors, 00000 Total Errors

The errors field contains the number of errors for the pass. The total errors field contains a running
total of errors accumulated since the start of the diagnostic.

6.4.5 Offline Cache Test Error Information
The offline cache test displays the errors detected during execution on the console tenninaI. All
error messages follow the diagnostics generic error message format (Section 6.1.5) preceded by an
OFLCXT> prompt.
Each error number has a unique text string associated with it. For errors with results that did not
compare with the expected value, the diagnostic uses the optional lines to show EXPected/ACTual
data.
Soft errors (such as cache parity errors) can accumulate to a point where the diagnostic classes them as
fatal. The test then terminates on a fatal error.
6.4.5.1 Specific Offline Cache Error Messages
The following list describes in detail each possible error message. The errors are listed in numerical
order.

•

Error 00, memory parity error, VPC = xxxxxx-Applicable to all tests. Can occur at any time
during execution of the diagnostic. The virtual PC on the stack is printed to help identify the
program area where the error occurred. The content of the error address register also is displayed.
Both the virtual PC and the error address register content are optional lines. Detection of this error
causes the testing to cease. Then the diagnostic returns to the Reuse parameters prompt.

~21

OFFLINE DIAGNOSTICS

•

Error 01, NXM trap, VPC = xxxxxx-Applicable to all tests. Causes the diagnostic to return
to the Reuse parameters prompt. Additional data (such as the virtual PC of the instruction which
caused the trap and the physical address co.p.tained in the error address register) are printed as
optional lines.

•

Error 02, Cache parity error, VPC = xxxxxx-Applicable to tests 2 through 16. Results when a
trap through the parity error vector is detected and the cache is enabled. The virtual PC where the
error was detected is printed, as well as the content of the error address register. If the 22-bit value
in the error address register is 177770024, no main memory error was present. Assume the parity
error is from the cache.

•

Error 03, bit stuck in cache control register-Applicable to test 2. Indicates a bit is stuck-atfault in the cache control register. The EXPected and ACTual data values are printed as optional
lines.

•

Error 04, forced miss operation failed-Applicable to test 3. Bit 2 of the cache control register
does not prevent the cache from allocating a test location. This could be a problem in the cache
control gate array or in the hit/miss compare logic.

•

Error OS, forced miss with abort failed-Applicable to test 3. Bit 3 did not prevent the cache
from allocating when set. Failures of this nature mean the cache cannot be disabled, and all
memory references may be allocating cache regardless of the intent of the code .being executed.
The cache control gate array or the tag compare logic may be at fault.

•

Error 06, expected cache hit did not occur-Applicable to tests 4, 6, 9, 12, and 14. Did not
allocate a given test location to the cache as expected, causing a miss condition in the hit/miss
register.

•

Error 07, expected cache miss did not occur-Applicable to tests 7, 9, and 10. Shows a test
location not expected to be allocated, or valid, as a hit on access.

•

Error 10, value in hit/miss register incorrect-Applicable to test 5. Indicates the six-bit value in
the hit/miss register was incorrect after a certain sequence of instructions. The expected values, as
well as the actual content of the hit/miss register, are printed as optional lines.

•

Error 11, write byte operation caused cache update-Applicable to test 6. A byte operation (on
a miss) did not cause cache to deallocate the test location. Thus, when the test location was read
back, a cache hit resulted.

•

Error 12, write byte did not cause cache update-Applicable to test 6. A byte-value did not get
written into cache or main memory.

•

Error 13, cache failed to flush successfully-Applicable to test 8. When checking cache after a
flush command was executed, one or more locations still contained valid data (were detected as
cache hits).

•

Error 14, access with force bypass did not cause invalidate-Applicable to test 9. The second
access to an allocated location, with the force bypass bit (bit 9) set in the control register, did not
result in a miss as expected..

•

Error IS, tag parity error did not set-Applicable to test 10. The diagnostic could not set the
tag parity error bit in the memory system error register when faced with an actual tag parity error.

•

Error 16, abort on cache parity error did not occur-Applicable to test 11. The cache logic did
not abort the instruction under execution when a cache parity error was forced, and the abort bit
(bit 7) was set in the control register.

•

Error 17, unexpected parity trap during abort test-Applicable to test 10. Although expected
to, cache control bit 0 did not prevent the cache logic from taking a trap on bad parity. The address
where the trap occurred is printed as optional information.

6-22
OFFLINE DIAGNOSTICS

•

Error 20, content of memory system error register incorrect-Applicable to test 11. The error
bits in the memory system error register (1777744) do not reflect the correct status for the operation
under test. The EXPected and ACTual content are printed as optional lines.

•

Error 21, return PC wrong during abort/interrupt test-Applicable to test t t. The return PC
on the stack is not equal to the value expected during an abort or interrupt operation caused by a
cache parity error. The state sequencer gate array is most likely defective.

•

Error 22, cache data parity bit(s) did not set-Applicable to test 10. The diagnostic was unable
to set the data parity error bit(s) in the memory system error register on a forced parity error.
The parity logic may not be detecting parity errors or one of the bits in the memory system error
register may be stuck low.

•

Error 23, interrupt on parity error did not occur-Applicable to test 11. The cache did not
interrupt through vector 114 on a forced parity error. The state sequencer or the parity detection
logic may be faulty.

•

Error 24, expected NXM trap did not occur-Applicable to test 13. A NXM trap was not
detected during an access to location 1777757776. The timeout logic that detects a NXM may be
defective, or some problem may exist in the cache data path gate array that prevents it from acting
on timeout.

•

Error 25, parity error was not blocked by NXM-Applicable to test 13. When accessing a
location expected to result in a NXM, the parity error flag set instead, and a trap occurred through
vector 114. The NXM signal may not have been detected by the cache data path gate array.
Error 26, cache data miscompare on word operation-Applicable to test 14. A word address
in the cache array did not have the correct data when read. This may indicate address line faults
or data path faults allowing the location to be rewritten after the test value was placed there. The
EXPected!ACTual data values are printed as optional lines.

•

Error 27, cache data miscompare on byte operation-Applicable to tests 14 and 15. A location
in the cache, when addressed in a byte fashion, did not have the EXPected data pattern. This may
indicate address line faults or data path control faults which allowed overwriting the EXPected
value.

•

Error 30, DMA write to memory did not cause cache to invalidate-Applicable to test 12. A
OMA write by the RX33 controller to a test location, allocated to cache, still resulted in a hit status
after the transfer. The cache has stale data.

•

Error 31, instruction still completed during abort condition-AppI"icable to test 11. With the
abort bit set in the cache control register, an instruction set up to detect a parity error on an operand
fetch still finished execution modifying the destination of the instruction.

•

Error 32, load device error during DMA test-Applicable to test 12. The load device subsystem
did not respond correctly to the OMA test operation. There may be faults in the load device
controller or the interrupt service logic. This message is informational in nature, and this error is
outside the scope of this diagnostic.

•

Error 33, PDR cache bypass failed-Applicable to test 7. Setting the POR bypass bit in the
PAR/POR pair under test did not bypass the cache. This points to a MMU or cache data path gate
array problem. The POR number and the CPU execution mode (Kernel or User) are printed as
optional lines in the error message.

•

Error 34, tag store address hit failure-Applicable to test 16. Changing the value of the tag bits
(bit~ 16:22 of the physical address) still resulted in a hit condition (even though the address should
not have compared) forcing a fetch to main memory. There may be a problem in the tag RAMs or
the tag compare logic in the cache data path is not working.

6-23
OFFLINE DIAGNOSTICS

•

Error 35, tag store address miss failure--Applicable to test 16. When going through the possible
values for the tag bits (16:22 of the physical address), the cache failed to allocate for some
combination of the bits. Possible problems are stuck bits in the address lines going to the cache
array, bad RAMs in the cache array, or a fault in the tag compare logic.

•

Error 41, processor type is not JII-Applicable to test 1. The processor type register does not
show the correct value for a J11 chip set. Attempting to run this diagnostic on anything other than
a J 11 produces this error.

6.4.6 Offline Cache Test Troubleshooting
All of the logic under test is contained on the J11 (P.ioj) module with the exception of the memory
used by the diagnostic. Main memory parity errors usually point to the memory module. Because
much of the logic tested is buried within the two gate arrays on the module, troubleshooting is often
limited to a best-guess replacement of one or both of these gate arrays.
Cache parity errors and data miscompare errors can usually be traced to specific RAMs if proper
attention is paid to the data content and address.
For scope loops, the cache test 'should be run with a large number of passes, and a ICTRuol typed on
the console to inhibit error message printout.
Constant hit/miss errors, or tag address hit problems, also may be caused by the tag compare logic,
which is separate from the gate arrays and the data path.

6.4.7 Offline Cache Test Descriptions
Following are descriptions of the Offline Cache tests 1 through 16.
•

Test 1, cache register access test--Checks for the presence of the necessary cache controVstatus
registers, the cache control register (17777746), the hit/miss register (17777752), and the memory
system error register (17777744). To perfonn further diagnosis, these registers must respond.

Test 2,' cache control register bits-Tests the read/write bits of the cache control register
(17777746) for stuck-at faults. In addition, bits (8,11: 15), which are write-only, are checked
for read data of O. Bits 6 and 10 which cause data and tag parity to be written incorrectly on new
data allocated to cache are treated as special cases. Mter writing/reading each of these bits, the'
cache is flushed to remove any bad parity locations.

•

Test 3, force miss action-Verifies all references made with either bit 3 or bit 2 of the cache
control register set that cause a cache miss and leave the cache entry unchanged. To perform this
test, first write a test address with bits 3:2 cleared to allocate cache and place a known data pattern
into the cache. Then bit 2 is set, and the same test location is written again. With bit 2 set, the
cache will not update, and the data in cache is still considered valid. When bit 2 is cleared and the
test location is accessed again, the old data from cache should be the result. If not, the force miss
action of bit 2 did not work. The same sequence is repeated for bit 3, and the same results are
expected.

•

Test 4, hit/miss register, part I-Checks the basic operation of the hit/miss register in logging
hit/miss information on instruction fetches and data reads/writes. The hit/miss register is critical to
further cache diagnosis because it is the window into what is actually going on inside the cache.
First, a test location is allocated with cache enabled. Then cache is bypassed, and the test location
is accessed again by a write. This write should go directly to main memory and bypass the cache.
The cache is enabled, and a read access to the test location should result in a hit condition in the
hit/miss register. Then the test location offset by 8 K words is accessed. This should result in a
miss, since the upper bits of the address (tag) will not match.

6-24
OFFLINE DIAGNOSTICS

•

Test 5, hit/miss register, part II-Checks all the combinations of the six bits in the hit/miss
register for a single miss at different bit positions. This is done by caching a certain sequence of
instructions and executing them, with miss conditions forced at each bit position. At the completion
of this test the hit/miss register has been checked for both 1s and Os at each bit position.

•

Test 6, byte accesses-Ensures byte references to the cache are handled correctly by the control
logic. The first operation is a write byte to the test location not allocated followed by a byte-read
of the test location. The read should result in a miss. Then the entire word at the test location is
allocated. The upper byte of the test location is modified, and a cache hit is expected. The entire
word also is read and compared against the expected result to see if the byte-write occurred. A
similar chain of events follows, this time modifying the low byte.

•

Test 7, PDR cache bypass test-Tests all of the Kernel PORs <0:7> as well as the User
PORs. It is very important for the bypass cache bit (bit 15 of any POR) to work correctly in
the multiprocessing environment of the HSC70.
To test PDR bypass, select from a table the PAR/pDR pair to test. This POR is remapped to
point to Control memory. Control memory is then written via the MMU writing a data pattern
and allocating cache. Control memory windows are used to write Control memory to a second
pattern without involving the cache control logic. When Control memory is read through the MMU
with the bypass bit set, the actual Control memory content (second pattern) should be the result if
the bypass bit is actually set. If the old content (first pattern) is read back, the bypass bit is not
working. PARs 1, 2, 3, 5, and 6 are tested in this way.
PARs 0, 4, and 7 are treated as special cases due to programming environment restrictions. They
are tested by allocating cache with some location mapped by the PAR/pOR under test and then
setting the bypass bit. When the test location is read, the hit/miss register should record a hit and
then invalidate the location. If the location is written or read again, it should result in a miss as
long as the bypass bit is set.
Mter all the Kernel PAR/POR registers are tested, the program maps user space identical to Kernel
space and switches into user mode to re-execute all the tests. After all User PAR/POR pairs have
been tested, the program swaps back into Kernel mode and proceeds to the next test.

•

Test 8, cache 8ush action-Allocates all 4 Kwords of cache. and then executes a flush command
by setting bit 8 in the cache control register. The cache control logic then writes every location
in cache with the data value 17777746 and resets the valid bit for each location. All 4 Kwords of
cache allocated before the flush are read again, and if any location responds with a hit when read,
an error is declared.

•

Test 9, unconditional bypass to main memory-Checks the correct operation of bit 9 of the
cache control register. Bit 9 is used to bypass cache in a fashion similar to the bypass bits in the
PAR/PORs. Any location allocated in cache before the bypass bit is set results in a hit on the first
access, and further accesses all show as misses.
This function is used when it is desirable to temporarily disable the cache in a fashion that does not
leave the cache with stale data when re-enabled. A test location is allocated, and then the bypass
bit is set. The first access of the test location should be a hit, and the second should be a miss.

•

Test 10, force tag/data parity errors-Forces parity errors in the tag and data fields of the cache
array to test the parity detection logic. A special diagnostic mode is used, with bit 0 of the cache
control register and one of the force parity error bits set. When bit 0 is set, any trap through 114 is
disabled on a parity error detected in cache. If a parity trap does occur, an error is declared.
First, tag errors are forced using bit lOin the cache control register. When this bit is set, locations
allocated to cache do so with bad tag parity. When accessed again (resulting in a cache hit), they
should set the tag parity error bit (bit 5 in the memory system error register). The force data parity
error bit (bit 6 of the cache control register) is checked next. After a location is allocated to cache
with bad data parity, further reads of that location result in setting the data parity error bits (bits 6:7

6-25
OFFLINE DIAGNOSTICS

of the memory system error register). After using the force bad parity bits, the program flushes the
cache to remove these parity errors.
•

Test 11, abort/interrupt on parity errors-Uses the force parity error bits in the cache control
register to force parity errors in the cache array. Because testing of the detection of such errors has
been done, testing of the other logic related to cache data or tag parity errors can be done.
Different combinations of tag and parity errors are forced, with the cache control register set to
interrupt through 114, or abort through 114 on parity errors. An interrupt through 114 should set
the correct error bit(s) in the memory system error register. Also, the instruction detecting the
parity error should complete.
On an abort through 114, the correct error bit(s) should be set, but the instruction should not
complete. IT the parity error is detected on the fetch of the source data, the data in the destination
of the instruction is not modified. The PC on the stack after each interrupt or abort instruction is
checked against the PC that is expected.

•

Test 12, DMA invalidate-Modifies a location resulting in the cache acquiring stale data unless
cache logic detects the DMA change. The RX33/M.std1 subsystem is used to generate DMA
operations to Program memory. A DMA write to a Program memory location allocated to cache
should result in a cache miss when it accesses after the DMA write.
Test 13, check blockage of parity error on NXM abort-Generates simultaneous NXM and
parity errors. The NXM trap should occur overriding the parity error.

•

Test 14, cache data RAM test-Tests the cache data RAMs by mapping one PAR and using the
cache solely for data storage. A data pattern to detect dual-addressing is written to the cache.
Failures of the cache data to match the EXPected data on read-back are considered miscompare
errors. The test is first done using word addresses and test values, and then repeated with byte
addr-esses -and byte data patterns. Each location allocated is expected to be a hit from cache, and
the content is checked as well.

•

Test 15, tag store RAM test-Checks the tag bits of the cache array for dual address errors and
stuck-at faults. With the cache flushed and completely deallocated, the first 256 locations of the
cache are written with a unique data value in each address. Then the entire cache is read. Only the
256 locations written should be cache hits, and only these locations should have the EXPected data
pattern. Then the upper address bits are changed so a new combination of tag bits results. This
test is repeated 15 times until all of the tag bits have been tested.

•

Test 16, data RAM reliability test-Performs a modified moving inversions test on the cache data
RAM array. Due to the geometry of the data RAMs, every fourth bit is done concurrently to save
time. This results in using the same pattern in both nibbles of the data word. This test must be
selected by the user as it does not normally run by default. About four minutes are required to
complete one pass of this test.

6.5 OFFLINE BUS INTERACTION TEST
The offline bus interaction test creates Control and Data bus contention among the requestors in the
HSC subsystem. The contention is generated by simultaneously testing different portions of the same
memory (Control and/or Data) from different requestors. In the process of testing the memories, the
various requestors in the subsystem contend with each other for the use of the Control and Data buses.
In addition to the bus contention generated by the requestors, I/O Control Processor interaction can be

selected with the Program, Control, and Data memories, with the OCP, and/or with the load device. IT
I/O Control Processor interaction is selected, it occurs simultaneously with the bus contention generated
by the requestors.

6--26
OFFLINE DIAGNOSTICS

This test requires a minimum of two working requestors in order to operate and uses a maximum of
nine requestors if they are available. The more requestors available for use by this test, the greater
the amount of bus contention. A larger number of requestors makes it easier to isolate failures to
a particular source. Also, the run time of this test increases linearly as the number of requestors is
increased.
IT the bus interaction test fails, it must first be determined if the failure was caused by an interaction
problem. This is determined by rwming the offline KIP memory test (test memory by K). When the
test prompts for parameters, specify the requestor number of the requestor that detected the failure in
the bus interaction test. Also specify the same starting and ending addresses displayed with the error
report from the bus interaction test. H the requestor also fails the offline KIP memory test, the original
problem was not an interaction problem. The problem should be localized in the same manner as any
ordinary memory failure.

6.5.1 Offline Bus Interaction Test System Requirements
Hardware required to run this test is shown in the following list.
•

I/O Control Processor module with HSC boot ROMs

•

At least one memory module

•

Working Control and Data memories

•

Load device with at least one working drive

•

Terminal connected to I/O Control Processor console interface
At least two working requestors (K.sdi, K.sti, or K.ci)

6.5.2 Offline Bus Interaction Test Prerequisites
Booting procedures and testing through successful loading of the offline diagnostic loader program is
described in Section 6.1.2, Section 6.1.3, and Section 6.2.
Due to the sequence of tests that precede the memory test, the bus interaction test assumes the I/O
Control Processor module and the load device are tested and working. This test also assumes the
Control and Data memories were previously tested with the offline memory test or the offline KIP
memory test, and are working.

6.5.3 Offline Bus Interaction Test Operating Instructions
At the loader prompt ODL>, the operator types the TEST BUS command and the offline bus interaction
test is loaded and started. The test indicates it has been loaded properly by displaying the following:
HSC OFL Bus Interaction Test

The test then sizes the Program, Control, and Data memories and determines the number of requestors
available for testing.

6-27

OFFLINE DIAGNOSTICS

6.5.4 Offline Bus Interaction Test Parameter Entry
After displaying the progiam name and version. the Program, Control, and Data memories are sized.
The bounds of each memory are displayed on the terminal.
NOTE

For any of the bus interaction test prompts, use the DELete key to delete mistyped parameters
before IRETURNI is typed. If an error in a parameter already terminated with /RETURNI is noted,
type a ICTRucl to return to the offline loader. Then type START IRETURNL to restart the test from
the beginning.
The test prompts for selection of the requestors used for the test, as follows:
[Y) ?

Use requestor #001, K.ci (YIN)

Answer with a IRETURNI (or Y IRETURND if the K.ci should be used. Answer with N IRETURNI if the K.ci
should not be used.
At least two working requestors must be used to run the bus contention test because one requestor
cannot generate bus contention by itself. The program displays the following error message if less than
two requestors remain after the requestors which should be used have been indicated.
Not Enough Ks Available for Test

Next, the program prompts for the type of I/O Control Processor interaction desired.
P.ioj Memory Interaction desired (YIN)

[Y) ?

Answer the projPt Wi, a IRETURN/ if I/O Control Processor interaction with memory is wanted.
Answer with N RETURN if I/O Control Processor interaction with memory is not wanted. If the prompt
is answered with an N, the following three prompts are skipped. IT the prompt is answered with a
{RETURN), the following prompts are displayed:
Interact with Program memory (YIN) [Y) ?
Interact with Control memory (YIN) [Y] ?
Interact with Data memory (YIN) [Y) ?

For each prompt, answer with a lRETURN I if I/O Control Processor is to interact with the specified
m,mory wiile the requestors are generating contention on the Control and Data buses. Answer with
N RETURN if the I/O Control Processor is not to interact with the specified memory. (IT I/O Control
Processor interaction is selected, the I/O Control Processor interacts with the memory at the same time
the requestors are generating Control and Data bus contention.) The program next prompts for OCP
interaction.
OCP Interaction Desired (YIN)

[Y] ?

IT I/O Control Processor interaction with the OCP is wanted, answer with IRETURN!. If OCP interaction
is not wanted, answer with N IRETURN L The test then prompts for load device interaction.
Interact with load device (YIN)

[Y] ?

If I/O Control Processor interaction with the load device is wanted, answer with I RETURN L If such

interaction is not wanted, answer with N /RETURNL The program then prompts:
Number of passes to perform (D)

[1] ?

Enter a decimal number between 1 and 2,147,483,647 (Omittirg cOlas) to specify the number of
times the bus interaction test should be repeated. (Entering 0 RETURN or just I RETURN l causes one pass
of the test.) After the number, of pasjes is entered, the bus contention test begins. The test can be
aborted at any time by typing CTRUC. (The test may continue running for a few seconds after ICTRucl
is typed.)
After the specified number of passes is completed, the following prompt is issued:
Reuse parameters (YIN)

[Y] ?

6-28
OFFLINE DIAGNOSTICS

To repeat the last test specified using the parameters, answer this prompt with IRETURNI or Y IRETURN!.
To cause the test to prompt for new parameters, answer the prompt with N IRETURNI, Answering the
prompt with ICTRucl returns control to the offline loader.

6.5.5 Offline Bus Interaction Test Progress Reports
Each time the program completes one full set of bus contention tests, an end of pass report is displayed.
A pass consists of completing a full set of contention tests, including: Control bus tests, Data bus tests,
and combined Control and Data bus tests. The end of pass message is displayed as follows:
End of Pass nnnnnn, xxxxxx errors, yyyyyy total errors.

Where:
•

nnnnnn is the decimal count of the number of passes completed.

•

xxxxxx is the decimal count of the number of errors detected on the current pass.

•

yyyyyy is the decimal count of the total number of errors detected since the test was initiated.

6.5.6 Offline Bus Interaction Test Error Information
All error messages produced by this test conform to the generic diagnostic error message format
(Section 6.1.5). Following is a typical bus interaction test error message.
OBIT>hh:mm Ttaaa Etbbb U-OOO
Memory Test Error
Detected By K.sdi, requestor 006
MA -xxxxxxxx

EXP-yyyyyy
ACT-zzzzzz
< K-error-Summary-Info >
Memory Test Configuration:
K.ci , requestor 001, M.ct1 16000700
K.sdi ,requestor 006, M.ctl 16100300

16100274
16177674

Where:
•

hh is the hours since the offline loader was last booted.

•

nun is the minutes since the offline loader was last booted.

•

aaa is the decimal number denoting the test.

•

bbb is the decimal number denoting the error detected.

•

xxxxxxxx is the address of the location causing the error.

•

yyyyyy is the data that was EXPected.

•

zzzzzz is the data that was ACTually found.
< K-Error-Summary-Info >
Memory Test Configuration

= Refer to Section 6.5.6.1
Refer to Section 6.5.6.2

6-29
OFFLINE DIAGNOSTICS

6.5.6.1 Requestor Error Summary
When the requestor reports a memory test failure to the I/O Control Processor, the following
information is suppiied:

1. Address of the failing memory location
2. Data EXPected and data ACTually found
3. Error summary information
The error summary information is supplied as a three-bit field, including:
1. A bit indicating a parity error occurred while reading the location.
2. A bit indicating an NXM error occurred while accessing the location.
3. A bit indicating a Control bus (CBUS) error occurred while accessing the location.
When a memory error report is issued for an error detected by the requestor, the last line of the error
report includes a list of the error summary bits that were set (if any).
A Control bus (CBUS) error indicates the requestor asserted an illegal combination of the three
CCYCLE lines when accessing Control memory. Because these lines were previously tested from the
I/O Control Processor (in the OFL P.ioj/c test), a Control bus error is probably caused by a problem
with the requestor's drivers that assert the CCYCLE lines.
6.5.6.2 Memory Test Configuration
The memory test configuration lists each requestor being used for bus interaction tests along with the
section of memory each requestor was testing when the failure occurred. The configuration information
consists of:

1. Type of requestor (K.d, K.sdi, K.sti, or K.si) and the requestor number
2.

Memory being tested by the requestor (M.cd = Control memory, M.data = Data memory)

3. First address of the chunk of memory being tested
4. Last address of th.e chun.". of memory being tested
6.5.6.3 Error Messages
The following list describes the nature of the failure indicated by each error number.

Error 000, memory test error~Indicates one of the requestors detected a memory error in the
Control or Data memories. The following is a sample error report.
Memory Test Error
Detected by K.ci, requestor 001
MA -16010234
EXP-000177
ACT-000377
Parity error
Memory Test Configuration:
K.ci ,requestor 001, M.ctl 16000700 -- 16100274
K.sdi ,requestor 007, M.ctl 16100300 -- 16177674

Where:
•

MA is the 22-bit address of the failing location.

•

EXP is the data pattern EXPected by the requestor.
ACT is the data pattern found by the requestor. .

•

Memory Test Configuration are the other requestors that enabled when failure occurred.

6-30
OFFLINE DIAGNOSTICS

This sample error report indicates the K.sdi detected a memory parity error while reading address
16010234 of Control memory (M.ctl). The requestor expected to find the value 000177 in the
location but instead found the value 000377. At the time the error occurred, the K.ci in requestor 1
was testing addresses 16000700 through 16100274 of Control memory, and the K.sdi in requestor
7 was testing addresses 16100300 through 16177674 of the Control memory.
•

Error 001, K timed-out during Init-Displayed when a requestor fails to complete its Init
sequence in time. This error usually indicates the specified requestor failed one of its internal
microdiagnostics. A sample error report follows.
K Timed-out During Init
K.ci , requestor 001, status = 104
Other Ks Enabled:
K.sdi, requestor 6
K.sdi, requestor 7

This sample error report indicates the K.ci in requestor 1 did not finish its initialization diagnostics
in the required time. The requestor status displayed with the error report indicates the requestor
failed test 4 of its microdiagnostics (lxx in status = failed test xx). Two other requestors were
enabled at the time the requestor K.ci timed out. (One of these requestors may be responsible for
K.ci time-out.)
When the I/O Control Processor enables the requestor to perform the memory test, the requestor
begins its initialization sequence (which includes executing certain microdiagnostics). At the end of
the requestor's lnit sequence, the requestor indicates it found the K Control Area by complementing
a pointer word in Control memory. If the requestor fails to complement this pointer word within
50 milliseconds (4.2 seconds for the K.ci) of being enabled, error 001 is reported. The contents of
the K status register are displayed with the error report.
Error 002, K timed-out during test-Indicates the specified requestor failed to complete its
memory test within the expected time. A sample error report follows.
K Timed-out During Test
K.sdi, requestor 007, Status = 002
Memory Test Configuration:
K.ci , requestor 1, M.ctl 16000700 -- 16100274
K.sdi, requestor 7, M.ctl 16100300 -- 16177674

The sample error report indicates the K.sdi in requestor 7 never completed the memory test it was
assigned. (Ks are allowed up to one minute to complete a memory test.) The memory configuration
displayed with the error report shows all Ks testing at the same time the K.ci timed-out. In this
example, the K.ci in requestor 1 was also testing at the time the K.sdi timed-out.
Test time-out failures may be caused by a failure in the requestor that timed-out. They may also be
caused by a failure in one of the other requestors that was testing at the same time.
•

Error 003, parity trap-Indicates the I/O Control Processor detected a parity error. The 22-bit
address of the location causing the error is displayed as the MA data in the error report, where:

•

MA is the address causing the parity trap .

•

VPC is the Virtual PC of the memory test at the time the trap occurred. Reference this address
in the listing to locate the area of the test where the error occurred.

The data is lost when a parity trap occurs so no EXPected or ACTual data can be displayed.
•

Error 004, NXM trap-Indicates the I/O Control Processor detected a Non-Existent Memory
(NXM) error. An NXNI error is caused when no memory responds to a particular address. The
MA data in the error report indicates the address which produced the NXM trap. Mter the trap is
reported, the program attempts to restart the test from the beginning. The MA and VPC fields have
the same meanings as error 003.

6-31
OFFLINE DIAGNOSTICS

If this error occurs at a memory address that should be in the memory configuration, the memory
in question is not supplying an ACK to the I/O Control Processor when the specified address is
presented on the memory bus. The most probable point of failure is the logic on the memory
module that compares addresses on the memory bus with the range of addresses to which the
module should respond. Also, the comparator itself could be faulty or the [C IN, C OUT], [0 IN,
o OUT], or [p IN, P OUT] lines on the backplane could be in error.

•

Error 005, memory test error (p.ioj/c detected)-Indicates the I/O Control Processor detected an
error while testing Program memory. This error can only occur if I/O Control Processor interaction
with Program memory is selected. This interaction consists of:

1. A series of PDP-II instructions that perfonn read/modify/write (RMW) cycles to selected
Program memory locations.
2. Quick-verify tests of the entire Program memory (done 6 Kwords at a time).
Error 005 can be caused by cross-talk between the Program memory bus and either the Control or
Data bus. It can also be caused by a failure in the Program memory logic which inhibits refresh
cycles in the middle of a RMW cycle.
NOTE

Errors 006 through 009 are HSC50-specific and do not apply to the HSC70.
•

Error 010 (12 octal), cache parity trap, VPC = xxxxxx-Can happen during any test. The J 11
trapped through the parity vector. The error was caused by the cache.
NOTE

Errors 011 through 017 can occur on an HSC70 when load device interaction is enabled.
•

ErrorOl1,RX33 drive not ready-Indicates the drive selected for the operation was not ready.
The door may be open or the diskette absent during a READ or POSITION command.

•

Error 012, RX33 CRC error during seek-Indicates the RX33 detects a CRC error during a
seek. The RX33 could not verify position when reading header infonnation from the diskette.
Error 013, RX33 track 0 not set on recaiibrate-indicates a Recaiibrate (seek to track 0)
operation is perfonned before each block of Read operations. If the RX33 does not show correct
status after the RECAL command, error 013 is printed.

•

Error 014, RX33 seek timeout-Prints if the RX33 does not respond by interrupting during a
seek.

•

Error 015, RX33 seek error-Sets the seek error bit (bit 4 of the CSR). At the end of a Seek
operation, the RX33 found out it is not where it thought it should be.

•

Error 016, RX33 read timeout-Indicates the RX33 did not interrupt at the end of a READ
command.
Error 17, RX33 CRC/RNF error on read command-Can be caused by a soft error or bad
spot(s) on the disk. For infonnational purposes, the following additional message prints out:
First LBN In Transfer = xxxx

Where xxx is the LBN of the first block in the transfer. The offline interaction bus test performs
reads in blocks of four.

6-32
OFFLINE DIAGNOSTICS

6.5.6.4 K Memory Test Algorithm

The moving inversions memory test (MOVI) is used to generate bus contention among the requestors.
Each requestor in an HSC contains the moving inversions test as part of its microdiagnostic software
set. The moving inversions RAM test is used to detect data and addressing problems in dynamic
semiconductor memories.
The following are the steps in the moving inversions algorithm:
1. Write 000000 in each location being tested.
2. Read all locations in order from lowest to highest. After reading a location and checking for a 0,
rewrite the same location with a 1 in the least significant bit. Then reread the location and verify
the write worked correctly.
3. Again, read all locations in order from lowest to highest, checking to see each location contains the
data previously written. Then rewrite the data found with a single additional 1 bit and reread to
check that the write worked properly.
4. Repeat step 3 until the test pattern consists of a word containing all Is (pattern 177777).
5. Repeat steps 1 through 4, but this time start at the highest memory address and work down to the
lowest each time. However, instead of adding an additional 1, add an additional O. This changes
each memory location from all Is back to all Os.
6. End of test. All memory is cleared to 000000.

6.6 OFFLINE K TEST SELECTOR
The offline K test selector allows a K to perform an internal microdiagnostic self-test on command.
This offline K test executes from the P.ioj/c and uses the HSC K Control Area for instnlction. Select
the K for testing and the test number of the microdiagnostic test for execution.

6.6.1 Offline K Test Selector System Requirements
The following hardware is required to run this test:
•

P.ioj/c (processor) module with HSC Boot ROMs

•

M.std2/M.std (memory) module

•

A working section of Control memory for use as a K Control Area

•

One working load device drive

•

Terminal connected to the P.ioj/c console interface

Due to the sequence of tests that precede this test, assume the P.ioj/c, Program memory, and load
device are working.

6.6.2 Offline K Test Selector Operating Instructions
If the HSC is not booted and loaded, refer to Section 6.1.2, Section 6.1.3, and Section 6.2. IT the loader
prompt ODL> is displayed, follow these steps to start the K test selector.

1. Type TEST K IRETURN l The load device drive-in-use LED lights as the test is loaded.
2. The test indicates it has been loaded properly by displaying the following:
HSC OFL K Test Selector

3. The test next prompts for parameters.

6-33
OFFLINE DIAGNOSTICS

6.6.3 Offline K Test Selector Parameter Entry
This section gives detailed infonnation on how to enter the test parameters for the offline K test
selector. Items in square brackets are the default value for each particular pronlpl. If no default is
possible, the brackets are empty.
NOTE

}i'or any of the offline K test prompts, use the DELete key to delete mistyped parameters before
terminating the entry with IRETURN L If an error in a parameter was terminated with IRETURN L
type /cTRucl to return to the initial prompt and re-enter all parameters.
The offline K test selector first prompts:
Requestor t of K (1 thru 9) [] ?
Answer this question with a single digit (1 t,ough 9), that specifies the requestor number of the K
to be used. Terminate the response by typing RETURN. After the requestor number is supplied, a K
Control Area is located in Control memory and tested. This area is required for communicating with
the K that will run its microdiagnostics. The test then prompts:
Test t (1 thru 11) (0) [ ] ?
SfcRt:..tJc.£ fflG'E..
Fott. reSTS

b - i/O

Legal test numbers are octal numbers between 1 and 11(8), except for test 5. (Test 5 is the K's Control
and Data jemory ,est, which is supported by the OFL KIP memory test.) Terminate the test number
entry with RETURN. The test then prompts:
t of passes to perform (D) [1] ?
L...-.._----J>

the number
results in the

The P.ioj/c next instructs the K to perform the selected test, and allows up to 4.2 seconds for the K
to complete its test. IT the K completes the test within this time, the P.ioj/c displays an end-or-pass
message. IT the K fails to complete within 4.2 seconds, the P.ioj/c displays a K time-out error (error
009).
The K microdiagnostics are designed to hang when an error is detected, so all failures in the
microdia nos tics are reported as time-out errors. The current test may be aborted at any time by
typing CTRUC.
After the first test has been specified and completed, the following prompt is issued:
Reuse parameters (YIN)

[Y] ?

If this prompt is answered with a IRETURN' or a Y IRETURN I, the last test specified is repeated using the
same parameters. If the prompt is answered with an N IRETURNI, the test prompts for new parameters.

6.6.4 Offline K Test Selector Progress Reports
Each time the K completes one fu11 pass through the test specified, an end-of-pass report is displayed.
A full pass is defined as:
1. The K completes the test with no errors detected.
2. The K fails its test, and the P.ioj/c times out.
The end-of-pass message is displayed as fo11ows:
End of Pass nnnnnn, xxxxxx Errors, yyyyyy Total Errors

The pass count nnnnnn is a decimal count of the number of complete passes made. The errors count
(xxxxxx) indicates the number of errors detected during the current pass. The total errors count
(yyyyyy) indicates the number of errors detected during all passes completed so far.

6-34
OFFLINE DIAGNOSTICS

6.6.5 Offline K Test Selector Error Information
All error messages produced by this test confonn to the HSC generic diagnostic error message format
(Section 6.1.5). Offline K selector test error nlessages are preceded by an OKTS> prompt. In this lest,
optional lines three, four, and five show the address of the failing location (MA), EXPected data (EXP),
and ACTual data (ACT).
6.6.5.1 K.ci Path Status Information
Whenever a K.ci is enabled, it runs the CI link test as part of its microdiagnostics. The link test
performs loop-back tests on CI paths A and B of the K.ci. To pass the link test, one of the paths
must work (one failing path is not a fatal error). The microdiagnostics then return information in the
K Control Area, which specifies which paths worked and how many retries were required. (The test
retries 64 times before declaring a failure.)

The offline K test selector reports the CI path status each time the K.ci is initialized. IT the link test is
selected (K.ci test 11), the path status is reported only after the link test completes. (When the K.ci is
enabled, it runs all of its microdiagnostics, including the link test. If the link test is selected, the K.ci
runs that test once more.)
The CI path status display indicates which path failed the link test, if any. If both paths fail, the
microdiagnostics fail in test 11, and no path status information is displayed. The status display also
includes the nwnber of retries required for paths that passed the link test.
6.6.5.2 Error Messages
Errors detected by this test fall into one of three classes:

1. Contro) memory errors occurring when the pjoj/c is testing the portion of Control memory used to
communicate with the K. (The P.ioj/c does not test Data memory.) Error numbers ()()() through 007
are all Control memory errors detected by the P.ioj/c. The difference between these errors is the
exact step in the memory test where they are detected. The step where an error was detected can
be a helpful clue to the cause of the error.
2.

Failures in a K microdiagnostic detected by a time-out. Error 008 indicates the K failed to initialize
properly. Error 009 indicates the K failed the selected microdiagnostic.

Unexpected traps detected by the P.ioj/c (NXM and Parity). Errors 010 and 011 are unexpected
trap errors detected by the P.ioj/c. Error 010 signifies a parity trap occurred, and error 011 indicates
a nonexistent memory trap. The reports for unexpected trap errors differ slightly from a data
error report since they do not display EXPected and ACTual data. Error 012 indicates no working
Control memory could be found for a K Control Area. Error 13 is a cache parity trap.

The following list describes the nature of the failure indicated by each error nwnber.

•

Error OOO-Occurs in the moving inversions test when the P.ioj/c is testing the K Control Area at
a memory location that did not contain the expected pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

The ACTual data contains a single additional 1.

6-35
OFFLINE DIAGNOSTICS

2. The additional 1 bit occurs immediately to the left of the leftmost one in the EXPected data.
For example:
EXP=000377, ACT=000777
EXP=077777, ACT=177777
EXP=OOOOOO; ACT=OOOOOl

For the first example, the location in error was probably written with the pattern 000777 when
a lower numbered address was being written with the same pattern. When the location in error
was subsequently checked to ensure it still contained the previous pattern (000377), it contained
the next pattern (000777).
Data errors at this step of the test fall into one of the following classes:
a. The ACTual and EXPected data differ by more than one bit:
EXP=017777, ACT=017477

b. The ACTual data contains fewer Is than the EXPected data:
EXP=003777, ACT=001777

c. The bit in error is not in the bit position immediately to the left of the leftmost 1 in the
EXPected data:
EXP=000777, ACT=002777

•

Error OOl-Occurs in the moving inversions test when the P.ioj/c is testing the K Control Area at
a location written with a pattern. Immediately after the write, the location was read and found to
contain an incorrect pattern, where:
•

MA is the address of the failing location.
EXP is the datapattem EXPected.

•

ACT is the data pattern ACTually found.

bit for that address is probably defective.
If the error occurs in many locations but only occurs in a particular nibble (four-bit field), one of
the bus data transceivers for that nibble probably is defective.
If the error occurs in many locations and the bits in error are randomly spaced throughout the word,
the memory or bus timing is probably faulty.
If the error occurs in more than one location but the addresses of the failing locations are similar,
there could be crosstalk between the memory data and addressing lines. For instance, all failing
addresses end with either 2 or 6.

•

Error 002-0ccurs in the moving inversions test when the P.ioj/c is testing the K Control Area. A
memory location did not contain the expected pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

6-36
OFFLINE DIAGNOSTICS

1. The ACfual data contains one more 0 than the EXPected data.
2. The additional 0 occurs in the same bit position as the leftmost bit in the EXPected data. For
example:
EXP=003777, ACT=001777
EXP;000017, ACT=000007
EXP=177777, ACT=077777

In the first example, the location in error was probably written with the pattern 001777 when a
lower numbered address was being written with the same pattern. When the location in error was
subsequently checked to ensure it still contained the previous pattern (003777), it contained the
next pattern (001777).
Data errors in this step of the moving inversions test fall into one of the following categories:
1. The ACfual and EXPected data differ by more than one bit:
EXP=177777, ACT=174777

2. The ACfual data contains more 1s than the EXPected data:
EXP=037777, ACT=077777

3. The bit in error is not in the same bit position as the leftmost bit in the EXPected data:
EXP=001777, ACT=001377

•

Error 003-0ccurs in the moving inversions test when the P.ioj/c is testing the K Control Area. A
location was written with a pattern. Immediately after the write, the location was read and found
to contain an incorrect pattern, where:
•

MA is the address of the failing location.
EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

This error indicates a memory data problem. One of the following hardware failures is indicated:
1. A bit was picked up or dropped when the location was written.
2. A bit was picked up or dropped when the location was read.
If the error occurs repeatedly but only in a single location, the memory chip containing the failing
bit for that address is probably defective.
If the error occurs in many locations but only occurs in a particular nibble (four-bit field), one of
the bus data transceivers for that nibble probably is defective.
If the error occurs in many locations and the bits in error are randomly spaced throughout the word,
the memory or bus timing probably is faulty.

If the error occurs in more than one location but the addresses of the failing locations are similar,
there could be crosstalk between the memory data and addressing lines. For instance, all failing
addresses end with either 2 or 6.

•

Error 004--0ccurs in the moving inversions test when the P.ioj/c is testing the K Control Area. A
memory location did not contain the expected pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

6-37
OFFLINE DIAGNOSTICS

This error can be caused by a data error in the address specified, or it may indicate a dualaddressing problem (the location was incorrectly addressed and written when some other location
was written). At this step in the test, a dual-addressing problem is characterized by:
1. The ACfual data contains a single additional 1.
2. The additional 1 bit occurs immediately to the left of the leftmost bit in the EXPected data.
For example:
EXP=000377, ACT=000777
EXP=077777, ACT=177777
EXP=OOOOOO, ACT=OOOOOI

In the first example, the location in error was probably written with the pattern 000777 when a
higher numbered address was being written with the same pattern. When the location in error was
subsequently checked to ensure it still contained the previous pattern (000377), it contained the
next pattern (000777). Data errors at this step of the test fall into one of the following classes:

1. The ACfual and EXPected data differ by more than one bit:
EXP=017777, ACT=017477

2. The ACfual data contains fewer Is than the EXPected data:
EXP=003777, ACT=001777

3. The bit in error is not in the bit position immediately to the left of the leftmost bit in the
EXPected data:
EXP=000777, ACT=002777

Error OOS-Occurs in the moving inversions test when the P.ioj/c is testing the K Control Area. A
location was written with a pattern. Immediately after the write, the location was read and found
to contain an incorrect pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

ACT is t.~e data pattern ACTually foun.d.

This error indicates a memory data problem. One of the following hardware failures is indicated:
1. A bit was picked up or dropped when the location was written.
2. A bit was picked up or dropped when the location was read.
IT the error occurs repeatedly but only in a single location, the memory chip containing the failing
bit for that address is probably defective. IT the error occurs in many locations but only occurs
in a particular nibble (four-bit field), one of the bus data transceivers for that nibble probably is
defective.
IT the error occurs in many locations and the bits in error are randomly spaced throughout the word,
the memory or bus timing is probably faulty.
If the error occurs in more than one location but the addresses of the failing locations are similar,
there could be crosstalk between the memory data and addressing lines. For instance, all failing
addresses end with either 2 or 6.

•

Error 006-0ccurs in the moving inversions test when the P.ioj/c is testing the K Control Area. A
memory location did not contain the expected pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

6-38
OFFLINE DIAGNOSTICS

This error can be caused by a data error in the address specified, or it may indicate a dualaddressing problem. (The location was incorrectly addressed and written when some other location
was being written). At this step in the test, a dual-addressing problem is characterized by:
1. The ACfual data containing one more 0 than the EXPected data.
2. The additional 0 occurring in the same bit position as the leftmost bit in the EXPected data.
For example:
EXP=003777, ACT=001777
EXP=000017, ACT=000007
EXP=177777, ACT=077777

In the first example, the location in error was probably written with the pattern 001777 when a
higher numbered address was being written with the same pattern. When the location in error was
subsequently checked to ensure it still contained the previous pattern (003777), it contained the
next pattern (001777). Data errors in this step of the moving inversions test fall into one of the
following categories:

1. The ACfual and EXPected data differ by more than one bit
EXP=177777, ACT=174777

2. The ACfual data contains more 1s than the EXPected data:
EXP=037777, ACT=077777

3. The bit in error is not in the same bit position as the leftmost bit in the EXPected data:
EXP=001777, ACT=001377

Error 007-Occurs in the moving inversions test when the P.ioj/c is testing the K Control Area. A
location was written with a pattern. Immediately after the write, the location was read and found
to contain an incorrect pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

If the error occurs in many locations but only occurs in a particular nibble (four-bit field), one of
the bus data transceivers for that nibble probably is defective.

H the error occurs in many locations, and the bits in error are randomly spaced throughout the
word, the memory or bus timing is probably faulty.
If the error occurs in more than one location but the addresses of the failing locations are similar,
there could be crosstalk between the memory data and addressing lines. For example, all failing
addresses end with either 2 or 6.

•

Error 008-Indicates the selected K did not complete its Init sequence properly. When the P.ioj/c
enables the K to perform a test, the K begins its Init sequence (which includes executing certain
microdiagnostics). At the end of the K's Init sequence, the K indicates it found the K Control Area
by complementing a pointer word in the Control memory. H the K fails to complement this pointer
word within 4.2 seconds of being enabled, error 008 is reported.
The contents of the K status register are displayed with the error report.

6-39
OFFLINE DIAGNOSTICS

If this error occurs, make sure the requestor number parameter given matches the actual requestor
number of the K.

•

Error 009-lndicates the K failed the selected microdiagnostic test. This usually indicates a
serious hardware problem in the K. The contents of the K status register are displayed with the
error report.

•

Error OIO-lndicates the P.ioj/c detected a parity trap. The 22-bit address of the location that
caused the trap is displayed as the MA data in the error report, where:
•

MA is the address causing the parity trap.

•

VPC is the virtual PC of the memory test at the time the trap occurred. Reference this address
in the listing to locate the area of the test where the error occurred.

Because the data is lost when a parity trap occurs, no EXPected or ACTual data is displayed. After
the trap is reported, the program attempts to restart the test from the beginning.
•

Error Oil-indicates the P.ioj/c detected a nonexistent memory trap. A NXM error is caused when
no memory responds to a particular address. The MA data in the error report indicates the address
which produced the NXM trap. After reporting the trap, the program attempts to restart the test
from the beginning, where:
•

MA is the address causing the NXM trap.

•

MA is the address causing the parity trap.

•

VPC is the virtual PC of the memory test at the time the trap occurred. Reference this address
in the listing to locate the area of the test where the error occurred.

If this error occurs at a memory address that should be in your memory configuration, the memory
in question is not supplying an ACK to the P.i<>j/c when t-he specified address is presented on the
memory bus. The most probable point of failure is the logic on the memory module that compares
addresses on the memory bus to the range of addresses the module should respond to. Also, the
comparator itself could be faulty, or the [C IN, C OUT], [D IN, D OUT], or [P IN, P OUT] lines
on the backplane could be in error.

•

Error OI2--lndicates no working Control memory could be found for a K Control Area. A K
Control Area is required to communicate with a K. The Control memory must be repaired before
the K test selector can be used to test a K. Use the offline loader command TEST MEMORY to
test Control memory.

•

Error OI3-Cache parity trap, vpe = xxxxxx-This can happen during any test. The JllfFll
trapped through the parity vector. The error was caused by the cache.
During the run of the diagnostic, the JII/FII took a trap through the parity error vector. This is a
cache error and the virtual PC at the time of the trap is printed.

6.6.6 Offline K Test Selector Summaries
The following is a list of offline K selector test summaries.
•

Test 000, moving inversions test-The moving inversions (MOVI) memory test is used by the
P.ioj/c to test a K Control Area. The K Control Area is used to pass memory test parameters to the
K and to return the results of memory tests to the P.ioj/c. The moving inversions RAM test is used
to detect data and addressing problems in dynamic semiconductor memories.
The following are the steps in the moving inversions algorithm.
1. Write 000000 in each location being tested.

6-40
OFFLINE DIAGNOSTICS

2. Read all locations in order from lowest to highest. After reading a location and checking for a
0, rewrite the same location with a single 1 in the least significant bit. Then reread the location
and verify the write worked correctly.
3. Again read all locations in order from lowest to highest. Check that each location contains
the data previously written. Rewrite the data found with a single additional 1 bit. Reread it to
verify the Write operation worked properly.

4. Repeat step 3 until the test pattern consists of a word containing all 1s (pattern 177777).

5. Repeat step 3, but this time substitute a single extra 0 each time, instead of a 1.
6. Continue step 5 until the test pattern consists of a word of alIOs (pattern 000000).
7. Repeat steps 1 through 6, but this time start at the highest memory address and work down to
the lowest each time. This will work each memory location from all Os to all Is, and back to
all Os.
8. End of test. All memory is cleared to 000000.
•

Test 001 through test 011, K microdiagnostics-Refer to the following three lists for the names
of each microdiagnostic. Included in each list is the type of K being used and the failing test
number.
1. K.ci microdiagnostics-The following list shows the test number and name of each of the K.ci
microdiagnostics.
Test 0 - Sequencer test
Test 1 - ALOE test
Test 2 - Data bus test
Test 3 - Control bus test
Test 4 - PROM parity test
Test 5 - Memory test (unavailable via K test selector)
Test 6 - RAM test
Test 7 - PLY interface test
Test 10- Packet buffer test
Test 11- Link test
2. K.sdi/K.si microdiagnostics-The following list shows the test number and name of each of the
K.sdi/K.si microdiagnostics.
Test 0 - Sequencer test
Test 1 - ALOE test
Test 2 - Data bus test
Test 3 - Control bus test
Test 4 - PROM parity test
Test 5 - Memory test (not available via K test selector)
Test 6 - RAM test
Test 7 - SERDES/RSGEN test
Test .1 0- Partial SDI interface test
3. K.sti/K.si microdiagnostics-The following list shows the test number and name of each of the
K.sti/K.si microdiagnostics.
Test 0 Test 1 Test 2 Test 3 Test 4 Test 5 -

Sequencer test
ALOE test
Data bus test
Control bus test
PROM parity test
Memory test (not available via K test selector)

6-41
OFFLINE DIAGNOSTICS

Test 6 - RAM test
Test 7 - SERDES test
Test 10 - Partial STI interface test

6.7 OFFLINE KIP MEMORY TEST
The offline KIP memory test tests the HSC Control and Data memories from a K.sdi, K.sti, K.si, or
K.ci. This test executes from the 1/0 Control Processor and uses the HSC K Control Area to instruct
one of the subsystem requestors to test either the Control or Data memories. Select the K to be used
as well as the starting and ending addresses of the section of memory to be tested. The test algorithm
used by the K stresses the memories trying to detect transient errors caused by bus and memory timing
problems. Errors are reported at the console terminal as they occur.

6.7.1 Offline KIP Memory Test System Requirements
Hardware required by this test includes:
•

I/O Control Processor module with HSC boot ROMs

•

At least one memory module

•

Load device and controller with at least one working drive

•

Terminal connected to 1/0 Control Processor console interface
At least one working K.sdi, K.sti, K.si, or K.ci

•

Working Control memory for a K Control Area

6.7.2 Offline KIP Memory Test Operating Instructions
If the HSC is not booted and loaded, refer to Section 6.1.2, Section 6.1.3, and Section 6.2. If these
preceding steps are complete, the ODL> prompt is present. Follow these next steps to start the memory
test.

1. Type TEST MEMORY BY K IRETURNI in response to the loader prompt ODL>. The load device
LED lights as the memory test is loaded.

2. The memory test indicates it has been loaded properly by displaying the following:
HSC70 OFL Kip Memory Test

3. The memory test then prompts for parameters.

6.7.3 Offline KIP Memory Test Parameter Entry
This section describes the various parameters for the offline KIP memory test.
NOTE

For any of the offline KIP memory test prompts, use the DELete key to delete mistyped
parameters before the terminating the entry with IRETURNL If an error in a parameter entry was
terminated with IRETURNb type ICTRucl to return to the initial prompt and re-enter all parameters.
The offline KIP memory test first prompts:
Requestor

of K (1 through 9)

[] ?

6-42
OFFLINE DIAGNOSTICS

Answer this question with the sinftle digit (1 through 9) that specifies the requestor number to be used.
Terminate the response by typing _RETURN!. Mter the requestor number is supplied, a K Control Area is
located in Control memory and tested. This area is required for communicating with the requestor that
performs tests of Data and Control memory. The test then prompts:
Control (0) or Data (1) memory [0] ?

Type 0 IRETURNI to test Control memory or type I/RETURNI to test Data memory. Type IRETURNI to
tenninate the response. (Typing just IRETURN J selects the Control memory test.) The memory test next
prompts for the first address to test.
(min] ?

First (min=XXXXXXXX)

Enter the first address to be tested. Addresses are eight octal digits in length. The rmin] address
displayed is the lowest address that may be entered for the memory chosen. Mter typing the address,
tenninate the response with IRETuRNI. (Typing just IRETURNI causes the first address to default to the
[Olin] address.)
NOTE

Because requestors test Control memory in 4-byte units, the lowest two bits of the starting
address are ignored (treated as binary Os). For example, if address 16000223 is entered as the
first address, the requestor starts testing at address 16000200.
Because requestors test Data memory in 64-byte units, the lower 6 bits of the starting address are
ignored (treated as binary Os). For example, if address 14012376 is entered as the first address,
the K starts testing at address 14012300.
The test next prompts for the last address to test:
Last (max=XXXXXXXX)

[] ?

Enter the last address to be tested. The max address displayed is the highest address still within the
memory chosen. H the system being worked on does not have a fully populated memory, the last
address that may be tested is less than the max address displayed. H a last address that excee-ds the
amount of memory in this system is chosen, the memory test displays a Non-Existent Memory (NXM)
error when the test reaches the first address beyond the end of the memory. (Use the offline loader
command SIZE to determine the actual last address in a given HSC.)
NOTE

Because requestors test Control memory in 4-byte units, the lower two bits of the ending address
are ignored (treated as binary Is). For instance, if address 16023400 is specified as the last
address, the K will test up to and including address 16023403.
Because requestors test Data memory in 64-byte units, the lower 6 bits of the ending address are
ignored (treated as binary Is). If address 14005400 is specified as the last address, the requestor
will test up to and including, address 14005477.
Finally, the memory test prompts:
t of passes to perform (D) [1] ?

Enter a decimal number between 1 and 2,147,483,647 (omitting commas) to specify the number of
times the memory test should be repeated (If 0 'RETURNI, or just ETURN I is entered. the test perfonns
one pass.) The test can be aborted at any time by typing CTRLJC
'.
Mter the first memory test completes, the following prompt is issued:
Reuse parameters (YIN)

[Y] ?

Answering this prompt with IRETURN I or Y IRETURNI repeats the last test specified using the same
parameters. Answering the prompt with an N IRETURN I causes the prompt for new parameters.

6-43
OFFLINE DIAGNOSTICS

6.7.4 Offline KIP Memory Test Progress Reports
Each time the requestor completes one full pass through the memory specified, an end-of-pass report is
displayed. A full pass is defined as:
1. A complete test of the memorj specified with no errors detected.
2. Testing the memory specified until an error occurs.
The end-of-pass message is displayed as follows:
End of Pass nnnnnn, xxxxxx Errors, yyyyyy Total Errors

The pass count nnnnnn is a decimal total of the complete passes made. The errors count (xxxxxx)
indicates the number of errors detected on the current pass. The total errors count (yyyyyy) indicates
the number of errors detected during the passes completed so far.

6.7.5 Offline KIP Memory Test Parity Errors
When a parity error occurs, it is desirable to know whether the error was produced by the loss or
gain of a data bit or by the loss or gain of a parity bit. When a parity trap occurs in the I/O Control
Processor, the data that was read is discarded by the PDP-II. However, a feature of the I/O Control
Processor allows parity traps to be disabled. Using this feature, a user can determine if a parity error is
being caused by a data or parity bit as follows:
1. After a parity trap (p.ioj/c detected) is reported, type ICTRucl to terminate the memory test.
2. Type another ICTRucl to return to the OFL diagnostic loader. The loader prompts ODL>.
3. Type Ex 17770042 I RETURN I. The contents of the I/O Control Processor switch control and status
register (SWCSR) are displayed as: (i) 17770042 nnnnnD.
4. Type De * nnnn4n I RETURN I. The nnnn4n represents the previous contents of the register, including
a 1 in bit 5. I/O Control Processor parity traps are now disabled.
5. Return to the memory test by typing START IRETURNL
6. Rerun the memory test with the original parameters.
If the location that previously produced a parity trap then produces a data error, the original parity
trap was caused by a data bit problem. The error report indicates the failing bit via the EXPected
and ACfual data displayed.
If the location that previously produced a parity trap does not fail again when the memory test is
rerun, the original parity trap was caused by an error in one of the parity bits (high or low byte)
for that word.

jlYpe a

RLlel to return to the loader, and re-enable parity errors by typing De 17770042 nnnnOn
RETURN. The nnnnOn represents original contents of the I/O Control Processor SWCSR, before
parity traps were disabled (refer to step 5).

6-44
OFFLINE DIAGNOSTICS

6.7.6 Offline KIP Memory Test Error Information
For generic diagnostic error message fonnat, refer to Section 6.1.5. Listed below is a typical error
nlessage from test memory by K.
OKPM>hh:mm T aaa E bbb u-ooo
< Text describing error >
MA -xxxxxxxx

EXP-yyyyyy
ACT-zzzzzz
< K-Error-Summary-Info >
< K-Error-Summary-Info >

See next section.

Where:
•

hh is the elapsed hours since the last bootstrap.

•

mm is the elapsed minutes.
aaa is the decimal number denoting the test.

•

bbb is the decimal number denoting the error detected.

•

xxxxxxxx is the address of the location causing the error.
yyyyyy is the data that was EXPected.

zzzzzz is the data that was ACTually found.
6.7.6.1 Summary Information

When the requestor reports a memory test failure to the I/O Control Processor, the following
information is supplied:
1. Address of the failing memory location
2. Data EXPected and data ACTually found
3. Error summary infonnation
The error summary infonnation is supplied as a three-bit field, including the following:
1. A bit indicating a parity error occurred while reading the location.
2. A bit indicating an NXM error occurred while accessing the location.
3. A bit indicating a Control bus (CBUS) error occurred while accessing the location.
When a memory error report is issued for an error detected by the K, the last line of the error report
includes a list of the error summary bits that were set (if any).
A control bus (CBUS) error indicates the requestor asserted an illegal combination of the three
CCYCLE lines when accessing Control memory. As these lines were previously tested from the
I/O Control Processor (in the OFL P.ioj/c test), a Control bus error is most likely caused by a problem
with the requestor's drivers that assert the CCYCLE lines.

6-45

OFFLINE DIAGNOSTICS

6.7.6.2 Messages

Error messages produced by this test can be caused by a memory error detected either by the I/O
Control Processor or by the requestor being used to test memory. Errors detected by the I/O Control
Processor occur when the I/O Control Processor is testing the portion of Control memory used to
communicate with the K. (The I/O Control Processor does not test Data memory.)
To determine whether the I/O Control Processor or the requestor detected an error, examine the second
line of the error message. The text begins either with a (P) or a (K). If the text begins with a (P), the
I/O Control Processor detected the error. If the text begins with a (K), the requestor detected the error.
Error numbers 000 through 007 are all Control memory errors detected by the I/O Control Processor.
The difference between these errors is the exact step in the memory test where they are detected. The
step where an error is detected can be a helpful clue to the cause of the error.
Error 008 indicates the requestor failed to initialize properly.
Error 009 indicates a Control or Data memory error detected by the K. In addition to the normal error
information, the last line of the error report contains a K error summary (see previous section).
Errors 010 and 011 are unexpected trap errors detected by the I/O Control Processor. Error 010
signifies a parity trap occurred. Error 011 indicates a Non-Existent Memory (NXM) trap. The reports
for unexpected trap errors differ slightly from a data error report because they do not display EXPected
and ACTual data.
Error 012 indicates no working Control memory could be found for a K Control area. Error 013
indicates a parity trap caused by cache.
The following list describes the nature of the failure indicated by each error number.
•

Error OOO--Occurs in the moving inversions test (see Section 6.7.7) when the I/O Contro)
Processor is testing the K Control Area. A memory location did not contain the expected pattern,
where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

This error can be caused by a data error in the address specified, or it may indicate a dualaddressing problem (the location was incorrectly addressed and written when some other location
was written). At this step in the test, a dual-addressing problem is characterized by:
1. The ACTuai data contains a single additional 1.
2. The additional 1 bit occurs immediately to the left of the leftmost bit in the EXPected data,
such as:
EXP=000377, ACT=000777
EXP=077777, ACT=177777
EXP=OOOOOO, ACT=OOOOOl

In the first example, the location in error was probably written with the pattern 000777 when a
lower numbered address was being written with the same pattern. When the location in error was
subsequently checked to ensure it still contained the previous pattern (000377), it contained the
next pattern (000777).
Data errors at this step of the test fall into one of the following classes:
1. The ACTual and EXPected data differ by more than one bit:
EXP=017777, ACT=017477

6-46
OFFLINE DIAGNOSTICS

2. The ACTual data contains fewer 1s than the EXPected data:
EXP=003777, ACT=001777

3. The bit in error is not in the bit position immediately to the left of the leftmost bit in the
EXPected data:
EXP=000777, ACT=002777

•

Error OOl-Occurs in the moving inversions test (Section 6.7.7) when the I/O Control Processor
is testing the K Control Area. A location was written with a pattern. Immediately after the write,
the location was read. It contained an incorrect pattern, where:

•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.
ACT is the data pattern ACTually found.

This error indicates a memory data problem. One of the following hardware failures is indicated:
1. A bit was picked up or dropped when the location was written.
2. A bit was picked up or dropped when the location was read.
If the error occurs repeatedly but only in a single location, the memory chip containing the failing
bit for that address probably is defective.
If the error occurs in many locations but only occurs in a particular nibble (four-bit field), one of
the bus data transceivers for that nibble probably is defective.
If the error occurs in many locations and the bits in error are randomly spaced throughout the word,
the memory or bus timing is probably the problem.
If the error occurs in more than one location but the addresses of the failing locations are similar,
crosstalk between the memory data and addressing lines may be present. For example, all failing
addresses end with either 2 or 6.

•

Error 002--Occurs in the moving inversions test (Section 6.7.7) when the I/O Control Processor
is testing the K Control Area. A memory location did not contain the expected pattern, where:

•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

1. The ACTual data contains one more 0 than the EXPected data.
2. The additional 0 occurs in the same bit position as the leftmost bit in the EXPected data, such
as:
EXP=003777, ACT=001777
EXP=000017, ACT=000007
EXP=177777, ACT=077777

6-47
OFFLINE DIAGNOSTICS

Data errors in this step of the moving inversions test fall into one of the following categories:
1. The ACfual and EXPected data differ by more than one bit:
EXP=177777, ACT=174777

2. IDe ACTual data contains Inore 1s than the EXPected data:
EXP=037777, ACT=077777

3. The bit in error is not in the same bit position as the leftmost bit in the EXPected data:
EXP=0017777, ACT=00377

•

Error 003-0ccurs in the moving inversions test (Section 6.7.7) when the I/O Control Processor
is testing the K Control Area. A location was written with a pattern. Immediately after the write,
the location was read. It contained an incorrect pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

If the error occurs in many locations but only occurs in a particular nibble (four-bit field), one of
the bus dat-a transceivers for that nibble probably is defective.
If the error occurs in many locations and the bits in error are randomly spaced throughout the word,
the memory or bus timing is probably the problem.
If the error occurs in more than one location but the addresses of the failing locations are similar,
crosstalk between the memory data and addressing lines could be present. For exampie, ali faiiing
addresses end with either 2 or 6.

•

Error 004--0ccurs in the moving inversions test (see Section 6.7.7) when the I/O Control
Processor is testing the K Control Area. A memory location did not contain the expected pattern,
where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

This error can be caused by a data error in the address specified, or it may indicate a dualaddressing problem (the location was incorrectly addressed and written when some other location
was written). At this step in the test, a dual-addressing problem is characterized by:
1. The ACfual data contains a single additional 1.
2. The additional 1 bit occurs immediately to the left of the leftmost bit in the EXPected data,
such as:
EXP=000377, ACT=000777
EXP=077777, ACT=177777
EXP=OOOOOO, ACT=OOOOOl

6-48
OFFLINE DIAGNOSTICS

In the first example, the location in error was probably written with the pattern 000777 when a

higher numbered address was being written with the same pattern. When the location in error was
subsequently checked to ensure it still contained the previous pattern (000377), it contained the
next pattern (000777).
Data errors at this step of the test fall into one of the following classes:
1. The ACfual and EXPected data differ by more than one bit:
EXP=017777, ACT=017477

2. The ACfual data contains fewer Is than the EXPected data:
EXP=003777, ACT=001777

3. The bit in error is not in the bit position immediately to the left of the leftmost bit in the
EXPected data:
EXP=000777, ACT=002777

•

Error 005-0ccurs in the moving inversions test (Section 6.7.7) when the 1/0 Control Processor
is testing the K Control Area. A location was written with a pattern. Immediately after the write,
the location was read. It contained an incorrect pattern, where:
MA is the address of the failing location.
•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

This error indicates· a memory data problem. One of the following hardware failures is indicated:

1. A bit was picked up or dropped when the location was written.
2. A bit was picked up or dropped when the location was read.
If the error occurs repeatedly but only in a single location, the memory chip containing the failing

bit for that address is probably defective.
If the error occurs in many locations but only occurs in a particular nibble (four-bit field), one of

the bus data transceivers for that nibble probably is defective.
If the error occurs in many location\) and the bits in error are randomly spaced throughout the word,

the memory or bus timing is probably the problem.
H the error occurs in more than one location but the addresses of the failing locations are similar,
crosstalk between the memory data and addressing lines could be present. For example, all failing
addresses end with either 2 or 6.

•

Error 006--0ccurs in the moving inversions test (Section 6.7.7) when the 1/0 Control Processor
is testing the K Control Area. A memory location did not contain the expected pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

This error can be caused by a data error in the address specified or it may indicate a dual-addressing
problem. (The location was incorrectly addressed and written when some other location was being
written.)
At this step in the test, a dual-addressing problem is characterized by:
1. The ACfual data contains one more 0 than the EXPected data.

6-49
OFFLINE DIAGNOSTICS

2. The additional a occurs in the same bit position as the leftmost bit in the EXPected data, such
as:
EXP=003777, ACT=001777
EXP=000017, ACT=000007
EXP=177777, ACT=077777

In the first example, the location in error was probably written with the pattern 001777 when a
higher numbered address was being written with the same pattern. When the location in error was
subsequently checked to ensure it still contained the previous pattern (003777), it contained the
next pattern (001777).
Data errors in this step of the moving inversions test fall into one of the following categories:
1. The ACfual and EXPected data differ by more than one bit:
EXP=177777, ACT=174777

2. The ACfual data contains more 1s than the EXPected data:
EXP=037777, ACT=077777

3. The bit in error is not in the same bit position as the leftmost bit in the EXPected data:
EXP=001777, ACT=001377

•

Error 007-0ccurs in the moving inversions test (Section 6.7.7) when the I/O Control Processor
is testing the K Control Area. A location was written with a pattern. Immediately after the write,
the location was read. It contained an incorrect pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

This error indicates a memory data problem. One of the following hardware failures is indicated:
1. A bit was picked up or dropped when the location was written.

2. A bit was picked up or dropped when the location was read.
If the error occurs repeatedly but only in a single location, the memory chip containing the failing
bit for that address probably is defective.
If the error occurs in many locations but only occurs in a particular nibble (four-bit field), one of
the bus data transceivers for that nibble probably is defective.
If the error occurs in many locations and the bits in error are randomly spaced throughout the word,
the memory or bus timing is probably the problem.
If the error occurs in more than one location but the addresses of the failing locations are similar,
crosstalk between the memory data and addressing lines may be present. For example, aU failing
addresses end with either 2 or 6.

•

Error OOS-Indicates the selected requestor did not complete its Tnit sequence properly. When the
I/O Control Processor enables the requestor to perform the memory test, the requestor begins its
Init sequence (which includes executing certain microdiagnostics). At the end of the requestor's
Init sequence, the requestor indicates it found the K Control Area by complementing a pointer word
in Control memory. If the requestor fails to complement this pointer word within 50 milliseconds
(4.2 seconds for K.ci) of being enabled, error 008 is reported.
The contents of the K status register are displayed with the error report. If this error occurs, make
sure the requestor number parameter given matches the actual requestor number.

6-50
OFFLINE DIAGNOSTICS

•

Error 009-Indicates a Control or Data memory error detected by the K, where:

•

MA is the 22-bit address of the failing location.

•

EXP is the data pattern EXPected by the K.

•

ACT is the data pattern found by the K.

In addition to the address and the EXPected/ACTual data, the K returns an error summary,
displayed as the last line of the error report. The error summary information indicates whether
the error was caused by a parity error, a Non-Existent Memory (NXM) error, or a Control bus
(CBUS) error. H the error was not caused by any of the these, the error summary line does not
appear in the error report. Refer to Section 6.5.6.1 for further information on the error summary.
•

Error OIO-Indicates the I/O Control Processor detected a parity trap. The 22-bit address of the
location that caused the trap is displayed as the MA data in the error report, where:

•

MA is the address causing the parity trap.

•

VPC is the virtual PC of the memory test at the time the trap occurred. Reference this address
in the listing to locate the area of the test where the error occurred.

Because the data is lost when a parity trap occurs, no EXPected or ACTual data can be displayed.
To further localize the problem, disable parity errors and rerun the test (Section 6.7.5). If the
original failure was in a data bit position, the memory test detects and reports the error, displaying
the EXPected and ACTual data. This helps to trace the error to a particular address and/or bit
position. H no further errors are detected after disabling parity errors, the original failure was in
one of the parity bits for the address displayed in the parity trap report.
•

Error OIl-Indicates the I/O Control Processor detected a Non-Existent Memory (NXM) trap. A
NXM error is caused when no memory responds to a particular address. The MA datu in the error
report indicates the address that produced the NXM trap. After the trap is reported, the program
attempts to restart the test from the beginning, where:

•

MA is the address causing the NXM trap.

•

VPC is the virtual PC of the memory test at the time the trap occurred. Reference this address
in the listing to locate the area of the test where the error occurred.

If this error occurs at a memory address that should be in the memory configuration, the memory in
question is not supplying an ACK message to the I/O Control Processor when the specified address
is presented on the Memory bus. The most probable point of failure is the compare logic on the
memory module. This logic compares addresses on the Memory bus with the range of addresses to
which the module should respond. The comparator itself could be faulty or the [C IN, C OUTj, [D
IN, D OUT]. or [P IN, P OUT] lines on the backplane could be in error.

•

Error OIl-indicates no working Control memory could be found for a K Control Area. A K
Control Area is required to communicate with a requestor. Control memory must be repaired
before the KIP memory test can be used. Use the offline loader command TEST MEMORY to test
the Control memory.

•

Error 013, cache parity trap, VPC = xxxxxx-Indicates the J11 took a trap through the parity
error vector during the run of the diagnostic. This is a cache error; the virtual PC at the time of the
trap is printed.

6-51
OFFLINE DIAGNOSTICS

6.7.7 Offline KIP Memory Test Summaries
The foHowing is a smnmary of individual KIP memory tests.

•

Test 000, moving inversions test from P.ioj/c-This is the moving inversions (MOVJ) memory
test used by the I/O Control Processor to test a requestor control area. The K Control Area is used
to pass memory test parameters to the requestor and to return the results of memory tests to the I/O
Control Processor. The moving inversions RAM test is used to detect data and addressing problems
in dynamic semiconductor memories.
The following are the steps in the moving inversions algorithm.
1. Write 000000 in each location being tested.
2. Read all locations in order from lowest to highest. After reading a location and checking for a
0, rewrite the same location with a single 1 in the least-significant bit. Then reread the location
and verify the write worked correctly.
3. Again read all locations in order from lowest to highest. Check each location for the data
previously written. Rewrite the data found with a single additional 1 bit. Reread it to verify
the Write operation worked properly.
4. Repeat step 3 until the test pattern consists of a word containing all 1s (pattern 177777).
5. Repeat step 3 but this time substitute a single extra 0 each time, instead of a 1.
6. Continue step 5 until the test pattern consists of a word of aliOs (pattern 0000(0).
7. Repeat steps 1 through 6 but this time start at the highest memory address each time and work
down to the lowest. This changes each memory location from aliOs to all 1s and back to all
Os,
8. End of test. All memory is cleared to 000000.

•

Test 001, moving inversions test from K-This is the moving inversions test implemented in the
K microcode. The algorithm is identical to that described in the previous test, except steps 5 and 6
are omitted to save time.
When the requestor detects an error, the remainder of the test is aborted, and the information
concerning the error is returned to the I/O Control Processor via the K Control Area. The 1/0
Control Processor is responsible for displaying the error report.

6.8 OFFLINE MEMORY TEST
The offline memory test exercises the HSC memories. Control, Data, or Program memory may he
selected for testing. Three memory testing algorithms are used: the quick verify algorithm, the moving
inversions algorithm, and the walking 1s algorithm.
The quick verify algorithm quickly uncovers stuck data and address bits. The other two algorithms
stress the memories, attempting to detect transient errors caused by bus and memory timing problems.
Errors are reported at the console terminal as they occur. After reporting a data error, or a parity error
from a location being tested, testing continues where it left off. H an NXM error occurs during the
memory test, testing is restarted from the beginning.

6-52
OFFLINE DIAGNOSTICS

6.8.1 Offline Memory Test System Requirements
Following are the hardware requirements for the offline memory test.
•

I/O Control Processor module with HSC boot ROMs

•

At least one memory module

•

Load device with at least one working drive

•

Terminal connected to I/O Control Processor console interface

6.8.2 Offline Memory Test Operating Instructions
If the HSC is not booted and loaded, refer to Section 6.1.2, Section 6.1.3, and Section 6.2. If the HSC
is booted and loaded, the terminal displays an ODL> prompt. At this point, follow these steps to start
the memory test:

•

Type SIZE IRETURNI in response to the loader prompt ODL>. The load device drive-in-use LED
lights as the offline system sizer is loaded. The sizer displays the bounds of the various memories
in the HSC. The memory size information includes the last address of each memory.

•

Type TEST MEMORY IRETURNI in response to the loader prompt ODL>. The load device drivein-use LED lights as the memory test is loaded. The memory test indicates it has been loaded
properly by displaying the following:
HSC OFL Memory Test

The memory test next prompts for parameters. Refer to Section 6.8.3.

6.8.3 Offline Memory Test Parameter Entry
This section describes the offline memory test parameter entry.
NOTE

For any of the offline memory test prompts, use the DELete key to delete mistyped parameters
before the typing \RETURNL If an error in a parameter already terminated with IRETURN I is noted,
type ICTRucl to return to the initial prompt and re-enter all parameters.
The offline memory test first prompts:
Control (0) , Data(1}, or Program(2} Memory [0] ?

Type IRETURNI or 0 IRETURNI to test Control memory. Type a l\RETURNI to test Data memory. Type 2

IRETURN I to test Program memory. The memory test next prompts for the first address to test.
First (min=XXXXXXXX)

[min] ?

Enter the first address to be tested. Addresses are eight digits in length. The [min] address ditPlayed liS
the lowest address that may be entered for the memory chosen. Terminate the response with RETURN.
(Typing just IRETURN I causes the first address to default to the [min] value.) The test next prompts for
the last address to test.
Last (max=XXXXXXXX)

[] ?

Type the last address to be tested. The max address displayed is the highest address still within the
memory chosen. If the system does not have a fully-populated memory, the last address to be tested
is less than the max address displayed. Use the memory size information displayed by the ODL SIZE
command to answer this prompt with the correct address for the HSC under test. If a last address
that exceeds the amount of memory in the system is chosen, the memory test displays a Non-Existent
Memory (NXM) error when the test reaches the first address beyond the eI)d of the memory. The test
then prompts:

t of passes to perform (D)

[1] ?

6-53
OFFLINE DIAGNOSTICS

Enter a decimal number between 1 and 2,147,483,647 (omitting commas) to specify the number of
times the memory test should be re eated. (Brtering I RETURN I or 0 IRETURN I results in one pass.) It can
be aborted at any time by typing a CTRUC or CTRUY .
After the first memory test is complete, the following prompt is issued:
Reuse parameters (YIN)

[YJ ?

OnI[

Answering this prompt with Y1R~URNI or with.IRETURN/
repeats the last test specified, using the
same parameters. If the prompt IS answered WIth N IRETURN_ the test prompts for new parameters.

6.8.4 Offline Memory Test Progress Reports
A complete pass through the memory test consists of one pass through the quick verify test, one pass
through the moving inversions test, and one pass through the walking 1s test. After each complete
pass, an end-of-pass message is displayed as follows:
End of Pass nnnnnn, xxxxxx Errors, yyyyyy Total Errors

The pass count nnnnnn is a decimal count of the number of complete passes made. The Errors count
xxxxxx indicates the number of errors detected on the current pass. The total errors count (yyyyyy)
indicates the number of errors detected on all passes of the test completed so far.
NOTE

A complete pass through the memory test for Program memory may take about eight hours.
Unless exhaustive memory testing is required, allow this test to run only until the quick verify
pass complete message is displayed. This should take no more than 10 minutes.

6.8.5 Offline Memory Test Parity Errors
The process to disable P.ioj/c parity traps is identical for the offline memory test and the offline KIP
memory test. This process is described in Section 6.7.5.

6.8.6, Offline Memory Test Error Information
Refer to Section 6.1.5 for the generic diagnostic error message format. The following is a typical
offline memory test error message.

OMEM>hh:mm T
aaa E
bbb U-OOO
<Text describing error>
MA -xxxxxxxx
EXP-yyyyyy
ACT-zzzzzz

Where:
•

hh is the elapsed hours since the last bootstrap.

•

mm is the elapsed minutes.
aaa is the decimal number denoting the test.

•

bbb is the decimal number denoting the error detected.

•

xxxxxxxx is the address of the location causing the error.

•

yyyyyy is the data that was EXPected.

•

zzzzzz is the data that was ACfually found.

Parity trap and NXM trap errors do not include EXPected and ACfual data.

6-54
OFFLINE DIAGNOSTICS

6.8.6.1 Messages

Error tnessages produced by the memory test can be classed as either data errors or unexpected traps.
Error numbers 000 through 010 are all memory data errors. The only difference between these errors
is the exact step in the testing algorithm where they are detected. The step at which a data error occurs
can be an important clue to the cause of the error. Errors 000 through 007 are declared in the moving
inversions algorithm; while errors 008 through 010 are declared in the walking 1s algorithm.
Errors 011 and 012 are unexpected trap errors. Error 011 signifies a parity trap occurred and error 012
indicates a nonexistent memory trap. The reports for unexpected trap errors differ slightly from a data
error report because they do not display EXPected and ACfual data.
The following list describes the nature of the failure indicated by each error number.
•

Error OOO-Occurs in the moving inversions test (see Section 6.7.7). A memory location did not
contain the expected pattern, where:
MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

This error can be caused by a data error in the address specified, or it may indicate a dualaddressing problem. In the second case, the location was incorrectly addressed and written when
some other location was written. At this step in the test, a dual-addressing problem is characterized
by:
1. The ACfual data contains a single additional 1.
2. The additional 1 bit occurs immediately to the left of the leftmost bit in the EXPected data,
such as:
EXP=000377, ACT=000777
EXP=077777, ACT=177777
EXP=OOOOOO, ACT=OOOOOI

In the first example, the location in error was probably written with the pattern 0fXJ777 when a
lower numbered address was being written with the same pattern. When the location in error was
subsequently checked to ensure it still contained the previous pattern (000377), it contained the
next pattern (000777).
Data errors at this step of the test fall into one of the following classes:
1. The ACfual and EXPected data differ by more than one bit:
EXP=017777, ACT=017477

2. The ACfual data contains fewer 1s than the EXPected data:
EXP=003777, ACT=001777

3. The bit in error is not in the bit position immediately to the left of the leftmost bit in the
EXPected data:
EXP=000777, ACT=002777

•

Error OOI-Occurs in the moving inversions test (Section 6.7.7) when the I/O Control Processor
was testing the K Control Area. A location was written with a pattern. Immediately after the write,
the location was read. It contained an incorrect pattern, where:

•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

This error indicates a memory data problem. One of the following hardware failures is indicated:

6-55
OFFLINE DIAGNOSTICS

If the error occurs in many locations but only occurs in a particular nibble (four-bit field), one of
the bus data transceivers for that nibble probably is defective.
If the error occurs in many locations and the bits in error are randomly spaced throughout the word,
the Inemory or bus timing probably is the problem.
If the error occurs in more than one location but the addresses of the failing locations are similar
and crosstalk could exist between the memory data and addressing lines. For example, all failing
addresses end with either 2 or 6.

Error 002--0ccurs in the moving inversions test (Section 6.7.7). A memory location did not
contain the expected pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

This error can be caused by a data error in the address specified, or it may indicate a dualaddressing problem. (The location was incorrectly addressed and written when some other location
was being written.)
At this step in the test, a dual-addressing problem is characterized by:
1. The ACfual data contains one m-ore o than the EXPected data.
2. The additional a occurs in the same bit position as the leftmost bit in the EXPected data. For
example:
EXP=003777, ACT=001777
EXP=000017, ACT=000007
EXP=177777, ACT=077777

In the first example, the location in error was probably written with the pattern 001777 when a
lower numbered address was being written with the same pattern. When the location in error was
subsequently checked to ensure it still contained the previous pattern (003777), it contained the
next pattern (001777).
Data errors in this step of the moving inversions test fall into one of the following categories:
1. The ACTual and EXPected data differ by more than one bit:
EXP=177777, ACT=174777

2. The ACTual data contains more Is than the EXPected data:
EXP=037777, ACT=077777

3. The bit in error is not in the same bit position as the leftmost bit in the EXPected data:
EXP=001777, ACT=001377

•

Error 003-0ccurs in the moving inversions test (Section 6.7.7). A location was written with
a pattern. Immediately after the write, the location was read and found to contain an incorrect
pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

6-56
OFFLINE DIAGNOSTICS

•

ACT is the data pattern ACTually found.

This error indicates a memory data problem and one of the following hardware failures is
indicated:
1. A bit was picked up or dropped when the location was written.
2. A bit was picked up or dropped when the location was read.
If the error occurs repeatedly but only in a single location, the memory chip containing the failing
bit for that address is probably defective.
If the error occurs in many locations but only occurs in a particular nibble (four-bit field), one of
the bus data transceivers for that nibble probably is defective.
If the error occurs in many locations and the bits in error are randomly spaced throughout the word,
the memory or bus timing is probably the problem.
If the error occurs in more than one location but the addresses of the failing locations are similar,
crosstalk could be present between the memory data and addressing lines. For example, all failing
addresses end with either 2 or 6.

•

Error 004-0ccurs in the moving inversions test (see Section 6.7.7). A memory location did not
contain the expected pattern, where:
•

MA is the address of the failing location.
EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

This error can be caused by a data error in the address specified, or it may indicate a dualaddressing problem. In the latter case, the location was incorrectly addressed and written when
some other location was written.
At this step in the test, a dual-addressing problem is characterized by:
1. The ACTual data containing a single additional 1.
2. The additional 1 bit occurring immediately to the left of the leftmost bit in the EXPected data.
For instance:
EXP=000377, ACT=000777
EXP=077777, ACT=177777
EXP=OOOOOO, ACT=OOOOOI

In the first example, the location in error was probably written with the pattern 000777 when a
higher numbered address was being written with the same pattern. When the location in error was
subsequently checked to ensure it still contained the previous pattern (000377), it contained the
next pattern (000777).
Data errors at this step of the test fall into one of the following classes:
1. The ACTual and EXPected data differ by more than one bit:
EXP=017777, ACT=017477

2. The ACTual data contains fewer 1s than the EXPected data:
EXP=003777, ACT=001777

3. The bit in error is not in the bit position immediately to the left of the leftmost bit in the
EXPected data:
EXP=000777, ACT=002777

6-57
OFFLINE DIAGNOSTICS

•

Error 005-0ccurs in the moving inversions test (Section 6.7.7). A location was written with a
pattern. Immediately after the write, the location was read and it contained an incorrect pattern,
where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

This error indicates a memory data problem. One of the following hardware failures is indicated:
1. A bit was picked up or dropped when the location was written.
2.

A bit was picked up or dropped when the location was read.

If the error occurs repeatedly but only in a single location, the memory chip containing the failing
bit for that address probably is defective.
If the error occurs in many locations but only occurs in a particular nibble (four-bit field), one of
the bus data transceivers for that nibble probably is defective.
If the error occurs in many locations and the bits in error are randomly spaced throughout the word,
the memory or bus timing is probably the problem.
If the error occurs in more than one location but the addresses of the failing locations are similar,
crosstalk between the memory data and addressing lines could be present. For example, all failing
addresses end with either 2 or 6.

•

Error 006-0ccurs in the moving inversions test (Section 6.7.7). A memory location did not
contain the expected pattern, where:
•

MA -is -the -addr-ess o-fthe failing 19cation.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

This error c~m. be caused by a data error in the address specified, or it may indicate a dualaddressing problem. (The location was incorrectly addressed and written when some other location
was being written.)
At this step in the test, a dual-addressing problem is characterized by:
1. The ACTual data contains one more 0 than the EXPected data.
2. The additional 0 occurs in the same bit position as the leftmost bit in the EXPected data. For
example:
EXP=003777, ACT=001777
EXP=000017, ACT=000007
EXP=177777, ACT=077777

In the first example, the location in error was probably written with the pattern 001777 when a
higher numbered address was being written with the same pattern. When the location in error was
subsequently checked to ensure it still contained the previous pattern (003777), it contained the
next pattern (001777).
Data errors in this step of the moving inversions test fall into one of the following categories:
1. The ACTual and EXPected data differ by more than one bit:
EXP=177777, ACT=174777

2. The ACTual data contains more 1s than the EXPected data:
EXP=037777, ACT=077777

6-58
OFFLINE DIAGNOSTICS

3. The bit in error is not in the same bit position as the leftmost bit in the EXPected data:
EXP=001777, ACT=001377

•

Error 607-0ccurs in the moving inversions test (Section 6.7.7). A location was written with
a pattern. Immediately after the write, the location was read and found to contain an incorrect
pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACT is the data pattern ACTually found.

bit for that address probably is defective.
If the error occurs in many locations but only occurs in a particular nibble (four-bit field), one of

the bus data transceivers for that nibble probably is defective.
If the error occurs in many locations and the bits in error are randomly spaced throughout the word,

the memory or bus timing is probably the problem.
If the error occurs in more than one location but the addresses of the failing locations are similar,

crosstalk may be present between the memory data and addressing lines. For example, all failing
addresses end with either 2 or 6.

•

Error 60S-Occurs in the walking 1s test (Section 6.8.7). All locations in the memory under test
were written with the pattern 000000. Then all locations were read to check that they contained
000000. When the location specified in the error report was read, it did not contain 000000,
where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected (000000).

•

ACT is the data pattern ACTually found.

Because all locations were cleared to 00000o before this error was detected, a dual-addressing
problem is unlikely. More likely, a bit was picked up when the word was written or read.
If the error occurs repeatedly but only in one location, the memory chip containing the bit in error

for that address is probably marginal.
If the error occurs in many locations but always occurs in a particular nibble (four-bit field), one of

the bus data transceivers for that nibble probably is marginal.
If errors occur in many locations and the bits in error are randomly spaced throughout the words,

the memory or bus timing is probably marginal.

•

Error 609-Occurs in the walking Is test (Section 6.8.7). One location in the memory under test
was written with the pattern 177777 and all the other locations should contain the pattern 000000.
While reading to check that all other locations are clear, a location was found containing something
other than 000000, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected (000000).

•

ACT is the data pattern ACTually found.

6-59
OFFLINE DIAGNOSTICS

This error is either a data error or a dual-addressing error. (The location was incorrectly addressed
and written when some other location was being written.)
At this step of the test a dual-addressing failure is possible if the ACfual data is 177777. During
this part of the test, one location in the memory was written to 177777. When this write was
performed, the failing location may also have been addressed and written with the same data.
When the test was checking that all other locations were clear, it found the second location with
the pattern 177777. If this is a true dual-addressing problem, the error is repeated on each pass of
the test.
At this step of the test, a data error is probable if the ACfual data is not 177777. Some clues to
the possible causes of a data error follow.
If the error occurs repeatedly but only in a particular bit in a single location, the memory chip that

contains the failing bit for that location is defective.
If errors occur in many locations but only occur in a particular nibble (four-bit field), one of the

bus data transceivers for that nibble probably is marginal.
If errors occur in many locations and the bits in error are randomly spaced throughout the words,

the memory or bus timing is probably marginal.

•

Error OlO--Occurs in the walking Is test (Section 6.8.7). At this step of the test, one location
in the memory under test was set to the pattern 177777 and all other locations were cleared to
000000. Mter checking that all other locations contain 000000, the location that should contain
177777 was read. It contained some other pattern, where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected (177777).

•

ACT is the data pattern ACTually found.

Because only Read operations were performed after writing the 177777, a dual-addressing problem
is highly improbable.
If the error occurs repeatedly but only h'1 a pw.1:icular bit of a single location, the memory cJ1Jp that
holds that bit for the failing location is defective.
If errors occur in many locations but only occur in a particular nibble (four-bit field), one of the
bus data transceivers for that nibble probably is marginal.
If errors occur in many locations and the bits in error are randomly spaced throughout the words,

the memory or bus timing is probably marginal.
If errors occur in more than one location but the addresses of the failing locations are similar,

crosstalk may be present between the memory data and addressing lines. For example, all failing
addresses end in 2 or 4.

•

Error OIl-Indicates a parity trap occurred. The parity trap probably occurred in a location under
test but may have been caused by Program memory where the memory test itself resides. The MA
data in the error report indicates the address of the location causing the parity trap. Mter reporting
the parity trap, the memory test continues if the parity error occurred in a memory location under
test, where:
•

MA is the address of the location causing the parity trap.

•

VPC is the virtual PC of the memory test at the time the trap occurred. Reference this address
in the listing to locate the area of the test where the error occurred.

Because the data is lost when a parity trap occurs, no EXPected or ACfual data is displayed. To
further localize the problem, disable parity errors and rerun the test. (Refer to Section 6.7.5.)

6-60
OFFLINE DIAGNOSTICS

If the original failure was in a data bit position, the memory test detects and reports the error,
displaying the EXPected and ACfual data. This helps trace the error to a particular address and/or
bit position. If no further errors are detected after disabling parity errors, the original failure was in
one of the parity bits for the address displayed in the parity trap report.

Error OIl-Indicates a Non-Existent Memory (NXM) trap occurred. An NXM error is caused
when no memory responds to a particular address. The MA data in the error report identifies the
address that produced the NXM trap. After reporting the error, the program attempts to restart
testing from the beginning, where:
•

MA is the address being tested at the time the NXM trap occurred.

•

VPC is the PC of the memory test at the time the trap occurred. Reference this address in the
listing to locate the area of the test where the error occurred.

This error frequently occurs when trying to test beyond system memory addresses.
H this error occurs at a memory address that should be within your memory configuration, the
memory in question is not supplying an ACK to the I/O Control Processor when the specified
address is presented on the memory bus. The most probable point of failure is the logic on the
memory module that compares addresses on the Memory bus with the range of addresses to which
the module should respond. The comparator itself could be faulty or the [C IN, C OUTJ, [D IN, D
OUT1, or [P IN, P OUT1 lines on the backplane could be in error.

•

Error 013-Occurs in the quick verify test. This error may indicate a dual-addressing problem.
The quick verify test consists of clearing the entire memory. then writing two patterns to each
location and checking that the writes worked properly. Before writing the first pattern to each
location, the contents of the location should be O. Error 013 indicates a location contain something
besides a 0 before the first pattern was written.
H the ACTual data in the error report is 031463(8) or 146314(8), a dual-addressing problem
probably is the cause of the error. (When an address lower in memory was written with a test
pattern, the failing location also was written with the same pattern.) Dual-addressing problems are
normally caused by shorts between memory address bits.

If the ACfual data is other than 031463(8) or 146314(8), the problem probably is caused by a
memory bit or bits stuck in the 1 state. The first pattern written is 146314(8). The second pattern
written is the Is complement of the first pattern, 031463(8).

•

Error 014--0ccurs in the quick verify test. The MA in the error report shows the failing address.
The ACfual data shows the bit or bits that failed.

•

Error 015-0ccurs when an NXM trap occurs as the memory under test is initially being cleared.
The last address to test (operator-supplied) exceeds the amount of memory actually installed in the
HSC or part of the jem0§j under test is not responding. If the NXM occurs at an address that
should respond, use CTRUC or ICTRUVI to return to the offline loader. Use the loader's REPEAT
EXAMINE (address that caused trap) to set up a scope loop for isolating the problem.

•

Error 016-Cache parity trap, VPC = xxxxxx-Indicates the J11 took a trap through the parity
error vector during the run of the diagnostic, and the error was determined to be from the cache.
The virtual PC at the time of the trap is printed.

&-61
OFFLINE DIAGNOSTICS

6.8.7 Offline Memory Test Summaries
The following list describes the three algorithms used by the offline memory test.
•

Test 000, quick verify test-Quickly detects stuck bits and dual-addressing problems. The
algorithm used by the quick verify test is as follows:
Write 000000 to each location of the memory
FOR i = First to Last address
IF < location i does not contain 0 >
THEN < display error >
Write test ~attern to location i

(146314(8»

IF < location i does not contain pattern >
THEN < display error >
Write complement of pattern to location i

(031463(8»

IF < location i does not contain complement >
THEN < display error >
NEXT i

•

Test 001, moving inversions test-Detects data and addressing problems in dynamic
semiconductor memories.
The moving inversions algorithm performs the following:
1. Writes 000000 in each location of the memory.
2. Reads all locations in order from lowest to highest. Mter reading a location and checking for
a O. rewrites the same location with a single 1 in the least-significant bit. Then rereads the
location and veri-fiesthe write worked eorreetly.

3. Again reads all locations in order from lowest to highest. Checks that each location contains
the data previously written. Rewrites the data found with a single additional 1 bit. Rereads it
to verify the Write operation worked properly.
4. Repeats step 3 until the test pattern consists of a word containing all Is (pattern 177777).
5. Repeats step 3 but this time substitutes a single extra 0 each time instead of a 1.
6. Continues step 5 until the test pattern consists of a word of all Os (pattern 000(00).
7. Repeats steps 1 through 6 but this time starts at the highest memory address each time and
works down to the lowest. This works each memory location from aliOs to all Is and back to
all Os.
8. Clears all memory to 000000.
•

Test 002, walking Is test-An algorithm that stresses semiconductor memories and is effective in
locating timing problems on the memory module or on the bus.
The walking Is algorithm performs the following:
1. Writes all memory to Os (pattern = 000(00).
2. Checks all memory for Os. Declares error 008 if not O.
3. Sets TESTADDRESS equal to the first address to test.
4. Writes 177777 to contents of TESTADDRESS.
5. Checks that all other locations are equal to 000000. Declares an error 009 if not equal to
000000.
6. Checks that TESTADDRESS contains 177777. Declares an error 010 if not equal to 177777.

6-62
OFFLINE DIAGNOSTICS

7. Writes 000000 to contents of TESTADDRESS.
8. IF TESTADDRESS is the last address to be tested. testing is complete. If TESTADDRESS is
not the last address to be tested, 2 will be added to TESTADDRESS and the process will go
back to step 4. This will continue until TESTADDRESS is the last address to be tested.

6.9 RX33 OFFLINE EXERCISER
OFLRXE is a combined hardware diagnostic and exerciser for the HSC70 M.std2/RX33 subsystem.
Diagnosis of the DMA hardware and diskette controller are provided, as well as a read/write exerciser
to provide exercise for the actual drive portion of the subsystem. OFLRXE is a stand-alone diagnostic
running under the offline diagnostic loader. This loader provides tenninal I/O service, time keeping,
string conversions, and interrupt handling. OFLRXE is an 8 Kword program of which approximately
half is control code and half is mapped for Data Buffer transfers.

6.9.1 RX33 Offline Exerciser System Requirements
This test must have alii P.ioj module and a M.std2 memory/controller board. At least one RX33 drive
must be present. One scratch diskette is needed for each drive to be tested (maximum of two).
Testing of the entire 111 chip set and the 111 cache is assumed if it is turned on. Two tested 4 Kword
partitions of memory are required by OFLRXE.

6.9.2 RX33 Offline Exerciser Operating Instructions
If the HSC70 is not booted and loaded, refer to Section 6.1.2, Section 6.1.3, and Section 6.2. H the

HSC70 is already booted and displaying the offline loader prompt ODL>, proceed as follows:
At the ODL> prompt, invoke the offline RX33 diagnostic by typing TEST RX /RETURN/. This loads
the offline RX33 diagnostic (OFLRXE) from the media, and transfers control to the diagnostic. At the
start, the diagnostic should print out the following string:
HSC70 Offline RX33 Exerciser Vxxx

Where Vxxx is a three-digit version/edit number.
NOTE

If unable to boot from drive 0, move the diskette to drive 1, try again, or use a backup copy of
the offline diagnostics diskette.
The offline RX33 exerciser tenninates on ICTRucllcTRUVI, or on expiration of the allotted time. The
program also terminates on fatal errors.

6.9.3 RX33 Offline Exerciser Parameter Entry
Following are the three user-modifiable parameters for this test.
I. Drive selection is prompted for by the program in the following manner:
Test drive n (YIN)

[Y] ?

Where n is the drive number (0 or 1). The default is yes. The prompt repeats for each available
diskette on the HSC70.
2. Operator is asked if initial Write operation should be performed:
Perform initial write on this drive (YIN)

(YJ ?

The default is yes. This lays down a background pattern on the entire disk in preparation for the
random read/write exerciser. Selecting this option adds 10 minutes of test time per drive.

6-63
OFFLINE DIAGNOSTICS

As soon as the previous prompts have been answered, the program directs placement of a scratch
diskette in the selected drive:
Insert a scratch diskette in the drive, type a carriage return to continue.

At this point, insert the scratch diskette. The random read/write exercise takes place over the entire
surface of the diskette, so be sure the diskette is a scratch one only to be used for the exercise.
3. Run time of the exerciser is user-selectable and is prompted for by the program as follows:
i of minutes to exercise (D)

[30] ?

Enter a number between 1 and 32767. The default. if the user types just a carriage return, is 30
minutes. This 30 minutes starts after the initial patterning of the disk (if selected) so the total test
time with two drives and initial patterning is amount of time selected plus 20 minutes. A value of
1440 minutes gives a 24-hour run time for bum-in purposes. The 30-minute default is sufficient for
installation use and repair verification.
At the end of the amount of time allotted for the exerciser, the program prompts the user by printing:
Reuse parameters (YIN)

[Y] ?

Answering this projPt wi, Y IRETURN I allows the diagnostic to run again with the same parameters.
Answering with N RETURN takes the process back through the parameter entry questions again.

6.9.4 RX33 Offline Exerciser Progress Reports
The offline RX33 exerciser does not run in a conventional pass sense. There are no pass completed
messages. Instead, some informational messages are printed indicating what the exerciser is currently
doing. At the end of the initial write test (if selected), the exerciser prints:
Initial write completed on drive

OOOn

Where n is the drive number (0 or 1).
When the exerciser begins the random read/write phase of the testing, the following message is printed:
Beginning random exerciser

The random exerciser is now in progress. It runs for the amount of time requested by the user. Wben
the requested time has expired, the program prints the following string:
Exerciser completed.

The program then returns to the parameter entry routine.
The program also has a user-requested status report available. If at any time the user types ICTRUTI on
the console, the program responds:
Number of sectors transferred = xxxxxxxxxx, yyyyyy errors.

Where:
•

xxxxxxxx is a 16-digit number of sectors successfully transferred.

•

yyyyyy is a 6-digit cumulative number of errors detected.

6-64
OFFLINE DIAGNOSTICS

6.9.5 RX33 Offline Exerciser Error Information
A generic message fonnat for all offline diagnostic errors is found in Section 0.1.5. The fol1owing
section contains infonnation on specific errors associated with RX33 offline exerciser. A typical RX33
offline exerciser error message is:
OFLRXE>52:22 T 008 E 010.D 001
SEEK error detected during positioning operation
LBN = 004356.
Track = 000114
Sector =000007
Surface = 00000

Soft errors, such as seek errors, can build up to a point where a diagnostic defines them as fatal and
terminates on a fatal error. The internal bias for soft errors is currently set to 20. When this nwnber is
exceeded, the exerciser detennines the errors are fatal and tenninates.
6.9.5.1 Specific RX33 Offline Exerciser Error Messages
The following is a list of errors associated with test failures.

•

Error 00, parity trap, VPC = xxxxxx-Applicable to all tests. Occurs at any time during
execution of the diagnostic. The virtual PC on the stack is printed to help identify the program
area where the error occurred. Both the content of the error address register and the virtual PC
are displayed as optional lines. This error tenninates the test. The diagnostic returns to the reuse
parameters prompt.
Error 0, NXM trap, VPC = xxxxxx-Applicable to all tests. Causes the diagnostic to return
to the reuse parameters prompt. Additional data, such as the virtual PC of the instruction which
caused the trap, and the physical address contained in the error address register are printed as
optional lines.

•

Error 02, bit stuck in register-Applicable to test 1. Indicates a stuck-at fault is present in one
of the RX33 control registers. The register address and the EXPected and ACTual data are printed
as optional lines in the error message. If the error is in the low byte, the problem is the diskette
controller chip. If the error is in the high byte. the problem is with the MAR register at that
address. If more than one register show the same bit(s) in error, the problem is probably in the bus
transceivers.

•

Error 03, interrupt occurred without enable set-ApplicabJe to test 2. Indicates there is a stuckat fault in the register, or the etch going into the DCOO3 interrupt control chip. The interrupt enable
bit, <13> of the CSR, does not disable interrupts.

•

Error 04, RX33 interrupt occurred at wrong priority-Applicable to test 2. Indicates the RX33
interrupt occurred with the priority at five or greater. The virtual PC where the interrupt occurred
is printed out as an optional line. Using the listing of the program, the priority at the lime of the
interrupt can be detennined.

•

Error 05, unexpected interrupt from RX33-Applicable to all tests. Indicates an unexpected
interrupt. An interrupt that occurs at any time when a command to the RX33 is not in progress is
defined as unexpected. The virtual PC where the interrupt occurred is printed as an optional liue.

•

Error 06, track 0 did not set after RECALIBRATE command-Applicable to test 5. Indicates
the track 0 status bit (bit 2 of the CSR) did not set upon completion of a RECALIBRATE
command. The drive may not be sending the signal or the cable to the drive may be faulty.

•

Error 07, RX33 did not interrupt as expected-Applicable to test 2. Indicates an expected
interrupt never occurred. The interrupt control chip (DC003) may be at fault, or the diskette
controller chip interrupt signal is stuck at 1. The J 11 may be unable to recognize interrupts from
the diskette controller or the backplane etches carrying interrupt control signals are open.

OFFLINE DIAGNOSTICS

•

Error 10, seek error detected during positioning operation-Applicable to tests 5, 6, 7, and
8. Indicates a seek error status (bit 4 of the CSR) was set after a SEEK or RECALIBRATE
command. The problem may be in the diskette controller chip or the diskette. IT the errors are
occurring mostly in test 5 starting with track 0, the problem probably is foodamental; the controller
cannot read the diskette at all. If the errors occur in a random fashion, the problem probably is the
diskette.

•

Error 11, current track register incorrect-Applicable to tests 5 and 6. Indicates the values in
the track register of the diskette controller chip are not as expected after a given operation. This
problem probably is in the diskette controller chip.

•

Error 12, CRC error in header detected during position verify-Applicable to tests 5, 6, 7, and
8. Detects a eRC error when reading a header during a position verify. This error occurs when a
valid header has been found and read, but the CRe at the end is incorrect. This probably is the
diskette. IT the controller is able to detect the address and data marks that precede a header (so that
it knows that a header is being read), the data separation logic probably is working.

•

Error 13, processor type is not JII-Applicable to test 0. Does not contain the value which
defines a J 11. This error causes the diagnostic to terminate.

•

Error 14, drive under test is not ready-Applicable to tests 5, 6, 7, and 8. Indicates the diskette
drive is sending NOT READY status to the controller. The door may open on the drive, or no
diskette is inserted. If these conditions are not the cause of the fault, the ready signal from the
drive may be stuck.

•

Error 15, last command did not complete-Applicable to tests 5, 6, 7, and 8. Indicates the last
command issued to the diskette controller never interrupted to show completion. This error points
to the diskette chip since it occurs after the interrupt logic has already been tested.

•

Error 16, RX33 header does not compare-Applicable to tests 7 and 8. The header information
written in the data area of a sector is not what it should be for that sector and side, written as part
of the data in that sector. This error happens when an undetected positioning error has occurred,
either during the read or the write of the sector involved. The LBN, track, sector, and side are
displayed as optional lines.

•

Error 17, record not found during read (could- also say write)-Applicable to tests 7 and 8.
Indicates the controller was ooable to find that sector on the current track when attempting to read
or write a given sector. Either a misposition occurred, or that sector is unreadable. Because this
error occurs after basic read capability has been tested, the most probable culprit is the diskette,
with the diskette chip being the next most probable problem point. The LBN, track, sector, and
side are displayed as optional lines.

•

Error 20, CRC error in data during read (could also say write)-Applicable to tests 7 and 8.
Indicates the controller detected a eRC error when reading the desired sector. IT the error occurs
multiple times in a row for a given sector, the problem is most likely the diskette (or the drive it is
installed in). Single errors when an LBN has this error only once are soft errors. The LBN, track,
sector, and side information is printed as optional lines.
Error 21, lost data detected during read (could also say write)-Applicable to tests 7 and 8.
Indicates the DMA logic did not service an I/O request of the diskette controller chip in time.
There are probably problems in the DMA logic, or stuck-at faults exist in the etch between the
controller chip and the DMA logic.

•

Error 23, invalid pattern code in buffer-Applicable to test 8. Indicates the data word, defined
as the pattern code, read from the diskette does not match any of the possible patterns used. It is
unlikely the data was read incorrectly from the diskette and not detected as a CRe error. Usually
this error occurs when a diskette is not written with the initial data pattern. The LBN, track, sector,
and side are displayed as optional lines.

6-66
OFFLINE DIAGNOSTICS

•

Error 24, drive is write-protected-Applicable to tests 7 and 8. Indicates the drive is sending
write protect status. Either the interface is bad, or the drive is in error (assuming there is not a
write-protected diskette in the drive). This error terminates the diagnostic, as a write-protected
diskette cannot be written on.

•

Error 25, eRe error in header during read (could also say write)-Applicable to tests 7 and
8. Indicates the controller detected bad CRC in the header it was reading as part of a data transfer
command. This probably is a diskette error. The LBN, track, sector, and side are displayed as
optional lines.

•

Error 26, data incorrect after DMA TEST MODE command-Applicable to tests 3 and 4.
Indicates the memory content after a DMA test mode command was not correct. There are either
stuck-at faults in the DMA registers, or the transfer did not happen at all (that is, the memory
is unchanged). This is a fundamental error in the diskette logic; the diagnostic terminates after
detecting it.
Error 27, data compare error-Applicable to tests 7 and 8. Indicates a manual check of data
read by the diskette turned up an error. Either the transfer did not complete, an intermittent error
occurred in the data or address path, or what was written on the disk was written incorrectly. The
LBN, track, sector, and side are displayed as optional lines.
Error 30, RX33 detected parity error during read (could also say write)-Applicable to tests 7
and 8. Indicates the RX33 detected a parity error when doing a DMA read from memory. Either
Program memory is bad or the parity logic on the controller is in error.

•

Error 31, RX33 detected NXM during read (could also say write)-Applicable to tests 7 and
8. Indicates the RX33 detected a NXM during a DMA operation. Either the DMA address was
loaded wrong and pointed to a nonexistent location, or the handshake logic on the M.std2 board is
in error.

•

Error 32, RX33 MAR value incorrect after DMA transfer-Applicable to test 3. Indicates
the value of the MAR address counters was in error after a DMA test operation. The problem is
probably in the counters or the etch associated with them. The EXPected and ACTual data are
printed out as optional lines.

•

Error 33, parity error was not forced in main memory-Applicable to test 4. Indicates a write
to Program memory with bad parity set (bit 11 of the CSR) did not result in bad parity in memory.
There is either a stuck-at fault in the parity logic or the operation never wrote memory in the first
place.

•

Error 34, parity error did not set in eSR-Applicable to test 4. Indicates a DMA read of a
location with known bad parity did not set the parity error bit (bit 15 of the CSR). Either the data
was never read or there is a stuck-at fault in the parity logic.

•

Error 35, NXM did not set in eSR-Applicable to test 4. Indicates a DMA read of a location
expected to give a NXM did not set NXM in the CSR. Look for stuck-at faults in the NXM
detection logic.

•

Error 36, parity error set along with NXM in eSR-Applicable to test 4. Indicates both the
parity error ~d the NXM error set simultaneously in the CSR. On a NXM error, the parity error
should not set. Check for stuck-at faults in the NXM/parity error logic.

•

Error '37, cache parity error, vpe = xxxxxx-Applicable to all tests. Indicates the JI1 took a
trap through the parity error vector, a cache error during the run of the diagnostic. The virtual PC
at the time of the trap is printed.

fr67
OFFLINE DIAGNOSTICS

6.9.6 RX33 Offline Exerciser Test Summaries
The following is a summary of RX33 offline tests.
•

Test 1, RX33 controller registers-Performs stuck-at testing on the RX33 controller registers at
17777400, 17777402, 17777404, and 17777406. A simple walking 18 test is performed on each
register, except for the CSR register at 177400 which only has the high byte tested.

•

Test 2, interrupt hardware--Exercises the interrupt hardware on the M.std2. The interrupts
generated are also tested for the correct priority when they occur.

•

Test 3, DMA logic and counters-Checks out all of the DMA handshake signals, the data path,
and the address path. A special DMA test mode in the controller is used to perform one read or
write to/from each memory location loaded in the DMA address registers. Correct incrementing
action from the counters is checked. The ACTual data loaded to memory on a DMA write is
checked as well.

Test 4, parity logic-Also uses DMA test mode in addition to the force bad parity function (bit
11 of the CSR) to prove parity errors can be detected, and correct parity is written to memory by
the DMA control logic. NXM action also is lwnped into this test. Correct handling of NXM errors
and correct reporting by the error bit in the CSR is checked.

•

Test 5, verify track counters and registers-Uses the step function of the diskette controller
chip to verify that all cases of the track counter bits internal to the diskette controller chip work
as advertised. Step functions are performed for each power of two in the diskette track register
(step four times, step eight times more, etc.). The verify option is set on each step command so the
diskette controller reads headers on each track to verify position.

•

Test 6, oscillating seek test-Performs an oscillating seek test using the algorithm:
oscillating seek test
begin
incnt = 0
outcnt = 124
while incnt<> outcnt do
begin
seek outcnt;
CHECK_STATUS;
If outcnt <> rxtrk then error 11
outcnt =outcnt-l;
seek incnt;
CHECK_STATUS;
if incnt <> rxtrk then error 11
incnt =incnt + 1;
end;
end { oscillating seek test.

In this manner, all seeks are performed in both directions with all seek counts between <0:77>.
Verification is performed on each track to check the step logic.
•

Test 7, sequential read/write test-Performs the basic patterning of the diskette with a background
pattern. This test is user-selected. If selected, this test writes each LBN on the RX33 diskette in
ascending order with a unique pattern consisting of the track, sector, and side of that LBN, and
then an incrementing-byte pattern for the remainder of the 512-byte sector. Each LBN so written is
then read back, and each word is compared to the data that was written. This test takes about 10
minutes per drive.

•

Test 8, random reads/writes-Does random reads and writes to the selected drives. If both drives
are selected for test, operations on each drive are performed in groups of five.
This test runs until the allotted time for the exercise expires, or the user terminates the test with

I CTRUCI. The mechanism of this test is as follows:

6-68
OFFLINE DIAGNOSTICS

A random number is generated. The value of this number determines if the operation is a read or a
write, and which LBN is used.
If the command is a read, the appropriate LBN is read from the disk. The header bytes (0:5) of

the data read are then compared against the values expected. The pattern number bytes (6:7) are
then compared against a list to see which pattern should be used to compare the rest of the buffer
(10:512).
If the command is a write, other bits of the random number are used to select one of four different

patterns to write to the disk. A buffer is then set up with the correct header bytes for the LBN to
be written and the correct background data pattern. This buffer is then written out on the diskette.
Descriptions of the data patterns used are found in the following section.

6.9.7 RX33 Offline Exerciser Data Patterns
Four unique data patterns were selected to give maximum delta of frequency with the modified
frequency modulation (MFM) encoding used on the RX33. These patterns are as follows:
PATTERN NUMBER I PATTERN VALUE
177400
11111
22222
33333
44444

Incrementing by bytes starting at 2404
1000101110001011 binary, 105613 octal
0011001100110011 binary, 031463 octal
0011000010010001 binary, 030221 octal
0000101110001011 binary, 005613 octal

6.10 OFFLINE REFRESH TEST
The offline memory refresh test finds memory problems related to refresh. Patterns are written to
memory and then checked after waiting one minute. Three separate patterns are used to test each
memory bit (including parity bits) in both the 1 and 0 states. All three HSC memories are tested
(Program. Control, and Data), although only the Program and Control memories require refreshing.
Tests of Data memory are included because some static RAM failures resemble refresh problems.
The refresh test can find problems in the memories not detected by the nonnal memory tests. The
refresh test is not intended to be run on memories that fail the normal memory tests.

6.10.1 Offline Refresh Test System Requirements
The following hardware is required to run this diagnostic:
•

I/O Control Processor module with HSC boot ROMs

•

At least one memory module that passes the offline memory test and/or the offline KIP memory
test

•

HSC load device with at least one working drive

•

Terminal connected to I/O Control Processor console interface

This test assumes the HSC memories pass both the offline memory test and the offline KIP memory
test. In addition, the test assumes the memories are working except for the refresh circuitry.

6-69
OFFLINE DIAGNOSTICS

6.10.2 Offline Refresh Test Operating Instructions
If the HSC is not booted and loaded, refer to Section 6.1.2, Section 6.].3. and Section 6.2. If the HSC
is already booted and displaying the offline loader prompt ODL>, proceed as follows:
L Type TEST REFRESH IRETURN! in response to the prompt OI?L>.
2. The refresh test indicates it is loaded properly by displaying the following:
HSC OFL Memory Refresh Test

3. The refresh test now prompts for parameters. Refer to Section 6.10.3 for test parameter entries.

6.10.3 Offline Refresh Test Parameter Entry
This section describes the prompts for the offline refresh test parameters.
NOTE

For any of the offline refresh test prompts, use the DELete key to delete mistyped parameters
before typing IRETURNL If an error in a parameter already terminated with IRETURNI is noted, type
ICTRucl to return to the initial prompt and re-enter all parameters.
The offline memory refresh test first prompts:
I of passes to perform (D)

[1] ?

Enter a decimal number between I and 2,147,483,647 (omitting commas) to specify the number of
times the refresh test should be repeated. (Entering a 0 or just a carriage return results in one pass.)
After selection of the number of passes the test begins. The test can be aborted at any time by typing
I CTRUC I. Each pass of the test requires three minutes to complete.
After· the refresh t-est completes, t-he -f-oHowin:g· prompt is· issued:
Reuse parameters (YIN)

[Y] ?

Answering this prompt with IRETURN! or a Y !RETURN! repeats the test using the same parameters.
Answering the prompt with N IRETURNI causes a prompt for new parameters.

6.10.4 Offline Refresh Test Progress Reports
Each time the refresh test completes one full pass, an end-of-pass report is displayed. Each pass of the
test requires three minutes to complete. The end-of-pass message is displayed as follows:
End of Pass nnnnnn, xxxxxx Errors, yyyyyy Total errors

Where:
•

nnnnnn is a decimal count of the number of complete passes made.
xxxxxx indicates the number of errors detected on the current pass.

•

yyyyyy indicates the number of errors detected during the passes completed so far.

6-70
OFFLINE DIAGNOSTICS

6.10.5 Offline Refresh Test Error Information
All error messages produced by the refresh test conform to the HSC diagnostic error message format
(refer to Section 6.1.5). Following is a typical offline refresh error message.

ORFT>hh:mm T
aaa E
bbb
<Text describing error>
MA -xxxxxxxx

EXP-yyyyyy
ACT-zzzzzz

Where:
•

MA is the address of the failing location.

•

EXP is the data pattern EXPected.

•

ACf is the data pattern ACTually found.

6.10.5.1 Messages
The following list describes the nature of the failure indicated by each error number.

•

Error Ol-Indicates the test detected a parity error when reading the pattern from the indicated
location. The EXPected and ACTual data are included in the error report. This error indicates
a data bit or parity bit was not refreshed (assuming the memory in question passed the offline
memory test). If the EXPected and ACfual data are the same, one of the parity bits was not
refreshed.

•

Error 02-Indicates the test detected a data compare error when reading the pattern from the
indicated location. The EXPected and ACfual data are displayed in the error report. Note, a parity
error did not occur so more than one bit must have failed to refresh.

•

Error 03-Indicates the I/O Control Processor detected a parity error. The 22-bit address of the
location that caused the trap is displayed as the MA data in the error report, where:
•

MA is the address causing the parity trap.

•

VPC is the virtual PC of the memory test at the time the trap occurred. Reference this address
in the listing to locate the area of the test where the error occurred.

Because the data is lost when a parity trap occurs, no EXPected or ACfual data can be displayed.
The parity error occurred within the program itself not within the memory being tested. After the
trap is reported, the program attempts to restart the test from the beginning.

•

Error 04-Indicates the I/O Control Processor detected a NXM trap. An NXM error is caused
when no memory responds to a particular address. The MA data in the error report indicates the
address that produced the NXM trap. After the trap is reported, the program attempts to restart the
test from the beginning. (The MA and VPC fields have the same meanings as those in error 03.)
If this error is at a memory address that should be in the memory configuration, the memory in
question is not supplying an ACK to the I/O Control Processor when the specified address is
presented on the Memory bus. The most probable point of failure is the logic on the memory
module that compares addresses on the Memory bus with the range of addresses to which the
module should respond. The comparator itself could be faulty or the [C IN, C OUT]. [D IN, 0
OUT], or [P IN, P OUT] lines on the backplane could be in error.

•

Error 05, cache parity trap, VCP = xxxxxx-Indicates the Jl1 took a trap through the parity
error vector during the run of the diagnostic. This is a cache error. The virtual PC at the time of
the trap is printed.

6-71
OFFLINE DIAGNOSTICS

6.10.6 Offline Memory Refresh Test Summaries
The following are the test summaries for the offline memory refresh test.
•

Test 01, pattern 177777-Fills the memories with the pattern 177777. This sets aU data bits and
aiso sets the upper and lower byte parity bits. The entire Control and Data memories are fined
with the pattern. All of Program memory not occupied by the refresh test and the offline loader
is also filled with the pattern. Mter filling the memories, the program delays for one minute, then
each memory location is read and checked for the pattern. Any errors detected are reported on the
terminal.
Test 02, pattern OOOOOO-Fills the memories with the pattern 000000. This clears all data hits and
sets the upper and lower byte parity bits. The entire Control and Data memories are filled with the
pattern. All of Program memory not occupied by the refresh test and the offline loader is also filled
with the pattern. Mter filling the memories, the program delays for one minute, then each memory
location is read and checked for the pattern. Any errors detected are reported on the terminal.

•

Test 03, pattern 100OOl-Fills the memories with the pattern 100001. This sets data bils 0 and 15
and clears data bits 1 through 14. Both parity bits are also cleared. The entire Control and Data
memories are filled with the pattern. All of Program memory not occupied by the refresh test and
the offline loader is also filled with the pattern. Mter filling the memories, the program delays for
one minute, then each memory location is read and checked for the pattern. Any errors detected
are reported on the terminal.

6.11

OFFLINE OPERATOR CONTROL PANEL (OCP) TEST

The oCP test checks the operation of the HSC lamps and switches. Testing includes the five OCP
lamps and switches, the State LED, Secure/Enable switch, and the enable LED.
This section includes troubleshooting procedures for localizing faults detected by this test.

6.11.1 Offline OCP Test System Requirements
The following hardware is required to run this test:

•

I/O Control Processor module with HSC boot ROMs
At least one memory module

•

HSC load device with at least one working drive

•

Terminal connected to I/O Control Processor console interface

•

OCP

Due to the sequence of tests that precede this test, it is safe to assume the I/O Control Processor
module, Program memory, and HSC load device are tested and working.

6.11.2 Offline OCP Test Operating Instructions
IT the HSC is not booted and loaded, refer to Section 6.1.2, Section 6.1.3, and Section 6.2. IT the HSC
is already booted and displaying the offline loader prompt ODL>, proceed as follows:
Type TEST OCP IRETURN I in response to the ODL> prompt. The HSC load device in motion LED
should be ON.
The test indicates it is loaded properly by displaying the following message:
HSC OFL OCP Test

The lest then prompts for parameters. Refer to Section 6.11.3 for test parameter entry.

6-72
OFFLINE DIAGNOSTICS

6.11.3 Offline OCP Test Parameter Entry
The test first checks the position of the SecurelEnahle switch via a hit in the 1/0 Control Processor
control and status register (address 17770040). If the switch is in the SECURE position, the following
prompt is issued. Otherwise, the test skips to the next prompt.
Put Secure/Enable switch into ENABLE position

If the Secure/Enable switch is in the ENABLE position and the above prompt is issued anyway, a
problem is indicated with the bit in the I/O Control Processor CSR that monitors the Secure/Enable
switch. Refer to the troubleshooting procedures in Section 6.11.6. The program waits until the
Secure/Enable switch is changed to the ENABLE position and issues the following message:
(Enable LED should be lit, State LED should be blinking)

Check to verify the enable LED is lit and the OCP State LED is blinking. There are two State LEDs:
one is to the left of the Init switch on the HSC OCP, and the other is located on the I/O Control
Processor module (the fourth LED from the bottom of the rightmost module in the HSC card cage).
If either LED is not blinking, refer to the troubleshooting procedures in Section 6.11.6. The test next
prompts for a lamp test.
Press Fault (all OCP lamps should light)

(Y/N)

[Y] ?

Press the fault lamp and observe that all OCP lamps light. If none of the lamps light, a problem may
be present in the lamp test logic on the OCP assembly. If all lamps light properly, type a carriage
return to continue the test. If the lamp test fails, replace the OCP.
Next, the program checks that all OCP switches are OFF (out position). If any switch bits in the
I/O Control Processor switch/display register read as Is (ON), the program lights the lamps for those
switches and prompts:
Put all lit switches in OFF (out) position (Y/N)

[Y] ?

If the fault or Init lamps are lit (nonlocking switches), a problem exists with the wiring in those
switches or with their respective bits in the switch/display register. Replace the OCP.

Otherwise, press all lit switches to release their locks and type a carriage return. If the message
repeats and one or more lamps remain lit even though the switches are OFF (out position), refer to the
troubleshooting procedures in Section 6.11.6.
The program then tests each of the OCP switches, one at a time. A switch lights and the following
prompt is displayed:
Press and release the lit switch

Press the switch that is lit. The program allows about one second for the switch to be released after
it is pressed and then continues to the next prompt. If the program fails to respond when a switch is
pressed, refer to the troubleshooting procedures in Section 6.11.6. For those switches that lock in the
ON position (online switch and the two unmarked switches), the program prompts:
Press and release the lit switch again

Press the switch again to return it to the OFF (out) position. If the online switch or either of the
unmarked switches fails to lock in the ON position, the switch is defective, and the OCP should be
replaced.
After the OCP switch tests are complete, several features of the Secure/Enable switch are tested. The
program begins these tests by prompting:
Put Secure/Enable switch into SECURE position

6-73
OFFLINE DIAGNOSTICS

The program waits until the Secure/Enable switch is in the proper position before continuing. If
the program fails to respond when the switch is moved to the SECURE position, refer to the
troubleshooting procedures in Section 6.11.6. Wnen the program detects the switch is in the SECURE
position, it prompts with:
(Enable LED should turn off)

Ensure the enable LED is off. If this LED fails to turn off when the switch is in the SECURE position,
a short or wiring problem is probable.
Next, the program prompts:
Press Init (HSC should not re-boot)

(Y/N)

[Y] ?

Press the Init switch. When the Secure/Enable switch is in the SECURE position, pressing the Init
switch should have no effect. (Do not press any other switch or an error message results.) If the HSC
starts to perform a bootstrap (Init lamp turns on and green LED on I/O Control Processor turns off),
the Secure/Enable switch is not disabling the action of the Init switch. After pressing the Init switch,
type IRETURN I to continue. The test responds with the following prompt:
Press terminal IB~AKI key (HSC should not halt)

(Y/N)

[Y] ?

Press the IBREAKI key as directed. When in SECURE mode, the IBREAKI key should not cause the
Jll/Fll processor to halt (enter ODT). If the terminal displjYS the @ character when IBREAKI is pressed,
the Secure/Enable switch is not disabling the action of the BREAK key. Refer to the troubleshooting

procedures in Section 6.11.6. Mter pressing the IBREAKI key, type I RETURN I to continue the test. The
final prompt of the test is:
Put Secure/Enable switch into ENABLE position.

The test waits until the Secure/Enable switch is returned to the ENABLE position. At that point the
test terminates and returns to the offline loader.
The test may be aborted at any time by typing ICTRucl.

6.11.4 Offline OCP Test Error Information
All error messages produced by this test conform to the HSC diagnostic error message format (refer to
Section 6.1.5). Listed below is a typical offline OCP test error message format.
OOCP>hh:mm T # aaa E # bbb
<Text describing error>
MA - xxxxxxxx

EXP-yyyyyy
ACT-zzzzzz

6.11.4.1 Messages

The following list describes the nature of the failure indicated by each error number.

•

Error 000, wrong bit set-Occurs when the test detects a switch bit other than the switch bit
being tested set in the I/O Control Processor switch/display register. This error can be caused by:
The operator pressing the wrong switch.
A short causing an additional switch bit to set along with the expected bit.
A wiring error causing the wrong bit to set when a switch is pressed.
The media address (MA) field of the error report gives the address of the I/O Control Processor
switch/display register. The EXPected and ACTual data in the error report show the switch bit the
program expected to find set and the bit or bits that actually were set.

6-74
OFFLINE DIAGNOSTICS

If the EXPected and ACfual data each consist of only one bit, the failure was caused by either
the operator pressing the wrong switch or by a wiring error. H the ACTual data consists of two
or more set bits, a short between switches is likely. Refer to the troubleshooting procedures in
Section 6.11.6.

•

Error 001, bit set when InU is pressed-Occurs when the Init switch is pressed while the HSC is
in the SECURE mode (test 008). This error can be caused by one of the following:
-

Pressing some switch other than the Init switch.

Pressing the Imt switch, causing a switch bit in the I/O Control Processor switch/display
register to set.

The media address (MA) field of the error report gives the address of the I/O Control Processor
switch display register. The EXPected data is always 0 (no bit is expected to set). The ACTual data
shows the bit or bits that read as a 1 when the Init switch was pressed. Refer to the troubleshooting
procedures in Section 6.11.6.

6.11.5 Offline OCP Test Summaries
The following sections summarize test 000 through test 009.
•

Test 000, observe enable and State LEDs-Performed by the operator, because the program
cannot tell whether the enable or State LEDs are lit. If the enable LED is off, a wiring problem
nlay be the cause (LED not connected to power/ground source) or the LED itself may be faulty.
If the State LED on the OCP fails to blink, check the State LED on the I/O Control Processor
module (fourth LED from the bottom of the rightmost module in the HSC card cage). If neither
State LED is blinking, the problem probably is caused by the bit in the I/O Control Processor CSR
register that controls the State LED (refer to Section 6.11.6.4). H one of the State LEOs is blinking
but the other is not, the nonblinking LED probably is wired wrong or is faulty.

•

Test 001, lamp test via Fault switch-Performs an automatic lamp test. When the Fault switch is
pressed, all lamps should light and remain lit until the switch is released.
If none of the lamps light when the Fault switch is pressed. the problem is probably in the lamp
test circuitry on the OCP assembly. It is possible all lamps are defective or they are not installed.
Replace the OCP.

H some lamps light when fault is pressed but others do not, replace the OCP.
•

Test 002, check all switches OFF-Reads the I/O Control Processor switch/display register to see
if any of the switch bits read as ON (switch bit is a 1). H the bit for any switch reads as ON, the
corresponding lamp is lit and the program prompts to turn off any switch that is lit. The program
will not proceed until all switch bits read as OFF.
H a lamp remains ON, even though the corresponding switch is OFF (out position). the switch

is either wired incorrectly or the bit in the I/O Control Processor switch/display register for that
switch is faulty. Refer to Section 6.11.6.1 to localize the problem.

•

Test 003, Fault switch-Directs pressing the lit switch. The program then monitors the switch bits
in the I/O Control Processor switCh/display register and waits for the Fault switch bit to set. If any
other switch bit sets, an error is reported and the program terminates.
H pressing the Fault switch has no effect, one of the following could be the cause:
-

Fault switch is broken.

Fault switch is not wired properly.

Fault switch bit in the I/O Control Processor CSR cannot be set.

6-75

OFFLINE DIAGNOSTICS

Refer to the troubleshooting procedures in Section 6.11.6.
If pressing the Fault switch results in an error message, refer to Section 6.11.4.1.

•

Test 004, Online switch-Directs pressing the lit switch. The program then monitors the switch
bits in the I/O Control Processor switch/display register and waits for the Online switch bit to set.
H any other switch bit sets, an error is reported and the program is terminated.
After the Online switch bit sets in the I/O Control Processor switch/display register, the program
directs pressing the lit switch as the next step. This returns it to the OFF (out) position. The
program then waits until the switch bit reads OFF (0) before proceeding to the next test.
H pressing the Online switch has no effect, one of the following could be the cause:

Online switch is broken.
Online switch is not properly wired.
Online switch bit in the I/O Control Processor CSR cannot be set.
Refer to the troubleshooting procedures in Section 6.11.6.
If pressing the Online switch results in an error message, refer to Section 6.11.4.1.

•

Test 005, first unmarked switch-Directs pressing the lit switch. The program then monitors the
switch bits in the I/O Control Processor switch/display register and waits for the first unmarked
switch bit to set. If any other switch bit sets, an error is reported and the program is terminated.
Mter the first unmarked switch bit sets in the I/O Control Processor switch/display register, the
program directs pressing the lit switch as the next step. This returns it to the OFF (out) position.
The program then waits until the switch bit reads OFF (0) before proceeding to the next test.
H pressing the first unmarked switc-h has no effect, one of the following could be the cause:

First unmarked switch is broken.
First unmarked switch is not wired properly.
First unmarked switch bit in the UO Controi Processor CSR Call1lot be set.
Refer to the troubleshooting procedures in Section 6.11.6.
If pressing the first unmarked switch results in an error message, refer to Section 6.11.4.1.

•

Test 006, second unmarked switch-Directs pressing the lit switch. The program then monitors
the switch bits in the I/O Control Processor switCh/display register and waits for the second
unmarked switch bit to set. If any other switch bit sets, an error is reported and the program
terminates.
After the first unmarked switch bit sets in the I/O Control Processor switch/display register, the
program directs pressing the lit switch as the next step. This returns it to the OFF (out) position.
The program then waits until the switch bit reads OFF (0) before proceeding to the next test.
If pressing the second unmarked switch has no effect, one of the following could be the cause:

Second unmarked switch is broken.
Second unmarked switch is not properly wired.
Second unmarked switch bit in the I/O Control Processor CSR cannot be set.
Refer to the troubleshooting procedures in Section 6.11.6.
If pressing the second unmarked switch results in an error message, refer to Section 6.11.4.1.

6-76
OFFLINE DIAGNOSTICS

•

Test 007, enable LED off-Begins with a prompt to put the Secure/Enable switch into the
SECURE position. The program waits until bit 15 of the I/O Control Processor control and status
register reads as a 0, indicating the switch is in the SECURE position. Then the program tells the
operator to observe that the enable LED is OFF.
If t~~ enable LED fails to turn off when the switch is in the SECURE position, replace the OCP.

•

Test 008, Init switch in secure mode--Checks that the Init switch has no effect when the
Secure/Enable switch is in the SECURE position. The test prompts for the Init switch to be
pressed while the program monitors the switch bits in the I/O Control Processor switch/display
register. Monitoring ensures that pressing the lnit switch does not cause any switch bits to set.
IT pressing the lnit switch causes the HSC to reboot, the SECURE position of the Secure/Enable
switch is not disabling the Init switch. Replace the OCP.
If pressing the Init switch causes one of the switch bits in the switch/display register to set, an error
message is displayed. Refer to Section 6.11.4.1 for further information.

•

Test 009, BREAK key in SECURE mode-Checks if the tenninal IBREAKI key has no effect when
the Secure/Enable switch is in the SECURE position. (Normally the IBREAK I key causes the I/O
Control Processor J11/F11 CPU to halt and enter ODT.) The prompt is to press the IBREAKI key and
to observe if the HSC does not halt.
If pressing the IBREAKI key causes the terminal to print an @ symbol, the SECURE position of the
Secure/Enable switch is not disabling IBREAKI from halting the J11fF11 CPU.

6.11.6 Offline OCP Registers and Displays via ODr
The following paragraphs and layouts are included to assist you with troubleshooting.
6.11.6.1 Switch Check via ODT

To check the operation of an HSC switch, follow this procedure:
1. With the Secure/Enable switch in the ENABLE position, press the terminal IBREAKI key. The I/O
Control Processor J ll/Fll CPU should halt and display an @ symbol.
2. Type: 17770042/ .
The contents of address 17770042 (the I/O Control Processor switch disp]ay register) are displayed
in octal. Refer to the layout of the switch display register in Figure 6-1 to locate the switch bits.

6-77
OFFLINE DIAGNOSTICS

ADDRESS 17770042 VIA DDT

___- - - - - - 4000(8) FAU L T SWITCH
r------2000(8) ONLINE SWITCH
.------1000(8) FIRST UNMARKED SWITCH
.---400(8) SECOND UNMARKED SWITCH

(UNUSED)

200(8) GREEN LED ---~
100(8) CHEM/DMEM NXM _ _-oJ
40(8) INH PARITY TRAP ----~

20(8) INIT LAMP _ _ _ _ _ _ _- - - J
10(8) FAULT LAMP - - - - - - - - - - '
4(8) ONLINE LAMP
2(8) FIRST UNMARKED LAMP-_ _ _ _ _ _ _...J
1(8) SECOND UNMARKED LAMP _ _ _ _ _ _ _ _- - 1
CX-1119A

Figure 6-1

P.ioj Switch Display Register Layout

Each bit is in the 1 state when the associated switch is ON (pressed in),
3. Type a carriage return.
4. Type a slash (I) to re-examine the switch display register.
5. To restart the offline loader (or the diagnostic that was interrupted), type I RETURN I, then type P
IRETURNL

Using this method, the switch bits of the switch/display register can be monitored when various
switches are in the ON or OFF position.

6-78
OFFLINE DIAGNOSTICS

6.11.6.2 Lamp Bit Check via OOT

To check the operation of the lamp control bits in the I/O Control Processor switch/display register, use
the following method.
1. With the Secure/Enable switch in the ENABLE position, press the terminal ~ key.
The I/O Control Processor JllfF11 CPU should halt and display an @ symbol.
2. Type 17770042 IRETURN I.
The contents of the switch/display register are displayed in octal.
3. Use Figure 6-1 to locate the bits controlling the OCP lamps.
When a lamp bit is set, the corresponding lamp should be lit.
4. To light a lamp, type the octal value that corresponds to the proper lamp, then type IRETURNl The
lamp should light.
5. Type a slash (I) to re-examine the contents of the switch/display register.
6. Iype IRjTURNI to restart the offline loader (or the diagnostic that was interrupted), then type a P
RETURN.
Using this method, various lamps can be manually enabled or disabled.
6.11.6.3 Secure/Enable Switch Check via OOT

To manually check the operation of the secure/enable bit in the I/O Control Processor control and
status register, use the following procedure. Using this method, the secure/enable bit in the I/O Control
Processor CSR can be checked with the Secure/Enable switch in both positions.
1. With the Secure/Enable switch in the ENABLE position, press the terminal IBREAKI key. (If the
HSC is stuck in the SECURE mode, this method cannot be used because IBREAKI is disabled.)
2. The I/O Control Processor JllfF11 CPU halts and displays an @ symbol.
3. Type 17770040 IRETURN I.
4. The content of the I/O Control Processor control and status register is displayed in octal.
Figure 6-2 identifies the various bits of this register.

6-79
OFFLINE DIAGNOSTICS

ADDRESS 17770040 VIA OOT
- - - - - - - - - - - - - 1 0 0 0 0 0 ( 8 ) OWHEN SECURE
. , . - - . - - - - - - - - - - 4 0 0 0 0 ( 8 ) ALWAYS 0
. - - - - - - - - - - 2 0 0 0 0 ( 8 ) ALWAYS 0
- - - - - - - - - 1 0 0 0 0 ( 8 ) ALWAYS 0
.--------4000(8) SWAP BOARD
------2000(8) SWAP BANK
-----1000(8) A LWA YS 0
400(8) SELECT BIT PG2

200(8) ENA CMEM A R B - - - - - - '
100(8) ALWAYS 0 - - - - - - - - - '
40(8) HI BYTE PAR ITY TEST _ _ _ _ _...J
20(8) LO BYTE PARITY TEST----------J
10(8) STATE LED _ _ _ _ _ _ _ _ _ _ _---l
4(8) NON-MEMORY-ACCESS (NMA) _ _ _ _ _ _ _....J
2(8) CONTROL MEMORY INTERRUPT ENABLE _ _ _ _- - J
1(8) CONTROL MEMORY LOCK CYCLE ENABLE _ _ _ _ _ _~

CX-1120A

Figure 6-2

P.ioj Control and Status Register Layout

When the Secure/Enable switch is in the ENABLE position, the contents of the register should be
lxxxxx. When in the SECURE position, the contents should be Oxxxxx.
5. Type IRETURNI and then a slash (I) to re-examine the register.
6. Type I RETURN I, then type P I RETURN 1to restart the offline loader (or the diagnostic that was
interrupted).

6-80
OFFLINE DIAGNOSTICS

6.11.6.4 State LED Check via OOT

There are two State LEDs in the HSC. One is on the OCP, far left. The other State LED is on the I/O
Control Processor module (righttnost module in the HSC card cage, fourth LED from the bottom of
the module). Both LEOs are controlled by a bit in the I/O Control Processor control and status register
(refer to Figure 6-2 for a layout of this register). To manually control the Slate LED, use the following
procedure:
1. With the Secure/Enable switch in the ENABLE position, press the terminal ~ key.
The I/O Control Processor JllfFll CPU should halt and display an @ symbol.
2. Type 17770040/ .
The contents of the control and status register are then displayed in octal.
3. Use Figure 6-2 to find the octal value corresponding to the State LED.
4. To light the State LED, type the octal value corresponding to the State LED, followed by IRETURNI.
To extinguish the State LED, put a 0 in the same bit position and press IRETURN!.
CAUTION

Bit 7 of the I/O Control Processor CSR must be set to allow the HSC Ks to access Control
memory. The setting of other bits in the CSR can result in strange side effects. Be careful
not to set any bits except the State LED bit and leave bit 7 set when done.
5. Type a slash (f) to re-examine the contents of the I/O Control Processor CSR.
6. To restart the offline loader (or the diagnostic that was interrupted), type IRETURN I, then type P
1

RETURN!.

7-1
UTILITIES

7
UTILITIES
7.1

INTRODUCTION

This chapter contains the information required to run six of the offline utilities: DKUTIL (Disk Utility),
VERIFY, FORMAT, RXFMT (RXFORMAT Utility), VTDPY (Video Terminal Display Utility), and
DKRFCf (RCT/FCf Merge). The HSC must be in the command mode before rwming the offline
utilities. Type ICTRUVI to get the command prompt.
Topics covered in this chapter include initiating the utility, using commands, and interpreting error
messages. These HSC utilities are interactive and therefore are prompt-oriented. Note that prompt
information displayed in square brackets is the default.
For information on the other HSC utilities, refer to the HSC User Guide (AA-GMEAA-TK). Utilities
described in that manual include:
J)K \.iii ~ - r H I ~ P,tjG-£
SETSH0?z
V£(llP'( 7-15
• BACKUP Package
foRM 14/- ; - 2.'2..
DKCOPY
Irl£S~

PATCH
/
COPY./

irv2l?C ...
IN ctfJ>Gv(Dt:
US~~

RXFMT -

7 -2.. 7

VTDPY' vkRFC-T-

7-3()

7-3 ~

7.2 OFFLINE DISK UTILITY (DKUTIL)
DKUTIL is a general utility for displaying disk structures and disk data. Unlike some other utilities,
DKUTIL is a command language interpreter. It is intended for use in debugging utilities, diagnostics,
error recovery, and bad block replacement. DKUTIL has become a general utility for displaying disk
structure and data. Initially, the program goes into command mode. The user must then issue a GET
command to obtain the unit to which other commands are to be applied. DKUTIL then returns to
the command mode, promtting flr a command, executing it, an, prOmpjing for another command.
DKUTIL is terminated by CTRUC ICTRUVL ICTRUZl or the EXIT RETURN command.

7.2.1 DKUTIL Initialization
DKUTIL is initiated via the standard CRONIC command syntax RUN DKUTIL.UTL IRETURNL It
ilnmediately enters the command mode. A drive must be acquired and brought online before any other
commands can be executed. Type GET Dnnn IRETURNI to acquire the drive and bring it online.
DKUT IL> GET Dnnn IRETUP,N I
The fonnat for entering the drive is a D followed by the unit number. If the drive parameter is omitted,
DKUTIL defaults to DOOO (unit 0).

7-2
UTILITIES

The first hlock of the Fonnat Control Table (PCT) is read, if possible, and dumped in a fonnat similar
to a VERIFY printout. The unit is brought online with the ignore media format error modifier so drives
improperly or not completely fonnatted can be examined. IT the FCT cannot be read or the mode is
invalid, the program prompts for the sector size.
DKUTIL-Q Enter sector size (512/576)

[512]?

The program places the unit in diagnostic mode to access the DBN area. The program returns to the
command mode and prompts for a command.
DKUTIL>

Comment lines can be entered by prefixing them with an exclamation point (!). A null line is ignored.
Entering ICTRLJZ\ terminates the program. Commands are executed immediately and take only the time
necessary to print the results. Entering ICTRlJY\ or ICTRLJC\ at any time aborts the program and releases
the drive.

7.2.2 DKUTIL Command Syntax
The DKUTa commands are:

•

DEFAULT

•

DISPLAY

•

DUMP

•

EXIT

•

GET

•

POP

•

PUSH

•

REVECfOR

•

SET

Any initial suhstring recognizes commands, command options, and modifiers. For example, DUMP
can be entered as DUM, DU, or D. In cases where the initial substring can indicate one of several
commands, the match depends on an order based on history and expected frequency of usage. Thus, D
specifies DUMP, DI specifies DISPLAY, and DE specifies DEFAULT. In the descriptions explained in
this chapter, only the command (or part of the command) in bold print must be specified.
Some command options take optional parameters which, if omitted, default.

7.2.3 DKUTIL Command Modifiers
Modifiers, specified only for commands that allow them, can occur anywhere after the command itself.
They are preceded by a slash (one slash for each modifier). The following are equivalent:
DUMP /NOEDC RBN 0
DUMP RBN/NOEDC 0
DUMP RBN O/NOEDC
DUMP RBN 0 /NOEDC
Modifiers are processed left to right and applied to the current default modifiers. The DUMP command
is the exception. The default modifiers for DUMP can be changed via the DEFAULT command. The
initial default modifiers for DUMP are /DATA, /EDC, and /IFERROR.

7-3
UTILITIES

7.2.4 DKUTIL Sample Session
The foHowing is a sample session using DKUTIL. Command input is indicated in bold print. Enter
ICTRUY Ito get the HSC> command prompt.
"Y
HSC> RON D1a7TIL IRETURN I
OKUTIL> OBT 0133

IRETURN I

Serial Number:
Mode:
First Formatted:
Date Formatted:
Format Instance:
FCT:

0000000004
512
17-Nov-1858 00:35:47.48
04-Apr-1984 00:05:09.20
6

VALID

DKUTIL> DIS/I' I'CT IRETURN I
Factory Control Table for D133 (RA80)
Serial Number:
Mode:
First Formatted:
Date Formatted:
Format Instance:
FCT:

0000000004
512
17-Nov-1858 00:35:47.48
04-Apr-1984 00:05:09.20
VALID

Bad PBNs in FCT:

1 (512), 0 (576)

Scratch Area Offset: 63
Size (Not Last):
417
Size (Last):
289
Flags:
Format Version:

000000
0

PBNs in 512 Byte Subtable
(04) 244865 (LBN 237213),
DKOT!L> !L1!V 1000 IRETUR..~1
ERROR-W Bad Block Replacement (Success) at 04-Apr-1984 17:47:24.20
Command Ref i
00000000
RA80 Unit #
133.
Err Seq i
6.
Error Flags
80
Event
0014
Replace Flags
A400
LBN
1000.
Old RBN
32.
New RBN
33.
Cause Event
004A
ERROR-I End of error.
OKUTIL> DIS/I' RCT IRETURN I
~
Revector Control Table for 0133 (RA80)
Serial Number:
Flags:

0000000004
000000

LBN Being Replaced:
Replacement RBN:
Bad RBN:

1000 (000000 001750)
33 (060000 000041)
32 (060000 000040)

Cache ID:
Cache Incarnation:
Incarnation Date:

Bad RBN:
139512 -->

32,
4500,

0000000000
17-Nov-1858 00:00:00.00

L C'G-I c.;4 l--

GRc t.' P ==

TR.AC...J(S ri-ll'l T cl'9tJ 15 ~
it ('c £SS C.V I TNI'\J TilE..
INIER s£ciO~ 67tP Ti/,,'U£",

7-4
UTILITIES

1 Bad RBNs,
3 Bad LBNs,
2 Primary Revectors,
1 Non-Primary Revectors,
o Probationary RBNs.

RCT Statistics:

L.~G-/C;f-'t;.~() VPS

TiI'I, c~AJ

Acc.Ess~b

WITHIN

11'\Jl:>£1<

DKUTIL> DD'/NODATA IRETURN I
DKUTIL> DOMP LBN 1000 IRETURN I

C Yt.. IN b£!< .:=

.pl.hCSC:

'I"",e.

****** Buffer for LBN 1000 (000000 001750), MSCP Status: 000000
Error Summary = header compare
Original Error Bits
004000
Error Recovery Flags = 000
Error Retry Counts
0,1,0

BN = 1000 (000000 001750)
ECC Symbols Corrected = 0,0
Error Recovery Command = 000

Header = 001750 030000 001750 030000 001750 030000 001750 030000
Calculated EDC Difference = 000000

EDC

000105

ECC

000000 000000 000000 000000 000000 000000
000000 000000 000000 000003 000000 000000

DKUTIL> DZS CHAR LBN 1000 IRETURN I
Characteristics for LBN 1000 (000000 001750)
Cylinder 1, Group 0, Track 4, Position 8
PBN 1032 (000000 002010)
Primary RBN 32 (060000 000040) in RCT Block 3 at Offset 128
DKUTIL> DZS CHAR DISK IRETURN I
Drive Characteristics for D133
Type:

RA80 (576 byte mode allowed)

Media:

FIXED

Cylinders:

275 LBN, 2 XBN, 2 DBN

Geometry:

14 tracks/group, 2 groups/cylinder, 28 tracks/cylinder
31 LBNs/track, 1 RBNs/track, 32 sectors/track, 32 XBNs
896 XBNs/cylinder, 868 LBNs/cy1inder, 28 RBNs/cylinder

Group Offset:

16 (LBN), 16 (XBN)

LBNs:

237212 (host), 238700 (total)

RBNs:

7700

XBNs:

1792

DBNs:

1344 (read/write), 448 (read only)

PBNs:

249984

RCT:

465 (size), 63 (non-pad), 4 (copies)

FCT:

480 (size), 63 (non-pad), 4 (copies)

SDI Version:

Transfer Rate: 97
Timeouts:

3 (short), 7 (long)

Retry Limit:

Error Recover: 0 command levels
ECC Threshold: 2 symbols
10 (microcode), 0 (hardware)

Til€"

7-5
UTILITIES
Drive ID:

OA7AOOOOOOOO

Drive Type ID: 1
DBN RO Groups: 1
Preamble Size: 11 (data), 4 (header)
DKUT IL> DUMP RC'l BLOC1t 3 IRETURN I

****** RCT Block 3, Copy 1 ******
****** Buffer for LBN 237214 (000003 117236), MSCP Status: 000000
Data =
+16
+32
+48
+64
+80
+96
+112
+128
+144
+160
+176
+192
+208
+224
+240
+256
+272
+288
+304
+320
+336
+352
+368
+384
+400
+416
+432
+448
+464
+480
+496

000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 040000 001750
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
0_000_0_0 0000_00 _000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000

EDC = 023277
DKUT IL> BU'l'

000000
000000
000000
000000
000000
000000
000000
000000
030000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000

000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
00_0_000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000

000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
0000_00
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000

Calculated EDC Difference = 000000

IRETURN I

7.2.5 DKUTIL Command Descriptions
Descriptions for the individual DKUTll.. commands are found in the lists following this paragraph.
Command options are shown by separate lines in the syntax specification. Parameters are indicated
lowercase in the syntax by braces ({ }). Options indicated by brackets ([]) can be omitted.

7-6
UTILITIES

7.2.5.1 DEFAULT Command

The DEFAULT command is outlined as follows:
•

Purpose: To change the default modifiers for the DUMP command.

•

Syntax: DEFAULT.

•

Parameters: None.

•

Modifiers: Shown in the following list.
lIFERROR (NOIFERROR) (defaults ON)-Dumps the error, header, and ECC fields in the
buffer if an error occurs when reading the block. When this modifier is used in conjunction
with the /RAW modifier, the error must occur on the reread of the block with the header code
extracted from the first read.
IERRORS (NOERRORS) (defaults OFF)-Dumps the error fields in the buffer.
IEDC (NOEDC) (defaults ON)-Dumps the EDC and calculated EDC fields in the buffer.
IECC (NOECC) (defaults OFF}-Dumps the ECC fields in the buffer.

/DATA (NODATA) (defaults ON)-Displays the data in the buffer unless the /NZ modifier is
also specified.
IHEADERS (NOHEADERS) (defaults OFF)-Displays the header fields in the buffer.

IALL (NONE)-The same as /ERRORS/EDC/ECC/DATA/HEADERS). Requests all fields
be displayed. Its opposite, /NONE, requests no fields be displayed. When using the /NONE
qualifier, only the MSCP status line prints.
IRAW (NORAW)-Al1ows reading the original LBN that was revectored rather than the RBN

that would be read without the /RAW qualifier. /RAW only affects revectored (primary or nonprimary) LBNs. If /lFERROR is in effect, this modifier applies only to dumping a revectored
LBN.

INZ (NONZ) (defaults OFF)-Prevents the data from being displayed if it is all Os. Instead,
a single line indicating the data is 0 is printed. It has no effect if the /DATA modifier is not
specified or if it is defaulted OFF.
IBBR (NOBBR) (defaults OFF)-UsuaJ)y inhibited when a block is accessed. If this modifier
is specified, bad block replacement can occur. It only occurs, however, if the error recovery
code detects the block being accessed as bad and the block is an LBN in the host area.
IORIGINAL (NOORIGINAL) (defaults OFF)-Saves the first data seen for display. When a
block is accessed for dumping, the data is seen twice by the program if an error occurs. It is
seen first just after the K detects the error and sends it to error recovery. It is seen again after
error recovery takes place and the data has been corrected or reread. Usually, the data is saved
for displaying when it is last seen.
•

Usage: The modifiers specified are applied to the current default modifiers for the DUMP
command. The result becomes the new default. Examples are:
DEFAULT/NONE
DEF/RAW/NODATA
DE/NOR/NZ

7-7
UTILITIES

7.2.5.2 DISPLAY Command

The DISPLAY command is outlined as follows:

•

Purpose: To display the disk characteristics, the characteristics of a given block, the error history
in the drive, the FeT, and/or the ReT.

•

Syntax:
- DISPLAY ALL . - - -

-Jv- S lS £- B f-L,C) w
q

DISPLAY CHARACTERISTICS DBN {block}
DISPLAY CHARACTERISTICS DISK
DISPLAY CHARACTERISTICS LBN {block} _

~dcL.,.7:J~It' /..8f\i TO

PBN

DISPLAY CHARACTERISTICS PBN {block}
DISPLAY CHARACTERISTICS RBN {block}
DISPLAY CHARACTERISTICS XBN {block}
DISPLAY ERRORS
DISPLAY FCT
DISPLAY RCT
•

Parameters: Block is a number specifying the DBN, LBN, PBN, RBN, or XBN whose
characteristics are displayed. The default radix is decimal, and can be changed to octal by prefixing
the number with the letter O.
Modifiers:
/FULL-Displays all defined fields in xCT block O. /FULL applies on1y to the ReT and FCT
command options. For the RCT option, the bad block replacement and write back caching
fields in RCT block 0 are only displayed if the appropriate flags in the flags field are set. These
flags indicate they are currently in use (BBR or caching in progress). This modifier forces all
fields to be displayed regardless of the flags' settings. For the FeT option, the n1L'Ilber of bad
PBNs field is normally displayed only if the FCT is valid. Also, the scratch area parameters,
format version, and format flags are normally not displayed. This modifier forces all fields in
FeT block 0 to be displayed.
INOITEMS-Does not display the individual items in the FCT or ReT. It applies only to the
FeT and ReT command options. If given, only the block 0 information is displayed.

•

Usage:

DISPLAY ALL-Displays FCT, RCT, disk characteristics, and error history. Because the
~
error history in the drive is dumped by this option, it should not be used for RA60 drives. Using the SOl command to read RA60 error history is illegal and causes the drive to become
inoperative.

DISPLAY CHARACTERISTICS DISK-Displays the drive type, media, cyJinders, geometry,
group offsets, number of LBNs, number of RBNs, number of XBNs, numbers of DBNs,
number of PBNs, ReT parameters, FCT parameters, SDI version, transfer rate, SOl timeouts,
SDI retry limit, error resume recovery command levels, ECC threshold, revision levels, drive
10, drive type 10, DBN Read/Only groups, and preamble sizes.
DISPLAY CHARACTERISTICS xBN {block}-Displays the characteristics of the given
block. For DBNs and XBNs, these are the block numbers in decimal and octal, cylinder,
group, track, position, and PBN in decimal and octal. For RBNs, the RCT block numbers and
offset also are displayed. For LBNs, the primary RBN number and its ReT block number and

7--8
UTILITIES

offset also are displayed. For PBNs, the display depends on the type of block: DBN, LBN,
RBN, or XBN.
DISPLAY ERRORS-Reads the error history in the drive. The error history in the drive is
read from region 2, offset 0, and dumped in hexadecimal. This option should not be used for
RA60 drives because it causes them to become inoperative. Current drives display only 16
bytes of error log data. Succeeding drives display the error log header and all selected error
log entries.
DISPLAY FCT-Displays the information in FCT block O. Certain fields are not displayed
unless the /FULL modifier is given. The list of bad PBNs is displayed unless the /NOITEMS
modifier is given. For each item in the list, the header bits, PBN number, type (DBN, LBN,
RBN, or XBN), and xBN number are displayed.
DISPLAY RCT-Displays the information in RCT block O. Certain fields are not displayed
unless the /FULL modifier is given. The list of revectors, bad RBNs, and probationary RBNs
are displayed unless the /NOITEMS modifier is given. For bad and probationary RBNs, just
the RBN number is displayed (in decimal). For revectors, the LBN number and RBN number
to which it is revectored are displayed (in decimal). A primary revector is distinguished by the
character sequence "->". A non-primary revector is distinguished by the character sequence
"*->" .
Examples are:
DISPLAY/FULL ALL
DI/F A
DI CD
DIS CHAR LBN 1000
Dl/NOIRCT
7.2.5.3 DUMP Command

The DUMP command is outlined as follows:
Purpose: To dump the given block or table of blocks.
•

Syntax:
DUMP [BUFFER]
DUMP DBN [{ block}]
DUMP FCT [BLOCK {number}] [COpy {copy}]
DUMP LBN [{ block} ]
DUMP RBN [{ block}]
DUMP RCT [BLOCK {number}] [COpy {copy}]
DUMP XBN [{ block}]

•

Parameters:
Block is a number specifying the DBN, LBN, RBN, or XBN to be dumped. The default radix
is decimal. It can be changed to octal by prefixing the number with the letter O.
Number is the relative block number in the FCT or RCT to be dumped. The default radix
is decimal and can be changed to octal by prefixing the number with the letter D. The value
must be in the range 1 through nonpad area of the FCT or RCT size. That is, the first block is
number 1 (not 0) and the block must lie in the nonpad area.
Copy specifies which copy of the given block in the FCT or RCT is to be dumped. The first
copy is number 1. The value must not exceed the number of copies.

7-9
UTILITIES

DUMP xBN [{bJock}]-The specified DBN, LBN, RBN, or XBN is read in and dumped
subject to the given modifiers. If the block number is not specified, it defaults to O.
DUMP xCT [BLOCK {number}] [COPY {copy}]-If a BLOCK number is given, that block
in the FCT or RCT is read in and dumped. If none is specified, every block in the nonpad area
of the FCT or ReT is read in and dumped. If COpy is not specified, it defaults to copy 1.
Examples of DUMP command parameters are:
DUMP RCT BLOCK 3 COpy 4
DU/NZRCT C 2
DU LBN 1000
DFB2
DX
D/DATA
•

Modifiers:
IIFERROR (NOIFERROR) (defaults ON)-Dumps the error, header, and ECC fields in the
buffer when an error occurs while reading the block. When used in conjunction with the IRAW
modifier, the error must occur on the read of the LBN (reread) with the header code extracted
from the RBN (first read). Refer to Section 7.2.5.1.
IERRORS (NOERRORS) (defaults OFF)-Dumps the error fields in the buffer.
IEDC (NOEDC) (defaults ON)-Dumps the EDC and calculated EDC fields in the buffer.
IECC (NOECC) (defaults OFF)-Dumps the ECC fields in the buffer.
!DATA (NODATA) (defaults ON)-Displays the data in the buffer unless the /NZ modifier is
also specified.

IHEADERS (NOHEADERS) (defaults OFF)-Displays the header fields in the buffer.

I ALL (NONE)-The same as /ERRORS/EDC/ECC/DATA/HEADERS. It requests display of
all fields. Its opposite, /NONE, requests display of no fields. When using the /NONE qualifier,
only the MSCP status line prints.
-

IRAW (NORAW)-Allows a read of the original revectored LBN (rather than the RBN that
would be read without the /RAW qualifier). /RAW only affects revectored (primary or nonprimary) LBNs. If in effect, the /lFERROR modifier applies only to dumping a revectored
LBN.

INZ (NONZ)-Prevents data from being displayed when it is all Os. Instead, a single line
prints indicating the data is Os. /NZ has no effect unless the /DATA modifier is specified. It
also has no effect if /DATA is not specified (or is defaulted OFF).
-

/BBR (NOBBR) (defaults OFF)-Permits bad block replacement. Normally, bad block
replacement is inhibited when a block is accessed. BBR occurs if the block being accessed is
detected as bad by the error recovery code and is an LBN in the host area.
IORIGINAL (NOORIGINAL)-Saves the first data seen for display. When a block is accessed
for dumping, the data is seen twice by the program when an error occurs. It is seen first just
after the K detects the error and sends it to error recovery. It is seen again after error recovery
takes place and the data has been corrected or reread. Normally, the data is saved for displaying
when it is last seen.

7-10
UTILITIES

7.2.5.4 EXIT Command
The EXIT command is outlined as follows:

•

Purpose: To tenninate execution of the program.

•

Syntax: EXIT.

•

Parameters: None.

•

Modifiers: None.

•

Usage: The current drive is released, all resources are returned, and the program exits. Examples
are:

EXIT
E
7.2.5.5 GET Command
The GET command is outlined as follows:

•

Purpose: To obtain a drive or change the current drive.
Syntax: GET [{ drive}].

•

Parameters: Drive is a valid drive unit specification of the fonn Dnnn. If this parameter is omitted,
GET defaults to DOOO (unit 0).

•

Modifiers:
INOIMF-Allows the reading of FCf block 0 to detennine the mode and the reading and
writing of RCT block 0 to verify the RCf is sane. H this modifier is specified, the IMF MSCP
modifier is not used in the online mode and these actions take place. By default, a new drive
is brought online with the IMF (MD.lMF) MSCP modifier.
IWP-Brings the drive online with the MSCP SET WRITE PROTECf modifier (MD.SWP)
and WRITE PROTECT unit flag (UF.WPS). The drive is then software or volume writeprotected.
INOWP-Brings the drive online with the MSCP SET WRITE PROTECT modifier. The drive
is not software or volume write-protected.
NOONLINE-The drive is acquired but not brought online with the MSCP online command.
Only the display characteristics, display errors, and the set size commands can be executed on
a drive in this state.

•

Usage: The current drive is released. The new drive is acquired and then brought online with the
requested modifiers and unit flags. If the drive is nonexistent, in use, or inoperative, the user is put
back in command mode. The modifiers cannot be changed for this other unit. If the mode word in
FCT block 0 is invalid or all copies of FCf block 0 are bad, the program prompts for the sector
size to use. Examples are:
GET 0133
G/WP D64
G

7-11
UTILITIES

7.2.5.6 POP Command

The POP command is outlined as follows:
•

Purpose: To restore the data in the current buffer from the save buffer.

Syntax: POP.

•

Parameters: None.

•

Modifiers: None.

•

Usage: The data in the save buffer is restored to the current buffer. The data in the current buffer
is lost. Examples are:
POP
P

7.2.5.7 PUSH Command

The PUSH command is outlined as follows:
•

Purpose: To save the data in the current buffer in the save buffer.

•

Syntax: PUSH.

•

Parameters: None.
Modifiers: None.

•

U sage: The data previously in the current buffer is saved in the save buffer. The data in the save
buffer is lost. Examples are:
PUSH
PU

7.2.5.8 REVECTOR Command

The REVECTOR command is outlined as follows:
•

Purpose: To force bad block replacement for one or more given LBNs.

•

Syntax: REVECTOR {block} [{ block}].

•

Parameters: Block is a number specifying the LBN to be replaced. The default radix is decimal. It
can be changed to octal by prefixing the number with the letter O.

•

Modifiers: None.

•

Usage: The specified LBNs are sent to the bad block replacement module to be revectored. IT it
is not a valid LBN or in the RCT, the revector fails and an error message prints. Otherwise, the
result of the replace attempt shows in the error log produced (if the appropriate level message level
is enabled [INFO]). The data in the "replacement RBN is read from the specified LBN. Examples
are:
REVECTOR 1000
R 100
R 200 210

7-12
UTILITIES

7.2.5.9 SET Command

The SET command is outlined as follows:
•

Purpose: To change various program parameters.

•

Syntax: SET [SIZE {size}].

•

Parameters: The size parameter specifies the new sector size to be used for the current drive. It
must be either 512 or 576 bytes.

•

Modifier: None.

•

Usage: SET SIZE {size}.
The sector size is changed to the given value and the disk parameters are recomputed. This new
sector size is used when doing I/O to the LBN area and is also reflected in the parameters printed
by the DISPLAY CHARACTERISTICS DISK command. Examples are:
SET SIZE 576
S S 512

7.2.5.10 Command Summary

A summary of all DKUTll.. commands follows:
•

DEFAULT-Change default modifiers for DUrvtP command.
DEFAULT

•

DISPLAY-Display characteristics, error history, RCT, or FCf.
DISPLAY ALL
DISPLAY CHARACfERISTICS DBN {block}
DISPLAY CHARACfERISTICS DISK
DISPLAY CHARACfERISTICS LBN {hlock}
DISPLAY CHARACfERISTICS PBN {block}
DISPLAY CHARACfERISTICS RBN {block}
DISPLAY CHARACTERISTICS XBN {block}
DISPLAY ERRORS
DISPLAY FCT
DISPLAYRCT

•

DUMP-Dump given block or table of blocks.
DUMP [BUFFER]
DUMP DBN [{block}]
DUMP FCT [BLOCK {number}] [COpy {copy}]
DUMP LBN [{ block}]
DUMP RBN [{ block}]
DUMP RCT [BLOCK {number}] [COpy {copy}]
DUMP XBN [{ block}]

•

EXIT-Terminate execution of the program.
EXIT

•

GET-Acquire or change the current drive.
GET [{ drive} ]

•

POP-Restore save buffer to current buffer.
POP

7-13
UTILITIES

•

PUSH-Save current buffer in save buffer.
PUSH

•

REVEefOR-Force bad block replacement for the given LBN(s).
REV ECTOR {block } [block]
SET--Change various program parameters.
SET [SIZE {size}]

7.2.6 DKUTIL Error Messages
DKUTIL error messages conform to the HSC utility error message format.
7.2.6.1 Error Message Variables
Certain portions of the error messages are variable and are shown in bold print. The meanings of
these variables are as follows:

n = A decimal number
par = BLOCK or COpy
pann =The part of the command in error (modifier, etc.)
status = MSCP status (an octal number)
text = The actual text in error
xBN = DBN, LBN, etc.
xCT = FCT or Ref
7.2.6.2 Error Message Severity Levels
Each DKUTIL error message cQntains the utility name at the start of the message followed by a letter
indicating the severity level of the message. These are defined as:

E = Error
F = Fatal
! := Information
7.2.6.3 Fatal Error Messages
The following are a list of the DKUTn.. fatal error messages.

•

DKUTIL-F Insufficient resources to RUN!-Prints if DKUTn.. cannot acquire the necessary
resources to run or if the disk functional code is not loaded. The program terminates after this
message is printed.

•

DKUTIL-F I/O request was rejected!-Prints if the diagnostic interface (DDUSUB) rejects a
request to start an I/O operation. It indicates a bug in DKUTIL and should be reported to field
service support. The program terminates after this message is printed.

7.2.6.4 Infonnation and Error Messages
The following is a list of the DKUTIL information and error messages.

•

DKUTIL-E Drive went AVAILABLE-Prints if the unit selected goes available while DKUTIL
is running. DKUTIL then goes into command mode and the user must issue a GET or EXIT
command at the DKUTIL> prompt.

•

DKUTIL-E Drive went OFFLINE!-Prints if the selected unit goes offline while DKUTlL
is running. DKUTIL then goes into command mode and the user must issue a GET or EXIT
command at the DKUTn..> prompt.

7-14
UTILITIES

•

DKUTIL-E Illegal response to start-up question.-Prints if an invalid response to a start-up
question or to a prompt for the GET command is entered. The program reprompts with the same
question.

•

DKUTIL-E Nonexistent. unit number.-Prints if the unit number entered does not correspond to
any known unit. DKUTIL then goes into command mode and the user must issue a GET or EXIT
command at the DKUTIL> prompt.

•

DKUTIL-E Unit. is not available.-Prints if the unit requested is unavailable. The unit may be
in use by a host or another diagnostic or it may be inoperative. DKUTIL then goes into command
mode and the user must issue a GET or EXIT command at the DKUTIL> prompt.
DKUTIL-E Cannot bring unit ONLINE.-Prints if the requested unit is available, but the
ONLINE command failed. The unit is released, and DKUTIL then goes into command mode and
the user must issue a GET or EXIT command at the DKUTIL> prompt.

•

DKUTIL-E Invalid decimal number.-Prints if an invalid decimal number is entered in a
command line..

•

DKUTIL-E Invalid octal number.-Prints if the user entered an invalid octal number in a
command line.
DKUTIL-E Missing parameter.-Prints if a command line is entered with a required parameter
missing.
DKUTIL-E There is no buffer to dump.-Prints jf th.e DUMP BUFFER command is entered,
and there is no current buffer. This can only happen if a drive has just been selected.

•

DKUTIL-E Missing modifier (only I was specified).-Prints if a command line is entered with
a slash (/) followed by a blank or is entered at the end of the line. A modifier is expected, but is
missing.

•

DKUTIL-E SDI command was unsuccessful.-Prints when an SDI command is rejected by the
drive. A DISPLAY ERRORS command for an RA60 drive always generates this message.

•

DKUTll.,-E n is an invalid par number; maximum is n.-Prints if an out-of-range number is
entered for a BLOCK or COpy value for the DUMP command.

•

DKUTIL·E xxx is an invalid xxx.-Generic error message that prints whe.n an invalid command,
invalid command option, invalid modifier, invalid block type, or invalid SET option is specified in
a command line.

•

DKUTIL-E Invalid block number for xBN space.-Prints if the block number specified for a
DISPLAY CHARACTERISTICS xBN command is out-of-range for the given space.

•

DKUTIL-E Copy n of xCT Block n (xBN n) is bad.-Prints when Fef or Ref blocks cannot be
read correctly with error recovery~ when the FCT or RCT is being read just after a drive has been
selected. It also occurs when the DISPLAY FCT or DISPLAY RCT command is being used.

•

DKUTIL-E All copies of xCT Block n are bad.-Prints when all copies of FCT or RCT blocks
are had. It occurs when the FCT or RCT is being read just after a drive has been selected, or when
the DISPLAY FCT or DISPLAY RCT command is being used.
DKUTIL-E Invalid sector size; only 512 and 576 are legal.-Prints if the sector size entered for
the SET SIZE command is other than 512 or 576 bytes.

•

DKUTIL-E Revector for LBN n failed, MSCP Status: (status).-Prints if a revector (using the
REV ECTOR command) fails. If the status indicated that the drive went OFFLINE or AVAll..ABLE,
DKUTIL goes into command mode.

•

DKUTIL·E Error log corrupted, cannot display header.-Prints when the DISPLAY ERRORS
command reads a header that does not begin with the standard FFFB code.

7-15
UTILITIES

•

DKUTIL-E Error log corrupted, cannot display entries.-Prints when the DISPLAY ERRORS
command is unable to read a valid entry from region FFFB.

•

DKUTIL-E Unable to read error log.-Prints when the DISPLAY ERRORS command is unable
to execute the read memory command.

•

DKUTIL-E Error log not implemented in drive.-Prints when the DISPLAY ERRORS
command is executed on an RA60.

•

DKUTIL-E Drive must be acquired to execute this command.-Prints if the requested command
requires that a drive must first be acquired before the command can be executed. A drive can be
acquired and not brought online by using the /NOONLINE modifier with the GET command.

•

DKUTIL-E Drive must be online to execute this command.-Prints if the requested command
requires that a drive first be acquired and brought online before the command can be executed.

•

DKUTIL-I CTRLIY or CTRL/C Abort!-Termination message that prints if DKUTIL is aborted
by typing ICTRUVI or ICTRucl.

7.3 OFFLINE DISK VERIFIER UTILITY (VERIFY)
VERIFY is a utility that checks the integrity of the disk architectural structure. This utility is a tool
designed for DIGITAL support personnel to check a disk to ensure it conforms to the DIGITAL
Standard Disk Format.
VERIFY has many messages that may print during the course of a disk structure verification. These
messages have significance only when VERIFY reports the drive is bad. At the end of its run, VERIFY
reports the drive is either OK or BAD.
NOTE

The VERIFY utility only reads the disk. It does not destroy user data and does not perform bad
block replacement.
The following steps describe the process by which this utility verifies a disk.
1. The first block of the Factory Control Table (FCI') is read to determine how the disk is formatted.
The serial number, format mode, date first formatted, date last formatted, format instance, state of
the FCI', number of bad PBNs, scratch area parameters (offset, size of not last, and size of last),
flags, and format version are printed.
2. The first block of the Revector Control Table (RCI') is then read. The information in it is
printed, including the serial number, flags, bad block replacement variables (LBN being replaced,
replacement RBN, and bad RBN), and cache variables (ID, incarnation, and incarnation date).
3. All copies of the first two blocks in the RCT (used by bad block replacement) are read and
compared. Discrepancies or bad blocks are reported.
4. All copies of the rest of the RCT are read and compared. Any discrepancies or bad blocks are
reported. The information about revectors and bad RBNs is dumped. A summary of the number of
bad blocks and revectors by type is printed.
5. All copies of FCI' block 0 are read and compared, and bad blocks or discrepancies are reported.
6. All copies of the appropriate FCT sub table are read (if not null) and bad blocks or discrepancies
are reporled.
7. The list of bad PBNs is printed. Each entry is printed with the header bits, PBN number, and xBN
number (in parentheses) as separate fields. IT a bad PBN which should be in the RCI' but is not is
found, the xBN field is printed in brackets instead of parentheses. IT any such PBNs are found, an
error message indicating the total number is printed at the end of the bad PBN list.

7-16
UTILITIES

8. After reading '3.Ild dumping the FCT, a quick scan of DBN space is done. Every block is accessed
only once. Counts of various detected errors are recorded for a summary printed at the end of the
scan. IT more than nine positioner errors are detected, a message is printed suggesting DBN space
be reformatted. IT more than nine EDC errors are detected, a message is printed suggesting the
INITIAL WRITE option should be used when running ILEXER.
9. All LBN space up to the RCT and all RBNs are scanned. Any block with an error is reread five
more times to determine the type of error. Information about bad blocks and revectors collected
in this phase is compared with information collected from reading the RCT. During the scan, four
error classes can be found:
Structure errors
Permanent recoverable errors
Permanent wrrecoverable errors
Transient errors
Structure and permanent unrecoverable errors are considered inconsistencies and are always
reported. Permanent recoverable errors, usually ECC errors, are reported if requested. During the
five rereads of a block with an error, a block read at least once with no detected error is considered
to have a transient error. Transient errors are reported if requested.
10. At the end of the scan, certain other errors are reported. Some errors can only be determined at
that time by examining information collected during the scan.
11. Finally, a swnmary, by type, of the errors detected and certain other information is printed. If no
inconsistencies were discovered, a message prints saying the drive is OK. Otherwise, the message
indicates the number of inconsistencies.

7.3.1 VERIFY Initiation
VERIFY is initiated via the standard CRONIC command syntax RUN DXO:VERIFY.UTL IRETURNI.
The following prompt asks for the unit number of the disk to verify.
VERIFY-Q Enter unit number to verify (U)

[DO]?

It then prompts to determine if the unit was recently formatted.
VERIFY-Q Was this unit just FORMATted (YIN)

[Y]?

This question is asked because certain errors are classed as inconsistencies only when the unit has
not been subject to bad block replacement following the execution of FORMAT. The next prompt
determines whether errors not considered inconsistencies should be reported.
VERIFY-Q Print infor.mational (non-warning) messages (YIN)

[N]?

If this question is replied with an N, only inconsistencies are reported. IT the reply is Y, the prompt
looks for further decision as to whether transient errors should be reported.
VERIFY-Q Report transient errors by block (YIN)

[N]?

Regardless of the response to this question, the number of transient errors is printed in the final
summary. The response to this question determines whether or not individual blocks with transient
errors should be reported.
A ICTRlJZl can be entered at any prompt for the remainder of the responses. ICTRuzl forces the default
response (in square brackets). Also, the responses to subsequent questions can be supplied at any
question by typing them separated with commas. For example, if unit 0133 (Whicr was jl~t formatted)
is to be verified and all options are to be selected, the user could type D133"Y,Y RETURN at the first
prompt.

7-17
UTILITIES

If the unit does not exist or cannot be accessed, notification and reprompt for another unit nwnber are
received. If the unit can be accessed, it is acquired and brought online. VERIFY runs to completion,
unless aborted by /CTRUVI or ICTRUCI.

7.3.2 VERI FY Sample Session
The following is a sample session using VERIFY. User input is in bold print.
Ay

IRETURN I

HSC50> RON OXO:VERIFY

VERIFY-Q Enter unit number to verify (U) [DO]? 0133 IRETURN I
VERIFY-Q Was this unit just FORMATted (YIN) [Y]? IRETURN I
VERIFY-Q Print informational (non-warning) messages (YIN) [N]? Y IRETURN I
VERIFY-Q Report transient errors by block (YIN) [N]? Y IRETURN I

***

FCT Block 0 Information

Serial Number:
Mode:
First Formatted:
Date Formatted:
Format Instance:
FCT:
Bad PBNs in FCT:

0000000004
512
17-Nov-1858 00:35:47.48
10-Apr-1984 00:05:09.20
6

VALID
1 (512), 0 (576)

Scratch Area Offset: 63
Size (Not Last):
417
Size (Last):
289
Flags:
Format Version:

***

000000

ReT Block 0 Information

Serial Number:
Flags:

0000000004
000000

LBN Being Repla"ced:
Replacement RBN:
Bad RBN:

o (000000 000000)
o (060000 000000)
o (060000 000000)

Cache ID:
Cache Incarnation:
Incarnation Date:

0000000000

***

o
17-Nov-1858 00:00:00.00

Revector Control Table for 0133

VERIFY-I Copy 1 of RCT Block 2 (LBN 237213.) is bad.
25512 -->
822, 139512 --> 4500,

o Bad RBNs,

RCT Statistics:

2 Bad LBNs,
2 Primary Revectors,
o Non-Primary Revectors,
o Probationary RBNs,
1 Bad RCT Blocks,
1 Bad First Copy RCT Blocks.

***

Factory Control Table for 0133
PBNs in 512 Byte Subtable

(04) 244865 (LBN 237213),

***

Quick Scan of DBN Area

Statistics:

o total blocks with any error.
***

Scan of LBN Area

7-18
UTILITIES
VERIFY-I LBN 26003. has a 1 symbol correctable ECC error.
VERIFY-I RBN 2471. has a 1 symbol correctable ECC error.
VERIFY-I LBN 139962. has a 1 symbol correctable ECC error.
Statistics:
3 total ECC symbols corrected,
3 blocks with 1 symbol ECC errors,
2 revectors verified,
5 total blocks with any error.
VERIFY-I Drive is OK.

The preceding example is the output of an actual session for an RA80 disk with one bad PBN in
the FCT. Notice this PBN corresponds to copy 1 of RCT block 2. ReT block 2 is used to store the
copy of the user data during bad block replacement. In its scan of the RCT, VERIFY noticed this
block was bad and printed an informational message indicating that. H informational messages had
been suppressed by responding with N to VERIFY-Q Print informational (non warning) messages, this
information would show only in the summary of the RCT dump.
In the example, VERIFY also printed informational messages for the three blocks it found with solid
one-sytnbol correctable ECC errors. If informational messages' had been suppressed, these messages

would not have printed. However, the number of such blocks would show up in the summary statistics.
No transient errors were detected and, therefore, no count is reported in the summary statistics. Also
note that although no messages were printed for them, the two revectors in the ReT were verified
(as indicated in the summary statistics). Note the odd date for the First Fonnatted field. This date is
the default when no date is supplied by a host or a human during manufacturing format. H structure
inconsistencies had been found, some of the following VERIFY error messages would also print.

7.3.3 VERIFY Error and Information Messages
This section describes error and infonnation messages that may be printed out by VERIFY. Error
messages are arranged alphabetically according to the actual message.
7.3.3.1 Variable Output Fields
Error message fields with variable output print are in bold print. Definitions for these fields are:

xCT = FCT or ReT
n = A decimal number
n. = A decimal LBN, RBN, or XBN
xBN = LBN, RBN, or XBN
o = An octal number
t = Type code: I or W
x = Error: ECC, EDC, etc.
7.3.3.2 Error Message Severity Levels
VERIFY error messages conform to the HSC utility error message format. In each case, the utility
nrune at the start of the message is followed by a letter indicating severity level. These are defined as:
F = Fatal
I Information

t = Type: either W or I, depending on the error
W = Warning

7-19
UTILITIES

7.3.3.3 Fatal Error Messages

Following is a list of the error messages fatal to the VERIFY utility. The program terminates after
printing one of these messages.
•

VERIFY-F All copies of xCT block n are bad!-Prints if all copies of some block in either the
ReT or the FCf are bad. The program cannot continue to run because vital information is missing.
In any case, it has verified that the unit is bad.

• . VERIFY-F Current system sector size is SI2!-Prints if the mode field in FeT block 0 indicates
the unit is formatted in 576-byte mode, but the system sector size is set to 512. In this case,
VERIFY cannot run because it cannot read sectors 576 bytes long.
VERIFY-F Drive went OFFLINE!-Prints if the unit selected goes offline while VERIFY is
running.
•

VERIFY-F Insufficient resources to runt-Prints if VERIFY cannot acquire the necessary
resources to run or the disk functional code is not loaded.

•

VERIFY-F 1/0 request was rejected!-Prints if the diagnostic interface (DDUSUB) rejects a
request to start an I/O operation. It is an indication of a bug in VERIFY and should be reported to
field service support.

•

VERIFY-F Mode is bad or format is in progress on this unitt-Prints if the mode field in FCT
block 0 of the selected unit is not valid.

7.3.3.4 Warning Messages

The following messages are warning messages. In many cases, they are true warnings; in other cases,
they simply precede a reprompt.

•

VERiFY-W n bad PBNs (in brackets above) not in the ReT.-Prints if the LBN/RBN count
is anything other than O. Mter the RCT has been collected, the appropriate subtable of the FeT
is read. The list of PBNs is printed. The collected ReT is searched for RBNs and non-ReT
LBNs corresponding to PBNs; they should be there. If they are not found, the LBN or RBN
corresponding to the PBN is printed in brackets and counted.

•

VERIFY-W Cannot ONLINE unit-Prints if the unit requested is available but the ONLINE
command failed. The unit is released and the user is reprompted for another unit.

•

VERIFY-W Cannot read track with starting xBN n-Prints if this access fails before the request
is sent to the drive. It is usually caused by faiJing hardware. When VERIFY accesses LBN space
or RBN space to check it, it reads all LBNs or RBNs on a track with one request. This operation
is done with VERIFY processing all errors for each LBN or RBN.

•

VERIFY-W Copy n of xCT block n (xBN n.) does not compare-Prints whenever a block is
found that does not compare to the first good one. All copies of every ReT or FCT block are read
and compared to the first good copy read.

•

VERIFY-W Illegal response to start-up question!-Prints if an invalid response is entered for a
start-up question. The program reprompts with the same question.

•

VERIFY-W LBN n., a non-primary revector, is improper.-Prints if an LBN was not a nonprimary revector but was recorded in the RCT as such. When VERIFY reads an LBN with a
header indicating it is a non-primary revector, it looks it up in the collected RCT information and
flags the fact if it was not found to be so.

•

VERIFY-W LBN n., a primary revector, is improper.-Prints if an LBN was not a primary
revector but was recorded in the ReT as such. When VERIFY reads an LBN with a header
indicating it is primarily revectored, it looks it up in the collected ReT information and flags the
fact that it was not found to be so.

7-20
UTILITIES

•

VERIFY-W LBN n. revectors to RBN n. which is bad.-If VERIFY finds an RBN is good (can
be read with error recovery) or only has a forced error (after error recovery), it looks it up in the
collected RCf infomlation. If found, VERIFY marks it as good. If, after the scan is finished, this
flag is not set for an RBN revectored to, this message is printed.

•

VERIFY-W Nonexistent unit number.-Prints if the unit number entered does not correspond to
any known unit. The program reprompts for the unit number.

•

VERIFY-W Unit is not available.-Prints if the unit requested is unavailable. It may be in use by
a host or another diagnostic, or it may be inoperative. The program reprompts for another unit.

•

VERIFY-W xBN n. has a hard EDC error.-Prints for LBNs and RBNs found to have a bad
EDC (neither correct nor forced error). This error is classed as an inconsistency. Only a software
error can result in a record with a bad EDC (unless the WRITE/BAD DKUTD.... command is
used).

•

VERIFY-W xBN n. is bad but not in the RCT.-VERIFY accesses a particular track for LBNs
or RBNs only once. Any LBNs or RBNs where errors are detected in this initial pass are recorded.
They are then read five more times, one LBN or RBN at a time, If errors are detected each time
the LBN or RBN is accessed, and all of the errors are header errors but the LBN or RBN is not
recorded in the RCT, this error message is printed.
VERIFY-W xBN n. I/O error in access (MSCP Code: o}.-Indicates a problem in the drive or
the K. When this message prints, it is an inconsistency. VERIFY provides its own error processing
for records read where the K detects errors. This message prints if the return from the I/O operation
is not a SUCCESS or a forced error, EDC error, or uncorrectable ECC error.

7.3.3.5 Type Error Messages
A list of the type error messages produced by VERIFY follows. The t for type in these messages can
stand for either I (infonnation) or W (warning).

•

VERIFY-t LBN n. has corrupted data (forced error).-Prints with t as a W if answered with a
Y to the prompt about FORMAT. However, if the unit has been subject to bad block replacement,
this message is printed (if at all) with t as an I.
Normally, all LBNs have a correct EDC indicating their data is good. However, a bad hlock
replacement that occurs when the data could not be recovered produces a revectored LBN with a
forced error flag. This indicates the data probably is bad. No such LBNs should exist just after
FORMAT has run.

•

VERIFY-t RBN n. is good but not used for a revector.-Prints if a good RBN with a valid EDC
is found in the verification pass but not recorded in the RCT as used. Unused RBNs on a disk are
written with a forced error indication (the EDC is the complement of the proper EDC). No such
records shou1d exist just after FORMAT has been run. If answered with a Y to the prompt about
FORMAT, this message prints with t as a W. However, if the unit has been subject to bad block
replacement, this message is printed (if at all) with t as an I.

•

VERIFY-t RBN n. marked bad in the RCT was not bad.-Prints with t as a W if answered
with a Y to the prompt about FORMAT. However, if the unit has been subject to bad block
replacement, this message prints (if at all) with t as an I. When VERIFY reads a bad RBN (had
header or header code of bad), it looks it up in the collected RCf information and flags the fact it
was indeed found to be bad. If bad RBNs recorded in the RCT are in fact all right, this flag is not
set. No such RBNs should exist just after FORMAT has been run.

•

VERIFY-t xBN n. Has an Un correctable ECC Error.-Prints when VERIFY discovers any
inconsistency. For example, no LBN should have an uncorrectable ECC error; it should be
revectored either by FORMAT or by bad block replacement. Thus, for an LBN, this error is
considered an inconsistency. Also, FORMAT should have discovered all RBNs with Wlcorrectable
ECC errors and marked them as bad in the RCT. If an RBN is found with an uncorrectable EeC

7-21
UTILITIES

error, but that RBN is not in the Ref, it is also considered an inconsistency. In both of these cases,
this message is printed with t as a W. If an RBN is discovered with an uncorrectable Eee error
marked bad in the ReT, this message prints (if at all) with t as an I.
7.3.3.6 Infonnational Messages

Following are descriptions of the informational messages printed by VERIFY. Note that this type of
message mayor may not need infonnational messages enabled in order to print.
•

VERIFY-I CTRLIY or CTRL/C Abort!-Prints if the user aborts VERIFY by typing a ICTRUVI
or ICTRucl.

•

VERIFY-I Drive is OK.-A tennination message which prints at the end of VERIFY if no
inconsistencies were discovered.
VERIFY-I There were n inconsistencies found for this drive.-A termination message which
prints at the end of VERIFY if inconsistencies were discovered.

•

VERIFY-I Copy n of xCT Block D (xBN n.) is bad.-Prints if informational messages are
enabled for Ref or FCT blocks that cannot be read correctly with error recovery.
NOTE

Table is null or empty (no bad PBNs). This message is printed for null or empty FCTs
whether or not informational messages are enabled.
•

VERIFY-I DBN area should probably be reformatted.-Prints whether or not infonnational
messages are enabled. If more than nine DBNs were detected with EDe errors (not forced errors),
this message prints after the DBN scan.

•

VERIFY-I INITIAL WRITE should be specified for ILEXER.-Prints whether or not
infonnational messages are enabled. If more than nine DBNs were detected with positioner
errors, this message prints after the DBN scan.

•

VERIFY-I LBN n., a primary hati) a bad header (is non-primary).-Prints if infonnational
messages are enabled for LBNs recorded in the Ref as primary revectors but have garbled
headers. Such a condition is abnormal but not erroneous.
VERIFY-I xBN n. has a transient (n out of 6) x error.-Prints if an LBN or RBN has been
read six times with a least one error-free read when informational and transient error messages are
enabled. The number of times out of six that errors were detected is i,ndicated in the message.

•

VERIFY-I xBN D. has a D symbol correctable ECC error.-Prints for LBNs or RBNs with
solid Eee errors (errors on all six accesses) that are correctable when informational messages
are enabled. The highest number of symbols corrected on a seventh access is indicated in the
message.

•

VERIFY-I xBN n. has solid errors: x.-Prints for LBNs or RBNs with errors on all six accesses
when informational messages are enabled. The errors included those other than Eee or BOC. The
record is read a seventh time with error recovery to detennine if the error is correctable. If it is
not, a warning message is printed along with the following:
"NOTE: Table is null or empty (NO BAD PBNs) .

7-22
UTILITIES

7.4 OFFLINE DISK FORMATTER UTILITY (FORMAT)
FORMAT is the utility used to format disks. It formats with either a 512- or 576-byte sector size. It
can be used to format only the read-only DBN space or to format both the LBN area and the read-only
DBN space.
CAUTION

The FORMAT utility destroys user data if used by persons not familiar with DSA.
The DBN area is always formatted. If the user requests it, the LBN area also is formatted. When
the LBN area is formatted, there are two modes of operation; the reformat and the best guess modes.
In reformat mode, the FCf on the disk is used and the XBN area is not formatted. If a reformat is
requested, but the FCf is null or clobbered, a modified best guess mode is used where only the LBN
area is formatted. The main difference between best guess mode and reformat mode is each track is
reread at least three times during the check pass (best guess mode) instead of once (reformat mode). If
any error is detected, the track is reread 20 times instead of 3 times for reformat mode.

CAUTION

Be careful when using ICTRucl or ICTRUVI to abort the FORMAT utility after formatting operations
begin. Doing this may destroy the contents of the FCT and/or the ReT. The FORMAT utility
should only be aborted under fatal-unrecoverable disk failure conditions.

7.4.1 FORMAT Initiation
FORMAT is initiated via the standard CRONIC command syntax RUN DXO:FORMAT.UTL IRETURN/'
Note the last field in the following prompts (shown in square brackets); this indicates the default for
that prompt.
The program prompts for the unit number of the disk to format with the following:
FORMAT-Q Enter unit number to format (U)

[DO]?

The next prompt determines whether the LBN (user data) area should be formatted or whether only the
DBN (diagnostic) area should be formatted. If this prompt is answered with a Y, user data is destroyed.
FORMAT-Q Format user data area (Y/N)

[N]?

If replied with an N or a carriage return only (to obtain the default), the program starts executing and
formatting only the DBN area. If a Y is entered, the program prompts for the sector size to use when

formatting the disk.
FORMAT-Q Enter sector size to be used (512/576)

[512]?

If only the carriage return is pressed, the sector size used is 512 bytes. Otherwise, either 512 or 576

should be entered.
FORMAT-Q Continue if bad block information is inaccessible (Y/N)

[N]?

If an N is entered, reformat mode is used if the FCT is valid. H it is not valid, the program aborts with
an appropriate error message. If Y is entered, reformat mode is used if the FCf is valid or a modified
best guess mode is used if the FCT is null or clobbered.
If the response to the preceding prompt is Y or the response to the destroy FCT prompt is Y, the

program prompts for a serial number:
FORMAT-Q Enter a non-zero serial number (D)?

This serial number is used when all copies of FCT block 0 are unreadable (in modified best guess
mode). FORMAT allows a number of special options, not only for debugging purposes but also to
increase data reliability. To determine if any of these options are desired, the program prompts with the
following:
FORMAT-Q Do you want special options (YIN)

[N]?

7-23
UTILITIES

If the response is N or a carriage return (the default of N), FORMAT starts processing.

If the response is Y, the following three special option prompts appear. The first prompt option is:
FORMAT-Q Revector blocks with 1 symbol ECC errors (YIN)

[N]?

NonnaHy, biocks discovered during me check pass of fonnatting with one-symbol ECC errors are not
retired. The program assumes this level of error is tolerable. If the response to this prompt is Y, all
blocks with solid (nontransient) ECC errors are retired. However, in all cases, blocks with two-symbol
(or more) ECC errors are always retired, regardless of the drive's ECC symbol threshold.
The second special option prompt is:
FORMAT-Q Revector blocks with transient errors (YIN)

[N]?

Mter a track is formatted, it is read either once (reformat) or three times (best guess). If an error is
detected, and the mode is reformat, the track is' read twice more. If any block not previously retired
shows an error twice, it is retired and the track is reformatted with this check pass dQne again. If
no block had errors twice, the track is read 3 more times (reformat) or 20 more times (best guess).
Blocks that show an error only once during all of these reads are normally not retired. Such errors are
considered tolerable transient errors. If the respo~e to this prompt is Y, blocks that show any error are
'
retired.
- ;'-. .,;~·. . . .,t "::~:~_ :~ , .

'Qe third and Jimtl ~l apili~l;~t is.;
EORMAT~

RepRrt

~osition

of bad hJoc~ (YIN)

[N]?

Blocks retired during the format process are reported with a single line printout. The type, block
number, and cause are printed. If the response to this prompt is Y, the PBN number, cylinder, track,
group, and position are also printed on a subsequent line.
The user can enter ICTRuzl at any prompt to use the default for L.1.e remainder of the responses. Also,
the responses to subsequent questions can be supplied at any question by typing the responses separated
by commas. For example, if unit Dl33 has an FCT and is to be fonnatted in 512-byte mode with no
special option.~, the user could type D133,Y"" IRETURNI at the first prompt.
~

".,---1 ',....... . . .

. . . ,. . '.,

... ,

7.4.2 FORMAT Sample Session
The following is a sample session using FORMAT. User input is in bold print.
"Y
HSC70> RON OXO:FORMAT IRETURN I
FORMAT-Q Enter unit number to format (U) [~O]? 0133 IRETmllil
FORMAT-Q Format user data area (YIN) [N]? Y IRETURN I
FORMAT-Q Enter sector size to be used (512/576) [512]? IRETURN I
FORMAT-Q Use existing bad block information (YIN) [Y]? IRETURN I
FORMAT-Q Continue if bad block information i~ inaccessible (YIN) [N]? IRETmllil
FORMAT-Q DO you want special options (YIN) [N]? Y IRETURN I
FORMAT-Q Revector blocks with 1 symbol ECC errors (YIN) [N]? IRETmlli I
FORMAT-Q Revector blocks with transient errors (YIN) [N]? IRETURN I
FORMAT-Q Report position of bad blocks (YIN) [N]? IRETURN I
FORMAT-S Format begun.
FORMAT-I
2 cylinders left in OBN space at 00:05:34.60.
FORMAT-I 275 cylinders left in LBN space at 00:05:39.60.
FORMAT-I Bad LBN 237213 (FCT), in the RCT area.
FORMAT-I 265 cylinders left in LBN space at 00:06:05.60.
FORMAT-I 255 cylinders left in LBN space at 00:06:31.40.

FORMAT-I
25 cylinders left in LBN space at 00:16:36.20.
FORMAT-I
15 cyLrnders left in LBN space at 00:17:02.00.
FORMAT-I
5 cylinders left in LBN space at 00:07:28.40.
FORMAT-S Format completed.

7-24
UTILITIES

o Bad RBNs,
2 Revectored LBNs,
2 Primary Revectored LBNs,
o Non-Primary Revectored LBNs,
1 Bad Blocks in RCT Area,
o Bad Blocks in DBN Area,
o Bad Blocks in XBN Area,
9 Blocks Retried on Check Pass.
FORMAT-I FCT was used successfully.
FORMAT-I Stats:

***********************************************************

*
*
*

VERIFY must be RUN to complete FORMAT verification!

*
*

***********************************************************

CAUTION

The message in the box indicates VERIFY must be run to complete verification. This is an
essential step and should not be skipped.
The preceding example is the output for an actual session for an RA80 disk with one bad PBN in the
FCT. Notice the message that indicates it was retired because it was in the FCT and also the RCT
area. Note the informational message that is printed every 10 cylinders. This confirms that progress is
actually being made and to show at what rate. Also, note the two LBNs that were retired because they
had two-symbol ECC errors; they became primary revectors. The error log messages were printed for
them because, in the case of an RA80, two symbols are in excess of the ECC drive threshold.
NOTE

The final statistics indicate two LBNs were revectored and one bad LBN was found in the RCT
area. The nine Blocks Retried on Check Pass include the two bad LBNs plus seven other blocks
with transient errors only and therefore not retired. The bad block in the RCT was not retried in
the check pass because it was known to be bad from the FCT. This would be true for any blocks
retired due to their location in the FCT. The final message indicates an FCT was found and was
successfully used.

7.4.3 FORMAT Errors and Information Messages
This section describes the error and information messages printed by FORMAT. Error messages are
arranged alphabetically according to the actual message.
7.4.3.1 Error Message Variables

Variable output in the error and information messages is shown in bold print. These fields are formed
as follows:
n = A decimal number
x = The way a block was found bad: FCT or check
xBN = A space: DBN, XBN, or LBN
hh = Hours
nun = Minutes
ss = Seconds
xx = Hundredths of a second

7-25
UTILITIES

7.4.3.2 Message Severity Levels
FORMAT error messages conform to the HSC utility error message format. In each case, the utility
name at the start of the message is foHowed by a letter indicating severity level. These are defined as:

F = Fatal
I = Information
E = Error
S = Success
W = Warning
7.4.3.3 Fatal Error Messages
This section describes the fatal error messages printed by FORMAT.

•

FORMAT-F Cannot position to DBN areal-Attempts to verify it has positioned the heads to the
DBN area before it fonnats the disk unless FORMAT is running in best guess mode. FORMAT
does this by reading the first sector of every track in the DBN read/write area until a sector is read
without a header error. This fatal error message is printed if no such sector can be found.

•

FORMAT-F Current maximum sector size is 512!-Prints if the user requests a 576-byte sector
size but the system sector size is set to 512. In this case, FORMAT cannot run because I/O cannot
be done with sectors that are 576 bytes long.

•

FORMAT-F DBN format error (drive FORMAT command Failed)!-Prints if a FORMAT
command fails for five retries when formatting the DBN area.
FORMAT-F Drive does not support 576 mode on this medial-Prints if the user requests a
576-byte sector size for a drive that does not support it.

•

FORMAT-F Drive is write-protected!-Prints if the requested drive is hardware write-protected
and therefore cannot be formaued~
FORMAT-F FCT Does not have enough good copies of each block!-Prints if any block in the
FeT does not have two good copies.

•

FORMAT-F FCT is improper!-Prints if one or more PBNs remain to be processed. When the
program finishes fonnatting the LBN area, it checks to see if all PBN s in the FCf have been
processed. It usually indicates an FCI' where some PBNs are out of order.
FORMAT-F FCT nonexistent!-Prints if the FCI' is null or clobbered, and the user has instructed
the program not to continue.

•

FORMAT-F FCT read error!-Prints if all copies of some given block of the FCI' cannot be
successfully read.

•

FORMAT-F FCT write error!-Prints if all copies of some given block of the FCI' cannot be
successfully written.

•

FORMAT-F Formatter initialization error!-Prints if FORMAT cannot acquire enough Data
Buffers or control blocks to start formatting, or if the disk functional code is not loaded.

•

FORMAT-F GET STATUS failure!-Prints if the unit requested is not available or cannot be
brought online.

•

FORMAT-F LBN format error (drive FORMAT command failed)!-Prints if a FORMAT
command fails for five retries when formatting the LBN area.

•

FORMAT-F Nonexistent unit number!-Prints if the unit requested does not exist.

•

FORMAT-F RCT does not have enough good copies of each block!-Prints if any block in the
RCT does not have· two good copies.

•

FORMAT-F RCT is full!-Prints if so many bad blocks are encountered that the RCI' overflows.

7-26
UTILITIES

•

FORMAT-F ReT read error!-Prints if all copies of some given block of the ReT cannot be
successfully read.

•

FORMAT-F ReT write error!-Prints if all copies of some given block of the ReT cannot be
successfully written.
FORMAT-F SDI receive error!-Prints if a track cannot be read at all after it has been
formatted.

•

FORMAT-F Too many bad RBNs found before ReT was formatted.-Prints if more RBNs
than can be recorded in memory are encountered before the ReT area has been formatted.

•

FORMAT-F Unsuccessful SDI command!-Prints if the drive fails to respond to an SDI
cOlrunand. FORMAT issues SEEK, RECALIBRATE, and DRIVE CLEAR SDl commands.

7.4.3.4 Warning Message

The FORMAT utility prints only one warning message.
•

FORMAT-W WARNING: Possible head addressing problem.-Prints if no sector was
successfully read from one or more tracks in the xBN area. Note that all cylinders are checked.
This is a simple check for a bad head.

7.4.3.5 Infonnation Messages

Following are the informational messages printed by FORMAT.
•

FORMAT-I Bad LBN n (x), a non-primary revector.-Prints for LBNs retired by being
revectored to some RBN other than the primary RBN; they are marked in the RCT as nonprimaries.
They are formatted with a header code of non-primary or with a header code of bad if their header
area is bad.

•

FORMAT-I Bad LBN n (x), a primary revector to RBN n.-Prints for LBNs retired by being
revectored to the first RBN on the same track; they are marked in the ReT as primaries. They are
formatted with a header code of primary.

•

FORMAT-I Bad LBN n (x), in the ReT Area.-Prints for retired LBNs in the ReT area. They
are formatted with a header code of bad.
FORMAT-I Bad RBN n (x).-Prints for retired RBNs. They are marked bad in the ReT and are
formatted with a header code of bad.

•

Cylinder n, Group n, Track n, Position n, PBN n.-Prints following the preceding four
messages, if the user requested the special option to print bad block position.

•

FORMAT-I CTRLIY or CTRL/C abort!-An informationa1 message and prints if the user aborts
FORMAT by typing a ICTRUVI or ICTRucl Note, this probably leaves the disk in an unusable state
if the fonnat has begun.

•

FORMAT-I FCT was not used.-Prints if a null or clobbered FCT was found on the disk or
generated at the request of the user (best guess mode).

•

FORMAT-I FCT was used successfully.-Prints if a valid FCT was found on the disk and used.

•

FORMAT-I n Cylinders left in xBN space at hh:mm:ss.xx.-Prints after every 10 cylinders are
formatted in order to record the progress of the FORMAT program.

•

FORMAT-I Only DBN area formatted (n bad DBNs).-Prints if the user requested formatting
of the DBN area only. It prints after the format of the DBN area is completed. Mter this message
prints, the program terminates.

7-27
UTILITIES

7.4.3.6 Error Messages

Following are the error messages printed by FORMAT.
•

FORMAT-E Illegal response to start-up question!-Prints if an invalid input is supplied for a
start-up question. The program reprompts with the same question.
FORMAT-E Nondefaultable parameter.-Prints if the user enters only a carriage return,
requesting the default for the only nondefaultable parameter (the serial number). The program
reprompts for the serial number.

7.4.3.7 Success Messages

Following are the FORMAT success messages.
•

FORMAT-S Format begun.-Prints when FORMAT actually begins formatting the disk.

•

FORMAT-S Format completed.-Prints after the format process is done, and all verification tests
are complete.

7.5 RX FORMAT UTILITY (RXFMT)
The RXFMT utility program allows the user to format and verify RX33 diskettes. These are 5 1/4inch, two-sided, double-density diskettes available from DIGITAL. This utility is used only to format
diskettes for the HSC70. The program should complete in less than five minutes.
CAUTION

Running RXFMT destroys any data present on the diskette.

7.5.1 RXFMT Initiation
To run the RXFMT utility, select an HSC70. At the KMON prompt, type:
Ay
HSC> RON dev:RX!'MT

IRETURN I

Where dev is the name of the drive containing the RXFMT utility.
The program prompts the user from beginning to end. As with all HSC prompts, material contained in
square brackets is the default. To accept the defa,lt, press,'RETURNI. With square brackets that do not
contain material, the value has to be supplied and RETURN pressed.
To abort the utility, enter ICTRUV' or ICTRucl at any point. However, note that this action leaves the
disket te in an unknown state.
After the RUN command is input, the utility prompts:
RXFMT-Q Unit to format []?

RXFMT allows the user to select either drive to run the program.
Following is an example of a typical RXFMT session.

7-28
UTILITIES

HSC70> RUN RXI'MT IRETURN I
RXFMT-I RXFMT - RX33 Diskette Formatter Program
RXFMT-Q Unit to format (DXO: or DX1:)? DX1: I~TURNI
RXFMT-Q Really perform format (YIN)? Y IRETURN I
RXFMT-Q Mount diskette in unit DX1: (write enabled)
Press RETURN to continue:
RXFMT-S Beginning Format ...
RXFMT-I Formatting track 0, side 0, LBN 0
RXFMT-E No media mounted in unit
RXFMT-Q Mount diskette in unit DX1: (write enabled)
Press RETURN to continue:
Formatting track 8, side 0, LBN 240
Formatting track 16,side 0, LBN 480
Formatting track 24,side 0, LBN 720
Formatting track 32,side 0, LBN 960
Formatting track 40,side 0, LBN 1200
Formatting track 48,side 0, LBN 1440
Formatting track 56,side 0, LBN 1680
Formatting track 64,side 0, LBN 1920
Formatting track 72,side 0, LBN 2160
RXFMT-S Beginning Verification ...
RXFMT-I Verifying track 0, side 0, LBN 0
RXFMT-I Verifying track 8, side 0, LBN 240
RXFMT-I Verifying track 16,side 0, LBN 480
RXFMT-I Verifying track 24,side 0, LBN 720
RXFMT-I Verifying track 32,side 0, LBN 960
RXFMT-I Verifying track 40,side 0, LBN 1200
RXFMT-I Verifying track 48,side 0, LBN 1440
RXFMT-I Verifying track 56,side 0, LBN 1680
RXFMT-I Verifying track 64,side 0, LBN 1920
RXFMT-I Verifying track 72,side 0, LBN 2160
RXFMT-I Format Successfully Completed
RXFMT-I Program Exit

7.5.2 RXFMT Messages
Messages that may occUr while RXFMT is running are described in the following list.
•

RXFMT-E No media mounted in unit-Unit does not contain an RX33 diskette.
RXFMT-E Please answer either Y or N-Most likely the IRETURNI key was pressed before the
question was answered.

•

RXFMT-E Requested unit is unavailable-The unit specified in the command line is
unavailable.

•

RXFMT-W Hardware or Verify errors. FORMAT NOT SUCCESSFUL-The target medium
is not a valid formatted diskette. This message is produced after the following error messages:
RXFMT-E Read failure on unit DXn: during verification pass at block LBN nnnn
continuing.•. -This error does not cause RXFMT to halt. The program continues to the
end and produces the RXFMT-W Hardware or Verify warning tnessage.
RXFMT-E Write failure on unit DXn: during Format pass at block LBN nnnn
continuing... -This error does not cause RXFMT to halt. The program continues to the
end and produces the RXFMT-W Hardware or Verify warning message.
RXFMT-W Invalid device name DXn:-The unit name specified in the command line is
invalid.

•

RXFMT-W No default unit allowed-RXFMT does not allow a default to either disk drive. The
user must select either DXO: or DX1:.

7-29
UTILITIES

•

RXFMT-F Unable to allocate sufficient resources-There is insufficient memory available to
perform the format. This may be a transient condition. Try RXFMT at a later time.

•

RXFMT-F Aborting-RXFMT tries to format and verify 10 times. If no progress is made,
RXFMT issues an error messa~e and the program exits. This message is also displayed after the
user eniers a !CTRUY! or !cTRLle!. Try a different diskette. If the problem persists, replace the disk
drive.

•

RXFMT-F Error comparing track-RXFMT detected an inconsistency. The data read from the
diskette in the verify pass did not match what was written. Retry.

•

RXFMT-F Error formatting track-This could be caused by a bad diskette or a hardware
problem. Retry. If the problem still persists, try a different diskette.

•

RXFMT-F Error reading track-This error could be caused by a bad diskette or a hardware
problem. RXFMT tries to verify the formatting 10 times. If no progress is made, the program
exits. Run the program again. If the problem persists, use a different diskette.

•

RXFMT-F Unable to allocate sufficient mapped memory-Not enough blocks in Program
memory are available to use as buffer space. Try again later.

•

RXFMT-F Unable to allocate sufficient XFRBs-The common pool did not contain enough
memory to allocate an XFRB, required for RXFMT using load media. This is a transient condition;
try again later.

•

RXFMT-W About to format diskette in boot device-RXFMT warns the user the utility is about
to format the diskette in the boot device. The user must be very cautious when running RXFMT.
As a result, RXFMT not only asks whether reformatting should start, but also outputs this warning
lnessage.

•

RXFMT-I Formatting track, side, LBN-RXFMT did not encounter any problem while
formatting previous track, and simply reports.

•

RXFMT-I Please specify a valid unit-The user must specify the unit 10, either OXO: or OXl:.

•

RXFMT-I Program Exit-The program is finished and is exiting.
RXFMT-I Verifying Track, side, LBN-RXFMT did not encounter any problems while verifying
the previous track.

•

RXFMT-S Format successfully completed-RXFMT completed without any errors or
interruptions .

•

RXFMT-Q Unit to format (DXO: or DXl:)?-RXFMT asks which unit the user will use to
format the diskette.

•

RXFMT-Q Really perform format (Y/N)?-RXFMT asks if the user is ready to format the
diskette. Ensure the diskette is loaded into the correct drive.

•

RXFMT-Q Mount diskette in DXn (write-enabled)-RXFMT directs the user to load the diskette
in the correct drive.

7-30
UTILITIES

7.6 VIDEO TERMINAL DISPLAY (VTDPY)
VTDPY is a utility for gathering system statistics. This uti1ity displays, on a continuing basis, activity
within the HSC. VTDPY can display system throughput, AVAILABLE or ONLINE status of disk
and tape drives, and utilities running on other tenninals. This utility also indicates which nodes have
Virtual Circuits, connections, and multiple connections to the HSC.
NOTE

Do not run VTDPY using the command SET HOST/HSC through the Diagnostic and Utility
Protocol (DW). DUP cannot manage VTDPY because too much optional interrupt data is
produced. This problem occurs in systems using VMS versions previous to VMS Version 4.6.
(The problem was fixed in VMS Version 4.6.)
This utility requires a video terminal and does not display on an LA12. Either a VT100, VT220, or
VT320 set at 9600 baud must be attached to the EIA port on the HSC to run VTDPY.
To run VTDPY, enter at the prompt:
"Y
HSC> RON dev:VTDPY (update-interval)

I~TURNI

In this command, update-interval is in seconds, anywhere from 2 to 420. If this update interval is not
provided, VTDPY prompts:
VTDPY-Q Interval (sees) ?

If the response is outside the allowable range, VTDPY displays an error message. The higher the

number for the update-interval, the smaller the perfonnance impact on the HSC.
VTDPY tenninates after the user enters ICTRUVI or ICTRucl. The screen is cleared upon termination.

7.6.1 VTDPY CTRL/x Display Commands
There are various CTRL/x commands that can be used while VTDPY is running.
ICTRUE~Tape Status is displayed on the next refresh. Thereafter, the display alternates the Disk

Status on subsequent refreshes.
•

ICTRUD~Disk Status is displayed on the next refresh. Thereafter, the display alternates the Tape

Status on subsequent refreshes.
•

ICTRUV~Host Path Status information (Le., A, B, or a diamond) displayed only on the next refresh.

• ICTRUW~Refresh the screen.
7.6.2 VTDPY Error Messages
This utility has only two error messages.
•

VTDPY-E Illegal interval value (2 to 420 seconds)-The user has entered an update interval
outside the range permitted. VTDPY reprompts for the update interval. Re-enter a value within the
correct range.

•

VTDPY·F Insufficient common pool-This message indicates insuf1:cient memory to run VTDPY.
Try again later.

7-31
UTILITIES

7.6.3 VrDPY Display Example
Following is an exmnple of a VTDPY screen disp]ay.
HSC70 V3.70 C3PO

Id 000000000000 On 14-Apr-1986 12:28:13.12
40 sectors/Sec

39 Work Requests/Sec

42.9% Idle

Free Lists
CTRL Blks
2269 +
32 +
SLCB/OCB
Buffers
889 +
Pool Sizes
SYSCOM
1800 +
6504 +
Kernel
821120 +
Program
Control
32436 +
Data B/W used:

.0%

Host Status
1111111111
+1234567890123456789
OMM .. C .... C .....• M....
20.M ... V ..••...........

Process Pr St
Kernel
4 VTOPY 11 Rn
24 SYSOEV 1 Bl
50 DEMON 11 Bl
52 POEMON 7 Bl
54 PSCHEO 13 Rn
72 DISK
9 Rn
110 ECC
6 Bl
120 TAPE
8 Bl
122 TTRASH 7 Bl
4 Bl
124 HOST
126 POLLER 5 Bl
130 SCSOIR 5 Bl
146 OPOUT 10 Bl
150 OP20UT 10 Bl
9 Bl
152 OUP

Time%
16.4%
19.2%

UP: 113.49

o Records/Sec

Disk Status
1111111111
+1234567890123456789

o .•.....••.......••••
42.9%
16.0%

.9%
.9%

20A.A .•.••.•.•. A •.....
40 . . . . . . . . . . A.A.A ....•
60 .AA ••••••• 0 •• A •• 0 •••
80 ..•........•..•.....
100 .•.•...•••.•.••.•.••
120 .•.••••••.•......••.
140 .•..••.••.••..••...•
160 . . . . . . . . . . . . . . . . . . . .
180 ....•.......••.... A.
200A .•.............•...
220 . . . . . . . . . . . • . . . . . . . .
240 ......•.•...•.••..•

7.6.3.1 Display Explanation
The previous display example constantly changes as different processes run in the HSC. These changes
are made automatically except for fields relating to HSC memory. Memory statistics are updated by
typing ICTRuWI. The major fields are explained as follows:
HSC70 V370 C3PO

Id 000000000000 On 14-Apr-1986 12:28:13.12

UP: 113.49

The top line, reading from left to right, shows the HSC model number (HSC70), the baselevel of the
operating software (V3.70), the system name (C3PO), the system ID (Id) which is any hexadecimal
number unique to the cluster (in this case OooODD), time, and date. The last number on the right
indicates the hours and ffiL.,utes t.~e HSC has been fUI'.uYJ.ing since the last boot or reboot.
42.9% Idle

39 Work Requests/Sec

40 Sectors/Sec

o Records/Sec

This second line in the display shows the percentage of current P.io idle time, average number of work
requests (Le., MSCP and TMSCP) per second, number of disk data sectors transferred per second, and
number of tape data records transferred per second. These numbers are normalized to match the update
interval.
7.6.3.2 Free Lists and Pool Size Display Explanation
This field represents the quantity of available memory and memory structures. The Si7--CS are usually
followed by plus (+) signs. H the sizes are followed by minus (-) signs, the system is in memory
deficit. Extremely prolonged memory deficit results in HSC slowdown and could eventually result in
an HSC crash.
Free Lists
CTRL Blks
2269 +
SLCB/OCB
32 +
Buffers
889 +
Pool Sizes
SYSCOM
1800 +
Kernel
6504 +
Program
821120 +
Control
32436 +

7-32
UTILITIES

7.6.3.3 Data Bandwidth Display Explanation

This display shows the percentage of data bandwidth used. This is an instantaneous display and
may often show 0% when the HSC is busy because the sampling interval missed the instantaneous
bandwidth usage.
Data B/W used:

.0%

7.6.3.4 Host Connection Display Explanation

This Held indicates the host connection status. The line below Host Connections shows the node
number (in the range 0 through 31) of the hosts in the cluster. The host display is read by adding the
base number at the far left of the line 0 and 20 to the number above the display. For example. nodes
16 and 21 show multiple connections. If no letter corresponds to the node number, that node number is
not a currently active host. Is a V appears on that line, a Virtual Circuit only is open and no connection
is present (host usually in a transient state). A C on this line indicates one connection to that host and
an M indicates multiple connections. Because each host can make a separate connection to each Disk,
Tape, and DUP servers, this field frequently shows multiple connections.
Host Connections
1111111111
+1234567890123456789
O~ •• C •••• C •••••• M•••

20.M ... V .•............

7.6.3.5 Host Path Status Display Explanation

The alternate Host Path Status display contains CI path status information. Each position can contain a
diamond symbol, an A, or a B. If one path goes down. this display alternates with the Host Connection
display. The meanings of the symbols are as follows:

•

A diamond symbol equals normal operation in any position with a connection .
An A or B indicates only one path is operational. If an A is displayed, Path A is running but Path
B is not; if a B is displayed, Path B is running but Path A is not. Either letter probably indicates a
hardware problem.
Host Path Status
1111111111
+1234567890123456789
O"'A ......... B •••••• A •••

20.

••• A

••••••••••••••

This example shows that nodes 0, 4, 21, and 25 have both paths operating. Nodes 1 and 16 only have
Path A operating and node 9 only has Path B operating.
NOTE

A t.rue video display contains solid diamond symbols which are indicated in this example as a
caret (A).

7-33
UTILITIES

7.6.3.6 Process Priority Status Display Explanation

This example shows the Process Priority Status display.
Process Pr St
Kernel
4 VTDPY 11 Rn
24 SYSDEV 1 Bl
50 DEMON 11 Bl
52 PDEMON 7 Bl
54 PSCHED 13 Rn
72 DISK
9 Rn
6 Bl
110 ECC
8 Blo
120 TAPE
122 TTRASH 7 Bl
4 Bl
124 HOST
126 POLLER 5 Bl
130 SCSDIR 5 Bl
146 DPOUT 10 Bl
150 DP20UT 10 Bl
9 Bl
152 DUP

Time%
16.4%
19.2%

42.9%
16.0%

.9%
.9%

The headings in this display (from left to right) are defined as follows:
The first column contains the process number.
•

The Process column shows the name of the process running at the time.

•

The Pr column shows the priority of the process.
The St column shows the status of the process, either running Rn or blocked BI.
The Time% column is the percentage of P.io time each currently-running process is using.

Certain process names in the first column under Kern~1 (the operating system) are defined as follows:
•

In this case, VTDPY. However, it could be another utility (in which case the priority number would
change also).

•

SYSDEV is the load device driver.

•

DEMON indicates demand and automatic device integrity tests are running.

•

PDEMON indicates periodic device integrity tests are running.
PSCHED is the scheduler for periodic device integrity tests. This is the HSC idle loop.

•

DISK is the Disk Server.

•

ECC is the Error Correction Code process and is always displayed when disk I/O is indicated.

•

TAPE is the Tape Server.

•

TIRASH is always displayed when the Tape Server is active. It is the process that sends tape error
logs to the host.

•

HOST is the process that interfaces to the host. It is always present.

•

POLLER polls for the host process and is always present when a connection is present.

•

SCSDIR processes directory requests from the host.

•

DPOUT and DP20UT are the I/O from two different DUP processes.

•

DUP is the Diagnostic and Utility Protocol Server.

Note, not all processes are necessarily shown. Because of limited space on the screen, the display of
some processes may be truncated and the CPU time percentages may not total 100 percent due to the
point in time in the polling interval when data is sampled.

7-34
UTILITIES

7.6.3.7 Disk or Tape Status Display Explanation

The last area in the display can indicate either Disk Status or Tape Status. This rightmost field
fluctuates between the two displays whenever both device types are connected to the HSC.
Disk Status
1111111111
+1234567890123456789

o ...••••••..••••.•••.
20A.A ••.••••••• A •..•.•
40 ••••••.••• A.A.A •••.•

60.AA . . . . . . . 0 •• A •• 0 •••
80 . . . . . . . . . . . . . . . . . . . .
100 ••••.•.•.••.•...••..

120 . . . . . . . . . . . . . . . . . . . .
140 .••.••••••••••••••..

160 • . . . . . . . . . . . . . . . . . . .
180 ••••••.••••••.•••• A.
200A •••••••••••••••••••
220 ••••••••••••.•••••••

240 . . . . . . . . . . . . . . . . . . .

The line immediately under Disk Status indicates the following unit numbers are augmented by 10
from the base number in the leftmost column. To find the identification number of the disk indicated
by a single letter in this field, count from the left. For instance, on the 20s line, the third A would be
disk unit number 33.
A letter anywhere in the field has a particular meaning for the particular disk unit identified, as follows:
An A indicates the drive is available but not mounted.
•

An () indicates Online status. The drive is in use by a host, an HSC utility, or an HSC device
integrity test.

A D indicates the HSC is connected to duplicate units (two or more drives with the same unit
number).
A U indicates the drive went into an undefined slate.
The letters and method of determining tape drive ID number are the same when tape status is displayed.
However. one additional letter can be shown~ an F, indicating no tape is mounted on the tape drive.

7.7 DISK RCT/FCT MERGE UTILITY (DKRFCT)

DKRFCf is the HSC utility used to update the Factory Control Table (FCf) on a disk to include
entries in the Revector Control Table (RCT) which are not present in the FCT. Such entries could exist
because of bad blocks detected during the check pass of the FOR1MAT ~rlgram,
durinf nonnal I/O
by error recovery (replaced by BBR). Execution is terminated by CTRUC, CTRUY, CTRUZ or the EXIT
command.

7.7.1 DKRFCT Initialization
DKRFCf is initiated via the standard CRONIC command syntax RUN DKRFCT IRETURN!. During
initialization, DKRFCf allocates an XFRB, loads the Disk Function Code (DFUNCT), and verifies
enough FCBs are available. IT DKRFCf cannot allocate an XFRB, load DFUNCf, or find enough
FRBs, the program automatically prints the appropriate error message and exit.

7-35
UTILITIES
"'Y
RON OltRFCT

IRETURN I

%DKRFCT-F-NOCODE-Disk functional code is not loaded!!
or
%DKRFCT-F-NOFCB-Not enough FCBs available!!
then
%DKRFCT-I-EXIT-Exiting!!

7.7.2 DKRFCT Sample Session
After a successful initialization, DKRFCT prints the following messages:
"'y
RON OltRFCT

IRETURN!

DKRFCT - HSC Disk RCT/FCT Merge Utility Vl.00
%DKRFCT-Q-SOURCE-Unit for RCT/FCT Merge [On]:

Reply with the appropriate unit number and IRETURN I.
Following is an example session that resulted in no new PBNs added to the FeT.
"'Y
RON OltRFCT

IRETURN!

DKRFCT - HSC Disk RCT/FCT Merge Utility Vl.00

IRETURN I

%DKRFCT-Q-SOURCE-Unit for RCT/FCT Merge [Dn]: 011
Serial Number:
Mode:
First Formatted:
Date Formatted:
Format Instance:
FCT:
Bad PBNs in FCT:

0872548990
512
II-Dec-1984 11:28:18.00
12-Dec-1984 00:00:00.00
1
VALID
163 (512),

Scratch Area Offset: 77
Size (Not Last) :
95
Size (Last):
95
Flags:
Format Version:

000000

%DKRFCT-I-NULLIST-There are no PBNs to be added to the FCT.
%DKRFCT-I-EXIT-Exiting.

Following is an example session that resulted in two new PBNs added to the FCf.
"'Y
RON OlaU'CT

IRETURN!

DKRFCT - HSC Disk RCT/FCT Merge Utility Vl.00
%DKRFCT-Q-SOURCE-Unit for RCT/FCT Merge [Dn]: 09
Serial Number:
Mode:
First Formatted:
Date Formatted:
Format Instance:
FCT:
Bad PBNs in FCT:

0000121558
512
I-Mar-1987 06:42:02.00
8-Dec-1987 09:22:16.61
3
VALID
673 (512), 0 (576)

IRETURN I

7-36
UTILITIES
Scratch Area Offset: 139
Size (Not Last) :
641
Size (Last):
433
Flags:
Format Version:

000000

PBNs To Be Added To 512 Byte Subtable
(00) 895867 (LBN 878631),

(00) 196917 (LBN 193099)

%DKRFCT-I-COPYDO-Copying new FCT from scratch area to subtable.
%DKRFCT-I-EXIT-Exiting.

7.7.3 DKRFCT Error Message Severity Levels
DKRFCf error messages conform to the HSC utility error message format. In each case, the utility
name at the start of the message is followed by a letter indicating severity level. These are defined as
follows:
F =Fatal
E = Error
I = Information
7.7.3.1 Fatal Error Messages

The following lists the error messages fatal to the DKRFCf utility.
NOTE

The program terminates after printing a fatal error message.
•

DKRFCT.F·BADFCT All copies of FCT block n are bad!!-Prints if all copies of some block
in the FCf are bad. The program cannot continue to run because vital information is missing, but
it has verified the unit is bad. The program terminates after this message is printed.

•

DKRFCT-F-BADRCT All copies of RCT block n are bad!!-Prints if all copies of some block
in the RCT are bad. The program cannot continue to run because vital information is missing, but
it has verified the unit is bad. The program terminates after this message is printed.

•

DKRFCT-F·INVHDR Invalid header n in 1/0 call! I-Prints if DKRFCf cannot read a header.
The program terminates after this message is printed.

•

DKRFCT-F-LOSTIO 110 lost!!-Starts an I/O operation through the diagnostic interface and
waits for the I/O to complete. If an error occurs or there is no I/O outstanding, the error message
is printed. The program terminates after this message is printed.

•

DKRFCT-F-NOBUF Not enough buffers available!!-Prints if DKRFCf cannot acquire the
necessary resources to run. The program terminates after this message is printed.

•

DKRFCT-F-NOCODE Disk functional code is not loaded!!-Prints if the disk functional code
cannot be loaded. The program terminates after this message is printed.

•

DKRFCT.F-NOFCB Not enough FCBs avaiiable!!-DKRFCf requires a minimum of five
FCBs. This message prints if available FCBs are less than five. The program terminates after this
message is printed.

•

DKRFCT-F-NOTFMT Unit is not formatted; mode is unknown!!!-Prints if the unit was not
formatted or if the mode field in FCf block 0 of the selected unit is not valid. The program
terminates after this message is printed.

7-37
UTILITIES

7.7.3.2 Error Messages
Following is a list of DKRFCT error messages.

DKRFCT-E-BADUNIT Illegal unit number specified-Prints jf the unit number entered does not
correspond to any known unit. The prognun reprompts for the unit number.
•

DKRFCT-E-lNUSE Specified unit is in use, broken, or otherwise unavailable-Prints if the
unit requested is unavailable. The unit may be in use by a host or another diagnostic or it may be
inoperative. The program reprompts for another unit number.

•

DKRFCT-E-OFFLlNE Specified unit is offline-Prints if the specified unit is offline or goes
offline while DKRFCT is running. The program terminates after this message is printed.

•

DKRFCT-E-DUPL Unit n is a duplicate-Indicates the HSC is connected to duplicate units (two
or more drives with the same unit number).

7.7.3.3 Information Messages
Following is a list of DKRFCT information messages.

•

DKRFCT-I-COPYCON Previous DKRFCT run was interrupted; COpy restarted-Prints if
DKRFCT was interrupted during the previous run. The program prints the COpyCON message
and restarts COPY. The program interruption may have been caused by an operator intervention or
by the unit going offline.
DKRFCT-I-COPYDO Copying new FCT from scratch area to subtable-Prints when the
program starts reading the scratch area and copying the new FCTs to the subtable.

•

DKRFCT-I-EXIT Exiting-Prints when the program is complete, aborted by a ICTRucl, ICTRUVI,
ICTRUZI, or after a fatal or information error message defaults to the EXIT command.

•

DKRFCT-I-FULL Too many PBNs to add; please RUN DKRFCT again-Prints when the
PBNs to be added exceed the allocated resource limits. The program exits after printing the
DKRFCT FULL message. To add the remaining PBNs, run the DKRFCf utility again.

•

DKRFCT-I-NONEW New FCT identical to old; FCT not changed-Prints when there are no
new changes to be added to the Fer.

•

DKRFCT-I-NULLIST There are no PBNs to add to the FCT-Prints when the program does
not find a PBN list for merge. The program exits after printing the NULLIST message.

Hsc
(("

C...ft~CJ<

C.lfl)S~.b

LooK

t4T
IF 20

3) FIND

#" N

G-o

To A-PPNbx

TeflPs

SEcTiON.

Lool' up 11 CR.A-SH c.ob£ •

BAD 1'<£ ~ V~~ TOR. STt1]1J.s
- L 001< up IN II PPNbX. D.

8-1
TROUBLESHOOTING TECHNIQUES

8
TROUBLESHOOTING TECHNIQUES
8.1

INTRODUCTION

This chapter describes the types of errors occurring during HSC boot and operation. The major
divisions are initialization errors and system-type errors. Initialization errors occur while the HSC is
trying to boot. System-type errors occur while the HSC is running functional code. System-type errors
may be reported to a host node and possibly the HSC console device. Some system errors may result
in the HSC crashing and rebooting. System errors include MSCP, TMSCP, BBR, and out-of-band
errors.

8.2 HOW TO USE THIS CHAPTER
Initialization error indications are displayed by the Operator Control Panel (OCP) fault codes and the
module LEOs. In addition, the bootstrap diagnostics may produce error messages printed out to the
_console. Read Section 8.3 for an understanding of initialization errors that do not produce a message.
AU errors displayed as En-gHsh messages on the console are li-sted in alphabetical order in Section 8.5
and are listed in this manual's index. Section 8.3 divides initialization errors into three types:
OCP fault codes
•

Module LEOs

•

Boot diagnostic messages

HSC console error message descriptions for system-type errors are described in this chapter and are
organized into the following sections:
•

MSCprrMSCP errors, Section 8.4.1
Controller errors, Section 8.4.2.5
MSCP SOl errors, Section 8.4.2.6
Oisk transfer errors, Section 8.4.2.7
BBR errors, Section 8.4.3

•

TMSCP errors, Section 8.4.4
STI communication or command errors, Section 8.4.4.1
STI formatter error log, Section 8.4.4.2
STI drive error log, Section 8.4.4.3
Out-of-band errors, Section 8.4.5
HOST-x-CI errors, Section 8.3.2.5
SYSOEV-x-Load device errors, Section 8.4.5.1

8-2
TROUBLESHOOTING TECHNIQUES

DISK-x-Disk functional errors, Section 8.4.5.2
TAPE-x-Tape functional errors, Section 8.4.5.3
SINI-x-Miscellaneous errors, Section 8.4.5.4
00

8.3 INITIALIZATION ERROR INDICATIONS
Initialization errors are indicated by:
•

OCP fault code displays

•

Module LEDs

•

Boot diagnostic messages

8.3.1 ·OCp Fault Code Displays
OCP fault codes are divided into two categories, hard fault codes and soft fault codes. Soft fault codes
are also called nonfatal fault codes. Soft faults impede HSC operation, but the fault does not hinder
the boot process. Hard fault codes are fatal to the HSC and prevent further operation of the HSC
subsystem until the condition is remedied.
Figure 8--1 shows the possible displays available on the OCP in the event of errors during initialization
or operation.

8-3
TROUBLESHOOTING TECHNIQUES

OCP IND ICATORS
DESCRIPTION

HEX

OCT B I N A R y B IFAULTIIONLINEI

PORT PROCESSOR
MODULE FAILUREt

00001

DISK DATA CHANNEL
MODULE FAI LUREt

00010

TAPE DATA CHANNEL
MODULE FAILUREt

00011

INSTRUCTION CACHE PROBLEM
IN I/O CONTROL PROCESSOR*

01000

HOSTINTERFACEERROR*

01001

c=J D
III
it
I;:;:;:;:;:;:;:;:;:;:;:;:;:;:;:;:;

::::

JTINJE
~f:

::::::

DATA CHANNEL ERROR"

01010

I/O CONTROL PROCESSOR
MODULE FAI LUR E

10001

MEMORY MODULE FAI LURE

10010

:;:;

::::::::::::::::::::::::::::r~

:::::::::::::::::::::::::::;:::::

:m~jrrtrtrm

l~l~ ~ljl
::::

BOOT DEVICE FAI LURE .....

PORT LINK MODULE FAILURE

10011

{

:::

1 0101

10110

NO WORKING K.SDI, K.STI,
OR K.CI

11000

REBOOT DURING BOOT

11001

:::::::

::;:

::::

f:::;

o:'!

::::

:~rr??~~)}r

••••

MISSING FI LES REQUIRED

:::::::::::::

;:::
;:;:

:;:;

••••

•

~t~ ; ;: j~ ~ ~t i~~f~~I~~~I~r~~I~~
::::::

SOFTWARE DETECTED
INCONSISTENCY

11010

:::::::::

tItttjIII
l!ljl

!{;~;~:r;;;;;;;;~;?~:;:;

tIit~;)r:::;:;:

t INCORRECT VERSION OF MICROCODE .
.. THESE ARE THE SO-CALLED SOFT OR NON-FATAL ERRORS.
*"'POSSIBLE MEMORY MODULE/CONTROLLER ON HSC70

Figure 8-1

CX-9058

Operator Control Panel Fault Codes

8.3.1.1 OCP Fault Code Interpretation
All failures occurring during the Init P.io test are reported on the OCP LEDs. When the Fault lamp
is lit, pressing the Fault switch results in the display of a failure code in the OCP LEDs. This code
indicates which HSC module is the most probable cause of the detected failure. The failure code blinks
on and off at one-second intervals until the HSC is rebooted if the fault code represents a fatal fault. A

8-4

TROUBLESHOOTING TECHNIQUES

soft fauh code is cleared in the OCP by depressing the Fault switch a second time. To restart the boot
procedure, press the lnit switch. To identify the probable failing module, see Figure 8-1.
The following paragraphs describe specific fault codes displayed in the OCP lamps. All fault codes are
indicated with octal values.
Fault Code 1, K.pli error-Indicates the CIMGR initialization routine discovered bad requestor
status from a previously-tested good requestor module in requestor slot 1. The expected requestor
status should be 001. The FRU is the LOI07.
During CIMGR initialization, the K.el is directed to set the HSC node address into its own control
structure. If the K.ci failed to modify this node address field after one-half second from K.ci
requestor initialization, this fault code is displayed. In addition, the K.pli microcode version is
checked to ensure it is compatible with this functional version. If compatibility checks fail, this is
the fault code displayed.
Run offline diagnostics to test the K.ci requestor. Replace the K.pli module on failure. If the fault
code persists, refer to the HSC revision control document to verify all HSC components are at the
current revision.
•

Fault Code 2, K.sdi/K.si incorrect version of microcode-All K.sdi/K.si modules are initialized
during the Disk Server functional code initialization. If a K.sdi/K.si passes initialization, the
Disk Server initialization code checks the K.sdi/K.si microcode version number to ensure it is
compatible with this version of functional code. If code versions are not compatible, this fault code
is displayed. The FRU is the LOI08-YA.
Fault Code 3, K.sti/K.si incorrect version of microcode-Indicates tape data channel microcode
is incompatible.

•

Fault Codes 10, 11, and 12, Soft errors--These are the so-called soft or nonfatal errors related
to the data channels, the K.ci host interface, and the P.ioj cache. None of these errors causes the
HSC70 functional operation to suspend when the fault is reported. Once displayed, soft error
indicators cannot be recalled. The HSC may buffer up to eight soft fault codes. Subsequent
toggling of the Fault switch displays all remaining soft fault codes until the buffer is empty.
Fault Code 10, P.ioj cache failure-Results in disabling the cache and displaying this soft
fault code for any failure detected in the J-ll instruction cache during HSC70 subsystem
initialization while the HSC70 continues operation. Replace the P.ioj module (LO 111) and
reboot.
Fault Code 11, K.ci failure-Is not present or has failed its initialization tests. This soft fault
is displayed while the HSC continues to operate. The most probable FRU is the port link
module (LOIOO\L0118).
Fault Code 12, Data channel module failure-Reports an unknown requestor type was found
in a requestor slot other than 0 or 1. Expected valid requestor types for requestor slots 2
through 8 are either 002 (LOI08-YA) or 203 (L0108-YB). The data channel with the red LED
on is the failing module.

•

Fault Code 21, P.ioj/c module failure-Indicates the P.ioj/c module is the most probable cause of
the failure detected by the Init P.io test. If possible, run the offline pjo test for a more definitive
report on the error. Otherwise, replace the P.ioj/c module and run the Init P.io test again. If the test
still fails, run the offline P.io test to help further isolate the failure.

•

Fault Code 22, M.std2 module failure-Indicates the M.std2 module (HSC70) is the most
probable cause of this bootstrap failure. Possible causes include:
The failure of the memory test of the first 1 Kword (vector area) of Program memory as well
as the use of the Swap Banks bit in the P.ioj/c in trying to correct the problem (test 2).

8-5
TROUBLESHOOTING TECHNIQUES

A contiguous 8 Kword partition not found in Program memory below address 00160000 (test
3).

A hard fault detected in the RX33 controller logic (test 4).
Determine the error that occurred by examirling physical location 17772340, which contains the
number of the failing boot ROM test. In each of these cases, replace the M.std2 module, and run
the initialization tests again. H the module still fails, run the offline P.io test.
Enter the SETSHO utility and execute the SHO MEM command. If any memory locations appear
in the suspect or disabled memory locations list, set the Secure/Enable switch to ENABLE and
execute the SET:MEM ENABLE/ALL command.
Fault Code 23, Boot device failure-Indicates a problem with an HSC boot device, the system
media, the boot device controller, or the read/write logic on the memory module. This fault can be
any of the following, in order of probability:
A failure in the P.ioc (HSC50).
A failure in the read/write logic of the M.std2 module. Replace M.std2 (HSC70).
A faulty boot device controller/drive interface cable. Replace the cable.
No diskettes or tapes are installed in the drives.
Doors were left open on the RX33 drives or the tape was improperly inserted in the TU58
drive.
The system device media does not contain a bootable image.
Ensure a known good HSC bootable media is properly loaded in the system boot device. H
checking the obvious (doors, diskettes, or tapes) does not remedy the situation, refer (0 Chapter 6
for more information before beginning repair. Running the offline P.io and offline RX33 or TU58
tests (if possible) is strongly recommended before modules are replaced. These tests may help
further isolate or define the problem.
•

Fault Code 25, port link node address switches out of range-Indicates the L0100/L0118
module node address switches are set to a value outside the currently-suggested range of 32
decimal (Version 3.70).

•

Fault Code 26, missing files required-Indicates the system diskette does not contain one of the
files necessary for operation of the HSC control program. This failure should occur only if one of
the required files is inadvertently deleted from the HSC system media.
Note that the condition of the State light must be observed prior to the fault occurrence. The State
light is always steady (either ON or OFF) when the fault light is lit during boot faults.
If the Stale light is steady (ON), it can mean:

SYSCOM.INI is not present on the load device.
EXEC.INI is not present on the load device.
A version mismatch was found between either EXEC, SUBLIB, or SYSCOM and OLBVSN
(Object Library Version Number).
If the State light was blinking before the fault, it can mean:

Any of the the normally-loaded programs (SINI, CERF, DEMON, etc.) is not present on the
load device.
A version mismatch was found on anyone of the normally-loaded programs.
Replace the system media with a backup copy.

8-6
TROUBLESHOOTING TECHNIQUES

•

Fault Code 30, No working K.ci, K.sdi, K.sti, or K.si in subsystem-Indicates the HSC does not
contain any working K.ci, K.sti, K.sdi, or K.si modules. Either none are installed in the HSC, or
all of those installed failed their initia1ization diagnostics. Also, if the ~isk Server code is loaded
and no working K.sdi is found, this fault code is displayed.
Insert the HSC Offline Diagnostic media into the appropriate system drive and reboot the HSC.
When the offline loader prompts with OOL>, type SIZE IRETURN!. The SIZE command displays
the status of all the Ks. This status indicates whether the modules are missing or are failing
initialization diagnostics.
If all else fails, replace the P.ioj (LOttt) or P.ioc (LOt05) and check subsystem power for proper
operation.

•

OCP error code of 31, Initialization failure-Indicates a crash occurred while the HSC was
attempting to load and initialize its control program.
Use Micro-OOT to diagnose these initialization crashes, as follows:

t. Press the break key on the local console terminal.
2. Type 17 777 656/.
This is the address of the UPAR7 register. The reasons for reboot codes are stored in UPAR7
bits 8 to It when an OCP code of 31 has been detected. The other UPAR registers store
useful information for some of the errors related to an OCP fault code of 31. Refer to the fault
code 3t reasons in the following paragraphs for UPAR content usage. Table 8-t shows the
addresses of the UPAR registers.
Table 8-1

UPAR Register Addresses

Address

UPARO

17 777 640

UPARI

17777 642

UPAR2

17 777 644

UPAR3

17 777 646

UPAR4

17 777 650

UPAR5

17 777 652

UPAR6

17 777 654

UPAR7

17 777 656

3. Analyze bits 8 to 11 of the 16-bit message displayed by examining UPAR7. Table 8-2 shows
the bit/error relationship.

8-7
TROUBLESHOOTING TECHNIQUES

Table 8-2

Control Program Bits

i6 Bit Message

Meaning

FRUs

x XXX XXX lXX XXX XXX

NXM

LOlli
L01l7
Software

x XXX XXI OXX XXX XXX

Ule gal inst.

LOlli
LOll7
Software

x XXX XXI lXX XXX XXX

Parity trap

LOtt7
LOllI

x XXX XIO OXX XXX XXX

Level 7 interrupt

LOt08
LOl07

x XXX XIO IXX XXX XXX

MMU trap

LOltl
Software

x XXX XII OXX XXX XXX

Software crash

Software

X XXX XlllXX XXX XXX

K.ci host reset

LOll 7

X XXX 100 OXX XXX XXX

User requested reboot

N/A

4. If this error occurs repeatedly, it indicates tUl intermittent hardware error or degiaded diskette
media. The boot-in-progress flag is indicated by KPDR7 bit 3 set. The KPDR7 register address
is 17 772 316. Use micro-ODT to examine bit 3 (it can be reset).
The following Jist describes actions to be taken for each type of error related to an OCP fault code
of 31 as pointed out by examining UPAR7.
NXM trap: Examine UPAR 1 to find the lower 16 bits of the failing memory address by typing
17 777 642/. Examine UPAR2's lower byte for the high 6 bits of the failing memory address
by typing 17 777 644/.

Illegal inst: Replace the P.ioj/P.ioc module.
Parity trap: Use the same method for parity traps as for NXM traps to determine the failing
address.
Level 7 interrupt: Determine which K UPAR4. Refer to Table 8-1 for the address of each
UPAR register. Each byte of each register contains module status for each requester (K) in
the HSC. Refer to Appendix C to determine a failing status code. Refer to Table 8-3 for the
designation of requestors to UPAR registers for a level 7 interrupt.

TROUBLESHOOTING TECHNIQUES

Table 8-3

Status of Rp,q(Jp.~tor~ for Lp.vel 7 Inferrupt

High Byte

Low Byte

UPARO

REQ2

REQ 1

UPARI

REQ4

REQ3

UPAR2

REQ6

REQ5

UPAR3

REQ8

REQ7

UPAR4

N/A

REQ9

Memory Management Un.t (MMU) trap: Examine UPAR t, UPAR.2, and UPAR3 to
determ~ne the status of the MMU at the time of the OCP fault code of 31. When an MMU trap
occurs, sta.tns of the J\.1.MU is f01md in these registers.
Softw~re cr3sh: Try using ~nother copy of the boot media. If the problem is not corrected,
replace the P.ioj/P.ioc mochIle. If Lhe problem still persists, replace the memory m.odule.

K.d host reset: Hit the break key again and at the @ symbol type 17 770 000/ when a host
reset is known as the r~.ason for an OCP fault code of 3t. This is the address of Control
memory winelow O. When the I is hit, the contents of control w;ndow 0 are displayed. Enter a
o into this location followed by a carriage return. Then type 17 760 002/. This is the second
location in Control memory. The number displayed as the contents of 17 600 002 is the
nwnber of the host that issu~.d the HOST RESET command.
•

OCP error code 32, Software inconsistency-Indicates an inconsistency in the software. Reboot
the HSC. IT this failure persists, use a backup copy of the system media. IT the failure still persists,
use the Offline diagnostics to help isolate any hardware failures in the subsystem. Also, try using
an earlier version of the HSC operating software.

8.3.2 HSC Module LE.Os
HSC modlJles contain LEOs used as State indicators for each module. Descriptions of these LEOs
follow in the next sections. Also, refer to Chapter 2 for the locations of the module LEOs.
8.3.2.1 P.ioj/c LEOs

Table 8-4 shows the LOtl1 or LOtOS (I/O Control Processor module) LEOs and their functions.

8-9
TROUBLESHOOTING TECHNIQUES

Table 8-4

L0111-0 (P.ioj/c) LEOs

LED

Color

Meaning

Yellow

Micro-ODT-Used during J-11 power-up mkrodiagnostics. ON when J-11 is
executing micro-ODT.

Yellow

TenninaJ Port OK-Used during J-11 power-up microdiagnostics. Serial Line
Unit (SLU) output of UART.

Yellow

Memory OK-Used during J-ll power-up microdiagnostics. Turned OFF as
J-11 successfully accesses Program memory.

Yellow

Sequencing indicator-Used during J-11 power-up microdiagnostics. Turned
OFF a"> J-11 verifies proper functioning of its sequencers for control store.

Yellow

State indicator-Mirrors the OCP State indicator (under software control).

Yellow

Run indicator-Pulses at the on-board microprocessor run rate. Blinks once
for every PDP-11 instruction fetched (1-11 run LED).

Red

Board status-Indicates an inoperable module except during initialization
when it comes on during module testing.

Green

Board status-Indicates the module has passed all applicable diagnostics.

8.3.2.2 Power-up Sequence of 1/0 Control Processor LEOs

This section defines the power-up sequence of the LEDs shown in Table 8-4. First, LED numbers
D8 and D7 are used to indicate whether the P.ioj/c module has successfully completed all of its
initialization diagnostics. The module powers up with the red (D7) LED ON and the green (D8) LED
OFF. Dl through D4 (yellow) are initially ON. As soon as the J-11 starts operating, Dl (micro-ODT
LED) turns OFF.
Several microcode steps later, D4 (sequence LED) is turned OFF, indicating the j- i i is sequencing
and succeeded in reaching this point in its microcode. The J-11 performs several Program memory
operations and, if successful, turns OFF D3 (memory OK LED). Finally, the J-ll accesses the console
terminal port of the UART (universal asynchronous receiver/transmitter) and turns OFF D2 (SLU or
Serial Line Unit LED).
lJpon successful completion of the boot time initialization diagnostics, D8 (module OK LED) turns
ON, and D7 (module failure LED) turns OFF. The J-11 then proceeds to the software initialization
programs.
In addition to being initially ON, the 01 (micro-ODT run LED) is ON any time the J-11 is executing

micro-ODT. D6 (the fetch LED, sometimes referred to as the run LED) blinks once for every PDP-II
instruction fetch cycle. When the J-ll is running, D6 is illuminated at half-brilliance compared to the
other yellow LEOs.

8-10
TROUBLESHOOTING TECHNIQUES

8.3.2.3 Memory Module LEOs

Table 8-5 shows the LO 117 (M.std2) and LOt 06 (M.std) module LEOs and their functions. These
LEOs are controlled by a bit in the system boot device FDC MAR02 register. The green LED is set to
ON by the PJoj/c boot/ROM self-test diagnostics after the system boot device has passed its self-tests,
and Program memory has found 8 Kwords to load INIPIO/OFLPIO.
Table 8-5

L0117 (M.std2) and L0106 (M.std) LEOs

LED

Color

Meaning

Red

Module not OK

Green

Module OK

Yellow

Memory active

NOTE

The entire LED package on the M.std2 or M.std is called D2. AU three LEDs are contained in
the D2 package.
8.3.2.4 Data Channel LEOs

Table 8-6 shows the LOt 08-YA/YB (K.sdi/K.sti) and L0119 (K.si) data channel module LEOs and their
functions with the system software.
Table 8-6

L0108-YA/YB (K.sdi/K.sti) L0119 (K.si) LEOs

LED

Color

Meaning

Red

Module failure-Indicates a module microdiagnostic faiJed to successfully
complete, or this module is still under initialization by the subsystem.

Green

Module OK-Turned on by the Init/Func FJag signal in the K functional
microcode. The green LEO comes ON after successful initialization or
while the data channel is running functional microcode.

Amber

Dt-OFF for PROM load, ON for RAM load.
02 through OS-Upper register #2 contents.

LED
pack
(8 LEOs)
(K.si
only)

The LEOs reflect the implemented bits of the upper error register #2.
When a microinstruction parity error is detected, the module clocks are
inhibited, stopping the module. The bit content of the upper error register
#2 is displayed on the LEOs.

8.3.2.5 Host Interface LED

Table 8-7 shows the three modules in the K.ci set, their LEOs, and the functions of the LEOs with the
system software.

8-11
TROUBLESHOOTING TECHNIQUES

Table 8-7

K.ci (LINK, PILA, K.pli) LEOs

Module

LED

Color

Meaning

K.pli

Red

ON when P.io has booted or rebooted, but K.pli module has not yet passed
its self-test.

K.pli

Green

ON when K.pli has passed its self-test.

PILA

Red

ON when Pll..A module has not yet passed the test performed by the
K.pli.

PILA

Green

ON when the PILA module has passed the test performed by the K.pli.
LED is controlled by the port processor.

PILA

Yellow

(Not found on all etch rev modules.) ON when K.pli is a~serting Init.
When Init is true, both the red and the green PILA LEOs are forced OFF.

LINK

D998

Green

ON when local activity is present on the LINK module (whenever the
LINK module detects a message directed to its node or when it detects an
outgoing message).

LINK

D999

Red

ON during the CI maintenance loop test.

8.3.3 Communication Errors
It is possible for the HSC to complete its initialization and not report the fact on the local console

teonina!. This is an indication of a failure in the seriai communication path oeiween the UART chip
on the P. ioc/j (LO 105/LO 111) and the local console terminal.
As a method of testing this serial path, the HSC echoes the characters typed on the local console
temlinal as if the terminal were in local mode. Use the following procedure to test the serial path.

1. Piace the Secure/Enable switch in the ENABLE position.
2. With power on, push in and hold the OCP Init switch.
3. Type a series of characters on the terminal keyboard.
4. Check to see if the series of characters echoed correctly on the terminal.
NOTE

When the Init switch is released, the HSC reboots.
If this procedure fails to echo characters typed at the keyboard, the failure is either a terminal to P.ioc/j
baud-rate mismatch (default is 96(0), a P.ioj/c module failure, or a problem within the terminal-cabling
subsystem. Ensure the terminal set-up parameters are correct. Refer to the HSC Installation Manual
(EK-HSCMN-IN) for the proper terminal configuration, the VTxxx Owner's Manual (EK-VTxxx-UG)
for problem-solving techniques related to the VTxxx, and the DECwriter Con'espondent Technical
Manual (EK-CPL12-TM) for problem-solving techniques related to the LA12.

8-12
TROUBLESHOOTING TECHNIQUES

8.3.4 Requestor Status for Nonfailing Requestors
When a requestor successful1y comp1etes all internal microdiagnostics, bits 0 through 5 contain the
following codes defining module types.
•

Code 001 represents a properly-functioning host interface module set (K.ci).

•

Code 002 represents a properly-functioning disk data channel module (K.sdi/K..si with the disk
channel microcode loaded).

•

Code 004 represents a K.si with no microcode loaded.

•

Code 203 represents a properly-functioning tape data channel module (K.sti/K.si with the tape
channel microcode loaded).
Code 377 indicates the requestor slot does not contain a module.

NOTE

When a module fails internal micrQdiagnostics or its functional code, the status byte reflect~ the
failure. See Appendix D for a complete list of K.ci-, K.sdi-, K.sti-, and K.si-detected failures.

8.3.5 HSC70 Boot Flow and Troubleshooting Chart
The HSC70 boot flow and troubleshooting chart cans out useful visual milestones that aid in
troubleshooting problems which can occur during initialization.
The flowchart has three main divisions:
1. Infonnation on activity common to both the system and offline diskettes is contained in boxes A
through O.

2. Information on activity specific to the system diskette is contained in boxes SA through SJ.
3. Information on activity specific to the offline diskette is contained in boxes OA through 00.
The flowchart begins when one of the following occurs:
•

Init button is pushed.

•

Powerup has started.

•

Other software caused reboot.

Figure 8-2 maps the entire HSC70 boot sequence.

8-13
TROUBLESHOOTING TECHNIQUES

INTERNAL/EXTERNAL
INITIALIZATION
ENTRY POINT
TIME = 0

J-ll PERFORMS INTERNAL
MICRO TEST ... A THRU C

TEST INTERNALJ-11
SEQUENCER; TURN OFF
D1 (MICRO-ODT) IF NOT
IN ODT; TURN OFF D4

B TEST MEMORY: . LOC 0
RESPOND (NO NXM?);
LOC 1777700 SHOU LD
NXM; TURN OFF D3

NOTE: LEDs D1-D4 AND D7 ARE ON THE P.ioj MODULE.

NO FAULT CODE
FAIL

STATE INIT FAULT

D7 (RED LED) ON
NOTE: ? MEANS OCP LEDs ARE
INDETERMINATE AND
HAVE NO MEAi\lING AT
THIS TIME.

NO FAULT CODE
FAIL

STATE INIT FAULT

NO·FAULT CODE
TEST FOR SLU, CHECK
177560 FOR RESPONSE;
TURN OFF D2

FAIL

BEGIN EXECUTION OF
BOOT ROM, TURN OFF
ALL OCP INDICATORS

FAIL

STATE

lli!.J FAU LT

)

NO FAULT CODE
STATE INIT FAULT
OFF
OFF
OFF

NO FAULT CODE
FAIL

STATE INIT FAULT
OFF OFF ~

FAULT = 21 OCTAL
FAIL

STATE INIT FAULT
OFF
OFF
ON

D7 STILL ON;
OCP INDICATORS
NOT RELIABLE

~
TIME
<1/2
SECOND

TURN ON INIT INDICATOR

CX-945C
Sheet 1 of 5

Figure 8-2 (Cont.)

HSC70 Boot Flow and Troubleshooting Chart

8-14
TROUBLESHOOTING TECHNIQUES

FAULT = 21 OCTAL
H TEST 1
TEST BANK SWAP
BITS IN P.ioj CSR

FAIL

TEST 2
TEST 1ST 1 KW OF GOOD
PROGRAM MEMORY

TEST 3
FIND 8 KW OF GOOD
PROGRAM MEMORY

FAIL

TEST 4
TEST RX33 CONTROLLER
HARDWARE

FAIL

STAT~

tmI FAULT

OFF

STATE
OFF

lli.!I FAULT
ON

IF MEMORY FAI LS
WITH NXM OR PARITY
ERROR, FAULT WILL
NOT BE SET

X
IF MEMORY
DATA ERROR IS
DETECTED, FAULT
IS 22 AND FAULT
LED WI LL BE ON

STATE INIT FAULT
OFF
ON
ON

FAUL T = 22 OCTAL
STATE INIT FAULT
OFF
ON
ON

FAULT = 23 OCTAL
FAIL

N READ FIRST 8 BLOCKS
FROM R X33 (BOOT
BLOCKS)

STATE INIT FAULT
OFF
ON
ON

FAULT = 23; OCCURS ONLY IF
BOTH DRIVES FAI L

FAULT = 23 OCTAL
FA!L

STATE INIT FAULT
OFF
ON
ON

FAULT = 23; OCCURS ON L Y IF
BOTH DRIVES FAI L

TRANSFER CONTROL
TO IMAGE JUST
LOADED

CX-945C

Sheet 2 of 5

Figure 8-2 (Cont.)

HSC70 Boot Flow and Troubleshooting Chart

8-15
TROUBLESHOOTING TECHNIQUES

SYSTEM
DISKETTE

INIT LED TURNED OFF,
STATE LED TURNED ON
SOLID, HSC CONSOLE O/P
INIPIO-I-BOOTING;
LOAD REMAINDER OF
INIPIO.INI
FAULT = 21 OCTAL
INIPIO PERFORMS
INSTRUCTION TESTS AND
MMU TESTS

FAIL

STATE INIT FAULT
ON
OFF
ON

INIPIO LOADS
INICAC AND
TRANSFERS CONTROL

INICAC TESTS CACHE;
I F CACHE FAI LS,
FLAGS FAI LURE TO INIPIO

INIPIO INITS ALL
REQUESTORS AND GETS
THEIR STATUS

INIPIO TESTS PROG MEM;
HIGHEST REQUESTOR
NUMBER TESTS CONTROL
AND DATA MEMORY

INIPIO LOADS EXEC;
INIPIO TURNS ON
GREEN LED ON THE
P.ioj MODULE

FAULT = 22 OCTAL
FAIL

STATE INIT FAULT
ON
OFF
ON

TOTAL MEMORY FAILURE
IN CONTROL OR DATA

FAULT = 23 OCTAL
FAIL

STATE INIT FAULT
ON
OFF
ON

FAULT OCCURS IF BOOT
DEVICE HAS ERROR WHEN
LOADING EXEC

CX-945C
Sheet 3 of 5

Figure 8-2 (Cont.)

HSC70 Boot Flow and Troubleshooting Chart

8-16
TROUBLESHOOTING TECHNIQUES

INIPIO TRANSFERS TO
EXEC, STARTS STATE
LIGHT BLINKING AT 1'2
SECOND INTERVALS

FAIL

STATE IliLI FAULT
SOLID OFF
ON
ON OR
OFF

MOST REMAINING FAULTS
INDICATE SOFT FAULTS

FAULT CODE DEPENDENT ON FAI LURE
EXEC RUNS SINI;
SINI LOADS AND
INITIALIZES REMAINING
S/W MODULES

SINI TRANSFERS
COMPLETELY TO EXEC,
STATE LIGHT BLINKS
AT 1 SECOND INTERVALS;
OUTPUT OPERATING
SOFTWARE HERALD

FAIL

STATE INIT FAULT
SOLID OFF
ON
ON OR
OFF

FAIL
SAME AS ABOVE

NOTE: AFTER THE OPERATING
SOFTWARE HERALD, OTHER
INITIALIZATION MESSAGES
MAY BE REPORTED.

CX-945C
Sheet 4 of 5

Figure 8-2 (Cont.)

HSC70 Boot Flow and Troubleshooting Chart

8-17
TROUBLESHOOTING TECHNIQUES

OFFLINE
DISKETTE

~ TURNS INIT INDICATOR
OFF; TURNS STATE
INDICATOR ON SOLID

~ LOADS REST OF OFFLINE
P.ioj TEST (OF LPIO)

STATE INIT FAULT
ON
ON
OFF

2..9 RUNS OFFLINE P.ioj
TEST (OF LPIO)

ERROR TYPEOUT OR
HALT AT 400

•

~ LOADS OFFLINE
DIAGNOSTIC LOADER
(ODL)

•

~ TURNS ON P.IO]
. .
GREEN LED

~ STARTS ODL. BLINKS
STATE INDICATOR; ODL
HERALD TO TERMINAL

j
~ ODL PROMPT WAITS FOR
OPERATOR COMMAND,
ROT A TES OCP LAMPS
FOR TEST

ODL FEATURES
8 TESTS
BUS
MEM
MEM BY K
K TEST SEL
OCP
REFRESH
CACHE
RX33

•

11 CONVENIENCES
SIZE
HELP

•

LOAD
START
SET DEFAULT
SHOW DEFAULT
SET RELOCATION
EXAMINE
DEPOSIT
REPEAT

I
NOTE: FIRST PORTION OF THE OFLPIO TESTS WAS LOADED WITH THE
PREVIOUS LOAD OF EIGHT BOOT BLOCKS.

CX-945C
Sheet 5 of 5

Figure 8-2

HSC70 Boot Flow and Troubleshooting Chart

8-18
TROUBLESHOOTING TECHNIQUES

8.3.6 HSC50 (Modified) or HSC50 Boot Flow and Troubleshooting Chart
The HSC50 (modified) or HSC50 boot flow and troubleshooting chart caBs out useful visual milestones
that aid in troubleshooting the problems which can occur during initialization.
The flowchart has three main divisions:
1. Information on activity common to both the system and offline media.
2. Information on activity specific to the system media.
3. Information on activity specific to the offline media.
The flowchart begins when one of the following occurs:
•

Init button is pushed

•

Powerup has started.

•

Other software caused reboot.

Figure 8-3 maps the entire HSC50 (modified) or HSC50 boot sequence.

8-19
TROUBLESHOOTING TECHNIQUES

FAULT CODE CHART (1)
OCTAL
CODE
01
02
03
21
22
23
25

EXTERNAL EVENTS
- POWER UP
- INIT SWITCH
- HOST RESET REQUEST

INTERNAL EVENTS
- HSC S/W CRASH
- MODULE FAI LURE

TIME

TO -

TURN ON P.ioc
RED LED (3)

26
30
31
32

FAIL?

FAI LURE

K.pli UCODE WRONG REV
K.sdi UCODE WRONG REV
K.sti UCODE WRONG REV
P.ioc OR POWER
M.std, P.ioc, OR POWER
BOOT DEVICE. P.ioc OR POWER
LINK NODE ADDRESS SWITCHES
SET HIGHER THAN A VALUE OF
HEX OF
= MISSING REQ UIRED FILE ON
BOOT MEDIA
= NO Ks FOUND IN SYSTEM (2)
= REBOOT BEFO RE PREVIOUS
BOOT COMPLE TED
= SIW DETECTE INCONSISTENCY

CHECK POWER (4)

1
TURN OFF ALL
OCP INDICATORS

FAIL?

I
TEST 0 - TEST F11
BASIC INSTRUCTION SET

FAULT CODE = NONE
FAIL?

I
TEST 0 - TEST MOR E
F11 INSTRUCTION SET

T< 1/2 SECONDT> 1/2 SECOND-

TEST 1 - TEST BOARD
AND BANK SWAP BITS
IN P.ioc CSR

INIT
FAULT
--- OFF

OFF

POSSIBLE FRUs
P.ioc OR POWER

STATE
-

INIT
-

FAULT
-

OFF

FAULT CODE = 21 OCTAL
FAIL?

I
TEST 2 - TEST FIRST
1 KW OF PROG RAM
MEMORY

STATE
OFF

FAULT CODE = 21 OCTAL
FAIL?

I
P.ioc TURNS ON
INIT INDICATOR

FAULTY P.ioc OR
POWER SUBSYSTEM

FAIL?

STATE

INIT
-

OFF

FAULT

FAULT CODE = 22 OCTAL
I STATE

-INIT

FAULT

OFF

NOTE 1: Ks (REQUESTORS) = K.sdi, K.sti, K.pli.
NOTE 2: ALL MODULE RED INDICATORS ON EXCEPT MEMORY (NO RED LED ON IT).
NOTE 3: REFER TO POWER SUPPLY TROUBLESHOOTING FLOWCHART.
CX-052B

Sheet 1 of 4

Figure 8-3 (Cont.)

HSC50 (Modified) or HSC50 Boot Flow and Troubleshooting Chart

8-20
TROUBLESHOOTING TECHNIQUES

TEST 3 - FIND GOOD 8 KW
CHUNK OF PROGRAM
MEMORY

TEST 4 - LOOK FOR LOAD
DEVICE; LOAD 8 BOOT
BLOCKS

OFFLINE
TAPE

SYSTEM
TAPE

FAIL?

FAULT CODE = 22 OCTAL
STATE
OFF

-INIT

FAULT
ON

FAULT CODE = 23 OCTAL
FAIL?

STATE

INIT

FAULT

OFF

~ SYSTEM
TAPE
TURNS INIT INDICATOR OFF,
TURNS STATE INDICATOR
ON SOLID

I
OUTPUTS TO TERMINAL,
INIPIO-I-BOOTING,
LOADS REST OF INIPIO (1;

I
RUNS INITPIO (INITS
REQUESTORS AND GETS
THEIR STATUS)

FAULT CODE DEPENDENT ON FAILURE (2)
FAIL?

I STATE

Izm-

-!NIT

OFF

FAULT
ON

LOADS OPERATING SOFTWARE
WHI LE CONTROL AND DATA
MEMORY ARE TESTED BY
HIGHEST NO. REQUESTOR;
STATE INDICATOR BLINKS AT
1/2 SECOND INTERVALS

I
P.ioc TESTS REMAINDER OF
PROGRAM MEMORY AND
CREATES BAD MEMORY
LINKED LIST

NOTE 1: FIRST PORTION OF THE INIT P.ioc TESTS (lNIPIO) WAS LOADED WITH THE PREVIOUS
LOAD OF EIGHT BOOT BLOCKS.
NOTE 2: FOR DETAI LED INFORMATION ON THE INIPIO TESTS AND ERROR REPORTS, REFER
TO THE HSC50 INLINE DIAGNOSTICS USER DOCUMENTATION.
CX-OS2B

Sheet 2 of 4

Figure 8-3 (Cont.)

HSC50 (Modified) or HSC50 Boot Flow and Troubleshooting Chart

8-21
TROUBLESHOOTING TECHNIQUES

TURNS ON P.ioc
GREEN LED

STARTS OPERATING SOFTWARE;
BLINKS STATE INDICATOR AT
ONE SECOND INTERVALS;
OPERATING SOFTWARE HERALD (1)

FAULT CODE DEPENDENT ON FAILURE
FAIL?

STATE

INIT

FAULT

ON OR OFF

OFF

OPERATING SOFTWARE WI LL NOT
PROMPT UNTI L REQUESTED BY
CTRL/Y; THE PROMPT IS:
HSC50>

NOTE 1: AFTER THE OPERATING SOFTWARE HERALD, ONE OF SEVERAL NONFATAL INITIALIZATION
FAI LURE MESSAGES MAY BE PRINTED:
-

REQUESTOR n FAI LED TO INIT STATUS = XXX

THIS MESSAGE INDICATES THE SPECIFIED REQUESTOR FAILED ITS INTERNAL INITIALIZATION
SELF·TEST OR COULD NOT BE LOADED WITH MICROCODE (K.si).
-

SWAP BANK BIT SET
THIS MESSAGE INDICATES THAT A GOOD CONTIGUOUS SECTION OF 8 KW PROGRAM MEMORY COULD
NOT BE FOUND WITHOUT USING THE SWAP BANK BIT IN THE P.ioc CSR. THE MEMORY MODULE IS
SUSPECT.

CX-052B
Sheet 3 of 4

Figure 8-3 (Cont.)

HSC50 (Modified) or HSC50 Boot Flow and Troubleshooting Chart

8-22

TROUBLESHOOTING TECHNIQUES

Y
3

OFFLINE

TAPE

TURNS INIT INDICATOR OFF,
TURNS STATE INDICATOR
ON SOLID

I
LOADS REST OF OFFLINE
P.ioc TESTS (OFLPIO)(1)

NO FAULT CODE (2)
FAIL?

RUNS OFF LINE P.ioc TESTS
(OFLPIO)

STATE
INIT
FAULT
- -ON

OFF

ERROR TYPEOUT OR
HALT AT 400

LOADS OFFLINE DIAGNOSTIC
LOADER (ODL)

I
TURNS ON P.ioc
GREEN LED

I
STARTS ODL,
BLINKS STATE INDICATOR,
ODL HERALD TO TERMINAL

.-----

ODL PROMPT WAITS FOR
OPERATOR COMMAND,
ROTATES OCP LAMPS FOR TEST

I
ODL FEATURES
6 TESTS

11 CONVENIENCES

BUS
MEM
MEM BY K
K TEST SEL
OCP
REFRESH

SIZE
HELP
@

LOAD
START
SET DEFAULT
SHOW DEFAULT
SET RELOCATION
EXAMINE
DEPOSIT
REPEAT

I
NOTE 1: FI RST PORTION OF THE OFLPIO TESTS WAS LOADED WITH THE PREVIOUS LOAD
OF EIGHT BOOT BLOCKS.
NOTE 2: REFER TO FAULT CODE CHART. FOR DETAI LED INFORMATION ON INITPIO TESTS, REFER
TO THE HSC50 IN LINE DIAGNOSTICS USER DOCUMENTATION.

CX-052B
Sheet 4 of 4

Figure 8-3

HSC50 (Modified) or HSC50 Boot Flow and Troubleshooting Chart

8-23
TROUBLESHOOTING TECHNIQUES

8.3.7 Boot Diagnostic Indications
The HSC can pass hoot diagnostics with a failing requestor. Although the HSC passed the boot, the
failure associated with the requestor is considered an initialization error.
Following is an example of an error message displayed when a requestor fails on initialization of the
operating software. The HSC has passed most of the initialization/boot diagnostics, but a requestor has
failed.
SINI-E ERROR SEQUENCE 2. AT 20-SEPT-1985 00:00:02.80
REQUESTOR 2 FAILED INIT DIAGS, STATUS = 107

The requestor with the red LED ON is the failing requestor. In this case, the diagnostic identifies
requestor 2 as failing its internal self-test number 7. Additionally, the fault indicator turns on, and a
soft fault code of octal 12 is displayed on the OCP after the Fault switch is pressed.
See Chapter 4 for more information on errors indicated by the OCP.

8.4 SOFTWARE ERROR MESSAGES
Software error messages are classified into three categories:
1. MSCprrMSCPerrors
}
2. Bad block replacement errors (BBR)
3. Out-of-band errors

fll-VA-76D A'jIf/3

flli'fo fL -r 7 "fC S
D[4 f- jt-Il

This section explains the different error types in each category, and shows examples of console error
printout [onnats for each type in a category.

8.4.1 Mass Storage -ControlPtotocol EtrOrs
The Mass Storage Control Protocol (MSCP) or Tape Mass Storage Control Protocol (TMSCP) errors
printed out at the console terminal and reported to a host can be one of the fonowing types:
1

.I..

Controller errors

2. SOl errors
3. Disk tnmsfer errors
4. STI communication errors

5. STI formatter errors
6. STI drive errors

8.4.2 MSCPITMSCP Error Format, Description, and Flags
Error fonnats, descriptions of the fields within the error format, and error flags are nearly identical for
MSCP and TMSCP errors. Differences are noted where they exist. See Section 8.5 for listings and
explanations of controller errors.

8-24
TROUBLESHOOTING TECHNIQUES

8.4.2.1 Error Format

Example 8-1 shows an error fonnat generic to all MSCprrMSCP errors. Some errors may contain
oplionallines with additional information.
ERROR-X Text of message at (date)
Command Ref i
xxxxxxxx
Err Seq i
x.
Format Type
xx
Error Flags
xx
Event
xxxx
(Optional line)
(Optional line)
(Optional line)
ERROR-I End of error.

Example 8-1

(time)

MSCPITMSCP Error Message Format

8.4.2.2 Error Message Fields

Table 8-8 describes the various fields found in an MScprrMSCP error message. These are common
fields to all error messages of this type.
Table 8-8

MSCPITMSCP Error Message Field Descriptions

Field

Description

ERROR-E

The E is a code indicating the severity level of an error. Other codes are: Q for inquiry,
I for infonllational, F for fatal, W for warning, and S for success.

NOTE

Only severity levels E and Q require user action.
Infonnation following the severity level code is a textual version of the error message
describing the event code, followed by the date and time.
Command Ref #

This number (in hexadecimal) is the MSCP{fMSCP command number which caused
the reported error. It is zero if the error does not correspond to a specific outstanding
command. This nwnber is nonnally assigned by the issuing host CPU.

Err Seq #

This number (in decimal) is a sequential number which count4\) error log messages
since the MSCP(fMSCP server established a connection with the host. It is zero if the
MSCP(Th1SCP Server does not implement error log sequence numbers.

Fonnat Type

This number (in hexadecimal) is the byte that describes the detailed format of the error
log message. Table 8-9 defines the fonnat type codes. Fomlat Type xx basically defines
the type of error packet.

Error Flags

This number (in hexadecimaJ) indicates bit flags, collectively caJled error log message
flags, used to report various attributes of the error. Refer to Table 8-10.

Event

This number (in hexadecimaJ) identifies the specific error or event being reported by this
error log message. This code consists of a 5-bit major event code and an ll-bit subcode.
The event codes and their meanings are listed in Appendix-R C.

Error-I

The I indicates the severity level of the end of error message is infonnational.

8-25
TROUBLESHOOTING TECHNIQUES

8.4.2.3 Format Type Codes
Table 8-9 defines the format type code numbers. The format type code numbers are in hexadecimal.
Table 8-9

Error Message Format Type Code Numbers

Number

Definition

Controller errors

Host memory access errors with memory address

Disk transfer errors

SOl errors

Small disk errors

Tape transfer errors

STI errors

STI drive error log

STI fonnauer error log

Bad block replacement

8.4.2.4 Error Ftags
Table 8-10 defines the MSCP{fMSCP error flags.
Table 8-10

MSCPITMSCP Error Flags

Bit
Number

Bit
Mask
Hex

Format Description

If set, the operation causing this error log message has successfully completed. The

error log message summarizes the retry sequence necessary to successfully complete
the operation.
6

If set, the retry sequence for this operation continues. This error log message reports

the unsuccessful completion of one or more retries.
5

This is MSCP-specific. If set, the identified logical block number (LBN) needs
replacement.

This is MSCP-specific. If set, the reported error occurred during a disk access initiated
by the controller bad block replacement process.

If set, the error log sequence number has been reset by the MSCP Server since the last
error log message was sent to the receiving class driver.

8-26
TROUBLESHOOTING TECHNIQUES

8.4.2.5 Controller Errors

Example 8-2 is a printout of a typical controller error.
ERROR-E Data memory error (NXM or parity) at 5-Mar-1985 12:52:14.43
Command Ref I
1C430008
Err Seq I
1.
Error Flags
41
Format Type
00
Event
012A
Buffer Addr
143611
Source Req.
o.
Detecting Req. 3.
ERROR-I End of error.

Example 8-2

Controller Error Message Example

NOTE

The direction of data transfer may be deduced from the types of requestors identified in the
Source Requestor and Detecting Requestor fields of the error message. In this example, the
source requestor (the P.ioj/c) filled the buffer and requestor 3 is reading it.
This section lists controller and compare errors together because their fonnat and fields are the
same. These errors contain three optional fields in addition to those described in Table 8-8. The
controller/compare specific fields are shown in Table 8-11.
Table 8-11

MSCP/TMSCP Controller Error Message Field Descriptions

Field

Description

Buffer Addr

This number (in octal) is the starting address of the HSC Data Buffer where the
error occurred.

Source Req.

This number (in decimal) is the requestor that originally filled the buffer with
data.

Detecting Req.

This number (in decimal) is the requestor that detected the error.

8.4.2.6 MSCP SOl Errors

The SDI-type errors total 15. Example 8-3 shows a typical SDI error message. Table 8-12 describes
the fields specific to SDI errors. Table 8-13, Table 8-14, Table 8-15, and Table 8-16 further define the
fields in Table 8-12. For the remaining fields, refer to Table 8-8. For listings and explanations of SOl
type errors, see Section 8.5.

8-27
TROUBLESHOOTING TECHNIQUES

ERROR-E Drive Detected Error at 5-Mar-1985 12:52:14.43
Command Ref t
00000000
RA81 unit t
124.
Err Seq t
4.
Error Flags
40
For-mat Type
03
Event
OOEB --Request
1B
Mode
00
Error
80
Controller
00
Retry/fail
00
Extended Status 88
00
03
~

{U'r"7J I ~EY

4B~

1A t!!:--

Requestor t
Drive port t
ERROR-I End of error.

Example 8-3

I< 11 GO $ do t~ 11-£~ L::

6.
2.

SOl Error Printout

Table 8-12 describes the SOl error printout fields.
Table 8-12

SOl Error Printout Field Descriptions

Field

Description

RA81 unit #

This is the number of the unit the error log message relates to, or is 4095 if the unit
number is unknown. In this example, the RA81 indicates the drive is an RA8I and is
unit 124.

Request

This number (in hexadecimal) is a byte describing the various requests from the drive for
controller action. Figure 8-4 shows the bits of this byte field, and Table 8-13 describes
the bits. In this example, the IB indicates:
RUN/STOP switch in
Port switch in
Logable information in extended area
Spindle ready

Mode

This number (in hexadecimal) is a byte describing the mode of the unit. These
modes are alterable by the controller. Figure 8-5 shows the bits of this byte field,
and Table 8-14 describes the bits. In this example, the 00 indicates:
No subunits are write-protected.
The disk is in 5I2-byte sector format.

8-28
TROUBLESHOOTING TECHNIQUES

Table 8-12 (Cont.)

SDI Error Printout Field Descriptions

Field

Description

Error

This number (in hexadecimal) is a byte describing the the current drive error conditions
that prevent normal drive operations. Figure 8-6 shows the bits of this byte field,
and Table 8-15 describes the bits. In this example, the 80 indicates a drive error has
occurred, and the drive Fault lamp may be on.

Controller

This number (in hexadecimal) is a byte describing the subunits with attention available
messages suppressed in the controller and a status code indicating various states of drive
operation. Figure 8-7 shows the bits of this byte field, and Table 8-16 describes the bits.
In this example, the 00 indicates:
No subunits with attention available message suppressed in the controller.
Drive normal operation.

Retry/fail

This number (in hexadecimal) is a byte containing one of two types of information
depending upon the status of the OF bit in the error field. The DF bit describes the drive
initialization process. The DF bit is a zero if the drive initialization was successful.
In this case, the Retry/fail field contains the retry count from the previous operation.
For example, a Seek operation required 14 retries to be successful. If a GET STATUS
command is initiated, the Retry/fail field contains the number 14.
The OF bit set indicates the drive initiali7~tion failed, and therefore, the Retry/fail
contains a specific drive error code. This error code is defined in the appropriate drive
service manual.
In this example, 00 indicates no retry count exists for the previous operation. (The DF
bit is zero in the Error field.)

Extended status

These bytes (in hexadecimal) contain the extended status of the particular drive. (In Ihis
example it is an RA8!.) Refer to the appropriate drive service manual for the meaning
of these bytes.
In this example, the extended status is:
88-Controller command functional code last executed by the drive. (In this case, a
GET SUBUNIT CHARACfERISTICS command.)
OO-Interface error status bits which are all reset.
•

03-Low-order cylinder address bits of the last Seek operation.

•

OO-High-order cylinder address bits of the last Seek operation.

•

07-The present group address.

•

4B-Error code (index pulse error) displayed by the drive LEDs during the
execution of a drive-resident diagnostic.
lA-Error code (servo fine positioning error) displayed on the OCP of the RA81.

Requestor #

This number (in decimal) is the number of the requestor connected to the drive.

Drive port #

This number (in decimal) is the number of the port on the requestor. (The ports are
numbered 0 through 3.)

8-29
TROUBLESHOOTING TECHNIQUES

CX-1121A

Figure 8-4

Request Byte Field

Table 8-13

Request Byte Field Descriptions

Bit

Description

A logical I in this position indicates the drive is unavailable to the controller. A logical 0 indicates
the drive is available to the controller.

A logical 1 in this position indicates the drive requires an internal readjustment. Some drives do
not use this bit.

A logical 1 in this position indicates a request is outstanding to load a diagnostic in the drive
microprocessor memory. A logical 0 indicates no diagnostic is being requested of the host system.

A logical I in this position indicates the drive spindle is up to speed A .logical 0 indicates the
drive spindle is not up to speed.

A logical I in thi~ position indicates usable information in the extended status area. A logical 0

imUcales no -mfoffiiafioii is aVaIlable ih the extended status area.
PB

A logical J in this bit position indicates the drive is connected to the controller through Port B. A
logical 0 indicates the drive is connected through Port A.

A iogicai j in this bit position indicates the drive port select switch for this controller is pushed in
(selected). A logical 0 indicates the switch is out.

A logical I in this position indicates the RUN/STOP switch is pushed in (RUN). A logical 0
indicates the switch is out (STOP).

CX-1122A

Figure 8-5

Mode Byte Field

8-30
TROUBLESHOOTING TECHNIQUES

Table 8-14

Mode Byte Field Descriptions

Bit

Description

W4-WI

A logical I in any of these four bit positions represents the write-protect status for the subunit.
(For example, a 0001 indicates subunit 0 within the selected drive is write-protected)

A logical I in this position indicates the drive was disabled by a controller error routine or
diagnostic. The fault light is on when this bit is set. A logical 0 indicates the drive is enabled for
communication with a controller.

A logical I in this position indicates the drive can be fonnatted.

A logical 1 in this position indicates the diagnostic cylinders on the drive can be accessed.

A logical I in this position indicates the 576-byte sector format is selected A logical 0 indicates
that the 512-byte sector format is selected.

CX-1123A

Figure 8-6

Error Byte Field

Table 8-15

Error Byte Field Descriptions

Bit

Description

A logical I in this position indicates a drive error has occurred and the drive Fault lamp may be
on.

A logical I in this position indicates an error occurred in the transmission of a command between
the drive and the controller. The error could be a checksum error or an incorrectly fonnatted
command string.

A logical I in this position indicates improper command codes or parameters were issued to the
drive.

A logical I in this position indicates a failure in the initialization routine of the drive.

A logical 1 in this position indicates a write-lock error has occurred.

8-31
TROUBLESHOOTING TECHNIQUES

CX-1124A

Figure 8-7

Controller Byte Field

Table 8-16

Controller Byte Field Descriptions

Bit

Description

S4-S1

This is a four-bit representation of the subunits with attention available messages suppressed
in the controller. The rightmost bit (SI) represents subunit 1. The leftmost bit (S4) represents
subunit 4.
If one of the bits is set, it indicates the controller is not to interrupt the host CPU with an
attention available message when the specified subunit raises its available real-time drive status
line to the controller. The S4 through SI bits reflect the results of a CHANGE CONTROLLER
FLAGS command in which attention available messages are not desired for certain subunits.

C4-Cl

This is a four-bit drive status code indicating various states of drive operation. At the present
time, only three codes are valid:
~Drive nonn-at operntion.

1000-Drive is offline because it is under the control of a diagnostic.
lool-Drive is offline due to another drive having the same unit identifier (for example,
serial number, drive type, class).

NOTE

When the HSC marks the drive as inoperative, it places the drive in a state of Unit-Offline with
a substate of unit-inoperative relative to this HSC.
8.4.2.7 Disk Transfer Errors

Disk transfer errors are either data or media format type errors. Example 8-4 shows an example disk
transfer error printout, and Table 8-17 describes the various fields of the printout. See Section 8.5 for
listings and explanations of the disk transfer errors.

8-32
TROUBLESHOOTING TECHNIQUES

ERROR-E SEVEN Symbol ECC Error at 27-Mar-1985 12:15:15.00
50400015
Command Ref #:
120.
RA81 unit 41=
9.
Err Seq I
02
Format Type
EO
Error Flags
01C8
Event
o.
Recovery level
o.
Recovery count
426978
LBN
100020
Orig err flags
000003
Recovery Flags
LvI A retry cnt
1.
O.
LvI B retry cnt
143022
Buffer addrs
5.
Source Req.
5.
Detecting Req.
Error-I End of error.

Example 8-4

Disk Transfer Error Printout

Table 8-17 describes the fields in a disk transfer error message not described in Table 8-8. Unless
otherwise specified, all fields in this table are shown in decimal numbers. These fields are specific to
an RA8! disk and may not be the same for other RAxx type drives.
Table 8-17

Disk Transfer Error Printout Field Descriptions

Field

Description

RA81 unit #

This is the number of the unit the error log message relates to, or is 4095 if the unit
number is unknown. In this example, the RA81 indicates the drive is an RA81 and is
unit 120.

Recovery level

This number indicates the drive error recovery level used for the most recent transfer
attempt by the unit. In this example, the 0 indicates it used error recovery level O. An
RA81 only has a recovery level of 0 (recalibration).

Recovery count

This number indicates the number of times the drive recovery level was tried. In this
example, the 0 indicates the recovery level was not retried.

LBN

This number indicates the logical block number. In this example, the LBN is 426978.

Orig err flags

This number (octal) indicates the original errors associated with this error. Table 8-18
describes the bits associated with this field. In this example, the 100020 indicates:
ECC Error
•

Recovery flags

EDC error

This number (octal) indicates the recovery flags the software processes should take to
recover from this error. Table 8-19 describes the bits associated with this field. In this
example, the 000003 indicates:
An LBN should be replaced.

The current error should be logged on the console and to the host if a connection is
present.

8-33
TROUBLESHOOTING TECHNIQUES

Table 8-17 (Cont.)

Disk Transfer Error Printout Field Descriptions

Field

Description

LvI A retry ent

This number indicates the number of times the HSC attempted the level A recovery
routines. These routines are those not requiring any exhaustive SI exchanges as pa...9'f of
the recovery sequence. In this example, the 1 indicates the ECC error correction was
completed in the HSC without going over the S1.

LvI B retry cnt

This number indicates the number of times the HSC attempted the level B recovery
routines. These routines require extensive SDI exchanges as part of the recovery
sequence. In this example, the 0 indicates no level B recovery was attempted.

Buffer addrs

This number (octal) is the address of the HSC internal Data Buffer associated with this
error. In this example, the buffer address is 143022.

Source Req.

This number is the requestor that filled the buffer with data In this example, the 5

indicates the source requestor was requestor number 5. A requestor of 1 in this field
would indicate a disk Write operation. All other values would indicate· a disk Read
operation.
This number is the requestor that detected that error. In this example, the 5 indicates
requestor number 5 detected the ECC error.

Detecting Req.

Table 8-18 shows definitions of the original error flags and Table 8-19 defines the recovery flags.

Table 8-18

Original Error Flags Field Descriptions

nit

.M.~_~k_{Qc;~1J

Definition
------ -------_. __ -

100000

ECC error

040000

SERDES overrun error

020000

SDI Response/Data line pulse error

12 and 11

014000

Suspected position error-low header mismatch

010000

Header sync timeout

004000

Header compare error-<=ompare-64 performed (high header mismatch)

002000

Data sync timeout

001000

Drive clock timeout

000400

SDI State line pulse or parity error

000200

Data bus overrun

000100

Data memory parity error

000040

Data memory NXM

000020

EDC error

03 and 02

000014

Read/Write Ready down at end of sector

8-34
TROUBLESHOOTING TECHNIQUES

Table 8-18 (Cont.)

Original Error Flags Field Descriptions

Bit
03

Mask (Octal)
000010

Definition

000004

Lost Receiver Ready before transfer began

000002

Forced error (EDC = ones complement of correct EDC)

000001

Drive inoperative

Table 8-19

Recovery Flags Field Definitions

Bit

Mask (Octal)

Definition

000200

Indicates a revector was done for this LBN.

000100

Indicates a positioner error was detected on this block.

000040

Indicates the error count reported by the ILEXER should be updated.

000020

Indicates an error log message has already been generated for the current
error.

000010

Indicates an RCf entry for the desired logical block number was found.

000004

Indicates revectoring and replacement should be suppressed.

000002

Indicates the current error should be logged on the console and to the host
if a connection is present.

000001

Indicates the logical block should be replaced.

Lost Read/Write Ready before transfer began

8.4.3 Bad Block Replacement Errors (BBR)
Another type of error displayed on the console tenninal is for a bad block replacement request. The
bad block replacement request is a result of the one of the following errors:
•

Data sync timeout

•

ECC symbol error above the threshold

•

Header compare error

•

Header sync timeout

•

Loss of R/W Ready at end of read from disk (SERDES read)

•

Uncorrectable ECC

Example 8-5 shows a bad block replacement message. This message reports completion, successful
or unsuccessful, of a bad block replacement attempt. A message is generated regardless of the
success or failure of the replacement attempt. Refer to Table 8-20 for a definition of the fields in
the message explicit to this type of message. Table 8-21 describes replace flag bits. Fields generic
to all MSCprrMSCP error messages are described in Table 8-8. See Section 8.5 for listings and
explanations of BBR errors.

8-35
TROUBLESHOOTING TECHNIQUES

ERROR-W Bad Block Replacement (Success) at 18-Dec-1985 18:05:37.1
Command Ref t
B8590012
RA60 Unit t
251
~Seq t
2
Format Type
09
Error Flags
80
Event
0014
Replace Flags
8000
LBN
205
Old RBN
0
New RBN
5
Cause Event
00E8
ERROR-I End of error

Example 8-5

Bad Block Replacement Error Printout

Table 8--20 defines BBR error fields not previously described in Table 8--8. The replace flags are
defined in Table 8--21.
Table 8-20

Bad Block Replacement Error Printout Field Definitions

Field

Description

Replace Flags

This number (in hexadecimal) indicates bit flags used to report in detail the outcome of
the bad block replacement attempt. In this example, the 8000 indicates the block was
verified as bad

LBN

This number (in decimal) is the logical block number that is the target of the
replacement. In this example, the LBN is 205.

Old RBN

This number (in decimal) indicates the RBN the bad LBN was formerly replaced with,
or zero if it was not formerly replaced. In this example, the 0 indicates it was not
formerly replaced.

New RBN

This number (in decimal) indicates the RBN the bad LBN wac; replaced with, or is zero
if no actual replacement was attempted. In this example the new RBN is 5.

Cause Event

This number (in hexadecimal) is the event code from the original error that caused the
replacement to be attempted. The number is zero if that event code not available. (Refer
to Appendix C.) In this example, the 00E8 indicates an uncorrectable ECC error caused
the bad block replacement.

8-36
TROUBLESHOOTING TECHNIQUES

Table 8-21

Replace Flags Bit Descriptions

Bit
Number

Bit
Mask
Hex

8000

Replacement attempted-This bit is set if the suspect bad block indeed tested
bad during the initial stages of the replacement process. If not set, the suspect
block did not check bad and no replacement was completed.

4000

Forced error-The data from the su~ct bad block could not be corrected
or obtained without error. The Forced Error Indicator will be written to the
replacement block along with the bad data from the block that was replaced.
The user data from the bad block is read with a forced error when accessed.
If this condition occurs frequently on a specific drive, then a closer analysis of
the drive for possible problems is recommended.

2000

Nonprimary revector-This bit is set if the replacement process was
accomplished and required putting the bad block data into a replacement
block that is not the bad block's primary RBN.

1000

Refonnat error-This bit is set during the replacement process if the status
coming back from the execution of the MSCP REPLACE command is not
successful. If this occurs, the drive should not be used until it is refonnatted.
NOTE: The HSC does not use the REPLACE command as it initiates its
own BBR. This message is printed for the HSC equivalent of the REPLACE
command such as FORMAT SECTOR.

800

RCf inconsistent-This bit is set if the Replacement Control Tables are not
usable. The drive should not be used until it can be refonnatted.

400

Bad replacement block-This bit is set if the bad block reported is a
replacement block. The replacement block can be replaced just like any
other LBN.

Flag Bit Definition

8.4.4 TMSCP-Specific Errors
The Tape Mass Storage Control Protocol (TMSCP) error messages printed out at the console terminal
are one of the following types:
•

STI communication or command errors

•

STI formatter error log errors

•

STI drive error log errors

•

Controller errors (Refer to Section 8.4.1)

See Section 8.5 for listings and explanations of tape errors.

8-37
TROUBLESHOOTING TECHNIQUES

8.4.4.1 STI Communication or Command Errors
Example 8-6 is a sample console printout of an STI communication or command error. Table 8-22
explains the fields additional to those defined in Table 8-8.
ERROR-E Drive detected error at 6-Mar-1985 09:51:11.88
Cormnand Ref t
864EOOO4
0
TA78 unit i
12
Err Seq :J
40
Error Flags
OOEB
Event
13026
Position
GSS Text
02 00 00 00
05 00 00 00 00 00 00 00
Error-I End of error

Example 8-6

STI Communication or Command Error Printout

Table 8-22

STI Communication or Command Error Printout Field Descriptions

Field

Description

Event

The number (in hexadecimal) identifies the specific error or event reported by thi.~ error log
message. The event codes and their meanings are shown in Appendix C. In this example, the
OOEB means drive-detected error.

Position

This is the last known tape position the formatter received. This is given in gap counts from BOT.
In this example, the number 13026 means 13026 gaps from BOT.

GSS Text

The GSS Text field is the response received by the HSC from the formatter when the HSC issues
the GET SUMMARY STATUS (GSS) and TOPOLOGY commands. The GSS text in this exanlple
is 02 00 0000 05 00 00 ()() ()() POOP 00. Thism~an~ lev~12 pr~tocol error, Speed Management
Enabled, and Zero Threshold. See Section 8.4.4.5 for details on field definitions and bit decoding.

8.4.4.2 STI Formatter Error Log
The following is an example of the console printout of an STI fonnatter error log. Example 8-7 shows
the printout, and Table 8-23 explains the fields not previously defined in Table 8-8.
ERROR-E Tape Formatter Requested Error Log at 30-Jan-1986 11:20:09.31
Cormnand Ref t
43900012
TA81 unit t
95
Err Seq t
47
Format Type
08
Error Flags
40
Event
FF6C
Position
1057
Formatter E Log 40 00 00 81 00 00 00
01 98 72 00 00 00 00
C4 48 00 00
ERROR-I End of error.

Example 8-7 STI Formatter Error Log Printout
Table 8-23 STI Formatter Error Log Field Descriptions

Field

Description

Position

The last known tape position the formatter received. This is given in gap counts from
BOT. In this example, the number 1057 means 1057 gaps from BOT.

STI Formatter E Log

See Table 8-24.

8-38
TROUBLESHOOTING TECHNIQUES

Table 8-24

STI Formatter E Log

Byte
No.

Data

Description

Fonnatter error

Byte

Data pulse parity error during data transfer
The information contained in these fields is product specific. Refer to the
appropriate drive manual for a description of the remainder of the bytes.

8.4.4.3 STI Drive Error Log

The following is an example of a console printout of an STI drive error log. Example 8-8 shows
the printout, and Table 8-25 explains the fields additional to those defined in Table 8-8. Table 8-26
describes GEDS Text field, and Table 8-27 describes the Drive Error Log field.
ERROR-E Tape Drive Requested Error Log at 5-Mar-1985 14:43:31.15
Command Ref t
06300023
TA78 unit t
528
Err Seq t
210
Error Flags
40
Event
FF6B
Position
1
GEOS Text
7D 04 5000 01000000
Drive Error Log 00 00 00 00 50 3B 04 00
46 FF 07 FF 00 00 00 00
81 00 00 00 FF 22 04 C4
00 00 80 FF 17 94 00 08
00 00 09 FF FF FF FF FF
FF 47 E6 EO 00 16 25 97
A2 00 00
ERROR-I End of error

Example 8-8
Table 8-25

STI Drive Error Log Printout

STI Drive Error Log Field Descriptions

Field

Description

Position

The last known tape position where the HSC believes the tape drive is, upon successful
completion of all outc;tanding commands. This is given in gap counts from BOT. In this
example the number 1 means 1 gap from BOT.

GEDS Text

See Table 8-26.

Drive Error Log

See Table 8-27.

Refer also to Section 8.4.4.4 for field definitions and bit decoding.

8-39
TROUBLESHOOTING TECHNIQUES

Table 8-26

GEDS Text

Byte No.

Byte Data

Description

125 ips tape drive

6250 bpi GCR encoding

MSCP unit number

Gap count = 1

=80

The infonnation shown in Table 8-27 is product specific to the TA78. See the TA78 service manual
for details.
Table 8-27

STI Drive Error Log (TA78 Drive Product Specific)

Byte No.

Byte Data

Description

1,2

No soft error

Set byte count

6, 7

3B,04

Operational error
Error ID = 59
CRC error
ACRC error
Pointer mismatch
Uncorrectable or two-track error set in ECCSTA register
Unknown fault number

RMC write fail bits

Statistics select clock stopped
STATUS VALID

Non-BOT command status is OK

Last cmd sent to M8953 via
RCMD = nonnal NON-BOT read

Read channel AMfIE status (CH 7:0)

8-40
TROUBLESHOOTING TECHNIQUES

Table 8-27 (ConI.)

STI Drive Error Log (TA78 Drive Product Specific)

Byte No.

Byte Data

Description

Read channel illegal status (CH 7:0)

End mark for read channels 7:0

Weak amplitude on parity bit
ECC corrected output (parity bit)

Read channel PE postamble detect

Data from read channels to ECC

CRC checker output bits

Corrected data (ECC to CRC)

Two-track BCC perfonned on data
AMTlE during data of record

Channel 0 tie bus 2
Amplitude track in error AMTIE

Channel 3 tie bus 3

Tie bus = OF(X)

Tape unit bus line AMTIE 7:0

AMTIE parity
READ parity
WCS parity
Tape unit present

TU bus line read data 7:0

STI bus error byte

CRC to WMC DR bus

33,34

Tape unit selected = 0

R/W Data, intennediate DRD bus

36, 37

Byte count = 65535

38, 39

PAD counter = 65535

40,41

Unknown error code

8-41
TROUBLESHOOTING TECHNIQUES

Table 8-27 (Cont.)

STI Drive Error Log (TA78 Drive Product Specific)

Byte No.

Byte Data

Description

DR :MBD parity error

PE write parity error
POWER OK

Tape unit ready and online

125 ips tape drive

47,48

25,97

Tape unit serial #2597

AMTIE thresho1d field = 2
READ ENABLE
Write BIT 4

8.4.4.4 Breakdown of GEDS Text Field
The following is an example of a tape drive-related error message printed on the HSC tenninal.
ERRQR~W

Tap.e_ Dri_ve Requ_estedError Log at lS-Au_g-19_8418: 43: 05 .80
Command Ref t
00001D8E
TA78 unit t
20.
Err Seq t
1.
Error Flags
40
Event
FF6B
Position
2.
GEDS Text
7D 02 0014 00000002
Drive Error Log 00 00 00 00 C5 38 04 04
46 FF 07 FF 00 00 00 00
81 00 00 21 FF BO 00 04
00 00 80 FF 17 DE 00 08
00 00 21 FF FF 00 00 99
99 47 F4 E8 00 56 85 19
A2 OA 80 FF 17 DE

Example 8-9

Tape Drive Related Error Message

Both the GEDS Text and Drive Error Log portions of this message result from a GET EXTENDED
DRIVE STATUS command to the drive from the HSC. The Drive Error Log portion can be interpreted
by referencing the service manual for the appropriate tape drive. (The preceding example is for a TA78
drive.)
Following is a breakdown of the information contained in the GEDS Text field. The leftmost byte is
referenced as the first byte and the rightmost byte as the eighth byte.
Bytes in the GEDS Text field are described in the following list.
•

First byte Speed-Currently set speed of the drive; it is an integer value (in hex) in inches per
second (ips) rOWlded down to the nearest integer. For a totally variable speed drive, the speed
returned is the lower bOWld on the range of pennissible speeds. In the example shown, this field
contains a value of 7D which corresponds to 125 ips.

8-42
TROUBLESHOOTING TECHNIQUES

•

Second byte = Density-The current operating density of the tape unit. Only one bit is set to
indicate the current operating density.
04 = 6250 bpi
02 = 1600 bpi
01 = 800 bpi

•

Third and fourth bytes =Unit number-Contain the drive unit number (in hex).

•

Fifth through eighth bytes = Gap count-The formatter's gap count is from the beginning of
the taPe to where the tape drive is. The contents of this field may differ from the Position field in
this error message. The HSC's gap count is contained in the Position field at the end of successful
completion of all outstanding commands.

8.4.4.5 Breakdown of GSS Text Field

Following is another example of a tape drive-related error message printed at the HSC console.
ERROR-E Drive detected error at 18-Aug-1984 12:05:34.82
Command Ref t
0346003
TA78 unit t
3.
Err Seq t
7.
Error Flags
40
Event
OOEB
Position
O.
GSS Text
02 20 00 00
28 00 00 00 00 00 14 00
ERROR-I End of error.

Example 8-10

Additional Tape Drive-Related Error Message

The HSC receives the GSS Text field form of this error message from the tape formatter when the
HSC issues the GET SUMMARY STATUS (GSS) and TOPOLOGY commands. The field is also the
unsuccessful response for all Level 2 commands. Figure 8-8 is a breakdown of this response.

8-43
TROUBLESHOOTING TECHNIQUES

SUMMARY MODE BYTE 2

CONTROLLER BYTE

MR EL

DRIVE 0 MODE BYTE

OA PS

SUMMARY ERROR BYTE

TM EaT BOT WL OL AV
DE

DRIVE 0 ERROR BYTE

MR EL

DRIVE 1 MODE BYTE

DRIVE 1 ERROR BYTE

MR EL

DRIVE 2 MODE BYTE

DTE SME DI

TM EaT BOT WL OL AV
PL

EX DTE SME DI

TM EaT BOT WL OL AV
DE ,LP

SUMMARY MODE BYTE 1

DRIVE 2 ERROR BYTE

TM EaT BOT WL OL AV MR EL

DRIVE 3 MODE BYTE

DTE SME DI

DRIVE 3 ERROR BYTE
CX-2116A

Figure 8-8

GSS Text Field Bits Summary Breakdown

8.4.4.6 GSS Text Field Bit Interpretation
An interpretation of the GSS text field bits follows.

•

AC: Cache attention

•

AF: Formatter attention asserted

•

A3: Drive 3 attention asserted

•

A2: Drive 2 attention asserted

•

AI: Drive I attention asserted

•

AO: Drive 0 attention asserted

•

ASM: Automatic speed management

•

AV: Drive available to formatter

•

BM: Block mode

•

BOT: Beginning of tape

•

CB: Cache busy

•

CC: Cache capable

•

CDL: Cache data list

•

CE: Cache error

8--44
TROUBLESHOOTING TECHNIQUES

•

CF: Cache full

•

CMT: Cache em pty

•

en: Controller flags (CO-C8)-The following combinations are implemented. All other
combinations are reserved.

co: Normal operation
Cl: Formatter offline--Fonnatter is offline to hosts due to being under diagnostic control.
•

DE: Drive error-Asserted when any drive error not covered by other status bits is detected.

•

DF: Formatter diagnostic failed

•

DI: Diagnostic mode--When set, instructs the fonnatter to use special internal algorithms to report
inlperfect performance.

•

DIR: Direction-When clear, indicates the tape will be positioned in the forward direction.

•

DR: Diagnostic requested-Asserted when the fonnatter is requesting permission to execute a
diagnostic.

•

DTE: Data transfer error-Asserted when any error occurs which prevents a data transfer from
completing successfully.

•

EL: Error logging request-Asserted by either the drive or formatter when error logging
infonnation is available.

•

EOT: End of tape--Asserted when the tape is positioned at or past the end of tape marker.

•

ER: Erase--When set, indicates that a Rewind operation will erase the tape from the current
position forward to EOT before rewinding the tape.

•

EX: Exception condition-Asserted whenever the formatter encounters TM, BOT, or EOT during
a data Transfer operation.
FD: Retry Bit, failure / direction-Asserted during error recovery to indicate the direction of
a retry or to indicate a failing operation. If RP = 0 and RT = 1, then FD = direction to transfer.
FD = 0 means transfer in the same direction as original operation; FD = 1 means transfer in the
opposite direction of original operation. If RP = 1 and RT.= 0, then FD indicates success or failure
of operation. FD = 0 means the retry sequence succeeded; FD = 1 means the retry sequence failed.

•

FE: Formatter error-Asserted on fonnatter errors not covered by the TE, PE, or DF bits.

•

LP: Lengthy operation in progress-Asserted when a Rewind operation (including the optional
data security erase portion of a rewind) is in progress.

•

LS: Long/short success time--When a formatter rejects a command with cache busy and cache
full, it also appropriately sets the LS bit. If the fonnatter thinks the rejected command can be
accepted if immediately issued, LS is clear. If not, LS is set. LS is clear if CB is cleared, and
therefore if CB is clear, LS must be clear.

•

MR: Maintenance mode request-Asserted when the drive is put into maintenance mode. On the
TA78, this is accomplished via a thumbwheel switch on the operator panel.

•

NR: No read-ahead-Set if read-ahead caching is disabled on this unit.

•

OA: Formatter online or available (for the TOPOLOGY command)

•

OL: Drive online to formatter

•

PB: Active port button-PB = 0 if the fonnatter is connected to the controller through port A; PB
= 1 if the fonnatter is connected to the controller through port B.

8-45
TROUBLESHOOTING TECHNIQUES

•

PE: Level 2 protocol error-Asserted when a protocol error is detected while processing a Level
2 command.

•

PL: Position lost-Asserted when the formatter is not certain of the current tape position.

PR: Position for retry

•

PS: Port switch-Asserted when the port switch is enabled.

•

PT: Position for termination-Positions the tape to where it would have been had there been no
error and exits the error recovery state.

•

RP: Request position-Used by the formatter along with RT to inform the controller of the next
step in the error recovery sequence.
Retryable RP = 1, RT = 1
Transfer RP = 0, RT = 1
Done RP = 1, RT = 0
No Error RP = 0, RT = 0

•

RR: Read reverse is supported

•

RT: Request transfer-Refer to the explanation for RP.

•

RWC: Rewrite capable-This bit must not be set if CC is not set.

•

RWE: Rewrite error recovery-Can only be set if CC is set.

•

SG: Space gaps-Indicates a location where the tape operation will position the tape. This is
detennined by the number of gaps specified in the gap field .

•

SM: Speed mask-SM = 0, supports up to four fixed speeds. SM = 1, supports totally variable
speeds.

•

SME: Speed management enabled-Asserted whenever the fonnatter may change the current
operating speed of a particular drive at any time (provided the changing of the drive operating
speed is transparent to the controller).

•

SR: Space records-Positions the tape according to the number of records in the count field.

•

TE: Transmission error-Used by the formatter to report level 0 and level 1 STI errors. The
formatter only reports level 0 real-time state parity errors and Write/Cmd Data Line pulse errors
when a transfer is in progress. Levell errors are framing errors, checksum errors, inappropriate
value in data field of real-time command, or a real-time command occurring in an invalid context.

•

TM: Tape mark

•

UO: Low order drive number bit-The drive to which a command applies.

•

UI: High order drive number bit-The drive to which a command applies.

•

UN: Unload-Unloads a tape after rewind.

•

WB: Write back-Set if write back caching is enabled on this unit. CC also must be set.

•

WL: Write locked

•

WP: Write protect-Set when the controller desires to illuminate the write protect light on the
selected unit.

. _... _---

---

8-46
TROUBLESHOOTING TECHNIQUES

•

ZT: Zero threshold-Instructs the formatter to change all error thresholds from their default values
to zero.

NOTE

Always verify proper dc voltage levels if the indicated possible FRUs do not rectify failure.

8.4.5 Out-of-Band Errors
The out-of-band errors are those not conforming to a specific template format, as the MSCP and
TMSCP errors do. The method of reporting differs for individual errors.
The HSC operating software allows the setting of different levels of error reporting for out-of-band type
errors using the SETSHO utility. These message error levels are Informational, Warning, Fatal, Error,
and Success. The identifiers for the out-of-band errors are followed by an I, W, F, E, or S, depending
on the SETSHO value. The x in the following list represents the message error level. Out-of-band
errors are classified into five categories, listed below.
1. CI errors-Identified by HOST-x identifier printed prior to message.
2. Load device errors-Identified by SYSDEV-x identifier prior to message.

3. Disk functional errors-Identified by DISK-x identifier prior to message.
4. Tape functional errors-Identified by TAPE-x identifier prior to message.
5. Miscellaneous (software inconsistencies)-Identified by SINI-x identifier prior to message.
See Section 8.5 for listings and explanations of the above categories of out-of-band errors.
NOTE

Some out-of-band errors report microcode-detected error status codes within the printout. Refer
to Appendix D for a full list of aU K.ci-, K.sti-, K.sdi-, K.si-, and microcode-detected errors.
NOTE

When replacing indicated FRUs, always verify correct dc voltage levels before and after replacing
a module.
8.4.5.1 RX33 Load Device Errors

Detected errors from the RX33 load device are classified in the out-of-band error category. The
following is an example printout of a detected RX33 error.
SYSDEV-S Seq 104. at 6-JAN-1986 10:12:00.76
DX1: LBN 1488. (49,0,02), Status 001
Seek 000, 000000
Tran 003, 021404
T.O. 000
87 3 1485 -7680 1 49 1 4

The -S following the SYSDEV prompt and before the Seq. number indicates the severity level. The
RX33 has three severity levels:
1. Success (S): Two or less errors during a command/retry.
2. Informational #(1): More than two errors.
3. Error (E): Unrecoverable error.
The status field is most important and is a direct indication of the error. Following is a list of the RX33
status codes.

•

000: Success.

•

001: Success with retries.

8-47
TROUBLESHOOTING TECHNIQUES

•

002: Software version mismatch (driver versus operating code).

200: Command aborted via a ICTRUV! or exception operation.

•

201: Illegal file name.

•

202: File not found.

•

203: File is not in a loadable image format.

•

204: Insufficient memory to load image.

•

205: No free partition to load image into.

•

206: Unit is software-disabled.

•

365: Unit is write-protected.

•

367: No media mounted.

•

375: EOF detected during read or write.

•

376: Hard disk error, other than the following:
-

370: Bad unit number.

357: Data check error.

343: Motor broken (would not spin up).

340: Uncorrectable seek error (desired cylinder not found).

311: Bad record (LBN) number (not on media).

2_7'},: Parity error in controller ()ll M.std2 module.

In the example, the failing floppy disk drive is indicated by DX1:. The logical block number where the
failure occurred is displayed by LBN 1488. The three numbers in parentheses, separated by commas
after the logical block number, indicate (in order) they are shown the cylinder, the media swiace, and
the drive sector.
The Seek entry's first group of zeros shows the retry count for seek/recal errors or the number of times
the command was issued but not completed. The second group of zeros shows an inclusive OR of the
control and status registers CSR bits set during seek error retries. The important bit in a seek error is
bit 4.
The Tran (transfers) entry's first group of zeros shows the retry count for read, write, and format errors,
or the number of times the command was issued and not completed. The second group of zeros shows
an inclusive OR of the CSR bits set during read, write, and format error retries. A breakdown of the
upper CSR bits is shown in Figure 8-9.

PAR
ERR

NXM INTR
DMA
ERR ENABLE DIS

TST
HI
PAR

TST
LO
PAR

MOTR
DRV
ENABLE SEL

CSR BITS

CX-1125A

Figure 8-9

RX33 Floppy Controller CSR Breakdown

Table 8-28 shows the status of the lower CSR bits.

8-48
TROUBLESHOOTING TECHNIQUES

Table 8-28

Status Register Summary

Bit

All Type I
Commands

Read
Address

Read
Sector

Read
Track

Write
Sector

Write
Track

Not Ready

Write
Protect

Head Loaded

Record 'JYpe

Seek Error

RNF

CRC Error

Track 0

Lost Data

Index Pulse

DRQ

Busy

The T.O. entry line is a timeout recording for each command type. This counter reflects the total
number of timeouts for the command in error. All commands (Read, Write, Recal, Spinup, and Fonnat
Track) time out in one second.
The last line in the error message is more complicated to break down. Figure 8-10 shows the
breakdown of the last line of the error message.

1485

-7680

SECTOR NUMBER

SURFACE NUMBER
'-------CyliNDER NUMBER
' - - - - - - - - - UNIT NUMBER
' - - - - - - - - - - - BYTE COUNT (NEGATIVE IMPLIES WRITE)
~-------------LBN

'---------------------------SUCCESSCOUNT
'---------------------ERRORCOUNTNUMBER
CX-2117A

Figure 8-10

RX33 Error Message Last Line Breakdown,

Most infonnation in the error printout is reiterated in the last line. Starting from the right, sector,
surface, cylinder number, and unit number are displayed as in the main body of the error message. The
byte count has an indicator for write and read commands; the negative indicates a Write operation.
The LBN in this field is the starting LBN for this transfer. The LBN in the main message body is the
failing LBN. The success count and error count are for informational purposes.

8-49
TROUBLESHOOTING TECHNIQUES

8.4.5.2 Disk Functional Errors

Although most disk drive-related errors are MSCP errors, several disk functional errors fall into the
out-of-band error category. They are identified by the DISK-E identifier printed on the terminal display
prior to the error.
The message, message description, field service action, and probable FRUs for the disk functional
out-of-band errors are located in Section 8.5.
8.4.5.3 Tape Functional Errors

Although most tape errors are covered under TMSCP errors, certain tape functional errors are classified
in the out-of-band error category. They are identified by the TAPE-E identifier printed prior to the error
printout on the local console terminal. See Section 8.5 for listings and explanations of out-of-band tape
functional errors.
8.4.5.4 Miscellaneous Errors

Miscellaneous errors are identified by the SINI-E identifier printed on the local console terminal. Many
of these messages are one-line or two-line messages, but some have several lines of informational text
that result frOlu subsystem exceptions. Subsystem exceptions detect inconsistet\cies in the operating
software. Listings and explanations of SINI errors are located in Section 8.5.
The SINI error messages are a result of the operating software performing a consistency check which
failed. When consistency checks fail, the HSC performs a soft initialization causing it to crash and
reboot. This is known as a subsystem exception. Upon successful completion of the reboot, the
subsystem exception printout displays the contents of several HSC registers as well as the status of all
requestors. As a result of the subsystem exception, the SINl error message is printed. This message
. tells why the last soft Init happened.
The actual sequence of events for a SINI-E out-of-band error printout is as foHows:
1. When the HSC detects an unrecoverable problem, a soft Init or crash occurs. A system dump is
performed under the heading SUBSYSTEM EXCEPTION. The HSC then reboots.
2. When the HSC reboots, a message indicating it has rebooted, followed by the multiline SINI
message, gives the reason for the iast soft lnit (crash).
3. The same message is written on the system diskette and can be examined with the SHO
EXCEPTION command. A host error message log is also filed in host memory as an HSC
datagram, storing the out-of-band error SINI message.

8.4.6 Traps
The four traps described in the following sections (Trap through 4, Trap through 10, Trap through 114,
and Trap through 134) are the same as are found in the 1170 CPU.
8.4.6.1 NXM (Trap through 4)
If the error registers in the NXM printout equal 170024 000077, the error is not a Non-Existent
Memory (NXM) error. Instead, it is a stack overflow or some illegal instruction. When the error
register is any number other than 170024 000077, the number represents the unresponsive address. The
NXM trap produces a subsystem exception printout similar to the example in Section 8.4.6.5.1.

If the error register equals 16xxxx, the Wmdow Bus register equals the Control memory address
causing the NXM error. If the failing address is in Control memory and shows an NXM error, it is
definitely a hardware problem. Otherwise, it can be either a software or a hardware problem.

8-50
TROUBLESHOOTING TECHNIQUES

8.4.6.2 Reserved Instruction (Trap through 10)
The subsystem exception message for this trap indicates the vector number is 10 and identifies the
trap as fLOP (an illegal Opcode). Refer to the (PC-6) to (PC): field in the example (Section 8.4.6.5.1).
With a Trap through 10, the third word from the left is the instruction causing the trap. If this is a valid
PDP-ll instruction, it is definitely a hardware problem. Otherwise, the program may not be executing
in the right place, indicating the problem could be either hardware or software.
8.4.6.3 Parity Error (Trap through 114)
This error, caused by hardware, does not crash the HSC but causes a reboot and SINI error message.
The error message shows the last reboot caused by the Trap through 114 and the address that caused
the trap.

Determine if the error occurred in memory or in cache memory by reading the contents of the low error
address displayed in the error printout. If the content is the address of the low error address register
(170024), the error is in cache memory. Any other address indicates the error is in memory.
In the following example printout, note the low error address and the high error address fields. When
these fields contain the exact addresses as shown in this example, the error is from the P.ioj cache.
SINI-E

Seq 1. at 17-Nov-1858 00:00:01.60
Parity Error (Trap through 114)
Process PSCHED
PC 111022
PSW 140000
Lo err adr 170024
Hi err adr 000077
WBUSR 020633

8.4.6.4 Level 7 K Interrupt (Trap through 134)
A level 7 K interrupt, detected by hardware or microcode, occurs when one or more requestors detect
a fatal error condition while executing functional code. The microcode-detected errors causing level
7 K interrupts result from a microcode consistency check failure in either K.sdi, K.sti, K.si, or K.ci
microcode. Requestor hardware-detected errors are the result of errors detected on the Control bus,
scratchpad RAM parity errors/Data bus parity errors, or host clears, or Control bus NXMs (not related
to data transfers). The requestor, upon detecting the error, generates a level 7 interrupt to the P.ioj/c.
The P.ioj/c traps through location 134, causing a reboot.
8.4.6.5 Control Bus Error Conditions (Hardware-Detected)
The hardware-detected Control bus errors causing level 7 K interrupts are:

•

Control bus error-The requestor was in the process of executing a Control bus cycle and
received CERR L (Control bus error low) from the P.ioj/c. The P.ioj/c had detected an illegal
Control bus cycle type.

•

Control bus parity error-The requestor detected bad parity on the data it read off the Control
bus.

•

Control bus NXM-The requestor tried to reference Control memory and did not receive an
acknowledgment (CACK L) from the M.std2 within the timeout period.

8-51
TROUBLESHOOTING TECHNIQUES

8.4.6.5.1 Level 7 K Interrupt Printout
An example of a detected level 7 K Interrupt follows.
SUBSYSTEM EXCEPTION *Vi 250
HSC LONDON
at 25 Oct 1985 00:08:46.64 ~21.40
User
PC:
PSW: 140011

110574 caused by

(134

~(-0 Dr
/'-1 I

PSCHED active

PCB addr = 054536

RO-R5:
000000

000000

000024

) Kint

000000

052744
047260

045412
000000

001012
051300

000000
000000

045644
054742

000000
000000

User Stack:
150042 147502
000000 000000

147516
000000

000000
000000

102146
000000

000000
000000

KPAR(0-7) :
000440 000640

001040

1577770

001440

001240

000240

177600

KPDR (0-7) :
077506 077506

077506

077406

077506

077406

077506

UPAR(0-7) :
000000 000000

000000

002204

001240

000240

177600

UPDR(0-7) :
077406 077406

077406

063406

077406

000116

Kernel SP: 000774
Kernel Stack
005046
052136

000004
000000

User SP: 000774

MMSR(0-2): 000017

000000

037260

Window Index Reg: 000026

Window Bus Reg: 001431
WADR (0-7) :
160004

161004

162004

163004

164004

165004

166004

167004

Translated WADR(0-7) :
001401 001401 001401

001401

000377

~ 000377

000371

Error Regs: 170024

000077

Status of Requestors (1-9) :
000001 000377 000377 000377
(PC-6) to (PC):
013737 141020 110560 013701
Control area for slot 1000006
Control area address: 017660:
Register area contents:

IS Ab

000377

STft Tf.!5

001.[-;

~!,~

)0)

\ t;T';';;

[e.e.cQ...
\,?il

S2-7

8-52

TROUBLESHOOTING TECHNIQUES

__ ~ i<' E:,&t ')Ie: f<
000000 -\.l(
000000 1<0
000011 R\
021154 Rz..
102557 {<.3
000770 R"t
000000 R'5
000000 I~ ,
017650
000000 RIc
057502
\3 IT b
~11
005317 Ri2002224
1(13
001000
Rl\.i
000000 RI5
000671 R.lb
000000 R,1
143444 R.20
107001
001000
005317
002212
000671
001000
000000
000000
000000
040506
000010
000374
043520
005400
001000

«7

Booting
INIPIO-I Booting

Requestor 6 has failed with a status of 175. Refer to Appendix D to determine if th\,; failure was a
Control bus error.
At this time the HSC reboots. A message is displayed on the local console terminal stating the HSC
has rebooted.
HSC Version 200 29-Sept-1985 23:17:28

System LONDON

The actual SINI error message is printed on the local console terminal after the HSC has rebooted.
SINI-E

Error sequence 1. at 17-Nov-1858 00:00:03.00
Last soft Init caused by level 7 K interrupt
From process PSCHED
PC 110574
Status: 001 377 377 377 377 175 377 377 377

The resulting 134 trap information is printed on the local console terminal. The PSCHED statement
indicates PSCHED was the active process when the error occurred. The status statement shows
requestor 6 failed with a status of 175. Also, three lines after the status line is a message line
indicating the control area for slot six and slot six control address. This indicates requestor 6 is
the failing requestor. The INIPIO-I Booting statement indicates the HSC is attempting to reboot.
When the HSC completes the initialization, the Last soft Ioit caused by level 7 K interrupt failure
is printed on the local console terminal identified by SINI-E. The active process at time of failure is
identified. In this case, the active process was PSCHED. If the failure is a hard failure, the following
message may also be displayed on the local console terminal.

8-53
TROUBLESHOOTING TECHNIQUES

SINI-E ERROR SEQUENCE 1. AT 25-0CT-1959 00:00:02.90
REQUESTOR 6 FAILED INIT DIAGS, STATUS 107

This message is also considered an out-of-band error.
8.4.6.6 MMU (Trap through 250)

Following is an sample printout of a detected Memory Management Unit (MMU) failure.
**SUBSYSTEM EXCEPTION**
Vi Y10B
at 12-DEC-1995 13:43:40.05

HSC70 LAYER
2 19:24:07.40

MMU

SETSHO active, PCB addr = 104116
RO-R5:
000320

000001

100000

100212

000266

000002

053314
047426

045762
000000

001012
052052

000000
000000

046214
051042

000000
000000

User Stack:
040314 021356
020040 020037

033552
020037

021356
000330

021246
101000

000040
027113

017440
000144

017440
060542

KPAR(0-7) :
000440 000640

001040

001440

002040

001240

000240

177600

KPDR.(D-7} :.
077506 077506

077506

Kernel SP: 000774
Kernel Stack:
005046 000004
047022 000000
User SP: 000226

UPAR(0-7) :
007074 007274

006410

000000

002240

001240

000240

177600

UPDR (0-7) :
077506 077406 _~ 077406

077406

077506

000116

MMSR(0-2) :~ 000000

004743

Window index reg: 000002
Window bus reg: 001407
WADR(0-7) :
160000

161004

162440

163000

164004

165004

166220

167034

Translated WADR(0-7) :
000000 001401 067510

040000

001401

010444

001407

000203

000377

Error rags: 170024

000077

Status of requestors (1-9) :
000001 000002 000002 000002
(PC-6) to (PC):
027441 067516 051040

000377

071545

Because the trap is a MMU trap, look first at the register contents of MMSRO (memory management
status register 0). Refer to Figure 8-11 for a breakdown of the bits in MMSRO.

8-54
TROUBLESHOOTING TECHNIQUES

1 15 114 1 13 112 111
~

110 1 9 1 8 I 7 1 6 1 5 1 4 1 3 12 11 10 1
~~

•I

ABORT, NONRESIDENT!
ABORT, PAGE LENGTH
ERROR
ABORT, READ ONLY
ACCESS VIOLATION
TRAP, M EMORY MANAGEMENT
NOT USE D
NOT US ED

ENABLE MEMORY MANAGEMENT TRAP
MAINTE NANCE MODE

'"'

.INSTRUCTION COMPLETED
PAGE MO DE
PAGE AD DRESS SPACE I/D
PAGE NU MBER
ENABLE RELOCATION

CX-1126A

Figure 8-11

MMSRO Bit Breakdown

---Look at the printout lines for MMSR (0-2). Compare the bits set in MMSRO to the bit breakdown in
Figure 8-11. The example indicates a page length violation on page 2. The page length error bit is set,
and the page number 2 bit is set.
Next, check the PSW line and detennine the mode in which the HSC reported this error. A 14xxxx in
the PSW means User mode, a OOxxxx in the PSW means Kernel mode. Also, above the PSW line the
word User or Kernel appears to identify the mode. Our example shows User mode is active. Therefore,
the next register contents of any value are the UPAR and UPDR. If the active mode had been Kernel,
the important registers would have been the KPDR and KPAR registers.
The first group of numbers under the UPAR(0-7) line is for page zero, the second for page one, the
third for page two, and so forth. The third group of numbers in the example are for page two, the
violated page. Note the difference in UPDR contents on page two versus the UPDR contents on other
pages. The UPDR contents on other pages all start with 077 designating a full page of memory to be
allocated for that page. The UPDR contents on page two starts with a 013., indicating a short page.
Two possible problems cause this error:
1. Memory Management Unit on the P.ioj/c
2. Software
Software inconsistency (Trap through 20) is reported similar to an MMU trap. A subsystem exception
is dumped on the local console tenninal with the trap vector reported being a Trap through 20 (AT),
An example printout and explanation are found in Appendix B.

8-55
TROUBLESHOOTING TECHNIQUES

The subsystem exception is followed by the HSC reboot. Upon successful reboot, the following
message is displayed.
HSC70 Version Y10B

16-Jan-1986

15:30:20.20

System MASTER

Then the SINI error resulting from the detected subsystem exception is printed.
SINI-E Sequence 1. at 16-Jan-1986 00:00:11.20
Last soft Init caused by software inconsistency
From process HOST
PC 007044
PSW 140001
Stack dump: 000016 006401 015476

8.5 ALPHABETICAL LISTING OF SOFTWARE ERROR MESSAGES
Each message description includes the following:
•

Actual error message--Displayed in English at the HSC console terminal.

•

Error type--The subsystem where the error occurred or was detected.

•

Error message severity level-Included in the error message.

•

Message description-A review of what the error is about.

•

Field service action-Remedies or troubleshooting paths that the field service representative can
take to correct the problem.

•

Possible FR Us-Suggested components that are likely suspects causing the malfunction.

Aborting Error Recovery Due to Excessive RECALs
Disk Unit xxx.
Requestor xx
Port xx

Error Type: Disk functional out-of-band
Severity: Error
Description: For each group is a transfer, a count of the number of RECALS issued to the drive
is kept. H the count exceeds a hard-coded value, this message is printed. Recovery from an error
is not possible because of excessive RECALS and the drive is declared inoperative.
Field Service Action: Refer to the drive service manual and any other type errors being logged to
determine reasons for persistent positioning failures.
Possible FRUs: Drive unit
Aborting Error Recovery Due to Excessive Timeouts
Disk Unit xxx.

Error Type: Disk functional out-of-band
Severity: Informational
Description: The HSC detects several timeouts on the disk drive. A timeout occurs because the
drive did not complete its expected work in the expected time. All error recovery attempts will be
aborted and the drive will be declared inoperative.
Field Service Action: May need to replace the following FRUs. Further testing may be necessary.
Possible FRUs:

8-56
TROUBLESHOOTING TECHNIQUES

1. Drive module (Refer to the drive service manual.)

2. K.sdi/K.si module
Acknowledge Not Asserted at Start of Transfer

Error Type: Tape error
Severity: Error
Description: The HSC is ready to start a transfer by sending the formatter a Levell command
and the formatter does not have ACKNOWLEDGE asserted.
Field Service Action: Check the formatter. This error may indicate a fonnatter STI
communications error, or if preceded by tape transport errors, may be a result of a transport
failure.
Possible FRUs:
1. Formatter
2. K.sti/K.si module
3. STI cable set
ATN Message Sent to Node xx, for Unit xx.

Error Type: Disk functional out-of-band
Severity: Informational
Description: An attention condition was found on the indicated drive unit and an attention message
has been sent to the host to notify it of this condition.
Field Service Action: None
Possible FRUs: None
Attention Condition serviced for ONUNE disk unit xxx.

Error Type: Disk functional out-of-band
Severity: Informational
Description: An attention condition indicating a state change in the drive needs servicing. A GET
STATUS exchange is invoked to the drive. Note: This may not indicate a failure condition.
Field Service Action: Refer to the console printed Get Status response.
Possible FRUs: Drive modules (Refer to the drive service manual.)
Bad Block Replacement (Block OK)

Error Type: BBR error
Severity: Warning
Description: Block tested OK-not replaced.
Field Service Action: Monitor drive for the frequency of these reports. If frequency increases,
troubleshoot the error that triggers BBR.
Possible FRUs: Refer to Cause Event error message field in Table 8-20.

8-57
TROUBLESHOOTING TECHNIQUES

Bad Block Replacement (Drive Inoperative)

Error Type: BBR error

Severity: Warning
Description: Replacement failure or drive access failure. One or more transfers specified by the
replacement algorithm failed. If necessary and possible, write-protect the drive and perform a
volume backup immediately.
Field Service Action: Drive should be tested further. Move the drive to another K.sdi/K..si (or to
just another K.sdi/K.si port) if available. If the problem persists, failure is probably in the drive.
Possible FRUs: Drive module (Refer to the drive service manual.)
Bad Block Replacement (RCT Inconsistent)

Error Type: BBR error
Severity: Warning
Description: Replacement failure-the RCT table is not usable.
Field Service Action: Drive media should not be used until replaced or verified as good. If
necessary, write-protect this drive and have the customer perform a volume backup immediately.
Further testing of the drive may be necessary.

Possible FRUs: Drive module (Refer to the drive service manual.)
Bad Block Replacement (Recursion Failure)

Error Type: BBR error
Severity: Warning
Description: Replacement failure-recursive failure. Two successive RBNs were bad.
Field Service Action: Monitor drive for the frequency of these reports. If frequency increases,
troubieshoot the error triggering BBR.

Possible FRUs: Refer to Cause Event error message field in Table 8-20.
Bad Block Replacement (REPLACE Failed)

Error Type: BBR error
Severity: Warning
Description: Replacement failure-REPLACE command or its analogue failed. The status
returned from the replacement process indicates the command was not successful.

Field Service Action: Drive media should not be used until it is replaced or verified as good. If
necessary, write-protect this drive and have the customer perform a volume backup immediately.
Further testing of the drive may be necessary.

Possible FRUs: Drive module (Refer to the drive service manual.)

8-58
TROUBLESHOOTING TECHNIQUES
Bad Block Replacement (Success)

Error Type: BBR error
Severity: Warning
Description: The bad block was successfully replaced,
Field Service Action: Monitor drive for the frequency of these reports. H frequency increases,
troubleshoot the error triggering BBR.
Possible FRUs: Refer to Cause Event error message field in Table 8-20.
Bad Dispatch State In CB ...

Error Type: CI-detected out-of-band
Severity: Warning
Description: The CI Manager sends a SCS control message and finds an invalid dispatch state
in the control block. The CI Manager then uses the dispatch state to detennine where to send the
proper control message. H this is the only known problem, a software problem could exist within
the HSC. Otherwise, the problem could be caused by a Control bus addressing problem with the
K.pli, M.std2/M.std, or P.ioj/c modules.
Field Service Action: Replace the following FRUs.
Possible FRUs:

1. K.pli
2. M.std2/M.std

3. P.ioj/c
Booted from Drive 1. Drive 0 Error (text)

Error Type: SINI error
Severity: Wormational
Description: The system was booted from system device drive 1. Normal boot is from drive O.
Field Service Action: None
Possible FRUs: Drive 0
Buffer EDC Error

Error Type: Tape error
Severity: Error
Description: The K.sti/K.si detected an EDC error on the Data Buffer it read from memory on a
Write operation.
Field Service Action: Test the data path from K.sti/K.si to HSC Data memory and the K.cL
Possible FRUs:

1. Formatter
2.

M.std2/M.std module

3. K.sti/K.si module
4. K.d module

8-59
TROUBLESHOOTING TECHNIQUES

Cache Disabled Due to Failure

Error Type: SIN! error
Severity: Error
Description: SINI looks back at the Cache diagnostic and senses the cache is disabled due to
cache failure or manually disabled in the diagnostic. This error also shows as a soft fault code on
the OCP.
Field Service Action: Load the Offline Cache diagnostic and answer the prompt asking to disable
or enable Cache with an enable. Reboot the system diskette and check if the original message is
displayed again.
Possible FRUs:
1. P.ioj module

2. M.std2 module
Clock dropout from ONLINE disk unit xx.

Error Type: Disk functional out-of-band
Severity: Error
Description: The online disk has lost its real-time state clock.
Field Service Action: Check the path between the K.sdi/K.si and the disk drive that was reported.
Determine if the problem is in the HSC or the disk drive. Other disk error reports may precede this
message and provide more detail about this error condition.

PossibleFRUs:
1. Drive modules (Refer to the drive service manual.)

2. SOl cable

3. K.sdi/K.si module
Compare Error

Error Type: Controller error
Severity: Error
Description: A compare error occurred during a Read-Compare or a Write-Compare operation.
For the Read-Compare operation, the HSC again obtains the data from the unit or shadow set and
compares it with data obtained from host memory. If the data is not the same, a compare error
results. For the Write-Compare operation, the controller obtains data from each destination and
compares it with data again obtained from host memory. If the data is not the same, a compare
error results.
Field Service Action: Isolate the FRU by moving the disk or tape unit to another data channel
and retrying the exact failing operation. Also, check the HSC Data memory buffer address for
repetition. If failure occurs on multiple physical units across multiple data channels and HSC Data
memory buffer address is not repetitive, investigate a possible K.ci problem.
Possible FRUs:
1. Isolated disk (or tape) unit
2. Data channel
3. M.std2/M.std

8-60
TROUBLESHOOTING TECHNIQUES

4. K.ci module set
5. Host CI/memory
Controller Detected Position Lost

Error Type: Tape error
Severity: Error
Description: Information contained in the response from the formatter to the HSC POSITION
command did not match the expected tape drive position.

Field Service Action: Check the formatter. If the error persists, run the Inline Tape (ILTAPE)
diagnostic to help isolate to the FRU.

Possible FRUs: Formatter
Controller Transfer Retry limit Exceeded

Error Type: Tape error
Severity: Error
Description: The controller failed to perform the command within the limit of allowable retries.
Field Service Action: Check the formatter and the drive.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. Formatter
Controller Detected Transmission or Timeout Error

Error Type: SDI
Severity: Error
Description: The controller detected an invalid framing code or a checksum error in a level 2
response from the SDI drive.

Field Service Action: Determine if this error is occurring on more than one drive, which may
indicate a K.sdi/K.si problem. However, if it is occurring only on one drive, the SDI cable or
the drive may be at fault. Refer to the appropriate drive service manual for assistance with drive
FRUs.

Possible FRUs:
1. SDI cable
2. Drive SDI interface module
3. K.sdi/K.si module
4. SDI transition bulkheads

8-61
TROUBLESHOOTING TECHNIQUES

Could Not Complete Online Sequence

Error Type: Tape error
Severity: Error
Description: Could not complete online sequence due to a condition in the drive.
Field Service Action: Check the formatter and the drive.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. Formatter
Could Not Get Extended Drive Status

Error Type: Tape error
Severity: Error
Description: Issued the GET EXTENDED DRIVE STATUS command and the drive did not
respond with the extended drive status.
Field Service Action: Check the formatter.
Possible FRUs: Formatter
Could Not Get Formatter Summary Status During Transfer Error Recovery

Error Type: Tape error
Severity: Error
Description: Issued the command and the formatter did not respond with the formatter summary.
Field Service Action: Check the formatter.
Possible FRUs: Formatter
Could Not Get Formatter Summary Status While Trying to Restore Tape Position

Error Type: Tape error
Severity: Error
Description: Issued the command and the formatter did not respond with the formatter summary
status.
Field Service Action: Check the formatter.
Possible FRUs: Formatter
Could Not Position for Formatter Retry

Error Type: Tape error
Severity: Error
Description: The HSC issued a command for data recovery with position required, and the drive
could not complete the command.
Field Service Action: Check the media, drive, and formatter.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)

8-62
TROUBLESHOOTING TECHNIQUES

2. Media
3. Fonnatter
Could Not Set Byte Count

Error Type: Tape error
Severity: Error
Description: Issued command to set byte count and could not complete command.
Field Service Action: Check the formatter.
Possible FRUs: Formatter
Could Not Set Unit Characteristics

Error Type: Tape error
Severity: Error
Description: Issued command to set unit characteristics and could not complete command.
Field Service Action: Check the formatter.
Possible FRUs: Formatter
Data Bus Overrun

Error Type: Controller error
Severity: Error
Description: The HSC attempted to perform too many concurrent transfers, causing one or more
of them to fail due to a data overrun or underrun. For example, data is sent to a bus by a data
producer and then removed from the bus by a data consumer. If the producer sends data to the bus
more quickly than the consumer can remove it, a data overrun occurs. If the consumer removes
data more quickly than the producer can send it, a data underrun occurs.
Field Service Action: Detennine which module is the data producer and which module is the
consumer for a given error. Use the requestor number for assistance.
If the problem persists after replacing the suspect module(s), an HSC software problem should be

investigated.
Possible FRUs: Source or detecting requestor modules.
Data Error Flagged In Backup Record
Disk Unit xx LBN xx
Tape Unit xx

Error Type: Tape functional out-of-band
Severity: Warning
Description: During a backup, a data error was encountered. During the BBR, the record was
written with a forced error bit set.
Field Service Action: Check BBR history on source drive.
Possible FRUs:
1. Disk unit
2. Media

8-63
TROUBLESHOOTING TECHNIQUES

Data Memory Error (NXM or Parity)

Error Type: Controller error
Severity: Error
Description: The HSC detected an error in internal Data memory. The error was either a parity
error, detected via a parity generator/checker (data only-not address) on the requestor module, or
a nonresponding address (the requestor did not receive a DACK from the memory module).
Field Service Action: Determine if this error is repetitive; if so, the problem is probably the
M.Sld2/M.std module. However, it may be a Data bus problem caused by a number of things, such
as failing bus drivers/receivers on the indicated requestor modules.
Possible FRUs: M.std2/M.std or a possible Data bus problem.
Data Ready Timeout

Error Type: Tape error
Severtty: Error
Description: The controller did not detect Data Ready from the formatter within 5 ms after
sending it a Level 1 command.
Field Service Action: Check the STI path.
Possible FRUs:
1. STI cable set
2. K.Sli/K..si module
3. Formatter
Data Sync Not Found

Error Type: Disk transfer error
Severity: Error
Description: This error occurs when the SERDES 16 does not detect the SYNC character (26BC
hex) immediately preceding read data from the disk drive. The K.sdi/K..si has already read a valid
header and is awaiting the data SYNC character.
Field Service Action: Determine if additional errors occur from this drive to indicate a drive or
media error. If not, the problem is probably the K.sdi/K..si module.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. K.sdi/K..si module
3. SDI interface

8-64
TROUBLESHOOTING TECHNIQUES

DatelTlme Set By Node nn

Error Type: CI-detected out-of-band error
Severity: Infonnational
Description: The HSC received either a START or STACK (start acknowledge) message over the
CI, and the date and time was not set.
Field Service Action: None. This is a nonnal message as part of establishing a VC between a
host and an HSC.
Possible FRUs: None
Deferred AnN. Message for Node xx, Unit xx.

Error Type: Disk functional out-of-band error
Severity: Infonnational
Description: An attention message is delayed in process.
Field Service Action: None
Possible FRUs: None
Disk unit xx. (Requestor xx., Port xx.) being INITialized.
DeB addr: xxxxxx

Error Type: Disk functional out-of-band
Severity: Infonnational
Description: A disk is being initialized.
Field Service Action: None
Possible FRUs: None
Disk unit xx. ready to transfer.
Retrieval failure or subsystem deadlock probable.

Error Type: Disk functional out-of-band
Severity: Infonnational
Description: A disk transfer did not complete within the allowable timeout period. The USC
software cannot detect any problems to account for the failure. Possible problems include:
1. No available buffers
2. Drive problems
3. K.sdi/K..si problems
Field Service Action: Check data transfer path. This error may indicate too many utilities or
inline diagnostics running simultaneously. The problem might also be an HSC software problem.
Possible FRUs: K.sdi/K..si module

8-65
TROUBLESHOOTING TECHNIQUES
Disk unit xxx. (Requestor xx., Port xx.) declared inoperative.
Intervention required.

Error Type: Disk functional out-of-band
Severity: Error
Description: The Disk Path process has conc1uded that the drive is no longer usable. Any pending
I/O is clenned up and the drive state is set to either UNDEFINED or OFFLINE. The HSC ignores
the disk until it detects some intervention. An example is to deport the port button to drop the state
clock.
Field Service Action: Examine previous error reports to help resolve failure. Toggle port switch
on drive.
Possible FRUs: Drive modules (Refer to the drive service manual.)
DRAT/SEEK timeout, disk unit xxx.

Error Type: Disk functional out-of-band
Severity: Informational
Description: A stimulus resulting in error recovery code action is the expiration of the
DRAT/SEEK timer for the drive. A DRAT represents data transfer action with the drive, whereas
the SEEK represents position requests to the drive.
Each drive has a timer (set to three times the SDI drive short timeout value) allocated on its behalf
at subsystem initialization time. This timer, called the DRAT/SEEK timer, is active whenever data
transfer activity to the drive is outstanding.
When the disk transfer code queues transfer work to K.sdi/K.si on behalf of a previously idle drive,
the timer starts. When it adds transfer work to a drive that already has transfer work, the timer
restarts. When it detects the completion of the last DRAT queued to the drive, the timer stops.
Thus, the timer is running only as long as transfer work is outstanding. A timer may expire for
several reasons:
1. The drive has detected a drive error and has lowered Read/Write Ready.
2. The drive has stopped sending clock signals.
3. A SEEK has timed out.
4. Another element in the subsystem that should have supplied resources to the disk transfer
operation in a reasonable time did not.
Field Service Action: Check the drive.
Possible FRUs: Drive modules (Refer to the drive service manual.)
DRIVE CLEAR attempt on disk unit xx. (Requestor xx., Port xx.).
DCB addr: xxxxxx Error count ******.

Error Type: Disk functional out-of-band
Severity: Informational
Description: The drive detected some previous error and the HSC is now attempting to clear that
error.
Field Service Action: Examine the host error log to determine what error the drive is trying to
clear.
Possible FRUs: Drive

8-66
TROUBLESHOOTING TECHNIQUES

Drive Clock Dropout

Error Type: SOl error
Severity: Error
Description: Either data or state clock was missing when it should have been present. This is
detected by the requestors connected to this SOl drive, usually by means of a timeout.
Field Service Action: Oetermine if this error is occurring on more than one drive, which may
indicate a K.sdi/K.si problem. However, if it is occurring on only one drive, the SOl cable or
the drive may be at fault. If other errors surround or precede this one, those errors may have
sequentially triggered this error. Refer to the appropriate drive service manual for assistance with
drive FRUs.
Possible FRUs:
1. SOl cables
2. Orive SOl interface module
3. K.sdi/K..si module
4. SOl transition bulkheads
Drive Detected Error

Error Type: SOl error
Severity: Error
Description: The controller received a GET STATUS command or unsuccessful response with
the EL bit set, or the controller received a response with the OR flag set and does not support
auloJnatic diagnosis for that SOl drive type.
Field Service Action: Oetermine if the drive has a hard fault (fault light on and an error code
in the drive microprocessor LEOs). Refer to the drive service manual for assistance with drive
internal diagnostics and LED error codes. Oecode remaining error message bytes for more detailed
error infonnation. If error message decoding does not clearly indicate a drive error, move the drive
to another requestor (or requestor port) to help isolate failure between HSC and drive.
Possible FRUs:
1. Orive modules (Refer to the drive service manual.)
2. SOl cables
3. SOl bulkheads
Drive Inoperative

Error Type: SOl error
Severity: Error
Description: The HSC has marked the drive inoperative due to an unrecoverable error in the
previous level 2 exchange, the drive's Cl flag is set, or the drive has a duplicate unit identifier.
Once the HSC reports the drive as inoperative, the drive state clocks must transition to return the
drive to an operational state.
Field Service Action: Refer to the drive service manual. Run ILDISK to help isolate failure
between HSC and drive.

Possible FRUs:
1. Drive modules (Refer to the drive service manual.)

8-67
TROUBLESHOOTING TECHNIQUES

2. K.sdi/K.si module
3. SDI cables
Drive Requested Error Log (EL Bit Set)

Error Type: SDI error
Severity: Error
Description: The controller requested a drive error log because the drive returned a status message
with the EL bit set in the request byte field.

Field Service Action: Determine what drive-detected error (previous error description) caused the
drive to request a drive error log by finding the error in the error log report. Also decode remaining
fields in the drive status response of this error message and any preceding errors on the unit.
Possible FRUs: Drive modules (Refer to the drive service manual.)
Duplicate Disk Unit xx

Error Type: Disk functional out-of-band
Severity: Informational
Description: Disk unit numbers are duplicated within the system.
Field Service Action: Locate the duplicate disks and change the plug number on one.
Possible FRUs: Drive modules (Refer to the drive service manual.)
EDC Error

Error Type: Controller error
Severity: Error
Description: The sector was read with correct or correctable ECC and invalid EDC. A fault
probably exists in the logic of either this controller or the controller that last wrote the sector.
Look at the source and detecting requestor fields in the error message to determine which requestor
detected the error and the direction of the transfer (read or write).

Field Service Action: Determine if other errors indicate a problem with the data path circuitry on
the indicated requestor modules.

Possible FRUs:
1. K.sdi/K.st module
2. M.std2/M.std, if an address parity error on Data memory occurs, as this is checked by the EDC
field.
ERASE Command Failed

Error Type: Tape error
Severity: Error
Description: Issued ERASE command and command failed.
Field Service Action: Check the formatter.
Possible FRUs: Formatter

8-68

TROUBLESHOOTING TECHNIQUES

ERASE GAP Command Failed

Error Type: Tape error
Severity: Error
Description: Issued ERASE GAP command and command failed.
Field Service Action: Check the formatter.
Possible FRUs: Formatter
Forced Error

Error Type: Disk transfer error
Severity: Error
Description: The sector was written with a Force Error modifier indicating this is a replaced image
and the original data could not be read correctly using retries and the ECC algorithms.
Field Service Action: Restore the media from a previous backup. A VMS (HSC70) backup and
restore of the current media will clear the forced error condition but will leave the sector corrupt.
Possible FRUs: None
Formatter Detected Position Lost

Error Type: Tape error
Severity: Error
Description: The formatter lost track of tape position.
Field Service Action: Check the media, drive, and formatter.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)

2. Formatter
3. Media
Formatter and HSC Disagree On Tape Position

Error Type: Tape error
Severity: Error
Description: The formatter and the HSC disagree on position of the tape.
Field Service Action: Check the formatter.
Possible FRUs:
1. Tape drive module
2. Formatter
3. K.sti/K.si module

8-69
TROUBLESHOOTING TECHNIQUES

Formatter Requested Error Log

Error Type: Tape error
Severity: Error
Description: The formatter detected an error and set the EL bit to request an error log be taken.
Field Service Action: Check the formatter.
Possible FRUs: Formatter
Formatter Retry Sequence Exhausted

Error Type: Tape error
Severity: Error
Description: The formatter failed to complete a command within the retry limit.
Field Service Action: Check the media, drive, and formatter.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. Formatter

3. Media
FRB Error: K.cl, 1st LBN xx., xx. buffers, FE$SUM xx

Error Type: Disk functional out-of-band
Severity: Informational
Description: An error was detected by the K.ci while processing a Fragment Request Block (FRB)
and the FRB has been sent to the disk error process. Example: EDC error.
Field Service Action: If excessive, refonnat drive.
Possible FRUs: Drive modules (Refer to the drive service manual.)
FRB Error: K.sdl, Unit xx., 1st LBN xxx., xx. buffers, FE$SUM xx

Error Type: Disk functional out-of-band
Severity: Informational
Description: An error was detected by the K.sdi/K.si while processing a Fragment Request Block
(FRB) and the FRB has been sent to the disk error process. Example: Suspected Positioner error.
Field Service Action: If excessive, reformat drive.
Possible FRUs: Drive modules (Refer to the drive service manual.)

8-70
TROUBLESHOOTING TECHNIQUES

Hard transfer error loading (file) xx

Error Type: SIN! out-of-band
Severity: Error
Description: The P.ioj/c detected a hard error while loading a file from the system media into
Program memory. The particular files that can produce this error are DUP and MIRROR. The xx
field is the error status value from the device driver.
Field Service Action: Load the file from the other system load device; load the back-up media.
Possible FRUs:
1. System media
2. System load device
Hard transfer error writing SeT xx

Error Type: SINI out-of-band error
Severity: Error
Description: The HSC detected an error while attempting to write the scr on the console load
media. The xx designates the octal byte that is the error status value returned from the device
driver.
Field Service Action: Make sure the drive is not write-protected; try the back-up media; try the
other system load device.
Possible FRUs:
1. System media
2. System load device
Header Error

Error Type: SOl error
Severity: Error
Description: The subsystem reads an inconsistent or invalid header for the requested sector.
The header is inconsistent if three out of four copies of the high order header word do not match.
The header is considered invalid if all of the following are true:
•

The header is consistent (three out of four copies of the high order header word match).

•

-Two out of four of the low-word header values match the desired target header low-word value.

•

The high-word header values do not match the respective target header values.

For recoverable errors, this code implies a retry of the transfer to read the valid header. For
unrecoverable errors, this code implies the subsystem attempted nonprimary revectoring and
determined the requested sector is not revectored. Causes of an invalid header include header
mis-sync, header sync timeout, and an unreadable header.
Field Service Action: Determine if this error is repetitive on this unit indicating a deteriorating
media.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)

8-71
TROUBLESHOOTING TECHNIQUES

2. K.sdi/K.si module
HML$ER set-HM$ERR

=nn

Error Type: CI-detected out-of-band
Severity: Warning
Description: A Host Memory Block (HMB) operation resulted in an error. A breakdown of HMB
error word (HM$ERR) bits follow.
•

000002 HME$BM-Insufficient BMBs to receive message.

•

000004 HME$NC-Sequenced message received over a connection with 0 in credit field.

•

000010 HME$NC-Sequenced message received over a connection with credit field> 1.
Excess has been added to CB$EM.
000020 HIvfE$OV-Oversize message received (>1096. bytes).

•

000040 HME$DN-Data memory NXM during BMB operation.

•

000100 HME$DP-Data memory parity error in BMB operation.

•

000200 HME$DO-Data memory overrun during BMB operation.

•

000400 HME$FP-Reception buffer parity error in packet header. Message not receivable.

•

00 1000 HME$PL--Reception buffer parity error in body of message.

•

002000 HME$CN-Transmission not attempted because connection not valid.
004000 HME$VC-Transmission not attempted because VC closed or connection invalid.

•

010000 HIvfE$TE-Transmission attempted but failed (no ACK).

•

020000 HME$TP-Transmission failed due to transmission buffer parity error.

•

040000 HIvfE$HC-Packet inconsistent with K.ci context received from host.

•

100000 HME$IC-Illegal control function Opcode.

Field Service Action: Compare the displayed code to the previous list and determine where the
problem lies. For example, a code of 000040 indicates a failure in the M.std2/M.std module, and a
code of 002000 indicates a problem in the K.ci module set.
Possible FRUs:
1. PILA module
2. K. pli module
3. M.std2/M.std module
Host Clear from CI Node

Error Type: SINI out-of-band
Severity: Error
Description: The host cannot function with the HSC for some reason, such as a nonresponse
within a certain amount of time or too many errors on the CI.
Field Service Action: Check the HSC console messages and the error logs of the systems
connected to the HSC.
Possible FRUs:
1. HSC

8-72
TROUBLESHOOTING TECHNIQUES

2. HSC operating software
3.

System software

Host interface (K.cl) failed INIT diags, status = xxx

Error Type: S~l out-of-band
Severity: Error
Description: The failing status indicates which module in the K.ci set has failed. A soft fault code
is generated and may be examined by pressing the fault button on the OCP.

Field Service Action: Detennine which is the failing module by comparing the failing status value
to the values in Appendix D. This comparison points more directly to the failing module.

Possible FRUs:
1. LINK module
2. PILA module

3. K.pli module
Host interface (K.ci) is required but not present

Error Type: SINI out-of-band
Severity: Error
Description: A K.ci modu1e set is absent, or the failure in the K.ci module set was so severe upon
initialization, the initialization diagnostics did not run.

Field Service Action: Check for the presence of a K.ci module set. If missing, install the K.ci
module set. If K.ci module set is present, determine which module is failing by running Offline
diagnostics. This error generates a soft fault and is examined by pressing the fault button on the
OCP.

Possible FRUs: See list below and error message Last soft Init resulted from unknown cause.
1. K.pli module
2. K.ci module set (anyone of the three modules in the set)
Host Requested Retry Suppression On A Formatter Detected Error

Error Type: Tape error
Severity: Error
Description: The formatter detected an error and the host issued a command to suppress the retry
of the command that failed.
Field Service Action: Check the formatter.
Possible FRUs: Formatter

8-73
TROUBLESHOOTING TECHNIQUES

Host Requested Retry Suppression On A K.stllK.si Detected Error

Error Type: Tape error
Severity: Error
Description: An error was detected in the K.sti/K..si and the host issued a command to suppress
the retry of the command that failed.
Field Service Action: Check the K.sti/K.si.
Possible FRUs: K.sti/K..si module
Illegal bit change in status from disk unit xxx.
EL bit forced on so status logged.

Error Type: Disk functional out-of-band
Severity: Error
Description: An unsupported bit was received in status returned from the disk unit.
Field Service Action: Check the drive and the version of software in HSC.
Possible FRUs:
1. Drive module (Refer to the drive service manual.)
2. Version of software
Insufficient Control Memory for K.stilK.si in Requestor xx

Error Type: Tape functional out-of-band

Severity: Error
Description: Not enough Control memory left in the pool to allocate a control block. A certain
amount of Control memory is needed to set up control blocks. Enough memory was not found to
set up control blocks for turning on the K.sti/K.si functional code.
Field Service Action: Use the HSC SETSHO utility to show available HSC memory (Control,
Data, and Program). If less than 87.5 percent of available Control memory is usable, replace
M.std2/M.std module. Run Offline lEST MEM by K diagnostic and test Control memory.
Possible FRUs:
1. M.std2/M.std module
2. P.ioj/c module
3. Software
Insufficient Private Memory remaining for TMSCP Server

Error Type: Tape functional out-of-band
Severity: Error
Description: In the scr, a parameter determines the maximum number of supported tape
formatters. During initialization, all the working K.sti/K.si modules are counted and a calculation
is done showing the maximum number of possible formatters. These two parameters are compared.
Based on the comparison, a certain amount of private memory is allocated for the TMSCP Server.
If that allocated portion of private memory is not enough, this message is displayed.
Field Service Action: Use HSC SETSHO utility to show available HSC Program memory. If Jess
than 87.5 percent of available Program memory is usable, replace M.std2. Run Offline Test Mem

8-74
TROUBLESHOOTING TECHNIQUES

or Test Refresh to test Program memory. Use the SETSHO SET MAX FORMATTER command to
reduce the maximum number of formatters supported.

Possible FRUs:
1. M.std2/M.std module
2. P.ioj/c module
3. Software
Internal Consistency Error

Error Type: Controller error
Severity: Error
Description: A high-level check detected an inconsistent data structure. For example, a reserved
field contained a nonzero value, or the value in a field was outside its valid range. This error is
probably caused by the requestor microcode or hardware.
Field Service Action: If the error is repetitive, check for consistent requestor numbers in detecting
requestor field of error. Determine if any other surrounding error reports indicate a possible internal
memory error.
Possible FRUs:
1. FRU noted in the detecting requestor field

2. M.std2/M.std memory module
K.cl exception detected, code = nnn

Error Type: CI-detected out-of-band
Severity: Warning
Description: The code is composed of the contents of KH$FLG (the second word in the K.ci
Control Area). Below is a breakdown of the bits contained in this word.
000001 KHF$PD-Path(s) disabled by K.ci due to a transmit error or VC breakage due to
other K.ci-detected errors.
000002 KHF$EQ-Item(s) placed on error queue (KH$EQ).
000004 KHF$BL-Data memory error during BMB list operation.
000010 KHF$UP-Unreceivable packet. K.ci stopped (causes a crash).
000 100 KHF$NH-Sequenced message received while reserved-to-receive queue was empty.
040000 KHF$PD-Set by diagnostics to disable interrupts.

--Field Service Action: Compare the code from the printout to the previous list, and determine
whether the error code points to an HSC module or to the host.
Possible FRUs:
1. Status 1: K.pli module

2. Status 4: M.std2/M.std module
3. Status 10: PILA module, host K.ci set
4. Status 100: Host K.ci set

8-75
TROUBLESHOOTING TECHNIQUES

K.cl loopback microcode loaded

Error Type: CI-detected out-of-band
Severity: Error
Description: The CIMGR detected K.ci loopback microcode was loaded during initialization.
When this message occurs, a problem with the K.pli (LOI07) module probably exists.

Field Service Action: Replace the following FRU.
Possible FRUs: K.pli
K.sdilK.sI In slot xx. failed its Inlt' OIT! status = xxx

Error Type: Disk functional out-of-band
Severity: Error
Description: A requestor fails during boot. The displayed K.sdi/K.si has failed with the displayed
status. This message is displayed only at the end of the boot procedure.

Field Service Action: Record the status for module repair purposes.
Possible FRUs: The K.sdi/K.si displayed.
K.stI/K.sI In Requestor xx has microcode incompatible with this TMSCP Server

Error Type: Tape functional out-of-band
Severity: Error
Descripti~n: The data structure version within the microcode version residing on the K.sti/K.si
module is a lower version than the TMSCP Server can support.

Field Service Action: Use the SET REQUESTOR command to ensure the version of microcode
on the K.sti/K.si module is up to current revision. If not, replace the microcode or replace the
K.sti/K.si module with a K.sti/K.si module of the current revision.

Possible FRUs: K.sti/K.si module
Last soft Inlt resulted from unknown cause

Error Type: SINI out-of-band
Severity: Error
Description: Software has a list of known reasons for reboot (Trap through 134, Trap through
250, CRASH$, SETSHO, etc.). If no reason for reboot is apparent, the software may have failed
to detect where the error came from.

Field Service Action: Check the HSC console error messages and the system error logs on all the
systems connected to the HSC. This error indicates a probable software problem.

Possible FRUs: Dependent upon the information obtained from the error logs.

8-76
TROUBLESHOOTING TECHNIQUES

LBN xx. repaired for shadow member unit xx.

Error Type: Disk functional out-of-band
Severity: Infonnational
Description: A shadow Repair operation was done in which good data was written to bad members
of a shadow set.
Field Service Action: An uncorrectable error occurred on an LBN on the subject drive and was
successfully rewritten. If the problem persists, check for other errors that would give infonnation
on what the uncorrectable error was.
Possible FRUs: Drive modules or media
LBN Restored with Forced Error In RESTOR operation
Disk Unit xx, LBN xx.
Tape Unit xx.

Error Type: Disk functional out-of-band
Severity: Warning
Description: An error was detected in the LBN data during backup. A forced error bit was set in
the LBN.
Field Service Action: If excessive, refonnat drive.
Possible FRUs: Drive modules (Refer to the drive service manual.)
Less than 87.5 percent of Control memory Is available or
Less than 87.5 percent of Data memory Is available or
Less than 87.5 percent of Program memory is available

Error Type: SINI out-of-band
Severity: Error
Description: These three messages are a result of the P.ioj/c polling the memories on initiaJi7.ation
and finding an insufficient amount of working memory in either one. Any combination of the three
messages may appear.
Field Service Action: The error printout determines which memory is failing.
Possible FRUs: M.std2/M.std module
Level 7 K interrupt (Trap through 134)

Error Type: SINI out-of-band, subsystem exception
Severity: Error
Description: A level 7 K interrupt occurs when any requestor detects a fatal error condition while
executing f¥nctiQnal code. The requestor, upon detecting the error, generates a level 7 K interrupt
to the P.ioj/c. The Pt5jFctraps through location 134, causing a reboot. The requestor status and the
failing requestors' status value are displayed for all requestors on the last line of the printout.
Field Service Action: In some cases, the error printout shows a failing requestor when the real
problem is in the M.std2/M.std module. This error can also be caused by software problems.

8-77
TROUBLESHOOTING TECHNIQUES

Wait for two or more failures of this type to detennine if the real problem is the M.std2/M.std
module. If the M.std2/M.std is at fault, the same requestor is not displayed twice as the failing
requestor. Refer to Appendix D for failing status values and their meanings. Check the status line
message to determine the failing requestor status. Change the requestor exhibiting the failing status
if the same requestor is displayed more L.~aIl once.
Possible FRUs:
1. Requestor displaying a continuous failing status value
2. M.std2/M.std module
Lost Read/Write Ready

Error Type: SOl error
Severity: Error
Description: Read/Write Ready drops when the controller attempts to initiate a transfer or at the
completion of a transfer with Read/Write Ready previously asserted. This usually results from
a drive-detected transfer error, where additional error log messages containing the drive-detected
error subcode may be generated.
Field Service Action: Look for surrounding drive-detected errors and/or associated disk tmnsfer
error log. Move suspect drive to another port or data channel to help isolate failure, as this error
may be caused by any of several communication components.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. K.sdilK.si module
3. SDI cables
4. SDI transition bulkheads
Lost Receiver Ready

Error Type: SOl error
Severity: Error
Description: Receiver Ready was negated when the controller attempted to initiate an SOl disk
transfer Oi did not assert at the completion of a transfer. This includes all cases of the controller's
timeout expiring for a Transfer operation (Level 1 real-time command).
Field Service Action: Look for a probable drive error or a possible SOl cable problem. Move
suspect drive to another port or data channel to help isolate failure, as this error may be caused by
any of several communication components.
Possible FRUs:
1. Orive modules (Refer to the drive service manual.)
2. K.sdi/K.si module
3. SOl cables
4. SOl transition bulkheads

8-78
TROUBLESHOOTING TECHNIQUES

Lower Processor Error

Error Type: Tape error
Severity: Error
Description; A bit was set in the Lower Processor error register. Bits included in the Lower
Processor error register are Data bus NXM, data SERDES overrun, Data bus overrun, Data bus
parity error, data pulse missing, and sync real-time parity error.
Field Service Action: Check the K.sti/K.si and the tape formatter.
Possible FRUs: K.sti/K.si module or tape formatter
Lower Processor timeout

Error Type: Tape error
Severity: Error
Description: The Upper Processor in the K.sti/K.si detected the Lower Processor had stopped and
restarted it.
Field Service Action: Check the K.sti/K.si and tape formatter.
Possible FRUs: K.sti/K.si module or tape formatter
MMU (Trap through 250)

Error Type: SINI out-of-band, subsystem exception
Severity: Error
Description: A failure was detected in the Memory Management Unit (MMU) on the P.ioj/c.
The active process is displayed as well as the bit assignments for the memory management status
registers.
Field Service Action: Examine the MMSR registers to determine the failure in the MMU.
Possible FRUs: P.ioj/c module or software error
nnn Symbol ECC Error

Error Type: Disk transfer error
Severity: Error
Description: If a drive has more symbols in error than a drive-defined threshold, the HSC will
print one of the following error messages, even though the error might have been corrected.
One Symbol ECC Error
Two Symbol ECC Error
Three Symbol ECC Error
Four Symbol ECC Error
Five Symbol ECC Error
Six Symbol ECC Error
Seven Symbol ECC Error
Eight Symbol ECC Error
Uncorrectable ECC Error
The following description covers all of the ECC error types that are printed.

8-79
TROUBLESHOOTING TECHNIQUES

ECC errors occur when the data read from the disk does not agree with the data written. When
data is written to the disk, an ECC is calculated (by the R-S GEN) and appended to the end of
the sector. When the data is subsequently read from the sector, the ECC is revalidated. The two
possible results are:

1. The data error falls within the ECC error correction capability (less than nine 10-bit symbols
in error) and data correction is performed. In this case, depending on the drive type, no data
errors are shown.
2. The data error does not fall within the error correction capability of the ECC, and the error is
retried according to drive dependent parameters. If all of the retries fail, an uncorreclable ECC
error occurred and a bad block is reported via an end packet.
NOTE

An uncorrectable ECC error is reported when a transfer with the Suppress Error Correction
modifier encounters an ECC error of any severity.
Field Service Action: Determine if the ECC errors are just nonnal occurrences or if a very large
number of blocks is being replaced. The latter indicates the drive may have a read path problem.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. K.sdi/K.si module
No control block available to satisfy HMB request.

Error Type: CI-detected out-of-band
Severity: Warning
Description: The CIMGR tried to allocate an Host Memory Block (HMB) from the Free Control
Block Queue when none were available. If a significant amount of Control memory was removed
from use due to errors detected during boot, this message occurs. Otherwise, it may indicate an
L'ltema! HSC software problem where control blocks in HSC memory are taken by some service
and never returned to the list of free control blocks.
Field Service Action: Type in the SHOW MEMORY command for HSC50 software version V300
and later and HSC70 software version VI00 and later to determine how much Control memory is
being used. Compare the amount of Control memory shown on the SHOW MEMORY printout
to the amount contained in the HSC. If more than 12.5% has been disabled from use, replace the
memory module.
For HSC50 software before V300, run the offline memory test on Control memory to determine if
excessive solid failures are causing removal of a large amount of memory. If memory amount is
adequate, the problem may be caused by a software or microcode problem within the HSC.

Possible FRUs:
1. M.std2/M.std module
2.

Software

8-80
TROUBLESHOOTING TECHNIQUES

No tape drive structures available for Requestor xx Port xx Unit xx
Increase structures via SET MAX_TAPE command

Error Type: Tape functional out-of-band
Severity: Error
Description: An additional tape drive has been added to an existing tape formatter, but the tape
structures set up in initialization have been exceeded.
Field Service Action: Use the SETSHO utility to increase to the number of tape structures with
the SET MAX_TAPE command.
Possible FRUs: None
No tape formatter structures available for Requestor xx Port xx

Increase structures via SET MAX_FORMATTER command
Error Type: Tape functional out-of-band
Severity: Error
Description: An additional tape formatter has been added to the HSC, but since tape fonnatter
structures are set up during initialization, not enough structure space is available for this additional
tape formatter.
Field Service Action: Use the SETSHO utility to set the structure level higher to compensate for
the additional tape formatter with the SET MAX_FORMATTER command.
Possible FRUs: None
No usable K.stilK.si boards were found by the TMSCP Server

Error Type: Tape functional out-of-band
Severity: Error
Description: The TMSCP Server polJed the HSC and found no working K.sti/K.si modules. This
message does not appear frequently because the TMSCP Server software is not usually loaded if
there are no K.sti/K.si modules.
Field Service Action: Check for a failed initialization diagnostic error message prior to this
message. This prior message displays the failed requestor slot and failing status.
Possible FRUs: The K.sti/K.si(s) displaying the failing status is the FRU.
Node nn cables have gone from crossed to uncrossed

Error Type: CI-detected out-of-band
Severity: Error
Description: This message occurs only when check for a crossed path finds a previously crossed
path no longer crossed. More detail is covered in the description of the error message Node nn
Cables have gone from uncrossed to crossed.
Field Service Action: Note, if both the "uncrossed to crossed" and "crossed to uncrossed"
messages are occurring, it is probably an indication of failing hardware, not a cable problem.
See the Field Service Action in the next message for more detail.
Possible FRUs:
1. CI cables, if a single message is displayed

8-81
TROUBLESHOOTING TECHNIQUES

2. K.ci module set, if both messages are displayed
Node nn cables have gone from uncrossed to crossed

Error Type: CI-detected out-of-band
Severity: Warning
Description: .. This message occurs when an IDRSP (ID Response) packet is received by an HSC in
response to an IDREQ (ID Request) message. Upon receiving an IDRSP packet, the HSC checks
two bits· in the IDRSP message that indicate which path was used by the sending node. If these
two bits do not indicate the same path the HSC received the message on, this error occurs.
Field Service Action: Determine if the problem is broken hardware in the HSC CI interface,
broken hardware in the host CI interface, or if the CI cables are crossed. Before replacing any
modules or cables, determine if the HSC is encountering crossed paths to multiple nodes in the
cluster or only to a particular node. If the HSC is encountering crossed paths to all nodes, the
problem is probably in the HSC or the cables. If it is encountering the problem to only one node,
it is likely a problem with that host node's CI module set or the cables running from the host to the
Star Coupler.
Possible FRUs:

t. Cables physically connected wrong at HSC, Star Coupler, or host CI
2. Any of the three K.ci modules in the HSC (LOtOO or LOt18, L0109, LOt07)
3. Host CI module set
4. Duplicate node address settings
Node nn path has gone from bad to good

Error Type: CI-detected out-of-band
Severity: Warning
Description: A disconnected CI cable has been reconnected, or an intermittent hardware or cahle
problem is indicated. More detail is found in the description of the error message Node nn Path
(A or B) has gone from good to bad.
This message also occurs if an open VC node path was previously found to be bad. During this
polling cycle the node sends out ID_REQ (ID Request) packets to all nodes and receives successful
ID_RSP ID Response messages.

Field Service Action: If the cable was reconnected, there is no further action. Otherwise, replace
the possible FRUs.
Possible FRUs:
1. CI cable
2. Host
3. CI interface hardware in the host

8-82
TROUBLESHOOTING TECHNIQUES

Node nn path (A or B) has gone from good to bad

Error Type: CI-detected out-of-band
Severity: Warning
Description: K.ci microcode detects a hard (unrecoverable) transmission error on a previously
good path. Examples of hard transmission errors are:
Transmit Buffer Parity Error
Unrecoverable NACK
Unrecoverable NO_RSP
Transmitter Attention Timeout
Determining the reason for failure using the error message is not possible.
Field Service Action: Before replacing any FRU, detennine if the message is occurring because
of problems with one host or problems with multiple hosts. If the problem involves one host. it is
probably in the Star Coupler's host side. If the problem involves multiple hosts, it is probably on
the Star Coupler's HSC side. Also, if the message occurs on both paths to a host, that host may
have been powered down, stopped, or may have crashed. Examine the host console log and the
error log to determine if something did happen to the host.
Detennining which error caused the bad path is not possible except with the Transmit Buffer Parity
Error (XBUF PE) which prints as an MSCP type message.
Possible FRUs:
1. CI cable
2. Host
3. CI interface hardware in the host
NXM (Trap through 4)

Error Type: SINI out-of-band, subsystem exception
Severity: Error
Description:
•

A memory location did not respond within the specified timeout period.

•

A stack overflow occurred.

•

An odd address access was attempted. For example, a word access instead of a byte.

•

A halt was executed in User mode.

Field Service Action: Determine which memory is failing by examining the low and high error
address registers for module repair.
Possible FRUs:
•

M.std2/M.std module

•

P.ioj/c module

8-83
TROUBLESHOOTING TECHNIQUES

Parameter change, process yyy
PC xxx
PSW xxx

Reason xxx

Error Type: SINI out-of-band, subsystem exception
Severity: Informational
Description: A parameter has been changed via the SET/SHO utility.
Field Service Action: None
Possible FRUs: None
Parity Error (Trap through 114)

Error Type: SINI out-of-band, subsystem exception
Severity: Error
Descriptio~:

This message covers parity errors in memory and in cache. In the case of a me·mory
parity error, the address of the failing memory is latched into the low error address register. In the
case of a cache parity error, the address is not latched into the low error address register. Instead,
the address of the low error address register is displayed in the error printout.
Field Service Action: Determine if the error occurred in memory or in cache memory by reading
the contents of the low error address displayed in the error printout. If the contents is the address
of the low error address register (170024), the error is in cache memory. If the error is in cache,
the probable FRU is the P.ioj.
Possible FRUs:
1. P.ioj/c
2. M.std2/M.std
P.loj/c running with memory bank or board swap enabled

Error Type: SINI out-of-band
Severity: Error
Description: Upon initialization, an error was detected in the low address space of private memory.
The P.ioj/c asserted the Swap Bank signal, and the second bank of private memory was enabled.
The P.ioj/c and memory combination can still function under limited capabilities.
Field Service Action: Exchange the M.std2/M.std module. The HSC still functions with limited
capabilities.
Possible FRUs: M.std2 module

8-84
TROUBLESHOOTING TECHNIQUES

PLI Receive Buffer Parity Error

Error Type: Controller error
Severity: Error
Description: When the data from the packet in a receive buffer on the PILA module was
transferred to the K.pli module, a parity error was detected on the bus. In this case, parity is
generated by the LINK module (LOlOO/L0118) and checked by the K.pli module (LOI07). The
Pll...A module stores the data without checking or generating parity.
Field Service Action: If faiJure is persistent and is accompanied by K.ci level 7 K interrupt
HSC crashes, analyze K.ci module status code for more detailed information. Run Offline Test
K diagnostic to test K.ci. Any error report should more clearly indicate the specific K.ci module
failure. For very intermittent failures follow the sequence of possible FRUs.
Possible FRUs:
1. Pll...A
2. K.pli

3. LINK
PLI Transmit Buffer Parity Error

Error Type: Controller error
Severity: Error
Description: When data was being transferred from the K.pli to the PILA transmit buffer, a parity
error was detected on the bus. In this case, parity is generated by the K.pli module and checked by
the LINK module. The Pll...A module stores the data without checking or generating parity.
Field Service Action: If failure is persistent and is accompanied by K.ci level 7 K interrupt
HSC crashes, analyze K.ci module status code for more detailed information. Run Offline Test K
diagnostic to test K.ci. Any error report should more clearly indicate specific K.ci module failure.
For very intermittent failures follow the sequence of possible FRUs.
Possible FRUs:
1. PILA
2. LINK

3. K.pli
Position or Unintelligible Header Error

Error Type: SOl error
Severity: Error
Description: The drive reported a Seek operation was successful by returning successful status
in response to the INITIATE SEEK SOl command and asserting R/W Ready when on the desired
cylinder. However, the controller determined the drive had positioned itself to an incorrect cylinder.
The header read from the drive is consistent (three out of four header copies are identical) but does
not match the desired target header value. The transfer will be retried several times and the error is
considered recoverable if the error flags bit indicates success or a subsequent replacement succeeds.
Field Service Action: The drive servo system or media is probably at fault in this case. If one is
available, move the drive to a different requestor. A drive failure is indicated if the failure persists
on the new requestor.
Possible FRUs:

8-85
TROUBLESHOOTING TECHNIQUES

1. Drive modules (Refer to the drive service manual.)
2. K.sdi/K.si module
Positioner error on disk unit xxx. DRAT addr: xxx
Desired hdr (Io,hi):xxx, xxx
Actual hdr (Io,hi):xxx, xxx

Error Type: Disk functional out-of-band
Severity: Informational
Description: The drive positioned the heads in the wrong place or the HSC software is processing
transfers out-of-order.
Field Service Action: Check drive modules and the K.sdi/K.si module.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. K.sdi/K.si module
Premature LP flag in RTNDAT sequence from host node xx

Error Type: Disk functional out-of-band
Severity: Warning
Description: A violation of packet protocol; the last packet flag was se~ ~ore all data was
received from a host.
Field Service Action: IT the problem is transient, monitor error for reperitive node numbers as this
may indicate a host CI problem. IT the problem is persistent across all clusler nodes, test the K.ci.
Possible FRUs:
1. K.ci modules

2. CI cables
Pulse or Parity Error

Error Type: SDI error
Severity: Error
Description: The controller detected a pulse error on either the SDI drive state or data line, or
the controller detected a parity error in a drive state frame. The HSC does. an SDI GET STATUS
command, reports any errors from it, and then clears those errors, if possible. Mter this, the HSC
retries the original command up to two more times before considering tP~ error unrecoverable.
Field Service Action: IT the error is reported on more than one drive, a K.sdi/K.si problem is
indicated. If the error is reported on only one drive, an SOl cable or drive problem is indicated.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. SDI cable
3. SOl transition bulkhead
4. K.sdi/K.si module

8-86
TROUBLESHOOTING TECHNIQUES

RCT Corrupted Error

Error Type: Disk transfer error
Severity: Error
Description: The Ref search algorithm encountered an invalid RCf entry. The subcode may be
returned under the following conditions:
During replacement of a block
During nooprimary revectoring of a block
When bringing a unit online

Field Service Action: Detetmine if this error is repetitive for this unit possibly indicating a
defective media or drive read path failure. Run the HSC utility VERIFY on the drive.

Possible FRUs: Drive modules (Refer to the drive service manual.)
Receiver ready not asserted at start of transfer

Error Type: Tape error
Severity: Error
Description: The HSC is ready to start a transfer by sending the formatter a Level 1 commari
and the formatter does not have Receiver Ready asserted.

Field Service Action: Check the formatter, cable, and K.sti/K.si.
Possible FRUs:
1. Formatter

2. Cable
3. K.sti/K.si module
Record EDC error

Error Type: Tape error
Severity: Error
Description: 00 a read from tape operation, the EDC calculated by the K.sti/K.si did not match
the EDC generated by the tape formatter.

Field Servi~e Action: Check the formatter, cable, and K.sti/K.si.
Possible FRUs:
1. Formatter

2. Cable
3. K.sti/K.si module

8-87
TROUBLESHOOTING TECHNIQUES
Requestor xx failed INIT diags, status = xxx

Error Type: SIN! out-of-band
Severity: Error
Description: The data channel in the displayed requestor has failed initialization diagnostics with
the displayed status.

Field Service Action: Detennine which data channel is in the displayed requestor slot. Make note
of the status value for module repair. Replace the failing data channel.
Possible FRUs: The data channel (K.sdi, K.sti, or K.si) exhibiting the failing status.
Requestor xx has failed Initialization diagnostics with status = xx

Error Type: Tape functional out-of-band
Severity: Error
Description: The requestor in slot xx has failed initialization diagnostics with the displayed status.
The message indicates the failed K.sti/K.si module.
Field Service Action: Refer to Appendix C to detennine what the displayed status indicates the
failure to be.

Possible FRUs: The K.sti/K.si module in the indicated slot.
Reserved Instruction (Trap through 10)
From process yyyy
PC xxx
PSW xxx

Error Type: SINI out-of-band, subsystem exception
Severity: Error
Description: The P.ioj/c detected an Opcode, resulting in the execution of an invalid instruction.
The process indicated is the process that executed the nonexistent instruction.
Field Service Action: Detennine what process was active for module repair.
Possible FRUs:
1. P.ioj/c module
2. M.std2/M.std module
3. Software
Resource lost to K.cl-xxx xxx HMBs

Error Type: CI-detected out-of-band
Severity: Error
Description: A Control memory Host Message Block (HMB) data structure was lost. HMBs were
expected in the sequence message ready to receive queue (.KHSRR), but none were found.

Field Service Action: Report the error, with frequency of occurrence, to support. Also, note
sequence of events that reproduce this failure. This message indicates a software bug. Verify dc
power levels are correct.

Possible FRUs:
1. Software

TROUBLESHOOTING TECHNIQUES

2. dc power
Retry limit exceeded while attempting to restore tape position

Error Type: Tape error
Severity: Error
Description: A command was issued to restore the tape position, and the command failed in the
limit of retries.
Field Service Action: Check the formatter.
Possible FRUs: Formatter
Reverse retry currently not supported

NOTE

As of V3.50 and above, Reverse Retry is supported.

Error Type: Tape error
Severity: Error
Description: Reverse Retry requests from the formatter were not supported before Version 3.50 of
HSe software.
Field Service Action: Update software
Possible FRUs: None
Rewind failure

Error Type: Tape error
Severity: Error
Description: A command for a rewind was issued, and the command failed (the controller received
an unsuccessful response from the formatter).
Field Service Action: Check the drive and/or formatter.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. Formatter
SCT read or verHication error. Using template SCT.

Error Type: SINI out-of-band
Severity: Error
Description: An error was detected by the P.ioj/c as it attempted to read the System Configuration
Table (SeT) or as it attempted to verify the SCT. This error message will occur when new,
previously uninitialized system diskette is booted. The default settings from SYSeOM are used
instead of the SeT from the load media. The second sentence in this message indicates the scr is
new, as derived from the template SCT settings set in the factory. IT the system has been previously
booted from the same media, a system load device failure is indicated.
Field Service Action: Reinstall the old system diskette and do a SHO SYSTEM. Instal1 the new
diskette exhibiting the error and set all system diskette fields to the old values using the SET
command. Reboot the HSe to validate these values and ensure system continuity.
Possible FRUs: System diskette

8-89
TROUBLF-SHOOTING TECHNIQUES

SOl exchange retry on disk unit xxx. (Requestor xx. Port xx.)

DCB addr xx Error count xx.

Error Type: Disk functional out-of-band
Severity: Informational
Description: Retry the SDI command on the drive.
Field Service Action: None
Possible FRUs: None
SOl Clock Persisted after INIT

Error Type: SDI error
Sevedty: Error
Description: The drive clock did not cease following a controller attempt to initialize the SDI
drive. This implies the drive did not recognize the initialization attempt. This error condition
causes the HSC to retry the lnit command eight more times before marking the drive inoperative.
Field Service Action: Determine if this drive has encountered any other related problems which
may be entered in an appropriate error log report. Also, this error may be due to an SDI cable
problem. Closely examine error logs for surrounding disk errors, as the error may be a result of a
previously-reported drive error.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. SDI cable
SI Clock Resumption Failed after INIT

Error Type: SDI error
Severity: Error
Description: The drive clock did not resume following a controller attempt to initialize the SDI
drive. This implies the drive encountered a fatal initialization error. Closely examine error logs for
surrounding disk errors, as this error may be the result of a previously-reported drive error.
Field Service Action: Determine if this drive has encountered any other related problems which
may be found in an appropriate error log report. Also, this error may be due to an SDI cable
problem.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. SDI cable

8-90
TROUBLESHOOTING TECHNIQUES
SI Command Timeout

Error Type: SDI error
Severity: Error
Description: The controller timeout expired for either a level 2 exchange or the assertion of
Read/Write Ready after an INITIATE SEEK command. The HSC retries the command three more
times, reinitializing the SDI drive each time. If the error persists on a single SDI level 2 exchange,
the drive is marked inoperative.
Field Service Action: Determine if this drive has encountered any other related problems which
may be found in an appropriate error log report. Also, this error may be due to an SOl cable
problem. Closely examine error logs for surrounding disk errors, as the error may be a result of a
previously-reported drive error.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)

2. SDI cable
Ensure the drive and all HSC modules are at the latest revision levels.
SI Receiver Ready Collision

Error Type: SOl error
Severity: Error
Description: This error occurs when the drive fails to follow the SOl protocol during SOl
command/reception. For example, the controller sends the drive a command, asserts Controller
Receiver Ready, and waits for the SOl response. The following lists the Possible drive operations
that lead to this error:
1. The drive fails to deassert Orive Receiver Ready. In this case, the drive indicates it did not
receive the command.
2. The drive deasserts Drive Receiver Ready and then reasserts it before sending a proper
SOl response. In this case, the drive believes it has sent a response and is indicating so by
reasserting Orive Receiver Ready, yet the controller has never received the response.
The HSC K.sdi/K.si detects this error. The HSC functional code does an SOl GET STATUS
command and clears the drive of any errors found. The original command is then retried. This
cycle is repeated twice before the drive is initialized by the HSC, and the entire operation is done
two more times. If the failure persists, the drive is marked inoperative.

Field Service Action: Oetermine if this drive has encountered any other related problems which
may be found in an appropriate error log report. Also, this error may be due to an SOl cable or
SDI transceiver/encoder/decoder problem. Closely examine error logs for surrounding disk errors,
as this error may be the result of a previously-reported drive error.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)

2. SOl cable
3. K.sdi/K.si module

8-91
TROUBLESHOOTING TECHNIQUES

51 Response Length or Opcode Error

Error Type: SDI error
Severity: Error
Description: A level 2 response from the drive had correct framing codes and checksum but
was not a valid response within the constraints of the SDI protocol. The response had an invalid
Opcode, was an improper length, or was not a possible response in the context of the exchange.
The HSC K.sdi/K.si detects this error. The HSC functional code does an SDI GET STATUS
command and clears the drive of any errors found. The original command is then retried. This
cycle is repeated twice before the drive is initialized by the HSC, and the entire operation is done
two more times. If the failure persists, the drive is marked inoperative.

Field Service Action: Determine if the drive has experienced other similar errors. Closely
examine error logs for surrounding disk errors, as this error may be the result of a previouslyreported drive error.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. K.sdi/K.si module
51 Response Overflow

Error Type: SDI error
Severity: Error
Description: A drive sent back more frames than the reception buffer could hold. This can be
caused by a hung drive microdiagnostic or a malfunctioning K.sdi/K.si.
Field Service Action: Determine if the drive is failing in other ways, indicating a drive problem.
If not, the K.sdi/K.si may be the more likely cause.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. K.sdi/K.si module
5ERDE5 Overrun

Error Type: Controller error
Severity: Error
Description: This error is either a SERDES overrun or underrun error. Either the drive is too fast
for the controller, or a controller hardware fault prevented controller microcode from keeping up
with data transfer to or from the drive.
Field Service Action: Determine if other errors have occurred that may indicate a K.sdi/K.si
problem. Move the offending drive to another requestor. If the problem persists, test the drive
further.
Possible FRUs: K.sdi/K.si module

8-92
TROUBLESHOOTING TECHNIQUES

Software inconsistency (Trap through 20)

Error Type: SINI out-of-band, subsystem exception
Severity: Error
Description: During operation, the operating software performs numerous consistency checks.
When one of these consistency checks fails, the HSC crashes and reboots. The active process is
displayed, as well as the stack dump.
Field Service Action: Submit a Software Problem Report (SPR) (refer to Appendix B).
Possible FRUs: None
Tape drive requested error log

Error Type: Tape error
Severity: Warning
Description: The drive detected an error condition and set the EL bit for an error log to be taken.
Field Service Action: Check the drive.
Possible FRUs: Drive modules (Refer to the drive service manual.)
Tape formatter connected to Requestor xx Port xx has been declared inoperative.
Intervention required.

Error Type: Tape functional out-of-band
Severity: Error
Description: The K.sti/K.si has sent a nondata transfer command over the STI cable to the
displayed tape formatter three times and has received back the same error three times. The HSC
then ignores the tape formatter until it detects some intervention such as a change in the state clock.
Field Service Action: Replace the possible FRUs. Deasserting the tape drive's port switches,
recycling power, unplugging the STI cable, or any action causing the state clock to come and go
is considered an intervention. The HSC will not attempt to communicate with the failing tape
formatter until it detects this change in state clock. Examine any previous error reports for more
specific data regarding this error message.
Possible FRUs:
1. Tape formatter
2. STI cabling
3. K.sti/K.si module
Tape unit number xx connected to Requestor xx Port xx ceased to exist while online

Error Type: Tape functional out-of-band
Severity: Error
Description: This message is similar to the previous error message except in the case where the
HSC was using the tape drive to do data transfers when the tape drive went offline.
Field Service Action: Check to see if a breaker has blown. The tape drive may be in testing mode
also, causing the tape drive to go offline.
Possible FRUs:
1. Tape drive

8-93
TROUBLESHOOTING TECHNIQUES

2. Tape formatter

3. STI cable
Tape unit number xx connected to Requestor xx Port xx dropped state clock while online

Error Type: Tape functional out-of-band
Severity: Error
Description: The formatter supplies the state clock over the STI cable. The state bits are encoded
on this state clock waveform such as AVAILABLE and ATTENTION. As long as the K.sti/K..si is
receiving a state clock, the STI cable must still be plugged in, and the formatter must he operating
correctly. Dropping state clock is equivalent to disconnecting the STI cable from the HSC.

Field Service Action: First isolate the problem to the HSC, STI cable, or tape unit. Next, try
replacing or swapping the K.sti/K..si module exhibiting the failure. If the problem is not solved, try
a known good tape unit.
Possible FRUs:
1. STI cable
2. Tape unit
3. K.sti/K..si module
Tape unit number xx connected to Requestor xx Port xx is not asserting available when it should be

Error Type: Tape functional out-of-band
Severity: Error
Description: The formatter is not online and is not asserting its Available signal to the HSC. The
HSC does not detect the Available signal and displays this message on the local console terminal.

Field Service Action: First isolate the problem to either the HSC, the STI cable, or the tape unit.
Next, try replaci.'1g or swapping the K.sti/K..si module exl-...ibiting the failure. If the problem is not
solved, try a known good tape unit.
Possible FRUs:
1. STI cable
2. Tape unit
3. K.sti/K.si module
Tape unit number xx connected to Requestor xx Port xx went available without request

Error Type: Tape functional out-of-band
Severity: Error
Description: When the formatter is online, Available is not normally asserted to the HSC. When
the formatter is online and doing I/O and an Available is asserted, the HSC detects this as an error.
A formatter does not need to send Available unless the K.sti/K.si requests it.

Field Service Action: First isolate the error to the formatter or to the active K.sti/K.si.
Possible FRUs:
1. K.sti/K.si
2. Formatter

8-94
TROUBLESHOOTING TECHNIQUES

3. STI cable
Tape unit number xx connected to Requestor xx Port xx went offline without request

Error Type: Tape functional out-of-band
Severity: Error
Description: The formatter lost contact with one of the tape drives. The HSC detected this loss of
a tape drive and printed this message.

Field Service Action: Check to see if a breaker has blown. The tape drive may be in diagnostic
mode also, causing the tape drive go offline.

Possible FRUs:
1. Tape drive
2. Tape formatter
3. STI cable
TMSCP fatal initialization error-TMSCP functionality not available

Error Type: Tape functional out-of-band
Severity: Error
Description: Something went wrong during initialization with the tape functional code (TFUNCT).
A routine was called up to initialize some part of the functional code, and that part failed to
initialize. Typically, some other message is displayed prior to this message giving more detail on
the error.
Field Service Action: Take action depending on the previous message.
Possible FRUs: Dependent on the previously-displayed error message
TMSCP Server operation limited by insufficient Private memory. Use the SET MAX command to reduce
private memory requirements.

Error Type: Tape functional out-of-band
Severity: Error
Description: This message appears before the message Insufficient private memory remaining
for TMSCP Server and indicates the same problem. Private memory has insufficient space to hold
the necessary structures the TMSCP Server needs as dictated by the number of K.sti/K..si modules
and the number of tape formatters on the HSC.

Field Service Action: Use HSC SETSHO utility to decrease maximum number of tape formatters
for which the HSC should reserve memory structures.
Possible FRUs:
1. M.std2/M.std

2. P.ioj/c
3. Software

8-95
TROUBLESHOOTING TECHNIQUES

TOPOLOGY command failed

Error Type: Tape error
Severity: Error
Description: A TOPOLOGY command was issued and the command failed.
Field Service Action: Check the formatter.
Possible FRUs: Formatter
TTRASH fatal Initialization error

Error Type: Tape functional out-of-band
Severity: Error
Description: This message is similar to the message TMSCP fatal initialization error--TMSCP
functionality not available except the process failing to initialize is TTRASH instead of the tape
functional process (TFUNCT).
Field Service Action: Check for previous error reports displaying a more specific reason for this
error report. If earlier error messages do not exist, reboot HSC using backup HSC software copy.
Possible FRUs:
1. M.std2 module/M.std
2. Software
Unable to position before LEOT

Error Type: Tape error
Severity: Error
Description: The command to position the tape was unable to complete before LEOT was
detected.

Field Service Action: Check the drive.
Possible FRUs: Drive module (Refer to the drive service manual.)
Unclearable Drive Error

Error Type: Tape error
Severity: Error
Description: Issued a clear bit three times and the bit does not clear.
Field Service Action: Check the formatter and drive. Further analysis of tape drive error log may
be necessary.
Possible FRUs:
1. Drive modules (Refer to the drive service manual.)
2. Formatter
3. STI cable set
4. K.sti/K.si module

8-96
TROUBLESHOOTING TECHNIQUES

Unclearable Formatter Error

Error Type: Tape error
Severity: Error
Description: Issued a clear bit three times and the error does not clear.
Field Service Action: Check the formatter
Possible FRUs:
1. Formatter

2. STI cable set
3. K.stilK.si module
Unexpected AVAILABLE signal from ONLINE disk unit xx.

Error Type: Disk functional out-of-band
Severity: Informational
Description: The disk is asserting AVAILABLE while the drive state is ONLINE. This is not an
expected condition.
Field Service Action: Determine why the disk drive is asserting the Available signal.
Possible FRUs: Drive modules (Refer to the drive service manual.)
Unit xx. declared Inoperative because no progress made on Command Reference xxxxx.

Error Type: Disk functional out-of-band
Severity: Error
Description: The HSC Disk Path has made no progress on the host command represented by
the given reference number in an extended time period. This scenario can occur if the drive is
degraded to a point where the Disk Path spends too much time in error recovery and can make no
progress on the host command.
Field Service Action: The HSC was unable to complete error recovery on the drive and took it off
line. Check the drive with diagnostics to determine the nature of the problem.
Possible FRUs: Drive modules
Unknown K.tape error

Error Type: Tape error
Severity: Error
Description: The ER bit was set but was undefined.
Field Service Action: Check the formatter.
Possible FRUs: Formatter

8-97
TROUBLESHOOTING TECHNIQUES

Unrecoverable error on disk unit xx. Drive appears inoperative.
Intervention required.

Error Type: Disk functional out-of-band
Severity: Error
Description: An error log message from the drive caused this message, or the drive may be offline.
The Disk Path has concluded that the drive in unusable.
Field Service Action: Check the error log and drive.
Possible FRUs: Drive modules (Refer to the drive service manual.)
Unsuccessful SEEK initiation, disk unit xxx. DCB addr: xxx

Error Type: Disk functional out-of-band
Severity: Informational
Description: The dialog control block sent the SEEK exchange and the DCB was sent to its error
queue by the K.sdi/K.si. The SEEK may have been rejected, lost, or completed with an error.
Field Service Action: Check drive.
Possible FRUs: Drive modules (Refer to the drive service manual.)
VC closed due to timeout of RTNDAT/CNF from host node xx

Error Type: Disk functional out-of-band
Sev~ri~I: _Informational

Description: The host issued a request over the CI, and the response timed out. .
Field Service Action: Determine if the problem lies in the HSC K.ci module set or the host CI
module.
Possible FRUs:
1. K.ci module set in the HSC
2. CI module set in the host
VC closed with node nn due to disconnect timeout

Error Type: CI-detected out-of-band
Severity: Warning
Description: A second disconnect call for the same connection block has been received by the CI
Manager.
.
Field Service Action: Verify other cluster nodes have not failed or have CI port problems. If
the problem persists, run Offline Test K diagnostic to test K.ci. If no failures exist, verify SET
parameters are valid, use backup copy of the HSC code, and replace FRUs indicated.
Possible FRUs: Host K.ci module set

8-98
TROUBLESHOOTING TECHNIQUES
VC closed with node nn due to request from K.cl

Error Type: CI-detected out-of-band
Severity: Warning
Description: The K.ci microcode has detected both CI paths have gone from good to bad during
polling. More details are found under the description for error message Node nn path n has gone
from good to bad.
Field Service Action: Set error and out band to info. See the descriptions and field service action
for the following error messages:
Node nn path (A or B) has gone from bad to good
Node nn path (A or B) has gone from good to bad
Possible FRUs:
1. K.ci hardware interface in HSC

2. CI cables
3. Host CI hardware
VC closed with node nn due to START received

Error Type: CI-detected out-of-band
Severity: Warning
Description: A start message is received over the CI to an already open Virtual Circuit (VC).
Field Service Action: Check for two HSCs with the same ID (not node address) on the cluster.
This happens when a new HSC is installed on the cluster and is given an existing ID.
Possible FRUs: CI cables
VC closed with node nn due to unexpected disconnect

Error Type: CI-detected out-of-band
Severity: Warning
Description: The HSC receives a DISCONNECf_REQ packet, and the following conditions exist
inside the HSC.
•

A connection is not open.

•

The HSC is not in the DISCONNECf_SENT state. (The DISCONNECT_SENT state indicates
the HSC also sent a DISCONNECT_REQ packet.)

Field Service Action: Verify no other nodes in the cluster failed and caused sending an unexpected
disconnect to the HSC. If failure persists, the K.ci module set may be causing this error. Run
Offline Test K diagnostic to test K.ci. If no failure, verify no duplicate node addresses exist in this
cluster (L0100\LOl18 node address switches).
Possible FRUs: K.pli module

8--99
TROUBLESHOOTING TECHNIQUES

VC open with node nn

Error Type: CI-detected out-of-band
Severity: Informational
Description: A Virtual Circuit (VC) has been established with the given node. The Online lamp
on the HSC Operator Control Panel lights the first time a VC is established to an HSC.
Field Service Action: None is required; this message is for informational purposes only.
Possible FRUs: None
***WARNING*** K.stilK.si microcode too low for large transfers.

Error Type: Tape functional out-of-band
Severity: Warning
Description: The amount of I/O the K.sti/K.si can accommodate is restricted. The code still
attempts to do transfers, but a warning has been issued.
Field Service Action: Update the microcode version level to the proper revision.
Possible FRUs: Change the level of K.sti/K.si microcode to a supported version, or change the
K.sti/K.si with the out-of-date code.
Word rate clock timeout

Error Type: Tape error
Severity: Error
Description: The K.sti/K.si detected the loss of clocks from a drive during a transfer.
Field Service Action: Check the formatter and the cable.
Possible FRUs:
1. Formatter
2. Cable

A-1
HSC INTERNAL CABLING DIAGRAMS

A
HSC INTERNAL CABLING DIAGRAMS
A.1

INTRODUCTION

This appendix contains diagrams of the internal cabling for the HSC70, HSC50 (modified), and HSC50.

A.1.1 HSC70 Internal Cabling
Figure A-I is a diagram of the HSC70 internal cabling.

A-2
HSC INTERNAL CABLING DIAGRAMS

I'WC

P41

DC ON/OFF
SWITCH

P42

DC ON/OFF CABLE
11701231-021

17020203-011

DRIVE

illl,.'

DRIVE

b~--------'
_ _ _ _ _ _ _ _---,

FLOPPY SIGNAL
CABLE,I
11701167-011

rr=============j'
_______

i OPERA TDR CONTROL PANEL
I 7023 : 38 -

~~~~

°:

\;,/

~OCP/CDVER ASSY
f7023132-011

SWITCH

17019680-01 I

II
/1<1'6

. I.T
KI-5 K'-3
P70
,
? I

J7,,0'

li17020197-01 I ,

ii
Ii
i,

i~!II

BACKPLANE

!'7019681-01'NI

IREAR VIEWI

If'"

~~~~~~~~~'

(
.v-,'.

1226092-01

/Ii
I
I

OF OUTLET
DUCT ASSV
Vf"IR
FLOW SENSOR
IPART

i( ()

I
I

I:
I

I I

IIII'll

TB~

'/ i'
il,:

i~BLOWER

AC LINE CORD
11701276-02 OR -031

:i.'7019683 Oil

I
I I.

v ' , '/

----..l

#' ,=", '"
;~~========~;========2' ~ ~~~~~oo,
rw~~Gt<l~~

!I i

i.\!

1
.

IlL

L====~~~==9F==============jp===~~

~~~----=----=~~~T~~~D'-~I~
I L

o liOo'
0
0
0
0
1
0
0
0
0
o
:
2 !
0
0
0
0
o
:i0
I----------------------------<If.----l
o ;:03:
0
0
0
0

POWER CONTROLLER
ASSEMBLY
13024374-01 DR -021

TOP 110 BULKHEAD
ASSV 17023134-011

~=======!~
~E

I--~---==---~--~~--~B~~~

10 0
0
0
o :[00:
il
r-1
·----O---:I~~
I
LJ
0
100
[J
o l~ 2 !
:' ~ BOTTCM I/O BULKHEAD
0
0
0
1---------------=----1f"=-j
I:
ASSY 17023135-011
r-1
i 0
o GCj31
I
0
LJ
C
I

CJ~---ii

"'"

~-----------------------~

" - - 3 PH"SE/Nr.UTRA~/GN[l
A'= POWER CORD
'---------

b---

Figure A-1 (Cont.)

HSC70 Internal Cabling

REL--'Y TO PC ,../f:"
If 701231 -Of

SEJ\jSO~
CX-944A
Sheet 1 of 5

A-3
HSC INTERNAL CABLING DIAGRAMS

WIRE TABLt:.
COLOR

RED
BLACK
WHITE

FROM
Al - +
AI-GND
AI-LOAD

TO
J70- 1
! J70-3
i J70-2

WIRt:.
COLOR

I
I

RED
BLK

YEL
YEL

WHT
WHT

FROM
P4-01
P4-02
P4-03
P4-04
P4-05
P4-06
P4-07
P4-08

;

/\t:Lt..

SI-3
SI-6

I S 1-4
SI-5
i

P4-09
P4- 10

1226092-01 A/F SENSOR
REMARKS
S I GNf\i_
I

SI -1
SI-2

1701202-01 OCP TO ROCKER SWITCH
REMARKS
SIGNAL
i NO CONNECTION
SPARE
NO CONNECTION
KEY I NG PL.Uli
!
!
+5 VOLT
i GND (+5 VOLT)
!
SPARE
NO CONNECTION
I
GND
:
I TERM ENABLE
i
NO CONNECTION
SPARE
i
INIT SWL
I
I
i
INIT L

WIRE TABLE
COLOR I
FROM
YELLOW 1 J40-1
YEL/ORG
J40-2
YEL/BLU
J40-3
J40-4
YEL/GRN
YEL/BLK i J40-5
YEL/VIO
J40-6
J40-7
YEL/GRY
YEL/WHT
J40-8
YEL/RED
J40-9
YEL/BRN I J40- 10
¥-EL/BL-K /GRY .! .J40-! I
YEL/GRN/ORGi J40- 12
YEL/RED/WHT: J40- 13
BLACK
J40-14
I J40- 15
RED

I
I

TO
P3-1
P3-2
P3-4
P3-3
P3-6 1
P3-5 1
P3-8 i
P3-7
P3-10
P3-9 i
P]- 12,P3-ll i
P3-15 ,
P3-14 i
P3-16 i
P3-20
I

1701203-01 OCP CABLE
REMARKS
OCP SIGNAL
STATE LAMP L
POWER LAMP L
LAMP ENA 0 L
TERM ENA L
I
:
LAMP ENA 2 L
LAMP ENA 1 L
LAMP ENA 4 L
i
LAMP EN!'. 3 L
PANEL SWITCH 1 L'
PANEL SWITCH 0 LI

-PANEL- SWITC~

WIRE TABLE
J12-1
YELLOW
J12-2
YELLOW/ORG
YELLOW/BLUE
J12-3
YELLOW/GRN
J12-4
YELLOW/BLACK J12-5
YELLOW/VIOLETIJI2-6
YELLOW/GRAY :JI2-7
YELLOW/WHITE J12-8
YELLOW/RED IJ12-9
YELLOW/BRN 'JI2- 10
YELL/BLK/GRY J12- 11
YELL/GRN/ORG J12-12
YELL/RED/WHT 'JI2-13
J12- 14
BLACK
'J12-16
RED
J12- 19
RED
'JI2-20
RED
J12-21
BLACK
J12-22
BL.ACK
J12-23
BLAr.K
J12-24
BLACK
J12-25
VIOLET
J12-26
VIOLET

P40-01
P40-02
P40-03
P40-04
P40-05
P40-06
P40-07
P40-08
P40-09
P40- 10
P40-11
P40- 12
P40-13
P40-14
D40- 15
P4! -04
P42-04
P41-02
P41-03
P42-02
P42-03
P41 -01
P42-01

PANEL SWITCH 2 L
BDCOKH (INIT LJ
GND
+5V

•

KEY j NG PJ liG {nr.p 1
1701215-01 OCP/BACKPLANE

STATE LAMP L
POWER LAMP L
LAMP ENA 0 L
TERM ENA L
I LAMP ENA 2 L
LAMP ENA 1 L
LAMP ENA 4 L
LAMP ENA 3 L
PANEL SWiTCH II
PANEL SWITCH 0 L
PANEL SWITCH 3 L
PANEL SW ITCH 2 L
BDCOK HI IN; LJ
GROUND
+5 VOLTS
+5 VOLTS
+5 VOLTS
GROUND
GROUND
GROUND
GROUND
+ 12 VOLTS
!
+12 VOLTS

CX-944A
Sheet 2 of 5

Figure A-1 (Cont.)

HSC70 Internal Cabling

A-4
HSC INTERNAL CABLING DIAGRAMS

WIRE TABLE
COLOR
WHITE
WHITE

FROM
K1-3
K1-5

TO
P8-1
PR-?

1701231-01 RELAY TO PC A/F SENSOR
REMARKS
SIGNAL
TRIP
RETURN

WIRE TABLE
TO
P33-4
P33-3
P33-2
P33-1

COLOR
YELLOW
ORANGE
BLUE
BLACK

FROM
S2-2
S2-1
S2-4
S2-3

COLOR
VIOLET
VIOLET
VIOLET
VIOLET
BLK
BLK
BLK
BLK
ORANGE
BLK
BRN
BLK
RED
BLK
VIOLET
BLK
RED
BRN

FROM
,,)13-1
,,)13-2
,,)13-3
,,)13-4
,,)13-5
,,)13-6
,,)13-7
,,)13-8
")13-9
,,)13-10
..) 13- 1 1
,,)13-14
,,)13-13
,,)13-16
,,)13-15
,,)13-17
,,)13-18
,,)13-20

1701231-02 DC ON/OFF

SIGNAL
ON/OFF ( -5.2VI
S2ON/OFF (+5.0VI
SI -

REMARKS

WIRE TABLE

1701266-01 BP TO PS
SIGNAL
REMARKS
:
+12V
+ 12V
+12V
+12V
GND(+12VI
i
GND(+12VI
GND(+12VI
DOUBLE
P31-4
CRIMPED
STANDARD
GND(+12VI
POWER
-5.2V SENSE
P31-6
TWISTED
SUPPLY
PAIR
P31-8
GND ( - 5V SENSE I
P31-10
POWER FAIL L
,,)32 - 1
GND ( +5V SENSE)
TWISTED
+5V SENSE
,,)32-2
PAIR
..)32-3
GND(+12V SENSE)
TWISTED
P"IR
+12V SENSE
,,)32-4
P50-2
GND(+5V SENSE)
OPTIONAL
TWISTED
POWER
PAIR
P50-1
+5V SENSE
SUPPLY
POWER FAIL L
P50-3
TO
P31-1
P31-3
P31-5
P31-7
P31-9
P31-2

WIRE TABLE
COLOR
WHITE
WHITE/BLK
WHITE/BLU
WHITE/ORG
WHITE/RED
WHITE/VIO
WHITE
WHITE/BLK
WHITE/BLU
WHITE/ORG
WHITE/RED
WHITE/VIO
WHITE
WHITE/BLK
WHITE/BLU
WHITE/ORG
WHITE/RED
WHITE/Via

FROM
TO
..) 1 1 - 1 [ ,,)60-20
..) 1 1 -2
,,)60-6
,,)11-3
,,)60-1
..) 1 1 - 4
,,)60-2
,,)11-5
,,)60-3
,,)60-7
,,)11-6
,,)61-20
,,)11-9
,,)61-6
,,)11 - 10
..) 1 1 - 1 1 ,,)61 - 1
,,)11 -12 ,,)61-2
..) 11 - 13
,,)61-3
..) 1 1 - 14 ,,)61-7
..) 1 1 - 17 . ,,)62-20
,,)11 - 18 ,,)62-6
..) 1 1 - 19 ,,)62- 1
..) 1 1 -20 ,,)62-2
,,)62-3
,,)1 I -21
..) 1 1 - 22 ,,)62-7

1701267-01 EIA
BACKPL"NE SiGN"L i
HSC RDY+
1
TERM PRES L
TERM XMTI
TERM XMT+
I
TERM RCV+
I
I
TERM RCVHSC RDY+
AUXI PRES L
AUXI XMTAUXI XMT+
AUXI RCV+
AUXI RCVHSC RDY+
"UX2 PRES L
"UX2 XMT"UX2 XMT+
AUX2 RCV+
AUX2 RCV-

REMARKS

CX-944A
Sheet 3 of 5

Figure A-1 (Cont.)

HSC70 Internal Cabling

A-5
HSC INTERNAL CABLING DIAGRAMS

WIRE TABU::.

1701275-01 A/F SENSOR CABLE
SIGNAL
REMARKS
+12 V
DOUBLE CRIMF
K I-I
LOAD ( -5 V]
K1-6
-5.2V BUSBAR @ BACKPLANE
-5.2V

FROM
P70-]
P35
P70-2
I P70-3

COLOR
VIOLET

VIOLET
ORANGE
ORANGE

WIRE TABLE
FROM
COLOR
GRN/YEL GND STUD
TB 1 - 1 -7
~LUE
TB 1 - 1 -6
eRN

TO
412 •
412 •
1!l2 •

1701276-01 STD POWER SUPPLY
SIGNAL
REMARKS

GND
: ACC
AC

.POWER CONTROLLER4I 2

WIRE TABLE
FROM
COLOR
GRN/YEL GND STUD
TBI-7
eLUE
TBl-6
BROWN

1701276-01 OPT POWER SUPPLY
SIGNAL
REMARKS
GND
• POWER CONTROLLER 41 3
ACC
AC

TO
413 •
413 •
413 •

WIRE TABLE
COLOR
BLUE
BROWN
GREEN
BLACK

FROM
IN MOLDED PLUG
P80-5

TO
P80-1
P80-2
P80-3
P80-4

WIRE TABLE
COLOR
BLUE
BROWN
GREEN
BLACK
BLACK

FROM
IN MOLDED PLUG

TO
P80-1
P80-2

P80-7
P80-6

P80-4
J P80-5 J

~80-3

1701276-02 BLOWER AC LINE CORD
REMARKS
SIGNAL
AC
NEUTRAL
AC
LINE
GROUND
JUMPER
1701276-03 BLOWER AC LINE CORD
REMARKS
SIGNAL
AC
NEUTRAL
AC
LINE
GROUNU
.JUMJ-'t.H

JUMPER

WIRE TABLE
COLOR
VIOLET
VIOLET
VIOLET
VIOLET
BLACK
BLACK
BLACK
ORANGE
BLACK
BROWN

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

COLOR
BLACK
RED
BLACK
VIOLET

FROM
P32-1
P32-2
P32-3
P32-4

COLOR
RED
BLACK
BROWN

FROM
J50-1
J50-2
J50-3

TB 1 -3-5

7019680-01
SIGNAL
REMARKS
DOUBLE
+12 V
CRIMP

TS 1 -3-6

+ 12 V

TB 1 -3-3
TB 1 - 3 - 3
TB1-2-2
TB1-2-1
TB1-1-4

j
I

DOUBLE
CRIMP
DOUBLE
I CRIMP

GND (+12 V]
(+ 12 V]
-5V SENSE!
GND (-5V SENSE)!
POWER FAIL
GND

TWISTED
PAIR

WIRE TABLE

7019681-01
SIGNAL
GROUND
TWISTED PAIR
+5V SENSE
GROUND
TWISTED PAIR
+ 12V SENSE
WIRE TABLE
7019683-01
TO
SIGNAL
REMARKS
TB1-1
+5V SENSE
TWISTED PAIR
TBI-2
GND (+5V SENSE]
TB1-4
PWR FAIL
TO
TB 1 - 1 - 2
TB1-1-1
TB1-3-4
TB 1 - 3 - 1

WIRE TABL.E

TO
TB 1 - 2 - 3
TB 1 -2-2
t.:B~L=U=-E;---+-=:J-=3=3--,-2=-~ TB I - 1 - 3
BLUE
J34-2
I-'B=L:..:..A=C:..:...;K,---+-=-J~33=---=-1_--I TB 1 - 1 - 2
BLACK
J34 - 1
COLOR
YELLOW
ORANGE

FROM
J33 - 4
J33 - 3

7020197-01
SIGNAL
REMARKS
ON/OFF (- 5 . 3V ]
S2ON/OFF (+5VI
DOUBLE CRIMP
SI-

DOUBLE CR I MP
CX-944A
Sheet 4 of 5

Figure A-1 (Cont.)

HSC70 Internal Cabling

A-6
HSC INTERNAL CABLING DIAGRAMS

WIRE TABLE

COLOR
BLUE
BLACK

I FROM
I J51 - 2
I J51 - 1

TO
I
I TBI-3
I TBI-2

COLOR
BLACK
BLUE

I FROM
I P34- 1
Ip34-2

TO
I
I P51 - 1
Ip51-2

7020198-01
SIGNAL
!
I
ION/OFF +5V
I
I 5I

REMARKS

WIRE TABLE

COLOR I FROM
VIOLET IJ35

7020199-01
SIGNAL
I
I
I 5I
ION/OFF ( +5VJ
I

WIRE TABLE

TO
I TB 1-3-2

7020203-01
SIGNAL
I
+12 V
!

REMARKS

REMARKS
CX-944A
Sheet 5 of 5

Figure A-1

HSC70 Internal Cabling

A-7
HSC INTERNAL CABLING DIAGRAMS

A.1.2 HSC50 (Modified) Internal Cabling
Figure A-2 is a diagram of the HSC50 (modified) internal cabling.

A-8
HSC INTERNAL CABLING DIAGRAMS
7.O.'0.8.77.-O.'...,.:1,'lIto.
. . .'II"'"_ _ _ _ _ _ _ _ _-..

~ ~ 1:5 t!t ~N 1

r--------L&O--------------L&O'
DRIVE 1

DRIVE 0

70Z0108-01

/
70z0z004-01"""""'-

FRONT
IULKHIiAD
7428570-01

TUse CONTROL
MODULE
(TUse-XI)

(RSAFI)

r::m:!r ' am
I

701oa78-01.......

7020522-01
70Z0203-01

I:Z;J

~S~T~~~D~AA~D~PO~W~E~R-----t--'
7010880-01
"

SUPPLY ASSEIotILY
(7OZoo33-01 OR -02)

~i TlI-3

iIi)

7010881-01",

e 7 8

'J4

" .lfJ~ --...
'"

3 Z/1

TlI-l

~ Ey~~:~~_/-t
'\.
1

TlOi---"iI
T"O~

R.ot-+-.......~V

Cl CMLES
/1700717-01
1--4X

R"O

.
~_~
'~-,~~~--+=----~~~~~--70-'._8e8---0-1-OR---;r02,.----~----~--~SICMLE'X~
____

:~~

:-Y

(1701278-01)

t1
....

.fl 701088Z-Ot'

/1700051-01)

..t-z--~ 3 - -..
41..1 -

.P TPPS
INTERCONNECT
(70 I oa7S-0I)

Jel CMLE
ASHU.LY
/713140-(1)

POWER CONTROLLER
ASSEMILY
/3OZ4374-01 OR 02)

~SOLE
FED

f'. FIIiAR SHEIlD

3 PHASElNEUTRALlGHD
AC POWER CORD
RELAY TO PC AIF
/1701231-01)

-------------..,/I

SENSOR~I!..-------.....

CXO-207GA
Sheet 1 of G

Figure A-2 (Cont.)

HSC50 (Modified) Internal Cabling

A-9
HSC INTERNAL CABLING DIAGRAMS

WIRE TABLE FOR 7019676-01
SIGNAL
+12V
+12V
GROUND
GROUND
GROUND
GROUND
+SV
+SV
TERM PRESS L
XMTXMT+
RCV+
,£
,.I
DATA SET READY COMMONING STRIP SEE NOTE '"'
ACVWHITE
TERM PRESS L
WHITE
XMTWHITE
XMT+
WHITE
RCV+
WHITE
I
,I
DATA SET READY COMMONING STRIP SEE NOTE '"'
I
RCVWHITE
TUO/1 PRESS L
WHITE
TUO/1 XMTWHITE
TUO/1 XMT+
WHITE
TUO/1 REV+
WHITE
TUO/1 RCV+
WHITE
TU2I3 PRESS L
WHITE
. . _-- ---Wfof1TE"" --- ---j-t1--~ -j40--oZ-= ---------rt1273---xMTJ11-36 J4S-03
TU2I3 XMT+
WHITE
J11-37 J4S-04
TU2I3 RCV+
WHITE
TU2I3 RCVJ11-38 J4S-0S
WHITE
STATE LAMP L
YELLOW J11-4S J40-01
POWER ON l
YELLOW J11-46 J40-02
LAMP 0 L
YELLOW J11-47 J40-03
TERM ENA L
YELLOW J11-48 J40-04
LAMP 2 L
YELLOW J11-49 J40-0S
LAMP 1 L
YELLOW J11-S0 J40-06
LAMP 4 L
J40-07
YELLOW J11-S1
LAMP 3 L
YELLOW J11-S2 J40-08
SWITCH 1 L
YELLOW J11-S3 J40-09
SWITCH 0 L
YELLOW J11-S4 J40-10
SWITCH 3 L
YELLOW J11-SS J40-11
SWITCH 2 L
YELLOW J11-S6 J40-12
BDCOK H (INT L)
YELLOW J11-S7 J40-13
J11-S8 J40-14
GROUND
BLACK
J11-60 J40-1S
+SV
RED
COLOR
VIOLET
ViOLET
BLACK
BLACK
BLACK
BLACK
RED
RED
WHITE
WHITE
WHITE
WHITE

FROM
J11-1
J11-2
J11-3
J11-4
J11-S
J11-6
J11-7
J11-8
J11-12
J11-13
J11-14
J11-1S
J60-20
J11-16
J11-18
J11-19
J11-20
J11-21
J43-20
J11-22
J11-26
J11-27
J11-28
J11-29
J11-30
J11-34

TO
J41-01
J44-01
J41-02
J41-03
J44-02
J44-03
J41-04
J44-04
J60-20
J60-01
J60-02
J60-03
J60-06
J60-07
J43-20
J43-01
J43-02
J43-03
J43-06
J43-07
J42-01
J42-02
J42-03
J42-04
J42-0S
J4S-01

REMARKS

'"' PINS AT J43-06 AND
J60-06 ARE WIRELESS
PINS. THEY ARE TIED
TO J43-20 AND J60-20
BY COMMONING STRIPS.

CXO-2076A
Sheet 2 of 6

Figure A-2 (Cont.)

HSC50 (Modified) Internal Cabling

A-10
HSC INTERNAL CABLING DIAGRAMS

WIRE TABLE FOR 7019677-01
COLOR
VIOLET
BLACK
BLACK
READ
WHITE
WHITE
WHITE
WHITE
WHITE

FROM
P41-1
P41-2
P41-3
P41-4
P42-1
P42-2
P42-3
P42-4
P42-S

YELLOW
YELLOW
YELLOW
YELLOW
YELLOW
YELLOW
YELLOW
YELLOW
YELLOW
YELLOW
YELLOW
YELLOW
YELLOW
BLACK
RED

P40-1
P40-2
P40-3
P40-4
P40-S
P40-S
P40-7
P40-S
P40-9
P40-10
P40-11
P40-12
P40-13
P40-14
P40-1S

COLOR
VIOLET
VIOLET
VIOLET
VIOLET
BLACK
BLACK
BLACK
ORANGE
BLACK
BROWN

FROM
J12-1
J12-2
J12-3
J12-4
J12-S
J12-7
J12-9
J12-11
J12-12
J12-13
J12-1S
J12-17
J12-1S
J12-19
J12-20

TO
P1-1
P1-3
P1-S
·P1-S
P2-F
P2-D
P2-C
P2-J
P2-H
P2-E
P3-1
P3-2
P3-4
P3-3
P3-S
P3-S
P3-S
P3-7
P3-10
P3-9
P3-12
P3-11
P3-1S
P3-14
P3-1S
P3-20

SIGNAL
+12V
GND (+12V)
GND (+5V
+SV
GND
RCVRCV+
XMT+
XMTI

STATE LAMP L
POWER ON L
LAMP 0 L
TERM ENA L
LAMP 2 L
LAMP 1 L
LAMP 4 L
LAMP 3 L
SWITCH 1 L
SWITCH 0 L
SWITCH 3 L
SWITCH 2 L
BDCOKH (INIT L)
GND
+SV

REMARKS
TU POWER
TU POWER
TU POWER
TU POWER
TU SIGNAL
TU SIGNAL
TU SIGNAL
TU SIGNAL
TU SIGNAL
KEYING PLUG (TU SIG)
OCP
OCP
OCP
OCP
OCP
OCP
OCP
OCP
OCP
OCP
OCP
OCP
OCP
OCP
OCP
KEYING PLUG (OCP)

WIRE TABLE FOR 7019679-01

BLACK
RED
BLACK
VIOLET

TO
P31-1
P31-3
P31-S
P31-7
P31-9
P31-2
P31-4
P31-S
P31-S
P31-10
,
J32-1
J32-2
J32-3
J32-4

SIGNAL
+12V
+12V
+12V
+12V
GND +12V
GND +12V
GND +12V
-SV SENSE
GND (-SV SENSE)
POWER FAIL
NO CONNECTION
GND (+SV SENSE)
+SV SENSE
GND +12V SENSE)
+12V SENSE

REMARKS

TWISTED
PAIR
KEYING PLUG
TWISTED
PAIR
TWISTED
PAIR
CXO-207SA
Sheet 3 of S

Figure A-2 (Cont.)

HSC50 (Modified) Internal Cabling

A-11
HSC INTERNAL CABLING DIAGRAMS

WIRE TABLE FOR 7019680-01
COLOR
VIOLET
VIOLET
VIOLET
VIOLET
BLACK
BLACK
BLACK
ORANGE
BLACK
BROWN

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

COLOR
BLACK
RED
BLACK
VIOLET

FROM
P32-1
P32-2
P32-3
P32-4

COLOR

FROM
P4-01
P4-02
P4-03
P4-04
P4-05
P4-06
P4-07

SIGNAL

REMARKS
DOUBLE
CRIMP
DOUBLE
CRIMP
DOUBLE
CRIMP

TB1-3-5

+12V

TB1-3-6

+12V

TB1-3-3

GND (+12V)

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

GND (+12V)
+5V SENSE
GND (-5V SENSE)
POWER FAIL

TWISTED
PAIR

WIRE TABLE FOR 7019681-01
SIGNAL
GROUND
+5V SENSE
GRO
+12V SENSE

TO
TB1-1-2
TB1-1-1
TB1-3-4
TB1-3-1

REMARKS
TWISTED
PAIR
TWISTED
PAIR

WIRE TABLE FOR 7019705-01

£
l

RED
BLACK

YELLOW
YELLOW
_.L

___

---

--1--

-P~08

WHITE
WHITE

P4-09
P4-10

COLOR
YELLOW
ORANGE
BLUE
BLACK

FROM
S2-2
S2-1
S2-4
S2-5

COLOR

RED
BLACK
BROWN

FROM
J13-2
J13-3
J13-4
J13-5

COLOR
RED
BLACK .:
BROWN

FROM
J50-1
J50-2
J50-3

,
,

,
,,
£

01-1
01-2

S1-4
S1-5
-

-- -

--.J,--------f -----

S1-1
S1-2

SIGNAL
NO CONNECTION
NO CONNECTION
+5V
GND (+5V)
NO CONNECTION
GND
TERM ENABLE
NO---CONNECTJON --INIT SWL
INIT L

REMARKS
SPARE
KI: Y IN~ PLUG

SPARE

- --_._-

-SEARl:

WIRE TABLE FOR 7020196-01
SIGNAL
ON/OFF (-S.3V)
S2ON/OFF (+5V)
S1-

TO
P33-4
P33-3
P33-2
P33-1

REMARKS

WIRE TABLE FOR 7019682-01

,l.

,t.

P50-1
P50-2
P50-3

,l.

SIGNAL

+5V SENSE
GND (+5V SENSE)
POWER FAIL

REMARKS
KEYING PLUG
TWISTED
PAIR

WI RE TABLE FOR 7019683-01
TO
TB1-1
TB1-2
TB1-3

SIGNAL
+5V SENSE
GND (+5V SENSE)
POWER FAIL

REMARKS
TWISTED
PAIR
CXO-2076A
Sheet 4 of 6

Figure A-2 (Cont.)

HSC50 (Modified) Internal Cabling

A-12
HSC INTERNAL CABLING DIAGRAMS

WIRE TABLE FOR 7019684-01
COLOR
BLACK
BLACK
BLACK
BLACK
ORANGE
ORANGE
ORANGE
ORANGE

FROM
+V2
+V2
+V2
+V2
-V2
-V2
-V2
-V2

COLOR
YELLOW
ORANGE
BLUE
BLUE
BLACK
BLACK

FROM
J33-4
J33-3
J33-2
J34-2
J33-1
J34-1

COLOR
BLUE
BLACK

FROM
JS-2
JS-1

COLOR
BLACK
BLUE

FROM
P34-1
P34-2

COLOR
RED
BLACK
WHITE

FROM
A1-+
A1-GND
A1-LOAD

SIGNAL
GRN1-SV
GND (-SV
GND I-SV
GND (-SV
-SV
-SV
-SV

TO
TB2-1
TB2-2
TBS-1
TBS-2
TB2-3
TB3-2
TB4-1
TBS-3

REMARKS

-sv

WIRE TABLE FOR 7020197-01
TO
TB1-2-3
TB1-2-2

SIGNAL
ON/OFF (-S.3V)
S2-

TB1-1-3

ON/OFF (+SV)

TB1-1-2

Sl-

REMARKS

WIRE TABLE FOR 7020198-01
TO
TB1-3
TB1-2

SIGNAL
ON/OFF (+SV)
S-

REMARKS

WIRE TABLE FOR 7020199-01
TO
PS1-1
PS1-2

SIGNAL
SON/OFF (+SV\

REMARKS

WIRE TABLE FOR 1228092-01 A/F SENSOR
TO
J70-1
J70-2
J70-3

SIGNAL
J~

REMARKS
)(

WIRE TABLE FOR 1701231-01 RELAY TO PC A/F SENSOR
FROM
Kl-3
K1-S

COLOR
WHITE
WHITE

SIGNAL
TRIP
RETURN

TO
P8-1
P8-2

REMARKS

WIRE TABLE FOR 1701275-01 A/F SENSOR CABLE
FROM
P70-1
P3S
P70-2
P70-3

COLOR
VIOLET
VIOLET
ORANGE
ORANGE

REMARKS
DOUBLE
CRIMP

SIGNAL

K 1-1

+SV

K10G
-S.2V BUSBAR 0 BACKPLANE

LOAD (-SV\
-S.2V

WIRE TABLE FOR 1701276-01 STD POWER SUPPLY
COLOR
GRN/YEL
BLUE
BROWN

FROM
GND STUD
TB1-1-7
TB1-1-G

TO
2"
2"
2"

SIGNAL
GND
ACC
AC

REMARKS
"POWER CONTROLLER' 2
CXO-207GA
Sheet S of G

Figure A-2 (Cont.)

HSC50 (Modified) Internal Cabling

A-13
HSC INTERNAL CABLING DIAGRAMS

WIRE TABLE FOR 1701276-01 OPT POWER SUPPLY
COLOR
GRNlYEL
BLUE
BROWN

FROM
GND STUD
TB1-1-7
TBJ-1-6

SIGNAL
GND
ACC
AC

c 3·

( 3·
c 3·

REMARKS
·POWER CONTROLLER' 3

WIRE TABLE FOR 1701276-02 BLOWER AC LINE CORD
COLOR
BLUE
BROWN
GREEN
BLACK

FROM
IN MOLDED PLUG
P80-5

TO
P80-1
P80-2
P80-3
P80-4

SIGNAL
AC
AC
GND

REMARKS
NEUTRAL
LINE
JUMPER

WIRE TABLE FOR 1701276-03 BLOWER AC LINE CORD
COLOR
BLUE
BROWN
GREEN
BLACK
BLACK

FROM
IN MOLDED PLUG
P80-7
P80-8

TO
P80-1
P80-2
P80-3
P80-4
P80-5

SIGNAL
AC
AC
GND

REMARKS
NEUTRAL
LINE
JUMPER
JUMPER
CXO-2076A
Sheet 6 of 6

Figure A-2

HSC50 (Modified) Internal Cabling

A-14
HSC INTERNAL CABLING DIAGRAMS

A.1.3 HSC50 Internal Cabling
Figure A-3 is a diagram of the HSC50 internal cabling.

A-15
HSC INTERNAL CABLING DIAGRAMS

II---r-'II

~:..:....,...~~~~~?'-----,I

I i,
I

"---rI

'---"Ii:,'.' C¥J
,
I

FRONT

II i

DRivE

\1 :

I TU58-XA

;i
II

III ~

l.1

I I

,,/17020196 O!

~ LJ~~.
l.-

i,'

I'
II

, , 7 4 2 0 : 5 : fl0U'Ht:AD
:'"/0-01
I HE AR I

70196 7 6-01

I
!

c:J1

II BRN B~ "CD

70",,020\4 - 0 1

')4~16N 11~

j'IIll::
I'

70~,,)22-01

II! L I

I: I

c=J. 7

70:9680-01

LlRIVE j1

Iws,,, I

c:J,

II FlRN

RED

7020204 - 0 1 =.7

TU:,8 c;ONTROL

11~~~~~~Bl

0 .) 1 .)3.)4
0p =1 =

01
.)2
O,P2

BI::ZEL ASSY

~~_ I_~ __ I'O~:~=~= _____ ~
~--

7020197-01

12188<'8-00

l i ! i ~~~A~LOW SENSORr--'-_ _ _--,

Ii
JI

7019681-01

7020201 -01

7020199-01

7019686-01 Q."l 02

: - n _ n _ u _ n LED------n-n-u----;:.~;:

7019677-01"]

r
TB2

TB
TB3
TA
TB4

RB
RA

TB5

7019679-01

160 HZI
150HZ I

3 PHASE/NEuTRAL/GROUND
AC POWE'" CORD

POwER CON rHOLU,R AL~'=>EUljL Y
17019122 -001 160 11Z1
OR
17020613-011 ISO HZI
,)1
,)1

..)3 160 HZ,
.)2 150 HZ I

7020206-01

-02

7020205-01
DEC PO\1rER

b=~F========4!::==!J CONTHOl..J:l~? _ _ _

DELAYED
OuTPUT

7020202 - 0_1_ J:

CX-051A
Sheet 1 of 5

Figure A-3 (Cont.)

HSC50 Internal Cabling

A-16
HSC INTERNAL CABLING DIAGRAMS

WIRE TABLE FOR LINt. CORD OF 7019122-00
COLOR
I
BLUE
BLACK
GRN/YEL
BLACK
BROWN

FROM
W

Z
GND
Y

REMARKS

TO
LXI-N
LF 1 -L3
LF 1 -Gf\I['
LF I -L2
LF I -Ll

LINE SIDE

WIRE TABLE FOR 7019676-01
~C~O~L~0~R~:~F~R~0~M~__~~7TO~~-r!~~~------------~S~1~G~N~A~L~--________________-r______ ~R~EMARKS
VIOLET! J l l - j
_.J41-01
+12V
VIOLET, _.JIl-2
i _.J44-01
+12V
BLACK I _.Jll -3
J41 -02
I
GROUND
BLACK
Jll-4
: J41-03
l GROUND
BLACK ' _.J II -5
J44 -02
i GROUND
BLACK
_.J 1 1 -6
_.J44 -03
GROUNO
R;::-D
l JII-7
'J41-04
+5V
RED
! J 1 I -8
• ..)44 -04
I
+5V
WH I TE
_.J 1 1 - 12
J60-20
TERM PRES L
J60-0 I
XMTWH I TE i J 1 1 - I 3

~W~H~JT~E~~I~J~I~I--~1~4~-r-J~6~0~-0~2~--~~X~M~T~+------------_____________________________~Ii

WHJTE
_.J11-15
.J60-03: RCV+
~/==~/=-~J~6~0~-~2~0~~~-.J~6~0~-~0~6--~D~A~T~A~S~E~T~R~E~A~D~Y~C~O~M~M~O~N~IN~G~~S~T~R~I~P~S~E~E~N~O~T~E~.__~I
~W~H~IT~E~-·~J~I~I--~1~6~----.J~6~0=_-0==7--~R~C~V~-~~~--------________________________~Ii
WH I TE
J 1 1 - 18
J43 - 20
TERM PRES L
WHITE
_.JII-19
J43-01
XMTWH I TE
J I 1-20
J43-02
XMT+
i
~\~~H~IT~E~~J~I~I~-~2~1---_;~J~4~3~-~0~3~_;~R~C~V~+~~~~~~~___~~~~~~~~~~~----~
)
/
J4]-20
J43-06
DATA SET READY COMMONING STRIP SEE NOTE •
Y 1-22
_.J43-07
RCVWH! TE
'NHI TF
JII-26
J42-01, TUO/I PRES L
WHITE
JII-27
J42-02
TUO/I XMTWH I TE
_.J I I - 28
J42 - 03
TUOI I XMT +
'NH ITt:.
J 1 1 - 29
J42 - 04
TUOI I RCV +

• PINS AT

'43-06
...J

AND J60-06 ARE
WIRELESS PINS.
THEY ,A.RE T I ED TO
J43-20 MJD J60-20
BY CO~.AMON I NG

STRIP'~.

~W~H-~,~IT~E~~J71~I~-~3~07_~~J~42=--~0~5--~T~U~0~/~I~R~C~V~-~-------------------------------~
4c---4-..::.
4c:::
J -:
5 ,---::0-::1
t-'·~--'.~H...:...:--:IT==E=----.::J--'.1....:.1_-....:::3-::
. TU2/3 PRES L.

WH! TE
J 1 1 - 35
J45 - o2----rr U2 I 3 XMTWHITE
JII-36
_.J45-03; TU2/3 XMT+
WHITE i _.J11-37
_.J45-04
TU2/3 RCV+
WHITE
_.J11-38
J45-05
TU2/3 RCVYELLOW I _.JII -45
J40-01
STATE LAMP L
YELLOW
_.J11-46
J40-02
POWER ON L
YELLOW I _.JII -47
J40-03
LAMP 0 L
YELLOW
_.J I I - 48
J40 - 04
TERM ENA L
YELLOW
JII -49
J40-05
LAMP 2 L
YELLOW
_.JI I -~O
J40-06
LAMP 1 L
YELLOW
_.J11-51
_.J40-07
LAMP 4 L
YELLOW
_.J I 1 -52
J40 - 08
LAMP 3 L
YELLOW
_.J II -53
_.J40-09
SW I TCH I L
YELLOW
_.J I I - 54
_.J40 - 10
SW ITCH 0 L
YELLOW
_.J 1 1 - 55
_.J40 - I 1
SWJ T:';, 3 L
YELLO',:
J I I - 56
_.J40 - 12
SW ITCH 2 L
YELLOW
_.JI I -57
_.J40-13
BDCOK H (INT LI
~B~L=A=C~K~~_.J~~I~I--5~8=--+~_.J-4~O--~14
GROUND
RED

-11 I -60

_.J40-15

+5V

CX-051A
Sheet 2 of 5

Figure A-3 (Cont.)

HSC50 Internal Cabling

A-17
HSC INTERNAL CABLING DIAGRAMS

WIRf:::. TABLE FOR 7019677-01
COLOR
ViOLET
oL,A,CK
BL:\CK
RED
WHITE
WHITE
WHITE
WHITE
WHITE
I

I FROM

' P41 - 1

P41-2

I P41-3

P41-4
i P42-1
I P42-2
: P42 - 3
: P42- 4
I P42-5

(

,
7

YELLOW i P40-1
YELLOW i P40-2
YELLOW I P40-3
·{>-LLOw I P40-4
YELLOW jP40-5
YELLOW I P40 - 6
YELLOW j ?40-7
YELLOW : P40-8
'r'ELLO'yIJ 1 P40 -9
YELLOW I P40 - 10
YELLOW ' P40-11
YELLOW ! P40-12
YELLOW I P40 - 13
BLACK i P40- 14
Rt.D
I P40-15

TO
PI - I
PI -3
PI -6
FI -5
f-'2-F
P2-D
P2-C
P2--.J
P2-H
P2-E
P3- 1
P3-2
P3-4
P3-3
P3-6
P3-5
P3-8
P3-7
P3- 10
P3-9
P3-12
P3- I I
P3-15
P3- 14
P3-16
P3-20

REMARKS
TU
POWER
I TU POWER
GND (+12V)
GND !+5Vl
TU POWER
+5V
TU POWER
GND
TU SIGNAL
RCVTU SIGNAL
RCV+
TU SIGNAL
XMT+
TU SIGNAL.
i XMTTU SIGNAL
KEY!NG PLUG lTU SIGl
I
7
STATE LAMP L
OCP
-OCP
POWE~ ON L
LAMP 0 L
i OCP
OCP
TERM ENA L
OCP
! LAMP 2 L
-' LAMP I L
I OCP
-I LAMP 4 L
OC?
-LAMP 3 L
OCP
OCP
SWITCH I L
CCP
SWITCH 0 L
OCP
SWITCH 3 L
OCP
SWITCH 2 L
OCP
BDCOKH ( INIT Ll
OCP
GND
+5V
OCP
KEYING PLUG (OCP)
SIGNA:""

~12V

WIRE TABLE FOR 7019679-01
COLOR
FROM
VIOLET .J 12 - I
VIOLET -.J12-2
V·IDLET JI-2 -3
VIOLET ! ~112- 4
BLACK : J12-5
BLACK
-.J12-6
BLACK ' -.J12-7
ORANGE -.J12-1 I
BLACK
-.J12- 12
BROWN
-.J12- 13
,7
,
-.J12-16
7
BLACK
-.J 12- 17
RED
-.J12-18
BLACK
-.J12-19
-.J12-20
VIOLET

REMARKS

TO
SIGNAL
+12V
P31-1
P31-3
+12V
' +12V
P31-5
+12V
P31 -7
GND(+12V)
P31-9
GND(+12V)
P31 -2
GND(+12V)
P31 -4
-5V SENSE
P31-6
GND (-5V SENSE I
P31-8
POWER FAIL
P31 - 10
, NO CONNECTION
,
I
7
GND (+5V SENSE)
-.J32- 1
+5V SENSE
-.J32-2
GND 1+12V SENSE)
-.J32-3
-.J32-4
+12V SENSE

TWiSTED
PA.!R
KEYING PLUG
TWISTED
PAIR
TWISTED
PAIR

WIRE TABLE FOR 7019680-01
COLOR
VIOLET
VIOLET
VIOLET
VIOLET
BLACK
BLACK I
BLACK
ORANGE
BLACK
BROWN

FROM
-.J31 - I
J31-3
J31 -5
-.J31 -7
J31 -9
J31 -2
..)31 - 4
-.J31 -6
..)31 - 8
..)31 - 10

COLOR I FROM
: F32-l
~tK
P32-2
FlED
P32-3
BLACK
'VIOLFT ; ?32-4

SIGNAL

TO
TBI -3-5

+ 12 V

TB 1 - 3-6

+12 V

TB 1 -3 - 3
TB I - 3 - 3
TB1 -2-2
, TBI -2- I
TB [- !-4

GND (+12 V)
GND ( + 12 V)
-5V SENSE
GND ( -5V SENSE)
POWER FAIL

REMARKS
DOUBLE
CRIMP
DOUBLE
CRIMP
DOUBLE
CRIMP
TWISTED
PAIR

FOR 7019681 - 01
WIRE TABLE
I
I

I TB 1- 1 -2
, TBI - I -I
I TB 1 - 3- 4
TB I -3- I

S; GN!\L
GROUND
"'5V SENSE
GFlOU!'\D
"'I2v SEf\;SE

REM/\RKS
TWISTED PAIR

TWISTED PAIR
CX-051A

Sheet 3 of 5

Figure A-3 (Cont.)

HSC50 Internal Cabling

A-18
HSC INTERNAL CABLING DIAGRAMS

WIRE TABLE FOR 7019686-02 STO PWR SUPPLY
SIGNAL
GND
Ace
AC

FROM
TO
COLOR
GRN/YELiGND STUD J~; TBI -2-7 J5BLUE
1 TBI -2-6
BROWN
.J5i

-POWER CONTROLLEH J5

WIRE T,A\5LE FOR 7019686-01 ,A\UX PWR SUPPLY
SIGNAL
GND
ACC
AC

!
TO
COlOR 1 FROM
GRf'JlYEL lGND STUD! J 13I TB 1 -7
BLUE
I J 13BROWN
! TB 1 -6
I J 13-

TABLE FOR 7019686-02

W!,~E

-POWER COf'JTROLLER Jt3

PWR SUPPLY

I~UX

(50HZ)

REMARKS

(60HZl

REMA.RKS

SIGNAL
I GND
1 ACC
I AC

TO
COLOR I FROM
GRN/YEL1GND SiLJO i .J5i ...J6I TB 1 -7
BLUE
:! B 1-6
i -..i6BRO.v~'J

('::lOHZl

REMARKS

-POWER CONTROLLER _·5

WiRE TABLE FOR 7019705-01
: FROM

+--+ :P4-01

COLeR

-f-----f- I r4 - C2

IP4-03
iP4-04
BL"Cr<
--+-------f- ! P 4 - 05
YELLCW 1P4-05
':.'t:.LL:::;W 'P4-07
+---+ 'P4-08
Wi-JiTE
i P 4-09
WHI IE
!P4- 10
F{r-iJ

01 - 1

0[-2
i

N I..J
I

S 1 -5

lSI - I
is t-2

REMARKS

~ARI="

::~\~~\~c::c:~ r (J~

r<cY I ~~G

+5 V
GND (+5VI
,I NO CONNECTION
! GND
! TERM ENABLE
,i 1 NO CONNECTION
L INIT SWL
I I ,-..j IT L

LVU

SPARE

! SI-4

SIGNAL
NO COl':i'JEC T ION

TO
(

SPARE

WIRE TABLE FOR 7020196-01
COLGR I FROM
YELLOW LS2-2
ORANGE IS2-1
~Ll.iE
!S2-4
BL..;"CK
I S2-5

SIGNAL
ON/OFF ( -5.3V)
S2ON/OFF (+5V)
SI-

TO
IP33-4
'?33-3
'P33-2
; P33- 1
I

REMARKS

WIRE TABLE FOR 7019682-01
FROM
--i----i- .J13-2
Re.o
.J13-3
I J13-4
BU\Cr<
! J13-5
cHOw:\!

COLOR

SIGNAL

REMARKS
KEYING PLUG

P50-1
P50-2
P50-3

i +5v SENSE
1 GND !~5V SENSEI
I POWER FA I L

TWISTED PAIR

WIRt:. TABLE FOR 7019683-01
COLOR
RED
BLACK
'::RC'.'i:"-J

FROM
.)50 - 1
I J50-2
I J50-3

FRCM
I +V2
! +V2
+1/2
I +V2
-V2
-V2
-V2
-V2

TO
TB 1 - 1
! TBI-2
: iB 1 -4

i
SIGNAL
+5V SENSE
G1"O ( +5V SENSEI I
I
PWR FAIL

REM,A.RKS
TWISTED PAIR

WIRE TABLE FOR 7019684-01
BLACK
BLACK
BLACK
BLACK
ORANGE
ORANGE
ORANGE
IORANGE

TO
TBI - I
I TBI-I
T53- 1
,T53-3
T52-3
TB3-2
T54-1
T55-3

I
!

SlGI'J.'\L
GROUND ( -5VI
GROUND ( -5V)
GROUND ( -5VI
GROUND ( -SVI
-5 V
-5 V
-5 V
-5 v

;

REM,ARKS

WIRE TABLE FOR 7019686-01 STO PWR SUPPLY 160HZ)

COLOR 1 FROM
TO
GRN/YEL I GND STUD J 1213LUE
! T5 I - 2 - 7 J 12 BRN
t TBI-2-6
J12-

SIGNAL
GND
Ace
,AC

REMARKS
-POWER CONTROLLER J 12

CX-051A

Sheet 4 of 5

Figure A-3 (Cont.)

HSC50 Internal Cabling

A-19
HSC INTERNAL CABLING DIAGRAMS

WIRE TABLE FOR 7020197-01
FROM
.J33-4
J33-3
.J33-2

REMARKS

SIGNAL
ON/OFF ( -5.3Vl
S2ON/OFF ( +5Vl

TB 1 - 1 - 2

S I-

T DOUBLE CRIMP

.J33 - 1
.J34 - I

COLOR
BLUE
BLACK

I FROM
I .J51 - 2
1.J51 - 1

COLOR
BLACK
BLUE

COLOR
RED
BLACK
WHITE

TO
I FROM
I
I Al - +
r .J70 - 1
: Al -GI\;D I .J70-3
tAl -LOAD i .J7C-2

J.j4-.t::,

I
I

TO
TS 1 - 2 - 3
TB 1 -2-2
T5 I - 1 - 3

COLOR
Ye.LLOW
ORANGE
BLUE
BLUE
BLACK
BLACK

DOUBLE CRIMP

WIRE TABLE FOR 7020198-01
SIGNAL
TO
T
I
I
ION/OFF +5V
I TBI-3
T
I TBI-2

1 s-

RFMARKS

WIRE TABLE FOR 7020199-01
FROM
I P34-1
IP34-2

TO
I
I P51-1
Ip51 -2

SIGNAL

REMt\RKS

I S-

ION/OFF (+:=iV I

WIRE TABLE FOR 7020200-01
SIGNAL

i
i

,
,

WIRE TABLE FOR 7020201 -01
COLOR I FROM
VIOLET I P70- 1
VIOLET ! P35
ORANGE i P70-2
ORANGE I P70-3

SIGNAL
LOAD I -5 VI
-5 V

WIRE TABLE FOR 7020202-01
COLOR
WHITE

I FROM
! K 1-3

,WHiTE

" XI-§'}

I COLOR

FROM
.J3:J

TO
I P8-1

[ ~,fk2

I
I
I

SIGNAL
TR;P
RETURN

TO
TBI -3-2

SIGNAL
+ 12 V

WIRE TABLE FOR 7020206-01
COLOR I FROM
BLUE
I
BROWN : .J 1 I •
GRN/Y>="L:
P80-7
BLACK
BU\CK
P80-6

TO
P80-1
i P80-2
i P80-3
P80-4
P80-5
t

AC
AC
GROUND
i

REMARKS

(60HZ)

<:;IGNAL

;

REMARKS

WIRE TABLf=' FOR 7020203-01

I VIOLeT

REMl\RKS

DOUBLE CRIMP

+12 V

K I-I
K 1 -6
I TB5-3

REMARKS

{

REMARKS

• POWER CONTROLLER .J 1 1
;
i

.JUMPER
.JUMPER

{

WIRE TABLE FOR 7020206-02 (50HZ)
~QLOR

FROM

I
BLUE
BROWN i.J4 •
GRN/YEL'
RLACK
PRO-5

TO
P80-1
t P80-2
, P80-3
. P80-4

REMARKS

SIGNAL
AC
AC
GROUND

• POWER CONTROLLER .J4
.JUMPER

WIRE IABLE ,OR 70L0522-01
COLOR
RED
BLACK

FROM
I TBI-2

ITB2- 1

TO
.J46-2
i .J46 - 1

SIGNAL
+5 V
GROUND

RE~.~ARKS

T FROM BACK PLAN>="
FROM BACKPLANE

WIRE TABLE FOR LINE CORD OF 7020613-01
COLOR
BROWN
BLACK
BLACKI2
BLUE
GRN/YEL

FROM
X

Y
Z

N
GNn

TO
LF I -PH3
LF 1 -PH2
LF I -PH 1
LF I-N
I F I -GND

SIGNAL
;
;

,
,

REMARKS
i

;

,
,

LINE SIDE
OF LFI.

CX-051A
Sheet 5 of 5

Figure A-3

HSC50 Internal Cabling

B-1
EXCEPTION CODES AND MESSAGES

B
EXCEPTION CODES AND MESSAGES
B.1

OVERVIEW

This appendix describes all known HSC exception (crash) codes caused entirely or in part by software
inconsistencies. For ease of reference, these codes are arranged in numerical order (octal radix). Each
message contains the code nwnber, the meaning of the crash, the facility causing it, an explanation, and
action to be taken.
For additional exception (crash) codes, refer to Chapter 1.
NOTE

The code number but not the text appears on hardcopy printouts.

B.2 CRASH DUMP PRINTOUT
In order to deter~!ne'Yhich exception code c~used a partictI1ar crash, refer to the crash dlllllP printed
on the terminal. The following HSC crash dump example breaks down and describes the various fields.
(The HSCxx refers to an HSC70, HSC50 [modified], or HSC50.)
1

SUBSYSTEM EXCEPTION *V100
HSCxx HSC001
at 17-Nov-1858 00:13:34.20
up
o 00:13:34.20
User Pc: 015066 caused by (20
j 3 lOT
PSW:
140001
DEMON active, PCB addr - 054214
RO-R5:
000005
000000
023004
147602
160020
154752
Kernel SP: 000774
Kernel Stack:
005045
000004
053336
046004
001012
046236
000000
047044
047450
000000
000000
052074
000000
055334
User SP: 154734
User Stack:
002013
104262
140310
000034
035064
102250
004305
000000
000003
000001
000000
002445
000004
000000

000000
000000

KPAR(0-7) :

Booting
INIPIO-I

Booting •••

This line calls out a crash and indicates the HSCxx is at software version number VIOO. The last
field is the assigned node name (set with SET NAME).

This is the mode of the crash; it can be either Kernel or User. This indicates in which processor
mode the crash occurred.

This three-letter mnemonic indicates the crash is a software inconsistency. Any other combination
of letters, such as Non-Existent Memory (NXM) would designate a crash outside the scope of this
appendix.
Hardware exceptions are defined in Appendix D.

B-2
EXCEPTION CODES AND MESSAGES
4

The initial name on this line identifies the process active at the time of the crash. It is valid only
during User-mode crashes. When looking up the crash description, this name can be used as a
cross check.

If the mode notation is Kernel, read the first word of the Kernel Stack for the crash code.

Because the mode notation in this example indicated User, check the User Stack for the crash code
number. This code is always the first word on the stack (in this case 002013)'''-YA:&E..-

e, - \\

The crash codes are listed numerically in this appendix (Section B.5). Consult them for explanations
and suggested action to be taken.

B.3 SINI-E ERROR PRINTOUT
The following SINI-E error example appears immediately upon reboot after a subsystem exception.
Information contained in this error message is a condensation of the crash dump.
SINI-E
7
8

Seq 1. at 17-Nov-18S8 00:00:02.00
Software inconsistency
Process DEMON
PC 000002
PSW 1400
Stack dump: 002013 104262 140310

This line defines the ca1Jse of the crash.

This and the following three lines duplicate the applicable information in the crash dump.

In each of the exception descriptions in this appendix, FACILITY indicates the process(es) running at
the time the crash occurred. The first name listed is the major process. The second is the module of
the process that generated the exception. This may be a subprocess of the main pr~ess or simply a
different code module.
A large number of these messages request submission of an Software Performance Report (SPR). This
process is described in the following section.

B.4 SOFTWARE PERFORMANCE REPORT (SPR) SUBMISSION
Several of the exception messages listed in this appendix suggest an SPR be submitted with a copy of
the crash dump. Before submitting the SPR, contact the Customer Support Center to see if additional
information is needed. An SPR should be submitted only after other possibilities (such as hardwarerelated problems) have been eliminated.
The customer will contact the local field service office or the Customer Support Center if a crash dump
appears with one of the exception messages described in this appendix. The HSC User Guide (AAGMEAA-TK) gives the customer a short explanation about the exception condition. This appendix
shows the same messages, but provides more detailed information needed to analyze the crash.
In many cases, the HSC User Guide tells the customer to submit an SPR.
In some cases, not all of the necessary information which must accompany the SPR is contained in the
crash dump (the message printed on the console when the HSC detects an exception). This appendix
lists the additional information that must be gathered after the HSC has printed its crash dump message.

After this additional information is known, the Customer Support Center may be able to provide
telephone assistance. Then, if an SPR is necessary, it must include all the information listed for the
specific exception code.

B-3
EXCEPTION CODES AND MESSAGES

Normally, HSC parameters are set to allow an HSC reboot after an exception occurs. If similar
exceptions occur, it may be necessary to change the HSC parameters to enter OOT after the crash
dump. OOT allows the gathering of additional information.
CAUTION

When an HSC is set to enter ODT, the HSC does not reboot without manual intervention. The
HSCODT parameter should be set only as instructed by the Customer Support Center.
To force the HSC into ODT after a crash dump message is printed, use the SETSHO command SET
ODT DUMP_BPT. Mter the next exception occurs, the exception message prints out and an ac;terisk
(*) prompt is displayed. The asterisk indicates that OOT is waiting for a command. Contact the
Customer Support Center for further instructions. If the customer requires immediate use of the HSC,
the HSC may be rebooted using the Init switch on the OCP, but information necessary for the SPR will
be lost. Include with the SPR the crash dump message and any other hardcopy information needed.
Mter two or three similar exception messages occur, an SPR should be submitted. Look up the
exception message in this appendix. If a data structure (for instance, HMB or PCB) should be included
with the SPR, set the OOT parameter, which causes the HSC to enter OOT after an exception. IT data
structures are not requested in the applicable exception code, do not enter OOT.
The following steps describe how to set the OOT parameter.
1. To get the HSC command prompt, enter ICTRUVL
2. At the HSC> prompt, type RUN SETSHOW IRETURNL
3. At the SETSHO> prompt, type SET ODT DUMP_BPT IRETURNL
4. To exit SETSHO, type EXIT I RETURN I.
The system displays the following information:
SETSHOW-Q Rebooting HSC; Y to continue, CTRL/Y to abort:?

5. Answer the question with Y IRETURN!.
The following is a sa..tnple session showing a typical display of the previous steps.
HSC> RUN SETSHOW
SETSHO> SET ODT DUMP BPT
SETSHO> EXIT
SETSHOW-Q Rebooting HSC; Y to continue, CTRL/Y to abort:? Y

The HSC then reboots with the new parameter OOT OUMP_BPT set. When the next exception occurs,
the HSC prints the exception message, followed by an asterisk (*) prompt. Instruct the customer to call
field service or the Customer Support Center when the next crash occurs.
When another crash does occur, check the appropriate exception code in this appendix for information
needed to analyze the crash. Include all the requested information with the SPR.
Oata structures needed with the SPR must be formatted. These data structures are addressed by a
register or the contents of another structure's field. To format the necessary data structure(s), substitute
the x in Table B-1 with the pointer from the specified register or location. Substitute only the x and

B-4
EXCEPTION CODES AND MESSAGES

type the rest of the line exactly as it appears in the table, except for the infonnation in parentheses.
The nwnber of equal (=) signs designates the data structure memory.

= indicates Program memory
== indicates Control memory
=== indicates Data memory
Table B-1

Obtaining Data Structure Information

Data
Structure
Needed

Type At * Prompt

x==CB$

Counter

x=C (and) x==C.

DCB

x==DC$DISK (or) x==DC$TAPE (if Tape Path problem)

DDCB

x=DD$

FRB

x==F$

HCB

x=HC$

liMB

x= =HM$ (command packet)
x= =HM$CPY (BACKUP)
x= =HM$DATA (with BMBs)
x==HM$QUIET (diagnostic)
x= =HM$XFR (used while work is outstanding)
x==HM$VC (used to alter VC state)

K Control Area

x==KG$

PCB

x=z.

SLCB

x=SL$

TDCB

x=TD.

TFCB

x=TF.

TICB

x=TT$

XFRB

x==X.

After the information is complete, the customer should fill out the SPR and submit it, together with all
hardcopy, as instructed on the SPR fonn.

8-5
EXCEPTION CODES AND MESSAGES

8.5 EXCEPTION MESSAGES
This section contains the numerically listed crash codes and their meaning, the facility, an explanation,
and the action to be laken.
001040,

Set Timer operation to Timer with address of 0

FACILITY: EXEC, EXEC
Explanation: This software inconsistency should not appear under normal circumstances. The
SETTM$ System Service was called with a queue head address of o. The process specified as active
is the offender.
Action: Submit an SPR with a dump.
001042, Tlme-of-Day overflowed
FACILITY: EXEC, EXEC
Explanation: During update of current time of day, the executive detected an overflow. This can
happen If a node on the CI sets an invalid time to the HSC.
Action: Examine previous console printouts to verify accurate date and time fields. If accurate,
submit an SPR with the console crash report. If inaccurate, set the HSC outband error level to INFO.
Then verify console report of date and time set by a host node on the next HSC reboot. If a host
node problem is not indicated, escalate the problem to field service support.
001043,

Power failure

FACILITY: EXEC, EXEC
ExpJanatlon:After apow-er fa~~urein4ica-tlQn GA the P~iec, CRONIC watts f-ive-seconds for power to
diminish fully enough to stop the processor. If the processor is still operating five seconds after a
power failure indication, CRONIC concludes that the powerfail indication was invalid.
Action: Verify the input power and dc voltages are correct. If so and the problem persists, notify
field service support.
001201,

Process on Recoverable List not Hibernating

FACILITY: EXEC, EXEC LOAD
Explanation: When requested to load a utility or diagnostic, the Loader first examined the
Recoverable Memory List (RML) of cached programs to determine whether a program might be
loaded from memory instead of from the load device. When the program was Indeed found on the
RML, its state was not Hibernate State. This software Inconsistency should not be seen under normal
circumstances. R3 points to PCB for process to restart.
Action: Submit an SPR with a dump, noting previous activity with the program requested.
001202, Memory extent encroaches defined area
FACILITY: EXEC, EXECLOAD
Explanation: The process to be loaded allocated the required memory for the additional buffer
space specified on the Loadable File Header (LFHEADER) directive. When the additional memory
was allocated and mapped to the process, it had encroached upon the loaded area. This software
Inconsistency shoUld not appear under normal circumstances. RO points to an Extended Function
Request Block (XFRB) for loading the image. R4 points to a Canonical File Header (CH$).
Action: Submit an SPR with a dump.

B-6
EXCEPTION CODES AND MESSAGES

001203, No code parent process loaded
FACILITY: EXEC, EXECLOAD
Explanation: When a process was loaded, Its Process Control Block (PCB) specified It should execute
and share code associated with another process. When attempting to locate the code parent, the
loader found the parent was not loaded. This software inconsistency should not appear under normal
circumstances. R2 equals Process Number of code parent. R3 points to the code child's PCB.
Action: Submit an SPR with a dump.
001204, Insufficient kernel pool
FACILITY: EXEC, EXECLOAD
Explanation: When attempting to allocate either a Process Control Block (Z.) (PCB) or an Address
Descriptor (A.) structure for a new process from kernel pool, kernel pool was Inadequate to support
the additional structures.
Action: Submit an SPR with a dump.
001205, FAO overrun
FACILITY: EXEC, EXEC LOAD
Explanation: When formatting a module version mismatch message, the string returned from
FAO was too large for the buffer. This software Inconsistency should not appear under normal
circumstances.
Action: Submit an SPR with a dump. If possible, send a copy of the load medium.
001401,

Performed receive when already busy with request

FACILITY: EXEC, EXECRDWR
Explanation: The READ$IWRITE$ service is single-threaded, handling only one request at a time. The
service, while in its exception routine, was already busy with one request while a RCV$P operation
was performed.
Action: Submit an SPR with a dump.
001402,

Requested driver not loaded

FACILITY: EXEC, EXECRDWR
Explanation: A process within the HSC specified a READ$ or WRITE$ operation with a Device Control
Block (DDCB) for a device not configured on that model. For example, a program specified a transfer
for a TU58 on an HSC70 model. Bec~use the device is not configured on the system, the driver Is
not loaded. R3 points to an Extended Function Request Block (XFRB). R4 points to a DDCB. R5
equals CSR for device. The process listed as active may be the READ$IWRITE$ service, and not the
process that performed the offending request.
Action: Submit an SPR with a dump, describing activity on the HSC at the time of the exception.
001403, Invalid DDCB specified
FACILITY: EXEC, EXECRDWR
Explanation: A request to the READ$/wRITE$ service specified a Device Control Block (DDCB) that
was Invalid (or specified an Invalid device type in the DD$TYPE field). R3 points to an XFRB. R4
points to DDCB. R5 equals CSR for device. The process listed as active may be the READ$/WRITE$
service, and not the process which performed the offending request.
Action: Submit an SPR with a dump, describing activity on the HSC at the time of the exception.

B-7
EXCEPTION CODES AND MESSAGES

001S01,

Software inconsistency-motor not running

FACiliTY: EXEC, EXECRX33

Explanation: The motor was not running when the Motor Shutdown Timer expired.
Action: Submit an SPR with a crash dump.
001S02,

Software inconsistency-non-RX33 command requested

FACILITY: EXEC, EXECRX33
Explanation: R4 pOints to Device Control Block (DDCB). RS points to an XFRB. An XFRB (CRONIC
transfer request) was received by the RX33 driver, but specified a DDCB for a non-RX33 device.
Action: Submit an SPR with a crash dump.
001S03, Software inconsistency-invalid unit number
FACILITY: EXEC, EXECRX33
Explanation: RS points to XFRB. The Device Control Block (DDCB) specified an RX33 device, but the
unit requested was not 0 or 1. RS points to XFRB.
Action: Submit an SPR with a crash dump.
001S04,

Software inconsistency-zero byte count transfer

FACILITY: EXEC, EXECRX33
Explanation: A transfer was requested with a zero byte count. R2 equals the byte count. RS points
to an XFRB.
Action: Submit an SPR with the crash dump.
001S0S,

Software inconsistency-invalid byte count

FACILITY: EXEC, EXECRX33
Explanation: A transfer was requested with a byte count that was not a multiple of S12 (sector size).
R2 equals byte count and RS points to an Extended Function Request Block (XFRB).
Action: Submit an SPR with a crash dump.
001S06,

Software inconsistency-invalid internal byte count

FACILITY: EXEC, EXECRX33
Explanation: Remaining byte count of a partially completed transfer was not a multiple of S12 (sector
size). The original (requested) byte count was a multiple of S12. R2 equals byte count and RS points
to an Extended Function Request Block (XFRB).
Action: Submit an SPR with a crash dump.
001S07,

Software/hardware inconsistency-RX33 hardware registers are incorrect

FACILITY: EXEC, EXECRX33
Explanation: RX33 hardware signaled successful completion of an 1/0 operation, but the hardware
registers (current sector, current track, or memory address register) did not contain the expected
values.
Action: If the problem persists, submit an SPR with crash dumps. The most probable candidates are
M.std2 and the RX33 drives.

B-8
EXCEPTION CODES AND MESSAGES

001510,

Software inconsistency-invalid head select

FACILITY: EXEC, EXECRX33
Explanation: Software attempted to select a head other than 0 or 1. RO equals head select.
Action: Submit an SPR with a crash dump.
001511,

Software inconsistency-memory management

FACILITY: EXEC, EXECRX33
Explanation: Relocation is not enabled in the memory management hardware. Bit 0 not set in MMRO.
Action: Submit an SPR with a crash dump.
001512,

Software inconsistency-invalid virtual address

FACILITY: EXEC, EXECRX33
Explanation: The virtual address passed in the XFRB is not in page 4. R5 points to an Extended
Function Request Block (XFRB).
Action: Submit an SPR with a crash dump.
001513,

Software/hardware inconsistency-unexpect~d interrupt from RX33

FACILITY: EXEC, EXECRX33
Explanation: An unexpected interrupt was received from the RX33 controller. This condition Is not
detected until a command is about to be issued (i.e., the crash does not happen when the Interrupt
is detected).
Action: If the problem persists, submit an SPR with crash dumps. Further testing of the subsystem
(load device area) may be necessary.
001514,

Software inconsistency-invalid internal unit number

FACILITY: EXEC, EXECRX33
Explanation: The unit number index value is not 0 or 2. This unit number index value Is contained in
R4.
Action: Submit an SPR with a crash dump.
001515,

Software/hardware inconsistency-Non-Existent Memory (NXM)

FACILITY: EXEC, EXECRX33
Explanation: RX33 controller returned an NXM error.
Action: Further testing of the HSC subsystem (load device area) may be necessary. If the problem
persists, submit an SPR with crash dumps.
001601,

TYPE$ crosses page boundary

FACILITY: EXEC, EXECTT
Explanation: A process requested a TYPE$ System Service (or an ACPT$ Service with a prompt)
specifying a buffer that crosses a memory management page boundary. This Is a restriction of the
driver. RO equals the size of print string. R1 points to a String Buffer. R4 points to a Device Control
Block (DDCB). R5 points to an Extended Function Request Block (XFRB).
Action: Submit an SPR with a dump. Describe the activity at the time of the exception.

8-9
EXCEPTION CODES AND MESSAGES

001602,

ACPT$ crosses page boundary

FACILITY: EXEC, EXECTT

Explanation: A process requested an ACPT$ System Service specifying a buffer that crosses a
memory management page boundary. This is a iestiictioii of the driver. R4 points to a Device
Control Block (TICB). R5 points to an Extended Function Request Block (XFRB).
Action: Submit an SPR with a dump. Describe the activity at the time of the exception.
001603,

PCB not found on run queue

FACILITY: EXEC, EXECTI
Explanation: When a process attached to a terminal is excepted by a keyboard command, the
exception manager of terminal service first performs an EXCPT$ on the terminal service and load
device driver. To prevent the attached process from running while the drivers potentially run down
any activity, the Process Control Block (PCB) for the active process is removed from the run queue.
When searching the run queue specified in the Z.RUNQ field of the PCB, the PCB itself was not
found. This is a software inconsistency. R4 points to the attached PCB.
Action: Submit an SPR with a dump.
001701,

READ$ or WRITE$ crossed page boundary

FACILITY: EXEC, EXECTU58
Explanation: A request to the TU58 driver specified a buffer that crossed a memory management
page boundary. This is a restriction of the driver. The process listed as active may be the
READ$/WRITE$ service and not the process that initiated the offending request.
Action: Submit an SPR with a dump. Describe the activity at the time of the exception.
002001,

Exception routine invoked for unknown reason

FACILITY: DEMON
Explanation: DEMON's exception routine was activated, but not for /CTRUV! , /CTRucl , or a diagnostic
timeout. A software problem is the most likely cause of this crash.
Action: Submit an SPR with the crash dump. If a certain sequence of HSC operations induced this
crash, include a description of that sequence.
002002,

Insufficient free memory to allocate a Program Stack

FACILITY: DEMON
Explanation: When DEMON was initialized, it could not allocate enough free Program memory for use
as a stack. A failing memory module is the most likely cause of the problem.
Action: If no hardware problem is found, submit an SPR and the crash dump. If a certain sequence
of operations causes this crash, include a description of that sequence.
002003,

DEMON was initiated when there was no diagnostic to run

FACILITY: DEMON
Explanation: DEMON did a receive on its work queue and received a nondiagnostic request. A
software problem is the most probable cause of this crash.
Action: Submit an SPR and the crash dump. If a certain sequence of HSC operations induced this
crash, include a description of that sequence.

8-10
EXCEPTION CODES AND MESSAGES
002004,

Failure in periodic Control or Data memory test

FACILITY: DEMON, PRMEMY
Explanation: One of the periodic Control or Data memory interface tests detected a failure. Failures
in these tests are fatal, and the HSC must reboot after displaying a message describing the failure.
Action: A failing P.ioj/c module is the most probable cause of this crash. Further testing of the HSC
memory and P.ioj/c may be necessary.
002005,

Failure in periodic K.sdi, K.sti, or K.si test

FACILITY: DEMON, PRKSDI, PRKSTI
Explanation: The periodic K.sdi/K.si test or the periodic K.sti/K.si test detected a failure. Failures in
either test are fatal, and the HSC must reboot after displaying a message which describes the type of
error and the requestor number of the failed module.
Action: A failing K.sdi, K.sti, or K.si module is the most probable cause of this crash. The requestor
number of the probable failing module is displayed in the error message preceding the crash. Further
testing of HSC data channels and HSC internal buses may be necessary.
002006, ILDISK received illegal queue address
FACILITY: DEMON, ILDISK
Explanation: ILDISK requested exclusive access to the Drive State Area. The Acquire operation
should return the Control memory address of the Attention/Available Service Queue for the specified
drive; the address returned was 0, an illegal address for a queue. A software problem Is the most
likely cause of this crash.
Action: Submit an SPR and the crash dump. If a certain sequence of HSC operations Induced this
crash, Include a description of that sequence. Also note if the problem occurs only when a particular
disk drive is tested.
002007,

ILDISK received illegal buffer descriptor

FACILITY: DEMON, ILDISK
Explanation: ILDISK received a buffer descriptor from the free buffer queue. A consistency check on
the buffer descriptor failed because the descriptor indicated the buffer was not In the HSC's buffer
memory. A software problem is the most likely cause of this crash.
Action: Submit an SPR which includes the crash dump information. If a certain sequence of HSC
operations induced this crash, include a description of that sequence. Also note If the problem
occurs only when a particular disk drive is tested.
002010,

ILDISK detected inconsistency in exception routine

FACILITY: DEMON, ILDISK
Explanation: ILDISK's internal flags indicated exclusive ownership of the Drive State Area, but the
address of the K.sdi/K.si Control Area was not available. When ILDISK has exclusive ownership
of the Drive State Area, the address of the K.sdilK.si Control Area should always be available. A
software problem is the most likely cause of this crash.
Action: Submit an SPR and the crash dump. If a certain sequence of HSC operations Induced this
crash, include a description of that sequence. Also note if the problem occurs only when a particular
disk drive is tested.

8-11
EXCEPTION CODES AND MESSAGES

002011,

An ILEXER disk 1/0 request failed to complete

FACILITY: DEMON, IlEXER
Explanation: ILEXER attempted to abort all outstanding disk 1/0 requests. After waiting two minutes,
the program found one or more 1/0 requests incomplete. The HSC crashed and rebooted because
ILEXER cannot exit with a request outstanding. A faulty disk drive is the most likely cause of this
problem.
Action: Submit an SPR and the crash dump. If a certain sequence of HSC operations Induced this
crash, Include a description of that sequence. Also note if the problem occurs only when a particular
disk drive is tested. Further testing of suspect disk and associated requestor{s) may be necessary.
002012, An ILEXER tape I/O request failed to complete
FACILITY: DEMON, ILEXER
Explanation: ILEXER attempted to abort all outstanding tape 1/0 requests. After waiting two minutes,
the program found one or more 1/0 requests incomplete. The HSC is crashed and rebooted because
ILEXER cannot exit with a request still outstanding. A faulty tape drive or formatter is the most likely
cause of this problem. This crash also could be caused by the K.sti/K.si clocks stopping due to a
hardware error (such as an Instruction Parity error).
Action: Submit an SPR and the crash dump. If a certain sequence of HSC operations induced
this crash, include a description of that sequence. Also note if the problem occurs only when a
particular tape drive or formatter is tested. Further testing of suspect tape subsystem and associated
requestor{s) may be necessary.
002013, ILTAPE was supplied an illegal requestor number
FACILITY: DEMON, ILTAPE
Explanation: ILTAPE was automatically initiated to test a particular formatter. One of the parameters
supplied to ILTAPE is the requestor number of the K.sti/K.sl connected to the formatter. ILTAPE
checked the specified requestor and found it was not a K.stilK.si. A software problem Is the most
likely cause of this crash.
Action: Submit an SPR and the crash dump. Also include a summary of any tape error messages
immediately preceding the crash. If a certain sequence of HSC operations induced this crash, include
a description of that sequence. Also note if the problem occurs only when a particular tape drive or
formatter Is used.
002014, ILTAPE time~-out waiting for Drive State Area
FACILITY: DEMON,ILTAPE
Explanation: In order to test a tape formatter, ILTAPE must acquire exclusive access to the Drive
State Area for that formatter. When ILTAPE requests exclusive access to a Drive State Area, the
request should complete within 60 seconds. Failure to complete indicates a problem with the Tape
Server.
Action: Submit an SPR and the crash dump. Also include a summary of any tape error messages
immediately preceding the crash. If a certain sequence of HSC operations Induced this crash, include
a description of that sequence. Also note if the problem occurs only when a particular tape drive or
formatter Is used.

8-12
EXCEPTION CODES AND MESSAGES

002015, ILTAPE detected inconsistency after a command failure
FACILITY: DEMON, ILTAPE
Explanation: ILTAPE issued a command to the HSC tape diagnostic interface, but the command
failed. In the process of preparing an error message, ILTAPE found the command Opcode was an
Illegal or unknown value. A software problem is the most likely cause of this crash.
Action: Submit an SPR and the crash dump information. Also include a summary of any tape error
messages immediately preceding the crash. If a certain sequence of HSC operations Induced this
crash, Include a description of that sequence. Also note if the problem occurs only when a particular
tape drive or formatter is used.
002016, ILTAPE detected inconsistency while restoring a TACB
FACILITY: DEMON, ILTAPE
Explanation: ILTAPE maintains a table of available Tape Access Control Blocks (TACBs). When a
particular TACB is in use by the program, the associated table entry Is zeroed. When finished with
a TACS, ILTAPE stores the address of that TACB into one of the table entries which contains a zero.
While trying to return a TACB to the table, ILTAPE discovered all table entries are nonzero, Implying
no TACBs were in use. A software problem is the most probable cause of this crash.
Action: Submit an SPR and the crash dump. Also include a summary of any tape error messages
Immediately preceding the crash. If a certain sequence of HSC operations induced this crash, Include
a description of that sequence. Also note If the problem occurs only when a particular tape drive or
formatter is used.
002017,

ILTAPE detected inconsistency in exception routine

FACILITY: DEMON, ILTAPE
Explanation: ILTAPE's internal flags Indicated exclusive ownership of the Drive State Area, but the
address of the K.sdi/K.si Control Area was not available. When ILTAPE has exclusive ownership
of the Drive State Area, the address of the K.stilK.si Control Area shOUld always be available. A
software problem is the most likely cause of this crash.
Action: Submit an SPR which includes the crash dump information. If a certain sequence of HSC
operations induced this crash, include a description of that sequence. Also note If the problem
occurs only when a particular tape drive is tested.
003001,

Illegal format type speCified

FACILITY: CERF
Explanation: An Illegal format type was specified In an error message to CERF. R4 equals format
type.
Action: Submit an SPR with a dump.
003002,

Output length too long

FACILITY: CERF
Explanation: When processing an MSCP error message, the FAO output of the text string was too
long for CERF's buffer. R1 equalS the number of bytes output.
Action: Submit an SPR with a dump.

8-13
EXCEPTION CODES AND MESSAGES

003003,

Output length too long

FACILITY: CERF

Explanation: When processing an out-of-band message, the FAO output of the text string was too
!ong for CERF's buffer. R1 equals the number of bytes output.
Action: Submit an SPR with a dump.
004001,

No structure to ONLINE disk to connection

FACILITY: DISK, MSCX
Explanation: When an MSCP ONLINE command was issued to bring a disk online to a connection,
there was no structure to record the necessary information. Since the initialization code allocates
enough structures to bring every disk online to every connection, this crash indicates either memory
corruption or mismanagement of the free pool for this structure.
Action: Submit an SPR with the crash dump. Specify the number of hosts In the cluster.
004002,

BMB reserved but not found

FACILITY: DISK, many
Explanation: A Big Message Buffer (BMB) was reserved via a system function but not found when
the table of BMBs was searched. This indicates memory corruption or mismanagement of the BMB
pool.
Action: Submit an SPR with the crash dump. Specify which process was running.
004003,

DUCB address 0 in K Control Area

FA-C-I-L-I-TY: -DISK, SOl
Explanation: A disk attention condition sent a Control Area to a disk subprocess. The subprocess
found a zero in the location which should have contained the DUCB address. This indicates an
Invalid structure address was passed to the process (possibly due to memory corruption), the
structure was corrupted. or it was not initialized properly.
Action: Submit an SPR with the crash dump.
004004,

Invalid action byte in Connection Block (CB)

FACILITY: DISK, SDI
Explanation: The subprocess within the Disk Path that processes requests from the CI Manager
received a Connection Block (CB) with an invalid action byte. This Indicates an invalid structure was
passed to the process, the structure was passed at the improper time, or that memory was corrupted.
Action: Submit an SPR with the crash dump. Note the contents of User register 2 in the crash dump.
004005,

Datagram received from a connection

FACILITY: DISK, MSCP
Explanation: The main MSCP command server process received a nonsequenced message from
some connection. This may indicate memory corruption or improper message reception. It also may
indicate an improper structure was passed to the process. Host software may have improperly sent
such a message.
Action: Submit an SPR with the crash dump. Note all levels of host software running in the cluster.

8-14
EXCEPTION CODES AND MESSAGES

004006, MSCP message size exceeded maximum
FACILITY: DISK, MSCP
Explanation: The main MSCP command server process received a sequenced message with a
length greater than the MSCP 36-byte maximum from some connection. This may Indicate memory
corruption or Improper message reception. It also may Indicate an Improper structure was passed to
the process. Host software may have improperly sent such a message.
Action: Submit an SPR with the crash dump. Note all levels of host software running In the cluster.
004007, Invalid error signaled by K.ci
FACILITY: DISK, MSCP
Explanation: An MSCP command packet with invalid error bits set was received by the main MSCP
command server from the K.ci. This may indicate memory corruption or Improper message reception.
It also may indicate an improper structure was passed to the process. Host software may have sent
an improper message.
Action: Submit an SPR with the crash dump. Note all levels of host software running In the cluster
and the revision level of the K.ci microcode.
004010,

Server queue on work queue with no items

FACILITY: DISK, many
Explanation: The main disk process received a subprocess work queue with no items from the main
work queue. This indicates either memory corruption or Improper manipulation of Items on the
subprocess work queue. An invalid structure may have been queued to the main work queue.
Action: Submit an SPR with the crash dump. Note the current process running.
004011, Invalid module number in subprocess work queue
FACILITY: DISK, many
Explanation: The main disk process received a subprocess work queue containing an Invalid module
number. This indicates memory corruption or an invalid structure was queued to the main work
queue.
Action: Submit an SPR with the crash dump. Note the process currently running.
004012,

SLCB not available when needed

FACILITY: DISK, SDI
Explanation: A Short Lifetime Control Block (SLCB) was needed by the Disk Path but one was not
available. Because many processes and subprocesses require SLCBs, this Is unlikely except under
extreme load circumstances. The number of SLCBs allocated by default should be sufficient to avoid
this crash.
Action: Submit an SPR with the crash dump. Note the configuration of the HSC and the number of
disk and tape drives online at the time of the crash.
004013,

State change to ONLINE requested via gatekeeper

FACILITY: DISK, SOl
Explanation: The state change processor within the sequential command gatekeeper received a Disk
Unit Control Block (OUCB) extension with the current state set to ONLINE. This crash Indicates an
Improper use of the state change mechanism.
Action: Submit an SPR with the crash dump.

8-15
EXCEPTION CODES AND MESSAGES

004014,

Inconsistent drive state detected

FACILITY: DISK, SOl

Explanation: The state change processor within the seqoential command gatekeeper received a
Disk Unit Control Block (DUCB) extension different than the current state. This crash Indicates an
Improper use of the state change mechanism.
Action: Submit an SPR with the crash dump.
004015,

Improper state change for shadow member

FACILITY: DISK, 501
Explanation: The sequential gatekeeper mechanism suspends activity for shadow units before
allowing a state change. This crash indicates the mechanism failed to operate properly.
Action: Submit an SPR with the crash dump.
004016,

Shadow unit not found in Disk Unit Table (OUT)

FACILITY: DISK, many
Explanation: The subroutine RMUNIT could not find the shadow unit in the Disk Unit Table (OUT).
This crash indicates improper sequencing of actions to remove a shadow unit. The most probable
cause is multiple calls on RMUNIT for the same unit.
Action: Submit an SPR with the crash dump.
004017,

Invalid diagnostic HMB

FACILITY: DISK, MSCP
Explanation: The diagnostic interface within the Disk Path received an HMB with a nonzero length
field In the HM$LOF word. This indicates an invalid request from some diagnostic or improper
routing of the HMB by the Disk Path.
Action: Submit an SPR with the crash dump. List any utilities or diagnostics running at the time of
the crash.
004020, Too many seek blocks requested by diagnostic
FACILITY: DISK, MSCP
Explanation: A diagnostic or utility requested an excessive number of seek blocks for transfers
during initialization.
Action: Submit an SPR with the crash dump. List any utilities or diagnostics running at the time of
the crash.
004021,

Diagnostic release of disk unit while online

FACILITY: DISK, MSCP
Explanation: A diagnostic or utility attempted to release a disk unit while it was still online.
Action: Submit an SPR with the crash dump. Specify the utilities or diagnostics running at the time
of the crash.

8-16
EXCEPTION CODES AND MESSAGES

004022,

Diagnostic release of HCB while units still online

FACILITY: DISK, MSCP
Explanation: A diagnostic or utility attempted to release a Host Control Block (HCB) which keeps
records of online units, while some disk units were online via that HCB.
Action: Submit an SPR with the crash dump. Specify the utilities or diagnostics executing at the time
of the crash.
004023,

DRAT/SEEK timer not allocated for disk unit

FACILITY: DISK, ERROR
Explanation: The Disk Path initialization code discovered a disk unit without a DRAT/SEEK timer
allocated (address of 0). This is an initialization inconsistency, possibly due to an improper load of
the Disk Path.
Action: Submit an SPR with~the crash dump. Specify the configuration of the crashed HSC.
004024,

Not enough mapped memory to initialize Disk Path

FACILITY: DISK, ERROR
Explanation: The Disk Path initialization routine could not allocate enough Program memory to
perform error recovery. The most probable cause is insufficient available memory.
Action: Determine the amount of available Program memory (P.loj). If It Is lower than the minimum
amount, replace the memory module. If the memory appears to be sufficient, submit an SPR with the
crash dump. Note the actual amount of available memory by executing the SHOW ALL command.
004025,

Error identification table overwritten

FACILITY: DISK, ERROR
Explanation: This crash can occur only if the disk error Identification table was overwritten or a wild
branch was taken. The most probable cause is a bad load.
Action: If this crash occurs immediately after a boot, try rebooting with a backup copy of the HSC
software. Otherwise, submit an SPR with the crash dump.
004026,

Invalid error bit value found during error recovery

FACILITY: DISK, ERROR
Explanation: The bit value describing a K.sdi/K.sl error was not valid for a given stage of the error
recovery. The most probable cause is a design error within the error recovery code. It Is possible,
although unlikely, the cause Is a malfunctioning K.sdilK.si.
Action: If no hardware problem exists, submit an SPR with the crash dump. If this error appears to
recur from the same K.sdi/K.si, replace the K.sdi/K.si.
004027,

Invalid disk characteristics for operation

FACILITY: DISK, ERROR
Explanation: An arithmetic operation to compute some disk parameter caused an overflow or
produced a result outside the allowed range. The most probable cause is a design error within
the error recovery code. It is also possible, although unlikely, a disk supplied invalid characteristics
to the HSC.
Action: If possible, get the number of the requestor involved from the last error log printed on the
console or from the system error log. If no hardware problem exists, submit an SPR with the crash
dump. Further testing of the disk and attached requestor(s) may be necessary. If this error appears
to recur from the same unit, repair the unit.

6-17
EXCEPTION CODES AND MESSAGES

004030,

S bit not set in FRB error state

FACILITY: DISK, ERROR
Explanation: The S bit in the K Control Area port subarea for a drive in FRS error state was not set
as expected. This logical inconsistency indicates improper manipulation of the port state. The most
probable cause is a design error within the error recovery code. It is also possible, although unlikely,
a K.sdi/K.si is malfunctioning.
Action: If possible, get the number of the requestor involved from the last error log printed on the
console or from the system error log. If no hardwa~e problem exists, submit an SPR with the crash
dump. Further testing of suspected requestor may be necessary. If this error appears to recur from
the same K.sdi/K.si, replace the K.sdi/K.si.
004031,

DT$ERQ not zero in FRB error state

FACILITY: DISK, ERROR
Explanation: The FRB error queue in the DRAT being processed by error recovery was not zero as
expected. This logical inconsistency indicates improper manipulation of the port state. The most
probable cause, is a design error within the error recovery code. It is also possible, although unlikely,
a K.sdi/K.si is malfunctioning.
Action: If possible, get the number of the requestor involved from the last error log printed on the
console or from the system error log. If no hardware problem exists, submit an SPR with the crash
dump. Further testing of the suspected requestor may be necessary. If this error appears to recur
from the same K.sdi/K.sI, replace the K.sdi/K.si.
004032,

Unable to get to FRB error state

FACILITY: DISK, ERROR
Explanation: Error recovery was unable to place a port In FRB error state in order to perform an
error recovery operation. This crash can occur in an extremely unlikely compound error situation.
The most probable cause, however, is a design error within the error recovery code.
Action: Reboot the HSC. If this error persists, submit an SPR with the crash dump.
004033,

Non-ECC/EDC errors remaining after ECC correction

FACILITY: DISK, ERROR
Explanation: ECC error correction should take place after all other errors except EDC have been
corrected. This crash occurs because other error bits are set after ECC correction. The most
probable cause is a design error within the error recovery code.
Action: Submit an SPR with the crash dump.
004034,

Level B retry in wrong state

FACILITY: DISK, ERROR
Explanation: This crash occurs because a level B retry operation is attempted without the drive port
being in FRB error state. The only cause is a design error within the error recovery code.
Action: Submit an SPR with the crash dump.
004035,

Level C retry in wrong state

FACILITY: DISK, ERROR
Explanation: This crash occurs because a level C retry operation is being attempted without the drive
port being in FRB error state. The only cause is a design error within the error recovery code.
Action: Submit an SPR with the crash dump.

8-18
EXCEPTION CODES AND MESSAGES

004036,

DCB state is busy with empty DCB queue

FACILITY: DISK, ERROR
Explanation: The drive state indicator in the K Control Area indicates a K.sdilK.sl Is processing a
DCB, but the DCB queue is empty. The most probable cause of this crash is a design error In the
error recovery code. It is also possible, but unlikely, that the K.sdilK.si is malfunctioning.
Action: If possible, get the number of the requestor involved from the last error log printed on the
console or from the system error log. If no hardware problem exists, submit an SPR with the crash
dump. Further testing of the suspect requestor may be necessary. If this error appears to recur from
the same K.sdi/K.si, replace the K.sdi/K.si.
004037,

Invalid error queue address in route

FACILITY: DISK, ERROR
Explanation: When attempting to route an FRB to an error queue, the error queue address in a route
descriptor was invalid. The most likely cause of this crash is a corrupted route descriptor, probably
due to a logic error in the error recovery code.
Action: Submit an SPR with the crash dump.
004040,

Undefined error bit in error word from K

FACILITY: DISK, ERROR
Explanation: The error recovery routine IDENTIFY found an undefined bit in the error word stored
by either a K.sdilK.si or K.ci. The most probable cause of this crash is a logic error within the error
recovery code. It is also possible, but unlikely, a K is malfunctioning.
Action: If possible, get the number of the requestor involved from the last error log printed on the
console or from the system error log. If no hardware problem exists, submit an SPR with the crash
dump. Further testing of suspect requestor may be necessary. If this error appears to recur from the
same K.sdilK.si, replace the K.sdi/K.si.
004041,

No buffer found in FRB when expected

FACILITY: DISK, ERROR
Explanation: The error recovery routine MAPBUF attempted to map a buffer but found the buffer
address to be O. The only cause of this crash is a design error within the error recovery code.
Action: Submit an SPR with the crash dump.
004042,

FRB not in error state for Level D 1/0 Operation (LVLDIO)

FACILITY: DISK, ERROR
Explanation: A call to the error recovery subroutine Level D 1/0 Operation (LVLDIO) was made
without the port being in FRB error state. The only cause of this logical inconsistency Is a design
error within the error recovery code.
Action: Submit an SPR with the crash dump.
004043,

Stack too deep to save in thread block

FACILITY: DISK, ERROR
Explanation: A call to the error recovery subroutine Level 0 1/0 Operation (LVLDIO) was made with
too many items on the stack to save in a thread block. The only cause of this logical inconsistency
is a design error within the error recovery code.
Action: Submit an SPR with the crash dump.

8-19
EXCEPTION CODES AND MESSAGES

004044,

Buffer not found for specified error

FACILITY: DISK, ERROR

Explanation: A call to the error recovery subroutine RCDHMX specified a buffer that was not found
In the list of buffers for the specified FRS. The only cause of this logical inconsistency is a design
error within the error recovery code.
Action: Submit an SPR with the crash dump.
004045,

Parent downcount failed

FACILITY: DISK, ERROR
Explanation: A downcount of the parent HMB failed during routing of an FRB in the error recovery
subroutine RETIRE. This crash is caused by improper manipulation of the parent counter by some
process or overwritten memory.
Action: Submit an SPR with the crash dump.
004046,

DRAT not found for FRB retirement

FACILITY: DISK, ERROR
Explanation: The error recovery subroutine RETIRE could not locate the DRAT for downcounting
while attempting to retire an FRB by simulating route completion. This crash is caused by either a
logic inconsistency within error recovery or overwritten memory. It is also possible, although unlikely,
it is caused by a malfunctioning K.sdi/K.si.
Action: If possible, get the number of the requestor involved from the last error log printed on the
console or from the system error log. If no hardware problem exists, submit an SPR with the crash
dump. Further testing of requestors and HSC internal buses may be necessary. If this error Elppears
to recur from the same K.sdilK.si, replace the K.sdilK.si.
004047,

SectorslTrack field in K Control Area is zero

FACILITY: DISK, ERROR
Explanation: The error recovery subroutine RETIRE found the Sectors/Track field in the K Control
Area to be zero while attempting to retire an FRB by simulating route completion. This crash is
caused by either a logic inconsistency within error recovery or overwritten memory. It is also
pOSSible, although unlikely, it is caused by a malfunctioning K.sdi/K.si.
Action: If possible, get the number of the requestor involved from the last error log printed on the
console or from the system error log. If no hardware problem exists, submit an SPR with the crash
dump. If this error appears to recur from the same K.sdi/K.si, replace it.
004050,

DRAT queue not empty for shadow copy

FACILITY: DISK, MSCP
Explanation: After obtaining exclusive use of a drive, the shadow copy code found a DRAT queue
for that drive was not empty. This crash can only be caused by a design error within the MSCP
command processing.
Action: Submit an SPR with the crash dump.
004051,

Inconsistent result for Repair operation

FACILITY: DISK, MSCP
Explanation: An impossible combination of results was found at the end of a Shadow Repair
operation. This crash can only be caused by a design error within the Shadow Repair code.
Action: Submit an SPR with the crash dump.

6-20
EXCEPTION CODES AND MESSAGES

004052,

Known drive not found in the Disk Unit Table (OUT)

FACILITY: DISK, MSCP
Explanation: While attempting to remove a known disk unit from the OUT, the unit was not found in
that table. This crash can be caused only by a design error within the MSCP command processing.
Action: Submit an SPR with the crash dump. Note any utilities or diagnostics running at the time of
the crash.
004053, Invalid block number for Transfer operation
FACILITY: DISK, MSCP
Explanation: All MSCP transfer commands are prechecked for valid parameters. This applies to most
diagnostic transfers as well. This crash indicates an invalid block number somehow slipped past the
checks. It indicates a design error within the Disk Path transfer processing or a corrupted Disk Unit
Control Block (DUCB).
Action: Submit an SPR with the crash dump. Note any utilities or diagnostics running at the time of
the crash.
004054,

Unexpected Compare failure following Write

FACILITY: DISK, ERROR
Explanation: The RCT.MWRITE routine writes, reads back, and one at a time compares a block of
data to all copies of that block in the RCT. This crash indicates a block was read back with no errors
detected; however, it did not compare with the original data written. This indicates data was delivered
incorrectly by the K.sdi/K.si without any error indications. It is possible, but unlikely, the failure is
due to a leg ltimate undetected error.
Action: If possible, get the number of the requestor Involved from the last error log printed on the
console or from the system error log. If no hardware problem exists, submit an SPR with the crash
dump. If this error appears to recur from the same unit, repair the unit.
004055,

Attempt to enable drive interrupt already enabled

FACILITY: DISK, many
Explanation: The ARM subroutine was called to enable the interrupt for drive state changes when the
interrupt was already enabled. The only possible cause for this crash is a design error.
Action: Submit an SPR with the crash dump. Note the process running at the time of the crash.
004056,

Attempt to enable drive Interrupt with pending state change

FACILITY: DISK, many
Explanation: The ARM subroutine was called to enable the Interrupt for drive state changes while a
drive state change was being processed. The only possible cause for this crash Is a design error.
Action: Submit an SPR with the crash dump. Note the process running at the time of the crash.
004057, State change requested for available but inoperative drive
FACILITY: DISK, many
Explanation: The SCHSQM subroutine was called to schedule a state change operation for an
available but inoperative drive. The only possible cause for this crash Is a design error.
Action: Submit an SPR with the crash dump. Note the process running at the time of the crash.

8-21
EXCEPTION CODES AND MESSAGES

004060,

Attempt to downcount DRAT already at zero

FACILITY: DISK, many
Explanation: A call was made to the DWNCDT subroutine to downcount a DRAT when the count was
already zero" The only possible cause for this crash is a design error.
Action: Submit an SPR with the crash dump. Note the process running at the time of the crash.
004061, Thread block count not be initialized
FACILITY: DISK, SOl
Explanation: During initialization, the routine which allocates thread blocks discovered the number
of threads to be allocated was set to zero. This was probably caused by the failure of a previous
initialization routine to initialize this count word. This inconsistency may indicate an improper load.
Action: Reboot the HSC. If the failure persists, submit an SPR with the crash dump.
004062, Thread block area too small
FACILITY: DISK, SOl
Explanation: During initialization, the routine which carves up thread blocks found the area too small
to allocate all the thread blocks required. This inconsistency may indicate an improper load.
Action: Reboot the HSC with a backup copy of the HSC system software. If the failure persists,
submit an SPR with the crash dump.
004063,

SEEK DCB without Clear 0 bit flag set

FACILITY: DISK, SOl
Explanation: A SEEK DCB failed because the Clear 0 bit flag was not set as expected. The DCa- was
not a SEEK DCB or the DCB was improperly set up. The only possible cause is a design error within
the DCB processing code.
Action: Submit an SPR with the crash dump.
004064, DRAT/SEEK timer running with SEEK DCB queued
FACILITY: DISK, SOl
Explanation: During processing a failed SEEK DCB, the DRAT/SEEK timer was not running as
expected. The only possible cause is a design error within the DCB processing code.
Action: Submit an SPR with the crash dump.
004065,

0 bit set for port with SEEK DCB being processed

FACILITY: DISK, SOl
Explanation: During processing a failed SEEK DCB, the 0 bit (Process DRAT) was set for the port to
which the SEEK DCB had been queued. The only possible cause is a design error within the DCB
processing code.
Action: Submit an SPR with the crash dump.
004066,

State changed during SOl ONLINE

FACILITY: DISK, SOl
Explanation: After completing an SOl ONLINE command, either the state was not AVAILABLE or a
state change was pending. Because state changes are inhibited during the SOl ONLINE, this is a
logical inconsistency. The only possible cause is a design error within the SOl manager.
Action: Submit an SPR with the crash dump.

8-22
EXCEPTION CODES AND MESSAGES

004067,

SOl WRITE MEMORY command not implemented

FACILITY: DISK, SOl
Explanation: The SOl WRITE MEMORY command cannot be issued In the current Implementation of
the SOl manager. This crash indicates some process attempted to issue an SOl WRITE MEMORY
command.
Action: Submit an SPR with the crash dump. Note the diagnostics or utilities running at the time of
the crash.
004070,

Nonzero status for SUCCESSful OCB

FACILITY: DISK, SOl
Explanation: A DCB completed with a status of SUCCESS, but the error word Indicated errors
anyway. The most probable cause is a design error within DCB processing. It is possible, although
unlikely, the cause is a malfunctioning K.sdilK.si. This is a logical Inconsistency.
Action: If possible, get the number of the requestor involved from the last error log printed on the
console or from the system error log. If no hardware problem exists, submit an SPR with the crash
dump. If this error appears to recur from the same K.sdI/K.si, replace the K.sdi/K.si.
004071,

0 bit set in DCB error state

FACILITY: DISK, SOl
Explanation: During processing of a DCB, the 0 bit (Process DRAT) was set for the port to which the
OCB had been queued. This is a logical inconsistency. The only possible cause is a design error
within OCB processing.
Action: Submit an SPR with the crash dump.
004072,

DCB state is busy with empty DCB queue

FACILITY: DISK, many
Explanation: The drive state indicator in the K Control indicates a OCB Is being processed by the
K.sdi/K.si but the DCB queue is empty. The most probable cause of this crash Is a design error
within DCB processing. It is also possible, but unlikely, the K.sdIlK.sl Is malfunctioning.
Action: If possible, get the number of the requestor Involved from the last error log printed on the
console or from the system error log. If no hardware problem exists, submit an SPR with the crash
dump. Further testing of requestors, HSC internal buses, and memory subsystem may be necessary.
If this error appears to recur from the same K.sdi/K.si, replace It.
004073,

K.sdi/K.si is not responding

FACILITY: DISK, SOl
Explanation: A K.sdilK.si failed to process an immediate DCB within one second. The most probable
cause is a malfunctioning K.sdi/K.si.
Action: If possible, get the number of the requestor involved from the last error log printed on the
console or from the system error log. If the error persists, replace the K.sdi/K.si.

8-23
EXCEPTION CODES AND MESSAGES

004074,

DCB state is blocked after aUIESCE or DCBSTS DCB

FACILITY: DISK, SOl

Explanation: The drive state indicator in the K Control indicates DCB activity is blocked. This should
not be possible after a aUIESCE or DCBSTS DCB. The most probable cause of this crash is a design
error within DCB processing. It is also possible, but unlikely, the K.sdl/K.sl is malfunctioning.
Action: If possible, get the number of the requestor involved from the last error log printed on the
console or from the system error log. If no hardware error eXists, submit an SPR with the crash
dump. Further testing of requestors, HSC internal buses, and memory subsystem may be necessary.
If this error appears to recur from the same K.sdi/K.si, replace the K.sdilK.si.
004075,

Call to DCBOPR from process other than DISK

FACILITY: DISK, many
Explanation: The DCBOPR routine may be called only from the DISK process. This crash Indicates a
call was made from some other process.
Action: Submit an SPR with the crash dump. Note the process running at the time of the crash.
004076,

Port not In DCB error state for error DCB

FACILITY: DISK, SOl, ERROR
Explanation: The DCBOPR routine received an error DCB, but the port was not in DCB error state as
expected. This logical inconsistency can only be the result of a design error within DCB processing.
Action: Submit an SPR with the crash dump.
004077,

Match enable not set for DIALOG DCB

FACILITY: DISK, SOl
Explanation: The DCBOPR routine received a DCB with an improper combination of request bits set.
This logical inconsistency can only be the result of a design error within DCB processing.
Action: Submit an SPR with the crash dump.
004100, No thread block for operation
FACILITY: DISK, SOl
Explanation: Insufficient thread blocks were available to suspend the process. This logical
inconsistency can only be the result of a design error within DCB processing.
Action: Submit an SPR with the crash dump.
004101,

Stack too deep to suspend process in thread block

FACILITY: DISK, SOl
Explanation: The DCBWAIT routine was called with too many words on the stack to suspend the
process in a thread block. This logical inconsistency can only be the result of a design error within
DCB processing.
Action: Submit an SPR with the crash dump.

8-24
EXCEPTION CODES AND MESSAGES

004102,

Thread block pointer corrupted in DCB

FACILITY: DISK, SDI
Explanation: A DCB was returned from a K.sdi/K.si with a corrupted thread block pointer. The most
probable cause of this crash is a design error within DCB processing. It is also possible, but unlikely,
the cause Is a malfunctioning K.sdi/K.si.
Action: If possible, get the number of the requestor Involved from the last error log printed on the
console or from the system error log. If no hardware error exists, submit an SPR with the crash
dump. If this error appears to recur from the same K.sdi/K.sI, replace It.
004103,

Insufficient pool to allocate a timer

FACILITY: DISK, SDI
Explanation: This crash indicates too much memory has been allocated from common pool. It can
be caused by any process.
Action: Submit an SPR with the crash dump. Specify the diagnostics or utilities running at the time
of the crash and if there were DUP connections.
004104,

DCB received with no errors and no frames

FACILITY: DISK, SDI
Explanation: A DCB was received from K.sdi/K.si with no frames In the response and no error
Indications. It can be caused by a design error within DCB processing. It is probably caused by a
malfunctioning K.sdi/K.si.
Action: If possible, get the number of the requestor involved from the last error log printed on the
console or from the system error log. If no hardware error exists, submit an SPR with the crash
dump. If this error appears to recur from the same K.sdi/K.sI, replace it.
004105,

Element In deferred SEEK queue with no FRB

FACILITY: DISK, MSCP
Explanation: An element was found in the deferred SEEK queue for a disk unit having no FRBs. The
only possible cause is a design error within SEEK queue element processing.
Action: Submit an SPR with the crash dump.
004106,

DRAT allocation failure

FACILITY: DISK, many
Explanation: While preparing to read the FCT during ONLINE processing, the DRAT allocation
subroutine failed.
Action: Submit an SPR with the crash dump.
004107,

Command not completed after drive declared Inoperative

FACILITY: DISK, MSCP
Explanation: GET COMMAND STATUS processing declared the drive inoperative, but the command
still failed to complete within the timeout period.
Action: Submit an SPR with the crash dump. Note the type of the drive Identified in the error
message.

8-25
EXCEPTION CODES AND MESSAGES

004110,

GCS status overflow

FACILITY: DISK, MSCP
Explanation: GET COMMAND STATUS processing determined that the calculated status will result in
an overflow.
Action: Submit an SPR with the crash dump.
004111,

A timer has link field values inconsistent to its current operational state

FACILITY: DISK, many
Explanation: A timer was found to be in a state that should not exist when adding or removing a
timer from an active list.
Action: Submit an SPR with the crash dump.
004112,

A unit is incorrectly marked as a shadow set member

FACILITY: DISK, many
Explanation: A unit is incorrectly marked as being a member of a shadow set.
Action: Submit an SPR with the crash dump.
004113,

NO DRAT list invalid

FACILITY: DISK, many
Explanation: While declaring a drive inoperative during FRB retirement, the NO DRAT list was found
to be invalid.
Actton: Submit an SPR with the crash dump.
004114,

Connection closed after delay in ATTN process

FACILITY: DISK, ATTN
Explanation: While the Disk Server was waiting to acquire resources to send an attention message to
the host, the connection closed.
Action: Submit an SPR with the crash dump.
004115,

DCB address inconsistency

FACILITY: DISK, SDI
Explanation: While processing an error on a SEEK DCB, an inconsistency was found between the
current SEEK DCB address and the DCB address which is stored in the DRAT.
Action: Submit an SPR with the crash dump.
005001,

ECC self-test string too big for FAO

FACILITY: ECC
Explanation: A self-test string generated for the ECC process was too big to print with the FAO
buffer allocated. This crash can only occur if the self-test code is present and enabled. The self-test
code is not enabled for distributed base levels. R1 contains the number of characters in the string.
Action: Submit an SPR with the crash dump.

8-26
EXCEPTION CODES AND MESSAGES

005002, No ECC errors to correct
FACILITY: ECC
Explanation: An FRB with no errors was sent to the ECC process. This logical Inconsistency can
occur only due to a design error within error recovery.
Action: Submit an SPR with the crash dump.
005003,

Can't allocate XFRB to print self-test messages

FACILITY: ECC
Explanation: The ECC process failed to allocate an Extended Function Request Block (XFRB) for
printing messages during self-test. This crash can occur only If the self-test code Is present and
enabled (not true for distributed base levels).
Action: Submit an SPR with the crash dump.
005004,

ECC found more than a 10-bit symbol error

FACILITY: ECC
Explanation: The ECC process was sent a buffer with more than a 10-bit symbol error. Error recovery
processing should never pass on such a buffer. This logical Inconsistency can only occur due to a
design error within error recovery.
Action: Submit an SPR with the crash dump.
006000, This class of crashes is for Tape Path software Inconsistency errors
FACILITY: TAPE, TFxxxx
Explanation: A software inconsistency error occurred.
Action: Submit an SPR with the crash dump. Specify the utilities or diagnostics active at the time of
the crash.
006001,

An STI GET LINE STATUS failed

FACILITY: TAPE, TFATNAVAL
Explanation: When issued to the tape data channel, the STI command GET LINE STATUS returned
with a failure. This command should not return a failure when issued to a working tape data channel.
General register 5 points to the windowed K Control Area for the tape data channel In question.
Offset KG$SLT points to the tape requestor in question.
Action: Investigate the tape data channel in question.
006002,

Received an interrupt from an unknown tape data channel

FACILITY: TAPE, TFATNAVAL
Explanation: Received an interrupt from an unknown tape data channel. This Is a software
inconsistency. General register 1 points to the windowed tape data channel control area for the
tape data channel in question. General register 2 contains the tape data channel slot number from
which the interrupt was received.
Action: Submit an SPR with the crash dump.

B-27
EXCEPTION CODES AND MESSAGES
006003,

Received an illegal Connection Block (CB) from the CIMGR

FACILITY: TAPE, TFCI

Explanation: A Connection Block (CB) with an illegal Opcode was sent to the Tape Path. General
register 1 points to the 'llindowed address of the CB in question. General register 2 contains the
Opcode In question.
Action: Submit an SPR with the crash dump. Include the CB structure.
006004,

An Illegal diagnostic Opcode was received

FACILITY: TAPE, TFDIAG
Explanation: A diagnostic Host Message Block (HMB) with an illegal Opcode was sent to the tape
diagnostic interface. General register 3 points to the windowed diagnostic HMB. General register 1
contains the Opcode in question.
Action: Submit an SPR with the crash dump. Specify the utilities or diagnostics active at the time of
the crash. Include the HMB structure.
006005,

Diagnostics trying to acquire assigned Drive State Area

FACILITY: TAPE, TFDIAG
Explanation: Diagnostics are trying to acquire a previously-assigned Drive State Area. General
register 3 points to the windowed Control memory address of the Host Message Block (HMB).
General register 2 points to the Tape Formatter Control Block (TFCB). General register 4 points to the
Tape Drive Control Block (TDCB).
Action: Submit an SPR with the crash dump. Specify the diagnostics or utilities active at the time of
the crash. Include the HMB, TFCB, and TDCB structures.
006006,

Inconsistencies during Drive State Area acquisition

FACILITY: TAPE, TFDIAG
Explanation: The software context word (KT$SFW) is not equal to the Tape Formatter Control Block
(TFCB) address and/or DIALOG list head is nonzero when diagnostics are trying to acquire the Drive
State Area. General register 0 points to the windowed K Control Area. General register 2 points to
the TFCB. General register 4 points to the Tape Drive Control Block (TDCB).
Action: Submit an SPR with the crash dump. Indicate the utilities or diagnostics active at the time of
the crash. Include the TFCB and TDCB structures.
006007,

No Block Header supplied by BACKUP

FACILITY: TAPE, TFDIAG
Explanation: BACKUP did not supply the initial Block Header buffer descriptor. General register 3
points to the windowed Host Message Block (HMB) address. General register 5 should point to the
buffer descriptor and, in this case, should be zero.
Action: Submit an SPR with the crash dump. Include details of the BACKUP operation. Include the
HMB structure.

8-28
EXCEPTION CODES AND MESSAGES

006010,

No buffers supplied in BACKUP operation

FACILITY: TAPE, TFDIAG
Explanation: No disk data block buffers were supplied in Host Message Block (HMB) for the BACKUP
operation. General register 3 points to the windowed Control memory address of the HMB in
question. General register 0 points to the Control memory Fragment Request Block (FRB) and, in
this case, will be zero.
Action: Submit an SPR with the crash dump. Include details of the BACKUP operation. Include the
HMB structure.
006011,

Could not allocate an XFRB

FACILITY: TAPE, TFLIB
Explanation: Could not allocate an Extended Function Control Block (XFRB) through ALOCB, a
CRONIC system service.
Action: Submit an SPR with the crash dump.
006012,

Required CIMGR functionality not yet implemented

FACILITY: TAPE, TFMSCP
Explanation: The host sent the Tape Server a command packet with an Opcode that was not a
sequenced message. General register 5 is the Opcode received. General register 3 is the windowed
Control memory address of the command packet received (HMB).
Action: Submit an SPR with the crash dump. Indicate the host software version. Include the HMB
(command packet) structure.
006013,

Required CIMGR functionality not yet implemented

FACILITY: TAPE, TFMSCP
Explanation: The Tape Server received a host command packet longer than allowed (36 bytes).
General register 4 is the size of the command packet received. General register 3 Is the windowed
Control memory address of the Host Message Block (HMB) command packet in question.
Action: Submit an SPR with the crash dump. Indicate the host software version. Include the HMB
command packet structure.
006014,

Required CIMGR functionality not yet implemented

FACILITY: TAPE, TFMSCP
Explanation: The Tape Server received a host command packet with a status that currently is not
executed. General register 3 points to the windowed Control memory address of the Host Message
Block (HUB) command packet in question. Offset HM$ERR is the field In question.
Action: Submit an SPR with the crash dump. Indicate the host software version. If no hardware
problem exists, submit an SPR. Further testing of HSC hardware may be necessary. Investigate K.cl.
Include the Host Message Block (HMB) command packet structure.

B-29
EXCEPTION CODES AND MESSAGES

006015,

Could not find correct Tape Drive Control Block (TOCB) pointer

FACILITY: TAPE, TFSEQUEN

Explanation: A call to remove a host's access to a drive resulted in searching the current chain of
Tape Dr!ve Control Blocks (TOeB) in that host's Host Control Block (HCB). Inability to find the correct
TOCB pointer resulted in this crash. General register 4 points to the TOCB that Is trying to have host
access removed. General register 3 points to the windowed Control memory address of the HMB.
Offset HM$CTX in the HMB points to the Host Disk Block (HOB). Offset HOB.TOCB In the HOB points
to the TOCB.
Action: Submit an SPR with the crash dump. Include the HMB, TOCB, and HOB structures.
006016,

Unable to allocate an HOB

FACILITY: TAPE, TFSEQUEN
Explanation: An attempt to add a host access (requiring allocation of an HOB) failed for lack of
resources.
Action: Submit an SPR with the crash dump.
006017, Tape formatter does not support allowed densities
FACILITY: TAPE, TFSEQUEN
Explanation: The tape formatter does not support a density the HSC supports. General register
4 points to the Tape Drive Control Block (TOCB) for the drive in question. R3 points to the Host
Message Block (HMB) and the error occurred because the offset was zero.
Action: Submit an SPR with the crash dump. Include the host software version and the tape
formatter revision. Also include the TOCB and HMB structures, host software version, and tape
formatter revIsion.
006020,

An invalid density is set in the Tape Drive Control Block (TOCB)

FACILITY: TAPE, TFSEQUEN
Explanation: An invalid density was set in the TOCB. This should not happen. General register 4
points to the TOCB in question.
Action: Submit an SPR with the crash dump. Include the TOCB structure.
006021,

Read reverse emulation not flagged

FACILITY: TAPE, TFSEQUEN
Explanation: The Tape Server entered the read reverse emulation code without read reverse emulation
being flagged in the Tape Drive Control Block (TOCB) at offset TO. FLAGS bit TOF.RREVEM. General
register 3 points to the windowed Control memory address of the Host Message Block (HMB). General
register 4 points to the TOCB for drive in question. General register 2 points to the Tape Formatter
Control Block (TFCB) for the formatter in question.
Action: Submit an SPR with the crash dump. Include the HMB, TOCB, and TFCB structures.
006022,

Route pointer for read reverse emulation zero

FACILITY: TAPE, TFSEQUEN
Explanation: The Tape Server entered the read reverse emulation code without having the route
pointer set in the Host Message Block (HMB). General register 3 points to the windowed Control
memory address of the HMB in question.
Action: Submit an SPR with crash the dump. Include the HMB structure.

8-30
EXCEPTION CODES AND MESSAGES

006023,

Requested transfer larger than 64 Kb

FACILITY: TAPE, TFSEQUEN
Explanation: The requested transfer size for a read reverse is larger than 64 Kb. This should not
happen. General register 3 points to the windowed Control memory address of the Host Message
Block (HMB) in question and offset HP. Be indicates the transfer size requested.
Action: Submit an SPR with the crash dump. Include the HMB structure.
006024,

Read reverse emulation not flagged

FACILITY: TAPE, TFSEQUEN
Explanation: The Tape Server entered the read reverse emulation short retry code without read
reverse emulation being flagged in the Tape Drive Control Block (TDCB) at offset TO.FLAGS bit
TOF.RREVEM. General register 3 points to the windowed Control memory address of the Host
Message Block (HMB). General register 4 points to the TOCB for drive in question. General register 2
points to the Tape Formatter Control Block (TFCB) for the formatter in question.
Action: Submit an SPR with the crash dump. Include the HMB, TOCB, and TFCB structures.
006025,

Read reverse emulation not flagged

FACILITY: TAPE, TFSEQUEN
Explanation: The Tape Server entered the read reverse emulation long retry code without read reverse
emulation being flagged in the Tape Drive Control Block (TOCB) at offset TO.FLAGS bit TDF.RREVEM.
General register 3 points to the windowed Control memory address of the Host Message Block
(HMB). General register 4 points to the TOCB for the drive in question. General register 2 points to
the Tape Formatter Control Block (TFCB) for the formatter in question.
Action: Submit an SPR with the crash dump. Include the HMB, TOCB, and TFCB structures.
006026,

KT$SEM is equal to zero

FACILITY: TAPE, TFSEQUEN
Explanation: The K Control Area offset KT$SEM is less than or equal to zero. this should not
happen. General register 3 points to the K Control Area In question.
Action: Submit an SPR with the crash dump. Include the K Control Area structure.
006031,

No available stacks

FACILITY: TAPE, TFSERVER
Explanation: There are no available stacks for a process trying to suspend.
Action: Submit an SPR with the crash dump.
006033, Top of User stack for a resume is not set to server return
FACILITY: TAPE, TFSERVER
Explanation: The top of the User stack on a process resume is not set to the server return
(SVR.RETURN) routine. This is a software inconsistency.
Action: Submit an SPR with the crash dump.

8-31
EXCEPTION CODES AND MESSAGES

006040,

No stack available to suspend with

FACILITY: TAPE, TFSTI

Explanation: No stack available for suspending a process. General register 2 points to the Tape
Formatter Control Block (TFCB). Genera! register 5 points to the K Control Area. Genera! register 4
points to the Dialogue Control Block (DCB).
Action: Submit an SPR with the crash dump. Include the TFCB, DCB, and K Control Area structures.
006043,

Buffer descriptor address missing

FACILITY: TAPE, TXREVERSE
Explanation: The next address is missing from the linked list of buffer descriptors. General register
5 points to the Fragment Request Block (FRB) in question. Offset F$BFHD points to the buffer
descriptor list in question.
Action: Submit an SPR with the crash dump. Include the FRB structure.
006044,

Unexpected Fragment Request Block (FRB) error received

FACILITY: TAPE, TFERR
Explanation: An error was received from a software station rather than from a hardware station.
General register 5 points to the FRB in error.
Action: Submit an SPR with the crash dump. Include the FRB structure.
006045,

Unknown Fragment Request Block (FRB) error received

FACILITY: TAPE, TFERR
Explanation: An unidentifiable error is flagged in a Fragment Request Block (FRB). General register 5
points to the FRB in error.
Action: Submit an SPR with the crash dump. Include the FRB structure.
006046,

K.ci did not return a Fragment Request Block (FRB)

FACILITY: TAPE, TFERR
Explanation: Transfer Request Blocks (TRB) have an associated FRB that point to Data Buffers.
When a TRB is received in error, the FRBs must be deallocated. If an FRB is held by K.cl and not
returned within 20 seconds, this crash occurs.
Action: If no hardware problem exists, submit an SPR with the crash dump. If the problem reoccurs,
.
investigate the K.ci.
006047,

Invalid downcount occurred on a Host Message Block (HMB) chain

FACILITY: TAPE, TFERR
Explanation: Whenever Transfer Request Blocks (TRB) are purged from the K.sti/K.si input queue,
the associated HMB must not be returned to the host as an end message. This catching mechanism
relies on a change of HMBs with associated counters. This is a software consistency check to
ensure Control memory is not corrupted by the end of the chain. General register 5 points to the
HMB.
Action: Submit an SPR with the crash dump. Include the HMB.

8-32
EXCEPTION CODES AND MESSAGES

006050,

Sequence number corruption occurred

FACILITY: TAPE, TFERR
Explanation: Error recovery ensures against a deadlock on ~.stIlK.si by preventing a Transfer
Request Block (TRB) from waiting for a Diagnostic Control Block (DCB) that will never execute. Such
a deadlock can only occur from a software inconsistency.
Action: Submit an SPR with the crash dump.
007000, This class of crashes includes CIMGR software consistency errors
FACILITY: CIMGR, any
Explanation: A software inconsistency error occurred.
Action: Submit an SPR with the crash dump. Specify the utilities or diagnostics active at the time of
the crash.
007001,

Received a sequence message without a credit

FACILITY: CIMGR, CIDIRECT
Explanation: The SCS$DIRECT process received a sequence message in a Host Message Block
(HMB) flagged by the K.ci as not having a credit for the connection. General register 1 has the
address of the HMB in error.
Action: Submit an SPR with the crash dump. Include the HMB.
007002,

Failed to acquire a control block from K.ci

FACILITY: CIMGR, CIMISCPRC
Explanation: The POllER process was not able to obtain a control block from K.cl to resend a
timed-out STACK datagram.
Action: If no hardware problem exists, submit an SPR with the crash dump. Further testing of the
HSC subsystem may be necessary. Investigate the available Control memory.
007003,

K.cl Is hung

FACILITY: CIMGR, CIMISCPRC
Explanation: During the polling interval the POllER ensures that K.cl Is still running. This trap
Indicates It Is not.
Action: II no hardware problem exists, submit an SPR with the crash dump. Further testing of the
HSC subsystem may be necessary. Investigate the K.ci boards.
007004,

K.cl detected an unrecoverable error and stopped

FACILITY: CIMGR, CIMISCPRC
Explanation: K.cl sent its Control Area to the CIMGR exception process. This Is done whenever K.cl
has detected a nonrecoverable hardware error.
Action: If no hardware problem exists, submit an SPR with the crash dump. Further testing of the
HSC subsystem may be necessary. Investigate the K.ci boards and Data memory.
007005,

K.ci patch status check failed

FACILITY: CIMGR, CIMISCPRC
Explanation: K.ci did not respond to a path status check within eight seconds.
Action: If no hardware problem exists, submit an SPR with the crash dump. Investigate the K.cl
boards. Further testing of the HSC subsystem may be necessary.

6-33
EXCEPTION CODES AND MESSAGES

007006,

System name is corrupted

FACILITY: CIMGR, CIROOT

Explanation: During initialization, the CIMGR discovered the System name was corrupted in the SCT.
Action: Release the Online switch on the HSC (out). Reboot the HSC by holding the Fault switch
down until the State light blinks. This will bypass using the SCT on the boot device. Run SETSHO
to reset system name and 10, then reboot HSC one more time before pushing in the Online switch on
the front panel.
007007,

HMB received with wrong number of BMBs

FACILITY: CIMGR, CISCS
Explanation: A Host Message Block (HMB) was received with the wrong number of Big Message
Buffers (BMB). A START or 10 packet was received from K.ci without the proper number of associated
Data memory blocks. General register 0 points the HMB.
Action: If no hardware problem exists, submit an SPR with the crash dump. Investigate the K.ci
boards.
007011,

Connection incarnation inconsistent

FACILITY: CIMGR, CISCS
Explanation: While a connection is in the process of opening, the incarnation of that connection is
flagged as formative. The final step of opening the connection is to remove the flag. This crash
indicates the flag was prematurely removed, indicating a State inconsistency for the connection.
General register 2 points to the Connection Block (CB).
Action: Submit an SPR with the crash dump. Include the CB.
007012,

Connection incarnation mismatch

FACILITY: CIMGR, CISCS
Explanation: The incarnation of an opening connection is kept in both the Connection Block (CB)
and the CB vector table. As a connection opens a check is made to ensure these incarnations agree.
A disagreement indicates dangling reference to an old carnation of the connection. Register 2 points
to the CB.
Action: Submit an SPR with the crash dump. Include the CB.
007013,

Inconsistent connection state due to a VC closure

FACILITY: CIMGR, CISCS
Explanation: An illegal state transition was attempted on a connection. The state transition was
initiated by a Virtual Circuit (VC) closure. General register 2 pOints to the Connection Block (CB).
Action: Submit an SPR with the crash dump. Include the CB.
007014,

Unable to retrieve resource from K.ci during a disconnect

FACILITY: CIMGR, CISCS
Explanation: During a disconnect, the CIMGR was unable to retrieve the resources associated with
the credits on that connection from K.ci.
Action: Submit an SPR with the crash dump.

8-34
EXCEPTION CODES AND MESSAGES

007015,

K.ci did not respond to notification of a VC closure

FACILITY: CIMGR, CISUBRS
Explanation: The CIMGR informs K.cl when it marks a Virtual Circuit (VC) as closed. It then allows
the K.cl eight seconds to respond to the notification. This crash occurs If the response times out.
Action: If no hardware problem exists, submit an SPR with the crash dump. Investigate the K.cl.
007016,

Illegal attempt to deallocate a Connection Block (CB)

FACILITY: CIMGR, CISUBRS
Explanation: An attempt was made to deallocate a CB without breaking the connection. General
register 2 points to the CB.
Action: Submit an SPR with the crash dump. Include the CB.
007017,

Attempt to deallocate a Connection Block (CB) without an incarnation

FACILITY: CIMGR, CISUBRS
Explanation: A CB did not have a valid incarnation at the time it was deallocated. This crash
Indicates a software inconsistency.
Action: Submit an SPR with the crash dump. Include the CB.
007020,

Failure to retrieve SCS resources from K.ci

FACILITY: CIMGR, CISUBRS
Explanation: When trying to allocate resources for use across a Virtual Circuit (VC), the count of
Data memory resources was Incorrect. The Host Message Block (HMB) for serializing VC traffic must
have two Big Message Buffers (BMB). General register 0 points to the HMB.
Action: Submit an SPR with the crash dump. Include the HMB.
007021,

The count of waiters for VC resources went negative

FACILITY: CIMGR, CISUBRS
Explanation: While processing the list of waiters for transmission resources for a Virtual Circuit (VC),
a nonempty list was detected to indicate a negative number of waiters. This Is strictly a software
Inconsistency. General register 1 points to the System Block (SB).
Action: Submit an SPR with the crash dump. Include the SB.
007022,

Invalid BMB address

FACILITY: CIMGR, CIMISCPRC
Explanation: A Host Message Block (HMB) arrived at the resource collector with an Invalid Big
Message Buffer (BMB) address attached to it.
Action: Note the K.pli microcode revision level with a SETSHO SHOW REQUESTORS command. The
K.ci MC version reported by this command is the K.pli microcode revision level. If the revision level
Is less than revision 45, contact the local field service representative for a K.pli microcode update.
Also, note the current disk configuration. If the K.pli microcode revision level is greater than or equal
to 45, submit an SPR with crash dump and the noted disk configuration.

8-35
EXCEPTION CODES AND MESSAGES

007023,

SCS buffer retrieval failure

FACILITY: CIMGR, CISUBRS
Explanation: When changing the status of the Virtual Circuit (VC), CIMGR tries to retrieve the SCS
buffer from the K.ci .KHSRR queue. This buffer should be on the queue because it is not in use at
the time of the crash. If no elements were enqueued on the .KHSRR queue, CIMGR forces a crash.
Action: Submit an SPR with the crash dump.
012001,

Can't find Connection Block (CB)

Explanation: When DUP receives an HMB, DUP tries to find a reference to the CB (referred to by
HM$CTX in the HMB) in the DG$ structures (DUP Context Control Blocks). DUP was unable to find a
reference to the CB, even though it searched every DG$ structure.
Action: Submit an SPR with the exception dump or startup message indicating the contents of the
stack.
012002,

Illegal BMB count

FACILITY: DUP
Explanation: The Host Message Block (HMB) (MSCP packet carrier) has an illegal number of Big
Message Buffers (BMBs) allocated. DUP allows only one. The HMB is invalid.
Action: Submit an SPR with the exception dump or startup message indicating the contents of the
stack. The second word of the stack contains the windowed address of the HMB. The third word of
the stack contains the value in HM$CN-the count of the number of BMBs.
012003,

Illegal HMB Opcode

FACILITY: CUP
Explanation: The Opcode specified in the HM$LOF field of the Host Message Block (HMB) was not
equal to HML$RM. (Received sequence message over connection; HML$RM=OOOOOO.) HMB Opcodes
must indicate the HMB is for a sequenced message.
Action: Submit an SPR with the exception dump or startup message indicating the contents of the
stack. The second word of the stack contains the illegal Opcode.
012004,

Illegal HMB Error

FACILITY: DUP
Explanation: The error specified in the HM$ERR field of the Host Message Block (HMB) was not equal
to 0, HME$EC, or HME$NC. (Extra credits received if HME$EC=10; no credits received if HME$NC=4.)
Action: Submit an SPR with the exception dump or startup message indicating the contents of the
stack. The second word of the stack contains the value in the HM$ERR fiel~.
012021,

Invalid Connection Block (CB)

FACILITY: DUP
Explanation: The DUP process received a CB with an invalid value in the CB$ACT field. The CB$ACT
field contains the action value (action to be performed by the DUP server).
Action: Submit an SPR with the exception dump or startup message indicating the contents of the
stack. The second word on the stack contains the contents of the CB$ACT field.

8-36
EXCEPTION CODES AND MESSAGES
012024,

Bad downcount

FACILITY: DUP
Explanation: DUP initiates return of the endpacket to the host by downcountlng the reference counter
in the related control block. The downcount action shoUld return one. If the downcount did not
decrement the reference counter to one, DUP crashes the HSC.
Action: Submit an SPR with the exception dump or startup message indicating the contents of the
slack. The second word on the stack is the value of the counter following the downcount.
012036,

Connection Broken

FACILITY: DUP
Explanation: While DUP was preparing to send a message to the K.cl, the connection to the host
was broken. The connection was broken after DUP did an extensive check to ensure the connection
existed. DUP detected the connection break the second time because the DG$CB field was set to
zero.
Action: Submit an SPR. This is an internal consistency check and should never be seen.
042001,

FAO message buffer overflow

FACILITY: DIRECT
Explanation: The program DIRECT was attempting to output the end message, but the length of that
message was longer than the allotted FAO output buffer.
Action: Submit an SPR with the crash dump.
043001,

Wrong HMB received when trying to bring source online

FACILITY: DKCOPY
Explanation: A Host Message Block (HMB) was sent to the Disk Server requesting the source unit be
brought online in a shadow set. When the completion queue of this HMB was checked, It pointed to
a different (Incorrect) HMB.
Action: Submit an SPR with the dump. Top of stack equals crash code. Second word points to
previous HMB.
043002,

Bad downcount when trying to bring source online

Wrong HMB received when trying to issue GCS to target unit

FACILITY: DKCOPY
Explanation: A Host Message Block (HMB) was sent to the Disk Server requesting a GET COMMAND
STATUS (GCS) command be sent to the target unit. When the completion queue of this HMB was
checked, it pointed to a different (incorrect) HMB.
Action: Submit an SPR with the dump. Top of stack equals the crash code. The second word points
to the previous HMB.

8-37
EXCEPTION CODES AND MESSAGES

043004, Bad downcount when trying to issue GCS to target unit
FAC!LlTY: DKCOPY

Explanation: When an MSCP end message was to be sent over a connection to a host, a counter
keeping track of the transaction (decrementing by one) failed to operate properly. This occurred after
the Disk server was asked to send a GET COMMAND STATUS (GCS) command to the target unit.
Action: Submit an SPR with the dump. Top of stack equals the crash code. The second word points
to the counter.
043005,

Bad downcount when trying to bring target unit online

Bad downcount when trying to issue abort command to target unit

FACILITY: DKCOPY
Explanation: When an MSCP end message was to be sent over a connection to a host, a counter
keeping track of the transaction (decrementing by one) failed to operate properly. This occurred after
the Disk server had been asked to abort an online command to the target unit.
Action: Submit an SPR with the dump. Top of stack equals the crash code. The second word points
to the counter.
043007, Wrong HMB received after Issuing AVL command to shadow unit
FACILITY: DKCOPY
Explanation: A Host Message Block (HMB) was sent to the Disk Server requesting the shadow unit
used to facilitate the copy operation be made available. When the completion queue of this HMB was
checked, It pointed to a different (incorrect) HMB.
Action: Submit an SPR with the dump. Top of stack equals the crash code. The second word points
to the previous HM B.
043010,

Bad downcount when trying to issue AVL command to shadow unit

Missing DRAT for FORMAT TRACK operation

FACILITY: FORMAT
Explanation: A DRAT that was to be put on its completion queue was not found on the DRAT queue.
Action: Submit an SPR with the crash dump.

6-38
EXCEPTION CODES AND MESSAGES
051001,

An XFRB was not acquired to print messages

FACILITY: SETSHO, SSMAIN
Explanation: An Extended Function Request Block (XFRB) was not acquired by the SETSHO main
routine. A crash was initiated because the lack of this item prevents communication between the
HSC and the console.
Action: Submit an SPR with the dump.
051002,

Failed to properly send HMB to K.ci

FACILITY: SETSHO, SSMAIN
Explanation: A Host Message Block (HMB) was sent to the K.ci (the hardware that handles
communication between the hosts and the HSC). A crash was initiated because confirmation of
the HMB was not received from the K.ci within the required time.
Action: Submit an SPR with the dump.
051003,

Too many characters intended for console printout

FACILITY: SETSHO, SSMAIN
Explanation: In this case, Formatted ASCII Output (FAO) was called and It generated more characters
than the buffer size allocated would allow. The maximum is 510 characters.
Action: Submit an SPR with the dump. R1 points to the string size.
051004,

The System Control Table (SCT) crossed a page boundary

FACILITY: SETSHO, SSMAIN
Explanation: The SCT must remain on one page in memory. It typically indicates an Incorrect amount
of padding was placed at the end of the file SSDATA.MAC.
Action: Submit an SPR with the dump.
051101,

Failed in sending HMB to Disk Server for SET On [NO]HOST

FACILITY: SETSHO, SET
Explanation: A Host Message Block (HMB) was sent to the Disk Server In order to SET a disk drive
HOST or NOHOST. The crash was initiated because the confirmation of this command was not
received within the required time.
Action: Submit an SPR with the dump.
051102,

Failed in sending HMB to Tape Server for SET Tn [NO]HOST

FACILITY: SETSHO, SET
Explanation: A Host Memory Block (HMB) was sent to the Tape Server In order to SET a tape drive
HOST or NOHOST. The crash was initiated because the confirmation of this command was not
received within the required time.
Action: Submit an SPR with the dump.
051201,

Failed in sending HMB to Disk Server for SHOW On

FACILITY: SETSHO, SHOW
Explanation: A Host Memory Block (HMB) was sent to the Disk Server in order to SHOW a specific
disk drive. The crash was initiated because the confirmation of this command was not received
within the required time.
Action: Submit an SPR with the dump.

8-39
EXCEPTION CODES AND MESSAGES

051202,

Failed in sending HMB to Tape Server for SHOW Tn

FACILITY: SETSHO, SHOW
Explanation: A Host Memory Block (HMB) was sent to the Tape Server in order to SHOW a specific
tape drive. The crash was initiated because the confirmation of this command was not received
within the required time.
Action: Submit an SPR with the dump.
051203,

SCT crash context table contained too many characters

FACILITY: SETSHO, SHOW
Explanation: The SCT crash context table contained too many characters. In this case FAO was
called and it generated more characters than the buffer size would allow. The maximum is 510
characters.
Action: Submit an SPR with the dump. R1 points to the string size.
052001,

Double word math not consistent

FACILITY: SINI
Explanation: During calculation and allocation of control blocks (allocated in quantities of doubleword), the count of words in control blocks was not a double-word multiple.
Action: Submit an SPR with the dump. RO pOints to Memory Descriptor (MD).
052002,

Divide operation set overflow

FACILITY: SINI
Explanation: During allocation of control-blocks (set as 80 percent of available Control memory), a
divide operation set the PSW Overflow bit.
Action: Submit an SPR with a dump.
052003, Multiply operation set overflow
FACILITY: SINI
Explanation: During allocation of control blocks (set as 80 percent of available Control memory), a
multiply operation set the PSW Overflow bit.
Action: Submit an SPR with a dump.
061001,

XCALL stack corrupted

FACILITY: DIAGINT
Explanation: The DDUSUB transfer routines use a stack allocated from common pool for XCALLs
(cross-address space calls) from the Disk Server. The low word of this stack is Initialized to a special
value which should never change. This crash occurs when the routine DDUTIO is called. The low
word of the stack contains a different value than the initialization value. The most probable cause is
corruption by the process running.
Action: Submit an SPR with the crash dump. Note the diagnostics or utilities running at the time of
the crash.

8-40
EXCEPTION CODES AND MESSAGES

062001,

Process does not have windows declared

FACILITY: SUBLlB, ERTYP
Explanation: A process that requested an out-of-band error log be Issued via the ERTYP$ service In
SUBLIB does not have windows declared in its Process Control Block (PCB) declaration. A Window
set Is required to use this service.
Action: Submit an SPR with a dump.

C-1
HSC GENERIC ERROR LOG FIELDS

HSC GENERIC ERROR LOG FIELDS
C.1

HSC GENERIC ERROR LOG FIELDS

Some fields described on HSC console message printouts are generic, regardless of error type.
The following example is a typical printout of the error log fields. Table C-l describes the error fields.
ERROR-S Bad Block Replacement (Success)
Command Ref f
OA66000D
77.
RA81 unit f
Err Seq f
166.
Format Type
09.
Error Flags
80
Event
002B
ERROR-I End of Error

Table C-1

Generic Error Log Fields

Field

Description

ERROR-x

The x represents the severity level of the error message. Severity levels are E for error,
S for success, W for warning, I for informational, and F for fatal. What follows is the
English version of the error message describing the event code, date, a..'1d time.

Command Ref #

This number, in hexadecimal, is the MSCP command number that caused the error
reported, or is zero if the error does not correspond to a specific outstanding command.

Err Seq #

This number, in decimal, is the sequence number of this error log message since the last
time the MSCP server lost context, or is zero if the MSCP server does not implement
error log sequence numbers.

Error Flags

This number, in hexadecimal, indicates bit flags, collectively called error log message
flags, used to report various attributes of the error. Refer to Table C-2 for a description
of the error flags.

Event

This number, in hexadecimal, identifies the specific error or event being reported by
this error log message. This code consists of a five-bit major event code and an II-bit
subcode. The event codes and what they mean are listed in Table C-3.

C.2 HSC ERROR FLAGS
Table C-2 is a list of error flags that can be set. The first column is the bit number that is set. The
second column is the bit mask hex number. The third column is the format description of the error
flag.

C-2
HSC GENERIC ERROR LOG FIELDS

Table C-2

Error Flags

Bit
Number

Bit Mask
Hex

Format Description

If set, the operation causing this error log message has successfully completed. The

error log message summarizes the retry sequence necessary to successfully complete
the operation.
6

If set, the retry sequence for this operation continues. This error log message reports

the unsuccessful completion of one or more retries.
5

This is MSCP-specific. If set, the identified logical block number (LBN) needs
replacement.

This is MSCP-specific. If set, the reported error occurred during a disk access
initiated by the controller bad block replacement process.

If set, the error log sequence number has been reset by the MSCP server since the

last error log message sent to the receiving class driver.

C.3 MSCPITMSCP STATUS OR EVENT CODES
Event codes are values reported to error logs and are equivalent to each status code.
The following table is a sequential list of all known MSCP and TMSCP event codes. Each event code
cross references to an error description. The first column is the event code number in hexadecimal.
The second column references the class of error. The third column is the expanded description that
matches the event code.

Table C-3

MSCPITMSCP Status or Event Codes

Event
Code Hex

Class

Description

0000

Success

Nonnal.

000 I

Invalid Command

Invalid message length.
Other invalid command suhcode values should be referenced as
follows (note that this is combined with the status code):
offset * 256. + code
offset * 256. is the command message and offset value in decimal
for the field in error.

+ code is the symbol for the invalid command status code.
0002

Command Aborted

Command aborted.

0003

Unit Omine

Unit unknown or online to another controller.

0004

Unit Available

Unit available.

C-3
HSC GENERIC ERROR LOG FIELDS

Table C-3 (Cont.)

MSCPITMSCP Status or Event Codes

Event
Code Hex

Class

Description

0007

Compare Error

Used only as an event code when the error occurs during a
Read-Compare or Write-Compare operation.

0008

Data Error

Disk-Sector was written with Force Error modifier.
Tape-Long gap encountered.

0009

Host Buffer Access Error

Cause not available.
The controller was unabJe to access a host buffer to perform a
transfer and has no visibility into the cause of the error.

OOOA

Controller Error

Reserved for host-detected command timeout logging.
This error is never reported by a controller.

OOOC

Shadow Set Status Has
Changed

Disk-Shadow set status has changed.
Tape-Formatter error.

OOOD

BOT Encountered

BOT encountered.

OOOE

Tape Mark Encountered

Tape mark: encountered.

0010

Record Data Truncated

Record data truncated, data transfer operation.

0013

LEOT Detected

LEOT detected.

0014

Bad Block Replacement

Bad block successfully replaced.

0020

Success

Disk-Spindown ignored. (Status only subcode.)
Tape-Unload ignored.

0023

Unit Offline

Disk-No volume mounted or drive disabled via RUN/STOP
switch. Unit is in known substate. (Status only subcode.)
Tape-No media mounted, disabled via switch setting, or online to
another controller.

002A

Controller Error

SERDES overrun or underrun error.
Either the drive is too fast for the controJ)er, or more typically, a
controller hardware fault has prevented controller microcode from
keeping up with data transfer to or from the drive.

002B

Disk Drive Error

Drive command timeout.
For SDI drives, the controller timeout expired for either a level
2 exchange or the assertion of Read/Write Ready after an Initiate
Seek.

C-4
HSC GENERIC ERROR LOG FIELDS

Table C-3 (Cont.)

MSCPITMSCP Status or Event Codes

Event
Code Hex

Class

Description

0034

Bad Block Replacement

Block verified good-not a bad block.

0035

Media Loader

Loader command timeout.
The key length is too short for the specified key type.

0040

Success

Still connected. (Status only subcode.)

0043

Unit Offline

Unit is inoperative. (Status only subcode.)
For SOl drives, the controller has marked the drive inoperative due
to an unrecoverable error in a previous level 2 exchange, the drive
Cl flag is set or the drive has a duplicate lUlit identifier.

0044

Unit Available

Shadow set copy in progress. (Status only subcode.)

0048

Disk Data Error

Invalid header.
The subsystem read an invalid or inconsistent header for the
requested sector. For recoverable errors, this code implies a retry
of the transfer read or a valid header. For unrecoverable errors,
this code implies the subsystem attempted nonprimary revectoring
and determined the requested sector was not revectored. (Ac; an
example, the ReT indicates the sector is not revectored.) Causes
of an invalid header include header mis-sync, header sync timeout,
and an unreadable header.

0049

Host Buffer Access Error

Odd byte count.

004A

Controller Error

EDC error.
The sector was read with correct or correctable ECC and an
invalid EDC. A fault probably exists in the ECC logic of either
this controller or the controller that last wrote the sector.
This can also be caused by any K module (including the K.ci)
writing bad EDC into Data memory.

004B

Disk Drive Error

Controller-detected transmission error.
For SOl drives, the controller detected an invalid framing code or
a checksum error in a Level 2 response from the drive.

0054

Bad Block Replacement

Replacement failure-REPLACE command or its analogue failed.

0055

Media Loader

Controller-detected transmission error.
The controller does not implement the specified key type.

0068

Disk Data

Data sync not found (data sync timeout).

0069

Host Buffer Access Error

Non-Existent Memory error.

C-5
HSC GENERIC ERROR LOG FIELDS

Table C-3 (Cont.)

MSCP/TMSCP Status or Event Codes

Event
Code Hex

Class

Description

006A

Controller Error

Inconsistent internal controi structure.
A high-level check detected an inconsistent data structure. For
example, a reserved field contained a nonzero value, or the value
in a field was outside its valid range. This error almost always
implies the existence of a microcode or hardware problem.

006B

Disk Drive Error

Positioner error (mis-seek).
The drive reported a seek operation was successful, but the
controlJer determined the drive had positioned itself to an incorrect
cylinder.

0074

Bad Block Replacement

Replacement failure-inconsistent RCI'.

0075

Media Loader Error

Controller-detected protocol error.

0080

Success

Duplicate unit number. (Status only subcode.)

0083

Unit Offline

Duplicate unit number. (Status only subcode.)

0084

Shadowing Unit Available

No members in ,shadow set.
An online command was addressed to a virtual unit of an existing
sb-adow set fr-om w-lHcb all members h-avebeen removed.

0085

Media Format (Shadowing)
Error

Characteristics or protection mismatch for shadow member.

0088

Disk Data Error

Correctable error in ECC field.
A transfer encountered a correctable error where only the ECC
field was affected. All data bits were correct, but a portion of the
ECC field was incorrect. The severity of the error (the number of
symbols in error) is unknown. If the number of symbols in error
is known, an n symbol ECC error subcode should be returned
instead.

0089

Host Buffer Access Error

Host memory parity error.

008A

Controller Error

Internal EDC error.
A low-level check detected an inconsistent data structure. For
example, a microcode-implemented checksum or veI1ical parity
(hardware parity is horizontal) associated with internal sector data
was inconsistent. This error usually implies a fault in the memory
addressing logic of one or more controller processing elements.
It can also result from a double bit error or other error exceeding
the error detection capability of the controller hardware memory
checking circuitry.

oo8B

Disk Drive Error

Lost Read/Write Ready during or between transfers.

C-6
HSC GENERIC ERROR LOG FIELDS

Table C-3 (Cont.)

MSCPITMSCP Status or Event Codes

Event
~ode Hex

Class

Description
For SDI drives, Read/Write Ready drops when the controller
attempts to initiate a transfer or at the completion of a transfer
with Read/Write Ready previously asserted. This usually results
from a dri.- .!-detected transfer error, where additional error log
messages containing the drive":detected error subcode may be
generated.

0094

Bad Block Replacement

Replacement failure-drive access failure.
One or more transfers specified by the replacement algorithm
failed.

OOA5

Media Fonnat Error

Disk-Not formatted with 512-byte sectors. (Status only subcode.)
The disk FCf indicates it is fonnatted with 576-byte sectors,
although either the controller or the drive support only 512-byte
sectors.
Tape-Block mode device not formatted for tape operations.

00A9

Host Buffer Access Error

Invalid page table entry.

OOAA

Controller Error

LESI adapter card parity error on input (adapter to controller).

OOAB

Disk Drive Error

Drive clock dropout.
For SDI drives, either data or state clock was missing when it
should have been present. This is usually detected by means of a
timeout.

00B4

Bad Block Replacement

Replacement failure, no replacement block available.
Replacement was attempted for a bad hlock, but a replacement
block could not be allocated. For example, the volume's RCf is
full.

OOC5

Disk Media Format Error

Disk not formatted or FCf corrupted. (Status only subcode.)
The disk FCf indicates the disk is not formatted in either 512- or
576-byte mode.

OOC9

Host Buffer Access Error

Invalid buffer name.
The key in the buffer name does not match the key in the buffer
descriptor, the V bit in the buffer descriptor is clear, or the index
into the buffer descriptor table is too large.

OOCA

Controller Error

LESI adapter card parity error on output (controller to adapter).

OOCB

Disk Drive Error

Lost Receiver Ready for transfer.

C-7
HSC GENERIC ERROR LOG FIELDS

Table C-3 (Cont.)

Event
Code Hex

MSCPITMSCP Status or Event Codes

Class

Description
For SDI drives, Receiver Ready was negated when the controller
attempted to initiate a transfer or did not assert at the completion
of a transfer. This includes all cases of the controller timeout
expiring for a transfer operation (Levell real-time command).

0004

Bad Block Replacement

Replacement failure, recursion failure.
Two successive RBNs were bad.

OOE8

Data Error

Disk-Uncorrectable ECC error.
A transfer without the Suppress Error Correction modifier
encountered an ECC error exceeding the correction capability
of the subsystem error correction algorithms, or a transfer with the
Suppress Error Correction modifier encountered an ECC error of
any severity.
Tape-Unrecoverable read error.

OOE9

Host Buffer Access Error

Buffer length violation.
The number of bytes requested in the MSCP or TMSCP command
exceeds the buffer length as specified in the buffer descriptor.

OOEA

Controller Error

OOEB

Disk Drive Error

~..!!I---'

LESI adapter cant cable in place notasserteQ.
or-.fL Q , / I tJ ? ~f- 1-06Drive-detected error.
f-l(~ (? v tJ f 5 £i '-

--- /

'D (2\

For SDI drives, th~ntroller received a get status or unsuccessful
response with EL ·set, or the controller received a response with
the DR flag set and it does not support automatic diagnosis for that
drive type.

0100

Success

Already online. (Status only subcode.)

0103

Unit Omine

Unit disabled by field service or diagnostic. (Status only subcode.)
For SDI drives, the drive DO flag is set.

0105

Disk Media Format Error

R CT corrupted.
The RCT search algorithm encountered an invalid RCT entry. The
subcode may be returned under the following conditions: during
replacement of a block, revectoring a faulty block, and when a unit
is brought online.

0106

Write-Protected

Unit is data safety write-protected. (Status only subcode.)

0108

Disk Data Error

One-symbol ECC error.
A transfer encountered a correctable ECC error with the specified
number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

C-8
HSC GENERIC ERROR LOG FIELDS

Table C-3 (Cont.)

MSCP/TMSCP Status or Event Codes

Event
Code Hex

Class

Description

0109

Host Buffer Access Error

Access control violation.
The access mode specified in the buffer descriptor is protected
against the PROT field in the PTE.

OIOA

Controller Error

Controller overrun or underrun.
The controller attempted to perfonn too many concurrent transfers,
causing one or more of them to fail due to a data overrun or
underrun.

010B

Disk Drive Error

Controller-detected pulse or state parity error.
For SDI drives, the controller detected a pulse error on either the
state or data line, or the controller detected a parity error in a state
frame.

0125

Disk Media Format Error

No replacement block available.
Replacement of a faulty block wa~ attempted, but a replacement
block could not be allocated (i.e., the RCT is full). This subcode
may be returned during actual replacement and when an interrupted
replacement is completed as part of bringing a unit online.

0128

Disk Data Error

Two-symbol ECC error.
A transfer encountered a correctable ECC error with the specified

number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

012A

Controller Error

Controller memory error.
The controller detected an error in an internal memory, such a.~ a
parity error or nonresponding address. This subcode applies only
to errors not affecting the ability of the HSC to properly generate
end and error log messages. Errors affecting end and error log
messages are not reported via MSCP. For most controllers, this
subcode is returned only for controller memory errors in data or
buffer memory and noncritical control structures. If the controller
has several such memories, the specific memory involved is
reported as part of the error address in the error log message.

012B

Disk Drive Error

Drive-requested error log (EL bit set).

0145

Disk Media Format Error

No multicopy protection.
All but one copy of a block in a multicopy structure are bad. The
disk should be reformatted or replaced at the earliest convenient
time.

0148

Disk Data Error

Three-symbol ECC error.

C-9
HSC GENERIC ERROR LOG FIELDS

Table C-3 (Cont.)

Event
Code Hex

MSCP/TMSCP Status or Event Codes

Class

Description
A transfer encountered a correctable ECC error with the speciiJed
number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

014A

Controller Error (Shadowing)

Insufficient resources.
The controller is unable to honor a request to create a shadow set
or to add an additional member to an existing shadow set. This
is due to the lack of internal resources to support the new entity.
This subcode must not be used for any other purpose.

014B

Disk Drive Error

Controller-detected protocol error.
For SDI drives, a level 2 response from the drive had correct
framing codes and checksum but was not a valid response within
the constraints of the SI protocol. The response had an invalid
opcode, was an improper length, or was not a possible response in
the context of the exchange.

0168

Disk Data Error

Four-symbol ECC error.
A transfer encountered a correctable ECC error with the specified
number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

016A

Controller Error

PU transmission buffer parity error.

016B

Disk Drive Error

Drive faiied initialization.
For SDI drives. the drive clock did not resume following a
controller attempt to initialize the drive. This implies the drive
encountered a fatal initialization error.

0188

Disk Data Error

Five-sym bol ECC error.
A transfer encountered a correctable Eee error with the specified
number of ECe symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

018B

Disk Drive Error

Drive ignored initialization.
For SDY drives, the drive clock did not cease following a controller
attempt to initialize the drive. This implies the drive did not
recognize the initialization attempt.

01A8

Disk Data Error

Six-symbol ECC error.
A transfer encountered a correctable ECC error with the specified
number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

01AB

Disk Drive Error

Receiver Ready collision.

C-10
HSC GENERIC ERROR LOG FIELDS

Table C-3 (Cont.)

Event
Code Hex

MSCP/TMSCP Status or Event Codes

Class

Description .
For SDI drives, the controller attempted to assert its Receiver
Ready when the Receiver Ready of the drive was still asserted.

OlC8

Disk Data Error

Seven-symbol ECC error.
A transfer encountered a correctable ECC error with the specified
number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

OlCB

Disk Drive Error

Response overflow.
A drive sent back more frames than the reception buffer could
hold. This can be caused by a hung drive microdiagnostic or a
malfunctioning K.sdi.

OlE8

Disk Data Error

Eight-symbol ECC error.
A transfer encountered a correctable ECC error with the specified
number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

0200

Success

Still online.

0203

Unit Offline

Exclusive use.

0208

Disk Data Error

Nine-symbol ECC error.
A transfer encountered a correctable ECC error with the specified
number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

0220

Success

Still online, unload ignored.

0228

Disk Data Error

Ten-symbol ECC error.
A transfer encountered a correctable ECC error with the specified
number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

0248

Disk Data Error

Eleven-symbol ECC error.
A transfer encountered a correctable ECC error with the specified
number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

0268

Disk Data Error

Twelve-symbol ECC error.
A transfer encountered a correctable ECC error with the specified
number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

0288

Disk Data Error

Thirteen-symbol ECC error.

C-11
HSC GENERIC ERROR LOG FIELDS

Table C-3 (Cont.)

Event
Code Hex

MSCP/TMSCP Status or Event Codes

Class

Description
A transfer encountered a correctable ECC error with the specified
number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

02A8

Disk Data Error

Fourteen-symbol ECC error.
A transfer encountered a correctable ECC error with the specified
number of BCe symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

02C8

Disk Data Error

Fifteen-symbol ECC error.
A transfer encountered a correctable ECC error with the specified
number of ECC symbols in error. The number of symbols in error
roughly corresponds to the severity of the error.

0400

Success

Disk-Incomplete replacement. (Status only subcode.)
Tape-EOT encountered.

0404

Unit Available

Already in use. (Status only subcode.)

044B

Tape Drive

Drive error.
-ControHerre-try limit exhausted.

0800

Success

Invalid RCf. (Status only subcode.)

1000

Success

Read only volume fonnat. (Status only subcode.)

1006

Write-Protected

Unit is software write-protected. (Status only subcode.)

2006

Write-Protected

Unit is hardware write-protected. (Status only subcode.)

F3AA

Controller Error

Unknown K.sti error.

FCAA

Controller Error

Word rate clock timeout.
The K.sti detected the loss of clocks from a drive during a transfer.

FCEA

Controller Error

Receiver Ready not asserted at start of transfer.
The HSC is ready to start a transfer by sending the fonnatter a
Levell command, and the fonnatter does not have Receiver Ready
asserted.

FD2A

Controller Error

Data ready timeout.
This controller did not detect data ready from the formatter within
5 ms after sending it a Level 1 command.

FD6A

Controller Error

Acknowledge not asserted at start of transfer.

C-12
HSC GENERIC ERROR LOG FIELDS

Table C-3 (Cont.)

Event
Code Hex

MSCP/TMSCP Status or Event Codes

Class

Description
The HSC is ready to start a transfer by sending the fonnatler a
Level 1 command, and the fomlatter does not have Acknowledge
asserted.

FDEC

Tape Fonnatter

Could not get extended drive status.

FEOC

Tape Fonnatter

Could not get fonnatter summary status while trying to restore
tape position.

FE2A

Controller Error

Record EDC error.
On a read from tape operation the EDC calculated by the K.sti did
not match the EDC generated by the tape formatter.

FE2B

Tape Drive

Could not set byte count.

FE4B

Tape Drive

Could not write tape mark.

FE6B

Tape Drive

Could not set unit characteristics.

FE8A

Controller Error

Lower Processor timeout.
The Upper Processor in the K.sti detected the Lower Processor had
stopped and restarted it.

FE8B

Tape Drive

Unable to position to before L_EOT.

FEAB

Tape Drive

Rewind failure.

FECB

Tape Drive

Could not complete online sequence.

FEEB

Tape Drive

Erase gap failed.

FFOB

Tape Drive

ERASE command failed.

FFOC

Tape Fonnatter

TOPOLOGY command failed.

FF31

Tape Drive Position Lost

Retry limit exceeded while attempting to restore tape position.

FF68

Tape Data

Formatter retry sequence exhausted.

FF6A

Controller Error

Lower Processor error.
A bit was set in the Lower Processor error register. B its included
in the Lower Processor error register are Data bus NXM, data
SERDES overrun, Data bus overrun, Data bus par err, data pulse
missing, and sync real-time par err.

FF6B

Tape Drive

Tape drive requested error log.

FF6C

Tape Fonnatter

Fonnatter requested error log.

FF71

Tape Drive Position Lost

Fonnatter-detected position lost.

C-13
HSC GENERIC ERROR LOG FIELDS

Table C-3 (Cont.)

MSCPITMSCP Status or Event Codes

Event
Code Hex

Class

Description

FF88

Tape Data

Controlier transfer retry limit exceeded.

FF8A

Controller Error

Buffer EDC error.
The K.sti detected an EDe error on the Data Buffer it read from
memory on a Write operation.

FFA8

Tape Data

Host requested retry suppression on a K.sti-detected error.

FFAA

Controller Error

Data overflow due to pipeline error.
No Data Buffers in HSC Data memory were available when the
K.sti needed one during a data transfer.

FFC8

Tape Data

Reverse retry currently not supported.

FFCB

Tape Drive

Could not position for (fonnatter) retry.

FFCC

Tape Fonnatter

Cannot clear fonnatter errol'S.

FFDl

Tape Drive Position Lost

Fonnatter and HSC disagree on tape position.

FFE8

Tape Data

Host requested retry suppression on a fonnatter-detected error.

FFEB

Tape Drive

Cannot clear drive errors.

FFEC

Tape Fonnatter

Could not get fonnatter summary status during transfer error
recovery.

FFFl

Tape Drive Position Lost

ControHer-detected position iost.

0-1
INTERPRETATION OF STATUS BYTES

D
INTERPRETATION OF STATUS BYTES
0.1

INTRODUCTION'

This appendix lists all possible codes each K (e.g. K.ci or data channel) can generate after detecting a
fatal error. Only K..,detected errors are listed here.
When a K detects a fatal error, it puts a code in its status register and perfonns a level 7 Control bus
interrupt to the P.io. This interrupt causes the HSC to trap through location 134 and crash. The crash
message contains the status codes from all Ks in the Status of requestors (1-9): field.
The following shows a printout example from a K-detected error. In this case, as in many others, the
crash was not caused by the K but was detected by the K which forced the crash. Section D.2 explains
this crash is detail. For additional explanations of the fields in the crash message, refer to Appendix B.

-* SUBSYSTEM EXCEPTION *-

V# Y10B
at 18-Jan-1986 01:15:14.50 up

User
PC: 0027360 caused by (134
PSW: 140000

HSC70 HSC002
0 00:08:46.20

'~fftG£ <6- 5D

KBCTRL active, PCB addr = 102636
RO-R5:
024302

047632

000020

047626

0000000

141404

Kernel SP: 000774
Kernel Stack:
005046 000004 053354 046022 001012 050476 050476 000000
047062 047466 047466 000000 047264 000000 055352 000000
User SP: 023346
User Stack:
052525 052525 025252 025252 025252 025252 025252 025252
025252 025252 025252 025252 025252 025252 025252 025252
KPAR(0-7) :
000440 000640 001040 001440 002040 001240 000240 177600
KPDR (0-7) :
077506 077506 177506 077506 077406 077506 077506 077506
UPAR(0-7) :
000440 000640 001040 001440 002040 001240 000240 177600
UPDR(0-7) :
007406 007406 177406 007406 007406 007406 007406 100016
MMSR(0-2): 000017 000020 037654
Window index reg: 000015

0-2
INTERPRETATION OF STATUS BYTES

Window Bus Reg: 140105
WADR(0-7) :
160004 161004 162004 163004 164004 165004 166034 167034
Translated WADR(0-7) :
001401 001401 001401 001401 001401 001401 001407 001607
Error regs: 170024

000077

_ _........ of requestors (1-9):
000002 000002 000377 000377 000377 000377 000377 000203
(PC- 6)

(PC):

104002 012600 000003 011505
Control area for slot '000001
Control area address: 022010
Register area contents:
Q 000000
o 000000
I 100307
z,. 040003
? 104000
4 140143
oj 100007
b 000552
'/ 000200
/0 012002
/1 000000
,Z 000533
I 3 104000
; "t 000401

17 022000
if;

OOOQO~

£E-1..0060003
I 7 000001

004572
000003
017176
000003
000063
000150
000000
000000
000372
040003
002501
002431
000000
000000
000000

SIlT/us -

0-3
INTERPRETATION OF STATUS BYTES

0.2 EXAMPLE EXAMINATION
Notice the third line of example states the crash was caused by (134) Kint. The 134 indicates a K
detected a fatal problem and interrupted the P.ioj with a level 7 interrupt.
In this crash, requestor number 1 (the K.ci) status shows a 000177. The K.ci detected a fatal condition.
The two digits in the status code are 77 (from the 000177 failure code).
Table 0-1 provides additional information regarding status code 77. The description of this error
indicates the HSC received a HOST CLEAR command from a host node. The description for the 77
status also shows that the node number of the host which sent the HOST CLEAR is found in R17.
To find Rt7, look at the Register area contents: field on the second page of the example. The
first entry in the register area contents is always the Q register from the K. The Q register contains
important information for some crashes. The second entry is RO. In the example, count in octal up to
R17 (remember the first entry is the Q register). The contents of R17 are 000001. Many of the error
descriptions in the following tables indicate additional information exists in one of these registers.
Notice ot.her entries below R17 in the register area contents. In the K.sdi, K.sti, and K.si register areas,
these other entries are RAMO through RAMI7, and they sometimes contain important information. On
the K.ci, these entries are not significant for troubleshooting crash messages.

D.3 ANALYZING K-DETECTED FAILURE CODES
The following sections aid field service in analyzing the K-detected failure codes through use of the
status code tables. This appendix contains one status code table for each type of K.
•

Table 0-1 describes the K.ci status codes and applies only to requestor number 1.

•

Table 0-2 describes the K.sd-i/K.si status codes.

•

Table 0-3 describes the K.sti/K.si status codes.

The use of the status code tables requires information about the type of requestor involved. In order
to determine which requestor detected the error, check the Status of requestors (1-9): field in the crash
message. This field shows the status register contents of all requestors present in the subsystem.
NOTE

The registers referred to in this appendix are not general registers, but the internal K registers.
All status codes followed by an asterisk (*) are hardware-detected errors. More detailed
information for these errors is found in the appropriate sequencer error register.
The nonnal operational status codes for requestors are:
001 for a K.ci
002 for a K.sdi/K.si
203 for a K.sti/K.si
377 means no requestor is in the slot
Any value other than a OOt, 002, 203, or 377 means the K detected an error. Because the K.ci
is always requestor 1, a K.ci-detected error always shows in the far left position in the Status of
requestors (1-9): field of the message. In any other position, the type of requestor must be determined.
Count over the Status of requestors (1-9): field to the status contents showing an error (this is the
requestor number). When the HSC reboots, type SHOW REQUESTOR at the HSC> prompt to see
whether the requestor detecting the error is a K.sdi, K.sti, or K.si. Find the number of the data channel
that found the error in the displayed response. This display shows whether that requestor number is
either a K.sdi, K.sti, or K.si.

D-4
INTERPRETATION OF STATUS BYTES

NOTE

If the HSC is not operational or the requestor in question fails initialization self tests, check the
module utilization label above the card cage to determine whether the involved requestor number
is a K.sdi, K.sti, or K.si.
Tables in this appendix consider only the rightmost two octal characters in failure code. Use the
appropriate table (dependent upon requestor type) to find the meaning of the status code.
NOTE

"(See NOTE.)" appears in several places in the following tables. In each table, this information
appears at the end of that table.
Table 0-1

Status Code
(Octal)
00

K.ci Status Bytes

Description
Two conditions cause failure of the 2911 sequencer test upon powerup or reinitialization.
In one case, the requestor sent status back to the pjo while lnit was asserted. In the
other case, the sequencer had already released the Init signal but the sequencer failed to
reach the point in its code where it could change the status bits.
A common reason for thi~ status code is from an HSC false power fail crash dump. In
this type of crash dump (lOT through 20), all requestors present report a 00 status code.

290 1 ALU test failed upon powerup or reinitialization.

Data bus (DBUS) test failed upon powerup or reinitialization.

Control bus (CBUS) test failed upon powerup or reinitialization.

CROM test failed upon powerup or reinitialization.

K.pli RAM test failed upon powerup or reinitialization.

PLI interface test failed upon powerup or reinitialization.

Packet buffer test failed upon powerup or reinitialization.

LINK board test failed upon powerup or reinitialization.

Control bus/memory error occurred during a lock cycle while the K.ci was attempting to
locate the K-Init packet in Control memory upon powerup or reinitialization.

K.ci could not find a properly formatted K-Init packet in Control memory after
completing powerup/lnit diagnostics.

An error was detected by the upper (control) sequencer. While attempting to update the
next buffer pointer in an FRB, the pointer was found to be zero (illegal). Rl1 contains
the FRB address.
An error was detected by the upper (control) sequencer. (See NOTE.)

An error was detected by the upper (control) sequencer. The control stream found
a structure on its own work queue which is not an fTh.1B or FRB. Rll contains the
structure address.

0-5
INTERPRETATION OF STATUS BYTES

Table 0-1 (Cont.)

K.ci Status Bytes

Status Code
(Octal)

Description

An error was detected by the upper (controi) sequencer. "roUe constructing a siot
(SNDDAT, REQDAT) from an FRB, the FRB address was found to be zero (illegal).
RI2 contains the slot address.
An error was detected by the upper (control) sequencer. (See NOTE.)

An error was detected by the upper (control) sequencer. A buffer allocate request was
initiated without sufficient buffers on the allocated queue in the control area to satisfy
the request. R II contains the FRB address.

An error was detected by the upper (control) sequencer. The queue head for an allocated
send buffer was zero.

23 *

An error was detected by the upper (control) sequencer. (See NOTE.)

An error wac; detected by the lower (control) sequencer. The lower sequencer
encountered an inconsistent internal data structure. R2 contains the message slot address.

An error was detected by the lower (control)'sequencer. During the RTNDAT routine,
the lower sequencer finds a zero (illegal) FRB address.

An error was detected by the lower (control) sequencer. The lower sequencer has
received a packet from a node with a node ID greater than 63. R7 contains the node
number.

An error was detected by the lower (control) sequencer. This error occurs when the
lower sequencer polling loop calls a routine which adds or removes Big Message Block
(BMB) pointers to or from the B!v1B chain, if the queue that is supposed to contain these
pointers is empty.

An error was detected by the lower (control) sequencer. This error occurs when the
lower sequencer detennines that BMBs need to be returned to the free BMB pool and
during a consistency check finds no BMBs to return. R2 contains the message slot
address.

31 *

An error was detected by the upper (control) sequencer. (See NOTE.)

An error was detected by the upper (control) sequencer. While attempting to transmit
over a connection, the upper sequencer found an incarnation number of zero (invalid) in
the Connection Block structure. Rll contains the HMB address and RI4 contains the
CB address.

33 through 41 *

An error was detected by the upper (control) sequencer. (See NOTE.)

An error was detected by the upper (control) sequencer. A hardware error was detected
following a block move to Control memory. RIO contains the Upper Processor error
register contents. RI6 contains the last Control memory address in the block that was
moved.

43 *

An error was detected by the upper (control) sequencer. A hardware error wac; detected
following a block move out of Control memory. RIO contains the Upper Processor error
register contents. R16 contains the last Control memory address in the block that was
moved

D--6
INTERPRETATION OF STATUS BYTES

Table 0-1 (Cont.)

Status Code
(Octal)

K.ci Status Bytes

Description
An error was detected by the upper (control) sequencer. A hardware error was detected
following a Control memory Receive operation. RIO contains the Upper Processor error
register contents. RI6 contains the Control memory address of the item received. RI7
contains the Control memory address of the queue head.

45 and 46 *

An error was detected by the upper (control) sequencer. (See NOTE.)
An error was detected by the upper (control) sequencer. A hardware error was detected
during a Downcount operation. RIO contains the Upper Processor error register value.
RI7 contains the counter address.
An error was detected by the upper (control) sequencer. A hardware error was detected
while de-queueing a Control memory item from a scratchpad list. RIO contains the
Upper Processor error register contents. Rll contains the Control memory address of the
item.

51 *

An error was detected by the upper (control) sequencer. A hardware error wa~ detected
while internalizing an FRB. RIO contains the contents of the Upper Processor error
register, Rll contains the FRB address and R14 contains the CB address. The Q register
contains the work queue index.

An error was detected by the upper (control) sequencer.

Either a consistency problem was found with the scratchpad queue or an attempt was
made to send to a queue at address zero (illegal address).
53 through 55 *

An error was detected by the upper (control) sequencer. (See NOTE.)

56 through 71 *

An error was detected by the lower (control) sequencer. (See NOTE.)
An error was detected by the lower (control) sequencer. This error occurs while the
Lower Processor is trying to link a BMB on the BMS free chain. RIO contains the
Lower Processor error register contents. R5 contains the BMB Data memory address.

73 *

An error was detected by the lower (control) sequencer. A hardware error was detected
during a BMB list operation. RIO contains the Lower Processor error register contents.
R5 contains the BMB Data memory address.
An error was detected by the lower (control) sequencer. A hardware error was detected
during a BMB list operation. RIO contains the Lower Processor error register contents.
R5 contains the BMB Data memory address.

75 *

An error was detected by the lower (control) sequencer. (See NOTE.)

An error was detected by the upper (control) sequencer. While copying data from an
HMB to a message slot, the upper sequencer found the byte count of the HMB was
larger than the slot capacity. R12 contains the slot address and RI7 contains the text
length.

An error was detected by the upper (control) sequencer. A host clear sequence has been
received. RI7 contains the address of the issuing node number.

NOTE

The sequencers access Control memory several times before checking for a hardware error. Thus,
to help determine the particular cause of the error, the sequencer saves the contents of the error

0-7
INTERPRETATION OF STATUS BYTES

register present at the time of the error check in RIO (octal). The contents of RIO are visible
within the crash dump and can help in narrowing the error possibilities.
The following lists show the bits available from both the Upper and Lower Processor error registers.
Those bits marked with an asterisk (*) may cause a crash.
•

Upper Processor error register:

=Even/odd bit Control memory address
Bits 3, 2, 1 = CCYCLE 2, 1, 0
* Bit 4 = Control bus error (illegal cycle)

Bit 0

* Bit 5 = Control bus NXM
* Bit 6 = Control data parity error
* Bit 7 = Instruction (CROM) parity error
* Bit 8 = Scratchpad parity error
Bit 9 = PLI parity error
Bits 10 through 15 indicate K.ci hardware revision level
•

Lower Processor error register:
Bit 0 = Data memory address bit 16

=Data memory address bit 17
Bit 2 = Data memory NMA
Bit 1

* B-it 5 =. Data btls NXM
* Bit 6 =Data memory parity error
* Bit 7 =Data memory overrun
* Bit 8 = SCiatchpad pa.t;ty error
* Bit 9 = PLI parity error
Bits 10 through 15 indicate K.ci hardware revision level

D-8
INTERPRETATION OF STATUS BYTES

Table 0-2

K.sdi/K.si Status Bytes

Status Code
(Octal)
00

Description
Two conditions cause failure of the 2911 sequencer test upon powerup or reinitiali7..3tion.
In one case, the requestor sent status back to the P.io while Init was asserted. In the
other case, the P.io had already released the Init signal but the sequencer failed to reach
the point in its code where it could change the status bits.
A common occurrence of this status code is from an HSC false power fail cmsh dump.
In this type of crash dump (lOT through 20), all requestors present report a 00 status
code.

2901 ALU test failed upon powerup or reinitialization.

Data bus (DBUS) test failed upon powerup or reinitialization.

Control bus (CBUS) test failed upon powerup or reinitialization.

PROM test failed upon powerup or reinitialization.

Scratchpad RAM test failed upon powerup or reinitialization.

R-S/Gen test failed upon powerup or reinitialization.

Partial SDI test failed upon powerup or reinitialization.

The K.sdi/K..si encountered a Control bus/memory problem while searching for the
K-Init packet in Control memory.

After completing powerup/lnif diagnostics, the K.sdi/K..si could not find a properly
formatted K-Init packet in Control memory.

While trying to write the microcode version into the control area at address R7+44 (R7
is base address), the upper sequencer encountered a Control bus error. Rll contains the
contents of the upper error register. (See NOTE.)

The Upper Processor tried to advance the buffer descriptor pointer when the old value of
the pointer is zero (illegal).

While attempting to read the block number (LBN) from a buffer descriptor in Control
memory, the Upper Processor encountered a hardware error. Rll contains the contents
of the upper error register. (See NOTE.)

17 through 30 *

The Upper Processor encountered an error while anempting to access Control memory.
Rll contains the Upper Processor error register contents. (See NOTE.)

This error occurs if, during transfer completion. a DRAT counter goes to zero and the
DRAT list head in the control area is not locked and not equal to the current DRAT
value.

32 through 42 *

The Upper Processor encountered an error while attempting to access Control memory.
Rll contains the Upper Processor error register contents. (See NOTE.)

This error occurs while processing an active DCB if the dialogue state indicator is not
locked (a value of 100000 is not in KS$DHD) and not valid (KS$IND does not contain
the values 0, I, 2, 3, OR4, or -1).

0-9
INTERPRETATION OF STATUS BYTES

Table 0-2 (Cont.)

Status Code
(Octal)

K.sdi/K.si Status Bytes

Description

The Upper Processor encountered an error while attempting to access Control memmy.
Rll contains the Upper Processor error register contents. (See NOTE.)

This error occurs if, after completing state 0 processing, the upper sequencer cannot find
a valid DCB opcode. (No valid state is present to go to next.)

46 through 55 *

The Upper Processor encountered an error while attempting to access Control memory.
Rll contains the Upper Processor error register contents. (See NOTE.)

74 through 76

The Upper Processor attempted to downcount a counter that was already at zero.

NOTE

The upper sequencer accesses Control memory several times before checking for a Control bus
error. Thus, to help determine the particular cause of the error, the upper sequencer saves the
contents of the error register present at the time of the error in Rll (octal). The contents of Rll
are visible within the crash dump and may help in narrowing the error possibilities.
The following list defines all the bits contained within the Upper Processor error register (value loaded
in Rll). Those bits that may cause a crash are denoted with an asterisk (*).
•

Upper Processor error register:
Bit 0 = Even/odd bit Control memory address
Bits 3, 2,1 = CCYCLE 2, 1,0

* Bit 4 = Control bus error (illegal cycle)
* Bit 5 = Control bus NXM
* Bit 6 = Control data parity error
* Bit 7 = Instruction (CROM) parity error
Bits 8 through 12 not used

* Bit 13 = Response pulse missing on SDI RD/RES Line (pulse error)
Bit 14 = Upper Processor RTCS clock present
Bit 15 = Parity error on RIDS Line

0-10
INTERPRETATION OF STATUS BYTES

Table 0-3

K.sti/K.si Status Bytes

Statll~ Code

(Octal)

Description

14 through 22 *

Control bus error. (See NOTE.)

During transfer completion, the buffer descriptor link word in the FRB was zero. RAM7
contains the Lower Processor status.

24 through 33 *

Control bus error. (See NOTE.) -

The Lower Processor has timed out on a Transfer operation and the Upper Processor
cannot restart it.

35 and 36 *

Control bus error. (See NOTE.) _

A software inconsistency. The STI state zero processing code was entered when the
drive state indicator was not zero.

State zero processing is complete. However, the next state (such as Send Levell frame
or Get Drive Status) is not specified. Thus, the state is undefined.

41 through 43 *

Control bus error. (See NOTE.)

While setting up a transfer, the next buffer deScriptor in the FRB was zero (no buffer
was there).

Attempted to downcount a counter that was already zero. Rl4 contains the FRS. R16
contains the counter minus one. R17 contains the address of the counter structure.

75 and 76 *

Control bus error. (See NOTE.1-- 6 N

NOTE

ON PflC~ I)

()N

pAt?£- / I

fltG£.

1.. i

N c-{ TiffS ~

In the following ~tatus codes, bit 7 is the parity bit. Parity is always odd for microdiagnostic
failures and is always even for functional code failures. Bit 6 is the error bit and is set for
microdiagnostic and functional code failures.
000

Two conditions cause failure of the 2911 sequencer test upon powerup or reinitiali1..ation.
In one case, the requestor sent status back to the P.io while Init was asserted. In the
other case, the sequencer had already released the Init signal but the sequencer failed to
reach the point in its code where it could change the status bits.
A common occurrence of this status code is from an HSC false power fail crash dump.
In this type of crash dump (lOT through 20), all requestors present report a 00 status
code.

103

Control bus (CBUS) test failed upon powerup or reinitialization.

106

Scratchpad RAM test failed upon powerup or reinitialization.

110

Partial STI test failed upon powerup or reinitialization.

112

The K.sti/K.si encountered a Control bus/memory problem while searching for the K-Init
packet in Control memory.

301

2901 ALU test failed upon powerup or reinitialization.

0-11
INTERPRETATION OF STATUS BYTES

Table 0-3 (Cont.)

K.sti/K.si Status Bytes

Status Code
(Octal)

Description

302

Data bus (DBUS) test failed upon powerup or reinitiaiization.

304

PROM test failed upon powerup or reinitialization.

307

SERDES test failed upon powerup or reinitialization.

313

After completing powerup/lnit diagnostics, the K.sti/K.si could not find a properly
formatted K-Init packet in Control memory.

~OTE

Upper Processor error register:
Bit 0 = Even/odd bit Control memory address
Bits 3, 2, 1 = CCYCLE 2, 1, 0

* Bit 4 = Control bus error (illegal cycle)

* Bit 5 = Control bus NXM
* Bit 6 = Control data parity error
* Bit 7 = Instruction (CROM) parity error
Bits 8 through 12 not used

* Bit 13 =Response pulse missing on SOl RD/RES Line (pulse error)
Bit 14 = Upper Processor RTCS clock present
Bit 15 = Parity error on RIDS Line

E-1

HSC REVISION MATRIX CHART

E
HSC REVISION MATRIX CHART
E.1

INTRODUCTION

This appendix lists the revision matrix charts for the HSC70, HSC50 (modified), and the HSC50.

E.1.1 HSC70 Revision Matrix Chart
Figure E-1 shows the revision status of all applicable HSC70 FRUs. An HSC70 must have all the
FRUs at a particular revision level in order to be supported.

m
~

'"T1

cC"

(rJ

REV

HSC70 - AA/CA

...a.

L0100 - 00

III (CI LINK)

o......

L0107 - YA

K.pli

L0108 - YA (HSC5X - BA)

K.sdi

0"
0"

:::s
3:
Q)

-.x"..,
o:::s-

(')

OESCR IPTION

::t

:tI
NUMBER

o
::D

L0108 - YB (HSC5X - CAl

K.sti

;::s.

L0109 - 00

PILA

LOlll - 00

P.ioj

m
<

REVISIONS

E2-ETCH

C - ETCH

01
C2

-..
-..
.

0- ETCH

Cl0 i---

E-ETCH

F-ETCH

C22

0- ETCH

Cl0

E-ETCH

F-ETCH

C23

.-.

0- ETCH

A - ETCH

LOl18

III (CI LINK)

LOl19

K.si

0- ETCH

5417764 - 01

BACKPLANE

C-ETCH

(')

»
~

.-.

C - ETCH

M.std2

:tI

----- C22 C23 C24 C25
..-

....
.

LOl17 - AA

.-.

C-ETCH

C23 C24 C25 C26

CX-1271B

Sheet 1 of 4

IREV A1

HSC70 - AA/CA
NUMBER

DESCR IPTION

REVISIONS

70 - 20033 - 03

STD PS ASSY - 120VAC IN

70 - 20184 - 01

OPT PS ASSY - 120VAC IN

30 - 24374 - 01

881A PWR CNTLR ASSY

70 - 23138 - 01

OCP ASSEMBLY

54 - 15286 - 01 * *

OCP

70 - 23129 - 01

FLOPPY DRIVE BKT ASSY

30 - 24962 - 01

RX33 DRIVE

EK - HSCMN - IN

INSTALLATION MANUAL

001

QX926 - H7

HSC70 SOFTWARE

V 100

BL - FH74X - DE

HSC70 OFFLINE DIAGS

---

------

--------...

V30a V370 V370+

---...

(J)

:::0

m
<
Ci)

oz
3:

:::0

o
J:
»

**THIS BREAKDOWN IS FOR FIELD SERVICE INFORMATION ONLY.
CX-1271B

Sheet 2 of 4

-n

ce'
e
'"'

HSC70 - AB/CB

.....I

"0
o

NUMBER

REV

All

III (CI LINK)

B-ETCH
C-ETCH

L0107 - YA

K.pli

L0108 - YA (HSC5X - BA)

K.sdi

L0108 - YB (HSC5X - CAl

K.sti

L0109 - 00

PILA

LOll1-00

P.ioj

I I

m
<

REVISIONS

DESCRIPTION
Dl

-..

..-

C - ETCH

D - ETCH

Cl0

~----

E ETCH

F-ETCH

C22

-----

D - ETCH

Cl0

E-ETCH

F-ETCH

C23
El

C - ETCH

D - ETCH

A - ETCH

LOl17 - AA

M.std2

LOl18

III (CI LINK)

LOl19

K.si

D - ETCH

5417764 - 01

BACKPLANE

C-ETCH

Dl
C2

(j)

-....

:::s

L0100 - 00

..-

»
~
C22 C23 C24 C25

..
..
· C23 C24 C25 C26
-

-..·

-Cl

CX-1271B
Sheet 3 of 4

REV

HSC70 - AB/CB

::J:

C/J

NUMBER

DESCRIPTION

70 - 20033 - 04

STD PS ASSY - 240VAC IN

70 - 20184 - 02

OPT PS ASSY - 240VAC IN

0'
::s

30 - 24374 - 02

881B PWR CNTLR ASSY

----

70 - 23138 - 01

OCP ASSEMBL Y

--III

""x'

54 - 15286 - 01**

OCP

-JIIo

70 - 23129 - 01

FLOPPY DRIVE BKT ASSY

--III

30 - 24962 - 01

RX33 DRIVE

EK - HSCMN - IN

INSTALLATION MANUAL

001

QX926 - H7

HSC70 SOFTWARE

V100

BL - FH74X - DE

HSC70 OFFLINE DIAGS

J]
(1)

iii'

C')

:::r
s:u

;::l

I
REVISIONS

C')

.....
o

-JIIo

---JIIo

V.300 V370 V370+

**THIS BREAKDOWN IS FOR FIELD SERVICE INFORMATION ONLY.
CX-1271B

Sheet 4 of 4

E-6
HSC REVISION MATRIX CHART

E.1.2 HSC50 (Modified) Revision Matrix Chart
Figure E-2 shows the revision status of alJ applicable HSC50 (modified) FRUs. An HSC50 (modified)
must have all the FRUs at a particular revision level in order to be supported.

"T1
cEo
c

(iJ

'0
o

HSC50-AA

,l,

NUMBER

REV

DESCRIPTION

REVISIONS

::::J

..:.....

L0100 - 00

III (CI LINK)

::I:

oc.n
o

L0105 - 00

P.ioc

E2-ETCH

C-ETCH

0- ETCH

E-ETCH

::::;;
Ci"

L0106 - AA

M.std

L0107 - VA

K.pli

L0108 - VA (HSC5X - B)

K.sdi

C-ETCH

0- ETCH

E-ETCH

K.sdi

F-ETCH

C23 C24 C25

K.sti

0- ETCH

Cl0

E-ETCH

F-ETCH

C24 C25 C26

<
iii"

---

0"
::::J

a
..,

;e"

Cl0

---

::::J"

;::t

L0108 - VB (HSC5X - C)

----

f-------.,---

r----------.,- , __ n_ - - - - ---

L0109 - 00

r----

54 - 14048 - 00
r----

K.sti

PILA

BACKPLANE

LOl18

III (CI LI NK)

LOl19

K.si

f - - - - - --- _".... _" __"__"_ _ n_ -----"----""

---"",,,-- - -"--"-,,------"- --

D-ETCH

-CX-2078A

Sheet 1 of 4

cc'
e:
ca

:t:

REV

HSC50 - AA

en
(")

II
DESCRIPTION

NUMBER

REVISIONS

(5
70 - 20033 - 01

STD PS ASSY - 120VAC IN

70 - 20033 - 03

STD PS ASSY - 120VAC IN

HSC5X - EA

OPT PS KIT - 120VAC IN

70 - 20184 - 01

OPT PS ASSY - 120VAC IN

70- 19122 - 00

PWR CNTLR ASSY . 120!208V

ZD300 - CG

HSC50 DK/TP SRVR F RMWR

70 - 20524 - 01

OCP ASSEMBL Y

54 - 15286 - 01

OCP

70 - 20186 - 01

BEZEL ASSEMBLY (TU58)

TU58 - XA

DRV MECH (70 - 15510 - 001)

TU58 - XB

S INTRFC (54 - 13489 - 00)

EK - HSCMN - IN

INSTALLATION MANUAL

001

002

AA-GMEAA-TK

USER GUIDE

OX926 - HG

HSC50 SOFTWARE

V350

V350 V370 V370+

BE - T493X - XX

HSC50 OFFLINE DIAGNOSTICS

E·DE

30 - 24374 - 01

CONTROLLER, PWR 120V 3 PHASE
9 OUTLET

~
II
X
(")

:t:

»
~

001

002

CX-2078A
Sheet 2 of 4

HSC50 - AB
NUMBER

REV

DESCRIPTION

L0100 - 00

III (CI LINK)

REVISIONS
E2-ETCH

C-ETCH

0- ETCH

E-ETCH

:::t:

fJ)

o(J1
o

~
o
a.
:::;;

L0105 - 00

P.ioc

(5'

L0106 - AA

M.')td

L0107 - YA

K.pli

L0108 - YA (HSC5X - B)

K.sdi

C-ETCH

0- ETCH

E-ETCH

K. sdi

F-ETCH

C23 C24 C25

K.sti

0- ETCH

Cl0

E-ETCH

F-ETCH

C24 C25 C26

L0108 - YB (HSC5X - C)

K.sti
PILA

54 - 14048 - 00

BACKPLANE

LOl18

III (CI LINK)

LOl19

K.si

Cl0

L0109 - 00

- - r-

:r:

()

m
<

en
(5
z

0- ETCH

()

:r:

>
~

CX-2078A
Sheet 3 of 4

"'T1

cO'

e
i

m
I

:x
oCJI

en
o

IREV

HSC50 - AB

I'\)

NUMBER

(')

DESCRIPTION

m
<

REVISIONS

(j)

~
o
a.
::::;;

70 - 20033 - 02

STD PS ASSY - 240VAC IN

70 - 20033 - 04

STD PS ASSY - 240VAC IN

C;'

HSC5X - EB

OPT PS KIT - 240VAC IN

70 - 20184 - 02

::r:
(J)

OPT PS ASSY-240VAC IN

70 - 20613 - 01

PWR CNTLR ASSY - 240/416V

ZD300 - CG

HSC50 DK/TP SRVR FRMWR
A3

0'
::::s

(')

::r:

»
lJ

-i

-...
I»

70 - 20524 - 01

OCP ASSEMB L Y

;:C'

54 - 15286 - 01

OCP

::r
Q)

70 - 20186 - 01

BEZEL ASSEMBL Y (TU58)

TU58 - XA

DRV MECH (70 - 15510 - 00)

TU58 - XB

S INTRFC (54 - 13489 - 00)

EK - HSCMN - IN

INSTALLATION MANUAL

001

002

AA-GMEAA-TK

USER GUIDE

OX926 - HG

HSC50 SOFTWARE

V300

V350

V350 V370 V370+

BE - T493X - XX

HSC50 OFFLINE DIAGNOSTICS

E-DE

30 - 24374 - 02

CONTROLLER, PWR 240V 3 PHASE
9 OUTLET

::L
K

001

002

Ci)'

001

002

CX-2078A

Sheet 4 of 4

E-11
HSC REVISION MATRIX CHART

E.1.3 HSC50 Revision Matrix Chart
Figure E-3 shows the revision status of an appHcable HSC50 FRUs. An HSC50 must have all the
FRUs at a particular revision level in order to be supported.

E-12
HSC REVISION MATRIX CHART

HSC50 REVISION NUMBER

FRU NAME

SLOT NO.

ETCH REV

MR/PR •

MR/PR*

01,02, E1

L0100

L0105

0, E

L0106-AH

L0107YA

L0108 YA
(HSC5X BA)

4,6,7,
8,9,10

C2, C3,
C4, C5

C2, C3.
C4

L0109
LOll8
LOl19

0
OPTION
REV F

TU58XA
TU58-XB
(54-13489)

E
F

F1, F2,
H, J, L

• MR/PR = MODULE REVISION OR PART REVISION.
NOTE: THE 50 HZ VERSION OF THE HSC50 IS AVAILABLE STARTING
WITH REVISION B1. BOTH THE HSC50 - AA (60 HZ) AND
HSC50· AB (50 HZ) ARE AT REVISION B1.

CX-242C
Sheet 1 of 2

Figure E-3 (Cont.)

HSC50 Revision Matrix Chart

E-13
HSC REVISION MATRIX CHART

HSC50 REVISION NUMBER

FRU NAME

SLOT NO.

ETCH REV

MR/PR*

OCP
(5415286)

BACKPLANE

MAIN POWER
SUPPLY
(70-20033)
60 HZ = 01
50 HZ = 02

AUXILIARY
POWER SUPPLY
(70·20184)
60 HZ '" 01
50 HZ = 02

POWER CONTROLLER
(70·19122)
60 HZ = 00
50 HZ = 01

SYSTEM TAPE
(BET492)

V100

V1l0
(C-DE)

INLINE DIAG
TAPE
(BET493)

V010l

V110
(C·DE)

TAPE KIT
(OOZD300-CG)

V100

V 100

UTI LlTY TAPE
(BET788C-DE)

• MR/PR = MODULE REVISION OR PART REVISION.
NOTE: THE 50 HZ VERSION OF THE HSC50 ISAVAILABLE STARTING
WITH REVISION B1. BOTH THE HSC50· AA (60 HZ) AND
HSC50 - AB (50 HZ) ARE AT REVISION B1.

CX-242C
Sheet 2 of 2

Figure E-3 HSC50 Revision Matrix Chart

Index
A

Auxiliary tenninal connection
HSC50 or HSC50 (modified), 4-3

Cables
baCkplane to bulkhead, 1-7
bulkhead to outside, 1-7
CI bus, 1-18
SDI bus, 1-18
STI bus, 1-] 8
Cache test parameters
leave cache enabled, 6-20
number of passes, 6-20
select data reliability test, 6-19
CERF
illegal fonnat type specified, B-12
output length too long, B-12, B-13
CI bus
connecting to multiple hosts, 1-1
CI-detected out-of-band errors
bad dispatch state in CB ... , 8-58
cables· have gone from uncrossed to
crossed, 8-82
date/time set by node nn, 8-64
HML$ER set-HM$ERR = nn, 8-71
K.ci exception detected, code = nnn,

8
BBR errors, 8-34
bad block replacement (block OK),
8-56
bad block replacement (drive
inoperative), 8-57
bad block replacement (RCf
inconsistent), 8-57
bad block replacement (recursive
failure), 8-57
bad block replacement (REPLACE
failed), 8-57
bad block replacement (success), 8-58
printout field definition, 8-35
Blower, 1-6
Bootstrap
progress reports, 6-3
Bootst..'1lp error infonnation, 6-4
Bootstrap failure troubleshooting, 6-4
lnit and Fault both lit, 6-4
Init and Fault both off, 6-4
Init is off, Fault is lit, 6-4
Bootstrap progress reports
Fault lamp, 6-4
lnit lamp, 6-3
lamps clear, 6-3
RX33 drive-in-use, 6-3
State lamp, 6-4
Bootstrap test summaries, 6-5
test O-basic PDP-ll instruction set,
6-5
test I-Program memory (Swap Bank),
6-5
test 2-Program memory (vector area),
6-5
test 3-Program memory (8 Kword
partition), 6-6
test 4-RX33 controller test, 6-6
test 5-RX33 drive/interface test, 6-6
test 6-transfer control to loaded image,
6-7

8-74
K.ci loopback microcode loaded, 8-75
no control block available to satisfy
HMB request., 8-80
node nn cables have gone from crossed
to uncrossed, 8-81 ~
node nn path (A or B) has gone from
good to bad, 8-83
node nn path n has gone from bad to
good, 8-82
resource lost to K.ci-xxx xxx HMBs,
8-88
VC closed with node nn due to
disconnect timeout, 8-98
VC closed with node nn due to request
from K.ci, 8-99
VC closed with node nn due to START
received, 8-99
VC closed with node nn due to
unexpected disconnect, 8-99
VC open with node nn, 8-100
CI Manager, 1-20
CIMGR, CIDIRECI'
received a sequence message without a
credit, B-32

Index 1

Index

CIMGR, CIMISCPRC
failed to acquire a control block from
K.ci. B-32
invalid bus address, B-34
K.ci detected an unrecoverable error and
stopped, B-32
K.ci is hung, B-32
K.ci patch status check failed, B-32
CIM:GR, CIROOT
system name is corrupted, B-33
CIMGR, CISCS
connection incarnation inconsistent,
B-33
connection incarnation mismatch, B-33
HMB received with wrong number of
BMBs, B-33
inconsistent connection state due to VC
closure, B-33
unable to retrieve resource from K.ci
during a disconnect, B-33
CIMGR, CISUBRS
attempt to deallocate a Connection
Block (CB) without an incarnation,
B-34
failure to retrieve SCS resources from
K.ci, B-34
illegal attempt to deallocate a
Connection Block (CB), B-34
K.ci did not respond to notification of a
VC closure, B-34
SCS buffer retrieval failure, B-35
the count of waiters for VC resources
went negative. B-34
Command prompt, 7-1
Console terminal
troubleshooting. 8-11
Console terminal connection
HSC70, 4-1
Control bus error conditions (hardwaredetected), 8-50
Controller byte field, 8-30
description, 8-31
Controller errors
compare error. 8-59
Data bus overrun, 8-62
Data memory error (NXM or parity),
8-63
EDC error, 8-67
internal consistency error, 8-74
PU receive buffer parity error, 8-85
PU transmit buffer parity error, 8-85
SERDES overrun, 8-92
Cooling, 1-6
Crash dump printout, B-1
example, B-1

o
DEMON
DEMON was initiated when there was
no diagnostic to run, B-9

DEMON (cont'd.)
exception routine invoked for unknown
reason, B-9
insufficient free memory to allocate a
Program Stack, B-9
DEMON, ILDISK
ILDISK detected inconsistency in
exception routine, B-I0
ILDISK received illegal buffer
descriptor, B-I0
ILDISK received illegal queue address,
B-I0
DEMON, ILEXER
an ILEXER disk I/O request failed to
complete, B-ll
an ILEXER tape I/O request failed to
complete, B-ll
DEMON, ILTAPE
ILTAPE detected inconsistency after a
command failure, B-12
ll..TAPE detected inconsistency in
exception routine, B-12
ILTAPE detected inconsistency while
restoring a TACB, B-12
ILTAPE timed-out while waiting for
Drive State Area, B-11
ILTAPE was supplied an illegal
requestor number, B-ll
DEMON, PRKSDI, PRKSTI
failure in periodic K.sdi, K.sti, or K.si
test, B-I0
DEMON, PRMEMY
failure in periodic Control or Data
memory test, B-I0
Device integrity tests
generic error message format, 5-1
generic prompt syntax, 5-1
DIAGINT
XCALL stack corrupted, B-39
Diagnostic manager, 1-20
Diagnostic subroutines, 1-20
DIRECT
FAO message buffer overflow, B-36
Disabling P.ioj/c parity errors, 6-43
DISK,ATIN
connection closed after delay in ATTN
process, B-25
DISK, ERROR
buffer not found for specific error, B-19
DCB state is busy with empty DCB
queue, B-18
DRAT/SEEK timer not allocated for disk
unit, B-16
DRAT not found for FRB retirement,
B-19
DT$ERQ not zero in FRB error state,
B-17
error identification table overwritten,
B-16
FRB not in error state for Level D I/O
Operation (LVLDIO), 8-18

Index

DISK, ERROR (cont'd.)
invalid disk characteristics for operation,
B-16
invalid error bit value found during error
recovery, B-16
invalid error queue address in route,
B-18
level B retry in wrong state, B-17
level C retry in wrong state, B-17
no buffer found in FRB when expected,
B-18
non-ECC/EDC errors remaining after
ECC correction, B-17
not enough mapped memory to initialize
Disk Path, B-16
parent downcount failed, B-19
S bit not set in FRB error state, B-17
Sectors/frack field in K Control Area is
zero, B-19
stack too deep to save in thread block,
B-18
unable to get to FRB error state, B-17
undefined error bit in error word from
K, B-18
unexpected Compare failure following
Write, B-20
DISK, many
a timer has link field values inconsistent
to its current operational status,
B-25
attempt to downc()un-t DRAT already at
zero, B-2l
attempt to enable drive interrupt already
enabled, B-20
attempt to enable drive with pending
state cha.'lge, B-20
a unit is incorrectly marked as a shadow
set member, B-25
BMB reserved but not found, B-13
call to DCBOPR from process other
than DISK, B-23
invalid module number in subprocess
work queue, B-14
NO DRAT list invalid, B-25
server queue on work queue with no
items, B-14
state change requested for available but
inoperative drive, B-20
DISK, MSCP
command not completed after drive
declared inoperative, B-24
datagram received from a connection,
B-13
diagnostic release of disk unit while
online, B-15
diagnostic release of RCB while units
still online, B-16
DRAT allocation failure, B-24
DRAT queue not empty for shadow
copy, B-19

DISK, MSCP (cont'd.)
element in deferred SEEK queue with
no FRS, B-24
GCS status overflow, B-25
inconsistent result for Repair operation,
B-19
invalid block number for Transfer
operation, B-20
invalid diagnostic HMB, B-15
invalid error signaled by K.ci, B-14
known drive not found in the Disk Unit
Table (DUT), B-20
MSCP message size exceeded
maximum, B-14
shadow unit not found in Disk Unit
Table (DUT), B-15
too many seek blocks requested by
diagnostic, B-15
DISK, MSCX
no structure to ONLINE disk to
connection, B-13
DISK, SDI
D bit set for port with SEEK DCB being
processed, B-21
D bit set in DCB error state, B-22
DCB address inconsistency, B-25
DCB received with no errors and no
frames, B-24
DCB state is blocked after QUIESCE or
DCBSTS DCB, B-23
DeB state is busy with -empty DCB
queue, B-22
DRAT/SEEK timer running with SEEK
DCB queued, B-21
DUCB address 0 in K Control Area,
B-13
improper state change for shadow
member, B-15
inconsistent drive state detected, B-15
insufficient pool to allocate a timer,
B-24
invalid action byte in Connection Block
(CB), B-13
K.sdi/K.si is not responding, B-22
match enable not set for DIALOG DCB,
B-23
nonzero status for SUCCESSFUL DCB,
B-22
no thread block for operation, B-23
port not in DCB error state for error
DCB, B-23
SDI WRITE MEMORY command not
implemented, B-22
SEEK DCB without Clear D bit flag set,
B-21
SLCB not available when needed, B-14
stack too deep to suspend process in
thread block, B-23
state changed during SDI ONLINE,
B-21

Index

DISK, SDI (cont'd.)
state change to ONLINE requested via
gatekeeper, B-14
thread block area too small, B-21
thread block count not initialized, B-21
thread block pointer corrupted in DCB,
B-24
Disk functional errors, 8-49
Disk functional out-of-band errors
aborting error recovery due to excessive
recat~, 8-55
aborting error recovery due to excessive
timeouts, 8-55
attention condition serviced for ONLINE
disk unit XXX., 8-56
ATIN. message sent to node xx, for unit
xx, 8-56
clock dropout from ONLINE disk unit
XX., 8-59
deferred ATN. message for node xx, unit
xx, 8-64
disk unit xx. (requestor xx., port xx.)
being INITialized, 8-64
disk unit xx. ready to transfer, 8-64
disk unit xxx. (requestor XX., port xx.)
declared inoperative, 8-65
DRAT/SEEK timeout, disk unit XXX.,
8-65
DRIVE CLEAR attempt on disk unit xx.
(requestor XX., port xx.)., 8-65
duplicate disk unit xx, 8-67
FRB error: K.ci, 1st LBN xx., xx.
buffers, FE$SUM xx, 8-69
FRB error: K.sdi, unit xx., 1st LBN
XXX., xx. buffers, FE$SUM xx,
8-69
illegal bit change in status from disk
unit xxx, 8-73
K.sdi/K.si in slot xx. failed its !nit DIT,
status = xxx, 8-75
LBN restored with forced error in
RESTOR operation!, 8-76
LBN xx. repaired for shadow member
unit xx., 8-76
positioner error on disk unit xxx. DRAT
addr:xxx, 8-86
premature LP flag in RTNDAT sequence
from host node xx, 8-86
SDI exchange retry on disk unit xxx,

8-90
unexpected AVAILABLE signal from
ONLINE disk unit xx, 8-97
unit xx. declared inoperative because
no progress made on Command
Reference xxxxx., 8-97
unrecoverable error on disk unit xx.
Drive appears inoperative, 8-98
unsuccessful SEEK initiation, disk unit
xxx. DCB addr: xxX, 8-98

Disk functional out-of-band errors (cont'd.)
VC closed due to timeout of
RTNDAT/CNF from host node
xx, 8-98
Disk I/O manager, 1-20
Disk transfer error
printout field description, 8-32
Disk transfer errors
data sync not found, 8-63
eight-symbol ECC error, 8-78
five-symbol ECC error, 8-78
forced error, 8-68
four-symbol ECC error, 8-78
one-symbol ECC error, 8-78
RCf corrupted error, 8-87
seven-symbol ECC error, 8-78
six-symbol ECC error, 8-78
three-symbol ECC error, 8-78
two-symbol ECC error, 8-78
uncorrectable ECC error, 8-78
DKCOPY
bad down count when trying to bring
source online, B-36
bad down count when trying to bring
target unit online, B-37
bad downcount when trying to issue
abort command to target unit, B-37
bad downcount when trying to issue
AVL command to shadow unit,
B-37
bad downcount when trying to issue
GCS to target unit, B-3 7
wrong mvm received after issuing AVL·
command to shadow unit, B-37
wrong mvm received when trying to
bring source online, B-36
wrong mvm received when trying to
issue GCS to target unit, B-36
DKRFCT
disk RCT/FCT merge utility, 7-34
error messages, 7-37
error message severity levels, 7-36
fatal error messages, 7-36
information messages, 7-37
initialization, 7-34
sample session, 7-35
DKRFCT error messages
DKRFCT-E-BADUNIT illegal unit
number specified, 7-37
DKRFCT-E-DUPL unit n is a duplicate,
7-37
DKRFCT-E-INUSE specified unit
is in use, broken, or otherwise
unavailable, 7-37
DKRFCT-E-OFFLINE specified unit is
offline, 7-37
DKRFCf fatal error messages
DKRFCT-F-BADFCT all copies of FCf
block n are bad, 7-36
DKRFCf-F-BADRcr all copies of Rcr
block n are bad, 7-36

Index 5

DKRFCf fatal error messages (cont'd.)
DKRFCf-F-INVHDR invalid header n
in I/O call, 7-36
DKRFCf-F-LOSTIO I/O lost, 7-36
DKRFcr-F-NOBUF Not enough buffers
available, 7-36
DKRFcr-F-NOCODE Disk functional
code is not loaded, 7-36
DKRFcr-F-NOFCB Not enough FCBs
available, 7-36
DKRFcr-F-NOTFMT Unit is not
formatted; Mode is unknown, 7-36
DKRFCf information error messages
DKRFcr-I-EXIT exiting, 7-37
DKRFCf information messages
DKRFCf-E-COPYCON previous
DKRFCf run was interrupted;
COpy restarted, 7-37
DKRFCf-E-COPYDO copying new
FCf from scratch area to subtable,

7-37
DKRFCf-l-FULL too many PBNs to
add; please RUN DKRFCf again,
7-37
DKRFCf-I-NONEW new FCf identical
to old; FCf not changed, 7-37
DKRFCf-I-NULLIST there are no
PBNs to add to the FCf, 7-37
DKlITIL, 7-1
command descriptions, 7-5
command· niOOffiers,7...;.2
command prompt, 7-3
command syntax, 7-2
DEFAULT command, 7-6
DEFAULT modifiers, 7-6
DISPLAY command, 7-7
DISPLAY modifiers, 7-7
DISPLAY parameters, 7-7
DISPLAY usage, 7-7
DUMP command, 7-8
DUMP command modifiers, 7-9
DUMP command parameters, 7-8
DUMP command syntax, 7-8
error messages, 7-13
error message severity levels, 7-13
error message variables, 7-13
EXIT command, 7-10
GET command, 7-10
GET command modifiers, 7-10
GET command usage, 7-10
initialization, 7-1
POP command, 7-11
POP command usage, 7-11
PUSH command, 7-11
PUSH command usage, 7-11
REVECfOR command, 7-11
REVECfOR command usage, 7-11
sample session, 7-3
SET command, 7-12
DKlITIL DEFAULT modifiers
ALL/NONE, 7-6
BBR/NOBBR, 7-6

DKUTIL DEFAULT modifiers (cont'd.)
DATA/NODATA, 7-6
ECC/NOECC, 7-6
EDC/NOEDC, 7-6
ERRORS/NOERRORS, 7-6
HEADERS/NOHEADERS, 7-6
~RROR/NO~RROR, 7-6
NZ/NONZ,7-6
ORIGINAL/NOORIGINAL, 7-6
RAW/NORAW, 7-6
DKUTIL DISPLAY modifiers
FULL, 7-7
NOITEMS, 7-7
DKUTIL DISPLAY usage
DISPLAY ALL, 7-7
DISPLAY CHARACI'ERISTICS DISK,
7-7
DISPLAY CHARACI'ERISTICS xBN,
7-8
DISPLAY ERRORS, 7-8
DISPLAY FCf, 7-8
DISPLAY RCf, 7-8
DKUTIL DUMP command modifiers
/ALL/NONE, 7-9
/BBR/NOBBR, 7-9
/DATNNODATA, 7-9
/ECC/NOECC, 7-9
/EDC/NOEDC, 7-9
/ERRORS/NOERRORS, 7-9
/HEADERS/NOHEADERS, 7-9
~OR/NO~OR, 7-9

fNZlNeNZ-, -7-9

/ORIGINAL/NOORIGINAL, 7-9
/RAW/NORAW, 7-9
DKUTIL DUMP command parameters
DUMP xBN [{block}], 7-9
DUMP xCf [BLOCK {number}]
[COpy {copy}], 7-9
DKUTIL error messages, 7-13
all copies of xCf block n are bad, 7-14
cannot bring unit ONLINE, 7-14
copy n of xCf block n (xBN n) is bad,
7-14
CfRL/Y or CfRL/C abort, 7-15
drive must be acquired to execute this
command, 7-15
drive must be online to execute this
command, 7-15
drive went AVAILABLE, 7-13
drive went OFFLINE, 7-13
error log corrupted, can not display
entries, 7-15
error log corrupted, can not display
header, 7-14
error log not implemented in drive,
7-15
illegal response to start-up question,
7-14
invalid block number for xBN space,
7-14
invalid decimal number, 7-14
invalid octal number, 7-14

Index

OKUTIL error messages (cont'd.)
invalid sector size; only 512 and 576 are
legal, 7-14
missing modifier only "f' was specified,
7-14
missing parameter, 7-14
n is an invalid par number; maximum is
n, 7-14
nonexistent unit number, 7-14
revector for LBN n failed, MSCP status:
status, 7-14
SOl command was unsuccessful, 7-14
there is no buffer to dump, 7-14
unable to read error log, 7-15
unit is not available, 7-14
xxx is an invalid xxx, 7-14
DKUTIL fatal error messages, 7-13
I/O request was rejected, 7-13
insufficient resources to RUN, 7-13
DKUTIL GET command modifiers
/NOI~, 7-10
/NOONLINE, 7-10
/NOWP, 7-10
/wp, 7-10
Documents
ordering, 1-30
OUP

bad downcount, B-36
can't find Connection Block (CB), B-35
connection broken, B-36
illegal BMB count, B-35
illegal HMB error, B-35
illegal HMB Opcode, B-35
invalid Connection Block (CB), B-35

E
ECC
can't allocate XFRB to print self-test

messages, B-26
ECC found more than a 100bit symbol
error, B-26
ECC self-test string too big for FAO,
B-25
no ECC errors to correct, B-26
Error byte field, 8-30
description, 8-30
Error message format, generic, 6-8
Error processor, 1-20
Exception codes and messages, B-1
SPR submission, B-2
Exception message, B-5
001040, B-5
001042, B-5
001043, B-5
001201, B-5
001202, B-5
001203, B-6
001204, B-6
00]205, B-6
001401, B-6
001402, B-6

Exception message (cont'd.)
001403, B-6
001501, B-7
001502, B-7
001503, B-7
001504, B-7
001505, B-7
001506, B-7
001507, B-7
001510, B-8
001511, B-8
001512, B-8
001513, B-8
001514, B-8
001515, B-8
001601, B-8
001602, B-9
001603, B-9
001701, B-9
002001, B-9
002002, B-9
002003, B-9
002004, B-] 0
002005, B-I0
002006, B-I0
002007, B-I0
002010, B-I0
002011, B-Il
002012, B-Il
002013, B-11
002014, B-11
002015, B-12
002016, B-12
002017, B-12
003001, B-12
003002, B-12
003003, B-13
004001, B-13
004002, B-13
004004, B-13
004005, B-13
004006, B-14
004007, B-14
004010, B-14
004011, B-14
004012, B-14
004013, B-14
004014, B-15
004015, B-15
004016, B-15
004017, B-15
004020, B-15
004021, B-15
004022, B-16
004023, B-16
004024, B-16
004025, B-16
004026, B-16
004027, B-16
004030, B-17
004031, B-17
004032, B-17
004033, B-!7

Index 7

Exception message (cont' d.)
004034, B-17
004035, B-17
004036, B-18
004037, B-18
004040, B-18
004041, B-18
004042, B-18
004043, B-18
004044, B-19
004045, B-19
004046, B-19
004047, B-19
004050, B-19
004051, B-19
004052, B-20
004053, B-20
004054, B-20
004055, B-20
004056, B-20
004057, B-20
004060, B-21
004061, B-21
004062, B-21
004063, B-21
004064, B-21
004065, B-21
004066, B-21
004067, B-22
004070, B-22
004071, B-22
0040-72, B-22
004073, B-22
004074, B-23
004075, B-23
004076, B-23
004077, B-23
004100, B-23
004101, B-23
004102, B-24
004103, B-24
004104, B-24
004105, B-24
004106, B-24
004107, B-24
004110, B-25
004111, B-25
004112, B-25
004113, B-25
004114, B-25
004115, B-25
005001, B-25
005002, B-26
005003, B-26
005004, B-26
006001, B-26
006002, B-26
006003, B-27
006004, B-27
006005, B-27
006006, B-27
006007, B-27
006010, B-28

Exception message (cont' d)
006011, B-28
006012, B-28
006013, B-28
006014, B-28
006015, B-29
006016, B-29
006017, B-29
006020, B-29
006021, B-29
006022, B-29
006023, B-30
006024, B-30
006025, B-30
006026, B-30
006031, B-30
006033, B-30
006040, B-31
006043, B-31
006044, B-31
006045, B-31
006046, B-31
006047, B-31
006050, B-32
007001, B-32
007002, B-32
007003, B-32
007004, B-32
007005, B-32
007006, B-33
007007, B-33
00+011, . B-33
007012, B-33
007013, B-33
007014, B-33
007015, B-34
007016, B-34
007017, B-34
007020, B-34
007021, B-34
007022, B-34
007023, B-35
012001, B-35
012002, B-35
012003, B-35
012004, B-35
012021, B-35
012024, B-36
012036, B-36
042001, B-36
043001, B-36
043002, B-36
043003, B-36
043004, B-37
043005, B-37
043006, B-37
043007, B-37
043010, B-37
046001, B-37
051001, B-38
051002, B-38
051003, B-38
051004, B-38

8 Index

Exception message (cont'd.)
051101, B-38
05tJ02, B-38
051201, B-38
051202, B-39
051203, B-39
052001, B-39
052002, B-39
052003, B-39
061001, B-39
062001, B-40
EXEC, EXEC
power failure, B-5
Set Timer operation to Ttmer with
address of 0, B-5
Tooe-of-Dayoverflowed, B-5
EXEC, EXECLOAD
FAO ovenun, B-6
insufficient Kernel pool, B-6
memory extent encroaches defined area,
B-5
no code parent process loaded, B--6
EXEC, EXECRDWR
invalid DDCB specified, B-6
performed receive when already busy
with request, B--6
requested driver not loaded, B-6
EXEC,EXECRX33
software/hardware inconsistencyNon-Existent Memory (NXM),
B-8
software/hardware inconsistency-RX33
hanlware registers are incorrect,
B-7
software inconsistency-invalid byte
count, B-7
software inconsistency-invalid head
select, B-8
software inconsistency-invalid internal
byte count, B-7
software inconsistency-invalid internal
unit number, B-8
software inconsistency-invalid unit
number, B-7
software inconsistency-invalid virtual
address, B-8
software inconsistency-memory
management, B-8
software inconsistency-motor not
running, B-7
software inconsistency-non-RX33
command requested, B-7
software inconsistency-unexpected
interrupt from RX33, B-8
software inconsistency-zero byte count
transfer, B-7
EXEC, EXECIT
ACPT$ crosses page boundary, B-9
PCB not found on run queue, B-9
TYPE$ crosses page boundary, B-8
EXEC, EXEcru58

EXEC, EXECfU58 (cont'd.)
READ$ or WRITE$ crosses page
boundary, B-9
EXEC EXECLOAD
process on Recoverable list not
Hibernating, B-5
External interfaces, 1-17

F
Fo~~~

CTRUC caution, 7-22
CTRUY caution, 7-22

FORMAT
CAUTION, 7-22
error messages, 7-27
error message variables, 7-24
errors and information messages, 7-24
fatal error messages, 7-25
information messages, 7-26
initiation, 7-22
message severity levels, 7-25
missing DRAT for FORMAT TRACK
operation, B-37
offline disk formatter utility, 7-22
sample session, 7-23
special option prompts, 7-23
success messages, 7-27
VERIFY requirement, 7-24
warning message, 7-26
FORMAT error messages
FORMAT-E illegal response to start-up
question, 7-27
FORMAT-E nondefaultable parameter,
7-27
FORMAT fatal error messages
FORMAT-F cannot position to DBN
area, 7-25
FORMAT-F current maximum sector
size is 512, 7-25
FORMAT-F DBN format error, 7-25
FORMAT-F drive does not support 576
mode on this media, 7-25
FORMAT-F drive is write-protected,
7-25
FORMAT-F FCT does not have enough
good copies of each block, 7-25
FORMAT-F FCT is improper, 7-25
FORMAT-F FCT nonexistent, 7-25
FORMAT-F FCT read error, 7-25
FORMAT-F FCT write error, 7-25
FORMAT-F formatter initialization error,
7-25
FORMAT-F GET STA1US failure, 7-25
FORMAT-F LBN format error, 7-25
FORMAT-F nonexistent unit number,
7-25
FORMAT-F RCT does not have enough
good copies of each block, 7-25
FORMAT-F RCT is full, 7-25
FORMAT-F RCT read error, 7-26
FORMAT-F RCT write error, 7-26

Index 9

FORMAT fatal error messages (cont'd.)
FORMAT-F SDI receive error, 7-26
FORMAT-F too many bad RBNs found
before RCf was formatted, 7-26
FORMAT-F unsuccessful SDI command,
7-26
FORMAT information messages
FORMAT-I bad LBN n (x), a nonprimary revector, 7-26
FORMAT-I bad LBN n (x), a primary
revector to RBN n., 7-26
FORMAT-I bad LBN n (x), in the RCf
area, 7-26
FORMAT-I bad RBN n (x), 7-26
FORMAT-I CTRL/Y or CTRL/C abort,
7-26
FORMAT-I cylinder n, group n, track n,
position n, PBN n, 7-26
FORMAT-I FCf was not used, 7-26
FORMAT-I FCf was used successfully,
7-26
FORMAT-I n cylinders left in xBN
space at hh:mm:ss.xx, 7-26
FORMAT-I only DBN area formatted (n
bad DBNs), 7-26
FORMAT success messages
FORMAT-S format begun, 7-27
FORMAT-S format completed, 7-27

G
General information, 1-1

H
HSC50
FRU removal sequence, 3-S8
I/O Control Processor module baud rate
jumper, 3-64
removal and replacement procedures,
3-S4
removing ac power, 3-S6
removing airflow sensor, 3-66
removing auxiliary power supply, 3-71
removing back door, 3-S9
removing blower, 3-6S
removing dc power, 3-S7
removing front door, 3-S8
removing logic modules, 3-63
removing main power supply, 3-69
removing OCP, 3-63
removing power, 3-S4
removing power controller, 3-67
removing TU58 bezel assembly, 3-59
removing TUS8 controller module, 3-62
HSC50 (modified)
FRU removal sequence, 3-30
I/O Control Processor module baud rate
jumper, 3-36
removing ac power, 3-29
removing airflow sensor assembly, 3-42

HSCSO (modified) (cont'd.)
removing auxiliary power supply, 3-S1
removing back door, 3-31
removing blower, 3~
removing dc power, 3-29
removing front door, 3-30
removing logic modules, 3-3S
removing main power supply, 3-48
removing OCP, 3-3S
removing power, 3-28
removing power controller, 3-4S
removing TUS8 bezel assembly, 3-31
removing TUS8 controller module, 3-34
rotating the 881 line cord elbow, 3-47
HSCSO (modified) blower, 1-10
HSCSO (modified) boot flow/troubleshooting
chart, 8-18
HSCSO (modified) cables
backplane to bulkhead, J-11
bulkhead to outside, 1-11
a, 1-11
SDI, 1-11
STI, 1-11
HSCSO (modified) cooling, 1-8, 1-10
HSCSO (modified) internal cabling, A-7
HSCSO (modified) L01l8 jumper
configuration
Rev-A module, 3-39
Rev-Bl module, 3-41
Rev-B2 module, 3-42
HSCSO (Modified) Module Utilization
Label, 1-10
HSCSO (modified) node address switches
LOI00, Rev-E2 or L01l8 LINK module,
3-38
LOI00 LINK module, 3-37
HSC50 (modified) packaging, 1-8
HSCSO (modified) power, 1-8
HSCSO (modified) power Control bus
See power controller, 1-11
HSCSO (modified) power controller
Delayed output line, 1-11
Noise isolation filters, 1-11
power Control bus, 1-11
HSCSO (modified) removal and replacement
procedures, 3-28
HSCSO boot flow/troubleshooting chart,
8-18
HSCSO inside front door controls/indicators, 2-6
Enable indicator, 2-6
Secure/Enable switch, 2-6
TUS8 Run indicators, 2-6
TUS8 Self-Test indicator, 2-7
HSCSO internal cabling, A-14
HSCSO LOl00-E2/L01l8
green, 2-17
red, 2-17
HSCSO LOl00-E2/L01l8 CI port link
module
switch settings, 2- J 7
HSCSO LO 1OS I/O control module

Index

HSC50 LOI05 I/O control module (cont'd.)
baud rate jumper, 2-18
HSC50 LOI05 module
amber Run indicator, 2-16
amber State indicator, 2-16
green, 2-16
red, 2-16
HSC50 LOI06 module
green, 2-16
HSC50 LO 107/L0 109 CI port modules
switch settings, 2-17
HSC50 LO I 07/L0 109 port link and port
buffer modules
switch settings, 2-17
HSC50 LOI07-YA module
green, 2-17
red, 2-17
HSC50 LOI08-YA-YB/L0119 LEOs
green, 2-16
red, 2-16
HSC50 LOI09 module
amber, 2-17
green, 2-17
red, 2-17
HSC50 LO 118 jumper configuration
Rev-A module, 3-65
Rev-B I module, 3-65
Rev-B2 module, 3-65
HSC50 LO 119 LEDs
amber (eight LEDs), 2-17
HSC50 maintenance access panel, 2-7
dc power switch, 2-7
maintenance panel connectors, 2-8
HSC50 module indicators, 2-14
HSC50 node address switches
L0100, Rev-E2 or L0118 LINK module,

3-65
LO I 00 UNK. module, 3-65
HSC70
dc power switch location, 3-3
FRU removal sequence, 3-4
opening back door, 3-5
opening front door, 3-4
removal and replacement procedures,
3-1
removing ac power, 3-2
removing airflow sensor assembly, 3-17
removing auxiliary power supply, 3-25
removing blower, 3-19
removing dc power, 3-3
removing disk drives, 3-6
removing logic modules, 3-11
removing main power supply, 3-23
removing OCP, 3-9
removing power, 3-1
removing power controller, 3-20
rotating the 881 line cord elbow, 3-22
RX33 cover plate removal, 3-5
RX33 disk drive jumper configurations,
3-9
HSC70 boot flow/troubleshooting chart,
8-12
HSC70 cables

HSC70 cables (cont'd.)
a,I-7
SDI, 1-7
S11, 1-7
HSC70 cooling, 1-3
HSC70 inside front door controls/indicators
de power switch, 2-5
Enable indicator, 2-4
RX33 LEDs, 2-5
Secure/Enable switch, 2-4
HSC70 internal cabling, A-I
HSC70 LOl00-E2/L0118
green, 2-11
red, 2-11
HSC70 LOI00-E2/L0118 CI port LINK
module
switch settings, 2-11
HSC70 LOI07/LOI09 CI port modules
switch settings, 2-11
HSC70 LOI07-YA LEOs
green, 2-11
red, 2-11
HSC70 LOI08-YA-YB/L0119 LEOs
green, 2-11
red, 2-11
HSC70 LOI09 LEDs
amber, 2-11
green, 2-11
red, 2-11
HSC70 LOllI LEDs
Dl amber, 2-10
D2 amber, 2-10
D3 amber, 2-10
D4 amber, 2-10
D5 amber, 2-10
D6 amber, 2-10
D7 red, 2-10
D8 green, 2-10
HSC70 L0117 LEOs
amber, 2-10
green, 2-10
red, 2-11
HSC70 LO 118 jumper configuration
Rev-BI module, 3-16
Rev-B2 module, 3-17
HSC70 LO 119 LEOs
amber LEDs, 2-11
HSC70 module indicators/switches, 2-8
HSC70 modules switches, 2-11
HSC70 module utilization label, 1-6
HSC70 node address switches
L0100, Rev-E2 or L0118 LINK module,
3-13
LOlOO LINK module, 3-12
HSC70 P.ioj module (LOllI)
switch settings, 2-12
HSC70 packaging, 1-3
HSC70 power, 1-3
HSC70 power Control bus
See power controller, 1-7
HSC70 power controller
delayed output line, 1-7
noise isolation filters, 1-7

Index

HSC70 power controller (cont' d.)
power Control bus, 1-7
HSC control program, 1-19
HSC fault code interpretation, 4-9
HSC generic error log fields, C-l
ESC maintenance strategy, 1-27
HSC models
content differences, 1-2
HSC specifications, 1-28
HSC terminal connection
console or auxiliary, 4-1

ILDISK
availability, 5-9
disk drive integrity test, 5-7
error message example, 5-10
hardware requirements, 5-8
operating instructions, 5-8
progress reports, 5-10
software requirements, 5-8
specifying requestor and port, 5-10
system requirements, 5-8
test parameter entry, 5-9
tests perfonned, 5-8
test termination, 5-10
ILDISK error messages, 5-11
error, 10 K.sdi/K.si does not support
microdiagnostics, 5-11
error 01, DDUSUB initialization failure,
5-11
error 02, unit selected is not a disk,
5-11
error 03, drive unavailable, 5-11
error 04, unknown status from
DDUSUB, 5-ii
error 05, drive unknown to disk
functional code, 5-11
error 06, invalid requestor or port
number, 5-11
error 07, requestor is not a K.sdi/K.si,
5-11
error 08, specified port contains a known
drive, 5-11
error 09, drive can't be brought online,
5-11
error 11, change mode failed, 5-11
error 12, drive disabled bit set, 5-12
error 13, command failure, 5-12
error 14, can't write and sector on track,
5-12
error 15, Read/Write Ready not set in
online drive, 5-12
error 16, error releasing drive, 5-12
error 17, insufficient memory, test not
executed, 5-12
error 18, microdiagnostic did not
complete, 5-12
error 19, K microdiagnostic reported
error, 5-12

ILDISK error messages (cont'd.)
error 20, DCB not returned, K failed for
unknown reason, 5-13
error 21, error in DCB on completion,
5-13
error 22, unexpected item on drive
service queue, 5-13
error 23, failed to reacquire unit, 5-13
error 24, state line clock not running,
5-13
error 25, error starting I/O operation,
5-13
error 26, Init did not stop state line
clock, 5-14
error 27, state line clock did not start up
after Init, 5-14
error 28,110 operation lost, 5-14
error 29, echo data error, 5-14
error 30, drive went offline, 5-14
error 31, drive acquired but can't find
control area, 5-14
error 32, requestor does not have control
area, 5-14
error 33, can't read any sector on track,
5-14
error 34, drive diagnostic error, 5-15
error 35, drive diagnostic detected fatal
error, 5-15
error 36, error bit set in drive status
error byte, 5-15
error 37, attention set after seek, 5-15
error 38, available not set in available
drive, 5-15
error 39, attention not set in available
drive, 5-15
error 40, Receiver Ready not set, 5-15
error 41, Read/Write Ready set in
available drive, 5-15
error 42, Available set in online drive,
5-15
error 43, Attention set in online drive,
5-15
error 44, drive did not clear errors, 5-15
error 45, error reading LBN, 5-16
error 46, echo framing error, 5-16
error 47, K.sdi/K.si does not support
echo, 5-16
error 48, req/port number information
unavailable, 5-16
error 49, drive spindle not up to speed,
5-16
error 50, can't acquire Drive State Area,
5-16
error 51, failure while updating drive
status, 5-16
error 52, 576-byte format failed, 5-17
error 53, 512-byte format failed, 5-17
error 54, insufficient resources to
perform test, 5-17
error 55, drive transfer queue not empty
before format, 5-17

Index

ILDISK error messages (cont'd.)
error 56, K.sdi/K.si detected error during
format, 5-17
error 57, wrong structure on completion
queue, 5-17
error 58, Read operation timed out,
5-17
error 59, K.sdi/K.si detected error in
read preceding fonnat, 5-17
error 60, read DRAT not returned to
completion queue, 5-17
error 61, Format operation timed out,
5-17
error 62, fonnat DRAT was not returned
to completion queue, 5-18
error 63, can't acquire specific unit,
5-18
error 64, duplicate unit detected, 5-18
error 65, format tests skipped due to
previous error, 5-18
error 66, testing aborted, 5-18
error 67, not good enough OBNs for
format, 5-18
ILOISK test summaries, 5-19
test 0, parameter fetching, 5-19
test 01, K.sdi/K.si microdiagnostics,
5-19
test 02, check for clocks and drive
availability, 5-19
test 03, drive initialize test, 5-19
test 04, SOl echo test, 5-19
test 05, run drive integrity tests, 5-20
test 06, discormect from drive, 5-20
test 07, check drive status, 5-20
test 08, drive initialize, 5-20
test 09, bring drive online, 5-20
test 10, recalibrate and seek, 5-20
test II, disconnect from drive, 5-20
test 12, bring drive online, 5-20
test 13, read only I/O operations test,
5-21
test 14, 1/0 operations test (read!write
512 byte format), 5-21
test 17, tenninate ILDISK 5-21
ILEXER
'
communications error format, 5-50
communications error report, 5-48
data compare error format, 5-49
data patterns, 5-44
data transfer error report, 5-46
disk drive user prompts, 5-40
error message format, 5-48
error messages, 5-50
global user prompts, 5-42
inline multidrive exerciser, 5-37
operating instructions, 5-38
perfonnance summary, 5-46
progress reports, 5-46
prompt error fonnat, 5-49
setting/clearing flags, 5-46
system requirements, 5-37
tape drive exercise commands, 5-55

ILEXER (cont'd.)
tape driver user prompts, 5-41
test parameter entry, 5-39
test termination, 5-48
ILEXER disk errors, 5-52
command failed-invalid header code,
5-52
command failed-no buffer available,
5-52
command failed-no control structures
available, 5-52
couldn't put drive in OBN space, 5-52
data compare error, 5-52
disk unit numbers must be between 0
and 4095 decimal, 5-52
drive error not up to speed, 5-52
drive no lOnger online, 5-53
EOC error, 5-52
hard failure on Compare operation,
5-53
hard failure on disk, 5-52
hard failure on initial Write operation,
5-53
hard failure on Read operation, 5-53
hard failure on Write operation, 5-53
no OACB available, 5-52
pattern number error, 5-52
s~e disk 1/0 failed to complete, 5-52
thIS drive removed from test, 5-52
unknown unit number not allowed in
ILEXER, 5-52
write requested on write-protected drive,
5-52
ILEXER generic errors, 5-51
couldn't get buffeIS for transfers, 5-52
couldn't get drive status, 5-51
couldn 'f get timer for J\.IDE, 5-51
couldn't return drive to available state,
5-51
could not get control block for timer,
5-51
disk functionality unavailable, 5-51
drive cannot be brought online, 5-51
drive is unavailable, 5-51
drive is unknown, 5-51
invalid time entered, 5-52
no disk or tape functionality, 5-51
no tape mounted on unit, 5-51
record length larger that 12K or 0, 5-52
tape functionality unavailable, 5-51
tape rewind commands were lost 5-52
this unit already acquired, 5-52'
user requested write on write-protected
unit, 5-51
ILEXER informational message, 5-50
at most, 16 words may be entered in a
data pattern, 5-50
disk interface not available, 5-50
number must be between 0 and 15,
5-50
pattern number must be within specified
bounds, 5-50

Index

ILEXER infonnational message (cont'd.)
please mount a scratch tape, 5-50
please wait-clearing outstanding 110,
5-51
starting LBN is either larger than ending
LBN or larger than totai LBN on
disk, 5-50
tape interface not available, 5-50
ILEXER tape errors, 5-53
comm error: TDUSUB call failed, 5-53
controller error... hard error, 5-54
couldn't get fornlatter characteristics,
5-53
couldn't get unit characteristics, 5-53
couldn't set unit char, 5-53
data pattern word error, 5-53
data read EDC error, 5-53
drive error...hard error, 5-53
drive went available, 5-54
drive went offline, 5-54
fonnatter error... hard error, 5-54
hard error limit exceeded, 5-54
read data error, 5-53
retry required on tape drive, 5-54
short transfer error, 5-54
some tape I/O failed to complete, 5-53
tape marie error, 5-53
tape position discrepancy, 5-54
tape position lost, 5-53
truncated record data error, 5-53
unexpected BOT encountered, 5-53
unexpecteo -error condition, 5-53
unrecoverable read error, 5-54
unrecoverable write error, 5-53
ILEXER test summaries, 5-54
test number 1, main program: :MOE,

5-54
test number 10, CDISK, 5-56
test number 11, TEXER, 5-56
test number 12, EXCEPT, 5-56
test number 2, INITT, 5-54
test number 3, INICOD, 5-54
test number 4, ACQUIRE, 5-54
test number 5, INITD, 5-54
test number 6, TPINIT, 5-54
test number 7, EXERciser, 5-54
test number 8, QDISK, 5-55
test number 9, RANSEL, 5-55
ILMEMY
error message example, 5-6
error messages, 5-7
hardware requirements, 5-6
memory integrity tests, 5-5
operating instructions, 5-6
progress reports, 5-6
software requirements, 5-6
system requirements, 5-6
test summaries, 5-7
ILMEMY error messages
error 000, tested twice with no error,
5-7

ILMEMY error messages (cont' d.)
error 001, returned buffer to free buffer
queue, 5-7
error 002, memory parity error, 5-7
error 003, memory data error, 5-7
ILRX33
device integrity tests, 5-2
error message example, 5-3
operating instructions, 5-3
progress reports, 5-3
setting/clearing, 5-3
system requirements, 5-2
test parameter entry, 5-3
test summary, 5-5
test tennination, 5-3
ILRX33 Error messages, 5-4
error 000, retries required, 5-4
error 001, operation aborted, 5-4
error 002, write-protected, 5-4
error 003, no diskette mounted, 5-4
error 004, hard 1/0 error, 5-4
error 005, block number our of range,
5-4
error 006, unknown status, 5-4
error 007, data compare error, 5-4
error 008, illegal device name, 5-4
ILTAPE
boot process, 5-22
error message example, 5-27
hardware requirements, 5-22
operating instructions, 5-22
pro-gress reports, 5-27
software requirements, 5-22
system requirements, 5-22
tape device integrity test, 5-21
test tennination, 5-27
user dialogue, 5-23
user sequence commands, 5-25
user sequences, 5-25
ILTAPE error messages, 5-28
error 1, initialization failure, 5-28
error 10, load device write error--check
if write-locked, 5-28
error 11, command failure, 5-28
error 12, read memory byte count error,
5-28
error 13, fonnatter test detected error,
5-28
error 14, fonnatter test detected fatal
error, 5-28
error 15, load device read error, 5-28
error 16, insufficient resources to acquire
specified device, 5-28
error 17, K microdiagnostic did not
complete, 5-29
error 18, K microdiagnostic reported
error, 5-29
error 19, DCB not returned, K failed for
unknown reason, 5-29
error 2, selected unit not a tape, 5-28
error 20, error in DCB upon completion,
5-29

Index

ILTAPE error messages (cont'd.)
error 21, unexpected item on drive
service queue, 5-29
error 22, state line clock not running,
5-29
error 23, Init did not stop state line
clock, 5-29
error 24, state line clock did not start up
after Init, 5-29
error 25, fonnatter state not preserved
across lnit, 5-29
error 26, echo data error, 5-29
error 27, receiver ready not set, 5-29
Error 28, available set in online
fonnatter, 5-29
error 29, RX33 error-file not found,
5-29
error 3, invalid requestor/port number,
5-28
error 30, data compare error, 5-29
error 31, EDC error, 5-29
error 32, invalid multiunit code from
GUS command, 5-29
error 33, insufficient resources to acquire
timer, 5-30
error 34, unit unknown or online to
another controller, 5-30
error 4, requestor not a K.sti/K.si, 5-28
error 5, timeout acquiring drive service
area, 5-28
error 6, requested device unknown,
5-28
error 7, requested device is busy, 5-28
error 8, unknown status from tape test
interface, 5-28
error 9, unable to release device, 5-28
ILTAPE prompts
data entry, 5-25
data pattern, 5-24
drive unit number, 5-23
enter canned sequence run time in
minutes, 5-23
enter port number, 5-23
enter requestor number, 5-23
execute formatter diagnostics, 5-23
execute test of tape transport, 5-23
functional test sequence number, 5-23
how many data entries?, 5-25
input step 00:, 5-23
is media mounted, 5-23
iterations, 5-25
memory region number, 5-23
select density, 5-23
select fixed speed, 5-24
select record size, 5-25
select variable speed, 5-24
variable speeds available, 5-24
ILTAPE sequence prompts
functional test sequence number, 5-26
input step, 5-26
store sequence as sequence number,
5-26

ILTAPE sequence prompts (cont'd.)
user sequence input step entries, 5-26
ILTAPE test summaries, 5-31
canned sequence test summary, 5-31
formatter test summary, 5-31
interface test summary, 5-31
streaming sequence test summary, 5-31
user sequences test summary, 5-31
ILTCOM
error message example, 5-36
operating instructions, 5-34
system requirements, 5-33
tape compatibility test, 5-32
test parameter entry, 5-34
test summaries, 5-37
test termination, 5-36
ILTCOM error messages, 5-36
ILTCOM function select
erase, 5-35
exit, 5-35
list, 5-35
read, 5-35
rewind, 5-35
write, 5-35
ILTU58
device integrity tests, 5-5
INIPIO
test prerequisites, 4-7
INIPIO test
Init P.io test, 4-7
load fai lure steps, 4-8
operation, 4-7
system requirements, 4-7
Initialization
HSC50 or HSC50 (modified), 4-8
HSC70,4-6
Initialization error indications, 8-2
Init P.ioc diagnostic, 4-9
Internal software, 1-19
ITLCOM error messages
error 1, initialization failure, 5-36
error 10, can't find end of bunch, 5-36
error 11, data compare error, 5-37
error 12, data EDC error, 5-37
error 2, selected unit not a tape, 5-36
error 3, command failure, 5-36
error 5, specified unit not available,
5-36
error 6, specified unit cannot be brought
online, 5-36
error 7, specified unit unknown, 5-36
error 8, unknown status from TDUSUB,
5-36
error 9, error releasing drive, 5-36

K
K.ci path status information, 6-34
K.ci status bytes
00, D-4
01, D-4
02, D-4

Index

K.ci status bytes (cont' d.)
03, D-4
04, D-4
06, D-4
07, D-4
10, D-4
11,D-4
12, D-4
13, D-4
14, D-4
15, D-4
16, D-4

17, 0-5
20, 0-5
21, 0-5
·22, 0-5
23, 0-5
24, 0-5
25, 0-5
26, D-5
27, 0-5
30, 0-5
31, D-5
32, 0-5
42, 0-5
43, D-5
44, D-6
47, D-6
50, D--6
51, D--6
52, D--6
72, D--6
73, D--6
74, D--6
75, D-6
76, D-6
77, D--6
45 and 46, D--6
33 through 41, D-5
53 through 55, D-6
56 through 71, D-6
K.pli module
functions, 1-23
interfaces, 1-23
K.sdi/K.si status bytes
00, D-8
01, D-8
02, D-8
03, D-8
04, D-8
06, D-8
07, D-8
10, D-8

12, D-8
13, D-8
14, D-8
15, D-8
16, D-8
17, D-8
31, D-8
43, D-8
44, 0-9
45, 0-9

K.sdi/K..si status bytes (cont' d.)
32 through 42, 0-8
46 through 55, 0-9
74 through 76, 0-9
K.sdi module
functions, 1-24
K.si (LO 119)
switch settings, 2-13
K.si (L0119) data channel
switchpack settings, 2-12
K.si module
functions, 1-24
K.sti/K.si status bytes

000, 0-10
103, 0-10
106, 0-10
110, 0-10
112, 0-10
23, 0-10
301, 0-10
302, 0-11
304, 0-11
307, 0-11
313, 0-11
34, 0-10
37, 0-10
40, 0-10
44, 0-10
74, 0-10
35 and 36, 0-10
75 and 76, 0-10
14 through 22, 0-10
24 through 33, 0-10
41 through 43, 0-10
K.sti module
functions, 1-24
K-detected failure codes
analyzing, 0-3

L
LO 118 jumper configuration
Rev-A module, 3-14
UNK module, 1-22
ACK/NACK, 1-22
CRC, 1-22
interfaces, 1-23
packet reception, 1-23
packet transmission, 1-23
SERDES, ENDEC, 1-22
Logic modules, 1-21
card cage
module utilization label, 1-5, 1-9

M
M.std2 module
Control memory (M.ctl), 1-25
Data memory (M.dat), 1-25
functions, 1-25
Program memory (M.prog), 1-25
RX33 diskette controller (K.rx), 1-25
M.std module

Index

M.std module (cont'd.)
functions, 1-26
Maintenance features, 1-28
Maintenance tenninal connection
HSC50 or HSC50 (modified), 4-3
Microcode-detected errors
K.ci, D-7
K.sdi/K.si, D-9
K.sti/K.si, D-11
Miscellaneous errors, 8-49
Mode byte field, 8-29
description, 8-30
Module LEDs
data channel LEDs, 8-10
host interface LEDs, 8-10
memory module LEDs, 8-10
P.ioj/c, 8-8
P.ioj/c LEDs
power up sequence, 8-9
Module table, 1-21
Moving inversions algorithm, 6-32
MSCP/fMSCP controller errors, 8-26
MSCP/fMSCP error flags, 8-25
MSCP/fMSCP error fonnat, 8-24
description and flags, 8-23
MSCP/fMSCP error message fields, 8-24
MSCP/fMSCP fonnat type codes, 8-25
MSCP errors, 8-23
disk transfer errors, 8-31
SDI errors, 8-26
MSCP processor, 1-20
MSCP status codes
lLDISK error reports, 5-18

o
OCP controls and indicators, 2-1
Blank indicators, 2-3
fault codes, 2-2
Fault indicator and switch, 2-2
Init switch, 2-2
lamp test, 2-3
Online indicator, 2-3
Online switch, 2-3
Power indicator, 2-2
State and Init indicators, 2-2
OCP fault code
interpretation, 8-3
OCP fault code 31 actions
illegal inst, 8-7
K.ci host reset, 8-8
level 7 interrupt, 8-7
Memory Management Unit (:M:MU) trap,
8-8
NX.M trap, 8-7
parity trap, 8-7
software crash, 8-8
OCP fault code displays, 8-2
OCP fault code interpretation
fault code 1, K.pli error, 8-4
fault code 10, P.ioj cache failure, 8-4
fault code 11, K.ci failure, 8-4

OCP fault code interpretation (cont'd.)
fault code 12, data channel module
failure, 8-4
fault code 2, K.sdi/K.si incorrect version
of microcode, 8-4
fault code 21, P.ioj/c module failure,
8-4
fault code 22, M.std2 module failure,
8-4
fault code 23, boot device failure, 8-5
fault code 25, port link node address
switches out of range, 8-5
fault code 26, missing files required,
8-5
fault code 3, K.sti/K.si incorrect version
of microcode, 8-4
fault code 30, no working K.ci, K.sdi,
K.sti, or K.si in subsystem, 8-6
fault code 31, initialization failure, 8-6
fault code 32, software inconsistency,
8-8
OCP fault codes, 8-4
Offline bus interaction memory test
configuration, 6-29
Offline bus interaction test, 6-25
error infonnation, 6-28
operating instructions, 6-26
parameter entry, 6-27
prerequisites, 6-26
progress reports, 6-28
system requirements, 6-26
Offline bus interaction test error messages,
6-29
error OOO-memory test error, 6-29
error 001-K timed-out during Init,
6-30
error 002-K timed-out during test,
6-30
error 003-parity trap, 6-30
error 004-NXM trap, 6-30
error OOS-memory test error (P.ioj/c)
detected, 6-31
error 011-RX33 drive 110t ready, 6-31
error 012-RX33 CRC error during
seek, 6-31
error 013-RX33 track 0 not set on
recalibrate, 6-31
error 014-RX33 seek timeout, 6-31
error 01S-RX33 seek error, 6-31
error 016--RX33 read timeout, 6-31
error 017-RX33 CRC/RNF error on
read command, 6-31
error 10 (12 octalkache parity error,
VPC = xxxxxx, 6-31
Offline cache test
error infonnation, 6-20
operating instructions, 6-19
parameter entry, 6-19
progress reports, 6-20
system requirements, 6-] 9
Omine cache test descriptions, 6-23

Index

Offline cache test descriptions (cont'd.)
test II-abort/interrupt on parity errors,
6-25
test I2-DMA invalidate, 6-25
test 13-check blockage of parity error
on NXM abort, 6--25
test 14-cache data RAM test, 6-25
test 15-tag store RAM test, 6-25
test 16----data RAM reliability test, 6-25
test I-cache register access test, 6-23
test 2-cache control resister bits, 6-23
test 3-force miss action, 6-23
test 4-hit/miss register, part I, 6--23
test 5-hit/miss resister, part IT, 6--24
test 6-byte accesses, 6--24
test 7-PDR cache bypass test, 6-24
test 8-cache flush action, 6-24
test 9-unconditional bypass to main
memory, 6--24
test force tag/data parity errors, 6-24
Omine cache test error messages, 6-20
error OO---memory parity error, 6-20
error OI-NXM: trap, 6-21
error 02-cache parity error, 6-21
error 03-bit stuck in cache control
register, 6-21
error 04-forced miss operation failed,
6--21
error 05-forced miss with abort failed,
6-21
error 06--expected cache hit did not
occur, 6--21
error 07-expected cache miss did not
occur, 6--21
error IO-value in hit/miss register
incorrect, 6--21
error II-write byte operation caused
cache update, 6--21
error 12-write byte did not cause cache
update, 6-21
error 13-cache failed to flush
successfully, 6-21
error 14---access with force bypass did
not cause invalidate, 6--21
error 1s.-tag parity error did not set,
6-21
error 16-abort on parity error did not
occur, 6-21
error 17-unexpected parity trap during
abort test, 6-21
error 2O-content of memory system
error register incorrect, 6-22
error 21-return PC wrong during
abort!interrupt test, 6-22
error 22 cache data parity bit(s) did not
set, 6-22
error 23-interrupt on parity error did
not occur, 6--22
error 24-expected NXM: trap did not
occur, 6-22

Offline cache test error messages (cont' d.)
error 25-parity error was not blocked
by NXM:, 6--22
error 26-cache data miscompare on
word operation, 6-22
error 27-c-ache data miscompare on
byte operation, 6-22
error 30-DMA write to memory did
not cause cache to invalidate, 6-22
error 31-instruction still completed
during abort condition, 6-22
error 32-load device error during DMA
test, 6-22
error 33-PDR cache bypass failed,
6-22
error 34---tag store address hit failure,
6-22
error 35-tag store address miss failure,
6-23
error 41--processor type is not J11,
6-23
Offline cache test troubleshooting, 6-23
Offline common characteristics, 6--1
Offline diagnostics
bootstrap failures, 6--3
boot<strap initialization, 6--3
bootstrap operational requirements, 6-2
EXAMINE and DEPOSIT qualifiers
(switches), 6-13
HSC50 load procedure, 6-2
HSC70 load procedure, 6-2
loader help file, 6-16
memory refresh test, 6-68
offline cache test, 6-19
P.ioj/c ROM bootstrap, 6-2
softwa..~ requirements,

6--1

trap and interrupt vectors, 6-15
Offline diagnostics KIP memory test, 6-41
Offline diagnostics loader, 6-8
commands, 6-9
HELP command, 6-9
operating instructions, 6-9
prerequisites, 6-9
SIZE command, 6-10
system requirements, 6-9
TEST command, 6-10
Offline diagnostics memory test, 6-52
error information, 6-54
operating instructions, 6-52
parameter entry, 6-52
parity errors, 6-53
progress reports, 6-53
quick verify algorithm, 6-52
system requirements, 6-52
Offline diagnostics OCP test, 6-71
operating instructions, 6-72
parameter entry, 6-72
system requirements, 6-71
Offline diagnostics tape
HSC50 or HSC50 (modified), 4--8
Offline diagnostics tests
asterisk (*) symbolic address, 6-11

Index

Offline diagnostics test") (confd.)
at symbol (@) symbolic address, ~12
bus interaction test, ~ 10
cache test, 6-10
DEPOSIT command, 6-11
EXAMINE and DEPOSIT commands,
6-11
EXAMINE command, 6-11
INDIRECT command files, 6-14
KIP memory test, 6-10
K test selector, 6-10
LOAD command, 6-10.
memory refresh test, 6--10
memory test, ~10
minus sign (-) symbolic address, 6--12
OCP test, 6-10
plus sign (+) symbolic address, 6--11
qualifier switch /byte, 6--13
qualifier switch /DECIMAL, 6--14
qualifier switch /HEX, 6--14
qualifier switch /lNffiBIT, 6--14
qualifier switch /long, 6--13
qualifier switch /next, 6--13
qnalifier switch /OCTAL, 6--14
qualifier switch /quad, 6--13
qualifier switch /word, 6-13
relocation register, 6--13
repeating EXA1v1INE and DEPOSIT
commands, 6--12
RX33 exerciser, 6--10
set default command, 6--14
START command, ~10
symbolic addresses, 6--11
Offline diagnostic WCS loader, 6--17
load command, 6--18
offline K WCS command, 6--17
operating instructions, 6--18
parameter entry, 6--18
system requirements, ~18
Offline generic error message fonnat, 6--8
Offline KIP memory test
error infomlation, fr44
error messages, 6--45
error summary infonnation, 6--44
operating instructions, 6--41
panuneter entry, 6--41
parity errors, 6--43
progress reports, 6--43
system requirements, 6--41
Omine KIP memory test error messages
error 000, 6--45
error 001, 6--46
error 002, 6--47
error 003, 6--47
error 004, 6--48
error 005, 6--48
error 006, 6--49
error 007, 6--49
error 008, 6--50
error 009, ~50
error 010, 6--50
error 011, 6--50

Offline KIP memory test error messages
(cont'd.)
error 013-cache parity trap, VPC =
XXXXXX, 6--51
Offline KIP memory test summaries, 6--51
test OOO-moving inversions test from
P.ioj/c, 6--51
test 001-moving inversions test from
K, 6--51
Offline K test selector, 6--32
error infonnation, 6--34
error messages, 6--34
operating instructions, 6--32
parameter entry, 6--33
progress reports, ~33
summaries, 6--39
system requirements, 6--32
Offline K test selector errors
error 000, 6--34
error 001, ~35
error 002, 6--35
error 003, 6--36
error 004, 6--36
error 005, 6-37
error 006, 6--37
error 007, 6--38
error 008, ~38
error 009, 6--39
error 010, ~39
error 011, 6--39
error 012, ~39
error 013-cache parity trap, VPC =
XXXXXX, 6--39
Offline K test selector summaries
test OOO-moving inversions test, 6--39
test 00 1 through 011 (K microdiagnostics), 6--40
Offline K WCS loader prompts
list of requestors, ~18
load other requestors, ~ 19
WCS file to use, 6--19
Offline memory test error messages, 6--54
error 000, ~54
error 001, 6--55
error 002, 6--55
error 003, 6--56
error 004, 6--56
error 005, 6--57
error 006, 6--57
error 007, 6--58
error 008, 6--59
error 009, 6--59
error 010, 6--60
error 011, 6-60
error 012, 6--60
error 013, 6--60
error 014, 6--61
error 015, 6--61
error 016-cache parity trap, VPC =
XXXXXX, 6--61
Offline memory test summaries, ~1
test OOO-quick verify test, ~ 1

Index

Offline memory test summaries (cont'd.)
test 00 I-moving inversions test, ~ 1
test 002-walking Is test, 6-62
OOOne OCP registers and displays via
ODT,6-76
Offline OCP test error infonnation, 6-73
Offline OCP test error messages, 6-74
error OOO-wrong bit set, 6-74
error 00 I-bit set when Init is pressed,
6-74
Offline OCP test lamp bit check via ODT,
6-78
Offline OCP test Secure/Enable switch
check via ODT, 6-78
Offline OCP test State LED check via
ODT,6-80
Offline OCP test summaries, 6-74
test OOO-observe enable and State
LEDs, 6-74
test 001-lamp test via Fault switch,
6-74
test 002~heck all switches off, 6-74
test 003-Fault switch, 6-75
test OO4-OnJine switch, 6-75
test 005-first unmarked switch, 6-75
test 006-second unmarked switch,
6-75
test 007-enable LED off, 6-76
lest oo9-break key in secure mode,
6-76
Omine
test switch check via ODT,
6-76
Offline refresh test
error information, 6-70
operating instructions, 6--69
parameter entry, 6--69
progress reports, 6-70
system requirements, 6-69
Omine refresh lest error messages, 6-70
error 01, 6-70
error 02, 6-70
error 03, 6-70
error 04, 6-70
error 05-cache parity trap, VCP =
XXXXXX, 6-71
Offline refresh test summaries, 6-71
test Ol-pattern 177777, 6-71
test 02-pattern 000000, 6-71
test 03-pattern 100001, 6-71
Operational status codes
example examination, 0-3
requestors, 0-3
Operator Control Panel
Init switch, 2-2
Original error flags field description, 8-33
OUl-or-band errors, 8-46
categories, 8-46
CI errors, 8-46
disk functional errors, 8-46
load device errors, 8-46
miscellaneous, 8-46
tape functional errors, 8-46

ocr

p
PJoj/c modules
function, 1-25
Parameters
LA12, 4-5
PILA module
functions, 1-23
881 power controller
BUS/ON/OFF switch, 2-21
circuit breaker, 2-20
description, 2-18
DIGITAL power Control bus
connections, 2-21
fuse, 2-20
operating instructions, 2-19
TOTAL OFF connector, 2-21

R
Recovery flags field definition, 8-34
Request byte field, 8-28
description, 8-29
Requestor error summary, 6-29
Requestor status
nonfailing requestors, 8-12
Revision matrix chart
HSC50, B-ll
HSC50 (modified), E-6
HSC70, B-1
RX33 error code table, 6-7
RX33 elTDr table~ 6-6
RX33 load device
CSR breakdown, 8-47
error message last line breakdown, 8-48
errors, 8-46
status register summary, 8-47
RX33 offline exerciser, 6--62
data patterns, 6--68
error information, 6-64
operating instructions, 6--62
parameter entry, 6--63
progress reports, 6--63
system requirements, 6--62
RX33 offiine exerciser error messages,
6-64
error OO-parity trap, VPC = xxxxxx,
6-64
error 01-NXM: trap, VPC = xxxxxx,
6-64
error 02-bit stuck in register, 6-64
error 03-interrupt occurred without
enable set, 6-64
error 04-RX33 interrupt occurred at
wrong priority, 6-65
error 05--unexpected interrupt from
RX33, 6--65
error 06-track 0 did not set after
recalibrate command, 6-65
error 07-RX33 did not interrupt as
expected, 6-65

Index

RX33 offline exerciser error messages
(cont'd.)
error 10--seek error detected during
positioning operation, fH>5
error ll-current track resister incorrect,
6-65
error 12-CRC error in header detected
during position verify, 6-65
error 13-processor type is not JII,
6-65
error 14--drive under test is not ready,
6-65
error 15-last command did not
complete, 6-65
error 16-RX33 header does not
compare, 6-65
error 17-record not found during read
(could also say write), 6--65
error 2O-CRC error in date during read
(could aL~o say write), 6--66
error 21-lost data detected during read
(could also say write), 6--66
error 23-invalid pattern code in buffer,
6-66

error 24--drive is write-protected, 6-66
error 25-CRC error in header during
read (could also say write), 6-66
error 26---{lata incorrect after DMA test
mode command, 6-66
error 27--data compare error, 6-66
error 30--RX33 detected parity error
during read (could also say write),

RXFMT (cont 'd)
RX fonnat utility, 7-27
RXFMT error messages
RXFMT-E No media mounted in unit,
7-28
RXFMT-E Please answer either Y or N,
7-28
RXFMT-E Read failure on unit DXn:,
7-28
RXFMT-E Requested unit is unavailable,
7-28
RXFMT-F Aborting, 7-29
RXFMT-F Error comparing track, 7-29
RXFMT-F Error fonnatting track, 7-29
RXFMT-F Error reading track, 7-29
RXFMT-F Unable to allocate sufficient
mapped memory, 7-29
RXFMT-F Unable to allocate sufficient
resources, 7-29
RXFMT-F Unable to allocate sufficient
XFRBs, 7-29
RXFMT-I Fonnatting track, side, LBN,
7-29
RXFMT-I Please specify a valid unit,
7-29
RXFMT-I Program exit, 7-29
RXFMT-I Verifying track, side, LBN,
7-29
RXFMT-Q Mount diskette in DXn:,
7-29
RXFMT-Q Really perfonn fonnat
(YIN)?, 7-29

RXFMT-Q Unit to fonnat (DXO: or
OX1:)?, 7-29
RXFMT-S Fonnat successfully
completed, 7-29
RXFMT-W About to format diskette in
boot device, 7-29
RXFMT-W FORMAT NOT
SUCCESSFUL, 7-28
RXFMT-W Hardware or Verify errors,
7-28
RXFMT-W Invalid device name oXn:,
7-28
RXFMT-W No default unit allowed,
7-28
RXFMT-Write failure on unit OXl:,
7-28

6-66

error 31-RX33 detected NXM during
read (could also say write), 6-66
error 32-RX33 MAR value incorrect
after OMA transfer, 6-66
error 33-parity error was not forced in
main memory, 6--66
error 34--parity error did not set in
CSR,6-67
error 35-NXM did not set in CSR,
6-67
error 36-parity error set along with
NXM in CSR, 6-67
error 37-cache parity error, VPC XXXXXX, 6-67
RX33 offline exerciser test summaries,
6--67
test I-RX33 controller registers, 6-67
test 2-interrupt hardware, 6-67
test 3-DMA login and counters, 6-67
test 4-parity logic, 6-67
test 5-verify track counters and
registers, 6-67
test 6-oscillating seek test, 6-67
test 7-sequential read/write test, 6-68
test 8-random reads/writes, 6-68
RXFMT
initiation, 7-27
messages, 7-28

s
Safety precautions, 3-1
SOl error printout, 8-26
field description, 8-27
SDI errors
controller-detected transmission or time
out error, 8-60
drive clock dropout, 8-66
drive-detected error, 8-66
drive inoperative, 8-66

Index 21

SDI errors (cont'd.)
drive-requested error log (EL bit set),
,
8-67
header error, 8-70
lost Read/Write Ready, 8--77
lost Receiver Ready, &-77
position or unintelligible header error,
8-85
pulse or parity error, 8--86
SDI clock persisted after Init, 8-90
SI clock resumption failed after !nit,
8-90
SI command timeout, 8-91
SI Receiver Ready collision, 8-91
SI response length or Opcode error,
8-92
SI response overflow, 8-92
SDI manager, 1-20
SETSHO, SET
failed in sending HMB to Disk Server
for SET Dn LNO]HOST, B-38
failed in sending lTh1B to Tape Server
for SET Tn [NO]HOST, B-38
SETSHO, SHOW
failed in sending HMB to Disk Server
for SHOW Dn, B-38
failed in sending lTh1B to Tape Server
for SHOW Tn, B-39
scr crash context table contained too
many characters, B-39
SETSHO, SSMAlN
an XFRB was not required to print
messages, B-38
failed to properly send lTh1B to K.ci,
B-38
the scr crossed a page boundary, B-38
too many characters intended for console
printout, B-38
SIN!
divide operation set overflow, B-39
double word math not conC)istent, B-39
multiply operation set overflow, B-39
SINI-E error printout, B-2
example, B-2
SINI errors
booted from drive 1. Drive 0 error
(text), 8--58
cache disabled due to failure, 8-59
See miscellaneous errors, 8-49
SINI out-of-band errors
hard transfer error loading (file) xx,
8-70
hard transfer error writing scr xx,
8--70
host clear from a node, 8--71
host interface (K.ci) failed INIT diags,
status xxx, 8-72
host interface (K.ci) is required but not
present, 8-72
last soft Init resulted from unknown
cause, 8--75

SINI out-of-band errors (cont'd.)
less than 87.5 percent of xx memory is
available, 8-76
P.ioj/c running with memory bank. or
board swap enabled, 8-84
parity error Trap ihrough 114, 8-84
requestor xx failed lNIT diags, status =
xxx, 8-88
reserved instruction Trap through 10,
8-88
scr read or verification error. Using
template scr., 8-89
software inconsistency Trap through 20,
8-93
subsystem exception, level 7 K interrupt
Trap through 134, 8-76
subsystem exception, MN.IU Trap
through 250, 8-78
subsystem exception, NXM Trap
through 4, 8-83
subsystem exception, parameter change,
process yyy, 8-84
subsystem exception, PC xxx, 8-84
subsystem exception, PSW xxx, 8--84
subsystem exception, Reason xxx, 8-84
Software, 1-19
Software error messages
categories, 8-23
Software Release Notes, 1-1
Status bytes interpretation
K.ci, D-7
K.sdi/K.si, D-9
K.sti/K.si, D-l1
Status or event codes
MSCP, C-2
TMSCP, C-2
STI bus
Maximum number of tape formatters,
1-2
STI manager, 1-20
SUBLIB, ERTYP
process does not have windows declared,
B-40
Subsystem block diagram, 1-20
Subsystem exception
K-detected error printout example, D-l

T
TAPE, TFATNAVAL
an STI GET UNE STATUS failed,
B-26
received an interrupt from an unknown
tape data channel, B-26
TAPE, TFCI
received an illegal Connection Block
(CB) from the CIMGR, B-27
TAPE, TFDIAG
an illegal diagnostic Opcode was
received, B-27

Index

TAPE, TFDJAG (cont'd.)
diagnostics trying to acquire assigned
Drive State Area, B-27
inconsistencies during Drive State Area
acquisition, B-27
no Block Header supplied by BACKUP,
B-27
no buffers supplied in BACKUP
operation, B-28
TAPE,TFERR
illegal downcount occurred on a Host
Message Block (HMB) chain, B-31
K.ci did not return a Fragment Request
Block (FRB), B-31
sequence number corruption occurred,
B-32
unexpected Fragment Request Block
(FRB) error received, B-31
unknown Fragment Request Block
(FRB) error received, B-31
TAPE, TFLIB
could not allocate an XFRB, B-28
TAPE,TFMSCP
required CIMGR functionally not
implemented, B-28
required CIMGR functionally not yet
implemented, B-28
TAPE, TFSEQUEN
an invalid density is set in the Tape
Drive Control Block (TDCB), B-29
could not find correct Tape Drive
Control Block (IDCB) pointer,
B-29
KT$SEM is equal to zero, B-30
read reverse emulation not flagged,
B-29, B-30
requested transfer larger that 64 Kb,
B-30
route pointer for read reverse emulation
zero, B-29
tape formatter does not support allowed
densities, B-29
unable to allocate an HOB, B-29
TAPE,TFSERVER
no available stacks, B-30
top of User stack for a resume is not set
to server return, B-30
TAPE, TFSTI
no stack available to suspend with,
B-3 1
TAPE,TXREVERSE
buffer descriptor address missing, B-31
Tape errors
acknowledge not asserted at start of
transfer, 8-56
buffer EDC error, 8-58
controller-detected position lost, 8~0
controller transfer retry limit exceeded,
8-60
could not complete online sequence,
8-61

Tape errors (cont'd.)
could not get extended drive status,
8-61
could not get formatter summary status
during transfer error recovery, 8-61
could not get formatter summary status
while trying to restore tape position,
8~1

could not position for formatter retry,
8-61
could not set byte count, 8~2
could not set unit characteristics, 8-62
data ready timeout, 8-63
ERASE command failed, 8-67
ERASE GAP command failed, 8~8
formatter and HSC disagree on tape
position, 8-68
fonnatter-detected position lost, 8-68
fonnatter-requested error log, 8-69
formatter retry sequence exhausted,
8-69
host requested retry suppression on a
formatter-detected error, 8-72
host requested retry suppression on a
K.sti/K..si-detected error, 8-73
Lower Processor error, 8-78
Lower Processor timeout, 8-78
Receiver Ready not asserted at start of
transfer, 8-87
record EDC error, 8-87
retry limit exceeded while attempting to
restore tape position, 8-89
reverse retry currently not supported,
8-89
rewind failure, 8-89
tape drive requested error log, 8-93
topology command failed, 8-96
unable to position to before LEOT,
8-96
unclearable drive error, 8-96
unclearable formatter error, 8-97
unknown K.tape error, 8-97
word rate clock timeout, 8-100
Tape functional errors, 8-49
Tape functional out-of-band errors
data error flagged in backup record,
8-62
increase drive structures via SET MAX_
TAPE command, 8-80
increase formatter structures via SET
MAX_FORMATTER command,
8-81
insufficient Control memory for
K.sti/K..si in requestor xx, 8-73
insufficient private memory remaining
for TMSCP Server, 8-73
K.sti/K.si in requestor xx has microcode
incompatible with this TMSCP
Server, 8-75
no tape drive structures available for
Requestor xx Port xx Unit xx, 8-80

Index 23

Tape functional out-of-band errors (cont'd.)
no tape fonnatter structures available for
Requestor xx Port xx, 8-81
no usable K.sti/K.si boards were found
by the TMSCP Server, 8-81
requestor xx has failed initialization
diagnostics with status = xx,. 8-88
tape fonnatter declared inoperative,
8-93
tape unit number xx connected to
requestor xx port xx ceased to exist
while online, 8-93
tape unit number xx connected to
requestor xx port xx dropped state
clock, 8-94
tape unit number xx connected to
requestor xx port xx went available
without request, 8-94
tape unit number xx connected to
requestor xx port xx went offline
without request, 8-95
TMSCP fatal initialization errorTMSCP functionality not available,
8-95
TMSCP Server operation limited by
insufficient private memory, 8-95
1TRASH fatal initialization error, 8-96
......... WARNING ......... K.sti/K.si microcode
too low for large transfers., 8-100
Tape I/O man~ger, 1-20
TMSCP specific errors, 8-36
GEDS text field breakdown, 8-41
GSS text field bit interpretation, 8-43
GSS text field breakdown, 8-42
S11 communication or command error
printout, 8-37
S11 communication or command errors,
8-37
S11 communication or command
printout field description, 8-37
S11 drive error log, 8-38
STI drive error log (TA78 drive
specific), 8-39
S11 drive error log field description,
8-38
STI drive error log printout, 8-38
S11 fonnatter E log, 8-37
S11 fonnatter error log, 8-37
S11 fonnatter error log field description,
8-37
S11 GEDS text, 8-38
Traps, 8-49
level 7 K interrupt (Trap through 134),
8-50
level 7 K interrupt printout, 8-51
1vlMU (Trap through 250), 8-53
NXM (Trap through 4), 8-49
parity error (Trap through 114), 8-50
reserved instruction (Trap through 10),
8-50

Traps (cont' d.)
software inconsistency (Trap through
20), 8-54

u
tlpper and Lower Processor
K.ci error register bits, 0-7
Upper Processor
K.sdi/K.si error register bitl), 0-9
K.sti/K.si error register bits, 0-11
Utilities
default prompts, 7-1
Utility processes, 1-20

v
VERIFY
error classes, 7-16
error message severity levels, 7-18
errors and infonnation messages, 7-18
fatal error messages, 7-19
infonnational messages, 7-21
initiation, 7-16
offline disk verifier utility, 7-15
process steps, 7-15
sample session, 7-17
type error messages, 7-20
variable output fields, 7-18
warning messages, 7-19
VERIFY fatal elT-OI' messages
VERIFY-F All copies of the xCT block
n are bad, 7-19
VERIFY-F Current system sector size is
512, 7-19
VERIFY-F Drive went offline, 7-19
VERIFY-F 1/0 request was rejected,
7-19
VERIFY-F Insufficient resources to run,
7-19
VERIFY-F Mode is bad or fonnat is in
progress on this unit, 7-19
VERIFY infonnational messages
VERIFY-I copy of n of xCT block n
(xBN n.) is bad, 7-21
VERIFY-I CTRL/Y or CTRL/C abort,
7-21
VERIFY-I DBN area should probably be
refonnatted, 7-21
VERIFY-I Drive is OK, 7-21
VERIFY-I initial write should be
specified for ILEXER, 7-21
VERIFY-! LBN n., a primary, has a bad
header (is non-primary), 7-21
VERIFY-I There were inconsistencies
found for this drive, 7-21
VERIFY-I xBN n. has a n symbol
correctable ECC error, 7-21
VERIFY-I xBN n. has a transient (n out
of 6) x error, 7-21

Index

VERIFY infonnational messages (cont'd.)
VERIFY-I xBN n. has solid errors: x.,
7-21
VERIFY type error messages
VERIFY-l LBN n. has corrupted data
(forced error), 7-20
VERIFY-t RBN n. is good but not used
for a revector, 7-20
VERIFY-t RBN n. marked bad in the
Ref was not bad, 7-20
VERIFY-t xBN n. has an uncorrectable
ECC error, 7-21
VERIFY warning messages
VERIFY-W cannot online unit, 7-19
VERIFY-W cannot read track with
starting xBN n, 7-19
VERIFY-W copy n of xCf block n
(xBNn.) does not compare, 7-19
VERIFY-W illegal response to start-up
question, 7-19
VERIFY-W LBN n., a non-primary
revector, is improper, 7-19
VERIFY-W LBN n., a primary revector,
is improper, 7-19
VERIFY-W LBN n. revectors to RBN
n. which is bad, 7-20
VERIFY-W n bad PBNs not in the RCf,
7-19
VERIFY-W nonexistent unit number,
7-20
VERIFY-W unit is not available, 7-20
VERIFY-W xBN n. has a hard EDC
error, 7-20
VERIFY-W xBN n. I/O error in access
(MSCP code: 0), 7-20
VER I FY-W xBN n. is bad but not in
the RCf, 7-20
Voltage test points
HSC50 (modified) auxiliary power
supply, 3-51
HSC50 (modified) main power supply,

3-48
HSC50 auxiliary power supply, 3-72
HSC50 main power supply, 3-69
HSC70 auxiliary power supply, 3-26
HSC70 main power supply, 3-23
VTDPY
CfRL/x display commands, 7-30
data bandwidth display explanation,
7-32
Disk or Tape Status display explanation,
7-34
display example, 7-31
display explanation, 7-31
error messages, 7-30
free lists and pool size display
explanation, 7-31
host connection display explanation,
7-32
Host Path Status display explanation,
7-32

VTDPY (cont'd.)
interval updates, 7-30
introduction, 7-30
process priority status display
explanation, 7-33
running VTDPY t 7-30
tenninating VTDPY, 7-30