Everything You Always Wanted To Know About Sysgen But Were Afraid To Ask 1.0 Introduction It is assumed that the reader is at least somewhat fam- iliar with the RSX system and DEC operating systems in gen- eral. This document will give you my perspective on per- forming sysgens and may be of use in helping you bypass some problems that inevitably occur during sysgen. Sysgen is a word that has struck fear into the heart of many a computer user. It means system generation, which is a process of configuring the system software (operating system) to a par- ticular hardware and software environment. This document will attempt to remove the mysticism from sysgen and hope- fully will endow the reader with enough knowledge and confi- dence to be able to perform a sysgen. The system which will be used for purpose of example is a PDP-11/70 with 320K words. Your job, should you decide to accept it, will be to perform an RSX-11M sysgen from scratch, including the appli- cation of patches, the rebuilding of user written drivers and building various system utility programs. The remainder of this document is divided into the fol- lowing sections: * Pre-sysgen * Autopatch * Sysgen * Drivers and privileged tasks * Creating the target disk A question often asked is "Why do I have to do a sysgen?". The answer is simple: Assuming you have a run- ning system (i.e., they didn't just wheel in your new com- puter) the only reason for doing a sysgen is to make changes to the executive program. These changes may be necessitated by procuring new hardware, fixing bugs in RSX (i.e., apply- ing patches), or adding support for new system services. A sysgen does not have to be performed periodically (RSX doesn't wear out!). Before we begin there are a few points of terminology that should be discussed. Privileged tasks are programs which are mapped to the executive (i.e., RSX11M.SYS) and must be rebuilt after each sysgen because symbolic locations which these tasks refer- ence may change physical location within the executive each time it is built. User written drivers must be rebuilt for the same reason. Anything else need not be rebuilt and can be copied over asis and used from one system to the next! The logical assignments SY: and LB: are normally di- rected to the system disk (DP0:) for most user's work. By design SY: was intended to be the default disk upon which most activity takes place, LB: is the library device, that Everything You Always Wanted To Know About Sysgen Page 2 But Were Afraid To Ask is, the device where the programs reside. For the purpose of the sysgen SY: and LB: frequently have to reassigned to other than the default assignments. If you are not familiar with the ASN subcommand of MCR please take the time to get intimately familiar with it. When you log onto the system you find yourself in your logon directory (e.g., [237,34] on your logon device (as- sumed to be DP0:). Users with logon directories with group numbers less than or equal to 7 are privileged, the rest are nonprivileged. For the purpose of the sysgen you must be privileged therefore you should be logged into a privileged account (e.g., [1,100]). Your working directory may be changed via the SET /UIC= command (or UIC command of CCL). Though you change to a nonprivileged directory a privileged user still retains privilege. There are sysgens and there are SYSGENS. Not all the steps in this document need to be followed each time you must do a sysgen. For example, if your autopatch level doesn't change then you can use the same patched distribu- tion disk for subsequent sysgens. Use common sense, but when in doubt, start from scratch. Everything You Always Wanted To Know About Sysgen Page 3 But Were Afraid To Ask 2.0 Pre-sysgen Two things to remember before performing a sysgen are to organize what you are going to do and to have enough free space to work with. It is practically impossible to perform a sucessful sysgen on a system without large disks, that is, any disk bigger than an RL02. For the purpose of example we have 3 RP03 drives (40M bytes each). The current running system is on DP0: and our sysgen will be performed on DP1: or DP2:. Note, only for the final phase of our procedure (creating the target disk) will we require the use of both DP1: and DP2:. Most of the sysgen activity can take place online, that is, with other users working on the system. You should have 3 disk packs free for use in the sys- gen, though it is possible to get by with less. The disk which is to be the target system disk should have few (if any) bad blocks. Copy the RSX11M distribution kit to a pack, label it "SYSGEN" and date it. If you have mag tape distribution (and have not made a BRU copy of it) you must use DSC to create your distribution disk, otherwise use BRU. Copy your utility distribution software to another pack and label it "UTIL". Note, this software may consist of site specific software, such as user written drivers, and other software that must be rebuilt each sysgen, such as Jim Down- ward's KMS accounting system. A plain "vanilla" RSX system will not have this disk, however, the following procedures rely on a site having implemented several DECUS utility pro- grams. So if you have a "vanilla" system you will not be able to do the sysgen as easily as I describe it. 3.0 Autopatch DEC Autopatch service provides a cumulative distribu- tion of patches to RSX11M in machine readable form. A new autopatch comes out every 4 months (or so) and includes all patches which appeared in the Software Dispatch. The auto- patches are cumulative and must be applied to the virgin RSX distribution. The autopatch consists of source and object patches and command files to automatically do the operation. In addition to patches for RSX11M executive, drivers, privi- leged and utility tasks there are patches to the layered products (such as FORTRAN). In this discussion we will not deal with patching the layered products (it's much easier than doing the RSX patches). It is not uncommon for auto- patch to introduce some bugs so it is best to wait a few months after the release of autopatch to see if any bugs surface (look in the software dispatch or talk to some other users). For our example we will assume that we have a mag tape Everything You Always Wanted To Know About Sysgen Page 4 But Were Afraid To Ask autopatch distribution. Though it is easier to run the au- topatch from tape we will first transfer the tape to disk because it is easier to get other patches (ie. for the lay- ered products) from the disk. If you don't have virtual disks implemented at your site (tsk tsk) then you may use a physical disk of at least 10,000 blocks. On the SYSGEN disk create a virtual disk of 10000. blocks. Using the FFL pro- gram, copy the tape (which is in DOS format) to the virtual disk. The necessary commands are shown below: UIC [200,200] !Change UIC MOU DP2:SYSGEN !Mount sysgen disk AVD VD:=DP2:AUTPATCH/CR:10000. !Assign a virtual disk ALL VD: !Allocate the virtual disk INI VD:AUTPATCH !Initialize the disk MOU VD:AUTPATCH !Mount the disk FFL VD:/UI=MM:[*,*]*.* !Copy the tape to disk TYP VD:AUTOPATCH.DOC !Type out document PIP DP2:=VD:AUTOPATCH.CMD !Copy command file to sysgen disk ASN VD:=DM: !Assign DM: to fool AUTOPATCH.CMD At this point you may follow the directions in the AU- TOPATCH document. You should respond DM: when the command file asks what disk the autopatch distribution is on. If you have DM: type disks you may use another device (which you don't have) like DB:. This subterfuge is necessary be- cause AUTOPATCH.CMD has hard coded names of "legal" auto- patch distribution media and VD: or SY: isn't considered valid. The autopatch should proceed without problem. Cleanup is as follows: DMO VD: !Dismount the virtual disk DVD VD: !Deassign it DEA VD: !Deallocate it ASN =DM: !Remove assignment At this point you should back up the sysgen disk with BRU (e.g., BRU /MOU/DEN:1600 DP2: MM: ). This backup copy will constitute your first fallback position should some- thing go wrong in a later phase of sysgen. Everything You Always Wanted To Know About Sysgen Page 5 But Were Afraid To Ask 4.0 Sysgen The sysgen requires the execution of three command files (SYSGEN.CMD, SYSGEN2.CMD, SYSGEN3.CMD). The first command file collects information about the specific hardware and software features of your target system and as- sembles the executive and device drivers. SYSGEN2.CMD per- forms phase two of the sysgen which includes the taskbuild- ing of the executive, drivers, and privileged tasks. SYSGEN3.CMD performs the final phase of the sysgen and al- lows you to build the non-privileged utilities (such as PIP, BRU, etc.) and the user mode diagnostics. Once phase 3 has been performed, for a particular autopatch level, it need not be repeated. Phase 1 and 2 must be performed every time there is a change to the executive. Most installations run BIGMAC and BIGTKB with large task increments. If this is not the case be sure to remove and reinstall them with an increment of 50000. Failure to do this will greatly slow down your sysgen! Since you are doing the sysgen online you must assign the SYSGEN disk to be SY: and LB: (e.g., ASN DP2:=SY: etc.).If you have a saved answer file from a previous sysgen, you may edit it and rename it from SYSAVED.DAT to SYSAVED.CMD. SYSGEN.CMD will allow you to fill in any answers that are missing. Now you can proceed with the sysgen by typing @[200,200]SYSGEN . If this is a virgin sysgen you will have to answer all the questions, so be sure to go over the questions before you get to this step (you can't easily back up). Assuming Phase I succeeds you may proceed to Phase II. When Phase II com- pletes you may boot your new system just to be sure it works (first make sure all other users have logged off the sys- tem). Phase III should then be performed because frequently the utility tasks (such as BRU, TKB, or PIP) are patched by autopatch and must be rebuilt. Look in the autopatch docu- mentation to determine what nonprivileged tasks need to be rebuilt. At this point you should again backup the sysgen disk with BRU (e.g., BRU /MOU/DEN:1600 DP2: MM: ). This backup copy will constitute your second fallback position should something go wrong in a later phase of sysgen. In case the current sysgen is not for attaining a new patch level, this tape will already exist (having been saved from the last "autopatch" sysgen) and will be your starting point now. A word must be said about the virtues of FCS resident libraries. Lack of memory and lack of disk space are two of the most common problems with non 11/70 or 11/44 systems. A FCS resident library can dramatically help with either prob- lem. It has been estimated that if each DEC utility was built with FCSRES it would save about 500 blocks of disk space, allow more simultaneous users in memory before swap- ping starts and allow tasks to load faster. It is beyond the scope of this document to go into more detail so PLEASE Everything You Always Wanted To Know About Sysgen Page 6 But Were Afraid To Ask look into the stuff on FCSRES (including command files to rebuild most DEC utilities) in [344,*] on the Fall 79 (and subsequent) RSX SIG tapes from DECUS! Everything You Always Wanted To Know About Sysgen Page 7 But Were Afraid To Ask 5.0 Drivers and privileged tasks At this point you should assemble and taskbuild all user written drivers. Privileged tasks such as parts of the KMS accounting system must also be rebuilt. At our site there are several user written drivers in use. We have con- structed a command file to build each driver. This activity can take place online using the "old" system. In addition, we are using most of the KMS software enhancements. Since many of these tasks replace the DEC privileged utilities, they must be rebuilt also. There is a commandfile, KMSGEN.CMD, which does most of the work; however, we need to prepare the disk for the KMSGEN, so we created a file PREKMS.CMD . The procedure is as follows: 1. Log onto a privileged account. 2. Mount the SYSGEN and UTILITY disks and assign SY: to UTILITY and LB: to SYSGEN. 3. Run the command files to build the site specific privileged tasks (such as WHO and SETPRV) and user written drivers. 4. Execute PREKMS.CMD on the sysgen disk. 5. Change the assignment of SY: to the disk containing the KMS sources. 6. Execute KMSGEN.CMD The KMSGEN is prone to failure so don't get discour- aged. At this point you should backup the SYSGEN disk with BRU (e.g., BRU /MOU/DEN:1600 DP2: MM: ). This backup copy will constitute the final backup and will contain the new system. 6.0 Creating the target disk The target disk is the disk that you will actually use as your system disk. It is better to create a new disk than to use your old disk and copy the new files from SYSGEN to it for two reasons. One, it is always wise to have a readi- ly accessable (and immediatly usable) copy of your old sys- tem for several months following a sysgen, in case a serious bug is discovered in the new system. Second, by "construct- ing" the disk from scratch it is possible to position the files on the disk that will insure minimum seek time for frequently used files (such as TKB and syslib). The first step in creating a target disk is to run BAD on a pack and initialize it. We like to use a disk with no bad blocks for our system disk (this insures a minimum of fragmentation at disk initialization). The next step is to create all the UFDs needed (use a command file to do this!). The UFDs needed are the ones which are active (ie. are not Everything You Always Wanted To Know About Sysgen Page 8 But Were Afraid To Ask empty) on your current system disk. Next copy SYSLIB.OLB and BIGTKB.TSK to the target disk. We then use a command file to copy the privileged tasks, drivers, and executive built during sysgen to the target disk. Now comes the time to VMR the new system. You may have already sucessfully done this on the SYSGEN disk but it now needs to be done on the target disk because by using PIP to copy the tasks from one disk to another we no longer main- tain the same file IDs, therefore the tasks need to rein- stalled on the new disk. Again, use a command file (not SYSVMR.CMD) which contains site specific information; loadable drivers, privileged tasks, utility tasks, and ter- minal setups. We use a main command file (VMR.CMD) which call several other command files (e.g., DRIVER.CMD, UTIL.CMD, etc.) so that changes can be easily made. Don't forget to make a new copy of RSX11M.SYS from RSX11M.TSK be- fore you attempt the VMR. At this point copy over the user's accounts with a co- mand file that preserves creation date and file ownership! Next copy the nonexecutalbe system files such as command files, help files, etc. Finally copy the account file [0,0]RSX11.SYS from your current system disk to the new disk. Then get the users off the system, shut it down, then boot and save your new system disk. Before you allow any user activity, backup this disk, label it "virgin new system autopatch level ?" and date it. APPENDIX A Command Files The following command files are listed: PREKMS.CMD -Ready a virgin system for the KMSGEN COPY.CMD -Copy the privileged and nonpriv tasks from the UTILITY disk to the TARGET disk COPYPRIV.CMD -Copy the privileged tasks from the SYSGEN disk to the TARGET disk COPYNPRIV.CMD -Copy the nonprivileged tasks from the SYSGEN disk to the TARGET disk VMR.CMD -Main VMR command file (sets up partitions and terminals) DRIV.CMD -VMR subfile to load drivers PRIV.CMD -VMR subfile to install privileged tasks NPRIV.CMD -VMR subfile to install nonprivileged tasks ; ; P R E K M S . C M D ; ; This file will make backup copies of all the RSX files needed for ; the KMSGEN. Note, the first version is used, THEREFORE any patches ; applied by autopatch will be ignored! ; ; Assign SY: to the SYSGEN disk before execution of this file! ; PIP [15,10]ACNT.VGN=[15,10]ACNT.MAC;1 PIP [15,10]BROAD.VGN=[15,10]BROAD.MAC;1 PIP [12,10]BYE.VGN=[12,10]BYE.MAC;1 PIP [12,10]HELLO.VGN=[12,10]HELLO.MAC;1 PIP [1,24]IND.VLB=[1,24]IND.OLB;1 PIP [12,10]INDERR.VGN=[12,10]INDERR.MAC;1 PIP [12,10]INDFIL.VGN=[12,10]INDFIL.MAC;1 PIP [12,10]INDIMP.VGN=[12,10]INDIMP.MAC;1 PIP [12,10]INDINX.VGN=[12,10]INDINX.MAC;1 PIP [12,10]INDOPN.VGN=[12,10]INDOPN.MAC;1 PIP [12,10]INDPDW.VGN=[12,10]INDPDW.MAC;1 PIP [12,10]INDROT.VGN=[12,10]INDROT.MAC;1 PIP [12,10]INDSU1.VGN=[12,10]INDSU1.MAC;1 PIP [12,10]INDSU2.VGN=[12,10]INDSU2.MAC;1 PIP [1,24]INS.VLB=[1,24]INS.OLB;1 PIP [12,10]INSFL.VGN =[12,10]INSFL.MAC;1 PIP [12,10]INSHD.VGN =[12,10]INSHD.MAC;1 PIP [12,10]INSPS.VGN =[12,10]INSPS.MAC;1 PIP [12,10]INSROT.VGN=[12,10]INSROT.MAC;1 PIP [1,24]MCR.VLB=[1,24]MCR.OLB;1 PIP [12,10]MCRDEF.VGN=[12,10]MCRDEF.MAC;1 PIP [12,10]MCRDIS.VGN=[12,10]MCRDIS.MAC;1 PIP [12,10]MGCML.VGN =[12,10]MGCML.MAC;1 PIP [12,10]SDSOV.VGN =[12,10]SDSOV.MAC;1 PIP [12,10]SDSOVFDT.VGN=[12,10]SDSOVFDT.MAC;1 PIP [12,10]SETOV.VGN =[12,10]SETOV.MAC;1 PIP [12,10]SETOVFDT.VGN=[12,10]SETOVFDT.MAC;1 PIP [200,200]SGNTT.VMD =[200,200]SGNTT.CMD;1 PIP [12,10]RPSOV.VGN =[12,10]RPSOV.MAC;1 PIP [12,10]SPROV.VGN =[12,10]SPROV.MAC;1 PIP [12,10]SPROVFDT.VGN=[12,10]SPROVFDT.MAC;1 PIP [11,10]SYSCM.VGN =[11,10]SYSCM.MAC;1 PIP [1,24]SYSROT.VBJ=[1,24]SYSROT.OBJ;1 PIP [11,10]TDSCH.VGN =[11,10]TDSCH.MAC;1 ;Proceed with the KMSGEN ; COPY.CMD ; ; This command file will copy system utility tasks from the source disk ; to the output disk ; ; Note: normally only the drivers and privileged tasks need be copied! ; .ENABLE SUBSTITUTION .ASKS DEVI Enter input device [S: SY:] .ASKS DEVO Enter target device [S: SY:] .; THIS STUFF GOES TO SYSUIC [1,54] (PRIVILEGED SYSTEM TASKS) .SETS OUT "[1,54]" .ASK SKIP Copy user written drivers .IFF SKIP .GOTO 1 .SETS UIC "[7,1]" PIP 'DEVO''OUT'='DEVI''UIC'FSDRV.TSK PIP 'DEVO''OUT'='DEVI''UIC'ZBDRV7.TSK PIP 'DEVO''OUT'='DEVI''UIC'ZMDRV.TSK PIP 'DEVO''OUT'='DEVI''UIC'FSDRV.STB PIP 'DEVO''OUT'='DEVI''UIC'ZBDRV7.STB PIP 'DEVO''OUT'='DEVI''UIC'ZMDRV.STB .ASK SKIP Copy virtual disk stuff .IFF SKIP .GOTO 2 .SETS UIC "[7,2]" PIP 'DEVO''OUT'='DEVI''UIC'AVD.TSK PIP 'DEVO''OUT'='DEVI''UIC'DVD.TSK PIP 'DEVO''OUT'='DEVI''UIC'VDDRV.TSK PIP 'DEVO''OUT'='DEVI''UIC'VDDRV.STB .ASK SKIP Copy FPEM & XDT .IFF SKIP .GOTO 3 .SETS UIC "[7,3]" PIP 'DEVO''OUT'='DEVI''UIC'FPEM .TSK PIP 'DEVO''OUT'='DEVI''UIC'XDT.TSK .ASK SKIP Copy WHO .IFF SKIP .GOTO 4 .SETS UIC "[7,12]" PIP 'DEVO''OUT'='DEVI''UIC'WHO.TSK .ASK SKIP Copy GAB RMC TRUNC WHEN SETPRV .IFF SKIP .GOTO 5 .SETS UIC "[7,5]" PIP 'DEVO''OUT'='DEVI''UIC'GAB.TSK PIP 'DEVO''OUT'='DEVI''UIC'RECEIV.TSK PIP 'DEVO''OUT'='DEVI''UIC'RMC.TSK PIP 'DEVO''OUT'='DEVI''UIC'TRUNC.TSK PIP 'DEVO''OUT'='DEVI''UIC'SETPRV .TSK PIP 'DEVO''OUT'='DEVI''UIC'WHEN .TSK .; THIS STUFF GOES TO LIBUIC [2,54] (NON PRIVILEGED SYSTEM TASKS) .SETS OUT "[2,54]" .ASK SKIP Copy EDT & KED .IFF SKIP .GOTO 6 .SETS UIC "[7,4]" PIP 'DEVO''OUT'='DEVI''UIC'EDT.TSK PIP 'DEVO''OUT'='DEVI''UIC'KED.TSK .ASK SKIP Copy SRD .IFF SKIP .GOTO 7 .SETS UIC "[7,10]" PIP 'DEVO''OUT'='DEVI''UIC'SRD.TSK .ASK SKIP Copy RNO .IFF SKIP .GOTO 8 .SETS UIC "[7,11]" PIP 'DEVO''OUT'='DEVI''UIC'RNO.TSK .ASK SKIP Copy TYPE .IFF SKIP .GOTO 9 .SETS UIC "[7,5]" PIP 'DEVO''OUT'='DEVI''UIC'TYPE.TSK .; THIS STUFF GOES TO THE GAMES UIC [200,200] .SETS OUT "[200,200]" .ASK SKIP Copy Dungeon & Adventure etc... .IFF SKIP .GOTO 10 .SETS UIC "[7,7]" PIP 'DEVO''OUT'='DEVI''UIC'*.* .10: ; COPYNPRIV.CMD ; ; This command file will copy utility tasks from the source disk ; to the output disk ; .ENABLE SUBSTITUTION .ASKS DEVI Enter input device [S: SY:] .ASKS DEVO Enter target device [S: SY:] .; ALL THIS STUFF GOES TO LIBUIC [2,54] (NON-PRIVILEGED SYSTEM TASKS) PIP 'DEVO'[2,54]/FO='DEVI'BIGTKB.NCP PIP 'DEVO'[2,54]/FO='DEVI'BAD.TSK PIP 'DEVO'[2,54]/FO='DEVI'BRU.TSK PIP 'DEVO'[2,54]/FO='DEVI'CDA.TSK PIP 'DEVO'[2,54]/FO='DEVI'COMP.TSK PIP 'DEVO'[2,54]/FO='DEVI'DSC.TSK PIP 'DEVO'[2,54]/FO='DEVI'EDI.TSK PIP 'DEVO'[2,54]/FO='DEVI'FLX.TSK PIP 'DEVO'[2,54]/FO='DEVI'FMT.TSK PIP 'DEVO'[2,54]/FO='DEVI'LBR.TSK PIP 'DEVO'[2,54]/FO='DEVI'PIP.TSK PIP 'DEVO'[2,54]/FO='DEVI'RP03.TSK PIP 'DEVO'[2,54]/FO='DEVI'VMR.TSK ; COPYPRIV.CMD ; ; This command file will copy system tasks from the source disk ; to the output disk ; .ENABLE SUBSTITUTION .ASKS DEVI Enter input device [S: SY:] .ASKS DEVO Enter target device [S: SY:] .; ALL THIS STUFF GOES TO SYSUIC [1,54] (PRIVILEGED SYSTEM TASKS) PIP 'DEVO'='DEVI'SYSVMR.CMD PIP 'DEVO'='DEVI'SYSVMR.NEW PIP 'DEVO'='DEVI'CODRV.STB PIP 'DEVO'='DEVI'DLDRV.STB PIP 'DEVO'='DEVI'DPDRV.STB PIP 'DEVO'='DEVI'F11MSGSTB.STB PIP 'DEVO'='DEVI'LPDRV.STB PIP 'DEVO'='DEVI'MMDRV.STB PIP 'DEVO'='DEVI'RSX11M.STB PIP 'DEVO'='DEVI'TTDRV.STB PIP 'DEVO'='DEVI'RSX11M.SYS PIP 'DEVO'='DEVI'ACNT.TSK PIP 'DEVO'='DEVI'ACS.TSK PIP 'DEVO'='DEVI'BOO.TSK PIP 'DEVO'='DEVI'BRO.TSK PIP 'DEVO'='DEVI'BYE.TSK PIP 'DEVO'='DEVI'CODRV.TSK PIP 'DEVO'='DEVI'COT.TSK PIP 'DEVO'='DEVI'DLDRV.TSK PIP 'DEVO'='DEVI'DMO.TSK PIP 'DEVO'='DEVI'DPDRV.TSK PIP 'DEVO'='DEVI'ERF.TSK PIP 'DEVO'='DEVI'ERL.TSK PIP 'DEVO'='DEVI'FCPRO2.TSK PIP 'DEVO'='DEVI'F11MSG.TSK PIP 'DEVO'='DEVI'HEL.TSK PIP 'DEVO'='DEVI'IND.TSK PIP 'DEVO'='DEVI'INI.TSK PIP 'DEVO'='DEVI'INS.TSK PIP 'DEVO'='DEVI'LOA.TSK PIP 'DEVO'='DEVI'LPDRV.TSK PIP 'DEVO'='DEVI'LPP.TSK PIP 'DEVO'='DEVI'MCRMU.TSK PIP 'DEVO'='DEVI'MMDRV.TSK PIP 'DEVO'='DEVI'MOU.TSK PIP 'DEVO'='DEVI'MTAACP.TSK PIP 'DEVO'='DEVI'QMG.TSK PIP 'DEVO'='DEVI'QMGCLI.TSK PIP 'DEVO'='DEVI'QMGPRT.TSK PIP 'DEVO'='DEVI'RMD.TSK PIP 'DEVO'='DEVI'RSX11M.TSK PIP 'DEVO'='DEVI'SAV.TSK PIP 'DEVO'='DEVI'SHF.TSK PIP 'DEVO'='DEVI'SHUTUP.TSK PIP 'DEVO'='DEVI'SYS.TSK PIP 'DEVO'='DEVI'TKN.TSK PIP 'DEVO'='DEVI'TTDRV.TSK PIP 'DEVO'='DEVI'UFD.TSK PIP 'DEVO'='DEVI'UNL.TSK ; VMR.CMD ; ; SET UP PARTITIONS AND LOAD DRIVERS ; SET /MAIN=CEXPAR:1120:60:COM SET /POOL=* SET /MAIN=TTPAR:*:400:TASK LOA TT: SET /MAIN=DRVPAR:*:*:SYS @DRIV SET /TOP=DRVPAR:-* SET /TOP=DRVPAR:+200 SET /MAIN=GCGLO:*:200:COM SET /MAIN=FCSRES:*:200:COM SET /MAIN=FORRES:*:400:COM SET /MAIN=FCPPAR:*:500:SYS SET /MAIN=SYSPAR:*:100:TASK SET /MAIN=GEN:*:*:SYS ; ; INSTALL COMMON BLOCKS AND LIBRARIES ; INS [1,1]FCSRES INS [1,1]GCGLO INS [1,1]FORRES ; ; INSTALL PRIVILEGED TASKS ; @PRIV ; ; INSTALL NON-PRIVILEGED TASKS ; @NONPRIV ; ; SET UP TERMINALS ; SET /LA120=TT0: SET /BUF=TT1:132. SET /VT05B=TT1: SET /BUF=TT1:80. SET /LOWER=TT1: SET /VT100=TT2: SET /LOWER=TT2: SET /BUF=TT2:80. SET /BUF=TT3:80. SET /LOWER=TT3: SET /BUF=VT0:132. SET /BUF=VT1:132. ; SET /UIC=[1,54]:TT0: ; SET /POOL ; ; DRIV.CMD ; ; THIS FILE LOADS THE LOADABLE DRIVERS LOA CO: LOA DL: LOA DP: ;LOA FS: ;LOA LP: LOA MM: LOA RD: LOA VD: LOA VT:/PAR=DRVPAR LOA ZB: ;LOA ZM: ; NONPRIV.CMD ; ; INSTALL NON-PRIVILEGED TASKS ; INS [2,54]BIGMAC/INC=50000/PAR=GEN INS [2,54]BIGTKB/INC=50000/PAR=GEN INS [2,54]COOKIE INS [2,54]CRF INS [2,54]EDI/INC=40000 INS [2,54]EDT/PRI=66./TASK=...EDT INS [2,54]FOR/INC=20000 INS [2,54]PIP/INC=10000 INS [2,54]RAT INS [2,54]RNO INS [2,54]SRD INS [2,54]TYPE/TASK=...TYP INS [2,54]UPDATE ; PRIV.CMD ; ; THIS FILE INSTALLS THE PRIVILEGED TASKS INS ACC ;INS ACCLOG ;INS ACNT INS ACS INS AVD INS BATCH ;INS BOO INS BRO INS BTQ INS BYE INS CCL INS COT ;INS CVL INS DMO INS DVD ;INS ERF INS ERL INS FCPRO2 INS F11MSG INS GAB INS HEL INS IND INS INI INS INS INS LOA INS LOGTSK ;INS LPP INS MAIL INS MAITSK INS MCRMU INS MOU INS MTAACP INS PIN INS QMG INS QMGCLI ;INS QMGPRT INS RECEIV ;INS RESET ;INS RMC INS RMD ;INS SAV INS SETPRV ;INS SHF ;INS SHUTUP INS SUBMIT INS SYS INS SYSLOG INS TKN ;INS TRUNC ;INS TSKLOG ;INS UFD INS UNL INS WHEN INS WHO ;INS XDT Table of Contents 1.0 Introduction . . . . . . . . . . . . . . . 1 2.0 Pre-sysgen . . . . . . . . . . . . . . . . 3 3.0 Autopatch . . . . . . . . . . . . . . . . . 3 4.0 Sysgen . . . . . . . . . . . . . . . . . . 5 5.0 Drivers and privileged tasks . . . . . . . 7 6.0 Creating the target disk . . . . . . . . . 7 A.0 Command Files . . . . . . . . . . . . . . . A-1