top - download
⟦dbdd24d20⟧ Wang Wps File
Length: 98472 (0x180a8)
Types: Wang Wps File
Notes: ASC - GREECE, TECHNICAL
Names: »4661A «
Derivation
└─⟦4ac6f2002⟧ Bits:30006023 8" Wang WCS floppy, CR 0438A
└─ ⟦this⟧ »4661A «
WangText
U…00……00……00……00…#…0a……00……00…#…0b…#…01…"…08…"…0c…" !…09…!…0e…!…02…!…05…!…06… …0e… …05……1f……08……1f……0a……1f… …1e……0b……1e… …1e……07……1d……0d……1d……0e……1d…
…1c……0e……1c……0f……1c……01……1b……08……1b……0e……1a……08……1a……0e……1a… …19……09……19……01……18……0a……18……01……18……07……17……08……17……09……17……0a……17…
…17… …17……05……16……0e……16……86…1 …02… …02… …02… …02…
ASC GREECE - PART II SYS/84-03-10
TECHNICAL PROPOSAL Page
4̲ ̲ ̲A̲S̲C̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲/̲T̲E̲C̲H̲N̲I̲C̲A̲L̲ ̲A̲S̲S̲I̲S̲T̲A̲N̲C̲E̲
4.1 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲P̲H̲I̲L̲O̲S̲O̲P̲H̲Y̲
4.1.1 G̲e̲n̲e̲r̲a̲l̲
The maintenance concept described in this chapter is
based on Christian Rovsing A/S (CR) having a system
maintenance specialist placed within HCAA during the
warranty period.
However, CR assumes that HCAA takes over the responsibility
for all on site maintenance from the installation and
onwards. The following sections describe the contents
of this responsibility in case that CR was participating.
If so wanted this will be included in a separate maintenance
contract.
4.1.1.1 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲P̲l̲a̲n̲n̲i̲n̲g̲
The purpose of the Maintenance Planning Phase is to
establish a complete maintenance program which will
fulfill the contractual requirements for maintenance
and insure system reliability and availability to HCAA.
Simultaneously it shall provide a solid base for the
development of a detailed maintenance documentation.
4.1.1.2 M̲a̲i̲n̲t̲a̲n̲e̲n̲c̲e̲ ̲P̲l̲a̲n̲
a) I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
The basic philosophy used in the configuration
of the system is to enable maintenance, both preventive
and emergency, to be performed with a minimum of
system downtime thereby meeting the availability
requirements. This is achieved through the use
of redundant hardware modules and by extensive
use of the board swap principle once the sophisticated
fault detection software has isolated a faulty
assembly.
b) M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲
Maintenance engineering describes the effort in
the area of maintenance and support necessary prior
to the installation of the equipment.
The general approach to preventive maintenance
is that the applicable procedures are referenced
via an overall system maintenance sheet incorporated
in the various technical manuals. The special
tools and test equipment which will be used for
maintenance are listed and their applications shown
through scenarious displaying the structure of
the hardware with breakpoints.
A failure reporting system will be generated and maintained.
Incorporated in this system are:
- A maintanance record which will be filled in at
the installations and used in the screening of
systematic errors and used to modify the spare
parts stock.
- a log book which will be located at the installation.
- Field Change Notices (FCN) used as applicable for
updating of the systems.
c) O̲n̲-̲S̲i̲t̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
During the warranty period a resident system maintenance
specialist will be on-site during normal business
hours
The technicians selected by HCAA to perform system
maintenance are having several years experience
in supporting similar systems. The technicians
will carry out preventive and corrrective maintenance
both on the CR80 equipment and the connected peripherals
as well as on the delivered software. The preventive
maintenance required on the CR80 equipment is restricted
to simple tasks such as cleaning of dust filters,
inspection of LED's etc. Emergency maintenance
will typically be carried out on a module/terminal
exchange basis. The trouble
shooting techniques developed for the system configuration
will enable the maintenance personnel to isolate
and replace modules in the CR80 equipment within
one hour. Also the technicians will perform modifications
according to Field Change Notices.
d) M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
The maintenance technicians will carry out 1st
level maintenance consisting of preventive and
emergency maintenance as previously described.
In most cases logic boards with known faults will
be returned to Christian Rovsing A/S for repair
and then returned to the spare parts complement
of the site. In some instances faulty module,
i.e. power supply, fan assembly, will be repaired
on-site. Christian Rovsing A/S will provide 2nd
and 3rd level maintenance through field service
engineers, in house repair facilities, and software
maintenance support.
4.1.2 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲S̲t̲r̲a̲t̲e̲g̲y̲ ̲(̲H̲a̲r̲d̲w̲a̲r̲e̲)̲
4.1.2.1 P̲r̲e̲v̲e̲n̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
Preventative maintenance will be carried out by the
site technicians, in accordance with the procedures
established in the maintenance manual. The overall
design of the system utilizing redundant hardware will
insure that preventive maintenance will have a minimal
effect on the performance of the system.
4.1.2.2 E̲m̲e̲r̲g̲e̲n̲c̲y̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
Emergency maintenance, i.e. fault identification and
module replacement will be carried out by the site
technicians. Repair of defective subassemblies will
be undertaken by Christian Rovsing A/S at no cost during
the warranty period.
Isolation of faulty subassemblies is accomplished by
the use of both on-line and off-line Maintenance &
Diagnostic (M&D) software programs. On-line error detection
programs will detect hardware faults when they occur.
This is accomplished both by background checks and
by error detection during data transfer from one subsystem
to another. Depending on the type of fault the "Watchdog"
subsystem will reconfigure the system designating the
standby processor as active. The defective subsystem
is now off-line where further fault diagnosis can take
place in the event the on-line diagnostic program did
not give specific error identifications pinpointing
a specific module. The off-line diagnostic program
provides for a much more thorough check of the various
elements of a subsystem. In addition, this program
will be used to verify repaired modules.
4.1.2.3 W̲o̲r̲k̲s̲h̲o̲p̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
All equipment placed within the workshop will be maintained
and repaired by the HCAA hardware technicians. All
applicable Tools & Test Equipment is described in chapter
8 of this proposal.
4.1.3 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲S̲t̲r̲a̲t̲e̲g̲y̲ ̲(̲S̲o̲f̲t̲w̲a̲r̲e̲)̲
4.1.3.1 T̲h̲e̲ ̲A̲S̲C̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
All software development and maintenance will be done
at the equipment delivered to the workshop. In some
rare cases, i.e. implementation and test, the standby
system of the operational system,will be used.
4.1.3.2 F̲i̲r̲m̲w̲a̲r̲e̲
The software team will be responsible for implementation
and maintenance of all firmware delivered.
4.1.4 I̲m̲p̲a̲c̲t̲ ̲o̲n̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
4.1.4.1 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
The equipment to be used for hardware and software
maintenance is described in chapter 8.
4.1.5 I̲m̲p̲a̲c̲t̲ ̲o̲n̲ ̲S̲t̲a̲f̲f̲i̲n̲g̲ ̲a̲n̲d̲ ̲T̲r̲a̲i̲n̲i̲n̲g̲
Staffing and training are described in detail in chapter
7 of this proposal.
The training program for the ASC system will be developed
by the responsible hardware- and software engineers
in connection with Christian Rovsing's own training
staff.
4.1.6 S̲p̲e̲c̲i̲a̲l̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
Attached to this chapter as Annex 1, requirements for
M&D software developed for similar projects, is to
be found.
These requirement will be the guideline for the ASC
M&D program to be developed. The use of M&D programs
is described in chapter 4.1.2.2 of this proposal.
4.2 T̲E̲C̲H̲N̲I̲C̲A̲L̲ ̲A̲S̲S̲I̲S̲T̲A̲N̲C̲E̲
4.2.1 G̲e̲n̲e̲r̲a̲l̲
The maintenance of the equipment will, from the provisional
acceptance date and on, be HCAA responsibility.
4.2.1.1 F̲i̲e̲l̲d̲ ̲S̲u̲p̲p̲o̲r̲t̲
Field service engineers will be available from Christian
Rovsing A/S facilities in Copenhagen. This function
will, together with the repair facilities and spares
stock provided at Christian Rovsing A/S, provide the
2nd level of maintenance. The 3rd level of maintenance
is software and hardware maintenance support performed
by Engineers resident at Christian Rovsing. This personnel
will assist the Field Service Engineers in case of
severe problems. After the warranty period, a support
contract can be negotiated.
4.2.1.2 R̲e̲p̲a̲i̲r̲
Repair of modules and subassemblies will be undertaken
by CR free of charge during the warranty period, as
specified in the RFP. After the warranty period a repair
contract can be negotiated.
4.2.2 A̲p̲p̲r̲o̲v̲a̲l̲ ̲o̲f̲ ̲P̲e̲r̲s̲o̲n̲n̲e̲l̲
The HCAA has the right to request information on the
qualification of the technical assistance personnel
designated.
4.2.3 V̲e̲n̲d̲o̲r̲ ̲R̲e̲p̲a̲i̲r̲ ̲o̲f̲ ̲L̲R̲U̲'̲s̲ ̲a̲n̲d̲ ̲S̲R̲U̲'̲s̲
Cost for an open vendor repair contract can be negosiated.
Alternative repairs can be performed on time and material
basis.
The turnaround time will typical be 90 days.
Spares of LRU's and SRU's will be required on site.
The price for these initial spares are given in the
price proposal.
4.2.4 O̲n̲-̲s̲i̲t̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
The requested price quotation for different kind of
hardware and software support can be negosiated .
4.2.5 G̲e̲n̲e̲r̲a̲l̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
4.2.5.1 During the warranty period CR will have one maintenance
engineer on-site. Additional system engineers will
be available from CR.
4.2.5.2 Most of the failing LRU's and SRU's shall be repaired
in the workshop. Spares shall be kept in a on-site
storage.
4.2.6 S̲y̲s̲t̲e̲m̲ ̲S̲u̲p̲p̲o̲r̲t̲
4.2.6.1 G̲e̲n̲e̲r̲a̲l̲
The system support is described in chapter 4.2.1.1.
4.2.6.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲a̲n̲d̲ ̲H̲a̲r̲d̲w̲a̲r̲e̲
Changes to software and hardware delivered will be
submitted as Field Change Notices (FCN).
The FCN's are prepared by CR and deals with any kind
of changes to hardware and software delivered.
The software and hardware applicable for the FCN's
will during the warranty period be delivered free of
charge.
4.2.6.3 D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲/̲M̲o̲d̲i̲f̲i̲c̲a̲t̲i̲o̲n̲s̲
CR will at least once a year, after the final acceptance,
send Field Changes Notice and Documentation Changes
Notice (DCN) to HCAA.
Modifications decided to be used will be ordered by
HCAA as technical orders (TO).
A N N E X I
M&D USER REQUIREMENT SPECIFICATION
(GUIDELINE)
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
Page
1 INTRODUCTION .................................
3
1.1 SCOPE AND PURPOSE ........................
3
1.2 DOCUMENT ORGANIZATION ....................
3
1.3 M&D OBJECTIVES ...........................
4
1.4 APPLICABLE DOCUMENTS AND REFERENCES ......
5
1.5 ABBREVIATIONS AND DEFINITIONS ............
5
1.5.1 Abbreviations ........................
5
1.5.2 Definitions ..........................
4
2 M&D COMPLEX OVERVIEW .........................
7
2.1 ADN SYSTEM ENVIRONMENT ...................
7
2.2 M&D FUNCTIONAL OVERVIEW AND INTERFACE .... 10
2.2.1 Event Messages ....................... 10
2.2.2 Error Reports ........................ 10
2.2.3 Level 2 Reports ...................... 10
2.2.4 Message to Supervisor ................ 10
2.2.5 Test Reports ......................... 12
3 REPORT FORMATS ............................... 13
3.1 OVERVIEW ................................. 13
3.2 ERROR REPORTS ............................ 13
3.3 LEVEL 2 REPORTS .......................... 16
3.4 TEST REPORTS ............................. 18
4 M&D CONTROL PROGRAM .......................... 20
4.1 M&D CONTROL PROGRAM INTERFACES ........... 20
4.2 M&D MENUS ................................ 21
4.2.1 General Requirements ................. 21
4.2.2 Main Menu ............................ 22
4.2.3 Sub-menus ............................ 26
4.2.3.1 Level 2 Report Menu .............. 26
4.2.3.2 Test Area Menu ................... 26
4.2.3.3 Test Program Menu ................ 29
4.2.3.4 Predefined Test Program Packages . 29
Page
5 TEST PROGRAM REQUIREMENTS .................. 33
5.1 GENERAL TEST REQUIREMENTS .............. 33
5.1.1 Test Boot Loading Media ............ 33
5.1.2 Boot and Activation Control Program 34
5.1.3 Test Activation Commands ........... 34
5.1.4 Editorial Facilities ............... 34
5.1.5 Test Program HELP Commands ......... 35
5.2 MXAMOS TEST M&D REQUIREMENTS ........... 37
5.2.1 DISK ............................... 38
5.2.2 LTU ................................ 39
5.2.3 IBM ................................ 40
5.2.4 UNIVAC ............................. 41
5.2.5 STI ................................ 41
5.2.6 TAPE ............................... 42
5.2.7 PARR ............................... 44
5.3 STAND ALONE TEST M&D REQUIREMENTS ...... 45
5.3.1 CPU ................................ 45
5.3.2 MAP ................................ 45
5.3.3 RAM ................................ 45
5.4 WD TEST M&D REQUIREMENTS ............... 46
5.4.1 WPU ................................ 46
5.4.2 LP Driver .......................... 46
5.4.3 VDU Driver ......................... 46
5.4.4 CCA ................................ 46
6 BUILT-IN-TEST PROGRAM REQUIREMENTS ........... 47
6.1 GENERAL BIT REQUIREMENTS ................. 48
APPENDIX A. TEST AREAS FOR ACDN V.I. ........... 49
ACDN/AADN H/W M&D USER REQUIREMENT SPECIFICATION
CD-PRD/SPC/0001
JBP, LOL, CL, BB, KJA, PMS, OWE
J]rgen Staal
OWE, PMS, LOL, JBP, CL, BB, KJA,JH[, JSL, JRV,
PHG, JRN, HVK
…0f… ACDN PO 831220
AADN PO 831220
Prelim. ILS Mgmt 831220
831220
…0e… 831220
…0e… 4430A/rt…02… CD-PRD/SPC/0001
…02… BB/831220…02… …02…ii
ACDN/AADN
H/W M&D USER REQUIREMENT SPECIFICATION …02… …02… ACDN/AADN
…0f…
Issue One of Document
1 INTRODUCTION
1 INTRODUCTION
1 INTRODUCTION
1 INTRODUCTION
1 INTRODUCTION
1.1 SCOPE AND PURPOSE
1.1 SCOPE AND PURPOSE
1.1 SCOPE AND PURPOSE
1.1 SCOPE AND PURPOSE
1.1 SCOPE AND PURPOSE
This Maintenance and Diagnostics User Requirement Specification
is a specification of the procedures and program complex
which monitor the correct function of a total hardware
system and communication links.
Based upon this document, the projects must issue S̲ystem
D̲esign S̲pecifications and construct/implement the facilities
in the running ADN-systems.
The aim of the document (and the resulting M&D complex)
is directed towards the needs on the Air Canada Data
Network System (ACDN) and the American Airlines Data
Network System (AADN) - in this document commonly referred
to as the Airlines Data Networks (ADN) Systems - but
the principles are of general relevance. The overall
philosophy may therefore be implemented in any system,
even though the M&D specifics may vary according to
the actual system configuration.
The purpose of this document is therefore to describe
the requirements to the ACDN/AADN projects concerning
the diagnostic information retrieved from the networks
and to describe the test program facilities to be implemented
in the networks. These requirements, when approved,
will be the basis for the hardware maintenance manuals
to be written for the ACDN and AADN Systems.
1.2 DOCUMENT ORGANIZATION
1.2 DOCUMENT ORGANIZATION
1.2 DOCUMENT ORGANIZATION
1.2 DOCUMENT ORGANIZATION
1.2 DOCUMENT ORGANIZATION
Chapter 1 gives an introduction to the use of the document
and to M&D in general.
Chapter 2 provides an overview and introduction to
the
M & D complex and interface to the network systems.
The different kinds of reports and their routings
are mentioned.
Chapter 3 deals with the detailed requirements for
the different kinds of reports exchanged between ADN
and the
M & D program modules.
Chapter 4 explains the requirements to the M & D Control
Program, including the input and output to the test
programs.
Chapter 5 provides the requirements to the test programs,
for the H/W modules. Requirements to test facilities
in three main types of test programs are described.
Chapter 6 contains a brief discussion of the built-in-tests
of hardware modules.
Appendix A specifies the actual test areas and the
contents of the Error Reports and Level 2 Reports for
ACDN V.I.
1.3 M&D OBJECTIVES
1.3 M&D OBJECTIVES
1.3 M&D OBJECTIVES
1.3 M&D OBJECTIVES
1.3 M&D OBJECTIVES
The overall objectives of the M&D complex are threefold:
1. To monitor the functionality of the running system
by means of status messages, statistics etc. and
unambiguously report any deviation from predetermined
values.
2. To detect and unambiguously report any malfunction
caused by hardware or line failure.
3. To enable identification of faulty (or suspected)
hardware modules or lines by a combination of status/statistics
extracts upon request and load of test programs
executing on isolated hardware parts.
A fourth objective - to check proper function of hardware
units during start up the socalled built-in-test (B.I.T.)
may also be considered part of the M&D complex and
will be covered briefly in this document.
1.4 APPLICABLE DOCUMENTS AND REFERENCES
1.4 APPLICABLE DOCUMENTS AND REFERENCES
1.4 APPLICABLE DOCUMENTS AND REFERENCES
1.4 APPLICABLE DOCUMENTS AND REFERENCES
1.4 APPLICABLE DOCUMENTS AND REFERENCES
For information concerning the system environment please
refer to
o ACDN System Requirement Specification
ACDN/SRS/0001
o AADN System Requirement Specification
AADN/SRS/0001
and related project documentation.
Information concerning the hardware configuration may
be found in
o ACDN H/W Configurations
ACDN/SPC/0003
o AADN System Design Specification
AADN/SDS/0001
1.5 ABBREVIATIONS AND DEFINITIONS
1.5 ABBREVIATIONS AND DEFINITIONS
1.5 ABBREVIATIONS AND DEFINITIONS
1.5 ABBREVIATIONS AND DEFINITIONS
1.5 ABBREVIATIONS AND DEFINITIONS
1.5.1 Abbreviations
1.5.1 Abbreviations
1.5.1 Abbreviations
1.5.1 Abbreviations
1.5.1 Abbreviations
In this document the project relevant abbreviations
and acronymous are used as listed in the ACDN/SRS/001
and AADN/SRS/0001 respectively. Please refer to these
documents.
1.5.2 Definitions
1.5.2 Definitions
1.5.2 Definitions
1.5.2 Definitions
1.5.2 Definitions
T̲e̲s̲t̲ ̲A̲r̲e̲a̲ ̲D̲e̲f̲i̲n̲i̲t̲i̲o̲n̲
The definition of a test area is the minimum collection
of equipment, from which a failure can be identified
to come. Appendices define the test areas involved.
P̲e̲r̲m̲a̲n̲e̲n̲t̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
Permanent statistics are counters which are maintained
by the CR80 equipment at all times. The counter values
are collected at regular time intervals.
T̲e̲m̲p̲o̲r̲a̲r̲y̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
Temporary statistics are counters which are maintained
by the CR80 equipment. The counters are started and
stopped upon request.
E̲x̲t̲e̲r̲n̲a̲l̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
External statistics are counters which are maintained
by equipment external to CR80 equipment. The counters
are started and stopped upon request.
E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲
For definition refer to section 2.2.2.
L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲
For definition refer to section 2.2.3.
M̲e̲s̲s̲a̲g̲e̲-̲t̲o̲-̲S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲
For definition refer to section 2.2.4.
T̲e̲s̲t̲ ̲R̲e̲p̲o̲r̲t̲
For definition refer to section 2.2.5.
2 M&D COMPLEX OVERVIEW
2 M&D COMPLEX OVERVIEW
2 M&D COMPLEX OVERVIEW
2 M&D COMPLEX OVERVIEW
2 M&D COMPLEX OVERVIEW
2.1 ADN SYSTEM ENVIRONMENT
2.1 ADN SYSTEM ENVIRONMENT
2.1 ADN SYSTEM ENVIRONMENT
2.1 ADN SYSTEM ENVIRONMENT
2.1 ADN SYSTEM ENVIRONMENT
The running ADN systems must generate status, statistics
and event messages to be stored for retrieval and analysis
in order to report imminent or actual events in the
systems.
Some of these messages, concerning possible or definite
hardware or line malfunction are displayed to the system
supervisor and directed to the Maintenance Position
for further investigation or repair action.
This document specifies the requirements to the system
environment, the types of messages concerned and the
editing and display format requirements as well as
the request/retrieval facilities and test programs
necessary to fulfill the M&D objectives.
Figure 2.1-1 shows the logical function and connection
between the running system and the M&D complex.
RUNNING ADN SYSTEM
Figure 2.1-1
M&D Logic
Comments to Figure 2.1-1:
1. Indicates the automatic forwarding of the event
message displayed to be considered and handled
by the system supervisor.
The supervisor can either consider the event message
unimportant and drop it, or important and direct
it to the Error Report Queue for the technician
- if appropriate after inserting supplementary
information to the technician.
Additionally, as a result of a series of "unimportant"
event messages, the supervisor can also manually
generate a pseudo event report to inform the technician
about suspected hardware to be tested.
2. Denotes the call for Error Report for investigation
and test by the technician.
Error Report can either be dropped (test completed)
or be used as a basis for retrieval of further
information out of the events/statistics data base.
After such decision and possible retrieval/receipt
of level 2 report, the technician can load and
execute test programs to unveil a possible error
source.
3. Indicates the technicians request to the retrieval
services of the running system for further data
to be presented in the Level 2 Report.
2.2 M&D FUNCTIONAL OVERVIEW AND INTERFACE
2.2 M&D FUNCTIONAL OVERVIEW AND INTERFACE
2.2 M&D FUNCTIONAL OVERVIEW AND INTERFACE
2.2 M&D FUNCTIONAL OVERVIEW AND INTERFACE
2.2 M&D FUNCTIONAL OVERVIEW AND INTERFACE
Figure 2.2-1 provides an overview of the M & D requirements
and the relations to the ADN.
2.2.1 Event Messages
2.2.1 Event Messages
2.2.1 Event Messages
2.2.1 Event Messages
2.2.1 Event Messages
The ADN generated event messages must be filtered and
stored in the Events/Statistics Data Base. The event
messages shall transport completion codes and specified
memory and register contents.
It must be possible to extract sorted information from
the Event/Statistics Data Base.
The Event/Statistics Data Base is the basis for the
contents of the Level 2 Reports.
2.2.2 Error Reports
2.2.2 Error Reports
2.2.2 Error Reports
2.2.2 Error Reports
2.2.2 Error Reports
When a part of the ADN equipment has been isolated
because of a hardware failure the supervisor sends
an Error Report to the maintenance position.
All Error Reports shall be stored in an Error Report
Queue (ref Figure 2.2-1). From the maintenance position
it shall be possible to retrieve all Error Reports
issued within the last 72 hours.
2.2.3 Level 2 Reports
2.2.3 Level 2 Reports
2.2.3 Level 2 Reports
2.2.3 Level 2 Reports
2.2.3 Level 2 Reports
If more information about the system is needed, a Level
2 Report Request is generated by the technician and
the answer, a Level 2 Report, is received.
2.2.4 Message to Supervisor
2.2.4 Message to Supervisor
2.2.4 Message to Supervisor
2.2.4 Message to Supervisor
2.2.4 Message to Supervisor
To carry out a test it might be necessary to perform
isolation of the equipment. To do this, a Message-to-Supervisor
is sent, and the acknowledgement is received in dummy
Error Report.
Figure 2.2-1…01…M & D Requirements and Relations to the ADN
2.2.5 Test Reports
2.2.5 Test Reports
2.2.5 Test Reports
2.2.5 Test Reports
2.2.5 Test Reports
The test program execution is initiated by the M &
D control program (ref. Figure 2.2-1) and a Test Report
shall be received and displayed.
3 REPORT FORMATS
3 REPORT FORMATS
3 REPORT FORMATS
3 REPORT FORMATS
3 REPORT FORMATS
3.1 OVERVIEW
3.1 OVERVIEW
3.1 OVERVIEW
3.1 OVERVIEW
3.1 OVERVIEW
Error reports contain the following information:
a. type of failed equipment
b. address of failed equipment
c. historical error messages and status information
Section 3.2 and 3.3 show the Error Report and Level
2 Report. Section 4.5 provides detailed requirements
to the reports. For examples ref. appendix A.
3.2 ERROR REPORTS
3.2 ERROR REPORTS
3.2 ERROR REPORTS
3.2 ERROR REPORTS
3.2 ERROR REPORTS
The Error Report shall contain (ref. Figure 3.2-1):
1A. Time when error was detected.
1B. The report is of type "Error" when the failure
is detected with high realibility. If the failure
is intermittent the report must be of type "Warning",
e.g. if too many retransmissions have been required.
1C. An unambiguously identification of the faulty test
area. For identification of test areas refer to
the appendices.
1D. The suspected module in the test area mentioned
above must be identified. The identification must
include:
- PU AREA: includes the modules in a PU crate
or the modules in a CU crate which is connected
to the PU via the data channel.
The PU crate is identified as NSP# and NCP#.
The CU crate is identified as NSP#/CU# or NCP#/CU#.
The hardware must be marked with labels according
to this identification.
- MODULE NAME: Name of module
- MODULE LOGICAL ID: Logical address of module
- MODULE H/W ID: Hardware Input/Output address
of module
- SUBMODULE H/W ID: Hardware Input/Output address
of submodule
1E. The supervisor's appraisal of the cause why equipment
was isolated and which module is to be suspected.
Supervisors report must be in plain language.
1F. The event message generated by the system. The
event message shall include the code and the interpretation
of the code in plain language.
1G. A description of the reconfiguration which has
been performed when the error was isolated. The
reconfiguration identifies the isolated equipment.
In case of a supervisor initiated change in the
configuration, this field is used to inform the
maintenance technician ("Dummy Error Report").
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^
^
^ ERROR REPORT
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
1A. ^ Error Detection Time: (MONTH DD YYYY HH:MM:SS)
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
1B. ^ Report Type: ( Error, Warning )
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
1C. ^ Test Area ID: ( SITE, TEST AREA )
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
1D. ^ Suspected Module in Test Area, ID:
^
^
^
^ PU AREA : (crate identification)
^
^ MODULE NAME : (name of module)
^
^ MODULE LOGICAL ID: (logical address)
^
^ MODULE H/W ID : (H/W I/O address)
^
^ SUBMODULE H/W ID : (H/W I/O address)
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
1E. ^ Supervisor's reason for isolation
^
^
^
^
^
^
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
1F. ^ Information concerning suspected module:
^
^
^
^ Event Message: ( No., Text)
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
1G. ^ Configuration change:
^
^
^
^
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
Figure 3.2-1…01…Error Report
3.3 LEVEL 2 REPORTS
3.3 LEVEL 2 REPORTS
3.3 LEVEL 2 REPORTS
3.3 LEVEL 2 REPORTS
3.3 LEVEL 2 REPORTS
This section contains the general requirements to External
Statistics, Permanent Statistics, Temporary Statistics
and Event Messages in the Level 2 Report (Figure 3.3-1).
The specific requirements to the Level 2 Report are
described in appendices.
The following options in the Level 2 Report are required:
- It shall be possible to receive at the maintenance
position the same statistics and event messages
as for the supervisor.
- It shall be possible to receive summarized statistics
and event messages generated in a specific time
period for a specific H/W module.
- It shall be possible to start/stop a temporary
statistics counter for a specific test area by
a Level 2 Report Request.
Requirements to contents of Level 2 Report:
2A. There shall be an identification of the hardware
related to the Level 2 Report.
2B. Event messages including additional information
generated by the system collected during the specified
time period.
2C. Specifications of the time period.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^
^
^ LEVEL 2 REPORT
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
2A. ^ H/W ID:
^
^ SITE : (name of site)
^
^ PU AREA : (crate identification)
^
^ MODULE NAME : (name of module)
^
^ MODULE LOGICAL ID: (logical address)
^
^ MODULE H/W ID : (H/W I/O address)
^
^ SUBMODULE H/W ID : (H/W I/O address)
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
2B. ^ Event Messages
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
2C. ^ Time Period, Stop Time: Month DD.YYYY.HH:MM:SS
^
^ Lenght: HH:MM
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
Figure 3.3-1…01…Level 2 Report
3.4 TEST REPORTS
3.4 TEST REPORTS
3.4 TEST REPORTS
3.4 TEST REPORTS
3.4 TEST REPORTS
When a test program is started, the result of each
subtest and the corresponding contents (registers,
status words, etc.) shall be logged on a disk file.
The result of the test is also sent to the Maintenance
Position by a socalled Test Report.
The Test Report shall contain (ref. Figure 3.4-1):
3A Time when the test was started.
3B An unambiguously identification of the module(s)
tested, e.g. fysical and logical identification.
3C Description of the result of the test. The description
is specific for each type and dependent of the
report level. The description shall include both
the identification number of test, error, arguments,
and a translation of the identification numbers.
An example of a Test Report is shown in Figure 4.2.3.4-2.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^
^
^ TEST REPORT
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
3A. ^ TIME: (MONTH DD YYYY HH:MM:SS)
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
3B. ^ TESTED MODULE:
^
^
^
^ SITE : (name of site)
^
^ TEST AREA ID : (test area id)
^
^ PU AREA : (crate identification)
^
^ MODULE NAME : (name of module)
^
^ MODULE LOGICAL ID: (logical address)
^
^ MODULE H/W ID : (H/W I/O address)
^
^ SUBMODULE H/W ID : (H/W I/O address)
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
3C. ^ Information concerning tested module:
^
^
^
^ Test ID: Translation of Test ID
^
^ Error No.: Translation of Error No.
^
^
^
^ Arguments: Translation of Arguments
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
Figure 3.4-1…01…Test Report
4 M&D CONTROL PROGRAM
4 M&D CONTROL PROGRAM
4 M&D CONTROL PROGRAM
4 M&D CONTROL PROGRAM
4 M&D CONTROL PROGRAM
The functional system interface to the technician shall
be a menu-driven program, in this document referred
to as the M&D Control Program.
The M&D Control Program shall be able to load and run
M&D Test Programs in every relevant module in the entire
network.
4.1 M&D CONTROL PROGRAM INTERFACES
4.1 M&D CONTROL PROGRAM INTERFACES
4.1 M&D CONTROL PROGRAM INTERFACES
4.1 M&D CONTROL PROGRAM INTERFACES
4.1 M&D CONTROL PROGRAM INTERFACES
A technician shall be able to monitor the total system
hardware and connected lines from a dedicated Maintenance
Position located at the Network Control Center or on
any site. The Maintenance Position shall consist of
a VDU and a printer.
The man-machine interface part of the M&D Control Program
shall include
- the display of all information initiated by the
supervisor or the technician
- handling of menus for selection of actions by the
technician.
The M&D Control Program shall interface the CR80MX
Test Programs by means of a collection of disk files.
For each CR80MX Test program, there shall exist a disk
file containing the required sequence of low-level
command string input to the Command Interpreter (CMI).
This command sequence shall form a predefined package
of test functions.
The necessary parameters are dynamically extracted
from the menus.
The command file should be loaded together with the
test program in the off-line part of the double-PU
controlling the test area.
The low-level command input to the test program is
then taken from the attached command file and output
is sent via the network to the test log-file selected
by the technician.
4.2 M&D MENUS
4.2 M&D MENUS
4.2 M&D MENUS
4.2 M&D MENUS
4.2 M&D MENUS
4.2.1 General Requirements
4.2.1 General Requirements
4.2.1 General Requirements
4.2.1 General Requirements
4.2.1 General Requirements
When an asyncronous Error Report is generated at the
Supervisor Position, it shall be placed in an incoming
queue and a message shall be displayed on the Maintenance
Position VDU, showing the new queue status to the technician.
Each time an update of the queue occurs, an audible
signal shall be used to attract the attention of the
technician.
As the Maintenance Position VDU is not expected to
have format mode (cursor positioning) capabilities,
the menus will not require this. It means that the
data and text shall be output to the screen until a
"data entry field" is met. Then the program will wait
for an input before continuing.
If more than one "data entry field" exists in a menu,
it shall, therefore, be possible to jump back to the
start of the menu. Furthermore, it shall always be
possible to jump back to the Main Menu.
In the initial state, i.e. when the control program
is entered, the main menu is displayed on the screen.
4.2.2 Main Menu
4.2.2 Main Menu
4.2.2 Main Menu
4.2.2 Main Menu
4.2.2 Main Menu
When the technician is ready to read the Error Report
(refer to example Figure 4.2.2-1), he shall be able
to have it displayed on the screen.
At the same time, the Main Menu (for menu and report
overview, refer Figure 4.2.2-2) shall be displayed,
making it possible to select one of the following options
(refer to example Figure 4.2.2-3):
o Get Test Area Report
Selection of this option shall display a Level
2 Report menu.
o Select Test program
Selection of this option shall display the Select
Testarea Menu
o Get next Error Report in queue
o Get previous Error Report in queue
These options will allow browsing the Error Reports
in the queue.
o Print current Error Report
The Error Report last displayed is printed on the
Maintenance Position printer (entered in the print
queue).
o Delete current Error Report
The Error Report last displayed is removed from
the queue and is thereby lost.
o Message to Supervisor
A message entered in free format shall be sent
to the Supervisor Position. This can be used for
configuration change requests.
Figure 4.2.2-1…01…Error Report Example
Figure 4.2.2-2…01…Menu and Report Overview
Figure 4.2.2-3…01…Main Menu Example
4.2.3 Sub-menus
4.2.3 Sub-menus
4.2.3 Sub-menus
4.2.3 Sub-menus
4.2.3 Sub-menus
In the following menus, a general requirement to default
values applies:
For every parameter, a default value shall be set by
using the information in the current Error Report.
These default values shall be displayed immediately
in front of the corresponding "data entry fields",
using exactly the same syntax and semantics as required
for input.
If the technician wants to use the default value of
an entry, he just presses the enter-key, if he wants
to enter another value, he is able to see the correct
format of the parameter to be entered.
4.2.3.1 Level 2 Report Menu
4.2.3.1 Level 2 Report Menu
4.2.3.1 Level 2 Report Menu
4.2.3.1 Level 2 Report Menu
4.2.3.1 Level 2 Report Menu
This menu shall enable the technician to retrieve statistical
information from the Event Message Database (refer
example Figure 4.2.3.1-1). Sorting and data reduction
is performed according to the retrieval-key supplied
by the technician or the default facility.
A time window of maximum 72 hours and with resolution
of 1 minute can be entered as well. The stop-time shall
be selected with a resolution of 1 minute as well.
Completion codes and additional data must be displayed
on request.
4.2.3.2 Test Area Menu
4.2.3.2 Test Area Menu
4.2.3.2 Test Area Menu
4.2.3.2 Test Area Menu
4.2.3.2 Test Area Menu
This menu is an intermediate stage in the hierarchy
of menus for selecting testprograms.
All possible test areas shall be listed in this menu
(refer example Figure 4.2.3.2-1).
Figure 4.2.3.1-1…01…Level 2 Report Menu Example
Figure 4.2.3.2-1…01…Test Area Menu Example
The main purpose of this menu is to list the different
possibilities of running predefined test program packages.
The technician will then, when selecting a test area
(or letting the default facility do it) see the modules
that should be tested due to the limited resolution
of the automatic error detection system. This is done
by displaying the next menu in the hierarchy: the Test
Program Menu.
4.2.3.3 Test Program Menu
4.2.3.3 Test Program Menu
4.2.3.3 Test Program Menu
4.2.3.3 Test Program Menu
4.2.3.3 Test Program Menu
The testprograms selectable in this menu are grouped
in predefined packages. This means that the only informaton
required at this stage is the type and application
of the module (refer example Figure 4.2.3.3-1).
4.2.3.4 Predefined Test Program Packages
4.2.3.4 Predefined Test Program Packages
4.2.3.4 Predefined Test Program Packages
4.2.3.4 Predefined Test Program Packages
4.2.3.4 Predefined Test Program Packages
This level in the hierarchy of menus specifies a predefined
package of testfunctions to a specific testarea or
subset hereof (e.g. an LTU and connected communication
lines).
The technician is asked to enter the identificaton
of the subject to test (refer example Figure 4.2.3.4-1).
The report level (level of details), the number of
runs, and a log-filename can be specified.
It shall also be possible to communicate directly with
the testprogram using low level commands, thus enabling
the technician to run individual tests.
An error message shall be displayed if the equipment
chosen is on-line.
The testprogram shall terminate if an error is encountered,
displaying status messages on the selected log-file
for each start and completion of subtests (refer example
Figure 4.2.3.4-2).
A message telling when the entire testprogram has been
loaded and terminated should be displayed on the screen.
Figure 4.2.3.3-1…01…Test Program Menu Example
Figure 4.2.3.4-1…01…Predefined Test Program Package Example
Figure 4.2.3.4-2…01…Statusmessages from Test Programs
5 TEST PROGRAM REQUIREMENTS
5 TEST PROGRAM REQUIREMENTS
5 TEST PROGRAM REQUIREMENTS
5 TEST PROGRAM REQUIREMENTS
5 TEST PROGRAM REQUIREMENTS
5.1 GENERAL TEST REQUIREMENTS
5.1 GENERAL TEST REQUIREMENTS
5.1 GENERAL TEST REQUIREMENTS
5.1 GENERAL TEST REQUIREMENTS
5.1 GENERAL TEST1REQUIREMENTS
a. Test programs shall be designed for local and remote
operation.
b. Test programs shall commmunicate with the external
environment (terminals, communication lines, or
application programs) through a standardized interface.
c. Test programs shall have a common, standard, communication
module that shall allow operation of the test program
from a local terminal or from a communication line.
The test program is able to direct output to a
specified disc file or other alternative output
devices and to accept input from a disc file or
another alternative input device.
d. Test programs shall execute extensive tests of
hardware modules and shall have full control over
the hardware module being tested. (i.e. it is assumed
that the module is taken off-line).
e. Test programs shall be able to determine whether
a module being tested is functionally and performance-wise
in accordance with its specifications (confidence
level of 99%). The effect from errors in other
modules than the one being tested shall be negligible.
f. The test programs shall automatically reset parity
errors in the PU where the test program is loaded.
5.1.1 Test Boot Loading Media
5.1.1 Test Boot Loading Media
5.1.1 Test Boot Loading Media
5.1.1 Test Boot Loading Media
5.1.1 Test Boot Loading Media
The testprograms shall be booted from hard disk, except
the WD test program which shall be stored in a PROM
area.
5.1.2 Boot And Activation Control Program
5.1.2 Boot And Activation Control Program
5.1.2 Boot And Activation Control Program
5.1.2 Boot And Activation Control Program
5.1.2 Boot And Activation Control Program
Optionally the tests shall be booted and activated
by one of the below listed programs:
- M&D Menu Control Program (ref. sec. 4)
- MXAMOS Module
- MXAMOS Bootloader
5.1.3 Test Activation Commands
5.1.3 Test Activation Commands
5.1.3 Test Activation Commands
5.1.3 Test Activation Commands
5.1.3 Test Activation Commands
It shall be possible to choose between the following
activation commands:
- Low Level Commands,
i.e. test command id (parameter 1, parameter2,
..)
Example: DISK.INITIALIZE(#1023, #500)
- the name of a jobfile (if controlled by MXAMOS),
i.e. DO jobfilename.
Example: DO DISK.FORMAT
- M&D Control Command (if controlled by M&D Menu
Control Program)
The activation commands are described in section
5.1.
5.1.4 Editorial Facilities
5.1.4 Editorial Facilities
5.1.4 Editorial Facilities
5.1.4 Editorial Facilities
5.1.4 Editorial Facilities
It shall be possible to correct the activation command
(in case of a misspelling) without typing the command
from the start again.
5.1.5 Test Program HELP Commands
5.1.5 Test Program HELP Commands
5.1.5 Test Program HELP Commands
5.1.5 Test Program HELP Commands
5.1.5 Test Program HELP Commands
The following "HELP" commands shall be included in
the test programs:
D̲e̲f̲i̲n̲e̲ ̲P̲a̲t̲t̲e̲r̲n̲.̲
Function Description
Define or re-define a test pattern.
G̲e̲n̲e̲r̲a̲t̲e̲ ̲B̲u̲f̲f̲e̲r̲
Function Description:
Generate a specific test pattern in a specific buffer.
C̲l̲e̲a̲r̲ ̲B̲u̲f̲f̲e̲r̲
Function Description:
Clear the specified buffer, by overriding zeroes.
C̲o̲m̲p̲a̲r̲e̲ ̲B̲u̲f̲f̲e̲r̲
Function Description:
Compare a number of words of two buffers and output
the result of the comparison.
C̲o̲p̲y̲ ̲B̲u̲f̲f̲e̲r̲
Function description:
Copy a number of words from one buffer to another.
J̲u̲m̲p̲ ̲o̲n̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
Function Description:
Compare the result of test with a specified result
and jump to a defined location in the testprogram.
P̲a̲t̲c̲h̲
Function Description:
Patch in a physical address, specified by the page
and displacement.
The data may be a text string, a decimal or hexadecimal
constant.
D̲u̲m̲p̲ ̲(̲M̲A̲P̲,̲ ̲T̲T̲,̲ ̲S̲T̲I̲)̲
Function Description:
MAP DUMP: Dumps a part of the MAP memory
TT DUMP: Dumps a part of the MAP memory which is
dedicated to the translation tables.
STI DUMP: Dumps a part of the STI central RAM.
S̲e̲t̲ ̲T̲i̲m̲e̲
Function Description:
Insert the specified values into the MAP real time
clock.
D̲e̲v̲i̲c̲e̲ ̲M̲e̲m̲o̲r̲y̲ ̲(̲R̲e̲a̲d̲/̲w̲r̲i̲t̲e̲)̲
Function Description:
Reads from the device and outputs the received data
Writes to a device.
R̲e̲a̲d̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲M̲e̲m̲o̲r̲y̲/̲I̲/̲O̲ ̲a̲d̲d̲r̲.̲
Function Description:
Reads the memory configuration in steps of 4 kwords.
Reads the I/O addr. configuration.
B̲r̲e̲a̲k̲
Function Description:
Jumps out of a test. The Break command is issued by
pressing the "ATTN" key on the operators console.
R̲e̲p̲e̲a̲t̲ ̲B̲e̲g̲i̲n̲ ̲E̲n̲d̲
Function Description:
Perform a command or a number of commands of times.
Q̲u̲i̲t̲
Function command:
Terminate the test program execution and return to
the control program:
R̲e̲p̲o̲r̲t̲ ̲L̲e̲v̲e̲l̲
It shall be possible to change the output information
from the test programs.
The following four report levels are required:
0: At the end of a test, the accumulated number of
errors is given
1: When an error is detected, it is reported with
an id of the actual test etc.
2: When an error is detected, it is reported with
all information about input values/patterns, output
values and deviations from expected values.
3: When an atomic test is terminated this is reported
with full information about input values/patterns
and output values.
K̲e̲e̲p̲ ̲A̲l̲i̲v̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲.̲
Function Description:
Output by a specified time interval a message to the
control program/console that the test program is still
alive.
T̲i̲m̲e̲ ̲O̲u̲t̲
Function Description.
Stop the test if it is not completed within the time
period.
5.2 MXAMOS TEST M&D REQUIREMENTS
5.2 MXAMOS TEST M&D REQUIREMENTS
5.2 MXAMOS TEST M&D REQUIREMENTS
5.2 MXAMOS TEST M&D REQUIREMENTS
5.2 MXAMOS TEST M&D REQUIREMENTS
The MX-AMOS test programs are programs which are executed
in an off-line part of the system and in the same environment
(MXAMOS) as the application programs.
The following modules are tested by MXAMOS test programs:
- DISK CTRL/DCA/DRIVE
- LTU/LIA/Adapters/Terminals/Ext. Lines
- IBM CTRL/IBA
- UNIVAC CTRL/VIA
- STI/SBA
- TAPE CTRL/TCA/TAPE DECK
- PARR CTRL/PCA/PRINTER
5.2.1 DISK
5.2.1 DISK
5.2.1 DISK
5.2.1 DISK
5.2.1 DISK
3 different types of DISK tests are required:
a. D̲i̲s̲k̲ ̲S̲t̲a̲t̲u̲s̲ ̲T̲e̲s̲t̲
Internal Disk Ctrl test, status of drives and seek
test (access and read).
No information stored on the disk pach is destroyed.
Contents:
- Enable DISK Ctrl.
- Read Status of DISK Ctrl.
- Compare DISK Ctrl Status with expected status
- Read status of DISK drive
- Compare drive status with expected status
- Execute Built-In-Test
- Execute DISK RAM Test
- Seek Test (Access only) Random
- Read Test Random
b. F̲o̲r̲m̲a̲t̲ ̲T̲e̲s̲t̲
Initiate a disk pack. Check if it is initiated.
All information stored on the disk pack is destroyed
during this test.
Contents:
- Enable DISK Ctrl.
- Format DISK pack
- Check format of DISK pack
c. W̲r̲i̲t̲e̲/̲R̲e̲a̲d̲ ̲T̲e̲s̲t̲
W/R test to/from a disk.
Test mark and write protect facility.
It shall be possible to specify functions to this
test.
Contents
- Enable DISK Ctrl.
- Execute disk tests with the following options:
o SELECT: SEEK/READ/WRITE/WRITE-READ-COMPARE
o SECTOR: CONTINOUSLY/Direct
o SEQ: FORWARD/REVERSE/X N/RANDOM
o HEAD: MAN/SEQ/RAN
o DATA: ERROR: OVERRIDE/STOP
o ADDR: ERROR: OVERRIDE/STOP
5.2.2 LTU
5.2.2 LTU
5.2.2 LTU
5.2.2 LTU
5.2.2 LTU
4 different types of LTU TESTS are required :
a. L̲T̲U̲ ̲L̲O̲O̲P̲ ̲T̲e̲s̲t̲
Internal LTU test and loop test on connected local
adapters, modems, and remote adapters.
It is required that the loop test can be performed
by a S/W loop back connection in the local LIA,
the local modem, the remote modem, and the remote
LIA (if trunkline).
Contents
- Enable LTU (Not reset)
- Read LTU status
- Compare LTU status with expected status
- Execute LTU RAM Test
- Execute S/W Loop test in predefined Loop back
test points.
b. L̲T̲U̲-̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲T̲e̲s̲t̲
Functional test of terminals connected to LTU channels,
i.e. write to/read from a terminal - if possible,
otherwise only writing to the terminal.
Contents
- Enable LTU
- Write a message to a buffer in a specified
terminal
- Read the message from the buffer
- Compare the received message with the transmitted
c. L̲T̲U̲-̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲K̲e̲y̲b̲o̲a̲r̲d̲ ̲T̲e̲s̲t̲
Test of the keyboard on a VDU connected to a LTU
channel, i.e. the following data will appear on
the VDU connected to a specified channel. "PLEASE
TYPE SAME DATA".
The operator will then type same data. The typed
data will be transmitted to the maintenance position.
Contents
- Enable LTU
- Write "TYPE SOME DATA" to a specified terminal
- Read and display the typed data.
d. I̲n̲t̲e̲n̲s̲i̲v̲e̲ ̲T̲e̲s̲t̲ ̲o̲f̲ ̲L̲T̲U̲-̲t̲e̲r̲m̲i̲n̲a̲l̲ …0e…(*)…0f…
An intensive test of the terminal connected to
a LTU-channel.
Contents
- Enable LTU
- Test terminal Baud Rate (+/- 2,5%)
- Test keyfilter
- Test PF keys
- Test Field Setup (optional/Mandatory)
- Test Programming of splits (Setup and Recalls)
(*) This test is to be specified to each type of
terminal.
The contents specified is an example of an intensitive
test.
5.2.3 IBM
5.2.3 IBM
5.2.3 IBM
5.2.3 IBM
5.2.3 IBM
1 type of IBM test is required:
a. I̲B̲M̲ ̲S̲t̲a̲t̲u̲s̲ ̲t̲e̲s̲t̲
Internal IBM Ctrl test and
status of IBM Ctrl and Adapter
Contents
- Offline test
- Enable IBM Ctrl (Not reset)
- Read H/W Status word (RAM adr 39…0f…H…0e…)
- Compare H/W Status word with expected.
- Read Control Word One (RAM adr. 12…0f…H…0e…)
- Compare Control Word One with expected.
- Read Control Word Two (RAM adr. B…0f…H…0e…)
- Compare Control Word Two with expected.
- Read Illegal Command Status (RAM adr 20…0f…H…0e…)
- Compare Ill. Command Status with expected.
- Disable IBM Ctrl (Reset)
- Interrupt Test
- Shared RAM Test
- IO RAM Test
- Disable IBM Ctrl. (Reset)
5.2.4 UNIVAC
5.2.4 UNIVAC
5.2.4 UNIVAC
5.2.4 UNIVAC
5.2.4 UNIVAC
1 type of UNIVAC test is required:
a. U̲N̲I̲V̲A̲C̲/̲V̲I̲A̲ ̲T̲e̲s̲t̲
Internal UNIVAC Ctrl test and status of UNIVAC
Ctrl and Adapter.
Contents
- Enable UNIVAC Ctrl (Not Reset)
- Read SEND PROCESS STATUS WORD
- Compare SEND PROCESS STATUS WORD with the expected
- Read RECEIVE STATUS WORD
- Compare RECEIVE STATUS WORD with expected.
- Execute UNIVAC Ctrl Built-In-Test
- UNIVAC Ctrl RAM Test
- Interrupt Test
5.2.5 STI/SBA
5.2.5 STI/SBA
5.2.5 STI/SBA
5.2.5 STI/SBA
5.2.5 STI/SBA
2 types of STI/SBA tests are required:
a. S̲T̲I̲/̲S̲B̲A̲ ̲S̲t̲a̲t̲u̲s̲ ̲T̲e̲s̲t̲
Internal Status of STI Ctrl and loop test on local
and remote SBA.
Contents
- Read Status of STI
- Compare Status with expected status
- Execute STI ̲INTERRUPT Test
- Execute STI ̲DMA Test
- Execute STI ̲Z80 Test
- Execute STI ̲RAM Test
- Execute STI ̲SBA ̲LOCAL ̲LOOP ̲Test
- Execute STI ̲SBA ̲REMOTE ̲LOOP ̲Test
b. S̲T̲I̲/̲S̲B̲A̲ ̲S̲t̲a̲b̲i̲l̲i̲t̲y̲ ̲T̲e̲s̲t̲
Test of STI ̲RAM and Z ̲80 RAM stability.
Contents
Execute STI ̲RAM ̲STABILITY Test
Execute STI ̲Z80 ̲RAM ̲STABILITY Test
5.2.6 TAPE
5.2.6 TAPE
5.2.6 TAPE
5.2.6 TAPE
5.2.6 TAPE
3 different types of Tape Ctrl/TCA/Tape Deck tests
are required:
a. T̲A̲P̲E̲ ̲C̲t̲r̲l̲ ̲T̲e̲s̲t̲
Internal Tape Ctrl test, status of Tape Ctrl and
Tape Deck. Seek (access and read) test.
No information stored on the Tape is destroyed.
Contents:
- Enable Tape Ctrl (No Reset)
- Read Tape Ctrl Status
- Compare the status with the expected
- Read Tape Deck Status
- Compare the Status with the expected
- Execute Built-In-Test
- Execute Tape Ctrl RAM test
- Seek Test (Access only) Random
- Read Test Random
b. W̲r̲i̲t̲e̲/̲R̲e̲a̲d̲ ̲T̲e̲s̲t̲
W/R to/from a tape
Write Protect facility
It should be possible to specify functions in this
test.
Contents:
Enable Tape Ctrl
Execute W/R/Seek with the following options:
- SEEK/W/R
- Bytes: CONT/DIRECT
- SEQ: FORWARD/REVERSE/RANDOM
- DATA ERROR: OVERRIDE/STOP
- ADDR ERROR: OVERRIDE/STOP
c. A̲d̲j̲u̲s̲t̲m̲e̲n̲t̲ ̲t̲e̲s̲t̲ ̲o̲f̲ ̲t̲a̲p̲e̲ ̲d̲e̲c̲k̲
This test contain two subtests:
- a test containing measurements of time interval
of:
start Tape motion; start information read.
stop information read, stop tape motion.
(If the time interval is out of tolerances then
a bell should sound, if possible). The time interval
should be displayed.
- Continously start/stop reading from the tape in
specified time interval. This test makes it possible
to adjust the start/stop time of the tape deck.
The two tests are to be executed when the tape
is running forward/reverse/forward-reverse.
Contents
Enable TAPE Ctrl.
Continously test time interval of:
- Start of Tape motion, start information read
- Stop information read stop tape motion
Continously start/stop reading from tape deck:
- Read 200 bytes containing F's (app 50 msec.)
- Stop app 50 msec.
5.2.7 PARR CTRL/PCA/Printer
5.2.7 PARR CTRL/PCA/Printer
5.2.7 PARR CTRL/PCA/Printer
5.2.7 PARR CTRL/PCA/Printer
5.2.7 PARR CTRL/PCA/Printer
3 different types of PARR Ctrl/PCA/PRINTER tests are
required:
a. P̲A̲R̲R̲ ̲C̲t̲r̲l̲ ̲T̲e̲s̲t̲
Internal Status test of Parr Ctrl and S/W loop
test on specified channels.
Contents:
- Enable Parr Ctrl (Not Reset)
- Read Parr Ctrl Status
- Compare Parr Ctrl Status with expected status
- Execute Built-In-Test
- Execute Parr Ctrl RAM test
- Execute S/W looptest in predefined loopback
test points.
b. P̲A̲R̲R̲ ̲C̲t̲r̲l̲ ̲L̲i̲n̲e̲ ̲P̲r̲i̲n̲t̲e̲r̲ ̲T̲e̲s̲t̲
Functional Test of printer.
Contents
- Enable Parr Ctrl
- A number of times:
Write a message to the line printer.
c. P̲A̲R̲R̲ ̲C̲t̲r̲l̲ ̲I̲n̲t̲e̲n̲s̲i̲t̲i̲v̲e̲ ̲L̲i̲n̲e̲ ̲P̲r̲i̲n̲t̲e̲r̲s̲ ̲T̲e̲s̲t̲
An intensive test of the printer connected to a
PARR Ctrl/PCA channel.
Contents:
- Enable Parr Ctrl
- Check Baud Rate (+/- 2.5%)
- Check Vertical Tabulation Format
- Check keylock function
- Check Suspend Print and Receive Buffer
- Check Paper in Motion Switch
- Check parity
- Check Paper Out Indication
(This test has to be specified to the type of printer
connected to the channel. Above is just an example
of an intensitive test).
5.3 STAND ALONE TEST M&D REQUIREMENTS
5.3 STAND ALONE TEST M&D REQUIREMENTS
5.3 STAND ALONE TEST M&D REQUIREMENTS
5.3 STAND ALONE TEST M&D REQUIREMENTS
5.3 STAND ALONE TEST M&D REQUIREMENTS
The Stand Alone Test Programs are offline test programs
which are executed in a non-XAMOS environment. The
following modules are tested by stand Alone Test Programs:
- CPU
- RAM
- MAP
5.3.1 CPU
5.3.1 CPU
5.3.1 CPU
5.3.1 CPU
5.3.1 CPU
The CPU should be tested as required in the General
Requirements (sec. 5.1)
One specific requirement should be stated:
The CPU in test shall not be the master, if possible.
If it is not the master then the error reporting is
better in case an error is discovered.
5.3.2 MAP
5.3.2 MAP
5.3.2 MAP
5.3.2 MAP
5.3.2 MAP
No specific requirements
5.3.3 RAM
5.3.3 RAM
5.3.3 RAM
5.3.3 RAM
5.3.3 RAM
Specific requirements:
- The RAM test should not detect error when one or
more LTU's is enabled to the PU under test.
5.4 WD TEST M&D REQUIREMENTS
5.4 WD TEST M&D REQUIREMENTS
5.4 WD TEST M&D REQUIREMENTS
5.4 WD TEST M&D REQUIREMENTS
5.4 WD TEST M&D REQUIREMENTS
The WD test programs are tests of each of the WD functions.
The following functions should be tested:
WPU
LP driver
VDU driver
CCA drivers/receivers
5.4.1 WPU
5.4.1 WPU
5.4.1 WPU
5.4.1 WPU
5.4.1 WPU
Contents of the WPU test:
Enable WD LTU
Read LTU Status
Compare LTU status with expected status
5.4.2 LP Driver
5.4.2 LP Driver
5.4.2 LP Driver
5.4.2 LP Driver
5.4.2 LP Driver
Read LP status
Compare LP status with the expected status
Transmit message to the LP.
5.4.3 VDU Driver
5.4.3 VDU Driver
5.4.3 VDU Driver
5.4.3 VDU Driver
5.4.3 VDU Driver
Read VDU status
Compare it with the expected status
Transmit a message to the VDU buffer
Receive and compare the buffer with the expected status.
5.4.4 CCA Driver/Receiver
5.4.4 CCA Driver/Receiver
5.4.4 CCA Driver/Receiver
5.4.4 CCA Driver/Receiver
5.4.4 CCA Driver/Receiver
It shall be possible to test each CCA command.
6 BUILT-IN-TEST PROGRAM REQUIREMENTS
6 BUILT-IN-TEST PROGRAM REQUIREMENTS
6 BUILT-IN-TEST PROGRAM REQUIREMENTS
6 BUILT-IN-TEST PROGRAM REQUIREMENTS
6 BUILT-IN-TEST PROGRAM REQUIREMENTS
The following modules shall have included a Built-In-Test:
- CPU
- MAP
- STI/SBA
- DISK CTRL/DCA
- LTU/LIA
- IBM CTRL/IBA
- UNIVAC CTRL/VIA
- TAPE CTRL/TCA
- PARR CTRL/PCA
6.1 GENERAL BIT REQUIREMENTS
6.1 GENERAL BIT REQUIREMENTS
6.1 GENERAL BIT REQUIREMENTS
6.1 GENERAL BIT REQUIREMENTS
6.1 GENERAL BIT REQUIREMENTS
a) BIT shall be activated upon power-on of a module,
master ̲clear of a module, and on request by an
I/O instruction.
b) BITs shall not automatically be activated when
a module is enabled on a bus or switched from A-bus
to B-bus (or vice versa).
c) Results of BITs shall be readable by the CPU by
means of I/O instructions.
d) The I/O commands for activating and reading results
of BITs shall have a common format (Test program
I/O command and MXAMOS Boot loader command).
e) Results of BITs shall have a common format.
f) An I/O interrupt shall be generated when a BIT
is completed.
g) BITs shall include tests of all connected adapter
modules.
h) The result of a BIT of an I/O module shall give
the following indication for each adapter module
which could be connected to the I/O module:
- Adapter OK
- Adapter failed
- Adapter not configured (missing)
A̲ ̲P̲ ̲P̲ ̲E̲ ̲N̲ ̲D̲ ̲I̲ ̲X̲ ̲ ̲ ̲ ̲A̲
T̲E̲S̲T̲ ̲A̲R̲E̲A̲S̲ ̲F̲O̲R̲ ̲A̲C̲D̲N̲ ̲V̲E̲R̲S̲I̲O̲N̲ ̲1̲
1 SCOPE ..............................................
2 TEST AREA DESCRIPTIONS .............................
2.1 Disk Test Area ...................................
2.1.1 Disk-Requirements to the Error Report ..........
2.1.1.1 Disk-Requirements to the Error Report
Point 1F .....................................
2.1.2 Disk-Requirements to the Level 2 Report ........
2.1.2.1 Disk-Requirements to the Level 2 Report
Point 2B .....................................
2.1.3 Disk-Example of Error Report ...................
2.2 LTU Test Area ....................................
2.2.1 LTU-Requirements to the Error Report ...........
2.2.1.1 LTU-Requirements to the Error Report Point
1F
2.2.2 LTU-Requirements to the Level 2 Report .........
2.2.2.1 LTU-Requirements to the Level 2 Report
Point 2B .....................................
2.2.3 LTU-Example of Error Report ....................
2.3 IBM Test Area ....................................
2.3.1 IBM-Requirements to the Error Report ...........
2.3.1.1 IBM-Requirements to the Error Report
Point 1F .....................................
2.2.3 IBM-Requirements to the Level 2 Report .........
2.3.2.1 IBM-Requirements to the Level 2 Report
Point 2B .....................................
2.3.3 IBM-Example of Error Report ....................
2.4 UNIVAC Test Area .................................
2.4.1 UNIVAC-Requirements to the Error Report ........
2.4.1.1 UNIVAC-Requirements to the Error Report
Point 1F .....................................
2.4.2 UNIVAC-Requirements to the Level 2 Report
2.4.2.1 UNIVAC-Requirements to the Level 2 Report
Point 2B .....................................
2.4.3 UNIVAC-Example of Error Report .................
2.5 STI/SBA Test Area ................................
2.5.1 STI/SBA-Requirements to the Error Report .......
2.5.1.1 STI/SBA-Requirements to the Error Report
Point 1F .....................................
2.5.2 STI/SBA-Requirements to the Level 2 Report......
2.5.2.1 STI/SBA-Requirements to the Level 2 Report
Point 2B .....................................
2.5.3 STI/SBA-Example of Error Report ................
2.6 Tape Test Area ...................................
2.6.1 Tape-Requirements to the Error Report...........
2.6.1.1 Tape-Requirements to the Error Report Point
1F
2.6.2 Tape-Requirements to the Level 2 Report.........
2.6.2.1 Tape-Requirements to the Level 2 Report
Point 2B .....................................
2.6.3 Tape-Example of Error Report ...................
2.7 Parr Test Area ...................................
2.7.1 Parr-Requirements to the Error Report ..........
2.7.1.1 Parr-Requirements to the Error Report Point
1F
2.7.2 Parr-Requirements to the Level 2 Report.........
2.7.2.1 Parr-Requirements to the Level 2 Report
Point 2B .....................................
2.7.3 Parr-Example of Error Report ...................
2.8 CPU/MAP/RAM Test Area ............................
2.8.1 CPU/MAP/RAM-Requirements to the Error Report....
2.8.1.1 CPU/MAP/RAM-Requirements to the Error Report
Point 1F .....................................
2.8.2 CPU/MAP/RAM-Requirements to the Level 2 Report
.
2.8.2.1 CPU/MAP/RAM-Requirements to the Level 2
Report Point 2B ..............................
2.8.3 CPU/MAP/RAM-Example of Error Report ............
2.9 Data Channel Test Area ...........................
2.9.1 Data Channel-Requirements to the Error Report
..
2.9.1.1 Data Channel-Requirements to the Error Report
Point 1F .....................................
2.9.2 Data Channel-Requirements to the Level 2 Report
2.9.2.1 Data Channel-Requirements to the Level 2
Report Point 2B ..............................
2.9.3 Data Channel-Example of Error Report ...........
2.10 WD Test Area ...................................
2.10.1 WD-Requirements to the Error Report ..........
2.10.1.1 WD-Requirements to the Error Report Point
1F
2.2.10 WD-Requirements to the Level 2 Report ........
2.10.2.1 WD-Requirements to the Test Area Report
Point 2B ...................................
2.10.3 WD-Example of Error Report ...................
1 S̲C̲O̲P̲E̲
This appendix defines the actual test areas for ACDN
V.I. Requirements to the Error Reports for each test
area are stated, and some examples are given.
2 T̲E̲S̲T̲ ̲A̲R̲E̲A̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲S̲
2.1 D̲i̲s̲k̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲
Figure 2.1-1…01…DISK TEST AREA
Test Area Contents:
- Components: Disk Ctrl., DCA,Disk Drive Disk Pack,
Crate
- Test Area ID: 11
2.1.1 D̲I̲S̲K̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲
2.1.1.1 D̲I̲S̲K̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲1̲F̲
The information concerning the suspected module(s)
contain:
COMPLETION CODE: completion code
translation of completion codes
DISK CTRL STATUS: disk controller status
translation
of
disk
ctrl
status
DRIVE STATUS: disk drive status
translation of drive status
SECTOR NO: sector id where the error was discovered
2.1.2 D̲I̲S̲K̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲
2.1.2.1 D̲I̲S̲K̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲2̲B̲
T̲B̲D̲
2.1.3 D̲I̲S̲K̲ ̲-̲ ̲E̲X̲A̲M̲P̲L̲E̲ ̲O̲F̲ ̲A̲N̲ ̲E̲R̲R̲O̲R̲ ̲R̲E̲P̲O̲R̲T̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
ERROR REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error Detection Time: DEC 05 1983 09:30:34
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Test Area ID:
Site: TOR
Test Area: 11
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUSPECTED MODULE IN TEST AREA
PU AREA : NSP1/SCU0
MODULE NAME : DISK
MODULE LOGICAL ID : 00AAMIRM
MODULE H/W ID : #23
SUBMODULE H/W ID : 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUPERVISORS REASON FOR ISOLATION:
SEEK ERROR REPORTED
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
INFORMATION CONCERNING SUSPECTED MODULE:
COMPLETION CODE: #3503: DISK ̲UNEXPECTED ̲STATUS
DISK CTRL STATUS: #0080: SEEK ̲INITIATED
DISK DRIVE STATUS: #02A8: SEEK ̲ERROR
SECTOR NO: 16271
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
CONFIGURATION CHANGE:
DISK NO 00AAMIRM Closed
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2.2 L̲T̲U̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲ ̲
Figure 2.2-1
LTU - Test Area
LTU - Test Area Contents:
- Components: LTU, LIA, Adapters, Terminals, External
Lines
- Test Area ID: 12
2.2.1 L̲T̲U̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲
2.2.1.1 L̲T̲U̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲1̲F̲
The information concerning the suspected module(s)
contain:
COMPLETION CODE: completion code
translation of completion code
Info-0
Info-1
LTU STATUS: LTU Status
2.2.2 L̲T̲U̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲
2.2.2.1 L̲T̲U̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲2̲B̲
TBD
2.2.3 L̲T̲U̲ ̲-̲ ̲E̲X̲A̲M̲P̲L̲E̲ ̲O̲F̲ ̲A̲N̲ ̲E̲R̲R̲O̲R̲ ̲R̲E̲P̲O̲R̲T̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
ERROR REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error Detection Time: DEC 05 1983 09:30:45
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Test Area ID:
SITE: TOR
TEST AREA: 12
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUSPECTED MODULE IN TEST AREA
PU AREA : NSP1/CU1
MODULE NAME : LTU
MODULE LOGICAL ID : 00ABL1
MODULE H/W ID : #07
SUBMODULE H/W ID : 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUPERVISORS REASON FOR ISOLATION:
RECEIVE ERROR ON CHANNEL NO 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
INFORMATION CONCERNING SUSPECTED MODULE:
COMPLETION CODE: #21: Rx-status-sequence-error
Expected LDU No: 12389
Received LDU No: 12345
LTU STATUS: 0095: DMAO-SIO2A Data Error
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
CONFIGURATION CHANGE:
LTU NO. 00ABL1 Closed
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2.3 I̲B̲M̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲
Figure 2.3-1…01…IBM Test Area
I̲B̲M̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲ ̲C̲o̲n̲t̲e̲n̲t̲s̲:
- Components: IBM Ctrl., IBA, Connector Panel
- Test Area ID: 13
2.3.1 I̲B̲M̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲
2.3.1.1 I̲B̲M̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲T̲e̲s̲t̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲I̲F̲
The information concerning the suspected module(s)
contains:
COMPLETION CODE: completion code
translation of completion code
info-0
info-1
H/W STATUS WORD: IBM CTRL RAM adr 39…0f…H…0e…
translation of statusword
Control Word One: IBM CTRL RAM adr 12…0f…H…0e…
translation of Control Word one
Control Word Two: IBM CTRL RAM adr 13…0f…H…0e…
translation of Control word Two
Illegal Command
Status: IBM CTRL RAM adr 2D…0f…H…0e…
translation of Ill.Cmd status
2.3.2 I̲B̲M̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲
2.3.2.1 I̲B̲M̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲2̲B̲
TBD
2.3.3 I̲B̲M̲ ̲-̲ ̲E̲X̲A̲M̲P̲L̲E̲ ̲O̲F̲ ̲A̲N̲ ̲E̲R̲R̲O̲R̲ ̲R̲E̲P̲O̲R̲T̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
ERROR REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error Detection Time: DEC 05 1983 09:30:45
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Test Area ID:
Site: TOR
Test Area: 13
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUSPECTED MODULE IN TEST AREA
PU AREA : NSP1/SCU1
MODULE NAME : IBM CTRL
MODULE LOGICAL ID : 00ABI1
MODULE H/W ID : #12
SUBMODULE H/W ID : 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUPERVISORS REASON FOR ISOLATION:
H/W ERROR DETECTED IN IBM CTRL
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
INFORMATION CONCERNING SUSPECTED MODULE:
COMPLETION CODE: (?), (?)
H/W Status Word: 0080: RAM ERR2
Control Word One: 0080: NON ZERO STATUS
Control Work Two: 0082: DATA CHECK ERROR
Illegal Command Status: 0000: COMMAND STATUS OK.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
CONFIGURATION CHANGE:
IBM CTRL. NO 00ABI1 Closed
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2.4 U̲N̲I̲V̲A̲C̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲
Figure 2.4-1
UNIVAC TEST Area
U̲N̲I̲V̲A̲C̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲ ̲C̲o̲n̲t̲e̲n̲t̲s̲:̲
- Contents: Univac Ctrl, UIA, Crate
- Test Area ID: 14
2.4.1 U̲N̲I̲V̲A̲C̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲
2.4.1.1 U̲N̲I̲V̲A̲C̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲1̲F̲
The information concerning the suspected module(s)
contains:
COMPLETION CODE: completion code
translation of completion code
Info-0 translation
Info-1 translation
SEND PROCESS STATUS: location 0 in cmd buffer
translation of loc. 07
RECEIVE PROCESS STATUS: location 5 in cmd buffer
translation of loc. 5
2.4.2 U̲N̲I̲V̲A̲C̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲
2.4.2.1 U̲N̲I̲V̲A̲C̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲ ̲P̲o̲i̲n̲t̲ ̲2̲B̲
TBD
2.4.3 U̲N̲I̲V̲A̲C̲ ̲-̲ ̲E̲X̲A̲M̲P̲L̲E̲ ̲O̲F̲ ̲A̲N̲ ̲E̲R̲R̲O̲R̲ ̲R̲E̲P̲O̲R̲T̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
ERROR REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error Detection Time: DEC 05 1983 09:30:45
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Test Area ID:
Site: TOR
Test Area ID: 14
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUSPECTED MODULE IN TEST AREA
PU AREA : NSP1/CU1
MODULE NAME : UNIVAC
MODULE LOGICAL ID : 00ABU1
MODULE H/W ID : #13
SUBMODULE H/W ID : 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUPERVISORS REASON FOR ISOLATION:
H/W ERROR DETECTED IN UNIVAC CTRL
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
INFORMATION CONCERNING SUSPECTED MODULE:
COMPLETION CODE: (?), (?)
Send Process Status: 0008: Par.ERR OCCURED DURING READ
Receive Process Status: 0100: RECEIVE COMPLETE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
CONFIGURATION CHANGE:
UNIVAC CTRL. No. 00ABU1 Closed
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2.5 S̲T̲I̲/̲S̲B̲A̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲
Figure 2.5-1
STI/SBA - TEST Area
S̲T̲I̲/̲S̲B̲A̲ ̲C̲o̲n̲t̲e̲n̲t̲s̲
- Components: STI, SBA, Crate
- Test Area ID: 1
2.5.1 S̲T̲I̲/̲S̲B̲A̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲
2.5.1.1 S̲T̲I̲/̲S̲B̲A̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲1̲F̲
The information concerning the suspected module(s)
contain:
COMPLETION CODE: completion code
translation of completion code
info-0 translation
info-1 translation
2.5.2 S̲T̲I̲/̲S̲B̲A̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲
2.5.2.1 S̲T̲I̲/̲S̲R̲A̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲2̲
TBD
2.5.3 S̲T̲I̲/̲S̲B̲A̲ ̲E̲X̲A̲M̲P̲L̲E̲ ̲O̲F̲ ̲A̲N̲ ̲E̲R̲R̲O̲R̲ ̲R̲E̲P̲O̲R̲T̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
ERROR REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error Detection Time: DEC 05 1983 09:30:45
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Test Area ID:
Site: TOR
Test Area ID: 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUSPECTED MODULE IN TEST AREA
PU AREA : NSP1
MODULE NAME : STI/SBA
MODULE LOGICAL ID : 00ABS00
MODULE H/W ID : #32
SUBMODULE H/W ID : 00
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUPERVISORS REASON FOR ISOLATION:
Not possible to communicate with NSP2
via SBA No 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
INFORMATION CONCERNING SUSPECTED MODULE:
COMPLETION CODE: #3947: TDXH ̲SBA ̲not ̲connected
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
CONFIGURATION CHANGE:
SBA No. 00ABS00 closed; Redundant SBA opened.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2.6 T̲A̲P̲E̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲
Figure 2.6-1…01…Tape Test Area
Tape Test Area Contents:
- Components: Tape Ctrl, TCA, Tape Deck, Crate
- Test Area ID: 15
2.6.1 T̲A̲P̲E̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲
2.6.1.1 T̲A̲P̲E̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲1̲F̲
The information concerning the suspected module(s)
contain:
COMPLETION CODE: completion code
translation of completion code
info-0 translation
info-1 translation
TRANSFER STATUS: loc. 6 in command buffer
translation of loc. 6
STATUS CODE: loc 6 bit 9-12 in cmd buffer
translation of bit 9-12
2.6.2 T̲A̲P̲E̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲
2.6.2.1 T̲A̲P̲E̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲2̲B̲
TBD
2.6.3 T̲A̲P̲E̲-̲ ̲E̲X̲A̲M̲P̲L̲E̲ ̲O̲F̲ ̲A̲N̲ ̲E̲R̲R̲O̲R̲ ̲R̲E̲P̲O̲R̲T̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
ERROR REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error Detection Time: DEC 05 1983 09:30:45
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Test Area ID:
Site: TOR
Test Area ID: 15
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUSPECTED MODULE IN TEST AREA
PU AREA : NCP1/SCU0
MODULE NAME : TAPE
MODULE LOGICAL ID : 00AAT05
MODULE H/W ID : #15
SUBMODULE H/W ID : 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUPERVISORS REASON FOR ISOLATION:
TAPE CTRL Status not correct
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
INFORMATION CONCERNING SUSPECTED MODULE:
COMPLETION CODE: (?), (?)
Transfer Status: #0F00: Tape Hard Error, Status Code
Status Code: # 7: Missing Identifier at PE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
CONFIGURATION CHANGE:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2.7 P̲A̲R̲R̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲
Figure 2.7-1…01…PARR - Test Area
PARR - Test Area Contents:
- Components: PARR Ctrl, PCA, Printer, Crate
- Test Area ID: 15
2.7.1 P̲A̲R̲R̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲
2.7.1.1 P̲A̲R̲R̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲1̲F̲
The information concerning the suspected module(s)
contain:
COMPLETION CODE: completion code
translation of completion code
info-0 translation
info-1 translation
LINE PRINTER STATUS status of LP
translation of LP status
2.7.2 P̲A̲R̲R̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲
2.7.2 P̲A̲R̲R̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲ ̲P̲o̲i̲n̲t̲ ̲2̲B̲
TBD
2.7.3 P̲A̲R̲R̲ ̲-̲ ̲E̲X̲A̲M̲P̲L̲E̲ ̲O̲F̲ ̲A̲N̲ ̲E̲R̲R̲O̲R̲ ̲R̲E̲P̲O̲R̲T̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
ERROR REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error Detection Time: DEC 05 1983 09:30:45
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Test Area ID:
Site: TOR
Test Area ID: 16
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUSPECTED MODULE IN TEST AREA
PU AREA : NSP1/SCU0
MODULE NAME : PARR
MODULE LOGICAL ID : 00AAP01
MODULE H/W ID : #28
SUBMODULE H/W ID : 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUPERVISORS REASON FOR ISOLATION:
Error detected i LP connected to Parr Ctrl.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
INFORMATION CONCERNING SUSPECTED MODULE:
COMPLETION CODE: (?), (?)
LINE PRINTER STATUS: #0002: A Printer Fault is detected.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
CONFIGURATION CHANGE:
The Line printer is taken offline
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2.8 C̲P̲U̲/̲M̲A̲P̲/̲R̲A̲M̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲
Figure 2.8-1…01…CPU/MAP/RAM Test Area
CPU/MAP/RAM Test Area Contents:
- Components: CPU, MAP, RAM, MIA
- Test Area ID: 00…86…1 …02… …02… …02… …02… …02…
2.8.1 C̲P̲U̲/̲M̲A̲P̲/̲R̲A̲M̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲
2.8.1.1 C̲P̲U̲/̲M̲A̲P̲/̲R̲A̲M̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲ ̲t̲o̲ ̲p̲o̲i̲n̲t̲ ̲1̲F̲
The information concerning the suspected module(s)
contain:
MAP STATUS WORD: MAP Status word
translation of status word
MAP CAUSE CODE: MAP Cause Code
translation of Cause code
DMA ERROR ADDRESS: Page No, offset where the error
was discovered
INTERRUPT CAUSE CODE
PRIMARY CAUSE CODE
translation of 1. cause code
SECONCARY CAUSE CODE
translation of 2. cause code
2.8.2 C̲P̲U̲/̲M̲A̲P̲/̲R̲A̲M̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲
2.8.2.1 C̲P̲U̲/̲M̲A̲P̲/̲R̲A̲M̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲2̲B̲
TBD…86…1 …02… …02… …02… …02… …02…
A.2.8.3 C̲P̲U̲/̲M̲A̲P̲/̲R̲A̲M̲ ̲E̲X̲A̲M̲P̲L̲E̲ ̲O̲F̲ ̲A̲N̲ ̲E̲R̲R̲O̲R̲ ̲R̲E̲P̲O̲R̲T̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
ERROR REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error Detection Time: DEC 05 1983 09:30:45
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Test Area ID:
Site: TOR
Test Area ID: 00
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUSPECTED MODULE IN TEST AREA
PU AREA : NSP1
MODULE NAME : PU
MODULE LOGICAL ID :
MODULE H/W ID :
SUBMODULE H/W ID :
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUPERVISORS REASON FOR ISOLATION:
Not possible to load programs into the PU
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
INFORMATION CONCERNING SUSPECTED MODULE:
MAP STATUS WORD: #0400: Read Error, Error at Data Buffer
MAP CAUSE Code: #0400: Parity Error Detected by MAP
DMA ERROR ADDRESS: 03F8: Page No, Page Off set
INTERRUPT CAUSE CODE PRIMARY: 3: Page Fault in Program
Space.
INTERRUPT CAUSE CODE SECONDARY: 3F8: ALA of Absent
Location.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
CONFIGURATION CHANGE:
PU No. NSP1 is taken offline
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2.9 D̲A̲T̲A̲ ̲C̲H̲A̲N̲N̲E̲L̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲
Figure 2.9-1…01…Data Channel Test Area
Data Channel - Test Area Contents:
- Components: MAP, MIA, CIA, MBT
- Test Area ID: F
2.9.1 D̲A̲T̲A̲ ̲C̲H̲A̲N̲N̲E̲L̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲
2.9.1.1 D̲A̲T̲A̲ ̲C̲H̲A̲N̲N̲E̲L̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲1̲F̲
The information concerning the suspected module(s)
contain:
MAP STATUS WORD: MAP STATUS WORD
translation of status word
MAP CAUSE CODE: MAP Cause Code
translation of Cause Code
DMA ERROR ADDRESS: Page No, Offset where the error
was discovered
INTERRUPT CAUSE CODE
PRIMARY: Primary Cause Code
translation of 1. Cause Code
SECONDARY: Secondary cause code
translation of 2. cause code
2.9.2 D̲A̲T̲A̲ ̲C̲H̲A̲N̲N̲E̲L̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲ ̲R̲e̲p̲o̲r̲t̲s̲
2.9.2.1 D̲A̲T̲A̲ ̲C̲H̲A̲N̲N̲E̲L̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲ ̲R̲e̲p̲o̲r̲t̲ ̲P̲o̲i̲n̲t̲ ̲2̲B̲
TBD
2.9.3 D̲A̲T̲A̲ ̲C̲H̲A̲N̲N̲E̲L̲ ̲-̲ ̲E̲X̲A̲M̲P̲L̲E̲ ̲O̲F̲ ̲A̲N̲ ̲E̲R̲R̲O̲R̲ ̲R̲E̲P̲O̲R̲T̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
FIRST LEVEL ERROR REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error Detection Time: DEC 05 1983 09:30:45
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Test Area ID:
Site: TOR
Test Area ID: F
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUSPECTED MODULE IN TEST AREA
PU AREA : NSP1/CU1
MODULE NAME : MIA-CIA
MODULE LOGICAL ID : 00AB
MODULE H/W ID :
SUBMODULE H/W ID :
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUPERVISORS REASON FOR ISOLATION:
Timeout from data channel
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
INFORMATION CONCERNING SUSPECTED MODULE:
MAP STATUS WORD: #0400: Error during Read, Error at
Data
Buffer
MAP CAUSE Code: #0800: Timeout on Data Channel
DMA ERROR ADDRESS: #400, #0000: Page No, Page Offset
INTERRUPT CAUSE CODE 1.: 15: Time out
INTERRUPT CAUSE CODE 2.: #1007: Device LTU No 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
CONFIGURATION CHANGE:
PU No. NSP 1 CU No. CU1 Closed.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2.10 W̲D̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲
Figure 2.10-1…01…WD - VDU Driver…01…(sheet 1 of 4)
2.10 W̲D̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲
Figure 2.10-1…01…WD - PU Driver…01…(sheet 2 of 4)
2.10 W̲D̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲
Figure 2.10-1…01…WD - LP Driver…01…(sheet 2 of 4)
2.10 W̲D̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲
Figure 2.10-1…01…WD - CCA Driver…01…(sheet 4 of 4)
W̲D̲ ̲-̲ ̲T̲e̲s̲t̲ ̲A̲r̲e̲a̲ ̲C̲o̲n̲t̲e̲n̲t̲s̲:̲
- Components: WD CRATE, WD CPU, WCA, CCBA, CUCP,
CCAs, Maint. Pos. VDU, Maint. Pos. MSP
- Test Area ID: WD: 20
WD-PU: 21
VDU: 22
LP: 23
CCB: 24
2.10.1 W̲D̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲
2.10.1.1 W̲D̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲1̲F̲
The information concerning the suspected module(s)
contain:
ERROR ID: Error No translation of error no.
ACTUAL VALUE: actual value translation
EXPECTED VALUE: expected value translation
2.10.2 W̲D̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲R̲e̲p̲o̲r̲t̲s̲
2.10.2.1 W̲D̲ ̲-̲ ̲R̲e̲q̲.̲ ̲t̲o̲ ̲t̲h̲e̲ ̲L̲e̲v̲e̲l̲ ̲2̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲ ̲p̲o̲i̲n̲t̲ ̲2̲B̲
TBD
2.10.3 W̲D̲ ̲-̲ ̲E̲X̲A̲M̲P̲L̲E̲ ̲o̲f̲ ̲O̲n̲ ̲E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲s̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
ERROR REPORT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error Detection Time: DEC 05 1983 09:30:45
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Error
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Test Area ID:
Site: TOR
Test Area ID: 10
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUSPECTED MODULE IN TEST AREA
PU AREA : NSP1/CU2
MODULE NAME : CU
MODULE LOGICAL ID : 00AB
MODULE H/W ID :
SUBMODULE H/W ID :
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SUPERVISORS REASON FOR ISOLATION:
H/W error detected in CU Crate No. 00AB
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
INFORMATION CONCERNING SUSPECTED MODULE:
ERROR ID: 02: +5V CU POWER BUS A
ACTUAL VALUE: 0 VOLTS
EXPECTED VALUE: 5 VOLTS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
CONFIGURATION CHANGE:
No change in the configuration
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
A N N E X B
DATASHEETS
