software

• Simh
• MAME / MESS
• Hercules

hardware

• Collection

resources

• Manuals
• Software
• ROMs
• How-to Guides

VAX-11/782

• Introduction
• Simulator
• Boot Flags
• Setting up the VAX-11/782
• Setting up the VAX-11/784
• Known Problems
• Downloads

---

The VAX-11/782 is a dual processor version of the VAX-11/780 and was introduced in 1982. Rather than a single machine containing 2 CPUs, the VAX-11/782 is actually two VAX-11/780 systems connected via an MA780 multi-port shared memory. The system operates in an asymmetric multiprocessor (ASMP) configuration where the primary CPU handles the process scheduling and I/O and the secondary is only used for additional computationally-intensive work. This is the configuration as supported by VAX/VMS for multi-processing however the MA780 multi-port shared memory can also be used for other user-defined purposes.

The diagram below shows a typical VAX-11/782 configuration

This diagram clearly demonstrates the asymmetric nature of the system whereby all I/O devices must be connected to the primary processor. The attached processor has to route all I/O requests through the primary which means that only certain types of workloads will benefit from this multi-processor configuration.

---

Simulator

There are various documents that describe the VAX-11/782 and the MA780 multi-port shared memory but unfortunately not all of them are available online.

• EK-MA780-TD - MA780 Technical Description (currently unavailable)
• MP-00826-00 - MA780 Field Maintenance Print Set (currently unavailable)
• EK-VAXV2-HB-002 - VAX Maintenance Handbook (VAX-11/780)
• AA-M543A-TE - VAX-11-782 User's Guide

The simulation has largely been based on the MA780 register descriptions on pages 235 to 253 of the VAX Maintenance Handbook and the setup information in the VAX-11-782 User's Guide.

The VAX-11/782 simulation is a minor variation of the existing Simh VAX-11/780. Apart from the addition of the MA780 devices the only major difference is that it has the ability to remap the physical memory pages on the MS780 and MA780. This is something that would normally be done by the PDP-11 console processor.

The VAX-11/782 simulation contains four MA780 subsystems, with the device names ma0, ma1, ma2 and ma3. Each device supports the following commands:

sim> set ma0 enable
sim> set ma0 disable

These commands enable or disable a specific MA780 subsystem. All MA780 subsystems are disabled by default.

sim> set ma0 256k
sim> set ma0 512k
sim> set ma0 768k
sim> set ma0 1m
sim> set ma0 1280k
sim> set ma0 1536k
sim> set ma0 1792k
sim> set ma0 2m

These commands set the size of the shared memory. The size can only be changed if the device is not attached. Changing the memory size will cause a reset of all VAX-11/782 devices so you should only use this command prior to booting.

sim> set ma0 port=1

This command sets the port or 'node' number of the local system. The range of this value is 0..3 and must be unique between each of the nodes attached to the same multi-port memory device.

sim> attach ma0 vaxmem

This command attaches the MA780 to a shared memory section named 'vaxmem'. If the section does not exist then it will be allocated otherwise the process will map to the existing section. If the section already exists then the memory size will be adjusted to match the size of the existing section.

The MA780 can still be used when it is not attached and it will behave like MS780 local memory.

---

Boot flags

There are 3 boot flags that can be passed to VMB in the R5 register which relate to the MA780.

;       11  RPB$V_MPM. (/R5:800)
;           Specifies that multi-port memory is to be used
;           for the total exec memory requirement.  No local
;           memory is to be used.  This is for tightly-coupled
;           multi-processing.  If the DIAG is also on, then
;           the diagnostic supervisor enters "AUTOTEST" mode.

This is that boot flag that must be used on the primary 11/782 system. The MA780 devices will be used exclusively and local MS780 memory is ignored. This means that the memory as seen by VMS must be setup through the ma0 - ma3 devices and the normal commands for setting the memory size (i.e. set cpu 8m) will have no effect.

;       12  RPB$V_USEMPM. (/R5:1000)
;           Specifies that multi-port memory should be used in
;           addition to local memory, as though both were one
;           single pool of pages.
;
;       14  RPB$V_FINDMEM. (/R5:4000)
;           Requests use of MA780 memory if MS780 is insufficient
;           for booting.  Used for 11/782 installations.

As the VAX-11/782 has to use the MA780 exclusively when operaring in it's multi-processor configuration they usually didn't have much local memory installed. When VAX/VMS is installed the primary processor has to be booted as a standard VAX-11/780 however there may not be enough local MS780 memory to complete the installation. To get around this problem these boot flags allow the shared memory to supplement local memory during the installation process.

---

Setting up the VAX-11/782

The VAX-11/782 is supported on any version of VAX/VMS from 3.0 to 4.7. For the example here we will install VMS 4.4. See the downloads section for the resources needed to complete this installation.

First you need to create a simh configuration file 'vax782.ini' that looks like this:

attach rq0 vms46sys.dsk
attach rq1 vms040stb.dsk
attach ts bb-bt05c-be_vms_v4_4_c1986.tap
attach cs vms044mup.rx1

set ma0 enable
set ma0 2m
attach ma0 vaxmem0

set ma1 enable
set ma1 2m
attach ma1 vaxmem1

• vms46sys.dsk will be created by Simh
• vms040stb.dsk is VAX/VMS V4.0 Standalone Backup on an RX33
• bb-bt05c-be_vms_v4_4_c1986.tap is the VAX/VMS V4.4 distribution tape
• vms044mup.rx1 is the VAX/VMS V4.4 mandatory update on an RX01

Two MA780 devices are configured here with 2MB of memory each. They are then attached to their own shared memory sections. You may wish to make additional changes to this configuration file to use a telnet console for example.

Run the VAX-11/782 simulator with this configuration file and boot from the standalone backup disk.

VAX 11/782 simulator V4.0-0 Beta
sim> b rq1

   VAX/VMS Version V4.0 15-SEP-1984 22:29


%BACKUP-I-IDENT, Stand-alone BACKUP V4.0; the date is 19-NOV-2024 09:20:29.40
$ BACKUP/IMAGE/INIT MSA0:REQUIRED./SAV DUA0: /LOG

%BACKUP-S-CREATED, created DUA0:[000000]000000.DIR;1
%BACKUP-S-CREATED, created DUA0:[000000]BACKUP.SYS;1
%BACKUP-S-CREATED, created DUA0:[000000]CONTIN.SYS;1
%BACKUP-S-CREATED, created DUA0:[000000]CORIMG.SYS;1
%BACKUP-S-CREATED, created DUA0:[000000]SYS0.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSCBI.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSERR.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSERR]ERRSNAP.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSEXE.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]BACKUP.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]BADBLOCK.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CLUSTRLOA.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CNDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CONFIGURE.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CONINTERR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]COPY.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CRDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CREATE.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CSP.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CVDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CWDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DBDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DCL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DDDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DELETE.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DIRECTORY.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DISMOUNT.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DLDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DMDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DQDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DRDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DUDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DXDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DYDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DZDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]ERRFMT.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]ERRSNAP.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]ESDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]ETDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]F11BXQP.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]FILESERV.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]FPEMUL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]INSTALL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]JOBCTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]LADRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]LCDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]LIDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]LOGINOUT.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]LPDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]MASK_IMAGE.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]MBXDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]MP.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]MSCP.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]MTAAACP.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]NODRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]NOTICE.TXT;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]OPCCRASH.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]OPCOM.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]PADRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]PAGEFILE.SYS;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]PBDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]PDDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]PUDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RENAME.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]REPLY.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]REQUEST.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RMS.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RMS.STB;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RUNDET.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RXDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SCSLOA.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SET.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SETP0.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SHOW.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SHUTDOWN.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SMGMAPTRM.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]STACONFIG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]STARTUP.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]STARTUP.INS;5
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SWAPFILE.SYS;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYS.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSBOOT.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSGEN.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSINIT.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA730.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA750.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA780.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA790.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA8NN.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA8SS.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOAUV1.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOAUV2.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOAWS1.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOAWS2.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOAWSD.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSUAF.DAT;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSUAF.RL2;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TERMTABLE.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TFDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TMDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TPU.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TSDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TTDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TUDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TYPE.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]VAXEMUL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]VAXVMSSYS.PAR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]VMB.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]VMOUNT.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]VMSHELP.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XADRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XDDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XEDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XFDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XGDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XMDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XQDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XWDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]YCDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]YFDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]YIDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSHLP.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSHLP]EXAMPLES.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSLIB.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]ADARTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]BASRTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]BASRTL2.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]CDDSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]COBRTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]CRFSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]DCLTABLES.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]DCXSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]DISMNTSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]DTKSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]EDTSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]ENCRYPSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]FORRTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]IMGDMP.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]LBRSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]LIBRTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]LIBRTL2.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]MOUNTSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]MTHRTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]PASRTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]PLIRTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]RPGRTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]SCNRTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]SCRSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]SECURESHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]SMGSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]SUMSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]TPU$CCTSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]TPUSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]TRACE.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]UISSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]UVMTHRTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]VAXCRTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]VAXCRTLG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]VMSRTL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSMAINT.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSMGR.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]SECAUDIT.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]SYCONFIG.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]SYSHUTDWN.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]SYSTARTUP.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]VMSIMAGES.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]VMSIMAGES.DAT;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSMSG.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]ADAMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]CLIUTLMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]DBGTBKMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]FILMNTMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]NETWRKMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]PASMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]PLIMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]PRGDEVMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]RPGMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]SCNMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]SHRIMGMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]SYSMGTMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]SYSMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]TPUMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]VAXCMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSTEST.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSUPD.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]BLISSREQ.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]CVTLICENSE.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]DECNET.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]DEVELOP.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]EXAMPLES.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]FILETOOLS.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]HELP.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]LIBRARY.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]MANAGER.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]MASK_IMAGE.CLD;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]MISCTOOLS.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]QUEUES.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]REQUIRED.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]SETDEFBOO.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]TEXTTOOLS.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]UETP.TLR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]VMSINSTAL.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]VMSINSTAL.FDL;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]VMSTAILOR.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]VMSUPDATE.COM;1
%BACKUP-S-CREATED, created DUA0:[000000]SYSEXE.DIR;1
%BACKUP-S-CREATED, created DUA0:[000000]VOLSET.SYS;1
%BACKUP-I-IDENT, Stand-alone BACKUP V4.0; the date is 19-NOV-2024 09:20:59.48
$ 

Now we boot from the newly created system disk to continue the installation process

sim> b rq0

   VAX/VMS Version  TK  09-Mar-1986 10:00


%%%%%%%%%%%  OPCOM  19-NOV-2024 09:21:35.29  %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1

Please enter the date and time (DD-MMM-YYYY HH:MM): 19-NOV-2024 09:21

Enter drive holding distribution kit (DDCU): MSA0:

%MOUNT-I-MOUNTED, VMS044 mounted on _MSA0:

Restoring library saveset.
%BACKUP-I-STARTVERIFY, starting verification pass

Restoring optional saveset.
%BACKUP-I-STARTVERIFY, starting verification pass

Now we will ask you for new passwords for the following accounts:
        SYSTEM, SYSTEST, FIELD



Enter new password for account SYSTEM: MANAGER

Re-enter the password for account SYSTEM for verification: MANAGER

%UAF-I-MDFYMSG, user record(s) updated


Enter new password for account SYSTEST: TESTING

Re-enter the password for account SYSTEST for verification: TESTING

%UAF-I-MDFYMSG, user record(s) updated


Enter new password for account FIELD: SERVICE

Re-enter the password for account FIELD for verification: SERVICE

%UAF-I-MDFYMSG, user record(s) updated

Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT
Ignore any "%SYSTEM-F-DUPIDENT, duplicate identifier" errors.
%UAF-I-RDBCREMSG, RIGHTSLIST.DAT created
%UAF-I-RDBADDMSGU, identifier DEFAULT value: [000200,000200] added to RIGHTSLIST.DAT
%UAF-I-RDBADDMSGU, identifier FIELD value: [000001,000010] added to RIGHTSLIST.DAT
%UAF-I-RDBADDMSGU, identifier SYSTEM value: [000001,000004] added to RIGHTSLIST.DAT
%UAF-I-RDBADDMSGU, identifier SYSTEST value: [000001,000007] added to RIGHTSLIST.DAT
%UAF-E-RDBADDERRU, unable to add SYSTEST_CLIG value: [000001,000007] to RIGHTSLIST.DAT
-SYSTEM-F-DUPIDENT, duplicate identifier
%UAF-I-NOMODS, no modifications made to system authorization file
%UAF-I-RDBDONEMSG, rights database modified

AUTOGEN computes the SYSGEN parameters for your configuration
and then reboots the system with the new parameters.

After the reboot, you may want to do one or more of the following tasks
(consult the Guide to VAX/VMS System Management and Daily Operations for
detailed information): 

- Delete SYS$SYSTEM:STARTUP.INS

- DECOMPRESS THE SYSTEM LIBRARIES - For space considerations, many of the system
libraries are shipped in a data compressed format.  If you have enough disk
space, you may decompress them for faster access. Use SYS$UPDATE:LIBDECOMP.COM
to data expand the libraries.  If you choose not to decompress these libraries
there will be a negative impact on the performance of the HELP and LINK
commands.

- APPLY THE MANDATORY UPDATE - The mandatory update for VMS V4.4 must be applied
as soon as possible.   You will be unable to install any layered products until
this update has been applied.


Running AUTOGEN -- Please wait.

%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
        You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
        You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
        You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%AUTOGEN-I-PAGEFILE, creating 30000 block page file.
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;1 extended
%AUTOGEN-I-SWAPFILE, creating 23000 block swap file.
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;1 extended
%AUTOGEN-I-DUMPFILE, creating 16388 block dump file.
%SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYSDUMP.DMP;1 created
%AUTOGEN-I-END, GENFILES phase has successfully completed.
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.

The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.

The system will automatically reboot after the shutdown and the
upgrade will be complete.



        SHUTDOWN -- Perform an Orderly System Shutdown


%SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check...
%SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed

%SHUTDOWN-I-OPERATOR, This terminal is now an operator's console.
%SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled.
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.
%JBC-E-JOBQUEDIS, system job queue manager is not running

SHUTDOWN message from user SYSTEM at  Batch   09:23:48The system will shut down in 0 minutes; back up soon.  Please log off.
Reboot system with AUTOGENerated parameters


%SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked.
%SHUTDOWN-I-STOPUSER, All user processes will now be stopped.
%SHUTDOWN-I-REMOVE, All installed images will now be removed.
%SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.


   VAX/VMS Version  TK  09-Mar-1986 10:00


%%%%%%%%%%%  OPCOM  19-NOV-2024 09:24:23.97  %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1

%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
  SYSTEM       job terminated at 19-NOV-2024 09:24:24.02


Username: SYSTEM
Password: MANAGER
        Welcome to VAX/VMS version  TK 

$

It's highly recommended at this point to install the mandatory update for VAX/VMS 4.4

$ RUN SYS$SYSTEM:SYSGEN

SYSGEN>  CONNECT CONSOLE
SYSGEN>  EXIT

$ @SYS$UPDATE:VMSINSTAL VMSMUP044


        VAX/VMS Software Product Installation Procedure  TK     


It is 19-NOV-2024 at 09:25.
Enter a question mark (?) at any time for help.

* Are you satisfied with the backup of your system disk [YES]? ↵
* Where will the distribution volumes be mounted: CSA1:

%DCL-I-ALLOC, _CSA1: allocated

Please mount the first volume of the set on CSA1:.
* Are you ready? Y

%MOUNT-I-MOUNTED, VMSMUP044    mounted on _CSA1:

The following products will be processed:

  VMSMUP V4.4


        Beginning installation of VMSMUP V4.4 at 09:25
%VMSINSTAL-I-RESTORE, Restoring product saveset A...


This kit contains the Mandatory Update for VMS V4.4



        1)  Apply all fixes to the system
        2)  Create a file with the descriptions of all fixes
        3)  Both of the above

* What would you like to do [3]: ↵

%VMSMUP-I-FIXDESC, The fixes are described in SYS$UPDATE:VMSMUP044.TXT
* Do you want to purge files replaced by this installation [YES]? ↵

%MOUNT-I-MOUNTED, VMSMUP044    mounted on _CSA1:

 1) CLUSTRLOA (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-NOGBL, some or all global symbols not accessible
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]CLUSTRLOA.EXE;1

 2) COBRTL (miscellaneous fix)

 3) COBRTL (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]COBRTL.EXE;1

 4) DSDRIVER (miscellaneous fix)

 5) ETDRIVER (new image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]ETDRIVER.EXE;3

 6) JOBCTL (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-NOGBL, some or all global symbols not accessible
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]JOBCTL.EXE;1
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]JOBCTL.EXE;1

 7) LBRSHR (new image)

 8) LOGINOUT (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-NOGBL, some or all global symbols not accessible
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]LOGINOUT.EXE;1

 9) NETACP (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-NOGBL, some or all global symbols not accessible
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]NETACP.EXE;1
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]NETACP.EXE;1
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]NETACP.EXE;1

10) NETCONFIG (edit text file)

11) NETDRIVER (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-NOGBL, some or all global symbols not accessible
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]NETDRIVER.EXE;1

12) NODRIVER (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]NODRIVER.EXE;1

13) RMS (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-NOGBL, some or all global symbols not accessible
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]RMS.EXE;1

14) SYS (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-NOGBL, some or all global symbols not accessible
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]SYS.EXE;1

15) SYSLOA8NN (new image)

16) SYSLOA8SS (new image)

17) TPUSHR (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]TPUSHR.EXE;1

18) TTDRIVER (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]TTDRIVER.EXE;1

19) UETUNAS00 (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-NOGBL, some or all global symbols not accessible
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP044]UETUNAS00.EXE;1

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

        Installation of VMSMUP V4.4 completed at 09:26
%VMSINSTAL-I-REBOOT, This product requires that the system be rebooted.
Please mount the console volume on CSA1:.
* Are you ready? Y

%MOUNT-I-MOUNTED, CONSOLE      mounted on _CSA1:


        SHUTDOWN -- Perform an Orderly System Shutdown


%SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check...
%SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed

%SHUTDOWN-I-OPERATOR, This terminal is now an operator's console.
%%%%%%%%%%%  OPCOM  19-NOV-2024 09:26:39.73  %%%%%%%%%%%
Operator status for operator _OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11,
OPER12

%SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled.
%SET-I-INTSET, login interactive limit = 0, current interactive value = 1
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.
%JBC-E-JOBQUEDIS, system job queue manager is not running

SHUTDOWN message from user SYSTEM at _OPA0:   09:26:39The system will shut down in 0 minutes; back up soon.  Please log off.
Reboot after VMSMUP V4.4 installation.

1 terminal has been notified.

%SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked.
%SHUTDOWN-I-STOPUSER, All user processes will now be stopped.
%SHUTDOWN-I-REMOVE, All installed images will now be removed.
%SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.
%SHUTDOWN-I-DISMOUNTDEV, Dismounting device _CSA1:.
%%%%%%%%%%%  OPCOM  19-NOV-2024 09:26:40.08  %%%%%%%%%%%
Message from user SYSTEM
_OPA0:, The system shutdown was requested by the operator.

%%%%%%%%%%%  OPCOM  19-NOV-2024 09:26:40.09  %%%%%%%%%%%
Logfile was closed by operator _OPA0:
Logfile was SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1

%%%%%%%%%%%  OPCOM  19-NOV-2024 09:26:40.11  %%%%%%%%%%%
Operator _OPA0: has been disabled, username SYSTEM


SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM

The installation of VAX/VMS is now complete.

The VAX-11/782 User's Guide now directs us to boot VAX/VMS and create two RX01 floppy disks for the primary and secondary console processors. These will contain command files which will map the MA780 devices into low memory and move any MS780 devices to upper memory. As the PDP-11 console processor is not present in simh we can skip this step. The necessary logic for remapping the memory boards and setting up the registers prior to boot is handled automatically.

To start VAX/VMS for multiprocessing we need to use one of the R5 boot flags mentioned earlier to tell the operating system to use the MA780 exclusively (and to ignore any local MS780 memory). This means that within simh the usual commands for setting the memory size e.g. set cpu 8m will have no effect. The memory size as seen by VMS is determined by the sum of the size of all enabled MA780 devices.

sim> boot rq0 /r5:800


   VAX/VMS Version V4.4 09-Mar-1986 10:00


%%%%%%%%%%%  OPCOM  19-NOV-2024 09:27:20.38  %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2

%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
  SYSTEM       job terminated at 19-NOV-2024 09:27:20.43


Username: SYSTEM
Password: MANAGER
        Welcome to VAX/VMS version V4.4
    Last interactive login on Sunday, 19-NOV-2024 09:24
$

If we try to show the state of the attached processor at this stage VAX/VMS will tell us that the multi-processing code has not been loaded.

$ SHOW CPU
%SYSTEM-F-DEVOFFLINE, device is not in configuration or not available
$

The multi-processing code can be loaded with the following command

$ START/CPU

Now if we show the state of the attached processor again we can see that VAX/VMS is waiting for the attached processor to boot.

$ SHOW CPU

        Attached processor is in the INITIALIZE state.
$

Now we need to start another intance of the VAX-11/782 simulator with the following configuration file

set ma0 enable
set ma0 port=1
attach ma0 vax0

Now we boot from the lowest numbered MA780 device

sim> boot ma0

There will be no console output. We can check the state of the attached processor from the primary

$ SHOW CPU

        Attached processor is in the IDLE state.
$

That's it, both processors are running.

---

Setting up the VAX-11/784

VAX/VMS only supports multi-processing with two VAX-11/780s connected to the MA780 multi-port shared memory. You can however connect up to four systems and use the shared memory for user-defined purposes. This configuration is supported on any version of VMS from 2.0 to 7.3. To setup the MA780 you use the SHARE command from within SYSGEN.

Note: The VAX-11/784 configuration is not currently working

---

Known Problems

The VAX architecture provides a number of 'interlocked' instructions which are for performing atomic operations. These instructions are:

• ADAWI
• BBSSI
• BBCCI
• INSQHI
• INSQTI
• REMQHI
• REMQTI

Special SBI bus cycles are use to implement the locking for these instructions and the MA780 is meant to recognise these bus cycles and lock access to the shared memory for other nodes until the operation is complete. These interlocked read bus cycles are not currently implemented so there is the potential for race conditions to occur between the processors attached to the MA780. This issue will hopefully be addressed in a future version.

---

Downloads

VAX-11/782 simulator downloads

File	Type	Date
vax782.zip	Source (Github)	-
vax782-win32.zip	Executable (Win32)	19/05/2017

Resources for the VAX-11/782 setup guide

File	Description	Format
vms040stb.rx3.bz2	VAX/VMS V4.0 Standalone Backup	RX33 Disk Image
bb-bt05c-be_vms_v4_4_c1986.tap.bz2	VAX/VMS V4.4 Distribution Tape	Simh TAP
vms044mup.rx1.bz2	VAX/VMS V4.4 Mandatory Update	RX01 Disk Image

---

9track.net