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...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Track Initialization ProceduresThe following procedures are recommended for track initialization programs used with<strong>the</strong> 5022 Disk Storage Module. They must be performed for each disk (upper or lower)to format <strong>the</strong> tracks and analyze <strong>the</strong> condition of <strong>the</strong> disk surface. (Steps 2 to 5 must beperformed twice for each cylinder—once for <strong>the</strong> upper track and once for <strong>the</strong> lowertrack.)OperationDescription1. Read sector ID Determine that <strong>the</strong> track has not been previously flagged.(This step need not be performed when initializing a prevouslyunused disk.)2. Format track Write address marks, sector identifiers, and gaps on <strong>the</strong> track.3. Read verify Check all <strong>the</strong> sectors to ensure that data can be recoveredcorrectly. If an error occurs, go to step 10.4. Write data Write on each sector with a data word of hexadecimal 5555.5. Read verify Check all <strong>the</strong> sectors to ensure that data can be recoveredcorrectly. If an error occurs, go to step 10.6. Proceed If both tracks in <strong>the</strong> cylinder are formatted, seek to <strong>the</strong>next cylinder and repeat steps 2 through 5. If both tracksare not formatted, repeat steps 2 through 5 for <strong>the</strong> o<strong>the</strong>rtrack in this cylinder.7. Repeat Perform steps 2 through 6 until all tracks have been processed.8. Read sector ID Read a sector ID on all tracks to check fo- seek errors. Aseek error during a format track operation causes two differenttracks to contain <strong>the</strong> same identifiers or <strong>the</strong> identifiersfor one track to be missing.If a seek error occurred during <strong>the</strong> formatting operation,repeat steps 1 through 7.9. Proceed Perform steps 2 through 8 at least once to complete <strong>the</strong>initialization procedure.10. Error handling If an error occurs, analyze <strong>the</strong> ISW and ISWEX. If a missingaddress mark or file data check occurs, retry a read verifycommand at least 10 times. On <strong>the</strong> first unsuccessful retrythat indicates a missing address mark or file data check, flag<strong>the</strong> track as defective and go to step 11. If all 10 retries aresuccessful, proceed with <strong>the</strong> initialization procedure from<strong>the</strong> point at which it was interrupted.For any error o<strong>the</strong>r than missing address mark or file datacheck, follow <strong>the</strong> normal error recovery procedures describedlater under "Suggested Error Recovery Procedures."11. Assign track Alternate tracks must be proved reliable by steps 2 through5 before <strong>the</strong>y are used as alternates.12. Format track Write sector identifiers on <strong>the</strong> defective track with <strong>the</strong> flagbits set to 1 and 0, respectively, and <strong>the</strong> cylinder and sectorvalues of <strong>the</strong> alternate track. A defective alternate trackshould be formatted with its own address and flag bits bothset to 1.13. Read sector ID Read a sector ID from <strong>the</strong> defective track just formatted. If<strong>the</strong> address of <strong>the</strong> alternate track cannot be recovered, <strong>the</strong>disk must be repaired unless this is an alternate track.

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

Saved successfully!

Ooh no, something went wrong!