|
------------------------------------------------------------------------------- |
|
SYSGEN |
|
http://bitsavers.trailing-edge.com/pdf/dec/pdp11/rsx11/RSX11Mplus_V4.x/2a/AA-H431H-TC_RSX-11M-PLUS_4.3_System_Generation_and_Installation_Guide_Jan90.pdf |
|
|
|
NOTE: because I chose to rebuild some stuff, this sysgen is super slow |
|
------------------------------------------------------------------------------- |
|
PDP-11 simulator V4.0-0 Current REALCONS build Jan 16 2019 |
|
Disabling XQ |
|
Eth: opened OS device tap-simh1 |
|
XU address=17774510-17774517, vector=120, BR5, MAC=AA:00:04:00:0C:39 |
|
type=DEUNA, throttle=disabled |
|
attached to tap:tap-simh1 |
|
RP0: 'RP06.000' Contains an ODS1 File system |
|
RP0: Volume Name: RSX11MPBL87 Format: DECFILE11A Sectors In Volume: 340670 |
|
pdp11.ini-60> ATTACH DZ 12023 |
|
Listening on port 12023 |
|
sim> boot rp |
|
|
|
|
|
|
|
RSX-11M-PLUS V4.6 BL87 1920.KW System:"Baseline" |
|
>RED DB:=SY: |
|
>RED DB:=LB: |
|
>RED DB:=SP: |
|
>MOU DB0:"RSX11MPBL87" |
|
>@[2,54]BASTART.CMD |
|
>SET /CRASHDEV=MM0: |
|
SET -- Crash device MM000: has been successfully loaded |
|
>; |
|
>* Do you wish to see the Installation Notes? [Y/N]: n |
|
>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 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. |
|
>; |
|
>; |
|
>* Please enter time and date (HH:MM DD-MMM-YYYY) [S]: 23:16 19-jan-2019 |
|
>TIME 23:16 19-jan-2019 |
|
>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 LP0:/SP/FL:2/LOWER/FO:0 |
|
>QUE BAP0:/BATCH |
|
>QUE LP0:/AS:PRINT |
|
>QUE BAP0:/AS:BATCH |
|
>@ <EOF> |
|
>set /uic=[200,200] |
|
>@sysgen |
|
>; |
|
>; RSX-11M-PLUS V4.6 BL87 SYSGEN |
|
>; |
|
>; Copyright (c) 1995-1999 by Mentec Inc., U.S.A. |
|
>; |
|
>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 19-JAN-19 at 23:16 |
|
>;=================================================== |
|
>; |
|
>; |
|
>; |
|
>; 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]: y |
|
>; |
|
>; 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. |
|
>; |
|
>; If you have performed a SYSGEN (or PREPGEN) before, you can use the |
|
>; saved answer file created during that SYSGEN as input to this SYSGEN. |
|
>; SYSGEN uses the saved answers as your responses to the Executive |
|
>; questions. |
|
>; |
|
>* 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]: |
|
>; |
|
>; A PREPGEN allows you to answer all the SYSGEN questions and create |
|
>; saved answer files without actually generating a system: no MCR |
|
>; commands are executed, no files are deleted, and the Executive is |
|
>; not assembled or built. |
|
>; |
|
>; After you have successfully completed a PREPGEN, you can perform a |
|
>; SYSGEN using the saved answer files from the PREPGEN. The SYSGEN |
|
>; will then run unattended. |
|
>; |
|
>* SU080 Do you want to do a PREPGEN? [Y/N D:N]: |
|
>; |
|
>; You should have a disk spinning in a disk drive which is a copy of |
|
>; your distribution kit. This is your target system disk, the disk on |
|
>; which you will perform the SYSGEN. This disk should already be |
|
>; mounted with the MOUNT command so that you have access to it. |
|
>; |
|
>; Enter the name of the drive containing this disk in the form ddnn:, |
|
>; i.e., DB2:. |
|
>; |
|
>* 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: |
|
>; |
|
>; The Autoconfigure procedure will attempt to determine your peripheral |
|
>; configuration by examining the device registers contained in the I/O |
|
>; page. Autoconfigure will print a table of those devices which it |
|
>; finds. You can either use the Autoconfigure results directly, or |
|
>; you can override them. |
|
>; |
|
>; If you answer Yes to the following question, SYSGEN will run |
|
>; Autoconfigure. If no results are printed within a few minutes, |
|
>; Autoconfigure has failed and you should reboot your system and |
|
>; restart the SYSGEN. Next time do not use Autoconfigure. |
|
>; |
|
>; Note: If you have already run a PREPGEN or SYSGEN during which you |
|
>; ran Autoconfigure, and you are using the saved answer files from that |
|
>; GEN, it is not necessary to run Autoconfigure again. |
|
>; |
|
>* SU100 Do you want to run Autoconfigure on the host system |
|
>* hardware? [Y/N D:N]: y |
|
>; |
|
>; Running Autoconfigure: |
|
>; |
|
>INS $ACF |
|
>ACF |
|
>INS $ACO |
|
>ACO SHOW |
|
Processor Type: 11/70 Memory Size: 1920. Kw |
|
|
|
Options: |
|
|
|
Floating Point Processor (FP11) |
|
Extended Instruction Set (EIS) |
|
Extended (22-Bit) Addressing |
|
Switch Register (SWR) |
|
Display Register |
|
Cache Memory |
|
Parity Memory |
|
|
|
Name Vector CSR Unit Type Remark |
|
RHA 254 176700 Mixed MASSBUS devices |
|
0 RP06 |
|
1 RP06 |
|
2 RM03 |
|
3 RM03 |
|
4 RM03 |
|
5 RM03 |
|
6 RM03 |
|
7 RM03 |
|
DLA 160 174400 |
|
0 RL02 |
|
1 RL02 |
|
2 RL01 |
|
3 RL01 |
|
MSA 224 172522 |
|
LPA 200 177514 |
|
PPA 074 177554 |
|
PRA 070 177550 |
|
YLA 060 177560 |
|
YZA 300 160100 |
|
|
|
>ACO SYSGEN |
|
>; |
|
>; If you choose to override the Autoconfigure results, SYSGEN asks all |
|
>; the peripheral configuration questions using the Autoconfigure |
|
>; results as defaults for the questions. This allows you to examine |
|
>; and change the Autoconfigure results. |
|
>; |
|
>; If you do not choose to override the Autoconfigure results, SYSGEN |
|
>; uses the Autoconfigure results as the responses to the appropriate |
|
>; questions, and does not ask you those questions. |
|
>; |
|
>* SU110 Do you want to override the Autoconfigure results? [Y/N D:N]: y |
|
>; |
|
>; You can: |
|
>; |
|
>; o do a complete SYSGEN |
|
>; |
|
>; o continue a previous SYSGEN from where you left off |
|
>; |
|
>; o do an individual section of SYSGEN |
|
>; |
|
>; |
|
>; A complete SYSGEN consists of: |
|
>; |
|
>; Choosing Executive options |
|
>; Choosing Peripheral Configuration |
|
>; |
|
>; Assembling the Executive and Drivers |
|
>; |
|
>; Building the Executive and Drivers |
|
>; Building the Privileged Tasks |
|
>; Building the Nonprivileged Tasks |
|
>; |
|
>; Creating the System Image File |
|
>; |
|
>; If you do not choose to do a complete SYSGEN, you can continue |
|
>; a previous SYSGEN from where you left off or do an individual |
|
>; section of SYSGEN. |
|
>; |
|
>* SU120 Do you want to do a complete SYSGEN? [Y/N D:Y]: 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 19-JAN-19 at 23:20 |
|
>;====================================================== |
|
>; |
|
>; |
|
>; |
|
>; The answers to the questions in this section are put in the saved |
|
>; answer file [200,200]SYSGENSA1.CMD. |
|
>; |
|
>; You may now enter a comment describing the system you are building. |
|
>; This comment is included in the SYSGENSA1 saved answer file for |
|
>; documentation, and is printed out when the saved answer file is |
|
>; later used as input. |
|
>; |
|
>; 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.]: |
|
>; |
|
>; RSX-11M-PLUS may be run on the following PDP-11 processors: |
|
>; |
|
>; 11/23-PLUS (also called MicroPDP-11/23 and 11/23-B) |
|
>; 11/24 |
|
>; 11/44 |
|
>; 11/53 |
|
>; 11/70 |
|
>; 11/73 (also called MicroPDP-11/73) |
|
>; 11/83 (also called MicroPDP-11/83) |
|
>; 11/93 (also called MicroPDP-11/93) |
|
>; 11/84 |
|
>; 11/94 |
|
>; |
|
>; M70,80,90,100 MENTEC modules (treated as an 11/83) |
|
>; M11 processor (MENTEC) |
|
>; |
|
>; LSI-11/73 |
|
>; |
|
>* CE010 What is your target processor type? [S R:3.-12. D:"11/70"]: |
|
>; |
|
>; The following RSX-11M-PLUS Executives may be generated: |
|
>; |
|
>; o Full-functionality Executive |
|
>; |
|
>; o User-tailored Executive |
|
>; |
|
>; |
|
>; The Full-functionality Executive includes all features of the |
|
>; RSX-11M-PLUS operating system that can be used on your processor. |
|
>; |
|
>; Executive data space support |
|
>; User data space support |
|
>; Task headers out of pool support |
|
>; Extended logical name support |
|
>; Supervisor-mode library support |
|
>; Fast map facility |
|
>; All DIGITAL-supplied drivers are loadable |
|
>; ICB pool size of 128. words |
|
>; Shadow recording/load sharing support |
|
>; Floating point processor (FPU) support |
|
>; Disk data caching support |
|
>; Console driver support |
|
>; Accounting support |
|
>; Batch processor support |
|
>; Queue Manager for spooling |
|
>; DIGITAL Command Language and alternate CLI support |
|
>; CTRL/C abort support |
|
>; Extended security support |
|
>; Alternate checkpoint algorithm support |
|
>; High performance FCP |
|
>; File windows in secondary pool support |
|
>; Decimal version numbers in file specifications |
|
>; Virtual terminal support with a default virtual terminal |
|
>; unit buffer size of 120. bytes and a maximum of 184. bytes |
|
>; Character translation support |
|
>; Terminal driver extended I/O support |
|
>; Time-out on unsolicited terminal input of 30. seconds |
|
>; |
|
>; |
|
>; The User-tailored Executive will require you to answer at least |
|
>; twenty additional questions specifying which standard RSX-11M-PLUS |
|
>; features you wish to disable. You should not choose the User-tailored |
|
>; Executive unless you need to disable specific RSX-11M-PLUS features. |
|
>; |
|
>; |
|
>; For information and guidelines on generating a User-tailored Executive, |
|
>; please refer to the RSX-11M-PLUS System Generation and Installation |
|
>; Guide. |
|
>; |
|
>; If you do not understand the options presented by the system |
|
>; generation process when configuring an Executive yourself, please |
|
>; select the Full-functionality Executive. |
|
>; |
|
>; |
|
>* CE020 Do you want the Full-functionality Executive? [Y/N D:Y]: |
|
>; |
|
>; If a primary pool failure occurs, this option will allow the |
|
>; the system to utilize ICB pool space as a secondary source to |
|
>; be able to attempt to resolve the pool allocation failure. |
|
>; |
|
>; Some applications may have to be aware of this possibility, or |
|
>; undefined results may occur. All supported software products |
|
>; are aware of this change, and do function correctly if this option |
|
>; is chosen. |
|
>; |
|
>* CE115 Do you want to use ICB pool as backup for primary pool ? [Y/N D:N]: y |
|
>; |
|
>; Network software provides the capability of simultaneously |
|
>; operating tasks on different systems to establish logical |
|
>; communication links and to exchange data. This software is |
|
>; not provided with RSX-11M-PLUS, but must be purchased separately. |
|
>; |
|
>; If you choose this option, DCL and alternate CLI support will |
|
>; also be included. |
|
>; |
|
>* CE120 Do you want support for communications products |
|
>* (such as DECnet, PSI, and LAT)? [Y/N D:N]: y |
|
>; |
|
>; The system name is an arbitrary six-character name. |
|
>; This should be the same as the DECnet node name, if any. |
|
>; |
|
>* CE130 What is the system name? [S R:0-6 D:"RSXMPL"]: RSX1 |
|
>; |
|
>; This option determines if dates should be displayed according to |
|
>; ISO 8601 format specification. |
|
>; |
|
>; For example; if the date February 1, 2000 should be displayed |
|
>; as 2000-02-01 |
|
>; |
|
>; |
|
>* CE215 Do you want the default date format to be |
|
>* ISO 8601:1988 compliant? [Y/N D:N]: y |
|
>; |
|
>; The IP11 industrial I/O subsystem is a combined software and |
|
>; hardware package used for process control and monitoring in |
|
>; the industrial and manufacturing environment. It consists |
|
>; of an RSX device driver (IPDRV) and a set of FORTRAN-callable |
|
>; interface routines, used to interface to a variety of hardware |
|
>; I/O modules, including digital sense interrupt, change-of-state, |
|
>; digital output, digital-to-analog converter, and analog-to-digital |
|
>; converter modules. |
|
>; |
|
>; See the IP11 I/O Subsystem Software Installation Guide for |
|
>; information on installing the software. |
|
>; |
|
>* CE264 Do you want IP11 industrial I/O subsystem support? [Y/N D:N]: |
|
>; |
|
>; The Executive Debugging Tool (XDT) provides a subset of ODT-11 |
|
>; that runs as a part of the RSX-11M-PLUS Executive. This tool |
|
>; allows interactive debugging of Executive modules, I/O drivers, |
|
>; and interrupt service routines. Selection of this option also |
|
>; includes consistency checks in the dynamic memory routines and |
|
>; the loader. |
|
>; |
|
>; Note: If your system does not have Executive data space support, |
|
>; XDT will reduce the size of primary pool. If your system does |
|
>; have Executive data space support, XDT does not affect the size |
|
>; of pool. |
|
>; |
|
>* CE270 Do you want to include XDT? [Y/N D:N]: |
|
>; |
|
>; If the system crashes, a message is printed on the crash |
|
>; notification device. This device must be a paper tape, |
|
>; teletype, or line printer compatible device; that is, the |
|
>; device must transmit a single byte at a time. Normally, |
|
>; the crash notification device is the console terminal which |
|
>; is always at the default CSR address given below. |
|
>; |
|
>* CE280 Enter the crash notification device CSR |
|
>* address [O R:160000-177700 D:177564]: |
|
>; |
|
>; If the system crashes, you can cause all of memory to be written |
|
>; onto a device for later analysis with the Crash Dump Analyzer (CDA). |
|
>; |
|
>; The device on which the crash dump is written must be selected from |
|
>; the following list of devices and cannot be a fixed media device: |
|
>; |
|
>; DB: DM: MM: |
|
>; DD: DR: MS: |
|
>; DK: DT: MT: |
|
>; DL: DU: MU: |
|
>; |
|
>; 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]: XX: |
|
>; |
|
>; Virtual disks allow the system to better manage large amounts |
|
>; of storage. If you expect to hardware of software boot virtual |
|
>; drives, select the maximum depth of virtual devices which will |
|
>; be booted. |
|
>; |
|
>* CE300 Enter the initial number of virtual disks to be |
|
>* included [D R:0.-16. D:2.]: |
|
>; |
|
>; The minimum supported memory size is 256K words for |
|
>; an RSX-11M-PLUS system. The maximum memory size is 2044K words. |
|
>; |
|
>; This value is only used by VMR when it creates the system image |
|
>; file. VMR does not allow you to create a partition or load |
|
>; anything beyond the end of memory. When the system is booted, |
|
>; your actual memory size is calculated and overrides the value |
|
>; you enter here. |
|
>; |
|
>* CE310 Enter memory size (in K words) [D R:256.-2044. D:1920.]: |
|
>; |
|
>; Some PDP-11/44 and PDP-11/84 systems are configured with UNIBUS |
|
>; memory which disables some UNIBUS Map registers. If support for |
|
>; UNIBUS memory is selected, then special UNIBUS memory partitons |
|
>; are supported, and specific UMR resources reserved when UNIBUS |
|
>; memory is detected on the system. If your system does not contain |
|
>; any memory devices on the UNIBUS, this option will have no effect. |
|
>; |
|
>* CE315 Support UNIBUS memory occupying UNIBUS map address space? [Y/N D:N]: |
|
>; |
|
>; RSX-11M-PLUS requires a real-time clock for its operation. The |
|
>; KW11-P programmable frequency clock, the KW11-L line frequency |
|
>; clock, or the DL11-W line frequency clock/console interface may |
|
>; be used. |
|
>; |
|
>* CE330 Is your system clock programmable (KW11-P)? [Y/N D:N]: |
|
>; |
|
>; Line frequency is either 50 or 60 Hz. In the U.S.A., line frequency |
|
>; is always 60 Hz. |
|
>; |
|
>* CE350 Is your line frequency 50 Hz? [Y/N D:N]: y |
|
>; |
|
>; |
|
>; |
|
>;============================================================= |
|
>; Choosing Peripheral Configuration 19-JAN-19 at 23:26 |
|
>;============================================================= |
|
>; |
|
>; |
|
>; |
|
>; The answers to the questions in this section are put in the saved |
|
>; answer file [200,200]SYSGENSA2.CMD. |
|
>; |
|
>; You may now enter a comment describing the system you are building. |
|
>; This comment is included in the SYSGENSA2 saved answer file for |
|
>; documentation, and is printed out when the saved answer file is |
|
>; later used as input. |
|
>; |
|
>; 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.]: |
|
>; |
|
>; |
|
>; The RH11 and RH70 MASSBUS controllers are the controllers for |
|
>; the following devices: |
|
>; |
|
>; DB: RP04, RP05, RP06, RM06 disks |
|
>; DR: RM02, RM03, RM05, RM06, RM80, RP07 disks |
|
>; DS: RS03, RS04 disks |
|
>; EM: ML11 semiconductor disk emulator |
|
>; MM: TM02, TM03 formatters, TE16, TU16, TU45, TU77 tapes |
|
>; |
|
>* CP0604 How many RH controllers do you have? [D R:0.-15. D:1.]: |
|
>; |
|
>; A mixed MASSBUS configuration has different device types on the |
|
>; same RH controller. For example, a DB type disk and a DR type disk |
|
>; both connected to RHA. Having an RP04 and an RP06 (both DB type |
|
>; disks) connected to the same controller is NOT a mixed MASSBUS |
|
>; configuration. |
|
>; |
|
>; If you choose to generate a mixed MASSBUS configuration, all the |
|
>; MASSBUS device data bases will be resident. |
|
>; |
|
>* CP0612 Do you want to generate a mixed MASSBUS configuration? [Y/N D:Y]: n |
|
>; |
|
>; |
|
>; DB: controllers: RH11, RH70 devices: RP04, RP05, RP06, RM06 |
|
>; |
|
>; The RP04/05/06 are 19 data surface, removable, random access |
|
>; bulk storage systems with storage capacities of 88 megabytes |
|
>; (RP04/05) and 176 megabytes (RP06) per pack. The RM06 is the |
|
>; SETASI Shelby replacement drive for RM/RP drives. |
|
>; |
|
>* CP0808 How many RP04/05/06 disk drives do you have? [D R:0.-63. D:2.]: |
|
>; |
|
>; |
|
>; The physical unit number of a drive is the number shown on the |
|
>; unit number plug (or other indicator) on the drive. |
|
>; |
|
>* CP0836 What is the physical unit number of DB0:? [O R:0-7 D:0]: |
|
>; |
|
>; Enter the drive type for this logical unit. |
|
>; |
|
>; Note: As far as SYSGEN is concerned, there is no difference between |
|
>; an RP04 and an RP05 drive. |
|
>; |
|
>* CP0860 Is DB0: an RP04, RP05, RP06, or RM06? [S R:4-4 D:"RP06"]: |
|
>; |
|
>; |
|
>* CP0836 What is the physical unit number of DB1:? [O R:0-7 D:1]: |
|
>; |
|
>* CP0860 Is DB1: an RP04, RP05, RP06, or RM06? [S R:4-4 D:"RP06"]: |
|
>; |
|
>; |
|
>; DR: controllers: RH11, RH70 devices: RM02, RM06 |
|
>; RH70 RM03, RM05, RM06, RM80, RP07 |
|
>; |
|
>; The RM02/03/05 are removable pack, random access disk storage |
|
>; systems with a storage capacity of 67 megabytes (RM02/03) and |
|
>; 256 megabytes (RM05) per pack. |
|
>; |
|
>; The RM80 and RP07 are fixed media, random access disk storage |
|
>; systems with a storage capacity of 124 megabytes (RM80) and |
|
>; 516 megabytes (RP07) per pack. |
|
>; |
|
>; The RM06 is a SETASI drive with a massbus ID using 47, which is |
|
>; autosizeable when the drive is brought online. This option should |
|
>; only be selected when not using a personality diskette for another |
|
>; type of RM device. |
|
>; |
|
>* CP1008 How many RM02/03/05/06/80/RP07 disk drives do you |
|
>* have? [D R:0.-63. D:6.]: 0 |
|
>; |
|
>; |
|
>; DS: controllers: RH11, RH70 devices: RS03, RS04 |
|
>; |
|
>; The RS03/04 are small, fast, fixed-media disks. The RS03 has a |
|
>; capacity of 256K words. The RS04 has a capacity of 512K words. |
|
>; The transfer rate is 4 microseconds per word with an average latency |
|
>; of 8 milliseconds. |
|
>; |
|
>* CP1208 How many RS03/04 disk drives do you have? [D R:0.-63. D:0.]: |
|
>; |
|
>; |
|
>; EM: controllers: RH11, RH70 device: ML11 |
|
>; |
|
>; The ML11 is a fast, random access, block mode MOS memory system. |
|
>; The ML11-A (16K chips) provides up to 4 megabytes of storage. |
|
>; The ML11-B (64K chips) provides up to 16 megabytes of storage. |
|
>; |
|
>* CP1408 How many ML11 disks do you have? [D R:0.-63. D:0.]: |
|
>; |
|
>; |
|
>; MM: controllers: RH11, RH70 devices: TE16, TU16, TU45, TU77 |
|
>; formatters: TM02, TM03 |
|
>; |
|
>; The TU16/45/77/TE16 magnetic tape drive unit is ideally suited |
|
>; for writing, reading, and storing large volumes of data and |
|
>; programs in a serial manner. The 10 1/2-inch tape reels |
|
>; contain up to 2400 feet of tape. The tape is 9-track, recorded |
|
>; either NRZI or phase encoded with recording densities of 800 or |
|
>; 1600 bpi. |
|
>; |
|
>* CP1608 How many TU16/45/77/TE16 tape drives do you |
|
>* have? [D R:0.-64. D:0.]: |
|
>; |
|
>; |
|
>; Enter the vector address for this controller. This vector address |
|
>; can be changed after the SYSGEN by using the VMR CON SET command. |
|
>; |
|
>* CP2068 Enter the vector address of RHA [O R:60-774 D:254]: |
|
>; |
|
>; Enter the CSR address for this controller. This CSR address can |
|
>; be changed after the SYSGEN by using the VMR CON SET command. |
|
>; |
|
>* CP2072 What is its CSR address? [O R:160000-177700 D:176700]: |
|
>; |
|
>; RH Configuration |
|
>; |
|
>; Physical Unit Number |
|
>; |
|
>; 0 1 2 3 4 5 6 7 |
|
>; |
|
>; RHA DB0: DB1: |
|
>; |
|
>; |
|
>; |
|
>; |
|
>; DK: controller: RK11 devices: RK05, RK05F |
|
>; |
|
>; The RK11 cartridge disk drive and control is a complete mass |
|
>; storage system for random access data storage. The system |
|
>; includes a modular mass storage device utilizing removable |
|
>; disk cartridges and a complete, easy-to-program, control unit. |
|
>; A disk cartridge holds over 2.4 megabytes. The system is |
|
>; expandable up to 8 drives per controller. An RK11 includes a |
|
>; controller and the first disk drive. Optionally, the controller |
|
>; can support up to four RK05F fixed platter drives each with twice |
|
>; the capacity of the standard RK05 drive. |
|
>; |
|
>* CP2204 How many RK11 cartridge disk controllers do you have? [O D:0]: |
|
>; |
|
>; |
|
>; DM: controllers: RK611, RK711 devices: RK06, RK07 |
|
>; |
|
>; The RK611/711 is a 3 data surface, removable, random access bulk |
|
>; storage system with a storage capacity of 14 megabytes (RK06) or |
|
>; 28 megabytes (RK07) per pack. The RK611/711 includes a control |
|
>; unit and the first disk pack drive. The system is expandable up |
|
>; to eight drives. |
|
>; |
|
>* CP2404 How many RK611/711 disk cartridge controllers do |
|
>* you have? [O D:0]: |
|
>; |
|
>; |
|
>; DL: controllers: RL11, RLV12 devices: RL01, RL02 |
|
>; |
|
>; The RL11/RLV12 disk subsystem uses a medium performance, RL01/02 |
|
>; direct access drive with a single read/write head per surface. |
|
>; Each drive provides 5.2 megabytes (RL01) or 10.4 megabytes (RL02) |
|
>; of storage on a removable, top-loading cartridge. The subsystem |
|
>; is expandable up to four drives. |
|
>; |
|
>* CP2604 How many RL11/RLV11 disk cartridge controllers do |
|
>* you have? [O D:1]: |
|
>; |
|
>; Enter the total number of RL01 and RL02 disk drives in your system. |
|
>; |
|
>* CP2608 How many RL01/RL02 disk drives do you have? [D R:1.-63. D:4.]: 2 |
|
>; |
|
>; |
|
>; The physical unit number of a drive is the number shown on the |
|
>; unit number plug (or other indicator) on the drive. |
|
>; |
|
>* CP2636 What is the physical unit number of DL0:? [O R:0-7 D:0]: |
|
>; |
|
>; Enter the drive type for this logical unit. |
|
>; |
|
>* CP2660 Is DL0: an RL01 or RL02? [S R:4-4 D:"RL02"]: |
|
>; |
|
>; |
|
>* CP2636 What is the physical unit number of DL1:? [O R:0-7 D:1]: |
|
>; |
|
>* CP2660 Is DL1: an RL01 or RL02? [S R:4-4 D:"RL02"]: |
|
>; |
|
>; |
|
>; Enter the vector address for this controller. This vector address |
|
>; can be changed after the SYSGEN by using the VMR CON SET command. |
|
>; |
|
>* CP2668 Enter the vector address of DLA [O R:60-774 D:160]: |
|
>; |
|
>; Enter the CSR address for this controller. This CSR address can |
|
>; be changed after the SYSGEN by using the VMR CON SET command. |
|
>; |
|
>* CP2672 What is its CSR address? [O R:160000-177700 D:174400]: |
|
>; |
|
>; DL Configuration |
|
>; |
|
>; Physical Unit Number |
|
>; |
|
>; 0 1 2 3 4 5 6 7 |
|
>; |
|
>; DLA DL0: DL1: |
|
>; |
|
>; |
|
>; |
|
>; |
|
>; DP: controller: RP11 devices: RP02, RPR02, RP03 |
|
>; |
|
>; The RP11 is a complete mass storage system using a magnetic |
|
>; disk pack with 20 data surfaces and a moving read/write head. |
|
>; The RP02 and RPR02 have a capacity of 20 megabytes. The RP03 |
|
>; has a capacity of 41 megabytes. |
|
>; |
|
>* CP2804 How many RP11 disk pack controllers do you have? [O D:0]: |
|
>; |
|
>; DU: controllers: RQZX1, RQDX1, RQDX2, RQDX3, |
|
>; RUX50, RQC25, KDA50, UDA50 |
|
>; |
|
>; devices: RX33, RX50, RD31, RD51, RD52, RD53, RD54, |
|
>; RC25, RA60, RA70, RA71, RA72, RA80, RA81, |
|
>; RA82, RA90, RA92, RZ23L, RZ24L, RZ26x, RZ29B |
|
>; |
|
>; The total of DU and MU controllers cannot be greater than 10. |
|
>; |
|
>; The MSCP disk controllers are: |
|
>; |
|
>; RQZX1, RQDX1, RQDX2, RQDX3, RUX50, RQC25, RUC25, KDA50, UDA50 |
|
>; |
|
>; These intelligent disk controllers provide enhanced I/O optimization, |
|
>; error correction capability, and, in some cases, dynamic bad block |
|
>; handling. |
|
>; |
|
>* CP3004 How many MSCP disk controllers do you have? [D R:0.-10. D:0.]: |
|
>; |
|
>; |
|
>; MU: controllers: TK50, TU81, TU81E, TQ81E, RQZX1 |
|
>; |
|
>; The TMSCP tape controllers are: |
|
>; |
|
>; TK50, TU81, TU81E, TQ81E, RQZX1 |
|
>; |
|
>; |
|
>* CP3404 How many TMSCP tape controllers do you have? [D R:0.-10. D:0.]: |
|
>; |
|
>; VF: Virtual disk/tape driver |
|
>; |
|
>; |
|
>; |
|
>; CR: controllers: CM11, CR11 |
|
>; |
|
>; The CR11 card reader reads EIA standard 80-column punched data |
|
>; cards at 300 cards per minute. It uses a riffle-air and a |
|
>; vacuum-pick mechanism to move the cards. The CM11-F reads 80- |
|
>; column mark-sense cards, which can have punched holes, at 285 |
|
>; cards per minute. |
|
>; |
|
>* CP4004 How many CM/CR11 card readers do you have? [O D:0]: |
|
>; |
|
>; |
|
>; CT: controller: TA11 device: TU60 |
|
>; |
|
>; The TA11 magnetic tape cassette system is a dual-drive, |
|
>; reel-to-reel unit designed to replace paper tape. Its two |
|
>; drives run non-simultaneously using proprietary Digital |
|
>; Equipment Corporation Philips-type cassettes. The TA11 |
|
>; includes a control unit and a dual tape transport. |
|
>; |
|
>* CP4204 How many TA11 dual cassettes do you have? [O D:0]: |
|
>; |
|
>; |
|
>; MS: controllers: TS11, TU80, TSV05, TK25 |
|
>; |
|
>; The TS11, TU80, and TSV05 are 1/2 inch 1600 bpi tape subsystems |
|
>; and the TK25 is a cartridge tape subsystem. |
|
>; |
|
>* CP4404 How many TS11/TU80/TSV05/TK25 |
|
>* magtape controllers do you have? [O D:1]: |
|
>; |
|
>; Enter the vector address for this controller. This vector address |
|
>; can be changed after the SYSGEN by using the VMR CON SET command. |
|
>; |
|
>* CP4468 Enter vector address of the next |
|
>* TS11/TU80/TSV05/TK25 [O R:60-774 D:224]: |
|
>; |
|
>; Enter the CSR address for this controller. This CSR address can |
|
>; be changed after the SYSGEN by using the VMR CON SET command. |
|
>; |
|
>* CP4472 What is its CSR address? [O R:160000-177700 D:172522]: |
|
>; |
|
>; |
|
>; DT: controller: TC11 device: TU56 |
|
>; |
|
>; The TC11 is a dual-unit bidirectional magnetic-tape transport |
|
>; system for auxiliary data storage. |
|
>; |
|
>; The system stores information at fixed positions on magnetic |
|
>; tape as in magnetic disk or drum storage devices, rather than |
|
>; at unknown or variable positions as in conventional magnetic |
|
>; tape systems. |
|
>; |
|
>; A DECtape system consists of up to 4 dual transports, a control |
|
>; unit (which will buffer and control information for up to four |
|
>; dual transports). A TC11 includes a control unit and the |
|
>; first dual tape transport. |
|
>; |
|
>* CP4604 How many TC11 DECtape controllers do you have? [O D:0]: |
|
>; |
|
>; |
|
>; DX: controller: RX11 device: RX01 |
|
>; |
|
>; The RX11 is an industry compatible disk storage system for |
|
>; flexible (floppy) disks. An RX11 is capable of controlling two |
|
>; flexible disk drives each having a capacity of 256K bytes. |
|
>; |
|
>* CP4804 How many RX11 disk controllers do you have? [O D:0]: |
|
>; |
|
>; |
|
>; DY: controller: RX211, RXV21 device: RX02 |
|
>; |
|
>; The RX211 and RXV21 are single or double density flexible (floppy) disk |
|
>; controllers with a storage capacity of 256K bytes (single density) or |
|
>; 512K bytes (double density). One controller is capable of controlling |
|
>; two drives. |
|
>; |
|
>* CP5004 How many RX211/RXV21 disk controllers do you have? [O D:0]: |
|
>; |
|
>; |
|
>; DD: controller: DL11 device: TU58 |
|
>; |
|
>; The TU58 driver interfaces with the 3M DC-100A tape |
|
>; cartridge drive and controller units via a parallel to ser- |
|
>; ial DL11 converter at baud rates up to 9.6K. Data is |
|
>; stored on the media on two parallel tracks recorded in the |
|
>; same direction. The tape is preformatted into 2048 physical |
|
>; records of 128 bytes each. Access to these physical records |
|
>; is by groups of four corresponding to a standard DEC block |
|
>; of 512 bytes. |
|
>; |
|
>* CP5204 How many TU58 controllers do you have? [O D:0]: |
|
>; |
|
>; |
|
>; LP: controllers: LA180, LN01, LP11, LS11, LV11 |
|
>; devices: LA180, LG01, LG02, LN01, LP01, LP02, LP04, LP05, |
|
>; LP06, LP07, LP14, LP25, LP26, LP27, LS11, LV01 |
|
>; |
|
>; The LP11 is a high-speed impact line printer with a rotating drum |
|
>; or band. It is available in a variety of models, with and without |
|
>; lowercase characters. |
|
>; |
|
>; The LS11 line printer is a medium-speed impact dot-matrix line |
|
>; printer. It prints at a rate of 165 characters per second at |
|
>; 10 characters per inch with up to 132 characters per line. |
|
>; |
|
>; The LA180 DECprinter is similar to the LS11 with the exception |
|
>; that it prints at the rate of 180 characters per second. |
|
>; |
|
>; The LV11 is a high-speed electrostatic printer-plotter that prints |
|
>; at a rate of 500 lines per minute. Only the print option is |
|
>; supported under RSX-11M-PLUS. |
|
>; |
|
>* CP5404 How many LP/LS/LV/LG/LN/LA180 line printers do you have? [O D:1]: |
|
>; |
|
>; If a task tries to access the line printer when the device is not |
|
>; ready, a message saying the line printer is not ready is printed |
|
>; on the console terminal. This message is repeated every n seconds, |
|
>; where n is your response to this question, for as long as the line |
|
>; printer remains not ready. |
|
>; |
|
>; Enter zero to disable this feature and suppress the messages. |
|
>; |
|
>* CP5408 Enter the number of seconds between |
|
>* line printer-not-ready messages [D R:0.-255. D:15.]: 60 |
|
>; |
|
>; Enter the vector address for this line printer. This vector address |
|
>; can be changed after the SYSGEN by using the VMR CON SET command. |
|
>; |
|
>* CP5468 Enter vector address of the next line |
|
>* printer [O R:60-774 D:200]: |
|
>; |
|
>; Enter the CSR address for this line printer. This CSR address can |
|
>; be changed after the SYSGEN by using the VMR CON SET command. |
|
>; |
|
>* CP5472 What is its CSR address? [O R:160000-177700 D:177514]: |
|
>; |
|
>; Here is a table of the valid line printer types and their |
|
>; characteristics: |
|
>; |
|
>; printer # of lines per supports |
|
>; type controller columns minute optimization |
|
>; |
|
>; LA180 LA180 132 150 no |
|
>; LG01 LP11 132 240-600 no |
|
>; LG02 LP11 132 240-600 no |
|
>; LN01 LN01 132 600 NA |
|
>; LP01 LP11-F/H 80 170-1110 yes |
|
>; LP02 LP11-J/K 132 170-1110 yes |
|
>; LP04 LP11-R/S 132 1110 yes |
|
>; LP05 LP11-V/W 132 300 no |
|
>; LP06 LP11-Y/Z 132 460-600 no |
|
>; LP07 LP11-G 132 1200 no |
|
>; LP14 LP11-C/D 132 660-900 no |
|
>; LP25 LP11-A/B 132 215-300 no |
|
>; LP26 LP11-E 132 445-600 no |
|
>; LP27 LP11-U 132 800-1200 no |
|
>; LS11 LS11 132 60-200 no |
|
>; LV01 LV11 132 500 yes |
|
>; |
|
>; The printer type is used to set two characteristics in the UCB: |
|
>; |
|
>; o Column or buffer width |
|
>; |
|
>; This is settable in VMR or MCR with the SET /BUF command. |
|
>; |
|
>; |
|
>; o Fast line printer support |
|
>; |
|
>; This is an optimization performed by the driver to eliminate |
|
>; unnecessary print cycles. This characteristic is not settable |
|
>; in VMR or MCR. |
|
>; |
|
>; If you specify the wrong printer type and the driver performs |
|
>; the optimization for a printer that does not support it, you |
|
>; will occasionally lose a line of a listing when the printer |
|
>; is taken off line. |
|
>; |
|
>; If you specify the wrong printer type and the driver does not |
|
>; perform the optimization for a printer that supports it, the |
|
>; printer will run a little slower than it would with the |
|
>; optimization, but there will be no other adverse effects. |
|
>; |
|
>; If you do not know the correct printer type for your printer, take |
|
>; the default. This will give you a 132-column printer without fast |
|
>; printer optimization. Once your system is running, you can change |
|
>; the number of columns if necessary with the MCR SET command. |
|
>; |
|
>* CP5480 Enter line printer type for LPA [S R:4-5 D:"LP25"]: LP02 |
|
>; |
|
>; If this line printer has both uppercase and lowercase characters, |
|
>; answer Yes to this question. If it only has uppercase characters, |
|
>; answer No. Your answer determines the initial setting for |
|
>; lowercase character conversion on this printer. You can change |
|
>; this at any time by using the MCR SET /LOWER command. |
|
>; |
|
>* CP5484 Does LPA have lowercase characters? [Y/N D:N]: y |
|
>; |
|
>; |
|
>; MT: controllers: TM11, TMA11, TMB11 devices: TE10, TU10, TU10W, TS03 |
|
>; |
|
>; The TM/TMA/TMB11 is a magnetic tape system ideally suited for |
|
>; writing, reading, and storing large volumes of data and |
|
>; programs in a serial manner. The system reads and writes in |
|
>; industry-compatible format. TU10 drives support 10.5-inch reels |
|
>; containing up to 2400 feet of tape upon which over 180 million |
|
>; bits of data can be stored on high density 9-track tape. TS03 |
|
>; drives support 7-inch reels containing up to 600 feet of tape in |
|
>; high density 9-track format. TU10W drives are compatible with |
|
>; TU10 drives except they operate only on 800 bpi, 9-track tape. |
|
>; |
|
>* CP5604 How many TM/TMA/TMB11 magtape controllers do you have? [O D:0]: |
|
>; |
|
>; |
|
>; PP: controller: PC11 |
|
>; |
|
>; The PC11 is a high speed paper tape reader/punch that is |
|
>; capable of reading eight-hole, unoiled, perforated paper tape at |
|
>; 300 characters per second, and punching tape at 50 characters |
|
>; per second. |
|
>; |
|
>* CP5804 How many PC11 paper tape reader/punches do you have? [O D:1]: 0 |
|
>; |
|
>; |
|
>; PR: controller: PR11 |
|
>; |
|
>; The PR11 is a high speed paper tape reader that is capable of |
|
>; reading eight-hole unoiled perforated paper tape at 300 |
|
>; characters per second. |
|
>; |
|
>; |
|
>* CP6004 How many PR11 paper tape readers do you have? [O D:1]: 0 |
|
>; |
|
>; |
|
>; LA: controller: LPA11 |
|
>; |
|
>; The LPA11 lab peripheral accelerator is a real-time subsystem which |
|
>; interfaces to the PDP-11 family of computers. The system consists |
|
>; of the LPA11, up to 2 A/D converters, a programmable real-time |
|
>; clock, a D/A converter, and up to five digital I/O modules. |
|
>; |
|
>* CP6204 How many LPA11 lab subsystems do you have? [D R:0.-16. D:0.]: |
|
>; |
|
>; |
|
>; TT: controllers: DL11, DLV11 controller mnemonic: YL |
|
>; |
|
>; The DL11/DLV11 series of asynchronous single line interfaces handle |
|
>; full or half-duplex communication between a wide variety of serial |
|
>; communication channels and a PDP-11 computer. |
|
>; |
|
>; SYSGEN automatically sets up the data bases for all mandatory |
|
>; DL11/DLV11s. (For each processor in the system, there must be a |
|
>; DL11/DLV11; these are mandatory.) Answer the next question with |
|
>; the number of additional DL11/DLV11s in your system. |
|
>; |
|
>; Note: Enter only the number of DL11s used as terminal interfaces. |
|
>; Do not include any DL11s used as controlers for the TU58 DECtape II. |
|
>; |
|
>* CP6804 Enter number of additional DL11/DLV11 line interfaces [O D:0]: |
|
>; |
|
>; The terminal types supported by RSX-11M-PLUS SYSGEN are: |
|
>; |
|
>; ASR33 LA12 VT05B |
|
>; ASR35 LA30P VT50 |
|
>; LA30S VT52 |
|
>; DTC01 LA34 VT55 |
|
>; LA36 VT61 |
|
>; KSR33 LA38 VT100 |
|
>; LA50 VT101 |
|
>; LA100 VT102 |
|
>; LA120 VT105 |
|
>; LA180S VT125 |
|
>; LA210 VT131 |
|
>; LN03 VT132 |
|
>; PC3xx VT2xx |
|
>; |
|
>* CP6832 Enter terminal type for YLA [S R:4-6 D:"LA120"]: VT102 |
|
>; |
|
>; |
|
>; TT: controller: DH11 controller mnemonic: YH |
|
>; |
|
>; The DH11 multiplexer connects the PDP-11 with 16 asynchronous |
|
>; serial communications lines operating with individually |
|
>; programmable parameters. These parameters are: |
|
>; |
|
>; transmitter speed (baud) |
|
>; receiver speed (baud) |
|
>; |
|
>* CP7004 Enter number of DH11 asynchronous line |
|
>* multiplexers [D R:0.-16. D:0.]: |
|
>; |
|
>; |
|
>; TT: controller mnemonic: YV |
|
>; |
|
>; controllers: DHU11, DHV11, CXA16, CXB16, CXY08 |
|
>; |
|
>; |
|
>; These multiplexers connect the PDP-11 with up to |
|
>; 16 (DHU11, CXA16, CXB16) or 8 (DHV11, CXY08) |
|
>; asynchronous serial communications lines operating with |
|
>; individually programmable parameters. These parameters are: |
|
>; |
|
>; transmitter speed (baud) |
|
>; receiver speed (baud) |
|
>; |
|
>; Modem control is available with the DHU11, DHV11 and CXY08. |
|
>; The CXA16 and CXB16 do not support modem control. Use the VMR |
|
>; or MCR SET /REMOTE commands in order to enable dialup lines. |
|
>; |
|
>* CP7104 Enter number of DHU11/DHV11/CXA16/CXB16/CXY08 (YV:-type) |
|
>* asynchronous line multiplexers [D R:0.-32. D:0.]: |
|
>; |
|
>; |
|
>; TT: controller: DJ11 controller mnemonic: YJ |
|
>; |
|
>; The DJ11 is a multiplexed interface between 16 asynchronous |
|
>; serial data-communications channels and the PDP-11 UNIBUS. The |
|
>; DJ11 is a unit whose character formats and operating speeds are |
|
>; jumper or strap selectable in groups of four lines. |
|
>; |
|
>* CP7204 Enter number of DJ11 asynchronous line |
|
>* multiplexers [D R:0.-16. D:0.]: |
|
>; |
|
>; |
|
>; TT: controllers: DZ11, DZQ11, DZV11, DFA01 controller mnemonic: YZ |
|
>; |
|
>; The DZ11/DZQ11/DZV11/DFA01 multiplexers connect the PDP-11 with up to |
|
>; 8 asynchronous serial communications lines operating with individually |
|
>; programmable parameters. These parameters are: |
|
>; |
|
>; Transmitter speed / Receiver speed (baud) |
|
>; |
|
>* CP7404 Enter number of DZ11/DZQ11/DZV11/DFA01 asynchronous line |
|
>* multiplexers [D R:0.-32. D:1.]: |
|
>; |
|
>; The DZ11/DZQ11/DZV11 has the ability to maintain a full-duplex connection |
|
>; through a BELL 103A type modem. Modem support requires added code in the |
|
>; terminal driver and increases system overhead. As a result, it should be |
|
>; selected only if needed. |
|
>; |
|
>* CP7420 Do any of the DZ lines require modem support? [Y/N D:N]: |
|
>; |
|
>; The vector address for the DZ11/DZQ11/DZV11 is assigned from the floating |
|
>; vector space starting at 300. The vector address can be changed after |
|
>; the SYSGEN by using the VMR CON SET command. |
|
>; |
|
>* CP7468 Enter vector address of YZA [O R:300-770 D:300]: |
|
>; |
|
>; The CSR address for the DZ11/DZQ11/DZV11 is assigned from the floating |
|
>; address space starting at 160010. The CSR address can be changed |
|
>; after the SYSGEN by using the VMR CON SET command. |
|
>; |
|
>* CP7472 What is its CSR address? [O R:160000-177700 D:160100]: |
|
>; |
|
>; Enter the number of lines on this controller. |
|
>; |
|
>* CP7480 How many lines does YZA have? [D R:1.-8. D:8.]: |
|
>; |
|
>; The terminal types supported by RSX-11M-PLUS SYSGEN are: |
|
>; |
|
>; ASR33 LA12 VT05B |
|
>; ASR35 LA30P VT50 |
|
>; LA30S VT52 |
|
>; DTC01 LA34 VT55 |
|
>; LA36 VT61 |
|
>; KSR33 LA38 VT100 |
|
>; LA50 VT101 |
|
>; LA100 VT102 |
|
>; LA120 VT105 |
|
>; LA180S VT125 |
|
>; LA210 VT131 |
|
>; LN03 VT132 |
|
>; PC3xx VT2xx |
|
>; |
|
>* CP7484 Enter terminal type for YZA [S R:4-6 D:"VT100"]: VT102 |
|
>; |
|
>; SYSVMR.CMD, the VMR command file which creates your system image file, |
|
>; contains commands that set the characteristics for each terminal as |
|
>; follows: |
|
>; |
|
>; Terminal type: as you specified for the controller |
|
>; Buffer width: 80 |
|
>; Speed: 300/300 for hardcopy terminals |
|
>; 9600/9600 for CRTs |
|
>; Lower to upper- |
|
>; case conversion: No for hardcopy terminals |
|
>; Yes for CRTs |
|
>; |
|
>; If you wish to change these characteristics for your terminals, SYSGEN |
|
>; will allow you to edit SYSVMR.CMD. |
|
>; |
|
>; |
|
>; |
|
>; Intercomputer communication devices consist of the following: |
|
>; |
|
>; PCL11 full-duplex DMA interprocessor communications |
|
>; device |
|
>; DMC11/DMR11 high-speed synchronous serial line interface |
|
>; DUP11 synchronous serial line interface |
|
>; DEUNA Ethernet communications controller |
|
>; |
|
>; Note: Do NOT include any devices which will be used with DECnet. |
|
>; Those devices should be included when you do your NETGEN. |
|
>; |
|
>* CP7604 Do you have any intercomputer communication devices? [Y/N D:N]: |
|
>; |
|
>; |
|
>; 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]: |
|
>; |
|
>; |
|
>; If you will be adding other devices after this SYSGEN or have |
|
>; included user-supplied devices, you will want to set the highest |
|
>; interrupt vector address high enough to accommodate the vectors for |
|
>; those devices. |
|
>; |
|
>; 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 19-JAN-19 at 23:38 |
|
>;================================================================ |
|
>; |
|
>; |
|
>; |
|
>; 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 |
|
>; |
|
>; Copy the files created by the Executive options and peripheral |
|
>; configuration sections into the correct directories. |
|
>; |
|
>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 |
|
>; |
|
>; |
|
>; Assembly listings of the Executive modules and the drivers can be |
|
>; generated and stored in a file or printed directly. |
|
>; |
|
>; Generating listings is time-consuming and they are not normally |
|
>; needed, so we recommend you answer No to this question. |
|
>; |
|
>* AE010 Do you want assembly listings of the Executive and |
|
>* drivers? [Y/N D:N]: y |
|
>; |
|
>; Listings can be sent directly to a printer or can be stored |
|
>; on a directory device for printing later. If you enter a |
|
>; directory device, the listings will be put in UFD [11,34]. |
|
>; |
|
>* AE020 What is to be the listing device [ddu:]? [S R:2-5 D:"SY:"]: |
|
>; |
|
>ASN SY:=LS: |
|
>; |
|
>; |
|
>; If you are building a specialized system you may wish to edit |
|
>; some of the files which SYSGEN produced before the Executive |
|
>; and drivers are assembled. |
|
>; |
|
>* AE030 Do you wish to pause to edit any files before |
|
>* assembling? [Y/N D:N]: |
|
>; |
|
>SET /UIC=[11,24] |
|
>; |
|
>; Now we assemble the Executive and resident drivers. |
|
>; |
|
>PIP *.OBJ;*/DE/NM,*.TTY;* |
|
>; |
|
>TIME |
|
23:39:15 19-JAN-19 |
|
>; |
|
>MAC @RSXASM |
|
>; |
|
>; Now we assemble the loadable drivers. |
|
>; |
|
>TIME |
|
00:04:44 20-JAN-19 |
|
>; |
|
>MAC @DRIVERS.ASM |
|
>; |
|
>TIME |
|
00:19:58 20-JAN-19 |
|
>; |
|
>; Now we build the concatenated object module file for the Executive. |
|
>; |
|
>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 |
|
>; |
|
>; Now we build the Executive library. |
|
>; |
|
>LBR RSX11M/CR:256.::256./-EP=[11,24]RSX11M.OBS |
|
>PIP [11,24]RSX11M.OBS;*,*.OBJ;*/DE |
|
>; |
|
>; Now we build the terminal driver library. |
|
>; |
|
>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 20-JAN-19 at 00:20 |
|
>;============================================================== |
|
>; |
|
>; |
|
>; |
|
>; 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] |
|
>; |
|
>; At this point, you can edit: |
|
>; |
|
>; the Executive task-build command files in [200,200] |
|
>; the driver task-build command files in [200,200] |
|
>; the privileged task task-build command files in [1,24] |
|
>; SYSVMR.CMD in [1,54] |
|
>; |
|
>; In most cases there is no need to edit the task-build command files. |
|
>; However, you may want to tailor SYSVMR for your system. |
|
>; |
|
>* BE030 Do you want to pause to edit any files before |
|
>* task-building? [Y/N D:N]: 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 |
|
>; |
|
>; Now we build the Executive. |
|
>; |
|
>TIME |
|
00:23:28 20-JAN-19 |
|
>; |
|
>TKB @RSXBLD |
|
>; |
|
>; Now we build the loadable drivers |
|
>; |
|
>TIME |
|
00:28:32 20-JAN-19 |
|
>; |
|
>TKB @[200,200]DRIVERS.BLD |
|
>; |
|
>TIME |
|
00:29:29 20-JAN-19 |
|
>SET /UIC=[200,200] |
|
>; |
|
>; |
|
>; |
|
>;========================================================= |
|
>; Building the Privileged Task 20-JAN-19 at 00:29 |
|
>;========================================================= |
|
>; |
|
>; |
|
>; |
|
>; The answers to the questions in this section are put in the saved |
|
>; answer file [200,200]SYSGENSA1.CMD. |
|
>; |
|
>; |
|
>; Maps of the privileged tasks can be generated and stored in a file |
|
>; or printed directly. |
|
>; |
|
>; Maps of the privileged tasks are not normally needed, so we |
|
>; recommend you answer No to this question. |
|
>; |
|
>* BP040 Do you want the maps of the privileged tasks? [Y/N D:N]: |
|
>; |
|
>ASN NL:=MP: |
|
>; |
|
>SET /UIC=[1,24] |
|
>; |
|
>TIME |
|
00:30:01 20-JAN-19 |
|
>; |
|
>TKB @SAVBLD |
|
>; |
|
>TIME |
|
00:31:02 20-JAN-19 |
|
>; |
|
>ASN LB:=OU: |
|
>SET /UIC=[200,200] |
|
>; |
|
>; |
|
>; |
|
>;============================================================ |
|
>; Rebuilding Supplied System Tasks 20-JAN-19 at 00:31 |
|
>;============================================================ |
|
>; |
|
>; |
|
>; |
|
>; The answers to the questions in this section are put in the saved |
|
>; answer file [200,200]SYSGENSA3.CMD. |
|
>; |
|
>; |
|
>; All nonprivileged and vectored privileged system tasks are supplied |
|
>; already task-built and can be found in the library UFD on the target |
|
>; system disk. It is not normally necessary to rebuild these supplied |
|
>; system tasks although you may wish to do so, for example if one of |
|
>; them has been patched. |
|
>; |
|
>* BN010 Do you want to rebuild any system tasks? [Y/N D:N]: y |
|
>; |
|
>; You may now enter a comment describing the system you are building. |
|
>; This comment is included in the SYSGENSA3 saved answer file for |
|
>; documentation, and is printed out when the saved answer file is |
|
>; later used as input. |
|
>; |
|
>; Enter a comment for inclusion in the SYSGENSA3 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.]: |
|
>; |
|
>; FCSRES is a resident library of commonly used FCS routines. |
|
>; Tasks can be built to map to the FCS routines in FCSRES instead of |
|
>; including the FCS routines in their task image. This saves physical |
|
>; memory because the many separate copies of the FCS routines in |
|
>; different task images are replaced by one copy in the library which |
|
>; all the tasks use. |
|
>; |
|
>; The FCSRES library may be mapped as a supervisor-mode library, |
|
>; referred to as FCSFSL (FCS Supervisor Library). In addition to |
|
>; the saving of physical memory, the supervisor-mode library also |
|
>; saves user-mode virtual address space since the FCS routines |
|
>; are mapped using the supervisor mode APRs. This frees user-mode |
|
>; virtual address space for the application task. This can be used |
|
>; to enlarge buffers or to reduce overlay activity, for example. |
|
>; |
|
>; SYSGEN can build many of the system tasks to use the FCS resident |
|
>; libraries if you desire. If you answer "Yes" to the following |
|
>; question SYSGEN will use FCSFSL AND FCSRES wherever possible. If you |
|
>; answer "No" to this question SYSGEN will only use FCSFSL AND FCSRES |
|
>; when you explicitly include them in the task specification. |
|
>; |
|
>* BN012 Use FCSFSL AND FCSRES when possible? [Y/N D:Y]: |
|
>; |
|
>; The following supplied system tasks and utilities can be rebuilt at this time |
|
: |
|
>; |
|
>; The letters "R" and "F" in parentheses following the task name indicate that |
|
>; versions may be built to use FCSRES and FCSFSL respectively. |
|
>; |
|
>; ACC (R) CRP HRC PAT (R) SYL (R) |
|
>; ACD DCL ICM (R&F) PIP (R&F) TDX |
|
>; ACNT (R&F) DLD INI PMD (R) TKB (R&F) |
|
>; ACS (R) DMO INS PMT TKN |
|
>; BAD DMP (R&F) IPP (R) PSW (R) UFD |
|
>; BOO DTE IOX (R&F) QMG (R) UML |
|
>; BRO EDI (R&F) LBR (R&F) QMGCLI UNL (R) |
|
>; BRU EDT (R&F) LOA QMGPRT VFY (R&F) |
|
>; BYE ELI (R) LPP (R) RCT VMR |
|
>; CDA (R) ERL MAC (R&F) RMD XDT |
|
>; CFL (F) FLX (R&F) MCD RPT (F) ZAP (R) |
|
>; CMP (R&F) FMT MCR SHA |
|
>; CON FTB (R&F) MFT SHF |
|
>; COT (R) FXR MOU SHU |
|
>; CRF (R&F) HEL (R) MTA SLP (R) |
|
>; |
|
>; Press ESC for the list of the nonprivileged utilities and |
|
>; vectored privileged system tasks that may be rebuilt here. |
|
>; |
|
>; Enter ALL to build all the tasks, using FCSFSL and FCSRES. |
|
>; Enter ALLVAN to build all tasks, not using the FCS libraries. |
|
>; Enter ALLRES to build all the FCSRES tasks. |
|
>; Enter ALLFSL to build all the FCSFSL tasks. |
|
>; |
|
>; SYSGEN will attempt to use FCSFSL and FCSRES where possible. |
|
>; |
|
>; Enter the task names separated by commas. You can enter them on |
|
>; more than one line. When you are done, finish the list with a |
|
>; period or press RETURN in response to the prompt. |
|
>; |
|
>* BN020 Enter task name(s) [S]: ALL |
|
>* BN020 Enter task name(s) [S]: |
|
>; |
|
>SET /UIC=[1,24] |
|
>SET /UIC=[200,200] |
|
>; |
|
>; Maps of the system tasks can be generated and stored in a file |
|
>; or printed directly. |
|
>; |
|
>; Maps of the system tasks are not normally needed, so we |
|
>; recommend you answer No to this question. |
|
>; |
|
>* BN030 Do you want the maps of the system tasks? [Y/N D:N]: |
|
>; |
|
>ASN NL:=MP: |
|
>; |
|
>; At this point, you can edit the system task task-build command |
|
>; files in [1,24]. In most cases there is no need to edit these files. |
|
>; |
|
>* BN050 Do you want to pause to edit any files before |
|
>* task-building? [Y/N D:N]: |
|
>SET /UIC=[1,24] |
|
>; |
|
>; Now we will build the requested system tasks. |
|
>; |
|
>; |
|
>TKB @ACDBLD |
|
>TKB @BADBLD |
|
>TKB @BOOBLD |
|
>TKB @BROBLD |
|
>TKB @BRUBLD |
|
>TKB @BYEBLD |
|
>TKB @CONBLD |
|
>TKB @CRPBLD |
|
>TKB @DCLBLD |
|
>TKB @DLDBLD |
|
>TKB @DMOBLD |
|
>TKB @DTEBLD |
|
>TKB @ERLBLD |
|
>TKB @FMTBLD |
|
>TKB @FXRBLD |
|
>TKB @HRCBLD |
|
>TKB @INIBLD |
|
>TKB @INSBLD |
|
>TKB @LOABLD |
|
>TKB @MCDBLD |
|
>TKB @MCRBLD |
|
>TKB @MFTBLD |
|
>TKB @MOUBLD |
|
>TKB @MTABLD |
|
>TKB @PMTBLD |
|
>TKB @QCLBLD |
|
>TKB @QPRBLD |
|
>TKB @RCTBLD |
|
>TKB @RMDBLD |
|
>TKB @SHABLD |
|
>TKB @SHFBLD |
|
>TKB @SHUBLD |
|
>TKB @TDXBLD |
|
>TKB @TKNBLD |
|
>TKB @UFDBLD |
|
>TKB @UMLBLD |
|
>TKB @VMRBLD |
|
>TKB @XDTBLD |
|
>TKB @ACCRESBLD |
|
>TKB @ACSRESBLD |
|
>TKB @CDARESBLD |
|
>TKB @COTRESBLD |
|
>TKB @ELIRESBLD |
|
>TKB @HELRESBLD |
|
>TKB @IPPRESBLD |
|
>TKB @LPPRESBLD |
|
>TKB @PATRESBLD |
|
>TKB @PMDRESBLD |
|
>TKB @PSWRESBLD |
|
>TKB @QMGRESBLD |
|
>TKB @SLPRESBLD |
|
>TKB @SYLRESBLD |
|
>TKB @UNLRESBLD |
|
>TKB @ZAPRESBLD |
|
>TKB @ACNFSLBLD |
|
>TKB @CFLFSLBLD |
|
>TKB @CMPFSLBLD |
|
>TKB @CRFFSLBLD |
|
>TKB @DMPFSLBLD |
|
>TKB @EDIFSLBLD |
|
>TKB @EDTFSLBLD |
|
>TKB @FLXFSLBLD |
|
>TKB @FTBFSLBLD |
|
>TKB @ICMFSLBLD |
|
>TKB @IOXFSLBLD |
|
>TKB @LBRFSLBLD |
|
>TKB @MACFSLBLD |
|
>TKB @PIPFSLBLD |
|
>TKB @RPTFSLBLD |
|
>TKB @TKBFSLBLD |
|
>TKB @VFYFSLBLD |
|
>; |
|
>SET /UIC=[200,200] |
|
>; |
|
>; |
|
>; |
|
>;========================================================== |
|
>; Creating the System Image File 20-JAN-19 at 01:22 |
|
>;========================================================== |
|
>; |
|
>; |
|
>SET /UIC=[1,54] |
|
>; |
|
>PIP RSX11M.TMP;*/DE/NM |
|
>; |
|
>PIP RSX11M.SYS/CO/NV/BL:1026.=RSX11M.TSK |
|
>; |
|
>ASN LB:=SY: |
|
>; |
|
>; Utility tasks stay in utility UFD [3,54]. |
|
>; |
|
>; RSX11M.TSK is a backup copy of the Executive you just built. |
|
>; |
|
>; |
|
>; VMR will now initialize the system. |
|
>; |
|
>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 00201300 00100000 SEC POOL |
|
SYSPAR 117670 00301300 00172100 MAIN |
|
117624 00301300 00115300 RO COM !DIR11M! |
|
117434 00416600 00005200 TASK [...LDR] |
|
117230 00424000 00033500 TASK [MCR...] |
|
117024 00457500 00010500 TASK [TKTN ] |
|
116620 00470200 00003200 TASK [SHF...] |
|
DRVPAR 116540 00473400 00127600 MAIN |
|
116474 00473400 00006600 RO COM !TTEXT ! |
|
116410 00502200 00020600 RO COM !TTCOM ! |
|
116324 00523000 00034200 DRIVER (TT:) |
|
115744 00557200 00004700 DRIVER (DB:) |
|
115354 00564100 00003500 DRIVER (DL:) |
|
115044 00567600 00005300 DRIVER (MS:) |
|
114624 00575100 00001400 DRIVER (LP:) |
|
114434 00576500 00000100 DRIVER (NL:) |
|
114370 00576600 00017700 DRIVER (VF:) |
|
114324 00616500 00000300 DRIVER (CO:) |
|
114260 00617000 00002500 DRIVER (VT:) |
|
114214 00621500 00001500 DRIVER (RD:) |
|
GEN 114150 00623200 16154600 MAIN |
|
...LDR 12.01 117500 SYSPAR 248. 00005200 LB0:-00177222 FIXED |
|
TKTN 07.01 117070 SYSPAR 248. 00010500 LB0:-00211176 FIXED |
|
F11MSG 15.00 112070 GEN 200. 00006300 LB0:-00045045 |
|
MTAACP 17.00 111474 GEN 200. 00016200 LB0:-00210360 |
|
SHE... 06.01 111224 GEN 200. 00014500 LB0:-00211106 |
|
MCR... 07.00 117274 SYSPAR 160. 00033500 LB0:-00207205 FIXED |
|
F11ACP 07.00D 113734 GEN 149. 00041000 LB0:-00043565 |
|
ERRLOG 05.03 113374 GEN 148. 00056200 LB0:-00206405 |
|
PMT... 02.02 112734 GEN 148. 00007500 LB0:-00210330 |
|
COT... 02.04 112214 GEN 145. 00014300 LB0:-00211740 |
|
HRC... 05.00 111620 GEN 140. 00042500 LB0:-00206646 |
|
PMD... 07.05 111350 GEN 140. 00017600 LB0:-00212773 |
|
SYSLOG 04.03 112464 GEN 130. 00024500 LB0:-00213155 |
|
SHF... 07.01 116664 SYSPAR 105. 00003200 LB0:-00210350 FIXED |
|
FXR... 03.02 111744 GEN 100. 00003300 LB0:-00206575 |
|
BAP0 04.11 113520 GEN 80. 00050300 LB0:-00035350 |
|
QMG... 06.04 112610 GEN 75. 00037300 LB0:-00213061 |
|
LP0 07.04 113154 GEN 70. 00020300 LB0:-00213024 |
|
ACNT 06.04 112340 GEN 50. 00057100 LB0:-00213263 |
|
SHUTUP 04.04 111100 GEN 50. 00016500 LB0:-00211125 |
|
...RMD 05.00 002051+ GEN 225. 00042000 LB0:-00211221 |
|
...DCL 06.01 002025+ GEN 160. 00062500 LB0:-00205513 |
|
...DMO 04.02 002027+ GEN 160. 00017300 LB0:-00205344 |
|
...MCR 07.00 002043+ GEN 160. 00040300 LB0:-00207471 |
|
...MOU 26.06 002045+ GEN 160. 00045600 LB0:-00207243 |
|
...CA. 01.00 002101+ GEN 150. 00026100 LB0:-00211146 |
|
...INS 16.00 002041+ GEN 100. 00053200 LB0:-00207015 |
|
...SAV 11.00 002075+ GEN 100. 00070500 LB0:-00203325 |
|
...UFD 07.02 002103+ GEN 100. 00014500 LB0:-00211463 |
|
...VCP V04.10 002105+ GEN 90. 00020300 LB0:-00056757 |
|
...ACS 04.00 002057+ GEN 70. 00006200 LB0:-00211502 |
|
...ACC 05.00 002017+ GEN 65. 00032100 LB0:-00211647 |
|
...SHA 06.01 002077+ GEN 65. 00032000 LB0:-00210607 |
|
...AT. 10.0 002033+ GEN 64. 00056500 LB0:-00214537 |
|
...INI 24.00 002035+ GEN 60. 00037200 LB0:-00206721 |
|
...HOM 24.00 002037+ GEN 60. 00037200 LB0:-00206721 |
|
...BRO 09.10 002021+ GEN 50. 00041500 LB0:-00204475 |
|
...BYE 05.01 002023+ GEN 50. 00021700 LB0:-00204541 |
|
...HEL 06.00 002031+ GEN 50. 00031600 LB0:-00212707 |
|
...PIP 21.00 002047+ GEN 50. 00027500 LB0:-00215143 |
|
...UNL 05.04 002053+ GEN 50. 00021500 LB0:-00213204 |
|
...ACD 03.00 002055+ GEN 50. 00042500 LB0:-00204235 |
|
...BOO 03.10 002061+ GEN 50. 00047200 LB0:-00204423 |
|
...CON 05.00 002063+ GEN 50. 00135600 LB0:-00205114 |
|
...ELI 04.03 002065+ GEN 50. 00032600 LB0:-00212341 |
|
...LOA 05.03 002067+ GEN 50. 00040000 LB0:-00207123 |
|
...MAG 03.00 002071+ GEN 50. 00037300 LB0:-00204153 |
|
...PSW 03.02 002073+ GEN 50. 00017500 LB0:-00212426 |
|
RHA OFL CPA CSR=176700 VEC=254 PRI=5 |
|
YLA OFL CPA CSR=177560 VEC=60 PRI=5 |
|
YZA OFL CPA CSR=160100 VEC=300 PRI=5 |
|
DLA OFL CPA CSR=174400 VEC=160 PRI=5 |
|
MSA OFL CPA CSR=172522 VEC=224 PRI=5 |
|
LPA OFL CPA CSR=177514 VEC=200 PRI=4 |
|
VF0: OFL DRIVER |
|
VF1: OFL DRIVER |
|
CO0: OFL DRIVER |
|
TT0: YLA0: OFL DRIVER |
|
TT1: YZA0: OFL DRIVER |
|
TT2: YZA1: OFL DRIVER |
|
TT3: YZA2: OFL DRIVER |
|
TT4: YZA3: OFL DRIVER |
|
TT5: YZA4: OFL DRIVER |
|
TT6: YZA5: OFL DRIVER |
|
TT7: YZA6: OFL DRIVER |
|
TT10: YZA7: OFL DRIVER |
|
VT0: OFL DRIVER |
|
RD0: ONL DRIVER |
|
DB0: RHA0: OFL DRIVER |
|
DB1: RHA1: OFL DRIVER |
|
DL0: DLA0: OFL DRIVER |
|
DL1: DLA1: OFL DRIVER |
|
MS0: MSA0: OFL DRIVER |
|
LP0: LPA0: OFL DRIVER |
|
NL0: OFL DRIVER |
|
POOL=1200:13464.:13464.:2013 |
|
>; |
|
>; When you are finished with SYSGEN, software boot in your target |
|
>; system. Set the date and time, and save the system without any |
|
>; switches to verify that the system is working. Then save the |
|
>; system again, this time with the /WB switch to make it hardware |
|
>; bootable. |
|
>; |
|
>; The optional SAVE switches are: |
|
>; |
|
>; /WB writes the boot block |
|
>; /SFILE="filename" uses "filename" as the startup file |
|
>; /MOU="mount-switches" specifies mount switches to be used |
|
>; when the system volume is mounted |
|
>; |
|
>; For example: |
|
>; |
|
>; >BOOT [1,54]RSX11M.SYS |
|
>; RSX-11M-PLUS V3.0 BL24 |
|
>; |
|
>; > |
|
>; TIM 19-APR-85 12:00:00 |
|
>; >SAV |
|
>; |
|
>; RSX-11M-PLUS V3.0 BL24 256.K System:"MJTOAD" |
|
>; >RED DB:=SY: |
|
>; >RED DB:=LB: |
|
>; >RED DB:=SP: |
|
>; >MOU DB:"RSX11MPBL24" |
|
>; >@DB:[1,2]STARTUP |
|
>; . |
|
>; . |
|
>; . |
|
>; >* Please enter time and date (HH:MM MM/DD/YY) [S]: ^Z |
|
>; >@ <EOF> |
|
>; >SAV /WB |
|
>; |
|
>; RSX-11M-PLUS V3.0 BL24 256.K System:"MJTOAD" |
|
>; >RED DB:=SY: |
|
>; >RED DB:=LB: |
|
>; >RED DB:=SP: |
|
>; >MOU DB:"RSX11MPBL24" |
|
>; >@DB:[1,2]STARTUP |
|
>; . |
|
>; . |
|
>; . |
|
>; >* Please enter time and date (HH:MM MM/DD/YY) [S]: 12:01 4/19/85 |
|
>; >TIME 12:01 4/19/85 |
|
>; >ACS SY:/BLKS=1024. |
|
>; >CON ONLINE ALL |
|
>; . |
|
>; . |
|
>; . |
|
>; >@ <EOF> |
|
>; >SET /UIC=[1,54] |
|
>; >PIP [2,54]*.*;*/DE |
|
>; > |
|
>; |
|
>; You may wish to edit [1,2]STARTUP.CMD and [1,2]QMGSTART.CMD |
|
>; to reflect your desired initialization operations. |
|
>; |
|
>SET /UIC=[200,200] |
|
>; |
|
>REM MACT0 |
|
>REM PIPT0 |
|
>REM LBRT0 |
|
>REM TKBT0 |
|
>REM VMRT0 |
|
>; |
|
>; End of SYSGEN |
|
>; |
|
>TIME |
|
01:23:24 20-JAN-19 |
|
>; |
|
>ASN = |
|
>; |
|
>@ <EOF> |
|
>set /uic=[1,1] |
|
>boot db0:[1,54] |
|
RSX-11M-PLUS V4.6 BL87 |
|
|
|
|
|
> |
|
set /uic=[1,1] |
|
>sav /wb |
|
|
|
|
|
RSX-11M-PLUS V4.6 BL87 1920.KW System:"RSX1 " |
|
>RED DB:=SY: |
|
>RED DB:=LB: |
|
>RED DB:=SP: |
|
>MOU DB0:"RSX11MPBL87" |
|
>@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-YYYY) [S]: 01:59 20-jan-2019 |
|
>TIME 01:59 20-jan-2019 |
|
>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 LP0:/SP/FL:2/LOWER/FO:0 |
|
>QUE BAP0:/BATCH |
|
>QUE LP0:/AS:PRINT |
|
>QUE BAP0:/AS:BATCH |
|
>@ <EOF> |
|
>run $shutup |
|
|
|
RSX-11M-PLUS Shut down program |
|
|
|
Enter minutes to wait before shutdown: |
|
Reason for shutdown (<CR> for none): |
|
OK to shutdown? [Y/N]: y |
|
All further logins are disabled |
|
|
|
2019-01-20 01:59 System is now shutting down -- RSX1 |
|
|
|
QUE /STO:QMG |
|
> |
|
STOP/ACCOUNTING SHUTUP |
|
01:59:45 SYSLOG -- 47. Exiting |
|
@LB:[1,2]SHUTUP |
|
> |
|
>VCP DISCONNECT /ALL |
|
>@ <EOF> |
|
> |
|
ELI /NOLOG |
|
> |
|
ACS DB0:/BLKS=0. |
|
ACS -- Checkpoint file now inactive |
|
> |
|
DMO DB0:/DEV/LOCK=V |
|
DMO -- System disk being dismounted |
|
DMO -- SYSTEM dismounted from DB0: *** Final dismount initiated *** |
|
01:59:47 *** DB0: -- Dismount complete |
|
> |
|
SHUTUP operation complete |
|
|
|
HALT instruction, PC: 126130 (CLRB @#177776) |
|
sim> |
