IN-186 RSX System Generation Guide Eileen Berman David Berg Data Acquisition Software Group Fermilab Computing Department 5 January 1987 This document describes the RSX system sysgen command files, how to use these command files to perform RSX updates and sysgens on the BISON VAX and offers help in updating the command files for any new versions of the RSX system. KEYWORDS: VMS, RSX-11M Systems Supported: VAX/VMS V4.4, RSX V4.2 RSX System Generation Guide Page 2 CONTENTS CHAPTER 1 INTRODUCTION 1.1 Statement Of Problem . . . . . . . . . . . . . . . 1-1 1.2 Solution . . . . . . . . . . . . . . . . . . . . . 1-2 1.3 MD Virtual Disk Error Messages - A Warning . . . . 1-2 CHAPTER 2 DEFAULTS CHAPTER 3 COMMAND PROCEDURE DESCRIPTIONS 3.1 ADDITIONS . . . . . . . . . . . . . . . . . . . . 3-2 3.2 ASSIGN_MD_TO_DL . . . . . . . . . . . . . . . . . 3-3 3.3 ASSOC_SYSGEN . . . . . . . . . . . . . . . . . . . 3-4 3.4 ASSOC_UPDATE . . . . . . . . . . . . . . . . . . . 3-5 3.5 BACKUP_DIR_TO_TAPE . . . . . . . . . . . . . . . . 3-6 3.6 BISON_BACKUP . . . . . . . . . . . . . . . . . . . 3-7 3.7 BRU_MD_DISK_TO_DISK . . . . . . . . . . . . . . . 3-8 3.8 BRU_MD_DISKS_TO_TAPE . . . . . . . . . . . . . . . 3-9 3.9 BRU_RSX_DISK_TO_DISK . . . . . . . . . . . . . . 3-10 3.10 BRU_TAPE_TO_MD_DISKS . . . . . . . . . . . . . . 3-11 3.11 BRU_UPDATES_TO_DISK . . . . . . . . . . . . . . 3-12 3.12 CLEANUP . . . . . . . . . . . . . . . . . . . . 3-13 3.13 CLEANUP_F77 . . . . . . . . . . . . . . . . . . 3-15 3.14 CREATE_RM03 . . . . . . . . . . . . . . . . . . 3-16 3.15 CREATE_RSX_MD_DISKS . . . . . . . . . . . . . . 3-17 3.16 DISASSOCIATE . . . . . . . . . . . . . . . . . . 3-18 3.17 INSTALF77 . . . . . . . . . . . . . . . . . . . 3-19 3.18 MDDISK . . . . . . . . . . . . . . . . . . . . . 3-20 3.19 POST_SYSGEN3 . . . . . . . . . . . . . . . . . . 3-21 3.20 PREHELP . . . . . . . . . . . . . . . . . . . . 3-22 3.21 PRELPRODUCT . . . . . . . . . . . . . . . . . . 3-23 3.22 PRESYSGEN . . . . . . . . . . . . . . . . . . . 3-24 3.23 PRETUNE . . . . . . . . . . . . . . . . . . . . 3-25 3.24 PREUPDATE . . . . . . . . . . . . . . . . . . . 3-26 3.25 PRIVILEGE . . . . . . . . . . . . . . . . . . . 3-27 3.26 PROTECTION . . . . . . . . . . . . . . . . . . . 3-28 3.27 RSXVMR . . . . . . . . . . . . . . . . . . . . . 3-29 3.28 SETUPDBGI . . . . . . . . . . . . . . . . . . . 3-30 3.29 SETUPF77U . . . . . . . . . . . . . . . . . . . 3-31 3.30 SETUP_FOR_RSX_U_S . . . . . . . . . . . . . . . 3-32 3.31 Command File Dependencies . . . . . . . . . . . 3-33 CHAPTER 4 CHECKLIST PRIOR TO RSX UPDATE OR RSX SYSGEN 4.1 Tapes . . . . . . . . . . . . . . . . . . . . . . 4-1 4.2 Disks . . . . . . . . . . . . . . . . . . . . . . 4-1 4.3 RSX Sysgen Documentation . . . . . . . . . . . . . 4-2 4.4 Privileges . . . . . . . . . . . . . . . . . . . . 4-2 RSX System Generation Guide Page 3 4.5 Process Quota . . . . . . . . . . . . . . . . . . 4-2 4.6 Defaults . . . . . . . . . . . . . . . . . . . . . 4-2 4.7 Log File . . . . . . . . . . . . . . . . . . . . . 4-2 4.8 Logical Names And Symbols - Caution . . . . . . . 4-3 4.9 Port Line . . . . . . . . . . . . . . . . . . . . 4-3 4.10 ARGUS . . . . . . . . . . . . . . . . . . . . . . 4-3 CHAPTER 5 CHECKLIST PRIOR TO LAYERED PRODUCTS INSTAL. OR UPDATE 5.1 Tapes . . . . . . . . . . . . . . . . . . . . . . 5-1 5.2 Disks . . . . . . . . . . . . . . . . . . . . . . 5-1 5.3 RSX Layered Product Documentation . . . . . . . . 5-1 5.4 Privileges . . . . . . . . . . . . . . . . . . . . 5-1 5.5 Process Quota . . . . . . . . . . . . . . . . . . 5-2 5.6 Defaults . . . . . . . . . . . . . . . . . . . . . 5-2 5.7 Log File . . . . . . . . . . . . . . . . . . . . . 5-2 5.8 Logical Names And Symbols - Caution . . . . . . . 5-2 CHAPTER 6 CHECKLIST PRIOR TO COPYING FERMI/DECUS ADDDITIONS 6.1 DECUS Additions . . . . . . . . . . . . . . . . . 6-1 6.1.1 SRD . . . . . . . . . . . . . . . . . . . . . . 6-1 6.1.2 TECO . . . . . . . . . . . . . . . . . . . . . . 6-1 6.2 Fermi Additions . . . . . . . . . . . . . . . . . 6-1 6.2.1 Drivers . . . . . . . . . . . . . . . . . . . . 6-1 6.2.2 Include Files . . . . . . . . . . . . . . . . . 6-2 6.2.3 IOPAGE . . . . . . . . . . . . . . . . . . . . . 6-2 6.2.4 MULTI Utility Files . . . . . . . . . . . . . . 6-2 6.2.5 RMDLSI . . . . . . . . . . . . . . . . . . . . . 6-2 6.2.6 System Manager Area . . . . . . . . . . . . . . 6-2 CHAPTER 7 AN RSX SYSTEM BUILD OUTLINE 7.1 RSX System Creation Outline . . . . . . . . . . . 7-1 7.2 Editing The VMR File . . . . . . . . . . . . . . . 7-6 7.2.1 Before Sysgen Phase III . . . . . . . . . . . . 7-6 7.2.2 After Sysgen Phase III . . . . . . . . . . . . . 7-7 CHAPTER 8 AN RSX LAYERED PRODUCTS INSTALLATION AND UPDATE 8.1 PDP-11 FORTRAN-77/RSX Installation And Update . . 8-1 8.2 PDP-11 Symbolic Debugger/RSX Installation . . . . 8-2 CHAPTER 9 AN RSX FERMI/DECUS ADDITIONS INSTALLATION CHAPTER 10 SAMPLE UPDATE AND SYSGEN OUTPUT 10.1 RSX Update . . . . . . . . . . . . . . . . . . . 10-2 10.2 RSX Prepgen . . . . . . . . . . . . . . . . . . 10-17 RSX System Generation Guide Page 4 10.3 RSX Sysgen - Phase I And II . . . . . . . . . . 10-27 10.4 RSX Sysgen - Phase III . . . . . . . . . . . . . 10-38 CHAPTER 11 SAMPLE LAYERED PRODUCTS INSTALLATION AND UPDATE 11.1 PDP-11 FORTRAN-77/RSX Installation And Update . 11-2 11.2 PDP-11 Symbolic Debugger/RSX Installation . . . 11-6 CHAPTER 12 SAMPLE SRD INSTALLATION CHAPTER 13 SAMPLE GENERATION OF HELP FILES CHAPTER 14 SAMPLE ERROR LOGGING LIBRARY TUNING CHAPTER 15 SYSGEN ETC. AFTER RSX V4.2 15.1 Parameter Change . . . . . . . . . . . . . . . . 15-1 15.2 Minor Constant Change . . . . . . . . . . . . . 15-1 15.3 Major Flow Change . . . . . . . . . . . . . . . 15-2 15.4 Additions Change . . . . . . . . . . . . . . . . 15-3 APPENDIX A ANSWER SHEET FOR PREPGEN APPENDIX B ANSWER SHEET FOR SYSGEN PHASE I AND II APPENDIX C ANSWER SHEET FOR SYSGEN PHASE III C.1 Task Build Non-Pivileged Tasks . . . . . . . . . . C-1 C.2 Task Build Privileged Tasks . . . . . . . . . . . C-1 CHAPTER 1 INTRODUCTION 1.1 Statement Of Problem Generating RSX systems is a multi-step process, including: 1. The DEC distribution tapes (RSX sources) must be copied to disks (using RSX BRU) and updates applied before a sysgen can be started. The target system uses RL02 disks, so the RL01/2 distribution kit is used. 2. Backups of the disks should be made before and after updates are applied, and after the sysgen is completed. 3. Each sysgen involves 3 phases which may or may not be performed at the same login session. Additional steps may be required before sysgen, between phases, or afterwards. 4. The newly gen'ed system must be put on a disk where it can be made hardware bootable. 5. Layered products must be installed from DEC distribution tapes, and have updates applied. 6. A number of additional products and tools, developed here at Fermi or by DECUS, complete the software package delivered to experimenters or other users as an RSX system. All updates and sysgens are to be executed on BISON using virtual disks. Seven MD virtual disks contain the RSX RL01 distribution kit originally located on magtape; each MD disk is configured to look like an RL01. These virtual disks are manipulated in many different ways during the above steps. Using virtual disks, and executing RSX command procedures under VMS, require that appropriate setup be done before the updates and sysgen phases in order to establish the environment in which they execute. It is very easy to forget a step in this complex process; doing so may render useless several hours of work. INTRODUCTION Page 1-2 1.2 Solution It is clear that a consistent documented procedure is needed to reduce the possibility of error while doing an RSX sysgen and to simplify the RSX sysgen procedure. The RSX sysgen procedure can not be fully automated because the procedure subtly changes with each RSX version; the sysgen process can, however, be broken into separately automated pieces which, when put together, perform the entire sysgen. These pieces appear as individual VMS command files. Each step of the sysgen process will usually involve running many of these command procedures along with user input commands. Hopefully the command procedures are general enough to require little alteration in order to work with later versions of RSX. This document describes these command procedures, how to use them to perform an RSX sysgen from start (RSX sources on tape) to finish (RSX bootable system on disk complete with layered products) and provides help in tuning the command procedures to work with subsequent versions of RSX. 1.3 MD Virtual Disk Error Messages - A Warning The MD driver used extensively throughout the RSX update and sysgen procedures has a tendency to report error messages in situations that are not the result of errors. For example, if an association of a file to an MD disk is attempted when the file is already associated to the disk, the reported error message says the file in question cannot be read. The message should say that the said MD disk is already associated with a file. If MD error messages (not in standard VMS format) are reported throughout the RSX update or sysgen procedures, make sure an error condition has actually occurred before attempting any error fix or change. CHAPTER 2 DEFAULTS All of the RSX sysgen command procedures described in this document assume the following defaults. In most cases these defaults can be changed by entering the new value as a parameter. The defaults which can always be changed by entering them as a parameter, are marked with the flag - PARAM. See the individual command procedure descriptions for more information on which defaults are parameter based. o RL02 with/for RSX system - DLA1: (PARAM) o RL02 with/for system and product updates - DLA0: (PARAM) o Magtape - MFA0: (PARAM) o RM03 disk - DRA1: (PARAM) o RM03 label - RSXSYSGEN (PARAM) o Directory of virtual disk files - DRA1:[VIRTUAL] (PARAM) o Directory of RSX sysgen command files - RSX_FACTORY$COMMANDS o Directory of RSX sysgen help files - RSX_FACTORY$HELP o Directory of latest version of RSX - RSX11M$ROOT o Names of RSX virtual disk files and associated virtual devices - 1. RSXM38.DSK - MDB0 (for update), MDB1 (for sysgen) (PARAM) 2. EXCPRV.DSK - MDB2 3. PRVBLD.DSK - MDB3 4. RLUTIL.DSK - MDB4 5. MCRSRC.DSK - MDB5 6. HLPDCL.DSK - MDB6 DEFAULTS Page 2-2 7. RMSV20.DSK - MDB7 o The RSX BRU backup sets DLSYS and RSXBAS are both copied to the single virtual disk - RSXM38 o RSX virtual disk and logical assignments - 1. MDB0: - DL10 2. MDB1: - DL11 3. MDB2: - DL12 4. MDB3: - DL13 5. MDB4: - DL14 6. MDB5: - DL15 7. MDB6: - DL16 8. MDB7: - DL17 o The virtual disks are the same size and geometry as an RL01. o The layered products and system update disk created by the command file BRU_UPDATES_TO_DISK, gets the RSX DLKIT copied to it automatically. o All RSX command files use the RSX logicals SR:, DS:, and UP: as the source and destination in any copy, rename or assign operations. CHAPTER 3 COMMAND PROCEDURE DESCRIPTIONS The following sections describe the various command procedures available to enable an RSX sysgen to be completed with a minimum of difficulty and time expenditure. Please note: All of the command files assume that the command file SETUP_FOR_RSX_U_S.COM has already been executed. COMMAND FILES USED IN AN RSX ... -------------------------------- SETUP UPDATE SYSGEN ----- ------ ------ BACKUP_DIR_TO_TAPE ASSOC_UPDATE ASSOC_SYSGEN BRU_TAPE_TO_MD_DISKS BACKUP_DIR_TO_TAPE BRU_MD_DISK_TO_DISK BRU_UPDATES_TO_DISK BISON_BACKUP BRU_MD_DISKS_TO_TAPE CREATE_RM03 PREUPDATE CLEANUP SETUP_FOR_RSX_U_S PROTECTION POST_SYSGEN3 PREHELP PRESYSGEN RSXVMR F77 UPDATE & DEBUG UPDATE & INSTALLATION INSTALLATION ------------ -------------- CLEANUP_F77 PRELPRODUCT INSTALF77 SETUPDBGI PRELPRODUCT SETUPF77U FERMI ADDITIONS AND DECUS ADDITIONS INSTALLATION ------------------- ADDITIONS PRETUNE PRIVILEGE COMMAND PROCEDURE DESCRIPTIONS Page 3-2 3.1 ADDITIONS Copy the RSX Fermi Additions and the RSX DECUS Additions from the appropriate areas to the master RSX system disk. The following operations are performed - o Compress system libraries and F77 libraries o Copy the following files to the system disk - Catchall.Cmd Tec.Tsk Libedt.Tsk, Libext.Tsk, Liblst.Tsk, Rbu.Tsk Srd.Tsk Srd help files Rmd build and ODL files Error log libraries Indsys.Clb Finalz.Cmd, Initlz.Cmd, Logout.Cmd, Shutup.Cmd, Startup.Cmd, TTsetup.Cmd Drerr.Inc, Ioerr.Inc, Rdbdf.Inc, Wdbdf.Inc Iopage files MT and MM Driver source update files MJ Driver sources o Update library and rebuild the RMD and RDMLSI tasks o Update sources, reassemble and rebuild the MT and MM drivers o Assemble and build the MJ driver Calling Command Line - @RSX_FACTORY$COMMANDS:ADDITIONS RSX_disk where RSX_disk - RSX name of device containing the master RSX system disk default = DL1: COMMAND PROCEDURE DESCRIPTIONS Page 3-3 3.2 ASSIGN_MD_TO_DL Assign RSX recognizable logical names to the MD devices as follows - MDB0: - DL10 MDB1: - DL11 MDB2: - DL12 MDB3: - DL13 MDB4: - DL14 MDB5: - DL15 MDB6: - DL16 MDB7: - DL17 Calling Command Line - @RSX_FACTORY$COMMANDS:ASSIGN_MD_TO_DL Assumed defaults - * RSX virtual disks and logical assignments will be as in chapter 2. COMMAND PROCEDURE DESCRIPTIONS Page 3-4 3.3 ASSOC_SYSGEN Associate devices MDB1 thru MDB7 with the RSX source virtual disks in preparation for a sysgen. The following associations are performed - MDB1 - RSXM38.DSK MDB2 - EXCPRV.DSK MDB3 - PRVBLD.DSK MDB4 - RLUTIL.DSK MDB5 - MCRSRC.DSK MDB6 - HLPDCL.DSK MDB7 - RMSV20.DSK Calling Command Line - @RSX_FACTORY$COMMANDS:ASSOC_SYSGEN disk_dir min max file where disk_dir - directory of the virtual disk files default = DRA1:[VIRTUAL] min - minimum MD device unit number at which to start the associations default = 1 max - maximum MD device unit number at which to stop the associations default = 7 file - name of primary virtual disk file default = RSXM38 All missing parameters are defaulted. Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP * Names of virtual disks are as stated in chapter 2. * Virtual disks are associated with the virtual devices as stated in chapter 2. * The size and geometry of the virtual disks are the same as for an RL01. COMMAND PROCEDURE DESCRIPTIONS Page 3-5 3.4 ASSOC_UPDATE Associate devices MDB0 thru MDB7 with the RSX source virtual disks in preparation for an update. The following associations are performed - MDB0 - RSXM38.DSK MDB2 - EXCPRV.DSK MDB3 - PRVBLD.DSK MDB4 - RLUTIL.DSK MDB5 - MCRSRC.DSK MDB6 - HLPDCL.DSK MDB7 - RMSV20.DSK Calling Command Line - @RSX_FACTORY$COMMANDS:ASSOC_UPDATE disk_dir min max file where disk_dir - directory of the virtual disk files default = DRA1:[VIRTUAL] min - minimum MD device unit number at which to start the associations default = 0 max - maximum MD device unit number at which to stop the associations default = 7 file - name of primary virtual disk file default = RSXM38 All missing parameters are defaulted. Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP * Names of virtual disks are as stated in chapter 2. * Virtual disks are associated with the virtual devices as stated in chapter 2. * The size and geometry of the virtual disks are the same as for an RL01. COMMAND PROCEDURE DESCRIPTIONS Page 3-6 3.5 BACKUP_DIR_TO_TAPE Backup all the files under the entered directory to magtape. Calling Command Line - @RSX_FACTORY$COMMANDS:BACKUP_DIR_TO_TAPE save_set label tape disk_dir where save_set - save set name label - label of tape if tape is to be initialized, else blank tape - magtape device default = MFA0: disk_dir - directory of the virtual disk files default = DRA1:[VIRTUAL] Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP COMMAND PROCEDURE DESCRIPTIONS Page 3-7 3.6 BISON_BACKUP Backup each of the virtual disks to an area on BISON as flat files. Calling Command Line - @RSX_FACTORY$COMMANDS:BISON_BACKUP dest where dest - destination area or logical, must to have [dirname...] appended to it default = RSX11M$ROOT: Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP * Directory of latest version of RSX is RSX11M$ROOT * Names of virtual disks are as stated in chapter 2. * Virtual disks are associated with the virtual devices as stated in chapter 2. COMMAND PROCEDURE DESCRIPTIONS Page 3-8 3.7 BRU_MD_DISK_TO_DISK Using the MCR BRU command, copy the contents of the virtual disk entered to the appropriate hard disk. An 'Analyze/Media' is performed on the hard disk prior to any copying. The hard disk is then initialized. Calling Command Line - @RSX_FACTORY$COMMANDS:BRU_MD_DISK_TO_DISK hard_disk virtual_disk where hard_disk - RSX name of the device containing the hard disk default = DL1: virtual_disk - RSX name of the device associated with the virtual disk default = DL11: All missing parameters are defaulted. Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP * RSX virtual disks and logical assignments exist as in chapter 2. COMMAND PROCEDURE DESCRIPTIONS Page 3-9 3.8 BRU_MD_DISKS_TO_TAPE Using the MCR BRU command, copy the contents of all the virtual disks to the appropriate magtape. The magtape is not initialized. Calling Command Line - @RSX_FACTORY$COMMANDS:BRU_MD_DISKS_TO_TAPE magtape file where magtape - RSX name of the device containing the tape default = MF0: file - name of primary virtual disk file default = RSXM38 All missing parameters are defaulted. Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP * Names of virtual disks are as stated in chapter 2. * Virtual disks are associated with the virtual devices as stated in chapter 2. * RSX virtual disks and logical assignments exist as in chapter 2. * The magtape has previosly been initialized. COMMAND PROCEDURE DESCRIPTIONS Page 3-10 3.9 BRU_RSX_DISK_TO_DISK BRU the new RSX system from the master RL02 to a distribution disk. An 'Analyze/Media' is performed on the distribution disk prior to any copying. The disk is then initialized. The following UIC's are copied in their entirety to the new disk - [1,1] : System Libraries [1,2] : System Message, Help and Command Files [1,3] : Lost Files (found by VFY) [1,4] : Console Log files and PMD dumps [1,6] : Error Log files [1,24] : Executive Task Build Command Files and Object Libraries [1,34] : Executive and System Maps [1,54] : Executive and System Tasks [200,200] : Sysgen Command Files Select files from the following UIC's are also copied - [11,10] : Driver Sources Calling Command Line - @RSX_FACTORY$COMMANDS:BRU_RSX_DISK_TO_DISK RSX_disk dest label where RSX_disk - device containing the master RSX system disk default = DL1: dest - device containing the new distribution disk default = DL0: label - label of the distribution disk default = RSXM38 All missing parameters are defaulted. Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS COMMAND PROCEDURE DESCRIPTIONS Page 3-11 3.10 BRU_TAPE_TO_MD_DISKS Using RSX BRU, copy the DEC distributed RSX sources to the appropriate virtual disks. Each virtual disk is initialized prior to any copying. The following copy operations are performed - DLSYS + RSXBAS --> DL10: EXCPRV --> DL12: PRVBLD --> DL13: RLUTIL --> DL14: MCRSRC --> DL15: HLPDCL --> DL16: RMSV20 --> DL17: Calling Command Line - @RSX_FACTORY$COMMANDS:BRU_TAPE_TO_MD_DISKS source where source - The RSX name of the device containing the DEC distributed RSX sources. default = MF0: All missing parameters are defaulted. Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP * Names of virtual disks are as stated in chapter 2. * Virtual disks are associated with the virtual devices as stated in chapter 2. * RSX virtual disks and logical assignments exist as in chapter 2. COMMAND PROCEDURE DESCRIPTIONS Page 3-12 3.11 BRU_UPDATES_TO_DISK Using RSX BRU, copy the desired layered product updates from the DEC update device to a hard disk. Also copy the update DLKIT to the hard disk. An 'Analyze/Media' is performed on the hard disk prior to any copying. The hard disk is then initialized. Calling Command Line - @RSX_FACTORY$COMMANDS:BRU_UPDATES_TO_DISK source dest prod1 ... where source - The RSX name of the device containing the DEC distributed copy of the layered product updates. default = MF0: dest - The RSX name of the device to which the selected updates are to be copied. default = DL1: prod1\ to | - A list of the layered product file names prod5/ Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS COMMAND PROCEDURE DESCRIPTIONS Page 3-13 3.12 CLEANUP Delete all unnecessary files from the virtual disk containing the newly genned system. The following operations are performed - o The protection for all files is set to the default o A general purge is done in [1,54] o The following files are deleted from [1,54] - ACF.BSL;0, BASVMR.CMD;0, FCPSML.TSK;0, PUCOM.*;0, RCT.TSK;0, SGNPARM.CMD;0 o all driver maps are deleted from [1,34], except TTDRV.MAP o The following files are deleted from [11,10] - ICDRV.MAC;0, ISDRV.MAC;0 o The following files are deleted from [200,200] - BLDLAINIT.CMD;0, SGNKLAB.CMD;0, SYSSAVED2.CMD;0 o All *DRV.*;1 are deleted from [1,54] if confirmed o A purge/confirm is done in [*,*] In general the *.DRV deletion process is as follows - [001,054]DBDRV.TSK;1, delete? [N]:y [001,054]DBDRV.STB;1, delete? [N]:y [001,054]DDDRV.TSK;1, delete? [N]:y [001,054]DDDRV.STB;1, delete? [N]:y [001,054]DMDRV.TSK;1, delete? [N]:y [001,054]DMDRV.STB;1, delete? [N]:y [001,054]DPDRV.TSK;1, delete? [N]:y [001,054]DPDRV.STB;1, delete? [N]:y [001,054]DRDRV.TSK;1, delete? [N]:y [001,054]DRDRV.STB;1, delete? [N]:y [001,054]DUDRV.TSK;1, delete? [N]:y [001,054]DUDRV.STB;1, delete? [N]:y [001,054]MSDRV.TSK;1, delete? [N]:y [001,054]MSDRV.STB;1, delete? [N]:y [001,054]MUDRV.TSK;1, delete? [N]:y [001,054]MUDRV.STB;1, delete? [N]:y [001,054]TTDRV.TSK;1, delete? [N]: [001,054]TTDRV.STB;1, delete? [N]: [001,054]CODRV.TSK;1, delete? [N]: [001,054]CODRV.STB;1, delete? [N]: Calling Command Line - @RSX_FACTORY$COMMANDS:CLEANUP MD_device where COMMAND PROCEDURE DESCRIPTIONS Page 3-14 MD_device - device associated with the virtual disk containing the newly genned system default = MDB1: All missing parameters are defaulted. Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP COMMAND PROCEDURE DESCRIPTIONS Page 3-15 3.13 CLEANUP_F77 Delete all unnecessary files from the RSX system disk after an F77 installation and/or update. The following files are renamed to their correct names - [1,1]F4P*.* [1,1]F77*.* Calling Command Line - @RSX_FACTORY$COMMANDS:CLEANUP_F77 RSX_disk where RSX_disk - device containing RSX system disk default = DLA1: Assumed defaults - * None COMMAND PROCEDURE DESCRIPTIONS Page 3-16 3.14 CREATE_RM03 Initialize, Mount and create the appropriate directories and virtual disks to be used in an RSX sysgen. An 'Analyze/Media' is done on the RM03 first. Calling Command Line - @RSX_FACTORY$COMMANDS:CREATE_RM03 disk_dir file label where disk_dir - directory of the virtual disk files default = DRA1:[VIRTUAL] file - name of primary virtual disk file default = RSXM38 label - label of the RM03 default = RSXSYSGEN All missing parameters will be defaulted. Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP * Names of virtual disks are as stated in chapter 2. * Virtual disks will be associated with the virtual devices as stated in chapter 2. * The size and geometry of the virtual disks are the same as for an RL01. COMMAND PROCEDURE DESCRIPTIONS Page 3-17 3.15 CREATE_RSX_MD_DISKS Create the virtual disks used during an RSX sysgen. Calling Command Line - @RSX_FACTORY$COMMANDS:CREATE_RSX_MD_DISKS disk_dir file where disk_dir - directory of the virtual disk files default = DRA1:[VIRTUAL] file - name of primary virtual disk file default = RSXM38 All missing parameters are defaulted. Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP * Names of virtual disks are as stated in chapter 2. * Virtual disks will be associated with the virtual devices as stated in chapter 2. * The size and geometry of the virtual disks are the same as for an RL01. COMMAND PROCEDURE DESCRIPTIONS Page 3-18 3.16 DISASSOCIATE Disassociate the virtual disk files from the MD units. The command file disassociates MD devices MDB0 through MDB7. If one or more of these MD devices was not associated to any file, an error message will be displayed. This message can be ignored. Calling Command Line - @RSX_FACTORY$COMMANDS:DISASSOCIATE min max where min - minimum MD device unit number at which to start the disassociations default = 0 max - maximum MD device unit number at which to stop the disassociations default = 7 All missing parameters are defaulted. Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP COMMAND PROCEDURE DESCRIPTIONS Page 3-19 3.17 INSTALF77 Perform the F77 installation procedure as stated in the PDP-11 FORTRAN-77/RSX installation guide. This is an RSX command file. The F77 source tape must be mounted on an MF tape drive. This is due to problems with FLX recognizing drivers. Calling Command Line - @RSX_FACTORY$COMMANDS:INSTALF77 Assumed defaults - * The logical DS: has been assigned to the destination device. * The logical SR: has been assigned to the source device. COMMAND PROCEDURE DESCRIPTIONS Page 3-20 3.18 MDDISK Handles the processing of all the commands relating to the MD virtual devices. The following functions can be performed - (these functions are performed in the following order no matter in which order they are entered) HELP - obtain help on all the RSX system command files ASSO - associate a virtual disk to an MD device INIT - initialize the virtual device MOUN - mount the virtual device DISM - dismount the virtual device DISA - disassociate a virtual disk from an MD device Qualifiers to the above parameters (except help) are specified by including them as /QUAL after one of the above commands. For example, to mount a virtual device as foreign use the following command - MOUN/FOR. Any legal qualifiers on the above commands can be enterd in this manner. Calling Command Line - @RSX_FACTORY$COMMANDS:MDDISK device virt_file comm1 comm2 ... where device - the MD device to access in the commands virt_file - the virtual file name connected to the MD device comm1 \ to | - commands/qualifiers (as described above) to comm2 / be performed on the entered device and file Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP COMMAND PROCEDURE DESCRIPTIONS Page 3-21 3.19 POST_SYSGEN3 Delete old versions of the tasks that were rebuilt in sysgen phase III. This is accomplished by doing a general purge of [1,54] Calling Command Line - @RSX_FACTORY$COMMANDS:POST_SYSGEN3 MD_device where MD_device - device associated with the virtual disk containing the newly genned system default = MDB1: All missing parameters are defaulted. Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP COMMAND PROCEDURE DESCRIPTIONS Page 3-22 3.20 PREHELP Perform the general setup prior to constructing the RSX help library. The following steps are performed - o Set Default to UIC [1,2] on the RSX master system disk o Spawn/Cli=MCR Calling Command Line - @RSX_FACTORY$COMMANDS:PREHELP MD_device where MD_device - device associated with the virtual disk containing the RSX help files default = MDB6: COMMAND PROCEDURE DESCRIPTIONS Page 3-23 3.21 PRELPRODUCT Perform the general setup prior to installing or updating an RSX layered product (PDP-11 FORTRAN-77/RSX, PDP-11 Symbolic Debugger/RSX) Calling Command Line - @RSX_FACTORY$COMMANDS:PRELPRODUCT source RSX_disk updat_disk where source - device containing DEC layered product distribution default = MF0: RSX_disk - device containing the RSX system disk default = DL1: updat_disk - device containing the layered product update kit default = DL0: Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS COMMAND PROCEDURE DESCRIPTIONS Page 3-24 3.22 PRESYSGEN Perform the necessary setup before doing an RSX prepgen, sysgen or phase III sysgen. This command file should be executed in addition to the SETUP_FOR_RSX_U_S command file. The following steps are performed - o Assign/Job Sys$disk LB o Mount MDB1 o Set Default to MDB1:[200,200] o Spawn/Cli=MCR Calling Command Line - @RSX_FACTORY$COMMANDS:PRESYSGEN Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP * Virtual disks are associated with the virtual devices as stated in chapter 2. COMMAND PROCEDURE DESCRIPTIONS Page 3-25 3.23 PRETUNE Perform the necessary setup before tuning the error logging library. This command file should be executed after the ADDITIONS command file. The following steps are performed - o Set privileges o Set default protection o Set Default to UIC [1,6] on the RSX master system disk o Spawn/Cli=MCR Calling Command Line - @RSX_FACTORY$COMMANDS:PRETUNE disk where disk - Device containing the RSX master system disk default = DLA0: COMMAND PROCEDURE DESCRIPTIONS Page 3-26 3.24 PREUPDATE Perform the necessary setup before doing an RSX update. This command file should be executed in addition to the SETUP_FOR_RSX_U_S command file. The following steps are performed - o Mount MDB0 o Set Default to MDB0:[200,200] o Spawn/cli=MCR Calling Command Line - @RSX_FACTORY$COMMANDS:PREUPDATE Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP * Virtual disks are associated with the virtual devices as stated in chapter 2. COMMAND PROCEDURE DESCRIPTIONS Page 3-27 3.25 PRIVILEGE Set the necessary privileges to access all devices and perform RSX updates and sysgens. The following privileges are set - SYSPRV CMKRNL VOLPRO LOG_IO SYSNAM Calling Command Line - @RSX_FACTORY$COMMANDS:PRIVILEGE flag where flag - if = "", turn the privileges on = anything else, turn the privileges off COMMAND PROCEDURE DESCRIPTIONS Page 3-28 3.26 PROTECTION Set the default protection and then set all the files in the virtual disks to this protection. The default protection is - (SYSTEM:RWE,OWNER:RWE,GROUP:RWE,WORLD:R) Calling Command Line - @RSX_FACTORY$COMMANDS:PROTECTION COMMAND PROCEDURE DESCRIPTIONS Page 3-29 3.27 RSXVMR This RSX command file VMR's the new RSX disk. It does the following - Set /uic=[1,54] Asn sy:[1,54]Vmr.Tsk=Vmr Asn sy:=lb: Del Rsx11m.Sys;* Pip Rsx11m.Sys/bl:498.=Rsx11m.Tsk VMR @Sysvmr Calling Command Line - @RSX_FACTORY$COMMANDS:RSXVMR Assumed defaults - * The logical SY: has been assigned to the RSX disk. COMMAND PROCEDURE DESCRIPTIONS Page 3-30 3.28 SETUPDBGI This RSX command file performs the following steps to set up for the Debug installation - Asn ds:=sy: Asn sr:=mf: BRU/Dens:1600/Bac:DBGREL/Rew/Noi/Ufd/New MF: SY: BRU/Dens:1600/Bac:INSTAL/Rew/Noi/Ufd/New MF: SY: Set /uic=[247,200] Ufd [247,200] Copy up:[247,200]*.* sy:[247,200] Asn =sy: Asn =mf: Set /uic=[1,61] Calling Command Line - @RSX_FACTORY$COMMANDS:SETUPDBGI Assumed defaults - * The logical DS: has been assigned to the destination device. * The logical SR: has been assigned to the source device. * The logical UP: has been assigned to the update device. * The Debug source tape is mounted in an MF tape drive. COMMAND PROCEDURE DESCRIPTIONS Page 3-31 3.29 SETUPF77U Perform the F77 update preparation as stated in the F77 update notes. This is an RSX command file. Calling Command Line - @RSX_FACTORY$COMMANDS:SETUPF77U Assumed defaults - * The logical DS: has been assigned to the destination device. * The logical UP: has been assigned to the update device. * The F77 source tape is mounted in an MF tape drive. COMMAND PROCEDURE DESCRIPTIONS Page 3-32 3.30 SETUP_FOR_RSX_U_S Executes the following steps to setup for any RSX update or sysgen operation. This command file need only be executed once for each login. o Execute the PRIVILEGE command file o Execute the ASSIGN_MD_TO_DL command file o Mount the RM03 if not mounted o Report to user if virtual disk files do not exist o Execute either ASSOC_SYSGEN or ASSOC_UPDATE Calling Command Line - @RSX_FACTORY$COMMANDS:SETUP_FOR_RSX_U_S flag disk_dir file label where flag - if = "S" then execute ASSOC_SYSGEN = "U" then execute ASSOC_UPDATE else do neither disk_dir - directory of the virtual disk files default = DRA1:[VIRTUAL] file - name of primary virtual disk file default = RSXM38 label - label of the RM03 disk default = RSXSYSGEN Assumed defaults - * Directory of RSX sysgen command files is RSX_FACTORY$COMMANDS * Directory of RSX sysgen help files is RSX_FACTORY$HELP * Names of virtual disks are as stated in chapter 2. * Virtual disks are associated with the virtual devices as stated in chapter 2. * RSX virtual disks and logical assignments will be as in chapter 2. * The size and geometry of the virtual disks are the same as for an RL01. COMMAND PROCEDURE DESCRIPTIONS Page 3-33 3.31 Command File Dependencies The following chart shows all the procedure calls in each command file. COMMAND FILE NAME CALLS ----------------- ----- Additions - Assign_MD_To_DL - Assoc_Sysgen Assoc_Update Mddisk Assoc_Update Mddisk Backup_Dir_To_Tape Disassociate Mddisk BISON_Backup Mddisk BRU_MD_Disks_To_Tape Mddisk BRU_MD_Disk_To_Disk Mddisk BRU_RSX_Disk_To_Disk - BRU_Tape_To_MD_Disks Mddisk BRU_Updates_To_Disk - Cleanup Mddisk Cleanup_F77 - Create_RM03 Create_RSX_MD_Disks Privilege Create_RSX_MD_Disks Mddisk Disassociate Mddisk InstalF77 - Mddisk - Post_Sysgen3 Mddisk Prehelp Mddisk Prelproduct Privilege Presysgen Mddisk Pretune Privilege Preupdate Mddisk Privilege - Protection - RSXVMR - SetupDbgI - SetupF77U - Setup_For_RSX_U_S Assoc_Sysgen Assoc_Update Assign_MD_To_DL Privilege CHAPTER 4 CHECKLIST PRIOR TO RSX UPDATE OR RSX SYSGEN The following discussion concerns steps that should be done before any of the sysgen procedure described in chapter 7 has been started. The steps in the next sections should be general enough to be applied to any RSX sysgen that is to be done. 4.1 Tapes The DEC distributed RSX source tape, RSX update tape and RSX layered product tapes must be available. 4.2 Disks Access must be allowed to the following devices - An RL02 disk drive A magtape drive for the DEC distributed tapes (dens = 1600) The MD virtual disk devices The RM03 (or similar) device which stores the virtual disks Two empty RL02 disks and three empty tapes must also be available. These will be used for the following - o 1st RL02 : update information put here o 2nd RL02 : master RSX system disk o 1st tape : BACKUP copy of original RSX distribution o 2nd tape : BACKUP copy of updated RSX distribution o 3rd tape : BRU copy of RSX sysgenned system CHECKLIST PRIOR TO RSX UPDATE OR RSX SYSGEN Page 4-2 4.3 RSX Sysgen Documentation Read the current RSX sysgen documentation, any notes supplied with the DEC distributed tapes and the RSX release notes to make sure the procedure has not changed from previous versions of RSX. If it has, see chapter 15. 4.4 Privileges The following privileges are used during the sysgen procedure - CMKRNL EXQUOTA LOG_IO SYSNAM SYSPRV VOLPRO The sysgen procedure must be run from a process that can set these privileges. 4.5 Process Quota Because all the work is done in subprocesses that are 2 or 3 levels deep in the job tree, it is recommended that the sysgen be done from an account with a subprocess quota of at least 4. 4.6 Defaults Make sure all of the defaults (discussed in chapter 2) are understood and those that are not parameter based have not changed. If they have, see chapter 15. Be aware of the defaults that need to be changed through parameters and which command files they effect. 4.7 Log File A log file of the sysgen may be obtained by using SET HOST /LOG=filespec BISON SET TERM /NOBROADCAST which also set the terminal to avoid mail and phone messages in the log file. CHECKLIST PRIOR TO RSX UPDATE OR RSX SYSGEN Page 4-3 4.8 Logical Names And Symbols - Caution It is recommended that all process logical names be deassigned after login, or that the login be done with the /NOCOMMAND switch to avoid defining process logical names and symbols in the first place. This is because a process logical or symbol that happens to have the same name as a command file or a task executed by sysgen could cause the procedure to fail in an obscure fashion. To deassign logicals, use DEASSIGN /PROCESS /ALL 4.9 Port Line The terminal connection to the BISON computer must be made over a port line that will not time out after a period of inactivity. Once the RSX sysgen gets going, the terminal will be tied up for a substantial amount of time. Unless the port line it is connected to does not time out, the terminal will be disconnected in the middle of the sysgen. The dedicated no time out port line may also be set to be ignored by ARGUS, but this is not sufficient, at least for the current version of ARGUS. 4.10 ARGUS The ARGUS program must be suspended during the RSX sysgen because most of the work is being done in a sub-subprocess and ARGUS does not credit the parent process with any activity. If not suspended, ARGUS will abort the process doing the sysgen before the sysgen has completed. To suspend ARGUS execute the following command file - @FERMI$MGR_UTIL:SUSPEND_ARGUS To resume ARGUS once the sysgen procedure has completed execute the following command file - @FERMI$MGR_UTIL:RESUME_ARGUS CHAPTER 5 CHECKLIST PRIOR TO LAYERED PRODUCTS INSTAL. OR UPDATE The following discussion concerns steps that should be done before any of the RSX layered product installations or updates have been started. 5.1 Tapes The DEC distributed RSX layered product source tape, RSX update disk and RSX system disk must be available. 5.2 Disks Access must be allowed to the following devices - Two RL02 disk drives A magtape drive for the DEC distributed tape (dens = 1600) 5.3 RSX Layered Product Documentation Read the current RSX layered product documentation (installation guide and update release notes) and any notes supplied with the DEC distributed tapes to see if the installation or update procedure has changed from previous version of the RSX layered product. If it has, alter the procedure in the command file to match the documented procedure. 5.4 Privileges The following privileges are used during the layered products procedures - CMKRNL CHECKLIST PRIOR TO LAYERED PRODUCTS INSTAL. OR UPDATE Page 5-2 LOG_IO SYSNAM SYSPRV VOLPRO The update or installation procedure must be run from a process that can set these privileges. 5.5 Process Quota Because all the work is done in subprocesses that are 2 or 3 levels deep in the job tree, it is recommended that the updates and installations be done from an account with a subprocess quota of at least 4. 5.6 Defaults Make sure all of the defaults (discussed in chapter 2) are understood. Be aware of the defaults that need to be changed through parameters and which command files they effect. 5.7 Log File A log file of the update or installation may be obtained by using SET HOST /LOG=filespec BISON SET TERM /NOBROADCAST which also set the terminal to avoid mail and phone messages in the log file. 5.8 Logical Names And Symbols - Caution It is recommended that all process logical names be deassigned after login, or that the login be done with the /NOCOMMAND switch to avoid defining process logical names and symbols in the first place. This is because a process logical or symbol that happens to have the same name as a command file or a task executed during an update or installation could cause the procedure to fail in an obscure fashion. To deassign logicals, use DEASSIGN /PROCESS /ALL CHAPTER 6 CHECKLIST PRIOR TO COPYING FERMI/DECUS ADDDITIONS The RSX Fermi and DECUS Additions are made up of a variety of software. Each piece must be handled indiviually when preparing it to be copied to the master RSX system disk. These procedures are outlined in the following sections. Often they involve editing or comparison with past versions of the files thus making any automated procedure impossible. 6.1 DECUS Additions 6.1.1 SRD The most recent version of SRD should be copied from a DECUS tape onto the appropriate area on BISON. Use the existing version setup as a guideline when creating any subsequent version areas. The SRD installation procedure as described in chapter 9 should then be executed. 6.1.2 TECO The most recent version of TECO should be copied from a DECUS tape onto the appropriate area on BISON. Use the existing version setup as a guideline when creating any subsequent version areas. 6.2 Fermi Additions Use the existing version setup as a guideline when creating any subsequent version areas for all the Fermi Addition files. 6.2.1 Drivers The drivers section of the Fermi Additions contains correction files to modify the DEC MT and MM drivers to eliminate the powerfail protection feature. It also contains the MJ driver, which is itself a version of the DEC MM driver modified to allow the driver to handle the STC 1921 drive with 1935 formatter CHECKLIST PRIOR TO COPYING FERMI/DECUS ADDDITIONS Page 6-2 and STC controller; this is a 1600/6250 bpi tape drive. Any major changes in the DEC MM driver should be reflected in the MJ driver. The assembly and task building of these drivers is done in the ADDITIONS command file. 6.2.2 Include Files The include files are DEC '.MAC' files extracted from the library RSXMAC.SML and then edited to become Fortran include files. (Note: These files did not change between V4.1 and V4.2 of RSX.) They are then copied by the ADDITIONS command file to the RSX disk. 6.2.3 IOPAGE These files need no preliminary setup and are copied by the ADDITIONS command file to the RSX disk. IOPAGE was originally assembled and built under VAX-11 RSX. 6.2.4 MULTI Utility Files These utility tasks should be copied from the latest release of RSX MULTI after a Multigen. They are then copied by the ADDITIONS command file to the RSX disk. 6.2.5 RMDLSI RMDLSI is a version of RMD enhanced to support ADM-3A terminals. Both RMD and RMDLSI are built to display the free space on RL disks by default. The new versions of the RMD files V1H*.* and the RMDBLD.BLD file should be compared with the old versions of these files. Any significant changes should be reflected in the corresponding A03*.* files, the RMDLSIBLD.CMD file, the RMDBLD.ODL file and the RMDBLD.CMD file in the RMDLSI area on BISON. RMD and RMDLSI are task built in the ADDITIONS command file. 6.2.6 System Manager Area This area contains many files useful in tailoring RSX systems. The STARTUP.CMD file is a modified version of the DEC distributed file. Use the existing STARTUP.CMD file as a guide to modifiying the new version. All the files are copied by the ADDITIONS command file to the RSX disk. CHAPTER 7 AN RSX SYSTEM BUILD OUTLINE The following steps describe the general procedure for completing an RSX sysgen (from DEC distribution tape to complete RSX system) and editing the SYSVMR file. 7.1 RSX System Creation Outline The procedure has been divided into separate portions as a single system generation is rarely completed at one login session. Each portion includes any setup necessary for that step. If the setup was done in an earlier portion in the same terminal session, the setup can be skipped. Setup steps that are duplicates of earlier steps are marked with an '*'. The following procedure assumes the defaults described earlier. 1. Setup RM03 Put Rm03 in drive (DRA1) @RSX_FACTORY$COMMANDS:privilege @RSX_FACTORY$COMMANDS:create_rm03 2. General system setup @RSX_FACTORY$COMMANDS:setup_for_rsx_u_s 3. Put RSX tapes on Bison, BRU them to MD disks, BACKUP the MD disks Load RSX sources tape in drive (MFA0) @RSX_FACTORY$COMMANDS:setup_for_rsx_u_s U @RSX_FACTORY$COMMANDS:bru_tape_to_md_disks Load empty tape in drive (MFA0) to use for BACKUP AN RSX SYSTEM BUILD OUTLINE Page 7-2 @RSX_FACTORY$COMMANDS:backup_dir_to_tape RSX11MV42.BCK BACKUP Load new disk in drive (DLA0) Load Update tape in drive (MFA0) Do directory of tape, note order of product files to BRU from tape: Mount/For mfa0: MCR BRU /REW/DIR MF0: The following call must list the products in same order as they appear on tape: @RSX_FACTORY$COMMANDS:bru_updates_to_disk "" "" decnet f77 f77dbg 4. Do Update Rewind update tape in drive (MFA0) @RSX_FACTORY$COMMANDS:setup_for_rsx_u_s U Deallocate and dismount device (DLA0) with updates created above @RSX_FACTORY$COMMANDS:preupdate @update (perform update as in answer sheets) BYE (exit MCR) @RSX_FACTORY$COMMANDS:protection Load another new tape into drive (MFA0) @RSX_FACTORY$COMMANDS:backup_dir_to_tape RSX11MV42B.BCK BACKUP @RSX_FACTORY$COMMANDS:assoc_sysgen Create the following directories - Dua0:[Rsx11msys.Rsx11m.Rsx11m_Vn_mx.Rsxm38] Dua0:[Rsx11msys.Rsx11m.Rsx11m_Vn_mx.Excprv] Dua0:[Rsx11msys.Rsx11m.Rsx11m_Vn_mx.Prvbld] Dua0:[Rsx11msys.Rsx11m.Rsx11m_Vn_mx.Rlutil] Dua0:[Rsx11msys.Rsx11m.Rsx11m_Vn_mx.Mcrsrc] Dua0:[Rsx11msys.Rsx11m.Rsx11m_Vn_mx.Hlpdcl] AN RSX SYSTEM BUILD OUTLINE Page 7-3 Dua0:[Rsx11msys.Rsx11m.Rsx11m_Vn_mx.Rmsv20] Define the following root: Define /trans=(term,conc) Rsx11m$root - Dua0:[Rsx11msys.Rsx11m.Rsx11m_Vn_mx.] @RSX_FACTORY$COMMANDS:bison_backup 5. Do Sysgen @RSX_FACTORY$COMMANDS:setup_for_rsx_u_s S @RSX_FACTORY$COMMANDS:presysgen Set /uic=[200,200] @sysgen (perform prepgen as in answer sheets) BYE (exit MCR) @RSX_FACTORY$COMMANDS:presysgen set /uic=[200,200] @sysgen (perform sysgen as in answer sheets) Edit the sysvmr.cmd file. This can be done with EDT for VAX-11 RSX Version 2.2 and above, but for earlier versions, must be done by attaching to the main process as follows: >Sho proc/sub 28-OCT-1986 15:04:01.45 User: BERG Processes in this tree: RSXGEN RSXGEN MCR (*) > Atta "RSXGEN" Now edit the sysvmr.cmd file, using EDT or whatever. $ Atta "MCR" AN RSX SYSTEM BUILD OUTLINE Page 7-4 Resume the sysgen. > Res MOU dl13: PRVBLD PIP dl11:[1,34]/cd/fo/nv=dl13:[1,34]*.map DMO dl13: BYE (exit MCR) 6. Cleanup after sysgen (*)@RSX_FACTORY$COMMANDS:setup_for_rsx_u_s S @RSX_FACTORY$COMMANDS:cleanup @RSX_FACTORY$COMMANDS:prehelp Set /uic=[1,2] LBR helpbuild.cmd=help.ulb/ex:build @helpbuild BYE (exit MCR) 7. Do Sysgen phase III (*)@RSX_FACTORY$COMMANDS:setup_for_rsx_u_s S @RSX_FACTORY$COMMANDS:presysgen Set /uic=[200,200] @sysgen3 (for non-privileged tasks, as in answer sheets) @sysgen3 (for privileged tasks, as in answer sheets) NOTE When building the non-privileged tasks in sysgen phase III, the tasks that are documented as being updated must be rebuilt. Check the update documentation for a list of these tasks. BYE (exit MCR) AN RSX SYSTEM BUILD OUTLINE Page 7-5 @RSX_FACTORY$COMMANDS:post_sysgen3 Edit the sysvmr.cmd file again. 8. Copy to tape Load new tape in drive (MFA0) (*)@RSX_FACTORY$COMMANDS:setup_for_rsx_u_s S @RSX_FACTORY$COMMANDS:bru_md_disks_to_tape 9. Copy to master disk Load new disk in drive (DLA1) (*)@RSX_FACTORY$COMMANDS:setup_for_rsx_u_s S @RSX_FACTORY$COMMANDS:bru_md_disk_to_disk Mount/over=id dla1: MCR MOU dl16: HLPDCL PIP dl1:[1,2]/cd/fo/nv=dl16:[1,2]*.hlp DMO dl16: ^Z 10. Perform Layered Products installation/update as in chapter 8 11. Add Fermi/DECUS Additions to master disk as in chapter 9 12. Tune the error logger library as in chapter 14 13. Perform VMR (*)@RSX_FACTORY$COMMANDS:privilege Set def dla1:[1,54] Spawn/cli=mcr @RSX_FACTORY$COMMANDS:rsxvmr AN RSX SYSTEM BUILD OUTLINE Page 7-6 7.2 Editing The VMR File 7.2.1 Before Sysgen Phase III The following modifications should be made to the file SYSVMR.CMD at the end of SYSGEN Phase II, before running VMR. 1. The maximum amount of pool (Dynamic Storage Region) available to the system far exceeds the needs of a typical experiment. Some of this can be traded for space for user tasks by making the following change: ;SET /POOL=* SET /POOL=1000 2. The full duplex terminal driver uses space remaining in its partition for a private buffer pool. The partition TTPAR is created with a default size of 8K words; this is larger than necessary. The guideline given in the sysgen manual is P = C + 20*T + 60*A where P is the size of TTPAR (decimal words), C is the code size of the driver (see task image size in [1,34]TTDRV.MAP), T is the number of terminals in the system, and A is the average number of terminal I/O requests pending at any given time. With all options selected, C = 5856. words; thus P = 7K words leaves more than adequate space for 12 terminals with an I/O request pending on each. The following sets the size of TTPAR to 7K words: SET /MAIN=TTPAR:*:340:TASK LOA TT: 3. Where devices are being loaded into DRVPAR, comment out any mutually exclusive device drivers, e.g., DX: and DY: both use the same CSR and vector, so at most one of them can be loaded. If certain devices are used infrequently, consider not loading them at all in VMR; load them at run time when needed. For example, SET /MAIN=DRVPAR:*:*:SYS LOA DL: ;LOA DK: ;LOA DX: ;LOA DY: LOA MM: AN RSX SYSTEM BUILD OUTLINE Page 7-7 LOA MT: LOA LP: LOA CO: SET /TOP=DRVPAR:-* 4. The BOO task is rather dangerous to leave installed in an open system where novice users may be tempted to experiment. Since its really only required for system management functions, there is no need for it to occupy pool space by being installed all the time. Therefore, the line installing it should be commented out: INS ACS ! INSTALL ALLOCATE CHECKPOINT FILE ;INS BOO ! INSTALL BOOT INS DMO ! INSTALL DISMOUNT 7.2.2 After Sysgen Phase III The following modifications should be made to the file SYSVMR.CMD at the end of SYSGEN Phase III, before running VMR on the new RSX master disk. Multi-user MCR provides a better time-sharing environment than MCR for program development by multiple users, at the expense of slightly higher system overhead. To use it, the tasks MCRMU and SYS must be installed in place of MCR, using VMR after Sysgen Phase III. Edit the SYSVMR.CMD file as follows: INS LOA ! INSTALL LOAD ;INS MCR ! INSTALL MCR INS MCRMU ! INSTALL MULTI-USER MCR PRIMARY INS SYS ! INSTALL MULTI-USER MCR SECONDARY INS MOU ! INSTALL MOUNT The file SYS becomes the task ...MCR, which runs in the GEN partition; the file MCRMU becomes the task MCR..., which runs in the SYSPAR partition. For multi-user MCR, SYSPAR can be smaller than for single-user MCR: SET /TOP=DRVPAR:-* ;SET /MAIN=SYSPAR:*:117:TASK AN RSX SYSTEM BUILD OUTLINE Page 7-8 SET /MAIN=SYSPAR:*:101:TASK SET /MAIN=FCPPAR:*:242:SYS SET /MAIN=GEN:*:*:SYS CHAPTER 8 AN RSX LAYERED PRODUCTS INSTALLATION AND UPDATE The following two sections describe the procedures used to install and update PDP-11 FORTRAN-77/RSX V5.0 and PDP-11 Symbolic Debugger/RSX V2.0. The procedures (especially the update procedure) will probably change from version to version. They are included here to show the general flow of the update or installation and to provide guidelines for establishing the next version's procedure. Read the documents included with each layered product update before performing the installation and update. 8.1 PDP-11 FORTRAN-77/RSX Installation And Update Load F77 source tape in drive (MFA0) Load update disk (created in chapter 7) in drive (DLA0) Load RSX master system disk in drive (DLA1) @RSX_FACTORY$COMMANDS:prelproduct ASN DL1:=DS: ASN MF0:=SR: @RSX_FACTORY$COMMANDS:instalf77 Rename ds:[1,54]f77.exe [1,1]f77.tsk ASN DL0:=UP: @RSX_FACTORY$COMMANDS:setupf77u @F77 Rename ds:[1,1]f77.exe [1,54]f77.tsk PIP ds:[1,1]/cd/fo/nv=ds:[11,36]f4pcvf.obj AN RSX LAYERED PRODUCTS INSTALLATION AND UPDATE Page 8-2 BYE (exit MCR) @RSX_FACTORY$COMMANDS:Cleanup_F77 8.2 PDP-11 Symbolic Debugger/RSX Installation Load Debug source tape in drive (MFA0) Load update disk (created in chapter 7) in drive (DLA0) Load RSX master system disk in drive (DLA1) @RSX_FACTORY$COMMANDS:prelproduct ASN DL1:=DS: ASN MF0:=SR: ASN DL0:=UP: @RSX_FACTORY$COMMANDS:setupdbgi Set /uic=[1,1] MOU dl17: RMSV20 Copy dl17:[1,1]rmslib.olb dl1:[1,1] DMO dl17: Set /uic=[1,61] Set def dl1:[247,247] Edit INSTAL.CMD and alter all lines beginning with 'DCL' as follows: DCL SET DEF 'TEMP' - Original Line SET DEF 'TEMP' - New Line @INSTAL Copy [247,247]PDPDBG.EXE [1,54]PDPDBG.TSK BYE (exit MCR) Set prot dla1:[0,0]247200.dir CHAPTER 9 AN RSX FERMI/DECUS ADDITIONS INSTALLATION The installation of the files in the Fermi Additions area and the DECUS Additions area are both done in the ADDITIONS command file. Note that spawning a sub-process to handle the copying insures restoring the correct environment upon returning to the present process. Load RSX master system disk in drive (DLA1) @RSX_FACTORY$COMMANDS:Privilege Spawn @RSX_FACTORY$COMMANDS:Additions @RSX_FACTORY$COMMANDS:Pretune ASN DL1:=LB: Set /uic=[1,6] LBR tune.cmd=errlogetc.ulb/ex:tune @Tune BYE (exit MCR) CHAPTER 10 SAMPLE UPDATE AND SYSGEN OUTPUT The following four sections are samples of terminal output generated by the RSX update and sysgen procedures. SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-2 10.1 RSX Update $ @rsx_factory$commands:setup_for_rsx_u_s u $ @rsx_factory$commands:preupdate > @update >; >; RSX-11M V4.2 UPDATE PROCEDURE 24-SEP-86 13:39:52 >; >; This command file initiates the Update Procedure for RSX-11M V4.2. >; It will determine what type of Update media is being used as well >; as what Update level is being applied. It will copy all of the files >; that are necessary to bring your system up to the current patch level. >; The destination of these files will be determined from what type of >; Update media you are using and what Update level you are applying. >; When this copying is complete and the Update has been applied, it may >; be necessary to perform a SYSGEN to incorporate the new software. >; >; >* Enter device and unit for update kit [ddn:] [S]: dl0: >; >* Enter device containing distribution kit [ddn:] [S]: dl10: >; >MOU DL0:/FOR %MOUNT-I-MOUNTED, M42UPDATEB mounted on _BISON$DLA1: >MOU DL10:/OVER=ID %MOUNT-F-DEVMOUNT, device is already mounted >BRU/NOINI/SUP/UFD DL0:[1,11]UP.REV DL10: BRU - Completed >DMO DL0:/NOUNLOAD >DEAL DL0: >MOU DL0:M42UPDATEB %MOUNT-I-MOUNTED, M42UPDATEB mounted on _BISON$DLA1: >; >; RSX-11M V4.2 BL38B Update B >; >; 24-SEP-86 13:40:15 >; >; This Update contains corrections for your RSX-11M V4.2 operating system >; software. This procedure applies these corrections to a copy of your >; distribution kit. >; >; This Update also contains corrections for the following layered products: >; >; DECnet-11M V4.2 >; DPM V4.1 >; FMS-11/RSX V1.0 >; KED V1.1 >; KMV11 V1.0 >; KMV11 X25 LINK LEVEL (KXI) V1.0 >; PASCAL V1.1 >; COBOL-81 V2.3 >; PDP-11 BASIC-PLUS-2 V2.3 SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-3 >; PDP-11 COBOL V4.4 >; PDP-11 SORT/MERGE V3.0 >; RSX-11 2780/3780 protocol emulator V4.1 >; PDP-11 FORTRAN IV V2.6 >; PDP-11 FORTRAN-77/RSX V5.0 >; PDP-11 FORTRAN-77 DEBUG V1.0 >; >; >; These layered product corrections are NOT automatically applied. For >; information on applying layered product corrections, see the Update >; Installation Guide. >; >SET /UIC=[200,200] >; >* 1. Have you made a copy of the distribution kit? [Y/N]: y >; >; The types of distribution kits are as follows: >; >; A -- Big disk (RP04, RP05, RP06, RM02, RM03, RM05, >; RM80, RP07, RA60, RA80, or RA81) >; B -- RK07 >; C -- RK06 >; D -- RL02 >; E -- RL01 >; >* What type of distribution kit do you have? (A, B, C, D, OR E) [S]: e >; >; >ASN DL0:=UP: >; >; >; Enter the names of the disk drives that will hold your >; distribution kit. (This includes the drive that you >; have already loaded your first disk (RSXM38) in.) >; >; For example: DL2:,DL3: >; >* Drive(s): dl17:,dl16:,dl15:,dl14:,dl13:,dl12:,dl11: >; >* Please load the RMSV20 disk from your distribution kit into DL17:, >; then press the RETURN key... >; >MOU DL17:RMSV20 %MOUNT-I-MOUNTED, RMSV20 mounted on _BISON$MDB7: >; >; >* Please load the HLPDCL disk from your distribution kit into DL16:, >; then press the RETURN key... >; >MOU DL16:HLPDCL SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-4 %MOUNT-I-MOUNTED, HLPDCL mounted on _BISON$MDB6: >; >; >* Please load the MCRSRC disk from your distribution kit into DL15:, >; then press the RETURN key... >; >MOU DL15:MCRSRC %MOUNT-I-MOUNTED, MCRSRC mounted on _BISON$MDB5: >; >; >* Please load the RLUTIL disk from your distribution kit into DL14:, >; then press the RETURN key... >; >MOU DL14:RLUTIL %MOUNT-I-MOUNTED, RLUTIL mounted on _BISON$MDB4: >; >; >* Please load the PRVBLD disk from your distribution kit into DL13:, >; then press the RETURN key... >; >MOU DL13:PRVBLD %MOUNT-I-MOUNTED, PRVBLD mounted on _BISON$MDB3: >; >; >* Please load the EXCPRV disk from your distribution kit into DL12:, >; then press the RETURN key... >; >MOU DL12:EXCPRV %MOUNT-I-MOUNTED, EXCPRV mounted on _BISON$MDB2: >; >; >* Please load the RSXM38 disk from your distribution kit into DL11:, >; then press the RETURN key... ^Y > atta BERG %DCL-S-RETURNED, control returned to process BERG $ dism mdb0: $ @RSX_factory$commands:mddisk mdb0 "" disa $ @RSX_factory$commands:mddisk mdb1 DRA1:[VIRTUAL]RSXM38.DSK asso $ atta BERG1 %MCR-S-RETURNED, control returned to process BERG1 > c >; >MOU DL11:RSXM38 %MOUNT-I-MOUNTED, RSXM38 mounted on _BISON$MDB1: >; 24-SEP-1986 13:44:33 >; >; >ASN DL17:=KT: >ASN DL17:=IN: SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-5 >ASN DL17:=OU: >ASN DL17:=WK: >ASN DL17:=WK0: >; >TIME >; >SET /UIC=[1,1] >; >LBR KT:RMSLIB/RP=UP:[53,60]RMSLIBRSX.INS Module "R0ACBB" replaced Module "R1GET " replaced Module "R1GBLD" replaced Module "R3IUDR" replaced Module "R0AUTN" replaced Module "R0EXSY" replaced Module "R0MAPC" replaced Module "R0PRFN" replaced Module "R0XPFN" replaced Module "R1RLBK" replaced >LBR KT:RMSLIB/RP/-EP=UP:[53,60]RMSLIBRSX.NEP Module "RMSEG1" replaced Module "RMSEG2" replaced Module "RMSEG3" replaced Module "RMSEG4" replaced Module "RMSEG5" replaced Module "RMSEG6" replaced Module "R3IUDL" replaced Module "R0AUTL" replaced Module "R0AUTO" replaced Module "R0AUTS" replaced Module "R0EXEC" replaced Module "R0MAPD" replaced Module "R0MAPL" replaced Module "R0MAPS" replaced >LBR KT:RMSLIB.OLB/CO=KT:RMSLIB.OLB >PIP KT:RMSLIB.OLB/TR >PIP KT:RMSLIB.OLB/PU >LBR KT:RMSDAP/RP=UP:[53,60]RMSDAPRSX.INS Module "R0PRFD" replaced Module "R0AUON" replaced >LBR KT:RMSDAP/RP/-EP=UP:[53,60]RMSDAPRSX.NEP Module "R0AULL" replaced Module "R0AULN" replaced Module "R0AULO" replaced Module "R0AULS" replaced Module "R0AUOL" replaced Module "R0AUOO" replaced Module "R0AUOS" replaced >LBR KT:RMSDAP.OLB/CO=KT:RMSDAP.OLB >PIP KT:RMSDAP.OLB/TR >PIP KT:RMSDAP.OLB/PU >PIP KT:RMSRESSUB.TSK/NV/CD=UP:[53,60]RMSRESSUB.TSK >PIP KT:RMSRESSUB.TSK/PU >PIP KT:RMSRES.TSK/NV/CD=UP:[53,60]RMSRES.TSK >PIP KT:RMSRES.TSK/PU SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-6 >; >SET /UIC=[1,24] >; >LBR KT:RMSUTL.OLB/RP/-EP=UP:[53,64]RMSUTLRSX.NEP Module "IFLPSO" replaced Module "IFLERR" replaced Module "IFLMAI" replaced Module "IFLPAR" replaced Module "IFLASO" replaced Module "IFLIDX" replaced Module "IFLPRI" replaced Module "IFLALT" replaced Module "RESATR" replaced Module "RESCLN" replaced Module "RESCTL" replaced Module "RESDAT" replaced Module "RESDTA" replaced Module "RESMAI" replaced Module "RESSEL" replaced Module "RESUTE" replaced Module "RESCVN" replaced Module "RESHCR" replaced Module "CNVABO" replaced Module "CNVEOF" replaced Module "CNVEXC" replaced Module "CNVRMS" replaced Module "CNVER3" replaced >LBR KT:RMSUTL.OLB/CO=KT:RMSUTL.OLB >PIP KT:RMSUTL.OLB/TR >PIP KT:RMSUTL.OLB/PU >PIP KT:IFLNON.ODL/NV/CD=UP:[53,60]IFLNON.ODL >PIP KT:IFLNON.ODL/PU >PIP KT:IFLNRN.ODL/NV/CD=UP:[53,60]IFLNRN.ODL >PIP KT:IFLNRN.ODL/PU >PIP KT:CNVNON.CMD/NV/CD=UP:[53,60]CNVNON.CMD >PIP KT:CNVNON.CMD/PU >PIP KT:CNVNRN.CMD/NV/CD=UP:[53,60]CNVNRN.CMD >PIP KT:CNVNRN.CMD/PU >; >SET /UIC=[1,34] >; >PIP KT:RMSRESSUB.MAP/NV/CD=UP:[53,60]RMSRESSUB.MAP >PIP KT:RMSRESSUB.MAP/PU >PIP KT:RMSRES.MAP/NV/CD=UP:[53,60]RMSRES.MAP >PIP KT:RMSRES.MAP/PU >; >SET /UIC=[1,54] >; >PIP KT:RMSIFL.TSK/NV/CD=UP:[53,60]RMSIFL.TSK >PIP KT:RMSIFL.TSK/PU >PIP KT:RMSCNV.TSK/NV/CD=UP:[53,60]RMSCNV.TSK >PIP KT:RMSCNV.TSK/PU >PIP KT:RMSRST.TSK/NV/CD=UP:[53,60]RMSRST.TSK >PIP KT:RMSRST.TSK/PU 24-SEP-1986 13:49:39 SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-7 >; %MCR-I-SUPERSEDE, previous value of KT has been superseded >ASN DL16:=IN: %MCR-I-SUPERSEDE, previous value of IN has been superseded >; >TIME >; >ASN DL16:=KT: >ASN DL16:=OU: %MCR-I-SUPERSEDE, previous value of OU has been superseded >ASN DL16:=WK: %MCR-I-SUPERSEDE, previous value of WK has been superseded >ASN DL16:=WK0: %MCR-I-SUPERSEDE, previous value of WK0 has been superseded >; 24-SEP-1986 13:49:41 >; >TIME >; >SET /UIC=[1,6] >; >LBR KT:ERRLOG.ULB/RP=UP:[104,60]DEVSM1 Module "DEVSM1" replaced >LBR KT:ERRLOG.ULB/RP=UP:[104,60]DEVUDA Module "DEVUDA" replaced >LBR KT:ERRLOG.ULB/IN=UP:[104,60]TMSCPE >LBR KT:ERRLOG.ULB/RP=UP:[104,60]MSCP60 Module "MSCP60" replaced >LBR KT:ERRLOG.ULB/RP=UP:[104,60]ETK50 Module "ETK50 " replaced >LBR KT:ERRLOG.ULB/RP=UP:[104,60]DSP3M1 Module "DSP3M1" replaced >LBR KT:ERRLOG.ULB/CO=KT:ERRLOG.ULB >PIP KT:ERRLOG.ULB/TR >PIP KT:ERRLOG.ULB/PU >; >SET /UIC=[23,10] >; >SLP @UP:[23,60]LIBRARY.COR >PIP KT:LIBRARY.MAC/PU >SLP @UP:[23,60]LINK.COR >PIP KT:LINK.MAC/PU >SLP @UP:[23,60]RUN.COR >PIP KT:RUN.MAC/PU >SLP @UP:[23,60]SUBMIT.COR >PIP KT:SUBMIT.MAC/PU >SLP @UP:[23,60]SET1.COR >PIP KT:SET1.MAC/PU >SLP @UP:[23,60]SHOW.COR >PIP KT:SHOW.MAC/PU >SLP @UP:[23,60]TSHOW.COR >PIP KT:TSHOW.MAC/PU >SLP @UP:[23,60]TSET.COR >PIP KT:TSET.MAC/PU 24-SEP-1986 13:53:16 SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-8 >; >; >TIME >; >ASN DL15:=KT: %MCR-I-SUPERSEDE, previous value of KT has been superseded >ASN DL15:=IN: %MCR-I-SUPERSEDE, previous value of IN has been superseded >ASN DL15:=OU: %MCR-I-SUPERSEDE, previous value of OU has been superseded >ASN DL15:=WK: %MCR-I-SUPERSEDE, previous value of WK has been superseded >ASN DL15:=WK0: %MCR-I-SUPERSEDE, previous value of WK0 has been superseded >; 24-SEP-1986 13:53:18 >; >TIME >; >SET /UIC=[12,10] >; >SLP @UP:[12,60]CLIOV.COR >PIP KT:CLIOV.MAC/PU >SLP @UP:[12,60]ALTOV.COR >PIP KT:ALTOV.MAC/PU >SLP @UP:[12,60]FIXOV.COR >PIP KT:FIXOV.MAC/PU >SLP @UP:[12,60]MCRDEF.COR >PIP KT:MCRDEF.MAC/PU >SLP @UP:[12,60]SAVSIZ.COR >PIP KT:SAVSIZ.MAC/PU >SLP @UP:[12,60]ICPPRE.COR >PIP KT:ICPPRE.MAC/PU >SLP @UP:[12,60]MOUSUB.COR >PIP KT:MOUSUB.MAC/PU >SLP @UP:[12,60]ICPATS.COR >PIP KT:ICPATS.MAC/PU >SLP @UP:[12,60]ICPERR.COR >PIP KT:ICPERR.MAC/PU >SLP @UP:[12,60]ICPFDC.COR >PIP KT:ICPFDC.MAC/PU >SLP @UP:[12,60]ICPGOT.COR >PIP KT:ICPGOT.MAC/PU >SLP @UP:[12,60]ICPIMP.COR >PIP KT:ICPIMP.MAC/PU >SLP @UP:[12,60]ICPPDW.COR >PIP KT:ICPPDW.MAC/PU >SLP @UP:[12,60]ICPSUB.COR >PIP KT:ICPSUB.MAC/PU >SLP @UP:[12,60]ICPSY1.COR >PIP KT:ICPSY1.MAC/PU >SLP @UP:[12,60]ICPAS2.COR >PIP KT:ICPAS2.MAC/PU >LBR KT:INDSYS.CLB/RP=UP:[77,60]INDVFY.CMD Module "INDVFY" replaced SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-9 >LBR KT:INDSYS.CLB/CO=KT:INDSYS.CLB >PIP KT:INDSYS.CLB/TR >PIP KT:INDSYS.CLB/PU >; >SET /UIC=[15,10] >; >SLP @UP:[15,60]HSTTAB.COR >PIP KT:HSTTAB.MAC/PU 24-SEP-1986 13:56:54 >; %MCR-I-SUPERSEDE, previous value of KT has been superseded >ASN DL14:=IN: %MCR-I-SUPERSEDE, previous value of IN has been superseded >ASN DL14:=OU: >; >TIME >; >ASN DL14:=KT: %MCR-I-SUPERSEDE, previous value of OU has been superseded >ASN DL14:=WK: %MCR-I-SUPERSEDE, previous value of WK has been superseded >ASN DL14:=WK0: %MCR-I-SUPERSEDE, previous value of WK0 has been superseded >; 24-SEP-1986 13:56:55 >; >TIME >; >SET /UIC=[1,20] >; >SLP @UP:[1,60]PIPBLD.COR >PIP KT:PIPBLD.BLD/PU >SLP @UP:[1,60]TKBBLD.COR >PIP KT:TKBBLD.BLD/PU >SLP @UP:[1,60]STKBLD.COR >PIP KT:STKBLD.BLD/PU >SLP @UP:[1,60]BRUBLD.COR >PIP KT:BRUBLD.BLD/PU >SLP @UP:[1,60]VMRBLD.COR >PIP KT:VMRBLD.BLD/PU >LBR KT:TKB.OLB/-EP/RP=UP:[31,64]MLSG2.OBJ Module "MLSG2 " replaced >LBR KT:TKB.OLB/-EP/RP=UP:[31,64]P2OPT.OBJ Module "P2OPT " replaced >LBR KT:TKB.OLB/-EP/RP=UP:[31,64]HEADR.OBJ Module "HEADR " replaced >LBR KT:TKB.OLB/CO=KT:TKB.OLB >PIP KT:TKB.OLB/TR >PIP KT:TKB.OLB/PU >LBR KT:PIP.OLB/RP=UP:[32,60]PIPDEL Module "PIPDEL" replaced >LBR KT:PIP.OLB/CO=KT:PIP.OLB >PIP KT:PIP.OLB/TR >PIP KT:PIP.OLB/PU >LBR KT:VMR.OLB/RP=UP:[70,60]SETUP SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-10 Module "SETUP " replaced >LBR KT:VMR.OLB/RP=UP:[70,60]SPROV Module "SPROV " replaced >LBR KT:VMR.OLB/RP=UP:[70,60]SADUM Module "SADUM " replaced >LBR KT:VMR.OLB/RP=UP:[70,60]SADUU Module "SADUU " replaced >LBR KT:BRU.OLB/RP=UP:[74,60]BACKLB Module "BACKLB" replaced >LBR KT:BRU.OLB/RP=UP:[74,60]BACKTP Module "BACKTP" replaced >LBR KT:BRU.OLB/RP=UP:[74,60]BEGIN Module "BEGIN " replaced >LBR KT:BRU.OLB/RP=UP:[74,60]BRUBAD Module "BRUBAD" replaced >LBR KT:BRU.OLB/RP=UP:[74,60]BRUDAT Module "BRUDAT" replaced >LBR KT:BRU.OLB/RP=UP:[74,60]BRUFILE Module "BRUFIL" replaced >LBR KT:BRU.OLB/RP=UP:[74,60]BRUHEAD Module "BRUHEA" replaced >LBR KT:BRU.OLB/RP=UP:[74,60]BRUPAR Module "BRUPAR" replaced >LBR KT:BRU.OLB/RP=UP:[74,60]BRURP Module "BRURP " replaced >LBR KT:BRU.OLB/RP=UP:[74,60]COMLIB Module "COMLIB" replaced >LBR KT:BRU.OLB/RP=UP:[74,60]DBLBUF Module "DBLBUF" replaced >LBR KT:BRU.OLB/RP=UP:[74,60]DKRDWT Module "DKRDWT" replaced >LBR KT:BRU.OLB/RP=UP:[74,60]DSKINI Module "DSKINI" replaced >LBR KT:BRU.OLB/RP=UP:[74,60]DSKIO Module "DSKIO " replaced >LBR KT:BRU.OLB/RP=UP:[74,60]ERROR Module "ERROR " replaced >LBR KT:BRU.OLB/RP=UP:[74,60]SCNDIR Module "SCNDIR" replaced >LBR KT:BRU.OLB/RP=UP:[74,60]TAPEIO Module "TAPEIO" replaced >LBR KT:BRU.OLB/CO=KT:BRU.OLB >PIP KT:BRU.OLB/TR >PIP KT:BRU.OLB/PU >LBR KT:BAD.OLB/RP=UP:[62,64]BADIO Module "BADIO " replaced >LBR KT:BAD.OLB/CO=KT:BAD.OLB >PIP KT:BAD.OLB/TR >PIP KT:BAD.OLB/PU >; >SET /UIC=[1,24] >; >LBR KT:ACF.OLB/RP=UP:[145,64]ACFROT Module "ACFROT" replaced >LBR KT:ACF.OLB/RP=UP:[145,64]ACFOUT SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-11 Module "ACFOUT" replaced >LBR KT:ACF.OLB/CO=KT:ACF.OLB >PIP KT:ACF.OLB/TR >PIP KT:ACF.OLB/PU >; >SET /UIC=[1,51] >; >PIP KT:BRU64K.SYS/NV/CD=UP:[1,51]BRU64K.SYS >PIP KT:BRU64K.SYS/PU >PIP KT:BRU64K.STB/NV/CD=UP:[1,51]BRU64K.STB >PIP KT:BRU64K.STB/PU >PIP KT:BRUSYS.SYS/NV/CD=UP:[1,51]BRUSYS.SYS >PIP KT:BRUSYS.SYS/PU >PIP KT:BRUSYS.STB/NV/CD=UP:[1,51]BRUSYS.STB >PIP KT:BRUSYS.STB/PU 24-SEP-1986 14:03:28 >; %MCR-I-SUPERSEDE, previous value of KT has been superseded >ASN DL13:=IN: %MCR-I-SUPERSEDE, previous value of IN has been superseded >ASN DL13:=OU: >; >TIME >; >ASN DL13:=KT: %MCR-I-SUPERSEDE, previous value of OU has been superseded >ASN DL13:=WK: %MCR-I-SUPERSEDE, previous value of WK has been superseded >ASN DL13:=WK0: %MCR-I-SUPERSEDE, previous value of WK0 has been superseded >; 24-SEP-1986 14:03:29 >; >TIME >; >SET /UIC=[1,20] >; >SLP @UP:[1,60]MOUBLD.COR >PIP KT:MOUBLD.BLD/PU >SLP @UP:[1,60]DCLBLD.COR >PIP KT:DCLBLD.BLD/PU >SLP @UP:[1,60]RCTBLD.COR >PIP KT:RCTBLD.BLD/PU >SLP @UP:[1,60]QCLBLD.COR >PIP KT:QCLBLD.BLD/PU >SLP @UP:[1,60]HELBLD.COR >PIP KT:HELBLD.BLD/PU >SLP @UP:[1,60]ICPBLD.COR >PIP KT:ICPBLD.BLD/PU >SLP @UP:[1,60]ICPCOMBLD.COR >PIP KT:ICPCOMBLD.BLD/PU >LBR KT:MCR.OLB/RP=UP:[12,60]ALTOV Module "ALTOV " replaced >LBR KT:MCR.OLB/RP=UP:[12,60]CLIOV Module "CLIOV " replaced SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-12 >LBR KT:MCR.OLB/RP=UP:[12,60]FIXOV Module "FIXOV " replaced >LBR KT:MCR.OLB/RP=UP:[12,60]MCRDEF Module "MCRDEF" replaced >LBR KT:MCR.OLB/CO=KT:MCR.OLB >PIP KT:MCR.OLB/TR >PIP KT:MCR.OLB/PU >LBR KT:SAV.OLB/RP=UP:[12,60]SAVSIZ Module "SAVSIZ" replaced >LBR KT:SAV.OLB/CO=KT:SAV.OLB >PIP KT:SAV.OLB/TR >PIP KT:SAV.OLB/PU >LBR KT:MLTUSR.OLB/RP=UP:[15,60]HSTTAB Module "HSTTAB" replaced >LBR KT:MLTUSR.OLB/CO=KT:MLTUSR.OLB >PIP KT:MLTUSR.OLB/TR >PIP KT:MLTUSR.OLB/PU >LBR KT:DCLO.OLB/RP=UP:[23,64]LIBRARY.OVR Module "LIBRAR" replaced >LBR KT:DCLO.OLB/RP=UP:[23,64]LINK.OVR Module "LINK " replaced >LBR KT:DCLO.OLB/RP=UP:[23,64]RUN.OVR Module "RUN " replaced >LBR KT:DCLO.OLB/RP=UP:[23,64]SUBMIT.OVR Module "SUBMIT" replaced >LBR KT:DCLO.OLB/RP=UP:[23,64]SET1.OVR Module "SET1 " replaced >LBR KT:DCLO.OLB/RP=UP:[23,64]SHOW.OVR Module "SHOW " replaced >LBR KT:DCLO.OLB/RP=UP:[23,64]TSHOW.OVR Module "TSHOW " replaced >LBR KT:DCLO.OLB/RP=UP:[23,64]TSET.OVR Module "TSET " replaced >LBR KT:DCLO.OLB/CO=KT:DCLO.OLB >PIP KT:DCLO.OLB/TR >PIP KT:DCLO.OLB/PU >LBR KT:FIL.OLB/RP/-EP=UP:[12,60]MOUSUB Module "MOUSUB" replaced >LBR KT:FIL.OLB/CO=KT:FIL.OLB >PIP KT:FIL.OLB/TR >PIP KT:FIL.OLB/PU >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,60]ICPATS Module "INDATS" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,60]ICPERR Module "INDERR" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,60]ICPFDC Module "INDFDC" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,60]ICPGOT Module "INDGOT" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,60]ICPIMP Module "INDIMP" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,60]ICPPDW Module "INDPDW" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,64]ICPSUB Module "INDSUB" replaced SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-13 >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,60]ICPSY1 Module "INDSY1" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,60]ICPAS2 Module "INDAS2" replaced >LBR KT:ICP11M.OLB/CO=KT:ICP11M.OLB >PIP KT:ICP11M.OLB/TR >PIP KT:ICP11M.OLB/PU >; >SET /UIC=[1,24] >; >LBR KT:MCR.OLB/RP=UP:[12,64]ALTOV Module "ALTOV " replaced >LBR KT:MCR.OLB/RP=UP:[12,64]CLIOV Module "CLIOV " replaced >LBR KT:MCR.OLB/RP=UP:[12,64]FIXOV Module "FIXOV " replaced >LBR KT:MCR.OLB/RP=UP:[12,64]MCRDEF Module "MCRDEF" replaced >LBR KT:MCR.OLB/CO=KT:MCR.OLB >PIP KT:MCR.OLB/TR >PIP KT:MCR.OLB/PU >LBR KT:SAV.OLB/RP=UP:[12,64]SAVSIZ Module "SAVSIZ" replaced >LBR KT:SAV.OLB/CO=KT:SAV.OLB >PIP KT:SAV.OLB/TR >PIP KT:SAV.OLB/PU >LBR KT:FIL.OLB/RP/-EP=UP:[12,64]MOUSUB Module "MOUSUB" replaced >LBR KT:FIL.OLB/CO=KT:FIL.OLB >PIP KT:FIL.OLB/TR >PIP KT:FIL.OLB/PU >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,64]ICPATS Module "INDATS" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,64]ICPERR Module "INDERR" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,64]ICPFDC Module "INDFDC" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,64]ICPGOT Module "INDGOT" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,64]ICPIMP Module "INDIMP" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,64]ICPPDW Module "INDPDW" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,64]ICPSUB Module "INDSUB" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,64]ICPSY1 Module "INDSY1" replaced >LBR KT:ICP11M.OLB/RP/-EP=UP:[12,64]ICPAS2 Module "INDAS2" replaced >LBR KT:ICP11M.OLB/CO=KT:ICP11M.OLB >PIP KT:ICP11M.OLB/TR >PIP KT:ICP11M.OLB/PU >LBR KT:MLTUSR.OLB/RP=UP:[15,64]HSTTAB Module "HSTTAB" replaced >LBR KT:MLTUSR.OLB/CO=KT:MLTUSR.OLB SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-14 >PIP KT:MLTUSR.OLB/TR >PIP KT:MLTUSR.OLB/PU >LBR KT:QMGCLI.OLB/RP=UP:[25,64]PRIWRN.CLI Module "PRIWRN" replaced >LBR KT:QMGCLI.OLB/CO=KT:QMGCLI.OLB >PIP KT:QMGCLI.OLB/TR >PIP KT:QMGCLI.OLB/PU >LBR KT:RCT/RP=UP:[75,64]RCTDAT Module "RCTDAT" replaced >LBR KT:RCT/RP=UP:[75,64]RCTSUB Module "RCTSUB" replaced >LBR KT:RCT/RP=UP:[75,64]RCTROT Module "RCTROT" replaced >LBR KT:RCT.OLB/CO=KT:RCT.OLB >PIP KT:RCT.OLB/TR >PIP KT:RCT.OLB/PU 24-SEP-1986 14:12:52 >; >TIME >; %MCR-I-SUPERSEDE, previous value of KT has been superseded >; >ASN DL12:=KT: >ASN DL12:=IN: %MCR-I-SUPERSEDE, previous value of IN has been superseded >ASN DL12:=OU: %MCR-I-SUPERSEDE, previous value of OU has been superseded >ASN DL12:=WK: %MCR-I-SUPERSEDE, previous value of WK has been superseded >ASN DL12:=WK0: %MCR-I-SUPERSEDE, previous value of WK0 has been superseded >; 24-SEP-1986 14:12:53 >; >TIME >; >SET /UIC=[2,200] >; >PIP KT:[11,10]PUCOM.MAC;1/DE >; >SET /UIC=[11,10] >; >PIP KT:PUCOM.MAC/NV/CD=UP:[11,60]PUCOM.MAC;1 >SLP @UP:[11,60]XEDRV.COR >PIP KT:XEDRV.MAC/PU >SLP @UP:[11,60]DRRAS.COR >PIP KT:DRRAS.MAC/PU >SLP @UP:[11,60]QUEUE.COR >PIP KT:QUEUE.MAC/PU >SLP @UP:[11,60]DRCIN.COR >PIP KT:DRCIN.MAC/PU >SLP @UP:[11,60]DRGCL.COR >PIP KT:DRGCL.MAC/PU >SLP @UP:[11,60]DRATP.COR >PIP KT:DRATP.MAC/PU SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-15 >SLP @UP:[11,60]DLDRV.COR >PIP KT:DLDRV.MAC/PU >SLP @UP:[11,60]DRCLI.COR >PIP KT:DRCLI.MAC/PU >SLP @UP:[11,60]REQSB.COR >PIP KT:REQSB.MAC/PU >SLP @UP:[11,60]DRSPW.COR >PIP KT:DRSPW.MAC/PU >SLP @UP:[11,60]MSCPDRV.COR >PIP KT:MSCPDRV.MAC/PU >SLP @UP:[11,60]DSAPRE.COR >PIP KT:DSAPRE.MAC/PU >; >SET /UIC=[200,200] >; >SLP @UP:[200,60]SGNPER.COR >SET /UIC=[7,67] >PIP KT:[200,200]SGNPER.CMD;1/PR/WO:RD >SET /UIC=[200,200] >PIP KT:SGNPER.CMD/PU >SLP @UP:[200,60]SGNEXEC.COR >PIP KT:SGNEXEC.CMD/PU >SLP @UP:[200,60]SGNTT.COR >PIP KT:SGNTT.CMD/PU 24-SEP-1986 14:17:23 >; %MCR-I-SUPERSEDE, previous value of KT has been superseded >ASN DL11:=IN: %MCR-I-SUPERSEDE, previous value of IN has been superseded >ASN DL11:=OU: >; >TIME >; >ASN DL11:=KT: %MCR-I-SUPERSEDE, previous value of OU has been superseded >ASN DL11:=WK: %MCR-I-SUPERSEDE, previous value of WK has been superseded >ASN DL11:=WK0: %MCR-I-SUPERSEDE, previous value of WK0 has been superseded >; 24-SEP-1986 14:17:24 >; >TIME >; >SET /UIC=[1,1] >; >PIP KT:ODT.OBJ/NV/CD=UP:[47,60]ODT.OBJ >; >SET /UIC=[1,54] >; >PIP KT:MFT.TSK/NV/CD=UP:[1,54]MFT.TSK >PIP KT:MFT.TSK/PU >; >SET /UIC=[11,10] >; SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-16 >SLP @UP:[11,60]TTATT.COR >PIP KT:TTATT.MAC/PU >SLP @UP:[11,60]TTCAN.COR >PIP KT:TTCAN.MAC/PU >SLP @UP:[11,60]TTICH.COR >PIP KT:TTICH.MAC/PU >SLP @UP:[11,60]TTRW.COR >PIP KT:TTRW.MAC/PU >SLP @UP:[11,60]TTSUB.COR >PIP KT:TTSUB.MAC/PU >SLP @UP:[11,60]TTMOD.COR >PIP KT:TTMOD.MAC/PU >SLP @UP:[11,60]TTYH.COR >PIP KT:TTYH.MAC/PU >SLP @UP:[11,60]TTYHV.COR >PIP KT:TTYHV.MAC/PU >SLP @UP:[11,60]TTDAT.COR >PIP KT:TTDAT.MAC/PU >SLP @UP:[11,60]TTMAC.COR >PIP KT:TTMAC.MAC/PU >; >SET /UIC=[200,200] >; >SLP @UP:[200,60]SYSGEN.COR >SET /UIC=[7,47] >PIP KT:[200,200]SYSGEN.CMD;1/PR/WO:RD >SET /UIC=[200,200] >PIP KT:SYSGEN.CMD/PU 24-SEP-1986 14:21:00 >; >TIME >; >; >; >; RSX-11M V4.2 BL38B Update B completed. >; >; 24-SEP-86 14:21:01 >; >; >* 7. Do you want to start the SYSGEN now? [Y/N]: n >; >SET /UIC=[101,105] >; >@ > bye SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-17 10.2 RSX Prepgen $ @fermi$mgr_util:suspend_argus Suspending ARGUS process $ set /term=nobroadcast $ def rsx_factory$commands dua0:[rsx11msys.rsx_factory.rsx_factory.com] $ set def rsx_factory$commands $ @setup_for_rsx_u_s s $ @presysgen %MOUNT-I-MOUNTED, RSXM38 mounted on _BISON$MDB1: %DCL-S-SPAWNED, process BERG_1 spawned %DCL-S-ATTACHED, terminal now attached to process BERG_1 > set /uic=[200,200] > @sysgen >; >; RSX-11M V4.2 BL38C System Generation PHASE I -- Version 3.05 >; >; 10-DEC-86 09:34:38 >; RL01/RL02 distribution kit >; >* 3. Do you want to inhibit execution of MCR commands (PREPGEN)? [Y/N]: Y >* 3A. Do you want to create the assembly and build files on the SY: device? [Y/N D:Y]: N >* 5. Are you generating an unmapped system? [Y/N]: N >* 6. Use an input saved answer file? [Y/N]: N >* 8. Do you want a Standard Function System? [Y/N]: N >* 9. Name of output saved answer file [D: SYSSAVED.CMD] [S]: >; >; Phase I output saved answers created in file LB0:[200,200]SYSSAVED.CMD;1 >; >* 15. Chain to Phase II after Phase I completes? [Y/N]: Y >* 16. Enter device for EXCPRV disk when it is ready (ddu:) [D: DL1:] [S]: DL12: >MOU DL12:EXCPRV %MOUNT-I-MOUNTED, EXCPRV mounted on _BISON$MDB2: >* 17. Enter device for PRVBLD disk when it is ready (ddu:) [D: DL2:] [S]: DL13: >MOU DL13:PRVBLD %MOUNT-I-MOUNTED, PRVBLD mounted on _BISON$MDB3: >; >; Target configuration >; >* 1. Processor Type [D: 11/34] [S]: 11/50 >* 2. Does processor have a switch register? [Y/N D:N]: Y >* 3. Memory size (in K-word blocks) [D R:16.-124. D:16.]: 124. >* 4. Include support for K-series devices? [Y/N D:N]: SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-18 N >* 6. Floating point processor (FP-11) present? [Y/N D:N]: Y >* 8. Extended instruction set (EIS) present? [Y/N D:N]: Y >* 9. If using KW11-P as system clock: number of intrps./sec. [D R:0.-1000. D:0.]: 0 >* 10. Line frequency: A- 60 Hz B- 50 Hz [D: A] [S]: A >* 11. KW11-Y Watchdog timer support? [Y/N D:N]: N >* 12. Memory parity support? [Y/N D:N]: N >; >; The response to the following question specifies the highest interrupt >; vector. If you respond with a value less than or equal to 400, SYSGEN >; will assign the value associated with the highest interrupt vector >; specified during the Peripheral Section. Therefore, if your system >; will include devices that are not specified during the Peripheral >; Section and which have vectors above 400 (devices such as K-series and >; certain communication devices), specify that value in the next question. >; >* 14. Highest interrupt vector [O R:0-774 D:0]: 774 >; For device configuration: "*" Prints device table, "." Terminates inquiry >; "?" Prints current configuration >; Enter devices and number of controllers for devices which require drivers >* 15. Devices [S]: NL,CO,LP,DL,DK,DX,DY,MM,MT,YL=4,YZ. >; >; Processor:11/50 Memory Size:124K,Mapped System:RSX-11M >; >; Host configuration >; >* 1. Is a line printer available? [Y/N]: Y >* 3. Does the listing/map device have at least 120 columns? [Y/N]: Y >* 4. Assembly listings device (ddu:) [D: "NL:"] [S]: >* 5. Map device for Executive and device drivers (ddu:) [D: DL13:] [S]: >; >* EOS * Do you want to: -continue R-repeat section E-exit P-pause [S]: >; >; Executive Options >; >; Answer Y(ES) if the following support is desired >; >* 1. Include support for DBMS-11? [Y/N]: N >* 2. FILES-11 ACP ? [Y/N]: Y >* 3. Bucket locking (file sharing) and placement control? [Y/N]: Y >* 4. Non-resident tasks (task loader)? [Y/N]: Y SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-19 >* 5. Loadable task loader? [Y/N]: Y >* 6. Executive Common? [Y/N]: Y >* 7. Memory management (PLAS) directives? [Y/N]: Y >* 8. Send/Receive by reference directives? [Y/N]: Y >* 9. Get mapping context directive? [Y/N]: Y >; Address checking support will be included >; I/O rundown support will be included >* 12. Multi-user protection? [Y/N]: N >* 13. ANSI Magtape ACP? [Y/N]: Y >* 14. Do you want on-line formatting (FMT) or diagnostic QIOs? [Y/N]: Y >* 15. Loadable device drivers? [Y/N]: Y >* 16. Should the default for all applicable drivers be loadable? [Y/N]: Y >; AST support will be included >* 18. Include support for Cancel Selective Marktime? [Y/N]: Y >* 19. Task termination and device not ready messages (TKTN)? [Y/N]: Y >* 20. Power fail recovery? [Y/N]: Y >* 21. Install, request, and remove on exit? [Y/N]: Y >* 22. Large (20K) Executive? [Y/N]: Y >* 23. Logical device assignment? [Y/N]: Y >* 24. Include support for error logging? [Y/N]: Y >* 25. Do you intend to include a user-written driver? [Y/N]: Y >* 26. Include routine $GTWRD? [Y/N]: Y >* 27. Include routine $PTWRD? [Y/N]: Y >* 28. Disk writecheck? [Y/N]: Y >* 29. Software write-lock? [Y/N]: Y >* 30. Executive Debugging Tool (XDT)? [Y/N]: Y >* 31. Rotating pattern in data lights? [Y/N]: Y >* 32. Include support for communications products (such as DECnet)? [Y/N]: Y >; >; If you will be generating DECnet into this system, be sure you have SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-20 >; read the section on SYSGEN requirements in the "RSX DECnet Network >; Generation and Installation Guide." >; Several DECnet features (eg. remote terminal support, 11S task >; loading/upline dumping, etc.) require special consideration during >; SYSGEN. >; >* 32A. Include Network Command Terminal support? [Y/N]: Y >* 33. System controlled partitions? [Y/N]: Y >* 34. Include support for the Shuffler? [Y/N]: Y >* 35. Queue manager and queued print spooler? [Y/N]: N >* 36. Group global event flags? [Y/N]: Y >; >; For directives: >; >; * - Prints the table >; . - Terminates inquiry >; % - Gets all valid directives and terminates inquiry >; >* 37. Enter code for system directives [S]: % >; Checkpointing support will be included >* 38. Number of pre-allocated QIO packets [D R:0.-15. D:5.]: 15. >* 39. Size of data transfer vector in words [D R:0.-33. D:33.]: 33. >* 40. Round-robin scheduling interval in ticks [D R:0.-1000. D:5.]: >* 41. Highest priority class for consideration [D R:1.-249. D:150.]: >* 42. Lowest priority class for consideration [D R:1.-150. D:1.]: >* 43. Executive level disk swapping interval [D R:0.-5000. D:30.]: >* 44. Swapping priority [D R:1.-20. D:5.]: >* 46. Seconds between printer not ready messages [D R:0.-255. D:30.]: 120. >* 48. System crash register and stack dump device CSR [O R:0-177700 D:177564]: >* 50. Checkpointing with system checkpoint file? [Y/N]: Y >* 51. Crash dump analysis: A- PANIC B- Crash Dump Analysis (CDA) C- None [D: B] [S]: B >* 52. CDA output notification device CSR [O R:160000-177700 D:177564]: >* 53. Enter CDA memory dump device mnemonic (ddu:) [S R:3-4]: DL3: >* 54. Enter CDA memory dump device CSR [O R:160000-177700 D:174400]: >* 56. RT-11 emulation support? [Y/N]: N >; >* EOS * Do you want to: -continue R-repeat section E-exit P-pause [S]: >; >; >; Terminal driver options >; The Full Duplex Terminal Driver will be included. >* 2. Unsolicited input timeout value in seconds [D R:0.-255. D:120.]: SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-21 >; >; Answer Y(ES) if the following support is desired >; >* 6. Unsolicited input character AST? [Y/N]: Y >* 8. Breakthrough write? [Y/N]: Y >; CTRL/R support will be included >* 10. Escape sequence handling? [Y/N]: Y >* 11. Get multiple characteristics? [Y/N]: Y >* 12. Set multiple characteristics? [Y/N]: Y >* 13. Get terminal driver options? [Y/N]: Y >* 17. Read after prompt? [Y/N]: Y >* 20. CRT rubout support? [Y/N]: Y >* 25. Hardware unrecoverable input error notification? [Y/N]: Y >* 26. Device independent cursor positioning? [Y/N]: Y >; >* EOS * Do you want to: -continue R-repeat section E-exit P-pause [S]: >; >; >; System Options >; >; >; Answer Y(ES) if the following support is desired >; >* 2A. Include support for the IP11 Industrial I/O Subsystem? [Y/N]: N >* 3. Build the PLAS resident FCS? [Y/N]: N >* 4. Code for FCP (A/B/C/D/E, * prints table) [D: C] [S]: * >; >; The five FCP codes are: >; >; A - MINIMUM: Minimum functionality (2KW) >; B - SMALL: Full functionality, heavily overlayed (2.5KW) >; C - MIDDLE: Full functionality, moderately overlayed (5KW) >; D - LARGE: Full functionality, non-overlayed (9KW) >; E - OTHER: User supplied FCP >; >* 4. Code for FCP (A/B/C/D/E, * prints table) [D: C] [S]: C >* 5. Build Post Mortem Dump (PMD)? [Y/N]: Y >* 6. Build the Resource Monitoring Display task (RMD)? [Y/N]: Y >* 7. Build the non-queue manager print spooler (PRT)? [Y/N]: SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-22 Y >* 10. Do you want pool monitoring and low pool recovery (PMT)? [Y/N]: Y >* 11. What name would you like to give your system [D: RSX11M] [S R:0-6]: >* 12. Do you want SPM-11 support? [Y/N]: N >; >* EOS * Do you want to: -continue R-repeat section E-exit P-pause [S]: >; >; Thinking ... >; End of Executive option generation at 09:47:53 on 10-DEC-86 >; >; Peripheral configuration >; >; Parameters appearing in square brackets "[...]" can only be >; specified for the first controller of a particular device. >; Parameters appearing in parentheses "(...)" only need be specified >; if the indicated option is present on the target system. >; >; The default for loadable drivers has been set to *TRUE*. >; To override this setting enter R (resident) as the first parameter >; for the first controller of the specified device. >; >; A/D and Laboratory devices: None specified >; >; Interprocessor communication devices: None specified >; >; Unit record devices: LP >; >; Enter [L/R,] vector, CSR, printer option >; (,[KMC timeout count <0=no KMC>, KMC vector, KMC CSR]) for: >; >* 16. LP controller 0 [D: 200,177514,LA180,0,300,160130] [S]: ,,LP11-W >; >; Disks: DK, DL, DX, DY >; >; >; For the third parameter of the next question, enter the number >; of RK05 drives your target system has. Realize that an RK05F >; is a fixed media RK05 drive equivalent to two removable RK05 >; drives. Specify every RK05F as two RK05s. >; >; Enter [L/R,] vector, CSR, number of drives for: >; >* 3. DK controller 0 [D: 220,177404] [S]: ,,4 >; >* 3. DL controller 0 [D: 160,174400] [S]: ,,4 >* 53. Contr 0 unit 0. is an RL01/RL02 [D: RL01] [S]: RL02 >* 53. Contr 0 unit 1. is an RL01/RL02 [D: RL01] [S]: RL02 >* 53. Contr 0 unit 2. is an RL01/RL02 [D: RL01] [S]: SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-23 RL01 >* 53. Contr 0 unit 3. is an RL01/RL02 [D: RL01] [S]: RL01 >; >* 3. DX controller 0 [D: 264,177170] [S]: ,,2 >; >* 3. DY controller 0 [D: 264,177170] [S]: ,,2 >* 58. Contr 0 unit 0. is SINGLE/DOUBLE density [S]: DOUBLE >* 58. Contr 0 unit 1. is SINGLE/DOUBLE density [S]: DOUBLE >; >; Tapes: MM, MT >; >; Enter [L/R,] vector, CSR, number of drives for: >; >* 3. MM controller 0 [D: 224,172440] [S]: 120,,2 >* 51. MM controller 0 unit 0. formatter [O R:0-7 D:0]: >* 51. MM controller 0 unit 1. formatter [O R:0-7 D:0]: >; >* 3. MT controller 0 [D: 224,172522] [S]: ,,2 >; >; Non-physical (pseudo) devices: CO, NL, TI, CL, LB, SY >; >; Terminal interface devices: YL, YZ >; >; Enter vector, CSR, E=DL11-E modem support/NO=no for: >; >* 21. YL controller 0 [D: 60,177560,NO] [S]: >* 21. YL controller 1 [D: ,,NO] [S]: 310,175610 >* 21. YL controller 2 [D: ,,NO] [S]: 320,175620 >* 21. YL controller 3 [D: ,,NO] [S]: 330,175630 >; >; Enter vector, CSR, highest line number <0 to 7> [, answer speed] for: >; >* 24. YZ controller 0 [D: ,160100,,300] [S]: 430,160010,7,0 >; >* EOS * Do you want to: -continue E-exit P-pause [S]: >; >; >; End of interrupt vector area has been set to 1000 >; >; >; Create Executive build files >; >; >* 1. Do you wish to edit any of the Executive files? [Y/N]: SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-24 N >; >; >* EOS * Do you want to: -continue R-repeat section E-exit P-pause [S]: >; >; >; Assemble user-written driver(s) >; >; The following instructions apply to resident drivers and >; loadable drivers with resident data bases. >; >; For loadable drivers, you must ensure that a symbol definition >; of the format: >; LD$xx=0 >; (where xx is the device name) appears in the assembly prefix >; file [11,10]RSXMC.MAC for each loadable driver xxDRV. >: >; SYSGEN will now pause to allow you to assemble your driver(s) >; and USRTB module. Using a driver name xxDRV (where xx is >; the device name; for example, DK), you can type commands >; in the following format to assemble the driver and USRTB >; modules. >; >; MAC >; MAC>xxDRV=SY:[1,1]EXEMC/ML,SY:[11,10]RSXMC,xxDRV >; MAC>USRTB=SY:[1,1]EXEMC/ML,SY:[11,10]RSXMC,USRTB >; MAC>^Z >; >; Prepare for task building >; >; >; Clean-up extraneous object files >; >; >* EOS * Do you want to: -continue R-repeat section P-pause [S]: >DMO DL12: >; >; End of SYSGEN phase I at 09:57:09 on 10-DEC-86 >; -- Chaining to [200,200]SYSGEN2.CMD >; >; >; RSX-11M V4.2 BL38 System Generation PHASE II -- Version 2.11 >; >; 10-DEC-86 09:57:11 >; >; >; RL01/RL02 distribution kit SYSGEN version 3.05 for RSX-11M BL38C >; >; Continuation from SYSGEN PHASE I done on 10-DEC-86 at 09:57:05 >; >; SYSGEN assumes that the map disk is already mounted in DL13: with >; UFD [1,34]. >; >; >; SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-25 >; Phase II output saved answers created in file LB0:[200,200]SYSSAVED.CMD;1 >; >; >; Library build >; >; >; Executive task build >; >* 1. List Executive map? [Y/N]: N >; >; System image creation >; >; >; Full duplex terminal driver task build >; >; >; Loadable driver task build >; >* 4. Build all selected loadable drivers into DRVPAR? [Y/N]: Y >; You can now build your user-written driver (if it is a loadable >; driver). If you choose not to build it now, or it is not loadable >; strike carriage return in response to the next question. >; >; When all drivers are built, strike carriage return. >; >* 5. Driver 2-character device mnemonic [S]: >; >; Privileged task build >; >; >; Note that the following tasks will be built for your system: >; >; BOO DMO COT FCPMDL ICP INI INS >; PMT MCR MOU F11MSG MTAACP SAV TKTN >; UFD LOA UNL PMD RMD SHF PRT >; HEL ACS ERRLOG ELI >; >; >* 1. Map device for privileged tasks (ddu:) [D: NL:] [S]: >* 5. Pause to edit any task build .CMD or .ODL files? [Y/N]: N >* 6. Delete task build .CMD and .ODL files after building? [Y/N]: N >; >; >; System VMR >; >* 1. Edit SYSVMR.CMD? [Y/N]: Y >; >; An alternate version of SYSLIB.OLB, the system object library, was >; created to provide support for ANSI magtape/FCS big-buffering (which >; you selected in Phase I). You may want to rebuild DMP, FLX, PIP, and SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-26 >; VFY in Phase III to use ANSLIB.OLB. Note, however, building tasks with >; ANSLIB.OLB causes an increase in the size of tasks as compared to the >; SYSLIB.OLB version of the tasks. >; >; Because of the lack of adequate disk space on the RSXM38 disk, the tasks >; BAD, BRU, CDA, CMP, CRF, DMP, FMT, IOX, PAT, VFY, and ZAP were not >; included in the baseline system. If you want these tasks in your target >; system, they should be built in Phase III. >; >; When SYSGEN finishes, boot in your target system, and save the system with a >; bootstrap. For example: >; >; >BOO [1,54]RSX11M >; XDT: 38 >; >; XDT>G >; RSX11M V4.2 BL38 >; >; >; >TIM 12:00 14-JUN-85 >; >SAV /WB >; >; RSX11M V4.2 BL38 124.K MAPPED >; >RED LB:=SY: >; >RED LB:=LB: >; >MOU LB:RSXM38 >; >@LB:[1,2]STARTUP >; . >; . >; . >; >DMO DL13: >; >; End of SYSGEN phase II at 10:00:45 on 10-DEC-86 >; >@ > bye SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-27 10.3 RSX Sysgen - Phase I And II $ @presysgen %DCL-I-SUPERSEDE, previous value of LB has been superseded %DCL-S-SPAWNED, process BERG_1 spawned %DCL-S-ATTACHED, terminal now attached to process BERG_1 > set /uic=[200,200] > @sysgen >; >; RSX-11M V4.2 BL38C System Generation PHASE I -- Version 3.05 >; >; 10-DEC-86 10:03:44 >; RL01/RL02 distribution kit >; >* 3. Do you want to inhibit execution of MCR commands (PREPGEN)? [Y/N]: N >ASN SY:=LB: >ASN SY:=LB0: >ASN LB:=WK: >ASN LB:=WK0: >* 4. Have you made a copy of the distribution kit? [Y/N]: Y >* 5. Are you generating an unmapped system? [Y/N]: N >* 6. Use an input saved answer file? [Y/N]: Y >* 7. Name of input saved answer file [D: SYSSAVED.CMD] [S]: >; >; Phase I input saved answers >; created on 10-DEC-86 at 09:36:27 >; by SYSGEN version 3.05 >; are from file LB0:[200,200]SYSSAVED.CMD;1 >; >* 9. Name of output saved answer file [D: LB0:[200,200]SYSSAVED.CMD] [S]: SYSSAVED2.CMD >; >; Phase I output saved answers created in file LB0:[200,200]SYSSAVED2.CMD;1 >; >* 10. Use saved host configuration? [Y/N]: Y >* 11. Use saved peripheral configuration? [Y/N]: Y >* 12. Skip end of section (EOS) breakpoints? [Y/N]: Y >* 13. Skip end of execution (EOX) breakpoints? [Y/N]: Y >* 14. Clean up files from previous GENs? [Y/N]: Y >* 15. Chain to Phase II after Phase I completes? [Y/N]: Y >* 16. Enter device for EXCPRV disk when it is ready (ddu:) [D: DL1:] [S]: DL12: >; >MOU DL12:EXCPRV SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-28 %MOUNT-I-MOUNTED, EXCPRV mounted on _BISON$MDB2: >* 17. Enter device for PRVBLD disk when it is ready (ddu:) [D: DL2:] [S]: DL13: >; >MOU DL13:PRVBLD %MOUNT-I-MOUNTED, PRVBLD mounted on _BISON$MDB3: >SET /UIC=[1,1] >PIP [1,20]RSXBLD.CMD;*/DE/NM >PIP [1,24]RSXBLD.CMD;*/DE/NM,TTDRVBLD;* >PIP [1,50]SYSVMR.CMD;*/DE/NM,[1,54]SYSVMR;* >PIP [11,20]*.OBJ;*/DE/NM,*.UDC;*,*.ICR;*,*.IDS;*,*.PCS;* >PIP [11,24]*.OBJ;*/DE/NM,*.UDC;*,*.ICR;*,*.IDS;*,*.TTY;*,*.PCS;* >PIP [11,10]RSXMC.MAC;*/DE/NM,ICTAB;*,[200,200]SGNPARM.CMD;* >PIP [200,200]RSXBLD.CMD;*/DE/NM,TTDRVBLD;* >PIP SY:[11,20]RSXASM.CMD;*/DE/NM,RSXDRVASM;*,[12,20]MCRSETASM;* >PIP SY:[11,24]RSXASM.CMD;*/DE/NM,RSXDRVASM;*,[12,20]MCRSETASM;* >PIP DL12:[11,24]RSXASM.CMD;*/DE/NM,RSXDRVASM;*,[12,24]MCRSETASM;* >PIP /FR LB0: has 4250. blocks free, 5990. blocks used out of 10240. Largest contiguous space = 3235. blocks 1390. file headers are free, 146. headers used out of 1536. >SET /UIC=[11,10] >; >; Target configuration >; >; Processor:11/50 Memory Size:124K,Mapped System:RSX-11M >; >; Switch Register >; Floating Point Processor >; Extended Instruction Set >; >; Host configuration >; >; Executive Options >; >; Checkpointing support will be included >; >; >; Terminal driver options >; The Full Duplex Terminal Driver will be included. >; >; System Options >; >; >; Thinking ... >; End of Executive option generation at 10:07:33 on 10-DEC-86 >; >; Peripheral configuration >; >; Parameters appearing in square brackets "[...]" can only be >; specified for the first controller of a particular device. >; Parameters appearing in parentheses "(...)" only need be specified >; if the indicated option is present on the target system. >; >; The default for loadable drivers has been set to *TRUE*. SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-29 >; To override this setting enter R (resident) as the first parameter >; for the first controller of the specified device. >; >; A/D and Laboratory devices: None specified >; >; Interprocessor communication devices: None specified >; >; Unit record devices: LP >; >; Disks: DK, DL, DX, DY >; >; Tapes: MM, MT >; >; Non-physical (pseudo) devices: CO, NL, TI, CL, LB, SY >; >; Terminal interface devices: YL, YZ >; >SET /UIC=[1,24] ! Creating TTDRVBLD.CMD >SET /UIC=[11,10] >; End of interrupt vector area has been set to 1000 >; >; >; Create Executive build files >; >PIP RSXMC.MAC=DL12:RSXMC0.MAC/AP %MCR-I-SUPERSEDE, previous value of LB has been superseded >; >ASN SY:=LB: >; Start of Executive assembly at 10:09:48 on 10-DEC-86 >SET /UIC=[11,24] >MAC @SY:RSXASM >; >; End of Executive assembly at 10:19:00 on 10-DEC-86 >; >; Start of MCR (subset) assembly at 10:19:00 on 10-DEC-86 >SET /UIC=[12,24] >PIP *.OBJ;*/DE/NM >MAC @SY:MCRSETASM >; >; End of MCR (subset) assembly at 10:21:20 on 10-DEC-86 >; >; >; Start of device drivers assembly at 10:21:21 on 10-DEC-86 >SET /UIC=[11,24] >MAC @SY:RSXDRVASM >; >; End of device drivers assembly at 10:33:38 on 10-DEC-86 >ASN =LB: >; Assemble user-written driver(s) >; >; The following instructions apply to resident drivers and >; loadable drivers with resident data bases. >; >; For loadable drivers, you must ensure that a symbol definition >; of the format: SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-30 >; LD$xx=0 >; (where xx is the device name) appears in the assembly prefix >; file [11,10]RSXMC.MAC for each loadable driver xxDRV. >; >; SYSGEN will now pause to allow you to assemble your driver(s) >; and USRTB module. Using a driver name xxDRV (where xx is >; the device name; for example, DK), you can type commands >; in the following format to assemble the driver and USRTB >; modules. >; >; MAC >; MAC>xxDRV=SY:[1,1]EXEMC/ML,SY:[11,10]RSXMC,xxDRV >; MAC>USRTB=SY:[1,1]EXEMC/ML,SY:[11,10]RSXMC,USRTB >; MAC>^Z IND -- Pausing. To continue type "RES" > res IND -- Continuing >; >; Prepare for task building >; >SET /UIC=[1,24] >PIP RSX11M.OBS=[11,24]*.OBJ >PIP TTDRV.OBJ=[11,24]*.TTY >LBR RSX11M/CR:100.:1010.:128./-EP=RSX11M.OBS >LBR TTDRV/CR:30.:380.:64.=TTDRV >PIP [1,24]MCR.OBJ/NV/NM=[12,24]*.OBJ >PIP [12,24]*.OBJ;*/DE/NM >PIP /NV=[11,10]RSXBLD.CMD >PIP [11,10]RSXBLD.CMD;*/DE/NM >; >; Clean-up extraneous object files >; >PIP RSX11M.OBS;*/DE/NM,TTDRV.OBJ;*,[11,24]*.OBJ;*,*.TTY;* >DMO DL12: >ASN =LB0: >ASN =WK: >ASN =WK0: >; >; End of SYSGEN phase I at 10:36:25 on 10-DEC-86 >; -- Chaining to [200,200]SYSGEN2.CMD >; >SET /UIC=[200,200] >; >; RSX-11M V4.2 BL38 System Generation PHASE II -- Version 2.11 >; >; 10-DEC-86 10:36:28 >; >; >; RL01/RL02 distribution kit SYSGEN version 3.05 for RSX-11M BL38C >; >; Continuation from SYSGEN PHASE I done on 10-DEC-86 at 10:36:23 >; >; SYSGEN assumes that the map disk is already mounted in DL13: with >; UFD [1,34]. >; SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-31 >; >ASN SY:[1,54]TKB.TSK;1=TKL >ASN SY:=LB: >ASN SY:=LB0: >ASN LB:=WK: >ASN LB:=WK0: >; >; Phase II input saved answers >; created on 10-DEC-86 at 09:57:33 >; by SYSGEN version 2.11 >; are from file LB0:[200,200]SYSSAVED.CMD;1 >; >; >; Phase II output saved answers created in file LB0:[200,200]SYSSAVED2.CMD;1 >; >; >SET /UIC=[1,24] >PIP DL13:[1,24]MCR.OBJ/NV/NM=SY:[1,24]MCR.OBJ >PIP SY:[1,24]*.OBJ;*/DE/NM >ASN SY:=LB: %MCR-I-SUPERSEDE, previous value of LB has been superseded >PIP /FR LB0: has 3950. blocks free, 6290. blocks used out of 10240. Largest contiguous space = 3235. blocks 1381. file headers are free, 155. headers used out of 1536. >; >; Start of library build at 10:36:55 on 10-DEC-86 >; >SET /UIC=[1,1] >PIP LB:ANSLIB.OLB/NV=LB:SYSLIB.OLB >LBR LB:ANSLIB/RP=DL13:FCSMTA Module "ANSPAD" replaced Module "ASSLUN" replaced Module "BIGBUF" replaced Module "CLOSE " replaced Module "CONTRL" replaced Module "CREATE" replaced Module "DIRECT" replaced Module "FCSTYP" replaced Module "GET " replaced Module "GETSQ " replaced Module "OPEN " replaced Module "OPENR " replaced Module "OPFID " replaced Module "OPFNB " replaced Module "PARSFN" replaced Module "POINT " replaced Module "PUT " replaced Module "PUTSQ " replaced Module "RDWAIT" replaced Module "RETADR" replaced Module "RSTFDB" replaced Module "RWBLK " replaced Module "RWLONG" replaced Module "WATSET" replaced SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-32 Module "WTWAIT" replaced Module "WTWATD" replaced Module "PUT " replaced Module "PUTSQ " replaced >SET /UIC=[1,24] >LBR DL13:MCR/RP=DL13:MCR.OBJ Module "DV2OV " replaced Module "SPSOV " replaced Module "STSUB " replaced Module "SX1OV " replaced Module "SX2OV " replaced Module "SX3OV " replaced Module "SX4OV " replaced Module "ST5OV " replaced >; >; End of library build at 10:38:46 on 10-DEC-86 >; >; >; Start of Executive task build at 10:38:46 on 10-DEC-86 >; >; >; Build user-written driver(s) >; >; You must now edit the Executive build command file RSXBLD.CMD >; to include your user-written driver and data base in your system. >; >; If you are including a resident data base, locate the line >; in which the module SYSTB is referenced and add :USRTB >; immediately after it, for example: >; LB:[1,24]RSX11M/LB:SYSTB:USRTB:SYTAB:INITL,LB:[1,1]EXELIB/LB/SS >; Also, delete the line >; GBLDEF=$USRTB:0 >; If you are not including a resident data base, this line should >; be left in the file. >; >; For each resident driver, add a line of the form: >; LB:[1,24]RSX11M/LB:xxDRV >; where other drivers are referenced (where xx is the device name, >; for example DK). >; NOTE: For each loadable driver, do not add a corresponding >; line to the build command file. >; >; SYSGEN will now pause to allow you to edit RSXBLD.CMD. >; After you exit from the editor and resume, SYSGEN builds the >; Executive and drivers. IND -- Pausing. To continue type "RES" > edt rsxbld.cmd Edit Exec build file to add /CR to map files > res IND -- Continuing >PIP [1,34]*.*;*/DE/NM >TKL @LB:RSXBLD >; SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-33 >; End of Executive task build at 10:47:34 on 10-DEC-86 >; >; >; Start of system image creation at 10:47:35 on 10-DEC-86 >; >SET /UIC=[1,54] >PIP RSX11M.SYS/CO/NV/BL:498.=RSX11M.TSK >; >; End of system image creation at 10:47:41 on 10-DEC-86 >; >; >; Start of full duplex terminal driver task build at 10:47:41 on 10-DEC-86 >; >SET /UIC=[1,24] >TKL @LB:TTDRVBLD >; >; End of full duplex terminal driver task build at 10:48:20 on 10-DEC-86 >; >; >; Start of loadable driver task build at 10:48:20 on 10-DEC-86 >; >ASN SY:[1,54]TKB.TSK;1=TKL %MCR-I-SUPERSEDE, previous value of TKL has been superseded >ASN SY:=LB: %MCR-I-SUPERSEDE, previous value of LB has been superseded >ASN SY:=LB0: %MCR-I-SUPERSEDE, previous value of LB0 has been superseded >ASN LB:=WK: %MCR-I-SUPERSEDE, previous value of WK has been superseded >ASN LB:=WK0: %MCR-I-SUPERSEDE, previous value of WK0 has been superseded >TKL @DL13:CODRVBLD >TKL @DL13:DKDRVBLD >TKL @DL13:DLDRVBLD >TKL @DL13:DXDRVBLD >TKL @DL13:DYDRVBLD >TKL @DL13:LPDRVBLD >TKL @DL13:MMDRVBLD >TKL @DL13:MTDRVBLD >; You can now build your user-written driver (if it is a loadable >; driver). If you choose not to build it now, or it is not loadable >; strike carriage return in response to the next question. >; >; When all drivers are built, strike carriage return. >; >ASN =TKL >ASN =LB0: >ASN =WK: >ASN =WK0: >; >; End of loadable driver task build at 10:50:57 on 10-DEC-86 >; >; >; Start of privileged task build at 10:50:58 on 10-DEC-86 >; SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-34 >; >; Note that the following tasks will be built for your system: >; >; BOO DMO COT FCPMDL ICP INI INS >; PMT MCR MOU F11MSG MTAACP SAV TKTN >; UFD LOA UNL PMD RMD SHF PRT >; HEL ACS ERRLOG ELI >; >; >; >ASN SY:[1,54]TKB.TSK;1=TKL >ASN SY:=LB: %MCR-I-SUPERSEDE, previous value of LB has been superseded >ASN SY:=LB0: >ASN LB:=WK: >ASN LB:=WK0: >; >; Creating the task build .CMD and .ODL files in DL13:[1,24] >; >TKL @DL13:[1,24]BOOBLD.CMD >TKL @DL13:[1,24]DMOBLD.CMD >TKL @DL13:[1,24]COTBLD.CMD >TKL @DL13:[1,24]FCPMDLBLD.CMD >TKL @DL13:[1,24]ICPBLD.CMD >TKL @DL13:[1,24]INIBLD.CMD >TKL @DL13:[1,24]INSBLD.CMD >TKL @DL13:[1,24]PMTBLD.CMD >TKL @DL13:[1,24]MCRBLD.CMD >TKL @DL13:[1,24]MOUBLD.CMD >TKL @DL13:[1,24]F11MSGBLD.CMD >TKL @DL13:[1,24]MTABLD.CMD >TKL @DL13:[1,24]SAVBLD.CMD >TKL @DL13:[1,24]TKNBLD.CMD >TKL @DL13:[1,24]UFDBLD.CMD >TKL @DL13:[1,24]LOABLD.CMD >TKL @DL13:[1,24]UNLBLD.CMD >TKL @DL13:[1,24]PMDBLD.CMD >TKL @DL13:[1,24]RMDBLD.CMD >TKL @DL13:[1,24]SHFBLD.CMD >TKL @DL13:[1,24]PRTBLD.CMD >TKL @DL13:[1,24]HELBLD.CMD >TKL @DL13:[1,24]ACSBLD.CMD >TKL @DL13:[1,24]ERLBLD.CMD >TKL @DL13:[1,24]ELIBLD.CMD >; >; End of privileged task build at 11:30:01 on 10-DEC-86 >; >; >; Start of system VMR at 11:30:01 on 10-DEC-86 >; >SET /UIC=[1,54] >; >; >; Pausing to allow editing of SYSVMR.CMD >; SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-35 IND -- Pausing. To continue type "RES" > edt sysvmr.cmd Edit system VMR file as proscribed. > res IND -- Continuing >ASN SY:[1,54]VMR.TSK;1=VMR %MCR-I-SUPERSEDE, previous value of LB has been superseded >ASN SY:=LB: >VMR @SYSVMR VMR -- *DIAG*-Partition reduced to executive common size INS EXCOM1 VMR -- *DIAG*-Partition reduced to executive common size INS EXCOM2 VMR -- *DIAG*-Loadable driver larger than 4K LOA TT: VMR -- *DIAG*-Installed tasks may no longer fit in partition SET /TOP=DRVPAR:-* POOL=1000:5650.:05650. EXCOM1 077734 100000 011200 MAIN COM EXCOM2 077670 111200 010100 MAIN COM LDRPAR 077624 121300 002600 MAIN TASK TTPAR 077260 124100 030000 MAIN TASK DRVPAR 076734 154100 013300 MAIN SYS 076670 154100 002100 SUB DRIVER - DL: 076570 156200 004200 SUB DRIVER - MM: 076470 162400 003400 SUB DRIVER - MT: 076370 166000 001100 SUB DRIVER - LP: 076270 167100 000300 SUB DRIVER - CO: SYSPAR 076224 167400 011700 MAIN TASK FCPPAR 076160 201300 024200 MAIN SYS GEN 076114 225500 532300 MAIN SYS LDR... 13.02 077510 LDRPAR 248. 002600 LB0:-00005027 FIXED TKTN 05.00 073020 SYSPAR 248. 011700 LB0:-00020132 ...RMD 03.00 075550 GEN 225. 027200 LB0:-00020621 F11MSG 13.00 074754 GEN 200. 005700 LB0:-00017460 MTAACP 15.00 074640 GEN 200. 014700 LB0:-00020143 ...DMO 04.00 075320 GEN 160. 014600 LB0:-00016562 MCR... 05.03 073500 SYSPAR 160. 011700 LB0:-00017560 ...MOU 27.01 073364 GEN 160. 037700 LB0:-00017402 F11ACP 05.01 076000 FCPPAR 149. 024200 LB0:-00016675 ERRLOG 2.00 075204 GEN 148. 040000 LB0:-00021153 PMT... 2.00 074160 GEN 148. 006300 LB0:-00017055 COT... 2.0 075664 GEN 145. 017100 LB0:-00016601 PMD... 08.01 074044 GEN 140. 017200 LB0:-00020551 SHF... 6.00 073134 SYSPAR 105. 011700 LB0:-00020532 ...INS 9.01 074274 GEN 100. 034600 LB0:-00017343 ...SAV 05.00 073250 GEN 100. 033300 LB0:-00020407 ...UFD 05.00 072704 GEN 100. 005700 LB0:-00020271 ...ACS 3.00 075434 GEN 70. 013700 LB0:-00021135 PRT... 9.00 073730 GEN 70. 010200 LB0:-00020747 ...AT. 8.2 074410 GEN 64. 060000 LB0:-00017147 ...ELI 1.00 075070 GEN 50. 040000 LB0:-00021217 ...MAG 03.00 074524 GEN 50. 031500 LB0:-00020002 SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-36 ...LOA 04.02 073614 GEN 50. 032600 LB0:-00020301 ...UNL 4.02 072570 GEN 50. 024500 LB0:-00020471 LP0: Loaded DK0: Unloaded DK1: Unloaded DK2: Unloaded DK3: Unloaded DL0: Loaded DL1: Loaded DL2: Loaded DL3: Loaded DX0: Unloaded DX1: Unloaded DY0: Unloaded DY1: Unloaded MM0: Loaded MM1: Loaded MT0: Loaded MT1: Loaded CO0: TT0: TT0: Loaded TT1: Loaded TT2: Loaded TT3: Loaded TT4: Loaded TT5: Loaded TT6: Loaded TT7: Loaded TT10: Loaded TT11: Loaded TT12: Loaded TT13: Loaded NL0: TI0: CL0: TT0: LB0: DK0: SY0: DK0: >; >; End of system VMR at 11:43:13 on 10-DEC-86 >; >; >; An alternate version of SYSLIB.OLB, the system object library, was >; created to provide support for ANSI magtape/FCS big-buffering (which >; you selected in Phase I). You may want to rebuild DMP, FLX, PIP, and >; VFY in Phase III to use ANSLIB.OLB. Note, however, building tasks with >; ANSLIB.OLB causes an increase in the size of tasks as compared to the >; SYSLIB.OLB version of the tasks. >; >; Because of the lack of adequate disk space on the RSXM38 disk, the tasks >; BAD, BRU, CDA, CMP, CRF, DMP, FMT, IOX, PAT, VFY, and ZAP were not >; included in the baseline system. If you want these tasks in your target >; system, they should be built in Phase III. >; >; When SYSGEN finishes, boot in your target system, and save the system with a >; bootstrap. For example: SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-37 >; >; >BOO [1,54]RSX11M >; XDT: 38 >; >; XDT>G >; RSX11M V4.2 BL38 >; >; >; >TIM 12:00 14-JUN-85 >; >SAV /WB >; >; RSX11M V4.2 BL38 124.K MAPPED >; >RED LB:=SY: >; >RED LB:=LB: >; >MOU LB:RSXM38 >; >@LB:[1,2]STARTUP >; . >; . >; . >; >ASN =TKL >ASN =LB0: >ASN =WK: >ASN =WK0: >DMO DL13: >; >; End of SYSGEN phase II at 11:43:14 on 10-DEC-86 >; >SET /UIC=[200,200] >@ > mou dl13:prvbld %MOUNT-I-MOUNTED, PRVBLD mounted on _BISON$MDB3: > pip dl11:[1,34]/cd/fo/nv=dl13:[1,34]*.map > dmo dl13: > bye SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-38 10.4 RSX Sysgen - Phase III $ @presysgen %DCL-I-SUPERSEDE, previous value of LB has been superseded %DCL-S-SPAWNED, process BERG_1 spawned %DCL-S-ATTACHED, terminal now attached to process BERG_1 > set /uic=[200,200] > @sysgen3 >ASN SY:[1,54]TKB.TSK;1=TKL >ASN SY:=LB: >ASN SY:=LB0: >ASN LB:=WK: >ASN LB:=WK0: >; >; RSX-11M V4.2 System Generation PHASE III -- Version 2.05 >; >; 10-DEC-86 12:42:45 >; >* 1. In what UIC is SGNPARM.CMD if not in [200,200] [S]: >; >; RL01/RL02 distribution kit SYSGEN version 3.05 for RSX-11M BL38C >; >; Continuation from SYSGEN PHASE I done on 10-DEC-86 at 10:36:23 >; >* 2. Are you building nonprivileged tasks? [Y/N]: Y >* 2A. Is this an RL01 kit? [Y/N]: Y >* 3. Enter device for RLUTIL device when it is ready (ddu:) [D: DL12:] [S]: DL14: >MOU DL14:RLUTIL %MOUNT-I-MOUNTED, RLUTIL mounted on _BISON$MDB4: >* 4. Enter map device (ddu:) [D: NL:] [S]: %MCR-I-SUPERSEDE, previous value of LB has been superseded >; >ASN SY:=LB: >; For nonprivileged tasks: * -- Prints the table of tasks >; % -- Builds all tasks >; . -- Terminates inquiry >; >; Enter responses separated by commas. All responses need >; not fit on one line. >; >; Example: BAD,LBR,PIP,. >; >* 5. Enter task name(s) [S]: BRU,DMP,FLX,PIP,VFY >* 5. Enter task name(s) [S]: BAD,CDA,CMP,CRF,DSC,EDT >* 5. Enter task name(s) [S]: FMT,FTB,IOX,PAT,RPT,ZAP >* 5. Enter task name(s) [S]: MAC,STK,TKB. >; SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-39 >; LB:[1,1]ANSLIB.OLB can be used to build certain tasks >; so that those tasks have ANSI/big-buffered support >; >* 7. Use LB:[1,1]ANSLIB.OLB when building those tasks? [Y/N]: Y >* 11. Pause to edit any task build .CMD or .ODL files? [Y/N]: N >* 12. Delete task build .CMD and .ODL files after task building? [Y/N]: N >SET /UIC=[1,24] >; >; Creating the task build .CMD and .ODL files in DL14:[1,24] >; >TKL @DL14:[1,24]BRUBLD.CMD >TKL @DL14:[1,24]DMPANSBLD.CMD >TKL @DL14:[1,24]FLXANSBLD.CMD >TKL @DL14:[1,24]PIPANSBLD.CMD >TKL @DL14:[1,24]VFYANSBLD.CMD >TKL @DL14:[1,24]BADBLD.CMD >TKL @DL14:[1,24]CDABLD.CMD >TKL @DL14:[1,24]CMPBLD.CMD >TKL @DL14:[1,24]CRFBLD.CMD >TKL @DL14:[1,24]DSCBLD.CMD >TKL @DL14:[1,24]EDTBLD.CMD >TKL @DL14:[1,24]FMTBLD.CMD >TKL @DL14:[1,24]FTBBLD.CMD >TKL @DL14:[1,24]IOXBLD.CMD >TKL @DL14:[1,24]PATBLD.CMD >TKL @DL14:[1,24]RPTBLD.CMD >TKL @DL14:[1,24]ZAPBLD.CMD >TKL @DL14:[1,24]MACBLD.CMD >TKL @DL14:[1,24]STKBLD.CMD >TKL @DL14:[1,24]TKBBLD.CMD >ASN =LB: >SET /UIC=[200,200] >@ > dmo dl14: > @sysgen3 >ASN SY:[1,54]TKB.TSK;1=TKL %MCR-I-SUPERSEDE, previous value of TKL has been superseded >ASN SY:=LB: %MCR-I-SUPERSEDE, previous value of LB has been superseded >ASN SY:=LB0: %MCR-I-SUPERSEDE, previous value of LB0 has been superseded >ASN LB:=WK: %MCR-I-SUPERSEDE, previous value of WK has been superseded >ASN LB:=WK0: %MCR-I-SUPERSEDE, previous value of WK0 has been superseded >; >; RSX-11M V4.2 System Generation PHASE III -- Version 2.05 >; >; 10-DEC-86 13:35:43 >; >* 1. In what UIC is SGNPARM.CMD if not in [200,200] [S]: >; SAMPLE UPDATE AND SYSGEN OUTPUT Page 10-40 >; RL01/RL02 distribution kit SYSGEN version 3.05 for RSX-11M BL38C >; >; Continuation from SYSGEN PHASE I done on 10-DEC-86 at 10:36:23 >; >* 2. Are you building nonprivileged tasks? [Y/N]: N >* 2A. Is this an RL01 kit? [Y/N]: Y >* 3. Enter device for PRVBLD device when it is ready (ddu:) [D: DL12:] [S]: DL13: >MOU DL13:PRVBLD %MOUNT-I-MOUNTED, PRVBLD mounted on _BISON$MDB3: >* 4. Enter map device (ddu:) [D: NL:] [S]: %MCR-I-SUPERSEDE, previous value of LB has been superseded >; >ASN SY:=LB: >; Enter responses separated by commas. All responses need >; not fit on one line. >; >; Example: BOO,DMO,INS,. >; >* 5. Enter task name(s) [S]: SHUTUP,MCRMU,BRO,TDX. >* 11. Pause to edit any task build .CMD or .ODL files? [Y/N]: N >* 12. Delete task build .CMD and .ODL files after task building? [Y/N]: N >SET /UIC=[1,24] >; >; Creating the task build .CMD and .ODL files in DL13:[1,24] >; >TKL @DL13:[1,24]SHUBLD.CMD >TKL @DL13:[1,24]MCMBLD.CMD >TKL @DL13:[1,24]BROBLD.CMD >TKL @DL13:[1,24]TDXBLD.CMD >ASN =LB: >SET /UIC=[200,200] >@ > dmo dl13: > bye $ @post_sysgen3 %PURGE-I-FILPURG, MDB1:[001,054]BRU.TSK;1 deleted (181 blocks) %PURGE-I-FILPURG, MDB1:[001,054]FLX.TSK;1 deleted (132 blocks) %PURGE-I-FILPURG, MDB1:[001,054]MAC.TSK;1 deleted (89 blocks) %PURGE-I-FILPURG, MDB1:[001,054]PIP.TSK;1 deleted (73 blocks) %PURGE-I-FILPURG, MDB1:[001,054]TKB.TSK;1 deleted (182 blocks) %PURGE-I-TOTAL, 5 files deleted (657 blocks) CHAPTER 11 SAMPLE LAYERED PRODUCTS INSTALLATION AND UPDATE The following two sections are samples of terminal output generated by the RSX layered product installation and update procedures. The errors reported in the procedures result from trying to INS and REM tasks. These commands produce errors since the procedures are running on a VAX and not on an RSX system. SAMPLE LAYERED PRODUCTS INSTALLATION AND UPDATE Page 11-2 11.1 PDP-11 FORTRAN-77/RSX Installation And Update $ def rsx_factory$commands dua0:[rsx11msys.rsx_factory.rsx_factory.com] $ set def rsx_factory$commands $ @prelproduct %DCL-I-ALLOC, _MFA0: allocated %DCL-I-ALLOC, _DLA1: allocated %DCL-I-ALLOC, _DLA0: allocated %MOUNT-I-WRITELOCK, volume is write locked %MOUNT-I-MOUNTED, mounted on _MFA0: %MOUNT-I-MOUNTED, RSXM38 mounted on _BISON$DLA1: %MOUNT-I-MOUNTED, M42UPDATEC mounted on _BISON$DLA0: %DCL-S-SPAWNED, process BERG_1 spawned %DCL-S-ATTACHED, terminal now attached to process BERG_1 > asn dl1:=ds: > asn mf0:=sr: > @rsx_factory$commands:instalf77 >; >Asn ds:=sy: >Asn sr:=mf: >Asn sy:=fp: >Asn sy:=lb: >Ufd [11,36] >Set /uic=[11,36] >Flx sy:=mf:f77.olb >Flx sy:=mf:f7711m.* >Flx sy:[11,36]=mf:[11,37]*.obj >Set /uic=[1,1] >Flx lb:[1,1]=mf:[11,40]*.obj,*.odl,*.mac >Flx lb:[1,1]=mf:[11,40]*.ftn >Set /uic=[1,2] >Flx lb:[1,2]=mf:[1,2]f77com.msg/im:64./bl:14. >; >Set /uic=[1,54] >Tkb @[11,36]f7711m >; >Set /uic=[1,1] >Lbr lb:f77ots.olb/cr:150.=[11,36]short.obj >Lbr lb:f77ots.olb/dg:$ertxt Entry points deleted: $ERTXT >Lbr lb:f77ots.olb=[11,36]f4pots.obj >Lbr lb:f77ots.olb=[11,36]fcs11m.obj >@ > rename ds:[1,54]f77.exe f77.tsk > asn dl0:=sr: %MCR-I-SUPERSEDE, previous value of SR has been superseded > @rsx_factory$commands:setupf77u >; >Asn ds:=sy: %MCR-I-SUPERSEDE, previous value of SY has been superseded >Asn sy:=fp: %MCR-I-SUPERSEDE, previous value of FP has been superseded >Asn sy:=lb: SAMPLE LAYERED PRODUCTS INSTALLATION AND UPDATE Page 11-3 %MCR-I-SUPERSEDE, previous value of LB has been superseded >Set /uic=[11,36] >Copy sr:[246,200]f77.cmd sy:[11,36]* >Copy sr:[246,200]*.obj sy:[11,36]* >@ > @f77 >; >; >; >; >; >; >; Begin Update process for FORTRAN-77 V5.0-20 software >; on 13-DEC-86 at 16:59:58. >; >; >; >; >; Patch the compiler object module library. >; >; >LBR SY:[11,36]F77/RP=SY:[11,36]F77COMUPD.OBJ Module "BINUTI" replaced Module "CLASFY" replaced Module "CODEMI" replaced Module "CODEX1" replaced Module "CODMOV" replaced Module "CODTAB" replaced Module "DCLDAT" replaced Module "DECLAR" replaced Module "ENTER0" replaced Module "EXPDRV" replaced Module "EXPRED" replaced Module "FTDMP " replaced Module "GETREC" replaced Module "IOBLKS" replaced Module "LEXAN0" replaced Module "OPTCSE" replaced Module "OPTDRV" replaced Module "OPTIOP" replaced Module "SYNIO " replaced >; >; ONLY DELETE THE UPDATED OBJECTS IF REQUESTED >; >* Do you want to delete the update file F77COMUPD.OBJ? [Y/N]: N >; >; Re-build the compiler. >; >* Do you wish to re-taskbuild the compiler? [Y/N]: Y >SET /UIC=[1,1] >ASN SY:=FP: %MCR-I-SUPERSEDE, previous value of FP has been superseded >* Do you want to delete the existing compiler? [Y/N]: SAMPLE LAYERED PRODUCTS INSTALLATION AND UPDATE Page 11-4 Y >PIP F77.TSK;0/DE PIP -- No such file(s) SY0:[1,1]F77.TSK;0 >TKB @SY:[11,36]F7711M >ASN =FP: >REM ...F77 %MCR-W-ACTIMAGE, error activating image REM >INS F77 %MCR-W-ACTIMAGE, error activating image INS >; -CLI-E-IMAGEFNF, image file not found BISON$DBA0:[SYS0.][SYSEXE]REM.EXE; -CLI-E-IMAGEFNF, image file not found BISON$DBA0:[SYS0.][SYSEXE]INS.EXE; >; Patch the OTS library. >; >* Is the FORTRAN-77 OTS library LB:[1,1]SYSLIB.OLB? [Y/N]: N >* Is the FORTRAN-77 OTS library LB:[1,1]F4POTS.OLB? [Y/N]: N >* Enter the FORTRAN-77 OTS file specification [S]: LB:[1,1]F77OTS.OLB >* Verify - OTS library is LB:[1,1]F77OTS.OLB? [Y/N]: Y >; >; Update the OTS >; >LBR LB:[1,1]F77OTS.OLB/RP=SY:[11,36]COMOTSUPD.OBJ Module "$CONVR" replaced Module "$DSINH" replaced Module "$FIO " replaced Module "$SINH " replaced Module "$VINIT" replaced >; >; Delete update file only if requested >; >* Do you want the update file COMOTSUPD.OBJ deleted? [Y/N]: N >* Is LB:[1,1]F77OTS.OLB an RMS OTS? [Y/N]: N >; >; Update the FCS OTS >; >LBR LB:[1,1]F77OTS.OLB/RP=SY:[11,36]FCSOTSUPD.OBJ Module "$OPEN " replaced Module "$OSU " replaced >; >; Delete update file only if requested >; >* Do you want the update file FCSOTSUPD.OBJ deleted? [Y/N]: N >* Does LB:[1,1]F77OTS.OLB contain the optional F4PCVF.OBJ module? [Y/N]: N >; >SET /UIC=[200,200] >; SAMPLE LAYERED PRODUCTS INSTALLATION AND UPDATE Page 11-5 >; Finished with Update process for FORTRAN-77 V5.0-20 software >; on 13-DEC-86 at 17:08:23. >; >@ > rename dl1:[1,1]f77.exe [1,54]f77.tsk > pip dl1:[1,1]/cd/fo/nv=dl1:[11,36]f4pcvf.obj > bye $ @cleanup_f77 %PURGE-I-FILPURG, DLA1:[001,054]F77.TSK;1 deleted (375 blocks) %PURGE-I-FILPURG, DLA1:[001,001]F4PCVF.OBJ;1 deleted (4 blocks) $ Rename DLA1:[1,1]F4P11S.* DLA1:[1,1]F7711S.* $ Rename DLA1:[1,1]F4PMAP.* DLA1:[1,1]F77MAP.* $ Rename DLA1:[1,1]F4PCVF.* DLA1:[1,1]F77CVF.* $ Rename DLA1:[1,1]F4PEIS.* DLA1:[1,1]F77EIS.* $ Rename DLA1:[1,1]F4PNIO.* DLA1:[1,1]F77NIO.* $ Rename DLA1:[1,1]F4PNER.* DLA1:[1,1]F77NER.* $ Rename DLA1:[1,1]F4PRAN.* DLA1:[1,1]F77RAN.* $ Rename DLA1:[1,1]F4PRES.* DLA1:[1,1]F77RES.* $ Set Noverify %PURGE-I-NOFILPURG, no files purged SAMPLE LAYERED PRODUCTS INSTALLATION AND UPDATE Page 11-6 11.2 PDP-11 Symbolic Debugger/RSX Installation $ def rsx_factory$commands dua0:[rsx11msys.rsx_factory.rsx_factory.com] $ set def rsx_factory$commands $ @prelproduct %DCL-I-ALLOC, _MFA0: allocated %DCL-I-ALLOC, _DLA1: allocated %DCL-I-ALLOC, _DLA0: allocated %MOUNT-I-WRITELOCK, volume is write locked %MOUNT-I-MOUNTED, BACKUP mounted on _MFA0: %MOUNT-I-MOUNTED, RSXM38 mounted on _BISON$DLA1: %MOUNT-I-WRITELOCK, volume is write locked %MOUNT-I-MOUNTED, M42UPDATEC mounted on _BISON$DLA0: %DCL-S-SPAWNED, process BERG_1 spawned %DCL-S-ATTACHED, terminal now attached to process BERG_1 > asn dl1:=ds: > asn mf0:=sr: > asn dl0:=up: > @rsx_factory$commands:setupdbgi >Asn ds:=sy: >Asn sr:=mf: >Asn sy:=lb: >BRU/Dens:1600/Bac:DBGREL/Rew/Noi/Ufd/New MF: SY: BRU - Starting Tape 1 on MF0: BRU - End of Tape 1 on MF0: BRU - Completed >BRU/Dens:1600/Bac:INSTAL/Rew/Noi/Ufd/New MF: SY: BRU - Starting Tape 1 on MF0: BRU - End of Tape 1 on MF0: BRU - Completed >Set /uic=[247,200] >Ufd [247,200] >Copy up:[247,200]*.* sy:[247,200] >@ > set /uic=[1,61] > set def [247,247] > edt instal.cmd DL1:[247,247]INSTAL.CMD;2 1227 lines @INSTAL RSX-11M/M-PLUS Auto-Installation Procedure for PDP-11 Languages 16-DEC-86 12:55:08 Type "?" for help; CTRL/Z to end; RETURN to accept default (given in <>); or valid input. Where are the distribution files located ? MF0:[247,247] Type "?" for help; CTRL/Z to go to previous question; RETURN to accept default (given in <>); or valid input. SAMPLE LAYERED PRODUCTS INSTALLATION AND UPDATE Page 11-7 Products <>: DBG BRU - Starting Tape 1 on MF0: BRU - End of Tape 1 on MF0: BRU - Completed Copying files from MF0:[247,247] to LB0:[247,247] BRU - Starting Tape 1 on MF0: BRU - End of Tape 1 on MF0: BRU - Completed BRU - Starting Tape 1 on MF0: BRU - End of Tape 1 on MF0: BRU - Completed Reading CONFIG.DBG Type "?" for help; CTRL/Z to go to previous question; RETURN to accept default (given in <>); or valid input. Do you want to edit CONFIG.DBG (Y/N) ? Y Configuration Data File Editor ------------------------------ Enter new values when prompted. RETURN leaves value unchanged. CTRL-Z copies any remaining values from old file and exits. PROD (Product name) = DBG TSKNAM (Task name) = ...D77 TSKDIR (Task directory) = NONE TSKDIR (Task directory) = PREPR (Build the command file used by TKB) = BLDTKB.CMD IVP (IVP command file name) = DBGVER.CMD IDSPAC (I/D space support) = NO IDSPAC (I/D space support) = EDITQ (Allow editing of this configurations file) = YES EDITQ (Allow editing of this configurations file) = PURGE (Purge old versions of the debugger if installation is successful) = YES PURGE (Purge old versions of the debugger if installation is successful) = FILSYS (File services (FCSD,RMSD,FCSM,FCSS,RMSS,UNKNOWN)) = UNKNOWN SAMPLE LAYERED PRODUCTS INSTALLATION AND UPDATE Page 11-8 FILSYS (File services (FCSD,RMSD,FCSM,FCSS,RMSS,UNKNOWN)) = RMSD UPDATE (Update the product) = YES UPDATE (Update the product) = ^Z New LB0:[247,247]CONFIG.DBG file created. Type "?" for help; CTRL/Z to go to previous question; RETURN to accept default (given in <>); or valid input. Do you want to edit CONFIG.DBG (Y/N) ? Determining system configuration Running pre-processing command procedure BLDTKB.CMD Module "D$B16 " replaced Module "D$BPT " replaced Updating DBG Module "ARITH " replaced Module "ARITH2" replaced Module "GVS " replaced Module "GVSBLI" replaced Module "GVSF77" replaced Module "INI " replaced Module "OVERLA" replaced Module "RESIDE" replaced Building product DBG TKB -- *DIAG*-Module VEXTA ambiguously defines P-section $$CBL Copying PDPDBG.OLB to LB:[1,1]PDPDBG.OLB Copying PDPDBG.OBJ to LB:[1,1]PDPDBG.OBJ Copying PDPDBG.ODL to LB:[1,1]PDPDBG.ODL Copying PDPDBG.HLP to LB:[1,2]PDPDBG.HLP Copying DBGREL.DOC to LB:[1,2]DBGREL.DOC %MCR-W-ACTIMAGE, error activating image REMOVE Copying PDPDBG.TSK to LB0:[1,54]PDPDBG.TSK -CLI-E-IMAGEFNF, image file not found BISON$DBA0:[SYS0.][SYSEXE]REMOVE.EXE; PIP -- No such file(s) LB0:[247,247]PDPDBG.TSK *** LB0:[247,247]PDPDBG.TSK not copied to LB0:[1,54] ***** Installation of PDP-11 Symbolic Debugger UNsuccessful Type "?" for help; CTRL/Z to go to previous question; RETURN to accept default (given in <>); or valid input. Products <>: Type "?" for help; CTRL/Z to end; RETURN to accept default (given in <>); SAMPLE LAYERED PRODUCTS INSTALLATION AND UPDATE Page 11-9 or valid input. Where are the distribution files located ? Auto-installation ended on 16-DEC-86 at 13:06:10. > copy [247,247]pdpdbg.exe [1,54]pdpdbg.tsk > bye CHAPTER 12 SAMPLE SRD INSTALLATION The following section contains output from an SRD installation procedure. $ Set Def dua0:[rsx11msys.decus_add.srd_v6_6.source] $ Ass dua0:[rsx11msys.rsx11m.rsx11m_V4_2b.rsxm38.] lb/TRANS=(CONC,TERM) $ Spawn/cli=mcr > @SRD >; >; Question/Answer phase >; >; To get help hit ESCAPE from any prompt. >; >* Are you using P/OS? [Y/N]: N >* Are you using Micro/RSX? [Y/N]: N >* Are you using RSX-11M-PLUS? [Y/N]: N >* Are you using RSX-11M, MAPPED? [Y/N]: Y >* Are you running RSX-11M Version 4.0 or later? [Y/N]: Y >* Do you have DCL or User-written CLI support? [Y/N]: N >* Do you have the extend task directive? [Y/N]: Y >* Are you using dynamic checkpoint allocation? [Y/N]: Y >* Do you want to build SRD using FCSRES? [Y/N]: N >* Does your machine have EIS? [Y/N]: Y >; >; Creating Switch Defaults >; >; The next few questions are for users who are familiar with the available >; SRD switches. Some of the switches are presented in groups, allowing you >; to choose the entire group as a default. Simply answer N if you do not >; want the entire group - questions for the individual switches will then be >; presented later. >; SAMPLE SRD INSTALLATION Page 12-2 >; Do you want these switch defaults: >* /LI /SR /-WD /-00? [Y/N]: Y >* /AT /M2 /WI ? [Y/N]: N >* /BK /HD /SM ? [Y/N]: N >* /-NA /-RD ? [Y/N]: N >; >; In the following section, you will be asked which switches you would >; like to have as the default. Help is also available at these >; prompts by typing the ESCAPE key. Answer Y for any switch default >; you would like. >; >; As a default, would you like switch ... >* /NA - the sort to be in name order? [Y/N]: Y >* /RD - to use the Revision Date in Date Matches? [Y/N]: >* /SY - System Accounts in [*,*] searches? [Y/N]: Y >* /AT - output device attached if terminal? [Y/N]: Y >* /WI - implicit wildcarding? [Y/N]: >* /M2 - the Type 2 Middle Size Listing? [Y/N]: Y >* /HD - the command line to appear in the header? [Y/N]: Y >* /SM - the summary listing by default? [Y/N]: Y >* /BK - two blanks preceding file names listed? [Y/N]: >; >; Q/A complete >; >; Creating SRDDEF.HLP >; Creating SRDCML.BLD >; Creating SRD.BLD >; Creating SRD.ODL >; Creating SRDSYS.MAC >; >; Assemble the source modules >; >* Do you want to assemble all the modules? [Y/N]: Y >MAC SRDATA=SRDSYS,SRDPRE,SRDATA >MAC SRDINI=SRDSYS/PA:1,SRDPRE/PA:1,SRDINI >MAC SRDLST=SRDSYS/PA:1,SRDPRE/PA:1,SRDLST >MAC SRDNUD=SRDSYS/PA:1,SRDPRE/PA:1,SRDNUD >MAC SRDOPR=SRDSYS/PA:1,SRDPRE/PA:1,SRDOPR >MAC SRDROT=SRDSYS/PA:1,SRDPRE/PA:1,SRDROT >MAC SRDSRT=SRDSYS/PA:1,SRDPRE/PA:1,SRDSRT >MAC SRDSUB=SRDSYS/PA:1,SRDPRE/PA:1,SRDSUB SAMPLE SRD INSTALLATION Page 12-3 >MAC SRDTST=SRDSYS/PA:1,SRDPRE/PA:1,SRDTST >MAC SRDTRP=SRDSYS/PA:1,SRDPRE/PA:1,SRDTRP >MAC SRDREP=SRDSYS/PA:1,SRDPRE/PA:1,SRDREP >MAC SRDDBF=SRDSYS/PA:1,SRDPRE/PA:1,SRDDBF >MAC SRDXX1=SRDSYS/PA:1,SRDPRE/PA:1,SRDXX1 >MAC SRDXX2=SRDSYS/PA:1,SRDPRE/PA:1,SRDXX2 >MAC SRDXX3=SRDSYS/PA:1,SRDPRE/PA:1,SRDXX3 >; >; Now taskbuild SRD >; >TKB @SRD.BLD >; >; SRD Build complete >; >@ > BYE $ Copy SRD.TSK [-.task]SRD.TSK CHAPTER 13 SAMPLE GENERATION OF HELP FILES The following output shows the extraction of the help files from the help library on the HLPDCL disk. Full help for MCR and utilities is selected, but no help for DCL or example files. $ @RSX_FACTORY$COMMANDS:PREHELP > set /uic=[1,2] > lbr helpbuild.cmd=help.ulb/ex:build > @helpbuild >; >; BRIEF HELP support for MCR and/or DCL gives the command, >; function, and syntax without extensive comments. >; >; FULL HELP support for MCR and/or DCL gives a full description >; of each command element rather than just listing them. >; >; There is no difference between FULL and BRIEF HELP support >; for the RSX-11M UTILITIES. >; >; Answer YES if you want FULL HELP support for MCR and all >; the UTILITIES. >; >* Do you want FULL HELP support for MCR? [Y/N]: Y >; >; Answer YES if you want FULL HELP support for DCL and all >; the UTILITIES. >; >* Do you want FULL HELP support for DCL? [Y/N]: N >; >; Answer YES if you want BRIEF HELP support for DCL and all >; the UTILITIES. >; >* Do you want BRIEF HELP support for DCL? [Y/N]: N >; >; Answer YES if you want the INTRODUCTORY files used with the manual >; 'INTRODuction to RSX-11M'. This manual includes a full interactive >; terminal session. These files are used with that session. See the >; section on help files in the Post-System-Generation Guidelines SAMPLE GENERATION OF HELP FILES Page 13-2 >; Chapter of the RSX-11M System Generation and Installation Guide for >; more information. >; >* Do you want the INTRODUCTORY FILES? [Y/N]: N >; >; The following options have been selected: >; >; FULL HELP SUPPORT FOR MCR >; >; The appropriate files will now be extracted from the >; HELP Universal Library. >; >LBR MCRFULL.CMD=HELP.ULB/EX:MCRFUL >; >; This file extracts all the files that are necessary when full MCR >; help is chosen. >; >LBR HELPF.HLP=HELP.ULB/EX:HELPF >LBR MCR.HLP=HELP.ULB/EX:MCR >LBR MCRACT.HLP=HELP.ULB/EX:ACT >LBR MCRALT.HLP=HELP.ULB/EX:ALT >LBR MCRASN.HLP=HELP.ULB/EX:ASN >LBR MCRATL.HLP=HELP.ULB/EX:ATL >LBR MCRBRO.HLP=HELP.ULB/EX:BRO >LBR MCRCLI.HLP=HELP.ULB/EX:CLI >LBR MCRFLA.HLP=HELP.ULB/EX:FLA >LBR MCRGENRL.HLP=HELP.ULB/EX:GENRL >LBR MCRHELO.HLP=HELP.ULB/EX:HELO >LBR MCRHELP.HLP=HELP.ULB/EX:MHELP >LBR MCRHOM.HLP=HELP.ULB/EX:HOM >LBR MCRINI.HLP=HELP.ULB/EX:INI >LBR MCRINS.HLP=HELP.ULB/EX:INS >LBR MCRLOA.HLP=HELP.ULB/EX:LOA >LBR MCRLOGIN.HLP=HELP.ULB/EX:MLOGIN >LBR MCRMOU.HLP=HELP.ULB/EX:MOU >LBR MCROPE.HLP=HELP.ULB/EX:OPE >LBR MCRRUN.HLP=HELP.ULB/EX:MRUN >LBR MCRSAV.HLP=HELP.ULB/EX:SAV >LBR MCRSET.HLP=HELP.ULB/EX:SET >LBR MCRTAS.HLP=HELP.ULB/EX:TAS >LBR MCRUFD.HLP=HELP.ULB/EX:UFD >LBR DCL.HLP=HELP.ULB/EX:DCL2 >LBR UTIL.CMD=HELP.ULB/EX:UTIL >; >; This file contains commands to extract all the utility files >; from HELP.ULB. These files are extracted if any form of HELP >; is requested (i.e. full MCR or DCL, or brief MCR or DCL). >; >LBR ASCII.HLP=HELP.ULB/EX:ASCII >LBR BAD.HLP=HELP.ULB/EX:BAD >LBR BRU.HLP=HELP.ULB/EX:BRU >LBR CDA.HLP=HELP.ULB/EX:CDA >LBR CMP.HLP=HELP.ULB/EX:CMP >LBR COT.HLP=HELP.ULB/EX:COT SAMPLE GENERATION OF HELP FILES Page 13-3 >LBR DMP.HLP=HELP.ULB/EX:DMP >LBR DSC.HLP=HELP.ULB/EX:DSC >LBR EDI.HLP=HELP.ULB/EX:EDI >LBR EDTHELP.HLP=HELP.ULB/EX:EDTHLP >LBR ERROR.HLP=HELP.ULB/EX:ERROR >LBR EXECUTIVE.HLP=HELP.ULB/EX:EXEC >LBR FCS.HLP=HELP.ULB/EX:FCS >LBR FLX.HLP=HELP.ULB/EX:FLX >LBR FMT.HLP=HELP.ULB/EX:FMT >LBR ICP.HLP=HELP.ULB/EX:ICP >LBR IOX.HLP=HELP.ULB/EX:IOX >LBR LBR.HLP=HELP.ULB/EX:LBR >LBR MAG.HLP=HELP.ULB/EX:MAG >LBR ODT.HLP=HELP.ULB/EX:ODT >LBR PAT.HLP=HELP.ULB/EX:PAT >LBR PIP.HLP=HELP.ULB/EX:PIP >LBR PMD.HLP=HELP.ULB/EX:PMD >LBR SLP.HLP=HELP.ULB/EX:SLP >LBR SYSGEN.HLP=HELP.ULB/EX:SYSGEN >LBR SYSLIB.HLP=HELP.ULB/EX:SYSLIB >LBR TKB.HLP=HELP.ULB/EX:TKB >LBR TDX.HLP=HELP.ULB/EX:TDX >LBR TKBOPT.HLP=HELP.ULB/EX:TKBOPT >LBR TKTN.HLP=HELP.ULB/EX:TKTN >LBR VFY.HLP=HELP.ULB/EX:VFY >LBR VMR.HLP=HELP.ULB/EX:VMR >LBR ZAP.HLP=HELP.ULB/EX:ZAP >LBR RMS.HLP=HELP.ULB/EX:RMS >LBR RMSBCK.HLP=HELP.ULB/EX:RMSBCK >LBR RMSCNV.HLP=HELP.ULB/EX:RMSCNV >LBR RMSDEF.HLP=HELP.ULB/EX:RMSDEF >LBR RMSDES.HLP=HELP.ULB/EX:RMSDES >LBR RMSDSP.HLP=HELP.ULB/EX:RMSDSP >LBR RMSIFL.HLP=HELP.ULB/EX:RMSIFL >LBR RMSRST.HLP=HELP.ULB/EX:RMSRST >LBR MCRUTIL.CMD=HELP.ULB/EX:MCRUTL >; >; This file extracts all the files required when either MCR brief >; or full help was chosen. >; >LBR BAS.HLP=HELP.ULB/EX:BAS >LBR MCRCORAL.HLP=HELP.ULB/EX:MCORAL >LBR MCREDT.HLP=HELP.ULB/EX:MCREDT >LBR MCRFORT.HLP=HELP.ULB/EX:MFORT >LBR MCRMAC.HLP=HELP.ULB/EX:MCRMAC >LBR MCRPRINT.HLP=HELP.ULB/EX:MPRINT >LBR MCRQUE.HLP=HELP.ULB/EX:MCRQUE >LBR MCRPASCAL.HLP=HELP.ULB/EX:MPASCL >@ > dmo mdb6: > bye CHAPTER 14 SAMPLE ERROR LOGGING LIBRARY TUNING The following output is a result of tuning the Error Logging library ERRLOG.ULB. The tuning procedure rebuilds the library to contain only the entered devices. $ @RSX_FACTORY$COMMANDS:PRETUNE > @tune >; >; This command procedure is used to tune the Error Log Control file for >; your system configuration. The procedure prompts for the location of >; the master control file (the shipped file), the CPU type, and the >; error logging devices available on your system. It then creates a new >; version of the control file that contains only the required support. >; The original control file is left unchanged. >; >; All files are created in your default directory on the default >; device. When cleaning up, all files with the extension of .ICF as >; well as TEMPTUNE0.TMP;* and TEMPTUNE1.TMP;* are deleted. >; >* Continue? [Y/N]: y >; >* Location of master file [D: LB:[1,6]ERRLOG.ULB] [S]: >; >; Now enter the CPU type. Hit the escape key for a list of legal >; CPU types. >; >* Enter CPU type [S]: 11/50 >; >; Now enter the devices in your configuration separated by commas. >; Terminate by entering a period. Hit the escape key for a list of >; acceptable device names. >; >* Enter device name(s) [S]: rl02,rk05,rx02,rx01,tu16,tu10. >; >; Extract the files from the master library. >; >LBR @TEMPTUNE0.TMP >; SAMPLE ERROR LOGGING LIBRARY TUNING Page 14-2 >; Build the new library. Note that you may see messages like "Module >; "XYZZY" replaced" if you have selected more than one device having >; the same mnemonic. For example, selecting RK06 and RK07 support will >; produce this message. This type of message can be ignored. >; >LBR @TEMPTUNE1.TMP >; >; Now clean up. >; >LBR TEMPLIB.ULB/CO=TEMPLIB.ULB >PIP TEMPLIB.ULB/PU >PIP TEMPLIB.ULB/TR >PIP ERRLOG.ULB/RE/NV=TEMPLIB.ULB >PIP *.ICF;*,TEMPTUNE0.TMP;*,TEMPTUNE1.TMP;*/DE >; >; Finished. >; >@ > pur > del tune.cmd;0 > bye CHAPTER 15 SYSGEN ETC. AFTER RSX V4.2 In the following discussion, the term 'RSX sysgen procedure' is meant to include sysgen, update, layered products and Fermi/DECUS Additions procedures. The RSX sysgen command file structure is general enough to allow minor changes in the RSX sysgen procedure (in versions of RSX greated than V4.2) to take place out side of the command procedures themselves. This may involve writing new command procedures, restructuring the order in which the command files are executed or adding several commands in between running the command files. It is however possible that a large change will be made to the RSX sysgen procedure that will require alterations to the command procedures. The following sections briefly discuss three types of alterations that may occur. This chapter should be viewed as helpful hints to update the command procedures to work with new versions of RSX. In no way does this chapter list the changes that will occur, or all of the possible changes. 15.1 Parameter Change Many of the constants used in the command procedures can be altered by passing the new value as a parameter. See the sections on the individual command files to see which procedures accept parameters. 15.2 Minor Constant Change Some of the constants in the command procedures can not be altered through parameter values. These constants are listed below along with the command procedures in which they appear. o Names of the virtual disks. ASSOC_SYSGEN ASSOC_UPDATE BISON_BACKUP SYSGEN ETC. AFTER RSX V4.2 Page 15-2 BRU_MD_DISKS_TO_TAPE BRU_TAPE_TO_MD_DISKS CREATE_RSX_MD_DISKS o Both DEC distributed sources for DLSYS and RSXBAS are copied to the RSXM38 virtual disk. BRU_TAPE_TO_MD_DISKS o The size and geometry of the virtual disk is the same as an RL01. ASSOC_SYSGEN ASSOC_UPDATE CREATE_RSX_MD_DISKS o The layered products update disk gets the DEC distributed sources for DLKIT copied to it automatically. BRU_UPDATES_TO_DISK o The number of virtual disks in use are 7 (MDB0, MDB2-7 for updates and MDB1-7 for sysgens). ASSOC_SYSGEN ASSOC_UPDATE BISON_BACKUP BRU_MD_DISKS_TO_TAPE BRU_TAPE_TO_MD_DISKS DISASSOCIATE CREATE_RSX_MD_DISKS 15.3 Major Flow Change If the flow of the sysgen process undergoes a large change, the flow of the command procedures themselves will also have to be changed. When doing this use the diagrams supplied with chapter 3 for assistance. SYSGEN ETC. AFTER RSX V4.2 Page 15-3 15.4 Additions Change The ADDITIONS command file contains explicit reference to many of the versions of files that were most current at the time the procedure was written. These versions will undoubtedly change in the future, and should then be changed in the command procedure. The versions that are explicitly mentioned are listed below. o Version of RSX DUA0:[RSX11MSYS.RSX11M.RSX11M_V4_2C.EXCPRV.] DUA0:[RSX11MSYS.RSX11M.RSX11M_V4_2C.PRVBLD.] DUA0:[RSX11MSYS.RSX11M.RSX11M_V4_2C.MCRSRC.] DUA0:[RSX11MSYS.RSX11M.RSX11M_V4_2C.HLPDCL.] o Version of TECO DUA0:[RSX11MSYS.DECUS_ADD.TECO_V36.TASK] o Version of SRD DUA0:[RSX11MSYS.DECUS_ADD.SRD_V6_6.TASK] DUA0:[RSX11MSYS.DECUS_ADD.SRD_V6_6.HELP] o Version of Multi Utils DUA0:[RSX11MSYS.FERMI_ADD.MULTI_UTIL_V3_0.TASK] o Version of RMDLSI DUA0:[RSX11MSYS.FERMI_ADD.RMDLSI_V2_0.RSXV42C] o Version of Sys Mgr Area DUA0:[RSX11MSYS.FERMI_ADD.SYS_MGR.RSXV42C] o Version of Drivers DUA0:[RSX11MSYS.FERMI_ADD.DRIVERS_V1_0.RSXV41A] DUA0:[RSX11MSYS.FERMI_ADD.DRIVERS_V1_0.RSXV42C] APPENDIX A ANSWER SHEET FOR PREPGEN The following questions are those asked during an RSX prepgen. Questions with no given answers are not asked and are only included for completeness. The answer '' means use the given default. PHASE I SETUP 1 Autoconfigure the host system hardware? [Y/N] : N 2 Do you want to override Autoconfigure results? [Y/N] : 3 Do you want to inhibit execution of MCR commands (PREPGEN)? [Y/N] : Y 3A Do you want to create the assembly and build files on the SY: device? [Y/N] : Y 4 Have you made a copy of the distribution kit? [Y/N] : Y 5 Are you generating an unmapped system? [Y/N] : N 6 Use an input saved answer file? [Y/N] : N 7 Name of input saved answer file [D: ] : 8 Do you want a standard function system? [Y/N] : N 9 Name of output saved answer file [D: ] : 10 Use saved host configuration? [Y/N] : N 11 Use saved peripheral configuration? [Y/N] : N 12 Skip End-of-Section (EOS) breakpoints? [Y/N] : N 13 Skip End-of-Execution (EOX) breakpoints? [Y/N] : 14 Clean up files from previous GENs? [Y/N] : N 15 Chain to Phase II after Phase I completes? [Y/N] : Y 16 Enter device for EXCPRV disk when it is ready (dduu:) [D: DL1:][S] : DL12: 17 Enter device for PRVBLD disk when it is ready (dduu:) [D: DL2:][S] : DL13: TARGET CONFIG 1 Processor Type [D: 11/34] : 11/50 2 Does processor have a switch register? [Y/N D:N] : Y 3 Memory size (in K-word blocks) [D R:16.-124. D:64.] : 124. 4 Include support for K-series devices? [Y/N D:N] : N 5 Extended arithmetic element (KE11-A/B EAE) present? [Y/N D:N] : N 6 Floating point processor (FP11) present? [Y/N D:N] : Y 7 Floating instruction set (FIS) present? [Y/N D:N] : N 8 Extended instruction set (EIS) present? [Y/N D:N] : Y 9 If using KW11-P as system clock: number of ints/sec. [D R:0-1000 D:0] : 0 10 Line Frequency: A-60Hz B-50Hz [D: A] [S] : A 11 KW11-Y Watchdog timer support? [Y/N D:N] : N 12 Memory parity support? [Y/N D:N] : N 13 Cache memory? [Y/N D:N] : N 14 Highest interrupt vector [O R:0-774 D:0] : 774 15 Devices [S] : NL,CO,LP,DL,DK,DX,DY,MM,MT,YL=4,YZ HOST ANSWER SHEET FOR PREPGEN Page A-2 CONFIG 1 Is a line printer available? [Y/N] : Y 2 Spool assembly listings and Executive and driver maps? [Y/N] : N 3 Does the listing/map device have at least 120 columns? [Y/N] : Y 4 Assembly listing file device (ddu:) [D: NL:] : NL: 5 Map device for Executive and device drivers (ddu:) [D: ] : EXEC OPTIONS 1 Include support for DBMS-11? [Y/N] : N 2 Files-11 ACP? [Y/N] : Y 3 Bucket locking (file sharing) and placement control? [Y/N] : Y 4 Non-resident tasks (task loader)? [Y/N] : Y 5 Loadable task loader? [Y/N] : Y 6 Executive Common? [Y/N] : Y 7 Memory management (PLAS) directives? [Y/N] : Y 8 Send/Receive By Reference directives? [Y/N] : Y 9 Get Mapping Context directive? [Y/N] : Y 10 Address checking? [Y/N] : Y 11 I/O rundown? [Y/N] : Y 12 Multiuser protection? [Y/N] : N 13 ANSI Magtape ACP? [Y/N] : Y 14 Do you want on-line formatting (FMT) or diagnostic QIOs? [Y/N] : Y 15 Loadable device drivers? [Y/N] : Y 16 Should the default for all applicable drivers be loadable? [Y/N] : Y 17 Include Support for Asynchronous System Traps (AST)? [Y/N] : Y 18 Include Support for Cancel Selective Marktime? [Y/N] : Y 19 Task termination and device not ready messages (TKTN)? [Y/N] : Y 20 Power fail recovery? [Y/N] : Y 21 Install, request, and remove on exit? [Y/N] : Y 22 Large (20K) Executive? [Y/N] : Y 23 Logical device assignment? [Y/N] : Y 24 Include support for error logging? [Y/N] : Y 25 Do you intend to include a user-written driver? [Y/N] : Y 26 Include routine $GTWRD? [Y/N] : Y 27 Include routine $PTWRD? [Y/N] : Y 28 Disk writecheck? [Y/N] : Y 29 Software write-lock support? [Y/N] : Y 30 Executive Debugging Tool (XDT)? [Y/N] : Y 31 Rotating pattern in data lights? [Y/N] : Y 32 Include support for communications products (such as DECnet)? [Y/N] : Y 32A Include Network Command Terminal support? [Y/N] : Y 33 System-controlled partitions? [Y/N] : Y 34 Include support for the Shuffler? [Y/N] : Y 35 Queue manager and queued print spooler? [Y/N] : N 36 Group global event flags? [Y/N] : Y 37 Enter code for system directives - % 38 Number of pre-allocated QIO packets [D R:0.-15. D:5.] : 15. 39 Size of data transfer vector in words [D R:0.-33. D:33] : 33. 40 Round-robin scheduling interval in ticks [D R:0.-1000. D:5] : 5. 41 Highest priority class for consideration [D R:1.-249. D:150] : 150. 42 Lowest priority class for consideration [D R:1.-x. D:1.] : 1. 43 Executive level disk swapping interval [D R:0-5000. D:y] : 44 Swapping priority [D R:1.-20. D:5.] : 5. 45 Size of Dynamic Storage Region (Pool) in words [D R:256.-16384. D:1024.] : 46 Seconds between printer not ready messages [D R:0.-255. D:30.] : 120. 47 Seconds between card reader not ready messages [D R:0.-255. D:30.] : 48 System crash register and stack dump device CSR [O R:0-177700 D:177564] : ANSWER SHEET FOR PREPGEN Page A-3 49 Checkpointing [Y/N] : Y 50 Checkpointing with system checkpoint file [Y/N] : Y 51 Crash dump analysis: A-PANIC B-Crash Dump Analysis (CDA) C-None [D: B] B 52 CDA output notification device CSR [O R:160000-177700 D:177564] : 53 Enter CDA memory dump device mnemonic (ddu:) [S R:3-4] : DL3: 54 Enter CDA memory dump device CSR [O R:160000-177700 D:174500] : 55 Enter PANIC memory dump device CSR [O R:160000-177700 D:177564] : 56 RT-11 Emulation Support? [Y/N] : N TERM DRIVER 1 Terminal driver desired (A/B/C/D, * prints table) - C 2 Unsolicited input timeout value in seconds [D R:0.-255. D:120.] : 0. 3 Pass form feeds directly to the terminal? [Y/N] : 4 Automatic carriage return/line feed? [Y/N] : 5 Task checkpointing during terminal input? [Y/N] : 6 Unsolicited input character AST? [Y/N] : Y 7 Write with CTRL/O cancellation? [Y/N] : Y 8 Breakthrough write? [Y/N] : Y 9 CTRL/R (retype)? [Y/N] : Y 10 Escape sequence handling? [Y/N] : Y 11 Get multiple characteristics? [Y/N] : Y 12 Set multiple characteristics? [Y/N] : Y 13 Get terminal driver options? [Y/N] : Y 14 Hold-screen mode? [Y/N] : Y 15 Transparent read/write? [Y/N] : Y 16 Settable case conversion for input? [Y/N] : 17 Read after prompt? [Y/N] : Y 18 Read with no echo? [Y/N] : Y 19 Read with special terminator? [Y/N] : Y 20 CRT rubout support? [Y/N] : Y 21 Terminal-host synchronization? [Y/N] : Y 22 User terminal input buffering? [Y/N] : Y 23 Variable length terminal input buffering? [Y/N] : Y 24 LA30P support? [Y/N] : Y 25 Hardware unrecoverable input error notification? [Y/N] : Y 26 Device independent cursor positioning? [Y/N] : Y SYSTEM OPTION 1 Include ANSLIB.OLB to support big-buffering? [Y/N] : Y 2 Build library of ISA FORTRAN industrial/lab routines? [Y/N] : 2A Include support for the IP11 industrial I/O Subsystem? [Y/N] : N 2B Include support for IP11 powerfail? [Y/N] : 3 Build the PLAS resident FCS? [Y/N] : N 4 Code for FCP (A/B/C/D/E, * prints table) [D: ] : C 5 Build Post Mortem Dump (PMD)? [Y/N] : Y 6 Build the Resource Monitoring Display task (RMD)? [Y/N] : Y 7 Build the non-queue manager print spooler (PRT)? [Y/N] : Y 8 Do you want DIGITAL Command Language (DCL)? [Y/N] : N 9 Enter the number of user-written CLIs [D R:<0-MAX> D:0] : 0 10 Do you want pool monitoring and low pool recovery (PMT)? [Y/N] : Y 11 What name would you like to give your system? [D: ] : RSX11M 12 Do you want SPM-11 support? [Y/N] : N PERIPH OPTION Enter [L/R,] parameter1, parameter2,...parametern for: AD controller 0 [D:176770] AF controller 0 [D:134,172570] AR controller 0 [D:,170400,,,,,170420] ANSWER SHEET FOR PREPGEN Page A-4 CR controller 0 [D:230,177160] CT controller 0 [D:260,177500] DB controller 0 [D:254,176700,,0,O] DB contr 0 unit 0. is an RP04/RP05/RP06 [D:RP06] DD controller 0 [D:300,176500] DF controller 0 [D:204,177460] DK controller 0 [D:220,177404] ,,4 DL controller 0 [D:160,174400] ,,4 DL contr 0 unit 0. is an RL01/RL02 [D:RL01] (2 RL02's & 2 RL01's) DM controller 0 [D:210,177440,,0] DM contr 0 unit 0. is an RK06/RK07 [D:RK06] DP controller 0 [D:254,176714] DP contr 0 unit 0. is an RP02/RP03 [D:RP03] DR controller 0 [D:254,176700,,0,O] DR contr 0 unit 0. is an RM02/03/05/80/RP07 [D:RM03] DS controller 0 [D:204,172040,,0] DS contr 0 unit 0. is an RS03/RS04 [D:RS04] DT controller 0 [D:214,177342] DU controller 0 [D:154,172150] DX controller 0 [D:264,177170] ,,2 DY controller 0 [D:264,177170] ,,2 (double dens ok) EM controller 0 [D: ,176400] LA controller 0 [D:300,170460,0] LP controller 0 [D:200,177514,LA180,0,300,160130] ,,LP11-W LS controller 0 [D:,170400,,,0,0,0,NO] MM controller 0 [D:224,172440] 120,,2 (formatter : 0) MM controller 0 unit 0 formatter [D R:0-7 D:0] MS controller 0 [D:224,172522] MT controller 0 [D:224,172522] ,,2 MU controller 0 [D:260,174500] PP controller 0 [D:74,177554] PR controller 0 [D:70,177550] UD controller 0 [D:234,171776] XB controller 0 [D:124,172414] XE controller 0 [D:,,0] XL controller 0 [D:,,H] XM controller 0 XP controller 0 [D:,174770,H] XQ controller 0 [D:,,H,E,C] XU controller 0 [D:,,F] XW controller 0 [D:,,H] YH controller 0 [D:,,,300,0,0] YJ controller 0 / 310,175610 YL controller 0 [D:60,177560, NO] 1st one ok then -> | 320,175620 YV controller 0 [,,,] \ 330,175630 YZ controller 0 [D:,,,0] 430,160010,7,0 1 Expanded comments for ICS/ICR questions? N 2 Do you want task activation from unsolicited interrupts? N 3 IC controller 0 vector address : N 4 CSR address : N 5 Is it an ICR-11? N 6 Number of A/D converter modules in this ICS/ICR : N 7 A/D converter module number : N 8 Number of expansion multiplexers : N 9 () module number N ANSWER SHEET FOR PREPGEN Page A-5 10 Restore module staus on power and error recovery? N 11 How many line errors are acceptable per second? N 12 Number of D/A converter modules in this ICS/ICR : N 13 Number of single-shot output modules in this ICS/ICR : N 14 Number of bi-stable output modules in this ICS/ICR : N 15 Number of digital sense modules in this ICS/ICR : N 16 Number of digital interrupt modules in this ICS/ICR : N 17 Number of I/O counter modules in this ICS/ICR : N 18 Expanded comments for DSS/DRS questions? N 19 Number of DRS-11 modules : N 20 Restore module status on power and error recovery? N 21 DRS-11 CSR address : N 22 DRS-11 vector address : N 23 Number of DSS-11 digital input modules : N 24 DSS-11 CSR address : N 25 DSS-11 vector address : N 26 Task activation from unsolicited interrupts? N * PHASE II SETUP 1 In what UIC is SGNPARM.CMD if not ? [S] : 2 Do you want to inhibit execution of MCR commands (PREPGEN)? [Y/N] : 2A Do you want to create the build files on the SY: device? [Y/N D:Y] : N 3 Use an input saved answer file? [Y/N] : 4 Name of input saved answer file [D: ] : 5 Name of output saved answer file [D: ] : 6 Skip end-of-execution (EOX) breakpoints? [Y/N] : 7 Enter device for PRVBLD disk when it is ready (ddu:) [D: DL1:] [S] : EXEC BUILD 1 List Executive map? [Y/N] : N 2 Edit Executive files? [Y/N] : N DRIVER BUILD 1 In what UIC is SGNPARM.CMD if not ? [S] : 2 Enter device for