|
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: 48000 (0xbb80)
Types: RcTekst
Names: »99109775.WP«
└─⟦dedaa6eab⟧ Bits:30005866/disk1.imd Dokumenter i RcTekst format (RCSL 99-1-*)
└─⟦this⟧ »99109775.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. DISC MEDIA DESCRIPTION ........................................... 3↲
╞ 2.1 The Data Medium ............................................. 3↲
╞ 2.2 RC8000 Disc Administration .................................. 4↲
╞ 2.3 Error Recovery .............................................. 6↲
↲
3. GENERAL COMMUNICATION RULES ...................................... 8↲
╞ 3.1 Message Format .............................................. 8↲
╞ 3.1.1 Mode ................................................. 9↲
╞ 3.1.2 First and Last Storage Address ....................... 9↲
╞ 3.1.3 Segment Number ....................................... 9↲
╞ 3.2 Answer Format .............................................. 10↲
↲
4. OPERATIONS ...................................................... 12↲
╞ 4.1 SENSE ...................................................... 12↲
╞ 4.2 INPUT ...................................................... 13↲
╞ 4.3 OUTPUT ..................................................... 14↲
╞ 4.4 FORMAT KIT ................................................. 15↲
╞ 4.5 POSITION ................................................... 16↲
╞ 4.6 EXTRACT STATISTICS ......................................... 17↲
╞ 4.7 POWER UP SPINDEL ........................................... 19↲
╞ 4.8 READ SYSTEM FIRMWARE ....................................... 20↲
╞ 4.9 POWER DOWN SPINDEL ......................................... 21↲
╞ 4.10 WRITE SYSTEM FIRMWARE ..................................... 22↲
╞ 4.11 SECURITY ERASE ............................................ 23↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆06┆ii↲
↲
┆a1┆┆b0┆TABLE OF CONTENTS (continued)┆05┆PAGE↲
↲
┆a1┆┆b0┆APPENDIX↲
↲
A. REFERENCES ...................................................... 24↲
↲
B. DETAILED STATUS FORMAT .......................................... 25↲
╞ B.1 Answer Format .............................................. 25↲
╞ B.2 Status Description ......................................... 25↲
╞ B.2.1 Control Module Status ............................... 26↲
╞ B.2.2 System Intervention Code ............................ 27↲
╞ B.2.3 Manual Intervention Code ............................ 27↲
╞ B.2.4 Delay Code .......................................... 28↲
╞ B.2.5 Slave Device Status ................................. 28↲
╞ B.2.6 Current Seek Address (byte 3-0) ..................... 28↲
↲
C. FORMAT OF STATISTICS INFORMATION ................................ 29↲
↲
D. MESSAGE/ANSWER FORMAT SURVEY .................................... 31↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆┆b0┆┆06┆┆0b┆↲
↲
┆a1┆┆b0┆1. INTRODUCTION.┆e1┆↲
↲
┆84┆This manual is only valid for disc storage modules connected to ↓
┆19┆┆89┆┄┄the RC8000 through an Intelligent Device Adapter (IDA801 - ↓
┆19┆┆89┆┄┄RC834x storage modules).↲
↲
↲
┆a1┆┆b0┆1.1. Changes.┆e1┆↲
↲
┆84┆The following has been changed compared to disc storage modules ↓
┆19┆┆89┆┄┄RC82xx (see ref. 1).↲
↲
- The monitor kind of an RC834x disc process has been changed.↲
↲
- ┆84┆The CLEAN TRACK and INITIALIZE operations have been cancel┄↓
┆19┆┆8b┆┄┄led.↲
↲
- ┆84┆The SENSE and EXTRACT STATISTICS operations have been ↓
┆19┆┆8b┆┄┄changed.↲
↲
- Six new operations have been added:↲
┆84┆FORMAT KIT, POWER UP SPINDEL, POWER DOWN SPINDEL, READ SYSTEM ↓
┆19┆┆8b┆┄┄FW, WRITE SYSTEM FW and SECURITY ERASE.↲
↲
- ┆84┆The MODE specification of the operations has been changed:↲
┆84┆It is no longer possible to operate on the address part of a ↓
┆19┆┆8b┆┄┄sector.↲
┆84┆It is no longer possible to specify limited error-recovery.↲
Specification of READ AFTER WRITE is now possible.↲
↲
- The format of the answer has been changed.↲
↲
╞ - ┆84┆The disc now contains a description of the logical format of ↓
┆19┆┆8b┆┄┄the kit i.e. a description of the autoload part and a de-↓
┆19┆┆8b┆┄┄scription of each logical disc on the kit.↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ - ┆84┆It is now possible to create and remove physical and logical ↓
┆19┆┆8b┆┄┄disc processes at run time. When a logical disc has been ↓
┆19┆┆8b┆┄┄created on a (physical) disc, it is no longer possible to ↓
┆19┆┆8b┆┄┄communicate with the physical disc process.↲
↲
↲
┆b0┆┆a1┆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).↲
↲
CM: ┆84┆Control Module. A control module supporting the ↓
┆19┆┆97┆┄┄ISI standard operations.↲
↲
IDA: ┆84┆Intelligent Device Adapter. An adapter which ↓
┆19┆┆97┆┄┄interfaces one or more ISI disc interfaces ↓
┆19┆┆97┆┄┄(and Pertec interfaces for magnetic tape ↓
┆19┆┆97┆┄┄stations) to RC8000.↲
↲
Segment: ┆84┆Logical data block containing 512 RC8000 ↓
┆19┆┆97┆┄┄halfwords (768 8 bits bytes). One RC8000 segment ↓
┆19┆┆97┆┄┄is composed of three physical disc ┆b0┆sectors┆f0┆.↲
↲
Sector: ┆84┆Physical data block on the disc, containing 256 8 ↓
┆19┆┆97┆┄┄bits bytes.↲
┆84┆It is not possible to address and transfer one ↓
┆19┆┆97┆┄┄single sector to or from RC8000, but only in ↓
┆19┆┆97┆┄┄groups of three sectors (one RC8000 segment).↲
↲
Slave Device: A physical disc connected to an ISI interface.↲
↲
FSD: Fixed Storage Drive.↲
↲
RSD: Removable Storage Drive.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆2. DISC MEDIA DESCRIPTION.┆e1┆↲
↲
┆84┆The RC834x disc units are connected to RC8000 through an Intel┄↓
┆19┆┆89┆┄┄ligent Device Adapter (IDA801), to which the physical disc ↓
┆19┆┆89┆┄┄units are connected through an Intelligent Standard Interface ↓
┆19┆┆89┆┄┄(ISI).↲
┆84┆The following general description applies to all RC834x disc ↓
┆19┆┆89┆┄┄units unless explicitly stated.↲
↲
↲
┆a1┆┆b0┆2.1. The Data Medium.┆e1┆┆e2┆┆e1┆↲
↲
┆84┆The disc packs used on the disc storage modules consist of a ↓
┆19┆┆89┆┄┄number of coax-like discs rotating together.↲
↲
┆84┆Data is stored in ┆b0┆tracks┆f0┆ that are concentric circles on the ↓
┆19┆┆89┆┆81┆┄disc ┆b0┆surface┆f0┆. A ┆b0┆read/write head┆f0┆ is allocated to each surface on ↓
┆19┆┆89┆┆83┆┄the disc pack; these read/write heads are movable in radial ↓
┆19┆┆89┆┆83┆┄direction by means of a common head activator. Hence the radial ↓
┆19┆┆89┆┆83┆┄position of the heads defines a track on all surfaces, these ↓
┆19┆┆89┆┆83┆┄tracks are in common called a ┆b0┆cylinder┆f0┆. To select a certain ↓
┆19┆┆89┆┆84┆┄track it is necessary to select a read/write head corresponding ↓
┆19┆┆89┆┆84┆┄to a certain disc surface.↲
↲
┆84┆Each track is further divided into a number of pie-shaped sec┄↓
┆19┆┆89┆┄┄tions which are called ┆b0┆sector┆f0┆┆b0┆s┆f0┆. A sector is the smallest ↓
┆19┆┆89┆┆82┆┄addressable unit on the disc pack.↲
↲
┆84┆Each sector is (logically) composed of two parts: A ┆b0┆header part┆f0┆ ↓
┆19┆┆89┆┆81┆┄and a ┆b0┆data part┆f0┆.↲
↲
┆84┆The header contains address, error and Error Correction Code ↓
┆19┆┆89┆┄┄(ECC) information. The error information is used to skip a ↓
┆19┆┆89┆┄┄group of 24 bits containing a permanent error of at most 8 bits ↓
┆19┆┆89┆┄┄in the data part of the sector. The ECC information is only ↓
┆19┆┆89┆┄┄used for error detection in the header although the control ↓
┆19┆┆89┆┄┄module has the ability to correct the header; but this is not ↓
┆19┆┆89┆┄┄done due to the impact that a miscorrection would have on the ↓
┆19┆┆89┆┄┄RC8000 file.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆84┆The ┆b0┆data part┆f0┆ of the sector contains 256 8 bits bytes and an ↓
┆19┆┆89┆┆81┆┄ECC of 8 bytes. The ECC can be used to correct a single burst ↓
┆19┆┆89┆┆81┆┄error of 25 bits or less.↲
↲
↲
┆a1┆┆b0┆2.2. RC8000 Disc Administration.┆e1┆↲
↲
┆84┆The smallest addressable unit of data from RC8000 is called a ↓
┆19┆┆89┆┄┄┆b0┆segment┆f0┆. A segment is a data block of 768 8 bits bytes (three ↓
┆19┆┆89┆┆81┆┄physical sectors).↲
↲
┆84┆Disc operations are initiated by sending messages to the RC8000 ↓
┆19┆┆89┆┄┄external process representing the disc.↲
┆84┆To each disc storage module corresponds one external process ↓
┆19┆┆89┆┄┄(representing the physical disc) which controls the entire disc ↓
┆19┆┆89┆┄┄module. To each physical disc may exist none, one or more so┄↓
┆19┆┆89┆┄┄cal┄led ┆b0┆logical discs┆f0┆ which is an external process describing a ↓
┆19┆┆89┆┆81┆┄part of the disc storage module. From the view of an internal ↓
┆19┆┆89┆┆81┆┄process, each physical or logical disc represents an indepen┄↓
┆19┆┆89┆┆81┆┄dent device identified by a unique device number.↲
┆84┆Segment numbers supplied in messages sent to a physical disc ↓
┆19┆┆89┆┄┄driver specify segments relative to the first segment on the ↓
┆19┆┆89┆┄┄disc storage module, whereas segment numbers supplied in mes┄↓
┆19┆┆89┆┄┄sages sent to a logical disc specify segments relative to the ↓
┆19┆┆89┆┄┄start of the logical disc.↲
↲
┆84┆A logical disc may be accessed via messages sent to the exter┄↓
┆19┆┆89┆┄┄nal process representing the logical disc or if the process ↓
┆19┆┆89┆┄┄represents a logical backing storage it may be accessed through ↓
┆19┆┆89┆┄┄┆b0┆area┆f0┆ processes. An area process is a process representing a ↓
┆19┆┆89┆┆81┆┄file on the logical disc. To maintain the logical backing ↓
┆19┆┆89┆┆81┆┄storage system each logical disc has a ┆b0┆catalog┆f0┆ and a ┆b0┆chaintable┆f0┆ ↓
┆19┆┆89┆┆83┆┄stored on the logical disc.↲
┆84┆The catalog contains information of the files stored on the ↓
┆19┆┆89┆┄┄logical disc whereas the chaintable contains information of ↓
┆19┆┆89┆┄┄which segments (┆b0┆slices┆f0┆) a given file occupies. Segments on the ↓
┆19┆┆89┆┆81┆┄logical disc is allocated in groups (called slices) to an area ↓
┆19┆┆89┆┆81┆┄(file).↲
════════════════════════════════════════════════════════════════════════
↓
┆84┆The number of segments in a slice is defined for each logical ↓
┆19┆┆89┆┄┄disc.↲
┆84┆Segment numbers supplied to an area process is relative to the ↓
┆19┆┆89┆┄┄start of the area. Although the segments of an area is allo┄↓
┆19┆┆89┆┄┄cated sequentially from the internal process' point of view, it ↓
┆19┆┆89┆┄┄may be allocated in a non-consecutively way on the logical ↓
┆19┆┆89┆┄┄disc, where the chaintable gives the sequentially connection ↓
┆19┆┆89┆┄┄between the segments (slices). For physical and logical discs ↓
┆19┆┆89┆┄┄the segments are allocated sequentially in both a physical and ↓
┆19┆┆89┆┄┄logical sense.↲
↲
┆84┆Disc processes (physical and logical) are created at runtime. ↓
┆19┆┆89┆┄┄When a physical disc process has been created, it can be di┄↓
┆19┆┆89┆┄┄vided into a number of logical discs each represented by a ↓
┆19┆┆89┆┄┄logical disc process.↲
╞ ┆84┆Creation and removal of disc-processes are carried out by ↓
┆19┆┆89┆┄┄sending messages to the IDA-main process supervising the IDA-↓
┆19┆┆89┆┄┄controller on which the disc-units are connected (see ref. ↓
┆19┆┆89┆┄┄(3)).↲
╞ ┆84┆It should be noted that it is impossible to communicate with a ↓
┆19┆┆89┆┄┄physical disc when the first logical disc process has been ↓
┆19┆┆89┆┄┄created. The disc may then only be accessed through logical ↓
┆19┆┆89┆┄┄discs or areas.↲
╞ ┆84┆All physical discs which are divided into logical discs will ↓
┆19┆┆89┆┄┄contain a logical disc (an autoload disc) which describes the ↓
┆19┆┆89┆┄┄first part of the disc. This autoload part of the disc ↓
┆19┆┆89┆┄┄contains:↲
↲
┆e1┆╞ - a description-part and↲
╞ - a system software part.↲
↲
╞ ┆84┆The description part contains information about the system-↓
┆19┆┆89┆┄┄software location and a description of all logical discs on the ↓
┆19┆┆89┆┄┄disc-kit. The logical discs are described by their location, ↓
┆19┆┆89┆┄┄size and type. The type specifies whether the logical disc con┄↓
┆19┆┆89┆┄┄tains a catalog or not. The description of the logical disc may ↓
┆19┆┆89┆┄┄also contain an RC8000 device number which specifies the exter┄↓
┆19┆┆89┆┄┄nal process that should be used when the logical disc is crea┄↓
┆19┆┆89┆┄┄ted (linked) (see ref. 3).↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ ┆84┆The system software part is used when the disc is used as an ↓
┆19┆┆89┆┄┄autoload disc. It contains:↲
↲
╞ - disc-space for RC8000 coredump,↲
╞ - IDA801 firmware,↲
- RC8000 bootloader,↲
- RC8000 monitor and↲
╞ - software for device-controllers.↲
↲
╞ ┆84┆This disc-description and the posibility of creation and ↓
┆19┆┆89┆┄┄removal of (physical and logical) disc processes at runtime ↓
┆19┆┆89┆┄┄implies that a disckit now is independent of a pre-defined ↓
┆19┆┆89┆┄┄monitor (see ref. (3)).↲
↲
↲
┆b0┆┆a1┆2.3. Error Recovery.┆e1┆↲
↲
┆84┆The Intelligent Standard Interface supports different kinds of ↓
┆19┆┆89┆┄┄error recovery including Error Correction Codes (ECC), repeated ↓
┆19┆┆89┆┄┄reading with early and late strobe and variable offset.↲
┆84┆In the following a description of the different errors and ↓
┆19┆┆89┆┄┄error corrections are noted.↲
↲
┆b0┆ Seek Error:┆f0┆↲
┆84┆This error indicates that it is impossible to verify a certain ↓
┆19┆┆89┆┄┄track. When this occurs the disc will always move to track zero ↓
┆19┆┆89┆┄┄and repeat the seek operation once more. If the recovery failed ↓
┆19┆┆89┆┄┄the operation is terminated and a seek error status is set.↲
↲
┆b0┆ Header (address information block) Error:┆f0┆↲
┆84┆If the address information part of a sector contains an error ↓
┆19┆┆89┆┄┄(which may be detected through an ECC mismatch) no ECC error ↓
┆19┆┆89┆┄┄correction is applied, but a re-reading of the header will be ↓
┆19┆┆89┆┄┄performed once. If this re-reading of the header is unsuccess-↓
┆19┆┆89┆┄┄full and it is impossible to verify that the slave device is on ↓
┆19┆┆89┆┄┄the proper cylinder, a return to track zero and a seek to the ↓
┆19┆┆89┆┄┄specified track is performed to ensure that the correct cylin┄↓
┆19┆┆89┆┄┄der is selected, before an error status is delivered.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆ Data Error:┆f0┆↲
╞ ┆84┆If an error is detected during a reading of the datapart 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.↲
╞ ┆84┆Then three attempts are made at each of the strobe offsets ↓
┆19┆┆89┆┄┄(early and late) while holding the carriage offset at nominal. ↓
┆19┆┆89┆┄┄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.↲
╞ ┆84┆A single burst ECC procedure is employed in the final attempt.↲
↲
┆b0┆ Intervention:┆f0┆↲
┆84┆This indicates that manual intervention has occurred on a slave ↓
┆19┆┆89┆┄┄device. If it concerns a removable storage device, the disc ↓
┆19┆┆89┆┄┄pack may have been changed.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆3. GENERAL COMMUNICATION RULES.┆e1┆┆f0┆↲
↲
The monitor kind of a (physical and logical) IDA disc is 6.↲
↲
┆84┆A logical disc cannot be reserved if the corresponding physical ↓
┆19┆┆89┆┄┄disc is reserved by another internal process, and a physical ↓
┆19┆┆89┆┄┄disc cannot be reserved if any of the logical discs situated on ↓
┆19┆┆89┆┄┄the physical disc are reserved by another internal process.↲
↲
╞ ┆84┆Remember that it is impossible to communicate with a physical ↓
┆19┆┆89┆┄┄disc if any logical disc processes have been created for that ↓
┆19┆┆89┆┄┄physical disc.↲
↲
┆84┆To use a logical disc, the corresponding physical disc need not ↓
┆19┆┆89┆┄┄have a name.↲
┆84┆A disc process representing a logical backing store is, during ↓
┆19┆┆89┆┄┄normal use, reserved by the anonymous process executing process ↓
┆19┆┆89┆┄┄functions.↲
↲
↲
┆a1┆┆b0┆3.1. Message Format.┆e1┆↲
↲
┆84┆The format of a message to a disc process depends on the ↓
┆19┆┆89┆┄┄operation. I/O messages may serve as an example:↲
↲
+ 0: operation<12 + mode↲
+ 2: first RC8000 storage address↲
+ 4: last RC8000 storage address↲
+ 6: segment number↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆3.1.1. Mode.┆e1┆↲
↲
↲
┆84┆The mode specifies a modification of the operation. The only ↓
┆19┆┆89┆┄┄allowed mode is:↲
↲
mode: read after write<0↲
↲
read after write: ┆84┆Only output operations. After the ↓
┆19┆┆a2┆┄┄specified block has been written or ↓
┆19┆┆a2┆┄┄the specified sectors have been ↓
┆19┆┆a2┆┄┄erased, it is read to check that it ↓
┆19┆┆a2┆┄┄contains no uncorrectable errors.↲
↲
↲
┆b0┆┆a1┆3.1.2. First and Last Storage Address.┆e1┆↲
↲
╞ ┆84┆If first or last storage addresses are odd they are decreased ↓
┆19┆┆89┆┄┄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.↲
↲
↲
┆b0┆┆a1┆3.1.3. Segment Number.┆e1┆↲
↲
┆84┆This is the address (number) of the (first) RC8000 segment ↓
┆19┆┆89┆┄┄which the operation concerns (relative to the begining of the ↓
┆19┆┆89┆┄┄physical or logical disc; first segment has number zero).↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆3.2. Answer Format.┆e1┆↲
↲
┆84┆When communicating with a (physical or logical) disc process, ↓
┆19┆┆89┆┄┄the following results are possible from the "wait answer" ↓
┆19┆┆89┆┄┄system call:↲
↲
Result 1: ┆84┆┆84┆Message accepted, answer contains further status ↓
┆19┆┆93┆┄┄information.↲
Result 2: ┆84┆┆84┆Message rejected because of violation of user/┄↓
┆19┆┆93┆┄┄reserver requirement.↲
Result 3: ┆84┆┆84┆Unintelligible message; illegal operation or mode.↲
Result 4: Malfunction, IDA controller troubles.↲
Result 5: ┆84┆┆84┆Receiver unknown, the specified disc process does not ↓
┆19┆┆93┆┄┄exist.↲
↲
┆84┆For every operation the meaning of result 2 and 3 will be ↓
┆19┆┆89┆┄┄specified.↲
↲
┆84┆If result 1 is returned the answer contains logical RC8000 ↓
┆19┆┆89┆┄┄status, RC8000/IDA communication status, control module (ISI) ↓
┆19┆┆89┆┄┄status and the status of the slave device (in case of a logical ↓
┆19┆┆89┆┄┄disc it concerns the physical disc on which the logical disc is ↓
┆19┆┆89┆┄┄situated).↲
↲
The answers have 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┆┆84┆system intervention code<16 + manual intervention ↓
┆19┆┆91┆┄┄code<8 + delay code<0↲
+12: ┆84┆┆84┆reserved<16 + slave device status<8 + flaw address, ↓
┆19┆┆91┆┄┄byte 3<0↲
+14: ┆84┆flaw address, byte 2<16 + flaw address, byte 1<8 ↓
┆19┆┆91┆┄┄+ flaw address, byte 0<0↲
↲
════════════════════════════════════════════════════════════════════════
↓
Status word:↲
The status word is bit encoded:↲
↲
bit 0: intervention↲
1: parity error or hard error↲
2: position error↲
5: end medium↲
11: disc error (always set when any errors).↲
All bits zero: operation completed.↲
↲
Number of Halfwords and Number of Characters Transfered:↲
╞ ┆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 has been modified (always a multiplum 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 of the answer ↓
┆19┆┆89┆┄┄is normally only of interest to test programs. For a detailed ↓
┆19┆┆89┆┄┄description see appendix B. This part of the answer is in the ↓
┆19┆┆89┆┄┄rest of this manual called Detailed Status.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆4. OPERATIONS.┆e1┆┆f0┆↲
↲
┆84┆The disc process (physical and logical) accepts the following ↓
┆19┆┆89┆┄┄messages:↲
↲
╞ ┆84┆SENSE, INPUT, OUTPUT, FORMAT KIT, POSITION, EXTRACT STATISTICS, ↓
┆19┆┆89┆┄┄POWER UP SPINDEL, READ SYSTEM FIRMWARE, POWER DOWN SPINDEL, ↓
┆19┆┆89┆┄┄WRITE SYSTEM FIRMWARE and SECURITY ERASE.↲
↲
╞ ┆84┆SENSE, FORMAT KIT, POSITION, POWER UP SPINDEL, POWER DOWN ↓
┆19┆┆89┆┄┄SPINDEL and SECURITY ERASE does not involve any data-transfer ↓
┆19┆┆89┆┄┄to or from RC8000.↲
↲
╞ ┆84┆FORMAT KIT, READ SYSTEM FIRMWARE and WRITE SYSTEM FIRMWARE are ↓
┆19┆┆89┆┄┄operations which concern the initialization of a disc kit. ↓
┆19┆┆89┆┄┄These operations and POWER UP and POWER DOWN SPINDEL will only ↓
┆19┆┆89┆┄┄be accepted by a physical disc driver (and only when there are ↓
┆19┆┆89┆┄┄no logical disc processes for that disc).↲
↲
↲
┆a1┆┆b0┆4.1. SENSE.┆e1┆↲
↲
Function:↲
↲
┆84┆The slave device is sensed. No input/output operation is init┄↓
┆19┆┆89┆┄┄iated but a seek operation is performed to the first track of ↓
┆19┆┆89┆┄┄the disc (track zero in case of a physical disc or the first ↓
┆19┆┆89┆┄┄track of the logical disc) to get a correct slave device sta┄↓
┆19┆┆89┆┄┄tus, i.e. SENSE acts like a POSITION to the first segment of ↓
┆19┆┆89┆┄┄the disc.↲
↲
The sending process must be user of the disc process.↲
↲
Message:↲
+ 0: 0<12 + 0↲
↲
════════════════════════════════════════════════════════════════════════
↓
Answer:↲
+ 0: status word↲
+ 2: 0↲
+ 4: 0↲
+ 6: i/o result↲
+ 8-+14: detailed status↲
↲
Errors: Result 2: Calling process is not user of disc process.↲
Disc process is reserved by another process.↲
Result 3: ┆84┆Message sent to a physical disc on which a ↓
┆19┆┆9b┆┄┄logical disc is linked.↲
↲
↲
┆a1┆┆a1┆┆b0┆4.2. INPUT.┆e1┆↲
↲
Function:↲
↲
┆84┆A number of consecutive segments of 256 words each are input to ↓
┆19┆┆89┆┄┄a storage area within the sending process. The first segment ↓
┆19┆┆89┆┄┄number wanted is given in the message.↲
┆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 storage address + 2 - first storage address)//512↲
↲
┆84┆If the input block thus specified exceeds the upper limit of ↓
┆19┆┆89┆┄┄the (physical or logical) disc, input is performed only of that ↓
┆19┆┆89┆┄┄part of the block that is within the disc. In any case the ↓
┆19┆┆89┆┄┄actual number of halfwords and characters transferred are given ↓
┆19┆┆89┆┄┄in the answer.↲
┆84┆The number of halfwords transferred is a multiple of 512. The ↓
┆19┆┆89┆┄┄number of characters is defined as three times the number of ↓
┆19┆┆89┆┄┄words transferred.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆84┆If the first segment is outside the limits of the (physical or ↓
┆19┆┆89┆┄┄logical) disc, input is not initiated, but the answer contains ↓
┆19┆┆89┆┄┄a status bit, end medium, and number of halfwords and charac-↓
┆19┆┆89┆┄┄ters transferred are zero.↲
↲
The sending process must be user of the disc process.↲
↲
Message:↲
+ 0: 3<12 + 0↲
+ 2: first storage address.↲
+ 4: last storage address.↲
+ 6: first segment number.↲
↲
┆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 user of disc process.↲
Disc process is reserved by another process.↲
Result 3: ┆84┆Message sent to a physical disc on which a ↓
┆19┆┆9b┆┄┄logical disc is linked.↲
↲
↲
┆b0┆┆a1┆4.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 disc, ↓
┆19┆┆89┆┄┄starting from the segment number given (the segment specified ↓
┆19┆┆89┆┄┄must be relative to the beginning of the (physical or logical) ↓
┆19┆┆89┆┄┄disc.↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ ┆84┆If the specified core area will exceed the upper limit of the ↓
┆19┆┆89┆┄┄(physical or logical) disc, the operation is initiated for that ↓
┆19┆┆89┆┄┄part of the core area which is within the disc.↲
┆84┆As for input only blocks of a multiple of 512 halfwords will be ↓
┆19┆┆89┆┄┄transferred.↲
The sending process must be reserver of the disc process.↲
↲
Message:↲
+ 0: 5<12 + mode↲
+ 2: first storage address.↲
+ 4: last storage address.↲
+ 6: first segment number.↲
↲
mode: See section 3.1.1.↲
┆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 disc ↓
┆19┆┆9b┆┄┄process.↲
Result 3: ┆84┆Illegal mode specification. Message sent to a ↓
┆19┆┆9b┆┄┄physical disc on which a logical disc is ↓
┆19┆┆9b┆┄┄linked.↲
↲
↲
┆a1┆┆b0┆4.4 FORMAT KIT.↲
↲
╞ Function:↲
↲
╞ ┆84┆The entire disc pack is formated and certified.↲
╞ ┆84┆Note that this operation requires approximately 8 hours for a ↓
┆19┆┆89┆┄┄RC8346 disc pack and 4 hours for a RC8345 disc pack.↲
╞ ┆84┆The answer will be returned when the operation is finished.↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ ┆84┆This operation will only be accepted by a physical disc (and no ↓
┆19┆┆89┆┄┄logical discs must be linked on it).↲
↲
╞ ┆84┆The sending process must be reserver of the disc process.↲
┆a1┆↲
╞ Message:↲
╞ + 0: 6<12 + 0↲
↲
╞ Answer:↲
╞ + 0: status↲
╞ + 2: 0↲
╞ + 4: 0↲
╞ + 6: i/o result↲
╞ + 8-+14: detailed status↲
↲
╞ Errors: Result 2: ┆84┆Sending process is not reserver of (physical) ↓
┆19┆┆9b┆┄┄disc.↲
╞ Result 3: ┆84┆Disc in not a physical disc.↲
╞ ╞ ╞ ┆84┆Logical disc linked to physical disc.↲
↲
↲
┆a1┆┆b0┆┆81┆4.5. POSITION.┆e1┆↲
↲
Function:↲
↲
┆84┆The read/write heads on the slave device are moved to the ↓
┆19┆┆89┆┄┄cylinder on which the segment specified in the message is ↓
┆19┆┆89┆┄┄located (if the disc is a logical disc, the specified segment ↓
┆19┆┆89┆┄┄must be relative to the beginning of the logical disc).↲
┆84┆If the segment is outside the limit of the disc, no operation ↓
┆19┆┆89┆┄┄is initiated, but the answer contains the END OF MEDIUM status ↓
┆19┆┆89┆┄┄bit.↲
The sending process must be user of the disc process.↲
↲
════════════════════════════════════════════════════════════════════════
↓
Message:↲
+ 0: 8<12 + 0↲
+ 2: irrelevant↲
+ 4: irrelevant↲
+ 6: segment number↲
↲
Answer:↲
+ 0: status word↲
+ 2: 0↲
+ 4: 0↲
+ 6: i/o result↲
+ 80+14: detailed status↲
↲
Errors: Result 2: Sending process is not user of disc process.↲
Disc process is reserved by another process.↲
Result 3: ┆84┆Message sent to a physical disc on which a ↓
┆19┆┆9b┆┄┄logical disc is linked.↲
↲
↲
┆a1┆┆b0┆4.6. EXTRACT STATISTICS.┆e1┆↲
↲
Function:↲
↲
┆84┆On each physical disc a table of statistical information re┄↓
┆19┆┆89┆┄┄flec┄ting the use and condition of the slave device is main┄↓
┆19┆┆89┆┄┄tained. If the operation is sent to a logical disc driver, the ↓
┆19┆┆89┆┄┄information concern the physical disc on which the logical disc ↓
┆19┆┆89┆┄┄is situat┄ed.↲
┆84┆The information may be transferred to a core area within an ↓
┆19┆┆89┆┄┄inter┄nal process by sending this message.↲
↲
╞ ┆84┆If the storage area is too small, only the amount of data which ↓
┆19┆┆89┆┄┄there is room for, is transferred.↲
╞ ┆84┆Number of characters in the answer, specifies the amount of ↓
┆19┆┆89┆┄┄valid statistical information.↲
↲
╞ ┆84┆The supplied information contains permanent statistics as the ↓
┆19┆┆89┆┄┄table is kept on the disc. The table on the disc is updated ↓
┆19┆┆89┆┄┄when the disc receives a 'POWER DOWN SPINDEL' operation.↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ ┆84┆If the disc is physical disc unit number zero, the supplied ↓
┆19┆┆89┆┄┄disc information is appended with information about the con┄trol ↓
┆19┆┆89┆┄┄module on which the disc unit is connected.↲
↲
The sending process must be user of the disc process.↲
↲
┆84┆Appendix C contains a detailed description of the supplied ↓
┆19┆┆89┆┄┄statistical information.↲
↲
Message:↲
+ 0: 9<12 + mode↲
+ 2: first storage address↲
+ 4: last storage address↲
↲
Mode: clear statistics <0↲
┆84┆ ┆84┆if one the table of statistics is cleared when ↓
┆19┆┆97┆┄┄the information has been transferred to RC8000.↲
↲
Answer:↲
+ 0: status↲
+ 2: number of halfwords transferred.↲
+ 4: number of characters transferred.↲
+ 6: i/o result↲
+ 8-+14: detailed status↲
↲
Errors: Result 2: Sending process is not user of disc process.↲
Disc process is reserved by another process.↲
Result 3: Illegal mode specification.↲
╞ ╞ ╞ ┆84┆Message sent to a physical disc on which a ↓
┆19┆┆9b┆┄┄logical disc is linked.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆a1┆┆b0┆4.7. POWER UP SPINDEL.┆e1┆↲
↲
Function:↲
↲
┆84┆The IDA801 controller will power up the spindel on the slave ↓
┆19┆┆89┆┄┄device.↲
┆84┆The slave device will be ready within aproximately 30 seconds ↓
┆19┆┆89┆┄┄for an FSD and within aproximately 70 seconds for an RSD slave ↓
┆19┆┆89┆┄┄device. The answer will be returned when the operation is ↓
┆19┆┆89┆┄┄finished.↲
↲
╞ ┆84┆This operation will only be accepted by a physical disc (and no ↓
┆19┆┆89┆┄┄logical discs must be linked on it).↲
↲
The sending process must be reserver of the disc process.↲
↲
Message:↲
+ 0: 10<12 + 0↲
↲
Answer:↲
+ 0: status↲
+ 2: 0↲
+ 4: 0↲
+ 6: i/o result↲
+ 8-+14: detailed status↲
↲
Errors: Result 2: ┆84┆Sending process is not reserver of disc ↓
┆19┆┆9b┆┄┄process.↲
Result 3: ┆84┆Message sent to a logical disc or sent to a ↓
┆19┆┆9b┆┄┄physical disc on which logical discs are ↓
┆19┆┆9b┆┄┄linked.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆4.8╞ READ SYSTEM FIRMWARE.↲
↲
╞ Function:↲
↲
╞ ┆84┆The firmware (the COS-program) or the test-program (the level ↓
┆19┆┆89┆┄┄II diagnostic test program) for the control module on which the ↓
┆19┆┆89┆┄┄disc is connected is transferred to the specified core area.↲
↲
╞ ┆84┆This operation will only be accepted by a physical disc (and no ↓
┆19┆┆89┆┄┄logical discs must be linked on it).↲
┆81┆↲
╞ ┆84┆The sending process must be reserver of the disc process.↲
↲
╞ Message:↲
╞ + 0: 11<12 + mode↲
╞ + 2: first storage address↲
╞ + 4: last storage address↲
↲
╞ mode: firmware <0 :↲
╞ ╞ firmware = 0: COS program.↲
╞ ╞ firmware = 1: level II diagnostic.↲
↲
╞ Answer:↲
╞ + 0: status↲
╞ + 2: number of halfwords↲
╞ + 4: number of characters↲
╞ + 6: i/o result↲
╞ + 8-+14: detailed status↲
↲
╞ Errors: Result 2: ┆84┆Calling process is not reserver of disc ↓
┆19┆┆9b┆┄┄process.↲
╞ ╞ Result 3: ┆84┆Message sent to a logical disc or logical ↓
┆19┆┆9b┆┄┄discs linked to physical disc.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆81┆┆81┆┆81┆┆a1┆┆b0┆4.9. POWER DOWN SPINDEL.┆e1┆↲
↲
Function:↲
↲
┆84┆This command causes IDA801 to power down the spindel on the ↓
┆19┆┆89┆┄┄slave device. This command completes within aproximately 20 ↓
┆19┆┆89┆┄┄seconds for FSD and aproximately 40 seconds for RSD. The answer ↓
┆19┆┆89┆┄┄will be returned when the operation has been completed.↲
↲
╞ ┆84┆This operation will only be accepted by a physical disc (and no ↓
┆19┆┆89┆┄┄logical discs must be linked on it).↲
↲
┆81┆The sending process must be reserver of the disc.↲
↲
Message:↲
+ 0: 12<12 + 0↲
↲
Answer:↲
+ 0: status↲
+ 2: 0↲
+ 4: 0↲
+ 6: i/o result↲
+ 8-+14: detailed status↲
↲
┆84┆ ┆84┆The slave device status and the current seek address part of ↓
┆19┆┆89┆┄┄the detailed status is not valid.↲
↲
Errors: Result 2: ┆84┆Calling process is not reserver of disc ↓
┆19┆┆9b┆┄┄process.↲
Result 3: ┆84┆Message sent to a logical disc or logical ↓
┆19┆┆9b┆┄┄discs linked to physical disc.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆4.10 WRITE SYSTEM FIRMWARE.↲
↲
╞ Function:↲
↲
╞ ┆84┆The specified core area, containing either the firmware (the ↓
┆19┆┆89┆┄┄COS-program) or the test-program (the level II diagnostic test ↓
┆19┆┆89┆┄┄program), is written on the system-cylinder of the disc.↲
↲
╞ ┆84┆This operation will only be accepted by a physical disc (and no ↓
┆19┆┆89┆┄┄logical discs must be linked on it).↲
↲
╞ ┆84┆The sending process must be reserver of the disc process.↲
↲
╞ Message:↲
╞ + 0: 13<12 + mode↲
╞ + 2: first storage address↲
╞ + 4: last storage address↲
↲
╞ ╞ mode: firmware <0:↲
╞ ╞ firmware =0: COS-program↲
╞ ╞ firmware =1: level II diagnostic.↲
↲
╞ Answer:↲
╞ + 0: status↲
╞ + 2: number of halfwords↲
╞ + 4: number of characters↲
╞ + 6: i/o-result↲
╞ + 8-+14: detailed status.↲
↲
╞ Errors: Result 2: ┆84┆Calling process is not reserver of disc ↓
┆19┆┆9b┆┄┄process.↲
╞ ╞ Result 3: ┆84┆Message sent to a logical disc or logical ↓
┆19┆┆9b┆┄┄discs linked to physical disc.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆4.11 SECURITY ERASE.↲
↲
╞ Function:↲
↲
╞ ┆84┆The specified segments on the disc are erased.↲
╞ A random bit-pattern are written on the segments.↲
↲
╞ The sending process must be reserver of the disc.↲
↲
╞ Message:↲
╞ + 0: 18<12 + 0↲
╞ + 2: 0↲
╞ + 4: 0↲
╞ + 6: first segment↲
╞ + 8: no of segments.↲
↲
╞ Answer:↲
╞ + 0: status↲
╞ + 2: (number of 'halfwords' erased)↲
╞ + 4: number of characters erased↲
╞ + 6: i/o-result↲
╞ + 8-+14: detailed status.↲
↲
╞ Errors: Result 2: ┆84┆Sending process is not reserver of disc ↓
┆19┆┆9b┆┄┄process.↲
╞ ╞ Result 3: ┆84┆Message sent to a physical disc on which ↓
┆19┆┆9b┆┄┄logical discs are linked.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆APPENDIX.┆e1┆↲
↲
↲
┆b0┆┆a1┆A. REFERENCES.↲
↲
↲
(1) ┆84┆RC8000 Disc Process, RCSL No 31-D528.↲
↲
↲
(2) ┆84┆┆84┆RC8000/IDA801 Backing Storage Area Process, Reference ↓
┆19┆┆8d┆┄┄Manual.↲
╞ RCSL No 991 09780.↲
↲
↲
(3) ┆84┆RC8000/IDA801 Main Process, Reference Manual.↲
RCSL No 991 09773.↲
↲
↲
╞ (4) Intelligent Standard Interface (ISI) Specification.↲
╞ Spec.: 77653440.↲
↲
↲
╞ (5) Product Specification for 9056 Control Module.↲
╞ Spec.: 64400100.↲
════════════════════════════════════════════════════════════════════════
↓
┆b0┆┆a1┆B. DETAILED STATUS FORMAT.┆e1┆↲
↲
┆84┆In this section a description of the status delivered in word ↓
┆19┆┆89┆┄┄+8 - +14 of the answer is given. ↓
┆19┆┆89┆┄┄It is recommended to consult ref. 4 and 5 for a more detailed ↓
┆19┆┆89┆┄┄description.↲
↲
↲
┆a1┆┆b0┆B.1. Answer Format.┆e1┆↲
↲
+ 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 + flaw Address, ↓
┆19┆┆91┆┄┄byte 3<0↲
+14: ┆84┆Flaw Address, byte 2<16 + flaw Address, byte 1<8↲
+ flaw Address, byte 0<0↲
↲
↲
┆a1┆┆b0┆B.2. Status Description.┆e1┆↲
↲
┆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.↲
↲
┆a1┆┆b0┆↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆B.2.1. Control Module Status:┆e1┆↲
↲
This is bit encoded:↲
↲
Bit 0: ┆84┆┆84┆Normal end (no further information in system/manual ↓
┆19┆┆92┆┄┄intervention status fields - but delay code may ↓
┆19┆┆92┆┄┄contain valid information).↲
1: ┆84┆┆84┆Check end (further information in system/manual ↓
┆19┆┆92┆┄┄intervention status fields).↲
2-4: ┆84┆Execution status: 100B ┆84┆ISI i/o parity error or ↓
┆19┆┆a9┆┄┄internal controller error.↲
110B ┆84┆┆84┆Disc pack change (RSD). This ↓
┆19┆┆a9┆┄┄will also be signaled in the ↓
┆19┆┆a9┆┄┄status word (answer word +0) ↓
┆19┆┆a9┆┄┄bit 0.↲
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 Code.┆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┆ ┆84┆A seek error may be detected in all of the operations. If it is ↓
┆19┆┆89┆┄┄detected the following is automatically done.↲
┆84┆ ┆84┆The seek is repeated once. If this second seek succeeded the ↓
┆19┆┆89┆┄┄status word will indicate OPERATION COMPLETED, the Control ↓
┆19┆┆89┆┄┄Module status will indicate NORMAL END, but the delay code will ↓
┆19┆┆89┆┄┄indicate SEEK RETRY APPLIED.↲
┆84┆ ┆84┆If the second seek failed, the status word indicates POSITION ↓
┆19┆┆89┆┄┄ERROR, Control Module status indicates CHECK END and delay code ↓
┆19┆┆89┆┄┄indicates SEEK RETRY APPLIED.↲
↲
Read header troubles:↲
┆84┆ ┆84┆No ECC correction is applied if an address information block ↓
┆19┆┆89┆┄┄(header) contains errors.↲
↲
Read data troubles:↲
┆84┆ See section 2.3: Data error.↲
↲
↲
┆b0┆┆a1┆B.2.3. Manual Intervention Code.┆e1┆↲
↲
00 (00H): No manual intervention status.↲
┆84┆Other values: Indicates an error which normally is correctable ↓
┆19┆┆89┆┄┄only through manual intervention (for further information see ↓
┆19┆┆89┆┄┄ref. 5).↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆B.2.4. Delay Code.┆e1┆↲
↲
╞ ┆84┆The delay code specifies whether or not an error recovery ↓
┆19┆┆89┆┄┄action has been performed. The delay code does not necessarily ↓
┆19┆┆89┆┄┄indi┄cate an error, as the data correction may have been suc┄↓
┆19┆┆89┆┄┄cessfull.↲
↲
00 (00H): No delay status.↲
33-39 (21H-27H): Bit encoded delay status:↲
┆84┆ 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.┆e1┆↲
↲
┆84┆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↲
↲
↲
┆81┆┆a1┆┆b0┆B.2.6. Current Seek Address (byte 3 -0).┆e1┆↲
↲
┆84┆The flaw address is given as an ┆b0┆absolute sector┆f0┆ address on the ↓
┆19┆┆89┆┆81┆┄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┆┄┄┆a1┆sector┆e1┆ address of the sector which needed data correction to be ↓
┆19┆┆89┆┄┄applied (only possible for input, output with read after ↓
┆19┆┆89┆┄┄write).↲
╞ ┆84┆If the operation failed because of an unrecoverable error, it ↓
┆19┆┆89┆┄┄contains the sector-address of the erroneous sector.↲
╞ If the operation succeeded it is undefined.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆C. FORMAT OF STATISTICS INFORMATION.↲
↲
┆84┆The statistics information supplied from a disc process does ↓
┆19┆┆89┆┄┄not contain information concerning the communication between ↓
┆19┆┆89┆┄┄RC8000 and the IDA801 controller.↲
↲
╞ ┆84┆The statistics information for the Control Module will only be ↓
┆19┆┆89┆┄┄delivered when reading statistics for the disc unit which has ↓
┆19┆┆89┆┄┄physical device address zero on the Control Module.↲
↲
┆84┆The detailed statistics are given as 16 bits count values ↓
┆19┆┆89┆┄┄unless others noted in the description. The statistics are ↓
┆19┆┆89┆┄┄input to RC8000 in a packed format. Along with the description ↓
┆19┆┆89┆┄┄the RC8000 layout is sketched. Some of the fields are separated ↓
┆19┆┆89┆┄┄in two parts which are stored in two consecutively placed ↓
┆19┆┆89┆┄┄RC8000 words. In the description these parts are denoted ↓
┆19┆┆89┆┄┄Most/Least Significant Byte (MSB/LSB). In the sketch of the ↓
┆19┆┆89┆┄┄layout a "," denotes a byte (8 bits) and a "!" denotes a byte ↓
┆19┆┆89┆┄┄┆a1┆and┆e1┆ a field limit.↲
↲
╞ ┆84┆The 16 bits count values must be interpreted as a countvalue ↓
┆19┆┆89┆┄┄concatenated of 2 8 bits counters, where the 8 leftmost bits ↓
┆19┆┆89┆┄┄are the ┆a1┆least┆e1┆ significant and the 8 rightmost bits are the ┆a1┆most┆e1┆ ↓
┆19┆┆89┆┄┄significant byte.↲
╞ ┆84┆Counters with more than 16 bits must be interpreted as a conca-↓
┆19┆┆89┆┄┄tenation of a number of 16 bits counters (interpreted as ↓
┆19┆┆89┆┄┄described) where the 16 leftmost bits are the most significant ↓
┆19┆┆89┆┄┄and the 16 rightmost bits are the least significant bits.↲
↲
╱04002d4e0c00060000000003014d3100000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
╱04002d4e0c0006000000000301483100000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
↓
════════════════════════════════════════════════════════════════════════
↓
Slave Device Detailed Statistics:↲
↲
╱04002d4e0c00060000000002014d3100000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
╱04002d4e0c00060000000003014d3100000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
↓
╞ Bit no:↲
╞ 0 8 16↲
+ 0: !...,...,..., No of seeks (48 bits count)↲
+ 2: ,...,...,...! ↲
+ 4: !...,...!..., Seek error. Unable to read header LSB.↲
+ 6: ,...!...,...! Unable to read header MSB. Unable to read data.↲
+ 8: !...,...!..., ┆84┆┆84┆Write protected media violation. No device ↓
┆19┆┆9c┆┄┄responce LSB.↲
+10: ,...!...,...! ┆84┆No device responce MSB. Data correction applied.↲
+12: !...,...!..., Seek retry applied. Data retry applied LSB.↲
+14: ,...!...,...! Data retry applied MSB. Unused.↲
+16: !...,...!..., Unused. No head select fault LSB.↲
+18: ,...!...,...! No head select fault MSB. Write fault.↲
+20: !...,...!..., (R+W) x Off cylinder fault. (RxW) fault LSB.↲
+22: ,...!...,...! (RxW) fault MSB. Voltage fault.↲
+24: !...,...!..., Head select fault. Unused.↲
+26: ,...!...,...! Unused. Software write protect fault.↲
+28: !...,...,...! Unused.↲
+30: !...,...,...! Unused.↲
┆84┆ ┆84┆The following sector addresses are absolute ↓
┆19┆┆9c┆┄┄sector addresses (32 bits):↲
+32: !...,...,..., 1. defective sector address, byte 2,3,0. ↲
+34: ,...!...,..., ┆84┆┆84┆1. defective sector address, byte 1. 2. defective ↓
┆19┆┆9c┆┄┄sector address, byte 2,3.↲
+36: ,...,...!..., ┆84┆┆84┆2. defective sector address, byte 0,1. 3. ↓
┆19┆┆9c┆┄┄defective sector address, byte 2.↲
+38: ,...,...,...! 3. defective sector address, byte 3,0,1.↲
+40: !...,...,..., 4. defective sector address, byte 2,3,0.↲
+42: ,...! 4. defective sector address, byte 1.↲
↲
↲
Control Module Detailed Statistics:↲
↲
+42: !...,...! Command block overwrite.↲
+44: !...,...!..., ┆84┆┆84┆Illegal command byte. Illegal secondary seek ↓
┆19┆┆9c┆┄┄address LSB.↲
+46: ,...!...,...! ┆84┆┆84┆Illegal secondary seek address MSB. Illegal ↓
┆19┆┆9c┆┄┄primary seek address.↲
+48: !...,...!..., ┆84┆┆84┆Illegal command parameter. I/o illegal write ↓
┆19┆┆9c┆┄┄error LSB.↲
+50: ,...!...,...! ┆84┆┆84┆I/o illegal write error MSB. I/o illegal ↓
┆19┆┆9c┆┄┄disconnect.↲
+52: !...,...,...! Unused.↲
+54: !...!...,...! Unused. I/o parity error.↲
+56: !...,...!..., ┆84┆R/w scheduler parity error. Buffer parity error ↓
┆19┆┆9c┆┄┄LSB.↲
+58: ,...!...,...! Buffer parity error MSB. ECC hardware fault.↲
+60: !...,...!..., ┆84┆┆84┆Illegal device no/control field. Diagnostic fault ↓
┆19┆┆9c┆┄┄detected LSB.↲
+62: ,...!...,...! Diagnostic fault detected MSB. Unused.↲
↲
════════════════════════════════════════════════════════════════════════
↓
╱04002d4e0c00060000000003014d3100000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
╱04002d4e0c00060000000002014d3100000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
↓
┆a1┆┆b0┆D. MESSAGE/ANSWER FORMAT SURVEY.↲
↲
┆e1┆┆e1┆ ┆a1┆┆e1┆ ┆a1┆Operation┆e1┆ ┆a1┆Message┆e1┆ ┆a1┆Answer┆e1┆↲
↲
Sense 0<12 + 0 status↲
0↲
0↲
i/o result↲
detailed status↲
- " -↲
- " -↲
- " -↲
↲
↲
Input 3<12 + 0 status↲
first storage address number of halfwords↲
last storage address number of characters↲
first segment i/o result↲
detailed status↲
- " -↲
- " -↲
- " -↲
↲
↲
Output 5<12 + mode status↲
first storage address number of halfwords↲
last storage address number of characters↲
first segment i/o result↲
detailed status↲
- " -↲
- " -↲
- " -↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ Format kit 6<12 + 0 status↲
╞ ╞ ╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ ╞ 0↲
╞ ╞ ╞ ╞ ╞ ╞ i/o result↲
╞ ╞ ╞ ╞ ╞ ╞ detailed status↲
╞ ╞ ╞ ╞ ╞ ╞ - " -↲
╞ ╞ ╞ ╞ ╞ ╞ - " -↲
╞ ╞ ╞ ╞ ╞ ╞ - " -↲
↲
↲
Position 8<12 + 0 status↲
irrelevant 0↲
irrelevant 0↲
segment i/o result↲
detailed status↲
- " -↲
- " -↲
- " -↲
↲
↲
Extract Statistics 9<12 + mode status↲
first storage address number of halfwords↲
last storage address number of characters↲
i/o result↲
detailed status↲
- " -↲
- " -↲
- " -↲
↲
↲
Power Up Spindel 10<12 + 0 status↲
0↲
0↲
i/o result↲
detailed status↲
- " -↲
- " -↲
- " -↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
╞ Read System FW 11<12 + mode status↲
╞ ╞ ╞ first storage address number of halfwords↲
╞ ╞ ╞ last storage address number of characters↲
╞ ╞ ╞ ╞ ╞ ╞ i/o result↲
╞ ╞ ╞ ╞ ╞ ╞ detailed status↲
╞ ╞ ╞ ╞ ╞ ╞ - " -↲
╞ ╞ ╞ ╞ ╞ ╞ - " -↲
╞ ╞ ╞ ╞ ╞ ╞ - " -↲
↲
↲
Power Down Spindel 12<12 + 0 status↲
0↲
0↲
i/o result↲
detailed status↲
- " -↲
undefined↲
undefined↲
↲
↲
Write System FW 13<12 + mode status↲
first storage address number of halfwords↲
last storage address number of characters↲
i/o result↲
detailed status↲
- " -↲
- " -↲
- " -↲
↲
↲
Security Erase 18<12 + 0 status↲
0 (number of halfwords)↲
0 number of bytes↲
first segment i/o result↲
no of segments detailed status↲
- " -↲
╞ ╞ ╞ ╞ ╞ ╞ - " -↲
╞ ╞ ╞ ╞ ╞ ╞ - " -↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆1a┆┆1a┆ - " -↲
nused.↲
+26: ,...!...,...! Unused. Soft