RSX-11M-PLUS Sysgen
This is a walkthrough guide for installing RSX-11M-PLUS v4.2 although with some interpretation it could be used for any of the 4.x releases. The preformatted text blocks show the console output and the bold blue text shows what was typed into the console. This particular guide shows installation on Simh, but the principal is much the same for a real PDP-11; It will just take a bit longer :)
Copy the installation kit to disk
The distribution tape contains a BRU saveset of the baseline system. BRU is the Backup/Restore Utility for RSX and is the equivalent of the VMS BACKUP program. Like VMS BACKUP there is a standalone version of BRU, which will be used here to copy the baseline system to disk. Attach the standalone BRU tape to the TS11 tape drive and boot from it. The tape used for this guide was BB-J083H-BC (RSX-11M-PLUS V4.2 MT:1600 BRUSYS STANDALONE COPY SYSTEM)
RSX-11M/RSX-11M-PLUS Standalone Copy System V04
MCR> ↵
RSX-11M/RSX-11M-PLUS Standalone Configuration and Disk Sizing Program
Valid switches are:
/CSR=nnnnnn to change the default device CSR
/VEC=nnn to change the default device vector
/FOR=n to change the default magtape formatter number
/DEV to list all default device CSR and vectors
>
Enter first device: MS0:
Enter second device: DB0:
Hit RETURN and enter date and time as 'TIM HH:MM MM/DD/YY'
>TIM 20:24 05/24/90
Now we check for any bad blocks on the target disks, which will create the bad block table. If using a simulator there should be no bad blocks of course but I would still recommend doing this because several RSX programs will complain if they can't find the bad block table.
>RUN BAD > BAD>DB0: BAD -- DB0: Total bad blocks= 0. BAD>^Z
Change the TS11 tape to the RSX distribution tape and run the Backup/Restore Utility. For this guide the tape used was BB-J081G-BC (RSX-11M-PLUS V4.2 BRU MT:1600 ID:RSX11MPBL58 DIST KIT)
>RUN BRU > BRU>/REW MS0: DB0: BRU - Starting Tape 1 on MS0: BRU - End of Tape 1 on MS0: BRU - Completed BRU>^Z >
Boot the baseline system
Halt the system and boot from the newly created system disk (device rp0 in Simh). The baseline system is an executive image that have a safe default configuration so that it can be booted on any model of PDP-11 (meeting the minimum requirement for RSX-11M-PLUS v4.x). There are also several device drivers configured in the baseline system to facilitate the system generation process.
RSX-11M-PLUS V4.2 BL58 1024.KW System:"Baseline" >RED DB:=SY: >RED DB:=LB: >RED DB:=SP: >MOU DB:"RSX11MPBL58" >@[2,54]BASTART.CMD >SET /CRASHDEV=MM0: SET -- Crash device MM0: has been successfully loaded >; >; >; RSX-11M-PLUS V4.2 Distribution Kit >; >; This is the baseline system of the RSX-11M-PLUS V4.2 >; distribution kit. This system contains an assortment of >; devices and may in fact be of some use on your target >; system. The main purpose of the baseline system, however, >; is to provide a working system environment which may be >; used to generate a custom-tailored operating system for >; your target hardware. We will now provide instructions >; to guide you through the startup procedure. >; >; >; It is important to specify the correct date and time. >; Use the format "DD-MMM-YY HH:MM". >; >* Please enter the date and time [S]: 24-MAY-90 20:25
Note that RSX-11M-PLUS versions prior to 4.6 are not Y2K compliant
>TIME 24-MAY-90 20:25 >; >; Now allocate checkpoint space for use by system utilities. >; >ACS SY:/BLKS=1024. >; >; The following information is necessary for this command file >; to correctly access the remainder of the distribution kit. >; >* Did you receive your RSX-11M-PLUS distribution kit on magnetic tape? [Y/N]: Y >; >; Please enter the name of the magnetic tape drive, which should >; still contain the distribution tape. The name is of the form: >; >; MM1: or >; MS0: etc... >; >* Which tape drive contains the distribution tape [S]: MS0: >; >; We will now set the CSR of the controller that will be >; used to bring in the remainder of the distribution kit to >; the standard value. If your controller is not at this address >; it will be necessary for you to manually configure the system >; by issuing the appropriate CON commands. Answer Yes to the >; manual configuration question to do this. If your controller >; is at the standard address, you do not have to do a manual >; configuration. >; >CON SET RHC CSR=160000 >CON SET MTA CSR=160000 >CON SET MSA CSR=172522 >CON SET MSA VEC=224 >CON SET MUA CSR=160000 >; >; We will now bring on line all devices which were generated into >; this baseline image and which exist in your hardware system. >; >; If there is hardware in your system occupying a control >; register address which conflicts with a standard DIGITAL >; register assignment, it is possible that the "CON ONLINE >; ALL" command might cause a system crash. This is because >; a DIGITAL device driver is attempting to manipulate foreign >; hardware or the CSR address assignments in your system are >; different from those assumed in this baseline configuration. >; On the first pass through this file please answer No to the >; following question. If such a mismatch exists and a crash >; does occur, rebootstrap the baseline system and answer Yes >; to this question. Instructions will then be provided to help >; circumvent the problem. >; >* Do you need to do manual configuration? [Y/N]: N >; >CON ONLINE ALL >; >; Prepare to bring in the remainder of the distribution kit >; >* Is your target system disk an RC25, RK07, or RD52? [Y/N]: N >; >; Since the files in the second backup set are not necessary to generate >; your system you may wish to skip the verify pass to save time. >; >* Do you want to verify the second backup set? [Y/N]: N >; >; We will now mount the tape in MS0: for access by BRU. >; >MOU MS0:/FOR/DENS=1600 >; >; Ensure that the BRU task is installed. >; >INS $BRU >; >; We will now load the remainder of the distribution kit. >; >TIME 20:25:40 24-MAY-90 >; >BRU /BAC:MPBL58SRC/UFD/NOINI/DENS:1600 MS0: SY: BRU - Starting Tape 1 on MS0: BRU - End of Tape 1 on MS0: BRU - Completed >; >DMO MS0:/LOCK=UNLOAD 20:25:46 *** MS0: -- Dismount complete DMO -- TT0: dismounted from MS0: *** Final dismount initiated *** >; >TIME 20:25:46 24-MAY-90 >; >; We will now create any UFDs that must be created on your disk(s). >; You will not see the UFD commands. >; >TIME 20:25:46 24-MAY-90 >; >; >; The preparation of the RSX-11M-PLUS kit is now complete. The next >; time this disk is bootstrapped, this dialog will only be repeated >; on request. We will now record the successful installation in the >; log file on the new system disk, and either exit if the installation >; was done on line, or proceed with the normal startup sequence if the >; baseline system was used. >; >SET /UIC=[2,54] >PIP LB:[1,1]KITIDENT.DAT/AP=LB:[2,54]INSTALOG.DAT >; >; >SET /UIC=[200,200] >; PLEASE NOTE >; >; If you have not yet read the system release notes, please do so >; now before attempting to perform a SYSGEN or to utilize the new >; features of this system. >; >; >; In order to start the SYSGEN process, type: >; >; >@SYSGEN >; >; When SYSGEN has completed and your generated system is >; running, you may wish to edit several DIGITAL-supplied >; prototype command and text files to suit your system >; and application: >; >; File Purpose >; ---- ------- >; [0,0]RSX11.SYS An account/password file >; This file does contain privileged accounts. >; >; [1,2]STARTUP.CMD (This file) Invoked at bootstrap time to >; control bringing up the system. >; >; [1,2]QMGSTART.CMD Invoked by STARTUP to start up the Queue >; Manager and spooling system. >; >; [1,2]SHUTUP.CMD Invoked by SHUTUP when taking down the system >; to perform system dependent shutdown tasks. >; >; [1,2]QMGSTOP.CMD Invoked by SHUTUP to stop the Queue Manager >; and spooling system. >; >; [1,2]LOGIN.TXT Displayed on user's terminal when logging in. >; >; [1,2]BATCH.TXT Displayed at the beginning of each batch log >; file. >; >; >ELI /LOG/LIM >CLI /INIT=DCL/CTRLC/DPR="<15><12>/$ /" >INS LB:[1,1]RMSRESAB.TSK/RON=YES/PAR=GEN >INS LB:[1,1]RMSLBL.TSK/RON=YES/PAR=GEN >INS LB:[1,1]RMSLBM.TSK/RON=YES/PAR=GEN >INS $QMGCLI >INS $QMGCLI/TASK=...PRI >INS $QMGCLI/TASK=...SUB >QUE /START:QMG >INS $QMGPRT/TASK=PRT.../SLV=NO >QUE LP0:/CR/NM >START/ACCOUNTING >CON ESTAT LP0: >QUE BAP0:/BATCH >QUE BAP0:/AS:BATCH >@ <EOF> > >SHO /DEF DB0:[200,200] Nonamed TT0: Protection UIC: [200,200] >
Run SYSGEN
Now we could use the baseline system, but it won't be optimized for our hardware configuration - it may not make use of all the physical memory and there may be serveral devices that are not configured. To create an executive image optimized for our setup we run the system generation utility. This is a series of command procedures that reside in the UFD [200,200] (UFD is a User File Directory). We can see from the command above that we are already in UFD [200,200] so run the SYSGEN.CMD command procedure as follows:
>@SYSGEN >; >; RSX-11M-PLUS V4.2 BL58 SYSGEN >; >; COPYRIGHT (c) 1988 >; DIGITAL EQUIPMENT CORP., MAYNARD MA., 01754 >; >SET /DPRO=[RWED,RWED,RWE,R] >; >; To exit from the SYSGEN procedure at any time, type CTRL/Z. >; >; If you are unsure of the answer to a question for which a de- >; fault answer exists, use the default answer. >; >; >; >;=================================================== >; Choosing SYSGEN Options 24-MAY-90 at 20:26 >;=================================================== >; >; >; >; Every question is preceded by a question number (for example SU010) >; which you can use to find the explanation of the question in the >; RSX-11M-PLUS System Generation and Installation Guide. >; >; An explanation of every question is also available by pressing >; the ESC key (or the ALTMODE key) in response to the question. >; >; If you are unfamiliar with the SYSGEN procedure, the explanation of >; each question can be printed automatically before the question. >; >* SU010 Do you always want the explanation printed? [Y/N D:N]: ? ↵ >; >; SYSGEN always creates saved answer files containing your responses >; to the SYSGEN questions: >; >; SYSGENSA1.CMD Setup questions, Executive options >; SYSGENSA2.CMD Peripheral configuration >; SYSGENSA3.CMD Nonprivileged task builds >; >; You should perform a PREPGEN first to create saved answer files, and >; then perform a SYSGEN, specifying those saved answer files as input >; to the Executive, peripheral, and nonprivileged task build sections. >; >* SU020 Do you want to use a saved answer file as input for >* the Executive options? [Y/N D:N]: ? ↵ >; >* SU040 Do you want to use a saved answer file as input for >* the peripheral configuration? [Y/N D:N]: ? ↵ >; >* SU060 Do you want to use a saved answer file as input for >* the nonprivileged task builds? [Y/N D:N]: ? ↵ >; >* SU080 Do you want to do a PREPGEN? [Y/N D:N]: ? ↵ >; >* SU090 Enter the name of the disk drive containing your >* target system disk [ddnn:] [S R:2-5]: DB0: >; >ASN DB0:=IN: >ASN DB0:=OU: >ASN DB0:=LB: >ASN DB0:=WK: >ASN DB0:=TK: >ASN DB0:=BC: >ASN DB0:=LI: >ASN DB0:=OB: >ASN DB0:=EX: >ASN DB0:=MP: >; >* SU100 Do you want to run Autoconfigure on the host system >* hardware? [Y/N D:N]: Y
Autoconfigure will work out the CSR and vector of most devices for us. This is only available in the later versions of RSX.
>;
>; Running Autoconfigure:
>;
>INS $ACF
>ACF
>INS $ACO
>ACO SHOW
Processor Type: 11/84 Memory Size: 1024. Kw
Options:
Floating Point Processor (FP11)
Extended Instruction Set (EIS)
Extended (22-Bit) Addressing
Cache Memory
Name Vector CSR Unit Type Remark
RHA 254 176700
0 RP04
1 RP04
DLA 160 174400
0 RL02
1 RL02
2 RL01
3 RL01
MSA 224 172522
DYA 264 177170
YLA 060 177560
>ACO SYSGEN
>;
>* SU110 Do you want to override the Autoconfigure results? [Y/N D:N]: ↵
>;
>; You can:
>;
>; o do a complete SYSGEN
>;
>; o continue a previous SYSGEN from where you left off
>;
>; o do an individual section of SYSGEN
>;
>;
>* SU120 Do you want to do a complete SYSGEN? [Y/N D:Y]: ↵
>;
>INS [3,54]MAC/TASK=MACT0
>INS [3,54]PIP/TASK=PIPT0
>INS [3,54]LBR/TASK=LBRT0
>INS [3,54]TKB/TASK=TKBT0
>INS [3,54]VMR/TASK=VMRT0
>;
>;
>;
>;======================================================
>; Choosing Executive Options 24-MAY-90 at 20:27
>;======================================================
>;
>;
>;
>; The answers to the questions in this section are put in the saved
>; answer file [200,200]SYSGENSA1.CMD.
>;
>; Enter a comment for inclusion in the SYSGENSA1 saved answer file.
>; The comment may contain more than one line. The "V" in the right
>; margin below marks the maximum line length. When you are done,
>; press RETURN in response to the prompt.
>; V
>* Comment [S R:0.-55.]: Test system for Simh
>* Comment [S R:0.-55.]:
>;
>* CE020 Do you want the Full-functionality Executive? [Y/N D:Y]: ↵
I recommend choosing the default option above unless you want to answer a LOT of questions
>; >* CE120 Do you want support for communications products >* (such as DECnet, PSI, and LAT)? [Y/N D:N]: Y >; >* CE130 What is the system name? [S R:0-6 D:"RSXMPL"]: RSX1 >; >* CE264 Do you want IP11 industrial I/O subsystem support? [Y/N D:N]: ↵ >; >* CE270 Do you want to include XDT? [Y/N D:N]: ↵ >; >* CE280 Enter the crash notification device CSR >* address [O R:160000-177700 D:177564]: ↵ >; >; Note: Enter both the device and the logical unit number. >; For example, MM0: or DL1:. >; >; Note: Enter XX: if you desire loadable DU:, DL:, MU:, MS: or MM: >; crash driver support. >; >* CE290 On what device and unit do you want crash dumps >* to be written? [S R:2-6]: DL0:
When RSX crashes it will halt immediately and ask you to load a scratch pack On this device. Once you have loaded the pack and set the cpu to run (type cont at the sim> prompt for simh) it will write a dump to this device.
>; >* CE330 Is your system clock programmable (KW11-P)? [Y/N D:N]: ↵ >; >* CE350 Is your line frequency 50 Hz? [Y/N D:N]: Y >; >; >; >;============================================================= >; Choosing Peripheral Configuration 24-MAY-90 at 20:28 >;============================================================= >; >; >; >; The answers to the questions in this section are put in the saved >; answer file [200,200]SYSGENSA2.CMD. >; >; Enter a comment for inclusion in the SYSGENSA2 saved answer file. >; The comment may contain more than one line. The "V" in the right >; margin below marks the maximum line length. When you are done, >; press RETURN in response to the prompt. >; V >* Comment [S R:0.-55.]: Test system for Simh >* Comment [S R:0.-55.]: >; >; >; DB: controllers: RH11, RH70 devices: RP04, RP05, RP06 >; >; RH Configuration >; >; Physical Unit Number >; >; 0 1 2 3 4 5 6 7 >; >; RHA DB0: DB1: >; >; >; >; >; DL: controllers: RL11, RLV12 devices: RL01, RL02 >; >; DL Configuration >; >; Physical Unit Number >; >; 0 1 2 3 4 5 6 7 >; >; DLA DL0: DL1: DL2: DL3: >; >; >; >; >; CR: controllers: CM11, CR11 >; >* CP4004 How many CM/CR11 card readers do you have? [O D:0]: ↵ >; >; >; MS: controllers: TS11, TU80, TSV05, TK25 >; >; >; DY: controller: RX211, RXV21 device: RX02 >; >; >; LA: controller: LPA11 >; >* CP6204 How many LPA11 lab subsystems do you have? [D R:0.-16. D:0.]: ↵ >; >; >; TT: controllers: DL11, DLV11 controller mnemonic: YL >; >* CP6832 Enter terminal type for YLA [S R:4-6 D:"LA120"]: VT100 >; >; >; TT: controller: DJ11 controller mnemonic: YJ >; >* CP7204 Enter number of DJ11 asynchronous line >* multiplexers [D R:0.-16. D:0.]: ↵ >; >; >* CP7604 Do you have any intercomputer communication devices? [Y/N D:N]: ↵
Be sure to select no to the previous question if you intend to run DECnet because the network devices cannot be shared between the RSX driver and the DECnet driver.
>;
>;
>; Enter device mnemonics for any user-supplied drivers. The driver
>; source files must reside in [11,10] and be named ddDRV.MAC and
>; ddTAB.MAC where dd is the device mnemonic.
>;
>; You may enter the mnemonics on more than one line. When you have
>; listed all the drivers, press RETURN when asked for the device
>; mnemonic.
>;
>; The device mnemonic must not include a colon.
>;
>* CP9604 Enter device mnemonics for user-supplied drivers [S]: ↵
>;
>;
>; The highest vector among the devices you specified in this SYSGEN
>; is 374(octal). This is the default response for this question.
>;
>* CP9632 What is the highest interrupt vector
>* address? [O R:374-774 D:374]: ↵
>;
>;
>;
>;================================================================
>; Assembling the Executive and Drivers 24-MAY-90 at 23:30
>;================================================================
>;
>;
>;
>; The answers to the questions in this section are put in the saved
>; answer file [200,200]SYSGENSA1.CMD.
>;
>PIP RSXMC3.MAC=RSXMC1.MAC,RSXMC2.MAC
>PIP RSXMC.MAC=RSXMC3.MAC,RSXMC0.MAC
>;
>SET /UIC=[1,24]
>PIP [11,10]/NV=[200,200]RSXMC.MAC
>PIP [11,10]/NV=[200,200]SYSTB.MAC
>PIP [11,24]/NV=[200,200]RSXASM.CMD
>PIP [11,24]/NV=[200,200]DRIVERS.ASM
>;
>;
>* AE010 Do you want assembly listings of the Executive and
>* drivers? [Y/N D:N]: ↵
>;
>ASN NL:=LS:
>;
>;
>* AE030 Do you wish to pause to edit any files before
>* assembling? [Y/N D:N]: ↵
>;
>SET /UIC=[11,24]
>;
>PIP *.OBJ;*/DE/NM,*.TTY;*
>;
>TIME
23:30:52 24-MAY-90
>;
>MAC @RSXASM
>;
>TIME
23:31:48 24-MAY-90
>;
>MAC @DRIVERS.ASM
>;
>TIME
23:32:31 24-MAY-90
>;
>PIP RSX11M.OBS=*.OBJ
>PIP TTDRV.OBS=*.TTY
>;
>SET /UIC=[200,200]
>PIP /NV=[11,10]RSXMC.MAC
>;
>SET /UIC=[1,24]
>PIP RSXBLD.CMD/PU/NM
>PIP RSX11M.OLB;*/DE/NM
>PIP [200,200]RSXMC.MAC/PU/NM
>;
>LBR RSX11M/CR:256.::256./-EP=[11,24]RSX11M.OBS
>PIP [11,24]RSX11M.OBS;*,*.OBJ;*/DE
>;
>LBR TTDRV/CR:40.:392.:128.=[11,24]TTDRV.OBS
>PIP [11,24]TTDRV.OBS;*,*.TTY;*/DE
>SET /UIC=[200,200]
>;
>;
>;
>;==============================================================
>; Building the Executive and Drivers 24-MAY-90 at 23:32
>;==============================================================
>;
>;
>;
>; The answers to the questions in this section are put in the saved
>; answer file [200,200]SYSGENSA1.CMD.
>;
>;
>; Allocate space to be used later for the system image file.
>;
>SET /UIC=[1,54]
>PIP RSX11M.TMP/CO/BL:1026.=NL:
>;
>SET /UIC=[200,200]
>;
>SET /UIC=[1,24]
>SET /UIC=[200,200]
>SET /UIC=[1,54]
>PIP SYSVMR.CMD=[200,200]SYSVMR.CMD,VMRTTY.CMD
>;
>SET /UIC=[200,200]
>;
>* BE030 Do you want to pause to edit any files before
>* task-building? [Y/N D:N]: ↵
>;
>SET /UIC=[1,24]
>PIP [1,24]/NV/NM=[200,200]RSXBLD.CMD,RSX11M,DSP11M,LDR11M
>PIP [1,24]/NV=[200,200]DIR11M.CMD,DR211M,DIRCOM,DR2COM,DIR
>PIP [1,24]/NV=[200,200]DR311M.CMD,DR411M,DR3COM,DR4COM
>PIP [1,24]/NV=[200,200]VEC11M.CMD,DCM11M,VECCOM
>;
>TIME
23:33:39 24-MAY-90
>;
>TKB @RSXBLD
>;
>TIME
23:33:53 24-MAY-90
>;
>TKB @[200,200]DRIVERS.BLD
>;
>TIME
23:33:56 24-MAY-90
>SET /UIC=[200,200]
>;
>;
>;
>;=========================================================
>; Building the Privileged Task 24-MAY-90 at 23:33
>;=========================================================
>;
>;
>;
>; The answers to the questions in this section are put in the saved
>; answer file [200,200]SYSGENSA1.CMD.
>;
>;
>* BP040 Do you want the maps of the privileged tasks? [Y/N D:N]: ↵
>;
>ASN NL:=MP:
>;
>SET /UIC=[1,24]
>;
>TIME
23:34:00 24-MAY-90
>;
>TKB @SAVBLD
>;
>TIME
23:34:02 24-MAY-90
>;
>ASN LB:=OU:
>SET /UIC=[200,200]
>;
>;
>;
>;============================================================
>; Rebuilding Supplied System Tasks 24-MAY-90 at 23:34
>;============================================================
>;
>;
>;
>; The answers to the questions in this section are put in the saved
>; answer file [200,200]SYSGENSA3.CMD.
>;
>;
>* BN010 Do you want to rebuild any system tasks? [Y/N D:N]: ↵
>;
>;
>;
>;==========================================================
>; Creating the System Image File 24-MAY-90 at 23:34
>;==========================================================
>;
>;
>SET /UIC=[1,54]
>;
>PIP RSX11M.TMP;*/DE/NM
>;
>PIP RSX11M.SYS/CO/NV/BL:1026.=RSX11M.TSK
>;
>ASN LB:=SY:
>VMR @SYSVMR
Loading Executive data space
Data space loading completed
VMR -- *DIAG*-Installed tasks or commons may no longer fit in partition
SET /TOP=SYSPAR:-*
VMR -- *DIAG*-Loadable driver larger than 4K
LOA TT:
VMR -- *DIAG*-Installed tasks or commons may no longer fit in partition
SET /TOP=DRVPAR:-*
SECPOL 117734 00172000 00100000 SEC POOL
SYSPAR 117670 00272000 00165300 MAIN
117624 00272000 00111500 RO COM !DIR11M!
117434 00403500 00005200 TASK [...LDR]
117230 00410700 00033100 TASK [MCR...]
117024 00444000 00010100 TASK [TKTN ]
116620 00454100 00003200 TASK [SHF...]
DRVPAR 116540 00457300 00133100 MAIN
116474 00457300 00006600 RO COM !TTEXT !
116410 00466100 00020600 RO COM !TTCOM !
116324 00506700 00034000 DRIVER (TT:)
115744 00542700 00004600 DRIVER (DB:)
115144 00547500 00003500 DRIVER (DL:)
115100 00553200 00003600 RO COM !PUCOM !
114524 00557000 00011400 DRIVER (MU:)
114214 00570400 00005200 DRIVER (MS:)
113670 00575600 00004700 DRIVER (DY:)
113420 00602500 00003300 DRIVER (XM:)
113230 00606000 00000100 DRIVER (NL:)
113164 00606100 00000300 DRIVER (CO:)
113120 00606400 00002500 DRIVER (VT:)
113054 00611100 00001300 DRIVER (RD:)
GEN 113010 00612400 07165400 MAIN
112744 00612400 00002000 RO COM !DYCOM !
...LDR 12.01 117500 SYSPAR 248. 00005200 LB0:-00143315 FIXED
TKTN 07.00 117070 SYSPAR 248. 00010100 LB0:-00055302 FIXED
F11MSG 15.00 110520 GEN 200. 00006200 LB0:-00043211
MTAACP 16.02 110124 GEN 200. 00016200 LB0:-00047317
SHE... 05.01 107654 GEN 200. 00014300 LB0:-00052711
MCR... 06.00 117274 SYSPAR 160. 00033100 LB0:-00046324 FIXED
F11ACP 06.02 112510 GEN 149. 00014400 LB0:-00041762
ERRLOG 05.01 112150 GEN 148. 00056100 LB0:-00041700
PMT... 2.01 111510 GEN 148. 00007100 LB0:-00050207
COT... 2.03 110644 GEN 145. 00014300 LB0:-00036223
HRC... 03.01 110250 GEN 140. 00057400 LB0:-00043470
PMD... 07.04 110000 GEN 140. 00017600 LB0:-00050157
SYSLOG 04.01 111240 GEN 130. 00022100 LB0:-00054176
SHF... 07.00 116664 SYSPAR 105. 00003200 LB0:-00052730 FIXED
UML... 2.00 111114 GEN 100. 00023200 LB0:-00055333
FXR... 03.01 110374 GEN 100. 00003300 LB0:-00043203
BAP0 04.11 112274 GEN 80. 00047700 LB0:-00033730
QMG... 03.06 111364 GEN 75. 00035200 LB0:-00050571
LP0 06.02 111730 GEN 70. 00017500 LB0:-00045642
ACNT 06.02 110770 GEN 50. 00053100 LB0:-00033345
SHUTUP 04.03 107530 GEN 50. 00015700 LB0:-00052735
...RMD 4.05 001756+ GEN 225. 00041200 LB0:-00050645
...DCL 5.01 001732+ GEN 160. 00060100 LB0:-00036505
...DMO 04.01 001734+ GEN 160. 00017300 LB0:-00037431
...MCR 06.01 001750+ GEN 160. 00040300 LB0:-00046361
...MOU 26.05 001752+ GEN 160. 00045400 LB0:-00047226
...CA. 14.01 002006+ GEN 150. 00025300 LB0:-00054222
...INS 15.01 001746+ GEN 100. 00052500 LB0:-00044342
...SAV 09.00 002002+ GEN 100. 00062000 LB0:-00147016
...UFD 7.00 002010+ GEN 100. 00014300 LB0:-00055314
...ACS 3.02 001764+ GEN 70. 00006200 LB0:-00033567
...ACC 04.01 001724+ GEN 65. 00032100 LB0:-00033112
...SHA 05.01 002004+ GEN 65. 00031000 LB0:-00052541
...AT. 9.1 001740+ GEN 64. 00054100 LB0:-00043742
...INI 23.02 001742+ GEN 60. 00036000 LB0:-00044250
...HOM 23.02 001744+ GEN 60. 00036000 LB0:-00044250
...BRO 07.00 001726+ GEN 50. 00040200 LB0:-00034055
...BYE 05.00 001730+ GEN 50. 00021400 LB0:-00034347
...HEL 04.05 001736+ GEN 50. 00037100 LB0:-00043333
...PIP 19.00 001754+ GEN 50. 00027100 LB0:-00047717
...UNL 5.03 001760+ GEN 50. 00021500 LB0:-00055426
...ACD 2.00 001762+ GEN 50. 00042500 LB0:-00033203
...BOO 02.00 001766+ GEN 50. 00034400 LB0:-00033671
...CON 03.00 001770+ GEN 50. 00131300 LB0:-00036026
...ELI 04.02 001772+ GEN 50. 00032400 LB0:-00041643
...LOA 5.02 001774+ GEN 50. 00037600 LB0:-00045447
...MAG 03.00 001776+ GEN 50. 00037200 LB0:-00046263
...PSW 03.01 002000+ GEN 50. 00016000 LB0:-00050272
RHA OFL CPA CSR=176700 VEC=254 PRI=5
YLA OFL CPA CSR=177560 VEC=60 PRI=5
DLA OFL CPA CSR=174400 VEC=160 PRI=5
MUA OFL CPA CSR=174500 VEC=260 PRI=5
MSA OFL CPA CSR=172522 VEC=224 PRI=5
DYA OFL CPA CSR=177170 VEC=264 PRI=5
XMA OFL CPA CSR=160070 VEC=310 PRI=5
CO0: OFL DRIVER
TT0: YLA0: OFL DRIVER
VT0: OFL DRIVER
RD0: ONL DRIVER
DB0: RHA0: OFL DRIVER
DB1: RHA1: OFL DRIVER
DL0: DLA0: OFL DRIVER
DL1: DLA1: OFL DRIVER
DL2: DLA2: OFL DRIVER
DL3: DLA3: OFL DRIVER
MU0: MUA0: OFL DRIVER
MS0: MSA0: OFL DRIVER
DY0: DYA0: OFL DRIVER
DY1: DYA1: OFL DRIVER
XM0: XMA0: OFL DRIVER
NL0: OFL DRIVER
POOL=1200:13510.:13510.:1720
>SET /UIC=[200,200]
>;
>REM MACT0
>REM PIPT0
>REM LBRT0
>REM TKBT0
>REM VMRT0
>;
>; End of SYSGEN
>;
>TIME
23:34:13 24-MAY-90
>;
>ASN =
>;
>@ <EOF>
>
Boot the new system
Now to boot the newly generated system. The first task we must do is to save the new executive image and write the boot block.
>BOOT [1,54]RSX11M
RSX-11M-PLUS V4.2 BL58
>
SAV/WB
RSX-11M-PLUS V4.2 BL58 1024.KW System:"RSX1 "
>RED DB:=SY:
>RED DB:=LB:
>RED DB:=SP:
>MOU DB:"RSX11MPBL58"
>@DB:[1,2]STARTUP
>; PLEASE NOTE
>;
>; If you have not yet read the system release notes, please do so
>; now before attempting to perform a SYSGEN or to utilize the new
>; features of this system.
>;
>;
>* Please enter time and date (HH:MM DD-MMM-YY) [S]: 23:37 24-MAY-90
>TIME 23:37 24-MAY-90
>ACS SY:/BLKS=1024.
>CON ONLINE ALL
>ELI /LOG/LIM
>CLI /INIT=DCL/CTRLC/DPR="<15><12>/$ /"
>INS LB:[1,1]RMSRESAB.TSK/RON=YES/PAR=GEN
>INS LB:[1,1]RMSLBL.TSK/RON=YES/PAR=GEN
>INS LB:[1,1]RMSLBM.TSK/RON=YES/PAR=GEN
>INS $QMGCLI
>INS $QMGCLI/TASK=...PRI
>INS $QMGCLI/TASK=...SUB
>QUE /START:QMG
>INS $QMGPRT/TASK=PRT.../SLV=NO
>QUE LP0:/CR/NM
>START/ACCOUNTING
>CON ESTAT LP0:
>QUE BAP0:/BATCH
>QUE BAP0:/AS:BATCH
>@ <EOF>
>BYE
Have a Good Evening
24-MAY-90 23:37 TT0: logged off RSX1
>
>HELLO
Account or name: SYSTEM
Password: SYSTEM
RSX-11M-PLUS V4.2 BL58 [1,54] System RSX1
24-MAY-90 23:37 Logged on Terminal TT0: as SYS1
Good Evening
*****************************************************************
* *
* Welcome to RSX-11M-PLUS *
* *
* Version 4.2 Base level 58 *
* This is file LB:[1,2]LOGIN.TXT *
* *
*****************************************************************
>SHOW DEV
CO0: TT0: Loaded
TT0: [1,1] [1,1] - Logged in Loaded
VT0: Loaded
VT1: Loaded
RD0: Loaded
DB0: Public Mounted Loaded Label=RSX11MPBL58 Type=RP04
Seek_Optimization=Nearest:10. Overlapped_Seeks
DB1: Loaded Type=RP04
Seek_Optimization=Nearest:10. Overlapped_Seeks
DL0: Loaded Type=RL02
Seek_Optimization=Nearest:10.
DL1: Loaded Type=RL02
Seek_Optimization=Nearest:10.
DL2: Loaded Type=RL01
Seek_Optimization=Nearest:10.
DL3: Loaded Type=RL01
Seek_Optimization=Nearest:10.
MU0: Loaded Type=TK50
MS0: Loaded Type=TS11
DY0: Loaded Type=RX02
DY1: Loaded Type=RX02
NL0: Loaded
TI0:
CL0: TT0:
SP0: DB0:
LB0: DB0:
SY0: DB0:
>