.ifi init_plm "SIB12.2" .srv section "B" .srv draft_date "" .srv draft "Formatting Disks With MTR" .ifi l0h "Formatting Disks with MTR" This appendix describes a procedure for formatting disk packs using the Media Test Routines (MTRs). The procedure utilizes an annotated script which shows typical input and output. Because the formatting procedures differ for MSU0451 and MSU0500/0501 devices, separate scripts are provided. In the scripts, input typed by the user is preceded .ur by a %BULLET% (bullet). ..l1h Formatting MSU0451 Disk Packs The following script shows how to run MTR tests 6 and 3 to format and test an MSU0451 disk pack, and to assign alternates to tracks found defective during testing. .fif .spb .bbk 1. Enter the Total OnLine Test System (TOLTS): .spb .inl .ur %BULLET% bound_tolts_$tolts_ .spb .inl 2 ***tolts executive version 810301 on 820812 at 20.071 .bek .spb .bbk .unl 1 2. Enter the MPC OnLine Test Subsystem (MOLTS): .spb ***enter "polts", "molts", "colts", "isolts", "quit", or "msg" .ur ??? %BULLET% molts .bek .spb .bbk .fin .inl 5 .unl 4 3. List the disk configuration for the disk string which formatting will be done (because of page constraints, the following message is not an exact copy of that which is displayed by the system): .inl 2 .fif .ur ??? %BULLET% test pcd peripheral configuration: dska 451 16 units; starting with device no. 1 020xx primary channel of 4 logical channels on mpc mspa 026xx secondary channel of 4 logical channels on mpc mspa 124xx secondary channel of 4 logical channels on mpc mspb 122xx secondary channel of 4 logical channels on mpc mspb .bek .spb .bbk .inl 5 .unl 4 4. Enter MTR test 6 to format and test the MSU0451 device: .unl 3 .ur ??? %BULLET% test mmt12020t6 .fin where "test mmt12020t6" is a sample of the input format "test mmtICCDDtT": .inl 13 .unl 5 .fin .unl 5 mmt identifies the MTR test package .unl 5 ICC gives the IOM number (0 = IOM A, 1 = IOM B, etc) and channel number (in decimal) of a channel by which the device to be formatted can be addressed. It must be one of those shown in the output of "test pcd" in step 3. In the sample input above, "120" is IOM B, channel 20. .spb .unl 5 DD gives the device number (in decimal) of the device to be tested. In the sample input, it is device 20 (dskb_20). .spb .unl 5 T gives the number of the MTR test to be run. In this case, test 6 should be run to format/test a pack. .bek .spb .inl 5 .unl 4 .bbk 5. The following output describes steps taken by MTR test 6 to attach the disk drive and mount the pack for writing: .fif .inl 2 ***molts executive versions 820601 820701 on 820812 at 19.97 **0(mmt12020) short wait, allocation queued **0(mmt12020) start tmt65a-rmc1, ttldat 820331, phy./log. id t//04 **0(mmt12020) start tmt65b-rmc2, ttldat 820331, phy./log. id t//04 **0(mmt12020) start tmt65c-rmc3, ttldat 820401, phy./log. id t//04 **0(mmt12020) start tmt65d-rmc4, ttldat 820405, phy./log. id t//04 **0(mmt12020) start tmt65e-rmc5, ttldat 820421, phy./log. id t//04 **0(mmt12020) start tmt65f-rmc6, ttldat 820331, phy./log. id t//04 **0(mmt12020) rmc6 is at your service to format a disk pack - **0(mmt12020) ***** write permission granted ***** **0(mmt12020) ***** begin format pack ***** the test will format all tracks on the pack. format will defined by device type. bad tracks will be marked defective (no alt. assigned). **0(mmt12020) system device code = .ds450 .bek .spb .inl 5 .unl 4 .fin .bbk 6. Answer MTR initialization questions (not a restart, normal formatting, and use 3 write patterns during testing): .fif .inl 2 **0(mmt12020) .ur is this a restart? enter (y or n) - %BULLET% n **0(mmt12020) select (f)ast or (n)ormal format? (f)ast format is designed for data security erase and/or test purposes. (n)ormal format is designed for disk packs that are going to be used in systems .ur applications. enter (f or n) - %BULLET% n **0(mmt12020) .ur select from "1" to "7" write patterns? enter (1 thru 7) - %BULLET% 3 .bek .spb .bbk .inl 5 .unl 4 7. At this point, formatting of the pack begins: .inl 2 .fif **0(mmt12020) ***** begin disk pack format ***** .bek .spb .fin .bbk .inl 5 .unl 4 8. After the message in Step 7 is displayed, press the BREAK key to interrupt formatting operations. When MOLTS prompts for input, set test options to: report the current cylinder/head (CCC/HH) address; display CCC/HH for transient errors; report test progress every 100 cylinders, with summary reports attached. .fif .inl 2 .ur %BULLET% .ur ??? %BULLET% test momt12020.r where "test momt12020.r" is a sample of the input format "test momtICCDD.O": .spb .fin .inl 16 .unl 8 momt identifies request to set options .unl 8 ICCDD are the IOM, Channel and Device numbers given in Step 4. .unl 8 .bbl 1 .r is the first option, to report current CCC/HH .bel location. .spb .inl 5 Set the remaining options when prompted: .fif .inl 2 .ur **0(mmt12020) t6 enter options: %BULLET% .i .ur **0(mmt12020) t6 enter options: %BULLET% .e .ur **0(mmt12020) t6 enter options: %BULLET% .s .ur **0(mmt12020) t6 enter options: %BULLET% .t .ur **0(mmt12020) t6 enter options: %BULLET% .go .bek .spb .bbk .fin .inl 5 .unl 4 9. When the .go option is entered in Step 8, MTR reports the current location being formatted and displays the defective tracks found. It then asks if you want to continue formatting: .inl 2 .fif **0(mmt12020) format function current addr. = 007/00 **0(mmt12020) format function current addr. = 007/00 **0(mmt12020) ***** rmc6 - summary report ***** no tracks were formatted defective **0(mmt12020) .ur do you want the test to continue? enter (y or n) - %BULLET% y .bek .spb .inl 0 .bbk .fin .inl 5 .unl 5 10. After every 100 cylinders are formatted, MTR displays defective tracks found. For example, the final summary displayed just before formatting completes, looks like: .fif .inl 2 **0(mmt12020) rmc6 has formatted tracks "000/00 thru 700/00" **0(mmt12020) ***** rmc6 - summary report ***** no tracks were formatted defective **0(mmt12020) rmc6 has formatted tracks "000/00 thru 800/00" **0(mmt12020) ***** rmc6 - summary report ***** no tracks were formatted defective **0(mmt12020) ***** disk pack format complete ***** .bek .spb .bbk .inl 5 .fin .unl 5 11. After formatting is complete, MTR begins testing the tracks on the formatted pack. Defective tracks are usually encountered only during the testing phase. Error summaries are displayed after every 100 cylinders have been tested. .spb .fif .inl 2 start media test phase **0(mmt12020) rmc6 has tested tracks "000/00 thru 100/00" **0(mmt12020) ***** rmc6 - summary report ***** no tracks were formatted defective **0(mmt12020) rmc6 has tested tracks "000/00 thru 200/00" **0(mmt12020) ***** rmc6 - summary report ***** no tracks were formatted defective **0(mmt12020) rmc6 has tested tracks "000/00 thru 300/00" **0(mmt12020) ***** rmc6 - summary report ***** defective - marginal data field on std track 217/10 **0(mmt12020) ***** rmc6 - summary report ***** defective - unrec. data field on std track 244/06,245/06 **0(mmt12020) ***** rmc6 - summary report ***** reclaimed - reformatted and certified 246/06 .bek .spb .bbk .fin .inl 5 .unl 5 12. When testing is complete, termination summary reports are displayed: .fif .inl 2 **0(mmt12020) ***** normal termination summary reports ***** **0(mmt12020) ***** rmc6 - summary report ***** defective - marginal data field on std track 217/10 **0(mmt12020) ***** rmc6 - summary report ***** defective - unrec. data field on std track 244/06,245/06 **0(mmt12020) ***** rmc6 - summary report ***** reclaimed - reformatted and certified 246/06 .bek .spb .bbk .inl 5 .fin .unl 5 13. MTR then asks if you want to select a new test (answer "y" for yes): .spb .inl 2 .fif **0(mmt12020) want to select a new test? .ur enter (y or n) - %BULLET% y .bek .spb .bbk .inl 5 .fin .unl 5 14. MTR then displays information describing how to select the next test: .inl 2 .fif **0(mmt12020) rmc6 will go into waiting! select test (t1 thru t6) enter test no. thru standard option call (test momticcddtx) - **0(mmt12020) waiting .bek .spb .bbk .fin .inl 5 .unl 5 15. To actually select the next test, press the BREAK key and wait for the MOLTS prompt. Then select test 3, which assigns alternate tracks for those tracks found to be defective above. .fif .inl 2 .ur %BULLET% .ur ??? %BULLET% test momt12020t3 .inl 5 where "test momt12020t3" is a sample of the input format "test momtICCDDtT": .inl 16 .unl 8 .fin momt identifies request to set options .unl 8 ICCDD are the IOM, Channel and Device numbers given in Step 4. .unl 8 tT gives the number of the next test to run. .inl 5 Test 3 initialization displays the following information: .inl 2 .fif **0(mmt12020) start tmt65e-rmc5, ttldat 820421, phy./log. id t//04 **0(mmt12020) start tmt65d-rmc4, ttldat 820405, phy./log. id t//04 **0(mmt12020) start tmt65c-rmc3, ttldat 820401, phy./log. id t//04 .bek .spb .bbk .inl 5 .fin .unl 5 16. Select subtest 4 of test 3, to assign alternates to all defective tracks: .inl 2 .fif **0(mmt12020) rmc3 is at your service for track and cylinder reformat - select a sub test a) subtst 1 - reformat 1 track (good) b) subtst 2 - reformat 1 cylinder (good) c) subtst 3 - reformat 1 track (defective) d) subtst 4 - assign alternate tracks .ur enter (1 thru 4) - %BULLET% 4 .bek .spb .bbk .inl 5 .fin .unl 5 17. MTR then briefly describes the subtest, and asks if you want to continue (answer "y" for yes) .inl 2 .fif **0(mmt12020) ***** begin subtst 4 ***** assign alternate tracks on the device a) subtst will search thru all standard tracks looking for tracks marked defective (no alternate assigned). b) when a track marked defective (no alternate assigned) is detected, the subtst will stop and process this track. c) the alternate track processor will go out to the alternate track cylinders and find the first available alternate. it will mark the track as assigned alternate. then it will mark the standard track as defective (alt. assigned). d) the search process will terminate after the last standard track completes testing and/or processing. .ur do you want the subtst to continue? enter (y or n) - %BULLET% y .bek .spb .bbk .inl 5 .fin .unl 5 18. MTR then asks for permission to overwrite the pack's label (answer "y" for yes): .fif .inl 2 **0(mmt12020) ***** rmc3 - label obliterate warning ***** all sub tests in rmc3 will overwrite the system label on track zero. .ur do you want the sub test to continue? enter (y or n) - %BULLET% y .bek .spb .bbk .inl 5 .fin .unl 5 19. MTR then asks if you are restarting (answer "n" for no): .inl 2 .fif **0(mmt12020) system device code = .ds450 **0(mmt12020) .ur is this a restart? enter (y or n) - %BULLET% n .bek .spb .bbk .inl 5 .fin .unl 5 20. MTR then begins displaying summary reports after every 100 cylinders are checked for alternate assignments: .fif .inl 2 **0(mmt12020) rmc3 has tested tracks "000/00 thru 200/00" **0(mmt12020) ***** rmc3 - subtst 4 summary report ***** no alternate tracks were assigned **0(mmt12020) rmc3 has tested tracks "000/00 thru 300/00" **0(mmt12020) ***** rmc3 - subtst 4 summary report ***** defective - alt assigned def alt def alt cyl/hd cyl/hd cyl/hd cyl/hd 217/10 811/00 244/06 811/01 245/06 811/02 .bek .spb .bbk .inl 5 .fin .unl 5 21. After alternate assignments are complete, MTR displays a summary report describing all alternates on the pack: .inl 2 .fif **0(mmt12020) ***** normal termination summary reports ***** **0(mmt12020) ***** rmc3 - subtst 4 summary report ***** defective - alt assigned def alt def alt cyl/hd cyl/hd cyl/hd cyl/hd 217/10 811/00 244/06 811/01 245/06 811/02 .bek .spb .bbk .inl 5 .fin .unl 5 22. MTR then asks if you want to select a new test (answer "n" for no, and "quit" to exit from TOLTS). .fif .inl 2 **0(mmt12020) want to select a new test? .ur enter (y or n) - %BULLET% n **0(mmt12020) normal term 1 ***molts executive version 820701 off 820812 at 21.45 p.t. 119530 ***enter "polts", "molts", "colts", "isolts", "quit", or "msg" .ur ??? %BULLET% quit ***tolts executive version 810301 off 820812 at 21.375 r 21:37 1107.348 1162 .bek .brp .fin .alb .inl ..l1h Formatting MSU0500/MSU0501 Disk Packs The following script shows how to run MTR tests 6 and 7 to format and test an MSU0500 or MSU0501 disk drive, and to assign alternates to tracks found defective during testing. .spb The MPC normally treats an MSU0500 or MSU0501 disk drive as two separately addressable devices. However, MTR formats and tests both logical devices during a single invocation, referring to one as the "odd device" (e.g., dskc_27) and the second as the "even device" (e.g., dskc_28). MTR refers to both logical devices as a single "head assembly" or "hda". .spb .fif .bbk .inl 5 .unl 4 1. Enter the Total OnLine Test System (TOLTS): .fif .inl 0 .ur %BULLET% bound_tolts_$tolts_ .inl 2 ***tolts executive version 810301 on 820812 at 20.071 .bek .spb .bbk .inl 5 .fin .unl 4 2. Enter the MPC OnLine Test Subsystem (MOLTS): .fif .inl 2 ***enter "polts", "molts", "colts", "isolts", "quit", or "msg" .ur ??? %BULLET% molts .bek .spb .bbk .inl 5 .unl 4 3. List the disk configuration: .inl 2 .ur ??? %BULLET% test pcd peripheral configuration: dskc 501 32 units; starting with device no. 1 028xx primary channel of 4 logical channels on mpc mspc 030xx secondary channel of 4 logical channels on mpc mspc 130xx secondary channel of 4 logical channels on mpc mspd 128xx primary channel of 4 logical channels on mpc mspd .bek .spb .bbk .inl 5 .fin .unl 4 4. Enter MTR test 6 to format and test the entire MSU0500 or MSU0501 device: .inl 2 .fif .ur ??? %BULLET% test mmt12827t6 .inl 5 where "test mmt12827t6" is a sample of the input format "test mmtICCDDtT": .inl 16 .fin .unl 8 mmt identifies the MTR test package .unl 8 ICC gives the IOM number (0 = IOM A, 1 = IOM B, etc) and channel number (in decimal) of achannel by which the device to be formatted can be addressed.It must be one of those shown in the output of "test pcd" in step 3. In the sample input above, "128" is IOM B, channel 28. .unl 8 DD gives the device number (in decimal) of the device to be tested. In the sample input, it is device 27 (dskc_27). Always give the device number of the "odd device" associated with the disk drive. .unl 8 T gives the number of the MTR test to be run. In this case, test 6 should be run to format/test the drive. .bek .spb .bbk .inl 5 .fin .unl 4 5. The following output describes steps taken by MTR test 6 to attach the disk drive for writing: .inl 2 .fif ***molts executive versions 820601 820701 on 820805 at 20.08 **0(mmt12827) short wait, allocation queued **0(mmt12827) short wait, allocation queued **0(mmt12827) start tmt67a-mtr1, ttldat 820401, phy./log. id t//04 **0(mmt12827) start tmt67b-mtr2, ttldat 820401, phy./log. id t//04 **0(mmt12827) start tmt67c-mtr3, ttldat 820402, phy./log. id t//04 **0(mmt12827) start tmt67d-mtr4, ttldat 820405, phy./log. id t//04 **0(mmt12827) start tmt67e-mtr5, ttldat 820421, phy./log. id t//04 **0(mmt12827) start tmt67f-mtr6, ttldat 820405, phy./log. id t//04 **0(mmt12827) mtr6 is at your service to format a physical device - **0(mmt12827) ***** write permission granted ***** **0(mmt12827) ***** begin upgrade/downgrade hda ***** the test will format all tracks on the hda. the format will be defined by device type. bad tracks will be marked defective (no alternate). .bek .spb .bbk .inl 5 .fin .unl 4 6. Answer MTR initialization questions (ok to format with 512 words per sector, not a restart, normal formatting, and use 3 write patterns during testing): .fif .inl 2 **0(mmt12827) device pair are configured as msu0501's the hda will be formatted in (512) words/sector. is this correct? .ur enter (y or n) - %BULLET% y **0(mmt12827) is this a restart? .ur enter (y or n) - %BULLET% n **0(mmt12827) select (f)ast or (n)ormal format? (f)ast format is designed for data security erase and/or test purposes. (n)ormal format is designed for hda's to be used in systems applications. .ur enter (f or n) - %BULLET% n **0(mmt12827) select from "1" to "7" write patterns? .ur enter (1 thru 7) - %BULLET% 3 .bek .spb .bek .inl 5 .unl 4 7. At this point, formatting of the pack begins: .fif .inl 2 **0(mmt12827) ***** begin hda format ***** .bek .spb .bbk .inl 5 .fin .unl 4 8. After the message in Step 7 is displayed, press the BREAK key to interrupt formatting operations. When MOLTS prompts for input, set test options to: report the current cylinder/head (CCC/HH) address; display CCC/HH for transient errors; report test progress every 100 cylinders, with summary reports attached. .fif .inl 2 .ur %BULLET% .ur ??? %BULLET% test momt12827.t .fin .inl 5 where "test momt12020.r" is a sample of the input format "test momtICCDD.O": .inl 16 .unl 8 momt identifies request to set options .unl 8 ICCDD are the IOM, Channel and Device numbers given in Step 4. .unl 8 .bbl .r is the first option, to report current CCC/HH .bel location. .inl 5 Set the remaining options when prompted: .fif .inl 2 .ur **0(mmt12827) t6 enter options: %BULLET% .e .ur **0(mmt12827) t6 enter options: %BULLET% .s .ur **0(mmt12827) t6 enter options: %BULLET% .i .ur **0(mmt12827) t6 enter options: %BULLET% .r .ur **0(mmt12827) t6 enter options: %BULLET% .go .bek .spb .bbk .inl 5 .fin .unl 4 9. When the .go option is entered in Step 8, MTR reports the current location being formatted and displays the defective tracks found. It then asks if you want to continue formatting: .inl 2 .fif **0(mmt12827) format function current addr. = 004/00 **0(mmt12827) format function current addr. = 004/00 **0(mmt12827) ***** statistics from format of hda ***** summary for msu0501 devices (27/28) no. of tracks with 1 defect skip = 1 no. of tracks with 2 defect skips = 0 no. of tracks with 3 defect skips = 0 no. of new defect skips generated = 0 total defect skips processed = 1 odd device defective tracks = 0 even device defective tracks = 0 physical device defective tracks = 0 total = 0 **0(mmt12827) ***** mtr6 - hda condition summary report ***** no tracks were marked defective. **0(mmt12827) do you want the test to continue? .ur enter (y or n) - %BULLET% y .bek .spb .bbk .inl 5 .fin .unl 5 10. After every 100 cylinders are formatted, MTR displays defective tracks found. For example, the final summary displayed just before formatting completes, looks like: .inl 2 .fif **0(mmt12827) mtr6 has formatted tracks "000/00 thru 800/00" **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 odd device report (27) --- defective - error logging track info 006/19,028/19,284/01,370/12 **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 even device report (28) --- defective - error logging track info 008/19,026/19,096/05,174/16,381/06,736/09,778/19 **0(mmt12827) ***** statistics from format of hda ***** summary for msu0501 devices (27/28) no. of tracks with 1 defect skip = 33 no. of tracks with 2 defect skips = 2 no. of tracks with 3 defect skips = 0 no. of new defect skips generated = 0 total defect skips processed = 37 odd device defective tracks = 4 even device defective tracks = 7 physical device defective tracks = 0 total = 11 **0(mmt12827) ***** hda format complete ***** .bek .spb .bbk .inl 5 .fin .unl 5 11. After formatting is complete, MTR begins testing the tracks on the formatted pack. Error summaries are displayed after every 100 cylinders have been tested. .inl 2 .fif start media test phase **0(mmt12827) mtr6 has tested tracks "000/00 thru 100/00" **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 odd device report (27) --- defective - error logging track info 006/19,028/19,284/01,370/12,816/04,818/04,832/04 **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 even device report (28) --- defective - error logging track info 008/19,026/19,096/05,174/16,381/06,736/09,778/19 **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 even device report (28) --- reclaimed - repaired data field 042/15 **0(mmt12827) ***** statistics from format of hda ***** summary for msu0501 devices (27/28) no. of tracks with 1 defect skip = 42 no. of tracks with 2 defect skips = 2 no. of tracks with 3 defect skips = 0 no. of new defect skips generated = 1 total defect skips processed = 47 odd device defective tracks = 7 even device defective tracks = 7 physical device defective tracks = 0 total = 14 .bek .spb .bbk .inl 5 .fin .unl 5 12. When testing is complete, termination summary reports are displayed: .inl 2 .fif **0(mmt12827) ***** normal termination summary reports ***** **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 odd device report (27) --- defective - error logging track info 006/19,028/19,284/01,370/12,816/04,818/04,832/04 **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 odd device report (27) --- reclaimed - repaired data field 764/09,830/04 **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 even device report (28) --- defective - error logging track info 008/19,026/19,096/05,174/16,381/06,736/09,778/19 **0(mmt12827) ***** mtr6 - hda condition summary report ***** --- msu0501 even device report (28) --- reclaimed - repaired data field 042/15,762/09,818/08 **0(mmt12827) ***** statistics from format of hda ***** summary for msu0501 devices (27/28) no. of tracks with 1 defect skip = 42 no. of tracks with 2 defect skips = 2 no. of tracks with 3 defect skips = 0 no. of new defect skips generated = 5 total defect skips processed = 51 odd device defective tracks = 7 even device defective tracks = 7 physical device defective tracks = 0 total = 14 .bek .spb .bbk .unl 1 .fin .inl 5 .unl 5 13. MTR then asks if you want to select a new test (answer "y" for yes) .inl 2 .fif **0(mmt12827) want to select a new test? .ur enter (y or n) - %BULLET% y .bek .spb .bbk .fin .inl 5 .unl 5 14. MTR then displays information describing how to select the next test: .inl 2 .fif **0(mmt12827) mtr6 will go into waiting! select test (t1 thru t7) enter test no. thru standard option call (test momticcddtx) - **0(mmt12827) waiting .bek .spb .bbk .fin .inl 5 .unl 5 15. To actually select the next test, press the BREAK key and wait for the MOLTS prompt. Then select test 7, which assigns alternate tracks for those tracks found to be defective above. Test 7 assigns alternates for the complete head assembly, whereas test 3 (used in the procedure for formatting MSU0451 disks) only assigns alternates for a single logical device. Thus, test 3 would have to be run twice (once for the odd device and once for the even device) to assign alternates on an MSU0500 or MSU0501 disk. .fif .inl 2 .ur %BULLET% .ur ??? %BULLET% test momt12827t7 .fin .inl 5 where "test momt12827t7" is a sample of the input format "test momtICCDDtT": .fin .inl 16 .unl 8 momt identifies request to set options .unl 8 ICCDD are the IOM, Channel and Device numbers given in Step 4. .unl 8 tT gives the number of the next test to run. .inl 5 Test 7 initialization displays the following information: .fif .inl 2 **0(mmt12827) start tmt67g-mtr7, ttldat 820405, phy./log. id t//04 .bek .spb .bbk .fin .inl 5 .unl 5 16. Select subtest 1 of test 7, to assign alternates to all defective tracks: .fif .inl 2 **0(mmt12827) mtr7 is at your service for special physical device formatting - select the subtst a) subtst 1 - assign all alternate tracks b) subtst 2 - create & write logging tracks .ur enter (1 thru 2) - %BULLET% 1 .bek .spb .bbk .fin .inl 5 .unl 5 17. MTR then briefly describes the subtest, and asks if you want to continue (answer "y" for yes): .fif .inl 2 **0(mmt12827) ***** begin subtst 1 ***** assign alternate tracks on the physical device the subtst will search "all" standard tracks on the hda for defective (no alt. assigned). if any are found, it will assign the 1st available alternate to them. **0(mmt12827) do you want subtst (1) to continue? .ur enter (y or n) - %BULLET% y .bek .spb .bbk .inl 5 .fin .unl 5 18. MTR then asks if you are restarting (answer "n" for no): .inl 2 .fif **0(mmt12827) is this a restart? .ur enter (y or n) - %BULLET% n .bek .spb .bbk .fin .inl 5 .unl 5 19. MTR then begins displaying summary reports after every 100 cylinders are checked for alternate assignments: .fif .inl 2 **0(mmt12827) mtr7 has processed tracks "000/00 thru 100/00" **0(mmt12827) ***** mtr7 - subtst 1 summary report ***** --- msu0501 odd device report (27) --- defective - alternate track assigned def alt def alt cyl/hd cyl/hd cyl/hd cyl/hd 006/19 840/00 028/19 840/03 **0(mmt12827) ***** mtr7 - subtst 1 summary report ***** --- msu0501 even device report (28) --- defective - alternate track assigned def alt def alt cyl/hd cyl/hd cyl/hd cyl/hd 008/19 840/01 026/19 840/02 096/05 840/04 .bek .spb .bbk .fin .inl 5 .unl 5 20. After alternate assignments are complete, MTR displays a summary report describing all alternates on the pack: .fif .inl 2 **0(mmt12827) ***** normal termination summary reports ***** **0(mmt12827) ***** mtr7 - subtst 1 summary report ***** --- msu0501 odd device report (27) --- defective - alternate track assigned def alt def alt cyl/hd cyl/hd cyl/hd cyl/hd 006/19 840/00 028/19 840/03 284/01 840/06 370/12 840/07 816/04 840/11 818/04 840/12 832/04 840/13 **0(mmt12827) ***** mtr7 - subtst 1 summary report ***** --- msu0501 even device report (28) --- defective - alternate track assigned def alt def alt cyl/hd cyl/hd cyl/hd cyl/hd 008/19 840/01 026/19 840/02 096/05 840/04 174/16 840/05 381/06 840/08 736/09 840/09 778/19 840/10 .bek .spb .bbk .fin .inl 5 .unl 5 21. MTR then asks if you want to select a new test (answer "n" for no, and "quit" to exit TOLTS). .inl 2 .fif **0(mmt12827) want to select a new test? .ur enter (y or n) - %BULLET% n **0(mmt12827) normal term 1 ***molts executive version 820701 off 820806 at 00.27 p.t. 5185916 ***enter "polts", "molts", "colts", "isolts", "quit", or "msg" .ur ??? %BULLET% quit ***tolts executive version 810301 off 820806 at 00.165 r 00:16 5188.584 1038 .bek .inl 0 ----------------------------------------------------------- Historical Background This edition of the Multics software materials and documentation is provided and donated to Massachusetts Institute of Technology by Group BULL including BULL HN Information Systems Inc. as a contribution to computer science knowledge. This donation is made also to give evidence of the common contributions of Massachusetts Institute of Technology, Bell Laboratories, General Electric, Honeywell Information Systems Inc., Honeywell BULL Inc., Groupe BULL and BULL HN Information Systems Inc. to the development of this operating system. Multics development was initiated by Massachusetts Institute of Technology Project MAC (1963-1970), renamed the MIT Laboratory for Computer Science and Artificial Intelligence in the mid 1970s, under the leadership of Professor Fernando Jose Corbato. Users consider that Multics provided the best software architecture for managing computer hardware properly and for executing programs. Many subsequent operating systems incorporated Multics principles. Multics was distributed in 1975 to 2000 by Group Bull in Europe , and in the U.S. by Bull HN Information Systems Inc., as successor in interest by change in name only to Honeywell Bull Inc. and Honeywell Information Systems Inc. . ----------------------------------------------------------- Permission to use, copy, modify, and distribute these programs and their documentation for any purpose and without fee is hereby granted,provided that the below copyright notice and historical background appear in all copies and that both the copyright notice and historical background and this permission notice appear in supporting documentation, and that the names of MIT, HIS, BULL or BULL HN not be used in advertising or publicity pertaining to distribution of the programs without specific prior written permission. Copyright 1972 by Massachusetts Institute of Technology and Honeywell Information Systems Inc. Copyright 2006 by BULL HN Information Systems Inc. Copyright 2006 by Bull SAS All Rights Reserved