Documentation changes for: How to Generate and Run DG/RDOS Part Number 093-000470-03 This file (filename 093000470.03) contains information that affects the following pages of your manual: *iii *5-4 *8-14 *16-2 *viii *5-6 *8-15 *16-4 *ix *5-10 *8-16 *16-5 *xii *5-11 *10-1 *16-6 *1-1 6-1 *10-7 *16-7 *1-4 *6-4 10-8 *16-8 *1-6 *6-5 *10-13 *16-12 *1-7 *6-6 *11-1 *16-13 *2-3 *6-8 *13-14 *16-15 *2-4 *6-9 *13-15 *16-18 *3-2 *7-4 13-20 *16-19 *3-3 *7-5 14-4 *16-20 *3-4 7-6 *14-5 *17-4 *4-6 *7-7 *14-6 17-5 *4-7 7-8 14-12 *A-1 *4-8 *7-10 14-21 A-3 *4-10 7-11 *14-27 *A-4 *4-14 *7-12 14-28 A-5 *5-1 *7-13 14-30 A-6 *5-2 7-14 14-31 *A-7 *5-3 *8-7 *14-32 This second revision of 093000470.03 was updated on October 9, 1992. Items appearing here are easy to identify: in the list above, asterisks (*) mark pages with changes printed in this file for the first time. And, in the margin of pages that follow, change bars (|) mark the new material. For example, this revision of 093000470.03 contains a change to page 1-1 of its parent manual. You are seeing this change for the first time, and bars appear next to it. To keep your manual current, you should do either of the following: o Mark the affected pages of your manual so that you will know to refer to this file for additional information. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 o Print this file, punch holes to fit your binder, and insert the pages into your manual. Copyright (c) Data General Corporation, 1983-1992 inclusive All Rights Reserved Licensed Material - Property of Data General Corporation ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page iii In the first paragraph of the preface, change "MV/9500 system" to | "MV/9000 Series system" and change "MV/3500 DC system" to "MV/3000 | DC Series system." | In the description of chapter 5 under the heading "Organization of | the Manual," change "MV/3500 DC" to "MV/3000 DC Series." In the description of chapter 6 under the heading "Organization of the Manual," change "MV/9500" to "MV/9000 Series." ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page viii | Change the title of Chapter 5 to "Loading DG/RDOS on an MV/3000 DC | Series or MV/5000 DC Series System." Change the title of Chapter 6 to "Loading DG/RDOS on an MV/7800 XP, MV/9000 Series, MV/15000, or MV/18000 System." ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page ix | In Chapter 10's contents, change the subsection that begins with | "MV/3500 DC" to "MV/3000 DC Series and MV/5000 DC Series Systems." In Chapter 10's contents, change the subsection that begins with "MV/7800 XP" to "MV/7800 XP, MV/9000 Series, MV/15000, and MV/18000 Systems." ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page xii | Change the title of Table A-4 to "MV/3000 DC Series and MV/5000 DC | Series System Storage Devices." Change the title of Table A-5 to "MV/7800 XP, MV/9000 Series, MV/15000, and MV/18000 System Storage Devices." ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 1-1 The first paragraph under "What Is DG/RDOS?" should read as follows: DG/RDOS is a version of Data General's Real-Time Disk Operating System (RDOS) that runs on DESKTOP GENERATION, DG/500, MV/1000 | DC, MV/1400 DC, MV/2000 DC, MV/2500 DC, MV/3200 DC, MV/3500 DC, | MV/3600 DC, MV/5500 DC, MV/5600 DC, MV/7800 XP, MV/9300, MV/9500, MV/9600, MV/15000, and MV/18000 systems. In each of these hardware environments, the operating system supports all of the computer's physical address space, 64 Kbytes of logical address space, and 16-bit accumulators. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 1-4 The entry in Table 1-1 for Cmd-Brk should read as follows: Pressing these two keys simultaneously returns you to the virtual console (DESKTOP GENERATION and DG/500 systems) or the System Control Program (MV/Family systems). On some machines, you must type Cmd-Brk three times to achieve this effect. You can resume processing at the point where you typed Cmd-Brk by | typing P (DESKTOP GENERATION and DG/500 systems), TTY | (MV/3000 DC Series and MV/5000 DC Series systems), or CONTINUE (other MV/Family systems). ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 1-6 The list of systems in the third paragraph should read as follows: | MV/1000 DC, MV/1400 DC, MV/2000 DC, MV/2500 DC, MV/3000 DC Series, and MV/5000 DC Series systems... The first sentence of the seventh paragraph has changed: | On MV/3000 DC Series and MV/5000 DC Series systems, use the asynchronous lines on the system board as LAC QTY lines. The last paragraph should read as follows: | If you choose not to use the lines on an MV/3000 DC Series or MV/5000 DC Series system board as LAC QTY lines, you can use master console emulation. In this case, your BG console and master console are the same. You cannot use the other asynch- ronous lines on the system board. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 1-7 The list of systems in the second paragraph should read as follows: | MV/1000 DC, MV/1400 DC, MV/2000 DC, MV/2500 DC, MV/3000 DC Series, and MV/5000 DC Series systems... The next to last paragraph should read as follows: | On MV/3000 DC Series and MV/5000 DC Series systems that use the asynchronous lines on the system board as LAC QTY lines, use the second to last QTY line on the system board. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 2-3 | In step 3, the question "Disk unit?" now comes before the question | "Disk drive model number?" The last question should read as follows: | Do you want a coresident diagnostic area [No] ? NO ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 2-4 The question after "***All patterns run***" should read as follows: | Do you wish to declare any blocks bad | that are not already in the bad black table [No] ? NO ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 3-2 | In step 3, the question "Disk unit?" now comes before the question | "Disk drive model number?" ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 3-3 | In step 3, the question "Disk unit?" now comes before the question | "Disk drive model number?" The question before the note should read as follows: | Do you want a coresident diagnostic area [No] ? YES ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 3-4 The question after "***All patterns run***" should read as follows: | Do you wish to declare any blocks bad | that are not already in the bad black table [No] ? NO ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 4-6 Change step 2 at the bottom of the page: | DKINIT is in bootable format on tape file 4, so type 4 to start the disk initializer program. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 4-7 | In step 1, the question "Disk unit?" now comes before the question | "Disk drive model number?" See Chapter 16 for more information. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 4-8 The first question should read as follows: | Do you want a coresident diagnostic area [No] ? YES | The question after "***All patterns run***" should read as follows: | Do you wish to declare any blocks bad | that are not already in the bad black table [No] ? NO ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 4-10 Change step 2: To install a boostrap root on the disk you just initialized, you must run a disk bootstrap program. This program, | DISKBOOT.SV, is in bootable format on tape file 5, so to start the program type 5. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 4-14 Change the second paragraph in step 3: The system now displays the date and time, loads the DG/RDOS files present on tape file 1 onto your disk, and establishes DA0 as your master directory. When you see the CLI prompt, R, you can use the LIST command to see the names of the files that have been moved: | R | LIST | IMOVE.SV 24064 SD | CLI.SV 29696 SD ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 5-1 | Change the title of Chapter 5 to "Loading DG/RDOS on an MV/3000 DC | Series or MV/5000 DC Series System." Change the first sentence to read as follows: | Read this chapter after (1) you have set up a new MV/3000 DC | Series or MV/5000 DC Series computer and (2) you have powered | up your system for the first time according to the instructions | in your hardware startup manual. From this point, you can | install DG/RDOS on a fixed disk by following the steps detailed | in the following sections: ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 5-2 Change step 2 at the bottom of the page: | DKINIT is in bootable format on tape file 4, so type 4 to start the disk initializer program. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 5-3 | In step 1, the question "Disk unit?" now comes before the question | "Disk drive model number?" See Chapter 16 for more information. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 5-4 The first question should read as follows: | Do you want a coresident diagnostic area [No] ? YES | The question after "***All patterns run***" should read as follows: | Do you wish to declare any blocks bad | that are not already in the bad black table [No] ? NO ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 5-6 Change step 2: To install a boostrap root on the disk you just initialized, you must run a disk bootstrap program. This program, | DISKBOOT.SV, is in bootable format on tape file 5, so to start the program type 5. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 5-10 Change the second paragraph in step 3: The system now displays the date and time, loads the DG/RDOS files present on tape file 1 onto your disk, and establishes DA0 as your master directory. When you see the CLI prompt, R, you can use the LIST command to see the names of the files that have been moved: | R | LIST | IMOVE.SV 24064 SD | CLI.SV 29696 SD ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 5-11 Change the first IMOVE command example to read as follows: | IMOVE/F/T/V 16384/S UT0:1 | Change the error message near the middle of the page: | Illegal file name: MV5.MCF | Enter new filename (NL to skip): | | Simply enter a legal filename, such as MV5.MF, and press New Line. IMOVE now loads the file and returns you to the CLI. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 6-1 Change the title of Chapter 6 to "Loading DG/RDOS on an MV/7800 XP, MV/9000 Series, MV/15000, or MV/18000 System." Change the first sentence to read as follows: Read this chapter when you have set up a new MV/7800 XP, MV/9000 Series, MV/15000, or MV/18000 computer and want to install DG/RDOS from the release tape. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 6-3 Insert the following note before the last sentence on the page: Note: You may be asked to choose between RTC/PIT and Architec- tural Clock. For DG/RDOS's purposes, you may choose either. However, choose RTC/PIT if your software requires a PIT. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 6-4 Change step 2 in the middle of the page: | DKINIT is in bootable format on tape file 4, so type 4 to start the disk initializer program. | In step 1, the question "Disk unit?" now comes before the question | "Disk drive model number?" See Chapter 16 for more information. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 6-5 The second question in step 2 should read as follows: | Do you want a coresident diagnostic area [No] ? NO | The question after "***All patterns run***" should read as follows: | Do you wish to declare any blocks bad | that are not already in the bad black table [No] ? NO ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 6-6 Change step 2: To install a boostrap root on the disk you just initialized, you must run a disk bootstrap program. This program, | DISKBOOT.SV, is in bootable format on tape file 5, so to start the program type 5. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 6-8 Change the second paragraph in step 3: The system now displays the date and time, loads the DG/RDOS files present on tape file 1 onto your disk, and establishes DA0 as your master directory. When you see the CLI prompt, R, you can use the LIST command to see the names of the files that have been moved: | R | LIST | IMOVE.SV 24064 SD | CLI.SV 29696 SD ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 6-9 Change the first IMOVE command example to read as follows: | IMOVE/F/T/V 16384/S MT0:1 ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 7-4 Replace step one with this information: The program first asks you to identify the type of computer you are generating a system for: Currently supported processors include DG/10, DG/10-SP, DG/20, DG/30, DG/500 MV/1000-DC, MV/1400-DC, MV/2000-DC, MV/2500-DC | MV/3000 DC Series, MV/5000 DC Series | MV/7800-XP, MV/9000 Series | MV/15000, MV/18000 Processor type ? [DG/500] To answer this question, enter one of the codes listed under the heading of currently supported processors and press the New Line key. The first four codes that begin with the letters DG represent DESKTOP GENERATION systems. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 7-5 The paragraph that includes a list of machines near the middle of the page should read as follows: If you are working on an MV/1000 DC, MV/1400 DC, MV/2000 DC, | MV/2500 DC, MV/3000 DC Series, or MV/5000 DC Series system, SYSGEN begins by asking if there are any DAn controllers in your system (for a list of the various disk, diskette, and tape drives, refer to Appendix A): The next to last paragraph should read as follows: On MV/1000 DC, MV/1400 DC, MV/2000 DC and MV/2500 DC systems, the first controller manages the hard disk drives in the main chassis, the second manages the diskette drive, and the third | manages the hard disk drives in any expansion chassis. On | MV/3000 DC Series and MV/5500 DC systems, the first controller manages all disk and diskette drives. On MV/5600 DC systems, the first and third controllers manage all disk and diskette drives. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 7-6 Change the second paragraph to read as follows: If you are working on an MV/7800 XP, MV/9000 Series, MV/15000, or MV/18000 system, SYSGEN begins by asking if there are any DAn controllers in your system (for a list of the various disk, diskette, and tape drives, refer to Appendix A): Any DAn disk(ette) controllers (Yes or No) ? [Yes] ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 7-7 Change the last paragraph to read as follows: If you are working on an MV/1000 DC, MV/1400 DC, MV/2000 DC, | MV/2500 DC, MV/3000 DC Series, or MV/5000 DC Series system, the utility asks: Any UTn tape controllers (Yes or No) ? [Yes] ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 7-8 Change the third paragraph to read as follows: If you are working on an MV/7800 XP, MV/9000 Series, MV/15000, or MV/18000 system, SYSGEN displays the following: Any MTn tape controllers (Yes or No) ? [Yes] ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 7-10 Change the first paragraph to read as follows: If you are working on an MV/1000 DC, MV/1400 DC, MV/2000 DC, | MV/2500 DC, MV/3000 DC Series, or MV/5000 DC Series system, SYSGEN's first prompt asks whether your system includes any Local Asynchronous Controllers: Number of LAC controllers (0-4) ? [0] Change the note in the middle of the page: | Treat the lines on an MV/3000 DC Series system board as an | LMC-8_2 on device code 42. Treat the lines on an MV/5000 DC | Series system board as a LAC-16 on device code 42. | | If you don't request this support for your MV/3000 DC Series or MV/5000 DC Series system, the master console is the only asynchronous line on the system board that you will be able to use. If you do request this support, you must use CONFIG to link the background console to a QTY line. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 7-11 The third paragraph should be changed: If you are working on an MV/7800 XP, MV/9000 Series, MV/15000, or MV/18000 system, SYSGEN's first prompt asks whether your system includes any IAC controllers: Number of IAC controllers (0-4) ? [0] ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 7-12 Change the third paragraph of step 7a: | On an MV/1000 DC, MV/1400 DC, MV/2000 DC, MV/2500 DC, MV/3000 | DC Series, or MV/5000 DC Series system, a secondary console controller cannot exist. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 7-13 In step 8, change the two paragraphs immediately before the note: | On a DG/500, MV/1000 DC, MV/1400 DC, MV/2000 DC, MV/2500 DC, | MV/3000 DC Series, or MV/5000 DC Series system, the possible answers are 0 and 1. Answer 1 only if you plan to connect a parallel printer to your system's printer port. On a DESKTOP GENERATION, MV/7800 XP, MV/9000 Series, MV/15000, or MV/18000 system, the range of possible answers is 0 to 2. If you have a parallel printer interface card and plan to connect a parallel printer to it, answer 1. If you have two such cards and two parallel printers, answer 2. Otherwise, answer 0. Also change the paragraph immediately after the note: If you have an MV/7800 XP, MV/9000 Series, MV/15000, or MV/18000 system and you indicate that you will have a printer on a parallel printer port, the utility asks if your controller uses a data channel interface: Primary printer using DCH interface (Yes or No) ? [No] ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 7-14 Renumber steps 10-12 so that they are steps 11-13. Add this infor- mation for step 10: On MV/7800 XP, MV/9000 Series, MV/15000, and MV/18000 systems, SYSGEN next inquires whether you have any Multiprocessor Communications Adapters: Number of MCA controllers (0 - 2) ? [0] MCA controllers let you transfer data words between the memory of one computer and that of another. DG/RDOS supports reading and writing over an MCA and the .GMCA system call. However, DG/RDOS does not support booting over an MCA. Respond with the number of such controllers in your configuration. If you have one MCA controller, the utility asks Primary device code (Yes or No) ? [Yes] Answer Yes if your controller uses device codes 6 and 7, or No if it uses device codes 46 and 47. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 8-7 Modify the second paragraph of step 3: If you are using the lines on an MV/1000 DC, MV/1400 DC, | MV/2000 DC, MV/2500 DC, MV/3000 DC Series, or MV/5000 DC Series system board as QTY lines, you should answer Y. Otherwise, answer N for the BG console. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 8-14 Change the next to last paragraph: On LMC-8_2, LAC-16, LAC-32, and IAC-8_3 controllers and the | lines on MV/3000 DC Series and MV/5000 DC Series system boards, DG/RDOS maps 50 to 75, 3600 to 4800, 7200 to 9600, and 135 to 38400 baud. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 8-15 Change the second paragraph in step 3: | If you have an MV/1000 DC, MV/1400 DC, MV/2000 DC, MV/2500 DC, | MV/3000 DC Series, or MV/5000 DC Series system, you should request 8 bits and no parity for the master console. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 8-16 Modify step 3: | MV/3000 DC Series and MV/5000 DC Series systems: * The first four and last four lines on the system board * All lines on each LMC-8_2 * The first four lines on each LAC-16 * The first eight lines on each LAC-32 Modify step 4: MV/7800 XP, MV/9000 Series, MV/15000, and MV/18000 systems: * All lines on each MCP-1 * All lines on each IAC-8_3 ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 10-1 The first paragraph under "Starting Up Your System" should be changed: Once you have generated your DG/RDOS system (Chapters 2-9), restarting that system is easy. Simply refer to the subsection "DESKTOP GENERATION Systems," "DG/500 Systems," "MV/1000 DC, | MV/1400 DC, MV/2000 DC, and MV/2500 DC Systems," "MV/3000 DC Series and MV/5000 DC Series Systems," or "MV/7800 XP, MV/9000 Series, MV/15000, and MV/18000 Systems," depending on the hardware you are using. Each of these subsections takes you to the point where you have the CLI running. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 10-7 | The heading on this page should read "MV/3000 DC Series and MV/5000 | DC Series Systems." The first sentence under that heading should be changed: If your system is shut down completely, consult the chapter on | routine powerups in the hardware manual for MV/3000 DC Series and MV/5000 DC Series computers. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 10-8 The heading on this page should read "MV/7800 XP, MV/9000 Series, MV/15000, and MV/18000 Systems." ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 10-13 | The subheading on this page should read "MV/3000 DC Series or | MV/5000 DC Series system:" ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 11-1 | Note that there is a new ICOPY utility. For more information, see | the release notice. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 13-14 Step 3 should read as follows: Transfer an operating system .SV file to tape file 2. For example, you might use this command line: | ICOPY MT0:2/T DGRDOS.SV | Change the paragraph after the question near the bottom of the page, "Number of tape file to boot? File =": If you are working on a DG/500, MV/1000 DC, MV/1400 DC, MV/2000 | DC, MV/2500 DC, MV/3000 DC Series, MV/5000 DC Series, MV/7800 XP, MV/9000 Series, MV/15000, or MV/18000 system, follow these directions: ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 13-15 Modify step 1d: | If you have an MV/3000 DC Series or MV/5000 DC Series system, you must mount your System Media tape or diskette. Enter the command BOOT n [optional-unit-number], where n is the appropriate device code of the unit on which you have mounted your System Media. (See Appendix A for a complete list of device codes.) Your console will display the Microcode Update and Installation menu; choose to load microcode into memory. After the system's microcode is loaded, choose to return to the SCP-CLI from the menu. Modify step 1e: If you have an MV/7800 XP, MV/9000 Series, MV/15000, or MV/18000 system, you must mount your System Media tape or diskette and boot your system's microcode. Enter the command BOOT n, where n is the appropriate device code of the unit on which you have mounted your System Media. (See Appendix A for a complete list of device codes.) You will see messages indicating that your system's microcode is being loaded, and then you will be returned to the SCP-CLI. Note: You may be asked to choose between RTC/PIT and Architec- tural Clock. For DG/RDOS's purposes, you may choose either. However, choose RTC/PIT if your software requires a PIT. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 13-20 Add this error message after the last one on this page: Warning: trailer label not found During a DUMP operation, BURST writes a trailer label at the end of each tape. If BURST cannot read this trailer label during a LOAD or during the verify phase of a DUMP/V or LOAD/V, it reports this message but tries to proceed. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 14-4 Change the description of global switch /O: Load: Overrides IMOVE's standard practice of not restoring a file from a backup if a file of the same name already resides in the directory into which IMOVE is trying to load the backup file. If you use the /O switch, the file you are trying to restore overwrites the existing file. Do not use /O and /R in the same command line. Dump: Dumps files even if they are in use. Note that the backups of such files may contain inconsistent information. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 14-5 Add this entry to Table 14-1: | /S Dumps files to or loads files from a sequential device, | such as an MCA line. Do not use this switch with tapes, | diskettes, or disk files. | Modify the "/T" entry in Table 14-1: | /T Dumps files to or loads files from tape. If you do not | use /T or /S, the utility assumes that you are using | diskettes or a disk file. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 14-6 Modify the "buffer-size/S" entry in Table 14-2: | buffer-size/S Lets you determine the size of the | tape/diskette buffers IMOVE will use for | a dump or load operation. If you use the | global /T switch, this defines the number | of bytes in each tape record and may be any | even number from 4 to 16834. If you do not | use the global /T switch, your buffer-size/S | can be any multiple of 512 from 1024 to 16384. | | By default the utility uses 8-Kbyte | tape/diskette buffers. You may need to | experiment to find out which buffer size works | best when you are dumping data to, or loading | data from, a reel-to-reel tape. The performance | of some cartridge drives is improved greatly if | you request large buffers; see Appendix A for | recommendations. | Add these entries to Table 14-2: buffer-size/B Lets you determine the size of the disk buffer. The default is 8192 bytes. buffers/N/B Allows you to define the number of tape/diskette buffers. percent/P/I Lets you select the percentage of the program's tape/diskette buffers that must be empty before IMOVE will resume input after filling all the buffers. percent/P/O Lets you select the percentage of the program's tape/diskette buffers that must be full before IMOVE will resume output after emptying all the buffers. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 14-12 Replace the third paragraph: After IMOVE reads this command, it prints the date and time; IMOVE then begins dumping the appropriate files. After IMOVE is done, the utility returns you to the CLI. Replace the sixth paragraph: After IMOVE reads your command, the program begins to load the files you requested that it move. After IMOVE is finished, the utility returns you to the CLI. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 14-21 In the section "DG/RDOS to AOS or AOS/VS," delete the line "Please insert disk 1, then press NEW LINE . . . ." In the section "AOS or AOS/VS to DG/RDOS," delete the line "Please insert disk 1, then press NEW LINE . . . ." ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 14-27 Change the error message "Attempt to alter a permanent file" to "Permanent file." | Change the error message "Buffer size must be a multiple of 2048" | to "Buffer size must be a multiple of 2." | Change the error message "Buffer size must be between 2048 and | 16384" to "Buffer size must be between 4 and 16384." Change both buffer size messages's descriptions as follows: | When you use buffer-size/S with global /T, the numeric argument | must be an even number between 4 and 16384. Delete the error message "Conflicting local switch setting." ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 14-28 The description for "File in use" should read as follows: You cannot use IMOVE to overwrite a file that is open. Also, you cannot dump a file that is open unless you use the global switch /O. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 14-30 Change the description for the error message "Invalid argument value specified": This error could occur if, for example, you used the argument/local-switch combination days/X on your command line and filled the days slot with something other than a number. It could also occur if you forgot to use hyphens to separate the day, month, and year in your date. In this case, retype the date in the proper format, for example, 31-JUL-91. Delete the error message "Invalid date." ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 14-31 Shorten the error message "Invalid VOL1 label on labeled media" to "Invalid VOL1 label." Delete the error message "Tape not ready." ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 14-32 Change the description of "Unit improperly selected": This error can occur if you issued a command for IMOVE to write to or read from an unlabeled tape without first mounting your tape. Another possibility is if you issued a command for IMOVE to write to or read from a labeled tape, and either there is no tape in the drive you specified on your command line, or the tape is not at the BOT mark. In this case, the utility does not terminate after issuing the error message, but prompts you again to insert your tape. Change the description of "Unrecognizable local switch setting": Your command line contained an invalid entry before the device-name argument. The valid local switches are listed in Table 14-2. Add these error messages: Insufficient logical memory is available Most likely you requested both a large buffer-size/S and a large buffer-size/B. Reduce these values so IMOVE will be able to fit its buffers in the 64 KB logical address space. Insufficient extended memory is available Use the CLI command SMEM to allocate more memory to your ground, or adjust the amount of memory IMOVE needs by reducing buffer-size/S and/or buffers/N/B. Buffer size must be between 1024 and 16384 | When you use buffer-size/S without global/T, and when you use | buffer-size/B, the numeric argument must be a multiple of 512 | between 1024 and 16384. Buffer size must be a multiple of 512 | When you use buffer-size/S without global/T, and when you use | buffer-size/B, the numeric argument must be a multiple of 512 | between 1024 and 16384. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Percentage must be between 0 and 100 When you use the argument/local-switch combination percent/P/I or percent/P/O on your command line, the numeric argument must be a value between 0 and 100. Number of buffers must be between 2 and 256 When you use the argument/local-switch combination buffers/N/B on your command line, the numeric argument must be a value between 2 and 256. Illegal partition size Most likely you're trying to load a dump that was created on AOS/VS and contains a Control Point Directory with a maximum size larger than 65535 blocks. You may be able to load the dump if you create the partition first. Illegal contiguous file size This error could occur if you're trying to load a dump that was created on AOS/VS and contains a file with zero maximum index levels and an element size larger than 65535 blocks. DG/RDOS does not support such large contiguous files. Illegal random file size You are probably trying to load a dump that was created on AOS/VS and contains a file whose size exceeds 65536 blocks. DG/RDOS does not support such large files. File type mismatch You might see this error if IMOVE tried to load a file or link but found a directory with the same name on the disk. In this case, IMOVE leaves the directory alone and does not load the file or link. This error can also occur if you use the local switch /R, but IMOVE cannot compare the time last modified (for example, a link doesn't have a time last modified). IMOVE leaves any existing files or links alone. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Invalid trailer label IMOVE is loading from labeled tape but cannot find the trailer labels that should be present at the end of each tape. IMOVE will do its best to cope with this problem, but be warned that your tapes may have been corrupted. Marginal blocks in range xxxxxx-xxxxxx An error was detected when IMOVE attempted a multi-block write to an MMOVE-format diskette, but all of IMOVE's single-block retries succeeded. The ability of your diskette to retain information is suspect. Remapped block xxxxxx IMOVE detected and remapped a bad block while writing to an MMOVE-format diskette. | Press NEW LINE to skip the rest of this file and continue | | This message appears after a more specific error message citing | the name of a disk file. An error occurred while IMOVE read | from a disk during a dump--the hard disk may have developed a | new bad block within the named disk file. | | If you press NEW LINE and let the dump run to completion, you | should be able to load the dump. However, any file that encoun- | tered this error will appear to be null-filled from where the | error occurred to the end of the file. A load operation cannot | tell you whether any such files are present; your only indica- | tion is the error during the dump operation. | | CAUTION: This is not the way to handle new bad blocks on a | disk. The proper procedures are documented in Appendix B of | this manual. This is only a tool that may help you save some of | your data in a catastrophic situation; for example, if your | disk develops more bad blocks than a bad block table can hold. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 16-2 Change the fourth and fifth paragraphs: Since the system cannot use a bad block, DKINIT also provides for a remap area, a set of disk blocks to which the operating system is referred when it tries to access a bad block. By | default, DKINIT bases the size of this remap area on the type | of the disk you are initializing, although the utility always supplies an area at least as large as the number of bad blocks it finds. Or you can specify the size of the remap area if you choose to. You may also select a starting address for this remap area, or you can accept the default placement among the highest addresses on the disk. DKINIT records both the size and location of the remap area in your disk's bad block table (block 4). Disk identification involves recording on block 3 of your disk key information about that disk. To obtain this information, | DKINIT begins all interactive sessions by requesting the unit | name and model number of your disk. Then, using your answers | (or information obtained from the disk controller itself), the | program defines such characteristics as the number of tracks per cylinder on your disk, the number of sectors per track, the number of logical blocks on your disk, and the checksum for block 3. The frame size, which influences the efficiency with which your system accesses files, is set either by default, according to the type of disk, or by you, according to the number of files you plan to have in each directory. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 16-3 Beginning with "Disk drive model number?" replace the text: | Disk unit? | | As this message indicates, DKINIT has on-line information to | help you answer any program queries you are not sure how to | respond to. For example, the first question DKINIT asks is Disk | unit? If you do not know the DG/RDOS mnemonic for the disk you | wish to work with, type ? or HELP, and a list contain- | ing entries similar to the following one appears: | | 6268 DJn .37 MB 5-1/4" 48 TPI diskette (Desktop) | | At the conclusion of this list, DKINIT repeats its question so | that you can enter the appropriate disk unit. What happens next | depends on whether or not your disk is of type DAn. | | Disk unit? DJ0 | | Disk drive model number? | | If your disk is not of type DAn, you must supply a model | number. Request help for DKINIT's second question to see a list | of just the disks of your requested type (in this case, DJn). | | If your disk is of type DAn, DKINIT proceeds differently: | | Disk unit? DA0 | | 662,907,392 byte DAn disk | | This revision asks a DAn disk about itself and is capable of | using its entire capacity. Old revisions looked up the model | number in a table and may have used a reduced capacity. You | only need to supply a model number if you want to use the | reduced capacity that old revisions used -- for example, if | you'll want to load old BURST backups. | | Disk drive model number? | | The program displays the disk's capacity (based on information | obtained from the disk controller) followed by hints on how to | answer the second question. | | If you're working with a new disk, will be performing FULL | initialization, and will not be loading old BURST backups of | the same model disk, simply press New Line in response to the | Disk drive model number? question and DKINIT will use the ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 | disk's full capacity. | | If you will be performing FULL initialization of a new disk in | order to load BURST backups of an old disk that you are | replacing, respond as you did when you formatted the old | disk--with either a model number followed by a New Line, or | with New Line alone. Respond similarly if you will only be | performing commands like LIST or TEST on a formatted disk. | Request help to see a list of just the DAn disks that old | revisions supported. | | Note: DKINIT supports some newer DAn disks that don't appear | in the help message. If you have such a disk, press | New Line in response to the Disk Drive model number? | question. | | Whether or not your disk is of type DAn, DKINIT displays | information about your disk and then asks for a command after | you respond to the Disk drive model number? question. | | Disk drive model number? 6268 | | 6268 DJn .37 MB 5-1/4" 48 TPI diskette (Desktop) | | Command? ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 | Page 16-4 | | Delete the DKINIT examples at the top of the page and the first | sentence of the following paragraph. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 16-5 Change the first sentence in "Full Initialization": | With the exception of diskettes that will hold IMOVE dump files | or a diskette mirror image created with FCOPY or ICOPY, you | must software format each of your disks with the FULL command | before you use that disk for the first time. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 16-6 In the "Coresident Diagnostics" section, change the question about a coresident diagnostic area: | Do you want a coresident diagnostic area [No] ? ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 16-7 Near the top of the page, change the question about a coresident diagnostic area: | Do you want a coresident diagnostic area [No] ? YES ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 16-8 After the message "*** All patterns run ***," change the question about declaring bad blocks: | Do you wish to declare any blocks bad | that are not already in the bad block table [No] ? ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 16-12 At the top of the page, change the question about declaring bad blocks: | Do you wish to declare any more blocks bad [No] ? NO | Near the bottom third of the page, change the question about declaring bad blocks: | Do you wish to declare any blocks bad | that are not already in the bad block table [No] ? ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 16-13 Near the top of the page, change the question about declaring bad blocks: | Do you wish to declare any more blocks bad [No] ? NO ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 16-15 | In the DISK command example, the question "Disk unit?" now comes | before the question "Disk drive model number?" ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 16-18 For the message "Disk ID is incorrect," add this information: | Yet another possibility is that you tried to use a command | other than FULL, DISK, or STOP while working on a disk that has | been initialized with DKINIT; however, you did not respond to | the question "Disk drive model number?" the same way as before. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 16-19 For the message "Illegal disk unit declaration," change the description: | Your response to the question "Disk unit?" was not a valid | DG/RDOS mnemonic such as DE0, DJ1, DZ10, or DA23. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 16-20 For the message "Unknown drive type," add this information: | Also, DKINIT supports some newer DAn disks; if you try to enter | one of these models' numbers, you will receive this error | message. Press New Line to continue in this case. Add this new error message: | That model is type Dxn, not type Dyn | (x and y are variables) | | Your response to the question "Disk drive model number?" is in | the utility's table of model numbers, but it is not the same | type as your response to the earlier "Disk unit?" question. | Either correct your response to the second question, or use the | DISK command to go back and correct your response to the first | question. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 17-4 Add this information to the bottom of the page: | * You can use the ICOPY utility to move a file from your | RAM disk to a magnetic storage device, and to restore | that file after you reboot DG/RDOS. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page 17-5 Change the last method of backing up your RAM disk: You can use the IMOVE utility to dump any or all of the files on your RAM disk to tapes, diskettes, or to a file on your hard disk. You can also use the utility to restore the contents of that disk after you reboot DG/RDOS. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page A-1 The first paragraph should read as follows: Tables A-1, A-2, A-3, A-4, and A-5 list information about all of the storage devices that DG/RDOS supports on DESKTOP GENERATION, DG/500, MV/1000 DC, MV/1400 DC, MV/2000 DC, MV/2500 | DC, MV/3000 DC Series, MV/5000 DC Series, MV/7800 XP, MV/9000 Series, MV/15000, and MV/18000 configurations. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page A-3 Add this item to Table A-3: 6591 Cartridge tape drive 2 Gbytes 63 UT1n See footnote 1. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page A-4 Add this note before table A-4: Note: If you are using an MV/5600 DC system, devices in Table A-4 with the device code 23 can also have the device code 63, and devices with the device code 24 can also have the device code 25. | Change the table title to "MV/3000 DC Series and MV/5000 DC Series | System Storage Devices." Add these items to Table A-4: 6591 Cartridge tape drive 2 Gbytes 23 UTn See footnote 1. | 6716 Winchester disk drive 1400 Mbytes 24 DAn | | 6762 Cartridge tape drive 2+ Gbytes 23 UTn | See footnote 1. | | 6796 3.5" Winchester disk 520 Mbytes 24 DAn | drive ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page A-5 Change the table title to "MV/7800 XP, MV/9000 Series, MV/15000, and MV/18000 System Storage Devices." ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page A-6 Change the table title to "MV/7800 XP, MV/9000 Series, MV/15000, and MV/18000 System Storage Devices." Add this item to Table A-5: 6590, Cartridge tape drive 2 Gbytes 23,63 UTn 6591 See footnote 1. ♀ How to Generate and Run DG/RDOS, 093-000470-03 9/Oct/92 Documentation Changes, Revision 02 Page A-7 Change the table title to "MV/7800 XP, MV/9000 Series, MV/15000, and MV/18000 System Storage Devices." Add these items to Table A-5: | 6716, Winchester disk drive 1400 Mbytes 24,64 DAn | 6718 25,65 | | 6762 Cartridge tape drive 2+ Gbytes 23,63 UTn | See footnote 1. | | 6796, 3.5" Winchester disk 520 Mbytes 24,64 DAn | 6799 drive 25,65 | --End of Update File--