Transfer Timing Alert; Transmission Parity Alert; Invalid Seek Address; Check Character Alert - Honeywell 6000 Series Reference Manual

Transfer Timing Ale rt
A Transfer Timing Alert occurs when data is lost during data transfer because some
hardware stage of the data transfer logic cannot keep up the transfer rate.
Transmis siun Parity Ale rt
A parity error was detected by the MPC during the transmission of data bytes frOrn the
EUS, or transmission to or from the device.
Invalid Seek Address
This substatus will occur if:
0 A Special Seek was issued to a user cylinder
0 A normal Seek instruction was is sued to the T 8: D cylinder
0 The Seek address exceeds the limit of one device
9 The Format Track verification data does not match the Seek address
0 Fewer than five bytes or more than five bytes are transferred as Seek data
This status also can occur when the check character test on the format instruction has
a compare mismatch.
Heade r Verification Failure
This status will be returned if the physical address bytes read from a count field do not
match the address in the previous Seek address, or if an error occurs during the Format
Track or Read Track Header instructions.
Check Characte r Alert
The field cyclic check character generated in the CA did not match the one recorded
on the media. This status will be set for check character failures, whether on a data field
or the home address. If the cyclic check occurs on the data field, the status returned will
be (010000). For Write and Compare operations, the status will be (110000) if, in addition
to the cyclic check error on the data field, the compare operation failed, as well.
Compare Ale'rt
This substatus results from 3 Write and Compare instruction. It indicates that the
data recorded does not match data received from the EUS.
END OF FILE
The data transfer for the last instruction tried to exceed some defined boundary. This
boundary may be a physical limit, the last block of an alternate track, or a program-imposed
limit (for example, sector count limit).
2-22 DB3?