e _vߋt ***THIS VOLUME DOES NOT CONTAIN A HARDWARE BOOTABLE SYSTEM *** VOL1D%B000HDR100010000000100 00000 00000 000000DECFILE11AEOF14444444444324410 P0 fwd%MS \ 5Bw56wU &w  P "b9)) VBEǁ  3   10ާÝ 35 w  Z)P N/ Bˋ (w` 0AUTOPATCHE1ha15MAY81135612AUTOPATCHE1 [001,001] DECFILE11A  A`}[ A`} 6& RSX-11M( AUTOPATCH E F PAGE 2FThe information in this document is subject to change without noticeFand should not be construed as a commitment by Digital EquipmentFCorporation. Digital Equipment Corporation assumes no responsibility0for any errors that may appear in this document.FThe software described in this document is furnished under a licenseFand may be used or copied only in accordance with the terms of suchlicense.FNo responsibility is assumed for the use or reliability of software onFequipment that is not supplied by DIGITAL or its affiliated companies.FCopyright c 1975, 1979, 1980, 1981 by Digital Equipment Corporation.- All Rights Reserved.p>The following are trademarks of Digital Equipment Corporation:1 DEC DECsystem-10 PDTf2 DECUS DECSYSTEM-20 RSTS1 DIGITAL DECwriter RSXe1 PDP DIBOL VMS 0 UNIBUS Edusystem VT VAX IAS$ DECnet MASSBUS F PAGE 3' CONTENTSdE Page C 1.0 INTRODUCTION 4SC 1.1 The Autopatch Process 4DC 1.2 Supported Hardware 4u: 1.3 Autopatch Revision E Documentation andC Support 5 C 1.4 Getting Ready for Autopatch 6 C 1.4.1 Autopatch Practice Run 6 C 1.5 On-Line Autopatch 7 C 1.6 Stand-Alone Autopatch 8r2 2.0 AUTOPATCH PROCEDURE FOR BIG DISKC DISTRIBUTION KITS 10 C 2.1 Notes for Big Disks 10 C 2.2 Autopatching Big Disk Distribution Kits 11 3 3.0 AUTOPATCH PROCEDURE FOR RL01/RL024C DISTRIBUTION KITS 135C 3.1 Notes for RL01/RL02 146C 3.2 Autopatching RL01/RL02 Distribution Kits 1404 4.0 AUTOPATCH PROCEDURE FOR DUAL RK05C DISTRIBUTION KITS 18 C 4.1 Notes for Dual RK05 18 ; 4.2 Autopatching the Dual RK05 Distribution C Kit 20TC 5.0 SOFTWARE DISPATCH ARTICLES 23oC 6.0 AUTOPATCH NOTES 37u aF PAGE 4#1.0 INTRODUCTION ____________ FRSX-11M Autopatch is an interactive procedure consisting of a seriesFof logical steps that apply machine-readable corrections and patchesto the RSX-11M software.FTwo Kits are used in the Autopatch procedure: the Autopatch Kit thatFis the medium carrying the machine-readable patches and corrections;Fand the Distribution Kit that is the distribution media to which.Autopatch applies the patches and corrections.FThere are two modes of operation for running Autopatch: stand aloneF(on the baseline system) and on line (on a previously generatedRSX-11M system).51.1 The Autopatch Process ___ _________ _______tFAutopatch copies files from the Autopatch Kit to temporary UFDs on aFcopy of the Distribution Kit's baseline system disk (RSXM26).FAutopatch uses files with a .COR file extension to correct theFcorresponding source files on the Distribution Kit disk(s). Files onFthe Autopatch Kit with the extensions .CMD, .ODL, .OBJ, .SYS, and .STBFare replacement files. Files having a .PAT extension are PATCH sourceFfiles. The .PAT files are included on the Autopatch Kit, andFAutopatch copies these files to all Distribution Kits (with the+exception of the RK05) for your inspection. FDue to the shortage of file headers and space on the RL01/RL02, RK05,Fand RK06 Distribution Kits, Autopatch replaces some object libraries/(.OLB) instead of replacing the objects (.OBJ).iFThe corrections and updates are assembled and/or task-built to produceFthe target operating system. You must perform a system generationF(SYSGEN) with the Distribution Kit after you do the Autopatch procedure.FThe corrections and patches in the Autopatch Kit are published in theFRSX-11M Software Dispatch (Section 5.0). To patch any layered productFsoftware, such as FORTRAN, please refer to your cover letter for instructions./1.2 Supported Hardware _________ ________ FThe Autopatch Kit is distributed on tape and disk. Table 1 lists the)hardware devices that Autopatch supports.m eD PAGE 5& Table 13 Description of Distribution Kitst> DISTRIBUTION DEVICE # OF VOLUME= KIT TYPE TYPE VOLS NAMESe> BIG DISK RK06/RK07 (DM:) 1 RSXM26) RM02/RM03 (DR:)s) RP02/RP03 (DP:)t) RP04/RP05 (DB:)p) RP06 (DB:) > RL01/RL02 RL01/RL02 (DL:) 4 RSXM26> RLUTIL> UNMSRC> MAPSRC> RK05 RK05 (DK:) 6 RSXM26> EXCSRC> UTLOBJ> PRVOBJ> DRVSRC> MCRSRCFAutopatch also supports the DSC Magtape equivalent of any of the aboveFdevice types. If you have a magnetic tape Distribution Kit, you mustFtransfer your Distribution Kit to a disk using the Disk Save andFCompress Utility (DSC). You can then apply Autopatch to the disk andFtransfer the corrected disk back to a scratch tape using DSC. CopyingFthe autopatched disk(s) to tape is not required but is useful as a8back-up procedure for your autopatched Distribution Kit.g1.3 Autopatch Revision E Documentation and Support _________ ________ _ _____________ ___ _______ FThis document describes, in separate sections, the Autopatch procedureFfor each type of Distribution Kit. Notes for the particularFDistribution Kit are included to provide you with further informationEabout the Autopatch procedure as it specifically relates to your Kit. FThe Kit notes are followed by an explanation of the series ofFSYSGEN-like questions you must answer before Autopatch begins updatingFthe files. A question (or several questions) may appear in more thanFone Kit. Whether certain questions appear depends on your hardwareFand software requirements. Read the section that pertains to your Kit as follows:i; BIG DISK DISTRIBUTION KIT SECTION 2.0n; RL01/RL02 DISTRIBUTION KIT SECTION 3.0 ; DUAL RK05 DISTRIBUTION KIT SECTION 4.0oFThe Autopatch Kit includes all the files in the machine-readable form hF PAGE 6Fthat you need to update your software. If you have a diskFconfiguration that Autopatch does not support (single driveFRL01/RL02), you can print a copy of the AUTOPATCH.CMD file and use it9as a guide to apply the patches and corrections manually. A1.4 Getting Ready for Autopatch _______ _____ ___ _________TFThe materials you need for Autopatch include a copy of your originalFDistribution Kit, the Autopatch Kit, a privileged account, and this document.6FMake a copy of your original Distribution Kit; you will run AutopatchFagainst this copy. This procedure is extremely important becauseFAutopatch deletes certain files and replaces certain object modules onFthe Distribution Kit. If you do not make a copy of your DistributionFKit, you will be unable to restart Autopatch if any mistakes occurduring the procedure.A% NOTE7 The Autopatch procedure is a cumulativet7 process and must be applied to a copy ofs7 your original Distribution Kit. Youp7 cannot apply Autopatch Revision E to ao7 Distribution Kit that has beeno& previously Autopatched.FFollow the steps outlined in the sections "On-Line Autopatch" orF"Stand-Alone Autopatch" after you make a copy of your DistributionFKit. The set-up procedure is the same for each type of DistributionKit.f1.4.1 Autopatch Practice Run - After you complete the set-up _________ ________ ___Fprocedure for Autopatch, you can do a practice run by invoking4AUTOPATCH.CMD using the /NOMCR switch. For example: >@AUTOPATCH/NOMCRFAutopatch runs, but does not execute the MCR command lines. If youFhave the dual RK05 or the RL01/RL02 Distribution Kit, you do not needFto load the additional disks during the practice procedure. ReplyFthat the disks are ready and successfully mounted when Autopatch asksthese questions. tF PAGE 7-1.5 On-Line Autopatch _______ _________U5To set up for an on-line Autopatch, do the following: + 1. Log on under a privileged account.nF 2. Copy the Distribution Kit to be used by the Autopatch procedure. F 3. Load the device driver to be used for the Autopatch Kit (if necessary).F 4. Allocate a drive for the Distribution Kit, and place the< baseline disk (RSXM26) in the drive, write enabled.F 5. Allocate a drive for the Autopatch Kit, and place the Kit in$ the drive, write protected.@ 6. Mount the baseline disk. For example: MOU ddu:RSXM26.F 7. Mount the Autopatch Kit (if a disk) with the label AUTOPATCHE1.eF 8. Assign the baseline system disk to the pseudo device SY:.# For example: ASN ddu:=SY:AF 9. Set the UIC to [200,200] if it is not already set. For% example: SET /UIC=[200,200] ; 10. Install PIP or FLX if it is not already installed.d" For a disk Autopatch Kit: >INS $PIP6" For a tape Autopatch Kit: >INS $FLX F 11. Copy the Autopatch command file AUTOPATCH.CMD to the baselineF disk as follows (where ddu: indicates the Autopatch device):" For a disk Autopatch Kit:( >PIP /NV=ddu:AUTOPATCH.CMD" For a tape Autopatch Kit:+ >FLX /RS=ddu:AUTOPATCH.CMD/DO0F 12. Logically dismount the Autopatch Kit if it is a disk. For example: DMO ddu::F If the Autopatch Kit is on a disk, Autopatch remounts theF disk when it needs it. If Autopatch is on tape, you may CF PAGE 84 leave it up until the end of the procedure.) 13. Invoke AUTOPATCH.CMD as follows:; >@AUTOPATCH (For practice: @AUTOPATCH/NOMCR)u=Proceed to the appropriate section for your Distribution Kit.i51.6 Stand-Alone Autopatch ___________ _________ 8To set up for a stand-alone Autopatch, do the following:F 1. Copy the Distribution Kit to be used by the Autopatch procedure. F 2. Place the baseline disk (RSXM26) in the appropriate unit, write enabled.dF 3. Hardware bootstrap the system, using the device that contains the baseline disk.tF 4. If you intend to generate a mapped system, and you have anF RK05, RK06/RK07, or an RL01/RL02 Distribution Kit, make theF mapped baseline system (in UIC [1,54]) hardware bootable;F you must run Autopatch from the mapped baseline system. This is done as follows: >INS $BOO;-1 >BOO [1,54]RSX11M RSX-11M V3.2 BL26  .y .a .bF The start-up command prompts you for the time and date.2 Issue a CTRL/Z and the following command: ^Z > SAV /WBmF To generate an unmapped system, make the unmapped baselineF system (in UIC [1,50]) hardware bootable; you must runF Autopatch from the unmapped baseline system. This is done as follows:  >INS $BOO;-1 >BOO [1,50]RSX11M  RSX-11M V3.2 BL26  .u .o . F PAGE 9F The start-up command prompts you for the time and date.2 Issue a CTRL/Z and the following command: ^Z >SAV /WBF 5. After answering the start-up questions, remove the installedD task ...AT. and install BIGIND. Specify a priority of 10.! This is done as follows:2 >REM ...AT." >INS $BIGIND/PRI=10.% NOTE 7 You will receive the following message, 7 which you should ignore: "INS-- WARNING 3 - PRIVILEGED TASK OVERMAPS I/O PAGE"mF 6. Load the device driver to be used for the Autopatch Kit (if necessary).? 7. Place the Autopatch Kit in the drive, write protected.DF 8. Mount the Autopatch Kit (if a disk) with the label AUTOPATCHE1.F 9. Set the UIC to [200,200] if it is not already set. For& example: SET /UIC=[200,200].; 10. Install PIP or FLX if it is not already installed.e" For a disk Autopatch Kit: >INS $PIP " For a tape Autopatch Kit: >INS $FLXpF 11. Copy the Autopatch command file AUTOPATCH.CMD to the baselineF disk as follows (where ddu: indicates the Autopatch device):" For a disk Autopatch Kit:( >PIP /NV=ddu:AUTOPATCH.CMD" For a tape Autopatch Kit:+ >FLX /RS=ddu:AUTOPATCH.CMD/DO0F 12. Logically dismount the Autopatch Kit if it is a disk. For F PAGE 10 example: DMO ddu: F If the Autopatch Kit is on disk, Autopatch remounts the diskF when it needs it. If Autopatch is on tape, you may leave it+ up until the end of the procedure.c- 13. Invoke the AUTOPATCH.CMD as follows:D; >@AUTOPATCH (For practice: @AUTOPATCH/NOMCR)S=Proceed to the appropriate section for your Distribution Kit.co2.0 AUTOPATCH PROCEDURE FOR BIG DISK DISTRIBUTION KITS _________ _________ ___ ___ ____ ____________ ____ FThe Autopatch procedure for Big Disk Distribution Kits takesFapproximately 30 minutes for disk-distributed Autopatch media, andFapproximately 45 minutes for magnetic tape-distributed Autopatchmedia.12.1 Notes for Big Disks _____ ___ ___ _____UFThe big disk Distribution Kits require that you have an RP04/RP05/RP06?drive, RM02/RM03 drive, or an RK06/RK07 drive to run Autopatch.EFThe big disk Autopatch Kits include a new option. You may now chooseFto retain the original .MAC, .OLB, .ODL, and .CMD files from your V3.2FDistribution Kit rather than purge them automatically. This optionFmakes it easier for you to manually apply the new patches from theFSoftware Dispatch. This feature is available on all big disks except<the RK06. The RK06 lacks sufficient space for this feature.FIf your Distribution Kit is an RK06, Autopatch deletes files from theFunused baseline system UIC in order to provide sufficient disk spaceFfor the SYSGEN following Autopatch. On a mapped system the unused UIC>is [1,50], and on an unmapped system the unused UIC is [1,54].FThe baseline data bases for the RP04/RP05/RP06 and RM02/RM03 on theFRSX-11M V3.2 Distribution Kits have an invalid bit set in the firstFcharacteristics word of the devices' UCB. Because UFD requires thisCbit to be clear for a Files-11 device, UFD generates the following:s UFD -- NOT FILES-11 DEVICE FIf your Distribution Kit is an RP04/RP05/RP06 or an RM02/RM03, and youFare performing a stand-alone Autopatch, perform one of the sequencesFlisted below, depending on the type of Distribution Kit that you have.FFirst, boot the appropriate baseline system. Then, perform the following: RP04/5/6 DISTRIBUTION KITSh eF PAGE 11 Unmapped Baseline% >OPEN 25442 1 025442 140110 / 140010 % >OPEN 25500 u1 025500 140110 / 140010  >SAVE Mapped Baseline% >OPEN 33476 1 033476 140110 / 140010 p% >OPEN 33534 I1 033534 140110 / 140010  >SAVE RM02/3 DISTRIBUTION KITSU Unmapped Baseline% >OPEN 25442 1 025442 140110 / 140010 % >OPEN 25500 1 025500 140110 / 140010  >SAVE Mapped Baseline% >OPEN 33376 1 033376 140110 / 140010 % >OPEN 33434 1 033434 140110 / 140010  >SAVEY2.2 Autopatching Big Disk Distribution Kits ____________ ___ ____ ____________ ____ FAutopatch asks the following questions when updating the Big DiskDistribution Kit. C* 1. Have you made a copy of the disk(s) to be patched? [Y/N]:AF Make a copy of your Distribution Kit. Subsequent releases ofF Autopatch will require a fresh copy of the Distribution Kit.F If you do not make a copy of the Distribution Kit and youF make a mistake in the Autopatch procedure, you will lose your only copy of the Kit.5 A yes allows you to continue with Autopatch.qF A no causes Autopatch to exit. (You can restart Autopatch by typing @AUTOPATCH.)F* 2. What type of Distribution Kit do you have (A, B, or C)? [S]: iF PAGE 12F Respond to this question with an upper-case "A". "A"1 indicates the Big Disk Distribution Kit.e% NOTE 7 Question 3 is not asked during theo7 Autopatch procedure for Big Diskh7 Distribution Kits. Questions 4, 5, and 7 6 are asked only if your Big Disk + Distribution Kit is an RK06. F* 4. Are you running Autopatch stand alone (on the baseline system)? [Y/N]: = Answer yes if you are running Autopatch stand alone. 8 Answer no if you are running Autopatch on line.F* 5. Are you going to perform a SYSGEN on a mapped system? [Y/N]:F Question 6 appears one of two ways depending on your response to this question.; If you are generating a mapped system, answer yes.. If you answered yes, question 6 asks:>* 6. Should the contents of UIC [1,50] be deleted? [Y/N]:6 A yes deletes the contents of the unused UIC.F A no causes Autopatch to exit. (You can restart Autopatch by typing @AUTOPATCH.); If you answered no to question 5, question 6 asks:?>* 6. Should the contents of UIC [1,54] be deleted? [Y/N]:6 A yes deletes the contents of the unused UIC.F A no causes Autopatch to exit. (You can restart Autopatch by typing @AUTOPATCH.)D* 7. When ready, enter the Autopatch device and unit (ddu:) [S]:F Respond with the mnemonic and unit number of the device to be$ used for the Autopatch Kit.= If your device is a disk, Autopatch asks question 8.dF If your device is a magnetic tape, Autopatch asks question 9.: Autopatch mounts the Autopatch Kit at this point.=* 8. Did the AUTOPATCHE1 disk mount successfully? [Y/N]:t6 A yes causes Autopatch to prompt question 10. )F PAGE 134 A no causes Autopatch to repeat question 7.F If you specify a MS device (the mnemonic for a TS11 tapeF drive), Autopatch defaults to 1600 BPI and advances to question 10.oF Question 9 appears only if you indicated that your device is a MM or MT magtape:-* 9. Is the tape a 1600 BPI tape? [Y/N]:* A yes indicates 1600 BPI magtape." A no defaults to 800 BPI.F* 10. Should .PAT, .COR, .CMD, and .ODL Autopatch files also be deleted? [Y/N]:o< A yes deletes the .PAT, .COR, .CMD, and .ODL files." A no retains these files.F Autopatch copies the Autopatch files to temporary UFDs on theF baseline disk in order to perform the Autopatch process.F These files occupy space that is at a premium on the RK06F Distribution Kit; therefore, it is recommended that youF delete these files from the disk before performing theF SYSGEN. The .MAC, .OBJ, .OLB, .SYS, and .STB Autopatch filesF are deleted from these UFDs at the conclusion of Autopatch.F (The files remain available for inspection on the Autopatch Distribution media.)sF* 11. Should old .MAC, .OLB, .CMD, .ODL, and .OBJ files be& automatically purged? [Y/N]:F A yes purges the old .MAC, .OLB, .CMD, .ODL, and .OBJ filesF from the Distribution Kit. A new version is created when+ Autopatch applies the corrections. " A no retains these files.F Autopatch does not ask this question for an RK06 DistributionF Kit. It automatically purges these files because of space considerations.FAt this point the actual Autopatch process begins and requires noFfurther input from you. Autopatch creates UFDs on the baseline disk,Fcopies the Autopatch files to the UFDs, makes the corrections, and;exits. You will see an @ when Autopatch is finished.aq3.0 AUTOPATCH PROCEDURE FOR RL01/RL02 DISTRIBUTION KITS _________ _________ ___ _________ ____________ ____ FThe Autopatch procedure for RL01/RL02 Distribution Kits takesFapproximately 75 minutes for disk-distributed Autopatch media, andFapproximately 90 minutes for magnetic tape-distributed Autopatchmedia. F PAGE 1413.1 Notes for RL01/RL02 _____ ___ _________EFThe RL01/RL02 Distribution Kit requires two RL01/RL02 drives on yourFsystem to run Autopatch; one drive contains the baseline diskF(RSXM26), and the other drive is for the RLUTIL, UNMSRC, and MAPSRCFdisks. If your system does not have two drives, use the AUTOPATCH.CMD;file as a guide to patching your Distribution Kit manually.iFAutopatch allows you to patch mapped sources, unmapped sources, orFyour entire Distribution Kit. It asks if you intend to generate aFmapped system, and depending on what your response is, it also asks if9you wish to patch the system you do not plan to generate. FBefore performing an RL01/RL02 Autopatch, you must have a scratchFRL01/RL02 initialized with a label. Autopatch prompts you for theFunit number and label of the scratch disk. It then mounts the diskFand copies the following baseline system tasks to it: ZAP.TSK,FEDT.TSK, EDI.TSK, PAT.TSK, DMP.TSK, VFY.TSK, CMP.TSK, BAD.TSK, and theFstand-alone system [1,51]BADSYS. Autopatch deletes the remainingFstand-alone systems in [1,51] and replaces them later in the patchingFprocess. At the end of the patching process, Autopatch restores to@the baseline system the files that it wrote to the scratch disk.FTo provide sufficient space for the Autopatch process and the SYSGENFthat follows, Autopatch deletes the contents of UIC [1,51] from theFUnmapped Source (UNMSRC) and Mapped Source (MAPSRC) disks. UIC [1,51]Fconsists of stand-alone systems and associated .STB files. TheFupdated stand-alone systems and their associated .STB files are copiedFonly to the baseline disk. Autopatch also transfers some unused filesFfrom the RLUTIL, UNMSRC, and MAPSRC disks to the baseline disk. ItFtransfers the files back to their original disk after it patches thedisk.NFAutopatch deletes nonprivileged tasks from the unused system UIC onFthe utility disk (RLUTIL). On a mapped system the unused UIC is;[1,50], and on an unmapped system the unused UIC is [1,54].lFIn addition, Autopatch deletes [1,54] CMP.TSK, EDT.TSK, and ZAP.TSKFfrom MAPSRC. You can restore these files from the baseline disk to"MAPSRC after the SYSGEN completes.[3.2 Autopatching RL01/RL02 Distribution Kits ____________ _________ ____________ ____ FAutopatch asks the following questions when updating the RL01/RL02Distribution Kit. C* 1. Have you made a copy of the disk(s) to be patched? [Y/N]: F Make a copy of your Distribution Kit. Subsequent releases ofF Autopatch will require a fresh copy of your Distribution Kit.F If you do not make a copy of the Distribution Kit and youF make a mistake in the Autopatch procedure, you will lose your( only available copy of the Kit. _F PAGE 155 A yes allows you to continue with Autopatch.cF A no causes Autopatch to exit. (You can restart Autopatch by typing @AUTOPATCH.)F* 2. What type of Distribution Kit do you have? (A, B, or C)? [S]: F Respond to this question with an upper-case "B". "B"2 indicates the RL01/RL02 Distribution Kit.=* 3. Do you have a second RL01/RL02 drive to use? [Y/N]: " A yes prompts question 4.F A no causes Autopatch to exit. (You can restart Autopatch by typing @AUTOPATCH.)F* 4. Are you running Autopatch stand alone (on the baseline system)? [Y/N]: = Answer yes if you are running Autopatch stand alone. 8 Answer no if you are running Autopatch on line.9* 5. Are you going to SYSGEN a mapped system? [Y/N]:2F Questions 6 and 7 appear one of two ways depending on your# response to this question.q; If you are generating a mapped system, answer yes.e. If you answered yes, question 6 asks:@* 6. Do you want to patch UNMSRC (unmapped sources)? [Y/N]:F A yes causes Autopatch to patch the RL01/RL02 baseline,* RLUTIL, UNMSRC, and MAPSRC disks.F A no causes Autopatch to patch only the RL01/RL02 baseline," RLUTIL, and MAPSRC disks.; If you answered no to question 5, question 6 asks: >* 6. Do you want to patch MAPSRC (mapped sources)? [Y/N]:F A yes causes Autopatch to patch the RL01/RL02 baseline,* RLUTIL, UNMSRC, and MAPSRC disks.F A no causes Autopatch to patch only the RL01/RL02 baseline," RLUTIL, and UNMSRC disks.< If you answered yes to question 5, question 7 asks:>* 7. Should the contents of UIC [1,50] be deleted? [Y/N]:6 A yes deletes the contents of the unused UIC.F A no causes Autopatch to exit. (You can restart Autopatch by typing @AUTOPATCH.) F PAGE 16; If you answered no to question 5, question 7 asks:t>* 7. Should the contents of UIC [1,54] be deleted? [Y/N]:6 A yes deletes the contents of the unused UIC.F A no causes Autopatch to exit. (You can restart Autopatch by typing @AUTOPATCH.)?* 8. Enter the label of your scratch RL01/RL02 [S R:1.-9.]:pF Enter the label with which you have initialized your scratch= disk. The label may be one to nine characters long. F* 9. Enter the unit number of the drive containing a scratch RL01/RL02 [0]: F Respond only with the unit number of the device to be used for a scratch disk..* 10. Did DLn: mount successfully? [Y/N]:F A yes allows Autopatch to create UFDs and to copy baselineF system task images not needed by Autopatch to the scratch disk.D A no repeats question 9 until the disk mounts successfully.F Autopatch dismounts the scratch disk after the files are copied to it.D* 11. When ready, enter the Autopatch device and unit (ddu:) [S]:F Respond with the mnemonic and unit number of the device to be$ used for the Autopatch Kit.> If your device is a disk, Autopatch asks question 12.F Autopatch asks question 13 only if you specify that yourF device is a MM or MT magtape. If you specify a MS deviceF (the mnemonic for the TS11 tape drive), Autopatch defaults to. 1600 BPI and advances to question 14.F If the Autopatch Kit is a disk, Autopatch mounts it at this point.w=* 12. Did the AUTOPATCHE1 disk mount successfully? [Y/N]:e6 A yes causes Autopatch to prompt question 14.5 A no causes Autopatch to repeat question 11.kE If the Autopatch Kit is on tape, Autopatch asks question 13. -* 13. Is the tape a 1600 BPI tape? [Y/N]: * A yes indicates 1600 BPI magtape." A no defaults to 800 BPI. F PAGE 17F* 14. Should .PAT, .COR, .CMD, and .ODL Autopatch files also be deleted? [Y/N]:yF A yes deletes the .PAT, .COR, .CMD, and .ODL files before Autopatch exits.t" A no retains these files.F Autopatch copies the Autopatch files to temporary UFDs on theF baseline disk in order to perform the Autopatch process.F These files occupy space that is at a premium on the RL01F Distribution Kit; therefore, it is recommended that youF delete the files from the disk prior to performing theF SYSGEN. The .MAC, .OBJ, .OLB, .SYS, and .STB Autopatch filesF are deleted from the UFDs at the conclusion of Autopatch.F (The files remain available for inspection on the Autopatch Distribution media.)sF Question 15 appears only if your Autopatch Kit is not an RL01/RL02.aF* 15. What will be your second RL01/RL02 device and unit (ddu:)? [S]:h# Enter the device and unit. F At this point, Autopatch begins patching the baseline disk of( the RL01/RL02 Distribution Kit.F After Autopatch finishes patching the baseline disk, question> 16 asks if the next RL01/RL02 disk, RLUTIL, is ready:4* 16. Is the RLUTIL disk ready in (ddu:)? [Y/N]:# A yes prompts question 17.iF A no causes Autopatch to repeat question 16. It repeatsF question 16 until the disk is ready and your response is yes.8* 17. Did the RLUTIL disk mount successfully? [Y/N]:2 A yes allows patching of the RLUTIL disk.5 A no causes Autopatch to repeat question 16.eF Autopatch repeats questions 16 and 17 for the remaining2 RL01/RL02 disk(s): UNMSRC and/or MAPSRC.FAt this point, the actual Autopatch process begins and requires onlyFthat you mount the remaining disks. Questions 18 and 19 prompt you toFmount these disks. Autopatch creates UFDs on the baseline disk,Fcopies the Autopatch files to the UFDs, and makes the corrections.FBefore Autopatch exits, it is necessary to restore the files saved onFthe scratch disk. Questions 22 and 23 prompt you for thisFinformation. (If you are patching only three disks, questions 20 and$21 prompt you for this information.)F* 22. Is the scratch disk RL01/RL02, "label", ready in DLn:? sF PAGE 18 [Y/N]:b# A yes prompts question 23. F A no repeats question 22 until the disk is ready and your response is yes.t.* 23. Did DLn: mount successfully? [Y/N]:F A yes causes Autopatch to copy the files from the scratch% disk to the baseline system.F A no repeats question 22 until the disk is successfully mounted.,FAt this point, Autopatch copies the files from the scratch disk to theDbaseline system. You will see an @ when Autopatch is finished.q4.0 AUTOPATCH PROCEDURE FOR DUAL RK05 DISTRIBUTION KITS _________ _________ ___ ____ ____ ____________ ____3FThe Autopatch procedure for Dual RK05 Distribution Kits takesFapproximately 90 minutes for disk-distributed Autopatch media, andFapproximately two hours for magnetic tape-distributed Autopatch media.14.1 Notes for Dual RK05 _____ ___ ____ ____cFThe RK05 Distribution Kit requires two RK05 drives on your system toFrun Autopatch; one drive contains the baseline disk (RSXM26), and theFother drive is for the EXCSRC, UTLOBJ, PRVOBJ, DRVSRC, and MCRSRCFdisks. If your system does not have two drives, use the AUTOPATCH.CMD;file as a guide to patching your Distribution Kit manually.iFAutopatch deletes files from the unused baseline system UIC in orderFto provide sufficient disk space for the Autopatch process. On aFmapped system the unused UIC is [1,50], and on an unmapped system theunused UIC is [1,54].uFBefore performing an RK05 Autopatch, you must have a scratch RK05Finitialized with a label. Autopatch prompts you for the unit numberFand label of the scratch disk. It then mounts the disk and copies theFfollowing baseline system tasks to it: ZAP.TSK, EDT.TSK, EDI.TSK,FPAT.TSK, DMP.TSK, VFY.TSK, CMP.TSK, BAD.TSK, and the stand-aloneFsystem [1,51]BADSYS. Autopatch deletes the remaining stand-aloneFsystems in [1,51] and replaces them later in the patching process. AtFthe end of the patching process, Autopatch restores to the baseline3system the files that it wrote to the scratch disk.pFTo replace certain object modules during the Autopatch process,FAutopatch needs the Librarian task (LBR.TSK). The Librarian task isFnot on the baseline disk; therefore, if you are running in aFstand-alone mode, Autopatch copies it from the Autopatch Kit to theFappropriate baseline UIC. If LBR is not installed, Autopatch installsit at this point.. tF PAGE 19FTo build certain tasks, SYSGEN Phase III requires the newF[1,1]VMLIB.OLB which Autopatch provides. Because VMLIB.OLB is inF[1,1] of the privileged object disk (PRVOBJ) rather than in [1,1] onFthe baseline disk, Autopatch copies VMLIB.OLB from PRVOBJ to [1,1] onthe baseline disk.FTo ensure that enough room exists on the MCR source disk (MCRSRC),FAutopatch copies some unused files to [200,200] on the baseline diskFbefore patching the MCR source disk. Autopatch then deletes theseFfiles from the MCRSRC disk, patches the MCRSRC disk, copies the filesFback to the MCRSRC disk, and deletes them from [200,200] on theFbaseline disk. Autopatch does not copy the file SDSOVFDT.MAC back toFMCRSRC because of a lack of space on that disk. This file is notFneeded during the SYSGEN process. You may obtain the file from yourDistribution Kit. FBefore updating the MCRSRC disk, Autopatch deletes all .COR files inFUICs [1,60] and [1,64] because all of the necessary corrections inFthose areas have been applied by that point. The remaining .COR filesFand the Autopatch UFDs are deleted when the Autopatch procedure hasbeen completed.eFFile header space is at a premium on the baseline disk; therefore, itFis necessary to delete at least seven of the loadable device driverFtasks and their corresponding .STB files. After question 6, AutopatchFpauses and allows you to delete the drivers. Follow the exampleFprovided in the procedure and delete the drivers that are not neededFin your hardware configuration, and/or that you will not need toFperform SYSGEN. Also, due to the shortage of header space, .PAT filesFare not copied to this disk. These files are, however, provided on)the Autopatch medium for your inspection.tFBecause contiguous space is at a premium on RK05s, you may need toFcomplete a few extra procedures during SYSGEN to successfully generateFyour system. In SYSGEN Phase II, SYSGEN asks if you want to edit anyFprivileged tasks. Answer yes so that SYSGEN will pause, then create/your system image using the following commands:N >SET /UIC=[1,54]a* >PIP RSX11M.SYS/NV/CO/BL:n=RSX11M.TSK >SET /UIC=[1,24]eResume SYSGEN as it directs.)The "n" in the PIP command is as follows:t' n=(memory size selected * 4.) + 2.mFSYSGEN pauses later to allow you to create your system image, resumeDSYSGEN immediately since you already have created your system image.FTo generate a multiuser system, you may also have to delete a fewFtasks from the baseline. (You may want to delete some of the tasksFthat Autopatch copies from the baseline to the scratch disk.) If you KF PAGE 20Fdecide to include ANSI support, you will have problems finding enough8continguous free space in which to complete your SYSGEN.a4.2 Autopatching the Dual RK05 Distribution Kit ____________ ___ ____ ____ ____________ ___tC* 1. Have you made a copy of the disk(s) to be patched? [Y/N]:aF Make a copy of your Distribution Kit. Subsequent releases ofF Autopatch will require a fresh copy of your Distribution Kit.F If you do not make a copy of your Distribution Kit and youF make a mistake in the Autopatch procedure, you will lose your( only available copy of the Kit.5 A yes allows you to continue with Autopatch. F A no causes Autopatch to exit. (You can restart Autopatch by typing @AUTOPATCH.)F* 2. What type of Distribution Kit do you have (A, B, or C)? [S]:F Respond to this question with an upper-case "C". "C"2 indicates the Dual RK05 Distribution Kit.% NOTE 7 Question 3 is not asked during thes7 Autopatch procedure for Dual RK05 ! Distribution Kits.hF* 4. Are you running Autopatch stand alone (on the baseline system)? [Y/N]:A= Answer yes if you are running Autopatch stand alone.(8 Answer no if you are running Autopatch on line.9* 5. Are you going to SYSGEN a mapped system? [Y/N]:aF Question 6 appears one of two ways depending on your response to this question.; If you are generating a mapped system, answer yes.e. If you answered yes, question 6 asks:>* 6. Should the contents of UIC [1,50] be deleted? [Y/N]:6 A yes deletes the contents of the unused UIC.F A no causes Autopatch to exit. (You can restart Autopatch by typing @AUTOPATCH.); If you answered no to question 5, question 6 asks:  ]F PAGE 21>* 6. Should the contents of UIC [1,54] be deleted? [Y/N]:6 A yes deletes the contents of the unused UIC.F A no causes Autopatch to exit. (You can restart Autopatch by typing @AUTOPATCH.)F After question 6, Autopatch pauses and asks you to deleteF seven device driver tasks to provide room for Autopatch. IfD PIP is not installed, you need to install it at this point.:* 7. Enter the label of your scratch RK05 [S R:1.-9.]:F Enter the label with which you have initialized your scratch= disk. The label may be one to nine characters long. F* 8. Enter the unit number of the drive containing a scratch RK05 (ddu:):F Respond only with the unit number of the device to be used for the scratch disk..* 9. Did DKn: mount successfully? [Y/N]:F A yes allows Autopatch to create UFDs and to copy baselineF system task images not needed by Autopatch to the scratch disk.F A no repeats question 8 until the disk is successfully mounted.tF Autopatch dismounts the scratch disk after the files are copied to it.D* 10. When ready, enter the Autopatch device and unit (ddu:) [S]:F Respond with the mnemonic and unit number of the device to be$ used for the Autopatch Kit.F If your device is a disk, Autopatch asks question 11.F Question 12 asks if your tape is 1600 BPI. It appears onlyF if you indicate that your device is an MM or MT magtape. IfF you specify a MS device (the mnemonic for the TS11 tapeF drive), Autopatch defaults to 1600 BPI and advances to question 14.nF If the Autopatch Kit is a disk, Autopatch mounts it at this point. <* 11. Did the AUTOPATCHE1 disk mount sucessfully? [Y/N]:6 A yes causes Autopatch to prompt question 14.5 A no causes Autopatch to repeat question 10.nD If the Autopatch Kit is a tape, Autopatch asks question 12.-* 12. Is the tape a 1600 BPI tape? [Y/N]:n nF PAGE 22* A yes indicates 1600 BPI magtape." A no defaults to 800 BPI.F If your Distribution Kit is an RK05, question 13 does notF appear. Question 14 does not appear if your Autopatch Kit is an RK05.iD* 14. What will be your second RK05 device and unit (ddu:)? [S]:# Enter the device and unit.pF At this point, patching of the Dual RK05 Distribution Kit7 begins with an Autopatch of the baseline disk. F After Autopatch finishes patching the baseline disk, questionF 15 asks if the next RK05 disk, the Executive sources disk (EXCSRC), is ready:4* 15. Is the EXCSRC disk ready in (ddu:)? [Y/N]:# A yes prompts question 16.F A no repeats question 15 until the disk is ready and your response is yes.n8* 16. Did the EXCSRC disk mount successfully? [Y/N]:2 A yes allows patching of the EXCSRC disk.F A no repeats question 15 until the disk is successfully mounted. F After Autopatch patches the EXCSRC disk, it repeats questionsF 15 and 16 for each of the four remaining disks: UTLOBJ,$ PRVOBJ, DRVSRC, and MCRSRC.FAt this point, the actual Autopatch process begins and requires onlyFthat you mount the remaining disks. Questions 17 through 24 promptFyou to mount these disks. Autopatch creates UFDs on the baselineFdisk, copies the Autopatch files to the UFDs, and makes theFcorrections. Before Autopatch exits, it is necessary to restore theFfiles saved on the scratch disk. Questions 25 and 26 prompt you forthe information.=* 25. Is the scratch RK05, "label," ready in DKn:? [Y/N]:t# A yes prompts question 26.sF A no repeats question 25 until the disk is ready and your response is yes.t.* 26. Did DKn: mount successfully? [Y/N]:F A yes causes Autopatch to copy the files from the scratch% disk to the baseline system.oF A no repeats question 26 until the disk is successfully mounted.u iF PAGE 23FAt this point, Autopatch copies the files from the scratch disk to theDbaseline system. You will see an @ when Autopatch is finished.?5.0 SOFTWARE DISPATCH ARTICLES ________ ________ ________lFThe following tables list "optional," "mandatory," "feature,"F"restriction," "note," and patch correction files published in theFRSX-11M Software Dispatch for the months September, 1979 through7April, 1981. From left to right the table entries are: F 1. Reference - The Software Dispatch article reference number.F The letters following the sequence numbers and their meanings are:e( O - The patch is optional.) M - The patch is mandatory.i6 F - The patch is a new software feature.3 R - The article states a restriction. = N - The article notes additional documentation.pF 2. Component - The software component to which the patch or% correction is to be applied.wF 3. Autopatch File - The UFD and file name for the Autopatch file.F 4. Autopatch Action - The RSX-11M utility that Autopatch uses toF make the patch. The 3-letter mnemonics have the following meanings:F o LBR denotes the Librarian Utility Program. The fileF on the Autopatch Kit is an object file. AutopatchF uses LBR to replace the incorrect object with the" Autopatch object.F o PIP denotes the Peripheral Interchange Program.F Autopatch uses PIP to delete the file on yourC Distribution Kit and to replace it with a new one.nF o SLP denotes the Source Language Input Program.F Autopatch uses SLP to apply the Autopatch correctionF file to the source or command file on your" Distribution Kit.F The files on the Autopatch Kit are cumulative. Therefore,F the patches or corrections for any given month also containF any patches or corrections to that file (if any) from any previous month. aF PAGE 24& Table 2> Autopatch Files from Software Dispatch, September, 1979Software DispatchnGArticle Reference Component Autopatch Files Autopatch Actionf@2.1.1.1 M EXEC [11,60]DRSED.COR SLP@3.1.2.1 M DRIVER [11,60]MTDRV.COR SLP@3.1.4.1 M DRIVER [11,60]LADRV.COR SLP@3.1.4.2 M DRIVER [11,60]IPDRV.COR SLP@5.1.4.1 M DMO [12,60]DISMNT.COR SLP@ [1,60]MCR.OLB PIP@ [1,64}MCR.OLB PIPI5.1.10.1 M (Superseded by 5.1.10.1 M article of November, 1979) @5.2.5.1 F K-SERIES [45,60]]KGHIST.COR SLP@5.7.2.2 R CDA [1,60]CDA.OLB PIP) Table 3 @ Autopatch Files from Software Dispatch, October, 1979Software Dispatch[GArticle Reference Component Autopatch Files Autopatch ActionRC2.1.6.1 M (Superseded by 2.1.6.1 M article of May, 1980) @3.2.1.2 F FCSRES [200,60]FCSRES.COR SLP@5.1.17.1 M BRU [1,60]BRU.OLB PIPH5.2.6.1 F (Superseded by 5.2.6.1 F article of December, 1979)) Table 4 @ Autopatch Files from Software Dispatch, November, 1979Software DispatchtGArticle Reference Component Autopatch Files Autopatch Actiont@2.1.1.2 R EXEC [11,60]DRGEF.COR SLP K PAGE 25 @2.1.5.1 F EXEC [11,60]LOADR.COR SLP@2.1.6.2 M EXEC [11,60]DRSPW.COR SLP@3.1.1.1 M DRIVER [11,60]DBDRV.COR SLP@3.1.3.1 M DRIVER [11,60]TTATT.COR SLP@ [11,60]TTFP.COR SLP@ [11,60]TTMIS.COR SLP@ [11,60]TTMOD.COR SLP@ [11,60]TTODN.COR SLP@ [11,60]TTOIS.COR SLP@ [11,60]TTSUB.COR SLP@ [11,60]TTYH.COR SLP@5.1.7.1 M FLX [33,60]DOSRSX.OBJ LBR@5.1.9.1 M LBR [42,60]LBRIN.OBJ LBR@5.1.9.2 M LBR [42,60]LBRCM.OBJ LBR@ [42,60]LBRWHD.OBJ LBR@5.1.10.1 M MOU [12,60]MOUPAR.COR SLP@ [12,60]MOUPAR.OBJ LBR@ [12,60]MPARMT.COR SLP@ [12,60]MPARMT.OBJ LBR@ [12,60]MMTOV.COR SLP@ [12,60]MMTOV.OBJ LBR@ [12,60]MDISOV.COR SLP@ [12,60]MDISOV.OBJ LBR@ [12,64]MOUPAR.OBJ LBR@ [12,64]MPARMT.OBJ LBR@ [12,64]MMTOV.OBJ LBR@ [12,64]MOISOV.OBJ LBR@ MOU (INI) [12,60]INIGCL.COR SLP@ [12,60]INIGCL.OBJ LBR@ [12,64]INIGCL.OBJ LBR@5.3.3.1 M TKB [1,60]SLOTKBBLD.ODL PIP) Table 5R@ Autopatch Files from Software Dispatch, December, 1979Software Dispatch GArticle Reference Component Autopatch Files Autopatch Action @1.1.2.2 R DRIVER [11,60]MSDRV.MAC;2 PIP@ (EXEC) [11,60]CRASH.COR SLP@ (VMR) [1,60]VMR.OLB PIP@ (DSC) [163,60]DSCS16.SYS PIP@ [163,60]DSCS16.STB PIP K PAGE 26E2.1.6.3 M (Superseded by 2.1.6.3 M article of March, 1980) @2.1.6.4 F EXEC [11,60]INITL.COR SLP@3.1.3.2 M DRIVER [11,60]CRDRV.COR SLP@3.1.5.1 M DRIVER [11,60]XMDRV.COR SLP@5.1.6.1 M DSC [63,60]DSCS8.SYS PIP@ [63,60]DSCS8.STB PIP@5.2.6.1 F SYSTEM LIB. [55,60]OVCTR.OBJ LBR@5.2.6.2 M SYSTEM LIB. [52,60]CRGF.OBJ LBR@ [52,60]ELGF.OBJ LBR) Table 6.@ Autopatch Files from Software Dispatch, January, 1980Software DispatchEGArticle Reference Component Autopatch Files Autopatch Action D1.1.1.1 M (Superseded by 1.1.1.1 M article of June, 1980)@2.1.1.3 M EXEC [11,60]DRDSP.COR SLP@ [11,60]DRCMT.COR SLPE3.1.3.3 M (Superseded by 3.1.3.3 M article of March, 1980)F@3.1.3.4 M DRIVER [11,60]CRDRV.COR SLP@3.1.4.3 M DRIVER [11,60]ICDRV.COR SLP@5.1.8.1 M INI [12,60]INIGCL.COR SLP@ [12,60]INIGCL.OBJ LBR@ [12,64]INIGCL.OBJ LBR) Table 7 @ Autopatch Files from Software Dispatch, February, 1980Software DispatchdGArticle Reference Component Autopatch Files Autopatch Action @1.1.2.4 F DRIVER [11,60]DRDRV.COR SLP@ [11,60]MMDRV.COR SLP@2.1.6.6 R EXEC [11,60]BFCTL.COR SLP 6K PAGE 27J@2.2.1.1 F BYE [12,60]BYE.COR SLP@ [1,60]MCR.OLB PIP@ [1,64]MCR.OLB PIP@ HELLO [12,60]HELLO.COR SLP@ [1,60]MCR.OLB PIP@ [1,64]MCR.OLB PIP@3.1.1.2 F DRIVER [11,60]IPDRV.COR SLP@5.1.1.1 M BAD [62,60]BADBLK.OBJ LBR@5.1.13.1 N PRESRV [41,60]PRESRV.SYS PIP@ [41,60]PRESRV.STB PIP@5.1.17.2 M BRU [1,60]BRU.OLB PIPF5.1.17.3 M (Superseded by 5.1.17.3 M article of March, 1980)@5.7.10.1 F QMG [25,64]QMGMOJ.OBJ LBR@ [25,64]QMGRSY.OBJ LBR@5.7.10.2 F QMGCLI [25,64]QUE3.OBJ LBR) Table 8N? Autopatch Files from Software Dispatch, March, 1980 Software Dispatch GArticle Reference Component Autopatch Files Autopatch Action0D1.1.1.1 M (Superseded by 1.1.1.1 M article of June, 1980)@2.1.1.4 M EXEC [11,60]DRSED.COR SLP@2.1.6.3 M EXEC [11,60]IOSUB.COR SLP@2.2.1.2 F MCR [12,60]MCROV.COR SLP@ [12,60]MCROV.OBJ LBR@2.2.1.3 F MCR [12,60]FLAOV.COR SLP@ [1,64]MCR.OLB PIP@2.2.5.1 F VMR [1,60]VMR.OLB PIP@3.1.3.3 M DRIVER [11,60]LKDRV.COR SLP@3.1.3.5 F DRIVER [11,60]LPDRV.COR SLP@3.2.1.3 F FCSRES [50,64]FCSRS1.CMD PIP@ [50,64]FCSRS1BLD.CMD PIP@ [50,64]FCSRS1BLD.ODL PIP K PAGE 284@5.1.17.3 M BRU [1,60]BRU.OLB PIP@5.6.1.1 F EDI [1,60]EDIBLD.CMD PIP@ [1,64]EDIBLD.CMD PIP@5.7.11.2 F QMGCLI [25,64]SHOWQ.OBJ LBR) Table 9 ? Autopatch Files from Software Dispatch, April, 1980 Software DispatchRGArticle Reference Component Autopatch Files Autopatch Action @2.1.1.5 M EXEC [11,60]DRSED.COR SLP@2.1.1.6 M EXEC [11,60]DREXP.COR SLP@2.1.1.7 M EXEC [11,60]DRASG.COR SLP@2.1.6.7 M EXEC [11,60]TOSUB.COR SLP@3.1.1.3 M DRIVER [11,60]DLDRV.COR SLP@3.1.1.4 M DRIVER [11,60]DYDRV.COR SLP@3.1.1.5 F DRIVER [11,60]DMDRV.COR SLP@3.1.2.2 M DRIVER [11,60]MMDRV.COR SLP@3.1.2.3 M DRIVER [11,60]MMDRV.COR SLP@3.1.3.6 M DRIVER [11,60]TTDRV.COR SLP@3.1.4.4 F DRIVER [11,60]IPDRV.COR SLP@ SYSGEN [200,60]SGNIP.COR SLP) Table 10.> Autopatch Files from Software Dispatch, May, 1980Software DispatchEGArticle Reference Component Autopatch Files Autopatch Action @2.1.6.1 M EXEC [11,60]CRASH.COR SLPE5.1.10.2 M (Superseded by 5.1.10.2 M article of July, 1980)6@5.1.17.4 M BRU [1,60]BRU.OLB PIP@5.2.5.3 M K-SERIES [45,60]KADINP.COR SLP NK PAGE 29 @ [45,60]KADGCH.COR SLP@5.7.3.1 M PMD [15,60]DUMP2.OBJ LBR@ [15,64]DUMP2.OBJ LBR@5.7.5.2 F RMDEMO [14,60]MDPAGE.COR SLP@ [14,64]MDPAGE.OBJ LBR@ [14,60]MDPAGE.OBJ LBR@5.7.10.3 F QMG [25,64]QMGSTA.OBJ LBRI5.7.12.2 F (Superseded by 5.7.12.3 F article of February, 1981) ) Table 11 > Autopatch Files from Software Dispatch, June, 1980Software Dispatch GArticle Reference Component Autopatch Files Autopatch Action6@1.1.1.1 M SYSGEN [200,60]SYSGEN2.COR SLP@ [200,60]SGNICIS.COR SLP@ [200,60]SGNIXEC.COR SLP@ [200,60]SGNPER.COR SLP@2.1.3.1 M TKTN [12,60]TKTN.COR SLP@2.1.5.3 M EXEC [11,60]SYSXT.COR SLP@2.1.6.9 F EXEC [11,60]IOSUB.COR SLP@2.2.1.4 F SAV [12,60]SAVSUB.COR SLP@ [12,60]SPCDRV.COR SLP@ [12,60]SAVSIZ.COR SLP@ [12,60]SAVDX.COR SLP@ [1,60]BOOBLD.CMD PIP@ [1,60]SAVBLD.CMD PIP@ [1,64]BOOBLD.CMD PIP@ [1,64]SAVBLD.CMD PIP@2.2.1.5 M RUN [12,60]RPSOV.COR SLP@3.1.1.6 M DRIVER [11,60]DMDRV.COR SLP@3.1.1.7 M DRIVER [11,60]DMDRV.COR SLP@3.1.1.8 M DRIVER [11,60]DBDRV.COR SLP@3.1.1.9 M DRIVER [11,60]DYDRV.COR SLP@3.1.2.4 M DRIVER [11,60]MTDRV.COR SLP@3.1.2.5 M DRIVER [11,60]MMDRV.COR SLP K PAGE 30]@3.1.4.5 M DRIVER [11,60]ICDRV.COR SLP@ SYSGEN [200,60]SGNICIS.COR SLP@5.1.17.5 M BRU [1,60]BRU.OLB PIP@5.7.3.2 M PMD [15,60]DUMP2.OBJ LBR@ [15,64]DUMP2.OBJ LBR@5.7.10.4 F QMG [121,60]PRTDN.OBJ LBR@ [121,60]RECEIV.OBJ LBR@ [121,60]JOBSTR.OBJ LBR@ [121,60]FILPRO.OBJ LBR) Table 12> Autopatch Files from Software Dispatch, July, 1980Software Dispatch GArticle Reference Component Autopatch Files Autopatch Action @2.2.1.6 M SET [12,60]SETOV.COR SLP@ [12,64]SETOVFDT.COR SLP@ [12,64]MCRTTFD.OBJ PIP@3.1.1.10 M EXEC [11,60]DMDRV.COR SLP@3.2.2.1 F FCP [13,60]INWIN.OBJ LBR@ [13,64]INWIN.OBJ LBR@5.1.10.2 M MOU [12,60]MOUROT.COR SLP@5.3.2.1 F FTB [106,60]P3MDS.OBJ LBR@5.5.1.1 F ODT [47,60]ODT.OBJ PIP) Table 13 ? Autopatch Files from Software Dispatch, August, 1980.Software Dispatch GArticle Reference Component Autopatch Files Autopatch Action @2.1.1.9 M EXEC [11,60]DRDSP.COR SLP@2.1.5.4 F EXEC [11,60]LOADR.COR SLP@2.2.1.7 M MCR [12,60]MCROV.COR SLP@3.1.2.6 M DRIVER [11,60]MMDRV.COR SLP DK PAGE 31 @3.1.4.6 M DRIVER [11,60]ICDRV.COR SLP@3.2.2.2 M FCP [13,60]CLDELNMH.OBJ LBR@ [13,60]CLDELFCP.OBJ LBR@5.1.17.7 M BRU [1,60]BRU.OLB PIP@5.1.17.8 M BRU [1,60]BRU.OLB PIP@5.1.17.9 N BRU [1,64]BRUBLD.CMD PIP@5.1.17.10 M BRU [1,60]BRU.OLB PIP@5.2.5.5 F DRIVER [52,60]IPOUT.OBJ LBR) Table 14.A Autopatch Files from Software Dispatch, September, 1980 Software Dispatch GArticle Reference Component Autopatch Files Autopatch Action,@2.1.1.10 M EXEC [11,60]DRREG.COR SLP@2.1.5.3 M EXEC [11,60]SYSXT.COR SLP@2.1.6.11 M EXEC [11,60]ERROR.COR SLP@2.2.1.8 F MCR [12,60]BYE.COR SLP@ [1,60]MCR.OLB PIP@ [1,64]MCR.OLB PIP@2.2.1.9 M MCR [12,60]CLQOV.COR SLP@ [1,60]MCR.OLB PIP@ [1,64]MCR.OLB PIP@2.2.1.10 M SAV [12,60]SAVINS.COR SLP@ [1,60]SAV.OLB PIP@ [1,64]SAV.OLB PIP@2.2.1.12 M UNFIX [12,60]FIXOV.COR SLP@ [1,60]MCR.OLB PIP@ [1,64]MCR.OLB PIP@2.2.1.13 M MCR [12,60]FLAOV.COR SLP@ [1,60]MCR.OLB PIP@ [1,64]MCR.OLB PIP@3.1.1.11 M DRIVER [11,60]DYDRV.COR SLP@5.1.18.2 M FMT [1,60]FMT.OLB PIP FK PAGE 32[@5.2.5.6 M K-SERIES [45,60]KSTADC.COR SLP@5.2.6.3 F LIBRARIES [55,60]OVCTR.OBJ LBR) Table 15 @ Autopatch Files from Software Dispatch, October, 1980Software DispatchBGArticle Reference Component Autopatch Files Autopatch Action @2.1.6.12 M EXEC [11,60]REQSB.COR SLP@2.2.1.14 M SYSTEM TASK [12,60]HELLO.COR SLP@ [1,60]MCR.OLB PIP@ [1,64]MCR.OLB PIP@2.2.5.3 M VMR [1,60]VMR.OLB PIPG3.1.1.13 M (Superseded by 3.1.2.9 M article of January, 1981)0@3.1.2.7 M DRIVER [11,60]MMDRV.COR SLP@3.1.4.7 M DRIVER [11,60]LADRV.COR SLP@3.2.2.3 M FCP [13,60]CLDELNMH.OBJ LBR@ [13,60]CLDELFCP.OBJ LBR@3.2.2.4 M FCP [13,60]WTRNINMH.OBJ LBR@ [13,60]WTRNIFCP.OBJ LBR@5.1.17.11 M BRU [1,60]BRU.OLB PIP@5.2.4.1 M LIBRARIES [52,60]WFLOR.OBJ LBR@ [52,60]INAST.OBJ LBR@ [52,60]ENAST.OBJ LBR@ [52,60]CNMRK.OBJ LBR@ [52,60]SPSUB.OBJ LBR@ [52,60]ENCKP.OBJ LBR@ [52,60]DSCKP.OBJ LBR@5.2.5.7 N LPA [1,60]LAINIT.OLB PIP@5.7.5.2 F RMD [14,60]MDPAGE.COR SLP@ [14,60]MDPAGE.OBJ LBR@ [14,64]MDPAGE.OBJ LBR) Table 16@ Autopatch Files from Software Dispatch, November 1980 K PAGE 33 Software DispatchSGArticle Reference Component Autopatch Files Autopatch ActionL@2.2.1.15 M MCR [12,60]SETOV.COR SLP@ [12,60]SETOVFDT.COR SLP@2.2.5.4 N VMR [1,60]VMR.OLB PIP@3.1.1.15 M DRIVER [11,60]DDDRV.COR SLP@3.1.2.8 M DRIVER [11,60]MTDRV.COR SLP@3.1.4.8 F DRIVER [11,60]ISDRV.COR SLP@5.1.12.2 M PIP [32,60]PIPCPY.OBJ LBR) Table 17.@ Autopatch Files from Software Dispatch, December, 1980Software Dispatch GArticle Reference Component Autopatch Files Autopatch Action[@3.2.3.4 M MTAACP [22,60]MMOMSG.OBJ LBR@ [22,60]MMSG.OBJ LBR@ [22,60]MEXMSG.OBJ LBR@ [22,60]MTOMSG.OBJ LBR@ [22,60]MMTMSG.OBJ LBR@ [64,60]F11MSG.OBJ LBR@5.1.6.6 M DSC [163,60]DSCS16.SYS PIP@ [163,60]DSCS16.STB PIP) Table 18R@ Autopatch Files from Software Dispatch, January, 1981Software Dispatch GArticle Reference Component Autopatch Files Autopatch Action @3.1.2.9 M DRIVER [11,60]MSDRV.COR SLP@5.1.17.12 M BRU [1,60]BRU.OLB PIP4 [74,60]BRUPAR.PAT4 [74,60]TAPEIO.PAT@5.1.17.14 M BRU [1,60]BRU.OLB PIP5 [74,60]BRUHEAD.PATh@5.7.5.3 F RMD [14,60]RMDRIV.OBJ LBR rK PAGE 34.@ [14,60]RMDRIV.COR SLP@ [14,64]RMDRIV.OBJ LBR) Table 19T@ Autopatch Files from Software Dispatch, February, 1981Software Dispatch GArticle Reference Component Autopatch Files Autopatch Action6@3.1.2.10 M DRIVER [11,60]MMDRV.COR SLP@3.1.3.12 M DRIVER [11,60]TTDRV.COR SLP@3.1.4.6 M DRIVER [11,60]ICDRV.COR SLP@5.1.12.3 M PIP [32,60]PIP.OLB PIP4 [32,60]PIPDEL.PAT5.2.4.2 M RSXMAC @5.7.12.3 F LPP [121,60]IOPRT.OBJ LBR4 [121,60]IOPRT.PAT) Table 20 ? Autopatch Files from Software Dispatch, March, 1981MSoftware Dispatch GArticle Reference Component Autopatch Files Autopatch Action6@2.1.6.13 M EXEC [11,60]CRASH.COR SLP@3.1.3.14 M DRIVER [11,60]TTATT.COR SLP@ [11,60]TTCAN.COR SLP@ [11,60]TTDAT.COR SLP@ [11,60]TTFP.COR SLP@ [11,60]TTICH.COR SLP@ [11,60]TTINI.COR SLP@ [11,60]TTMAC.COR SLP@ [11,60]TTMIS.COR SLP@ [11,60]TTMOD.COR SLP@ [11,60]TTODN.COR SLP@ [11,60]TTOIS.COR SLP@ [11,60]TTRW.COR SLP@ [11,60]TTSUB.COR SLP@ [11,60]TTTBL.COR SLP@ [11,60]TTYH.COR SLP@ [11,60]TTYZ.COR SLP@3.2.1.5 O FCS [50,60]CONTRL.OBJ LBR K PAGE 35 @ [50,60]PNTMRK.OBJ LBR4 [50,60]CONTRL.PAT4 [50,60]PNTMRK.PAT@3.2.2.6 M F11ACP [13,60]WTRNINMH.OBJ LBR6 [13,60]WTRNINMH.PAT) Table 21 ? Autopatch Files from Software Dispatch, April, 1981OSoftware Dispatch GArticle Reference Component Autopatch Files Autopatch Action@3.1.1.16 M DRIVER [11,60]DRDRV.COR SLP@3.1.4.9 M DRIVER [11,60]IPDRV.COR SLP@ [200,60]SGNIP.COR SLP@5.1.17.16 M BRU [1,60]BRU.OLB PIP4 [74,60]TAPEIO.PAT4 [74,60]BACKLB.PAT4 [74,60]SCNDIR.PAT@5.7.1.1 M ACNT [15,60]ACNT.COR SLP) Table 22 > Autopatch Files from Software Dispatch, May, 1981Software Dispatch GArticle Reference Component Autopatch Files Autopatch Action @2.1.6.14 F EXEC [11,60]DRSPW.COR SLP@ [11,60]MCRDIS.COR SLP@ [11,60]MCROV.COR SLP@ [1,60]MCR.OLB PIP@ [1,64]MCR.OLB PIP@2.2.5.5 F VMR [1,60]VMR.OLB PIP3 [70,60]SAMSM.PATc3 [70,60]SAMSU.PATo@3.1.1.10 M DRIVER [11,60]DXDRV.COR SLP@3.1.2.11 M DRIVER [11,60]MSDRV.COR SLP@5.7.10.5 M QMG [25,64]QMGSTA.OBJ LBR4 [25,64]QMGSTA.PAT@ [121,64]JOBEND.OBJ LBR5 [121,64]JOBEND.PAT0 RK PAGE 36 ) Table 23> Autopatch Files from Software Dispatch, June 1981Software Dispatch GArticle Reference Component Autopatch Files Autopatch ActionG@1.1.1.3 M SYSGEN [200,60]SGNKLAB.COR SLP@1.1.1.4 M SYSGEN [200,60]SGNICIS.COR SLP@2.1.5.5 M EXEC [11,60]LOADR.COR SLP@3.1.1.17 M DRIVER [11,60]DRDRV.COR SLP@3.1.1.20 M DRIVER [11,60]DYDRV.COR SLP@5.1.17.17 M BRU [1,60]BRU.OLB PIP3 [74,60]BRURP.PATm@5.3.1.1 M TKB [31,60]STINP.OBJ LBR3 [31,60]STINP.PAT@5.3.1.2 M TKB [31,60]SGALO.OBJ LBR3 [31,60]SGALO.PAT ) Table 24 A Autopatch Files to Appear in Future Software Dispatches > Component Autopatch Files Autopatch Action7 BRU [1,60]BRU.OLB PIP ) [74,60]BRUHEAD.PAT ) [74,60]BRUFILE.PATL( [74,60]BRUPAR.PAT7 FTB [106,60]P4MAL.OBJ LBR]( [106,60]P4MAL.PAT7 SHUTUP [15,60]SHUTUP.COR SLP 7 [15,60]SHUTUP.OBJ LBRa7 BRO [15,60]BROAD.COR SLP 7 [15,60]BROAD.OBJ LBR 7 TKB [31,60]P2POP.OBJ LBR ' [31,60]P2POP.PAT 7 VMR [1,60]VMR.OLB PIP6 RK PAGE 37 ( [70,60]LDVLDB.PAT7 K-SERIES [45,60]KBFSTS.COR SLP 7 DRIVER [11,60]EMDRV.MAC PIP 7 [11,60]EMTAB.MAC PIP 7 [200,60]EMDRV.CMD PIPK7 [1,60]SAV.OLB PIP 7 [1,64]SAV.OLB PIP[7 [12,60]SAVSUB.COR SLP 7 EDT [1,60]EDTBLD.ODL PIP7 INDIRECT [12,60]INDPAR.COR SLPI7 [12,60]INDPAR.OBJ LBRV)6.0 AUTOPATCH NOTES _________ _____ FDuring SYSGEN Phase III, nonprivileged tasks may be built. TheFfollowing tasks are patched by Autopatch and should be rebuilt inFSYSGEN Phase III: BAD, BRU, CDA, DSC, EDI, TKB, FLX, FMT, FTB, LBR, VMR, and PIP. FThe distributed version of MSDRV.MAC (Version 1) is no longerFsupported. It has been replaced with Version 2. MSDRV.MAC (Version=2) is the supported source for the TS11 magnetic tape driver.OFThe PURPCS.OBJ file, needed for IP-type devices, was inadvertentlyFleft off the Distribution Kit. Autopatch supplies the PURPCS.OBJ file+by copying it to UFD [1,1] of your disk(s).nFTo include support for the new ML11 device, first apply the AutopatchFnormally and do the SYSGEN. Then, set your UIC to [200,200] andFinvoke the indirect command file EMDRV.CMD. You will be asked toFprovide the CSR and VECTOR for your ML11. The command file will doFthe rest, requiring only that you load the driver into your system inFVMR. The system table will include two UCBs and support the ML11 onlyFas a data device. It is necessary that you SAV and boot the system:before using the ML11 so that SAV has a chance to size it.FAutopatch deletes the files [1,51]PRESRV.SYS and [1,51]PRESRV.STB fromFyour disk(s). Autopatch replaces these files with updated PRESRV.SYSand PRESRV.STB files.vFAutopatch also deletes the [1,51]DSCS8.SYS and [1,51]DSCS8.STB filesFfrom your disk(s). Autopatch replaces these files with updatedDSCS8.SYS and DSCS8.STB files.FQMGCLI.OLB on the RSX-11M V3.2 Distribution Kit contains severalFextended instruction set (EIS) instructions. There are too many ofFthese to make patching practical. Therefore, Autopatch includes anFupdated object library, named QMGCLIEIS.OLB. If you do not have EISFon your machine and you wish to use the Queue Manager, you must copy [F PAGE 38F[1,64]QMGCLIEIS.OLB to your RSXM26 disk. Replace the [1,24]QMGCLI.OLBFwith the QMGCLIEIS.OLB file and rebuild the task. This now means thatFthere are two divergent QMGCLI tasks in the field. For this reasonFplease state very clearly, in any future correspondence concerning the8Queue Manager, that you have the non-EIS object library.FCommand files and an overlay descriptor file have been provided inFUFD[1,24] on RSXM26 to build a memory-resident overlayed FCS residentFlibrary. This is a resident common containing almost all of FCS,Fusing at most 5.5KW of physical memory. You can use this overlayedFFCSRES on a mapped system if you select the memory-mapping (PLAS)Fdirectives. Please refer to the Software Dispatch article, "Overlayed7FCSRES - 1 APR 1980 for 5.5K," for further information.nFAutopatch copies a new stand-alone DSC to your disk(s). This new DSCFis DSCS16. It provides the functionality of running stand-alone DSCFwith a 1600 BPI magnetic tape device. The files DSCS16.SYS and0DSCS16.STB are copied to [1,51] of your disk(s).FDue to the lack of file headers, the correction files for theFExecutive, the drivers, the MCR sources, and INDIRECT have beenFconcatenated into four smaller groups of corrections. The universalFlibrary [11,60]CONCAT.ULB contains these concatenated .COR files. TheFfollowing table lists the new corrections, their location on theFAutopatch Kit, and the concatenated contents. None of the individualF.COR files are on the Kit; however, you may view an individual .CORFfile by extracting the concatenated .COR from [11,60]CONCAT.ULB usingLBR and printing it.' Table 25ED Concatenated Source Correction Files Contained in [11,60]CONCAT.ULB; Component Concatenated File Contentsa: EXEC [11,60]EXC1.COR BFCTL.COR: REQSB.COR: SYTAB.COR: EXEC [11,60]EXC2.COR CRASH.COR: DRCMT.COR: DRDSP.COR: EXEC [11,60]EXC3.COR DRASG.COR: DREIF.COR: DRREG.COR: EXEC [11,60]EXC4.COR DRGEF.COR: DRSED.COR: DRSPW.COR: EXEC [11,60]EXC5.COR INITL.COR: IOSUB.COR: LOADR.COR: EXEC [11,60]EXC6.COR ERROR.COR: LOWCR.COR: SYSXT.COR: EXEC [11,60]EXC7.COR DREXP.COR D PAGE 39: DRIVER [11,60]DRV1.COR DLDRV.COR: DMDRV.COR: DRDRV.COR: DRIVER [11,60]DRV2.COR MTDRV.COR: TTATT.COR9 TTFP.COR : DRIVER [11,60]DRV3.COR TTMIS.COR: TTMOD.COR: TTODN.COR9 TTRW.COR : TTTBL.COR9 TTYZ.COR : DRIVER [11,60]DRV4.COR TTOIS.COR: TTSUB.COR9 TTYH.COR : DRIVER [11,60]DRV5.COR CRDRV.COR: DBDRV.COR: ICDRV.COR: DRIVER [11,60]DRV6.COR DYDRV.COR: MMDRV.COR: IPDRV.COR: DRIVER [11,60]DRV7.COR LADRV.COR: LKDRV.COR: LPDRV.COR: DRIVER [11,60]DRV8.COR MSDRV.COR: TTDRV.COR: XMDRV.COR: DRIVER [11,60]DRV9.COR XBDRV.COR: ISDRV.COR: DDDRV.COR: DXDRV.COR: DRIVER [11,60]DRV10.COR TTCAN.COR: TTDAT.COR: TTINI.COR: DRIVER [11,60]DRV11.COR TTICH.COR: TTMAC.COR; MCR [12,60]MCR1.COR INIGCL.COR 8 BYE.COR: CLQOV.COR: MCR [12,60]MCR2.COR FLAOV.COR: MCROV.COR; DISMNT.COR : MCR [12,60]MCR3.COR HELLO.COR; MDISOV.COR : MMTOV.COR; MCR [12,60]MCR4.COR MOUPAR.COR ; MPARMT.COR : RPSOV.COR: MCR [12,60]MCR5.COR FIXOV.COR: SAVDX.COR; SAVSIZ.CORM .D PAGE 40; SPCDRV.CORT= MCR [12,60]MCR6.COR SETOVFDT.COR.9 TKTN.CORM; MOUROT.CORV; MCR [12,60]MCR7.COR SAVINS.CORC; SAVSUB.CORR: SETOV.COR .D PAGE 40; SPCDRV.CORT= MCR [12,60]MCR6.COR SETOVFDT.COR.9 TKTN.CORM;  .ENABLE SUBSTITUTION .ENABLE GLOBAL ; ;: ; AUTOPATCH Rev. E patches only the software for RSX-11M.6 ; If you wish to patch any layered product software, % ; please refer to your cover letter. ; ; ; .;= .; Logical symbols for patching of big disk distribution kit .; .SETT BDBASE .;? .; Logical symbols for patching of RL01/RL02 distribution kits .; .SETT RLBASE .SETT MAPSRC .SETT UNMSRC .SETT RLUTIL .;9 .; Logical symbols for patching of RK05 distribution kitN .;S .SETT RKBASE. .SETT EXCSRC .SETT DRVSRCP .SETT PRVOBJc .SETT UTLOBJf .SETT MCRSRC1 .;;2 .; Logical symbol for support V3.2 Autopatch kits .;p .SETT V3P2AKy .;o4 .; Logical symbol for support of TU58 Autopatch kit .;c .SETF TU58AKk .;r' .; Numeric symbol for Question numbers .;o .;  .SETN COUNT 1.i .SETS DOT ". "i .;u .;k .; V3.2 Autopatch info .;E .SETN $BASEL 26 .SETS $IDENT "1.80" .SETS $APTRV "E"a .SETN $APTVL 1c .SETN $GRP 0s .SETN $OSGRP 4. .;.4 .; Logical symbols concerning the system running on .;c .SETT MOU .SETT UFD .SETT PIP .SETT FLX .SETT SLP .SETT LBR .SETT DMO .SETT LOADED. .SETT VFY .SETF $SELDLi .SETT $PURGEs .SETS TMPDSK "" ;G ; RSX-11M V3.2 BL'$BASEL' Autopatch Revision '$APTRV' Version '$IDENT'r ; .C ; COPYRIGHT (C) 1981 DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASS.t ; ; ; .SETS UIC  SET /UIC=[1,1]D ;N.10: .ASK TEMPL 'COUNT''DOT' Have you made a copy of the disk(s) to be patched .INC COUNTi .IFT TEMPL .GOTO 100t ;: ; APT -- There is a possibility that the patching may be3 ; done to the original copy of the disk(s). MakeT- ; a copy of the disk(s) as described in theU1 ; RSX-11M V3.2 System Generation and ManagementE! ; Guide, and restart Autopatch.i ; .SETF DOGEN .GOTO 11100.100:8 .SETF $BGDSKM .SETF $RL .SETF $2RK .SETF RK07; .SETT $ALLRLC ;@ ; Specify the type of RSX-11M V3.2 distribution kit you have by@ ; responding to the next question with either A, B, or C where: ;/ ; A -- indicates the big disk distribution kitt5 ; (RK06/RK07, RM02/RM03, RP02/RP03, RP04/RP05/RP06)t0 ; B -- indicates the RL01/RL02 distribution kit0 ; C -- indicates the dual RK05 distribution kit ;P .ASKS TEMPS 'COUNT''DOT' What type of distribution kit do you have (A, B, or C) .IF TEMPS EQ "A" .SETT $BGDSK .IF TEMPS EQ "B" .SETT $RL0 .IF TEMPS EQ "C" .SETT $2RK$ .IFT $BGDSK .OR .IFT $2RK .GOTO 150 .;k@ .; Unsupported kit type (single RL01/RL02) or invalid response. .;  .IF TEMPS NE "B" .GOTO 120e .IF TEMPS EQ "B" .INC COUNTD .ASK TEMPL 'COUNT''DOT' Do you have a second RL01/RL02 drive to use .INC COUNTL .IFT TEMPL .GOTO 150t ;7 ; APT -- The RL01/RL02 distribution kit with just oneS: ; RL01/RL02 drive is not supported by RSX-11M BL'$BASEL'1 ; Autopatch. Please use this command file as aF6 ; quide to patching your RL01/RL02 distribution kit. ; .SETF DOGEN .GOTO 11100.120: ;k? ; APT -- "'TEMPS'" is an invalid response. Please try again.. ; .GOTO 100!.150: .IF TEMPS NE "B" .INC COUNT  .IFF $RL .INC COUNT .SETF DSYUICO+ .IFT $BGDSK .IF EQ "DM" .GOTO 155e .IFT $BGDSK .SETT $SELDL  .IFT $BGDSK .GOTO 200 .GOTO 158.155: .IFNINS VFY .SETF VFYs .IFNINS VFY INS $VFYr .IFNINS PIP .SETF PIP .IFNINS PIP INS $PIP  VFY SY:WORK.TMP=/FR .OPENR WORK.TMP .READ RECORDd .READ RECORDo PIP WORK.TMP;0/DE? .PARSE RECORD " " NUL NUL FREE NUL NUL NUL NUL NUL NUL NUL MAX" .IF MAX = "53790." .SETT RK07 .IFT RK07 .SETT $SELDL .IFT RK07 .GOTO 200[.158: .ASK TEMPL 'COUNT''DOT' Are you running Autopatch standalone (on the baseline system)" .INC COUNTe .IFT TEMPL .SETF $ONL .IFF TEMPL .SETT $ONL? .ASK $MAP 'COUNT''DOT' Are you going to SYSGEN a mapped system$ .INC COUNTS! .IFT $MAP .SETS TEMPM "unmapped"I .IFF $MAP .SETS TEMPM "mapped"  .IFT $MAP .SETS TEMPP "UNMSRC"R .IFF $MAP .SETS TEMPP "MAPSRC"SQ .IFT $RL .ASK $ALLRL 'COUNT''DOT' Do you want to patch 'TEMPP' ('TEMPM' sources)T .IFT $RL .INC COUNT .IFT $MAP .SETN $GRP 4O .IFF $MAP .SETN $GRP 0' .IFT $MAP .SETN $OSGRP 0  .IFF $MAP .SETN $OSGRP 4e# .IFT $MAP .IFF $ALLRL .SETF UNMSRCF# .IFF $MAP .IFF $ALLRL .SETF MAPSRC  .IFT $ONL .GOTO 160 ;@ ; The contents of UIC [1,5'$OSGRP'] must be deleted in order toC ; provide disk space for the Autopatch files. The baseline system B ; in UIC [1,5'$GRP'] must be hardware bootable and it must be the@ ; system under which the Autopatch is run. If this is not the A ; case, respond to the next question with N and do the followingM ; after Autopatch exits:P ; ; >INS $BOO;-1F ; >BOO [1,5'$GRP']RSX11MF ; ; RSX-11M V3.2 BL'$BASEL' ; .  ; .F ; .L ; >SAV /WB  ; ; Then restart Autopatch. ; .GOTO 165.160: ;O< ; If you answer Y to the next question, the contents of UIC9 ; [1,5'$OSGRP'] will be deleted to provide space for the$: ; Autopatch files. If you answer N, Autopatch will exit. ;R.165: .ASK DSYUIC 'COUNT''DOT' Should the contents of UIC [1,5'$OSGRP'] be deleted .INC COUNTN .IFF DSYUIC .SETF DOGEN .IFF DSYUIC .GOTO 11100 .IFF $2RK .IFT $RL .GOTO 1681 .IFF $2RK .IFF $RL .GOTO 200M ; ;5 ; You have indicated the dual RK05 distribution kit.T8 ; In order to have enough space and enough file headers5 ; for the Autopatch procedure, it is necessary that ;5 ; you delete at least 7 of the following drivers and$6 ; corresponding .STB files from your Base Line disk-- ; RSXM26. ; ; CTDRV DLDRV DRDRV DYDRV PPDRV ; DBDRV DMDRV DTDRV MMDRV ; DDDRV DPDRV DXDRV MTDRV ;6 ; Autopatch will now pause to allow you to delete the5 ; drivers. Follow the example provided deleting anyM ; unnecessary drivers.i ; ; Example:0O ; PIP CTDRV.*;*/DE,DDDRV.*;*,DTDRV.*;*,DXDRV.*;*,DYDRV.*;*,PPDRV.*;*,DBDRV.*;*; ; t ; .IFT $2RK SET /UIC=[1,5'$GRP']r .IFT $2RK .PAUSEl.168: .; .IFT $2RK .SETS TMPDSK "RK05"" .IFT $RL .SETS TMPDSK "RL01/RL02" .IFT $RL SET /UIC=[1,5'$GRP'] .IFINS MOU .GOTO 170D .SETF MOU INS $MOUD.170: .IFINS UFD .GOTO 175 .SETF UFD INS $UFD;.175: ;pJ ; To provide more space on the baseline disk for Autopatch files, severalF ; files which are not needed by Autopatch will be copied to a scratchH ; disk. These files include [1,5'$GRP']EDT.TSK,EDI.TSK,ZAP.TSK,VFY.TSK,N ; [1,5'$GRP']PAT.TSK,DMP.TSK,CMP.TSK,BAD.TSK, and [1,51]BADSYS.SYS,BADSYS.STB? ; These files will all be restored at the end of the Autopatch0M ; procedure. Other files in [1,51]*.* will also be deleted and replaced fromO ; the Autopatch kit.O ; .IFT $ONL .GOTO 180 .IFINS EDT REM EDT  .IFINS EDI REM EDI  .IFINS ZAP REM ZAP  .IFINS VFY REM VFYr .IFINS PAT REM PATe .IFINS DMP REM DMPt .IFINS CMP REM CMPa .IFINS BAD REM BADe ;D.180: ; Please insert a scratch 'TMPDSK' into a free 'TMPDSK' drive.H ; You will be asked to give the internal label of your scratch 'TMPDSK' ;J .ASKS [1:9.] SCRLBL 'COUNT''DOT' Enter the label of your scratch 'TMPDSK' .INC COUNT1_.185: .ASKN SCRNO 'COUNT''DOT' Enter the unit number of the drive containing a scratch 'TMPDSK'. .IF SCRNO NE .GOTO 190 ;6 ; '''SCRNO': is assigned as your system disk.B ; Please enter a different drive unit number into which to place  ; your scratch 'TMPDSK'.a ; .GOTO 185.190: .INC COUNT% .SETS SCRTCH +"'SCRNO'"+":"a MOU 'SCRTCH''SCRLBL'a6 .ASK RDY 'COUNT''DOT' Did 'SCRTCH' mount successfully .IFF RDY .DEC COUNT .IFF RDY .GOTO 180a .INC COUNT ; UFD 'SCRTCH'[1,51]  UFD 'SCRTCH'[1,5'$GRP']( PIP 'SCRTCH'[1,51]/NV=SY:[1,51]BADSYS.*Q PIP 'SCRTCH'[1,5'$GRP']/NV=SY:[1,5'$GRP']EDT.TSK,EDI.TSK,ZAP.TSK,VFY.TSK,PAT.TSKsA PIP 'SCRTCH'[1,5'$GRP']/NV=SY:[1,5'$GRP']DMP.TSK,CMP.TSK,BAD.TSKn ;1 ; Now delete copied files from the baseline disk ; PIP SY:[1,51]*.*;*/DE/NMTJ PIP SY:[1,5'$GRP']EDT.TSK;*,EDI.TSK;*,ZAP.TSK;*,VFY.TSK;*,PAT.TSK;*/DE/NM6 PIP SY:[1,5'$GRP']DMP.TSK;*,CMP.TSK;*,BAD.TSK;*/DE/NM DMO 'SCRTCH'F ;, ; Now remove the scratch disk from 'SCRTCH' ;E .IFT $2RK ; Reserve some contiguous space for the standalone systems- .IFT $2RK PIP TEMP.TMP/BL:100./CO=RSX11M.SYSS .IFT $2RK ; .;  .;,& .IFT $2RK .OR .IFT $RL SET /UIC=[1,1] .;' .;] .;S'.200: .IFT $BGDSK .SETS $KIT "Big disk"i, .IFT $BGDSK .IF NE "DM" .INC COUNT, .IFT $BGDSK .IF NE "DM" .INC COUNT, .IFT $BGDSK .IF NE "DM" .INC COUNT .IFT RK07 .INC COUNTD .IFT RK07 .INC COUNTT .IFT RK07 .INC COUNTH .IFT $RL .SETS $KIT "RL01/RL02"! .IFT $2RK .SETS $KIT "Dual RK05"; .SETN MAXDSK 1t .IFF $BGDSK .GOTO 210 .SETS DISK'MAXDSK' "BDBASE" .GOTO 230.210: .IFF $RL .GOTO 220 .SETS DISK'MAXDSK' "RLBASE" .IFT RLUTIL .INC MAXDSK( .IFT RLUTIL .SETS DISK'MAXDSK' "RLUTIL" .IFT UNMSRC .INC MAXDSK( .IFT UNMSRC .SETS DISK'MAXDSK' "UNMSRC" .IFT MAPSRC .INC MAXDSK( .IFT MAPSRC .SETS DISK'MAXDSK' "MAPSRC" .GOTO 230!.220: .SETS DISK'MAXDSK' "RKBASE"N .IFT EXCSRC .INC MAXDSK( .IFT EXCSRC .SETS DISK'MAXDSK' "EXCSRC" .IFT UTLOBJ .INC MAXDSK( .IFT UTLOBJ .SETS DISK'MAXDSK' "UTLOBJ" .IFT PRVOBJ .INC MAXDSK( .IFT PRVOBJ .SETS DISK'MAXDSK' "PRVOBJ" .IFT DRVSRC .INC MAXDSK( .IFT DRVSRC .SETS DISK'MAXDSK' "DRVSRC" .IFT MCRSRC .INC MAXDSK( .IFT MCRSRC .SETS DISK'MAXDSK' "MCRSRC".230: / .SETS APTLAB "AUTOPATCH"+"'$APTRV'"+"'$APTVL'" ;D ; Determine the Autopatch kit device and unit. Place the AutopatchB ; medium labeled 'APTLAB' on that unit. The unit should be writeC ; protected. When the unit is ready respond to the next question.. ; .SETF APTDM .SETF APTDL .SETF APTDK .SETF APTTP .SETF APTDDV.235: .ASKS APTDEV 'COUNT''DOT' When ready, enter the Autopatch device and unit (ddu:) .SETS $APDEV APTDEV& .SETS TEMPS $APDEV[:]- .IF TEMPS NE ":" .SETS $APDEV "'$APDEV'"+":"P .TEST $APDEV" .SETN TEMPN t .IF TEMPN LT 3 .GOTO 500v& .SETS TEMPD +"''"+":" .IF $APDEV EQ TEMPD .GOTO 240+ .IF EQ 0 .SETS TEMPD +":"  .IF $APDEV NE TEMPD .GOTO 245.240: ;x9 ; '''': is assigned as the system disk.H ; Please enter another device or unit as the Autopatch device and unit. ; .GOTO 235.245: .SETS NMNC $APDEV[1:2]) .IFT V3P2AK .IF NMNC EQ "DM" .SETT APTDME) .IFT V3P2AK .IF NMNC EQ "DL" .SETT APTDLV) .IFT V3P2AK .IF NMNC EQ "DK" .SETT APTDKMG .IF NMNC EQ "MT" .OR .IF NMNC EQ "MM" .OR .IF NMNC EQ "MS" .SETT APTTP>) .IFT TU58AK .IF NMNC EQ "DD" .SETT APTDDF3 .IFT APTDM .OR .IFT APTDL .OR .IFT APTDK .GOTO 400 $ .IFT APTTP .OR .IFT APTDD .GOTO 400 ;> ; APT -- A "'NMNC'" is a non standard RSX-11M V3.2 Autopatch6 ; Revision '$APTRV' kit device. You will be queried1 ; again. Please use a device which correspondsF0 ; to one of the supported Autopatch kit types. ; ; ; .GOTO 230:.400: .IFT APTDM .OR .IFT APTDL .OR .IFT APTDK .SETT ADKIT& .IFT APTTP .OR .IFT APTDD .SETF ADKIT.410: .DEC TEMPN .IF TEMPN EQ 2 .GOTO 600N .SETS TEMPS $APDEV[TEMPN:TEMPN], .IF TEMPS GE "0" .IF TEMPS LE "7" .GOTO 410.500: ;T2 ; APT -- "'APTDEV'" is an invalid system device." ; Reenter a valid system device. ; ; ; .GOTO 230.600: .INC COUNT% .IF MAXDSK EQ 1 .IFF ADKIT .GOTO 800e.620: .IFINS DMO .GOTO 630 .SETF DMO INS $DMO %.630: .IFT ADKIT MOU '$APDEV''APTLAB'N .IFT ADKIT .ASK TEMPL 'COUNT''DOT' Did the 'APTLAB' disk mount successfully! .IFT ADKIT .IFT TEMPL .INC COUNT" .IFT ADKIT .IFF TEMPL .DEC COUNT .IFT ADKIT .IFF TEMPL .GOTO 230! .IF MAXDSK EQ 1 .IFF MOU REM MOUP .IF MAXDSK EQ 1 .SETT MOU .IFF ADKIT .GOTO 800  .SETS $OUTSW "/NV"d! .SETS $OUTSW "'$OUTSW'"+"/UF/FO"d .SETS $INSW ""; .SETS $UFDSP "[*,*]"C .SETS $COPY "PIP" .GOTO 850.800: .IFT APTTP .INC COUNTD .IF NMNC EQ "MS" .INC COUNT .IF NMNC EQ "MS" .GOTO 805'A .IFT APTTP .ASK TEMPL 'COUNT''DOT' Is the tape a 1600 BPI tapeT,.805: .IFT APTTP .IFT TEMPL .SETS BPI "1600"& .IFT APTTP .IFF TEMPL .SETS BPI "800" .SETS $OUTSW "/RS" * .IFT APTTP .SETS $INSW "/DO/DNS:"+"'BPI'" .IFT APTDD .SETS $INSW "/RT"  .SETS $UFDSP "" .SETS $COPY "FLX".850: .INC COUNT .IFT $2RK .SETT $DLPATT .IFF $2RK ;C .IFF $2RK ; Autopatch copies the Autopatch files to temporary UFDsOA .IFF $2RK ; in order to perform the Autopatch process. The .MAC.; .IFF $2RK ; .OBJ, .OLB, .SYS, and .STB Autopatch files areD= .IFF $2RK ; automatically deleted from these UFDs at the endS& .IFF $2RK ; of the Autopatch process. .IFF $2RK ;` .IFF $2RK .ASK $DLPAT 'COUNT''DOT' Should .PAT, .COR, .CMD and .ODL Autopatch files be deleted .INC COUNTSn .IFT $SELDL .ASK $PURGE 'COUNT''DOT' Should old .MAC, .OLB, .CMD, .ODL and .OBJ files be automatically purged .IFT $SELDL .INC COUNTt .IFDF $2RK .SETF DOGENK.871: .SETT FUDr .SETS $2APDV $APDEV .IF MAXDSK EQ 1 .GOTO 890 .IFT $RL .IFT APTDL .GOTO 890 .IFT $2RK .IFT APTDK .GOTO 890a .IFT $RL .SETS TYPE "RL01/RL02" .IFT $2RK .SETS TYPE "RK05" ;+ ; Determine the second 'TYPE' unit to use.K ;Q .ASKS SCAPDV 'COUNT''DOT' What will be your second 'TYPE' device and unit (ddu:) .SETS $2APDV SCAPDV& .SETS TEMPS $2APDV[:]- .IF TEMPS NE ":" .SETS $2APDV "'$2APDV'"+":"a .TEST $2APDV .SETN TEMPN t .IF TEMPN LT 3 .GOTO 877 .SETS APNMNC $2APDV[1:2]A& .IFT $RL .IF APNMNC NE "DL" .GOTO 877' .IFT $2RK .IF APNMNC NE "DK" .GOTO 877K.876: .DEC TEMPN .IF TEMPN EQ 2 .GOTO 879" .SETS TEMPS $2APDV[TEMPN:TEMPN], .IF TEMPS GE "0" .IF TEMPS LE "7" .GOTO 876.877: ;K< ; APT -- "'SCAPDV'" is an invalid second 'TYPE' device and9 ; unit. Reenter a valid second 'TYPE' device and unit.M ; .GOTO 871 ;.879: .SETF FUDM.890: .INC COUNT ; ;G ; Begin Autopatch process for RSX-11M V3.2 BL'$BASEL' operating system  ; on '' at '