|
DataMuseum.dkPresents historical artifacts from the history of: CP/M |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about CP/M Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 24576 (0x6000)
Types: RcTekst
Names: »99109780.WP«
└─⟦dedaa6eab⟧ Bits:30005866/disk1.imd Dokumenter i RcTekst format (RCSL 99-1-*)
└─⟦this⟧ »99109780.WP«
╱04002d4e0c0006000000000301483100000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
┆06┆i↲
↲
↲
┆a1┆┆b0┆TABLE OF CONTENTS┆05┆PAGE↲
↲
1. INTRODUCTION ..................................................... 1↲
╞ 1.1 Changes ..................................................... 1↲
╞ 1.2 Glossary of Terms ........................................... 2↲
↲
2. GENERAL COMMUNICATION RULES ...................................... 3↲
╞ 2.1 Message Format .............................................. 3↲
╞ 2.1.1 Mode ................................................. 3↲
╞ 2.1.2 First and Last Storage Address ....................... 3↲
╞ 2.1.3 First Segment ........................................ 4↲
╞ 2.2 Answer Format ............................................... 4↲
↲
3. OPERATIONS ....................................................... 7↲
╞ 3.1 SENSE ....................................................... 7↲
╞ 3.2 INPUT ....................................................... 8↲
╞ 3.3 OUTPUT ..................................................... 10↲
╞ 3.4 POSITION ................................................... 11↲
╞ 3.5 SECURITY ERASE ............................................. 12↲
↲
↲
┆a1┆┆b0┆APPENDIX↲
↲
A. REFERENCES ...................................................... 13↲
↲
B. DETAILED STATUS FORMAT .......................................... 14↲
╞ B.1 Answer Format .............................................. 14↲
╞ B.2 Status Description ......................................... 14↲
╞ B.2.1 Control Module Status ............................... 15↲
╞ B.2.2 System Intervention Status .......................... 15↲
╞ B.2.3 Manual Intervention Status .......................... 17↲
╞ B.2.4 Delay Code .......................................... 17↲
╞ B.2.5 Slave Device Status ................................. 18↲
╞ B.2.6 Flaw Address (byte 3-0) ............................. 18↲
↲
C. MESSAGE/ANSWER FORMAT SUMMARY ................................... 19↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆06┆ii↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆┆b0┆┆06┆┆0b┆↲
↲
┆b0┆┆a1┆1. INTRODUCTION.┆e1┆↲
↲
┆84┆This manual is only valid for areas on RC834x discs connected ↓
┆19┆┆89┆┄┄through an IDA801 adapter.↲
┆84┆The error recovery procedure has been changed compared to the ↓
┆19┆┆89┆┄┄one used in connection with areas located on RC82xx discs. The ↓
┆19┆┆89┆┄┄error recovery procedure is similar to the one used when acces┄↓
┆19┆┆89┆┄┄sing the disc directly (see ref. 2).↲
↲
↲
┆a1┆┆b0┆1.1 Changes.┆e1┆↲
↲
┆84┆The following has been changed compared to areas stored on ↓
┆19┆┆89┆┄┄RC82xx disc (see ref. 1):↲
↲
- A new operation SECURITY ERASE has been added.↲
↲
- The SENSE operation has been changed.↲
↲
- ┆84┆The MODE specification in the operations has been changed. It ↓
┆19┆┆8b┆┄┄is no longer possible to specify limited or no error recove┄↓
┆19┆┆8b┆┄┄ry.↲
Specification of READ AFTER WRITE is now possible.↲
↲
- ┆84┆┆84┆The format of the answer has been changed. The four first ↓
┆19┆┆8b┆┄┄words in the answer resembles the old format but the contents ↓
┆19┆┆8b┆┄┄of the last four words has been changed.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆1.2. Glossary of Terms.┆e1┆↲
↲
ISI: ┆84┆Intelligent Standard Interface. Interface of the ↓
┆19┆┆97┆┄┄disc units to the RC8000 Intelligent Device ↓
┆19┆┆97┆┄┄Adapter (IDA).↲
↲
IDA: ┆84┆Intelligent Device Adapter. Adapter which inter┄↓
┆19┆┆97┆┄┄faces one or more ISI disc interfaces (and Pertec ↓
┆19┆┆97┆┄┄interfaces for magne┄tic tape stations) to RC8000.↲
↲
Segment: ┆84┆Logical data block containing 512 RC8000 half┄↓
┆19┆┆97┆┄┄words (768 8 bits bytes). One RC8000 segment is ↓
┆19┆┆97┆┄┄composed of three physical disc ┆b0┆sectors┆f0┆.↲
↲
Sector: ┆84┆Physical data block on the discs, containing 256 ↓
┆19┆┆97┆┄┄8 bits bytes. It is not possible to address and ↓
┆19┆┆97┆┄┄transfer one single sector to or from RC8000, but ↓
┆19┆┆97┆┄┄only in groups of three sectors (one segment).↲
↲
Slave device: A physical disc connected to an ISI interface.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆2. GENERAL COMMUNICATION RULES.↲
↲
The kind of a backing store area process is 4.↓
↲
↲
┆a1┆┆b0┆2.1. Message Format.┆e1┆↲
↲
┆84┆The format of a message to an area depends on the operation. An ↓
┆19┆┆89┆┄┄i/o message may serve as an example.↲
↲
+ 0: operation< 12 + mode↲
+ 2: first RC8000 storage address↲
+ 4: last RC8000 storage address↲
+ 6: first segment↲
↲
↲
┆b0┆┆a1┆2.1.1. Mode.┆e1┆↲
↲
┆84┆The mode specification in the operations has the following ↓
┆19┆┆89┆┄┄field:↲
↲
mode: read after write<0↲
↲
read after write: only in output operation.↲
┆84┆If one, the specified block is read to check ↓
┆19┆┆9b┆┄┄that it contains no uncorrectable errors.↲
↲
↲
┆b0┆┆a1┆2.1.2. First and Last Storage Address.↲
↲
╞ ┆84┆If first or last address is odd, they will be decreased by one.↲
┆84┆First and last storage address must point to a storage area ↓
┆19┆┆89┆┄┄within the sending process.↲
┆84┆If not the specified storage area is a multiple of the segment ↓
┆19┆┆89┆┄┄size (512 RC8000 halfwords) the last storage address will be ↓
┆19┆┆89┆┄┄adjusted (decreased) to fit a multiple of the segment size.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆2.1.3. First Segment.↲
↲
┆84┆This is the address (segment number) of the first segment which ↓
┆19┆┆89┆┄┄the operation concerns. The segment number is given relative to ↓
┆19┆┆89┆┄┄the beginning of the area (first segment of the area has number ↓
┆19┆┆89┆┄┄zero).↲
↲
↲
┆a1┆┆b0┆2.2. Answer Format.┆e1┆↲
↲
┆84┆When communicating with an area process the following results ↓
┆19┆┆89┆┄┄are possible from the "wait answer" system call:↲
↲
Result 1: ┆84┆Message accepted, answer contains further status ↓
┆19┆┆93┆┄┄information.↲
Result 2: Violation of user/reserver requirement.↲
Result 3: Unintelligible message; illegal operation or mode.↲
Result 4: Malfunction, IDA controller troubles.↲
Result 5: ┆84┆Receiver unknown, the specified area process does not ↓
┆19┆┆93┆┄┄exist.↲
↲
┆84┆For every operation the meaning of result 2 and 3 will be ↓
┆19┆┆89┆┄┄speci┄fied.↲
↲
┆84┆The answers contains logical RC8000 status, RC8000/IDA communi┄↓
┆19┆┆89┆┄┄cation status, control module (ISI) status and the status of ↓
┆19┆┆89┆┄┄the slave device on which the area is located.↲
↲
════════════════════════════════════════════════════════════════════════
↓
The answers has the following common format:↲
↲
+ 0: status word↲
+ 2: number of halfwords transferred↲
+ 4: number of characters transferred↲
+ 6: i/o result↲
+ 8: reserved<8 + control module status<0↲
+10: ┆84┆system intervention code<16 + manual intervention ↓
┆19┆┆91┆┄┄code<8 + delay code<0↲
+12: ┆84┆reserved<16 + slave device status<8 + flaw address, ↓
┆19┆┆91┆┄┄byte 3<0↲
+14: flaw address, byte 2<16 + flaw address, byte 1<8↲
+ flaw address, byte 0<0↲
↲
Status: This status word is bit encoded:↲
bit 0: intervention↲
1: parity error or hard error↲
2: position error↲
5: end of area↲
11: ┆84┆disc error after error recovery (always set of any ↓
┆19┆┆91┆┄┄error).↲
↲
Number of Halfwords and Number of Characters Transferred:↲
╞ ┆84┆Specifies the exact number of characters which have been trans-↓
┆19┆┆89┆┄┄ferred without errors. Number of halfwords specifies number of ↓
┆19┆┆89┆┄┄halfwords which have been modified (always a multiple of 2).↲
↲
════════════════════════════════════════════════════════════════════════
↓
i/o result:↲
0: normal termination↲
1: RC8000 system bus reject.↲
2: RC8000 system bus timeout.↲
3: software timeout.↲
6: power restart.↲
╞ 7: RC8000 system bus data reject↲
╞ 8: RC8000 system bus data timeout↲
9: RC8000 system bus parity error↲
╞ 10: controller bus reject↲
11: controller bus timeout↲
╞ 12: controller bus parity error↲
↲
┆84┆The information supplied in halfwords +8 to +14 is normally ↓
┆19┆┆89┆┄┄only of interest to test programs. In the rest of this manual ↓
┆19┆┆89┆┄┄it is called Detailed Status. For a detailed description see ↓
┆19┆┆89┆┄┄appendix B.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆3. OPERATIONS.┆e1┆↲
↲
The area process accepts the following messages:↲
↲
SENSE, INPUT, OUTPUT, POSITION and SECURITY ERASE.↲
↲
┆84┆SENSE and POSITION are control operations which concern the ↓
┆19┆┆89┆┄┄disc on which the area is located.↲
↲
┆84┆INPUT, OUTPUT and SECURITY ERASE concern transport of data ↓
┆19┆┆89┆┄┄from or to the area. SECURITY ERASE does not involve data ↓
┆19┆┆89┆┄┄transport from RC8000.↲
↲
↲
┆b0┆┆a1┆3.1. SENSE┆e1┆↲
↲
Function:↲
↲
The device, on which the area is stored, is sensed.↲
┆84┆No input/output operation is initiated on the disc but a seek ↓
┆19┆┆89┆┄┄operation is performed to the track on which the first segment ↓
┆19┆┆89┆┄┄of the area is stored, to get a correct slave device status; ↓
┆19┆┆89┆┄┄i.e. SENSE acts like a POSITION operation to segment zero of ↓
┆19┆┆89┆┄┄the area, but if the size of the area is zero (no segment allo┄↓
┆19┆┆89┆┄┄cated) no END OF AREA status is given and the slave device ↓
┆19┆┆89┆┄┄status will not be valid.↲
↲
The sending process must be user of the area process.↲
↲
Message:↲
+ 0: 0<12 + 0↲
↲
════════════════════════════════════════════════════════════════════════
↓
Answer:↲
+ 0: status↲
+ 2: 0↲
+ 4: 0↲
+ 6: i/o result↲
+ 8 - + 14: detailed status↲
↲
Errors: Result 2: Calling process is not user of area process.↲
Area process reserved by another process.↲
Result 3: Not possible.↲
↲
↲
┆b0┆┆a1┆┆a1┆3.2. INPUT.┆e1┆↲
↲
Function:↲
↲
┆84┆A number of consecutive segments of 256 RC8000 words each are ↓
┆19┆┆89┆┄┄input to a storage area within the sending process. The first ↓
┆19┆┆89┆┄┄segment number relative to the beginning of the area on the ↓
┆19┆┆89┆┄┄backing store must be given in the message.↲
↲
┆84┆The segments need only be consecutive in a logical sense, thus ↓
┆19┆┆89┆┄┄securing that the user does not have to be aware of the posi┄↓
┆19┆┆89┆┄┄tion of the segments of an area.↲
↲
┆84┆The operation transfers the maximum number of segments for ↓
┆19┆┆89┆┄┄which there is room within the storage area, i.e. ↲
↲
number of segments=↲
(last storeage address+2 - first storage address)//512↲
↲
┆84┆If the input block thus specified exceeds the upper limit of ↓
┆19┆┆89┆┄┄the area on the backing store, input is performed only for that ↓
┆19┆┆89┆┄┄part of the block which is within the area. In any case the ↓
┆19┆┆89┆┄┄actual number of halfwords transferred is given in the answer.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆84┆If the first segment is outside the limits of the area, input ↓
┆19┆┆89┆┄┄is not initiated, but the answer contains the END OF AREA bit ↓
┆19┆┆89┆┄┄in the status word, number of halfwords/characters will be zero ↓
┆19┆┆89┆┄┄and the detailed status will be undefined.↲
↲
The sending process must be user of the area process.↲
↲
Message:↲
+ 0: 3<12 + 0↲
+ 2: first storage address.↲
+ 4: last storage address.↲
+ 6: first segment number.↲
↲
┆84┆ ┆84┆First and last storage address must point to a core area within ↓
┆19┆┆89┆┄┄the sending process.↲
↲
Answer:↲
+ 0: status↲
+ 2: number of halfwords transferred↲
+ 4: number of characters transferred↲
+ 6: i/o result↲
+ 8- +14: detailed status↲
↲
┆84┆ ┆84┆Number of characters defines the actual number of characters ↓
┆19┆┆89┆┄┄which has been transferred without errors. Number of halfwords ↓
┆19┆┆89┆┄┄defines the number of halfwords (in multiple of 2) which has ↓
┆19┆┆89┆┄┄been modified (c.f. section 2.2.).↲
↲
Errors: Result 2: ┆84┆Sending process is not user of area process.↲
Area reserved by another process↲
Result 3: Specified core area outside sending process.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆3.3. OUTPUT.┆e1┆↲
↲
Function: ↲
↲
┆84┆The output operation is equivalent to the input operation ↓
┆19┆┆89┆┄┄except that the specified core area is output to the area ↓
┆19┆┆89┆┄┄starting from the segment number given (the segment specified ↓
┆19┆┆89┆┄┄must be relative to the beginning of the area).↲
┆84┆Only blocks of a multiple of 512 halfwords will be transferred.↲
↲
The sending process must be reserver of the area process.↲
↲
Message:↲
+ 0: 5<12 + mode ↲
+ 2: first storage address↲
+ 4: last storage address↲
+ 6: first segment number↲
↲
Mode: See section 2.1.1.↲
┆84┆ ┆84┆First and last storage address must point to a core ↓
┆19┆┆91┆┄┄area within the sending process.↲
↲
Answer:↲
+ 0: status↲
+ 2: number of halfwords transferred↲
+ 4: number of characters transferred↲
+ 6: i/o result↲
+ 8-14: detailed status↲
↲
Errors: Result 2: ┆84┆Sending process is not reserver of area ↓
┆19┆┆9b┆┄┄process.↲
Result 3: Illegal mode specification.↲
╞ ╞ ╞ Specified core area outside sending process.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆3.4. POSITION.┆e1┆↲
↲
Function:↲
↲
┆84┆The read/write heads on the device on which the area is stored ↓
┆19┆┆89┆┄┄are moved to the cylinder on which the segment specified in the ↓
┆19┆┆89┆┄┄message (specified relative to the beginning of the area) is ↓
┆19┆┆89┆┄┄located.↲
┆84┆If the segment is outside the limits of the area, no operation ↓
┆19┆┆89┆┄┄is initiated, but the answer contains the END OF AREA status ↓
┆19┆┆89┆┄┄bit. In this case the detailed status will be undefined.↲
↲
The sending process must be user of the area process.↲
↲
Message:↲
+ 0: 8<12 + 0↲
+ 2: irrelevant↲
+ 4: irrelevant↲
+ 6: segment↲
↲
Answer:↲
+ 0: status word↲
+ 2: 0↲
+ 4: 0↲
+ 6: i/o result↲
+ 8-14: detailed status↲
↲
Errors: Result 2: ┆84┆Sending process is not user of area process.↲
Area reserved by another process.↲
Result 3: Not possible.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆3.5. SECURITY ERASE.┆e1┆↲
↲
Function:↲
↲
┆84┆The specified segment(s) in the area are erased. A random bit ↓
┆19┆┆89┆┄┄pattern is written on the segments.↲
↲
The sending process must be reserver of the area process.↲
↲
Message:↲
+ 0: 18<12 + 0↲
+ 2: 0↲
+ 4: 0↲
+ 6: first segment↲
+ 8: no of segments↲
↲
Answer:↲
+ 0: status↲
+ 2: (no of halfwords erased)↲
+ 4: no of characters erased↲
+ 6: i/o result↲
+ 8- +14: detailed status↲
↲
Errors: Result 2: ┆84┆Sending process is not reserver of area ↓
┆19┆┆9b┆┄┄process.↲
Result 3: Not possible.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆APPENDIX.┆e1┆↲
↲
↲
┆a1┆┆b0┆A. REFERENCES.↲
↲
(1) RC8000 Backing store area process.↲
RCSL no 31-D539.↲
↲
↲
(2) RC8000/IDA801 Disc Process, Reference Manual.↲
RCSL no 991 09775.↲
↲
↲
(3) Intelligent Standard Interface (ISI) Specification.↲
Spec.: 77653440.↲
↲
↲
(4) Product Specification for 9056 Control Module.↲
Spec.: 64400100.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆a1┆┆b0┆B. DETAILED STATUS FORMAT.┆e1┆↲
┆a1┆↲
┆84┆In this section a description of the status delivered in word ↓
┆19┆┆89┆┄┄+8 - +14 of the answer is given.↲
╞ ┆84┆It is recommended to consult ref. 3 and 4 for a more detailed ↓
┆19┆┆89┆┄┄description.↲
↲
┆b0┆┆a1┆B.1. Answer Format.┆e1┆↲
↲
Summary of the answer format:↲
↲
+ 0: -↲
+ 2: -↲
+ 4: -↲
+ 6: -↲
+ 8: reserved<8 + Control Module status<0↲
+10: ┆84┆System intervention code<16 + Manual intervention ↓
┆19┆┆91┆┄┄code<8 + Delay code<0↲
+12: ┆84┆reserved<16 + slave device status<8 + flow address, ↓
┆19┆┆91┆┄┄byte 3<0↲
+14: ┆84┆Flow address, byte 2<16 + flow address, byte 1<8 ↓
┆19┆┆91┆┄┄+ flow address, byte 0<0↲
↲
↲
┆a1┆┆b0┆B.2. Status Description.↲
↲
┆84┆In the following description the bit number is given relative ↓
┆19┆┆89┆┄┄to the specified field, where bit 0 is the most significant ↓
┆19┆┆89┆┄┄bit.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆┆b0┆┆a1┆B.2.1. Control Module Status.┆e1┆↲
↲
This is bit encoded:↲
↲
Bit 0: ┆84┆Normal end (no further information in system/manual ↓
┆19┆┆92┆┄┄intervention status fields but delay code may contain ↓
┆19┆┆92┆┄┄valid information).↲
1: ┆84┆Check end (further information in system/manual ↓
┆19┆┆92┆┄┄intervention or delay status fields).↲
2-4: Execution status: 100B ISI i/o parity error or↲
internal controller error.↲
110B Disc pack change (RC8345).↲
5: System intervention status valid.↲
6: Manual intervention status valid.↲
7: Delay status valid.↲
↲
┆84┆Bit 5-7 indicates whether or not further information can be ↓
┆19┆┆89┆┄┄found in the corresponding fields of the answer.↲
↲
↲
┆a1┆┆b0┆B.2.2. System Intervention Status.┆e1┆↲
↲
00 (00H): No system intervention status↲
33 (21H): Seek error↲
65 (41H): Unable to read header (read operation)↲
67 (43H): Unable to read data↲
97 (61H): Unable to read header (write operation)↲
↲
════════════════════════════════════════════════════════════════════════
↓
Seek error:↲
┆84┆A seek error may be detected in all of the operations. If it is ↓
┆19┆┆89┆┄┄detected the following is automatically done:↲
┆84┆The heads are moved to track zero and the seek is repeated ↓
┆19┆┆89┆┄┄once. If this second seek succeeded the status word will ↓
┆19┆┆89┆┄┄indicate operation completed, the control module status will ↓
┆19┆┆89┆┄┄indicate NORMAL END but the delay status will indicate SEEK ↓
┆19┆┆89┆┄┄RETRY APPLIED.↲
┆84┆If the second seek failed, the status word indicates POSITION ↓
┆19┆┆89┆┄┄ERROR, control module status indicates CHECK END, system ↓
┆19┆┆89┆┄┄intervention status indicates SEEK ERROR and delay status ↓
┆19┆┆89┆┄┄indicates SEEK RETRY APPLIED.↲
↲
Read header trouble:↲
┆84┆If the address information (header) part of a sector contains ↓
┆19┆┆89┆┄┄an error (which may be detected through an ECC mismatch) no ECC ↓
┆19┆┆89┆┄┄error correction is applied, but a rereading of the header will ↓
┆19┆┆89┆┄┄be performed once. If this rereading of the header is unsuc┄↓
┆19┆┆89┆┄┄cessful and it is impossible to verify that the slave device is ↓
┆19┆┆89┆┄┄on the proper cylinder, a return to track zero and a seek to ↓
┆19┆┆89┆┄┄specified track is performed to ensure that the correct cylin┄↓
┆19┆┆89┆┄┄der is selected, before an error status is delivered (system ↓
┆19┆┆89┆┄┄intervention status will indicate UNABLE TO READ HEADER).↲
┆84┆If the rereading of the header was successful the control ↓
┆19┆┆89┆┄┄module status will indicate NORMAL END, but the delay code will ↓
┆19┆┆89┆┄┄indicate HEADER RETRY APPLIED.↲
↲
Read data trouble:↲
┆84┆If an error is detected during a reading of the data part of a ↓
┆19┆┆89┆┄┄sector the following is done:↲
┆84┆Two attempts to read the data are made with carriage and data ↓
┆19┆┆89┆┄┄offset at nominal, and single burst (of at most 25 bits) ECC ↓
┆19┆┆89┆┄┄employed. Then three attempts are made at each of the strobe ↓
┆19┆┆89┆┄┄offsets (early and late) while holding the carriage offset at ↓
┆19┆┆89┆┄┄nominal.↲
════════════════════════════════════════════════════════════════════════
↓
┆84┆Also three attempts are made at each of the carriage offsets ↓
┆19┆┆89┆┄┄(plus and minus) while holding the strobe offset at nominal. ↓
┆19┆┆89┆┄┄Finally, one more attempt is made with the offsets in their ↓
┆19┆┆89┆┄┄nominal conditions. A single burst ECC procedure is applied in ↓
┆19┆┆89┆┄┄the final attempt.↲
┆84┆If the error recovery is unsuccessful the control module will ↓
┆19┆┆89┆┄┄indicate CHECK END, system intervention status will indicate ↓
┆19┆┆89┆┄┄UNABLE TO READ DATA and the delay code will indicate DATA ↓
┆19┆┆89┆┄┄CORRECTION APPLIED and DATA RETRY APPLIED.↲
┆84┆If the error recovery was succesfull the control module will ↓
┆19┆┆89┆┄┄indicate NORMAL END but the delay code will indicate DATA ↓
┆19┆┆89┆┄┄CORRECTION APPLIED and/or DATA RETRY APPLIED depending on when ↓
┆19┆┆89┆┄┄the error recovery succeeded.↲
↲
↲
┆a1┆┆b0┆B.2.3. Manual Intervention Status┆e1┆↲
↲
00 (00H): No manual intervention status.↲
Other valu┆84┆es: ┆84┆Indicates an error which normally is correct┄↓
┆19┆┆9a┆┄┄able only through manual intervention. For ↓
┆19┆┆9a┆┄┄further information see ref. 3 and 4.↲
↲
↲
┆b0┆┆a1┆B.2.4. Delay Code┆e1┆↲
↲
┆84┆The delay code specifies whether or not an error recovery ↓
┆19┆┆89┆┄┄action has been performed. The dalay code does not necessarily ↓
┆19┆┆89┆┄┄indi┄cate an error as the data correction may have been success-↓
┆19┆┆89┆┄┄full.↲
↲
00 (00H): No delay status↲
33-39 (21-27H): Bit encoded delay status:↲
0010.0xx1 Data correction applied↲
0010.0x1x Seek retry applied↲
0010.01xx Data retry applied↲
66 (42H): Header retry applied.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆B.2.5. Slave Device Status.↲
↲
The slave device status is bit-encoded:↲
↲
╞ bit 0: No head select↲
╞ 1: Write fault↲
2: read/write off cylinder↲
3: read/write fault↲
4: voltage fault↲
5: head select fault↲
6: seek error↲
7: write protect↲
↲
↲
┆b0┆┆a1┆B.2.6. Flaw Address (byte 3 - 0)┆e1┆↲
↲
↲
┆84┆The flaw address is given as an absolute sector address on the ↓
┆19┆┆89┆┄┄physical disc.↲
┆84┆If the operation succeeded but the delay status indicates 'data ↓
┆19┆┆89┆┄┄correction applied' or 'data retry applied', it contains the ↓
┆19┆┆89┆┄┄sector address of the sector which needed data correction to be ↓
┆19┆┆89┆┄┄applied (only possible for input and output with read after ↓
┆19┆┆89┆┄┄write specified).↲
┆84┆If the operation failed because of an unrecovable error, it ↓
┆19┆┆89┆┄┄contains the sector-address of the eroneous sector.↲
╞ ┆84┆If the operation succeeded it is undefined.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆a1┆┆b0┆C. MESSAGE/ANSWER FORMAT SUMMARY.↲
↲
┆a1┆┆e1┆ ┆a1┆Operation┆e1┆ ┆a1┆Message┆e1┆ ┆a1┆Answer┆e1┆↲
↲
sense 0<12 + 0 status word↲
0↲
0↲
i/o result↲
detailed status↲
- " -↲
- " -↲
- " -↲
╱04002d4e0c00060000000003014c3100000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
╱04002d4e0c0006000000000301483100000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
↓
↲
↲
input 3<12 + 0 status word↲
first storage address number of halfwords↲
last storage address number of characters↲
first segment number i/o result↲
detailed status↲
- " -↲
- " -↲
- " -↲
↲
↲
output 5<12 + mode status word↲
first storage address number of halfwords↲
last storage address number of characters↲
first segment number i/o result↲
detailed status↲
- " -↲
- " -↲
- " -↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
position 8<12 + 0 status word↲
irrelevant 0↲
irrelevant 0↲
segment i/0 result↲
detailed status↲
- " -↲
- " -↲
- " -↲
↲
↲
security erase 18<12 + 0 status word↲
0 number of halfwords↲
0 number of characters↲
first segment i/o result↲
number of segments detailed status↲
- " -↲
- " -↲
- " -↲
┆1a┆┆1a┆16