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.

Operation Description14. Seek Seek to <strong>the</strong> alternate track.15. Format track Write sector identifiers on <strong>the</strong> alternate track with <strong>the</strong> flagbits set to 0 and 1, respectively, and <strong>the</strong> same cylinder andsector values that were originally in <strong>the</strong> defective track.16. Continue Proceed with initialization on <strong>the</strong> next track. (Return tostep 7 or step 10.)The basic requirement is for one pass through steps 1 to 8. An option must be providedto allow additional testing so that a track can be positively identified as good or defective.After initialization, only two types of programs should change track flags: (1) initializationprograms, which must be able to ignore all previously flagged tracks and unconditionallyflag or unflag any individual track; and (2) operating programs that can dynamicallyflag a track must perform steps 11 through 15 of this procedure.SUGGESTED RECOVERY PROCEDURESError or exception conditions are indicated by bits that are set in <strong>the</strong> device status word(DSW), <strong>the</strong> interrupt status word (ISW), and <strong>the</strong> interrupt status word extension(ISWEX) for <strong>the</strong> disk storage module. Minimum error recovery procedures are definedfor <strong>the</strong> disk storage module in <strong>the</strong> following discussions.Recovery from DSW ErrorsA condition that sets DSW bit 4 can be checked for recovery by first reading <strong>the</strong> ISWEXand checking for <strong>the</strong> presence of <strong>the</strong> unsafe bit (bit 0). If no unsafe condition exists (bit0 = 0), <strong>the</strong> disk file drive has not completed its starting sequence.If an unsafe condition does exist, a halt I/O command should be issued to reset <strong>the</strong> conditionsand <strong>the</strong> original operation retried. If <strong>the</strong> unsafe condition cannot be reset afterfive attempts, operator intervention is required.Recovery procedures for DSW bits 1 and 14 are described in Chapter 4 under "DeviceStatus Word," since <strong>the</strong>se status conditions are defined for all I/O modules.Recovery from ISW Error or ExceptionBit 2—OverrunIf <strong>the</strong> overrun condition occurred while executing a write sequence, any pertinent parameters(such as word count) should be saved and <strong>the</strong> original sequence of operations retried.After eight unsuccessful retries, <strong>the</strong> user should be notified.If <strong>the</strong> overrun condition occurred while executing a read sequence, any pertinent parameters(such as word count) should be saved and <strong>the</strong> original sequence of operations retried.After 16 unsuccessful retries, <strong>the</strong> user should be notified.Bit 4—Drive Became Not ReadyIt should be determined if an unsafe condition exists (ISWEX bit 0 present). If this conditiondoes exist, a halt I/O command should be issued to reset <strong>the</strong> unsafe condition(s) and<strong>the</strong> original operation retried. After five unsuccessful retries, <strong>the</strong> user should be notified.If no unsafe condition exists, <strong>the</strong> user should be notified to restart <strong>the</strong> file.<strong>IBM</strong> 5022 Disk Storage Module 15-29

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

Saved successfully!

Ooh no, something went wrong!