|
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: 31488 (0x7b00)
Types: RcTekst
Names: »99109774.WP«
└─⟦dedaa6eab⟧ Bits:30005866/disk1.imd Dokumenter i RcTekst format (RCSL 99-1-*)
└─⟦this⟧ »99109774.WP«
╱04002d4e0c0006000000000301483140000000000000000000000000000000000000000000000000050a0f12191e23282d32373c4146ffff04╱
════════════════════════════════════════════════════════════════════════
↓
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ____________________________↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ RCSL No.:┆05┆991 09774↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ Edition:┆05┆1984.08.15↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ Authors:┆05┆Ole Thomasen↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
________________________________________________________________________↲
↲
↲
Title:↲
↲
┆06┆RC8000/IDA801 Magnetic Tape Process↲
┆06┆Reference Manual↲
↲
↲
________________________________________________________________________↲
════════════════════════════════════════════════════════════════════════
↓
┆06┆i↲
↲
↲
┆a1┆TABLE OF CONTENTS┆05┆PAGE↲
↲
↲
1.╞ INTRODUCTION....................................................┆05┆1↲
╞ 1.1╞ Changes....................................................┆05┆1↲
↲
2.╞ COMMUNICATION PROTOCOL..........................................┆05┆2↲
↲
3.╞ OPERATIONS......................................................┆05┆3↲
╞ 3.1╞ Operation Modes............................................┆05┆3↲
╞ 3.2╞ Sense......................................................┆05┆5↲
╞ 3.3╞ Input......................................................┆05┆5↲
╞ 3.4╞ Output.....................................................┆05┆5↲
╞ 3.5╞ Erase......................................................┆05┆7↲
╞ 3.6╞ Move.......................................................┆05┆7↲
╞ 3.7╞ Output File Mark...........................................┆05┆8↲
╞ 3.8╞ Extended Sense.............................................┆05┆8↲
╞ 3.9╞ Set Mode...................................................┆05┆9↲
╞ 3.10╞ Data Security Erase........................................┆05┆9↲
↲
4.╞ ANSWERS.........................................................┆05┆10↲
↲
↲
┆a1┆APPENDIX:┆e1┆↲
↲
A.╞ REFERENCES......................................................┆05┆13↲
↲
B.╞ STATUS WORD.....................................................┆05┆14↲
↲
C.╞ DETAILED STATUS INFORMATION.....................................┆05┆17↲
↲
D.╞ EXTENDED STATUS INFORMATION.....................................┆05┆18↲
↲
E.╞ STANDARDS.......................................................┆05┆20↲
↲
F.╞ MESSAGE/ANSWER FORMAT SURVEY....................................┆05┆21↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆┆05┆Page ┆0b┆↲
┆a1┆1.╞ INTRODUCTION┆e1┆↲
↲
This manual describes the use of magnetic tape stations connected to ↓
RC8000 through IDA801 (IDA - Intelligent Device Adapter) (ref. 1).↲
↲
The tape stations supported are RC3715 (ref. 2), RC8343 (ref. 3) and ↓
RC8344 (ref. 4).↲
↲
The tape stations supported are ECMA, ISO, ANSI and IBM format compatible ↓
(see Appendix F).↲
↲
↲
┆a1┆1.1 Changes┆e1┆↲
↲
Some changes has been made compared to previous manuals for magnetic ↓
tape stations:↲
↲
╞ - operation mode↲
╞ - a sense command exist for RC8343 and RC8344↲
╞ - an extended sense command exist for RC8344↲
╞ - a data security erase command exist↲
╞ - the answer contains sense information (for sense commands)↲
╞ - the time out bit in the status word indicates severe error↲
╞ - file and block numbers does not take the value (-1)↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆2.╞ COMMUNICATION PROTOCOL┆e1┆↲
↲
The RC8000/IDA Magnetic Tape Process is an RC8000 external process (ref. ↓
5, section 3.3), representing a magnetic tape document.↲
↲
The Magnetic Tape Process operates in three states:↲
↲
╞ ╞ 1.╞ no_document_mounted↲
╞ ╞ 2.╞ unidentified_document_mounted↲
╞ ╞ 3.╞ identified_document_mounted↲
↲
The initial state of the process is ┆a1┆no document mounted┆e1┆. When a tape is ↓
mounted and the device is switched to ┆a1┆online┆e1┆ (remote), the process state ↓
will be changed to ┆a1┆unidentified document mounted┆e1┆. Internal processes ↓
which have sent a message to the ┆a1┆remoter process┆e1┆ (ref. 6), will now re┄↓
ceive an answer notifying them of the event (this facility will normally ↓
only be of interest to operating systems).↲
↲
When a device is named by means of the monitor procedure ┆a1┆create peri┄↓
┆19┆┄┄┆84┆pheral pro┄cess┆e1┆, the process state becomes ┆a1┆iden┄ti┄fied docu┄ment moun┄ted.┆e1┆↲
↲
Operations can be initiated in all process states by an internal process ↓
that has ┆a1┆initialized┆e1┆ or ┆a1┆reserved┆e1┆ the device. These monitor procedures do ↓
not change the process state.↲
↲
The device is sensed before each operation. If the status word indicates ↓
that the device is ┆a1┆offline┆e1┆ (local), the name of the process is removed, ↓
and the present reservation (if any) is cancelled. The process state is ↓
changed to ┆a1┆no document mounted┆e1┆ and all pending and future messages will ↓
be answered with result = 5: ┆a1┆receiver does not exist┆e1┆.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆3.╞ OPERATIONS┆e1┆↲
↲
The operations allowed are defined in section 3.2 to 3.10. Operations ↓
other than these will be returned with the answer:↲
↲
╞ ╞ ╞ result = 3 : unintelligible↲
↲
↲
┆a1┆3.1╞ Operation Modes┆e1┆↲
↲
Some magnetic tape stations allow several recording modes, tape speeds ↓
etc. These characteristics are controlled through the 12-bit pattern ┆a1┆mode┆e1┆ ↓
which must be given as a parameter with all input and output operations:↲
↲
╞ mode ::=╞ block gap length < 9↲
╞ ╞ ╞ + speed ╞ < 7↲
╞ ╞ ╞ + trail ╞ < 4↲
╞ ╞ ╞ + density╞ < 2↲
↲
block gap length:╞ ┆84┆only relevant for RC8343 and RC8344. Block gap length ↓
┆19┆┆93┆┄┄may be redefined at any time, independent of the ↓
┆19┆┆93┆┄┄position of the tape.↲
↲
╞ ╞ ╞ ╞ ╞ 0 standard block gap↲
╞ ╞ ╞ ╞ ╞ 1 long block gap↲
↲
speed:╞ ╞ ╞ ┆84┆only relevant for RC8343 and RC8344. Speed may be re┄↓
┆19┆┆93┆┄┄de┄fined at any time, independent of the position of ↓
┆19┆┆93┆┄┄the tape.↲
↲
╞ ╞ ╞ ╞ ┆84┆The stations will nor┄mally be strapped for fixed ↓
┆19┆┆93┆┄┄speed, with the speed definitions as follows:↲
↲
╞ ╞ ╞ ╞ ╞ RC3715╞ RC8343/low╞ RC8343/high╞ RC8344↲
╞ ╞ ╞ ╞ 0 ╞ 45 ips╞ 25 ips╞ ╞ 12.5 ips╞ ╞ 25 ips↲
╞ ╞ ╞ ╞ 1 ╞ 45 ips╞ 100 ips╞ ╞ 50 ips╞ ╞ 75 ips↲
↲
┆8c┆┆83┆┆bc┆↓
┆0e┆↓
╞ ╞ ╞ ╞ ┆84┆If they are strapped for adaptive velocity control ↓
┆19┆┆93┆┄┄(AVC), the speed definitions are:↲
↲
╞ ╞ ╞ ╞ ╞ RC3715╞ RC8343/low╞ RC8343/high╞ RC8344↲
╞ ╞ ╞ ╞ 0 ╞ 45 ips╞ AVC╞ ╞ AVC╞ ╞ AVC↲
╞ ╞ ╞ ╞ 1 ╞ 45 ips╞ 100 ips╞ ╞ 50 ips╞ ╞ 75 ips↲
┆0f┆↓
↲
trail:╞ ╞ ╞ only relevant for output operations↲
↲
╞ ╞ ╞ ╞ ┆84┆specifies that the last n (0 <= n <= 7) characters ↓
┆19┆┆93┆┄┄from the storage area are ┆a1┆not┆e1┆ to be output.↲
↲
density:╞ ╞ ╞ ┆84┆Specifies both recording method and density:↲
↲
╞ ╞ ╞ ╞ ╞ 0╞ - HIGH↲
╞ ╞ ╞ ╞ ╞ 1╞ - LOW↲
↲
╞ ╞ ╞ ╞ ┆84┆The actual recording method and density depends upon ↓
┆19┆┆93┆┄┄the type of the tape devices:↲
↲
╞ ╞ ╞ ╞ ╞ ╞ RC3715╞ ╞ RC8343╞ ╞ RC8344↲
╞ ╞ ╞ ╞ HIGH ╞ PE,1600 cpi╞ PE,3200 cpi╞ GCR,6250 cpi↲
╞ ╞ ╞ ╞ LOW ╞ NRZ,800 cpi╞ PE,1600 cpi╞ PE, 1600 cpi↲
↲
╞ ╞ ╞ ╞ PE╞ - Phase Encoding↲
╞ ╞ ╞ ╞ NRZ1╞ - Non Return to Zero Mark↲
╞ ╞ ╞ ╞ GCR - Group Coded Recording↲
↲
The density of a tape is defined at load point: Hardware will auto┄ma┄ti┄↓
cal┄ly initialize the tape area surrounding the BOT-marker when a write, ↓
write file mark, erase, or data security erase operation is executed, ↓
starting from load point. The density thus defined can not be redefined, ↓
except at load point as described.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆3.2╞ Sense┆e1┆↲
↲
The operation has the following format:↲
↲
╞ ╞ message:╞ 0<12 + 0↲
↲
┆84┆┆84┆The device is sensed. The answer contains status, position and de┄tailed ↓
status. Both 'hw transferred' and 'chars transferred' will equal 0.↲
↲
↲
┆0e┆↓
┆a1┆3.3╞ Input┆e1┆↲
↲
The operation has the following format:↲
↲
╞ ╞ message:╞ 3<12 + mode↲
┆84┆╞ ╞ ╞ ╞ first storage address↲
╞ ╞ ╞ ╞ last storage address↲
↲
┆84┆The tape moves forwards and the first datablock met will be trans┄fer┄red ↓
to the storage area specified by first and last storage address. The ↓
storage area must be within the sending process.↲
┆0f┆↓
↲
┆84┆Three 8-bit characters from the tape will be packed into each storage ↓
word in the sequence left-to right, i.e. the first character will be ↓
placed in the most significant 8 bits of the word. Unused character po┄si┄↓
tions in the last storage word will be filled with NULL-characters.↲
↲
┆84┆Input is terminated on one of the following conditions:↲
↲
╞ ╞ 1) when the data block on the tape is exhausted↲
╞ ╞ 2) when the storage area is full↲
╞ ╞ ┆84┆3) if a file mark is met before a data block↲
╞ ╞ 4) after hardware time-out (timer error), i.e. neither↲
╞ ╞ a data block, nor a file mark was met within a certain,↲
╞ ╞ hardware dependent time (corresponding to about 10 feet↲
╞ ╞ of tape movement)↲
╞ ╞ 5) if data overrun occurs during the transfer↲
↲
↲
┆8c┆┆83┆┆d4┆↓
┆a1┆3.4╞ Output┆e1┆↲
↲
The operation has the following format:↲
↲
╞ ╞ message:╞ 5<12 + mode↲
╞ ╞ ╞ ╞ first storage address↲
╞ ╞ ╞ ╞ last storage address↲
↲
The tape moves forwards and the storage area specified by first and last ↓
storage address and 'trail' in mode, is written as a data block on the ↓
tape. The storage area must be within the sending process.↲
↲
The number of characters to write in the block is computed as follows:↲
↲
╞ block length:= (last + 2 - first//2*2)//2*3 - trail↲
↲
The result must be within the range↲
↲
╞ 3 <= block length <= 65535↲
↲
If this is not satisfied, a dummy answer will be returned, with↲
↲
╞ result = 3: unintelligible↲
↲
Each storage word is written as three 8-bit characters on the tape in the ↓
sequence left-to-right, i.e. the first character written will be taken ↓
from the most significant 8 bits of the word.↲
↲
Output is terminated on one of the following conditions:↲
↲
╞ ╞ 1) the storage area specified has been output↲
╞ ╞ 2) if data overrun occurs during the transfer↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆3.5╞ Erase┆e1┆↲
↲
The operation has the following format:↲
↲
╞ ╞ message:╞ 6<12 + 0↲
↲
The tape moves forwards and 3 - 5 inches of the tape are erased.↲
↲
↲
┆0e┆↓
┆a1┆3.6╞ Move┆e1┆↲
↲
The operation has the following format:↲
↲
╞ ╞ message:╞ 8<12 + 0↲
╞ ╞ ╞ ╞ move operation↲
╞ ╞ ╞ ╞ file no.↲
╞ ╞ ╞ ╞ block no.↲
┆0f┆↓
↲
The values of 'file no' and 'block no' are only relevant if 'move ope┄ra┄↓
tion' = 6, see below.↲
↲
The values allowed for 'move operation' are:↲
↲
╞ move operation:╞ 0 upspace file↲
╞ ╞ ╞ ╞ ╞ 1 upspace block↲
╞ ╞ ╞ ╞ ╞ 2 backspace file↲
╞ ╞ ╞ ╞ ╞ 3 backspace block↲
╞ ╞ ╞ ╞ ╞ 4 rewind tape↲
╞ ╞ ╞ ╞ ╞ 5 unload tape↲
╞ ╞ ╞ ╞ ╞ 6 position tape↲
↲
Other values of 'move operation': treated as 'sense'.↲
↲
Move operation 5:↲
↲
╞ ┆84┆RC3715 will rewind the tape and then switch the station to off-line.↲
↲
┆8c┆┆83┆┆bc┆↓
╞ ┆84┆RC8343 and RC8344 will switch the station to off-line and then rewind ↓
┆19┆┆84┆┄┄and unload the tape.↲
↲
┆84┆Move operation 6:↲
↲
╞ ┆84┆If 'file no' = 'block no' = 0, the operation works as move operation ↓
┆19┆┆84┆┄┄4: 'rewind tape'. If either of these is nega┄tive, the operation is ↓
┆19┆┆84┆┄┄treated as a sense operation. Otherwise, the tape will be positioned ↓
┆19┆┆84┆┄┄as specified by file and block num┄ber, see section 4. If the block ↓
┆19┆┆84┆┄┄spe┄ci┄fied does not exist, the tape will be positioned at the start of ↓
┆19┆┆84┆┄┄the next file. The operation is exe┄cu┄ted as a sequence of simple ↓
┆19┆┆84┆┄┄upspace/backspace block operations.↲
↲
↲
┆0e┆↓
┆a1┆3.7╞ Output File Mark┆e1┆↲
↲
The operation has the following format:↲
↲
╞ message:╞ 10<12 + 0↲
↲
Two file marks are written (forward direction) and the tape is posi┄tio┄ned ↓
after the first file mark.↲
┆0f┆↓
↲
↲
┆a1┆3.8╞ Extended Sense┆e1┆↲
↲
The operation has the following format:↲
↲
╞ message:╞ 11<12 + 0↲
╞ ╞ ╞ first storage address↲
╞ ╞ ╞ last storage address↲
↲
For RC3715 and RC8343 a 'sense' operation is executed in which case the ↓
sense data are returned in the answer. The data format is specified in ↓
Appendix C.↲
↲
For RC8344 a 'read (extended) sense' operation is executed. The ex┄ten┄ded ↓
sense data will be transferred to the storage area specified by first and ↓
┆8c┆┆83┆┆c8┆↓
last storage address. The storage area must be within the sending pro┄↓
cess. The data transfer rate will correspond to a low speed, low density ↓
transfer. If the storage can not hold the data (27 cha┄rac┄ters) 'block ↓
length error' will be reported. The data format is specified in Appendix ↓
D.↲
↲
┆0e┆↓
┆a1┆3.9 Set Mode┆e1┆↲
↲
The operation has the following format:↲
↲
╞ ╞ message:╞ 14<12 + mode↲
┆0f┆↓
↲
The device is sensed and the ans┄wer contains status, position and de┄↓
tailed status. Both 'hw trans┄fer┄red' and 'chars transferred' will equal ↓
0. Further the 'mode error' bit in the status word is set, if the speci┄↓
fied recording method and density does not correspond with the actual ↓
values.↲
↲
↲
┆a1┆3.10 Data Security Erase┆e1┆↲
↲
The operation has the following format:↲
↲
╞ message: 18<12 + 0↲
↲
The tape will be erased from the present position until approxima┄te┄ly 10 ↓
feet after the end-of-tape marker. The operation is executed as a sequen┄↓
ce of simple erase operations.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆4.╞ ANSWER FORMAT┆e1┆↲
↲
↲
All answers have the following format:↲
↲
╞ answer + 0: status word↲
+ 2: halfwords transferred↲
+ 4: characters transferred↲
+ 6: file number↲
+ 8: block number↲
+10: detailed status 0 (byte 0-2)↲
+12: detailed status 1 (byte 3-5)↲
+14: detailed status 2 (byte 6-7)↲
↲
┆a1┆status word┆e1┆↲
↲
A bit-pattern used for reporting errors as well as reporting certain ↓
conditions in the station state. A detailed ex┄pla┄na┄tion of the meaning ↓
and use of each status bit is given in Appendix B. A survey is given ↓
here:↲
↲
↲
╞ ╞ Bit no. Brief explanation↲
↲
╞ ╞ ╞ 0╞ ┆84┆Intervention↲
╞ ╞ ╞ 1╞ Parity Error↲
╞ ╞ ╞ 2╞ Time Out↲
╞ ╞ ╞ 3╞ Data Overrun↲
╞ ╞ ╞ 4╞ Block Length Error↲
╞ ╞ ╞ 5╞ EOT (End-of-Tape Marker) sensed↲
╞ ╞ ╞ 6╞ BOT (Begin-of-Tape Marker) sensed↲
╞ ╞ ╞ 7╞ File Mark sensed↲
╞ ╞ ╞ 8╞ Writing Enabled↲
╞ ╞ ╞ 9╞ Mode Error↲
↲
↲
┆84┆┆a1┆Halfwords transferred┆e1┆ (hw transferred) and ┆a1┆Characters transferred┆e1┆ (chars ↓
transferred) are used to report the amount of data actually transferred ↓
┆8c┆┆83┆┆c8┆↓
in operations involving data transfers to or from a data storage area in ↓
RC8000. Chars transferred is the controller's count of characters ↓
actually written on or read from the tape. Hw trans┄fer┄red is a calculated ↓
value:↲
╞ ╞ hw transferred:= (chars transferred + 2) // 3 * 2↲
↲
┆84┆Both values will equal zero after operations which do not involve such ↓
data transfers, i.e. if the operation definition does not require a data ↓
storage area to be stated.↲
↲
┆a1┆File and Block Number┆e1┆↲
↲
All answers from magnetic tape stations contain a file and block number ↓
defining the position of the tape after the operation.↲
↲
These simple file and block numbers are supplied by the IDA controller ↓
and based solely on keeping track of operations performed and status bits ↓
sensed. There is no check against file and block numbers in labels and ↓
data blocks.↲
↲
The IDA controller internally uses one more number, 'old block number', ↓
to keep track of the block numbers. Both the file number and the two ↓
block numbers are initialized to 0 when load point (the BOT-marker on ↓
the tape) is sensed. When the on/off-line status of the tape station ↓
changes, this will result in rewinding of the tape, resulting in initia┄↓
lizing the file number and block numbers to 0.↲
↲
When a file mark is output or when a file mark is sensed during a for┄ward ↓
move or read operation, the file number is increased by one, 'old block ↓
number' is set to 'block number' and 'block number' is set to zero.↲
↲
When a file mark is sensed after a backward opera┄tion, the file number is ↓
decreased by one, 'block number' is set to 'old block number' and 'old ↓
block number' is set to -1. If now 'block number' = -1, a backspace file ↓
operation is performed, followed with upspace file and one backspace ↓
file operation. Now 'block number' will be defined.↲
↲
┆8c┆┆83┆┆bc┆↓
The block number is increased by one when a block is input, output, or ↓
upspaced. Partial blocks and other blocks with errors count as normal ↓
blocks. The block number is decreased by one when a block is backspaced.↲
↲
┆a1┆Detailed Status┆e1┆ are 8 bytes of additional status information as defined ↓
in Appendix C. This information is not available from RC3715, in which ↓
case all 8 bytes (three words) will equal zero. This status is only ↓
available after the operations sense and set mode.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆A.╞ REFERENCES↲
↲
↲
(1)╞ RCSL No: 991 09776↲
╞ RC8000/IDA801 Tape and Disc Controller↲
╞ Maintenance Manual↲
↲
(2)╞ RCSL No: 42-i1362↲
╞ RC3715 Magnetic Tape Unit↲
╞ Datasheet↲
↲
(3)╞ Control Data Corporation SPEC 49791700↲
╞ Streaming Tape Unit (STU) Model 92182↲
↲
(4)╞ Control Data Corporation SPEC 49793200↲
╞ Streaming Tape Unit (STU) Model 92185↲
↲
(5)╞ RCSL No: 31-D686↲
╞ RC8000 MONITOR↲
╞ Part 1, System Design↲
↲
(6)╞ RCSL No: 31-D451↲
╞ Remoter Process↲
╞ External Process Description↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆B.╞ STATUS WORD↲
↲
↲
The status word in an answer (see 4) is a bit pattern used to re┄port ↓
errors as well as to report certain conditions in the station state as ↓
described below. Only the 10 most significant bits (bit 0-9) in the word ↓
are used. The remaining bits will have the value zero.↲
↲
┆a1┆bit 0╞ Intervention↲
↲
┆84┆Indicates the device went off-line ┆a1┆during┆e1┆ the operation. If the device ↓
was off-line before the operation, this would be indicated as stated in ↓
section 2: the answer would be returned with result = 5 (receiver does ↓
not exist).↲
↲
┆a1┆bit 1╞ Parity Error↲
↲
Indicates an unrecoverable error in the data on the tape or some sort of ↓
hardware malfunction. On RC8343 and RC8344, the 'detailed status' (see ↓
Appendix C) obtained by executing the operation 'sense' (see 3.2) give ↓
further information on the nature of the error. On RC8344, the 'extended ↓
status information' (see Appendix D) obtained by exe┄cuting the operation ↓
'extended sense' (see 3.9) will give a very precise description of the ↓
error.↲
↲
However, parity error can also indicates "soft" errors:↲
↲
After 'input' (3.3):╞ ┆84┆Neither a data block, nor a file mark, was found ↓
┆19┆┆98┆┄┄within a certain time (corresponding to about 10 ↓
┆19┆┆98┆┄┄feet of tape movement at the tape speed ↓
┆19┆┆98┆┄┄selected).↲
↲
┆0e┆↓
┆a1┆bit 2╞ Time Out↲
↲
┆84┆The operation was timed out by software in IDA: This indicates an severe ↓
error, i.e. hard┄ware malfunction.↲
┆0f┆↓
↲
┆8c┆┆83┆┆bc┆↓
In this case the position of the tape is not well defined, and the t┄ape ↓
driver ┄therefore rewind the tape in order to reinitialize the file and ↓
block counters (see sect. 4)↲
↲
┆a1┆bit 3╞ Data Overrun↲
↲
The data channel between primary storage and the tape station was over┄↓
loaded and could therefore not transfer the data as fast as they were ↓
delivered from or required by the tape station.↲
↲
┆a1┆bit 4╞ Block Length Error↲
↲
This error indicates the data block on the tape was larger than the sto┄↓
rage area specified in the operation. It can only occur after an 'input' ↓
ope┄ration (3.3).↲
↲
┆a1┆bit 5╞ EOT (End-of-Tape marker) Sensed↲
↲
This bit is set when the EOT-marker on the tape is passed during an ope┄↓
ration in the forward direction. It will be latched until the EOT-marker ↓
is again sensed during an operation in the reverse direction. The EOT-↓
marker is placed approximately 25 feet from the physical end of the tape. ↓
The last 15 feet of the tape should not be used.↲
↲
┆a1┆bit 6╞ BOT (Begin-of-Tape marker) Sensed↲
↲
Indicates that the tape is positioned at the BOT-marker on the tape or, ↓
with an equivalent expression: it is positioned at 'load point'.↲
↲
┆0e┆↓
┆a1┆bit 7╞ File Mark Sensed↲
↲
Indicates that a file mark (also called a tape mark) was read on the ↓
tape. May occur after 'input' and 'move' operations. Will always occur ↓
after 'output file mark' (because of the automatic read-after-write veri┄↓
fication).↲
┆0f┆↓
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆bit 8╞ Writing Enabled↲
↲
Indicates that the tape is mounted with a write-enable ring, so that ↓
write operations are possible.↲
↲
If the write-enable ring is not present, the operations 'output', ↓
'output file mark', 'erase', and 'data security erase' will result in no ↓
move of the tape and nothing will be written (hw transferred = chars ↓
transferred = 0).↲
↲
┆a1┆bit 9╞ Mode Error↲
↲
Indicates that either↲
╞ - ┆84┆'density' in the operation mode (see 3.1) did not cor┄respond to the ↓
┆19┆┆86┆┄┄density of the tape,↲
or:╞ ┆84┆this particular value of den┄sity is not available on the ↓
┆19┆┆86┆┄┄station,↲
or:╞ ┆84┆the station is strapped for pushbutton selection of density and the ↓
┆19┆┆86┆┄┄density in the operation did not correspond to the density pre┄sent┄↓
┆19┆┆86┆┄┄ly selected.↲
↲
Nothing will be written/read and (hw transferred = chars transferred = ↓
0).↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆C.╞ DETAILED STATUS INFORMATION↲
↲
↲
The following status bytes (see ref. 3, ref. 4) are returned in the ↓
answer:↲
↲
↲
╱04002d4e0c0006000000000201493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
╱04002d4e0c0006000000000301483140000000000000000000000000000000000000000000000000050a0f12191e23282d32373c4146ffff04╱
↓
MSB┆05┆LSB ↲
_________________________________________________________________________↲
┆a1┆byte ! bit0 bit1 bit2 bit3 bit4 bit5 bit6 bit7 ↲
! command inter- drive equip- data unit unit↲
0 ! reject vention type ment check overrun check exception↲
┆a1┆ ! required check ↲
! write high thres-↲
1 ! reverse write edit file erase speed hold long gap↲
┆a1┆ ! mark select ↲
! file positi- high ↲
2 ! ready on-line rewind protect oning/ speed BOT EOT ↲
┆a1┆ ! ramp ↲
! file illegal dens. dev. positi- channel write gap ↲
3 ! mark command conflict resp. oning parity HW control↲
┆a1┆ ! detect check check* error check check ↲
! read noise pe id uncor- post- multi- no ↲
4 ! time- check check tectable amble drop track tie4 ↲
┆a1┆ ! out data error pointer ↲
! ↲
5 ! tie7 tie6 tie5 tie3 tie9 tie1 tie8 tie2 ↲
┆a1┆ ! ↲
! ↲
6 ! fault symptom code ↲
┆a1┆ ! ↲
! ↲
7 ! marginal device indication ↲
┆a1┆ ! ↲
╱04002d4e0c0006000000000301493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
╱04002d4e0c0006000000000201493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
↓
↲
* this bit will be zero in GCR mode.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆D.╞ EXTENDED STATUS INFORMATION↲
↲
The following bytes (see ref. 4) are returned in the operation 'extended ↓
sense':↲
↲
╱04002d4e0c0006000000000201493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
╱04002d4e0c0006000000000301493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
↓
MSB┆05┆LSB ↲
_________________________________________________________________________↲
┆a1┆byte ! bit0 bit1 bit2 bit3 bit4 bit5 bit6 bit7 ↲
! command inter- equip- data unit unit↲
0 ! reject vention 0 ment check 0 check exception↲
┆a1┆ ! required check ↲
! write high thres-↲
1 ! reverse write edit file erase speed hold long gap↲
┆a1┆ ! mark select select ↲
! file high ↲
2 ! ready on-line rewind protect 0 speed BOT EOT ↲
┆a1┆ ! ↲
! i/f write read read remote i/f ↲
3 ! command parity parity buffer density unit - - ↲
┆a1┆ ! reject error error overflow select check ↲
! illegal device file reset device device ↲
4 ! channel command - protect key - not off- ↲
┆a1┆ ! command check ready line ↲
! channel channel read write device device velocity device ↲
5 ! parity response HW HW response HW check interrupt↲
┆a1┆ ! error check check check check check ↲
! AGC read id ↲
6 ! fault - data fault - error recovery code ↲
┆a1┆ ! check ↲
! ↲
7 ! formatter command code ↲
┆a1┆ ! ↲
! GCR high adaptive file diagnos- start/ variable variable ↲
8 ! mode speed velocity mark tic stop long gap short gap↲
┆a1┆ ! mode detect mode mode mode mode ↲
! ↲
9 ! diagnostic fault code ↲
┆a1┆ ! ↲
! ↲
10 ! diagnostic fault sub-code ↲
┆a1┆ ! ↲
! ↲
11 ! write error symptom code ↲
┆a1┆ ! ↲
! write residual write 45 write ↲
12 ! transfer byte crc parity - aux crc - - ↲
! check count parity error parity ↲
┆a1┆ ! check check error ↲
! residual read read resync ECC 3 uncorrec- no excessive↲
13 ! check CRC aux CRC check check table track pointers↲
┆a1┆ ! check data pointer ↲
! noise postamble skew read write id ARA ARA id ↲
14 ! check error error time-out it check burst check ↲
┆a1┆ ! check check ↲
╱04002d4e0c0006000000000301493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
╱04002d4e0c0006000000000201493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
↓
↲
════════════════════════════════════════════════════════════════════════
↓
╱04002d4e0c0006000000000201493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
╱04002d4e0c0006000000000301493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
↓
MSB┆05┆LSB ↲
_________________________________________________________________________↲
┆a1┆byte ! bit0 bit1 bit2 bit3 bit4 bit5 bit6 bit7 ↲
! EC read read read end dual single tie4 ↲
15 ! HW buffer transfer data mark track track (P) ↲
! check parity check parity check correct correct ↲
┆a1┆ ! error error ↲
! ↲
16 ! tie7 tie6 tie5 tie3 tie9 tie1 tie8 tie2 ↲
┆a1┆ ! ↲
! ↲
17 ! read error symptom code ↲
┆a1┆ ! ↲
! ↲
18 ! reverse write DSE GCR LGAP s/s mode - - ↲
┆a1┆ ! ↲
! logical remote LWR LWR LWR ↲
19 ! diag- diag- i/f PE GCR - - - ↲
┆a1┆ ! nostic nostic ↲
! command inter- diag- equip- AGC reset reverse ↲
20 ! reject vention nostic ment check key in BOT - ↲
┆a1┆ ! required request check ↲
! ↲
21 ! drive command code ↲
┆a1┆ ! ↲
! ↲
22 ! marginal condition code ↲
┆a1┆ ! ↲
! ↲
23 ! fault/test completion code ↲
┆a1┆ ! ↲
! ↲
24 ! sub-fault/sub-test completion code ↲
┆a1┆ ! ↲
! ↲
25 ! RFU ↲
┆a1┆ ! ↲
! ↲
26 ! microcode revision level ↲
┆a1┆ ! ↲
╱04002d4e0c0006000000000301493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
╱04002d4e0c0006000000000201493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
↓
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆E.╞ STANDARDS┆e1┆↲
↲
↲
┆a1┆ECMA STANDARD↲
↲
The following standard covers both the unrecorded and the recorded tape. ↓
It defines and explains all the technical terms used in this manual.↲
↲
╞ STANDARD ECMA-62╞ (Janurary 1980)↲
╞ Data Interchange on 12.7 mm↲
╞ 9-track Magnetic Tape↲
╞ 32 ftpmm - NRZ1 - 32 cpmm ( 800 cpi)↲
╞ 126 ftpmm - PE - 63 cpmm (1600 cpi, Phase Encoding)↲
╞ 356 ftpmm - NRZ1 - 246 cpmm (6250 cpi, GCR - Group Coded Recording)↲
↲
It supersedes the standards ECMA-12 and ECMA-36.↲
↲
↲
┆a1┆ISO STANDARD↲
↲
The corresponding ISO standards are:↲
↲
ISO 1863, ISO 1864, ISO 3788 and ISO 5652.↲
↲
↲
┆a1┆ANSI STANDARD↲
↲
The corresponding ANSI standards are:↲
↲
╞ ANSI X3.22-1973 ( 800 cpi, NRZ)↲
╞ ANSI X3.39-1973 (1600 cpi, Phase Encoded)↲
╞ ANSI X3.40-1976 (6250 cpi, Group Coded Recording)↲
↲
↲
┆a1┆IBM STANDARD↲
↲
The IBM standards are compatible with the standards above.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆F.╞ MESSAGE/ANSWER FORMAT SURVEY┆e1┆↲
↲
↲
┆a1┆Operation┆e1┆╞ ╞ ╞ ┆a1┆Message┆e1┆╞ ╞ ╞ ╞ ┆a1┆Answer┆e1┆↲
↲
╱04002d4e0c0006000000000201493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
╱04002d4e0c0006000000000301493140000000000000000000000000000000000000000000000000050a0f14191e23282d32373c41464bff04╱
↓
Sense╞ ╞ ╞ ╞ 0<12╞ ╞ ╞ ╞ ╞ status↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ file number↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ block number↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ detailed status↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ -↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ -↲
↲
↲
Input╞ ╞ ╞ ╞ 3<12 + mode╞ ╞ ╞ status↲
╞ ╞ ╞ ╞ ╞ first storage address╞ number of halfwords↲
╞ ╞ ╞ ╞ ╞ last storage address╞ number of characters↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ file number↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ block number↲
↲
↲
Output╞ ╞ ╞ ╞ 5<12 + mode╞ ╞ ╞ status↲
╞ ╞ ╞ ╞ ╞ first storage address╞ number of halfwords↲
╞ ╞ ╞ ╞ ╞ last storage address╞ number of characters↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ file number↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ block number↲
↲
↲
Erase╞ ╞ ╞ ╞ 6<12╞ ╞ ╞ ╞ ╞ status↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ file number↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ block number↲
↲
↲
Move╞ ╞ ╞ ╞ 8<12╞ ╞ ╞ ╞ ╞ status↲
╞ ╞ ╞ ╞ ╞ operation╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ file number╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ block number╞ ╞ ╞ file number↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ block number↲
↲
↲
Output File Mark╞ ╞ 10<12╞ ╞ ╞ ╞ status↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ file number↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ block number↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆Operation┆e1┆╞ ╞ ╞ ┆a1┆Message┆e1┆╞ ╞ ╞ ╞ ┆a1┆Answer┆e1┆↲
↲
↲
Extended Sense╞ ╞ 11<12╞ ╞ ╞ ╞ status↲
╞ ╞ ╞ ╞ ╞ first storage address╞ number of halfwords↲
╞ ╞ ╞ ╞ ╞ last storage address╞ number of characters↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ file number↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ block number↲
↲
↲
Set Mode╞ ╞ ╞ ╞ 14<12 + mode╞ ╞ ╞ status↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ file number↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ block number↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ detailed status↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ -↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ -↲
↲
↲
Data Security Erase╞ 18<12╞ ╞ ╞ ╞ status↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ file number↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ block number↲
↲
┆1a┆┆1a┆ p sho