DataMuseum.dk

Presents historical artifacts from the history of:

Rational R1000/400 DFS Tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about Rational R1000/400 DFS Tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download

⟦30017cf38⟧ ERRMESS, TextFile

    Length: 4096 (0x1000)
    Types: ERRMESS, TextFile
    Names: »P2VAL.ERRMESS«

Derivation

└─⟦b4205821b⟧ Bits:30000743 8mm tape, Rational 1000, DFS, D_12_7_3 SEQ288
    └─ ⟦this⟧ »P2VAL.ERRMESS« 
└─⟦b434774df⟧ Bits:30000528 8mm tape, Rational 1000, DFS, D_12_6_5
    └─ ⟦this⟧ »P2VAL.ERRMESS« 
└─⟦bc1274df5⟧ Bits:30000750 8mm tape, Rational 1000, DFS backup from PAM's R1000
    └─ ⟦this⟧ »P2VAL.ERRMESS« 

TextFile

0	No errors detected by P2VAL.
1	VAL WCS Addressing error detected (P2VAL).
2	VAL WCS data bit error detected (P2VAL).
3	VAL WCS parity detection error detected (P2VAL).
4	VAL WCS RAM error. A cell in one of the WCS RAMS is either stuck
	high or stuck low (P2VAL).
5	The VAL board cannot load data into the WDR from the VAL BUS (P2VAL).
6	The VAL board cannot load correct parity into the WDR from the
	VAL BUS (P2VAL).
7	The VAL board cannot load correct parity into the WDR from the
	VAL BUS. No further isolation was done so the problem could be caused
	by any of the following: a problem on some other board connected to the
	VAL bus, a problem with the foreplane, or a problem with th VAL board.
	(P2VAL)
8	The VAL board cannot load data into the WDR from the VAL BUS.
	No further isolation was done so the problem could be caused
	by any of the following: a problem on some other board connected to the
	VAL bus, a problem with the foreplane, or a problem with th VAL board.
	(P2VAL)
9	The VAL board cannot receive data correctly from the FIU BUS (P2VAL).
10	The VAL board cannot receive data correctly from the FIU BUS.
	No further isolation was done so the problem could be caused
	by any of the following: a problem on some other board connected to the
	FIU bus, a problem with the foreplane, or a problem with th VAL board.
	(P2VAL)
11	The VAL LOOP COUNTER cannot be loaded correctly (P2VAL).
12	The VAL LOOP COUNTER cannot count correctly (P2VAL).
13	VAL LOOP COUNTER overflow does not work correctly (P2VAL).
14	VAL RF data bit error detected (P2VAL).
15	RF frame addressing error detected (P2VAL).
16	RF GP addressing error detected (P2VAL).
17	RF parity checker error detected (P2VAL).
18	Logical ALU error detected (P2VAL).
19	The ALU cannot generate all ones or all zeros (P2VAL).
20	The zero drivers on the A_BUS cannot drive all zeros (P2VAL).
21	The PASS_A_HIGH or PASS_B_HIGH randoms do not work porperly (P2VAL).
22	The SHIFT_MUX cannot shift the ALU output properly (P2VAL).
23	Arithmetic ALU error detected (P2VAL).
24	An error in the ALU carry look ahead logic was detected (P2VAL).
25	A Register File location has a stuck at fault.
26	An error in the leading zero counter was detected (P2VAL).
27	An error in the multiplier logic was detected  (P2VAL).
28	A problem was found in the logic that compares the parity bits coming
	out of the RF parity RAMS with the parity bits generated by the data
	on the A_BUS  (P2VAL).
29	A problem was found in the logic that compares the parity bits coming
	out of the RF parity RAMS with the parity bits generated by the data
	on the B_BUS  (P2VAL).
30	An error was detected in the logic associated with the arithmetic
	divide operation (M_BIT logic, Q_BIT logic, or conditional ALU ops).
31	An error was detected in an address bit to one of the RF A parity RAMS
	(P2VAL)
32	An error was detected in an address bit to one of the RF B parity RAMS
	(P2VAL)
33	An error was detected in a location in one of the RF A parity RAMS. A
	cell in the bad RAM is either stuck high or stuck low (P2VAL).
34	An error was detected in a location in one of the RF B parity RAMS. A
	cell in the bad RAM is either stuck high or stuck low (P2VAL).«nul»