I am taking another trip down memory lane and revisiting a favorite computer with introspectable operating systems.
Eight years ago I did an RSX-11M SYSGEN and bemoaned the lack of an Operator's Console. What a pleasant surprise when I learned of the PiDP-11 kit by Oscar Vermeulen! This is a kit for a PDP-11/70 Operator's Console. Thanks to the code by Jörg Hoppe, Operator's Consoles are now supported by simh. A Raspberry Pi inside the console monitors the switches and controls the lights. If you use a Raspberry Pi 3 with a quad-core CPU, there is plenty of processing power to also run simh on the Pi -- the result is a PDP-11/70 totally contained within the console case.
Simh has been enhanced in recent years. Additional types of devices are supported. Logging and simh controls have improved. For details, refer to the documentation in doc/pdp11_doc.doc and doc/simh_doc.doc in the simh github repository.
To see a rotating lights display on the operator's console, RSX must be regenerated with support for that feature. This a good time to add other devices to the configuration since that also requires a SYSGEN. I also see this as an opportunity to refine my prior SYSGEN. It will be beneficial to have some familarity with the prior SYSGEN because I will not repeat all those details here.
There are newer versions of RSX-11M and RSX-11M-Plus with more features and support for additional devices. Even the venerable VT100, introduced in August 1978, is not well supported by M3.2. When I tried RMDemo in the past on RSX-11M V3.2 it did not properly display on a VT100. In an undocumented SYSGEN Phase III, VT100 was not one of the terminal types that could be chosen in the EDTBLD.CMD file used to customize EDT.
On the DECUS RSX SIG tapes, there are a few documents with recommendations on performing a SYSGEN. (See: rsx82a/333001/ and rsx83b/346103/) I hope to use these to improve my technique. Therefore I choose to revisit RSX-11M V3.2 for comparison to my prior SYSGEN and because for that release, all these are easily available:It is desirable to have devices for any software I might discover. Thus I have added devices like DECtape, additional disk types and cassette tape. To provide a possibility for more storage, the controller for MSCP disks was added.
It is not much of a problem if RSX-11M V3.2 does not support all the devices in the configuration. Unsupported devices will be ignored by an OS. However, those devices will be available when running some other OS. This works fine as long as there is a way for each OS to discover the addresses (CSR and interrupt vector) of all the supported devices.
In RSX-11M V3.2 device addresses are manually configured by answering questions during SYSGEN Phase I. Newer software might be able to autoconfigure by detecting the devices present and thus reduce manual input needed to SYSGEN.
The table below shows the devices in the new configuration. The simh
commands to select this device configuration are in the file
pdp_hw_config.ini. Another
file called
RHA RH70/RH11 Massbus adapter (for RP) address=17776700-17776753, vector=254, BR5 RHB RH70/RH11 Massbus adapter (for TU) address=17772440-17772477, vector=224, BR5 CLK 60Hz, address=17777546-17777547, vector=100, BR6 PCLK KW11-P programmable real time clock 100K Hz, address=17772540-17772545, vector=104, BR6 PTR PC11 paper tape reader address=17777550-17777553, vector=70, BR4 PTP PC11 paper tape punch address=17777554-17777557, vector=74, BR4 TTI address=17777560-17777563, vector=60, BR4 (console keyboard) TTO address=17777564-17777567, vector=64, BR4 (console printer) TDC TU58 cartridge controllers=1, address=17776500-17776507, vector=300*, BR4, 2 units CR CR11/CD11/CD20 card reader no EOF pending, address=17777160-17777167, vector=230, BR4 1000 cards per minute, translation=029 LPT LP11 line printer address=17777514-17777517, vector=200, BR4 DZ DZ11 8-line terminal multiplexer address=17760100-17760117*, vector=310-324*, BR5, lines=16 RK RK11/RKV11 cartridge disk controller address=17777400-17777417, vector=220, BR5, 8 units RL RL11/RL01(2) cartridge disk controller RL11, address=17774400-17774411, vector=160, BR5, 4 units HK RK611/RK06(7) cartridge disk controller address=17777440-17777477, vector=210, BR5, 8 units RY RX211 floppy disk controller address=17777170-17777173, vector=264, BR5, 2 units RP RP04/05/06/07 RM02/03/05/80 Massbus disk controller Massbus adapter 0 (RHA), 8 units RQ RQDX3 MSCP disk controller address=17772150-17772153, no vector, BR5, RQDX3, 4 units TC TC11/TU56 DECtape controller address=17777340-17777351, vector=214, BR6, 8 units TQ TUK50 TMSCP magnetic tape controller TK70 (300MB), address=17774500-17774503, no vector, BR5, 4 units TU TM03 tape formatter Massbus adapter 1 (RHB), FORMATTER, TM03, 8 units TA TA11/TA60 Cassette Tape address=17777500-17777503, vector=260, BR6, 2 units XU DEUNA/DELUA Ethernet controller address=17774510-17774517, vector=120, BR5, MAC=08:00:2B:88:4D:14 type=DELUA, throttle=disabled |
Even though devices have been added, most devices that were in the prior configuration have unchanged CSR/vector addresses. Therefore I can use the RSX system that was previously generated as a starting point on this hardware configuration. (Except the DZ11 terminal multiplexer has a new vector. Only the console terminal was usable until SYSGEN Phase II was complete.)
The most recent autopatch kit consists of two RK05 disks. The RSX-11M distribution kit is on five RL01 disks. This procedure updates the RSX-11M distribution kit with the most recent fixes. Autopatch modifies the distribution kit. Before running the autopatch procedure, make a backup copy of your original RSX-11M distribution kit.
The first autopatch RK05 disk updates the RSX-11M distribution kit. That first disk also contains the instruction for applying autopatch in this file [200,200]AUTOPATCH.DOC. The second autopatch RK05 can be used to patch layered products.
Four of the RL01 distribution disks, baseline, unmapped sources, mapped sources, and utilities get updated by the first autopatch disk. The RMS11 disk is not needed during SYSGEN. But it can be patched later as a layered product.
It is possible to apply autopatch with only two mass storage units. However by using more drives, one can reduce the number of times a disk pack be moved. By using the two RP06 disks, the system is available for timesharing with other users while the patches get applied.
The copies of the RSX-11M distribution kit disks to be updated will be inserted into either DL1: or DL2:. Here are all the disks which were mounted during the autopatch procedure:
Here is an abridged transcript of running autopatch. Long sequences of commands with no interaction are not shown. The full transcript is in autopatch_console.log. From the timestamps we can see that applying patches took only a few minutes, much less time than predicted by AUTOPATCH.DOC. (This was run via simh on a Raspberry Pi 3). When applying patches be careful and review the entire printout from this procedure to verify that no error has occurred.
Connected to the PDP-11 simulator CON-TELNET device RSX-11M V3.2 BL26 1920K MAPPED >RED DB:=SY: >RED DB:=LB: >MOU DB:SYSGENBL26 >@DB:[1,2]STARTUP >* PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY) [S]: 28-mar-19 10:20 >TIM 28-mar-19 10:20 >* ENTER LINE WIDTH OF THIS TERMINAL [D D:132.]: >SET /BUF=TI:132. >set /pub=db1: >mou db1:USERDIRS >ACS SY:/BLKS=512. >; >; NOTE - The Baseline INDirect must be replaced by BIGIND with >; a priority of 10. for SYSGEN. >; >; ie >REM ...AT. >; >INS $BIGIND/PRI=10. >; >@ <EOF> > >;;; Examine the autopatch kit >all dk: >mou dk:autopatchE1 >pip dk:[200,200]/li DIRECTORY DK0:[200,200] 28-MAR-19 10:20 AUTOPATCH.DOC;1 168. 15-MAY-81 13:56 AUTOPATCH.CMD;1 69. 15-MAY-81 13:56 TOTAL OF 237./237. BLOCKS IN 2. FILES >;;; Read the autopatch documentation >pip lp:=dk:[200,200]autopatch.doc > >;;; Get information about layered product updates of interest >all dk1: >mou dk1:autopatchE2 >pip lp:=dk1:[*,*]/li >pip lp:=dk1:[245,200]ed2.doc >pip lp:=dk1:[250,200]fort4.doc >pip lp:=dk1:[275,200]rms.doc > >;;; Setup for running autopatch > >;;; Initialize the scratch disk >all dl: >ini dl:scratch >dea dl: > >all dl1: >mou dl1:rsxm26 >pip lp:=dl1:[*,*]/li > >;;; Distribution kit on bitsavers.org is not pristine -- delete detritus >pip dl1:[200,200]syssaved.cmd;*/de > >;;; Setup is complete. Run the autopatch procedure. >tim 10:22:47 28-MAR-19 >asn dl1:=sy: >set /uic=[200,200] >pip sy:=dk:autopatch.cmd >dmo dk: DMO -- TT0: DISMOUNTED FROM DK0: *** FINAL DISMOUNT *** >@[200,200]autopatch >; >; >; AUTOPATCH Rev. E patches only the software for RSX-11M. >; If you wish to patch any layered product software, >; please refer to your cover letter. >; >; >; >; >; RSX-11M V3.2 BL26 Autopatch Revision E Version 1.80 >; >; COPYRIGHT (C) 1981 DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASS. >; >; >; >SET /UIC=[1,1] >; >* 1. Have you made a copy of the disk(s) to be patched? [Y/N]:y >; >; Specify the type of RSX-11M V3.2 distribution kit you have by >; responding to the next question with either A, B, or C where: >; >; A -- indicates the big disk distribution kit >; (RK06/RK07, RM02/RM03, RP02/RP03, RP04/RP05/RP06) >; B -- indicates the RL01/RL02 distribution kit >; C -- indicates the dual RK05 distribution kit >; >* 2. What type of distribution kit do you have (A, B, or C) [S]: B >* 3. Do you have a second RL01/RL02 drive to use? [Y/N]:y >* 4. Are you running Autopatch standalone (on the baseline system)? [Y/N]: >* 5. Are you going to SYSGEN a mapped system? [Y/N]:y >* 6. Do you want to patch UNMSRC (unmapped sources)? [Y/N]:y >; >; If you answer Y to the next question, the contents of UIC >; [1,50] will be deleted to provide space for the >; Autopatch files. If you answer N, Autopatch will exit. >; >* 7. Should the contents of UIC [1,50] be deleted? [Y/N]:y >SET /UIC=[1,54] >; >; To provide more space on the baseline disk for Autopatch files, several >; files which are not needed by Autopatch will be copied to a scratch >; disk. These files include [1,54]EDT.TSK,EDI.TSK,ZAP.TSK,VFY.TSK, >; [1,54]PAT.TSK,DMP.TSK,CMP.TSK,BAD.TSK, and [1,51]BADSYS.SYS,BADSYS.STB >; These files will all be restored at the end of the Autopatch >; procedure. Other files in [1,51]*.* will also be deleted and replaced from >; the Autopatch kit. >; >; Please insert a scratch RL01/RL02 into a free RL01/RL02 drive. >; You will be asked to give the internal label of your scratch RL01/RL02 >; >* 8. Enter the label of your scratch RL01/RL02 [S R:1.-9.]: scratch >* 9. Enter the unit number of the drive containing a scratch RL01/RL02 [O]: 0 >MOU DL0:scratch >* 10. Did DL0: mount successfully? [Y/N]:y >; >UFD DL0:[1,51] >UFD DL0:[1,54] >PIP DL0:[1,51]/NV=SY:[1,51]BADSYS.* >PIP DL0:[1,54]/NV=SY:[1,54]EDT.TSK,EDI.TSK,ZAP.TSK,VFY.TSK,PAT.TSK >PIP DL0:[1,54]/NV=SY:[1,54]DMP.TSK,CMP.TSK,BAD.TSK >; >; Now delete copied files from the baseline disk >; >PIP SY:[1,51]*.*;*/DE/NM >PIP SY:[1,54]EDT.TSK;*,EDI.TSK;*,ZAP.TSK;*,VFY.TSK;*,PAT.TSK;*/DE/NM >PIP SY:[1,54]DMP.TSK;*,CMP.TSK;*,BAD.TSK;*/DE/NM >DMO DL0: DMO -- TT0: DISMOUNTED FROM DL0: *** FINAL DISMOUNT *** >; >; Now remove the scratch disk from DL0: >; >SET /UIC=[1,1] >; >; Determine the Autopatch kit device and unit. Place the Autopatch >; medium labeled AUTOPATCHE1 on that unit. The unit should be write >; protected. When the unit is ready respond to the next question. >; >* 11. When ready, enter the Autopatch device and unit (ddu:) [S]: DK0: >MOU DK0:AUTOPATCHE1 >* 12. Did the AUTOPATCHE1 disk mount successfully? [Y/N]:y >; >; Autopatch copies the Autopatch files to temporary UFDs >; in order to perform the Autopatch process. The .MAC >; .OBJ, .OLB, .SYS, and .STB Autopatch files are >; automatically deleted from these UFDs at the end >; of the Autopatch process. >; >* 14. Should .PAT, .COR, .CMD and .ODL Autopatch files be deleted? [Y/N]:y >; >; Determine the second RL01/RL02 unit to use. >; >* 15. What will be your second RL01/RL02 device and unit (ddu:) [S]: DL2: >; >; >; Begin Autopatch process for RSX-11M V3.2 BL26 operating system >; on 28-MAR-19 at 10:24:48. >; >; RL01/RL02 distribution kit >; >; >; Delete [1,50] system files. >; >PIP [1,50]*.*;*/DE/NM >; >; Copy the files from the Autopatch kit to the distribution kit. >; >PIP SY:[*,*]/NV/UF/FO/NM=DK0:[*,60]*.*,[*,64]*.* >; >DMO DK0: DMO -- TT0: DISMOUNTED FROM DK0: *** FINAL DISMOUNT *** ;;; A sequence of commands with no interaction was deleted here. >; >; Now place the RLUTIL in DL2:. The drive should be write >; enabled. >; >* 16. Is the RLUTIL disk ready in DL2:? [Y/N]:y >MOU DL2:RLUTIL >* 17. Did the RLUTIL mount successfully? [Y/N]:y ;;; A sequence of commands with no interaction was deleted here. >DMO DL2:RLUTIL DMO -- TT0: DISMOUNTED FROM DL2: *** FINAL DISMOUNT *** >; >; Remove the RLUTIL disk from DL2: and replace it with the >; UNMSRC disk. The drive should be write enabled. >; >* 18. Is the UNMSRC disk ready in DL2:? [Y/N]:y >MOU DL2:UNMSRC >* 19. Did the UNMSRC mount successfully? [Y/N]:y ;;; A sequence of commands with no interaction was deleted here. >DMO DL2:UNMSRC DMO -- TT0: DISMOUNTED FROM DL2: *** FINAL DISMOUNT *** >; >; Remove the UNMSRC disk from DL2: and replace it with the >; MAPSRC disk. The drive should be write enabled. >; >* 20. Is the MAPSRC disk ready in DL2:? [Y/N]:y >MOU DL2:MAPSRC >* 21. Did the MAPSRC mount successfully? [Y/N]:y ;;; A sequence of commands with no interaction was deleted here. >DMO DL2:MAPSRC DMO -- TT0: DISMOUNTED FROM DL2: *** FINAL DISMOUNT *** >ASN =IN: >ASN =OU: >; >; >; >; Delete the Autopatch files. >; ;;; A sequence of commands with no interaction was deleted here. >; >; >; Please put the scratch disk labelled, scratch, into DL0: so that >; the files which were temporarily saved there may be restored. >; >* 22. Is the scratch RL01/RL02, scratch, ready in DL0:? [Y/N]:y >MOU DL0:scratch >* 23. Did DL0: mount successfully? [Y/N]:y >SET /UIC=[1,54] >PIP [1,54]=DL0:[1,54]EDT.TSK,EDI.TSK,ZAP.TSK,VFY.TSK,PAT.TSK >PIP [1,54]=DL0:[1,54]DMP.TSK,CMP.TSK,BAD.TSK >PIP [1,51]=DL0:[1,51]BADSYS.* >DMO DL0: DMO -- TT0: DISMOUNTED FROM DL0: *** FINAL DISMOUNT *** >REM SLP >REM LBR >; >; Finished with Autopatch process for RSX-11M V3.2 BL26 operating >; system software on 28-MAR-19 at 10:29:33. >; >; >; >; >; >; Upon completion of Autopatch, [200,200]AUTOPATCH.*;* >; should be deleted from the baseline disk (RSXM26). >; This will provide additional space for completing the >; SYSGEN. >; >; >; Autopatch exiting. >; >@ <EOF> > >dea dk: >dmo dk1: DMO -- TT0: DISMOUNTED FROM DK1: *** FINAL DISMOUNT *** >dea dk1: >asn =sy: >dmo dl1: DMO -- TT0: DISMOUNTED FROM DL1: *** FINAL DISMOUNT *** >run $shutup RSX11M SHUT DOWN PROGRAM ENTER MINUTES TO WAIT BEFORE SHUTDOWN: 0 OK TO SHUTDOWN? [Y/N]: y ALL FURTHER LOGINS ARE DISABLED ;;; A sequence with no interaction was deleted here. Disconnected from the PDP-11 simulator |
NOTE: Now that you have patched your distribution kit, make a backup copy of all the updated disks. On a real PDP-11, you can use DSC to make backups to either disk or magtape. If you are using simh, you can simply make a copy of the virtual disk files.
Like any privileged task, INDirect must be rebuilt to match the executive. This was not done during the previous SYSGEN. This must be done before an online SYSGEN is possible. All needed files were copied from the distribution disks when the previously generated system was transferred to RP06.
;;; Commands that execute at RSX boot were deleted here. >; >; NOTE - The Baseline INDirect must be replaced by BIGIND with >; a priority of 10. for SYSGEN. >; >; ie >REM ...AT. >; >INS $BIGIND/PRI=10. >; >@ <EOF> > >asn lb:=tk: >asn lb:=mp: >set /uic=[1,24] >run $bigtkb INS -- PARTITION PAR14K NOT IN SYSTEM, DEFAULTING TO GEN TKB>@bigindbld TKB>^Z >asn =tk: >asn =mp: |
This same procedure was demonstrated in the prior SYSGEN Phase I from 2010. That procedure is repeated here with a few variations. The focus of this discussion is about variations as perhaps a better example of SYSGEN. The full transcript is available in prepgen_console.log.
>all dl1: >mou dl1:rsxm26 >asn dl1:=sy: >rem ...at. >ins $bigind/pri=10. INS -- WARNING - PRIVILEGED TASK OVERMAPS I/O PAGE >set /uic=[200,200] >@sysgen >; >; RSX-11M Ver. 3.2 BL26 System Generation 3.2.3a done on 28-MAR-19 at 16:10:19 >; >; Copyright (C) 1979 Digital Equipment Corporation, Maynard Mass. >; >; RL01 distribution kit >; >* 1. Inhibit MCR command lines (Type <ESC> for explanation)? [Y/N]:y >* 3. Use saved or canned answer file for input responses? [Y/N]: >* 10. Save responses (i.e.: create SYSSAVED.DAT)? [Y/N]:y >* 11. UIC for SYSSAVED files if not [200,200] [S]: >* 12. UIC for SYSGEN command files if not [200,200] [S]: >* 14. Device, when ready, for Executive sources (ddu:) [S]: dl2: >; ;;; A sequence of interaction was deleted here. >* 30. Rotating pattern in data lights? [Y/N]:y ;;; A sequence of interaction was deleted here. >; >; Enter [L/R,] vector, CSR, number of drives for: >; >* 3. DD controller 0 [D: 300,176500] [S]: ,,2 >; ;;; A sequence of interaction was deleted here. >; Enter [L/R,] vector, CSR, # drives, O=offset recovery/NO=no offset rec. for: >; >* 13. DM controller 0 [D: 210,177440,,O] [S]: ,,8,NO >* 54. Contr 0 unit 0. is an RK06/RK07 [D: RK06] [S]: >* 54. Contr 0 unit 1. is an RK06/RK07 [D: RK06] [S]: >* 54. Contr 0 unit 2. is an RK06/RK07 [D: RK06] [S]: >* 54. Contr 0 unit 3. is an RK06/RK07 [D: RK06] [S]: RK07 >* 54. Contr 0 unit 4. is an RK06/RK07 [D: RK06] [S]: RK07 >* 54. Contr 0 unit 5. is an RK06/RK07 [D: RK06] [S]: RK07 >* 54. Contr 0 unit 6. is an RK06/RK07 [D: RK06] [S]: RK07 >* 54. Contr 0 unit 7. is an RK06/RK07 [D: RK06] [S]: RK07 >; ;;; A sequence of interaction was deleted here. >; Enter vector, CSR, highest line number <0 to 7> [, answer speed] for: >; >* 24. DZ controller 0 [D: ,,,0] [S]: 300,160100,7,9600 >* 24. DZ controller 1 [S]: 310,160110,7,9600 >; SGN -- Illegal trailing characters or extra parameters "9600" -- RETRY >* 24. DZ controller 1 [S]: 310,160110,7 >; >* EOS * Do you want to: |
The saved answer file is written out as SYSGEN questions are asked. Since the wrong answers were near the end of the SYSGEN Phase I dialog, corrected lines are near the end of the SYSSAVED.DAT file. Errors are flagged in this copy of SYSSAVED.DAT. Answers were corrected in two passes with the EDI line editor. The saved answer file is renamed as SYSSAVED.CMD to be usable by SYSGEN and older copies are deleted.
>;;; Fix saved Sysgen Phase I answers >asn dl1:=sy: >set /uic=[200,200] >edi syssaved.dat [00036 LINES READ IN] [PAGE 0] * .ENABLE GLOBAL *pl $2DM0 [00036 LINES READ IN] [00036 LINES READ IN] [00028 LINES READ IN] .SETS $2DM0 "" * .SETS $3DM0 "RK07" *ch /RK07// .SETS $3DM0 "" *ex [EXIT] >edi syssaved.dat [00036 LINES READ IN] [PAGE 0] *pl $$DZ [00036 LINES READ IN] [00036 LINES READ IN] [00028 LINES READ IN] .SETS $$DZ0 "300,160100,7,9600" *ch /,9600/ .SETS $$DZ0 "300,160100,7" *ed [EXIT] > >;;; Make saved answers usable as input to SYSGEN >pip syssaved.cmd=syssaved.dat >pip SYSSAVED.DAT;*/de > |
There was one more problem. It was only discovered near the end of SYSGEN Phase II when this error was displayed.
>pip rsx11m.sys/co/bl:498.=rsx11m.tsk >asn sy:=lb: >ins db0:vmr >vmr @sysvmr VMR -- INTERRUPT VECTOR ALREADY IN USE LOA DD: |
Both the DECtape-II (DD:) and the first DZ11 (TT1:) were given the vector at 300. Both devices use floating vectors. From the simh device configuration printout, one can see the tape has priority; it uses 300. The DZ11's use vectors at 310 and 320. I made a mistake by not verifying vector and CSR when originally answering the question about the DZ11's.
>edi SYSSAVED.CMD [00036 LINES READ IN] [PAGE 0] *pl $$DZ [00036 LINES READ IN] [00036 LINES READ IN] [00028 LINES READ IN] .SETS $$DZ0 "300,160100,7" *ch /300/310/ .SETS $$DZ0 "310,160100,7" * .SETS $$DZ1 "310,160110,7" *ch /310/320/ .SETS $$DZ1 "320,160110,7" *ed [EXIT] > |
There are only a few questions to answer. And there is no need to create another saved answers file. Since the PiDP is much faster than a PDP-11/70, running SYSGEN Phase I with saved answers only takes a few minutes. The full log is in rerun_ph_I_II_console.log.
>rem ...at. >ins $bigind/pri=10. INS -- WARNING - PRIVILEGED TASK OVERMAPS I/O PAGE >asn dl1:=sy: >set /uic=[200,200] >@sysgen >; >; RSX-11M Ver. 3.2 BL26 System Generation 3.2.3a done on 30-MAR-19 at 14:50:26 >; >; Copyright (C) 1979 Digital Equipment Corporation, Maynard Mass. >; >; RL01 distribution kit >; >* 1. Inhibit MCR command lines (Type <ESC> for explanation)? [Y/N]: >* 2. Have you made a copy of the distribution kit? [Y/N]:y >* 3. Use saved or canned answer file for input responses? [Y/N]:y >* 4. Undefined answer wakeup? [Y/N]:y >* 5. Use saved host configuration? [Y/N]:y >* 6. Use saved peripheral configuration? [Y/N]:y >* 7. Skip end of section (EOS) breakpoints? [Y/N]:y >* 8. Skip end of execution (EOX) breakpoints? [Y/N]:y >* 10. Save responses (i.e.: create SYSSAVED.DAT)? [Y/N]: >* 11. UIC for SYSSAVED files if not [200,200] [S]: >* 12. UIC for SYSGEN command files if not [200,200] [S]: >* 13. Clean up files from previous GENs? [Y/N]:y >; >; Saved-answer file created 28-MAR-19 AT 16:11:29 by SYSGEN version 3.2.3a >; >* 14. Device, when ready, for Executive sources (ddu:) [S]: dl2 >; >MOU DL2:MAPSRC >ASN DL2:=LB: >; >SET /UIC=[1,1] >PIP [1,20]RSXBLD.CMD;*/DE/NM,SYSPAR;* >PIP [1,24]RSXBLD.CMD;*/DE/NM,TTDRVBLD;*,SYSPAR;* >PIP [1,50]SYSVMR.CMD;*/DE/NM,[1,54]SYSVMR;* >PIP [11,20]*.OBJ;*/DE/NM,*.UDC;*,*.ICR;*,*.IDS;*,*.PCS;* >PIP [11,20]RSXASM.CMD;*/DE/NM,RSXDRVASM;*,RSXBLD;* >PIP [11,24]*.OBJ;*/DE/NM,*.UDC;*,*.ICR;*,*.IDS;*,*.TTY;*,*.PCS;* >PIP [11,24]RSXASM.CMD;*/DE/NM,RSXDRVASM;*,RSXBLD;* >PIP [11,10]SYSTB.MAC;*/DE/NM,ICTAB;*,RSXMC;*,[200,200]SGNPARM.CMD;* >PIP [11,10]RSXASM.CMD;*/DE/NM,RSXDRVASM;*,RSXBLD;* >PIP /FR DL1: HAS 5052. BLOCKS FREE, 5188. BLOCKS USED OUT OF 10240. LARGEST CONTIGUOUS SPACE = 3493. BLOCKS >SET /UIC=[11,10] >; >; Target configuration >; >; Processor:11/70 Memory Size:128K,Mapped System:RSX-11M >; >; Host configuration >; >; Executive Options >; >; Terminal driver options >; >; Thinking ... >; >; End of Executive option generation at 14:51:22 on 30-MAR-19 >; >; 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: CR, LP, PR, PP >; >; Disks: DB, DD, DK, DL, DM, DT, DY >; >; Tapes: CT, MM >; >; Non-physical (pseudo) devices: CO, TT, NL, TI, CL, LB, SY >; >SET /UIC=[1,24] ! Creating TTDRVBLD.CMD >SET /UIC=[11,10] >; End of interrupt vector area has been set to 400 >; >; >; Create Executive build files >; >PIP RSXMC.MAC=LB:RSXMC0.MAC/AP >; >; Assemble the Executive >; >PIP [11,24]/NV=RSXASM.CMD,RSXDRVASM.CMD >PIP RSXASM.CMD;0/DE,RSXDRVASM;0 >INS SY:$BIGMAC INS -- PARTITION PAR14K NOT IN SYSTEM, DEFAULTING TO GEN >;SET /COFFEEBREAK=TI: Start of Executive assembly at 14:51:44 on 30-MAR-19 >SET /UIC=[11,24] >MAC @RSXASM >;SET /NOCOFFEEBREAK=TI: Executive assembly ended at 14:53:32 on 30-MAR-19 >;SET /COFFEEBREAK=TI: Start of device drivers assembly at 14:53:32 on 30-MAR-19 >SET /UIC=[11,24] >MAC @RSXDRVASM >;SET /NOCOFFEEBREAK=TI: Device drivers assembly ended at 14:55:06 on 30-MAR-19 >REM MAC >; >; Prepare for task building >; >PIP RSX.OBS=*.OBJ >PIP *.OBJ;*/DE/NM >PIP RSX11M.OBJ/RE=RSX.OBS >PIP TTDRV.OBJ=*.TTY >PIP *.TTY;*/DE/NM >SET /UIC=[1,24] >PIP /NV=[11,10]RSXBLD.CMD >; >; >; End of SYSGEN phase I at 14:55:11 on 30-MAR-19 >; -- To continue type: @[200,200]SYSGEN2 >; >SET /UIC=[200,200] >@ <EOF> |
All of SYSGEN Phase II console interaction is recorded in rerun_ph_I_II_console.log.
Create a directory for maps. Then save some of the driver sources. To provide enough space on the MAPSRC RL01 disk, the RSX-11M System Generation and Management Guide suggests removing infrequently used driver sources.
>;;; create dirs for maps and exec sources >ufd db:[1,34] >ufd db:[11,10] > >;;; remove some driver sources to make room on MAPSRC disk >pip PIP>db:[11,10]/nv/fo/cd=dl2:[11,10]ADDRV.MAC;,AFDRV.MAC;,ARDRV.MAC; PIP>db:[11,10]/nv/fo/cd=dl2:[11,10]ICDRV.MAC;,IPDRV.MAC;,ISDRV.MAC; PIP>db:[11,10]/nv/fo/cd=dl2:[11,10]LADRV.MAC;,LSDRV.MAC;,UDDRV.MAC; PIP>db:[11,10]/nv/fo/cd=dl2:[11,10]XBDRV.MAC;,XLDRV.MAC;,XMDRV.MAC; PIP>db:[11,10]/nv/fo/cd=dl2:[11,10]XPDRV.MAC;,XQDRV.MAC;,XUDRV.MAC; PIP>db:[11,10]/nv/fo/cd=dl2:[11,10]XWDRV.MAC; PIP>dl2:[11,10]ADDRV.MAC;*/de,AFDRV.MAC;*,ARDRV.MAC;* PIP>dl2:[11,10]ICDRV.MAC;*/de,IPDRV.MAC;*,ISDRV.MAC;* PIP>dl2:[11,10]LADRV.MAC;*/de,LSDRV.MAC;*,UDDRV.MAC;* PIP>dl2:[11,10]XBDRV.MAC;*/de,XLDRV.MAC;*,XMDRV.MAC;* PIP>dl2:[11,10]XPDRV.MAC;*/de,XQDRV.MAC;*,XUDRV.MAC;*,XWDRV.MAC;* PIP>^Z > |
SYSGEN2.CMD does most of the work. But an error occurs when creating the object library for the executive modules. Autopatch and/or the additional device drivers in the new configuration require more space in that library. Manually rebuilding the library with slightly larger space allocations allows SYSGEN to proceed.
>set /uic=[200,200] >@sysgen2 >; >; RSX-11M Version 3.2 System Generation Phase II started 30-MAR-19 at 16:55:33 >; >; Copyright (C) 1979 Digital Equipment Corporation, Maynard Mass. >; >* 1. In what UIC is SGNPARM.CMD if not [200,200] [S]: >; >; RL01 distribution kit SYSGEN versions 3.2.3a / 2:3.2.2d for RSX11M BL26 >; >; Continuation from SYSGEN phase I done on 30-MAR-19 at 14:55:10 >; >; The map device ( DB: ) must already be mounted with UIC [1,34]. >; If it is not, ^Z SYSGEN2 at the next question and do so. >; >* 2. Expanded comments desired for SYSGEN phase II? [Y/N]: >* 3. Is SYSGEN still running on-line? [Y/N]:y >* 5. If not in DL2: enter object files device when ready (ddu:) [S]: >; >MOU DL2:MAPSRC >ASN DL2:=LB: >ASN SY:=TK: >PIP /FR DL1: HAS 4684. BLOCKS FREE, 5556. BLOCKS USED OUT OF 10240. LARGEST CONTIGUOUS SPACE = 3493. BLOCKS >* 6. Have you already built the libraries, the Exec, and the loadable drivers? [Y/N]: >; >; Start of Executive and driver build phase at 16:56:10 on 30-MAR-19 >; >; >; Create system libraries at 16:56:10 on 30-MAR-19 >; >INS $LBR >SET /UIC=[1,1] >PIP ANSLIB.OLB/NV=SYSLIB.OLB >LBR ANSLIB/RP=LB:FCSMTA MODULE "ANSPAD" REPLACED ;;; A sequence of "REPLACED" messages was deleted here. MODULE "WTWAIT" REPLACED >SET /UIC=[1,24] >PIP RSX11M.OLB;*/DE/NM,TTDRV;* >LBR RSX11M/CR:80.:640.:256.=[11,24]RSX11M.OBJ LBR -- *FATAL*-EPT OR MNT EXCEEDED IN RSX11M.OBJ;1 >LBR TTDRV/CR:52.:256.:64.=[11,24]TTDRV.OBJ >PIP LB:/NV=LB:MCR.OLB >LBR LB:MCR/RP=LB:MCRTTFD MODULE "SETOV " REPLACED MODULE "SPROV " REPLACED MODULE "SDSOV " REPLACED >INS SY:$BIGTKB INS -- PARTITION PAR14K NOT IN SYSTEM, DEFAULTING TO GEN >; >; Taskbuild the Executive and the terminal driver at 16:56:21 on 30-MAR-19 >; >PIP [1,34]*.*;*/DE/NM >TKB @RSXBLD TKB -- *FATAL*-LIBRARY FILE RSX11M.OLB;1 HAS INCORRECT FORMAT >; >* EOX * Did the Executive build successfully? [Y/N]:n >; >; We will pause now so that you can correct the problem. After >; resuming, we will build the Executive again. AT. -- PAUSING. TO CONTINUE TYPE "RES ...AT." ;;; Recreate RSX11M.OLB with larger space allocations >pip rsx11m.olb;*/de >lbr rsx11m/cr:83.:660.:265.=[11,24]rsx11m.obj >res ...at. AT. -- CONTINUING > >PIP [1,34]*.*;*/DE/NM >TKB @RSXBLD >; >* EOX * Did the Executive build successfully? [Y/N]:y >; >SET /UIC=[1,54] >PIP LB:/NV=RSX11M.STB >SET /UIC=[1,24] >TKB @TTDRVBLD >; >* EOX * Did the terminal driver build successfully? [Y/N]:y >; >* 10. List Executive map? [Y/N]: >; >; Build Loadable drivers >; >* 6. Device for driver's maps [D: NL:] [S]: db: >* 9. Build all selected loadable drivers into DRVPAR? [Y/N]:y >; >TKB @[200,200]CODRVBLD >PIP [200,200]CODRVBLD.CMD;*/DE >PIP [1,54]CODRV.STB/TR ;;; Similar commands to build the other drivers are not shown here. >; >; End of library, Executive and driver build phase at 17:32:26 on 30-MAR-19 >; |
SYSGEN2.CMD is still running. It next builds the privileged tasks.
>; >; Start task building privileged tasks at 17:32:26 on 30-MAR-19 >; >* 11. FCP desired (Type |
SYSGEN2.CMD is still running. It pauses at this point so the administrator can manually create the file containing the generated system. SYSGEN assumes the generated system will be on the baseline disk.
Contrary to that assumption, the RP06 disk that now is inserted into drive DB2: will become the new system disk. That volume gets initialized and all relevant files are copied there. Then the file RSX11M.SYS is created on the target RP06 disk.
>; >REM TKB >ASN LB:=SY: >ASN =LB: >ASN =SY: >ASN DL1:=SY: >ASN DL2:=LB: >SET /UIC=[1,54] >PIP /FR DL1: HAS 3517. BLOCKS FREE, 6723. BLOCKS USED OUT OF 10240. LARGEST CONTIGUOUS SPACE = 3463. BLOCKS >; >; SGN -- SYSGEN will now pause to allow you to create your >; RSX11M.SYS file using the following example. Ideally >; your system it should occupy the same number of blocks >; as indicated in the example. >; >; PIP RSX11M.SYS/NV/CO/BL:498.=RSX11M.TSK AT. -- PAUSING. TO CONTINUE TYPE "RES ...AT." >;;; Create target disk to receive generated system. > >;;; Initialize and mount the target disk >set /uic=[1,1] >all db2: >asn db2:=sy: >ini sy:rsxm26patchE/lru=7/mxf=25000 >mou sy:rsxm26patchE > >;;; Copy files for sysgen phase III >all dl3: >mou dl3:rlutil >pip sy:[*,*]/uf/fo/cd/nv=dl3:[*,*]*.* > >;;; Copy mapped source files >pip sy:[*,*]/uf/fo/cd/nv=db0:[11,10]*.*,dl2:[*,*]*.* >pip sy:[*,*]*.*/pu > >;;; Copy baseline files >pip sy:[*,*]/uf/fo/cd/nv=dl1:[*,*]*.* >pip sy:[*,*]*.*/pu > >;;; Copy listings, maps, customized startup file >pip sy:[*,*]/uf/fo/cd/nv=db0:[11,34]*.*,[1,34]*.*,[1,2]startup.cmd > >;;; Copy the system accounts file >pip sy:[0,0]/fo/cd=db0:[0,0]rsx11.sys >pip sy:[*,*]*.*/pu > >;;;Create bootable system image file >set /uic=[1,54] >pip rsx11m.sys;*/de >pip rsx11m.sys/co/bl:498.=rsx11m.tsk > >res ...at. |
SYSGEN2.CMD is still running. The final step is to load drivers and install privileged tasks into the bootable system file. This is necessary to create a complete system that is viable when loaded into memory by a bootstrap.
The RSX-11M System Generation and Management Guide recommends that the driver for the target system disk should be the first to be loaded into DRVPAR. In response to answering YES to question 19, SYSGEN2.CMD launches the EDI text editor. After verifing that DB: is loaded first, just exit the editor without changing SYSVMR.CMD.
AT. -- CONTINUING > >; >* 19. Edit SYSVMR.CMD? [Y/N]:y >; >EDI SYSVMR.CMD [00036 LINES READ IN] [PAGE 0] *pf LOA LOA TT: * SET /MAIN=DRVPAR:*:*:SYS * LOA DB: *kill EDI>^Z [EXIT] >ASN SY:=LB: >; >; You will have to run VMR after the command file exits >; since we dont know what is the real system volume. >; >; When the indirect file exits, boot in your target system, >; set the date and time, and save the system with a bootstrap. >; When your system reboots itself, purge the old task files. >; >; >; An alternate version of SYSLIB called ANSLIB has been created >; on the RSXM26 disk to take into account ANSI support and Big-buffering. >; >; Since you have selected ANSI magtape support you may want to >; rebuild PIP and other utilities in SYSGEN phase III to take >; advantage of ANSI support. Note this will cause an increase >; in the size of the utility compared with the non-ANSI version. >; >; Don't forget to create accounts after saving your system >REM LBR >ASN =LB: >; >; End of SYSGEN phase II at 15:30:08 on 31-MAR-19 >; >@ <EOF> > >asn db2:=lb: >asn db2:=sy: >ins db:vmr >vmr @sysvmr VMR -- INSTALLED TASKS MAY NO LONGER FIT IN PARTITION SET /TOP=DRVPAR:-* POOL=1200:5818.:05818. ;;; Printout of partitions, tasks & drivers by VMR are not shown here. > |
Need to type ";g" to proceed from the XDT debugger prompt. After a few settings, the system is saved back to disk. The /WB switch on the SAV command writes the boot block making this system the one that will get booted when this disk is booted.
Once again the privileged task BIGIND needs to be built to correspond to the new executive. Finally the system is shutdown to allow backup and moving the system disk to DB: unit 0.
> >boo rsx11m XDT: 26 XDT>;g RSX11M V3.2 BL26 >TIM 31-MAR-19 15:38 >SET /LOWER=TT0: >set /nologon >sav/wb RSX-11M V3.2 BL26 1920K MAPPED >RED DB2:=SY: >RED DB2:=LB: >MOU DB2:RSXM26PATCHE >@DB2:[1,2]STARTUP >* Enter date and time ( dd-mmm-yy hh:mm ) [S]: 15:39 >TIM 15:39 >@ <EOF> >tim 15:39:04 31-MAR-19 > >;;; Build BIGIND for this system >asn lb:=tk: >asn lb:=mp: >set /uic=[1,24] >run $bigtkb INS -- PARTITION PAR14K NOT IN SYSTEM, DEFAULTING TO GEN TKB>@bigindbld TKB>^Z >asn =tk: >asn =mp: > >;;; Shutdown to allow re-arranging disks >run $shutup |
During SYSGEN Phase III, nonprivileged tasks may be built. Nonprivileged tasks do not map to the executive address space. For this reason a SYSGEN does not imply that nonprivileged tasks need to be rebuilt to match the new executive. There are a few reasons to build a nonprivileged task:
First SYSGEN3 is run with ANSLIB.OLB as the default library to rebuild PIP. Another directory entry is created so the name SYSLIB.OLB points to the file for ANSLIB.OLB. After building PIP that directory entry is removed.
All of SYSGEN Phase III console interaction is recorded in ph_III_console.log.
>pip lb:[1,1]*.olb/li DIRECTORY DB0:[1,1] 2-APR-19 13:19 EXELIB.OLB;2 24. C 26-MAY-79 13:52 VMLIB.OLB;2 16. C 26-MAY-79 13:52 SYSLIB.OLB;2 188. 26-MAY-79 13:52 ANSLIB.OLB;1 214. 31-MAR-19 15:08 TOTAL OF 442./443. BLOCKS IN 4. FILES >pip lb:[1,1]syslib.olb/en/nv=lb:[1,1]anslib.olb >pip lb:[1,1]*.olb;*/li DIRECTORY DB0:[1,1] 2-APR-19 13:22 SYSLIB.OLB;3 214. 31-MAR-19 15:08 EXELIB.OLB;2 24. C 26-MAY-79 13:52 VMLIB.OLB;2 16. C 26-MAY-79 13:52 SYSLIB.OLB;2 188. 26-MAY-79 13:52 ANSLIB.OLB;1 214. 31-MAR-19 15:08 TOTAL OF 656./657. BLOCKS IN 5. FILES >set /uic=[200,200] >asn lb:=sy: >@sysgen3 >; >; SYSGEN PART 3 |
With SYSLIB.OLB restored, all the other tasks are built by a second run of SYSGEN3. This time EDT will be modified to use the message file on LB: instead of on SY:.
>asn lb:=sy: >set /uic=[200,200] >@sysgen3 >; >; SYSGEN PART 3 |
Although the system is generated, some customization will make it more convenient to use.
STARTUP.CMD is automatically run when RSX boots. It invokes the other command files shown here.
.ENABLE SUBSTITUTION .ASKS TIM Enter date and time ( dd-mmm-yy hh:mm ) TIM 'TIM' @LB:[1,2]SETCOLOG set /pub=db1: mou db1:USERDIRS .IFT |
SETCOLOG.cmd starts the Console Output Task and routes messages to the default logfile [1,4]CONSOLE.LOG instead of to TT0:. Without the delay, the COT... task would crash when "set /nocoterm" was processed.
; SetCOlog.cmd - hush most console messages set /logfile .; allow COT... to become ready for another command .DELAY 1S set /nocoterm |
SetTTYs.cmd sets the characteristics of all terminals and the printer. Due to ".ENABLE QUIET" echo of most of the commands this procedure executes is suppressed,
; SetTTYs.cmd set terminal characteristics set /term=TT0:LA120 set /buf=TT0:132. .ENABLE QUIET set /crt=tt0: .; set /fdx=tt0: set /formfeed=tt0: .; set /hfill=tt0:0 set /lines=tt0:66. set /lower=tt0: .; set /typeahead=tt0: .; set /wrap=tt0: .; set /buf=lp0:132. .; .ENABLE SUBSTITUTION .; Apply common settings to terminals 1 through TERMNO .SETN TERMNO 20 .10: .GOSUB VT100 .DEC TERMNO .IF TERMNO > 0 .GOTO 10 .; .EXIT .; .VT100: .BEGIN .; Subroutine to set user terminal TT |
InstTasks.cmd installs the unprivileged tasks. These are not installed via VMR to avoid pool fragmentation if tasks rebuilt multiple times.
; InstTasks.cmd install nonprivileged tasks .IFNINS BRU ins $bru .IFNINS CMP ins $cmp .IFNINS CRF... ins $crf .IFNINS DMP ins $dmp .IFNINS DSC ins $dsc .IFNINS EDI ins $edi .IFNINS EDT ins $edt .IFNINS FLX ins $flx .IFNINS FTB ins $ftb .IFNINS IOX ins $iox .IFNINS LBR ins $lbr .IFNINS MAC ins $bigmac .IFNINS PAT ins $pat .IFNINS PIP ins $pip .IFNINS PSE ins $pse .IFNINS SLP ins $slp .IFNINS SYE ins $sye .IFNINS TKB ins $bigtkb .IFNINS ZAP ins $zap |
QMGSETUP.cmd creates and starts the printer queues.
; QmgSetup.cmd - setup print queues .IFNINS QMG... ins $qmg/pri=70 .IFNINS LPP0 ins $lpp/pri=70 .IFNINS PRT... ins $qmgprt .IFNINS ...PRI ins $qmgcli/task=...pri .IFNINS ...QUE ins $qmgcli/task=...que que /start:qmg que lp:/spool/flag:1/form:0 que lp:/assign:print |
SHUTUP.CMD is automatically run when RSX is shutdown. This command removes old copies of the console log.
pip lb:[1,4]console.log/pu:5 |
A resident library is a collection of commonly used re-entrant subroutines that reside in memory. The use of a resident library allows any number of tasks to share a single copy of the routines in memory. This ability to share common code reduces the total physical memory requirements of the tasks linked to the library. Resident libraries also reduce the size of the task files on the disk since the memory resident routines do not get included in the files for tasks linked to the resident library.
After creating the FCSRES File Control Services resident library, one could edit the DEC supplied taskbuild command files and rebuild the privileged and utility tasks. (There are files on the RSX SIG DECUS tapes that make it easier to use FCSRES with the DEC-supplied tasks.) But here, the resident FCSRES is being created mostly for use by user-written applications.
A source file, [200,200]FCSRES.MAC is provided in the RSX-11M distribution kit. Comments in that file contain the documentation about FCSRES. For convenience, file [200,200]fcsresbld.cmd was manually created before these steps. Contents of [200,200]fcsresbld.cmd appear in the transcript below.
>set /uic=[200,200] >mac lb:fcsres=lb:fcsres >pip ti:=fcsresbld.cmd fcsres/-hd/mm/pi,fcsres,fcsres=[200,200]fcsres / stack=0 par=fcsres:0:20000 task=FCSRES // >asn lb:=sy: >set /uic=[1,1] >tkb @[200,200]fcsresbld > >pip fcsres.*/li DIRECTORY DB0:[1,1] 6-APR-19 15:05 FCSRES.TSK;1 18. C 06-APR-19 15:05 FCSRES.MAP;1 3. 06-APR-19 15:05 FCSRES.STB;1 3. 06-APR-19 15:05 TOTAL OF 24./28. BLOCKS IN 3. FILES |
Resident libraries need to reside in a common partition. A new partition will need to be created. This is accomplished by creating a new bootable system image using VMR, a repeat of the steps performed at the end of SYSGEN Phase II. First the SYSVMR.CMD file is modified to add partition FCSRES and install the FCSRES library into that partition.
>set /uic=[1,54] >asn lb:=sy: >edi sysvmr.cmd [00036 LINES READ IN] [PAGE 0] *pl FCPPAR SET /MAIN=FCPPAR:*:500:SYS *i SET /MAIN=FCSRES:*:200:COM *pl FCP INS FCPRO2 ! INSTALL FILE SYSTEM *i INS [1,1]FCSRES ! INSTALL MEMORY RESIDENT FCS LIBRARY *ex [EXIT] > >pip rsx11m.sys/nv/co/bl:498.=rsx11m.tsk >ins vmr >vmr @sysvmr ;;; Printout by VMR is not shown here. > >boo rsx11m XDT: 26 XDT>;g RSX11M V3.2 BL26 >TIM 6-APR-19 17:10 >SET /LOWER=TT0: >set /nologon >sav /wb |
To use this library, tasks need to be built with this TKB option: LIBR=FCSRES:RO
Because the library code is position independent, any APR may be use to map this library into a task's virtual address space.
RSX-11M includes a help facility that depends upon the presence of *.HLP files in LB:[1,2]. These commands show that help is not present, creates the help files and demonstrates that help is functioning. The procedure for enabling help is described in the RSX-11M System Generation and Management Guide.