top - download
⟦56df3c0c6⟧ Wang Wps File
Length: 4323 (0x10e3)
Types: Wang Wps File
Notes: Req.for Error Handling
Names: »0121A «
Derivation
└─⟦2c0571bd0⟧ Bits:30005816 8" Wang WCS floppy, CR 0005A
└─ ⟦this⟧ »0121A «
WangText
…02…CPS/TCN/0012
…02…19800801…02……02…#
REQUIREMENTS FOR ERROR HANDLING
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 INTRODUCTION .................................
2 ERRORS AND ERROR HANDLING CATEGORIES
(FUNCTIONAL BREAKDOWN)........................
2.1 GENERAL BREAKDOWN.........................
2.2 DETAILED BREAKDOWN........................
1̲.̲ ̲I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲ ̲
A requirements specification for error handling may
be composed of descriptions of
1. Error Categories and a detailed breakdown within
each category.
2. Error Detecting Modules needed. Requirements
for reporting and/or corrective action shall
be defined and the associated performance specified.
It is the purpose of this paper to propose a breakdown
in error categories and error handling categories and
combine these.
The result of an attempt to map the system performance
requirements to the subsystems may be used as a guide
for specifying proper requirements for the error handling
expressed for single modules or subsystems within each
of the categories (see the paper: MAPPING OF PERFORMANCE
REQUIREMENTS TO SUBSYSTEMS, CPS/TCN/0013)
2̲.̲E̲R̲R̲O̲R̲S̲ ̲A̲N̲D̲ ̲E̲R̲R̲O̲R̲ ̲H̲A̲N̲D̲L̲I̲N̲G̲ ̲C̲A̲T̲E̲G̲O̲R̲I̲E̲S̲
(̲F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲B̲R̲E̲A̲K̲D̲O̲W̲N̲)̲
2.1 G̲E̲N̲E̲R̲A̲L̲ ̲B̲R̲E̲A̲K̲D̲O̲W̲N̲
Hardware (or equipment) errors may be handled by hardware
only; but they may also be subject to further firmware
- and maybe software handling.
The term h̲a̲n̲d̲l̲e̲d̲ implies the following steps
- detection of error
- evaluation (may not be present)
- reporting (final or to higher level of handling)
- automatic action (may not be present)
Firmware errors may be handled by firmware and software.
Software errors may only be handled by software.
Fig. 2.1-1 provides an overview of Error Types and
error handling tools.
Further, error handling tools may be of the following
types
- on line
- selftest
- off line
Also, error handling may be supported by system software
or by the application software.
Fig. 2.1-1
2.2 D̲E̲T̲A̲I̲L̲E̲D̲ ̲B̲R̲E̲A̲K̲D̲O̲W̲N̲
2.2.1 H̲/̲W̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲e̲d̲ ̲b̲y̲ ̲H̲/̲W̲
2.2.1.1 O̲f̲f̲ ̲L̲i̲n̲e̲
- Test Equipment
- Dip Switches
2.2.1.2 S̲e̲l̲f̲t̲e̲s̲t̲
None
2.2.1.3 O̲n̲ ̲L̲i̲n̲e̲
- LED Indications
- Fuses
- Thermometers, Hygrometers, V-Ameters
- Bells
2.2.2 H̲/̲W̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲e̲d̲ ̲b̲y̲ ̲F̲/̲W̲
2.2.2.1 O̲f̲f̲ ̲L̲i̲n̲e̲
- Test Equipment
2.2.2.2 S̲e̲l̲f̲t̲e̲s̲t̲
The following cyclic selftest shall be required
- LTU
- DISC Controller
- TDX
- I/O bus
- MAP (+DMA)
- RAM
- CPU/CACHE
2.2.2.3 O̲n̲ ̲L̲i̲n̲e̲
- LTU Protocol (Device errors, CRC, parity errors)
- TDX Protocol (Host I/F, Controllers)
- MAP ACCES (I/O, RAM)
- DISC Controller (disc error)
2.2.3 H̲/̲W̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲e̲d̲ ̲b̲y̲ ̲S̲/̲W̲
2.2.3.1 O̲f̲f̲ ̲L̲i̲n̲e̲
- (System) Test S/W (Test Drivers)
2.2.3.2 S̲e̲l̲f̲t̲e̲s̲t̲
Refer to section 2.2.2.2: This test may be performed
totally (in some cases) or in part by S/W.
Certain tests (checks) have been built into the application
S/W (Channel check, channel continuity)
2.2.3.3 O̲n̲ ̲L̲i̲n̲e̲
- System Integrity Check (SUM-check)
- Drivers (Completion Codes)
2.2.4 F̲/̲W̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲e̲d̲ ̲b̲y̲ ̲F̲/̲W̲
2.2.4.1 O̲f̲f̲ ̲L̲i̲n̲e̲
- Test Equipment
2.2.4.2 S̲e̲l̲f̲t̲e̲s̲t̲
None
2.2.4.3 O̲n̲ ̲L̲i̲n̲e̲
- TDX protocol check of LTU F/W
- TDX internal checks
- LTU protocol check of device F/W
2.2.5 F̲/̲W̲ ̲E̲r̲r̲o̲r̲s̲ ̲H̲a̲n̲d̲l̲e̲d̲ ̲b̲y̲ ̲S̲/̲W̲
2.2.5.1 O̲f̲f̲ ̲L̲i̲n̲e̲
- (System) Test S/W
2.2.5.2 S̲e̲l̲f̲t̲e̲s̲t̲
None
2.2.5.3 O̲n̲ ̲L̲i̲n̲e̲
- TDX Drivers/Protocol (Completion Codes)
- I/O Drivers/Protocol (Completion Codes)
2.2.6 S̲/̲W̲ ̲E̲r̲r̲o̲r̲s̲ ̲H̲a̲n̲d̲l̲e̲d̲ ̲b̲y̲ ̲S̲/̲W̲
2.2.6.1 O̲f̲f̲ ̲L̲i̲n̲e̲
As 2.2.6.3 but more detailed
2.2.6.2 S̲e̲l̲f̲t̲e̲s̲t̲
None
2.2.6.3 O̲n̲ ̲L̲i̲n̲e̲
- Child process to Parent process Completion Codes
- Security Violations