12.07.2015 Views

IBM System/7 Functional Characteristics - All about the IBM 1130 ...

IBM System/7 Functional Characteristics - All about the IBM 1130 ...

IBM System/7 Functional Characteristics - All about the IBM 1130 ...

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Sector Identifier FormatEach identification area recorded on a sector contains six 8-bit bytes—three bytes of flagsand address information and three bytes of check information:Flags I AddressCheck charactersF C S CC CC BCAF (flag byte): Contains flagging information in bits 6 and 7 to indicate <strong>the</strong> condition of<strong>the</strong> track surface. <strong>All</strong> o<strong>the</strong>r bits in this byte should be 0. Flagging information is coveredin more detail under "Flagging," later in this chapter.C (cylinder byte): Contains <strong>the</strong> binary number corresponding to <strong>the</strong> physical location of<strong>the</strong> track on <strong>the</strong> disk.S (sector byte): Contains <strong>the</strong> number of <strong>the</strong> sector. Sectors on <strong>the</strong> top surface of <strong>the</strong>disk have sector numbers from 0 through 23. Sectors on <strong>the</strong> lower surface of <strong>the</strong> diskhave sector numbers from 32 through 55.CC (cyclic check): Contains an automatically generated check character used by <strong>the</strong> filecircuits to verify <strong>the</strong> data field.BCA (bit count appendage): Contains an automatically generated check character usedby <strong>the</strong> file circuits to verify <strong>the</strong> entire read or write operation.The address of any individual sector is contained in <strong>the</strong> first three bytes (F, C, and S)of <strong>the</strong> sector identifier. This address applies only to <strong>the</strong> disk on which <strong>the</strong>se bytes arelocated. Sectors occupying <strong>the</strong> same physical location on all disks have identical binarynumbers in <strong>the</strong> cylinder and sector bytes. The sectors on <strong>the</strong> upper surface of <strong>the</strong> disk arenumbered 0 through 23, starting with <strong>the</strong> index mark, and <strong>the</strong> sectors on <strong>the</strong> lower surfaceare numbered 32 through 55. A specific sector, <strong>the</strong>n, is addressed by specifying <strong>the</strong>upper or lower disk, a cylinder number, and <strong>the</strong> sector number.OPERATING AND PROGRAMMING RESTRICTIONSThe disk storage module operates only when (1) <strong>the</strong> drawer containing <strong>the</strong> disk file driveis closed, and (2) a disk cartridge is properly installed on <strong>the</strong> drive (models 1 and 2 only).The drawer cannot be opened unless <strong>System</strong>/7 power is on and <strong>the</strong> file ready indicator isturned off. The drawer should be kept closed at all times unless a disk cartridge is beinginserted or removed. A disk cartridge must be stored in <strong>the</strong> operating environment for atleast two hours before <strong>the</strong> cartridge is used for processing.On a disk storage module without CS, a data overrun condition occurs if an interruptionrequest for data (called a data-service interruption request) is not servicedwithin 40 microseconds. Although <strong>the</strong> disk storage module can be prepared to requestinterruptions on any priority level, care should be exercised in assigning a priorityinterruption level to <strong>the</strong> disk. It is advisable to assign <strong>the</strong> disk storage module to <strong>the</strong>highest priority level in order to avoid a data overrun condition. (If a data overruncondition occurs, data is not lost, but <strong>the</strong> data transfer rate is reduced due to <strong>the</strong>rotational delay of <strong>the</strong> disk before <strong>the</strong> I/O operation can be started again.)On a disk storage module with CS, an overrun occurs when <strong>the</strong> channel fails torespond in time to a request for service from <strong>the</strong> module. In a typical operatingenvironment, occurrence of an overrun should be extremely rare. It can occur only wheno<strong>the</strong>r modules cause a high level of activity on <strong>the</strong> channel during a read orwrite operation on <strong>the</strong> disk storage module. An overrun condition results in terminating<strong>the</strong> operation and presenting an interruption. Overrun (bit 2), any error (bit 3),channel end (bit 11), and device end (bit 13) will be present in <strong>the</strong> ISW.15-6 GA34-0003

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!